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
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
Hi.
I need some help with this ROM (http://forum.xda-developers.com/showthread.php?t=1846760) because when I install it with the normal kernel I have problems with the WiFi and so, as it is written in the thread, I flash the kernel that fixes the problems, the only problem is that the ROM becomes very unstable.
So, with the normal kernel the ROM is fast and stable, but has the WiFi problem. With the kernel that fixes the WiFi the WiFi works just fine but the ROM becomes very unstable and is always rebooting.
Can you suggest me another kernel or another ROM. I like this one because it is very clean and fast.
Thanks for your attetion.:good:
Happy Holidays.
PS: sorry about my English, I am Portuguese
J.Diogo said:
Hi.
I need some help with this ROM (http://forum.xda-developers.com/showthread.php?t=1846760) because when I install it with the normal kernel I have problems with the WiFi and so, as it is written in the thread, I flash the kernel that fixes the problems, the only problem is that the ROM becomes very unstable.
So, with the normal kernel the ROM is fast and stable, but has the WiFi problem. With the kernel that fixes the WiFi the WiFi works just fine but the ROM becomes very unstable and is always rebooting.
Can you suggest me another kernel or another ROM. I like this one because it is very clean and fast.
Thanks for your attetion.:good:
Happy Holidays.
PS: sorry about my English, I am Portuguese
Click to expand...
Click to collapse
Search for feralab's ROMs.. he has many versions of GB and also an ICS ROM.. GB ones have everything working.. his latest GB kernel is like booster juice for x10
Sent from my Xperia X10 using xda app-developers app
J.Diogo said:
Hi.
I need some help with this ROM (http://forum.xda-developers.com/showthread.php?t=1846760) because when I install it with the normal kernel I have problems with the WiFi and so, as it is written in the thread, I flash the kernel that fixes the problems, the only problem is that the ROM becomes very unstable.
So, with the normal kernel the ROM is fast and stable, but has the WiFi problem. With the kernel that fixes the WiFi the WiFi works just fine but the ROM becomes very unstable and is always rebooting.
Can you suggest me another kernel or another ROM. I like this one because it is very clean and fast.
Thanks for your attetion.:good:
Happy Holidays.
PS: sorry about my English, I am Portuguese
Click to expand...
Click to collapse
On the "normal kernel" you might haven't flash its wifi module.
On the fixed kernel, the kernel may not suitable with the rom.
Try fera kernel. Dont forget to load its wifi module
Sent from my SO-01C using xda app-developers app
AdX9170 said:
Search for feralab's ROMs.. he has many versions of GB and also an ICS ROM.. GB ones have everything working.. his latest GB kernel is like booster juice for x10
Sent from my Xperia X10 using xda app-developers app
Click to expand...
Click to collapse
Still active here, eh ?
Shaaan said:
Still active here, eh ?
Click to expand...
Click to collapse
Yea I will be even after I get new phone anyways.. wrong to post this stuff here
Sent from my Xperia X10 using xda app-developers app
I got this problem since flash fluorescent rom, i think it's not because the rom and the kernel since i have flashed many roms and kernels.
so, my problem is my battery indicator get stucked at 100%, and suddenly 0% and my phone turn off. if i charge, it shows 100%.
i have flashed stock rom, clear battery status via cwm and the problem still there.
how to fix it? i frustrated
coconut.
thanks
TeranG__ said:
I got this problem since flash fluorescent rom, i think it's not because the rom and the kernel since i have flashed many roms and kernels.
so, my problem is my battery indicator get stucked at 100%, and suddenly 0% and my phone turn off. if i charge, it shows 100%.
i have flashed stock rom, clear battery status via cwm and the problem still there.
how to fix it? i frustrated
coconut.
thanks
Click to expand...
Click to collapse
same here
that's was happento me yesterday whan i back to zelly rom 4 from pac rom
flashed stock rom, clear battery status via cwm change kernel too kappa1.6 and kappa 1.4 and the problem still there
anyone can help us
TeranG__ said:
I got this problem since flash fluorescent rom, i think it's not because the rom and the kernel since i have flashed many roms and kernels.
so, my problem is my battery indicator get stucked at 100%, and suddenly 0% and my phone turn off. if i charge, it shows 100%.
i have flashed stock rom, clear battery status via cwm and the problem still there.
how to fix it? i frustrated
coconut.
thanks
Click to expand...
Click to collapse
abu gaber said:
same here
that's was happento me yesterday whan i back to zelly rom 4 from pac rom
flashed stock rom, clear battery status via cwm change kernel too kappa1.6 and kappa 1.4 and the problem still there
anyone can help us
Click to expand...
Click to collapse
hope your problem resolved.
did you check stat_sys_battery on framework-res.apk\res\drawable-mdpi ?
maybe it have something wrong
hurriX8 said:
hope your problem resolved.
did you check stat_sys_battery on framework-res.apk\res\drawable-mdpi ?
maybe it have something wrong
Click to expand...
Click to collapse
The problem was solved
Thank you for your try to help
and sorry for my bad english
---------- Post added at 02:05 AM ---------- Previous post was at 01:51 AM ----------
TeranG__ said:
I got this problem since flash fluorescent rom, i think it's not because the rom and the kernel since i have flashed many roms and kernels.
so, my problem is my battery indicator get stucked at 100%, and suddenly 0% and my phone turn off. if i charge, it shows 100%.
i have flashed stock rom, clear battery status via cwm and the problem still there.
how to fix it? i frustrated
coconut.
thanks
Click to expand...
Click to collapse
ok man ,
The problem was solved
i flashed pac rom 24-7-2013
and my battery 85 % now . and i'm going to flash zellycream rom again
you can try to flash pac rom or LegacyXperia and see what is going on
sorry for my bad english
...
this problem seems kernel related.. simply use other kernel than kappa for this and other stock roms if u getting int this problem...
abu gaber said:
ok man ,
The problem was solved
i flashed pac rom 24-7-2013
and my battery 85 % now . and i'm going to flash zellycream rom again
you can try to flash pac rom or LegacyXperia and see what is going on
sorry for my bad english
Click to expand...
Click to collapse
it works!! thanks. i flashed newest legacy experia and the problem gone
bejunk said:
this problem seems kernel related.. simply use other kernel than kappa for this and other stock roms if u getting int this problem...
Click to expand...
Click to collapse
I also faced this problem after flashing nAl's kernel on my coconut but if i flash stock kernel, it shows 100% but if i use any other kernel, then yhe battery indicator is working fine. seems i can't go back to stock kernel. Tried SEUS flashing but dosen't worked for me, please suggest me what should i do to get my battery icon working on stock ROM and kernel
shivamcheat said:
I also faced this problem after flashing nAl's kernel on my coconut but if i flash stock kernel, it shows 100% but if i use any other kernel, then yhe battery indicator is working fine. seems i can't go back to stock kernel. Tried SEUS flashing but dosen't worked for me, please suggest me what should i do to get my battery icon working on stock ROM and kernel
Click to expand...
Click to collapse
hmm this is really strange man :silly:
did u wipe batery stats (after flashin stock kernel) or may try a tool like battery calibrator from market (sry for question if u already do it..)
also how u flashed back using seus?? did u reflashed rom + kernel in repair mode??? --> i allways recommend this guide/flashtool method http://talk.sonymobile.com/thread/35239?tstart=0 if u have to get on stock rom + kernel.... just follow it but may u wipe battery stats bfore u do this (on custom kernl) then power off (dont boot) now if stock kernel is flashed it will make a new batterystats.bin...
hope u getting it to work
peace
bejunk said:
hmm this is really strange man :silly:
did u wipe batery stats (after flashin stock kernel) or may try a tool like battery calibrator from market (sry for question if u already do it..)
also how u flashed back using seus?? did u reflashed rom + kernel in repair mode??? --> i allways recommend this guide/flashtool method http://talk.sonymobile.com/thread/35239?tstart=0 if u have to get on stock rom + kernel.... just follow it but may u wipe battery stats bfore u do this (on custom kernl) then power off (dont boot) now if stock kernel is flashed it will make a new batterystats.bin...
hope u getting it to work
peace
Click to expand...
Click to collapse
Thanks for reply but I used flashtool too and followed what you said earlier wiped battery stats using custom kernel's recovery then flashed stock FTF using flashtool but then also it shows 100 %.All custom kernels of jellybean and ics are working fine but not the stock kernel.
shivamcheat said:
Thanks for reply but I used flashtool too and followed what you said earlier wiped battery stats using custom kernel's recovery then flashed stock FTF using flashtool but then also it shows 100 %.All custom kernels of jellybean and ics are working fine but not the stock kernel.
Click to expand...
Click to collapse
Wiping battery stats and flashing stock kernel worked for me this time thanks bejunk
Check the link..it might help..
TeranG__ said:
I got this problem since flash fluorescent rom, i think it's not because the rom and the kernel since i have flashed many roms and kernels.
so, my problem is my battery indicator get stucked at 100%, and suddenly 0% and my phone turn off. if i charge, it shows 100%.
i have flashed stock rom, clear battery status via cwm and the problem still there.
how to fix it? i frustrated
coconut.
thanks
Click to expand...
Click to collapse
Check this post of mine even i had the same prob on kappa kernel and optimax ROM..
http://forum.xda-developers.com/showpost.php?p=44840177&postcount=1125
Hope i helped you..
Regards..
a|\|droid_user said:
Check this post of mine even i had the same prob on kappa kernel and optimax ROM..
http://forum.xda-developers.com/showpost.php?p=44840177&postcount=1125
Hope i helped you..
Regards..
Click to expand...
Click to collapse
hey bro i see ur very xperienced in kappa-related stuffs , so would like to ask a question :
can u tell me a soultion for removing/decreasing buttonbacklight?? i tried so mnay things i even cant remember i used apps, scripts, edited hwconfig as well as prehwconig etc etc.... NOTHING WORKED
for me ics is only usable with this kernel but thsi buttonbacklite is so annoying it blends me and nights its brighter than screen
but i want to use it!!!
so i would really appreciete if u can give me a solution, thx in advance.
Give me some time i will get back to you..
bejunk said:
hey bro i see ur very xperienced in kappa-related stuffs , so would like to ask a question :
can u tell me a soultion for removing/decreasing buttonbacklight?? i tried so mnay things i even cant remember i used apps, scripts, edited hwconfig as well as prehwconig etc etc.... NOTHING WORKED
for me ics is only usable with this kernel but thsi buttonbacklite is so annoying it blends me and nights its brighter than screen
but i want to use it!!!
so i would really appreciete if u can give me a solution, thx in advance.
Click to expand...
Click to collapse
Alright give me some time i will get back to you bro...
Do remember that i m not a proper developer..i will try my best
EDIT:Hold on i think i found something..see if this helps you..
http://forum.xda-developers.com/showpost.php?p=41120591&postcount=749
a|\|droid_user said:
Alright give me some time i will get back to you bro...
Do remember that i m not a proper developer..i will try my best
EDIT:Hold on i think i found something..see if this helps you..
http://forum.xda-developers.com/showpost.php?p=41120591&postcount=749
Click to expand...
Click to collapse
yes bro, dont be hurry take ur time at now using 4.2.2 anyway, only asked bcuz until now no working solution found even on kernel thread, nobody replied (bcuz then also dunno) but thank u very much that u looked into it :angel: if u found sth in future tell me pls, thank u!
but for now may disappoint u but link solution not workin' (tested) its same string as for method with initd script... but i know u wanted only help so i appreciete it
thanks anyway! peace
bejunk said:
yes bro, dont be hurry take ur time at now using 4.2.2 anyway, only asked bcuz until now no working solution found even on kernel thread, nobody replied (bcuz then also dunno) but thank u very much that u looked into it :angel: if u found sth in future tell me pls, thank u!
but for now may disappoint u but link solution not workin' (tested) its same string as for method with initd script... but i know u wanted only help so i appreciete it
thanks anyway! peace
Click to expand...
Click to collapse
Ok bro.. i will get back to you..
Regards..
Hi, just remove the battery 15s and replace it. for me that solve the problem...
Sony Ericsson X;eria Arc
hurriX8 said:
hope your problem resolved.
did you check stat_sys_battery on framework-res.apk\res\drawable-mdpi ?
maybe it have something wrong
Click to expand...
Click to collapse
Dear All,
I am also facing the same issue from yesterday, where my battery is stuck to 100% and not reducing its % level.
I have tried to repair the phone by PC companion, as suggested by Customer service of Sony Ericsson, However the problem is still not resolved.
I would appriciate if some one can please help me to resolve the issue.
Regards,
Vishal Bhatt
TeranG__ said:
I got this problem since flash fluorescent rom, i think it's not because the rom and the kernel since i have flashed many roms and kernels.
so, my problem is my battery indicator get stucked at 100%, and suddenly 0% and my phone turn off. if i charge, it shows 100%.
i have flashed stock rom, clear battery status via cwm and the problem still there.
how to fix it? i frustrated
coconut.
thanks
Click to expand...
Click to collapse
change kernel you may revert back after some time
Hello there
Here is the the CM11 made for X10
Still be in alpha 1 as not everything's working
Nearly same bugs as Evervolv 4.4.2 as bugs are due to kernel
Recovery access is working, sdcard mount only in recovery .
To download the ftf file it's here
To enter recovery mod :
wait the 2nd vibration
tap the screen
Don't forget to check "no final verification" in flashtool
Sources are available here on github
Only for unlocked bootloader device
First boot can be long, but cpu frequency is 998 so no problem with oc
Credits : CM Team, FXP for initial repo (tell me if I forgot someone
Good job.
"Envoyé depuis mon C6903 avec Tapatalk"
Tof37, you're the best!
Thanks How about 2.6 kernel? It will act better definetly.. Wish to see what kitkat could realy do on x10..
Thanks a lot
FeraVolt said:
Thanks How about 2.6 kernel? It will act better definetly.. Wish to see what kitkat could realy do on x10..
Thanks a lot
Click to expand...
Click to collapse
Building with an "old good" 2.6.29 for now ... if it's ok it'll be the v1 for cm11 and evervolv's rom
:fingers-crossed:
@FeraVolt
I need your egl files !!! would you send me them please ? I can't remember where they are not good to be old...
EDIT : Found them ... rom is booting but no display ; see log
Tof37 said:
Building with an "old good" 2.6.29 for now ... if it's ok it'll be the v1 for cm11 and evervolv's rom
:fingers-crossed:
@FeraVolt
I need your egl files !!! would you send me them please ? I can't remember where they are not good to be old...
EDIT : Found them ... rom is booting but no display ; see log
Click to expand...
Click to collapse
as you can see the SurfaceFlinger is the problem ..
W/SurfaceFlinger( 1182): getting VSYNC period from fb HAL: 6535947
W/SurfaceFlinger( 1182): no suitable EGLConfig found, trying a simpler query
F/SurfaceFlinger( 1182): no suitable EGLConfig found, giving up
F/libc ( 1182): Fatal signal 6 (SIGABRT) at 0x0000049e (code=-6), thread 1182 (surfaceflinger)
chack your sources..
Tof37 said:
Building with an "old good" 2.6.29 for now ... if it's ok it'll be the v1 for cm11 and evervolv's rom
:fingers-crossed:
@FeraVolt
I need your egl files !!! would you send me them please ? I can't remember where they are not good to be old...
EDIT : Found them ... rom is booting but no display ; see log
Click to expand...
Click to collapse
Thanks dude.. I know my kernel boots but without display.. I said that graphical part needed to be updated to work on 4.x roms since current kernel setup is very "mutant" (GB KGSL - new FB - Tripple Buffering - 32bpp & many many more things..). You may just try to replace whole KGSL and Video/MSM folders with board config & misc updates from scritch v21 kernel.. we will loose 32bpp.. but i think it will be enough... one more thing.. I didn't updated msm_mdp.h it's old. because new verion starves double more PMEM than default and returns black & white camera.. so my video folder is tuned that way.. So i believe it's totally kernel fault.. BUT this setup works perfectly on GB. Maybe you realy can bypass/modify current surfaceflinger.. since current kernel setup is that what i realy want to see in 4.x roms.. I belive that there we will have HW video recording working super fine..
Also I wish to advice you LegacyXperia CM11 sources.. This project is created to be close as much as possible to original CM11 development but is optimized for legacy xperia devices (2011)(things like default browser..torch..data..etc).. Thank you very much...
Boots without problems.
Attached the following dmesg log.
If there's something you're looking for in specific let us know.
Thank you for your ongoing hard work.
Finally got sdcard mount and ums working... will update device tree later .
Got boot with an "old" 2.6.29 kernel.
Have to fix wifi and bt now....
Sent from my XT890 using xda app-developers app
Maybe this is just me, or does anyone also have their sdcard almost wiped out while using this ROM? I'm not sure what caused it, but all that I know is that a lot of my files are missing ever since I booted into this ROM. I remember wiping the data with the recovery from this kernel, but again, I am not sure if that is the cause of it. If not, it might be something else that I did before that, that is why I need to know if anyone else experienced the same thing as me.
I'm not expecting anything from a pre-alpha build, but the fact that it boots and we have a hope alone fascinates me.
Hzu said:
Maybe this is just me, or does anyone also have their sdcard almost wiped out while using this ROM? I'm not sure what caused it, but all that I know is that a lot of my files are missing ever since I booted into this ROM. I remember wiping the data with the recovery from this kernel, but again, I am not sure if that is the cause of it. If not, it might be something else that I did before that, that is why I need to know if anyone else experienced the same thing as me.
I'm not expecting anything from a pre-alpha build, but the fact that it boots and we have a hope alone fascinates me.
Click to expand...
Click to collapse
Strange issue ... didn't noticed that ...
As sdcard was only recognised and mounted in recovery + you may have app installed on your sd, wiping data should be the cause.
Can't be rom installation cause sd is not mounted / recognized in user land.
As Hzu asked, did someone else had this issue ?
Tof37 said:
As Hzu asked, did someone else had this issue ?
Click to expand...
Click to collapse
No it must have been something in his phone, i did not have any problems, rom buted fine, and when i returned to feras v37 everything was ok.
Tof37 said:
As Hzu asked, did someone else had this issue ?
Click to expand...
Click to collapse
I also do not have any problem with this ROM. Some thing is wrong with him..................................
Kornelije23 said:
No it must have been something in his phone, i did not have any problems, rom booted fine, and when I returned to feras v37 everything was ok.
Click to expand...
Click to collapse
Same here, but I returned to Tof37 GB 2.3 X10S v9 ROM
CWM recovery and all fine.
Dr Goodvibes said:
Same here, but I returned to Tof37 GB 2.3 X10S v9 ROM
CWM recovery and all fine.
Click to expand...
Click to collapse
How good is that room compaired to feras v37, i have tried x10s v9 a long time ago, so is it worth trying it again ?
Tof37 said:
Strange issue ... didn't noticed that ...
As sdcard was only recognised and mounted in recovery + you may have app installed on your sd, wiping data should be the cause.
Can't be rom installation cause sd is not mounted / recognized in user land.
As Hzu asked, did someone else had this issue ?
Click to expand...
Click to collapse
Kornelije23 said:
No it must have been something in his phone, i did not have any problems, rom buted fine, and when i returned to feras v37 everything was ok.
Click to expand...
Click to collapse
kamalyaadav said:
I also do not have any problem with this ROM. Some thing is wrong with him..................................
Click to expand...
Click to collapse
Dr Goodvibes said:
Same here, but I returned to Tof37 GB 2.3 X10S v9 ROM
CWM recovery and all fine.
Click to expand...
Click to collapse
I see, thank you for your responses. Something must have happened before I flashed the ROM. Well, a lot of things happened, but I'm glad it's not this ROM that caused it.
Kornelije23 said:
How good is that room compaired to feras v37, i have tried x10s v9 a long time ago, so is it worth trying it again ?
Click to expand...
Click to collapse
um since this alpha alot of things dont work like the wifi/camera/audio/bluetooth/many applications.......and as such is not suited for daily use but its snappy and for a alpha is quite stable .
Any progress bro ????????
or we should forget about this rom, because this is too much wait.
Can someone tell what work/doesn't work, wifi work?
Adigo18 said:
Can someone tell what work/doesn't work, wifi work?
Click to expand...
Click to collapse
Well ...
As wrote in op the rom boots, calls sms mms seem to work but wifi not ...
No camera and many other things don't work.
Since may didn't made any progress with kernel / kitkat based rom due to personnal reasons.
However, this project is not stopped, just can't when I'll be able to do work on it ... sorry