So recently I flashed some Marshmallow roms and i missed my xposed so i went back to lollipop. After noticing some smoothness loss, I then flashed stock lollipop and still have issues.
Has anybody else had this problem? If so, do you have any solutions? Thanks!
TheGingerlyGamer said:
So recently I flashed some Marshmallow roms and i missed my xposed so i went back to lollipop. After noticing some smoothness loss, I then flashed stock lollipop and still have issues.
Has anybody else had this problem? If so, do you have any solutions? Thanks!
Click to expand...
Click to collapse
That happened to me too when I went back to Lollipop a few days ago for the exact same reason. I tried everything and nothing could match the smoothness and/or battery life of Marshmallow. I said screw it and flashed 6.0 a few hours ago. That's the only solution I found.
Related
Hi,
I have a rooted I9295, after the last ota update (2 weeks ago) i noticed that my wifi stopped working and i get an annoying message "Prevention Information". I think the update failed on the radio part which is causing this.
I'm currently on android 4.2.2 with baseband version MF5 and ML3 buildnumber.
can anyone point to a fix ?
thx !
Rexxen said:
Hi,
I have a rooted I9295, after the last ota update (2 weeks ago) i noticed that my wifi stopped working and i get an annoying message "Prevention Information". I think the update failed on the radio part which is causing this.
I'm currently on android 4.2.2 with baseband version MF5 and ML3 buildnumber.
can anyone point to a fix ?
thx !
Click to expand...
Click to collapse
I'm not sure if this is the right modem, but it could be. Hopefully somebody else will reply with a proper solution.
The latest OTA update was for 4.3. Looks like you didn't update at all, but the process borked something up on your phone. Maybe a factory reset will fix your phone. Yeah, major pain, but had you gotten the 4.3 update you'd really be screwed since going back would not be an option and you would have lost root.
Miami_Son said:
The latest OTA update was for 4.3. Looks like you didn't update at all, but the process borked something up on your phone. Maybe a factory reset will fix your phone. Yeah, major pain, but had you gotten the 4.3 update you'd really be screwed since going back would not be an option and you would have lost root.
Click to expand...
Click to collapse
Unfortunately we're not so lucky in Europe, still no 4.3 update.
The latest OTA update we had here added some more Samsung bloatware and a nice message warning you to close the flappy charge port after charging.
I had a rooted 4.2.2, and i think that caused the problem.
Going to try to update the radio with Odin.
Rexxen said:
Unfortunately we're not so lucky in Europe, still no 4.3 update.
The latest OTA update we had here added some more Samsung bloatware and a nice message warning you to close the flappy charge port after charging.
I had a rooted 4.2.2, and i think that caused the problem.
Going to try to update the radio with Odin.
Click to expand...
Click to collapse
Did this work out for you? I'm having the same issue.
Sent from my SAMSUNG-SGH-I537 using Tapatalk
So i ended up doing this:
First i flashed the entire phone (since i couldn't find just the modem)
http://honai-android.blogspot.nl/2014/01/how-to-update-galaxy-s4-active-i9295.html
After that i rooted the phone again
http://androidxda.com/root-samsung-galaxy-s4-active-gt-i9295
And that fixed the issues.
Everything works fine again, and i didn't loose any data in the process.
I have been running my nexus 6 with bbedward's disable encrypt since 5.0. I have since upgraded to 5.0.1 no issue. I hav eonly unlocked, and rooted, running stock 5.1.
I now upgraded to 5.1, but the built in battery meter now resets every reboot of the phone. Is this new in 5.1? Or a possible bug? It also doesn't actually show anything, it just says "battery usage data isn't available."
Anyone else experience this?
vivithemage said:
I have been running my nexus 6 with bbedward's disable encrypt since 5.0. I have since upgraded to 5.0.1 no issue. I hav eonly unlocked, and rooted, running stock 5.1.
I now upgraded to 5.1, but the built in battery meter now resets every reboot of the phone. Is this new in 5.1? Or a possible bug? It also doesn't actually show anything, it just says "battery usage data isn't available."
Anyone else experience this?
Click to expand...
Click to collapse
I'm also seeing this. Thinking of wiping and reflashing.
Gordonx42 said:
I'm also seeing this. Thinking of wiping and reflashing.
Click to expand...
Click to collapse
I ended up waiting and data showed up.; I rebooted and it retained, so i'll give it another battery cycle to see if it stays.
I've noticed since I got L my phone's battery is absolutely horrible, it heats up like crazy even if it's just in my pocket, it's almost always awake... I thought lollipop was supposed to increase battery life. If anybody has any solution please share it. I can't even get a full day yet on kk I would get like 3 days
Not sure how you got lollipop installed... but I know that a full wipe before install helps eliminate gremlins from the previous rom causing a conflict with the new rom.
Even with a stock OTA update to 5.0 on my wife's S4, she has had a lot of glitches. Having to uninsyall and reinstall apps and such to get them to work.
When I updated my note 3 to the stock rooted 5.0 I did a full wipe and had significantly worse battery life than on 4.4.4.
On my note 3, I recently did a full wipe and installed the dompop v2.2.3 rom (lollipop) and my battery life is good again.
Have you at least tried wiping dalvik & cache?
Try this
I full wiped when I installed. I will give Dompop a try. Thanks I appreciate it. I tried the disable carrier iq prior to starting this thread.
I know, I know, there are a ton of posts by people asking how to return to stock. My situation is quite peculiar though.
I was part of the Motorola Feedback Network and I got to test 5.1 Lollipop on my XT1053 along with maybe 100 other people a few months. I was quite fortunate, but I felt like messing around and I flashed CM12.1. Now that 5.1 is available for everyone, I want to go back since CM has a cell radio battery drain bug that isn't present in stock.
So here's the problem:
I am unable to return to 4.4.4 to receive the OTA. Because I was already on Motorola's 5.1, my bootloader, motoboot and other important files were all upgraded to 5.1 and I can't downgrade. I tried flashing them using fastboot but no dice. Thankfully, I had a back up of CM12 or else my phone would be bricked.
I tried downloading a flashable OTA but it won't install because it's expecting me to come from 4.4.4, not 5.1.
I think what I would need is a generic 5.1 zip for the XT1053 in order to return to stock, but what do you think?
Like I said, I have the CM12 back that restored just fine so my phone is functional so I'm in no hurry. Thanks for any help!
My wife and I both have H811 G4s. I've gone through and rooted both of our phones with Low Effort, flashed twrp, debloated, updated to 10n debloated. Everything has been great until last week. My wifes phone started randomly rebooting. It's actually random. I can't find anything consistent. I removed apps with updates, factory reset and it would reboot during the setup wizard. Yesterday I did a full return to stock 10n, and it behaved all day.
Today I try to root with the 10n debloat , and now it's rebooting again. I have a hard time thinking it's bad hardware as the full stock works fine, and with it not rebooting on stock how would I prove it for the replacement?
What else can I check or do to fix this, and why is it only happening to one of the phones?
Bad download.
Sent from my LG-H811 using Tapatalk
MicroMod777 said:
Bad download.
Click to expand...
Click to collapse
Good idea, but I've used the same file on multiple phones without issue. It's only the one device having problems. Also the md5 matches, just double checked.
As I work my way backwards I'm pretty sure this it turning into failed hardware. I've had it reboot a few times on stock during the setup wizard. But it's nowhere as frequent as the rooted roms.