Google Play Apps & YouTube Force close after last update. {Solved!} - Android Q&A, Help & Troubleshooting
I like many other have been experiencing Force closes on Google Play Music, Movies, and YouTube after the latest updates on ICS based roms. I have seen people report experiencing this problem on Stock, Liquid, AOKP, and CM9 on various devices. I myself have wiped data and even tried it on a completely fresh rom install from what I could tell there were no files on my SD card generated from previous versions of Google Play Music that would cause the problem. On my regular rom I uninstalled and wiped any existence of the old version multiple times. When I place the widget on my home screen it'll shuffle and play through my locally stored music on my sd card (not pinned music actually music I copied my self). It seems to be wanting to display an element but that it doesn't exist so it crashes.
I reported the crash inside the Stack trace it includes the error:
java.lang.RuntimeException: Unable to start activity ComponentInfo{com.google.android.music.activitymanagement.TopLevelActivity}: android.view.InflateException: Binary XML file line #6: Error inflating class android.app.MediaRouteButton
Here is a logcat for the Google Play Music FC as well http://pastebin.com/VP2cSmN1 It seems to be the same exact bug that causes YouTube to crash although the Play Movies is a slightly different but similar bug from what I can tell.
I think more people are needed so that this bug is noticed and fixed. I created a thread on the Google Support forums here I encourage everyone that is having this problem to make a post so that it is noticed and fixed.
https://productforums.google.com/forum/#!msg/mobile/a6u2tK6a49g/-Juju-8C9vQJ
Please post in this thread if you are having this problem or if you have a solution to the problem. Now obviously the easiest solution would be for Google to update all the apps with a fix but possibly the problem could lie with the individual custom roms. Any information that anyone has on these issues would be welcome and needed to get this problem fixed.
EDIT: Here is the old Google Play Music APK to downgrade. http://forum.xda-developers.com/showthread.php?t=1533816
EDIT: After a little research I found this in the documentation for Android and apparently it's a class that is only found in Jelly Bean which brings me to the question why is it trying to use it on an ICS rom?
http://developer.android.com/reference/android/app/MediaRouteButton.html
EDIT: Raeled found out if you remove the res/layout-v16 folder from the apk file the apps no longer force close. The Movies app had an additional res/menu-v16 folder I had to remove. Keep in mind I don't know what side effects this will have on the apps but so far from what I have seen they work fine however I haven't rented any movies. Also because these are modified with an APKTool the signature was broken so you will have to uninstall your older versions to use them and I don't think you will be able to install any updates from the Google Play Store since the signature won't match. Anyways at least a solution until Google can fix the problem or our custom rom developers can find what causes the apps to want to use the Level 16 API.
EDIT: If you're a rom developer you can fix this problem in your rom by applying this change and recompiling from source. Explanations of why you need to do this can be found below.
https://github.com/aospX/platform_build/commit/a34ffcecc7c237ac9c9e263984f6a74d3a7c3831
I'm on AOKP and having the same issue. Would very much appreciate a fix :fingers-crossed:
Thanks for posting hopefully we get more attention to this issue!
I am using EOS ICS (4.0.4) on my Xoom 3G and aospx ICS on my Desire HD and was experiencing the FC's on both of them.
Have been doing some experimenting on altering the APK to get it to work on my device. I've been using APKTool to remove the "\res\layout-v16" folder from the APK. That seemed to do the trick and the modified app seemed to run fine on both the devices.
This raises the question for me why "layout-v16" would get used at all in the first place as my limited Android knowledge tells me it should not be used on API 15 (4.0.4).
I'm not completely sure what this all means but to me it looks like the devices are telling the apps that it is running on Jelly Bean while it is actually not.
Would you be able to post your modified apk files?
EDIT: I was able to do it however if you know how to do it without breaking signatures so that they can just update over the other apps that would be great.
Altering the APK without breaking the sign should not be possible. Even if it was we'd probably need to "fix" every new version anyways.
I have been looking in the android documentation and the resource should indeed not be used according to the specs on the Android development website.
To test further i have created a simple APK file (attached) that will print out the current API level. It also has to "res\layout" and a "res\layout-v16". When i run it on my device it will (just like music apk) select the v16 resource while the API level is 15. When i ask the API level using code it correctly reports 15.
Also changed folder to "res\layout-v17" quick just for a test but then the devices didn't pick this resource. So it will correctly skip API 17 content
So it seems the system does know it's API 15 but will still get API 16 resources.
If the case is that the problem is in the custom roms and the official ICS roms do not have this problem i think the change that Google is gonna fix this is pretty low.
Raeled said:
Altering the APK without breaking the sign should not be possible. Even if it was we'd probably need to "fix" every new version anyways.
I have been looking in the android documentation and the resource should indeed not be used according to the specs on the Android development website.
To test further i have created a simple APK file (attached) that will print out the current API level. It also has to "res\layout" and a "res\layout-v16". When i run it on my device it will (just like music apk) select the v16 resource while the API level is 15. When i ask the API level using code it correctly reports 15.
Also changed folder to "res\layout-v17" quick just for a test but then the devices didn't pick this resource. So it will correctly skip API 17 content
So it seems the system does know it's API 15 but will still get API 16 resources.
If the case is that the problem is in the custom roms and the official ICS roms do not have this problem i think the change that Google is gonna fix this is pretty low.
Click to expand...
Click to collapse
Yeah basically the Google Guy basically said our custom rom people need to fix it which is probably true however in my mind they could just as easily make a separate ICS APK like they have a separate APK for Gingerbread not a hard thing to do. But I hope that you're able to find the root of this problem I don't really have enough experience with this to know how to solve it in the rom. But you are saying that if there is API 16 material in the Apps it will pick it up and use it no matter what app it is?
I've used the android SDK to create 2 ICS Virtual devices. (4.0: API 14 and 4.0.3: API 15). These devices resolved the resources as they where supposed to do. After that i installed the Google Play Music app on them and also those worked perfectly fine.
The change that google is gonna fix this is next to none. The APK is not in error here. If they do this fix then they'd be saying that the specs are "more like guidelines"
And yes, this problem will spread to every app that will use API 16 only functionality in an API 16 only resource.
Yeah I've pretty much come to the conclusion that there is something wrong with the actual roms that need to be fixed by our developers! Just the root of the problem needs to be found.
The following are speculations as i messed up my Xoom by testing it. So use caution when trying to do what i did.
After some exploration in the Android source i found that the resource manager (the component that is responsible for loading the "res\layout", a.o.) is initialized not by using the "Build.Version.SDK_INT" (this has the correct value of 15), but by another property "Build.Version.RESOURCES_SDK_INT". This can be found in the source at: "\core\java\android\content\pm\PackageParser.java" (line 497 & 712).
Moving to source at "\core\java\android\os\Build.java" (line 120) we find out that "RESOURCES_SDK_INT" is based on "SDK_INT" but adds +1 if "CODENAME" is not equal to the value "RES". A few lines up we see that codename is read from the "ro.build.version.codename" key in the "build.prop" file. In the roms i use this value is "AOSP" so this means the resource sdk version gets +1 and will start to prefer Jelly Bean resources.
I tried to modify my "build.prop" file but this caused my xoom to not get past the boot animation. So once more: be carefull
doesn't this mean it should be 15 instead of aosp? This other rom theirs has the value of REL they claim not to have the same issue we are having but I can't confirm this.
Oh by changing this for whatever reason it thought apps weren't there and decided to wipe a bunch of the app data... I just backed up the system so that was awesome!
Sent from my ThunderBolt using Tapatalk 2
Link_of_Hyrule said:
doesn't this mean it should be 15 instead of aosp?
Sent from my ThunderBolt using Tapatalk 2
Click to expand...
Click to collapse
The "ro.build.platform.codename" is automatically set by the flag PLATFORM_VERSION_CODENAME in build/core/version_defaults.mk when compiling from source..Which =AOSP stands for development build and REL is release build. But by changing PLATFORM_VERSION_CODENAME := REL this does in fact fix this issue as Raeled suspected (tested by installing latest Google Play Music and latest YouTube, both work fine now.. )..
https://github.com/aospX/platform_build/commit/a34ffcecc7c237ac9c9e263984f6a74d3a7c3831
thanks Raeled
But it requires recompiling the entire rom from source?
existz said:
The "ro.build.platform.codename" is automatically set by the flag PLATFORM_VERSION_CODENAME in build/core/version_defaults.mk when compiling from source..Which =AOSP stands for development build and REL is release build. But by changing PLATFORM_VERSION_CODENAME := REL this does in fact fix this issue as Raeled suspected (tested by installing latest Google Play Music and latest YouTube, both work fine now.. )..
https://github.com/aospX/platform_build/commit/a34ffcecc7c237ac9c9e263984f6a74d3a7c3831
thanks Raeled
Click to expand...
Click to collapse
So this means that your next rom build is going to be possible to use the google music and youtube app from the market without any problems?!?!
Link_of_Hyrule said:
But it requires recompiling the entire rom from source?
Click to expand...
Click to collapse
Correct..it seems that once compiled with =AOSP, all the system packages check this and if it doesn't return as a development platform (=AOSP) it crashes..this is why just changing it in build prop does not work..So the whole rom needs recompiled with =REL.
onesolo said:
So this means that your next rom build is going to be possible to use the google music and youtube app from the market without any problems?!?!
Click to expand...
Click to collapse
Yes, changes are already pushed to git and will be in next release.
Sent from my Inspire 4G using xda app-developers app
Well your devices are lucky to have a dev actively working on fixing this it seems us Mecha users will have to wait for a dev to come along and release a new build or new ICS rom with the fix.
EDIT: Finally got it fixed in the up coming build
can u please update to the latest yt version?
Bump
Sent from my MZ601 using XDA Premium HD app
Youtube app (v4.1.23) & Google Play Music (v4.3.615.481147):
Thanks raeld can you put up the latest version 4.1.47 to please?
Related
[Q] is there an app that checks all installed or purchased apps for ICS compatibilty?
maybe either through API level, or by querying market info Reason: i want to check on GB before I upgrade to ICS, which apps will not work. don't know if relevant but it is for SGS II Thx in advance repost from here as nobody could really answer my question
can't believe I'm the only one with that issue maybe an idea for a dev? would be willing to pay for that ;-)
I don't see why this can't be done: -http://stackoverflow.com/questions/2695746/how-to-get-a-list-of-installed-android-applications-and-pick-one-to-run -http://developer.android.com/reference/android/content/pm/PackageManager.html -http://developer.android.com/reference/android/content/Context.html#getApplicationInfo() I haven't thought through the problem just yet, but its seems to be doable. If you don't find an app soon, I will start working on a script that does it and, if successful, a proper, free software app. I am hoping the available methods won't require something as stupid as launching each app fully. But again, I haven't thought it through. Thanks for the idea btw. EDIT: Made a little more effort https://groups.google.com/forum/?hl=en&fromgroups#!topic/android-developers/dXLACRIizKc I will work on something this weekend and get back with y'all. EDIT 2: So it looks like I would need maxSdkVersion which I don't find in the API. Furthermore, it is strongly suggested that one not use maxSdkVersion when building an app so that doesn't sound all that useful. I have received another, much more complicated suggestion that may do what I want, but I will have to look hard at it. Looks like I'm going nowhere in my effort. Always open to suggestions. More to come later this weekend.
I'm not the sharpest tool in the shed, but I thought this was mostly a straightforward task using the API's exposure to AndroidManifest.xml. As per my previously posted link to an Android Developers discussion on the topic, my approach is dead in the water as far as I can see. I did try to find an answer though to the best of my limited ability. If anyone has or ever solves this problem (I consider it a problem) I would hope they find the this thread. Thanks for the learning experience. I give up.
Most older apps will work fine on ICS, its pretty backwards compatible. If the app uses legacy menus the button will appear in the old lower left hand corner location instead of the upper right hand corner like apps written for ICS.
i'm no dev so bear with me if i write stupid stuff one likely but not very promising sounding way might be to use android:targetSdkVersion as "As Android evolves with each new version, some behaviors and even appearances might change. However, if the API level of the platform is higher than the version declared by your app's targetSdkVersion, the system may enable compatibility behaviors to ensure that your app continues to work the way you expect. You can disable such compatibility behaviors by specifying targetSdkVersion to match the API level of the platform on which it's running. For example, setting this value to "11" or higher allows the system to apply a new default theme (Holo) to your app when running on Android 3.0 or higher and also disables screen compatibility mode when running on larger screens (because support for API level 11 implicitly supports larger screens)." question though is how many apps actually use this? However after having read this re android:maxSdkVersion "Warning: Declaring this attribute is not recommended. First, there is no need to set the attribute as means of blocking deployment of your application onto new versions of the Android platform as they are released. By design, new versions of the platform are fully backward-compatible. Your application should work properly on new versions, provided it uses only standard APIs and follows development best practices. Second, note that in some cases, declaring the attribute can result in your application being removed from users' devices after a system update to a higher API Level. Most devices on which your application is likely to be installed will receive periodic system updates over the air, so you should consider their effect on your application before setting this attribute." (taking from here) i now don't know how important my op is, but then why do all app devs release new versions "fixing things" for ICS? One pretty significant example which actually currently will prevent my phone from getting ICS for now is that the subsonic app in the current version produces stuttering when playing audio while downloading (problem description here). Isn't there any way to instead of searching the phone searching google play/android market instead?
Randi said: maybe either through API level, or by querying market info Reason: i want to check on GB before I upgrade to ICS, which apps will not work. don't know if relevant but it is for SGS II Thx in advance repost from here as nobody could really answer my question Click to expand... Click to collapse Here's a list of some working games/apps for ICS
Theoretically an Android app (or a combo of say App Engine and Android) could find your installed apps, seacrh Play for said apps and then scrape the page for relevant information. Doesn't sound to hard, but I didn't think about too hard either. Perhaps I will check out what useful info is on Play and how feasible scraping its markup will be. I will get back at y'all if I do.
[ROM][DISCUSSION] CM10----DisarmedToaster by AGRABREN [PERMISSION GRANTED]
Download Link: http://goo.im/devs/agrabren/cm10/shooter/cm-10-DisarmedToaster-0.1-shooter.zip GAPPS:http://goo.im/gapps/gapps-jb-20120726-signed.zip TERMS AND CONDITIONS 0. Definitions. “This License” refers to version 2 of the GNU General Public License. “Copyright” also means copyright-like laws that apply to other kinds of works, such as semiconductor masks. “The Program” refers to any copyrightable work licensed under this License. Each licensee is addressed as “you”. “Licensees” and “recipients” may be individuals or organizations. To “modify” a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The resulting work is called a “modified version” of the earlier work or a work “based on” the earlier work. A “covered work” means either the unmodified Program or a work based on the Program. To “propagate” a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well. To “convey” a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying. An interactive user interface displays “Appropriate Legal Notices” to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion. 1. Source Code. The “source code” for a work means the preferred form of the work for making modifications to it. “Object code” means any non-source form of a work. A “Standard Interface” means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language. The “System Libraries” of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form. A “Major Component”, in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it. The “Corresponding Source” for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work. The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source. The Corresponding Source for a work in source code form is that same work. Toolchain: GCC ARM version 4.4.3 Kernel Source: https://github.com/agrabren/android_kernel_htc_shooter This is a Discussion thread for the rom and is only to be used for that purpose. This ROM Thread is posted with Permission of Agrabren WORKING: SOUND WI-FI CALLING DATA You Tell Me! Note I AM NOT the creator of this rom. IT IS AGRABREN He gave me permission to post a discussion thread I will keep this open until he feels like the build is alpha quality I will then close this thread I'm posting a thread as he has not. Also If you phone explodes or you create a black hole I Take NO RESPONSIBILITY
I'm fine with the thread, at least until the ROM is stable enough to meet my standards to be posted as an alpha. People in the CM9 thread wanted to see it, since I had posted a build for the GSM phones (to test if I had the basic infrastructure working) and they were thrilled. So I posted for CDMA after the last builds came out. Now everyone, settle down. You're all more than welcome to use this thread to discuss what works, doesn't work, and how to help each other make the most out of it.
This forum is supposed to be about helping each other. Is the ROM in development? Yes. Does it work up to my requirements for alpha quality? No. Why? Because the microphone doesn't work right. If that were fixed, I'd likely switch to developing for CM10 instead of CM9, because the camera won't kill me to get working and everything else is trivial between the two for me to not lose any time or features.
Thread moved to GENERAL - it will stay here as a discussion thread. Edited OP and thread title to reflect that, also left a couple posts from agrabren so people know he's ok with this thread. Any and all flames or name calling will get you an immediate infraction and likely a ban if you cross the line too much. Keep XDA what it shold be, open and a place to learn. Have a nice day.
im still confused why the dictionary exists in the OP? - why not just link to where that was copied and pasted from? its pretty distracting from the actual OP
Xda is the best... Sent from my GT-XPERIA S using xda app-developers app
Can't wait to install this once I get home.
Thank you il Duce! I'm excited to see CM10 on the Shooter, and can't wait to see how far Agrabren and others take this rom!!
minieod said: im still confused why the dictionary exists in the OP? - why not just link to where that was copied and pasted from? its pretty distracting from the actual OP Click to expand... Click to collapse It's the op decision to put what they want there. You'll live. jasonvanfebr said: Xda is the best... Sent from my GT-XPERIA S using xda app-developers app Click to expand... Click to collapse I agree.
I've been running this for a little over 12 hours now. It's very nice and makes me very excited to see where we can see Jellybean in the future. Not Working: 4G will not enable 3D Camera Google Now/Search FCs Headphones are not detected - sound continues to play through external speaker Potential battery drain - BetterBatteryStats shows phone as awake 100% of the time, though I had an app running that may have been the cause of it Watching Youtube can cause a reboot after 20-30 seconds I also was unable to boot with the stock kernel, and if I had the newer ICS firmware it refused to boot at all with any combination I tried. It's incredibly fast though, you can definitely feel the Butter in play. I'm very impressed with the ROM and will continue to run it until I go back to the USA, at the very least.
Hi. I've been out for a bit, glad to see much hasn't changed (sarcasm). One troll has already been banned from the mess that had to be deleted. Please behave yourselves, I really don't like spending my free time deleting drivel and banning people. The op has permission to post this, it's compliant, just discuss away. Don't be rude to each other. Thanks and have a pleasant evening
Can't Wait wwjoshdew said: Thank you il Duce! I'm excited to see CM10 on the Shooter, and can't wait to see how far Agrabren and others take this rom!! Click to expand... Click to collapse I feel the same way. I would feel better when an official RUU is available then I would start ROM'ing all crazy lol.
FusionNeo said: I've been running this for a little over 12 hours now. It's very nice and makes me very excited to see where we can see Jellybean in the future. Bugs: 4G will not enable 3D Camera Google Now/Search FCs Headphones are not detected - sound continues to play through external speaker Potential battery drain - BetterBatteryStats shows phone as awake 100% of the time, though I had an app running that may have been the cause of it I also was unable to boot with the stock kernel, and if I had the newer ICS firmware it refused to boot at all with any combination I tried. It's incredibly fast though, you can definitely feel the Butter in play. I'm very impressed with the ROM and will continue to run it until I go back to the USA, at the very least. Click to expand... Click to collapse 4g is not integrated into this build , neither is camera , neither is 3d , neither is voice search - that is why those are bugs
Love the idea here, just dropped in to see only shooter, not shooteru. Perhaps a CDMA thread title, or people posting whether they are gsm or cdma. We all want to ditch sense after all.
scariola said: Love the idea here, just dropped in to see only shooter, not shooteru. Perhaps a CDMA thread title, or people posting whether they are gsm or cdma. We all want to ditch sense after all. Click to expand... Click to collapse you can get a fully functioning cm9 rom (no sense) for gsm in the gsm developers section
minieod said: 4g is not integrated into this build , neither is camera , neither is 3d , neither is voice search - that is why those are bugs Click to expand... Click to collapse Oh I know, I wasn't expecting them to work. I just wanted people to be aware of what isn't working, even if it's things people shouldn't expect to work.
FusionNeo said: Oh I know, I wasn't expecting them to work. I just wanted people to be aware of what isn't working, even if it's things people shouldn't expect to work. Click to expand... Click to collapse :good: - OP should be updated reflecting a "not working" feature set
Found another bug - attempting to watch Youtube for more than 30 seconds or so causes a reboot. Will update my post to reflect this (in 5 minutes, due to my lack of user permissions). I agree that these bugs should be listed in the OP, to make them easier for people to find as well as remove all the posts like "DOES FOUR GEEZ WORK" from people who only choose to read the OP.
minieod said: you can get a fully functioning cm9 rom (no sense) for gsm in the gsm developers section Click to expand... Click to collapse yes, a cm9 and cm10 Rom if you know where, the thread hasn't been created for 10 yet. Was just hoping someone could find out why audio goes out after phone connects call through SIP(Internet calling) ? Problem with all cm9+ roms, by 3 different gsm devs.
Titanium backup won't restore Facebook. It's not critical, but it is a problem I've been having. Unchecking Facebook fixes it. It hung on something else too - had to force close TB a couple times, but I got most of my stuff back. Over all, very fast, and the phone (the old neglected bit some people actually use to talk with other people verbally, rather than via txt) works well. I've also had issues downloading paid apps from the market - and TB warned me that my device ID had changed. It offered to change it back, which also crashed TB. After restoring accounts from TB (and possibly the device ID as well - not sure if that completed or not), the market issues have gone away.
Help with building an apk
Hi, I'm trying to build the default Email app from source. Using the CM10.2 as base: https://github.com/CyanogenMod/android_packages_apps_Email I used some patches, which I successfully applied, as this is the main reason of doing this whole thing At first I tried using apktool but that didn't work out. Currently I'm struggling with importing the necessary libs in eclipse (adt-bundle-windows-x86_64-20130917; target API 18 aka 4.3.x). First issue is that even though I am using Google APIs i'm still missing com.google.common. Without google APIs i'm missing the whole com.google... apparently the app has it's own libs com.android.emailcommon which are provided with the application. I had to add emailcommon/src in the buildpath because the rest of the app was referencing it. Problem here is under com.android.emailcommon.service.EmailServiceProxy: IEmailService cannot be resolved to a type. I'm seeing though that IEmailService.aidl exists so why isn't it seeing that interface? I'd be gratefull for any help here. Thanks!
bump please help any some hint would be nice!
bump?
App not allowing me to sign in due to custom rom
Hi everyone, So the company that provides the TV channels in my country (like the cable companies in the US) has a streaming service that streams most of these channels online to phones, tablets, computers. The problem is that their app is, according to them "not supported on hacked devices". Just so we're clear, we're talking about Android here, and hacked = root/custom rom, which this stupid company considers illegal. In some devices, they check both root and custom rom, in some only one of them, and in some the app will work even if you have both. For example, on my Nexus 4 the app worked with stock rom that was rooted. Now that I am running a custom rom, trying to hide root using various apps does not work. So obviously the problem, with my device at least, is running the custom rom. I'm currently learning Java & Android development and have decided to use the little knowledge that I have to try to find the lines of code responsible for this idiotic check. I looked up many tools for decompiling apps and have finally found a good one, called JadX. http://androidcracking.blogspot.co.il/2014/03/jadx-dex-to-java-decompiler.html#links This decompiler is excellent, but gives me a scary amount of code files to look. Even so, trying to search all of them (JadX has that functionality) for the code that checks for root/custom rom has turned up nothing. I have also tried to search for the message they give me when I open the app (about hacked devices not working) but I found nothing, again. One more thing - a developer that also tried to solve this problem said he traced the problem back to DxDrmDlcCore. I searched it, found it a some class, but not sure what to do now (delete the entire class and recompile?) Can someone here direct me towards what I need to be looking for? OR Is the solution really simple, such as editing my build.prop? Someone suggested it once, but did not know what lines to edit. If someone is ready to step up to the challenge, I can upload the apk. Thank you!
Question App crashing--developer blaming numerous Pixel users
Midea Air - Apps on Google Play Midea Air allows you to control your AC from wherever you are play.google.com Would some of you Pixel 6 users mind installing and seeing if it crashes on you, please? Because it's not 100% of users encountering the issue, they blame some Pixel users due to a "classnotfound" error within their application. Since we've all seen people copy & paste code and other silly things they shouldn't do, which cause crashes, I asked them if they used a root checker: Yes, and we also have our test team both in China and the U.S. using a couple of problematic models which are reported by users too. But nothing more is found and none of the trails show the problem. And according to the feedback situation, not all users using these phone models are having issues, so we assume it is related to a specific user environment. Click to expand... Click to collapse But they didn't expand on it beyond "yes", unfortunately. Spoiler: my thoughts & minutia Other than Play Store app updates and automatic Google-pushed Play/Services updates, all I've done in the past 10-14 days is update Lsposed. I've disabled and rebooted without it, and the issue remains. I've also used a stock boot.img and the app still crashes, which makes me think it's detecting an unlocked bootloader or some similar and unnecessary check(s), and moving forward with its checks which then fails due to Google no longer supporting whatever methods the app is using, and they don't know how to figure it out since it's probably copied & pasted code from many months ago and they're unwilling to suspect that old code is the cause, even though Google normally rolls out subtle security changes like this, very gradually. Is it really just me and 5-8 other users in the entire world with this issue, or does it crash on some of you as well? I can't imagine it being such bad code that it's only rooted/unlocked bootloaders with the issue. It must be non-rooted and stock Pixel users with the issue as well, and those devices just haven't been pushed the Play Store/Services update yet. I'd like to know if I'm just getting older and dumber or not, and if I'm truly the cause for the crash, haha. I'm open to being entirely to blame for this, but I don't want to wipe my phone and relock the bootloader for testing quite yet. Thanks for testing and voting in the poll!
Huh? If you've got a "class not found" it seems like it would be pretty easy to determine where the problem lies. Is it some esoteric Kotlin thing or java.util.boring?
Renate said: Huh? If you've got a "class not found" it seems like it would be pretty easy to determine where the problem lies. Is it some esoteric Kotlin thing or java.util.boring? Click to expand... Click to collapse Yeah, I figured something like that should be pretty simple, unless they have zero failures in their own testing. But...is there some new background auto-report for crashes on Android, which ties in to the email address, that I'm unaware of? I never said anything to them other than email them my phone model, Android build, and posted a google app review (under the same name & email address) with no information other than it crashing. And they repllied, via email, with this: Due to the uniqueness of this bug, no more code trace can be reported as you received only a line of error indicating "classnotfound". normally there will be at least a few lines more which helps with debugging. Click to expand... Click to collapse
Well, there could easily be conditional code for almost anything. If you can repeatedly bomb this, why don't you get a logcat and see where the problem is? Code: $ logcat The logcat should say what the class is and where it's called from. Heck, it could even be in JNI code.
I just tested it, opened but due I am not registered and have no compatible AC, I didn't processed further. My cast vote is given, but not sure whether this is helpful, due not sure whether the app crashes when you open it or after login. Pixel 6, A13, rooted and unlocked bootloader. Cheers Tom
oops!
So.... they have test teams in... China? You want to give CHINA control of your air conditioner? And access to data on your phone?
I'm same with tom1807
Yesterday Instagram app started crashing after I got a video message from a friend, I had to clear cache and reinstall it and reboot the phone, its now working fine, it was weird though