Related
Hi guys,
i installed Megatron and franco's kernel and I have an annoying problem. My CPU usage is very high, always at about 80 % and I don't know why. My launcher is always freezing after I unlock my phone. I tried Launcher Pro, ADW Launcher and GO Launcher. Does anyone have a solution for me?
The problem might be franco's kernel. did you have this problem before flashing the kernel? Franco has always maintained that the kernel is for his devoid.franco rom, and to try it on another rom at your own risk.
Sent from my LG-P500 using XDA App
Yeah reflash your ROM again.. without Kernel. Franco's Kernel work's on other ROM some don't..
Flash cavermans v3 kernel
its franco's kernel... i CONFIRM this i switched back to sippolo's
I can't find sippolo's kernel. Does anyone have the link for it?
Chun-kun said:
I can't find sippolo's kernel. Does anyone have the link for it?
Click to expand...
Click to collapse
1) version 1.0 http://forum.xda-developers.com/showpost.php?p=11256797&postcount=198
2) version 1.1 http://forum.xda-developers.com/showpost.php?p=11270721&postcount=237
Hello,
I have the same problem and I have 2.6.32.39-franco.Kernel.v13
and devoid.franco.v5 ROM. When I switch off and switch on my Optimus, for a few minutes it's working perfect, but after a few minutes of using phone I have the problem with Launcher freezing. I tried use default Zeam Launcher, GO Launcher, Launcher Pro but I'm affraid, that it doesn't depend's on launcher.
Can somebody help me?
Thank a lot for any suggestion!
EDIT:
I have installed kernel from blackz1982's post and it's absolutly perfect!!
So I'm using devoid.franco.v5 ROM and Sippolo's Touchscreen Optimizations Kernel v1.1 and everything seem's to be OK.
Hello everybody, after the installation of the ROM tw008 and custom kernel 3.60 photos does not register and video does not work , somebody would have a solution?
I test all the goro's kernel and its always the same problem . Please help me!!
vinss68 said:
I test all the goro's kernel and its always the same problem . Please help me!!
Click to expand...
Click to collapse
I really want to help but unfortunately i don't know what to help you on:
But:
1: Did you install the ROM/kernel properly?
2: Did you try re-installing?
3: Did you try flashing stock firmware than Wolfbreak's ROM.
4. Did it work on stock kernel?
5. DID YOU MAKE SURE YOU DOWNLOADED THE RIGHT 3.60 KERNEL BECAUSE GORO PUT THE WRONG LINK? (oops caps)
Download the goro kernel again and flash it HERE
Hope this helps
Hello thank you for your reponse, indeed I tried some thing, and with the good kernel .
I have try:
- to make a fresh instalation of bb.67 and of the ROM tw008, then of the custom kernel 360 (by trying all the camera resolution, and play on frequence cpu, anything has to make its not working). I have not try to make a fresh installation of firmware via SEUS (I try it now!!)
-Camera is completely functional with the stock kernel , with z's custom kernel (22,23,05) and with custom kernel 3.47 when i was on tw7 bb52, but I prefere the ck 360 for the underclock and bb.67
- with and without the theme which I use
And camera make always her tantrums
Well I try the fraiche installation firmware and I informed
Works fine for me and everyone else using it...
Must be something you're doing
Just for information if it can help to resolve the problem, when I takes a photo the image gallery makes an black screen and when I want to pass in video mode the application makes a sudden closure
always similar after a full fresh installation of all.... i don't know what's the problem. i think i will wait a future kernel with underclocking and stay with z's kernel for the moment ,but if anyone got a idea or question about situation ...
vinss68 said:
always similar after a full fresh installation of all.... i don't know what's the problem. i think i will wait a future kernel with underclocking and stay with z's kernel for the moment ,but if anyone got a idea or question about situation ...
Click to expand...
Click to collapse
you might be flashing the wrong version of the kernel for your rom....
it's strange because all working fine, just this problem with camera . i trying to reorganize my sd card she's in a mess... maybe it's the cause of my problem.
some opinion?
I don't think its related to the rom or custom kernel. I've had this problem on some of the custom roms I've tried. What ultimately fixed it for me is by formatting the sd card so make a backup of your entire sd card then format it.
Sent from my X10x using XDA App
Good news,
my problem is resolved. Yesterday evening I completely cleaned my card sd then I left the telephone have it reconfiguré. I remake fresh installation rom tw008 and of the custom kernel 360 and hop all work fine. I think that the problem came because I tested several applications camera,background which created several files for photos,images, because which never clean .i am finally going to be able to take advantage of quite its hey hey.
Thx all to be interested in you has my case and sorry for my bad english
Hello everyone I have a problem with touchsreen on GingerCrust v2.3,
Firstly I want to say sorry because this question is supposed to be in development thread but, since I still have a less posts in this forum so I have to post it in this thread.
Okay this is the problem
I already succeed to flash the GingerCrust v2.2 via CWM 5.0.2.6
And I found there's no problem with touchscreen and then I did the GingerCrust v2.3
And i've got the touchscreen problem (the touchscreen strongly not accurate and hard to swipe for changing app drawer and desktop page)
I already tried to do touch screen calibration test via *#*#2664#*#* touch screen test
but the code won't work
and I tried to find additional framework on it's official thread(by nims11) but there's none of it.
Did anybody have a problem like me? Is there already a solution for the problem that I found
Thats new bug you phased not anyone tell about and not im phasing any that thing
v2.2 and v2.3 are almost same just few things like odexed and some fix not much other thing
I have this problem also.
It's most apparent when typing, because random keys will frequently touch itself, mostly the s and d keys.
For example, I write "I love you", it will turn out as:
"Ids sdldovsed ysdous"
or something like that. Very frustrating.
I really like Gingercruzt, but I'm unable to use it because of that touchscreen bug. I think it's a bug from CM7.2, since the J.A.F's and jusada's ROM also have this problem.
Sent from my GT-S5830
I got this too http://forum.xda-developers.com/showthread.php?t=1271268
I don't have that bug... did you flash the framework for v2.2 before flashing 2.3? maybe this dosn't afect to the touchscreen but just only to see what was your flashing process.
@CambaStorm I already tried flash the framework when in GingerCrust 2.2 (without framework Gingercrust v2.2 didn't have bootloop) with frameworkgcv2.2.zip , but after flashing the framework, I had the bootloop everytime v after that i flash again with Gingercrust v2.3 and i got the touchscreen problem but the bootloop already solved.
@nims11 thanks for the reply, I want to ask some questions to you. Is there additional framework for Gingercrust 2.3 or the framework for 2.2 still valid in 2.3? I mean if I want to upgrade from 2.2 to 2.3, is it required to flash the framework again? or the GC 2.2 that you post in http://forum.xda-developers.com/showthread.php?t=1324628 already have modified framework inside? Thanks nims!! I really want to try the GC v2.3 by the way it's really a very great work of you!!
@adinq yeah I have the same problem in GingerCrust v2.3 just like your video in your thread
acesteady said:
@CambaStorm I already tried flash the framework when in GingerCrust 2.2 (without framework Gingercrust v2.2 didn't have bootloop) with frameworkgcv2.2.zip , but after flashing the framework, I had the bootloop everytime v after that i flash again with Gingercrust v2.3 and i got the touchscreen problem but the bootloop already solved.
@nims11 thanks for the reply, I want to ask some questions to you. Is there additional framework for Gingercrust 2.3 or the framework for 2.2 still valid in 2.3? I mean if I want to upgrade from 2.2 to 2.3, is it required to flash the framework again? or the GC 2.2 that you post in http://forum.xda-developers.com/showthread.php?t=1324628 already have modified framework inside? Thanks nims!! I really want to try the GC v2.3 by the way it's really a very great work of you!!
@adinq yeah I have the same problem in GingerCrust v2.3 just like your video in your thread
Click to expand...
Click to collapse
moded framework allready gave in rom
touchscreen prob of keypad you tell is not happen atall in my phone
Im reply all things from my phone not from pc means not phasing that stuff yet
will try to solve for those phasing in new version
adeklipse said:
I have this problem also.
It's most apparent when typing, because random keys will frequently touch itself, mostly the s and d keys.
For example, I write "I love you", it will turn out as:
"Ids sdldovsed ysdous"
or something like that. Very frustrating.
I really like Gingercruzt, but I'm unable to use it because of that touchscreen bug. I think it's a bug from CM7.2, since the J.A.F's and jusada's ROM also have this problem.
Sent from my GT-S5830
Click to expand...
Click to collapse
thanks for the quick reply nims, just info for you the bug that I found is just exactly the same as adeklipse said
acesteady said:
Hello everyone I have a problem with touchsreen on GingerCrust v2.3,
Firstly I want to say sorry because this question is supposed to be in development thread but, since I still have a less posts in this forum so I have to post it in this thread.
Okay this is the problem
I already succeed to flash the GingerCrust v2.2 via CWM 5.0.2.6
And I found there's no problem with touchscreen and then I did the GingerCrust v2.3
And i've got the touchscreen problem (the touchscreen strongly not accurate and hard to swipe for changing app drawer and desktop page)
I already tried to do touch screen calibration test via *#*#2664#*#* touch screen test
but the code won't work
and I tried to find additional framework on it's official thread(by nims11) but there's none of it.
Did anybody have a problem like me? Is there already a solution for the problem that I found
Click to expand...
Click to collapse
I have exactly the same problem. The cause of his OC kernel is unfortunately in some lucky so forth. I asked about this before but no one knows the solution. The only way that works is throwing a kernel that is nonOC "cm-7.1-kernel-2.6.35.7-perf-CL562111.zip" from this topic. http://forum.xda-developers.com/showthread.php?t=1296905 and the problem is gone.
icemanhi said:
I have exactly the same problem. The cause of his OC kernel is unfortunately in some lucky so forth. I asked about this before but no one knows the solution. The only way that works is throwing a kernel that is nonOC "cm-7.1-kernel-2.6.35.7-perf-CL562111.zip" from this topic. http://forum.xda-developers.com/showthread.php?t=1296905 and the problem is gone.
Click to expand...
Click to collapse
And "#throwinag##"% fthus akernael wdill make it wsorks,h rigsht?
This is the text that I typed without any correctionss
And "throwing" thus kernel will make it work, right?
Sent from my GT-S5830
Sorry for the dopost.
I think I've figured out why the touchscreen is acting up (thanks to icemanhi, I'll be pressing that thanks button when I get on the computer). It does have something to do with the OC kernel, but not specifically because of it.
I underclocked my device to 700MHz, and the problem dissappeared. I OCed it to just above 800, and would start seeing it again. I OCed all the way up to just under 900, and it was very apparent.
So possible solutions are:
1. Underclock to <800MHz (for max clock)
2. Flash ketut's regular, non-OC kernel (link provided by icemanhi).
Sent from my GT-S5830
adeklipse said:
Sorry for the dopost.
I think I've figured out why the touchscreen is acting up (thanks to icemanhi, I'll be pressing that thanks button when I get on the computer). It does have something to do with the OC kernel, but not specifically because of it.
I underclocked my device to 700MHz, and the problem dissappeared. I OCed it to just above 800, and would start seeing it again. I OCed all the way up to just under 900, and it was very apparent.
So possible solutions are:
1. Underclock to <800MHz (for max clock)
2. Flash ketut's regular, non-OC kernel (link provided by icemanhi).
Sent from my GT-S5830
Click to expand...
Click to collapse
I take the 2nd solution..... underclock????? i think flash non-oc kernel is better than that
matur nuhun.......
acesteady said:
I take the 2nd solution..... underclock????? i think flash non-oc kernel is better than that
matur nuhun.......
Click to expand...
Click to collapse
Yep, I went with flashing the non-oc kernel as well. Underclocking will still leave you with the problem.
Sami-sami.
*ane orang Banjar nyasar ke Bandung, gan.
Sent from my GT-S5830
I use 800 MHz on oc kernel and not facing this problem.. maybe I'll try above 800..
1. Underclock to <800MHz (for max clock) THIS SOLVE PROBLEM
2. Flash ketut's regular, non-OC kernel (link provided by icemanhi). THIS NOT
Can somehow fix this without reducing the MHz to 700?
adinq said:
1. Underclock to <800MHz (for max clock) THIS SOLVE PROBLEM
2. Flash ketut's regular, non-OC kernel (link provided by icemanhi). THIS NOT
Can somehow fix this without reducing the MHz to 700?
Click to expand...
Click to collapse
Yes: reduce to 800MHz. Though I still have some problems with that.
Sent from my GT-S5830
I also have the same Problem.
It was all fine with froyo 2.2, when i switched to stock 2.3.3 kpe or 2.3.4 kph this problem occured. It stopped happening with 2.3.3 kpy and its perfectly fine with the 2.3.5 stock firmwares.
My big problem is, i cant use any custom roms, it happens with every single custom rom.
So it's not really a warranty issue when it happens with custom roms. Coz samsung could say it works fine with stcok firmware, 2.3.3 kpy for example.
I really don't know what the cause of the problem is, because my friends galaxy ace doesnt have these problems with the custom roms i tried.
I'm not sure but besides the kernel i kinda think it might be a battery issue, because it happens less frequently when its plugged to the charger.
adeklipse said:
Yes: reduce to 800MHz. Though I still have some problems with that.
Sent from my GT-S5830
Click to expand...
Click to collapse
may be this mod can help you..
http://forum.xda-developers.com/showthread.php?t=1365434
i OCed to 883MHz without problem on touchscreen
matur nuwun
aku wong solo bro...╋╋ム ╋╋ム ╋╋ム =)) ╋╋ム ╋╋ム ╋╋ム
pls press thanks button if you like this.
sorry for my bad english
Hi
i got a vibrant that i installed Cm9 Nightly 04/18/2012 and i want to fix the bug of the gps that if you turn it on and then after a while you disconnect the gps its still drains the battery like the GPS was on.
i heard if you update the kernel to Subzero release 70 it will fix this problem.
my question is : does anyone tried to install Subzero kernel in this cm9 nightly rom and can tell me if there are any bugs with it or lags or anything else i should know that the stock kernel didnt do?
thanks
Lior
batista25 said:
Hi
i got a vibrant that i installed Cm9 Nightly 04/18/2012 and i want to fix the bug of the gps that if you turn it on and then after a while you disconnect the gps its still drains the battery like the GPS was on.
i heard if you update the kernel to Subzero release 70 it will fix this problem.
my question is : does anyone tried to install Subzero kernel in this cm9 nightly rom and can tell me if there are any bugs with it or lags or anything else i should know that the stock kernel didnt do?
thanks
Lior
Click to expand...
Click to collapse
Subzero's kernel is sweet.
Been running it for about a week or two - everything is awesome.
I know this report should rather be posted in the developer forum (http://forum.xda-developers.com/showthread.php?t=1780326), but as I've just registered, I'm not allowed to post there, so I hope you all will excuse me.
I've been testing the latest CyanogenMod 10 version (FXP145) on my Xperia Active (ST17i), tried both the bundled and DDS kernel, but I've been encountering two bugs:
Gallery bug
Right after the ROM starts and I insert my PIN, I get a message: "Unfortunately, Gallery has stopped". Everything then works as expected, no trouble with the gallery or anything else, just this (a bit annoing, but not deadly) message.
WiFi bug
I'm unable to connect to a WPA2-PSK protected network. An unsecured WiFi works well, but WPA2 gets into a loop, where it keeps trying to authenticate and aquite an IP. I tried to change my hostname, tried to change the kernel to DDS, nothing helped. It seems like the same bug that's troubling the stock ICS for Xperia Active, though how it got into the JB is a mystery. In all the custom ICS kernels I tested (with the fixed WLAN modules) it worked well, but the fix is not usable in the JB kernel.
In the DDS kernel thread (http://forum.xda-developers.com/showthread.php?t=1956283) there seemed to be some talking about WiFi trouble since FXP144, but it puzzles me that no one else seemed to notice anyting (might be very isolated bug).
Just wanted to report my findings and see if I'm the only one having these trouble and if there's something to be done about it...
https://code.google.com/p/freexperia/issues/list
Thanks, gotta admit I know about this bug list, I was hoping to get some feedback on the matter before posting it as a bug (because here I know that I'm talking to people with similair phones, in the buglist, my phone and bug will be quite rare).
probably its just you, or everyone else haven't notice it yet. u should do clean install with cm default kernel and try to replicate the bug. if its still there then just do bug report with logcat included on the fxp's googlecode page. that should help fxp to fix the bug (if its a bug).
I have no problem with wpa2 psk I use it everyday with the kernel in the rom zip. May be u can give a try with mesa kernelv2.2 by an0nym0us Im currently using it with no wifi trouble. & if u want the gallery force close to be fixed u can go through it
http://forum.xda-developers.com/showpost.php?p=33806921&postcount=1739
an0nym0us_ said:
probably its just you, or everyone else haven't notice it yet. u should do clean install with cm default kernel and try to replicate the bug. if its still there then just do bug report with logcat included on the fxp's googlecode page. that should help fxp to fix the bug (if its a bug).
Click to expand...
Click to collapse
Thanks, I'll try to replicate it and see what happens.
saqib nazm said:
I have no problem with wpa2 psk I use it everyday with the kernel in the rom zip. May be u can give a try with mesa kernelv2.2 by an0nym0us Im currently using it with no wifi trouble. & if u want the gallery force close to be fixed u can go through it
http://forum.xda-developers.com/showpost.php?p=33806921&postcount=1739
Click to expand...
Click to collapse
Thanks for the tip for the first bug. As for the second one, I thought MESA kernel isn't compatible with CM10? I remember reading in an0nym0us's MESA thread, that CM10 isn't mature enough, so he's not using it and his kernel is not made to be used with it (maybe he'll correct me, if I'm wrong ).
fox-03 said:
Thanks for the tip for the first bug. As for the second one, I thought MESA kernel isn't compatible with CM10? I remember reading in an0nym0us's MESA thread, that CM10 isn't mature enough, so he's not using it and his kernel is not made to be used with it (maybe he'll correct me, if I'm wrong ).
Click to expand...
Click to collapse
No he made a wonderful job & released v2.2. Im using it with fxp 145 cm10. U will get better battery life with better performance with more CPU governor & I/O scheduler try it & if wifi doesnt turn on to system & delete wlanfixed & reboot twice & thank an0nym0us :highfive:
saqib nazm said:
No he made a wonderful job & released v2.2. Im using it with fxp 145 cm10. U will get better battery life with better performance with more CPU governor & I/O scheduler try it & if wifi doesnt turn on to system & delete wlanfixed & reboot twice & thank an0nym0us :highfive:
Click to expand...
Click to collapse
So, I've been experimentating some more during the weekend and: I've tested the WiFI with the following: a clean installation of FXP145 (+its original kernel), FXP146 (and its original kernel) and finally with MESA v2.2 for JB + FXP146, tried to delete wlanfixed and reboot twice. The problem is always the same, WiFi generally works, but doesn't want to connect to my WPA2+AES protected router. There is no MAC filtering or anything like that enabled on the router. Just to be sure I'll try to find the ICS kernel + ROM that used to work and test it again, so I can see there is a working config.
fox-03 said:
I know this report should rather be posted in the developer forum (http://forum.xda-developers.com/showthread.php?t=1780326), but as I've just registered, I'm not allowed to post there, so I hope you all will excuse me.
I've been testing the latest CyanogenMod 10 version (FXP145) on my Xperia Active (ST17i), tried both the bundled and DDS kernel, but I've been encountering two bugs:
Gallery bug
Right after the ROM starts and I insert my PIN, I get a message: "Unfortunately, Gallery has stopped". Everything then works as expected, no trouble with the gallery or anything else, just this (a bit annoing, but not deadly) message.
WiFi bug
I'm unable to connect to a WPA2-PSK protected network. An unsecured WiFi works well, but WPA2 gets into a loop, where it keeps trying to authenticate and aquite an IP. I tried to change my hostname, tried to change the kernel to DDS, nothing helped. It seems like the same bug that's troubling the stock ICS for Xperia Active, though how it got into the JB is a mystery. In all the custom ICS kernels I tested (with the fixed WLAN modules) it worked well, but the fix is not usable in the JB kernel.
In the DDS kernel thread (http://forum.xda-developers.com/showthread.php?t=1956283) there seemed to be some talking about WiFi trouble since FXP144, but it puzzles me that no one else seemed to notice anyting (might be very isolated bug).
Just wanted to report my findings and see if I'm the only one having these trouble and if there's something to be done about it...
Click to expand...
Click to collapse
Alright, after hours of flashing and booting, I need to correct my first statement and appologize for misleading all of you. After testing 4 ICS kernels with various ROMS (stock+stock ROM, Rage v3.2 + HaSa MIUI v2.11.2, Mesa v2.2 + RealICSLite r4, KernelPanic v1.25 + HyperbeamCream v4.0) I can confirm, that WiFi with WPA2+AES security works on none of them (with my Xperia Active). It only works on GB (tested with stock kernel + ROM and also Rage v3 + Hasa v5) .
Looks like I'm stuck with GB, because both ICS and JB Wifi drivers fail to work properly for me :-/.
fox-03 said:
Looks like I'm stuck with GB, because both ICS and JB Wifi drivers fail to work properly for me :-/.
Click to expand...
Click to collapse
I think you would have done it but still, have you tried factory wipe from CWM AFTER flashing the kernel? I've faced this problem sometimes but doing factory wipe after flashing the kernel helped me.
Press thanks if I helped you
Sent from my ST15i using xda app-developers app
gouthamthemostwanted said:
I think you would have done it but still, have you tried factory wipe from CWM AFTER flashing the kernel? I've faced this problem sometimes but doing factory wipe after flashing the kernel helped me.
Press thanks if I helped you
Sent from my ST15i using xda app-developers app
Click to expand...
Click to collapse
What I generally did during the tests was this:
1) Enter CWM and do a full wipe (data, cache, system, dalvik cache)
2) Flash Kernel
3) Flash ROM
4) Test WiFi
5) if the Wifi does not work -> fiddle with the ROM
- delete wlanfixed and reboot twice
- flash some wifi fixes, reboot, test
Though I did follow the instructions written for each kernel and ROM, so sometimes I did the wipes after the kernel flash.