Develop Bugs

[Q] No vibration (at all), and touchpad dead?

Hi eveyone,
I have a HTC desire, originally bought unbranded and unlocked. About two months ago I rooted with unrevoked (after downgrading the HBOOT as I had installed the OTA vanilla Froyo). I have been running OpenDesire and was until recently using v.4.0.34.
Everything has been working fine until yesterday, when it was in my pocket and I got caught in a rainstorm. It got damp, but not super-wet, and was still working fine at the time. Inside the back case and under the battery was dry. Several hours later I updated to 4.0.36. Immediately after update, it was fine and acting normally. In the morning when I woke up and ever since then, the phone has not been vibrating at all. I first noticed it in Swiftkey entering text and thought it must be a setting, but it doesn't vibrate on texts, phonecalls, turning on, turning into vibrate mode, anything.
I thought I might as well reflash from scratch in case something had gone wrong with 4.0.36 so I went to do a wipe, reflash the radio and the rom, and see if this fixed it.
At this point I got back to ClockworkMod recovery and couldn't use the trackpad. It doesn't scroll, it doesn't press, nothing. It also doesn't do anything when booted. Every other bit of my phone works perfectly - charger, headphones, touchscreen, volume and power buttons, the lot.
I am *assuming* these problems are related to the damp rather than anything software-related, but other than the update to 4.0.36 I haven't done anything different or installed any new software. I would also be surprised if it was due to the water, cos it really wasn't that damp.
Any help would be appreciated. I am *this* close to stripping it down and taking it to bits to clean all the contacts of any deposits or anything, but just in case that's a bit OTT, I thought I'd ask you guys on here, because, well, you know everything
Cheers,
Dan

I have this on very rare occasions. Softly hitting the phone on the back helps. If you unsure what I mean. Just drop the phone on your bed once and it'll fix. (Atleast for me it does then)

Z1 Compact with Cyanogenmod - Screen doesn't wake

Hi,
I have:
Sony Xperia Z1 Compact
Rooted
CyanogenMod version 11-20141112-SNAPSHOT-M12-amami
Android version 4.4.4
Kernel version 3.4.0cyanogenmod-g1b20e398 [email protected] #1
Build number cm_amami-userdebug 4.4.4 KTU84Q a265284510 test-keys
My phone's screen has the annoying problem of sometimes not waking when I press the power button (while the phone is turned on). The phone is still on, but doesn't respond to input. I can call it, but nothing happens. I can connect the charger, but it doesn't respond.
I did not experience the issue before rooting. After rooting and installing CyanogenMod, the problem occurred perhaps 1-2 a week.
Recently I encrypted my phone. After that the problem has become much more frequent. The screen is now unwakable roughly 2-3 times a day, some times even more!
The only solution I have found, it to either turn the phone off via the red off button next to the SIM card, or by rebooting it by holding the power button in for so long.
The issue is extremely annoying, especially after it started occurring 2-3 times a day.
I have tried searching for similar issues, but haven't found any solutions.
I have tried changing the brightness levels so the max level is 99% instead of 100%, as someone had suggested, but that hasn't made any difference. Unscrewing the phone and cleaning the proximity sensor, as someone else had suggested, is something I haven't tried yet, as I don't feel competent enough to unscrew the phone.
The phone used to have the protection plastic provided from the fabric, but I tore that off not too long ago. No change in behaviour.
I have not managed to find one special event that triggers this behaviour or reproduce the issue on demand.
Hopefully someone will have some tips as to what I can do to solve this issue. Thanks in advance.

Any modifications on the kernel? Like special governors or under/overclocking?
As you are using a custom ROM the clear advise here is: try out with stock ROM and see if the problem is still there.
If not, it is a problem with the ROM.

I'm having the exact same problem. I flashed cm11 snapshot two days ago, and today my screen wouldn't wake no matter what.not even a restart would solve the issue, cause the moment the phone goes to sleep after a boot, that was the last time the screen was on. I'm following this thread in case somebody comes up with a solution.

hi there, my phone is acting the same way as yours described. Mine is rooted on stock lolipop and it never happened before although i had a replacement unit and the one before that acting the same way. Pressed the power button and nothing happend regardless screen on or off. Had to do hard reset and it worked for like 1 or 2 days. I went to sony talk forum and ppl seems to say it a bug since the phone released. If anyone got anything would be great help. Thanks

