I'm just not getting it.
I have a tmobile 10.1 galaxy tablet SGH-T898.
I've downloaded pershoot's kernel boot-cm_2636.4_tmo-oc-xtra-vfpv3-d16_fp-010912 and went in to CMW and flashed then i rebooted.
After reboot i installed setcpu apk
then it says your su binary is outdated, i try to update but it says it cant be updated.
setcpu range max is 628 and min is 528
what am i missing?
Here we discuss the same problem:
http://forum.xda-developers.com/showthread.php?t=1792473
Recommendation:do not overclock...(recommendation,not obligation)
arashtarafar said:
Here we discuss the same problem:
http://forum.xda-developers.com/showthread.php?t=1792473
Recommendation:do not overclock...(recommendation,not obligation)
Click to expand...
Click to collapse
Didn't help me...
Anyone?..?.?
I would suggest looking for a rom that has the pershoot kernel built into it already so it's in place when you flash it. When I first installed a custom rom on my galaxy tab I had the same issue with the kernel. Ended up just using a different rom and problem was fixed. May have been an incompatibility with your device in some way.
kosuke85 said:
I would suggest looking for a rom that has the pershoot kernel built into it already so it's in place when you flash it. When I first installed a custom rom on my galaxy tab I had the same issue with the kernel. Ended up just using a different rom and problem was fixed. May have been an incompatibility with your device in some way.
Click to expand...
Click to collapse
Would have to agree with this! Easiest option
Related
My first root, eng-off and all that I did through a guide on the internet that included kernel and rom for Leedroid.
Now I've installed AR3.6 and I'm wondering if I need to manually instal a new kernel or if the roms contain the appropriate kernels themselves.
a ROM always includes a kernel, but you can flash another one if you want to.
Yeah can't wait till theres a kernel for ARHD 4B4
here you got your oc kernel rolando88 click me
Blezz said:
here you got your oc kernel rolando88 click me
Click to expand...
Click to collapse
I wouldn't recommend that for daily use though.. apparently it's buggy as.
i'm using this kernel since an hour now and haven't found any problems yet. battery life seems quite good also but i'll report back after a while
I was wondering about the overclocking kernal for cm7. just how do i put it in. Do I have to do that when I first install or can I add it later. also does it really help. I mean is the difference really noticeable or not at all. I am still deciding if I should do it or not.
Kernels are flashed through ClockworkMod and can be flash anytime after you flash a rom. If you use the search bar you can easily find what particular kernel works for your setup.
OK, I think I found the right one but I was also wondering if I could install it when I first installed cm7. When I installed it I saw that it was searching for the kernel and for gapps but didn't find the n and skipped it. Could I install it then
chad11 said:
OK, I think I found the right one but I was also wondering if I could install it when I first installed cm7. When I installed it I saw that it was searching for the kernel and for gapps but didn't find the n and skipped it. Could I install it then
Click to expand...
Click to collapse
CM7 has the ability to be overclocked as it sets.
settings > CM settings > performance > CPU settings.
just be extremely careful when Overclocking devices. it can takes it's toll in the long run.
and the g/apps are not kernel dependent they are ROM dependent.
OK but what do you mean by gapps are not kernal dependant
chad11 said:
OK but what do you mean by gapps are not kernal dependant
Click to expand...
Click to collapse
On *UNIX based devices. They have a section of the firmware called the "kernel". The kernel accepts the coding, binary and scripts from the RAM/ROM and tells the hardware how to act, what to do, and when to do it.
The g/apps have nothing to do with the kernel.
The g/apps are Google's property and cannot be included in AOSP based ROMs. Those ROMs are developed from Google's code. And developers do not have the ability to add those at will. So we must flash them after/prior (depending on he ROM) to get the Google Apps.
YES! DO IT!
for me its like day and night, it so much smoother with dals OC kernel. and yes you can flash the OC kernel any time. you can flash cm7 rc1 then OC kernel in the same boot. or you can first install cm7 to check it out for a while and then later flash the new kernel. if you planning to flash dal's 6/18 kernel, make sure to get his app NC Tweaks.
NC Tweaks here:
http://forum.xda-developers.com/showthread.php?t=1104039
Dal's Kernel here:
http://forum.xda-developers.com/showthread.php?t=925451
thanks. What I want to know is how to flash it. do I do it the same way as gapps( have wifi and reboot in recovery mode) or is there a different way?
chad11 said:
thanks. What I want to know is how to flash it. do I do it the same way as gapps( have wifi and reboot in recovery mode) or is there a different way?
Click to expand...
Click to collapse
You place the over clock zip file in the root of your sd card and flash it through cwm like you would a rom or gapps. So for example you would flash cm7 then gapps then the overclock kernel.
Not to Jack this thread, but I want to update from cm7 old kernel to New nightly build. Does the new kernel flash with the nightly?
Sent from my Optimized Shift using XDA App
JeramyEggs said:
Not to Jack this thread, but I want to update from cm7 old kernel to New nightly build. Does the new kernel flash with the nightly?
Sent from my Optimized Shift using XDA App
Click to expand...
Click to collapse
When you move from stable cm7 to cm7 nightly the new kernel is included. However the included kernel is overclockable only to 975mhz. If you want a higher clock speed you'll have to use dals 6182011 kernel, up to 1200mhz.
whats is cmw?
chad11 said:
whats is cmw?
Click to expand...
Click to collapse
it's actually CWM.
ClockWork Manager
basically boot into recovery then flash.
OK. but this may be a stupid question but will the cm7 kernal work with the stable version7.0.3 because that is what I have.
chad11 said:
OK. but this may be a stupid question but will the cm7 kernel work with the stable version7.0.3 because that is what I have.
Click to expand...
Click to collapse
I'm not following you cannot use just a Cyanogen(mod) kernel. They are built into their ROMs.
chad11 said:
OK. but this may be a stupid question but will the cm7 kernal work with the stable version7.0.3 because that is what I have.
Click to expand...
Click to collapse
sorry, but no. dal's 6/18 OC kernel will not work with 7.0.3....
...just flash n118 and you'll be fine
Ok thanks anyway. do you know when the kernal will work with a stable version
chad11 said:
Ok thanks anyway. do you know when the kernal will work with a stable version
Click to expand...
Click to collapse
The latest nightly should be considered stable. It is in release candidate stable for the next stable build. The next stable build should be released in the next couple of days.
neidlinger said:
it's actually CWM.
ClockWork Manager
basically boot into recovery then flash.
Click to expand...
Click to collapse
No--It's- Clock Work Mod Recovery
CWMR ;^}
Jimbo67 said:
No--It's- Clock Work Mod Recovery
CWMR ;^}
Click to expand...
Click to collapse
There is a Clockwork ROM Manager and a ClockworkMod Recovery image.
Together they are known as "CWM" Since one is a recovery and the other is a ROM manager.
Hi guys,
I use Cyanogenmod 10.1 shortly after I bought my Nexus 10 and had these reboots the whole time.
Usually I update once or twice a week to the current nightlys (depending on the changelog).
A problem I have from the beginning (with CM): When I stream music with Google Music to a Logitech Bluetooth receiver it works. But every 20-30 seconds I have a litte break in the playback. On my Galaxy S2 also with CM 10.1 I never had this problem.
What I did to solve the problem. Today I installed the stock Nexus 10 4.2.2 from Google and tried to reproduce the error. It worked fine. No problem at all.
Then I completely wiped the Nexus 10 again and installed the current nightly - from the scratch. Just installed Google Music and did a test. The same bluetooth problem again.
Ah and when I use a bluetooth keyboard the keyboard also loses connection time and again. Here the problem is even worse. When I´m are in web form the page gets reloaded and all I entered so far is gone...
Has anybody an idea?
I´m willing to give you all the information you need to help me (logcats etc.)
Thanks in advance
Marrtin
Have you tried using the stock kernel with CM10?
stiggy2012 said:
Have you tried using the stock kernel with CM10?
Click to expand...
Click to collapse
Hi and thanks for you answer.
Good idea. But I have no clue how to do that? And isnt´t the kernel always overwritten when I install a nightly of CM10.1?
Wishes
Martin
Martin7404 said:
Hi and thanks for you answer.
Good idea. But I have no clue how to do that? And isnt´t the kernel always overwritten when I install a nightly of CM10.1?
Wishes
Martin
Click to expand...
Click to collapse
I actually don't know off-hand, but it probably is, if its like other ROM's.
dibblebill said:
I actually don't know off-hand, but it probably is, if its like other ROM's.
Click to expand...
Click to collapse
Hmm - and where can I get the stock kernel from? Off course I found the whole stock firmware. But just the kernel out of it? And does this work together with CM?
Please make a bug report @ jira.CyanogenMod.org
Sent from my Nexus 10 using Tapatalk HD
Martin7404 said:
Hmm - and where can I get the stock kernel from? Off course I found the whole stock firmware. But just the kernel out of it? And does this work together with CM?
Click to expand...
Click to collapse
I don't think you can pull just the kernel out of it... I use KTManta myself.
dalingrin said:
Please make a bug report @ jira.CyanogenMod.org
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
Thanks - I just did so.
Martin7404 said:
Thanks - I just did so.
Click to expand...
Click to collapse
Thanks!
dibblebill said:
I don't think you can pull just the kernel out of it... I use KTManta myself.
Click to expand...
Click to collapse
You can. :good:
If you download and unzip the official rom package from google, you will find another zip inside. Extract that, and you will see a different rom for each partition of your nexus 10. boot.img is the kernel, and it can be flashed from fastboot using command "fastboot flash boot boot.img".
Thanks,
EDIT: If the KTManta kernel doesn't suffer bluetooth streaming issues for anyone else, flashing it instead of stock should serve as an equally good test. The original reason I mentioned flashing the stock kernel is because I too have seen bluetooth streaming issues, both with CM10 and when using the stock rom with franko r12 kernel. I'm now running completely stock rom and kernel, and have no issues.
stiggy2012 said:
You can. :good:
If you download and unzip the official rom package from google, you will find another zip inside. Extract that, and you will see a different rom for each partition of your nexus 10. boot.img is the kernel, and it can be flashed from fastboot using command "fastboot flash boot boot.img".
Thanks,
EDIT: If the KTManta kernel doesn't suffer bluetooth streaming issues for anyone else, flashing it instead of stock should serve as an equally good test. The original reason I mentioned flashing the stock kernel is because I too have seen bluetooth streaming issues, both with CM10 and when using the stock rom with franko r12 kernel. I'm now running completely stock rom and kernel, and have no issues.
Click to expand...
Click to collapse
If I switch back to CM, I'l be sure to test it. I'm currently in the process of deciding just how much I love "CRT Off", which I don't know if CM has added yet
Is there a solution for this stuttering problem? I have tried many roms and kernels, but bluetooth stutters when wifi is on.
Any rom I ccok on the kitchen wont boot. I even tried the stock m919 firmware and it wont pass the boot logo. I wonder if this have something to do with kitchen or not?
Cant do logcat because phone wont fully connect to computer. It says waiting for device on adb commands.
I wonder if anybody could help me out. I can send you the rom and see for yourself.
Is this a kitchen problem or not. Also kitchen wont deodex rom I had to do it on a 3rd party app like universal deodex. This is getting annoying since I want my own rom with my own mods. I never had problems with other devices before.
I got the same issue, anybody can help us here? mine gets to the samsung logo, after the bootanimation, and stays there.....
pendejerto said:
I got the same issue, anybody can help us here? mine gets to the samsung logo, after the bootanimation, and stays there.....
Click to expand...
Click to collapse
Use logcat to debug what the issue is..
pendejerto said:
I got the same issue, anybody can help us here? mine gets to the samsung logo, after the bootanimation, and stays there.....
Click to expand...
Click to collapse
gypsy214 said:
Any rom I ccok on the kitchen wont boot. I even tried the stock m919 firmware and it wont pass the boot logo. I wonder if this have something to do with kitchen or not?
Cant do logcat because phone wont fully connect to computer. It says waiting for device on adb commands.
I wonder if anybody could help me out. I can send you the rom and see for yourself.
Is this a kitchen problem or not. Also kitchen wont deodex rom I had to do it on a 3rd party app like universal deodex. This is getting annoying since I want my own rom with my own mods. I never had problems with other devices before.
Click to expand...
Click to collapse
don't use stock kernel. if you are making rom for i9500 use perseus kernel. only problem for not booting up is stock kernel. i don't know custom kernel for other s4 variants but do use best custom kernel available
nish983 said:
don't use stock kernel. if you are making rom for i9500 use perseus kernel. only problem for not booting up is stock kernel. i don't know custom kernel for other s4 variants but do use best custom kernel available
Click to expand...
Click to collapse
there is nothing wrong with stock kernel. it is perfect. the problem is kitchen is usin deodexing api which is a lower version. now 4.3 needs a higher version.
perseus is good kernel. but it gives errors in mtp so beware
Degrated Shadow said:
there is nothing wrong with stock kernel. it is perfect. the problem is kitchen is usin deodexing api which is a lower version. now 4.3 needs a higher version.
perseus is good kernel. but it gives errors in mtp so beware
Click to expand...
Click to collapse
i know it has lower api level but the problem is stock kernel . i faced the same problem but as soon as i replaced it with persues it booted up. and de-odexing works perfect i dont know why but it does
nish983 said:
i know it has lower api level but the problem is stock kernel . i faced the same problem but as soon as i replaced it with persues it booted up. and de-odexing works perfect i dont know why but it does
Click to expand...
Click to collapse
i repeat no problem with stock kernel. 4.3 stock kernel and sources need higher api of deodexing
perseus adds support also for lower api as higher i think.
But even stock 4.2.2 wont boot. It gets annoying it just stay on boot logo. I tried many roms I made in kitchen and none work. So I figure it was a kitchen issue on my end. Stock kernel too.
The sad thing about the thread is that it basically proves the developer discussion idea isnt working. Most rom devs with roms released do boot, otherwise they wouldnt still have those threads. I was really hoping a rom dev would answer here... but the issue doesn't have to do api or the kernel really. I don't release custom roms for the public but I do make myself a new one every couple days if I want to try something. If it doesn't boot that means you either edited the kernel on a locked device, editied the recovery partition on a locked device, didnt change the update-script to an updater-script script, added modules to the kernel that are not compatible, or make a rom from a base not compatible with your device, etc. I don't think its fair to blame kitchen for any of those issues, Dsidia does give clear instructions. Just my two cents.
dont use the kitchen to actually build the rom, zip it up yourself
Personally, i use the kitchen to extract, deodex and zipalign...nothing more, and i never have issues
DSA said:
dont use the kitchen to actually build the rom, zip it up yourself
Personally, i use the kitchen to extract, deodex and zipalign...nothing more, and i never have issues
Click to expand...
Click to collapse
I use it for the updater-script cause I'm too lazy to make it myself lol
Sent from my SGH-M919 using Tapatalk
Hi guys, happy new year!
So, i'm testing the rom "Nexus 5 Experience (Kitkat 4.4.2)" and everything seems ok, i'm testing the version CAF Kernel. now i'm tryin install new kernels on this rom, but at every kernel I install i get the same error, after instal any kernel, I turn on my N4 and the screen seems very strange, colors flashing, sometimes when i start a game (or anything that forces the gpu) the screen is filled by one or two colors, but the touch is still working, is just a screen or gpu (i dont know) error.
I tryed to take some printscreens, but when i will check this on my pc, everything is ok, like if theres no error.
When i flash the rom again, everything works normally.
what i'm doing wrong ? I thought to change kernel is only flash him, is it wrong ?
i'm newbie, got my n4 yesterday but i have some experience in my old xperia..
sorry the bad english, im br
Thanks guys!!
Are you installing CM compatible kernels?
Try the AK kernel CM version
http://ak.hiddenbytes.org/old/cm//AK.309.CM11P.zip
goofball2k said:
Are you installing CM compatible kernels?
Try the AK kernel CM version
Click to expand...
Click to collapse
heyy, this worked!
but i don't understand, i tryed this and a lot of kernels before (all compatible with CM) and doesnt work
so.. thanks! i will check this, recommend me another kernel ?
thanks again! cheers
mendes1995 said:
heyy, this worked!
but i don't understand, i tryed this and a lot of kernels before (all compatible with CM) and doesnt work
so.. thanks! i will check this, recommend me another kernel ?
thanks again! cheers
Click to expand...
Click to collapse
I can't say what you did wrong, maybe you got the wrong version since many make 2 versions of their kernel, one for AOSP and one for CM.
I don't run CM ROM's so I don't know which kernels are out there. HellsCore is also another kernel to consider, I believe there are CM versions of it as well.
goofball2k said:
I can't say what you did wrong, maybe you got the wrong version since many make 2 versions of their kernel, one for AOSP and one for CM.
I don't run CM ROM's so I don't know which kernels are out there. HellsCore is also another kernel to consider, I believe there are CM versions of it as well.
Click to expand...
Click to collapse
yes, i'll try HellsCore.
thanks for the help, i appreciate it!