Database Info

[Q] Phone turning off randomly twice a day using Android Revolution 1.1.7

Here we go:
As of update 1.1.7 of mike1986's Android Revolution ROM I experienced a strange issue:
My phone just randomly turns off at least two times a day. I'm not talking about a reproduceable error, since my phone only showed an unresponsive black screen (waking it up by pressing the power button didn't work, too), when I was carrying it in my pocket. I thought at first it was an SOD issue like with the early Android builds for the HD2. But today my phone just literally turned off before my own eyes while I was checking my mail. I wasn't even able to turn it on anymore without performing a battery pull. I was confronted with this issue the third time just a couple of minutes ago. I even did a full wipe and reflashed the ROM (I know, I'm just a Junior Member, but trust me, I know how to this properly), before this happened - again.
Should I just revert to an older version of the ROM or wait for an update? I don't want to just sit around and do nothing about it.
Any help is much appreciated!

Please search the Android Revolution Thread before posting next time.
A lot of people are having these issues. Just install a different kernel and that should fix the problem or go back to 1.1.5 or 1.1.6. I'm waiting for 1.1.8

adam_deluxe said:
Here we go:
As of update 1.1.7 of mike1986's Android Revolution ROM I experienced a strange issue:
My phone just randomly turns off at least two times a day. I'm not talking about a reproduceable error, since my phone only showed an unresponsive black screen (waking it up by pressing the power button didn't work, too), when I was carrying it in my pocket. I thought at first it was an SOD issue like with the early Android builds for the HD2. But today my phone just literally turned off before my own eyes while I was checking my mail. I wasn't even able to turn it on anymore without performing a battery pull. I was confronted with this issue the third time just a couple of minutes ago. I even did a full wipe and reflashed the ROM (I know, I'm just a Junior Member, but trust me, I know how to this properly), before this happened - again.
Should I just revert to an older version of the ROM or wait for an update? I don't want to just sit around and do nothing about it.
Any help is much appreciated!
Click to expand...
Click to collapse
Hi,
This is a kernel issue.
Try flashing the kernel in my sig using CWM.

Dacoit said:
Please search the Android Revolution Thread before posting next time.
A lot of people are having these issues. Just install a different kernel and that should fix the problem or go back to 1.1.5 or 1.1.6. I'm waiting for 1.1.8
Click to expand...
Click to collapse
I did. Thing is, I'm still a Junior Member, so I'm not allowed to post the experience I had or ask questions about it. I know, it's a ROM-specific question which belongs in the thread of the aforementioned ROM, but asking someone out of the to post it for me would have been about just as much annoying. Still, I'm sorry.
Still, it seemed somehow that no one reported the exact situation, as there were different solutions proposed. But - as I said - I couldn't even add anything to the discussion, since I'm not allowed.
I hope, it didn't disturb you too much.
Regards

Thanks for the quick (and hopefully helpful) reply.
I have to wait and see, if it works for me, but if you say so, there must be something true about it.
Anyway, thanks again!
Regards
EDIT: The UI runs pretty smoothly now and my WIFI and mobile data are not lagging anymore. It MUST have been the kernel.

adam_deluxe said:
Thanks for the quick (and hopefully helpful) reply.
I have to wait and see, if it works for me, but if you say so, there must be something true about it.
Anyway, thanks again!
Regards
Click to expand...
Click to collapse
Hi,
It worked for me,and I've had no black screens since.

Yes, reverting to RC Mix 2.3 solves many glitches IMO. Should do the trick while waiting for a better version.

burned into the screen?

Hi, My problem is that sometime stuff get's bruned into the screen. If i reboot my device the problem is solved but what happends if i don't do a reboot?
Thanks in advance, P.S i will try to get a img so i can show you guys what i mean.

Hi.
I made a thread about it some time ago, but apparently not many of us have this problem. Anyway, I also had it, but it goes away after some time with screen off. Also I've disabled auto brightness (left 25%) and I haven't noticed it coming back for quite a while.

I have started noticing a little bit of screen burning, mainly with the clock, but that's about it.

havent faced such problem, It would be great if you post a screenshot

jullejul said:
Hi, My problem is that sometime stuff get's bruned into the screen. If i reboot my device the problem is solved but what happends if i don't do a reboot?
Thanks in advance, P.S i will try to get a img so i can show you guys what i mean.
Click to expand...
Click to collapse
I wonder if you try using the fast reboot application from the market whether that would be a faster and simpler way to resolve the problem than a full device reboot (saver battery too)
Swyped from my Desire S using XDA Premium

