I'll go straight to the problem:
There are 2 rows of pixels, (one below another) that are too sesitive on all ROMs except: CM7.2 by vo-1 WITH zImage kernel and XWKPT WITHOUT cf-root (I'm stuck with these 2, because on any other the thing happens). They very frequently react to touches all over the screen and even touch-buttons.
Why is that happening? Does anyone have a problem like that too? How can I fix it?
Sonic0509 said:
I'll go straight to the problem:
There are 2 rows of pixels, (one below another) that are too sesitive on all ROMs except: CM7.2 by vo-1 WITH zImage kernel and XWKPT WITHOUT cf-root (I'm stuck with these 2, because on any other the thing happens). They very frequently react to touches all over the screen and even touch-buttons.
Why is that happening? Does anyone have a problem like that too? How can I fix it?
Click to expand...
Click to collapse
Yes, that is kernel problem. even i had that problem in ketut's blackhawk and other OC kernel. i flashed ketut's non-oc kernel then the problem was solved. u can try flashing zImage v1.5 or ketut's 7.1 kernel(lenovo). i hope this helps
But would zImage or keut's 7.1 work on stock based ROM?
Sent from my GT-S5830 using XDA
Sonic0509 said:
But would zImage or keut's 7.1 work on stock based ROM?
Sent from my GT-S5830 using XDA
Click to expand...
Click to collapse
Unfortunately no. But I prefer stock kernel when I'm on stock, it's smoother for me (I dont use init.d)
Sent from my GT-S5830 using Tapatalk
Sonic0509 said:
I'll go straight to the problem:
There are 2 rows of pixels, (one below another) that are too sesitive on all ROMs except: CM7.2 by vo-1 WITH zImage kernel and XWKPT WITHOUT cf-root (I'm stuck with these 2, because on any other the thing happens). They very frequently react to touches all over the screen and even touch-buttons.
Why is that happening? Does anyone have a problem like that too? How can I fix it?
Click to expand...
Click to collapse
i am facing the same problem...i too use zImage 1.5 ..it seems to be a bit hardware issue as well...bcz there are very few users facing this type of problem..till now i came across only three of them.
but thnx for mentioning this..
i musing ddkq6 and have same problem..
have the same issue. but reverted back to CF-ROOT B82-EX kernel and no more problems on any ROM. but sometimes(very rarely) i experience less responsive screen.
amrith.28 said:
have the same issue. but reverted back to CF-ROOT B82-EX kernel and no more problems on any ROM. but sometimes(very rarely) i experience less responsive screen.
Click to expand...
Click to collapse
Less responsive screen wouldn't be bad for me and cf-root b82 sounds promising. Thanks for a hint
Sonic0509 said:
I'll go straight to the problem:
There are 2 rows of pixels, (one below another) that are too sesitive on all ROMs except: CM7.2 by vo-1 WITH zImage kernel and XWKPT WITHOUT cf-root (I'm stuck with these 2, because on any other the thing happens). They very frequently react to touches all over the screen and even touch-buttons.
Why is that happening? Does anyone have a problem like that too? How can I fix it?
Click to expand...
Click to collapse
I got the same problem
Same problem for me. I think it's a combination of hardware issue and kernel problem as it's not present on every kernel...
Did all of you bought the Ace at the very begininng when it went out?
I did, and i think that maybe Samsung solved the problem in the older relase of ace...
Sent from my GT-S5830 using xda premium
Yeh im having that problem too on oc kernels...
Darvadouille said:
Same problem for me. I think it's a combination of hardware issue and kernel problem as it's not present on every kernel...
Did all of you bought the Ace at the very begininng when it went out?
I did, and i think that maybe Samsung solved the problem in the older relase of ace...
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
Yep. Just when it came out in Poland.
If there is only small group of us, complaining about it, there is high chance that Samsung really fixed touch sensors in later releases.
Related
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 just noticed a problem that I didn't have before on my SGS2. There is a small "jump" when I touch and drag just a little. It's not as smooth as before.
I'm running the last version of Resurrection Remix. I didn't have that bug on stock ROM (Gingerbread), and I can't remember if I had it on stock ICS update, because I didn't like it and updated to the custom ROM right away.
It's really annoying because I lose a lot of precision (for DrawSomething or Swype keyboard... Because of the "jumps", Swype thinks I type 2 words and I always get something like "E Hello" instead of one single word....
I tried to make the best video I could... It's not very clear but you can still see the jumps on the device on the left.
Does someone know how to fix this?
Same problem on stock ICS.
I forgot to mention that the two devices are running the same Resurrection Remix ROM.
I think the stock vitalij value ( i think that's what its called ) is 15. That means you need to move your fingers 16pixels before the move is recognized. Some custom kernels like siyah can adjust that up to zero and you just need to move it atleast 1pixel until the move is recognized.
Sent from my GT-I9100 using xda premium
I was on Siyah before updating to Rerruction Remix, now I'm on a CM kernel.
Can I flash Siyah again without any problem ?
I've just noticed that the ROM v1.8 (that I flashed) comes with CM9 kernel. I'll just update to v1.9 with Siyah
Yay! Updated to v1.9.1 with Siyah kernel and the problem is solved! ^^
remifr said:
Yay! Updated to v1.9.1 with Siyah kernel and the problem is solved! ^^
Click to expand...
Click to collapse
Congrats dude. Hope i helped and it would mean much if you press the thanks button
Sent from my GT-I9100 using xda premium
Hi brothers, i experience the situation that the proximity sensor of my phone stop working after flashing either CM7 or oxygen rom, and I have tried difference kernels, the problem exists. but my proximity sensor work normally if I flash back the stock rom using kdz.
Anyone experience this before and any solution for solving this bug?
Thanks a lot!
i have the same situation
Push myself
mine works, using CM7.2 RC 3 & roq's kernel 2.6.35.13-XIV
Yes it works.
Mine doesn't work properly.
Using Ginger Snap ROM: neko95 with Roq Kernel IX by: roqu3on my p500. Works perfectly.
Vertejas said:
Using Ginger Snap ROM: neko95 with Roq Kernel IX by: roqu3on my p500. Works perfectly.
Click to expand...
Click to collapse
the proximity sezor problem is GONE with GingerSnap v1.2 (with Roq IX kernel implemented).....cheers
barbuletiu.marius said:
the proximity sezor problem is GONE with GingerSnap v1.2 (with Roq IX kernel implemented).....cheers
Click to expand...
Click to collapse
I have installed gingersnap 1.2 but the bugs exist, would it related to the hardware?
but the sensor work again if I use stock rom...
Thanks!
proximity problem
hoyinboy said:
I have installed gingersnap 1.2 but the bugs exist, would it related to the hardware?
but the sensor work again if I use stock rom...
Thanks!
Click to expand...
Click to collapse
I apologize for rushing, but sensor problem still there. first hours of operation went smoothly but after a back problem. **** happened
Do you format system and boot when you flash a new rom?
And do you wipe dalvik cache when you flash a new kernel?
i have a optimus t running Cyanogenmod 9, Android ICS 4.0.4, CAF Kernel by arjen and my proximity sensor works flawlessly.
Haven't had any proximity sensor issues since day one. I only do full wipes when transferring from one rom to another. Sounds like it's a hardware issue. Could be software but the contents and configuration can change from one user to another. There's too many variables.
Just throwing a suggestion here, but how about performance options? Ever since CM7, I have been setting mine to Interactive/768/245. zRam 10%. kernel samepage on.
I know hep and the other devs are trying to figure it out. I'm just curious as to why it's working for some and not for others.
Solution found
Today I installed DynamiteRomJB from http://forum.xda-developers.com/showthread.php?t=1626281. The problem with the proximity sensor does not exist at all
Never had problems, now i'm on piccolo alpha3.
I think first models have that issue. Mine is quite recent: 10 months.
Maybe a different revision of the proximity sensor hardware?
off topic but do P500 has auto brightness?
No.
Sent from my LG-P500 using xda app-developers app
Hello!
I've recently installed the fxp cm9 ICS firmware port and kernel on my X10. Now, it turns out several games have a bit of a problem with touchscreen commands. For example, after having installed the mobile Rayman game, the buttons on the main menu seem to respond to my touch at first, but don't actually do anything.
Having looked around for this problem, I ultimately found this quote:
"that problem is with your Kernel. There's a problem with the ICS Kernel 4.1.B.0.431 using touch games. You have to upgrade to a Kernel based on 4.1.B.0.587 or a CyanogenMod Kernel."
I'm not that knowledged in the field of android development, but I'm under the impression that the kernel I installed along with the CM9 x10 port is obviously a CM kernel. All kernels currently available on the X10 dev forums here seem to be based on the fxp cm9 kernel port as well. Thus, my question is: has anyone else encountered this problem, is the problem really relevant to the kernel as stated in that quote, and is there anything specific I need to know or do to fix this problem?
Thanks in advance for your help!
Draycken said:
Hello!
I've recently installed the fxp cm9 ICS firmware port and kernel on my X10. Now, it turns out several games have a bit of a problem with touchscreen commands. For example, after having installed the mobile Rayman game, the buttons on the main menu seem to respond to my touch at first, but don't actually do anything.
Having looked around for this problem, I ultimately found this quote:
"that problem is with your Kernel. There's a problem with the ICS Kernel 4.1.B.0.431 using touch games. You have to upgrade to a Kernel based on 4.1.B.0.587 or a CyanogenMod Kernel."
I'm not that knowledged in the field of android development, but I'm under the impression that the kernel I installed along with the CM9 x10 port is obviously a CM kernel. All kernels currently available on the X10 dev forums here seem to be based on the fxp cm9 kernel port as well. Thus, my question is: has anyone else encountered this problem, is the problem really relevant to the kernel as stated in that quote, and is there anything specific I need to know or do to fix this problem?
Thanks in advance for your help!
Click to expand...
Click to collapse
Same rom with version 5.1 kernel with same problem. The games seem to work when you first load them but doesn't last long until it stops recognizing the touch screen.
dgoby said:
Same rom with version 5.1 kernel with same problem. The games seem to work when you first load them but doesn't last long until it stops recognizing the touch screen.
Click to expand...
Click to collapse
So what you mean, the game doesn't responding anymore even when u touch menu it didnt exit so have to force restart?
Sent from my GT-I8150 using xda app-developers app
Oyongx said:
So what you mean, the game doesn't responding anymore even when u touch menu it didnt exit so have to force restart?
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
It it's the same problem I have, here's an example: you get into angry birds, select your level, fire about once or twice with slingshot and then no response from the screen. Back, menu and home buttons work but not the screen.
Yeah, I hadn't tried angry birds yet after having installed the new firmware, but I just gave one of the games a testrun and I can't even get in-game, main menu is completely unresponsive.
But no, there's no freezing or anything, I can just leave the game with my hard buttons, it's only the touchscreen in-game that's being unresponsive.
Not all games either since there's plenty of stuff that still works though.
dgoby said:
It it's the same problem I have, here's an example: you get into angry birds, select your level, fire about once or twice with slingshot and then no response from the screen. Back, menu and home buttons work but not the screen.
Click to expand...
Click to collapse
I see.. that must be kernel problem. Im using cm9 galaxy w but no such issue.. have u tried other kernel?
Sent from my GT-I8150 using xda app-developers app
I'm not sure but I thought the other kernels for ICS for X10 were all based on the FXP CM9 port... Please correct me if I'm mistaken.
Hey, a very noob question, but does flashing just another kernel, and not flashing a whole new firmware, also result in all your data being lost? If not, I could just try a few different kernels out without having to take a new backup.
Draycken said:
I'm not sure but I thought the other kernels for ICS for X10 were all based on the FXP CM9 port... Please correct me if I'm mistaken.
Hey, a very noob question, but does flashing just another kernel, and not flashing a whole new firmware, also result in all your data being lost? If not, I could just try a few different kernels out without having to take a new backup.
Click to expand...
Click to collapse
Nope. But for just in case, do a full backup using cwm recovery. A backup is a must when you do such thing.. As long as you read ics kernel for your x10 not other device maybe everything will be okay. Get what i mean? (Bad english )
Sent from my GT-I8150 using xda app-developers app
Oyongx said:
I see.. that must be kernel problem. Im using cm9 galaxy w but no such issue.. have u tried other kernel?
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
Not yet but I was looking to try Amin for CM9, unless you have another suggestion for Fera V4 ICS.
Edit: Amin Kernel didn't even allow the phone to boot, next
Draycken said:
I'm not sure but I thought the other kernels for ICS for X10 were all based on the FXP CM9 port... Please correct me if I'm mistaken.
Hey, a very noob question, but does flashing just another kernel, and not flashing a whole new firmware, also result in all your data being lost? If not, I could just try a few different kernels out without having to take a new backup.
Click to expand...
Click to collapse
The kernel has ntn to do with ur apps n data. It is the basic link between ur hardware and ur os. It has the libraries and drivers etc. So ur data won't be lost
Sent from my Xperia X10 using xda app-developers app
---------- Post added at 11:11 AM ---------- Previous post was at 11:08 AM ----------
dgoby said:
Not yet but I was looking to try Amin for CM9, unless you have another suggestion for Fera V4 ICS.
Edit: Amin Kernel didn't even allow the phone to boot, next
Click to expand...
Click to collapse
I'm using feralab v4 ROM with kernel v5.1.. I don't hv ne such issues. I didn't hv these issues on ne cm based kernel for that matter.
Sent from my Xperia X10 using xda app-developers app
I have a problem with my x10 mini pro for almost a year .. I don't know when it exactly has started ... when I'm working with my phone suddenly screen goes crazy and divides into 2 part...touch is steel working ...I have to turn off my phone or put battery out to make it right even for 2,3 times...I've installed different ROMs but the problem happens every time after 1,2 days working...(I've unblocked my bootloader longs tome ago)
I need SE ORIGINAL ROM link to test...
any other ideas?
pingulii said:
I have a problem with my x10 mini pro for almost a year .. I don't know when it exactly has started ... when I'm working with my phone suddenly screen goes crazy and divides into 2 part...touch is steel working ...I have to turn off my phone or put battery out to make it right even for 2,3 times...I've installed different ROMs but the problem happens every time after 1,2 days working...(I've unblocked my bootloader longs tome ago)
I need SE ORIGINAL ROM link to test...
any other ideas?
Click to expand...
Click to collapse
Your flex (the cable that connects the screen to the rest of your phone ) may be damaged or broken, it's the most common cause of this kind of behaviour.
SmG67 said:
Your flex (the cable that connects the screen to the rest of your phone ) may be damaged or broken, it's the most common cause of this kind of behaviour.
Click to expand...
Click to collapse
is it expensive?
pingulii said:
is it expensive?
Click to expand...
Click to collapse
Depends on where you live and if you can replace it yourself, I found one for about 10euros in an online shop.
I think I know your answer !
In my opinion, I think it's nAa kernel's bug. (If you're using it)
Simply update kernel or change to another like alfs kernel.
-I had the same problem(touch screen operates fine but screen out-put goes wild) , reflashing kernel solved my screen issue
sent via ULTIMATE GB beta
jay-z-s said:
I think I know your answer !
In my opinion, I think it's nAa kernel's bug. (If you're using it)
Simply update kernel or change to another like alfs kernel.
-I had the same problem(touch screen operates fine but screen out-put goes wild) , reflashing kernel solved my screen issue
sent via ULTIMATE GB beta
Click to expand...
Click to collapse
can u provide the link for alfs kernel ?
Sent from my U20i using Tapatalk 2
jay-z-s said:
I think I know your answer !
In my opinion, I think it's nAa kernel's bug. (If you're using it)
Simply update kernel or change to another like alfs kernel.
-I had the same problem(touch screen operates fine but screen out-put goes wild) , reflashing kernel solved my screen issue
sent via ULTIMATE GB beta
Click to expand...
Click to collapse
yes I've used nAa kernel !! last night I flashed the Original ROM android 1.6 ...and then with update service updated it to android 2.1
is it necessary to change my kernel now? I don't know whether my kernel is nAa or is it the stock kernel now ....
in my phone(about phone) its written :
2.6.29
SEMC user...
pingulii said:
yes I've used nAa kernel !! last night I flashed the Original ROM android 1.6 ...and then with update service updated it to android 2.1
is it necessary to change my kernel now? I don't know whether my kernel is nAa or is it the stock kernel now ....
in my phone(about phone) its written :
2.6.29
SEMC user...
Click to expand...
Click to collapse
You've got stock kernel now, If you still have the problems, it's not a kernel-fault. And I don't think our phones have the alfs-kernel available, i think that that was only cooked for the x8 or x10 (big one).
SmG67 said:
You've got stock kernel now, If you still have the problems, it's not a kernel-fault. And I don't think our phones have the alfs-kernel available, i think that that was only cooked for the x8 or x10 (big one).
Click to expand...
Click to collapse
Since I've changed my ROM into original , it didn't happen again....
pingulii said:
Since I've changed my ROM into original , it didn't happen again....
Click to expand...
Click to collapse
So it's perfect
If this happened again just reflash stock 2.1 rom
Or reflash your custom kernel (if you are using one)
sent via ULTIMATE GB beta
---------- Post added at 11:43 PM ---------- Previous post was at 11:41 PM ----------
SmG67 said:
You've got stock kernel now, If you still have the problems, it's not a kernel-fault. And I don't think our phones have the alfs-kernel available, i think that that was only cooked for the x8 or x10 (big one).
Click to expand...
Click to collapse
I've experienced this on my X8 on a rom built on pure cyanogen (ios themed)
So it's caused by kernel
sent via ULTIMATE GB beta
jay-z-s said:
So it's perfect
If this happened again just reflash stock 2.1 rom
Or reflash your custom kernel (if you are using one)
sent via ULTIMATE GB beta
---------- Post added at 11:43 PM ---------- Previous post was at 11:41 PM ----------
I've experienced this on my X8 on a rom built on pure cyanogen (ios themed)
So it's caused by kernel
sent via ULTIMATE GB beta
Click to expand...
Click to collapse
Rawwr said:
never
ever slide open the phone when the screen is locked
ur flex cable will get damaged and ur display will be in 2 partition
Sent from my U20i using Tapatalk 2
Click to expand...
Click to collapse
It`s true. Firstly my proxymity sensor stoped working. After that display was in 2 partions. Status-bar was at the bottom of the screen. Also my phone was unable to boot. It was always rebooting at the start. after disassembly i saw broken flex cable. now i am waiting for replacement parts. It is not a bug of nAa kernel !!! I tried both stock and custom rom!
if you happen to use an X10 mini pro then this is your problem. I already posted it on my thread here. http://forum.xda-developers.com/showthread.php?t=1935124
but if you are using an x10 mini then I can't answer you about your prob. but please read the thread and spread the word.