Related
Okay let first start off by saying I have commitment issues. Lol. I rooted my Epic yesterday, i"m pretty sure it is a permanent root. After rooting I did a full wipe of data/factory and cache.
Now I didn't know which rom to install. Bakedsnack or epicexperience. My preferences are better battery life and best looking launchers/themes after first boot without installing any other kernels since I'm a noob. So idk which Rom fits my preferences more (some help with please?)
However, I installed bakedsnack, used it for a few mins and went back to recovery to install epicexperince (I did not wipe data/factory again). After I installed it I rebooted the phone but all i get is a blank screen after the sprint 4g logo. I could hear some notifications like when I connect my charger it makes that sound. SO the phone is on but screen is blank/black. I did get a bit tense so I went back to recovery and again I didn't wipe anything but I just reinstalled Bakedsnack.
Now for the commitment issues, I was using bakedsnack without a default launcher for 3 hours. Didn't know which one to choose (touchwiz, awd or launcherpro). After 3 struggling hours i ended up with launcher pro(and now I found out about the app called home switcher -_-).
So idk if its a problem for me installing a rom 3 times. Did my epicexperience get automatically uninstalled? or is it still in the system?
Another question, when I go to settings>about phone, for my firmware version it says Baked-snack-1.2, and the kernel version says 2.6.29. Is the kernel supposed to say that or is it supposed to show that a custom kernel is installed?
(i think bakedsnack has a custom kernel).
Now can anyone pleaseeee help me about choosing a rom. Hopefully epicexperience will work if I do a clean wipe which I didn't try yet. But i'm open to any advices, suggestions. Can anyone with experience tell me which rom is all around better for battery life, looks.themes/launchers/widgets, performance?
One last question (sorryyy!!!), I leave juicedefender running 24/7 so my data/3g could be disabled whenever the phone is idle. Logically, I think this saves battery, but i've read here and there that literally bakedsnack rom saves more battery without juicedefender running. Is this true? if yes, then how?
I am sorry for such a huge post but I am confused lol.. Thank you very much for bearing with me. I appreciate it a lot and will appreciate any help. Once again Thanks.
Wrong section, but ill take a stab at these.
When your asking the question about performance and battery life between backedsnack and epicexperience. You really can't compare. The battery/performance driving engine aka kernal is not included in epic experience. You find and flash your own. However the EE (epic experience) rom has quite a few tweaks to it. Including the new reboot from system menu. Backedsnack I can't say forsure about it. I ran 1.3 but seemed buggy to me. And switched back to epic. And for you battery question. Overclocked kerrnals save battery ushually by undervolting the cpu and setting the govener to save you battery. Therefore any program that would run in your backround 24/7 is just going to eat battery. Even if it says it saves battery, it still has to run to do so. And that's just my 2 cents. Next time please post in a different section
Sent from my SPH-D700 using XDA App
skelit0r said:
Wrong section, but ill take a stab at these.
When your asking the question about performance and battery life between backedsnack and epicexperience. You really can't compare. The battery/performance driving engine aka kernal is not included in epic experience. You find and flash your own. However the EE (epic experience) rom has quite a few tweaks to it. Including the new reboot from system menu. Backedsnack I can't say forsure about it. I ran 1.3 but seemed buggy to me. And switched back to epic. And for you battery question. Overclocked kerrnals save battery ushually by undervolting the cpu and setting the govener to save you battery. Therefore any program that would run in your backround 24/7 is just going to eat battery. Even if it says it saves battery, it still has to run to do so. And that's just my 2 cents. Next time please post in a different section
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
ahh sorry for posting here.. just very new to these.. i think bakedsnack already has the cpu undervolted, but how can I do it and set the govener manually just to be sure?
thx a lot for your reply.. increasing my knowledge base.. can you please be a bit more specific to how epicexperience has more tweaks to it? and does it look better than bakedsnack? i'm loving the bakedsnack notification pull down window..
Thread moved to General.
y2bangali said:
Okay let first start off by saying I have commitment issues. Lol. I rooted my Epic yesterday, i"m pretty sure it is a permanent root. After rooting I did a full wipe of data/factory and cache.
Now I didn't know which rom to install. Bakedsnack or epicexperience. My preferences are better battery life and best looking launchers/themes after first boot without installing any other kernels since I'm a noob. So idk which Rom fits my preferences more (some help with please?)
However, I installed bakedsnack, used it for a few mins and went back to recovery to install epicexperince (I did not wipe data/factory again). After I installed it I rebooted the phone but all i get is a blank screen after the sprint 4g logo. I could hear some notifications like when I connect my charger it makes that sound. SO the phone is on but screen is blank/black. I did get a bit tense so I went back to recovery and again I didn't wipe anything but I just reinstalled Bakedsnack.
Now for the commitment issues, I was using bakedsnack without a default launcher for 3 hours. Didn't know which one to choose (touchwiz, awd or launcherpro). After 3 struggling hours i ended up with launcher pro(and now I found out about the app called home switcher -_-).
So idk if its a problem for me installing a rom 3 times. Did my epicexperience get automatically uninstalled? or is it still in the system?
Another question, when I go to settings>about phone, for my firmware version it says Baked-snack-1.2, and the kernel version says 2.6.29. Is the kernel supposed to say that or is it supposed to show that a custom kernel is installed?
(i think bakedsnack has a custom kernel).
Now can anyone pleaseeee help me about choosing a rom. Hopefully epicexperience will work if I do a clean wipe which I didn't try yet. But i'm open to any advices, suggestions. Can anyone with experience tell me which rom is all around better for battery life, looks.themes/launchers/widgets, performance?
One last question (sorryyy!!!), I leave juicedefender running 24/7 so my data/3g could be disabled whenever the phone is idle. Logically, I think this saves battery, but i've read here and there that literally bakedsnack rom saves more battery without juicedefender running. Is this true? if yes, then how?
I am sorry for such a huge post but I am confused lol.. Thank you very much for bearing with me. I appreciate it a lot and will appreciate any help. Once again Thanks.
Click to expand...
Click to collapse
Alright, well since your new to all of this I wont get into technical detail to confuse you.
But, now that you have flashed Baked Snack, you are running Baked Snacks kernel as well as the ROM. What I suggest you do is go to recovery and than wipe data/cache/dalvik cache (Located in Advanced). And than flash Epic Experience, than reboot. After it boots up, you will be running Epic Experience with Baked Snack kernel because Epic Experience doesn't have its own Custom Kernel so it keeps the kernel you have on the system already.
Now, Epic Experiences theme is nothing like BakedSnacks, and your probably nto going to like EE's theme if you like BakedSnacks, so what you should do is go to the Themes And Apps part of this forum and go to Baked Snack Theme. Download that and put it on your SD card, go into recovery and flash it just like you flash ROM's and Kernels.
Now you will be running Epic Experience ROM, Baked Snacks Kernel, and Baked Snacks theme. Thats your best bet because Epic Experience has a great rep around here because its constant updates.
Theres my two cents.
Also, check out the Emotionless Beast theme in the themes and apps section, Mysteryemotionz combined Baked Snacks theme and Androdena Theme together, it looks awesome.
SemiGamer said:
Alright, well since your new to all of this I wont get into technical detail to confuse you.
But, now that you have flashed Baked Snack, you are running Baked Snacks kernel as well as the ROM. What I suggest you do is go to recovery and than wipe data/cache/dalvik cache (Located in Advanced). And than flash Epic Experience, than reboot. After it boots up, you will be running Epic Experience with Baked Snack kernel because Epic Experience doesn't have its own Custom Kernel so it keeps the kernel you have on the system already.
Now, Epic Experiences theme is nothing like BakedSnacks, and your probably nto going to like EE's theme if you like BakedSnacks, so what you should do is go to the Themes And Apps part of this forum and go to Baked Snack Theme. Download that and put it on your SD card, go into recovery and flash it just like you flash ROM's and Kernels.
Now you will be running Epic Experience ROM, Baked Snacks Kernel, and Baked Snacks theme. Thats your best bet because Epic Experience has a great rep around here because its constant updates.
Theres my two cents.
Also, check out the Emotionless Beast theme in the themes and apps section, Mysteryemotionz combined Baked Snacks theme and Androdena Theme together, it looks awesome.
Click to expand...
Click to collapse
whoaa I didn't know that was possible. So it keeps my bakedsnack kernel which already has the cpu undervolted? how can I know for sure one I install EE? gonna give it a shot now. THANKSSSS a lot man.
SemiGamer said:
Alright, well since your new to all of this I wont get into technical detail to confuse you.
But, now that you have flashed Baked Snack, you are running Baked Snacks kernel as well as the ROM. What I suggest you do is go to recovery and than wipe data/cache/dalvik cache (Located in Advanced). And than flash Epic Experience, than reboot. After it boots up, you will be running Epic Experience with Baked Snack kernel because Epic Experience doesn't have its own Custom Kernel so it keeps the kernel you have on the system already.
Now, Epic Experiences theme is nothing like BakedSnacks, and your probably nto going to like EE's theme if you like BakedSnacks, so what you should do is go to the Themes And Apps part of this forum and go to Baked Snack Theme. Download that and put it on your SD card, go into recovery and flash it just like you flash ROM's and Kernels.
Now you will be running Epic Experience ROM, Baked Snacks Kernel, and Baked Snacks theme. Thats your best bet because Epic Experience has a great rep around here because its constant updates.
Theres my two cents.
Also, check out the Emotionless Beast theme in the themes and apps section, Mysteryemotionz combined Baked Snacks theme and Androdena Theme together, it looks awesome.
Click to expand...
Click to collapse
Oh and what do you recommend I do for the best battery performance? should I leave this kernel or should I flash phoenix? still having commitment issues whether I should keep this EE (i have installed it successfully). Its running perfect for me but I compare the logs between EE and Bakedsnack, and bakedsnack seems to offer so much more: better battery all around, faster performance (from what the log states), camera tweaked to get better videorecording framrates (im a huge camera guy). The only thing stopping me from going back to bakedsnack is that the forums are only for authorized help, so I cannot educate myself further about the rom lol.. and the developer is less fan-friendly.
what od you think about me running juicedefender 24/7? will it help me or harm me with the battery usage?
anyone? please..
Well I was looking for a new kernel the other day. I was getting tired of the lag of kingklicks kernels for gps. No offense king, Ive used your kernels since day one of my inc. So I went searching for a new kernel and tried out ziggys outrageous 1.28 lightspeed kernel which turned out to b false (really 1.15, somebody lied to him bout the code). Well on Oct 26th he came out with his new BFS kernel of the source code 2.6.32.24 with being overclock to 1.19. He uses this for bfs which king is still using 2.6.32.15. So far as using it no lag on gps and still get the same quadrant(1680) and linpack(40.223) as kings BFS. If you looking to try a new kernel heres the link. I hope ziggy471 dont mind but mad props to him.
http://www.ziggy471.com/2010/10/26/ziggy471-incredibleincredible-aospevobravo-kernels-updated-26-oct/
Thanks for the word sir.
Sent from my ADR6300 using XDA App
thisguy23 said:
Thanks for the word sir.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
No problem. Im always looking for new kernels and other mods.
did you download the AOSP kerenel or the other one? whats the diff? i downloaded both and they kept on making my phone freez so i went back to hydrakernel.
Dinc User said:
did you download the AOSP kerenel or the other one? whats the diff? i downloaded both and they kept on making my phone freez so i went back to hydrakernel.
Click to expand...
Click to collapse
I have used it on skyraider 3.3.2 now for the last 3 days with exceptional responsiveness and exceptional battery life. I heard people use the AOSP kernel for cyanogenmod and it has been worthy for them too. Difference is AOSP is for people who dont use SENSE UI in the rom. What rom are you using? Also did you clear dalvik cache and regular cache for. I downloaded the non-AOSP.
You can't be using one or the other kernel, either your running an AOSP rom or a Sense rom. That right there tells you which kernel to choose.
shoman24v said:
You can't be using one or the other kernel, either your running an AOSP rom or a Sense rom. That right there tells you which kernel to choose.
Click to expand...
Click to collapse
I hope this is in reference to the comment above my last one. Cuz I do know what kernel and rom Im running. I use the non-AOSP cuz my sense ui is still intact. NON_VANILLA
This is BFS with HAVS correct? How is the battery life/responsiveness?
Battery life is excellent, best I have had. Quadrant has been in the 1400's consistently (overclocked to 1.113), as apposed to others that are in the 1100-1200 range (including king's) with random moments of greatness into 1400.
Panda Fuzz said:
Battery life is excellent, best I have had. Quadrant has been in the 1400's consistently (overclocked to 1.113), as apposed to others that are in the 1100-1200 range (including king's) with random moments of greatness into 1400.
Click to expand...
Click to collapse
Does it lag at all though? I installed King's CFS on CM 6.0.2 and it lagged alot. The 6.1rc2 kernel is very snappy
Nope, no lag. Just a good kernel. I am actually very pleased considering I have suffered with others.
After about 20 or so hours my phone has to be restarted, for some reason there is lag that occurs that can only be fixed with a reboot.
I've had this happen with other kernels too
shoman24v said:
After about 20 or so hours my phone has to be restarted, for some reason there is lag that occurs that can only be fixed with a reboot.
I've had this happen with other kernels too
Click to expand...
Click to collapse
This is why I stopped using Kings kernals, phone gets stuck at 100% cpu and needs to be reset.
That sucks this kernal does the same.
I just wiped Dalvik and system cache, installed and rebooted. It's seemingly stuck on the bootscreen. How long has it taken to reboot you guys?
Up to ten minutes after wiping Dalvik cache. Hang tight!
It's probably the BFS scheduler... even though the bfs faq says it's good to use in phones.. lol
http://ck.kolivas.org/patches/bfs/bfs-faq.txt
I wonder if our phones would benefit from a higher tickrate when using bfs..
james_pnut said:
I have used it on skyraider 3.3.2 now for the last 3 days with exceptional responsiveness and exceptional battery life. I heard people use the AOSP kernel for cyanogenmod and it has been worthy for them too. Difference is AOSP is for people who dont use SENSE UI in the rom. What rom are you using? Also did you clear dalvik cache and regular cache for. I downloaded the non-AOSP.
Click to expand...
Click to collapse
I use the same ROM 3.3.2 as you. I downloaded the non-aosp version of ziggy's kernal. I wiped my cache and dalvik...but no luck with this kernal. My phone just keeps rebooting. See my signature line below and tell me what is different from your setup. Are you using HBoot .92???
im using radio .07.28 and CMR 2.5.0.5 Difference in you your signature
james_pnut said:
I have used it on skyraider 3.3.2 now for the last 3 days with exceptional responsiveness and exceptional battery life. I heard people use the AOSP kernel for cyanogenmod and it has been worthy for them too. Difference is AOSP is for people who dont use SENSE UI in the rom. What rom are you using? Also did you clear dalvik cache and regular cache for. I downloaded the non-AOSP.
Click to expand...
Click to collapse
i using the stock rom, so i guess yea, im using sense ui. do i need a different rom for this kernel to work? ... and yes i did clear my dalvik and regular cache, but my phone still froze.
james_pnut said:
im using radio .07.28 and CMR 2.5.0.5 Difference in you your signature
Click to expand...
Click to collapse
Well, user "Panda Fuzz" is using this kernal okay with my radio version. Hmm.. Must be my 2.5.1.1 version of CMR. People have reported problems with SR 3.3.2 and 2.5.1.1, but not me. This will be the first problem I have encountered with it. Guess I will try going back to CMR 2.5.0.5 and give ole ziggy another shot.
I'm happily running EViO 1.8 with the modded #15 kernel, but want to try out Net's and Ziggys. Is there a package based way to revert to the stock kernel if I don't like them or is it only via restoring the nandroid image of /system and /boot?
Calkulin has made his ROMs (current and prior) and the kernel used in 1.8 available here.
Prior ROM Versions
droidbird said:
I'm happily running EViO 1.8 with the modded #15 kernel, but want to try out Net's and Ziggys. Is there a package based way to revert to the stock kernel if I don't like them or is it only via restoring the nandroid image of /system and /boot?
Click to expand...
Click to collapse
Thanks nviron, that was exactly what I was looking for. I do wish there was a native package manager so you could be sure you removed all the trailings from a previous kernel or package before installing another.
Think RPM or .ipk
Just remember to clear dalvik cache (and or other cache?) between flashes and you should be good.
Also, be aware of some issues with some kernels. For example, with net's 4.3.x, I had to power the device down after the first boot, power it back up with power/vol-down, and wipe dalvik cache again. Otherwise, it hard locks for some reason. Once this is done, however, it works flawlessly.
Yeah, but where is the fun in that?? lol J/K
Wait, I have an idea!
Code:
# apt-get remove htc-sense
droidbird said:
Thanks nviron, that was exactly what I was looking for. I do wish there was a native package manager so you could be sure you removed all the trailings from a previous kernel or package before installing another.
Think RPM or .ipk
Click to expand...
Click to collapse
nivron,
I just noticed your sig, that is exactly the setup I'm considering, Ziggy's 1/21 kernel, how do you like it for:
a) performance?
b) battery life?
c) compared to net's 4.3.1 havs nosbc?
A. Excellent
B. Excellent (with -100uv script)
C. Comparable so far, but haven't had the combo running long enough to give you a definite answer. ROM and kernel combos require a break-in period.
droidbird said:
nivron,
I just noticed your sig, that is exactly the setup I'm considering, Ziggy's 1/21 kernel, how do you like it for:
a) performance?
b) battery life?
c) compared to net's 4.3.1 havs nosbc?
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App
I've been running Ziggy's 1/21 for a few hours now and it seems pretty stable and performance seems decent. I'm considering dropping the battery saver scripts and going to smartass as conservative has a bit of ramp-up time between when you start doing something and when the governor gets your CPU speed up to match. Also, I like the idea of smartass handling the screen state in the governor instead of a script.
__
EVO 0004, EViO 1.8, Ziggy's 1/21, Conservative battery saver, ADW.Launcher
I was just wondering about the kernels for CM7, it seems like every other week pershoot comes out with a new kernel, what's the advantage of flashing the new kernels?
___________________________
Sent from my T-Mobile G2 using XDA App
Android 2.3.3
OC'd to 1017 Mhz
CyanogenMod 7.0.0 Stable
ClockworkMod Recovery 3.0.2.4
Battery life, performance and under the hood stuff mostly. Pershoot is UV'd really low so you'll get better battery life. It's smooth as butter too. Flippy's is just a monster.
So, we can flash a new kernel, when we already have a CM. I'm on CM7, can a flash a pershoot kernel still? Would I have to wipe data, and re-flash CM7, then the kernel?
Just dalvik and cache if anything. You'll be safe with Pershoot's kernel if you're running anything that came out after nightly #31. I'm not sure about the G2 Fast kernel but it might be the same way. That's when the new gpu drivers came out.
Ok, that sounds good, better battery life is always worth it.
___________________________
Sent from my T-Mobile G2 using XDA App
Android 2.3.3
OC'd to 1017 Mhz
CyanogenMod 7.0.0 Stable
ClockworkMod Recovery 3.0.2.4
Honestly i have found that Flippys kernel includes the powersave governor, using that with a screen off profile in set cpu is a HUGE battery saver, as long as when the screen is on your not clocked too high cause then it defeats the purpose.. .. not to mention it includes the ability to well.. go fast..
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