|
Is AVD corruption a common thing, and anyone have any tips to spot when it's happened? Just spent an hour troubleshooting why data wasn't showing up in views/why the app started crashing with no stacktrace and just a runtime exception in a thread, then I made a new AVD and oh hey, everything's working fine again. The broken one seemed completely fine though, I thought the new gradle plugin had messed things up
|
# ? Sep 4, 2017 19:56 |
|
|
# ? Jun 8, 2024 08:38 |
|
.
kitten smoothie fucked around with this message at 02:39 on Dec 3, 2022 |
# ? Sep 4, 2017 20:00 |
|
Well I had an issue resuming the computer from sleep, so I had to hard reboot it and the emulator was probably running, so that might be what did it (why it would persist after a restart though... 🤔) Definitely not Instant Run, this is after multiple Cleans and Rebuilds, running git bisect to find out what broke it, trying to downgrade the gradle plugin in case that update messed something up, uninstalling the app, multiple debugging attempts... Seems like a platform issue honestly. At first some list views were either empty or not showing up, then it started crashing immediately with that not at all helpful error. Using the debugger to break on exceptions got some View Stub missing class exceptions, then the last one left the debugger in a waiting state forever. Feels like something got corrupted, but in a really awkward to diagnose way. Maybe I just got super unlucky!
|
# ? Sep 5, 2017 01:37 |
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. Good board: <last-platform-version internal="8" external="8" /> Bad board: <last-platform-version internal="8" external="0" /> I'm not %100 that there is a correlation between that line and a board being bad but I'm wondering if anyone here can shed some light on the packages.xml file and specifically that entry for <last-platform-version>. Any thoughts on why it's choking parsing this xml file? It happens consistently on every boot once the board goes bad but only once the boards reach our customer does it happen, we cannot get our boards in factory or on cycle testing to get into this state. Here is an ADB capture. Popete fucked around with this message at 23:08 on Sep 5, 2017 |
|
# ? Sep 5, 2017 23:05 |
|
Have you asked the customer to factory reset as a short term workaround, and does that work? Can the customer send a board back overnight for analysis, or is it a center car console or something
|
# ? Sep 6, 2017 00:12 |
Volmarias posted:Have you asked the customer to factory reset as a short term workaround, and does that work? The customer has sent us back dozens of these units, it has only occurred after we sent them and as they install it in the plane roughly half the units are stuck in this boot loop. Digging further in, Package Manager is definitely failing to start because of this parse error but I can't for the life of me figure out why it thinks the file is ending prematurely the good/bad files look the same. and I've never even touched or known about this xml file the entire time I've been on this project. We've asked the customers what they are doing with the unit's prior to installation and it doesn't seem like anything different than what our factory does as part of testing. I'm starting to think it's an eMMC corruption issue but I don't know how to confirm that yet. Reflashing Android onto the eMMC fixes the issue but it can still happen after we send it back so we need a more permanent solution.
|
|
# ? Sep 6, 2017 00:34 |
|
Could it just be bad/counterfeit eMMC? Cosmic rays from the planes being further in the atmosphere? If you're a bad person you could always hardcode something in the parsing code to more... Permanently work around this.
|
# ? Sep 6, 2017 00:56 |
Volmarias posted:Could it just be bad/counterfeit eMMC? Cosmic rays from the planes being further in the atmosphere? I'm very tempted to do that latter. MMC is good we source it from Micron and have worked with them on some other corruption issues in the past. I'm hoping I can blame it on hardware but it's probably something I'm doing that is very stupid.
|
|
# ? Sep 6, 2017 02:16 |
|
Seriously tho if you're doing vehicle stuff then me and u are now Postin Pals
|
# ? Sep 6, 2017 04:00 |
FAT32 SHAMER posted:Seriously tho if you're doing vehicle stuff then me and u are now Postin Pals Using Android in embedded systems is all the rage these days, customers love having a slick interface that everyone already knows how to use to interface with there in-flight entertainment or seat controls. Android is nice but there are times where it is an ungodly pain in the rear end and I wish we would have just gone with a more traditional OS. Having to mess with HAL's and frameworks is a mess that I'm not very good at coming from a micro controller bare metal coding perspective. Are you doing embedded Android stuff, my Postin Pal?
|
|
# ? Sep 6, 2017 04:43 |
|
Popete posted:Using Android in embedded systems is all the rage these days, customers love having a slick interface that everyone already knows how to use to interface with there in-flight entertainment or seat controls. Android is nice but there are times where it is an ungodly pain in the rear end and I wish we would have just gone with a more traditional OS. Having to mess with HAL's and frameworks is a mess that I'm not very good at coming from a micro controller bare metal coding perspective. Nah the lowest level I got to was loving around with the HVAC control system and trying to figure out how it talked to the CAN/LIN buses lol Based on my experience with OEMs building a full OS in house I'll put up with androids quirks any day
|
# ? Sep 6, 2017 04:52 |
|
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 |
b0lt posted:Are you seriously shipping a froyo device in 2017? This device is for a specific customer that was designed for them, it's been in production for years now and there is no way we'd spend the effort to upgrade Android. But yes it's using ancient Android technology and it's a terrible pain in the rear end.
|
|
# ? Sep 6, 2017 15:39 |
|
b0lt posted:Are you seriously shipping a froyo device in 2017? android dot text ok here's a question regarding views and dynamically adding textviews into them. I'm building a sidebar that will load in categories from a Firebase, and when an item is clicked it will show subitems, like this (except without the radio buttons) It has three columns: categoryName, completed, and score. When you click anywhere on that header it will turn grey to show that it is selected and show the subcategories and if they're completed or not. I was attempting to do this by hiding a view containing the subcategories and unhiding it with an onClick of the view like this Java code:
I made a layout specifically for the categories here: XML code:
XML code:
EDIT: ok turns out an ELV will solve all of my problems and i'm a gigantic dummy FAT32 SHAMER fucked around with this message at 20:16 on Sep 6, 2017 |
# ? Sep 6, 2017 18:47 |
|
I'm interested in getting into Android dev, but I don't have an Android phone. I have an iPhone but no Mac, and rather than throw any more money into the Apple ecosystem, I was thinking of maybe getting a cheap Android phone for testing purposes. Would something like this be ok, or is it more preferable to get something standard like a Nexus, Samsung phone, etc? How far along can I get in Android dev without a phone? From some searching online, it looks like you'd only really need it to test your apps out in the actual environment. Would it be right to say that you can still do a lot of development/testing otherwise without one? Sorry if this has been (likely) answered before, couldn't find anything in the OP about it. Edit: Also, are there any Coursera/edX/etc. courses that people recommend for Android development? There seem to be about a dozen different ones, if anyone has any positive experience with a particular one, it'd be helpful to know! reversefungi fucked around with this message at 20:41 on Sep 12, 2017 |
# ? Sep 12, 2017 20:37 |
|
I dont use a physical device for android, just the emulator. Do that, unless your PC is slow to begin with also, can anyone explain why the hell this is happening when i click on an EditText that is inside an ExpandableListView? https://giant.gfycat.com/GenuineUnluckyHyrax.gifv To me it looks like the toolbar is extending over everything, but maybe it's a weird quirk that has a quick fix? FAT32 SHAMER fucked around with this message at 21:13 on Sep 12, 2017 |
# ? Sep 12, 2017 21:09 |
|
Tried looking in the Hierarchy Viewer for where the views went?
|
# ? Sep 13, 2017 02:27 |
|
I'd recommend getting an actual device if your app is going to touch any real hardware aspect like telephony, location, etc. Any device that has Play on it is likely fine. If you're just loving around an emulator is fine short term. Also, not sure if it's because I'm on mobile, but I'm getting access denied for that giphy link
|
# ? Sep 13, 2017 03:38 |
|
kitten smoothie posted:Tried looking in the Hierarchy Viewer for where the views went? How would i look to see where the views went? Heres what it looks like (EditText is highlighted)
|
# ? Sep 13, 2017 16:39 |
|
Tools -> Android -> Layout inspector may help. It's not doing something weird related to the input type is it? On phones TextViews can do this weird fullscreen thing unless you set flagNoExtractUi on them. This shouldn't happen on a tablet though.
|
# ? Sep 13, 2017 17:26 |
|
Tunga posted:It's not doing something weird related to the input type is it? On phones TextViews can do this weird fullscreen thing unless you set flagNoExtractUi on them. This shouldn't happen on a tablet though. Hmm, I don't think so. I'll try the flagNoExtractUi thing and see what happens, but I would assume that if they were expanding, the background would be the colour of the TextView instead of something else edit: also for some reason when i click on the edit text then click out of it I can no longer click on one of the boxes (or at least, it makes the click sound but it doesnt change the color to highlighted) Edit two: I think the issue is going to be resolved if I convert my activities to fragments, based on what I'm reading Ugh FAT32 SHAMER fucked around with this message at 19:23 on Sep 13, 2017 |
# ? Sep 13, 2017 18:18 |
|
FAT32 SHAMER posted:How would i look to see where the views went? Heres what it looks like (EditText is highlighted) The view properties tab is helpful for looking at layout dimensions and such for a given view. https://developer.android.com/studio/profile/hierarchy-viewer.html Also I usually like to start at the target view and walk my way back up the hierarchy in the preview to see where things got wonky. FAT32 SHAMER posted:Edit two: I think the issue is going to be resolved if I convert my activities to fragments, based on what I'm reading Mind sharing where you're reading that? I'm thinking this is a red herring and you're just going to hate yourself by adding fragments into the mix.
|
# ? Sep 13, 2017 20:52 |
|
After talking with FAT32 SHAME I came in here to see what bad advice looks like and boy, I was not let down. How can anyone be an Android developer and not embrace fragments? They single-handedly enable the creation of responsive apps that can adapt to handle all screen sizes, from Android Wear up through to Android TV on a 4K TV. To load a fragment? Just get FragmentManager in the mix and point it to a FrameLayout in your activity's layout: Java code:
Java code:
Java code:
Fragments are the backbone of Android apps and have been for quite some time. Back then these concepts were a little challenging to wrap my head around, and there was a learning curve no doubt, but once you stop listening to bad advice and take the time to learn about and include Fragments in your app, you'll be setting yourself up to easily handle all kinds of weird form factors down the line. IAmKale fucked around with this message at 00:33 on Sep 14, 2017 |
# ? Sep 14, 2017 00:31 |
|
You can still build activities and not have to worry about the device's screen size, i'm more concerned given the complexity of the app that i'm building vs the pain in the rear end ratio of rewriting my activities to fragments and debugging this weird edittext issue. I could rewrite it in fragments and still have the two bugs that i'm currently experiencing, which will be hard to justify as i slink farther behind
|
# ? Sep 14, 2017 00:57 |
|
kitten smoothie posted:The view properties tab is helpful for looking at layout dimensions and such for a given view. This is the ActionBar before clicking on the EditText After: For some reason it's expanding the height to 996 even though I've set android:maxHeight="?attr/ActionBarSize" Here is the first view that gets wonky And to the left of the red line/arrow here is where it continues to be wonky, all the way to the root of all the views I'm currently looking at my inflation methods in my BaseActivity that I wrote so I dont have to write so much boilerplate and other activities can inherit from, so fingers crossed I find the issue. I wonder if my CustomExpandableListAdapter inflaters are loving something up with the inflation of the ActionBar FAT32 SHAMER fucked around with this message at 13:06 on Sep 14, 2017 |
# ? Sep 14, 2017 13:00 |
|
TURNS OUT ALL I HAD TO DO WAS CHANGE THE MANIFEST TO adjustNothing THANK THE GODS
|
# ? Sep 14, 2017 13:32 |
|
Anyone have any idea why an ExpandedListView expands and collapses fine with a textview in it, but when i add a widget.Switch it no longer expands? I'm assuming its something with the layout inflater
|
# ? Sep 19, 2017 21:45 |
|
Anyone know if it's possible to theme or influence the look of spelling popups? Or what's responsible for them? The kind where you spell a word wrong, it gets underlined in red, and then you can tap on it to get some suggestions Someone's got that going on, and there are a lot of reports of similar fuckery with Samsungs thanks to a recent update, but that one looks like a weirdly faded light theme and everyone else is complaining about dark themes. But it would be good to be able to force a dark theme on that popup anyway - it looks fine on my device but it's still using a light theme. It'd be nice to make it dark to match the app
|
# ? Sep 27, 2017 16:04 |
|
Hello. I'm looking for statistics/some reference on what ABI (armeabi, armeabi-v7a, arm64-v8a, x86, x86_64, mips, mips64) android phones use, preferably a percentage. armeabi (arm v5+) and mips aren't used at all in todays market I guess?
|
# ? Oct 2, 2017 12:45 |
|
x86 is mostly ignorable too right now afaik.
|
# ? Oct 2, 2017 14:23 |
|
Support for the armv5 arch went away with KitKat so minSdkVersion 19 and you're good there.
|
# ? Oct 2, 2017 15:38 |
|
Thanks. How about mips?
|
# ? Oct 2, 2017 19:09 |
|
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 |
|
Also if there is any reference to this I would be grateful. Doing some research
|
# ? Oct 2, 2017 19:12 |
|
b0lt posted: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). Great info. Thanks a bunch.
|
# ? Oct 2, 2017 19:18 |
|
I know this is a longshot, but does anyone have experience with building QT QML for android armv7? QT has issues with keeping their build tools up-to-date with the latest versions of Android but now I'm not even able to build with older versions of the android sdk and none of the ideas from the official forums have helped. Here's the error I'm getting: quote:Android build SDK not defined. Check Android settings.
|
# ? Oct 12, 2017 15:52 |
|
So with RecyclerView being encouraged to be used instead of ListViews, did they bother to update ExpandableListView? I discovered the beauty of using FirebaseUI's FirebaseRecyclerAdapter to build my RecyclerViews and I would really like to uncomplicate my wicked complicated ExpandableListViews
|
# ? Nov 20, 2017 08:45 |
|
FAT32 SHAMER posted:So with RecyclerView being encouraged to be used instead of ListViews, did they bother to update ExpandableListView?
|
# ? Nov 20, 2017 09:29 |
|
Tunga posted:I've literally never used an ExpandingListView but I'd have thought you could recreate that behaviour with a RecyclerView fairly easily. Just have a view with whatever expanding behaviour that you want and put a bunch of them in a RecyclerView. It looks like there's an open source thingo to do it, but I was trying to avoid needing to deal with needing to write custom Firebase code into the adapter since I'm pressed for time. edit: i guess I could look at the source code of the FirebaseUI.FirebaseRecyclerAdapter and figure it out from there. My dumbass PM told a customer that a six month app would be done in 4.5 when 6 months was best case, which means i need to have a working demo by december 8th lol FAT32 SHAMER fucked around with this message at 19:39 on Nov 20, 2017 |
# ? Nov 20, 2017 19:35 |
|
|
# ? Jun 8, 2024 08:38 |
|
FAT32 SHAMER posted:My dumbass PM told a customer that a six month app would be done in 4.5 when 6 months was best case, which means i need to have a working demo by december 8th lol
|
# ? Nov 20, 2017 20:19 |