[noob inside] - Screen unlocking problem, faulty device or android bug ?

Hey there guys , I've been searching through the forum topics about my issue but so far I've found nothing close to my scenario.
A few months ago I bought my first HTC phone (M8). Its a great device for sure , despite the fact that I had to return it back twice.
First time it was a faulty microphone , so they sent me back a brand new device. Great isn't it ?
However recently I've noticed a few .... let me call them 'glitches' .
Let me give you some details on what I've experienced with the device:
Despite the issues that i'm going through ... the phone works great, but...
Sometimes the screen wont turn on when I'm receiving incoming calls (same goes for the alarm clock) but the phone is able to recognize touches - i've managed to pick up the call when I swiped the screen in the area where the "green" answer button appears .
The above issue doesnt happen so often but the thing that bothers me is the unlocking issue.
At first I thought that it was stuck or faulty power button.
When the phone is idle for some time and I pick it up and press the unlock button ... nothing seems to happen I've tried pressing it hard ... i've tried pressing it gently ... i've tried pressing it multiple times until the screen wakes up .
Same goes for motion launch unlocking .
When I use motion launch to unlock it the phone only gives me a vibration feedback ... and thats it until I try harder to bring the screen back to ''life'' .
(I can also press my security pattern buttons while the screen is dead and feel the phone vibrating , BUT NOT ALWAYS , sometimes is just .. dead )
I already sent the phone back describing the same problems and they just flashed the firmware , which did not fix any of the issues.
Stock Rom android 5.0.1 , not rooted
Soo what do you guys think? What can I do next .. is it android bug or a faulty unit ?
is it possible to be a sensor problem (proximity , accelerometer)
Already tried factory reset and dalvik cache wipe.
Any advice would be useful.
Thanks for taking your time .
Cheerz

I have the same issue. There are times it takes me hitting the power button 20 times for it to finally light up but I can press buttons with it black. The weird thing is it does it on every single ROM but I havent noticed it on Stock...maybe I'm not using stock enough to see. I'll probably throw stock on there today and take it into sprint and let them replace it.

I have the same problem whether it's on stock or custom ROM (KK or L). I am pretty sure this is a hardware problem. Unfortunately, my m8 is out of warranty so HTC won't fix it for free. I read it some where that it could be a faulty proximity switch so shining a light beam to the top part of the phone may wake up the screen. I haven't tried it yet because every time it happens, I don't have a flash light handy. It is an annoying problem to say the least.
When this happens, I pushed the power button, the volume up button, and swiping the screens. Eventually the screen would wake up and every thing works fine... until the next time.

Its a ****ing pain in the ass.
however none of the sensor reading apps report a faulty/stuck sensor.
the wors thing... I've already sent my phone for repair, describing the problems in details. .. and it took them a whole f*cking month to bring it back to me with no results.
I don't think they will replace it because its a problem that takes time to be experienced...and no one is going to wait for it to happen. ...
Any other ideas?
Should I wait for android 6.0 or should I try a custom rom too see if these problems presist.
Fml I love the phone but this is frustrating.

I have the same problem I think. I just bought an M8 on Ebay. I am S-off, unlocked and rooted, using the Viper Rom currently. I have also tried AICP, the stock Tmobile Rom and a few others. Same issue.
If I double tap, I feel the screen vibrate, but nothing comes on. Then, I keep pushing power button a few times. Sometimes it comes on and sometimes I am too impatient to wait, so I just hold power and volume up.
I also know that the phone internals come on, because after that vibration, I swipe up and push the screen a few times. Then, when I am fiddling with the power button and it does come on, I do see that there is an app already on the screen.
I think this is a rare issue, as I haven't even been able to find many posts regarding this. I may have to get a new one if this keeps going on so bad.

Ozger said:
I have the same problem I think. I just bought an M8 on Ebay. I am S-off, unlocked and rooted, using the Viper Rom currently. I have also tried AICP, the stock Tmobile Rom and a few others. Same issue.
If I double tap, I feel the screen vibrate, but nothing comes on. Then, I keep pushing power button a few times. Sometimes it comes on and sometimes I am too impatient to wait, so I just hold power and volume up.
I also know that the phone internals come on, because after that vibration, I swipe up and push the screen a few times. Then, when I am fiddling with the power button and it does come on, I do see that there is an app already on the screen.
I think this is a rare issue, as I haven't even been able to find many posts regarding this. I may have to get a new one if this keeps going on so bad.
Click to expand...
Click to collapse
I am experiencing the exact same issue with my M8. I have seen a lot of people stating it may be a hardware fault related to heat and internals but something about how it reacts seems software related.
I really hope someone who has fixed or uncovered the reason comes forward. At this rate I may be switching back to a S4 LTE-A.