Okay i will try to take a SS but it really hard to see it on the camera because i failed at the gym and dropped my ds on the floor and the screen cracked
ben_pyett said:
I wonder if you try using the fast reboot application from the market whether that would be a faster and simpler way to resolve the problem than a full device reboot (saver battery too)
Click to expand...
Click to collapse
Okay will try that, i often get it when i read on the web. the zoom in and zoom out buttons get stuck

Nexus S touchscreen calibration?

Hey guys, is there a way to calibrate the nexus s touchscreen? Sometimes it is unresponsive...

Anybody?

unresponsive? Maybe you just need to make a good wipe and fresh instal of your rom/kernel..
no?

I don't think so because it happened since gingerbread 2.3.6, and now i have brainmaster's stock 4.0.3 with eugene's kernel and still happens sometimes... and i did a full wipe before flashing ICS.

i used the nook screen calibrator from the market...it worked fine for me
sent from Ice Cream Infused NS4g

I'll give it a shot and let you know, thanks. BTW, on the market i've found Nook Screen Recalibrate, it is the same as you used, right?
Edit: I've tried the app and it managed to improve the touchscreen response, but didn't solve my problem at all (phantom touches). But they're almost gone. Is there any other app like that?

jedijos said:
I'll give it a shot and let you know, thanks. BTW, on the market i've found Nook Screen Recalibrate, it is the same as you used, right?
Edit: I've tried the app and it managed to improve the touchscreen response, but didn't solve my problem at all (phantom touches). But they're almost gone. Is there any other app like that?
Click to expand...
Click to collapse
Found anything else mate? I ran NSR, still have phantom touches

JohnSteveDoe said:
Found anything else mate? I ran NSR, still have phantom touches
Click to expand...
Click to collapse
Same thing with mine. The phantom touches are only vertical but the device has become unusable.
I'm installing Cyanogenmod 10 now. Let's see if that helps.

gcaliari said:
Same thing with mine. The phantom touches are only vertical but the device has become unusable.
I'm installing Cyanogenmod 10 now. Let's see if that helps.
Click to expand...
Click to collapse
It didn't help. touch seems to work but if I hold the touch the touch sensor goes crazy and starts touching several random points in the screen, all in the same vertical as the place I touch.
Does anyone have any suggestions?

gcaliari said:
It didn't help. touch seems to work but if I hold the touch the touch sensor goes crazy and starts touching several random points in the screen, all in the same vertical as the place I touch.
Does anyone have any suggestions?
Click to expand...
Click to collapse
Replace the screen, sounds like a physical issue to me.

polobunny said:
Replace the screen, sounds like a physical issue to me.
Click to expand...
Click to collapse
Could be but since the problem started after I ran the Nook Screen Recalibrate my first suspicion was the program.
I'm trying several different solutions from other threads and none seems to work:
- TouchRecalibrate.apk
- calibration.ini
- ts_calib-signed.zip

gcaliari said:
Could be but since the problem started after I ran the Nook Screen Recalibrate my first suspicion was the program.
I'm trying several different solutions from other threads and none seems to work:
- TouchRecalibrate.apk
- calibration.ini
- ts_calib-signed.zip
Click to expand...
Click to collapse
If you wipe everything and flash a rom, there's no way it's a software issue.

polobunny said:
If you wipe everything and flash a rom, there's no way it's a software issue.
Click to expand...
Click to collapse
Well, it's working now. I don't know exactly what soved the problem but in my despair I re-executed all procedures and something must have gone right. Wish I could tell what fixed it for others but I really don't know.
Thanks for the help polobunny

Same problem
Hey,
I got the same problem,
so I did some research, I found out that there lots of people got the same problem.
A wipe, or install an other kernel or rom will work, but it will for some reason return.
For some models it's enough to install a kernel with some other touchscreen preference. One problem, it will only work on android 2.3 there are not jet other newer kernels published
But 99% its not a screen problem, so u can buy a new screen and replace it with no success. But most of the people say it's a hardware problem. So modify the touchscreen driver.
sorry, bad english​

[Q] SK4G dropping keystrokes randomly

I've been looking around for any mentions of this for a while now, but i only found vague mentions of it a while back. I thought it'll eventually get fixed in one of the custom roms.
I'm starting to think this is an isolated case since no one is mentioning it at all. (or it's me going crazy. i hope not.)
When trying the key test in the recovery, it doesn't seem to drop anything at all, but when booting android, it drops whenever i type fast enough.
Can anyone confirm whether or not their phone drops keys randomly when typing?

