Hi all,
I have CM10.2 nighly (JLS36G build) + Franco Kernel 188 JSS.
Since I flashed CM10.2, I started noticing random freezes when I write something with the on-screen keyboard.
It lasts 5-6 seconds and then everything starts working again.
I remember that I read somewhere that this issue happens on JSS/JLS builds... but I'm wondering if some fix/workaround has been already found. Any solution while we wait KitKat?
Thank you.
giaomnitel1 said:
Hi all,
I have CM10.2 nighly (JLS36G build) + Franco Kernel 188 JSS.
Since I flashed CM10.2, I started noticing random freezes when I write something with the on-screen keyboard.
It lasts 5-6 seconds and then everything starts working again.
I remember that I read somewhere that this issue happens on JSS/JLS builds... but I'm wondering if some fix/workaround has been already found. Any solution while we wait KitKat?
Thank you.
Click to expand...
Click to collapse
Those are called Deadlocks. It's a bug in the AOSP Mako source. You solve it by using a Hybrid ROM, like PA, or others.
abaaaabbbb63 said:
Those are called Deadlocks. It's a bug in the AOSP Mako source. You solve it by using a Hybrid ROM, like PA, or others.
Click to expand...
Click to collapse
Thank you. So there is no way to solve it in CM 10.2 or other AOSP-based roms.
giaomnitel1 said:
Thank you. So there is no way to solve it in CM 10.2 or other AOSP-based roms.
Click to expand...
Click to collapse
Nope, sadly.
Related
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.
until to 10.0.0 cyanogen i used marmite v7, now i update to 10.1.2, so i would an advice about the kernel...
marmite_v8.7 or the default kernel of cyanogen??
or if yor are any advice...
thanks
I would advise to stay with the stock cm kernel. For the past few weeks cm has been working very well, performance-wise.
andrei1015 said:
I would advise to stay with the stock cm kernel. For the past few weeks cm has been working very well, performance-wise.
Click to expand...
Click to collapse
ok i'll try !!!
In the post of cm 10.1.2 i've read about franco'kernel, how about ?
Yea stay with CM kernel especially if your on CM ROM
Sent from my Nexus 7 using xda premium
Ok let me make this clear. Marmite is not bad at all. But I don't use it for two reasons:
1. I flash daily. Flashing another thing daily (the kernel) is too much of a hassle for me.
2. I did have some small problems with it, but they might have been just random.
Hi guys, i rooted my phone days ago and i decided to flash a custom ROM into it. I chose AOKP latest nightlies build but after flashing it i realise that the wifi is not working (take forever to turn on in grey color even after i rebooted for many times). I thought maybe the nightlies build is not stable so i changed to m2 but the same problem occurfed. I really need help please,.. Thanks alot for the considerations.
strife91 said:
Hi guys, i rooted my phone days ago and i decided to flash a custom ROM into it. I chose AOKP latest nightlies build but after flashing it i realise that the wifi is not working (take forever to turn on in grey color even after i rebooted for many times). I thought maybe the nightlies build is not stable so i changed to m2 but the same problem occurfed. I really need help please,.. Thanks alot for the considerations.
Click to expand...
Click to collapse
Try wiping cache, davilk cache and then data. If WiFi still don't work try reflashing ROM. If the issue still here, try flashing factory image and see if the WiFi is working. If it is working on stock ROM, install CM or Paranoid Android or SlimKat.
msihp said:
Try wiping cache, davilk cache and then data. If WiFi still don't work try reflashing ROM. If the issue still here, try flashing factory image and see if the WiFi is working. If it is working on stock ROM, install CM or Paranoid Android or SlimKat.
Click to expand...
Click to collapse
Thanks for the reply. i tried reflashing rom but the pproblem is still there. The WIFI work perfectly in stock ROM.. Anyway, any Nice ROM have similar customization as AOKP recommended?
Restore your Nandroid backup, it would definitely solve the problem.
Btw what device are you on?
Sent from my GT-I9082 using XDA Premium 4 mobile app
Well, you can customize every ROM with Xposed which is now out for Android 4.4. I'd recommend you SlimKat but to be honest it dosen't have many features due to early Alpha stage of KitKat but they are coming in every update!
If you've gone from 4.3 to a 4.4 rom, you may need to flash the latest radio to have WiFi working.
agrawalshlok96 said:
Restore your Nandroid backup, it would definitely solve the problem.
Btw what device are you on?
Sent from my GT-I9082 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Im using N4.. i did restore my stock ROM and it work perfectly ff that's what u mean by nandroid backup..
could be kernel issue. Try flashing stock kernel.
meangreenie said:
If you've gone from 4.3 to a 4.4 rom, you may need to flash the latest radio to have WiFi working.
Click to expand...
Click to collapse
I' staying at 4.3.x
badboy47 said:
could be kernel issue. Try flashing stock kernel.
Click to expand...
Click to collapse
II guess it's kernel problem.. I try to flash franco.Kernel.Plus-r193-1110-JSS-CAF but the phone wont start at all...
If you insist on staying on 4.3.1, i would like to suggest the below rom:
AOKPK by kecinzer
Thread:
http://forum.xda-developers.com/showthread.php?t=2491689
Download this version:
aokpk_mako_jb-mr2_daily_1310271731
http://goo.im/devs/kecinzer/aokpk/mako
It comes with forked of franco.Kernel JWR version with new prima drivers (faster wifi speed, better battery life). Its a great rom with lots of features.
You need to change baseband to something like .33. Look on xda and you will find it.
Sent from my Nexus 4 using xda app-developers app
wcn said:
If you insist on staying on 4.3.1, i would like to suggest the below rom:
AOKPK by kecinzer
Thread:
http://forum.xda-developers.com/showthread.php?t=2491689
Download this version:
aokpk_mako_jb-mr2_daily_1310271731
http://goo.im/devs/kecinzer/aokpk/mako
It comes with forked of franco.Kernel JWR version with new prima drivers (faster wifi speed, better battery life). Its a great rom with lots of features.
Click to expand...
Click to collapse
Thanks for the suggestion What if i wanted to move to 4.4? Any good suggestion?
Hello, you have to flash older radio to enable wifi. Try version 84. Just flash the zip from CWM.
http://forum.xda-developers.com/show....php?t=2087227
strife91 said:
Hi guys, i rooted my phone days ago and i decided to flash a custom ROM into it. I chose AOKP latest nightlies build but after flashing it i realise that the wifi is not working (take forever to turn on in grey color even after i rebooted for many times). I thought maybe the nightlies build is not stable so i changed to m2 but the same problem occurfed. I really need help please,.. Thanks alot for the considerations.
Click to expand...
Click to collapse
I‘ve met problems similar to you using AOKP, I've solved it by flashing another stable AOKP rom.
i had my nexus on 4.4 rooted, when i use a rom based on 4.3 wifi, bluetooth and sounds doesnt work, when i flash a rom based on 4.4 (omni, crdroid) everything work just fine... could it be a RADIO problem??? where i can find the older radio since the link in here doesnt work?
Thank you
strife91 said:
Thanks for the suggestion What if i wanted to move to 4.4? Any good suggestion?
Click to expand...
Click to collapse
Well, everyone has their own preferences. There are many great 4.4 roms out there. I could not suggest something that I've had never used before. I've tried a few roms and only the below stayed on my phone:
Multiboot:
•Cataclysm-Nov-25 - by atlantis
•Project KitKat v2.1 - by gnome
Kernel:
•hells-Core-b42 (kexec-harboot patched)
•AK.207.KK
Give yourself chances to try some other rom. There is nothing to loose. Nandroid backup your existing rom. If you don't like the new rom, restore from Nandroid. You'll then determine which rom suits you best.
i found out the solution is very simple....
if you use a 4.4 based rom.... flash the radio version 97
if you use a 4.3 based rom.... flash the radio version 84
thats it
Are they still going the CAF route? Or is that ending since it mainly had to do with freezes (if I recall) in 4.3?
It's going to affect my decision to go back to 10.1. I really want to have touch2wake on my kernel and these fixes to make faux and franco kernels function are starting to cause issues on 10.2.
AFAIK, these developers will not be supporting CAF =/
Elegant996 said:
Are they still going the CAF route? Or is that ending since it mainly had to do with freezes (if I recall) in 4.3?
It's going to affect my decision to go back to 10.1. I really want to have touch2wake on my kernel and these fixes to make faux and franco kernels function are starting to cause issues on 10.2.
AFAIK, these developers will not be supporting CAF =/
Click to expand...
Click to collapse
freezes on 4.3 was due to bug in aosp jss code, witch have been fixed in 4.3.1. so update to lastest cm.
and in 4.4 they will continue.
Yeah, I'm running the stable release of 10.2 with ziddley's franco kernel and it's causing issues here and there now. I was hoping they were going to revert back to AOSP. I guess I'll revert back to 10.1 to maintain my desired functionality for now.
Elegant996 said:
Yeah, I'm running the stable release of 10.2 with ziddley's franco kernel and it's causing issues here and there now. I was hoping they were going to revert back to AOSP. I guess I'll revert back to 10.1 to maintain my desired functionality for now.
Click to expand...
Click to collapse
ahh u using custom kernel, not cm one.no issue while i was on cm 10.2 with my modified build of franco.kernel
opssemnik said:
ahh u using custom kernel, not cm one.no issue while i was on cm 10.2 with my modified build of franco.kernel
Click to expand...
Click to collapse
Yeah, unless there's some way to get touch2wake working on 10.2; I heard you have gamma settings now with the caf kernel included so I figure I can maintain my color scheme.
Elegant996 said:
Yeah, unless there's some way to get touch2wake working on 10.2; I heard you have gamma settings now with the caf kernel included so I figure I can maintain my color scheme.
Click to expand...
Click to collapse
try with other kernels.
On CM11 and Cm10.2 try these: 1) Modified franco and faux to work on Cm : http://forum.xda-developers.com/showthread.php?t=2487246
2) AK has CM exclusive kernel : http://forum.xda-developers.com/showthread.php?t=2473454
opssemnik said:
ahh u using custom kernel, not cm one.no issue while i was on cm 10.2 with my modified build of franco.kernel
Click to expand...
Click to collapse
You can always follow a tutorial to build your own cm from source code and enable module support. In that way you won't be using custom kernels, everything will be cm 100%.
I am using touchcontrol in that way, and I'm quite happy with the results.
Sent from my Nexus 4 using xda app-developers app
CM11 is great with hells-core. Touch control works, and battery/performance is amazing.
korockinout13 said:
CM11 is great with hells-core. Touch control works, and battery/performance is amazing.
Click to expand...
Click to collapse
I have been trying to find a link for 15 minutes!
Could you provide me with a link?
Thanks!
myweca said:
I have been trying to find a link for 15 minutes!
Could you provide me with a link?
Thanks!
Click to expand...
Click to collapse
Right in the general section: http://forum.xda-developers.com/showthread.php?t=2495373
I have a Note 3 with Cyanogenmod 11 nightly, a custom kernel from Temasek (3.4.83-cm11-SM-900x-v3.10+) and Nova Launcher.
And sometimes my phone freezes, screen goes out, I feel it vibrate short and it restart. What can I do about this?
(And is this owing to CM11 or the custom kernel? (Or Nova Launcher?))
Absolutly nobody knows whats cousing this?
JaimyLuca said:
Absolutly nobody knows whats cousing this?
Click to expand...
Click to collapse
I'm not sure about cm11 as i'm using tw but it could be the kernel. Try dirty flash the rom to get back to stock cm11 kernel and see it it persists. Worth a try
Thanks for the given option. I will try it when battery is full.
Rosli59564 said:
I'm not sure about cm11 as i'm using tw but it could be the kernel. Try dirty flash the rom to get back to stock cm11 kernel and see it it persists. Worth a try
Click to expand...
Click to collapse
I have given it some time, but since I dirty flashed Cm11 and not the Custum Kernel I have no more freezings and reboots! Thanks!