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.
I can’t post this in the original thread because one needs 10 posts to participate in the development related sections of the forum. So I have to report my problem here.
I'm currently running the jan31 build of CM and have had the Sleep of Death with every build of this ROM, especially reproducable when the phone has been on the charger for several hours. It justs sits there, the notification LED works, but it can’t be waked up. I have to press the power button for 15 or so seconds to forcibly reboot the device.
Even the "Wake my Android Pro" app on default values (wake up every 29 minutes) wasn’t able to fix this. I can fully prevent the SoD using the "Wake Lock" app and setting PARTAL_WAKE_LOCK, however this drains the battery massively.
I have done a full wipe before switching from stock to CM and did another full wipe before going to the jan31 build, however the problem persists.
Nobody else in the main thread seems to be affected by this problem.
This is on a German Moto G XT1032.
Any ideas?
Does nobody have an idea, or can forward this to the developer via the official thread?
Hey guys
i have a little problem with my Oneplus One. I'm running on Temaseks unofficial build v4.0 with AK kernel 0.76. but the same problem goes on slimsaber.
the problem i have is that often when i get a lockscreen notification from whatsapp + or other applications, the OPO restarts itself. before it does that, the notification light comes on and when i double tap or use the power button to wake the phone, the screens stays black. it takes nearly 3 seconds before it reboots itself and i can't find a solution. it does not happen everytime, mostly when i get a whatsapp notification from whatsapp. but that is not uncommon, since the most nots comes from whatsapp+.
So i guess it is the AK kernel or the 5.0.2. Android rom itself. anyone else got this problem so far?
What i tried:
Fresh installing the Rom, no dirty flash, tried to deactivate the lockscreen notifications, tried to turn off the not light. turned off the notification from whatsapp itself, all that doesn't help.
Sometime it reboots even when the screen is on, after i taped the screen, when i got a notification, but it only appears when the screen is off.
Any solutions? Or someone got the same prob?
Regards Mike
EDIT:
okay i solved the problem myself. Seems to be a problem with AK kernel. tried it now multiple times with and without AK Kernel and without the lockscreen notification works good, with AK it reboots nearly everytime. Would be great if someone could contact the developer, since i cannot answer in his thread itself. sorry and thanks
I've got an odd problem with my p900. If I install any lollipop ASOP ROMs, the first time I reboot after initial install, the display mostly stops working. The first boot works fine, I go through the setup wizard, set everything up, and the tablet works and displays fine as long as I don't reboot.
Specifically, what will happen if I reboot is that the tablet will go through the normal boot, and get to the point when the wallpaper and status bar will come up, but no homescreen icons or anything. Then after a while, about 2-5 minutes, the display will go black except for the status bar. I can pull down the notifications drawer from the status bar, and it will display, as will the quick settings, but anything I tap to try to interact with will seemingly just do nothing. If I have 'show touches' on, then touches will display properly, anywhere on the screen, but they seem to do nothing. I've tried trebuchet, google now, and adwex, the home app doesn't seem to make a difference.
The problem first began in I want to say october, when I flashed a CM12 nightly update. I unfortunately no longer remember which nightly I was on nor which I flashed to. I of course immedately tried to flash back to the previous nightly when I discovered the problem, but it did no good. It took me a while to figure out the pattern to the problem after it first occurred, as I often don't reboot the device for a long while after a first install. I don't have a lot of spare time to devote to sitting down and just focusing on trying different things, so it wasn't until president's day weekend that I tried what I *thought* would fix it, ODINing back to stock and installing the latest CM12.1. Clearly that didn't work, or I wouldn't be posting.
I've tried the 20151104, 1029, 1006, and 0910 CM12.1s from http://forum.xda-developers.com/gal...nt/rom-cyanogenmod-12-lollipop-5-0-1-t2971945. I've also tried Civz lollipop, pacman, and resurection remix. Anything not stock based has the problem. I tried running stock, but I've been running CM since G1 days, and I just can't stand stock, even the stripped down and modded versions. It just doesn't work right, and I can't get used to it, even after forcing myself to use it for several days.
I've never encountered such a weird problem, and I can't seem to find anyone else having a similar problem. I have no idea how to troubleshoot this beyond what I've done already. I'm currently running thompatry's Cm12.1 20160212, having not rebooted after the initial install, and it's running mostly ok, but I live in dread of my battery dying, and of course I can't install any xposed modules like xprivacy or multiwindow, which is bothersome. I have the wifi only US model, v1awifi, and I'm currently running TWRP 3, tho I was on TWRP 2.8.something when the issues first started happening.
what's the last 3 characters of your bootloader version?
heldc said:
I've got an odd problem with my p900. If I install any lollipop ASOP ROMs, the first time I reboot after initial install, the display mostly stops working. The first boot works fine, I go through the setup wizard, set everything up, and the tablet works and displays fine as long as I don't reboot.
Specifically, what will happen if I reboot is that the tablet will go through the normal boot, and get to the point when the wallpaper and status bar will come up, but no homescreen icons or anything. Then after a while, about 2-5 minutes, the display will go black except for the status bar. I can pull down the notifications drawer from the status bar, and it will display, as will the quick settings, but anything I tap to try to interact with will seemingly just do nothing. If I have 'show touches' on, then touches will display properly, anywhere on the screen, but they seem to do nothing. I've tried trebuchet, google now, and adwex, the home app doesn't seem to make a difference.
The problem first began in I want to say october, when I flashed a CM12 nightly update. I unfortunately no longer remember which nightly I was on nor which I flashed to. I of course immedately tried to flash back to the previous nightly when I discovered the problem, but it did no good. It took me a while to figure out the pattern to the problem after it first occurred, as I often don't reboot the device for a long while after a first install. I don't have a lot of spare time to devote to sitting down and just focusing on trying different things, so it wasn't until president's day weekend that I tried what I *thought* would fix it, ODINing back to stock and installing the latest CM12.1. Clearly that didn't work, or I wouldn't be posting.
I've tried the 20151104, 1029, 1006, and 0910 CM12.1s from http://forum.xda-developers.com/gal...nt/rom-cyanogenmod-12-lollipop-5-0-1-t2971945. I've also tried Civz lollipop, pacman, and resurection remix. Anything not stock based has the problem. I tried running stock, but I've been running CM since G1 days, and I just can't stand stock, even the stripped down and modded versions. It just doesn't work right, and I can't get used to it, even after forcing myself to use it for several days.
I've never encountered such a weird problem, and I can't seem to find anyone else having a similar problem. I have no idea how to troubleshoot this beyond what I've done already. I'm currently running thompatry's Cm12.1 20160212, having not rebooted after the initial install, and it's running mostly ok, but I live in dread of my battery dying, and of course I can't install any xposed modules like xprivacy or multiwindow, which is bothersome. I have the wifi only US model, v1awifi, and I'm currently running TWRP 3, tho I was on TWRP 2.8.something when the issues first started happening.
Click to expand...
Click to collapse
Have you tried changing kernel? I mean in the case of civz lollipop rom you do get an option of 2 different kernels try choosing the opposite to the one you had chosen before. Thank you, hope it helps.
I won a year ago 2 Note Pro, one works flawlessly while the other is slow af and it has the same issue that you speak about. If I stay on stock everything is good more or less (sometime little slow), but if I install Lineage or any other Custom Rom is too slow and has the same issue you speak.
I changed both batteries, but nothing to do. If anyone knows, text please.
Thank you!
Hello all, I need a hand with this one. I'm running the newest version of CM 13 nightly, yesterdays build. The past 2 builds my quick settings seems to have disappeared. I have the setting the turn it on, it does not matter if it is turned on or not, still nothing. On top of that I am missing any and all tiles from the menu as well. As you can imagine this has put me at a major loss, I love my tiles! No more double pull for setting, heck even my notifications are missing, they don't even show up in the bar. Does anyone have any ideas? When I installed this build I did a complete wipe/reinstall to there are no older versions to get borked on.
Figured this out! Seems to be a know issue from openGAPPs. Wipe everything but internal storage, flash the latest nightly, flash the nano package of OpenGAPPs, wipe cache and dalvik, reboot. Should be good to go! For posterity!
Sent from my DROID Turbo using XDA-Developers mobile app
Glad you got it figured out.