khaldood said:
I've been looking around for any mentions of this for a while now, but i only found vague mentions of it a while back. I thought it'll eventually get fixed in one of the custom roms.
I'm starting to think this is an isolated case since no one is mentioning it at all. (or it's me going crazy. i hope not.)
When trying the key test in the recovery, it doesn't seem to drop anything at all, but when booting android, it drops whenever i type fast enough.
Can anyone confirm whether or not their phone drops keys randomly when typing?
Click to expand...
Click to collapse
It is fixed in my cm merged v2.0.0
Sent from my SPH-D710 using xda premium

i am using CM merged 2.0.0 and it's still dropping.
but if it's really fixed, maybe it's something i installed? will do a clean install and report back

I know that the stock ROM did this (KG2, and KJ2), and my install of GOv2 does this, as well.
I'm just waiting for some extra time to get CMv2 installed.

afr33sl4ve said:
I know that the stock ROM did this (KG2, and KJ2), and my install of GOv2 does this, as well.
I'm just waiting for some extra time to get CMv2 installed.
Click to expand...
Click to collapse
this problem can be fixed from what i've read by using NXD's kernel as well

Formatted /system, dalvik, cache, deleted userdata, reinstalled CM merged 2.0, still drops.

try flashing nxd's kernal over what you already have it might work
https://carbon.flatlan.net/nxd/Bali_SK4G_20120520_nxd.zip

HewettBR said:
try flashing nxd's kernal over what you already have it might work
https://carbon.flatlan.net/nxd/Bali_SK4G_20120520_nxd.zip
Click to expand...
Click to collapse
My rom has nxds kernel installed by default...
Sent from my SPH-D710 using xda premium

ReActiveDisorder said:
My rom has nxds kernel installed by default...
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
yeah... just figured id offer the only advice i could, aside from his device being messed up. i think its still worth a shot

interestingly enough, the Samsung Epic 4G also had dropped keystrokes issues. But this one seems to be a different problem.
On the SK4G, keys are dropped at random when typing fast.
on the E4G, keys are dropped when repeating the same character quickly (eg. hello, according to that post anyway)
HewettBR said:
yeah... just figured id offer the only advice i could, aside from his device being messed up. i think its still worth a shot
Click to expand...
Click to collapse
well, thanks for the attempt, but it's still the same. I doubt it's hardware-related, since the keytest in recovery isn't dropping keys.

Yeah, the Epic 4G was WAY worse lol. I actually contacted the dev. that pretty much fixed the problem on the Epic, and he was curious and took a look at the SK. He said indeed that the SK shouldn't suffer nearly the same keyboard woes. But he did make a little patch for us anyway, to try and improve some other stuff, but it was never put into a kernel I don't think.
I do get a missed keystroke on this device every now and then, but not too often.

yogi2010 said:
Yeah, the Epic 4G was WAY worse lol. I actually contacted the dev. that pretty much fixed the problem on the Epic, and he was curious and took a look at the SK. He said indeed that the SK shouldn't suffer nearly the same keyboard woes. But he did make a little patch for us anyway, to try and improve some other stuff, but it was never put into a kernel I don't think.
Click to expand...
Click to collapse
Sounds good. I wonder what happened to that patch though, and whether or not it worked.
yogi2010 said:
I do get a missed keystroke on this device every now and then, but not too often.
Click to expand...
Click to collapse
Well, i noticed it happens VERY randomly. sometimes it's just once every 10 messages in gtalk, sometimes, it hits twice or thrice in a single message. drives me crazy :/

Lol, I hear ya. That patch was posted, possibly even in the thread you linked, so it might still be there. Sduvick didn't feel motivated to add it to a kernel, and even tho it is simple, my patching skills were limited, so it never got tested.
I'll see if I can find where the interaction took place, and see if the patch link is still good.

This is me typing as fast as I can I drop keystrokes all the tim but it only seems to be the e the g and sometimes t I think its a hardware problem I'm not looking at the screen at all so you can see where the keystrokes might be dropping also I've had sidekicks since 2007 so I'm used to the full keyboard and typing extremely fast on it lol lalalalalala typey typey typey...
And now a few 4 letter words typed 20 tmes in a row watch for drops
Time time time time time time time time time time tim time time time time time time time time time
Ding ding ding ding din ding ding ding ding ding digng ding ding ding ding ding ding ding ding ding
Dirt dirt dirt dirt dirt dirt dirt dirt dirt dirt dirt dirt dirt dirt dirt dirt dirt dirt dirt dirt
And there you have it looking back on this post now I dropped a total of 2 e's and 1 g.
Currently running reactives cm6 merge v 2.1.0
Sent from my SGH-T839 using XDA

