Database Develop

Note turns off

Hi, sometimes my note turns off by itself. When I try to wake the screen it doesn't wake and I have to push power button for some seconds before the note restarts. Is any if you experiencing the same issue?
Sent from my GT-N7000 using XDA

docsportello said:
Hi, sometimes my note turns off by itself. When I try to wake the screen it doesn't wake and I have to push power button for some seconds before the note restarts. Is any if you experiencing the same issue?
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
Are you on a custom rom or stock rom ?
If on custom what rom and kernel u using?

Flashing another kernel may help
Sent from my GT-N7000 using XDA

docsportello said:
Hi, sometimes my note turns off by itself. When I try to wake the screen it doesn't wake and I have to push power button for some seconds before the note restarts. Is any if you experiencing the same issue?
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
Are you sure it's totally off? I had this issues when phone looked like it's turned off, but when I pushed buttons for a while it was waking up, so I didn't have to restart it. Some people recommend using jBroid Kernel Cleaning script before you flash new kernel.
And if it's happening after installing new ROM I would recommend to flash stock ROM, then doing a full wipe twice and then flashing ROM you currently use or want to use.
I don't have such problem anymore so it might help.

I'm on the custom rom, I've never rooted my device. The phone is like dead, it's not even turned off. At first I had to put the battery out and then put it in again. Then I discovered that if I pressed the power button for something like 5-6 secs it started again, with the samsung logo and all. Not a big issue but if I don't check my note often I risk to miss important calls. Please help me! Thanks
Sent from my GT-N7000 using XDA

docsportello said:
I'm on the custom rom, I've never rooted my device. The phone is like dead, it's not even turned off. At first I had to put the battery out and then put it in again. Then I discovered that if I pressed the power button for something like 5-6 secs it started again, with the samsung logo and all. Not a big issue but if I don't check my note often I risk to miss important calls. Please help me! Thanks
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
What apps do you have installed? I had this problem with both WidgetLocker and NoLed.
WidgetLocker I have just given up with - wish id never bought the stupid thing, as it's never worked reliably on my Note or my tablet! (rant over).
NoLed I traced the problem to the flash-the-screen battery saving features. Changing it to leave the screen on all the time when notifying hadn't seemed to use any more battery life and my dead screen problems have gone away.
Just something to consider!

You can try connecting your Note to the PC when running Samsung Kies software. Maybe it will find an update to the ROM you are on right now and this might fix your issue. If not you should go to the developement section of this forum and search for the recent stock rom available and then follow dr. ketan's guide http://forum.xda-developers.com/showthread.php?t=1424997
If flashing new ROM wouldn't solve your problem, then I guess it's a hardware issue that requires professional service.

squicky said:
You can try connecting your Note to the PC when running Samsung Kies software. Maybe it will find an update to the ROM you are on right now and this might fix your issue. If not you should go to the developement section of this forum and search for the recent stock rom available and then follow dr. ketan's guide http://forum.xda-developers.com/showthread.php?t=1424997
If flashing new ROM wouldn't solve your problem, then I guess it's a hardware issue that requires professional service.
Click to expand...
Click to collapse
I think he should try a different kernel first. Another possibility is that some apps in your phone cause this problem.
Sent from my GT-N7000 using XDA

kelvin fong said:
I think he should try a different kernel first. Another possibility is that some apps in your phone cause this problem.
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
I think its a stock kernel and ROM he's on... Even though he says 'custom ROM' he also says its never been rooted, so how would he get the custom ROM working if not by rooting the phone?!
That being the case it must be something interfering with the sleep mode so its probably best to check what has been installed recently, remove those apps one by one over a period of time and check if the problem goes away!

Yes it's a stock rom I am using and the issue happens randomly... Is it maybe lockscreen app? I read the users' comments and no one mentioned such a problem...
Sent from my GT-N7000 using XDA

me too my ho jus shuts off by itself.. I m using KL1 kernel wif KL3 rom

Note randomly shuts down - Did you solve this issue?
Hi,
I was wondering if you managed to solve this issue as I am experiencing the same issue where the phone randomly switches off when the screen is locked.
I am using easy battery saver app which sets the sleep schedule to check network data every 15 min.
Cheers

