Related
Hi!
Im thinking about install a new rom to my phone but cant decide which...
I want a rom with so small bugs thats possible but still some features that makes the phone better
I installed this Clockwork Recovery for a pretty long time ago and dont remember what it do
http://forum.xda-developers.com/showthread.php?t=1044585
So I wounder if I need it or just can remove it?
And if I gonna install a new rom, which Recovery is the best at the moment?
Would be very thankfull if somone with more experience could tell me their opinion!
My prefer is void. (2.2.2; #eridanus) by Noejn.
Install Perfect Recovery 4.0.0.5 and try yourself all ROMS.
Sent from my u8800 using XDA App
Okey will try that rom and recovery
But if im not happy with the rom can I then change back to the orginal?
IF you take a backup with recovery yes,!
Sent from my u8800 using XDA App
At the moment definitely VOID 2.2.2 latest
What makes void so great? Dec got rid if his phone so no more updates. Might as well use something that'll get new fw updates..
I believe that Oxygen is the best Rom at the moment. Miui is very good as well, but with Oxygen battery life is amazing (more than 40h, with wifi and BT on all the time) and it's got most things sorted.
katu2006 said:
I believe that Oxygen is the best Rom at the moment. Miui is very good as well, but with Oxygen battery life is amazing (more than 40h, with wifi and BT on all the time) and it's got most things sorted.
Click to expand...
Click to collapse
actually Oxygen drains more battery than geno's CM7 beta....
magictwins said:
actually Oxygen drains more battery than geno's CM7 beta....
Click to expand...
Click to collapse
It maybe so, but at least camera is fully functional.
So, which ROM would you suggest overall? Fully fuctional, acceptable battery life, speed etc. I'm with B137 v8.2 and I feel I need something new.
FYI, I usually clock the cpu to 1Ghz or 1,2Ghz.
then go for the v8.4 & his new kernel
http://bbs.goapk.com/thread-3177723-1-1.html
http://bbs.goapk.com/thread-3423090-1-1.html
this is the most stable rom atm with good performance. other roms are faster but some things dont work or they are not stable.
your choice.
iakoboss7 said:
then go for the v8.4 & his new kernel
http://bbs.goapk.com/thread-3177723-1-1.html
http://bbs.goapk.com/thread-3423090-1-1.html
this is the most stable rom atm with good performance. other roms are faster but some things dont work or they are not stable.
your choice.
Click to expand...
Click to collapse
Thank you re iakoboss7!!!
Alexcxvtr said:
Thank you re iakoboss7!!!
Click to expand...
Click to collapse
how do you know that is. good Rom. did you tested it already? so is a room like void with Android 2. 2. 2
i use this rom for almost 2 months now. from v7 i think.
i never ever had a fc reboot etc (except 1 time i had the cpu at 1.5ghz).
everything is working fine, the only small problem lies in the modified franco kernel genokolar used (he modified it to be even more stable),
it has some problems on charging (franco's kernel had them also as i have read, i dont know if its fixed on his newest version cause the modified one is 1 version older than 20 july one).
(u can avoid that problem the kernel creates by not flashing the kernel and keeping v8.4 kernel).
here is a link that i have uploaded both 3
http://www.megaupload.com/?d=V99GYVBN
dont forget to install superuser from market or root will not work without it (as everywhere else also).
for the ones that want performance its not the best out there but its still a good one.
i get 24xx at quadrant at 1.3ghz when this void user gets the same at 1.5ghz but i get lower on antutu (3018, made a 2nd run and scored 3167 if it matters) propably cause of the 0.2gz less cpu speed http://forum.xda-developers.com/showpost.php?p=15978575&postcount=326
but this oxygen user gets allot more than me on 1.3ghz http://forum.xda-developers.com/showpost.php?p=16303582&postcount=391
(i have also 1.2gb worth of apps installed if this matters)
the good thing this rom has is stability and everything works, from what i read most other roms have things not working, bugs and not that great stability, miui is a VERY good rom also (has its small bugs) cause its based on 2.3.5 but i dont like miui style ^^ (personal opinion).
oh i forgot to mention that its totally stock (except 1 small app with reboot,shutdown etc options).
i made some changes please re-read my answer
iakoboss7 said:
the good thing this rom has is stability and everything works, from what i read most other roms have things not working, bugs and not that great stability, miui is a VERY good rom also (has its small bugs) cause its based on 2.3.5 but i dont like miui style ^^ (personal opinion).
oh i forgot to mention that its totally stock (except 1 small app with reboot,shutdown etc options).
i made some changes please re-read my answer
Click to expand...
Click to collapse
bro, thanks for ur info.
btw, my ideos is u8800H, is it compatible also? and i had flash with muui1.7.3 (android2.3), is it can flash back? ( use recovery tools to flash?)
thanks for help.
yeah its for the u8800H also as i can remember. you can keep a backup and if you dont like you can go back anytime...
oh and flash works just fine, i dont see any reason not working.
there is a new miui version that came out before an hour, try it first cause you maybe like it better (since i see you already have miui).
iakoboss7 said:
i use this rom for almost 2 months now. from v7 i think.
i never ever had a fc reboot etc (except 1 time i had the cpu at 1.5ghz).
.
.
the good thing this rom has is stability and everything works, from what i read most other roms have things not working, bugs and not that great stability, miui is a VERY good rom also (has its small bugs) cause its based on 2.3.5 but i dont like miui style ^^ (personal opinion).
oh i forgot to mention that its totally stock (except 1 small app with reboot,shutdown etc options).
i made some changes please re-read my answer
Click to expand...
Click to collapse
Thank you very much. I have flashed your uploaded three files and would like to confirm that this v8.4 is the best ROM for u8800 nowadays. BTW, since the original ROM is from China, I do hope to have your help to keep update this ROM whenever there is a new version or any changes.
no problem, i can keep you updated, at least until Genokolar decides to put his work here.
tried the v8.4 from Genokolar on my UK Huawei U8800 and it didn't work kept looping at the start screen, so I went back to using the FLB Custom ROM
Hello all,
i have been an owner of a nexus s gsm s-lcd since August 2011 and i have been experimenting mostly with cyanogenmod and cyanogenmod based roms such as nscollab.
Using my phone mainly for my jobs, since the beginning of the usage of non official roms, i am always having stability problems ending up not trusting my phone for everyday use.
I have tried cyanogenmod stable, rc, lots of nightly builds and various nscollab versions from 1.0.39.
From my experience so far, except when using matr1x 5.5 cfs i always have some of the following problems, some times some of them and sometimes all of them:
1. reboots
2. reboots with no ability to load the os, with only solution the removal of battery
3. crashes with the result of the pin needed to be given again
4. never waking up after deep sleep
The kernels i have used so far are all the matr1x cfs(sorry, i do not trust con Kolivas and his bfs, being a linux user for 10 years), various netarchy and the stock cyanogenmod .
The only kernel that has been stable for me until now is matr1x 5.5 cfs.
The reason for not going back to the official rom, and be ok with my mobile is mainly the bln and voodoo(although i have bought the paid app and i can use the module with the official rom) modules.
The first thing I though having all these problems is that the main cause of them would be the undervolting that all most of the kernels have. After some tests i realized that with the voltages that proton suggests or even with the stock voltages, the problems do not disappear.
Although, i have found my stable kernel and i always flash matr1x 5.5 cfs in all the roms i use, i would really like to know what is the usual suspect of all these problems. Is there any possibility that some of them are not kernel related and the cause is in the source code of cyanogenmod?
To sum up, i really believe that we should try an effort to create a kernel that is very close to the stock one, and be very careful with the extra modules that we add. Although i do not have the experience of making a kernel package for android, i will try for sure to make a flashable kernel for my needs, and if it's stable i will upload it and share with all of you.
I believe that every mobile has to be bug-free(as possible), and reliable for everyday use and at least i should be reboot-free.
I would really like to read other users experience and opinions.
Regards,
Michael
it was the same for me. nscollab was unusable since it was always freezing in two minutes after boot. changing the kernel did not help. so I decided to change the rom to Nexus MV 10.05. it works very stable (not a single reboot or freeze) and faster than nscollab.
mikkkg said:
The reason for not going back to the official rom, and be ok with my mobile is mainly the bln and voodoo(although i have bought the paid app and i can use the module with the official rom) modules.
Click to expand...
Click to collapse
Well, I found that custom kernels can work with stock ROM's. I'm using stock Google 2.3.6 on my 9023 + pete's kernel with Voodoo sound and BLN. Stable as ****, practically no issues, I'm happy with my NS as never before just because of the lack of constant flashing the **** around to "optimize". It just works flawlessly.
Here's the link to the kernel : http://www.peteralfonso.com/2011/08/download-nexus-s-263514-kernel.html
Had the no wake issue with cm7 216 and nscol 1.4.5. On nscol 1.4.6 and no problems yet. If it happens again it would seem to be a cm7 issue. While annoying devs are constantly hunting down and correcting problems, just the way it is and doesn't bother me.
Sent from my Nexus S using xda premium
Jeez loueeeeze
Just use nscollab .46 because that has stock voltages and you should be fine
Sent from my Nexus S using XDA App
The hole point for me is not using any other kernel but the stock one.. compile yourself a nexus s kernel (google it for how to) and be happy without any reboot, crash..
baterry? normally 1.5 days @ 1.0ghz..
You could do that as well
Sent from my HTC Sensation 4G using XDA App
mathkid95 said:
Jeez loueeeeze
Just use nscollab .46 because that has stock voltages and you should be fine
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
.45 with stock voltages caused the "pin asking" issue even with stock voltages(even with 5.5 cfs - maybe a cyanogen problem?), so that's why i am stuck at .42 with 5.5 cfs and did not even try .46.
Try .46 and lemme know
Sent from my HTC Sensation 4G using XDA App
mathkid95 said:
Try .46 and lemme know
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse
If you see, in the thread of nscollab, there are also problems with the phone dying etc, even with the new stable cyanogenmod + matr1x kernel.
I only do tests in my mobile during the weekend, because i use it all week for my job. So stuck with matr1x 5.5 until i see a really stable matr1x kernel coming after 8.
madd0g said:
Here's the link to the kernel :
Click to expand...
Click to collapse
Thank you very much for posting this link. I did not know that kernel. I just found some time to flash nscollab .50 with this kernel and i only changed interactive governor with ondemand to be even closer to stock kernel.
I hope that it is as stable as it is for you.
After some hours with this new kernel, i am not sure about stability(although it seems stable) but nexus is running smoothier than ever.
I've used ondemand from the beginning I started using this kernel, then I tried interactive (default) just to try it out. Not really a difference, same stability/speed and I could get rid of NoFrillsCPU app setting the default governor at startup. So to wrap up, kernel runs beautiful from the start, no extra fiddling necessary.
I do not believe the issues described in the OP are kernel related. They persist in all custom kernels. I think it is from Dalvik VM crash but I have no proof.
Sent from my Nexus S using XDA App
http://forum.xda-developers.com/showthread.php?t=959282&page=309
As I read here I am not alone in the problems described, and after lots and lots of tests i am sure that this is a matr1x specific issue.
So, as i do not have permission to write in a development thread yet, I suggest the following:
1. if the developer of nscollab wants to continue with Matr1x kernels, makes a new release with the last well known stable kernel, which is Matr1x 5.5 until Matr1x developer finds out what is the problem with the new kernels.
2. Matr1x is replaced with another kernel, such as Peter Alfonso's kernel(running FINE for 24 hours. In the same period with Matr1x kernels i would have at least 2-3 problems- 5.5 cfs excluded).
EDIT:
I just got the first "dead phone" issue with alfonso kernel. I should be more patient about stability results of this kernel, or this issue is not kernel related.
After many days of testing with nscollab and different kernels, i am sure that the major problem of "dead phone" is not kernel related but a cyanogenmod issue.
The most stable kernel i tried was Peter Alfonso, but after 4 days of use the issue appeared.
As i need a really stable rom, before going back to stock, i am testing Oxygen 2.3.1, which i do not know yet if it's stable(i hope) but until now is the fastest and smoothest experience.
Id say if you want stability, stay on stock, extra features like BLN and Voodoo sound are added via kernel anyway.
Sent from my Nexus S using Tapatalk
mikkkg said:
After many days of testing with nscollab and different kernels, i am sure that the major problem of "dead phone" is not kernel related but a cyanogenmod issue.
The most stable kernel i tried was Peter Alfonso, but after 4 days of use the issue appeared.
As i need a really stable rom, before going back to stock, i am testing Oxygen 2.3.1, which i do not know yet if it's stable(i hope) but until now is the fastest and smoothest experience.
Click to expand...
Click to collapse
Kalimocho found a kernel error and a missing vendor file in the CM kernel. It will be fixed in the next nightly. The hope is that this was the cause of the freezes/reboots/bootloops/dimscreen bootloops that people were seeing.
mikkkg said:
Hello all,
i have been an owner of a nexus s gsm s-lcd since August 2011 and i have been experimenting mostly with cyanogenmod and cyanogenmod based roms such as nscollab.
Using my phone mainly for my jobs, since the beginning of the usage of non official roms, i am always having stability problems ending up not trusting my phone for everyday use.
I have tried cyanogenmod stable, rc, lots of nightly builds and various nscollab versions from 1.0.39.
From my experience so far, except when using matr1x 5.5 cfs i always have some of the following problems, some times some of them and sometimes all of them:
1. reboots
2. reboots with no ability to load the os, with only solution the removal of battery
3. crashes with the result of the pin needed to be given again
4. never waking up after deep sleep
The kernels i have used so far are all the matr1x cfs(sorry, i do not trust con Kolivas and his bfs, being a linux user for 10 years), various netarchy and the stock cyanogenmod .
The only kernel that has been stable for me until now is matr1x 5.5 cfs.
The reason for not going back to the official rom, and be ok with my mobile is mainly the bln and voodoo(although i have bought the paid app and i can use the module with the official rom) modules.
The first thing I though having all these problems is that the main cause of them would be the undervolting that all most of the kernels have. After some tests i realized that with the voltages that proton suggests or even with the stock voltages, the problems do not disappear.
Although, i have found my stable kernel and i always flash matr1x 5.5 cfs in all the roms i use, i would really like to know what is the usual suspect of all these problems. Is there any possibility that some of them are not kernel related and the cause is in the source code of cyanogenmod?
To sum up, i really believe that we should try an effort to create a kernel that is very close to the stock one, and be very careful with the extra modules that we add. Although i do not have the experience of making a kernel package for android, i will try for sure to make a flashable kernel for my needs, and if it's stable i will upload it and share with all of you.
I believe that every mobile has to be bug-free(as possible), and reliable for everyday use and at least i should be reboot-free.
I would really like to read other users experience and opinions.
Regards,
Michael
Click to expand...
Click to collapse
I use this, if it helps you.
Thread here.
mikkkg said:
http://forum.xda-developers.com/showthread.php?t=959282&page=309
As I read here I am not alone in the problems described, and after lots and lots of tests i am sure that this is a matr1x specific issue.
So, as i do not have permission to write in a development thread yet, I suggest the following:
1. if the developer of nscollab wants to continue with Matr1x kernels, makes a new release with the last well known stable kernel, which is Matr1x 5.5 until Matr1x developer finds out what is the problem with the new kernels.
2. Matr1x is replaced with another kernel, such as Peter Alfonso's kernel(running FINE for 24 hours. In the same period with Matr1x kernels i would have at least 2-3 problems- 5.5 cfs excluded).
EDIT:
I just got the first "dead phone" issue with alfonso kernel. I should be more patient about stability results of this kernel, or this issue is not kernel related.
Click to expand...
Click to collapse
lol i keep looking but i dont find anything
ahhhh
My primary concern is with battery life and 4G. Thanks.
kush deck's 1.3 aosp rom
tiamat sbc kernel
underclock cpu 768/384 with
smartassV2 governor
go launcher ex
youll have excellent battery life plus 4G if its in ur area. launcher u can customize.
also perhaps u can update radio/nv to newest.
Sent from my PC36100 using XDA App
Yup!!!
Decks tiamat 3.3.7 aka. Lee kernel, COD tweaks.
Sent from my PC36100 using xda premium
Stock ROM with bloatware removed with stock kernel
Sent from my PC36100 using XDA App
MIKG 3.0 Kernel that comes with it. I have had no issues with this ROM and you can add themes to it. It has Wimax working and have had no major issues with it. I go all day (work day) without a charge.
gonna agree with decks 1.3d
honestly i have been trying to figure out if the newer tiamat 4.1.0 and 3.3.7.
i like the smartass v2 4.1.0 seems to be ramp up a bit quicker and isnt a bad thing. 3.3.7 may have a little more battery life to it and i'll admit any lag may be just me lol
sidenote: the older tiamat doesnt have smartass v2 and i dont know the differences if any just saying im going off personal experienced
using stock launcher atm this time i've used adw and the newer kernel seemed to stay snappier if that makes sense. havent tried launcher pro plus yet but im sure that will be about the same since hell adw has been updated more than lpp.
i forgot to add to have a "partioned" sd card with at least 1024 in ext partition, then also to convert that from ext2 to ext3 (u can do all that in amon ra recovery) .
after rom settles flash dark tremors a2sd zip from recovery, go to market n get a2sdgui. inside this app choose to move dalvik cache to ext partition. also u can select to zip align on boot.
ps. this goes with my previous post above.
Sent from my PC36100 using XDA App
Thanks guys. I will try Deck's ROM and the suggested kernel.
I used to have 3 hrs (give or take) of battery life on stock HTC Sense. After switching to MIUI w/ a Tiamat kernel undervolted by -50V via viperMOD, my battery lasted for days at a time.
According to Green_Arrow's guide to the best GB and ICS ROMs, MIUI is described as having "the longest battery life" and is hailed as "very customizable." Green_Arrow goes on to say that "this rom is based off of CM7 and is an excelent rom."
I'd recommend MIUI to anyone looking for a fast, stable, energy-saving Gingerbread ROM as long as they stay away from the latest 1.12.23+ versions. A lot of people are reporting a lot of issues that shouldn't be issues on those builds; Most people would recommend MIUI 1.12.9. Happy flashing!
no 4G in miui...
it is very cool how u can customize the looks of it though!!
to OP: one last thing is to flash the "updated gps fix" zip file which is somewhere in these forums. will give u near instant lock.
pm me for any questions u have or if u need help!
Sent from my PC36100 using XDA App
For ICS users only
I was just curious, since many users (including me), never got SOD on the phone, not even once..
And being a heavy user, I tried many GB and ICS builds (But I use Criskelo's stuff most of the time...)and so far no SOD..
Just give your vote, for the statistics (or curiosity? )
Thanks
.
When using the Rocket Rom, 1.5, I only ever got one and that was when sync was on and wifi was doing it's little glitch-out thing. Other than that, have never had one on 1.5.
It happened often when i flashed via Mobile ODIN. Re-flashing via full PC ODIN and then installing iMilka's AOSP has given me no problems.
I don't have any hard evidence that mobile odin is to blame, but flashing with full PC odin make a big difference for a friend and I.
Lots of SODs when running Chinese Repack, just a couple since switching to imilka's AOSP.
Repack flashed via Mobile Odin.
chasmodo said:
Lots of SODs when running Chinese Repack, just a couple since switching to imilka's AOSP.
Click to expand...
Click to collapse
Didnt try imilka's , started up (and staying) with Criskelo's and then tried a couple of other builds just to compare ...
Never got SOD on any of the other builds including ,when running CF repack with gapps 7.1
And always flashing with Mobile Odin with the necessary full wipes
.
I have not had a single SOD. Was on ROMOW ICS until imilka AOSP, have used imilka V1-V4 and been on V4 since release day with 0 SOD's. Mobile Odin CF Repack to imilka.
Have had several on Midnote.....matter of fact just had one 2 minutes ago...lol Otherwise this rom is perfect!
I just had one on the latest stock build of GB from India. I haven't rooted my phone or anything. Interesting. I will keep my eye on this thread. Thanks!
Feel free to mock me .... but what do you mean when you say SOD (screen of death)? Total system crash?
For some reason I get about 3 a day. I'm pretty sure its app installed. Once I raised the minimum CPU to 500 it got a lot better. When I get a chance I'll reinstall everything.
All in all I'm pretty sure its user error and not the rom. I'm using asop rom v4.
Sent from my GT-N7000 using xda premium
Yep same question here. (what do you mean by SOD?)
Many times I have the black screen when launching some app that sometimes work and sometimes don't (when I reboot the app is not accessible anymore).
I have an issue, it seems access to the external SD is not functioning well. Since I moved to ICS, I can't tell if it's Rom related or if its the SD that's faulty (it seems all OK when plugged to the computer).
I might have also to reboot when wifi toggled back on is not working well.
I'm using criskeloRom +15 toggles (but had more or less the same behavior with all the rom I used, Midnote or RocketRom).
Never on Criskelo's 1.5 ROM....in fact it is now 3 days without a reboot...I have had a couple of crashes without need for reboot, but its when Touchdown updates the stock contact list, which even happened on gingerbread...
Are you guys sure this is ROM related and not some other software?
I had SOD on GB
been using Team Rocket 1.5 since the first release, I totally had 4 times of SOD, not that much really.
i been using midnote repacked by me for atleast 6 days now NO SOD.
i give u guys a secret.
download midnote.dont download gapps from that thread.
download gapps from hptouchpad cm9 thread.its called gapps v11
youtube is tablet version.
@betoNL
Actually, it's not screen of death. It's sleep of death.
Using Chinese repacked ICS, flashed using Mobile Odin, got 4 SOD, once per day, going back to GB.
chasmodo said:
@betoNL
Actually, it's not screen of death. It's sleep of death.
Click to expand...
Click to collapse
Yep...just the other day I corrected somebody that wrote screen of death instead of sleep...
And I now I made the same mistake
Thanks for the observation though...
Just corrected it.
.
I am on criskelo v1 b3 with kernel Angelom, modem lb1, setcpu, but i have SOD yet
I love ICS and Chrome and i don't want return to GB
intruda119 said:
For some reason I get about 3 a day. I'm pretty sure its app installed. Once I raised the minimum CPU to 500 it got a lot better. When I get a chance I'll reinstall everything.
All in all I'm pretty sure its user error and not the rom. I'm using asop rom v4.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Yes, let's continue blaming the user despite how some have gotten SOD on a fresh flash on a stock Chinese ROM with no apps installed.
Hello,
Using CM7.1 jordan stable on my MB525 Red Lens. Everything is working perfectly, but i have some pretty nasty battery uptimes. I charged the phone to 100% last night, the moment i unplug it i already have 99%, and after 8 hours spent with the phone unplugged while i was sleeping overnight, it went down to 46%. Any ideas as to why this happens and what i can do to tame it?
Thanks.
This is nasty.did you calibrated the battery after you installed cm7?
I too have red lens and running 1403 quarx defy + build with Walter 4.5.3-109 kernel which gives best battery life. The same kernel is used in ms2 ginger 3.0 which is known to have best battery.
Sent from my MB526 using XDA App
Running kernel 2.6.32.9-gb08c3c8, EPU93 baseband. I have not calibrated, but after reading around on the forums it looks like it's not much use. Or is it? I installed the calibrator, i will let the phone power down completely and then will charge up to 100% and recalibrate. Any other advice that might be useful?
Thanks.
Since your defy is red lens I would suggest you to flash defy + builds. You can use latest quarx 0316 cm72 defy + build and flash walter79 4.5.3.109 kennel.that would give awesome battery life and at the same time you are on beauty of cm7.
For quarx builds, get it from http://quarx2k.ru/cm7-nightly-defy+/
For kernel just see the ms2 ginger thread, there you would find 4.5.3.109 and zip file which can be flashed by cwm.
Btw, earlier releases had problem in booting with that kernel which quarx fixed on 0316. If you flash earlier cm72 releases, then flash 4.5.2.109dht22 kernel, which you can find in the same ms2ginger thread.
Sent from my MB526 using XDA App
Can i flash the Kernel you suggested on my current CM7 without flashing CM7.2 for Defy+? If i can, what will the effects be? Will it mean any changes in my settings, applications or any other thing, or will it just improve certain computing aspects?
Luppertazzi said:
Can i flash the Kernel you suggested on my current CM7 without flashing CM7.2 for Defy+? If i can, what will the effects be? Will it mean any changes in my settings, applications or any other thing, or will it just improve certain computing aspects?
Click to expand...
Click to collapse
No don't flash that kernel which leads to boot loop on cm7 stable which uses froyo kernel. I assume you have froyo kernel now correct.
Kernel won't change any computing aspects nor will change any settings, you don't find any noticeable difference as far as the system goes.
Sent from my MB526 using XDA App
Correct. 2.2.2 CEE as base. Any other kernel you might recommend for this base and CM7.1 stable? Or any other battery calibration suggestions, way to make it last longer?
Well on froyo I don't have one to recommend. GB builds give better battery life and we have alternatives.
I was with cm7 fire quite some time but didn't like battery life. Then I moved to ms2ginger, battery life was awesome but then it's stock, missing cm7.
Now finally I have mix of cm72 with ms2ginger kernel, loving it.
If you have nandroid backup of original stock froyo and gives better battery life then try restoring it's 'boot' through cwm recovery, please nandroid backup the existing 'boot' before you do this, just in case if you stuck in boot loop, you can restore it back.
Sent from my MB526 using XDA App
premaca said:
No don't flash that kernel which leads to boot loop on cm7 stable which uses froyo kernel. I assume you have froyo kernel now correct.
Kernel won't change any computing aspects nor will change any settings, you don't find any noticeable difference as far as the system goes.
Sent from my MB526 using XDA App
Click to expand...
Click to collapse
I was using the MS2Ginger 3.0 based rom by walter79 and I got wifi issues with my office wifi not working.. I then flashed to cm7.1 and though battery life is not that good, wifi works smoothly...
I will try the cm7.2 with ms2ginger and see if I get wifi issues with that as well.