Related
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
I just want to confirm that in android, both kernel and OS (custom/stock ROM) can be flashed in a phone separately. Just asking as I am surprised to know this fact about android and this is not possible in computer operating systems like windows or mac as these OSes, kernel is integrated with OS and you cannot change them as in android.
Sent from my GT-I5801 using XDA App
Afaik the OS runs on top of the kernel. So, whether it is a phone or a PC, if the kernel is compiled with the specific hardware modules it can be changed separately from the OS. I don't know how to do it in windows but have tried it in Ubuntu!
sent from my CM7 nokia 3210
can you reinstall kernel in ubuntu without reinstalling/formatting OS?
Sent from my GT-I5801 using XDA App
You can compile the Linux kernel according to your needs (add patches, filesystem support, power management tweaks, etc) and then boot from there! But the kernel will boot only if it is compiled for the OS version (or firmware when referring to phones) and certain hardware you want it to use. That is why a galaxy 3 froyo kernel for example runs only on a galaxy 3 and (except CM6) any froyo version (JPS, JPU, JPF...).
sent from my CM7 nokia 3210
Thanks panos. can you please let me know, in which scenarios we want to flash kernel and in which scenarios we want to flash custom ROM?
Sent from my GT-I5801 using XDA App
You choose a custom rom if you are not satisfied with stock. Most custom roms have their own modded kernel. If you want more features you can flash another kernel which has the functions you want. Now if you are happy with stock rom feel and looks but want overclock for example, then you get to choose one of the kernels which suits you.
sent from my CM7 nokia 3210
So, basically for look and feel, we choose ROM that suits us and for features and performance improvements, we choose different kernel other than stock one...Am I correct?
Basically yes. Some tweaks like JIT are part of the rom, not the kernel but performance is a kernel issue!
sent from my CM7 nokia 3210
Thanks panos for the clarification.
Sent from my GT-I5801 using XDA App
which is the best ics rom for gaming?
I think that kernel has more to do with games...
But with slimics + semaphore (xl ram) +smartass i am very happy with my gaming experience
I'm using the same config slimics 4.2 and semaphore 1.26s max mem option and smartassv2 with great results. Previously was using gamerzrom which is also a great gaming platform but is lacking on the user interface, just not smooth enough for my liking.
Sent from my GT-I9000 using xda premium
cm9 with sgs3 pack & semaphore 2.3.6
games run very well =>like gta 3, maxpayne etc .. thanks to live oc and our powerfull gpu
iam using a live oc of 17%
what about devil kernel for gaming and battery?
Elite scorpion 2 kernel have awesome 3D. It's the default kernel in Elite´s RC 1.4.1 ROM.
ThorEe said:
Elite scorpion 2 kernel have awesome 3D. It's the default kernel in Elite´s RC 1.4.1 ROM.
Click to expand...
Click to collapse
The 3D drivers in Elite's ROM are improved, nothing in kernel. Kernel doesn't affect gaming, they are all based on Linux kernel with some added functions and updated drivers.
gamerz rom v11 the games run smoothly ..
how the battery life in gamerzrom????
currently i have an i9000 , ICS 4.0.4 , f4kmod, with semaphore 1.2.5 VC, with bigmem, (200MB of ram FREE) and i CANT make gta 3 playable without lag...
what i can try?
what is smartassv2?
dark_knight35 said:
The 3D drivers in Elite's ROM are improved, nothing in kernel. Kernel doesn't affect gaming, they are all based on Linux kernel with some added functions and updated drivers.
Click to expand...
Click to collapse
lol,,, Kernel doesn't affect gaming :laugh: :laugh:
then why the kernel developers are here?
check the Speedmod Kernel and Stock one and Semaphore Kernel on NenaMark3D
for Best result on gaming you have to disable all services on Phone.
check the background application and services, close them all via app freezers
CM9
USE CM9 HES THE MOST STABLE dont use roms with ROM control cause it sometimes get stuck
1-elite comes with neo kernel not scorpion 2 kernel
2-use slimICS with devil3_O.99 it has gpu overclock . and you can control your amount of ram
3-kernels do affect 3d gaming .
dark_knight35 said:
The 3D drivers in Elite's ROM are improved, nothing in kernel. Kernel doesn't affect gaming, they are all based on Linux kernel with some added functions and updated drivers.
Click to expand...
Click to collapse
U high?? Lol
Sent from my GT-I9000 using xda app-developers app
For me many Roms are good to gaming, why? because everyone do OC, use ultimate Kernell, with some perfomance changes and voltages cpu,
but specialy don´t forget some signs like heater, because when we want power and perfomance, battery will die soon, screen will be little hot, and off course cpu.
gaming with carefull
M_J_Nazari said:
lol,,, Kernel doesn't affect gaming :laugh: :laugh:
then why the kernel developers are here?
check the Speedmod Kernel and Stock one and Semaphore Kernel on NenaMark3D
Click to expand...
Click to collapse
But they all have the more or less same fixes, comparing a custom kernel to stock kernel of course is senseless.
dark_knight35 said:
But they all have the more or less same fixes, comparing a custom kernel to stock kernel of course is senseless.
Click to expand...
Click to collapse
Try to oc to 1400 mHz on stock kernel or even custom kernel ( semaphore)
Sent from my GT-I9000 using xda app-developers app
You can use Slim rom with lastest Devil kernel. And you have 403Mb and CPU 1.5Ghz. You'll get best for gaming
I can oc to maximum 1440 mhz
Sent from my GT-I9000 using xda app-developers app
Currently running CM12, but I've been thinking between XenonHD, RastaPop, Euphoria OS, Terminus and LiquidSmooth.
Any experience about these ROMs? Most of these seem pretty same if you look at the features. But does some of these stand out?
Just start flashing and find out what you like the best.
sent with my Nexus 4.
As much as I hate CM I quite like the xenon.
Very stable and doesn't require too much micro management.
Well I had to install better battery stats but my battery problems might be down to a dodgy app.
I haven't tried them all but so far my favorite is my setup now...boostpop 2.7 with Franco sabermod kernel, overclocked to 1.7ghz max 192mhz minimum. Rro layers running giving the black look I liked on slimkat. It's as fast as I've ever felt this phone.
I've tried liquidsmooth v4 and a recent paranoid android and cm12 I think. Those are the only recent LP ROMs I've tried.
Sent from my Nexus 4 using XDA Free mobile app
Frank Rom and Rastapop both great 5'0'2 Roms with all latest optimizations like RRO etc
Hi,
I want to see if i can get Franco Kernel on my Nexus 4 running CyanogenMod 12.1. I tried using auto flash on the Franco Kernel app on the app store and it gave me a warning stating it might not work... Any suggestions whether it works or not? I don't want to ruin my phone
I tried this yesterday and my Nexus 4 was stuck in a bootloop after until I reflashed CM 12.1.
In short; no, don't do it.
There is two different types of Rom's and kernels. There is those that are based on AOSP and those who are based on CAF.
You can't mix different types of Rom's and kernels. So to you can't use a AOSP kernel on a CAF Rom and vice verca.
CM is a CAF based Rom and Franco kernel is an AOSP based kernel. So you can't use those together.