Related
Hi all, I'm running Cyanogenmod 6.5.7 and in the last couple weeks I've picked up my phone only to find it was off, not sleeping. It still has plenty of charge left (I can't remember when my phone last went below 50%), and it boots back up without a problem. You wouldn't know there was anything wrong except for the fact that it sometimes turns off on its own.
My first problem is that I don't know where to look to see what could be the trouble. It's running ADWLauncher EX. Beyond that and the OS I don't know what could be relevant. I switched to CM7 last month, up to then I'd been running GingerLOL and I never had this issue.
Any help or advice is appreciated.
The devs would say do a full format and flash and see if it still happens.
Sent from my LG-P500 using XDA App
if you want to know what is happening install logcat from market and check for errors..
i used it to know why mms wont downlaoad and logcat showed that mms ip is wrong and changed it and it works
Oneiros42 said:
Hi all, I'm running Cyanogenmod 6.5.7 and in the last couple weeks I've picked up my phone only to find it was off, not sleeping. It still has plenty of charge left (I can't remember when my phone last went below 50%), and it boots back up without a problem. You wouldn't know there was anything wrong except for the fact that it sometimes turns off on its own.
My first problem is that I don't know where to look to see what could be the trouble. It's running ADWLauncher EX. Beyond that and the OS I don't know what could be relevant. I switched to CM7 last month, up to then I'd been running GingerLOL and I never had this issue.
Any help or advice is appreciated.
Click to expand...
Click to collapse
Try tuning down your overclock frequency... if you have overclocked it... it sometimes happens cuz of that... if you havent overclocked then theres some other problem...
Sent from my LG-P500 using xda premium
samrox144 said:
if you want to know what is happening install logcat from market and check for errors..
i used it to know why mms wont downlaoad and logcat showed that mms ip is wrong and changed it and it works
Click to expand...
Click to collapse
I've done that, but does logcat hold on to recent logs automatically, or do I have to turn on "save to sd card"?
I think I might be having this same issue. I left my phone on and plugged in to charge not even for a half hour or less then I came back to it later and pressed the power button to try to turn it back on but it wouldn't turn on. Then I pressed and held it a second and it wouldn't turn on. I unplugged the battery then plugged it back in then it powered up fine. I seem to be having this issue every once in awhile and I am not quite certain why it is doing this. Also it seems like it has an issue with charging on my computer. I plug it and it the computer is telling me that it can be connected to a higher speed port which makes no since as I have 2 usb 2.0 ports and 1 usb sata port. But basically I plug it in with a full charge and it has no problem keeping it charged but when it ends up going down to at least 50% the charge just keep deceasing and never charges. I just hope that I can make it stop this as it is getting quite annoying maybe it is just the battery or something but I can't see how as it isn't even 6 months old.
I've tried using Logcat but unless you set it to save the log every few seconds it doesn't help. If there's an error it doesn't get caught by Logcat because whatever it does, it turns off the whole phone.
What are you overclocked to?
I'm not, unless CM7 comes already set to overclock. I don't play games on my phone so not much point overclocking for me.
Oneiros42 said:
I'm not, unless CM7 comes already set to overclock. I don't play games on my phone so not much point overclocking for me.
Click to expand...
Click to collapse
Well then. I don't know. Have you tried reflashing the ROM?
Not yet. I was hoping Mik's CM7 6.6.1 would have been declared stable by now, but I guess I'll have to settle for 6.5.8.
Quick off-topic question: ADW Launcher always comes to a grinding halt immediately after a reboot, to the point it gives the force-close option window. Is that because there are widgets installed to the partition on the sdcard, thanks to app2sd? I checked under applications and it says they're installed to the phone, but I thought I heard that app2sd (I'm using Darktremor's, as suggested by Mik) effectively takes the option out of your hands, making it moot. If that's the case, how do I delete the partition, since I'll be doing a full wipe and reinstall when I flash the ROM again.
I don't play games 2
Dammit! Yesterday I did a complete wipe (return to factory, wipe dalvik), reformatted the sd card, and updated the ROM to 6.5.8 and it just shut down on its own again. I even saw it happen... while it was sleeping, I saw the buttons light up and blink once or twice, then it shut off. The screen stayed off.
I did a clean install and haven't touched the clock settings. I reinstalled my apps of course, but I don't have anything that runs constantly in the background that I'm aware of. I installed ADW Launcher EX, I don't know if that matters.
Does this mean it could have a physical fault somewhere? I'd really hate to have to go through the hassle of reloading the LG stock ROM and unrooting it (that's possible, right) to send it in for repair.
I had the same problem with gingerbread and the related roms.
But my problems were about the overclock frequencies. I used the italian rom GingerLoL 1.5.2 and I set the frequencies in this mode: 320-729 smartass v2. No more problems.
I don't know why I hadn't this problem with Froyo's rom...
I'm tempted to fiddle with the clock settings now that I know just reflashing the rom doesn't help. It seems by default CM7 is set to 245-600mhz, with the "smartass" governor. I figure I might as well bump the low end to 320, but where's the "v2" version of smartass you mention? It's not in the list.
I have exactly the same issue! Tried 3 different firmwares, 3 different roms and different kernels too, but it seems to reboot by itself and also really slow sometimes to scroll. Can't solve this... maybe some hardware troubles? some new defected cpu ? I sent this phone 1 month ago in warranty and they changed me the logic board, then when i got it back, it started to have this trouble. Before this, never had this trouble.
Oneiros42 said:
Hi all, I'm running Cyanogenmod 6.5.7 and in the last couple weeks I've picked up my phone only to find it was off, not sleeping. It still has plenty of charge left (I can't remember when my phone last went below 50%), and it boots back up without a problem. You wouldn't know there was anything wrong except for the fact that it sometimes turns off on its own.
My first problem is that I don't know where to look to see what could be the trouble. It's running ADWLauncher EX. Beyond that and the OS I don't know what could be relevant. I switched to CM7 last month, up to then I'd been running GingerLOL and I never had this issue.
Any help or advice is appreciated.
Click to expand...
Click to collapse
Make a full wipe and don't let your phone with low internal memory, it worked for me and i was having the same issue
FPChaim said:
Make a full wipe and don't let your phone with low internal memory, it worked for me and i was having the same issue
Click to expand...
Click to collapse
I have done a full wipe, but I don't understand your other suggestion. I'm using Darktremor's Apps2SD, so I'm pretty sure I'm not running low on ACTUAL internal memory.
As per my last comment, I bumped the low end of the governor to 320mhz and there was no trouble until two days ago when it turned off on its own again, making it the longest it went without the spontaneous shutdown. However, it then broke its record for SHORTEST time because it shutdown again five hours later.
Can anyone thing of anything else, or should I start looking for my warranty info?
Oneiros42 said:
I have done a full wipe, but I don't understand your other suggestion. I'm using Darktremor's Apps2SD, so I'm pretty sure I'm not running low on ACTUAL internal memory.
As per my last comment, I bumped the low end of the governor to 320mhz and there was no trouble until two days ago when it turned off on its own again, making it the longest it went without the spontaneous shutdown. However, it then broke its record for SHORTEST time because it shutdown again five hours later.
Can anyone thing of anything else, or should I start looking for my warranty info?
Click to expand...
Click to collapse
I'm my case the phone boots and when it load all the aplications it reboots... but one time i quickly go to setting>applications>manage applications and there has less than 1 mb... so i think it was building something like caches... I wiped everything and my phone worked as usually... but i installed a lot of things again and it keeps rebooting and rebooting... i wiped everything again and installed just few things, leaving my phone to have high internal memory... it worked!(actually i have 42 mbs of free space and it never happened again)
I apologize if this thread is a tad redundant, but I believe it goes beyond your run-of-the-mill glitches that one might post about in the ICS Bugs thread.
I got my OTA upgrade about 10 days ago, and since then my RAZR has been utterly useless.
The biggest problem is an obvious issue with power management. With GB I used to get almost a full day of heavy use. Now I get 2 hours, 3 if I'm lucky. I often find that the phone is extremely hot, as if the processor and radios are running at 100% for no reason.
Perhaps worse than that, it takes infinitely longer to charge than it used to. As in, 5+ hours to go from 0% to 100% -- and that's while the phone is powered off. Powered on, it'll take even longer.
I've experienced issues with almost every app, and with some I've had literally no success whatsoever. Facebook freezes half of the time before even loading up. The stock Browser will freeze a few times a day. Alarm Clock Xtreme freezes whenever I try to edit an alarm. Neither the stock Gallery nor third-party image apps will load up any of my photos without freezing. Google Talk won't initiate video chats. The list goes on and on.
Moreover, the phone will often just freeze outright. Sometimes the screen won't light up, regardless of how many times I press the power button. Sometimes the phone gets stuck on the home screen, and responds to nothing. Sometimes the phone becomes unresponsive, although pressing the capacitive buttons still triggers haptic feedback. Because of this, several times a day I just hold power+down to shut it off the hard way.
At this point, I actually avoid using it. It's that useless. It's more burdensome than it is helpful. It sucks because, when it's working, everything is really smooth and the ICS interface is really cool. I can tell it would be awesome, if only it worked.
Has anyone experienced such madness as this?
FYI, I'm running:
Android version 4.0.4
System version 6.16.211.XT912.Verizon.en.US
Baseband version CDMA_N_05.11.01PLTEDC_U_09.11.00
Kernel version 3.0.8-g29cf5e7, [email protected] #1
Build number 6.7.2-180_DHD-16_M4-31
I can't believe they would release something so unstable.
And yes I've gone into recovery and wiped the cache partition several times to no avail.
I admit there are some issues with the battery and heat and bugs, but i have not experienced any freezing with the stock browser or any program really, alarm clock extreme and it works for me, I don't use the Facebook app often but the few times i have, no real issues sometimes it lags trying to update. I will say thay the market SUCKS or play whatever they call it. Maybe you got a corrupt OTA file or something is wrong with your update installation. Maybe try doing a factory reset, i know that sucks to do but i do it before every OTA and im not really experiencing any of the software issues you are experiencing. If that doesn't help, root it and use the razr 1.7 utility to reinstall the system files.
Did you try to wipe the device (factory default)? It helped in my case.
Sent from my XT910
If you wana solution to some problems without wiping the phone, boot into recovery and wipe the cache, fixed my battery and a few other problems, It doesnt remove anything you have done, also it eliminated my lagg problem.
abw1987 said:
I apologize if this thread is a tad redundant, but I believe it goes beyond your run-of-the-mill glitches that one might post about in the ICS Bugs thread.
I got my OTA upgrade about 10 days ago, and since then my RAZR has been utterly useless.
The biggest problem is an obvious issue with power management. With GB I used to get almost a full day of heavy use. Now I get 2 hours, 3 if I'm lucky. I often find that the phone is extremely hot, as if the processor and radios are running at 100% for no reason.
Perhaps worse than that, it takes infinitely longer to charge than it used to. As in, 5+ hours to go from 0% to 100% -- and that's while the phone is powered off. Powered on, it'll take even longer.
I've experienced issues with almost every app, and with some I've had literally no success whatsoever. Facebook freezes half of the time before even loading up. The stock Browser will freeze a few times a day. Alarm Clock Xtreme freezes whenever I try to edit an alarm. Neither the stock Gallery nor third-party image apps will load up any of my photos without freezing. Google Talk won't initiate video chats. The list goes on and on.
Moreover, the phone will often just freeze outright. Sometimes the screen won't light up, regardless of how many times I press the power button. Sometimes the phone gets stuck on the home screen, and responds to nothing. Sometimes the phone becomes unresponsive, although pressing the capacitive buttons still triggers haptic feedback. Because of this, several times a day I just hold power+down to shut it off the hard way.
At this point, I actually avoid using it. It's that useless. It's more burdensome than it is helpful. It sucks because, when it's working, everything is really smooth and the ICS interface is really cool. I can tell it would be awesome, if only it worked.
Has anyone experienced such madness as this?
FYI, I'm running:
Android version 4.0.4
System version 6.16.211.XT912.Verizon.en.US
Baseband version CDMA_N_05.11.01PLTEDC_U_09.11.00
Kernel version 3.0.8-g29cf5e7, [email protected] #1
Build number 6.7.2-180_DHD-16_M4-31
I can't believe they would release something so unstable.
And yes I've gone into recovery and wiped the cache partition several times to no avail.
Click to expand...
Click to collapse
Data wipe, itll fix it. If you dont want to.do.that then root and wipe the cache and dalvik cache.
Sent from my DROID RAZR using Tapatalk 2
AndroidGreg said:
If you wana solution to some problems without wiping the phone, boot into recovery and wipe the cache, fixed my battery and a few other problems, It doesnt remove anything you have done, also it eliminated my lagg problem.
Click to expand...
Click to collapse
This is step 1... see if this fixes it... if not, full wipe.
Erik
Sent from my DROID RAZR using xda app-developers app
syrnett said:
This is step 1... see if this fixes it... if not, full wipe.
Erik
Sent from my DROID RAZR using xda app-developers app
Click to expand...
Click to collapse
+1
ICS is very different from GB, and Motonverizola tried really hard to get ICS to play well with existing GB cache data and GB settings. All of that stuff changed a LOT.
The problem isn't ICS: the problem is data conversion from GB to ICS.
Wipe the cache and dalvik. If that doesn't get it, then do a factory reset and set everything up again.
Mine runs for days with light use (1-3 hours a day), or a day+ with heavy use. It doesn't get hot, unless you mean that the other way. But that'd be kinda creepy.
Hi
This is my first post here at this forum and I'm not a Razr user but thinking about getting the Maxx because of it's hardware and big battery which fits my usage of a smartphone, I have a Galaxy S right now.
I have looked at some of the posts and screenshots of the battery usage on the new leaked/released ICS for the Razr and read about complains about the short lived battery and the devices that overheat, well, we had the same problem when GB has been released to the Galaxy S and that is all related to the Android OS app that is using the battery because it's got into a loop, this will not get fixed unless you make Motorola aware of the problem. I could be wrong but I think that is related to the dalvik-machine. Android OS should be using around a single-digit of the battery of all time (3%-7%), we don't have this issue anymore since Samsung fixed this bug in the later releases of GB firmwares.
A temporary fix of the Android OS is to reboot the phone when you can see that it's hijacking the battery, this is until Motorola fixes the issue.
I wish you all good luck and hope that you will get a better firmware soon.
Its always good practice to start fresh when accepting an update that big. Less variables = less problems.....
Id do a factory reset and start from scratch... that sux... i know, but so does a useless phone
Ics def wasnt all the hype.... but its also not that bad... just gotta start clean.
Good luck!
Complete disaster? How is it a disaster compared to my update? After the update I could no longer receive text messages, Consider the fact that I send a receive hundreds of text messages per day this is honestly the biggest cause of outrage I have with a flagship that can't perform even what a Nokia 6280 could, when I finally receive texts they come in 4 hours late and worse still, in DUPLICATES and I can't seem to find any solution to this as of yet. A factory reset fixes this for an hour at best but the problem suffices after that. Does anyone have a SOLUTION to this? Honestly driving me nuts
I agree with most others... do a factory reset. I always do after a major upgrade (and ICS is a major upgrade!)
Then check what apps you are putting on the machine; some cause issues. For instance, I put the new Starbucks 2.0 app upgrade on my phone yesterday - consumed battery like mad, phone ran hot (like cook-an-egg-on-it hot), runaway processes, etc. Turns out it was the new Starbucks app; after removing it the phone ran normal.
Otherwise I love ICS! So try the cache wipe; and if that doesn't help then do a factory reset and reinstall things. Takes time, but it saves in the long run.
Wow, this is crazy to hear. My update has been flawless but I did a factory reset after getting it. I bet if you did that it would fix 99% of your problems.
I also rooted after and now I'm running a cm9 rom. This is the best my phone has ever run.
Ultimately, even if you don't root you can fix most of these problems with a factory reset.
Sent from my Droid Razr using xda premium
Hold down the Home button to see what's running, download a task manager to see what's dominating the CPU. The phone won't get hot by itself, something is using up the CPU (like you said) if you don't want to factory reset you've got to figure out what it is. Rooting and setting the CPU governor to hotplug will save quite a bit in battery (shuts the 2nd core off when not needed).
I'm on a Canadian leak, the first day battery performance was terrible. By the 4th day, the battery lasted longer than GB
I concur with everyone here about the factory reset.
As other's have mentioned, going from GB to ICS is a major overhaul. I've read elsewhere what this really entails and it's not pretty. Suffice it to say, I backed up all my user apps and data (using Titanium Backup), saved off all other things that were on my internal SD card just to be safe and then applied the OTA update in stock recovery, wiped data and cache and rebooted. I then rooted, installed Safestrap and flashed Eclipse ICS v1.2 RC1 and restored my apps with TiBu.
I also tried stock ROM as well and restored my apps via TiBu.
In both cases, no performance issues nor forced closes. Runs like a champ.
I'm running the latest .214 leak and my battery life has improved over .211.
.214
Razr Maxx
I was having shorter battery life with the ICS .211 build and then updated to .214
My battery life is way better then it ever was with GB or ICS .211
I ran it the other day for 36hrs and 3 of it actually talking on the phone and had 20% battery life left.
It has currently been on for 4hrs 6 min and is at 90%. light email and phone use. I do have an IMAP email account that poles every 10 minutes with push for instant updates.
Mine is running fine after simple reboot
I am getting great battery life and my Razr Maxx is working almost flawlessly after the ICS OTA stock update. I just rebooted it shortly after the update when it was running hot and haven't had any problems since.
If .214 is even better, great.
Looking forward to Jelly Bean to get even more from my device.
Jeff
Was on the soak test and had the same battery problems. Only way to fix was via a factory reset. This did however fix all the problems.
Cant use motocast, it wont connect to my motocast on my mac. So i cant sync my media. How to solve this?
Sent from my XT910 using Tapatalk 2
Thanks for the replies everyone.
As mentioned I have tried booting into recovery and clearing the cache, but it doesn't help.
Some have suggested wiping the dalvik cache. However I don't see that as an option in the recovery menu. Do I need to root to have that option? Excuse my newness to this.
Worst case I guess I'll just have to do a factory reset
abw1987 said:
Thanks for the replies everyone.
As mentioned I have tried booting into recovery and clearing the cache, but it doesn't help.
Some have suggested wiping the dalvik cache. However I don't see that as an option in the recovery menu. Do I need to root to have that option? Excuse my newness to this.
Worst case I guess I'll just have to do a factory reset
Click to expand...
Click to collapse
Its under the advanced menu.
Sent from my DROID RAZR using Tapatalk 2
I'm getting rather fed up with my Rezound. My battery life has been poor, and I am constantly dealing with all sorts of crashes and glitches. I've gone from Sense to AOSP and back again, and since JB came out with working Bluetooth have stuck with JB. I've wiped and started from fresh so many times, and though everything works fine at first, it seems to just be a matter of time. I don't want to nuke all my Titanium Backup backups but I'm getting to the point where I don't know what else to do.
To the point: Is there a way to test and confirm the integrity of the phone's hardware? I know that some PCs can test hardware via BIOS, so I imagine something similar might be possible with mobile devices. This is most likely something that could not be done while running Android, due to the compartmentalization and sandboxing implemented in the OS. I want to test the RAM, NVRAM, and the CPU (possibly with a stress test though this can be done through Android via apps) and find out if there are any hardware issues.
On the other hand, if I'm going in the wrong direction, please let me know. As aforementioned, I'm running JB AOSP, been going back and forth between Wildstang83's CM10 build and Neo's RAGE (currently Infection). I've stopped trying different kernels as my battery life sucks either way. Recovery is AmonRa 3.15, HBOOT is 2.27.xxx, baseband is 2.22.10.0801r/2.22.10.0803r.
Problems include screen freezing on wake (soft keys light up, screen stays dark and doesn't respond); System UI crashing, generally followed by whatever app I'm trying to use such as Messaging, and often results in wallpaper resetting to default; ANRs in Maps and other apps; Phone crashing when trying to make an outbound call; poor battery life (I've killed all startups and stripped down idle run apps to bare minimum, it doesn't help, I replaced the battery about 6 months ago) and various other issues.
Phone has never been wet and has no significant damage; it has worn rather well for being over a year old.
Kernel tuner for "bios" type stuff and stability test for stress testing. Undervolting helps save battery for me. I also use dancedance/badass governor. Idk about your bug problems though, I have had issues with restoring data from old ROMs that completely made a new ROM unusable
Sent from my ADR6425LVW using xda app-developers app
You got a good point. I've just tried a fresh setup, restoring only data for user apps. We'll see how things go.
So here is my current problem: My phone will drastically slow down when trying to multitask. I.e. I basically cant do anything when Pandora is running or ill start to get stops and skips (not connection related), and occasionally, depending on the app, the phone with freeze for an extended period, things disappear from the screen, then it goes blank and back to lock screen asking for pattern rather than fingerprint for "added security." (this is what I'm calling a crash)
Many apps will also start to lag and crash after periods of time, even running on their own. Like tumblr, meetme and facebook.
I have my CPU usage up, and idle is around 7 across the board. Once it starts to creep up above 12-15 is when ill start to get the lagging, lock ups and freezes occur around 20-30, and I've seen it spike as high as ~55 before a crash. Thing is, I'm getting lock ups and freezes while the graphical bar (the red, green, blue one) is barely moving past the CPU usage numbers.
Sorry, I'm not too sure what info to provide. This is a new problem for me. My old phone (running a 1.2ghz quad core, LG optimus G) was able to multitask better than this phone. I never had any skips or freezes while running pandora AND one of those other apps on that phone. Is this a corrupted install? Is this Octo core phone just THAT slow?! I'm not super experienced with ADB, but experienced enough to use it if need be. Any help would be appreciated.
KobaltPanther said:
So here is my current problem: My phone will drastically slow down when trying to multitask. I.e. I basically cant do anything when Pandora is running or ill start to get stops and skips (not connection related), and occasionally, depending on the app, the phone with freeze for an extended period, things disappear from the screen, then it goes blank and back to lock screen asking for pattern rather than fingerprint for "added security." (this is what I'm calling a crash)
Many apps will also start to lag and crash after periods of time, even running on their own. Like tumblr, meetme and facebook.
I have my CPU usage up, and idle is around 7 across the board. Once it starts to creep up above 12-15 is when ill start to get the lagging, lock ups and freezes occur around 20-30, and I've seen it spike as high as ~55 before a crash. Thing is, I'm getting lock ups and freezes while the graphical bar (the red, green, blue one) is barely moving past the CPU usage numbers.
Sorry, I'm not too sure what info to provide. This is a new problem for me. My old phone (running a 1.2ghz quad core, LG optimus G) was able to multitask better than this phone. I never had any skips or freezes while running pandora AND one of those other apps on that phone. Is this a corrupted install? Is this Octo core phone just THAT slow?! I'm not super experienced with ADB, but experienced enough to use it if need be. Any help would be appreciated.
Click to expand...
Click to collapse
I would first try a clean flash/factory reset/cache wipe but is there a reason why you are still using cm13 vs los14? I had no issues with cm13 but los14 is much better anyways.
NinjaL said:
I would first try a clean flash/factory reset/cache wipe but is there a reason why you are still using cm13 vs los14? I had no issues with cm13 but los14 is much better anyways.
Click to expand...
Click to collapse
Los14 was not avail when I was flashing my phone. I use it for business so its always risky to flash and what not. Never had a problem, I just don't wanna risk it. But if this is the case, may as well move to los14.
KobaltPanther said:
Los14 was not avail when I was flashing my phone. I use it for business so its always risky to flash and what not. Never had a problem, I just don't wanna risk it. But if this is the case, may as well move to los14.
Click to expand...
Click to collapse
Ah I see, yeah makes sense haha
Yeah I would backup and then try a clean flash/factory reset if you want to stay on cm13, other than that, I don't know anything general you could do as far as staying on marshmallow goes.
Los14 and Los14 based roms are much smoother however and most of the bugs have been worked out by now. If you're not set on staying with marshmallow, try out some of the nougat roms :good:
Obv you'll want to backup, wipe, flash a rom, flash gapps, wipe cache/dalvik, and reboot but you prob know the drill already haha. You are on twrp or cm recovery?
NinjaL said:
Ah I see, yeah makes sense haha
Yeah I would backup and then try a clean flash/factory reset if you want to stay on cm13, other than that, I don't know anything general you could do as far as staying on marshmallow goes.
Los14 and Los14 based roms are much smoother however and most of the bugs have been worked out by now. If you're not set on staying with marshmallow, try out some of the nougat roms :good:
Obv you'll want to backup, wipe, flash a rom, flash gapps, wipe cache/dalvik, and reboot but you prob know the drill already haha. You are on twrp or cm recovery?
Click to expand...
Click to collapse
Nah, I'm not stuck with MM. I like to stay with the best available, so yeah, I'll definitely go with Los14. Thanks for the input! As long as its smoother and allows me to actually multitask, I'm sold. I tend to use TWRP, but that's probably just because its what I'm used to. The interface is nice. And you can update OTA.
KobaltPanther said:
Nah, I'm not stuck with MM. I like to stay with the best available, so yeah, I'll definitely go with Los14. Thanks for the input! As long as its smoother and allows me to actually multitask, I'm sold. I tend to use TWRP, but that's probably just because its what I'm used to. The interface is nice. And you can update OTA.
Click to expand...
Click to collapse
Yeah twrp is what I use too :good:
Hi All knowledgeable folks / @linusdan
Ok, so I've tried to re-build my dad's S2 (i9100P) which he has had for a couple of years. All appeared ok at first, although suffering battery drain recently... He tried a couple of batteries, as he has about 2 or 3 batteries lying around (as they are so cheap). Neither seemed to make much difference, so I said I would wipe the phone and start again. Whilst switching in and out of Recoveries, I noticed the battery go from like 93% to 80% to 60% to 20% to 13% in a very very short time. Equally strange when it was at its lowest, 13% and leaving it charging for a few minutes... say around 15 minutes, it then jumps up to like 70%.
So I switch the battery over for another one. I have a little play around with the phone, thought I'd try a new Android 9 / PIE rom and use Emulated Storage. However I thought this rom, as amazing as it is... would not be for my dad. I tried a couple of others out, and dropped him down to a Android 6 / Marshmallow rom. Purely based on speed, lean and fairly decent battery usage. I took the phone to the pub, played around and all seemed good. Stable, no crashing, but due to playing around... Thought I'd flash it again, and start a fresh.
However now...
Straight after flashing the rom, it will constantly reboot at the login screen. If I unlock the phone, then things like the default Launcher will crash, as will Google Music, Settings and File Manager. So I tried another rom, Nougat and Lollipop, and they both randomly crash too...
So I hooked it up to Odin, and used the STOCK partition (PIT) file and STOCK rom (Orange UK 4.1.2) and returned it back to FACTORY settings. Now all seems good again, battery seems to last a long time and had ZERO crashing since back to stock. However, so that he can use a Smartwatch I got him, he needs a minimum of KitKat on the phone....
However, why do you think the phone will be constantly crashing now ?? Has something died inside, and what could of died?? Why is it stable on stock and not on custom roms?? It used to be fine on customs before hand...?? Any idea's??
Model: i9100P
ROM: Resurrection Remix LP, MM, N, O... and Pixel PIE. Currently back to Resurrection Remix MM.
Partition: RePit, 2GB System, 6GB Data, rest to SDCard
Batteries: Tried a couple of batteries, still got a couple more could tried... all supposedly genuine...
Cheers, Lister