I recently updated to One UI 3.1 and it's performing much worse than it was on Android 10, especially with one of my games constantly crashing when trying to enter the main menu.
I want to know if there's a way to revert the update somehow... so that at least I can get things keep running for the time being until GSIs can be made working.
EDIT: Okay... I finally managed to log back in to the game in question after about 100 tries over the past hour... what an effort... it's getting more and more difficult to login lately...
EDIT 2: Guess I'm asking for the impossible... and as for the game in question, I suspect it was a known Unity-related issue caused by permission changes introduced in Android 11. I'm considering rooting the device to test if that's the case as I cannot just grant the permission since the app itself didn't declare it in the manifest. But in overall, it doesn't change the fact that the tablet is performing much worse on Android 11 than it was on Android 10.
EDIT 3: It seems even with root I cannot grant a permission an app didn't request... so I really can't test if the permission in question is indeed the cause of the crashes...
EDIT 4: Downgrading is no longer possible since build BUC1. Samsung has incremented SW REV on this build so you can no longer downgrade once you upgraded past this version.
LSS4181 said:
I recently updated to One UI 3.1 and it's performing much worse than it was on Android 10, especially with one of my games constantly crashing when trying to enter the main menu.
I want to know if there's a way to revert the update somehow... so that at least I can get things keep running for the time being until GSIs can be made working.
EDIT: Okay... I finally managed to log back in to the game in question after about 100 tries over the past hour... what an effort... it's getting more and more difficult to login lately...
EDIT 2: Guess I'm asking for the impossible... and as for the game in question, I suspect it was a known Unity-related issue caused by permission changes introduced in Android 11. I'm considering rooting the device to test if that's the case as I cannot just grant the permission since the app itself didn't declare it in the manifest. But in overall, it doesn't change the fact that the tablet is performing much worse on Android 11 than it was on Android 10.
EDIT 3: It seems even with root I cannot grant a permission an app didn't request... so I really can't test if the permission in question is indeed the cause of the crashes...
Click to expand...
Click to collapse
Most apps should work fine on Android 11, but some may have issues and need updates.
Downgrading to Android 10 is technically possible. Download the Android 10 firmware and flash it with Odin on a PC via USB cable to your device.
But I would prefer running on the newest firmware version and trying to get an update of the app. And there will be updated if Android 11, too ... which optimizations of stability, performance, etc.
It_ler said:
Most apps should work fine on Android 11, but some may have issues and need updates.
Downgrading to Android 10 is technically possible. Download the Android 10 firmware and flash it with Odin on a PC via USB cable to your device.
But I would prefer running on the newest firmware version and trying to get an update of the app. And there will be updated if Android 11, too ... which optimizations of stability, performance, etc.
Click to expand...
Click to collapse
Thanks, but it's not really that relevant now as the crashing issue was finally fixed by the developer.
However, on Android 11 things are indeed performing worse than on Android 10. Frame rates are much lower, and touch issues (erratic or sudden delay/loss of touches) become more frequent. Ironically, when I used GPUWatch (from Developer Options) to diagnose the sluggish frame rates, I found that neither CPU nor GPU was maxing out while playing.
Now that I've rooted, I'm considering looking for some alternatives as the stock ROM is indeed terrible regardless (a good example would be that it's tough to take logcats here, as the system itself spams logs at an incredible rate I've never seen before). However, I'm yet to get a GSI to boot.
Related
Hi guys i see a ota fpr the b008 ibam on 501u model the update is 69 mb wil; post changes later
Sent from my X1 7.0 using XDA Free mobile app
it is complete firmware not just update
Here's the Changelog
1. When solving an upgraded version appeared in a special issue of resuming the scene repeated.
2. Optimization of data services in the open access power situation
3. 4G Network optimization strategy in Afghanistan, and reduce the probability of a fast moving situation out in the network.
4. Automatic light perception to solve the problem of slow response regulator.
5. Solved encrypted phone GPS is unavailable problem.
6. Solve low probability theme, weather and other applications Force Close issues.
7. Failure to solve the problem and paste function calculator.
8. Solve the system time on the 10th of each month before traffic flow management interface does not show the waveform problem..
9. Drops of a taxi home, the glory of the user enjoy five large welfare
#9, what the hell?
Thanks
Done .. Regarding the (drop taxi ) it's just a Chinese removable application
Has anyone tried this update? Does it break root?
theboundless said:
Has anyone tried this update? Does it break root?
Click to expand...
Click to collapse
i have upgraded if u do ota it wont break the root as its just ota , you can also do complete firmware then I am not sur e
for complete firmware:
503L
http://www.emui.com/nsp/geturl.php?path=7D-503L_EMUI3.0_Android4.4_V100R002C208B009.zip&rid=963
501u
http://www.emui.com/nsp/geturl.php?path=7D-501u_EMUI3.0_Android4.4_V100R002C208B009.zip&rid=962
i have read in the chinese forums that this version is supposed to be the one that can retain user data when upgrading from EMUI 2.3, however problems seem to exist after flashing (dark screen when camera is launched, the pull down notification menu stopping midway etc) and Huawei ended up suggesting wiping system / user data to solve them, kinda defeats the purpose. anyway, ymmv.
BTW, does anyone know how to get rid of the update prompt? It keeps nagging me to update.
In going from R001C233B021 to R002C208B009 on the 7D-501u with the OTA update, will it change the dpi from 320 to 400? If so, I'm not upgrading.
Moandal said:
In going from R001C233B021 to R002C208B009 on the 7D-501u with the OTA update, will it change the dpi from 320 to 400? If so, I'm not upgrading.
Click to expand...
Click to collapse
yes it is 400 dpi firmware
Moandal said:
Ichange the dpi from 320 to 400? If so, I'm not upgrading.
Click to expand...
Click to collapse
you can manually change at will the dpi after updating, by modifiyng buildprop if rooted. Or with adb commands if non rooted.
Check for (or open up yourself) a devoted DPI change thread of this forum, if you want to know more about it.
i was also pushed B009.
btw im from singapore using starhub and B008 chinese rom.
updating now.. excites much!
Djiban said:
you can manually change at will the dpi after updating, by modifiyng buildprop if rooted. Or with adb commands if non rooted.
Check for (or open up yourself) a devoted DPI change thread of this forum, if you want to know more about it.
Click to expand...
Click to collapse
As far as I can tell from the other threads, changing the dpi to 320 breaks other stuff. Also some of my apps won't
work with root or with root cloak. There's no way I'm doing an upgrade that I know will break stuff rather than fix stuff, just for a slightly newer version of Android. My battery icon is already white anyway.
Moandal said:
As far as I can tell from the other threads, changing the dpi to 320 breaks other stuff. Also some of my apps won't
work with root or with root cloak. There's no way I'm doing an upgrade that I know will break stuff rather than fix stuff, just for a slightly newer version of Android. My battery icon is already white anyway.
Click to expand...
Click to collapse
It Is same android version like 320 dpi kitkat!
I am in China but checking for updates tells me there is no update (I'm on 2.2). So perhaps this is still not the build intended for general release.
OK, it is now showing as available as an OTA today BUT trying to download it always ends in failure. Perhaps loads of other people are trying to download it at the same time....
Just download it from the EMUI page.
I waited for the OTA, hoping that it would not wipe the device (unlike the emui page download version?).
After taking 8 hours to download, it finally tells me it will wipe my personal data. What kind of stupid upgrade is this? No other brand of Android phone I have ever owned has wiped data on upgrading from one version to another. Very disappointing. Huawei, you must do better than this if you expect people to buy your phones more than once.
It did not wipe mine.
I just installed it, and wished I hadn't. ALL paid for apps were wiped. Other apps were also deleted. I can no longer connect to Google services (Play store, Gmail, etc). What a pile of rubbish. An OTA update shouldn't do this kind of thing. This is my first, and last, Huawei phone. Nice hardware, shame about the software.
I am reading the site the last couple of hours, and I can't find a step by step for Root. I can't Enable ADB because it is not there! So I guess the method for HD is not working? Please help me and sorry if it was asked, but I can't find it,
You can't root 4.5.3, you have to roll back to 3.2.8 (and root it, plus you can install Safestrap on that build and use the Nexus 1.0.1 ROM which is Jelly Bean but that's as far as you go) and then upgrade to 4.5.2 which is still rootable with the CVE exploit.
But with 4.5.3 you're stuck, and with 4.5.4 around the corner there's a chance that update could totally block all rooting period so, be aware of this - stay away from 4.5.4 (when it becomes available) if there's even a potential update or as long as you can, and within reason roll back to 3.2.8 then bump it to 4.5.2, root that build then disable the OTA capability and go from there.
To get ADB, go into Settings, Device, Serial Number - Tap Serial Number 7 times which gives you the Developer Options (just like tapping the build number in normal Android does). Once you have them (go back a menu) you can then enable ADB from there.
But again, the recommendation is to get off 4.5.3 (at least it's my recommendation if you want any possible root at all) as soon as possible.
The instructions are here, I just got an HDX on Wednesday and I've learned quite a bit in the past 48 hours or so (no that doesn't mean I've been lurking/reading/posting for the past 48 hours, of course). It's not that tough, but it does require actual reading with comprehension and not just skimming topics or barely reading the posts in threads.
atti_mac said:
I am reading the site the last couple of hours, and I can't find a step by step for Root. I can't Enable ADB because it is not there! So I guess the method for HD is not working? Please help me and sorry if it was asked, but I can't find it,
Click to expand...
Click to collapse
In addition to the comments from br0adband be aware adding gapps (Google Play Services, Store, etc) to Fire OS can be problematic as you can not completely purge the device of Amazon equivalents. It works but not without some annoyances. At present there is a broader issue with the current release of Google Play Services (v7.3)that is impacting a wide swath of devices including many rooted Kindles. Google will likely issue a fix but they do not seem in any hurry to do so.
A rooted HDX running Fire OS 4.x isn't like other Android devices. Root helps you get around some Amazon annoyances and add addition capabilities but it's nothing like pure Android. Even simple things like changing wallpaper can be a hassle.
If you want to move forward w/root see this post for further instructions.
Davey126 said:
In addition to the comments from br0adband be aware adding gapps (Google Play Services, Store, etc) to Fire OS can be problematic as you can not completely purge the device of Amazon equivalents. It works but not without some annoyances. At present there is a broader issue with the current release of Google Play Services (v7.3)that is impacting a wide swath of devices including many rooted Kindles. Google will likely issue a fix but they do not seem in any hurry to do so.
A rooted HDX running Fire OS 4.x isn't like other Android devices. Root helps you get around some Amazon annoyances and add addition capabilities but it's nothing like pure Android. Even simple things like changing wallpaper can be a hassle.
If you want to move forward w/root see this post for further instructions.
Click to expand...
Click to collapse
It said : "Put roolback file into the Internal storage folder of your Kindle." !
I downloaded a "mod-update-kindle-thor-13.3.2.8_user_713328020" folder and i have no idea where I have to copy it. I just did it to a main folder put it between the "Kindle" and "Movies" but it doesn't do anything when I want to do an update. Without wifi, didn't even start.
UPDATE, just realized i had to copy a "bin" file not a folder version. So now is downgrading. How to root 3.2.8? should i update to 4.5.2 first and root or root the 3.2.8?
update
I was able to downgrade , and upgrade to 4.5.2, rooted, and I was able to follow the other guides to disable OTA updates.
But when I try to install the Google play apps, it said at step 1 "aquire the GApps.."http://forum.xda-developers.com/kindle-fire-hdx/general/tut-disable-ota-4-5-2-install-gapps-t3043550
So when I followed the link , it takes me here :http://forum.xda-developers.com/android/software/gapps-google-apps-minimal-edition-t2943330
And Step 2 Boot into recovery to able to install Zip file....
I can't boot in recovery, the step by step guide said power on, and when i will see the "kindle fire" hold the power till turns blue and let it go. Mine newer turns blue just orange and if I let the power go nothing happen.
Will you guys help? I am so close!
Do not do the recovery instructions. Grab the file from the link and follow the instructions from this forum. If you are rooted, be very careful with stock recovery.
The spoiler is instead of installing the zip, unzip it and copy many of the files to their respective folders. Skip priv/app/ setupwizard.apk and priv/app/prebuiltgmscore.apk. install the gms core as a normal app and you are good to go... almost. Look around the HDX general threads for a fix to prevent google play services updating themselves.
Good luck
Sent from my KFTHWI using Tapatalk
a chinese root toolkit named Kingroot seems able to support Fire OS 4.5.3 now. Several guys tested it and succeeded.
but it contians a su manager named KingUser from the same company. if anybody can install SuperSU instead, you can have a try.
some one dont understand chinese? PM me, i can help.
BTW. Personally, I never recommend Chinese APPs from chinese companies. They use the APPs/Softwares to play a role as thief to steal your information, contacts, maybe more. And they always ask for more permissions.
For economic benefits, they can do anything.
FotixChiang said:
a chinese root toolkit named Kingroot seems able to support Fire OS 4.5.3 now. Several guys tested it and succeeded.
but it contians a su manager named KingUser from the same company. if anybody can install SuperSU instead, you can have a try.
some one dont understand chinese? PM me, i can help.
BTW. Personally, I never recommend Chinese APPs from chinese companies. They use the APPs/Softwares to play a role as thief to steal your information, contacts, maybe more. And they always ask for more permissions.
For economic benefits, they can do anything.
Click to expand...
Click to collapse
FYI recieved OTA 4.5.4 and it breaks root. Kingroot 4.1 no longer works.
koda1789 said:
FYI recieved OTA 4.5.4 and it breaks root. Kingroot 4.1 no longer works.
Click to expand...
Click to collapse
Must be a lucky day that I've just rooted 4.5.3 with Kingroot and disabled OTA today :fingers-crossed:
koda1789 said:
FYI recieved OTA 4.5.4 and it breaks root. Kingroot 4.1 no longer works.
Click to expand...
Click to collapse
Unbelievable. Had an HDX 7" with 13.3.1.0, rooted, was ready to unlock bootloader and install CM12. Received a surprise visit, and when I got back to my desk I was on 4.5.4...
Bad day...
Well, it could be worse, you could have gotten bricked during the update.
Davey126 said:
In addition to the comments from br0adband be aware adding gapps (Google Play Services, Store, etc) to Fire OS can be problematic as you can not completely purge the device of Amazon equivalents. It works but not without some annoyances. At present there is a broader issue with the current release of Google Play Services (v7.3)that is impacting a wide swath of devices including many rooted Kindles. Google will likely issue a fix but they do not seem in any hurry to do so.
A rooted HDX running Fire OS 4.x isn't like other Android devices. Root helps you get around some Amazon annoyances and add addition capabilities but it's nothing like pure Android. Even simple things like changing wallpaper can be a hassle.
If you want to move forward w/root see this post for further instructions.
Click to expand...
Click to collapse
Watch this video to fix that issue with Google Play Services...
[Fix] - Play store and COC not Working on Kindle …: https://youtu.be/7RxuP9X3Mgo
Ali Ejea Mc said:
Watch this video to fix that issue with Google Play Services...
[Fix] - Play store and COC not Working on Kindle …: https://youtu.be/7RxuP9X3Mgo
Click to expand...
Click to collapse
Thanks.
Another option now exists for locked devices that involves replacing FireOS with Nexus which natively supports the Play store. See: http://forum.xda-developers.com/showthread.php?t=3137840
I don't know if others are facing the similar problem but it has turned my life into hell after the new update. I will list down the issues on ALL ROMS after the new OOS 3 update with bootloader in my device.
I had issue in accessing storage, which means gallery, file explorer or literally any app crashes when I try to access from the storage, be it internal or external sd card.
Couldn't use the latest snapchat at all, can't post in story, can't save any snap, can't upload from camera roll. It was just a dead end. However I could only post into story with a older Snapchat version, still due to storage access issue, I couldn't save or upload from Camera Roll
Facebook picture upload would ocassionally crash the app.
Couldn't take more than 1 picture in latest youcam app, storage issue would crash the app.
Gallery apps fail to generate thumbnail previews.
All these above problems caused permanent storage access unavailability until I rebooted device.
Need to charge my device twice as Battery runs faster than Usain Bolt.
So finally after a lot of tingling, I finally downgraded my device to OOS 2.1.3 with TWRP 2.8.7. Trust me it's very stable, bug free and battery friendly. Though I miss the new security patches features and snappy feel from Android 6 & 7.
The above problems are not happening in 2.1.3. I can use latest snapchat, youcam & facebook without any issue at all. Is there any way to prevent these issues on new Android OS in my device ? I believe it's not a device issue as 2.1.3 is running very stable and bug less.
Never had any of those issues on OOS 3 update. Think you might of gone wrong somewhere maybe.
Exodusche said:
Never had any of those issues on OOS 3 update. Think you might of gone wrong somewhere maybe.
Click to expand...
Click to collapse
I am really eager to find that out. I have almost tried every ROM on the new bootloader. Except MOOS 2.0 or something, each and every ROM had this bug, even official OOS 3.1.4. Any idea what might went wrong ? The bugs are not reproducing in OOS 2.1.3 though. Which makes me believe that my device is ok.
arafat_mw said:
I am really eager to find that out. I have almost tried every ROM on the new bootloader. Except MOOS 2.0 or something, each and every ROM had this bug, even official OOS 3.1.4. Any idea what might went wrong ? The bugs are not reproducing in OOS 2.1.3 though. Which makes me believe that my device is ok.
Click to expand...
Click to collapse
Think I figured it out for you. You are on really old OOS2 build you need to flash 2.2.3 before you update to OOS3. It was made for the update to MM.
Are you sure you gave the good permission. On MM, when you first launch an app, it should ask you for it. Maybe a bug appear at one point.
You should go to menu settings / app / 3 dots menu at the top right an reset app prefs.
Then re open app one by one.
You can try first without your SD inside to see if it happens again.
Hello
I have an Xperia Ray and was running a 4.4.4 ROM based on CyanogenMod till a few weeks ago when I started to realize that many of the newer versions of different apps caused strange troubles. Some of them crashed most file explorers I tried just on loading the icon from the downloaded APK. Some I managed to install nonetheless only to have the same problem with the launcher/drawer itself. Every time it tries to display the icon of the app it dies. Looking for a solution I discovered that CM13 got ported for my phone and was happy to be able to change to Android 6.0.1.
Sadly the troubles did not go away. The apps that showed the above mentioned symptoms on 4.4.4 have similar effects on 6.0.1. Only that now these apps are crashing the whole phone forcing a reboot and that the launcher app does not load at all anymore. Only solution is to uninstall the app manually in recovery mode via adb shell.
After a lot of tinkering, experimenting, talking to other app devs, and rebuilding open source apps I found that the problems appeared with the update to Android Studio 3. It seems that without changing anything code wise for these apps only the update from gradle wrapper 3.5 to 4.1 seems to cause these troubles. On the other hand I can build my own apps with the newest Android Studio with everything up to date without these problems showing up. So I guess it is some library, API, or whatever in combination with the newer gradle versions that causes these troubles.
Well, it seems that there is a bug in the CyanogenMod ROMs, as far as I know by now. It's not a Xperia Ray specific problem as people with other hardware running CyanogenMod have the same problems. For example this thread here. And I got confirmation from an app developer team that they were able to reproduce the problems on a Galaxy S2 running CM13.
It's also not Android version related as updating to 6.0.1 did not help at all.
Have you experienced what I'm talking about and maybe found the solution for that problem? I think there is a bug in the CyanogenMod system somewhere but I'm not skilled enough to find it.
I fear that these problems will render my phone incompatible with more and more upcoming app versions and would really hate to have to switch to a bulky modern phone.
Here are some log files showing the errors. Maybe you can read something useful from them.
Thanks in advance!
EDIT:
Here some additional info that came as answer from a dev team I contacted regarding this issue:
The issue you have reported tends to only occur in devices with the older memory layout used by manufacturers for devices that run Android 2.x onwards, such as the Galaxy S2 - this layout still sticks around even when upgrading to custom ROMs with newer android versions. A unified internal layout for Android devices only started to appear in 2013 and it became the de-facto layout in 2014 or so.
In the old layout, you have both an Internal System Partition (1-2GB) and then an Internal System Memory (the rest of the device's advertised internal memory - its seen as emulated "External memory" - an external SD card then becomes "SD2" in these devices when running a custom ROM). This causes problems for apps that are created and compiled with the unified memory layout in mind, even if the old SDK is the target, because the system will not direct them to an accessible storage area to store user data.
The apps that do not have problems were the ones that have been around since android 2.x; they will instead have their own set of problems for newer devices and versions of Android.
Right now I'm not sure what to think of this...
Push...
push too , if i use a non cyangenmod based rom like paranoid android (6.0 Android MarshMallow Pure AOSP for Google Nexus 7 2012 WIFI), is this prob fixed then ?
i have nexus 7 (2012) wifi only device , i have cyanogenmod 11 (20141112) / android 4.4.4 ( this tablet has no SD card slot so no SD2 assignment )
Not Sony Xperia,..
Only a cheap Haier A16C3H with CM13 Nightly...but..
Yes the trouble is exactly the same in my experience here. I don't know what to do for the solution, except perhaps one of:
# "keep/looking for & install - only the old version of apps, or
# buying a new phone (if I can)
Sad
Nothing new
Push
Nothing new from my side, except that I think twice before updating an APP by now.
So far I've managed to get around with my old Xperia, but would be nice if someone more knowledgable could look into this matter.
Thanks.
Anyone figured out how to fix this? or even a workaround?
My problem was the cm13 based rom I am using on my LG G3 Beat had this problem with newer versions of apps, but someone made a cm14 based rom that fixes this problem but in exchange it created another problem, lag in the touchscreen, playing games where you have to do combo/multiple taps became impossible.
I got so frustrated that I just went back to stock lol.
I'm trying to upgrade my Samsung p7510 10.1 tablet from Ice Cream Sandwich 4.0.4 to either Marshmallow or Nougat, or better. I've installed TWRP 3.1.1 and rooted with SuperSu. I've had to assume root has worked as can't download root checker onto my tablet.
So, far I've managed to find a version of Marshmallow "ROM-STOCK_MMB29K-seed.zip" on androidfilehost.com. But when I try installing I keep getting error message "Updater process ended with signal: 4". I've wiped the Data, cleared the Cache and Dalvik Cache. Also searched the internet for info on the signal 4 problem but not found much other than to remove the "assert" line from the updater-script file in the OS zip.; that did nothing.
So, a few questions:
- Anyone know where I can get OS zips from for a Samsung P7510?
- And any ideas on resolving the signal 4 issue?
- Any other ideas?
P.S. The only reason I'm updating is I want to use it for Kindle but can only reach HTTP sites, not HTTPS. Assumed that is because it's so old that everything is out of date. And that stops me from downloading anything from just about anywhere, including Google Play.
P.P.S I have searched the forums but couldn't find anything helpful or with links that worked.
Thanks in anticipation
Might I suggest the stabelest ROM I've ever run on my P7510. I've had this installed on mine for over a year now. There are of course some minor bugs.
The signal 4 issue is most likely a Binary issue and should no longer be relevant since you should reset the device to factory and start over. Another thing is once you Root it you can't download from Google play because you now have an unverified device, it has something to do with Google Pay. You'll want to look for APKs. Although SuperSu is usable, you're going to want Majisk insted. I hear of some problems using SuperSu.
I have these files here in my PC if any of the links no longer work but you'll want to know how to flash it so you'll need the video. I'll check back soon and drop a link to my files. if you need them. I'd need to upload them to my Google Drive first.
If you have any other difficulties I'm usually here about once every week.
P.S. Your tab is better than a Kindle and I would not suggest using it as such, it runs pretty crappy that way . Amazon does have an app you can use. And I see that you have been having difficulties finding Operating Systems for your tab and yes it's because the P7510 first hit the market in March of 2011 there aren't many people doing much with it anymore. There's about 3 or 4 of us left.
Firstly, thanks for your help @Casper Young .
In particular the video was brilliant. I did have a few runs at the update, however, the process was very straightforward. The key issue was the TWRP version I was using. It was supposed to be for the P7510, but realised it was actually for the P7500, consequently the aosp files weren't loading. I think that was also the cause of the errors I was getting. And although none of the links were working I managed to get the file names from the video and sourced them from androidfilehost.com:
twrp2870-20150814-p4wifi.tar.md5
aosp-7.1-p4wifi-20170506.zip
Once I had those it was simple and the update worked smoothly.
I've also added the app from apkpure.com as Google play was a complete pain trying to get the tablet recognised. Now very pleased with the build and apps, all running very smooth.
thanks again
Glad you had no problems. There are some minor bugs. Flash doesn't work for the camera. And check your memory capacity. I use Apex Launcher for my home screen which organizes better for me.