Related
I had a SGS i9000 before. I flashed it serveral times with different OS an different programms and even bricked it one time.
I recovered it with my hommade JIG.
No matter what ROM/kernel i always had battery-drain in cell-standby-only without any apps installed/sync.
Now on my Nexus S i'm very satisfied with the standby-time (2.3.4 stock, locked, VDF i9023)
I'd like to root it and install CWM and maybe a custom kernel.
Now my question: Is anybody out there who had a good batterylife on his Nexus S before flashing and a bad after flashing?
basti107 said:
I had a SGS i9000 before. I flashed it serveral times with different OS an different programms and even bricked it one time.
I recovered it with my hommade JIG.
No matter what ROM/kernel i always had battery-drain in cell-standby-only without any apps installed/sync.
Now on my Nexus S i'm very satisfied with the standby-time (2.3.4 stock, locked, VDF i9023)
I'd like to root it and install CWM and maybe a custom kernel.
Now my question: Is anybody out there who had a good batterylife on his Nexus S before flashing and a bad after flashing?
Click to expand...
Click to collapse
Consequences of flashing:
1 Getting addicted and flashing a new ROM every day
2 Visting XDA every minute of free time which leads too....
3 ... neglecting family and losing job
But in all seriousness my battery life has always been around 18 hours with mdoerate usage
bringonblink said:
Consequences of flashing:
1 Getting addicted and flashing a new ROM every day
2 Visting XDA every minute of free time which leads too....
3 ... neglecting family and losing job
But in all seriousness my battery life has always been around 18 hours with mdoerate usage
Click to expand...
Click to collapse
Very true for 1 and 2 but not really the number 3 as I have controlled by parents. LOL/
But yes, the battery life has always been around 18 hours
I have tried 4 different radios and this phone still randomly reboots with frequency. I am the the 802 radio and it seems even worse then earlier radios. I am currently on gingerritis rom which i installed yesterday and have probably had 12 reboots since then.
Is it a combination of the rom and radio, or does just the radio make the phone reboot? I am really just tempted to flash it back to stock, sell it with the warning of this phone enjoys random reboots and get another phone.
while i typed this up it just rebooted twice on its own
I dont think the radio is what is going to fix the reboot issue. I know for some of the roms the fix was flashing the ziggy kernel.
Maybe give that a shot.
brownsfan said:
I dont think the radio is what is going to fix the reboot issue. I know for some of the roms the fix was flashing the ziggy kernel.
Maybe give that a shot.
Click to expand...
Click to collapse
If hes using gingeritis, hes already using ziggy's kernel. Sounds weird i know, but try a new battery
Sent from my TBolt using my f***king thumbs...
i think overclocking to high and all the kernel cpu mods are whats causing this, not the radios.
fixxxer2008 said:
i think overclocking to high and all the kernel cpu mods are whats causing this, not the radios.
Click to expand...
Click to collapse
I agree. Ziggy's stock voltage settings are very conservative north of about 1.5GHz. If you're tweaking it, definitely pay attention to the voltage.
nope not touching voltage or overclocking, i just put rom on thats about as far as i go tweaking phone.
Installed M0N0LITHTH3ORY rom and so far no reboots today, the gingeritis one must hate my phone cause in the less than 24 hours it was on the phone damn thing rebooted easy 10 times. But now this one is giving me some unexpected errors with weather app. I will give this one a week and see how it does and if no good on to next rom i guess.
-magnum- said:
nope not touching voltage or overclocking, i just put rom on thats about as far as i go tweaking phone.
Installed M0N0LITHTH3ORY rom and so far no reboots today, the gingeritis one must hate my phone cause in the less than 24 hours it was on the phone damn thing rebooted easy 10 times. But now this one is giving me some unexpected errors with weather app. I will give this one a week and see how it does and if no good on to next rom i guess.
Click to expand...
Click to collapse
Have you ever formatted /system?
yeah every time i put new rom i go into clockwork recovery
i wipe / factory reset
then format /system /cache /data
and wipe davlik cache
then install rom
double post...
i know my phone didnt like a few different roms. try a diffeerent one. also try doing each step 3 times. i did that after my phone rebooted on an a0sp rom by droidtheroy, after that it worked just fine on the rom that was rebooting
You know what? I was having the same problem and tired as hell of my TB. I was so tired of the little problems and the large rebooting problem that I had learned to really hate this phone.
A few days ago I decided to just use the new leaked, stock, unrooted, GB 210 RUU and give that one more try before I either took a hammer to this phone or unrooted and tried to get VZW to replace it.
I've had the latest leaked RUU on this phone for a few days now and I'm loving it again. Yeah, stock, unrooted, but also super fast GPS locking, fast 3g/LTE switching, no more reboots, not one. Battery is actually not bad at all after turning off a few of the stock bloat like Blockbuster. The gui is fast and smooth, I can't say whether or not it is as fast as it was when I was running custom ROMs but as far as I'm concerned its a big who cares. I now have a nicely working phone again. This is just my experience and my opinion, YMMV!
R
-magnum- said:
I am currently on gingerritis rom which i installed yesterday and have probably had 12 reboots since then.
Click to expand...
Click to collapse
I got reboots with gingeritis and liquid ROMs, I've had no reboots in a week now running Virus' Synergy ROM. Try a different ROM, it should fix your problems.
Here's a link to Virus' work:
http://forum.xda-developers.com/showthread.php?t=1003891
Second the ROM recommendation. Try a different one. I had the same issue with wanting to grenade this thing until I found a combo of ROM and radio that was stable for my use and applications.
Now I wouldn't think of tossing this phone.
Sent from my ADR6400L using Tapatalk
Stability and battery life good for me with stock 1.70.605.0. Currently at 868 hours uptime.
yeah i am on monolith rom and so far no reboots, i am going to give this one a shot for now, hopefully this cures it.
I Rooted my Phone some time ago, i have installed some roms, some run good, some freezes my phone up, have remove my battery.
so what I need more info on, is should i do like I read about the Radio?, Kernel?, and then ROM?
What I show,
Kernel Version
2.6.35.14-RCMIX3D-V12-CRD-gec898d5-dirty
Baseband Ver: ( Radio)
12.29.60.19U_26.06.04.06_M
ROM
RunnyDroid v3.0
I have StraightTALK Sims, all DATA, SMS all working,
My Battery dose not last so long, 3 to 4 hrs, mostly not in use.
I seen a lot of post talking about this rom, and that rom works the best. or the battery last for 7+ hours.
My phone is not running a lot of apps, I even uninstalled my Anti-Virus.
I have to keep my phone on the Charger a lot. I even bought a New battery and same thing.
Thanks
Have you tried recalibrating the battery? Also, how much "screen -on" time during your 3-4 hours use?
Sent from a payphone!
Sorry, just noticed you said mostly not in use.
There's a apps you can download from the market- Battery Recalibration and Current Widget...with these 2 tools and a little knowledge of what running app/services are doing, you can track what's going on.
Or, you could just simply have a bad battery or a gooned-up flash (it happens).
Hope this helps.
Sent from a payphone!
Dinman said:
Sorry, just noticed you said mostly not in use.
There's a apps you can download from the market- Battery Recalibration and Current Widget...with these 2 tools and a little knowledge of what running app/services are doing, you can track what's going on.
Or, you could just simply have a bad battery or a gooned-up flash (it happens).
Hope this helps.
Sent from a payphone!
Click to expand...
Click to collapse
On the contrary, battery calibration has been proved to be nothing more then just a peace of mind type of procedure and really not a huge benefit. My advice would be to get Current Widget and fully charge your phone. Unplug it and let it sleep for about 6-8 hours with current widget logging the mA drain (the log is an option in the app itself, you just need to enable it). After the 6-8 hours ( I normally do this when I sleep so I know the phone is not in use) check the log and see if there is any weird mA drain. weird would look something like
1ma
3ma
180ma
230ma
1ma
2ma
Normal would be:
1ma
1ma
4ma
5ma
1ma
You get the picture hopefully haha. If you have weird drain then best bet would be to full wipe and reinstall the rom and individually install your apps one at a time and monitoring the mA usage to see what apps cause the drain and what doesn't. You can also try new radios with their matching RILs and see if that helps. There are also apps like Juice Defender and Green Power that have been said to improve battery life up to 2x. Hope that helps.
I have tested apps, done the ( Let the battery die, and then charge wait off to give a more of it charge.
buggme said:
I have tested apps, done the ( Let the battery die, and then charge wait off to give a more of it charge.
Click to expand...
Click to collapse
let your phone die and then recharging it fully does nothing for abnormal battery drain. So in that regard the only thing you proved to yourself was that your phone can charge properly. Are you 100% sure you are running the proper radio for the ROM or have the matching RIL for your radio? I still think its an app running in the background that is causing your problem. Are you sure that you full wiped and reinstalled the rom. Then with each app you want, install one. wait for 30 minutes and allow current widget to log the mA activity. Check the log to be sure there are no crazy spikes in mA and proceed to the next app repeating the same process. I know its annoying but that's the only way to be sure that your apps aren't causing the drain.
Also consider turning off sync, which I've heard can be a battery drainer. Turn off wifi as well when need in range since the scanning for wifi causes battery drain as well.
I really don't know, when I first got the phone, I Rooted it and unlocked it.
I Do have straight talk Sim I have been using.
all I did was change the ROM( I Think).
with all the little problems I'm having, I was think I have a lot wrong with it!
So I was going to download a need ROM, I seen talk about Radios, or RIL, and ROMS.
so No I don't know If I have everthing right.
I wasl looking atRCMixHD 4G V3.4 ROM, and if I used it, what Radio and RIL would I need.
having Stright Talk Service, witch runs on ATT, with difference APN settings.
what Would I need?
Thanks. Terrell
Usually, the ROM has all the correct radios, RILs, kernels etc inside the ROM itself and you would only need to change if you had some need for a different radio, like if you got poor service where you live. Kernels are dictated by the ROM.
jimcasey1768 said:
Usually, the ROM has all the correct radios, RILs, kernels etc inside the ROM itself and you would only need to change if you had some need for a different radio, like if you got poor service where you live. Kernels are dictated by the ROM.
Click to expand...
Click to collapse
And where did you get your info? Custom ROMs do not include radios.
Agoattamer said:
And where did you get your info? Custom ROMs do not include radios.
Click to expand...
Click to collapse
And that's why I asked. I need to set down one day and search, read, test,
On a different note.
All I can say is wow. 2,000,000 Roms and I still not know LOL. Thanks for all the info so far.
When you install a custom ROM it will include ROM, a certain RIL, and the kernel that the DEV has used with the ROM all in one package. The DEV will USUALLY let you know what the recommended radio should be to match the included RIL. You could flash it before or after you flash the ROM.
If you are having battery issues I would first start with a new battery. If you have already done that then flash a simple ROM for testing purposes. Stay away from highly tweaked and modified ROMs with a kernel set up for overclocking. I recommend juicy ROM from my sig. Install the 2.52 (R2) version which is still sense 2.5 and gingerbread 2.3.3. The ROM is flawless and you will get the best battery life than from anyother ROM. SEE how your battery lasts with it.
If you have your brightness set high, have many apps running in the background, are in an area where your signal is poor and is constantly lost, are syncing many accounts constantly, and you can't seem to put your phone down, then your battery will not last that long.
aospX rom problem
I installed the asopX rom and when my phone rebooted its stuck at a colorful animation screen. it's been doing it for a few hours... not sure if its still installing or stuck. Anyone ever experience this or know whats going on?
danielminter85 said:
I installed the asopX rom and when my phone rebooted its stuck at a colorful animation screen. it's been doing it for a few hours... not sure if its still installing or stuck. Anyone ever experience this or know whats going on?
Click to expand...
Click to collapse
Its bootlooping (not good) ...I would suggest to boot back into recovery and wipe and check your md5 sum & reflash or redownload file if needed.
Sent from a payphone!
dang!! that sucks! How do you do that?
danielminter85 said:
dang!! that sucks! How do you do that?
Click to expand...
Click to collapse
bootlooping isn't the end of the world. It only becomes an issue if you can't boot into HBOOT. You can boot into HBOOT by turning off the device and then holding the volume up and power button at the same time. You will then boot into HBOOT. From here your device will scan for a "PD98IMG.zip". I'm guessing since you don't know how to get into HBOOT then you've probably haven't flashed a radio so you shouldn't have a stray PD98IMG.zip on your sdcard. After it scans and doesn't find a a PD98IMG.zip you will be given a few options. One of which will be to boot into recovery. Do that. From there you can check the md5 (if you're using EXT4 recovery). If you want you can re-download another ROM and from recovery you can mount your SDcard so you can put the new ROM on your sdcard and flash per usual.
After a search, I know other people have had this issue with the MT4GS. I'm currently running Virtuous Inquisition 4.02. I'm pretty sure i've flashed any updates. Also, I don't remember having this issue on any other ROM that I have ran in the past (virtuous unity, CM 7). The issue is the soft keyboard not responding randomly to certain keys. The weirder thing is if i use a different finger, it usually responds, but if i keep using the same finger, it won't. Is this my digitizer going bad, or just a soft keyboard thing? I haven't experienced the issue in any other part of android, just when using the soft keyboard. is there a touchscreen driver to flash or anything i can do to fix this? thank you!
At least someone else has my same problem
anitgandhi said:
After a search, I know other people have had this issue with the MT4GS. I'm currently running Virtuous Inquisition 4.02. I'm pretty sure i've flashed any updates. Also, I don't remember having this issue on any other ROM that I have ran in the past (virtuous unity, CM 7). The issue is the soft keyboard not responding randomly to certain keys. The weirder thing is if i use a different finger, it usually responds, but if i keep using the same finger, it won't. Is this my digitizer going bad, or just a soft keyboard thing? I haven't experienced the issue in any other part of android, just when using the soft keyboard. is there a touchscreen driver to flash or anything i can do to fix this? thank you!
Click to expand...
Click to collapse
It isn't anything related to the digitizer aparently. I say this because it never gave me a problem using stock rom. This usually happens when the phone gets too hot (you can feel this on the touchscreen). It starts lagging from what i could see, i mean my touches are not recognized properly.
If anyone has a screen calibration .zip laying around i would highly appreciate you to share it
ahh ok thanks for the info. after flashing cm 9.1.0 i can definitely tell the phone isn't getting as hot (according to spare parts, on inquisition the battery would go upwards of 35 celsius regularly, with cm it hasn't gone above 25), and the issue isn't happening anymore. thanks for the help!
rafaelrfq said:
It isn't anything related to the digitizer aparently. I say this because it never gave me a problem using stock rom. This usually happens when the phone gets too hot (you can feel this on the touchscreen). It starts lagging from what i could see, i mean my touches are not recognized properly.
If anyone has a screen calibration .zip laying around i would highly appreciate you to share it
Click to expand...
Click to collapse
You won't believe it but I do have something. This will help to increase sensitivity but for the life of me I can't remember where I got it.
anitgandhi said:
ahh ok thanks for the info. after flashing cm 9.1.0 i can definitely tell the phone isn't getting as hot (according to spare parts, on inquisition the battery would go upwards of 35 celsius regularly, with cm it hasn't gone above 25), and the issue isn't happening anymore. thanks for the help!
Click to expand...
Click to collapse
That's something I just can't understand...when people have troubles with Virtual Inquisition, that is. My wife runs it ALWAYS and I will jump back to it at least once a month for a while myself. It's always been one of the most stable, coolest running and longest battery life ROMs in my nandroids of my favorites. ANYway....give that flashable a try & see if it helps. The best I remember, you can reflash it until you achieve the sensitivity you're looking for. Good Luck!
WeekendsR2Short said:
That's something I just can't understand...when people have troubles with Virtual Inquisition, that is. My wife runs it ALWAYS and I will jump back to it at least once a month for a while myself. It's always been one of the most stable, coolest running and longest battery life ROMs in my nandroids of my favorites. ANYway....give that flashable a try & see if it helps. The best I remember, you can reflash it until you achieve the sensitivity you're looking for. Good Luck!
Click to expand...
Click to collapse
inquisition definitely was very stable and had great battery life, there is little doubt about that. i'm guessing i just didn't flash it correctly, and that caused some really high temps. other than that, i had no issues with it...for example, though, when i was running inquisition, if i left the phone in my pocket and forgot about it until say someone texted me/called me/i got a notification, and i checked the temps, it was at 30-35 celsius, and felt burning. again, i'm guessing i didn't flash it right.
also, thanks for the touchscreen fixer zip, if i have the issue again, i will flash it. fingers crossed i don't need it.
side questions about kernel flashing: 1) do i wipe cache and dalvik cache then flash the kernel zip? 2) is there a way to go back to the original kernel without having to flash the rom all over again?
thanks!
anitgandhi said:
inquisition definitely was very stable and had great battery life, there is little doubt about that. i'm guessing i just didn't flash it correctly, and that caused some really high temps. other than that, i had no issues with it...for example, though, when i was running inquisition, if i left the phone in my pocket and forgot about it until say someone texted me/called me/i got a notification, and i checked the temps, it was at 30-35 celsius, and felt burning. again, i'm guessing i didn't flash it right.
also, thanks for the touchscreen fixer zip, if i have the issue again, i will flash it. fingers crossed i don't need it.
side questions about kernel flashing: 1) do i wipe cache and dalvik cache then flash the kernel zip? 2) is there a way to go back to the original kernel without having to flash the rom all over again?
thanks!
Click to expand...
Click to collapse
Wipe user data/cache .....cache....dalvik....battery stats. All of them 3 times. (CWM has some small issues getting everything on the first shot) Then you flash your Rom. Let it set a minute or two. Lastly....Flash your Boot.img. Be sure not to just let windows just show what's in the .zip file and copy it out but highlightit and open it with Winzip (or whatever you use). EXTRACT it to where you flash your files from. If you don't do it like that it will remain partially compressed and you'll forfet the parts of your kernel that are. Once flashed, let it rest for 5 minutes and you should be good to go.
If flashing another ROM ALWAYS follow those rules but if reflashing with another kernel you can forgo clearing user data so you will keep your apps & their placement in your ROM. Just clear everything else reflash your ROM again & then your kernel. It will look just like it did but with the new kernel. If by chance you then have an issue with force closes just go back to recovery & fix permissions & it should straighten that right out.
BTW....If you are unlocked & S-On you will not be able to flash it from recovery in any form or fashion. You will always need to extract the boot.img file and "ADB fastboot flast boot boot.img" from your command window.
WeekendsR2Short said:
Wipe user data/cache .....cache....dalvik....battery stats. All of them 3 times. (CWM has some small issues getting everything on the first shot) Then you flash your Rom. Let it set a minute or two. Lastly....Flash your Boot.img. Be sure not to just let windows just show what's in the .zip file and copy it out but highlightit and open it with Winzip (or whatever you use). EXTRACT it to where you flash your files from. If you don't do it like that it will remain partially compressed and you'll forfet the parts of your kernel that are. Once flashed, let it rest for 5 minutes and you should be good to go.
If flashing another ROM ALWAYS follow those rules but if reflashing with another kernel you can forgo clearing user data so you will keep your apps & their placement in your ROM. Just clear everything else reflash your ROM again & then your kernel. It will look just like it did but with the new kernel. If by chance you then have an issue with force closes just go back to recovery & fix permissions & it should straighten that right out.
BTW....If you are unlocked & S-On you will not be able to flash it from recovery in any form or fashion. You will always need to extract the boot.img file and "ADB fastboot flast boot boot.img" from your command window.
Click to expand...
Click to collapse
i'm s-off so i don't need to worry about the boot.img extraction and all that, but the rest was very helpful, thank you very much!
:good:
anitgandhi said:
it was at 30-35 celsius, and felt burning.
Click to expand...
Click to collapse
Whenever anyone mentions overheating issues with the device - the first questions should always be:
Are you on a stock battery?
If so, then that is your problem.
I've forgotten to manage setcpu and left it running at 1.7 more often then anything, yet very rarely run into overheating issues...unless I go back to a stock battery (even without overclocking)
Blue6IX said:
Whenever anyone mentions overheating issues with the device - the first questions should always be:
Are you on a stock battery?
If so, then that is your problem.
I've forgotten to manage setcpu and left it running at 1.7 more often then anything, yet very rarely run into overheating issues...unless I go back to a stock battery (even without overclocking)
Click to expand...
Click to collapse
i am on stock battery. good to know that it usually causes overheating...glad it's not happening with cm 9.1.0 though
WeekendsR2Short said:
You won't believe it but I do have something. This will help to increase sensitivity but for the life of me I can't remember where I got it.
Click to expand...
Click to collapse
the issue came back (although not as frequently) so i went to flash the zip that you attached... it says it's something relating to beats audio and then it errors out and the installation aborts. i looked at the files inside all have "beats" and "audio" in the filenames...
Hi all
i had my OPO for 2 months now
and i decided to root my phone and try some custom ROMs and kernels since they're so popular , so last month i rooted my phone and take a spin on those famous ROMs and kernels ( partly is also the touchscreen issue and random reboots are driving me nuts ) i won't specify what ROM or kernel i am using though
first impressions when i had a new ROMs is that , there's nothing much that is different i though things would be faster snappier with a new kernel built in but ...my OPO did not , my phone did get more stable but it did suffer from multigesture issue once and force rebooted 3 times in the span of 1 month , but the biggest issue is that my phone keeps getting systemui has stopped working , multitasking button gets bugged one too many times , wallpapers constantly missing when i unlock my phone and animations are very clunky
so yesterday i decided to go back to stock just to remind myself how stock feels , using NANdroid backup i restored everything and...
stock 44s feels so much better compared to custom ROMs which begs the question
why do people deviate from stock ROM on OPO ? stock cm is pretty sweet , I understand rooting the phone to get xposed etc but custom ROMs just don't feel right on the OPO ...so is it just me ?
still props to all the devs out there , no offense just my 2 cents
I think if varies for the phones and locations, but I was getting some pretty beastly battery life, smooth/fast experience with vanir and Franco. For some reason I just didn't like stock and was not getting as great battery life. I've tried many things and some are good, but there are better (to me at least). I'm just running Lollipop now and can't seem to go back to kk.
It all comes down to ones preference really...
Sent from my A0001 using XDA Free mobile app
wait , isn't cm12 for OPO currently a little unstable? i really wanted to give it a shot but i fear that it is too unstable for a daily driver
Working fine for me; I don't think it is to the point where it can't be a daily driver. I'm really liking it so far, the Lollipop experience feels really nice and smooth.
Check comments from others on the threads to see the kind of issues they're having. Devs are doing daily builds so as days pass it gets better and better.
Sent from bacon with lollipop!
tohno said:
Hi all
i had my OPO for 2 months now
and i decided to root my phone and try some custom ROMs and kernels since they're so popular , so last month i rooted my phone and take a spin on those famous ROMs and kernels ( partly is also the touchscreen issue and random reboots are driving me nuts ) i won't specify what ROM or kernel i am using though
first impressions when i had a new ROMs is that , there's nothing much that is different i though things would be faster snappier with a new kernel built in but ...my OPO did not , my phone did get more stable but it did suffer from multigesture issue once and force rebooted 3 times in the span of 1 month , but the biggest issue is that my phone keeps getting systemui has stopped working , multitasking button gets bugged one too many times , wallpapers constantly missing when i unlock my phone and animations are very clunky
so yesterday i decided to go back to stock just to remind myself how stock feels , using NANdroid backup i restored everything and...
stock 44s feels so much better compared to custom ROMs which begs the question
why do people deviate from stock ROM on OPO ? stock cm is pretty sweet , I understand rooting the phone to get xposed etc but custom ROMs just don't feel right on the OPO ...so is it just me ?
still props to all the devs out there , no offense just my 2 cents
Click to expand...
Click to collapse
Sounds like you didn't do any kernel configurations at all to experience changes.
On AK, with Synapse and UKM, you can change numerical values to configure how the phone handles processes. Default kernel settings aren't optimum for every phone.
My settings consist of: slim (300-2457), CPU boost driver (10ms, 1574MHz, 30ms, 1190MHz), CPU Volt (-35mV), I/O sio @ 1536KB read ahead, drop caches, laptop mode, Vibrator at 25, Fast Charge at 1500mA, C1 (Retention) disabled, 120 second Wifi Scan interval.
With those settings, it makes a HUGE difference compared to stock, as well as fix bugs (screen artifact/tearing) before they were fixed on the latest firmware, and increases battery life by 1.5 times stock.
tohno said:
Hi all
why do people deviate from stock ROM on OPO ? stock cm is pretty sweet , I understand rooting the phone to get xposed etc but custom ROMs just don't feel right on the OPO ...so is it just me ?
still props to all the devs out there , no offense just my 2 cents
Click to expand...
Click to collapse
I have the same questioning but without any problems that you had/have/ My phone works perfectly ( crossing fingers ) and i've had it since July. I always used to ROM my S3-S4-S5 to get a new feel of the phone, but with the Oppo i don't see the reason to. Maybe it's because CM is pretty near pure stock Android, and that's what we get when we switch ROMs on big brands.
tohno said:
Hi all
i had my OPO for 2 months now
why do people deviate from stock ROM on OPO ? stock cm is pretty sweet , I understand rooting the phone to get xposed etc but custom ROMs just don't feel right on the OPO ...so is it just me ?
still props to all the devs out there , no offense just my 2 cents
Click to expand...
Click to collapse
OP, it is not just you. Folks who mess about with custom ROMS, as the other posts here share, do so because they can customize the total phone experience, leaving things off, and putting other items on, to their liking. Giving that the background OS is stable, and the apps a person selects are stable, there should be little to no difference in 'performance', overall, due to the apps. However, you may get performance differences because there are less TSR's currently running in your system, so more memory is available, etc, which can make mainline apps run faster.
So many reasons to do custom apps.
As you said, and I agree, CM is a nice, generally smooth OS/ROM. I am coming from an LG G3, which I like very much, but to customize (remove all the junk), and fine tune (remove Google calling home = less battery live, etc), it take's some time to setup those conditions. With CM, most of the junk is not present at the onset (AT&T largely). Much more clean. I would like Google to be disassociated from CM completely, so that it is an add on only, providing better control of the base CM. I would like this in an official CM ROM/official variation.
That is the reason I have/am switching over to the OnePlus. I have tried a few custom ROMs as well, and the stock CM seems to have the best stability, reliability and consistency, to date. I suspect that will change when a large update comes out, such as L, and a great amount of energy goes into that development. I just changed from 38 to 44 last night on three OPO's. It took 5 minutes, or so, a piece, and all of the data/previous apps, setup etc, stayed with the updates, making for an all too easy update.
Awesome. Next will be "L". I will wait for the CM official, as that will likely be the most stable, as I suspect it is getting the most attention from the CM team, at this time. CM is a pretty nice OS.