Hey everyone, I'm having a weird issue with my GS3 SCH-I535. On any AOSP rom I try (CM10 Unofficial and Official, AOKP) my physical home button doesnt do anything except wake the screen when it's off. It wont return to my launcher. This doesn't happen on touchwiz roms (Synergy, stock).
Any ideas?
Isn't there an option to change hardware key functions? I'm not on CM10 yet. I will be tonight.
Sent from my SCH-I535 using Tapatalk 2
mustbepbs said:
Isn't there an option to change hardware key functions? I'm not on CM10 yet. I will be tonight.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I saw an option for changing the long press function and tried that, but even long pressing still doesnt work. the button is completely unreactive except for waking the screen
odd.. I tried flashing another kernel but it didnt support CM10 and wouldnt boot, so i reflashed CM10 without full wipe this time and everything works fine now.
my notification bar was also completely empty and that's fixed as well. maybe it just wasnt flashing correctly before?
either way problem solved
exershio said:
odd.. I tried flashing another kernel but it didnt support CM10 and wouldnt boot, so i reflashed CM10 without full wipe this time and everything works fine now.
my notification bar was also completely empty and that's fixed as well. maybe it just wasnt flashing correctly before?
either way problem solved
Click to expand...
Click to collapse
seems like i'm having the same problem. home button only wakes on screen off, also returns to home from notifications and recent apps ... but that's it.
Worked fine on a CM10 nightly 20121004 then flashed the 20121006 and it broke. Reflashed 20121004, and still broke.(just flashed the latest nightly, and still not luck) Tried what seems like all combinations of CM10/Nova Launcher/Trebuchet settings. Tried fixing permissions, wiping cache as well.
It randomly started working again last night, but again stopped working on a reboot.
I feel like this is possibly related; at the same time my Menu (long press) only works when I'm on the Homescreen
I have no legitimate answer to your issue, but on the galaxy players there is a variation in the us/international versions that require a home button/soft key patch built specifically into the kernel. Whether that can point someone to a solution, I don't know...
Sent from my VZW GS3 running Synergy/Trinity/Dark Horse Rises
In case anyone stumbles on this thread;
I seemingly found out how to replicate this on a consistent basis. On reboot, home button will not work (except for above mentioned features)
Using the "Toggle Lock Screen" Notification Drawer Widget once or twice seems to restore complete functionality until next reboot.
I have no idea how/why, but it does seem to work for me.
Related
I am having a major issue with multi touch, and it happened on stock so I don't think it's the rom I'm running (CleanRom Dev).
If I let go of my second touch, the screen loses the first touch location. So, if I am playing Minecraft or Shadowgun, I'll use one touch to move forward, that works, then I'll use one touch to move the screen, that works, but as soon as I let go of that second touch, I stop moving; even though the first touch is still being held on the screen. This happens in any game I play, even with the HTC Gestures off.
I saw a couple other people were having issues with multi touch, but I'm wondering if this is a problem with the kernel or the device. I saw that h8rift mentioned that the kernel's multi touch is a hacky implementation.
Any information is appreciated,
Thanks.
Hmm, appears to have gone away after powering off then back on after turning off HTC Gestures.
Edit:
Issue keeps coming back a few minutes after rebooting.
thebest said:
Hmm, appears to have gone away after powering off then back on after turning off HTC Gestures.
Click to expand...
Click to collapse
Yeah, same here. It took me forever to figure out that it was HTC gestures that was the culprit
Sent from my HTC One X
Same thing happening to me! Been trying all day to figure out why Gameboid was acting weird. Just tried Minecraft and something is definitely up. This wasn't a problem on CleanRom 4.1. Since flashing 4.5 I've been having this issue. Strange that you've had it since stock...
edit: already said
ThisWasATriumph said:
Same thing happening to me! Been trying all day to figure out why Gameboid was acting weird. Just tried Minecraft and something is definitely up. This wasn't a problem on CleanRom 4.1. Since flashing 4.5 I've been having this issue. Strange that you've had it since stock...
Click to expand...
Click to collapse
Hmmm, maybe this should be under CleanRom development then. I may not have had it on stock, I thought I did, but I wasn't on stock for very long
thats the same issue that we were having in AOSP ROMs which is weird since Clean ROM isn't AOSP based.
We fixed it in kernel source though.
rohan32 said:
thats the same issue that we were having in AOSP ROMs which is weird since Clean ROM isn't AOSP based.
We fixed it in kernel source though.
Click to expand...
Click to collapse
Good to know, I was just worried that my phone was jacked up D: lol
Do any of you guys use WidgetLocker? WL is known to cause issues with multitouch; I use WL, and my workaround is to simply disable it, turn my screen off and on, and reunlock with the stock launcher and multitouch works in games again. Then I turn it back on when I'm done.
I use Holo Locker does that cause issues?
samlingx said:
Do any of you guys use WidgetLocker? WL is known to cause issues with multitouch; I use WL, and my workaround is to simply disable it, turn my screen off and on, and reunlock with the stock launcher and multitouch works in games again. Then I turn it back on when I'm done.
Click to expand...
Click to collapse
Wow, that was the problem. Disabling Holo Locker, then turning the screen off and on resolved the problem. Weird....
samlingx said:
Do any of you guys use WidgetLocker? WL is known to cause issues with multitouch; I use WL, and my workaround is to simply disable it, turn my screen off and on, and reunlock with the stock launcher and multitouch works in games again. Then I turn it back on when I'm done.
Click to expand...
Click to collapse
You're a genius! Holo Locker was causing the issue. Thanks so much.
Yeah I had that problem too, it was being caused by HTC Gestures. I just turned it off because I didn't ever see myself using them.
now me too..but..
Hi, i am having the same problem that described in here but with a twist,
i noticed on my HOX on "HTC gestures" check button, it behaves the opposite from what it actually ticked.
I factory reset the device, the problem solved although the "HTC gestures" check button still behaves the opposite, after a while (hour or so) the problem with the touches repeats. i test it with the Multitouch Test app. (the only app installed).
I haven't rooted or changed the rom on the device only updated it with the official updates. last update on November, 4.1.1 , but it was great since so i don't know what triggered this.
please help...
david244 said:
Hi, i am having the same problem that described in here but with a twist,
i noticed on my HOX on "HTC gestures" check button, it behaves the opposite from what it actually ticked.
I factory reset the device, the problem solved although the "HTC gestures" check button still behaves the opposite, after a while (hour or so) the problem with the touches repeats. i test it with the Multitouch Test app. (the only app installed).
I haven't rooted or changed the rom on the device only updated it with the official updates. last update on November, 4.1.1 , but it was great since so i don't know what triggered this.
please help...
Click to expand...
Click to collapse
GOT IT. :silly::silly::silly:. (after alot of factory resets)
The trigger of the bug is If you select:
Personolize -> Lock screen style -> No lock screen
Try it.
you want to uncheck HTC Gestures. it is used for another purpose not what you think it is only used for when your phone is connected to tv.
Recently put ViperXL on and took updates now its ViperXL 3.2.5, put kernel 3.4.10-ElementalX v5.0 vanilla on, flashed radio 2.41.,S-OFF.. Now the screen at times becomes unresponsive like when deleting apps,touch the app , it opens but it wont move or delete.IF I reboot, the screen behaves like it should for an unknown period then problem starts to repeat itself untill rebooting again. Another issue I noticed lately before flashing Viper is in TWRP , especially when rebooting, tapping the reboot button it wont respond for a short period,I might have to tap several times to get reboot to happen. I am wondering if I put too much on the system or might it be something internal?
leesumm said:
Recently put ViperXL on and took updates now its ViperXL 3.2.5, put kernel 3.4.10-ElementalX v5.0 vanilla on, flashed radio 2.41.,S-OFF.. Now the screen at times becomes unresponsive like when deleting apps,touch the app , it opens but it wont move or delete.IF I reboot, the screen behaves like it should for an unknown period then problem starts to repeat itself untill rebooting again. Another issue I noticed lately before flashing Viper is in TWRP , especially when rebooting, tapping the reboot button it wont respond for a short period,I might have to tap several times to get reboot to happen. I am wondering if I put too much on the system or might it be something internal?
Click to expand...
Click to collapse
delay with twrp reboot is normal. issues with custom kernels are pretty common as you are pushing your phone beyond spec and making the phone do things it wasn't really designed to do. imo the screen freezing is due to s2w but i could be wrong. i think you can turn s2w off in elemental, try turning it off and see if you still get freezing.
could be.
DvineLord said:
delay with twrp reboot is normal. issues with custom kernels are pretty common as you are pushing your phone beyond spec and making the phone do things it wasn't really designed to do. imo the screen freezing is due to s2w but i could be wrong. i think you can turn s2w off in elemental, try turning it off and see if you still get freezing.
Click to expand...
Click to collapse
This could be the trick. I tried this morning and so far today there hasn't been a hangup on apps. I tried a couple and everything as usual. But this has been a intermittent thing not knowing when or how it would happen.
Yeah I have found some of the Venom tweaks really affecting responsiveness. For example if you could figure power long press to turn on the flashlight it takes NOTABLY longer to wake the phone. I can see s2w having the same effect
Here I thought I was the only one experiencing this issue. I did a full wipe and format and flashed a bone stock (default configuration) flash of ViperXL to see if that would solve the issue. Screen issue doesn't occur as often as before bit it still happens. I found that if I block the light sensor, the screen begins to behave normally. I don't have a logcat yet but can upload if necessary.
Sent from my HTC One X using xda app-developers app
same problem again.
leesumm said:
This could be the trick. I tried this morning and so far today there hasn't been a hangup on apps. I tried a couple and everything as usual. But this has been a intermittent thing not knowing when or how it would happen.
Click to expand...
Click to collapse
I thought wrong , again, tried this morning just moving an app from home screen to second screen. It will open but unable to move it or delete it from the screen. Rebooted and seems everything is normal again.
Are you using 4x5 Rosie?
Sent from my VENOMized HoxL
area51avenger said:
Are you using 4x5 Rosie?
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
Not really sure, I can't find anything that 4x5 is enabled. S2W I disabled also, this is not a big problem just irritating some times. Things usually start working normal when I reboot system .
You could try increasing the voltage.
ken bentley said:
You could try increasing the voltage.
Click to expand...
Click to collapse
At this point I am not sure I am that smart to be messing with volotage and such on the inside of this thing.
just stopped using a custom kernel. i stopped using them cause of freezing issues.
This is more to bring an issue to light than to ask a question about it, but I recently tested out a few other roms while waiting for a carbonrom update (crackflashing addiction got the better of me, don't judge) and I noticed something on a couple of them that was really worrying. My home button stopped working. I have no idea how it happened, but it wasn't really a big deal since I use the navbar anyway on my phone. That was the really strange thing though. When I activated the navbar the home button on the navbar stopped working. Tried a couple of things and tweaked around a little, but nothing worked. So after restoring my nandroid I installed the carbonrom update and my home button worked again. I was just wondering if anybody else has had this issue with 4.2 roms at all and if so, what do you think could be the culprit behind it? Thanks for the input.
saintsantos said:
This is more to bring an issue to light than to ask a question about it, but I recently tested out a few other roms while waiting for a carbonrom update (crackflashing addiction got the better of me, don't judge) and I noticed something on a couple of them that was really worrying. My home button stopped working. I have no idea how it happened, but it wasn't really a big deal since I use the navbar anyway on my phone. That was the really strange thing though. When I activated the navbar the home button on the navbar stopped working. Tried a couple of things and tweaked around a little, but nothing worked. So after restoring my nandroid I installed the carbonrom update and my home button worked again. I was just wondering if anybody else has had this issue with 4.2 roms at all and if so, what do you think could be the culprit behind it? Thanks for the input.
Click to expand...
Click to collapse
Did you do a full wipe before flashing a new ROM? If not then you should do that next time.
Skyrocket i727 running CM-10.1-20130807 nightly. Apex launcher. On Rogers with UCMC1 radio.
It's running stable with the (big) exception that occasionally (once or twice a day) the four buttons at the bottom (settings/home/back/search) will not respond to any touch. The only way to fix it is to restart the phone. I searched the forums and cannot find an answer to why this might be happening, nor to anyone else having this problem. I have the backlight on these buttons disabled (to save power).
Also, this might be related or maybe not, but on Monday I had a very strange crash. The HOME button wouldn't work, but the BACK button and SETTINGS button did. The notification bar wasn't functioning and no push notifications were coming through. The quick-settings panel was reverted to default, and the buttons within the quick settings panel were completely unresponsive.
Even stranger, Chrome was unresponsive, Maps/Navigation were constantly force-closing, and in general the phone was throwing a massive fit over almost anything I did. I pulled the battery but that didn't help. I was forced to go into recovery mode and perform factory reset, wipe dalvik cache, and reinstall the ROM. This has worked (although a PITA) but the issue I mentioned first (bottom buttons not working) has manifested itself since then.
Any ideas what to do here?
Much appreciated!
Eric
Run the recent nightly. Could be an issue with your rom, although I haven't seen your problem.
I just flashed the most recent nightly a few minutes ago.
Should I go back into recovery and wipe cache and dalvik? (note: When I flashed the ROM through CM Updater / TWRP, it 'optimized' 119 apps... so I think it automatically wiped the cache...?)
curls00 said:
I just flashed the most recent nightly a few minutes ago.
Should I go back into recovery and wipe cache and dalvik? (note: When I flashed the ROM through CM Updater / TWRP, it 'optimized' 119 apps... so I think it automatically wiped the cache...?)
Click to expand...
Click to collapse
You should be ok. I never go back and wipe caches
The original issue is still occurring even on newest nightly. Completely random (using different apps each time - Facebook, Messenger, Youtube, etc...).
Any idea if a setting I can change is causing this?
mtdew said:
Hardware failure.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
LOL time to sell then!
I currently have an N5 which is running PA (4.5 beta2) and Franco (R59) and i seem to come across this issue no matter what version (or combination of versions) i end up using.
The issue - After installing the rom and kernel it will work fine for a week or so and then after that period it will have this issue whereby I press the power button and nothing will happen to the screen, it just stays black but i know the phone is still on because the LED will flash. From this point onwards i usually just reset the phone and then it will work fine for the first maybe 20 mins and then it ends up doing the same thing again.
I know it isnt a problem with the power button itself cause it works totally fine after the phone resets (and im still able to reset the phone using the power button), sometimes the screen will actually power up when i press the button and it shows me my home screen but then fade to a black screen and it just does that over and over again (during that period you cant actually do anything, tried touching screen, volume up+down etc and there is just no response) unless you reset the phone.
any help would be appreciated
It could be one of a few things. Generally it will be an app or a kernel setting. I would recommend ruling out kernel first by flashing ROM without the kernel.
Sent from my Nexus 5 using Tapatalk
Yeah that definitely seems like a kernel issue. Try just flashing the rim by itself as mentioned above. Also what apps do you have install that deal with display stuff, ex. Lock screen notifications, led light etc.?
nym27jrey said:
...Try just flashing the rim...
Click to expand...
Click to collapse
Not sure you want to do that
hi guys, im pretty sure i have found the source of the problem now. I normally have the 'Twilight' app (nothing to do with teenage vampires + werewolves) in the background which softens the colours and dims the screen to a level which is more pleasant for the eyes at night. After uninstalling this it seems as though the problem has gone.
I think the app itself projects an overlay on top of the launcher to dim the screen but sometimes when the app is running and the screen is dimmed it seems to block out (unable to tick) some of the pop-up boxes which some programs throw up. Too bad, i really liked the app too, might just have to email the developer and let him know.
Now on to my next problem, anybody know of another app which does similar? lol
ticketseriously said:
Now on to my next problem, anybody know of another app which does similar? lol
Click to expand...
Click to collapse
Chainfire's C.F. Lumen
OK I was wrong. After uninstalling all the apps which have an effect on my display as well as reinstalling the ROM without the Franco kernel its still having the same issue.
I left a music app running this time and then left the phone till it put itself into sleep/lock mode. The app continued to run and I could change the volume with the side buttons but when i Pressed to get the screen on it just stays black now but it seems as though everything is still running in the background. Anybody had this type of issue with PA before? Thanks
One last question on the kernel, do you have any tweak apps running?
Sent from my Nexus 5 using Tapatalk
ticketseriously said:
OK I was wrong. After uninstalling all the apps which have an effect on my display as well as reinstalling the ROM without the Franco kernel its still having the same issue.
I left a music app running this time and then left the phone till it put itself into sleep/lock mode. The app continued to run and I could change the volume with the side buttons but when i Pressed to get the screen on it just stays black now but it seems as though everything is still running in the background. Anybody had this type of issue with PA before? Thanks
Click to expand...
Click to collapse
its sod, sleep of death. its not really known what causes it on the n5, but it happens. raising your voltages might help you, as it helps a few, but not all. if it happens that often, id see about an rma after flaahing the factory img to test.
Running beta software, custom kernel... Seems you're in for more that what you've bargained for.
Just do as simms22 says and flash latest factory image.