The AOD shows when the phone is locked and disappears when I cover the proximity sensor, but in direct sunlight the brightness wont increase as before, it stays the same, please help
Im on Fulmics Rom 3.3 with Asgard kernel 5.7
Same here..waiting official fix..
sad_but_cool1 said:
Same here..waiting official fix..
Click to expand...
Click to collapse
Somehow for me its working now, I was changing governors and loaded a profile in ex kernel manager, maybe by changing that fixed the problem, dont know :S
Related
I have cyano ace rom with ketut kernel for cm7...
I installed this bln-pro v15.70...static lights and blinking lights are not working.
It will only work if it is in charging mode.
I have tried all possible solutions but NOT WORKING.
ANY possible solutions about bln?
same problem here
Not the perfect solution but im using kang's version and the BLN works pretty well. Dont know if it is BLN that causes this but sometimes my backlight doesnt turn off.
QNBT said:
Not the perfect solution but im using kang's version and the BLN works pretty well. Dont know if it is BLN that causes this but sometimes my backlight doesnt turn off.
Click to expand...
Click to collapse
That is a known issue right?? I don't think that BLN functions properly..
internet prob.
hi . i flashed cyano ace. it awesome. but i cant connect internet with my docomo india.
i set up access point, as always it worked before. but in this rom i cant use it.
also there is no market in it. n it so market app installer closed unexpectedly.
help me plz. i want internet n market working in this ROM badly. plz plz
kush3495 said:
hi . i flashed cyano ace. it awesome. but i cant connect internet with my docomo india.
i set up access point, as always it worked before. but in this rom i cant use it.
also there is no market in it. n it so market app installer closed unexpectedly.
help me plz. i want internet n market working in this ROM badly. plz plz
Click to expand...
Click to collapse
In APN settings keep APN type blank.. and for the Market go through the comments in CyanoAce thread..
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
When i press *#0*#, proximity value is change but when i call LCD screen wont to turn off.
In settings i thick turn the prox. sensor!
I try few stock roms, but nothing
Is there something like drivers to put with root explorer?
Please help
Hello,
I have exactly the same problem...
When I do a proximity test in *#0*# my proximity sensor turns on (goes red) and works perfectly.
But when I do a call it doesn't work... Not even turns on.
Is there any settings to enable it or is it related to something different?
Tried 3 stock roms but they all had the same results...
Thanks
Have you tried flashing CM7 or if your not on the latest Samsung rom, updating to that
If I have helped you, please feel free to press the thanks button below
danielsf said:
Have you tried flashing CM7 or if your not on the latest Samsung rom, updating to that
If I have helped you, please feel free to press the thanks button below
Click to expand...
Click to collapse
Nope I haven't tried CM7. And I want to stick with the stock rom
But my rom is I think one of the latest official roms. I got it today from here. It is DXKL3.
Armenium said:
Nope I haven't tried CM7. And I want to stick with the stock rom
But my rom is I think one of the latest official roms. I got it today from here. It is DXKL3.
Click to expand...
Click to collapse
my stock rom is xxki3, do you solve your problem Armenium?
danielsf said:
Have you tried flashing CM7 or if your not on the latest Samsung rom, updating to that
If I have helped you, please feel free to press the thanks button below
Click to expand...
Click to collapse
do you have the same problem please help!
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
got a mega, but not global model,
my phoen is SHV-E310K..
flashed cm11
everything works good, but LED is on, and would't off, anytime..
and camera focus isn't working..
maybe 310k's kernel issue..
someone help how to rebuild kernel.. for fixing hw parameter...
asksays said:
got a mega, but not global model,
my phoen is SHV-E310K..
flashed cm11
everything works good, but LED is on, and would't off, anytime..
and camera focus isn't working..
maybe 310k's kernel issue..
someone help how to rebuild kernel.. for fixing hw parameter...
Click to expand...
Click to collapse
Why don't you ask first at the CM11 thread for solution to your problem? Rebuilding kernel is not easy and may even result in a complete brick for your mega.