Galaxy Note 2 shuts down
The issue exists on the Galaxy Note 2 as well and has nothing to do with software.
The problem is hardware related. The phone is flawed and shuts off on it's own under various conditions, all hardware related. Take a look at this video: http://www.youtube.com/watch?v=SjLn2yikYnI
Also, take a look at this site I built that goes in to more detail regarding the issue: www.GalaxyNote2ShutsOff.com
One look at that short video and I am sure there will be some light bulbs going off. Be sure to read the details I provided on that site as well. They go in to detail about the problems that I have had and the lack of proper support that Samsung is willing to provide.

thanks for the heads up with NoLed....I just hope my issue ( phone's screen just dies when not in use - but I think the device is on as the headphone jack responds with the disconnection sound when unplugged) gets resolved...
I was thinking too that philz cwm may be affecting it ( kernel issues )? ...any way I will update as time passess

Screen unresponsive

Hi everyone,
I bought a Samsung galaxy s last week from an eBay auction. The phone was described as touch screen lag. I was thinking that flashing a new firmware will solve the problem. I got really cheap though
The touch screen stops suddenly in every 5/6 minutes and I have to lock the screen using power key and unlock again to make it working.
when I got the phone:
Non Samsung battery and chargers were used, I changed and using original ones.
Stock XXJVS firmware in it.
First I flashed stock 2.2.1 froyo and test the screen using *#0*# code. it got pass. But when I start using it, the problem was still there.
Then I flashed stock GB, same story, now slim ics, same thing.
Please someone help me, there is nothing I can do with it now.
I search few threads related to screen problem but couldn't find one with similar problem. So asking here.

mregmi121 said:
Hi everyone,
I bought a Samsung galaxy s last week from an eBay auction. The phone was described as touch screen lag. I was thinking that flashing a new firmware will solve the problem. I got really cheap though
The touch screen stops suddenly in every 5/6 minutes and I have to lock the screen using power key and unlock again to make it working.
when I got the phone:
Non Samsung battery and chargers were used, I changed and using original ones.
Stock XXJVS firmware in it.
First I flashed stock 2.2.1 froyo and test the screen using *#0#* code. it got pass. But when I start using it, the problem was still there.
Then I flashed stock GB, same story, now slim ics, same thing.
Please someone help me, there is nothing I can do with it now.
I search few threads related to screen problem but couldn't find one with similar problem. So asking here.
Click to expand...
Click to collapse
Sounds like a hardware problem to me..but it's really hard to say if it is. But it would definitely seem like it since it isn't ROM related. Maybe a water damage or faulty digitizer?
Sent from my GT-I9000 using Tapatalk 2

This happens to me sometimes very rarely though, it will be weird and hard to touch but speaking to someone with the same phone they said they had this problem to all I do to resolve the problem is lock and unlock the screen, I thought this was normal?
Sent from my GT-I9000 running remICS-UX using XDA premium

It shouldn't be normal. I am using another galaxy s for almost two years. But never had this problem in such extent, little bit lag on touchscreen when on froyo. But never after. Now with slim ics Temple run is more smooth then iphone 4.
Sent from my Galaxy S using xda premium

Kurre said:
Sounds like a hardware problem to me..but it's really hard to say if it is. But it would definitely seem like it since it isn't ROM related. Maybe a water damage or faulty digitizer?
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for reply. When I got it first time, it was really annoying, the problem was so frequent that it was almost unusable. Now in new rom, after unlocking the screen it works little longer then before. Works like a charm when it works. So not sure this is hardware problem.
Sent from my Galaxy S using xda premium

I don't think this is a hardware or problem either, I broke the screen and replaced it and I still have the same thing when though it is very rare, so if it was the screen it should of gone after I installed the new one, btw I installed a whole new pre built front so the bevil and LCD, and my phone has never hib water damaged? Maybe its something to do with the bootloader? As that doesn't change through ROM flashes
Sent from my GT-I9000 running remICS-UX using XDA premium

mregmi121 said:
Please someone help me, there is nothing I can do with it now.
I search few threads related to screen problem but couldn't find one with similar problem. So asking here.
Click to expand...
Click to collapse
try using a LCD modder LCD density modder https://play.google.com/store/apps/details?id=com.birdapi.android.dpi&feature=search_result

@xsenman;
I did that couple of times going through Advance slim setting. That didn't change anything. Now I'll try this as well.
I change touchscreen into chainfire sensitive option in semaphore app. Still lagging.
Tried over clocking to 1200 but it freezes and automatically reboots into recovery mode. I can use only after changing to default
Sent from my GT-I9000 using xda premium

Guys its really annoying now. Its behaving strangely. I played with it few hours and found out that the screen near the home button freezes first. I cant press the dock but still pull the notification bar? then stops working whole screen. I checked the show touches in developers options setting. Sometimes it works randomly actually without touching it , I just place my finger near the screen but didn't touch and on few occasion it works opposite direction, like I scrolled down but it gone up:crying:
Is this the sensor issue? Is there any way to fix? Any idea please?

mregmi121 said:
Guys its really annoying now. Its behaving strangely. I played with it few hours and found out that the screen near the home button freezes first. I cant press the dock but still pull the notification bar? then stops working whole screen. I checked the show touches in developers options setting. Sometimes it works randomly actually without touching it , I just place my finger near the screen but didn't touch and on few occasion it works opposite direction, like I scrolled down but it gone up:crying:
Is this the sensor issue? Is there any way to fix? Any idea please?
Click to expand...
Click to collapse
try this tool to verify where the problem is , if its hardware, you have no choice but to take it to a technician
https://play.google.com/store/apps/details?id=com.gombosdev.displaytester&feature=search_result
and this
https://play.google.com/store/apps/details?id=com.vital.tst.n7000&feature=search_result
https://play.google.com/store/apps/details?id=zausan.zdevicetest&feature=search_result

xsenman said:
try this tool to verify where the problem is , if its hardware, you have no choice but to take it to a technician
https://play.google.com/store/apps/details?id=com.gombosdev.displaytester&feature=search_result
and this
https://play.google.com/store/apps/details?id=com.vital.tst.n7000&feature=search_result
https://play.google.com/store/apps/details?id=zausan.zdevicetest&feature=search_result
Click to expand...
Click to collapse
Screen+digitizer panel can be changed by yourself. For it, you just need couple of tools and little nerves
Instructions can be found from YouTube, this forum and many other places..
Sent from my GT-I9000 using Tapatalk 2

Kurre said:
Screen+digitizer panel can be changed by yourself. For it, you just need couple of tools and little nerves
Instructions can be found from YouTube, this forum and many other places..
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
I tried all of those apps, nothing wrong. I think I should change the screen and digitizer, I might need to go to the repair center because my hands shake (my usual problem) and hard to fix tiny things. I want to do few experiments before taking it to repair. I already put it in the freezer for two hours it was acting like crazy after.
Suggest me more...
Sent from my GT-I9000 using xda premium

Me too!
and i thought i'm the only one experiencing this kind of problem. it is exactly what i'm having on my sgs. seems to be temporarily fixed by turning the screen off and then on again, but after a while, the screen doesn't respond on the same spot as you're having.
i've managed a low level debug on screen touch response using adb logcat, and my touch doesn't really register any on adb logcat console.
they might be correct on the hardware problem, but when i'm on any gingerbread rom (2.3.6), the problem is gone.
guys, any idea what kind of drivers they're using on gingerbread for our touchscreen?

I have this too on ics, left half of screen stops responding, lock on/off sorts it....until the next time! Bugs the hell out of me!

Me too! on ICS
btw, i'm already on ics team nyx

change
flash CF KERNEL and put ICS CM9

middle screen not responding
- when in stock gb firmware (official from samsung), the touchscreen problem is gone.
- but i want the features of an ics rom, so i flashed one (first was slim ics); the problem appeared first; first guess was the custom rom was still in its early stages.
- flashed back to gb, no touchscreen problem.
- flashed new ics rom from cm9 (nightlies), problem appears again (ugh!).
- flashed backed to updated slim ics since this was the fastest and easiest to install, touchscreen problem still persist.
- found a temporary fix by turning the screen off then on again.
did a adb logcat full trace log of touchscreen input: what i noticed was the whole vertical middle part of the screen is not responding to touch; dragging touch from one side to middle is working just fine, but not starting from the mid vertical part.
the problem may sometimes go away after a while, and sometimes persist even after the temp fix. it's very intermittent indeed.
help please.

psycotrompus said:
- when in stock gb firmware (official from samsung), the touchscreen problem is gone.
- but i want the features of an ics rom, so i flashed one (first was slim ics); the problem appeared first; first guess was the custom rom was still in its early stages.
- flashed back to gb, no touchscreen problem.
- flashed new ics rom from cm9 (nightlies), problem appears again (ugh!).
- flashed backed to updated slim ics since this was the fastest and easiest to install, touchscreen problem still persist.
- found a temporary fix by turning the screen off then on again.
did a adb logcat full trace log of touchscreen input: what i noticed was the whole vertical middle part of the screen is not responding to touch; dragging touch from one side to middle is working just fine, but not starting from the mid vertical part.
the problem may sometimes go away after a while, and sometimes persist even after the temp fix. it's very intermittent indeed.
help please.
Click to expand...
Click to collapse
So your sgs touchscreen working fine on stock gb rom! It might not be a hardware problem then. We have similar problem, only difference is I have problem on GB too. I've even tried stock froyo, same story
Sent from my Nexus S using xda premium

same problem here, left part of the screen would be unresponsive at times
can fix by locking the phone through power button and unlocking it, thats why i think its a software problem.
I dont remember having this problem in GB also.
maybe something is messed up during flash?

I have the same problem with ics and jb roms from the onecosmic ics times and i had a topic http://forum.xda-developers.com/showthread.php?t=1648287
I have written here but no one seems to now what it is, i have been using ics from onecosmics first release and had the problem from that moment on, different kernels, roms etc it is still here i have flashed gb again and problem is gone, flash again with ics the middle part still acts sometimes. ?...
We should request from kernel developers and rom developers to look into it. I have tried almost everything no luck so far

[Bug][ICS 4.10.405.1]Touchbug

Hi all
I recieved the Update to ICS on 2. July. I was very happy about it and it is really great. But I recognized 2 problems:
-Preformance is not the best
and
-the touch doesn't always recognize more than 1 finger.
What I did to fix:
I tried a hard reset and it fixed the performance, but not the touch.
When does the bug appear:
Often, but not always. Sometimes it works fine and then it doesn't work properly
When I play games, some games needs to tap at varius points on the touch. When I fast tap then the touch doesn't always recognize any fingers. With 1 finger, the touch works fine, with 2 fingers, it doesn't always work.
I attached a link to show how the touch doesn't always work.
https://dl.dropbox.com/u/4910238/IncSTouchbug.mp4
I started the thread to find other people who have the same problem. At the moment I'm writing with the htc support, and I hope that I find more people who has the same problem, so I can give him the link and they try to fix that annoying bug.
i hope I'm not the only one out there and we and HTC can find a fix.
best regards
MrToastbrot

MrToastbrot said:
Hi all
I recieved the Update to ICS on 2. July. I was very happy about it and it is really great. But I recognized 2 problems:
-Preformance is not the best
and
-the touch doesn't always recognize more than 1 finger....
Click to expand...
Click to collapse
Hi MrToastbrot. I have the same issue, after getting OTA 4.0.4 update, from HTC. I noticed the problem early, so I've been searching all over the web to find some solutions, but couldn't find any.
Please write a message, if HTC Support does give you some useful information about this problem.
Best regards
Luckyone.

My Incredible S acts similar, if it is touched by 4 fingers - then fingers on screen are detected "jumping", like in video. That continues even when only 1 finger is still on screen, but ends when nothing touches the screen.

I would post a link of google ''android issues'' page, but I can't because of ''Spam protection''.
The thing I wanted to say is, that this problem doesn't only concern HTC users, but it appers on, for example, Galaxy Nexus with different android versions too.
One guy wrote : ''I've heard people claim its something to do with the digitizer losing calibration when getting hot and that locking and unlocking the device recalibrates it.''
Still waiting for solution.
Edit : p.s. yeah - factory reset didn't help it.
Edit2: ....or it did? Right after factory reset, i tested the multitouch - it still wasn't working. After I downloaded some apps, I decided to test it again, just in case, and it seems to be working now. .
Edit3: It seems, that the theory about digitizer getting hot is true. A minute after I plugged my phone to charger the multitouch stopped working properly. Sad. Well, I guess we will have to wait some updates from HTC, or put our phones in a fridge or something.
Cheers!

ALMOST Solution found!
All we can blame is HTC Sense. You see - when you unlock the phone, the locker(sense locker) does something to make multitouch not working.
When you go to the ''Apps'' menu in ''Settings'' and Force Kill HTC Sense(the one with green HTC logo), touch screen starts working flawlessly again.
After you lock and unlock screen again - it won't be working.
The thing is - I'm a bit afraid to disable Sense permanently.
Let me know if this work for you guys.
Cheers.
Edit : Force Stop ''HTC Sense'' with launcher logo too. I'm really confused, because I can't understand what Stock Launcher has to do with multi-touch issues...

Nice, so we have only to wait until htc fix this bug. But one question:
Why does HTC Sense affect, that the touch isn't working correct in games?
Sent from my HTC Incredible S using xda app-developers app

MrToastbrot said:
Nice, so we have only to wait until htc fix this bug. But one question:
Why does HTC Sense affect, that the touch isn't working correct in games?
Sent from my HTC Incredible S using xda app-developers app
Click to expand...
Click to collapse
Solution, I think, is to do HARD reset. Atleast it's working fine now in ''MultiTouch Visualizer 2''. Haven't tried in games.
:good:
Note: This will return your device to its original factory settings(all the data from internal storage will be removed).
- With the phone turned off, press and hold the Volume Down key;
- With the Volume key held down, press and release the Power key;
- Release the Volume down key;
- Press the Volume down key twice to highlight FACTORY RESET/CLEAR STORAGE;
- Press and release the Power key;
- Press the Volume up key to factory reset the handset;
The phone is restored to factory settings.
:good:
EDIT: GOSH, I'm sick of trying every freaking thing. Doesn't work with Hard reset!!!!
---------- Post added at 10:21 PM ---------- Previous post was at 09:47 PM ----------
The problem is inside HTC's kernel, so we can't really do anything about it.
And I think I will go for a custom kernel, because HTC will take it's time to fix this and realese update.
Cheers.

Luckyone199 said:
Solution, I think, is to do HARD reset. Atleast it's working fine now in ''MultiTouch Visualizer 2''. Haven't tried in games.
:good:
Click to expand...
Click to collapse
I tried a hard reset 1000 times and it doesn't work. I just think, the htc developers are noobs lvl infinity and the devs on xda are real pro's
We have to wait until htc releases the kernel source and the xda devs fix this bug
Sent from my HTC Incredible S using xda app-developers app

Any news? I'm getting pretty annoyed with this problem, because i can't write on Smart Keyboard Pro.

Yup. I'm facing this bug too. YOU'RE NOT ALONE.
Sent from my potato chips using xda boost

Any news on the touchbug yet?
I'm experiencing the same problem.
When I type fast (with two fingers) in Wahatsapp or SMS, the keyboard starts acting weird.
On a HTC Rhyme with ICS and Sense 3.6 (frow htcdev.com) everything runs smoothly. (same processor and resolution as htc incredible s).
So it's bug specific on HTC Incredible S ICS/Sense 3.6 software.
Has anyone received news yet or contact with htc about this? It's pretty annoying and I would think that HTC should issue a patch to resolve this.

hotdenio said:
I'm experiencing the same problem.
When I type fast (with two fingers) in Wahatsapp or SMS, the keyboard starts acting weird.
On a HTC Rhyme with ICS and Sense 3.6 (frow htcdev.com) everything runs smoothly. (same processor and resolution as htc incredible s).
So it's bug specific on HTC Incredible S ICS/Sense 3.6 software.
Has anyone received news yet or contact with htc about this? It's pretty annoying and I would think that HTC should issue a patch to resolve this.
Click to expand...
Click to collapse
With arhd, xs-kernel and v6 supercharger, i'm not facing the problem anymore.

MrToastbrot said:
With arhd, xs-kernel and v6 supercharger, i'm not facing the problem anymore.
Click to expand...
Click to collapse
I think so, or maybe it is less apparent
Sent from my Nexus 7

The problem is in kernel, so i guess if you put a custom kernel this bug will disappear.
Edit : nop, that didn't work for me.

Go for gingerbread, ics has to much issues for me, just like jb.
Sent from my HTC Incredible S using xda app-developers app

Silversniper said:
Go for gingerbread, ics has to much issues for me, just like jb.
Sent from my HTC Incredible S using xda app-developers app
Click to expand...
Click to collapse
False. Just flashed Nik Project X v4.1 with HTC Sense 4.0.
Multi-touch bug is gone, even though they use stock kernel. I guess the problem was in HTC Sense 3.6.
P.s. ROM is working flawlessly. Best rom I've ever had. :laugh:

I'm also facing the multi touch prob using niks project x v4.0, with lost prophets Kernel
Cheers
Sent from my HTC Incredible S using xda app-developers app

I'm getting tired. And anything I could say now is - ''What the f**k?''
Multitouch was working on Nik Project X v4.1 fine until.. I don't know really.
And now, when I want to get it working again, I randomly change some settings or force close some apps(for example ''Media Link HD setup'') it starts working again, but, unfortunately - not forever.
Trying to find solution, but can't find any.
Begging for solution... :laugh:
Peace!
p.s. Multitouch is working in some apps. For example N.O.V.A 3, but not working in other apps, like Jet Car Stunts, Gangstar Rio: City of Saints, MultiTouch Visualizer 2 etc. Zooming in browsers and something like that works fine.

can't type "P" or "0" on keyboard. dead spot on touch screen.
I can't type the alphabet "P" or "0" on sense 3.6 Rom.
and on sesne 4 rom, can't type "0" ( P is working)
With show touches & pointer location from dev option, clearly about 1 cm of touch screen is not working. (no touch show beyond 1 cm of right margin.)
take a look at pic, pls.
Because of dead spot, I can't type alphabet "P" and "0" and can't play some game like https://play.google.com/store/apps/...DEsImNvbS5lY2FweWNzdy5vbmV0b3VjaGRyYXdpbmciXQ..

drcrazy91 said:
I can't type the alphabet "P" or "0" on sense 3.6 Rom.
and on sesne 4 rom, can't type "0" ( P is working)
With show touches & pointer location from dev option, clearly about 1 cm of touch screen is not working. (no touch show beyond 1 cm of right margin.)
take a look at pic, pls.
Because of dead spot, I can't type alphabet "P" and "0" and can't play some game like https://play.google.com/store/apps/...DEsImNvbS5lY2FweWNzdy5vbmV0b3VjaGRyYXdpbmciXQ..
Click to expand...
Click to collapse
Have you tried changing kernels?

Random Reboots?

Not sure what is going on. I experienced it on stock rom, and I'm also experiencing it on Android Revolution HD Rom.
It seems like whenever the phone is tasked by an app opening or closing, I experience a random reboot.
Anyone know whats causing it?

Yeap me too, but only after closing final fantasy IV.. Dunno what's the deal here
°° no rest for the wiCKed °°

anyone?

S_Dot said:
anyone?
Click to expand...
Click to collapse
Me, too, but I didn't catch any regularity, yet.
I am on stock ROM.
One time a had a crash report from htc, but most times I only realize it, because I have to re-enter my pin.
Today I realised, that long-pressing the power-button does restart the phone without any other input.
Maybe it's that?

I'm using developer edition and have been suffered from heavily random reboot.
The phone rarely rebooted (2 or 3 times) while I was using it but just kept rebooting if I left it idle (5 reboots in 20 mins). I cannot reproduce the reboot because it was so random. One day, it just kept me annoying by rebooting itself more than a dozen time. The other day it just went super smooth and stable. This reboot has been happening on both completely stock and custom (Rom, kernel).
Anyone got a clue?

If you know a certain action is causing the reboot get a logcat, there's an app called catlog on the play store. Press record, repeat the action, after it reboots get the logcat and post it here
Sent from my Tricked out HTC One

Same issue here! I'm using TrickDroid though. Has anyone tried this with 4.2.2 to see if it still happens?

Sylpher said:
Same issue here! I'm using TrickDroid though. Has anyone tried this with 4.2.2 to see if it still happens?
Click to expand...
Click to collapse
I'm using Android Revolution ROM on 4.2.2., same thing. It happens once in a blue moon, and it's only on wake when I hit the power button. The whole phone freezes and reboots.
Is everyone here on the Developer's Edition?

I'm having the same issue, dev edition stock except recovery, and root. Some days it reboots, other days its fine. Not exactly sure whats up w/ that
Sent from my HTC One

I'm gonna go ahead and bump this, seeing as I'm facing the same issue on my 2 day old device.
At first I thought it was a problem with 4.1.2, but even after upgrading to 4.2.2 the issue is still there.

ViperOne 2.1.0 the same trouble
Hello,
I confirm the same problem on ViperOne ROM. I have tried out ElementalX 3.4 and Bulletproof kernels. But it seems to be kernel independent.
I attached the log, my configuration is as described in my signature except that I use Bulletproof kernel right now.
It is quite frustrating cause I just wanted to play a movie on my TV using Hama MHL cable, but everytime I connect my phone to the adapter the phone reboots, then it gets stuck on HTC logo, then I have to reboot it manually holding power button. I am also experiencing a reboot right after phone boots up.
This is such a serious issue that I am thinking of going back to stock kernel, but I am not sure if it will help
Any hints?
EDIT: I just installed stock kernel, but still the same, really does not seem to be a problem of the kernel
EDIT2: still trying to find the out whats the problem, I did a clean reinstallation of everything, even w/o using Titanium Backup, well, MHL still causes reboots

[Q] Need to wait a while for the screen to turn on

Hey,
So my dad isnt exactly satisfied with the custom ROM I flashed on his device, he needs to wait about 4 - 5 seconds (!) when theres an incoming call for the screen to turn on. The ringtone will keep on going off during that few seconds, but the screen will be black.
So I tested it on my Nexus 4, and no such issue has been spotted by me. Although, on his device, no matter how many times I tried, the issue was never gone and I had to wait a couple of seconds for the screen to turn on so I could see who's calling.
I'm not sure whether it is a kitkat issue or not, I tried 2 different roms, first BeanStalk, and now CyanFox, both had the same issue.
I also tried to flash CM10.1, but the keyboard kept on crashing after a fresh flash, wipes didnt help (maybe someone could give me a hand here?).
Another question is, where can I find some good call recording app? the ones from the play store aren't good, they only record one side of the call, never both
tl;dr:
is there some setting that I should change for the screen to turn on quicker when theres an incoming call on kitkat?
what to do if I want to downgrade from kitkat to jellybean?
is there some GOOD call recorder app around?
thank you

Pawelss said:
Hey,
So my dad isnt exactly satisfied with the custom ROM I flashed on his device, he needs to wait about 4 - 5 seconds (!) when theres an incoming call for the screen to turn on. The ringtone will keep on going off during that few seconds, but the screen will be black.
So I tested it on my Nexus 4, and no such issue has been spotted by me. Although, on his device, no matter how many times I tried, the issue was never gone and I had to wait a couple of seconds for the screen to turn on so I could see who's calling.
I'm not sure whether it is a kitkat issue or not, I tried 2 different roms, first BeanStalk, and now CyanFox, both had the same issue.
I also tried to flash CM10.1, but the keyboard kept on crashing after a fresh flash, wipes didnt help (maybe someone could give me a hand here?).
Another question is, where can I find some good call recording app? the ones from the play store aren't good, they only record one side of the call, never both
tl;dr:
is there some setting that I should change for the screen to turn on quicker when theres an incoming call on kitkat?
what to do if I want to downgrade from kitkat to jellybean?
is there some GOOD call recorder app around?
thank you
Click to expand...
Click to collapse
If you still on cm10.1 then download keyboard from market and you are good to go Also stock 4.1.2 has this lag issue when incoming call its pretty annoying really

tuncay_93 said:
If you still on cm10.1 then download keyboard from market and you are good to go Also stock 4.1.2 has this lag issue when incoming call its pretty annoying really
Click to expand...
Click to collapse
hey, thanks for your reply
actually no, STOCK 4.1.2 didnt have this issue, it started to show when I flashed 4.4.2 on it, is there some sort of fix for this or do I have to downgrade to JB? I'd rather stick to KK as I prefer it more.
on the other hand my dad hated google hangouts and he wants the stock messaging app back, I guess I can only go with CM
also I cant install a keyboard from the market, because I cant even log in to my google account, I cant get through the setup without a few things crashing over and over again, every second or so. the keyboard doesnt even show up

delete the latinIme.apk from the zip file you are trying to flash and substitute it with one from the other roms you tried flashing.
I know how to control the delay with which the ringer starts but not screen :s
These commands I think only help when call ends but it doesn't hurt to try, add them (or check the values if already present)
to build.prop in zipfile before you flash it
Code:
ro.lge.proximity.delay=5
mot.proximity.delay=5
I am on kitkat right now and have no lag issue...have you tried changing kernel?

Rudjgaard said:
delete the latinIme.apk from the zip file you are trying to flash and substitute it with one from the other roms you tried flashing.
I know how to control the delay with which the ringer starts but not screen :s
These commands I think only help when call ends but it doesn't hurt to try, add them (or check the values if already present)
to build.prop in zipfile before you flash it
Code:
ro.lge.proximity.delay=5
mot.proximity.delay=5
I am on kitkat right now and have no lag issue...have you tried changing kernel?
Click to expand...
Click to collapse
hey, thanks for your reply
I flashed Nameless ROM and surprisingly the lag issue is gone, and due to stripped gapps I flashed, I got the old messaging app back, which is quite the perfect combo, now the only thing I am missing is a good call recording app, is there a chance you can suggest one to me?
thanks again!

Pawelss said:
hey, thanks for your reply
I flashed Nameless ROM and surprisingly the lag issue is gone, and due to stripped gapps I flashed, I got the old messaging app back, which is quite the perfect combo, now the only thing I am missing is a good call recording app, is there a chance you can suggest one to me?
thanks again!
Click to expand...
Click to collapse
Still havent tried nameless but i did red the thread about it. Seems everyone likes it. It should be good

tuncay_93 said:
Still havent tried nameless but i did red the thread about it. Seems everyone likes it. It should be good
Click to expand...
Click to collapse
well I tried it out, the rom is nice and all, but my phone is extremely slow, the lag issue with phone calls is back, sometimes turning the screen off is impossible, or takes up to 2 minutes (!). turning it back on isnt much better either, I dont know what the problem is, the same thing happened on the BeanStalk ROM so I assume it isnt a software issue, but a hardware one, do you have any ideas what could be the problem and how can I solve it?

I want to tell you my experience about custom roms.
I don't know if you tried this combo: CM11 + kicos kernel (modified iodak's kernel) + minimal PA gapps
I works for me very well.

