hey guys i just flash the latest build(13/10) cm10.1(teamcanjica) i got a problem where sometimes i can't wake up my phone but with only lighted up black screen and softkey backlight but sometimes it can wake up but the moment i off my phone then on it, i only got lighted up black screen and softkey backlight, to solve this problem i had to press home or on and off button several times then it'll wake up, if it won't wake up i have to reboot it then set the screen timeout to 30 minutes
i'm sure this is not this build problem but my phone problem,i already wipe data,cache and dalvik cache but still doesn't solve the problem.I even download the build again and tried to flash it with wipe data,cache and dalvik cache but still the same.i hope you guys help me because this is really important to me:crying:
Does it occur on 17/10 release too? Does it also occur when receiving a phone call perhaps?
Sent from my GT-I8160 using xda app-developers app
ledjo said:
Does it occur on 17/10 release too? Does it also occur when receiving a phone call perhaps?
Sent from my GT-I8160 using xda app-developers app
Click to expand...
Click to collapse
yes it occur on 17/10 also occur on previous build except 8/10 and no it doesn't occur during phone call. i even go back to stock jb and flash the latest build again but still doesn't solve the problem..
this happens to me too on a once a day basis, so its pretty rare TBH. what i dont understand is why many other users dont experience this
i just put it to sleep again and wait around 10 seconds.. thatll usually do the trick, and i also confirm it doesnt happen during a call
littledude072 said:
this happens to me too on a once a day basis, so its pretty rare TBH. what i dont understand is why many other users dont experience this
i just put it to sleep again and wait around 10 seconds.. thatll usually do the trick, and i also confirm it doesnt happen during a call
Click to expand...
Click to collapse
i thought i'm only the one who having this problem,i'm having this problem also on cm10.2 by teamcanjica but not cm10.2 by ekim.tecul on the general section(which i'm still using it)but then i having again this problem after flashed polishvodka fix for this rom
but i think i know what's the problem? i think its because of the kernel on ekim.tecul's CM use rootbox kernel and teamcanjica's use cm stock kernel. Of course this just a guess, and i'm a noob and know nothing about rom development
Can you tell me which screen driver do you have ? /sys/devices and tell me if you see s6d... Or ws2401 folder
Sent from my GT-I8160
Rox said:
Can you tell me which screen driver do you have ? /sys/devices and tell me if you see s6d... Or ws2401 folder
Sent from my GT-I8160
Click to expand...
Click to collapse
well I have s6d
fict said:
well I have s6d
Click to expand...
Click to collapse
I have this problem too.. but i haven't folders (s6d or ws2401). I have pri_lcd_ws2401.0 folder
Sorry by my english.
So I see that ı am the not only one who has that black screen problem. :S ı have s6d screen driver. I can say that it occurs on cm 10.2 or even cm 11 too.
Screen seems black but it works. ı mean, you hear that phone unlock and when you touch you hear that an app opened.
(at last build of cm 10.2 , I haven't experience that yet)
is it solved yet? my samsung galaxy ace 2 CM 10.2 experienced this problem too and i haven't found any working solutions , please help
plsss i need the solution for this problem. it's still happening in my ace 2
Related
Hi everyone,
I've looked for a solution all over the net, but seems like no one had this problem before (guess i'm a special girl...):
The vibrate feedback when touching the screen just stopped working, in spite of the settings under "settings -> sounds -> vibrate on touch".
It started after an update to AOKP rom - milestone 5 (based on ICS 4.0.4) + Franco kernel nightly r151, but effects all the other roms. Maybe one untouched system file damaged.
I've tried everything: restore from previous nandroid backup, another rom (CM9), another kernel, another launcher, I even wiped everything and flashed new and clean rom-stock from google developers' page. And yet - no vibrate feedback.
The wired thing is that the haptic feedback is working in few specific applications, like the build-in ICS keyboard and the dialer Dialer-One, so it probably not some hardware failure.
All this time there are five softkeys that still have haptic feedback: the buttons of the nav-bar, the button that opens the applications drawer and the google-search widget.
I've tried using "KickBack" instead, but it's too aggressive and very uncomfortable.
PLEASE, PLEASE - Help me!
Same thing happened to me. I had the exact same setup and the haptic feedback went away after I flashed the kernel. Since I've had lots of issues when trying custom kernels, I just restored a nandroid and went back to the kernel included with aokp.
Sent from my Galaxy Nexus using XDA
Restore fixed my issue, so I'm not sure exactly what to tell you.
Sent from my Galaxy Nexus using XDA
taappel said:
Restore fixed my issue, so I'm not sure exactly what to tell you.
Click to expand...
Click to collapse
I've seen some ppl's msgs that even simple reboot fixed their vibrate problem.
Didn't work for me, unfortunately
Some kernels have haptic adjustment, see pic for kernel does.
I'm running Franco 152 and mines fine.
I know trinity kernels lower it
Sent from my Galaxy Nexus using XDA
Sveke said:
Some kernels have haptic adjustment, see pic for kernel does.
I'm running Franco 152 and mines fine.
I know trinity kernels lower it
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
I'm also using Franco kernel, but I don't think this is the problem because i've tried some other kernels and none of them fixed my haptic.
Hi TaliKa
I've just had this problem myself but it happens long after I flashed aokp m5 + franco r152 (too) so I'm not exactly sure what caused it. However after I went to clear my cache and dalvik cache, everything seems fine again.
nich0145 said:
Hi TaliKa
I've just had this problem myself but it happens long after I flashed aokp m5 + franco r152 (too) so I'm not exactly sure what caused it. However after I went to clear my cache and dalvik cache, everything seems fine again.
Click to expand...
Click to collapse
Thanks guys, but as I wrote in the first msg, those actions didn't help.
Is there any pro here who can offer a profound solution that I didn't tried before?
Which system file responsible for the haptic feedback?
Guess I'll have to stuck without haptic feedback...
Sveke said:
Some kernels have haptic adjustment, see pic for kernel does.
I'm running Franco 152 and mines fine.
I know trinity kernels lower it
Click to expand...
Click to collapse
How can I adjust the haptic feedback feature in Trinity kernel?
+1
just wanted to say...exactly the same thing happened to me (started with aokp milestone 5 and vibration gone afterwards...)
im trying several things to get it back...i use it alot (at work and most of the time..its on vibrate)
hopefully we'll find a solution
Yeah this just happened to me too. It was working fine for awhile on AOKP and then all of a sudden it stopped. No idea what happened exactly. I tried whiping everything and restoring CM9 but that didn't work either. I thought maybe hardware but the phone vibrated on boot so it isn't that. Hopefully we find a fix...
takomar said:
+1
just wanted to say...exactly the same thing happened to me (started with aokp milestone 5 and vibration gone afterwards...)
im trying several things to get it back...i use it alot (at work and most of the time..its on vibrate)
hopefully we'll find a solution
Click to expand...
Click to collapse
Dacian said:
Yeah this just happened to me too. It was working fine for awhile on AOKP and then all of a sudden it stopped. No idea what happened exactly. I tried whiping everything and restoring CM9 but that didn't work either. I thought maybe hardware but the phone vibrated on boot so it isn't that. Hopefully we find a fix...
Click to expand...
Click to collapse
unfortunately I didn't get any solution yet. Realy depressing.
I promise to update about any progress, and hope you'll both do the same...
Just don't give up! it isn't hardware thing, so there must be solution somewhere.
TaliKa said:
unfortunately I didn't get any solution yet. Realy depressing.
I promise to update about any progress, and hope you'll both do the same...
Just don't give up! it isn't hardware thing, so there must be solution somewhere.
Click to expand...
Click to collapse
im starting to believe its a hardware issue (well at least for me) i mean i dont even get a vibration upon booting or turning off the phone...and i even went back to full stock...same thing
maybe it might have been some software issue that led to the overburning of the motor(doubt that though)
what is weird though is that the same scenario happened to us so im lost...
maybe i should start talking to samsung for my replacement
meanwhile...im very open to suggestions that might help my case
hope we find something soon...u guys, does it vibrate at all?when u turn on ur phone?turn off? unlock ?
takomar said:
hope we find something soon...u guys, does it vibrate at all?when u turn on ur phone?turn off? unlock ?
Click to expand...
Click to collapse
Yes, it vibrates at boot and also when using application with it's own vibrate settings, like "dialer one" for example.
Did you try using KickBack just to check the hardware?
if it's some hardware issue, maybe you can apply to your warranty supplier about that, just flash stock rom and relock your device before.
TaliKa said:
Yes, it vibrates at boot and also when using application with it's own vibrate settings, like "dialer one" for example.
Did you try using KickBack just to check the hardware?
if it's some hardware issue, maybe you can apply to your warranty supplier about that, just flash stock rom and relock your device before.
Click to expand...
Click to collapse
thats what im gonna do i guess...such a sad day...
i couldnt find KickBack, its not available in my accessibility menu nor in my market (i live in France)
i tried googling an apk but nothing for android 4.0
do you have a link for it?
takomar said:
thats what im gonna do i guess...such a sad day...
i couldnt find KickBack, its not available in my accessibility menu nor in my market (i live in France)
i tried googling an apk but nothing for android 4.0
do you have a link for it?
Click to expand...
Click to collapse
I couldn't find it in play store either, but i download it from here:
http://code.google.com/p/eyes-free/downloads/detail?name=kickback-v1.1.1.apk
works fine for me.
TaliKa said:
unfortunately I didn't get any solution yet. Realy depressing.
I promise to update about any progress, and hope you'll both do the same...
Just don't give up! it isn't hardware thing, so there must be solution somewhere.
Click to expand...
Click to collapse
Good to know. I went ahead and flashed the base image and it restored vibration, then I rooted and flashed AOKP again. It worked for about that day and then this morning when I woke up the vibration is gone again. I'm almost positive it's AOKP's software. I'll test another ROM (Android Revolution) for a day and see if it happens again.
Dacian said:
I'm almost positive it's AOKP's software. I'll test another ROM (Android Revolution) for a day and see if it happens again.
Click to expand...
Click to collapse
Which kernel do you use? and did you set the quite hours on?
If you succeed to restore the vibrate, i'd like to hear exact instructions how to do that, including links to download the boot image, if you plesae...
Hello people!
I am a new member with XDA Developers
Anyways, I would like to ask if any of you face this problem where at any random time the phone would start vibrating continously until you shut down the phone and is there a fix for this?
l_daruwala said:
Hello people!
I am a new member with XDA Developers
Anyways, I would like to ask if any of you face this problem where at any random time the phone would start vibrating continously until you shut down the phone and is there a fix for this?
Click to expand...
Click to collapse
Hello and welcome the the XDA Forum!
I've found at time that the app "Whatsapp" when I get a message, My phone will constantly vibrate until the screen goes off for 5-10 seconds then it's fine until I turn the screen / unlock the phone, I think it's a common problem as I remember someone else had this issue.
Jamie
jamidodger1 said:
Hello and welcome the the XDA Forum!
I've found at time that the app "Whatsapp" when I get a message, My phone will constantly vibrate until the screen goes off for 5-10 seconds then it's fine until I turn the screen / unlock the phone, I think it's a common problem as I remember someone else had this issue.
Jamie
Click to expand...
Click to collapse
Yes i also found that too, but sometimes I encounter the problem with SMS too. Never encountered this problem with my previous phones, the GALAXY Ace (GT-S5830) and the GALAXY 3 (GT-I5801)
l_daruwala said:
Yes i also found that too, but sometimes I encounter the problem with SMS too. Never encountered this problem with my previous phones, the GALAXY Ace (GT-S5830) and the GALAXY 3 (GT-I5801)
Click to expand...
Click to collapse
It hasn't done it for SMS for me but yeah it never did it on my previous phone either ZTE Blade
When my profile switch app change profile and take phone to silent mode sometimes makes my W too...
The only solution reboot...
Looks like this affects all GALAXY W's
l_daruwala said:
Looks like this affects all GALAXY W's
Click to expand...
Click to collapse
Yes, and it happens always the best time... meetings, driving...etc.
never happen to me
but if it happened, I'll flash a new fresh ROM and see if it solves the problem
Happens to mine, seems like it was only when Whatsapp and something else had a notification at the same time.
soulbkd said:
never happen to me
but if it happened, I'll flash a new fresh ROM and see if it solves the problem
Click to expand...
Click to collapse
I had many ROMs like: Stock, Kezra, F.A.W Special. I get vibration in each case.
mayerkemp said:
I had many ROMs like: Stock, Kezra, F.A.W Special. I get vibration in each case.
Click to expand...
Click to collapse
that's weird, mine never experience it
I have tried stock, Bagux's, Blacknote, Kezra, and deodexed rom.
maybe something to do with HW version?
mine is rev 0.6 (via *#2222#)
soulbkd said:
that's weird, mine never experience it
I have tried stock, Bagux's, Blacknote, Kezra, and deodexed rom.
maybe something to do with HW version?
mine is rev 0.6 (via *#2222#)
Click to expand...
Click to collapse
Unfortunately mine too. No more idea.
Damn, mine is also REV 0.6 as well.
Still same problem
Mine also rev 0.6
Tried Rebel Rom, Bagux, Bionic Cow 2 v 7, stock DXLM3, stock XXLM8 , all still has the same random vibration.
And the vibration won't stop until you reboot.
Probably hardware related?
This happens to me since the first day I got this phone...
Honestly, it's annoying me !
Cause the only way to Stop it, is a reboot..
Sometimes it starts to vibrate in school, and as Im using a TPU SoftCase it's even more uncomfortable...
I thaught I was the only one, but seems like it affects all Wonders..
No matter which Rom I use, everytime the same Problem
A random time.
mayerkemp said:
I had many ROMs like: Stock, Kezra, F.A.W Special. I get vibration in each case.
Click to expand...
Click to collapse
same problem
hello i recently flashed this version of cyanogen-mod on my Samsung s2 and am having an issue. First of all, i used a non-touch CWM but it was confirmed to work as long as you use super swipe, so i did that and it worked no problem. However the back-lighting on my buttons will not come on. It is not broken because it sometimes works but mostly does not. i am wondering if there is a fix or a setting i need to use to get it to work.
Thank you
heatpro said:
hello i recently flashed this version of cyanogen-mod on my Samsung s2 and am having an issue. First of all, i used a non-touch CWM but it was confirmed to work as long as you use super swipe, so i did that and it worked no problem. However the back-lighting on my buttons will not come on. It is not broken because it sometimes works but mostly does not. i am wondering if there is a fix or a setting i need to use to get it to work.
Thank you
Click to expand...
Click to collapse
have you tried "settings > advanced > sensors" and checking the backlight and notification settings?
yes I have tried it, it fixes the issue but once I lock the phone and then unlock it it does not work anymore.
heatpro said:
yes I have tried it, it fixes the issue but once I lock the phone and then unlock it it does not work anymore.
Click to expand...
Click to collapse
It's a known issue with any aosp builds such as cm or aokp. No one has gotten it to work consistently yet with ics or jb
Sent from my SAMSUNG-SGH-T989 using xda premium
yoft1 said:
It's a known issue with any aosp builds such as cm or aokp. No one has gotten it to work consistently yet with ics or jb
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
i think ill just re-flash to dark-side evolution. can you please explain to me what the MD5 keys mean since there are like a few download mirrors and i an not sure which one to get.
i am having this problem on every version or CM9 past RC2 and CM10 i really would like a fix
i looked into this a little and it seems that it's a problem from the moment you turn off the screen until the first hard light timeout afte the screen is turned back on
Apparently the bug is also in Miui and AOKP
Hi guys, i've got a strange issue. My HOX is working, but the screen is off. Sometimes it turns on but with strange complicated issues like in the photo. The strangest thing is screenshot could't catch that view. i can receive income calls, all notifications, device is working. Only the screen is giving problem. I use my phone for one year and 3 months. It all started to happen a week ago. I was using Blade Elite rom, then i changed to Nik Project Rebirth rom, in aroma I ticked odex option, and after that... Now I don't know if it is a hardware or software issue. Can anybody please help me?
eyfa said:
Hi guys, i've got a strange issue. My HOX is working, but the screen is off. Sometimes it turns on but with strange complicated issues like in the photo. The strangest thing is screenshot could't catch that view. i can receive income calls, all notifications, device is working. Only the screen is giving problem. I use my phone for one year and 3 months. It all started to happen a week ago. I was using Blade Elite rom, then i changed to Nik Project Rebirth rom, in aroma I ticked odex option, and after that... Now I don't know if it is a hardware or software issue. Can anybody please help me?
Click to expand...
Click to collapse
Unfortunately that looks like the graphics chip has failed, I read about this happening to some devices. I think this might be a hardware issue but maybe someone else can confirm?
pakjebakmeel said:
Unfortunately that looks like the graphics chip has failed, I read about this happening to some devices. I think this might be a hardware issue but maybe someone else can confirm?
Click to expand...
Click to collapse
Does it take some time for screen to turn on as wel?. Mine had these symptoms and Mainboard had to be replaced.
http://forum.xda-developers.com/showthread.php?t=1859339
jomy117 said:
Does it take some time for screen to turn on as wel?. Mine had these symptoms and Mainboard had to be replaced.
http://forum.xda-developers.com/showthread.php?t=1859339
Click to expand...
Click to collapse
Thanks a lot mate.
If you chose odex option, did you wait until the device rebooted? On first boot, it does not boot up and rather odexes..maybe you interrupted that process...so just do a clean reflash of the rom, wiping system,data and cache... Make sure you wait for as long as needed before the system finally boots up...remember, first boot odex, then it will automatically restart and then next boot , you can finally access your phone (as in a complete boot)
Sent from my HTC One X using xda app-developers app
Sadman Khan said:
If you chose odex option, did you wait until the device rebooted? On first boot, it does not boot up and rather odexes..maybe you interrupted that process...so just do a clean reflash of the rom, wiping system,data and cache... Make sure you wait for as long as needed before the system finally boots up...remember, first boot odex, then it will automatically restart and then next boot , you can finally access your phone (as in a complete boot)
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Thank you for your reply, but i found that this is not a software issue. The same problem in this video is happening with my device now and i think it depends on overheating of device. http://www.youtube.com/watch?v=VFvABvJXDc8
Closed on OP request
Ok, straight to the point..
I have an issue in making a call exactly
When I am trying to call somebody, sometimes the dialing window won't appear.
Ok, it finnaly appear, but it takes a long time
Also, when typing, sometimes it wont type anything
I think there is an issue with the keyboard, but with different keyboard, the issue still exists
Clearing app data wont help, because those issue happen sometimes and it working again a couple minutes later
Those issues happen almost in all ROM i've installed.
I wonder what the problem is ?
Is there anyone having exactly the same issue with me ?
Any suggestion would be highly appreciated :beer:
Sent from my GT-S5660 using xda app-developers app
Hey!
I've been having the same problem on stock rom and the only way that seems to fix it is just rebooting your device. When I run cyanogenmod for example the problem doesn't occur anymore
Yea man, I have followed your suggestion and now I am on GingerDX ported by oldDroid, looking if the problems occur again
what is your daily ROM anyway ?
I mainly use maclaw's cyanogenmod for my gio
And does the problem still occur?
not for now..
is that CM 9 RC3 by maclaw ?
I used that rom a year ago, before i realised there is a problem with netd process taking high cpu usage when not connected to a wifi
I prefer to use gingerbread ROM
I've been using Jellybean 4.2.2 (CyanogenMod 10.1) from maclaw since it came out and I haven't had alot of problems with it!