as i've said, it drops them VERY randomly. And for some reason, it doesn't drop, or at least as much as during regular use, when you start testing for drops. That, or maybe we're testing it wrong.
In my case, I'm getting drops on seemingly all of the keys. Sometimes on T. Sometimes Space. Sometimes even Return. etc.
Can anyone else test in the recovery key test under advanced just to make sure it's not hardware related?

HewettBR said:
this problem can be fixed from what i've read by using NXD's kernel as well
Click to expand...
Click to collapse
It's worth a try, although I still don't see how the changes I made would alleviate dropped keystrokes. The printk logging statements have close to zero overhead compared to the rest of the Android stack.

yogi2010 said:
Yeah, the Epic 4G was WAY worse lol. I actually contacted the dev. that pretty much fixed the problem on the Epic, and he was curious and took a look at the SK. He said indeed that the SK shouldn't suffer nearly the same keyboard woes. But he did make a little patch for us anyway, to try and improve some other stuff, but it was never put into a kernel I don't think.
I do get a missed keystroke on this device every now and then, but not too often.
Click to expand...
Click to collapse
If you can find the patch, I will try to integrate it into my kernel.

khaldood said:
i am using CM merged 2.0.0 and it's still dropping.
but if it's really fixed, maybe it's something i installed? will do a clean install and report back
Click to expand...
Click to collapse
Just to be sure, would you check what kernel version shows up under Settings -> About Phone?
I'm wondering if perhaps sometimes, the kernel is failing to flash.

nxd said:
Just to be sure, would you check what kernel version shows up under Settings -> About Phone?
I'm wondering if perhaps sometimes, the kernel is failing to flash.
Click to expand...
Click to collapse
2.6.32.9-Bali_SK4G_20120205.nxd

nxd said:
If you can find the patch, I will try to integrate it into my kernel.
Click to expand...
Click to collapse
good news, the post was easy to find, and the patch is still there!
http://forum.xda-developers.com/showpost.php?p=16096212&postcount=79
this was back in the days of KD1, but i hope it could still be of use to us.

[Q][H]Touchscreen issue

Hi All,
During the last couple of weeks, with different ROMs I've been experiencing some touch screen issues. I feel like there is a 0.5s delay/lag on the touches which makes using the phone annoying. I can barely type and touches are not really accurate.
Not sure if there is any good app for testing the touchscreen, but I tried one (Test Touch) and as far as I can see, touches are not registered or are intermittently registered when fast touching the screen. (See Video). When I slowly drag the finger, a continuous line is traced.
I couldn't find anyone else having the same issue hence I'm posting this. Thanks for the help.
Current ROM: Temasek's UNOFFICIAL Build, 10.1, CM 12.1 .
Stock kernel.
Edit: Ram use is always lower than 50% and CPU usage is low.

Nikouy said:
Hi All,
During the last couple of weeks, with different ROMs I've been experiencing some touch screen issues. I feel like there is a 0.5s delay/lag on the touches which makes using the phone annoying. I can barely type and touches are not really accurate.
Not sure if there is any good app for testing the touchscreen, but I tried one (Test Touch) and as far as I can see, touches are not registered or are intermittently registered when fast touching the screen. (See Video). When I slowly drag the finger, a continuous line is traced.
I couldn't find anyone else having the same issue hence I'm posting this. Thanks for the help.
Current ROM: Temasek's UNOFFICIAL Build, 10.1, CM 12.1 .
Stock kernel.
Edit: Ram use is always lower than 50% and CPU usage is low.
Click to expand...
Click to collapse
You're not the only one- I opened a thread about this. Seems as something happened as people updated to android 5.x as did with me.
Hopefully someone can figure something out!
Seems more like an input lag- like you mentioned. Really annoying and makes it hard to type fast or use swype function.

You_got_owned123 said:
You're not the only one- I opened a thread about this. Seems as something happened as people updated to android 5.x as did with me.
Hopefully someone can figure something out!
Seems more like an input lag- like you mentioned. Really annoying and makes it hard to type fast or use swype function.
Click to expand...
Click to collapse
I've been having this issue too! I thought it was the ROM, but I am on my second one now with the same touch lag . I didn't have the issue in 5.0, though. I might consider downgrading and hope that that fixes my issue. Any help on this would be much appreciated

guih said:
I've been having this issue too! I thought it was the ROM, but I am on my second one now with the same touch lag . I didn't have the issue in 5.0, though. I might consider downgrading and hope that that fixes my issue. Any help on this would be much appreciated
Click to expand...
Click to collapse
Happy to know I am not the only one having this issue , good that we are on the same boat.
I'm travelling in a few days and can't go abroad with the phone in this "working" conditions so I will have to downgrade for sure. Any 5.0 ROM to recommend? A solution for 5.1 would be better