Soulink said:
I am experiencing the exact same issue with my M8. I have seen a lot of people stating it may be a hardware fault related to heat and internals but something about how it reacts seems software related.
I really hope someone who has fixed or uncovered the reason comes forward. At this rate I may be switching back to a S4 LTE-A.
Click to expand...
Click to collapse
I think it IS hardware related. I was able to return that one and got another M8. No problems at all.

SM-N7505 Wi-Fi not turning on

Hi everyone,
I'm having serious problems with my Wi-Fi on my Samsung Galaxy Note 3 Neo (SM-N7505). Whenever I click the button to activate the Wi-Fi, the icon goes from grey to a dull green (darker than the bright green which signals that a function is turned on), as it does when it's trying to turn itself on. Problem is, instead of turning on, it just stays in that state for a few minutes before reverting to grey. This has gone on for a while, and I've already tried several possible solutions which I found after online searches. I don't think it's a hardware issue (see point 1 for the reason), and I really hope it isn't, because my warranty has been voided due to rooting, so I can't have my phone replaced or repaired unless I pay for it (which I can't at the moment). So, I'm basically ignoring the possibility of hardware failure and trying every possible software solution, hoping one of them will work, otherwise I'm just stuck with no Wi-Fi. These are the fixes I've tried:
1) Take out the battery while the phone is on, wait a few seconds, then put it back in and boot the phone up. This used to work when the problem first presented itself a few months ago (which is why I don't think it's a hardware issue), and I've been since using this method to fix it whenever it happened again. But a few days ago, this method stopped working for whatever reason, so I was back to square one.
2) I tried renaming the data/misc/wifi/wpa_supplicant.conf file, which seems to have worked for some people, but not for me.
3) I tried updating the version from Kitkat to the recent Lollipop, hoping that would fix it, but nope.
4) I tried deleting practically every single app one by one, hoping that one of them was interfering with the Wi-Fi somehow, but nope.
5) As a last resort, I tried a factory reset, but not even that worked.
This is basically the long and short of what I've tried to fix this... I might've skipped a few of the simpler fixes I tried (for example, I just remember I tried disabling "Smart Network Switch", which seemed to do it for some people), but the big stuff is all there.
I'd really like to get my Wi-Fi back, so if anyone could help me fix this thing I'd be really grateful!
Thanks in advance to anyone who will bother to reply.

same problem dude
Same problem...wifi and bluetooth not working...pls help us

Same Problem for me, Initally it works fine even after updating Official Lollipop update (OTA), but after few months now wifi & bluetooth are not working for me. And finally faced battery drain issue for past few days. Battery goes down upto 20% per hour even in idle condition. Then i rooted & installed Note Rom & even after i face the same problem. Is there any way to fix?

SMT700 screen flicker & reboot issue - kinda solved

It started about 8 months ago, in retrospect, after an OTA update. I'd be looking at some app when the screen would flicker and shortly after it would either go blank, reboot or simply turn off, it was maddening and I thought the end of my little tablet. I tried a couple of different things, thinking that somehow the bootloader got corrupted I reflashed that, didn't work. I then flashed the previous version of the bootloader, that really didn't work so flashed back. I'd always kept the tablet with the stock Samsung ROM so flashed the latest Lineage ROM (great piece of work) but that didn't help and actually made it worse, when I would reboot it seemed like it would immediately flicker when things were updating, it wouldn't stay on for more than a minute. I read about the potential for cracked battery leads so changed the battery and reflowed the solder around the terminals, that didn't solve the problem either. After that I started to suspect some kind of memory/software issue so in desperation I flashed it back to the beginning of time, the original Samsung ROM and that worked. I have the TAR if anyone needs it just let me know. After you do this your back to Android 5 and you'll notice that it will notify you of OTA updates, I updated BUT I found that past the 4th update the flicker came back, this might just be an issue with my tab but just be aware. I only use this now to read the news or my Kindle books, I did notice that some apps would trigger the flicker like My Radar or Zillow so I uninstalled them.
Hope this helps.