|
Subjunctive posted:Why is that? I came across something else that said that recently, but didn't say what problem it avoided. I'm just getting back into Android development, so these sorts of gathered lore are interesting to me. One reason is that the R class gets generated in your application's package name's package, so if you want to use it in a class that's in a different package, you need to explicitly import it.
|
#
¿
Oct 30, 2015 02:19
|
|
|
|
| # ¿ Apr 29, 2024 04:37 |
|
|
speng31b posted:Anyone done any testing on Android N and found any major pitfalls? Been in a crunch-time project and haven't had a chance to check it out as much as I'd like. If you're using the NDK, linking against or dlopening private libraries will stop working as soon as your application has a target SDK level of N or greater.
|
|
#
¿
Mar 13, 2016 06:35
|
|
|
Lutha Mahtin posted:one of them implies that the poster only uses 1970s text editors without any kind of IDE functionality "my editor generates the meaningless boilerplate" is not a very compelling argument
|
|
#
¿
May 31, 2017 07:40
|
|
|
Vesi posted:UDP handles firewalls/NAT very inconsistently This is especially bad, because lots of mobile networks are using carrier NAT now.
|
|
#
¿
Jul 12, 2017 05:00
|
|
|
You're sending imminent forward collision alerts via UDP?
|
|
#
¿
Jul 14, 2017 00:38
|
|
|
Popete posted:Alright I got a real weird issue I can't seem to track. We ship embedded Android products out from our factory and everything is fine, customer recieves it and complains the startup application isn't launching. I'm digging into the issue and from ADB it looks like PackageManager is failing to parse the packages.xml file located at /data/system/packages.xml. I'm not entirely sure what the xml file is but it looks to be built on boot from all packages that comprise the system and I don't know why PackageManager is failing to parse this xml on some boards. On a good board the packages.xml file looks identical (according to diff) except occasionally one line is changed near the top of the file. Are you seriously shipping a froyo device in 2017?
|
|
#
¿
Sep 6, 2017 08:59
|
|
|
Volmarias posted:x86 is mostly ignorable too right now afaik. armv5 has been dead for like a decade now, and mips never existed. There are a few million mips devices in China, but it's a different mips ABI than the one in the NDK. Note that armv7 doesn't imply NEON or the idiv instruction (thanks nvidia). x86 is alive in chromebooks, the nexus player, and emulators. I'm not sure whether ChromeOS supports 64-bit, but the nexus player definitely does not.
|
|
#
¿
Oct 2, 2017 19:09
|
|
|
netcat posted:Is it possible to build Android with OEM unlocking enabled and dm-verity disabled by default? That does not involve hacking the uboot source and figuring out whatever magic the OEM unlocking service does? Or is it vendor specific? bootloading locking is orthogonal to the build, -eng builds have verity disabled by default
|
|
#
¿
Sep 25, 2019 01:55
|
|
|
|
| # ¿ Apr 29, 2024 04:37 |
|
|
Small White Dragon posted:Okay actual question. Firebase Test Lab
|
|
#
¿
Jul 12, 2023 05:31
|
|