I recently installed CM10.0 (The stable release) on my gs3, and I'm not too happy with the severe battery drain and glitchy lockscreen, so I want to swicth back to a TouchWiz based ROM that will provide a good balance of performance and great battery life. I have two questions. First, is there anything special I have to do with transitioning back to TouchWiz from CM10.0? I know I had to install the gapps package, but the factory wipe should remove that right?
Also ROM suggestions for stable performance with ability to tweak more settings, but at the same time retains healthy battery life? After researching a bit, CleanROM or Synergy seem like my best bet, but I would like opinions from more experience users than myself, I'm still pretty new to this.
Thank you in advance! :good:
i wipe data, cache, dalvik in between roms.
if im going to 4.2 to TW or TW to 4.2 or whatever.
if you like the looks of AOSP but the function of TW flash Beans build 10. you WILL NOT regret it.
xNali said:
I recently installed CM10.0 (The stable release) on my gs3, and I'm not too happy with the severe battery drain and glitchy lockscreen, so I want to swicth back to a TouchWiz based ROM that will provide a good balance of performance and great battery life. I have two questions. First, is there anything special I have to do with transitioning back to TouchWiz from CM10.0? I know I had to install the gapps package, but the factory wipe should remove that right?
Also ROM suggestions for stable performance with ability to tweak more settings, but at the same time retains healthy battery life? After researching a bit, CleanROM or Synergy seem like my best bet, but I would like opinions from more experience users than myself, I'm still pretty new to this.
Thank you in advance! :good:
Click to expand...
Click to collapse
Hey xNali,
I was in a similar position, in which I went from TW to CM10 stable, back to TW. To go back, all I did was, in Clockworkmod recovery, wipe the phone/factory restore, wipe cache, wipe dalvik cache, and then flashed the TW ROM.
As to your second question, I am using CleanROM 5.6 w/ lean kernel. I am only on the first battery cycle with very minimal usage (less than 1 hour of screen time), and I got about 1 day and 5 hours of battery life on it. Thus far, CleanROM seems to be very stable and I have yet to experience any issues - no apps crashing, wifi, BT tether all work, no screen flickering. At the same time, I use my phone primarily for work emails, so others on the board may be able to provide better advise.
In addition to CleanROM and Synergy, Jelly Beans also seems to be very popular (based solely on the # of posts in that thread).
JOLiu said:
Hey xNali,
I was in a similar position, in which I went from TW to CM10 stable, back to TW. To go back, all I did was, in Clockworkmod recovery, wipe the phone/factory restore, wipe cache, wipe dalvik cache, and then flashed the TW ROM.
As to your second question, I am using CleanROM 5.6 w/ lean kernel. I am only on the first battery cycle with very minimal usage (less than 1 hour of screen time), and I got about 1 day and 5 hours of battery life on it. Thus far, CleanROM seems to be very stable and I have yet to experience any issues - no apps crashing, wifi, BT tether all work, no screen flickering. At the same time, I use my phone primarily for work emails, so others on the board may be able to provide better advise.
In addition to CleanROM and Synergy, Jelly Beans also seems to be very popular (based solely on the # of posts in that thread).
Click to expand...
Click to collapse
Thanks for the advice. I'm getting like 12-15 hours with very minimal usage which is pathetic to me. I've never flashed a kernel before, can you link a thread for me?
ddurandSGS3 said:
i wipe data, cache, dalvik in between roms.
if im going to 4.2 to TW or TW to 4.2 or whatever.
if you like the looks of AOSP but the function of TW flash Beans build 10. you WILL NOT regret it.
Click to expand...
Click to collapse
Awesome that is essentially my issue are the bugs which I completely understand, because they are still doing nightlies to perfect it. How's your battery life?
xNali said:
Thanks for the advice. I'm getting like 12-15 hours with very minimal usage which is pathetic to me. I've never flashed a kernel before, can you link a thread for me?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2116415
I can't find the thread, but another thing I remember reading was to install CleanROM and, while still in recovery, flash the kernel (find Lean Kernel here - make sure you download the TW kernel, and not the AOSP one).
Once the kernel is flashed, and before you reboot, someone suggested clearing cache, dalvik cache, fix permissions, and then reboot. No idea what fix permissions does, and how it affects how the ROM and kernel run.
Also, what others have said is to allow the ROM to settle a few battery cycles to see the full effect of the ROM/kernel. Again, I have no idea how this has any effect on battery life, but a lot of people seem to swear by it.
Hope this helps.
I will give that a shot tomorrow. My other worry is I had to revert back to stock when I was flashing CM10 the first time because it was stuck on roaming and on stock you cannot change from NV to RUIM/SIM and it was stuck on roaming. Is there an option in CleanROM to change it or will it be ok when I flash it? I was stuck on roaming and had to flash back to CM10 change the setting then flash back to stock.
Sent from my SCH-I535 using xda app-developers app
xNali said:
I will give that a shot tomorrow. My other worry is I had to revert back to stock when I was flashing CM10 the first time because it was stuck on roaming and on stock you cannot change from NV to RUIM/SIM and it was stuck on roaming. Is there an option in CleanROM to change it or will it be ok when I flash it? I was stuck on roaming and had to flash back to CM10 change the setting then flash back to stock.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
You'll be fine when you flash clean ROM 5.6. When you're wiping cache and dalvic you shoul also format system. That will insure that you get a good clean install. Also is your imei backed up just in case? There is a thread on how to back it up if you need to.
Sent from my Nexus 7 using xda app-developers app
Related
Hi guys,
I was wondering, is there a decent way to revert to the 1.0.0 EOS Rom when coming from the 2.0.0 Stable or latest nightly?
Keeping in mind that I deleted my 1.0.0 backup a while ago.
Thanks!
First make a backup of your apps and your current ROM. Flash EOS 1.0 and gapps and wipe cache. Attempt to boot. If it loops or FCs, then wipe data and cache and reflash.
Sent from my MB860 using xda premium
If you want to have all your apps and appdata backed up with it, I would do what was suggested above, but also use Titanium Backup to back up apps and appdata. However, restoring the apps can be tedious, especially if you have many. This is because you would have to hit install for each one of them. For that reason, i'd spend a couple bucks and actually get Titanium Backup Pro, because it is just so much more convenient, for it does everything automatically.
d3athsd00r said:
First make a backup of your apps and your current ROM. Flash EOS 1.0 and gapps and wipe cache. Attempt to boot. If it loops or FCs, then wipe data and cache and reflash.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Thanks, will follow your instructions to the letter Do I need to wipe data?
yosterwp said:
If you want to have all your apps and appdata backed up with it, I would do what was suggested above, but also use Titanium Backup to back up apps and appdata. However, restoring the apps can be tedious, especially if you have many. This is because you would have to hit install for each one of them. For that reason, i'd spend a couple bucks and actually get Titanium Backup Pro, because it is just so much more convenient, for it does everything automatically.
Click to expand...
Click to collapse
Thanks, I already have Titanium BU Pro, so I am doing a backup right now.
Do any of you know why when trying to install EOS 1.0.0 earlier the device's recovery said installation aborted after a few seconds?
Thanks!
Is this with EOS 2.0.0 already installed?
Perhaps you should download EOS 1.0.0 again. Maybe the download got corrupted.
yosterwp said:
Is this with EOS 2.0.0 already installed?
Perhaps you should download EOS 1.0.0 again. Maybe the download got corrupted.
Click to expand...
Click to collapse
Will do so! .
Thanks for the help. I don't want a bricked Xoom I just want a battery efficient ICS from for my holidays coming up
Should I wipe data as well before flashing 1.0.0?
Thanks
I guess since you have a backup of all your apps, it would be safe and smart to wipe data.
Most recoveries don't wipe the internal storage (movies, music, pictures etc), however, i'd back the important things on your Xoom that are on your storage to a computer or to a sdcard, just in case something goes wrong.
yosterwp said:
I guess since you have a backup of all your apps, it would be safe and smart to wipe data.
Most recoveries don't wipe the internal storage (movies, music, pictures etc), however, i'd back the important things on your Xoom that are on your storage to a computer or to a sdcard, just in case something goes wrong.
Click to expand...
Click to collapse
Titanium is doing everything in its power to bug me .
It keeps on giving 0% backed up. Clearly, the app has turned against me lol
What now
Edit: TB worked after a couple of tries...
I still get that error message when installing EOS 1.0.0 (after wiping everything) even though I redownloaded the Rom.
Is it because of the fact that I am in 4.0.4 whereas EOS 1.0.0 is in 4.0.3 and thus I am downgrading?
Thanks
I still get that error message when installing EOS 1.0.0 (after wiping everything) even though I redownloaded the Rom. Is it because of the fact that I am in 4.0.4 whereas EOS 1.0.0 is in 4.0.3 and thus I am downgrading?
Thanks
adelancker said:
I still get that error message when installing EOS 1.0.0 (after wiping everything) even though I redownloaded the Rom. Is it because of the fact that I am in 4.0.4 whereas EOS 1.0.0 is in 4.0.3 and thus I am downgrading?
Thanks
Click to expand...
Click to collapse
I don't think it is because you are downgrading, if you did a data wipe, everything should of gone well. What error are you getting?
If you have everything that is important to you backed up from your xoom, I guess you could flash your xoom back to stock without locking the bootloader, and then flash the recovery of your choice. Finally, in that recovery, you can then flash EOS 1.0.0 and the gapps that go with it.
http://developer.motorola.com/products/software/ <- You can go there and download the stock images for the xoom. You would most likely have to sign up for a free account at MotoDev.
When the zip has been downloaded, extract the files. Assuming you have fastboot and adb set up correctly (in your command-line's path), you can follow the instructions on the MotoDev page for the xoom. THIS WILL ERASE EVERYTHING off of your xoom.
From there flash a fastboot-flashable recovery and then in that recovery, do a data wipe and flash that EOS rom! (and gapps too)
yosterwp said:
I don't think it is because you are downgrading, if you did a data wipe, everything should of gone well. What error are you getting?
If you have everything that is important to you backed up from your xoom, I guess you could flash your xoom back to stock without locking the bootloader, and then flash the recovery of your choice. Finally, in that recovery, you can then flash EOS 1.0.0 and the gapps that go with it.
http://developer.motorola.com/products/software/ <- You can go there and download the stock images for the xoom. You would most likely have to sign up for a free account at MotoDev.
When the zip has been downloaded, extract the files. Assuming you have fastboot and adb set up correctly (in your command-line's path), you can follow the instructions on the MotoDev page for the xoom. THIS WILL ERASE EVERYTHING off of your xoom.
From there flash a fastboot-flashable recovery and then in that recovery, do a data wipe and flash that EOS rom! (and gapps too)
Click to expand...
Click to collapse
Thanks lot for your help.
I keep getting this error (error 7 if I recall correctly) and right after the message "installation aborted"
When I follow your guide I'll lose my data right?
That sucks
Maybe I'd be better off waiting for a battery drain fix, however, holidays are coming soon, and I don't want this battery life on holiday lol
What ROM are you using, and do you suffer a lot of battery drain?
Thanks again O
adelancker said:
Thanks lot for your help.
I keep getting this error (error 7 if I recall correctly) and right after the message "installation aborted"
When I follow your guide I'll lose my data right?
That sucks
Maybe I'd be better off waiting for a battery drain fix, however, holidays are coming soon, and I don't want this battery life on holiday lol
What ROM are you using, and do you suffer a lot of battery drain?
Thanks again O
Click to expand...
Click to collapse
I just realized I posted twice because I just realized one of my posts made it on another page... [facepalm] My apologies
Well, I personally use the latest nightly from teameos. I am able to browse the web on chrome for the greater part of a day on good brightness and still have enough battery to last a bit more.
Have you tried wiping your batterystats? Do that at full charge. Also, if you use your tablet at night, you could try an app called rootdim. Its on the play store and it lets root user lower the brightness on a device to a level below what android lets you set. For me that's a good battery save.
Hope that helps
yosterwp said:
I just realized I posted twice because I just realized one of my posts made it on another page... [facepalm] My apologies
Well, I personally use the latest nightly from teameos. I am able to browse the web on chrome for the greater part of a day on good brightness and still have enough battery to last a bit more.
Have you tried wiping your batterystats? Do that at full charge. Also, if you use your tablet at night, you could try an app called rootdim. Its on the play store and it lets root user lower the brightness on a device to a level below what android lets you set. For me that's a good battery save.
Hope that helps
Click to expand...
Click to collapse
Maybe I should give that a go!
I just wiped my battery stats at full charge (just out of curiosity, why should this happen at full charge?)
I don't know what it does, but I trust you entirely! ;-)
Let's hope this works.
I use screen filter, but that app is starting to annoy the life out of me, so I'll give Rootdim a try!
Thanks,
And sorry for my English, it's only the fourth language here in Flanders
adelancker said:
Maybe I should give that a go!
I just wiped my battery stats at full charge (just out of curiosity, why should this happen at full charge?)
I don't know what it does, but I trust you entirely! ;-)
Let's hope this works.
I use screen filter, but that app is starting to annoy the life out of me, so I'll give Rootdim a try!
Thanks,
And sorry for my English, it's only the fourth language here in Flanders
Click to expand...
Click to collapse
Well, when I was reading on the internet, wiping the battery stats helped didn't necessarily help extend the life of the battery. Though online, some people said that when you switch between roms, the battery reading may be thrown off over time. So your tablet may be telling you that you have 20% battery left when you could actually have 25% battery left. As for the reason it should be done at full charge, it was actually part of a guide to calibrate the battery on android, which you could try. I am myself not clear on how the battery works. Your trust is appreciated, but dont take my word for it though...
And, whoa, your English is not bad!
yosterwp said:
Well, when I was reading on the internet, wiping the battery stats helped didn't necessarily help extend the life of the battery. Though online, some people said that when you switch between roms, the battery reading may be thrown off over time. So your tablet may be telling you that you have 20% battery left when you could actually have 25% battery left. As for the reason it should be done at full charge, it was actually part of a guide to calibrate the battery on android, which you could try. I am myself not clear on how the battery works. Your trust is appreciated, but dont take my word for it though...
And, whoa, your English is not bad!
Click to expand...
Click to collapse
Because of my stubbornness I managed to flashing EOS 1.0.0 !
First, I moved all of the flashable zips I needed ( Rom, gapss and a cool boot animation - of course! ) to the external SD .
Then, I wiped cache and flashed the Tiamat recovery and strangely - after wiping cache once again - it worked!
So I guess it was cause of the Rogue recovery for some reason!
I hope this fixes battery life. And since you said I should wipe battery stats when changing ROMs at full charge, I'll do that first thing when by battery light goes green!
Thanks so much!
I hope others who also want to revert can use this as their guideline!
And again, I'll
report about battery life
adelancker said:
Because of my stubbornness I managed to flashing EOS 1.0.0 !
First, I moved all of the flashable zips I needed ( Rom, gapss and a cool boot animation - of course! ) to the external SD .
Then, I wiped cache and flashed the Tiamat recovery and strangely - after wiping cache once again - it worked!
So I guess it was cause of the Rogue recovery for some reason!
I hope this fixes battery life. And since you said I should wipe battery stats when changing ROMs at full charge, I'll do that first thing when by battery light goes green!
Thanks so much!
I hope others who also want to revert can use this as their guideline!
And again, I'll
report about battery life
Click to expand...
Click to collapse
Wiping my battery stats improved my battery life a bit, I don't see why it wouldn't work for you!
And its been my pleasure helping you and I hope you do get better battery life
yosterwp said:
Wiping my battery stats improved my battery life a bit, I don't see why it wouldn't work for you!
And its been my pleasure helping you and I hope you do get better battery life
Click to expand...
Click to collapse
Okay, I wanted to wait just a little bit to report about the battery life, so that I wouldn't be influenced by the placebo effect
I have been using my Xoom just a bit and haven't connected him to a charger in 24h. Battery level: 75%!
Way better than I had with the later EOS.
I know that this isn't the same cutting edge rom, but this is so worth it!
adelancker said:
Okay, I wanted to wait just a little bit to report about the battery life, so that I wouldn't be influenced by the placebo effect
I have been using my Xoom just a bit and haven't connected him to a charger in 24h. Battery level: 75%!
Way better than I had with the later EOS.
I know that this isn't the same cutting edge rom, but this is so worth it!
Click to expand...
Click to collapse
Despite loving the new EOS roms, i cant help but say you are managing to get over 4x the battery i am getting!
I hope this really does become a guide for other people who were stuck in your case
I'm running stock jb and sadly its very laggy and many taps will result in many second of waiting. Even Google search takes ages to start.
Are the cyanogen Roms better? Is there already a working cm10 rom available?
Shahpur.Azizpour said:
I'm running stock jb and sadly its very laggy and many taps will result in many second of waiting. Even Google search takes ages to start.
Are the cyanogen Roms better? Is there already a working cm10 rom available?
Click to expand...
Click to collapse
I would give Jellybro a try. Seems to be fairly popular ROM based on CM10
http://forum.xda-developers.com/showthread.php?t=1791751
Make sure you make a nandroid backup and know how to flash beforehand.
i agree! jellybro is the sastest jb rom here !
I'm using paranoidandroid 1.9.5 its very smooth and fast but WiFi tethering is not working
Sent from my Nexus S using Tapatalk 2
Since you need to wipe the phone either way, have you tried a factory reset yet? It's worth a shot. You never said whether or not you did. But if you're looking for more features all baked in, go with a custom ROM
I think CM9 is still faster overall although it isn't buttery smooth like JB or CM10.
chronophase1 said:
Since you need to wipe the phone either way, have you tried a factory reset yet? It's worth a shot. You never said whether or not you did. But if you're looking for more features all baked in, go with a custom ROM
Click to expand...
Click to collapse
My boot loader is already unlocked so I shouldn't have to wipe for root, right? I'm just not sure if CM10 is worth it. Don't know if nexus s is capable of keeping it fast with Android 4.x...
You should try the jellybro rom because its super fast.
Sent from my Nexus S using xda premium
Try doing a full wipe/system reset. My Nexus S OTA to JB a few weeks ago. Even at stock, it was fast. No lag.
If you are experiencing lags, it is likely your phone's filled with resource contending stuff.
BTW, I've seen flashed in CMREX Beta9 JB. Boot up is insanely fast. Everything works.
Also you can try the V6 Supercharger mod. It helped my other phone - Gingerbread equipped XT615 Motoluxe speed up quite nicely.
Shahpur.Azizpour said:
My boot loader is already unlocked so I shouldn't have to wipe for root, right? I'm just not sure if CM10 is worth it. Don't know if nexus s is capable of keeping it fast with Android 4.x...
Click to expand...
Click to collapse
Mine runs very well on JB. You're already rooted and whatnot, all you need to do is backup via recovery. Properly wipe the phone and flash. There's a few 4.1 ROMs out there. Give them a shot and see what you like. The phone is still pretty quick despite its age. Like I said. The phone may just need to be cleaned up. I've never had mine lag, personally.
Should I wipe SD partition too? It takes ages to backup the SD partition to a PC first...doesn't seem to support USB 2.0...
I would try a factory reset first to see what happens...
Shahpur.Azizpour said:
Should I wipe SD partition too? It takes ages to backup the SD partition to a PC first...doesn't seem to support USB 2.0...
I would try a factory reset first to see what happens...
Click to expand...
Click to collapse
From my understanding just do a factory reset/wipe, wipe the dalvik cache and then flash your ROM.
Shahpur.Azizpour said:
I'm running stock jb and sadly its very laggy and many taps will result in many second of waiting. Even Google search takes ages to start.
Are the cyanogen Roms better? Is there already a working cm10 rom available?
Click to expand...
Click to collapse
First try change kernel..
Nocerino's Rulez with RAScarlo's ROM features TriNitY
I've had the same issue and came here to see if others shared. JB was initially pretty solid (I initially did a full wipe), but now it lags real bad. Google Now is the worst offender. It takes at least 5 seconds to appear, and then a good chunk of time to allow me to input text. It's too much.
I'm going to keep looking for another ROM, but honestly, I was counting on the fact that stock would be the most reliable. I've also had trouble using my radio to make calls / use data. I'm disappointed as I figured these problems were previously mostly due to custom ROMs. All I want is a stable, simple ROM that functions consistently.
Google Now was fast for me initially but it's super slow now but I doubt this is a ROM issue.
Everything else is fast and smooth.
Sent from my Nexus S using xda premium
I think its time to upgrade...just waiting for a nexus without pentile screen.
Do a full wipe, clear cache
This is the best time to check as many roms as possible. no need to worry about losing anything as you should of backed it all up by now. So clean slate and try some different Roms. To say stock is laggy does sound strange. So back up everything, even whats on your SD.
Clean start.
Best backup program to save apps and data - Titanium backup
Best app for everything else (app manager, processes etc..) - Romtoolbox.
Now go have fun!
try Xenonhd v6.0 and Air kernel JB weekly.
My phone is better than new with this combo. I am not going to try anything else until these give me a serious issue (I dont think they will)
i'm now on cm10, but the battery life is a bit disappointing
so i'm switching back to the stock rom now
is it just ok by pressing factory reset in the menu? or do i have to do anything else like flashing the stock rom again?
got no threads about this in the forum
justinyhc said:
i'm now on cm10, but the battery life is a bit disappointing
so i'm switching back to the stock rom now
is it just ok by pressing factory reset in the menu? or do i have to do anything else like flashing the stock rom again?
got no threads about this in the forum
Click to expand...
Click to collapse
First, sorry to hear CM10 isn't working out for you.
You will need to flash either a Sense based custom ROM or you can use an RUU to get back to stock.
A factory reset will only delete the contents of /data, dalvik cache and cache.
Sent from my One X using xda app-developers app
Just restore your nandroid. You made one right?
You understand it takes a couple of battery cycles after flashing a new ROM, before the battery meter is accurate? Give the ROM a couple of days, charging to full, then draining to 10-20% before you make judgements on battery life.
The easy way to go back to stock, if you want to stay rooted is to just flash one of the ROMs listed in my Index under "Stock Rooted": http://forum.xda-developers.com/showthread.php?t=1671237
You can just flash over cm10. I've switched ROMa quite a bit. I've been on cm10 but I switched to kingcobra1x because I missed sense too much. Still like the aokp look a lot
Sent from my HTC One XL using xda premium
If your looking for a great stock like ROM give Scotts CleanROM a try. Think you'll be very happy with it.
redpoint73 said:
You understand it takes a couple of battery cycles after flashing a new ROM, before the battery meter is accurate? Give the ROM a couple of days, charging to full, then draining to 10-20% before you make judgements on battery life.
The easy way to go back to stock, if you want to stay rooted is to just flash one of the ROMs listed in my Index under "Stock Rooted": http://forum.xda-developers.com/showthread.php?t=1671237
Click to expand...
Click to collapse
If my phone is from at&t should i use a specific one or any one can work?
I've flashed a few roms on my old phone - a moto droid x, and so far have not had any problems, and am currently toying with putting Liquid Smooth on my VZW GS3. I've read a lot of posts, old and new, and I could use some advice. Is there still a need to backup the imeid (?) before flashing a new rom? I am currently running the latest vzw firmware, am rooted and unlocked bootloader. Is this just a matter of flashing from CWM after wiping data/cache/dalvik? Ultimately, I'm fine with my phone the way it is, it works, but I'm a bit bored with it, and would love to be able to play with 4.2.2 instead of being stuck at 4.1.2 until vzw decides to update. At the same time though, I want to make sure to take any and all precautions so as to not hard brick it as I paid nearly full price for it so I could keep my unlimited. Thoughts? Suggestions?
Thanks
backing up imei is just a precaution you can do it or not thats really your choice. I would.
make sure you nandroid
clear data
clear cache
clear dalvik
flash rom
flash gapps
steps i run when flasing AOSP.
good luck.
ddurandSGS3 said:
backing up imei is just a precaution you can do it or not thats really your choice. I would.
make sure you nandroid
clear data
clear cache
clear dalvik
flash rom
flash gapps
steps i run when flasing AOSP.
good luck.
Click to expand...
Click to collapse
Thanks for the reply. Have you by chance used this rom? I'm looking for good battery life - prior to vzw's recent 2 updates, I was getting nearly 2 days on a full charge, but now am lucky to get 15 hours. If I do a nandroid, is there a need to backup the imei, or is that also backed up with the nandroid?
Thanks again
ddog511 said:
Thanks for the reply. Have you by chance used this rom? I'm looking for good battery life - prior to vzw's recent 2 updates, I was getting nearly 2 days on a full charge, but now am lucky to get 15 hours. If I do a nandroid, is there a need to backup the imei, or is that also backed up with the nandroid?
Thanks again
Click to expand...
Click to collapse
i got better battery on touchwiz roms.
beans rom is themed like AOSP and was great. a few otehrs have this theme but i have never tried them.
i liked the options in AOSP roms better so ive stuck with it.
i regularly get 4hrs screen on time. i got 7hrs screen on time with beans build once.
i also use ktoonz kernel everytime wth every rom.
i stick with AOSP for the customization and other options though. just personal preference. best bet is to try a bunch of roms and see what you need out of a rom with options.
i dont know if imei is backed up in nandroids. ive read that synergy rom backs up your imei when flashing but i dont know for sure.
Imei is not backed up in a nandroid.
You should definitely back it up. This phone has a potential to completely drop your imei on a custom rom even without flashing or modding anything, especially AOSP roms. It's very simple to do and saves you a huge headache if you do lose it.
Sent from my SCH-I535 using Tapatalk 2
I would like to recommend me a custom rom. I would prefer to be very smooth and a good performance. I don't care too much about themes. Until now, I've tried several Lola's old roms and they are good, but I think that is time to update my phone to a rom based on 4.2.2.
Also, I've two questions:
---Lola's roms are optimized for our devices or they are just ported ?
--- Do you recomend to use Ram Manager Pro or V6 SuperCharger by zeppelinrox? V6 SuperCharger, Kickass kernelizer and 3G TurboCharger are good for our phone?
Sorry for my bad english.
I would suggest CM10.1 A8 by master dhiru1602.
but first you need to backup your efs folder (thread here).
Lola's roms (based on CM10 or CM10.1 by dhiru1602) are ported to our device because we don't have Jelly bean stock roms.
well I don't use any of them... V6 SuperCharger seems to be more rated but Ram Manager Pro is easier to use
Notice: to enable "Performance" and "developer options" in CM10.1...7 hits on the Build number.
regards
Carbon rom by lola. Super smooth!
Sent from my GT-I9003 using xda app-developers app
Sorry for hijacking the thread. But I have some doubts about switching to a new rom. Currently my phone is facing these issues:
1) Wifi does not work for more than 10 feet, within the same room too. 50% strength at 2 feet distance from the router.
2) Battery backup is gone crazy low to about 9 hours on standby. Can't leave the phone unplugged for night, as by morning it is almost dead. (I guess it might be just my battery dying out).
3) Camera does not pick up any light at all. It is always too dark for any image.
I am currently using Cf-root by skin 1980 as the kernel, and the stock rom XXLE4. My common usage is playing games, occasional camera usage, internet using wifi/3g, and gps. Also, I am using go launcher themes, and stock rom's facebook sync to save contacts.
I am unsure if I should backup everything and reflash the phone with stock rom or go with a new one. CM10.1 looks good, but I am still unsure about specifically these two issues:
•Doesn't have wings
•Doesn't have 4 processor cores
How much will this affect my usage scenario? Based on my usage scenario, should I go for a new rom, or stock one?
Also, how can I best backup my synced contacts?
jitendragarg said:
Sorry for hijacking the thread. But I have some doubts about switching to a new rom. Currently my phone is facing these issues:
1) Wifi does not work for more than 10 feet, within the same room too. 50% strength at 2 feet distance from the router.
2) Battery backup is gone crazy low to about 9 hours on standby. Can't leave the phone unplugged for night, as by morning it is almost dead. (I guess it might be just my battery dying out).
3) Camera does not pick up any light at all. It is always too dark for any image.
I am currently using Cf-root by skin 1980 as the kernel, and the stock rom XXLE4. My common usage is playing games, occasional camera usage, internet using wifi/3g, and gps. Also, I am using go launcher themes, and stock rom's facebook sync to save contacts.
I am unsure if I should backup everything and reflash the phone with stock rom or go with a new one. CM10.1 looks good, but I am still unsure about specifically these two issues:
•Doesn't have wings
•Doesn't have 4 processor cores
How much will this affect my usage scenario? Based on my usage scenario, should I go for a new rom, or stock one?
Also, how can I best backup my synced contacts?
Click to expand...
Click to collapse
If you like stock roms, try DDMF1 and rooted using Bam kernel (PDA_BCK_CF-root_universal_beta14fix.tar)...you will get the best battery life
CM10.1 by dhiru1602 is awesome (and all the other JB roms especially Lola's roms) but GB is better for gaming and battery life
check this thread!
ASMI1 said:
If you like stock roms, try DDMF1 and rooted using Bam kernel (PDA_BCK_CF-root_universal_beta14fix.tar)...you will get the best battery life
CM10.1 by dhiru1602 is awesome (and all the other JB roms especially Lola's roms) but GB is better for gaming and battery life
check this thread!
Click to expand...
Click to collapse
Thanks for the response. Actually, I don't prefer stock at all, just the facebook sync thing. Saves me the hassle of saving the contacts. Also, I guess that low a battery life has something to do with dying battery, rather than rom. I think I should give custom JB rom a try, but before that was wondering if switching to cm10.1 will be worth it or not. If it does not bug out a lot, I will definitely prefer cm10.1. But as you mentioned, if it is slow at gaming, I would stay with stock for now.
BTW, is that wifi issue a normal thing? I get about 50% strength on stock rom, even if I keep my phone next to router,
Edit:
I checked that thread. Most of LoLation's post talk about how stable JB roms are now. While CM10.1 talks about not having all processor cores working. How much difference does that cause? Will it be extremely noticeable in the smaller games? I don't do games above 50mb anyway, so most of extreme games are out of question. heaviest game I play on my phone is temple run 2, and cut the rope. Will JB rom cause them to stutter too?
No, for normal games you won't notice any difference and some games work better on JB but i didn't get some heavy games to work on JB like NFS most wanted or dead trigger (i can run temple run Oz even on 600MHz frequency and conservative covernor).
If you go for JB roms, try to use greenify app...it will increase your battery life.
CM10.1 A8 is almost complete and it's really stable and smooth but has very small bugs.
Sent from my GT-I9003 using xda premium
A balanced rom?
Trust on
Like S4 v2.0.3 (odex) (4.2.2 A8) by Lola or
EHNDROIX™ II 13.2.9 (4.2.2 A8) by AlessandroXCV
Both are fast, stable & b e a u t i ful.
You will be smiling...
ASMI1 said:
No, for normal games you won't notice any difference and some games work better on JB but i didn't get some heavy games to work on JB like NFS most wanted or dead trigger (i can run temple run Oz even on 600MHz frequency and conservative covernor).
If you go for JB roms, try to use greenify app...it will increase your battery life.
CM10.1 A8 is almost complete and it's really stable and smooth but has very small bugs.
Sent from my GT-I9003 using xda premium
Click to expand...
Click to collapse
Sorry for delayed response. Was stuck with family issues.
I have some issues on Gingerbread stock, with temple run 2. If you say it can work with even 600MHz frequency, I will take your word on it. As for stability, small bugs are fine.
sam_777 said:
Trust on
Like S4 v2.0.3 (odex) (4.2.2 A8) by Lola or
EHNDROIX™ II 13.2.9 (4.2.2 A8) by AlessandroXCV
Both are fast, stable & b e a u t i ful.
You will be smiling...
Click to expand...
Click to collapse
I hope any one of them support facebook sync. Nothing makes me smile more than not having to manually backup my contacts.
Seriously though, I will keep looking for a contact backup tool in the forum. If I find one, will try EHNDROIX. S4 sux, so "Like S4" is not a good rom for me.
jitendragarg said:
Sorry for delayed response. Was stuck with family issues.
I have some issues on Gingerbread stock, with temple run 2. If you say it can work with even 600MHz frequency, I will take your word on it. As for stability, small bugs are fine.
Click to expand...
Click to collapse
Hey bro, I didn't play temple run 2, I said that I can run temple run Oz with 600MHz frequency on DDMF1 (I stick to DDMF1 because I get about %2 battery consumption in deep sleep even with a fat battery).
I you are looking for an app to backup/restore your contacts here is a good one.
Best regards
you can try proBAM ROM. it is quite stable then any other rom.
ASMI1 said:
Hey bro, I didn't play temple run 2, I said that I can run temple run Oz with 600MHz frequency on DDMF1 (I stick to DDMF1 because I get about %2 battery consumption in deep sleep even with a fat battery).
I you are looking for an app to backup/restore your contacts here is a good one.
Best regards
Click to expand...
Click to collapse
Thanks. That app sounds perfect for the job. Will check it out. :highfive:
As for game issue, I guess it might be specific with that game, but never mind, a game is not worth more than having better OS. :good:
Edit:
Tried installing the stock rom from scratch before flashing jb ones. As soon as I install cf-root, it simply says "Can't mount sdcard". Tried with a different cf-root and stock rom, same problem. Can't flash any jb roms because of it. Stock roms work well, even CWM scripts work fine. But, in recovery mode, it simply does not mount the internal sdcard.
jitendragarg said:
Thanks. That app sounds perfect for the job. Will check it out. :highfive:
As for game issue, I guess it might be specific with that game, but never mind, a game is not worth more than having better OS. :good:
Edit:
Tried installing the stock rom from scratch before flashing jb ones. As soon as I install cf-root, it simply says "Can't mount sdcard". Tried with a different cf-root and stock rom, same problem. Can't flash any jb roms because of it. Stock roms work well, even CWM scripts work fine. But, in recovery mode, it simply does not mount the internal sdcard.
Click to expand...
Click to collapse
Try to format your sdcard using cwm recovery.
BTW...hitting the "thanks" button is easier than write it
ASMI1 said:
Try to format your sdcard using cwm recovery.
BTW...hitting the "thanks" button is easier than write it
Click to expand...
Click to collapse
Ok, I will try that too.
And sorry, totally missed that button because of white background. :silly: Also, that super backup is awesome. Much better than titanium backup for me.
Edit: Nope. Same issue. "Can't mount sd card". Here is what I have done. Repartition and flash froyo (XXKPE). Flash DDLF2 (XXLE4). Flash the CF-root and then factory reset. Wiping dalvik cache works, but can't wipe battery stats. There is no message when selecting "wipe battery stats". IIRC, this happened last time too, and so I went back to stock rom. Also, as soon as I wipe dalvik cache, it stops booting and gets stuck at boot screen. Something is seriously wrong with this phone, I think.
Freez at boot screen
jitendragarg said:
Ok, I will try that too.
And sorry, totally missed that button because of white background. :silly: Also, that super backup is awesome. Much better than titanium backup for me.
Edit: Nope. Same issue. "Can't mount sd card". Here is what I have done. Repartition and flash froyo (XXKPE). Flash DDLF2 (XXLE4). Flash the CF-root and then factory reset. Wiping dalvik cache works, but can't wipe battery stats. There is no message when selecting "wipe battery stats". IIRC, this happened last time too, and so I went back to stock rom. Also, as soon as I wipe dalvik cache, it stops booting and gets stuck at boot screen. Something is seriously wrong with this phone, I think.
Click to expand...
Click to collapse
Try - wipe data/factory reset - from cwm menu. It worked for me when I was trying to flash DDLF2.
sam_777 said:
Try - wipe data/factory reset - from cwm menu. It worked for me when I was trying to flash DDLF2.
Click to expand...
Click to collapse
Tried. Same response. After flashing DDLF2, I did wipe cache, dalvik cache and data. Still hangs up. If I don't wipe cache, it boots but that same "unable to mount issue" exist.
Exact error in recovery mode after flashing the DDLF2. "Can't access to '/system/csc/KOR/system'". Any idea what this might be?
CSC Error
jitendragarg said:
Tried. Same response. After flashing DDLF2, I did wipe cache, dalvik cache and data. Still hangs up. If I don't wipe cache, it boots but that same "unable to mount issue" exist.
Exact error in recovery mode after flashing the DDLF2. "Can't access to '/system/csc/KOR/system'". Any idea what this might be?
Click to expand...
Click to collapse
No idea!. Try without sim and ext sd card. If does not work out try flash DDLF2 (if possible rooted) with odin again without sim & ext sd. Clean everything from cwm and reboot. Good luck.
sam_777 said:
No idea!. Try without sim and ext sd card. If does not work out try flash DDLF2 (if possible rooted) with odin again without sim & ext sd. Clean everything from cwm and reboot. Good luck.
Click to expand...
Click to collapse
Thanks a ton! Flashing without sim worked. Although, tbh, I did downloaded a different cf-root from that "big list of cf-root thread". But, it works wonders now.
Also, you were right. S4 might suck, but Like S4 is pretty smooth. Testing it out further, now. Once again, thanks a lot.
jitendragarg said:
Thanks a ton! Flashing without sim worked. Although, tbh, I did downloaded a different cf-root from that "big list of cf-root thread". But, it works wonders now.
Also, you were right. S4 might suck, but Like S4 is pretty smooth. Testing it out further, now. Once again, thanks a lot.
Click to expand...
Click to collapse
You are welcome. Probably smiling now.. Never mind. I found Like S4 is not stable after using 3 days, even if I change to Dhiru's kernel. Faced two sudden hot boot once after a call end and other while unlocking. Faced black screen whenever I tried to backup with Titanium. No problem at all with supper backup and other apps.
Anyway, we are here - happy to help each other.
sam_777 said:
You are welcome. Probably smiling now.. Never mind. I found Like S4 is not stable after using 3 days, even if I change to Dhiru's kernel. Faced two sudden hot boot once after a call end and other while unlocking. Faced black screen whenever I tried to backup with Titanium. No problem at all with supper backup and other apps.
Anyway, we are here - happy to help each other.
Click to expand...
Click to collapse
Ha ha! yep, definitely smiling now. Testing it out, for battery backup first. Hopefully, it will stable for me. Did a fresh install of everything, afterall, so I deserve some perks for that. noticed one weird issue though; even if I use go launcher, the default ui keeps running in background. hopefully this does not suck up all the battery. If not, I can now keep on trying all the roms.
Also, titanium is absurd in comparison to super backup; no contacts backup, and restore ask for permission for every app. Can't believe I was stuck on it for so long.
BTW, I have noticed the weird lack of fm, alarm clock, and facebook sync in all custom roms. Why do we hate these things? Atleast fm and alarm clock are a necessity of sorts.