Unfortunately I don't have the required number of posts to post in the ROM thread itself, so hopefully someone can answer me here.
Does anyone else running PA notice the long delay (relative to stock or Beans7) between pressing the lock button and the screen actually turning off? I understand there is an issue (for some people) with unlocking the screen and there being a delay on the Note 2 in general, but with PA I notice it turning the screen off as well.
I only notice a delay when I hit power to turn it on in Jelly Bean's
It's an AOSP thing. It is like this on CM 10 and 10.1 as well as any other AOSP based ROM for this phone.
DaRkL3AD3R said:
It's an AOSP thing. It is like this on CM 10 and 10.1 as well as any other AOSP based ROM for this phone.
Click to expand...
Click to collapse
Mmkay, thanks for the info.
Is it something that will ever be addressed on this device (have you heard anything)?
Related
Hello
I appreciate both the CM and AOKP roms built on 4.1.2 are no longer being supported but is anyone running these roms as daily drivers and can confirm their stability?
Over the last month I have tried both roms and found them great roms with no audio (speaker) issues which keeps me from using the 4.2 builds of these roms.
Unfortunately I am finding my phone occasionally will not turn back on when the phone has gone into sleep. When this happens the capacitive buttons at the bottom are illuminated in red but the phone will not turn on at all. I am forced to hold down the power button so that the phone reboots.
Just wondering if anyone else has experienced this?
For both CM and AOKP I just use the kernel within the rom zip. Perhaps I should use the latest Maxwen kernel?
Greetings my fellow XDA experts,
I have a Galaxy S2 (i9100) International version on the NeatROM 4.8 ( XXLSW). What has happened is that my Softkeys are dead and unresponsive.
There is no illumination and response from them. So I have a phone without the menu and back buttons, which implies that I have a f**ked up iPhone like phone with just one Home button to function with.
I took the phone to the service center and they said it's a single piece with the display so the entire display would need to be replaced which is unreasonable and needless since the display works absolutely perfect.
So I was thinking of a remedy in terms of the ROM I use with the phone. Is there any custom ROM available for the S2 which would enable me to use a part of the display as the MENU and BACK buttons itself ? Like the Nexus 4 has ? I don't mind losing out on screen space to enable me to get those buttons back.
Please do suggest me any such ROM's or methods through which I can use the phone without having to change a fully functional touchscreen display. Spending so much just to get the Soft key functionality back is plain ridiculous and a pure manufacturing drawback from Samsung. Yuck
Anyways, please do help with any pointers.
Thanks and Cheers !
HellRazorGod said:
Greetings my fellow XDA experts,
I have a Galaxy S2 (i9100) International version on the NeatROM 4.8 ( XXLSW). What has happened is that my Softkeys are dead and unresponsive.
There is no illumination and response from them. So I have a phone without the menu and back buttons, which implies that I have a f**ked up iPhone like phone with just one Home button to function with.
I took the phone to the service center and they said it's a single piece with the display so the entire display would need to be replaced which is unreasonable and needless since the display works absolutely perfect.
So I was thinking of a remedy in terms of the ROM I use with the phone. Is there any custom ROM available for the S2 which would enable me to use a part of the display as the MENU and BACK buttons itself ? Like the Nexus 4 has ? I don't mind losing out on screen space to enable me to get those buttons back.
Please do suggest me any such ROM's or methods through which I can use the phone without having to change a fully functional touchscreen display. Spending so much just to get the Soft key functionality back is plain ridiculous and a pure manufacturing drawback from Samsung. Yuck
Anyways, please do help with any pointers.
Thanks and Cheers !
Click to expand...
Click to collapse
You'll be hard pressed to find a 4.2.2 ROM that doesn't have some sort of on-screen control. Do a bit of searching around on XDA of all the 4.2.2 ROMs, look at screenshots etc. Navigation bar is the same style as a Nexus 4. Pie controls are a method of on-screen control. AOKP ribbons are also for on screen control. There's probably more. Then there exist ROM's which attempt to mimic the AOSP, Nexus-style experience. Plenty to choose from.
Hopper8 said:
You'll be hard pressed to find a 4.2.2 ROM that doesn't have some sort of on-screen control. Do a bit of searching around on XDA of all the 4.2.2 ROMs, look at screenshots etc. Navigation bar is the same style as a Nexus 4. Pie controls are a method of on-screen control. AOKP ribbons are also for on screen control. There's probably more. Then there exist ROM's which attempt to mimic the AOSP, Nexus-style experience. Plenty to choose from.
Click to expand...
Click to collapse
So basically My ROM territory is now limited to any 4.2.2 AOSP/AOKP Rom's ? Do all of them have on-screen navigation?
Like the Parandroid? No more Sammy Rom's obviously.
HellRazorGod said:
So basically My ROM territory is now limited to any 4.2.2 AOSP/AOKP Rom's ? Do all of them have on-screen navigation?
Like the Parandroid? No more Sammy Rom's obviously.
Click to expand...
Click to collapse
Hmm well I imagine you could find some lower than 4.2.2 with those controls if you wanted to, but no need to if you don't want. You can use ParanoidAndroid if you want, search my posts for a link for i9100, I posted it yesterday or the day before I think. It won't be the first link you find on Google thats for sure, version 3.6 is the latest. As far as 'limited to 4.2.2 AOSP/AOKP'.... Depends how you see it. I don't see it as a 'limitation'. Start here: http://forum.xda-developers.com/showthread.php?p=23231772. Go through AOKP and AOSP till you find something you like. Bear in mind that the AOKP contains waaay more than just plain AOKP, there's hybrid (combos of CM,AOKP,PA, AOSP usually) and all sorts in there.
Enable Navigation Bar in AOSP/AOKP roms etc for getting these functions back.
Alternatively if you want navigation bar in Sammy Roms you can still have them , look for soft key enabler in play store or else you can edit build.prop of your phone , there will be option of soft keys , change it from 0 to 1.
Use pimp my rom it have a option for on screen buttons (back menu and recents) so you can have any rom
Sent from my GT-I9100 using xda premium
S2 soft keys not working
Issue seems to be related to the usb charging receptacle. As long as a good charging cable is connected, the soft keys work. They work for a short time after unplugging and then stop working again.
HellRazorGod said:
Greetings my fellow XDA experts,
I have a Galaxy S2 (i9100) International version on the NeatROM 4.8 ( XXLSW). What has happened is that my Softkeys are dead and unresponsive.
There is no illumination and response from them. So I have a phone without the menu and back buttons, which implies that I have a f**ked up iPhone like phone with just one Home button to function with.
I took the phone to the service center and they said it's a single piece with the display so the entire display would need to be replaced which is unreasonable and needless since the display works absolutely perfect.
So I was thinking of a remedy in terms of the ROM I use with the phone. Is there any custom ROM available for the S2 which would enable me to use a part of the display as the MENU and BACK buttons itself ? Like the Nexus 4 has ? I don't mind losing out on screen space to enable me to get those buttons back.
Please do suggest me any such ROM's or methods through which I can use the phone without having to change a fully functional touchscreen display. Spending so much just to get the Soft key functionality back is plain ridiculous and a pure manufacturing drawback from Samsung. Yuck
Anyways, please do help with any pointers.
Thanks and Cheers !
Click to expand...
Click to collapse
Hi!
So I just updated my t-mobile s3 to android 4.3 expecting it to be great... It's not really any different other than a couple icons etc. (well I haven't noticed anyway).
Except I thought I'd give my lock screen a bit of a change, downloaded Go Locker and set it all up, except sometimes when I press my power/home button just to check the clock or something, I find myself waiting for a minute or two because the screen just doesn't do anything!
Several times I've had to restart my phone to make it do something because I got so impatient. I sound pretty ridiculous complainign that sometimes my phone doesn't start for a minute or two, but when I just want a quick look at the time it's ridiculous!
Anybody know if there's any way I can fix this, or is it likely just a bug with go locker and android 4.3?
Thanks,
Squiggmont
actually i have that issue too. i just updated my s3 with several 4.3 roms but all of them has lock screen wake up bug. waits a while. i think there is no stable 4.3 rom yet. so i turned back to 4.1.2 again.
by the way i tried other lock screens and still same bug. just wait for a stable 4.3 my friend.
untouchables221 said:
actually i have that issue too. i just updated my s3 with several 4.3 roms but all of them has lock screen wake up bug. waits a while. i think there is no stable 4.3 rom yet. so i turned back to 4.1.2 again.
by the way i tried other lock screens and still same bug. just wait for a stable 4.3 my friend.
Click to expand...
Click to collapse
Ah at least it's not just me! I'm on the official release of 4.3 though, OTA.. Would have thought they'd fix something like that before releasing it this far..
Check with the apps developer .
But it does look like 4.3 may be halted in its release by Samsung due to problems .
I just stumbled upon something kind of weird:
When I swipe across the very bottom of the screen it will turn off. Orientation and position of the navbar does not seem to matter it always works at the bottom of the screen (the side with the lg logo). Direction of the swipe doesn't matter and it works on the lockscreen as well.
I have a D802 running on Mahdi 08/17 with barts v5.x AOSP Dorimanx kernel.
Haven't found anything specific in either rom or kernel thread. Is that hardware related? Bug? Design?...
Touchscreen firmware updated via service menu on stock kk rom around 2-3 months ago...
Preggy said:
I just stumbled upon something kind of weird:
When I swipe across the very bottom of the screen it will turn off. Orientation and position of the navbar does not seem to matter it always works at the bottom of the screen (the side with the lg logo). Direction of the swipe doesn't matter and it works on the lockscreen as well.
I have a D802 running on Mahdi 08/17 with barts v5.x AOSP Dorimanx kernel.
Haven't found anything specific in either rom or kernel thread. Is that hardware related? Bug? Design?...
Touchscreen firmware updated via service menu on stock kk rom around 2-3 months ago...
Click to expand...
Click to collapse
You haven't read the feature list of dorimanx kernel too well, my friend It's a feature in that kernel. You can turn it off in STweaks Hope this helps.
vPro97 said:
You haven't read the feature list of dorimanx kernel too well, my friend It's a feature in that kernel. You can turn it off in STweaks Hope this helps.
Click to expand...
Click to collapse
Well crap, I say their fault for calling it "sweep2sleep" no wonder I didn't find anything with swipe or slide, found plenty of slide2wake though
Thank you for the kind heads up and apologies for the forum clutter.
Hi, there!
The issue I'm facing is that there is a really long delay between pushing the power button and the screen waking up. Like one second or more. I just can't seem to find a way to fix this. Any idea? Suggestions?
Details: This screen wake delay seems to be a major issue with all Android 9 (Pie) based ROMs. However, I can't just go back to 8.1 no matter what for two reasons. The devs keep leaving their Oreo ROMs and fill the forums with Pie ones. Beside Lineage OS no major ROM sticks still with Oreo and pushes fresh updates, fixes. I was on Lineage os 15.1 but an issue that is presumably ROM related kept rendering my system unusable.
i have same problem on aosp extended (pie) there is a really long delay (lock button, double tap to wake, fingerprint scanner unlock)
plakonn said:
i have same problem on aosp extended (pie) there is a really long delay (lock button, double tap to wake, fingerprint scanner unlock)
Click to expand...
Click to collapse
Its because the Android build that was given in open source was not that optimized
Once newer version of pie comes, possibly it will be fixed
Aashish Bakshi said:
Its because the Android build that was given in open source was not that optimized
Once newer version of pie comes, possibly it will be fixed
Click to expand...
Click to collapse
I guess that sounds about right. There is nothing I can do until then, or is there?
greenys' said:
I guess that sounds about right. There is nothing I can do until then, or is there?
Click to expand...
Click to collapse
As of now
You can't do anything, we have to wait for a new build from google to the let the developers to Port and hopefully it will be fixes