LGaljo said:
I want to tell you my experience about custom roms.
I don't know if you tried this combo: CM11 + kicos kernel (modified iodak's kernel) + minimal PA gapps
I works for me very well.
Click to expand...
Click to collapse
yeah, but shouldnt all the 4.4.2 ROMs be quite snappy? doesn't kitkat reduce the hardware requirements? why would JB work fine (or so I think, I'll go back to stock in a few mins and see) and KK be laggy as hell?
I've got a theory, I'm not a hardware guy and I dont know if I'm right or not, but:
could be that one of the cores is damaged and the system tries to switch some tasks to the damaged core (if android handles different cores the way I think) and that core doesnt really work the way it should, causing the entire system to work like a granny?

Pawelss said:
well I tried it out, the rom is nice and all, but my phone is extremely slow, the lag issue with phone calls is back, sometimes turning the screen off is impossible, or takes up to 2 minutes (!). turning it back on isnt much better either, I dont know what the problem is, the same thing happened on the BeanStalk ROM so I assume it isnt a software issue, but a hardware one, do you have any ideas what could be the problem and how can I solve it?
Click to expand...
Click to collapse
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.

tuncay_93 said:
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
Click to expand...
Click to collapse
That still the best sollution for him - optimized kernel with stable ROM. He probably isn't techno freak?

tuncay_93 said:
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
Click to expand...
Click to collapse
could be, however, it isnt only for the power button, when the screen is off and a call is coming, it needs a few seconds for the screen to turn on, after the call is done, the system is all choppy and laggy. Turning the screen off after that is also nearly impossible, due to power button malfunction. I went back to stock for now and I'll see if the lag is gone, if it isnt, then its probably a hardware issue.
edit:
yeah, I'm on stock 4.1.2 and the issue isnt gone.
crap.

sounds like a problem in the timing the processor uses for scaling frequencies...
hav no idea what could be causing it unless you have some kernel tweak app and set wrong values

Have you tried clean flashing the Roms you installed? Have you Factory-Reset, Cleared cache, cleared Dalvik cache, and maybe did a system partition format before flashing?
Inviato dal mio GT-P3110 utilizzando Tapatalk