Related
whats the fastest wildfire rom at the minute? sense or no sense doesnt really matter? like cyanogen or something, my phone is really slow at the minute which is really annoying me
wild puzzle, put an overclocked kernal on and use SetCPU to overclock, that might speed your phone up a bit.
Thats what i would do.
chrish2008 said:
wild puzzle, put an overclocked kernal on and use SetCPU to overclock, that might speed your phone up a bit.
Thats what i would do.
Click to expand...
Click to collapse
wth? cm7 by far...
Sent from my HTC Wildfire using XDA App
cm6 had bad graphics due to resolution on my WF is cm7 better res for WF?
Iv just tried cm7 and it lags, fcs and reboots like mad from a clean install
rosswaa said:
Iv just tried cm7 and it lags, fcs and reboots like mad from a clean install
Click to expand...
Click to collapse
It is probably a kernel issue. Try reusing HCDR.Kernel v4.1 from it's specific thread. Apart from that, you can try Openfire ROM as well, which is a completely vanilla AOSP build.
cold it be that rom manager didnt wipe properly? iv just manualy gone through and wiped everything and it hasnt crashed on me yet,
i thought the kernel would be flashed fresh from cm7?
rosswaa said:
cold it be that rom manager didnt wipe properly? iv just manualy gone through and wiped everything and it hasnt crashed on me yet,
i thought the kernel would be flashed fresh from cm7?
Click to expand...
Click to collapse
Yes, it is always recommended to wipe it manually through the Recovery Menu. You have to wipe data, cache, dalvik cache and /system for best results before installing a new ROM.
As for the kernel, yes, it is included by default in CM7, but it is v4.2. Using v4.2 has caused some stability issues for some members, and, in that case, it is recommended to revert back to kernel v4.1
yeh thanks for that info, was a kernel issue i hope, all been goin good so far
strange, cause the only difference between 4.1 and 4.2 is the wifi driver.
Sent from my HTC Wildfire using XDA App
Well since using the 4.1 keen every thing is working perfect, nice and fast no fcs or random reboots.
Well my mate said I have a desire hd and thank god I do, couldn't handle the wildfire lol
do not forget to enable jit
Sent from my HTC Wildfire using XDA App
Have done
Cm6 and Cm7 is a bit not very stable for me, have to reboot one or two times a day. Maybe I'll switch to other.
you are doing it wrong, cm7 is really stable. I m using nightly 19 for weeks without any problems.
Sent from my HTC Wildfire using XDA App
Don't think so, do a wipe data,system,darkvik cache, flash #53, boot in, first time ADW FC. reboot, flash 4.1 kernel, boot again, ADW FC again
I can reproduce it everytime, lol
I used CM the last two weeks..
Yesterday I went to the new CM7 Rc1 then i moved to Openfire..
it's very stable and fast, even without setCPU.. i've just backup all my apps and it is wonderful..
The last cyanogen seems to be quite slow sometimes..
Just rooted. Im new to the droid world, so im curious, can i get a low voltage kernel? A friend has Savage Zen and brags about battery life, but would it be compatible with my default-rooted rom? Also can i backup the kernel? Thanks.
Btw i tried googling but every time i got a good lead the links were dead
Sent from my HTC Evo 4G [rooted] Sprint 2.3.3(stock, came preinstalled) hardware v.4 bought new in July.
If you are referring to a rooted, stock HTC Sense ROM, no, do not use SavagedZen. It is only for AOSP ROMs.
AOSP - Android Open Source Project (vanilla, like on the Nexus)
Sense - HTC's UI
You cannot use a Sense kernel on an AOSP ROM, or an AOSP kernel on a Sense ROM.
(All Gingerbread)
AOSP Kernels:
Tiamat
SavagedZen
Cyanogenmod (kernel)
Godmode
PoonKang
I know that Tiamat and SavagedZen have HAVS and can be undervolted using Vipermod. Cyanogenmod, Godmode and Poonkang may come undervolted, but they do not have HAVS so you cannot adjust it.
Sense Kernels:
Freedom by Lithid
Golden Monkey by Netarchy
ChopSuey by barnacles10
Stock HTC
None of these kernels have HAVS (Freedom used to, but it was causing issues so he took it out). Golden Monkey, ChopSuey, and Freedom can come undervolted by certain degrees, it depends on which version of the kernel you download.
I can't think of any way to back up a kernel except for nandroiding system, but I am probably wrong. Just go into recovery, wipe cache and dalvik and flash a new kernel if you have any issues.
There is a good study guide in I think Q&A stickied, telling all that you need to know about kernels. I advise you to read it. Link: http://forum.xda-developers.com/showthread.php?t=894880
tropicalbrit said:
I can't think of any way to back up a kernel except for nandroiding system, but I am probably wrong. Just go into recovery, wipe cache and dalvik and flash a new kernel if you have any issues.
Click to expand...
Click to collapse
You can usually recover a bad kernel by flashing to back to the stock kernel and wiping cache and dalvik. Its usually worked for me, but depends on how much the custom kernel changed things.
To OP, go check out Kernel Manager in the market. It takes a good amount of the guesswork out of kernel flashing.
I say go with chopsuey 9.1 ill say its really good left my phone off charger for 8 hours while i slept was at 41% before and when i woke up it was still at 41% i mean does it get anybetter than that
Thanks for the help. Really in depth and helpful advice . Using freedom aggressive kernel now. Still testing to see if it helped. Great forums.
Sent from my HTC Evo 4G [rooted] Sprint 2.3.3(stock, came preinstalled) hardware v.4 bought new in July.
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
Hi,
Long time reader, 1st time contributor to these forums. Had some comments on this rom, but not yet allowed to post in Dev section yet so thought I would post here and hope it filters to dev and team.
1st, this is an excellent build and as always I want to thank the dev teams that work so hard on these. Ya'll are awesome
2nd, had issues with numerous SOD errors with this rom which mostly went away once, as suggested by someone else, I increased the Min CPU freq to 800 MHz. It seems to shorten the battery life some, but as it seems to help significantly, I can definitely live with this until this issue can be ironed out.
3rd, most of the remaining SOD issues I have had seem almost always to follow use of graphic intensive apps (e.g. games) or ones that attempt to show HD videos. I am unsure if this is related to the known graphic hardware acceleration issue, or to something as of yet unknown. I also wonder if this is the common experience or if this is specific to my hardware for some reason.
4th, these issues have persisted through out all the updates. I have already tried multiple wipes, repeated fresh downloads of the roms, and fresh re-installs of all apps (i.e. no Titanium restores of apps and/or data) with no change, better or worse, of these SOD issues.
Thanks for reading this post, and for your comments if any. I plan to add to this thread as I gain more experience with this rom.
Sincerely,
William
[Kindle Fire: Energy™ ICS CM9 Kang ROM Themed - Stock Kernel]
[HTC Evo 4G Supersonic: MikG 3.11 ROM - Chop Suey Custom Kernel]
[Retired: HTC CDMA Hero: Gingerbread Hero Deck ROM - Stock Kernel]
end.
I had some freeze issues. They were all solved by flashing intersectraven's kernel. I don't have link to kernel now, but I m sure a google search will bring it.
Sent from my HTC Incredible S using xda premium
Kernels
cenkoloji said:
I had some freeze issues. They were all solved by flashing intersectraven's kernel. I don't have link to kernel now, but I m sure a google search will bring it.
Sent from my HTC Incredible S using xda premium
Click to expand...
Click to collapse
Thanks for your reply The link you mentioned is http://forum.xda-developers.com/showthread.php?t=1382999
I had not flashed this because I heard that the Dev on this kernel was having RL issues and therefor not able to work on this kernel right now.
I have also been watching Hashcode's kernel http://forum.xda-developers.com/showthread.php?t=1545172 but looks like it is still not quite ready for widespread use.
Anyone else have experience with these kernels and would care to comment on one verses the other???
Thanks in advance for your time and interest
Sincerely,
William
[Kindle Fire: Energy™ ICS CM9 Kang ROM Themed - Stock Kernel]
[HTC Evo 4G Supersonic: MikG 3.11 ROM - Chop Suey Custom Kernel]
[Retired: HTC CDMA Hero: Gingerbread Hero Deck ROM - Stock Kernel]
end.
I tried to flash this rom, kept getting stuck in the boot animation. I let it set for about 10 minutes once, as someone suggested it might just take a while, but it still didn't boot. Had the same problem on the Reloaded Rom CM9. Finally I just installed the Hellfire CM7 Rom and was able to boot. So I'm sticking with this one for now. Someone suggested wiping after installing the CM9 rom and trying to reboot; I haven't tried this yet but will give it a go later.
I also had the SOD a lot while using this rom. But, I sold that Kindle Fire. So, I didn't really have time to troubleshoot.
The girl that bought it was not tech savvy in anyway. She was telling me the thing won't come on. I was like oh yeah, it does that sometimes. It's called the sleep of death. She didn't understand my technical terms there. So, I said, "It's zombie mode." It is un-dead. She understood that. Then, I told her how to fix it, and talked her through installing CM9.
The point of my awesome story is that SOD is now a feature called "Zombie Mode."
Just have her flash either hashcode's or intersectraven's (sluggish in my experience) kernel.
It's a pretty sweet ROM and the main issue (SODs) isn't the ROM's fault.
Now, if there was a way to switch between different wifi signals like in the stock one, without having to access the Settings menu...
I had numerous SODs while running the default clock frequencies. After changing to the following, I haven`t had a single one:
Sleep: 600 min / 600 max
Wake: 300 min / 1200 max
Sent from my Kindle Fire using XDA
Note that I`m using the default kernel provided in the Energy ROM package, and getting amazing battery life(11+ hours of reading)!
Sent from my Kindle Fire using XDA
Dasanko said:
Just have her flash either hashcode's or intersectraven's (sluggish in my experience) kernel.
It's a pretty sweet ROM and the main issue (SODs) isn't the ROM's fault.
Now, if there was a way to switch between different wifi signals like in the stock one, without having to access the Settings menu...
Click to expand...
Click to collapse
So you have tried Hashcode's kernel, has it been stable (relatively) with this ROM???
Anyone else with experience with this???
Thanks as always for your interest and responses
Sincerely,
William
[Kindle Fire: Energy™ ICS CM9 Kang ROM Themed - Stock Kernel]
[HTC Evo 4G Supersonic: MikG 3.11 ROM - Chop Suey Custom Kernel]
[Retired: HTC CDMA Hero: Gingerbread Hero Deck ROM - Stock Kernel]
end.
gedemis said:
I had numerous SODs while running the default clock frequencies. After changing to the following, I haven`t had a single one:
Sleep: 600 min / 600 max
Wake: 300 min / 1200 max
Sent from my Kindle Fire using XDA
Click to expand...
Click to collapse
gedemis said:
Note that I`m using the default kernel provided in the Energy ROM package, and getting amazing battery life(11+ hours of reading)!
Sent from my Kindle Fire using XDA
Click to expand...
Click to collapse
I have tried similar settings with virtual elimination of SOD's with the stock kernel with this ROM, but still occasionally getting some.
Though I had originally (see 1st post) said following graphic intensive apps, I realized last night that these apps are also sound intensive as well. Not sure if it might be a glitch in the sound driver as before the last update I was getting multiple FC's of the mixer.
Thanks as always for your comments/interest
Sincerely,
William
[Kindle Fire: Energy™ ICS CM9 Kang ROM Themed - Stock Kernel]
[HTC Evo 4G Supersonic: MikG 3.11 ROM - Chop Suey Custom Kernel]
[Retired: HTC CDMA Hero: Gingerbread Hero Deck ROM - Stock Kernel]
end.
Docs009 said:
So you have tried Hashcode's kernel, has it been stable (relatively) with this ROM???
Click to expand...
Click to collapse
The 2.6.* version, not the new 3.0 one - it was packed with Energy ROM up to 3-13, then it was switched to miui's kernel.
It's very stable and fast, in my experience. Intersectraven's kernel was stable, but performed poorly. Your mileage may vary...
Since getting my KF back in December I have tried numerous ROM's most of which refused to shut down for me without holding the button till my thumb went numb. Since I know nothing, I follow the loading instructions religiously although sometimes I do wipe twice, just to be sure. On some the wireless was a problem and most froze at one time or another and others would not access the market reliably.
After each trial I have returned to a ICS ROM which was released on Feb 09. Don't know what it's called anymore but it has worked flawlessly for me. It's not quite as fast and smooth as Energy or Reload, but it just works with decent battery life. There are not a lot of bells and whistles but what it does do, it does well. I will keep trying the latest ICS, just for kicks but until these great developers fix the video portion, the battery life portion and the freezing, I doubt I'll stay. I wish I knew who developed the one I am using. I'd like to thank him/her.
bbc0
bbc0 said:
Since getting my KF back in December I have tried numerous ROM's most of which refused to shut down for me without holding the button till my thumb went numb. Since I know nothing, I follow the loading instructions religiously although sometimes I do wipe twice, just to be sure. On some the wireless was a problem and most froze at one time or another and others would not access the market reliably.
After each trial I have returned to a ICS ROM which was released on Feb 09. Don't know what it's called anymore but it has worked flawlessly for me. It's not quite as fast and smooth as Energy or Reload, but it just works with decent battery life. There are not a lot of bells and whistles but what it does do, it does well. I will keep trying the latest ICS, just for kicks but until these great developers fix the video portion, the battery life portion and the freezing, I doubt I'll stay. I wish I knew who developed the one I am using. I'd like to thank him/her.
bbc0
Click to expand...
Click to collapse
I believe you are referring to the rom that now has the thread name "[ROM][24 Feb] IceCreamSandwhich Development/Discussion" originally posted by Bl1nk. Its dedicated to hash and jackpot clavins work. If you really want to thank them, go hit the donate button on there signature remember they work for free so do them a solid, even if its a dollar
Sent from my Kindle Fire using XDA
Thanks for the info.
Dasanko said:
The 2.6.* version, not the new 3.0 one - it was packed with Energy ROM up to 3-13, then it was switched to miui's kernel.
It's very stable and fast, in my experience. Intersectraven's kernel was stable, but performed poorly. Your mileage may vary...
Click to expand...
Click to collapse
Thanks for this information. For some reason I can't pull up Hashcode's web site, but I am at work with a very restrictive web blocking policy (In fact this site is blocked ) If I get a bit of non-family time at home this week I am going to see if I can find the previous version and try it out. I'll report back when I do.
Sincerely,
William
[Kindle Fire: Energy™ ICS CM9 Kang ROM Themed - Stock Kernel]
[HTC Evo 4G Supersonic: MikG 3.11 ROM - Chop Suey Custom Kernel]
[Retired: HTC CDMA Hero: Gingerbread Hero Deck ROM - Stock Kernel]
end.
Loving this rom on my KFire but there is a major SOD bug.
Sent from my Nexus S using XDA
Hey,
I'm having the same SOD problems with this ROM. It can happen at anytime really, getting email or browsing. The only ICS rom that doesn't do this for me is HellFire so I'm not sure what the diferences are between It and the others
DaLoGiE
End of Thread
I just realized that I had forgotten about this thread. Since I last posted here, I have had a lot of RL issues and I have since switched to gedeROM v1.1 {3.0 Kernel, CM9, Android 4.0.4} which includes Hashcode's Ver 3.0 Kernel. (http://forum.xda-developers.com/showthread.php?t=1619550) So far, I have NOT had anymore SOD's even with the standard CPU speeds set to standard. Also, HD video is working (yay!).
Thanks to all who replied to this thread. I would consider it closed.
Sincerely,
William
[Kindle Fire: gedeROM v1.1 {3.0 Kernel, CM9, Android 4.0.4} - Stock Kernel]
[HTC Evo 4G Supersonic: MikG 3.11 ROM - Chop Suey Custom Kernel]
[Retired: HTC CDMA Hero: Gingerbread Hero Deck ROM - Stock Kernel]
end.
Hi,
I was running Energy 3.19.2012 until now.
Tried to install Energy 4.29.2012 update (with Hashcode Kernel and new CM9) but I was stuck on boot animation (never got to the system itself).
Did a FULL Wipe (Factory reset > wipe cache > wipe dalvik > wipe system) before flashing. Got stuck on boot anim.
If anyone has the same issue : I had to reflash on top of already installed ROM (Full wipe > 1st install > factory reset > 2nd install > wipe cache + dalvik).
This solved my "stuck on bootanim" problem (which I never had before). Now with KF and HWA \o/
Just flashed the latest Energy ROM. Everything is AWESOME except for the fact that the Google Play Store force closes every time I try to open it. No more SOD or freezing, and it is extremely snappy.
Anyone know of a fix for the force closing of the google play store?
bengoblue said:
Just flashed the latest Energy ROM. Everything is AWESOME except for the fact that the Google Play Store force closes every time I try to open it. No more SOD or freezing, and it is extremely snappy.
Anyone know of a fix for the force closing of the google play store?
Click to expand...
Click to collapse
Never happened to me.
Did you wipe everything in TWRP before flashing the 4.29 version ?
"Forced Closed" market problems has been fixed since the 3.19. If you didn't wipe it may be the cause of market FC.
Or you could just try to go to apps > All > Google Play Store and delete cache here.