haha I was on Blisspop for a long time before moving to 5.1, it's a fantastic ROM!

guih said:
haha I was on Blisspop for a long time before moving to 5.1, it's a fantastic ROM!
Click to expand...
Click to collapse
I flashed Slim ROM, touches delay improved a bit but I was experiencing some lag on the hardware keys.
I just flashed last bacon firmware (from April 09) and RobbieL811 ROM and seems to be running smoothly, I wonder if it was a firmware issue. Thoughts?

Right, I have the same bloody problem, and I'm seriously thinking of going back to kit kat. What the hell happened, it worked perfectly. Does everybody have an unlocked bootloader? COS12 worked ok, lagged when hot, only after I unlocked the bootloader did it all go to ****. I just hope it'll go back to normal on KK and it isn't a permanent thing now..

Infinityyy said:
Right, I have the same bloody problem, and I'm seriously thinking of going back to kit kat. What the hell happened, it worked perfectly. Does everybody have an unlocked bootloader? COS12 worked ok, lagged when hot, only after I unlocked the bootloader did it all go to ****. I just hope it'll go back to normal on KK and it isn't a permanent thing now..
Click to expand...
Click to collapse
I have an unlocked bootloader and have moved from 11S to 12S and find its a lot better. I've seen people say they find the update better and some who have issues but your boot loader shouldnt really come into it. How did you update, what did you do since unlocking your bootloader?

gsmyth said:
I have an unlocked bootloader and have moved from 11S to 12S and find its a lot better. I've seen people say they find the update better and some who have issues but your boot loader shouldnt really come into it. How did you update, what did you do since unlocking your bootloader?
Click to expand...
Click to collapse
Went with COS12 for a while, then tried a 5.1 rom and it started going down from there. COS12 lagged a lot when the phone was charging, it got very hot for a while, and then cooled down. I don't know why touchscreen issues started happening, it worked ok for some time after installing 5.1, then for instance the settings app started scrolling slowly, the notification panel as well, some touches stopped being registered.. It's a weird issue, because it's not lagging, like skipping or so, but mostly it feels like the phone is in slow motion.

guih said:
I've been having this issue too! I thought it was the ROM, but I am on my second one now with the same touch lag . I didn't have the issue in 5.0, though. I might consider downgrading and hope that that fixes my issue. Any help on this would be much appreciated
Click to expand...
Click to collapse
Infinityyy said:
Went with COS12 for a while, then tried a 5.1 rom and it started going down from there. COS12 lagged a lot when the phone was charging, it got very hot for a while, and then cooled down. I don't know why touchscreen issues started happening, it worked ok for some time after installing 5.1, then for instance the settings app started scrolling slowly, the notification panel as well, some touches stopped being registered.. It's a weird issue, because it's not lagging, like skipping or so, but mostly it feels like the phone is in slow motion.
Click to expand...
Click to collapse
Same happens to mine.
I flashed 3 different ROMs today, 5.1 and 5.0, it was working fine for a few hours with one of them but after that It started with serious problems, to the point of nearly not registering any touch. After a reboot it improved a bit but it makes the phone unusable. I'm flying abroad in less than 12hrs and really need the phone.
Flashing a stock ROM or going to kit kat are the only options I see now.
Edit: Here I found some useful post, they state it's hardware not software.

Nikouy said:
Same happens to mine.
I flashed 3 different ROMs today, 5.1 and 5.0, it was working fine for a few hours with one of them but after that It started with serious problems, to the point of nearly not registering any touch. After a reboot it improved a bit but it makes the phone unusable. I'm flying abroad in less than 12hrs and really need the phone.
Flashing a stock ROM or going to kit kat are the only options I see now.
Edit: Here I found some useful post, they state it's hardware not software.
Click to expand...
Click to collapse
we're not alone man, multiple threads are popping up with people suffering from similar issues, including on reddit: http://www.reddit.com/r/oneplus/comments/33ky0u/open_post_to_oneplus_with_all_our_love_and/

I am having the same severe issues as well.
The nightmare begun after the 05Q update.
Ever since that update, no matter what I've tried, the touch problem is here.
I've tried numerous Roms + kernels combinations with no use.
OP support was trying twice to reset my phone to full factory reset to both Oxygen & CM11s with no use.
That is so frustrating.

i have the same problem, but only when i go outside and the weather is nice