Related
I have a serious problem.
I have HTC Evo 4G, My screen is getting dim (NOT BLANK), I cant see screen in bright sun, It's really dark.
But this happen only Sense based ROMs, but this doesn't happen with Cyanogen or MIUI.
I have tried many sense-based ROMS ( Infected, Runny, MikG, ICS,...etc).
With every Rom, I flashed it many times, sometimes with wipe everything. I though it's hardware problem why this doesn't happen with ASOP ROM. (I don't like Cyanogen, or MIUI... LOL), Also, I tried every setting related to brightness But the problem still.
I've read every thread, article about similar problem, but useless.
For additional info about my problem: after starting up my phone, Every thing is OK, but after screen off for first time the screen getting so dark.
(Only one workaround I found, Just set "Screen always on") I'm going to kill my Evo.
Please Help me, I'm getting Crazy.
Okay this may be a dumb question, but are you sure that you don't have it set for "automatic" brightness?
JB
Sent from my CIUI using xda premium
Yes I'm sure the automatic brightness is off.
and the brightness is so high.
What kernel are you using with the sense ROMs? Have you restored any apps after flashing the ROMs? Sounds like either an incompatible kernel, or a restored app limiting brightness to save battery, although it could be hardware related(LCD or a sensor) but since you said AOSP works fine it sounds like a software issue over a hardware issue.
-EViL-KoNCEPTz- said:
What kernel are you using with the sense ROMs? Have you restored any apps after flashing the ROMs? Sounds like either an incompatible kernel, or a restored app limiting brightness to save battery, although it could be hardware related(LCD or a sensor) but since you said AOSP works fine it sounds like a software issue over a hardware issue.
Click to expand...
Click to collapse
Currently I'm using : RCMix3D Runny
Android Version: 2.3.5
HTC Sense version: 3.5
Kernal Version: [email protected]
and I didn't Restore any apps after flashing the ROMs, and also I didn't change the kernal of Sense ROMs.(I did this one time with Cyanogen).
Hmmm do you have anything installed to save battery like juice defender or any similar apps?
-EViL-KoNCEPTz- said:
Hmmm do you have anything installed to save battery like juice defender or any similar apps?
Click to expand...
Click to collapse
no I don't
I'm not sure what else it could be you could try changing the kernel to another gingersense kernel and see if that helps search "goldenmonkey 1.1 evo4g" without the " and try that kernel and see if it changes anything
thank you. I'll try that kernal, I'll inform you the progress.
I'm not sure it will help but your downloads may have had a bad kernel or been slightly corrupt so flashing a fresh kernel may help out but it may not more than likely it wont but its the simplest fix you can try make sure to check the md5 sum on the download to verify your download is intact if you do it from your phone es fileexplorer has and option when you longpress the zip and select properties to calculate the md5 and then save it to a txt file, the txt will save in the same location as the zip
-EViL-KoNCEPTz- said:
I'm not sure it will help but your downloads may have had a bad kernel or been slightly corrupt so flashing a fresh kernel may help out but it may not more than likely it wont but its the simplest fix you can try make sure to check the md5 sum on the download to verify your download is intact if you do it from your phone es fileexplorer has and option when you longpress the zip and select properties to calculate the md5 and then save it to a txt file, the txt will save in the same location as the zip
Click to expand...
Click to collapse
I flashed that kernal but nothing happen. The problem still.
Have you possibly tried installing a stock rom for the phone? see if the problem still persists once you are on a stock rooted rom...at that point you can see if it is your brightness sensor/hw issue or user/rom error.
I've heard of this before. Im gonna say its a hardware issue.
Just for curiosity's sake, what happens when you adjust the screen brightness slider? Does it get even dimmer if you slide it to a lower setting, or is the dimness consistent regardless of where you have the brightness slider?
jesuspgt said:
Just for curiosity's sake, what happens when you adjust the screen brightness slider? Does it get even dimmer if you slide it to a lower setting, or is the dimness consistent regardless of where you have the brightness slider?
Click to expand...
Click to collapse
The dimness consistent, I mean it seem that brightness doesn't effect, and there is no change whether brightness 0% or 100%.
With a stock RUU, and still having brightness issues.. time to replace the cell. I have had this problem only one where screen filter app somehow got re-installed and enabled but other than that..replace your unit.
The only thing is it works on aosp but not sense if it was hardware failure it wouldn't work regardless
You mentioned that you SOMETIMES wipe everything when flashing new ROMS. I would definitely wipe everything clean every time when flashing a ROM to positively rule out that you don't have any left over garbage from a previous ROM. Just my two cents.
I'd say try wiping everything including your SD card do a fresh format and repartition the SD.
X2 on the wipe everything. Do NOT install any kernels when u flash the ROM. See if it works first, if it does then do a FULL nandroid, then flash a kernel.
Sent from my PC36100 using Tapatalk
I've had this issue with lag on the Nexus 4 lockscreen for quite a while.
The problem is that occasionally when I go to the unlock the phone, I press the lock, but the lock will freeze. Sometimes I have to turn the screen off, and turn back on a couple of times before I can unlock the phone.
I've had this issue running CM10.1 and stock rooted android 4.2.2. I've tried doing a complete wipe and re-flashing everything.
Has anyone else had this issue? I've asked a couple of people I know who have Nexus 4's and none of them have had this problem.
Did I do something wrong, is this a common issue, or this an issue with my phone?
nmunro said:
I've had this issue with lag on the Nexus 4 lockscreen for quite a while.
The problem is that occasionally when I go to the unlock the phone, I press the lock, but the lock will freeze. Sometimes I have to turn the screen off, and turn back on a couple of times before I can unlock the phone.
I've had this issue running CM10.1 and stock rooted android 4.2.2. I've tried doing a complete wipe and re-flashing everything.
Has anyone else had this issue? I've asked a couple of people I know who have Nexus 4's and none of them have had this problem.
Did I do something wrong, is this a common issue, or this an issue with my phone?
Click to expand...
Click to collapse
I also get this occasionally from time to time. I honestly have no clue what it could be, since the screen is completely dry as are my fingers when it happens. Its a minor bug so it doesn't bother me that much
brandonc0526 said:
I also get this occasionally from time to time. I honestly have no clue what it could be, since the screen is completely dry as are my fingers when it happens. Its a minor bug so it doesn't bother me that much
Click to expand...
Click to collapse
I also sometimes get lag when I do manage to unlock, scrolling through my screens is very laggy for 5-10 seconds, then it is usually fine.
I have a problem with lockscreen lag on a phone with a quadcore CPU and 2 GB of RAM.
Flash a custom kernel. You'll be less likely to experience lag
Don't get any lockscreen lag on my stock Android.
sigma392 said:
Flash a custom kernel. You'll be less likely to experience lag
Click to expand...
Click to collapse
Have any recommendations?
nmunro said:
Have any recommendations?
Click to expand...
Click to collapse
The latest trinity kernel (125) has perfected the lockscreen lag, It definitely unlocks instantly for me.
username8611 said:
The latest trinity kernel (125) has perfected the lockscreen lag, It definitely unlocks instantly for me.
Click to expand...
Click to collapse
Trying this out now. I especially liked how it told me my system was corrupted once it finished flashing...
First thing I've noticed is that the colour is a lot different. Do I need to play with any settings, or do I only need to have the kernel installed?
Also how often do updates come out?
Messing with the settings is totally up to you. It works great "right out of the box." I don't like the stock color settings, I use trickster mod to change them to rgb 255, 255, 255 and everything else at 0 except saturation and blacks all the way up. This kernel is underclocked to 1026mhz by default, I set it to stock clock speeds. It's also undervolted by default so if you are having stability problems, try bumping up the voltage on all steps by 25mv. Updates come out pretty often, prolly a few times a month.
username8611 said:
Messing with the settings is totally up to you. It works great "right out of the box." I don't like the stock color settings, I use trickster mod to change them to rgb 255, 255, 255 and everything else at 0 except saturation and blacks all the way up. This kernel is underclocked to 1026mhz by default, I set it to stock clock speeds. It's also undervolted by default so if you are having stability problems, try bumping up the voltage on all steps by 25mv. Updates come out pretty often, prolly a few times a month.
Click to expand...
Click to collapse
The colours bothered me so I'm trying the latest franco nightly. It seems to be at the stock clock speed, no weird colours, and it makes the haptic feedback when unlocking feel more like the GNex.
I'm still having this issue with franco kernel. I've been looking around a bit and people seem to say this is related to auto brightness. I'm going to turn auto brightness off for a bit and see if it still happens.
Also, does anyone know if using a 3rd party app for auto brightness would make any difference?
Okay, turns out auto brightness wasn't the issue. Still getting lockscreen lag. Help please.
If I put 5 fingers on the screen (when the screen is off), then press the lock button, when the screen comes on it will be completely unresponsive, some of the time. I'm not always able to replicate this.
for me, some releases of Franco have lockscreen lag, some don`t, try flashing the M2 or other post r121 builds, they are all great performers and maybe you`ll get lucky with one.
if ur using paranoid android, then its a stability issue i guesa cause the same thing used to happen with me...... or else try franco kernel... or update franco kernel if ur using franco, cause an older version had the lockscreen bug, which is now fixed!!!
sigma392 said:
Flash a custom kernel. You'll be less likely to experience lag
Click to expand...
Click to collapse
Flash a stock kernel. You'll be less likely to experience lag
I'm running CM 10.1 and the latest version of franco's kernel.
I've tried using a rooted stock and I had the same issue with lag.
I'm going to try franco's milestone build, see if I still get issues.
Would increasing the minimum clock likely help at all?
I had this problem no matter what custom ROM or kernel I would use I would get this problem I got a replacement phone and don't have this issue anymore
Sent from my Nexus 4
Good Guy Mark said:
I had this problem no matter what custom ROM or kernel I would use I would get this problem I got a replacement phone and don't have this issue anymore
Sent from my Nexus 4
Click to expand...
Click to collapse
I'm thinking this may have been the issue.
How does the replacement process work?
If I save a nandroid backup of my phone, can I just unlock it and restore from there?
Flash the reset kernel from _motley 's kernel thread, it replaces a lot of files that might of got changed via various other kernel flashes with stock ones.
the one that causes a lot of lock screen lag is the /system/lib/hw/power.msm8960.so file
N4_422_stock_kernel_and_components.zip
meangreenie said:
Flash the reset kernel from _motley 's kernel thread, it replaces a lot of files that might of got changed via various other kernel flashes with stock ones.
the one that causes a lot of lock screen lag is the /system/lib/hw/power.msm8960.so file
N4_422_stock_kernel_and_components.zip
Click to expand...
Click to collapse
Can I just flash this with CWM? And then flash back to franco m2?
I actually just got an RMA for my phone, because of this issue and that the back glass panel is a little loose and makes creaking noises. When I send the phone back to google, if I follow all the steps here and lock the bootloader, it should be fine to send back to them?
Google's RMA process was amazing. Took me all of 10 minutes. They're shipping a new one in 3-5 days, and they pay for the return shipping of my old device. The replacement is brand-new, not a refurbished device. My dad's iPhone 4S had a bunch of issues and he would have to book an appointment at the Apple store, which happens to be an hour away, and they would only replace his device with a refurbished one.
Hi all,
EDIT2: MAIN PROBLEM FIXED!
I was incredibly frustrated last night, so I figured I'd just re-root as I have a copy of the stock flash tools and a TOT file sitting on my PC should I need to return.
I rooted (again), installed binaries, uninstalled Superuser, installed Super SU, and (just for fun) installed Greenify.
Lo and behold, I rebooted three times now and NO KNOCK LOOP!
I'm still having issues with knock-on not waking the phone sometimes, but once I hit the power button everything works fine.
As I posted above, the proximity sensor app seems to have a huge delay when uncovered. 3-15 seconds at totally random intervals. This might explain my still present knock-on delay issues.... ?
EDIT: Not Greenify causing this, but some other combo of rooting and system file changes. Could also be the proximity sensor misbehaving or just a bad copy of the phone.
Just a friendly PSA, but Greenify (the popular hibernation app that is really awesome) will gimp your knock-on feature for good. As in: returning to stock does not fix it. Myself and at least one other user have had this problem. I'm now having to swap out my phone after just getting it how I like it, which is infuriating.
I'd rather wait until somebody gets a fix up, but I'm within 14-days so I'm not risking it.
Note: This is CLEARLY not the fault of Greenify. It's some bizarre file system/sensor error. Greenify is great.
Related thread where the problem was thought to be fixed... but is not for people who installed Greenify.
I'm using the Verizon variant, so I don't know if this applies to GSM models.
From a dev standpoint this makes zero sense to me, so I'm kind of curious if anybody has better insight. Greenify, for the most part, is just leveraging system-level features to disallow the start-up of a particular program when the screen is off.
I am personally using Greenify on a number of apps with success and no ill side-effects. There are a number of code dependencies involved in its use, but mainly it is the knock-on related apk/odex in /system/app - so is it possible these people are Greenifying the wrong things?
Also, I would question their return to stock, Greenify doesn't work on a hardware level. If they didn't return the right files and/or kernel to stock, yeah, it might have lingering ill-effects. I would say that merely flashing a stock ROM is not returning to stock. It isn't clean enough.
tl;dr: There is no logical reason in my mind that Greenify would permanently break knock-on. I need more proof.
I've been using greenify since the day after I got the phone and rooted it, so 2 weeks now, and knock on works perfectly every single time.
Sent from my VS980 4G using Tapatalk 4
---------- Post added at 12:14 PM ---------- Previous post was at 12:14 PM ----------
and I'm on the Verizon version. what app are you guys hibernating that's causing this?
Sent from my VS980 4G using Tapatalk 4
burningembers said:
From a dev standpoint this makes zero sense to me, so I'm kind of curious if anybody has better insight. Greenify, for the most part, is just leveraging system-level features to disallow the start-up of a particular program when the screen is off.
I am personally using Greenify on a number of apps with success and no ill side-effects. There are a number of code dependencies involved in its use, but mainly it is the knock-on related apk/odex in /system/app - so is it possible these people are Greenifying the wrong things?
Also, I would question their return to stock, Greenify doesn't work on a hardware level. If they didn't return the right files and/or kernel to stock, yeah, it might have lingering ill-effects. I would say that merely flashing a stock ROM is not returning to stock. It isn't clean enough.
tl;dr: There is no logical reason in my mind that Greenify would permanently break knock-on. I need more proof.
Click to expand...
Click to collapse
I'd have to agree with this!!
Sent from my GT-N7100 using xda app-developers app
Knock on seems to work on mine (most of the time anyway) while using Greenify for a couple of weeks now. If it was going to gimp it, I'm thinking it would have by now. I have the T-Mobile variant. Its basically just hibernating apps from the market, not any system apps so I guess I don't see the correlation.
Greenify works for me
I'm stock rooted and I heavily use Greenify with my Verizon G2. No problems with Knock On at all!
Edit: Stock rooted (not the chinese way), no OTA, auto-hibernation feature works perfectly too.
um question... did you guys who have the problem use the Chinese root method? someone brought it up and now I'm curious....
i did but then flashed back to stock to reroot the good way. you guys who aren't having the issue with me, you use Chinese or regular?
Sent from my VS980 4G using Tapatalk 4
I only froze Facebook and Twitter. Have completely Re flashed stock and BlackHole ROM to no avail. Read the thread, it seems to be vexing even advanced users. The fix of changing screen effect does not resolve it.
YMMV
Sent from my VS980 4G using XDA Premium 4 mobile app
lattiboy said:
I only froze Facebook and Twitter. Have completely Re flashed stock and BlackHole ROM to no avail. Read the thread, it seems to be vexing even advanced users. The fix of changing screen effect does not resolve it.
YMMV
Click to expand...
Click to collapse
When you say re-flashed stock, what does that mean?
Are all affected users on Verizon and using BlackHole ROM?
I'm just trying to narrow this scope down, because this still makes no sense to me.
burningembers said:
When you say re-flashed stock, what does that mean?
Are all affected users on Verizon and using BlackHole ROM?
I'm just trying to narrow this scope down, because this still makes no sense to me.
Click to expand...
Click to collapse
1) I rooted
2) installed Greenify
3) bug happens the next morning.
4) went back to stock, using these instructions.
5) bug happens again
6) re-rooted and installed BlackHole ROM.
Everything was (seemingly) cool for a bit, but last night it happened again. Twice this morning I've had the weird behavior sited in the original thread and I'm going to take it into VZW and leave stock in until this gets figured out.
Again, not trying to cause alarm or panic. I'll update my post to reflect the YMMV nature of this issue.
You should really rename this thread. I have not experienced any knock issues and I've installed this app since I bought the phone. False psa
---------- Post added at 12:44 PM ---------- Previous post was at 12:40 PM ----------
lattiboy said:
1) I rooted
2) installed Greenify
3) bug happens the next morning.
4) went back to stock, using these instructions.
5) bug happens again
6) re-rooted and installed BlackHole ROM.
Everything was (seemingly) cool for a bit, but last night it happened again. Twice this morning I've had the weird behavior sited in the original thread and I'm going to take it into VZW and leave stock in until this gets figured out.
Again, not trying to cause alarm or panic. I'll update my post to reflect the YMMV nature of this issue.
Click to expand...
Click to collapse
Are you using a custom launcher or does the rom install a custom launcher? That would surely affect the knock on feature.
SysAdmNj said:
Are you using a custom launcher or does the rom install a custom launcher? That would surely affect the knock on feature.
Click to expand...
Click to collapse
Nope, using stock home, never even installed Nova or anything else.
I added a big YMMV to it, but because the outcome seems quite dire on such an expensive device, I feel this is warranted.
lattiboy said:
Nope, using stock home, never even installed Nova or anything else.
I added a big YMMV to it, but because the outcome seems quite dire on such an expensive device, I feel this is warranted.
Click to expand...
Click to collapse
You went back to stock, rooted, installed greenify and still the same issue? Which root method did you use, the chinese one?
The issue might be caused by misuse of Greenify. Have you greenified any system apps related to the Knock-on feature?
Greenify should never "damage" your device in a non-recoverable way since it never touches any system files. Just simply de-greenify the app and manually relaunch it once to restore everything to normal.
Hope one of you G2 users could find out that key greenified app which caused this terrible issue, thus we could warn others in a more effective way.
lattiboy said:
Nope, using stock home, never even installed Nova or anything else.
I added a big YMMV to it, but because the outcome seems quite dire on such an expensive device, I feel this is warranted.
Click to expand...
Click to collapse
Yeah, it is an expensive device, but when you go rooting it and mucking around with system files, it is kind of a risk you take. My real issue is two-fold 1) Bad publicity for Greenify when I still don't believe it to be a problem with Greenify and 2) That LG/Verizon are taking a loss on time/cost because users are essentially breaking their own device. I put this on-par with you putting your phone in a bucket of water and then going back to Verizon and getting a new one because it doesn't work.
Now, that said, maybe this truly is a HARDWARE bug/issue with the Verizon model. On AT&T I have Facebook, Humble Bundle, Keep, OfficeSuite, Reddit News, Series Guide, and Google Search greenified. I've modified system APKs. I've flashed some ROMs. I've toggled Knockon off/on in settings. And my phone is fine.
Someone needs to start data collecting. What model phone do these users have, did they take the OTA, did they at some-point use Chinese root method, are they in a dark room, did they toggle Knockon on/off, does toggling knockon on/off on an in-store device result in a similar issue, are they all on Verizon, etc. etc.
One thing someone mentioned the other day was that the latest Verizon OTA changed the scheduler from CFQ to ROW. Is it possible that this is borking the knockon application from staying in the queue properly to register the knockon events?
burningembers said:
Yeah, it is an expensive device, but when you go rooting it and mucking around with system files, it is kind of a risk you take. My real issue is two-fold 1) Bad publicity for Greenify when I still don't believe it to be a problem with Greenify and 2) That LG/Verizon are taking a loss on time/cost because users are essentially breaking their own device. I put this on-par with you putting your phone in a bucket of water and then going back to Verizon and getting a new one because it doesn't work.
Now, that said, maybe this truly is a HARDWARE bug/issue with the Verizon model. On AT&T I have Facebook, Humble Bundle, Keep, OfficeSuite, Reddit News, Series Guide, and Google Search greenified. I've modified system APKs. I've flashed some ROMs. I've toggled Knockon off/on in settings. And my phone is fine.
Someone needs to start data collecting. What model phone do these users have, did they take the OTA, did they at some-point use Chinese root method, are they in a dark room, did they toggle Knockon on/off, does toggling knockon on/off on an in-store device result in a similar issue, are they all on Verizon, etc. etc.
One thing someone mentioned the other day was that the latest Verizon OTA changed the scheduler from CFQ to ROW. Is it possible that this is borking the knockon application from staying in the queue properly to register the knockon events?
Click to expand...
Click to collapse
I did take the OTA, but before flashing the current version of TWRP.
I feel bad about it and I should've waited until these kinds of things were worked out.
I'm trying one last flash back to stock to make sure it isn't a user generated problem with flashing incorrectly.
lattiboy said:
I did take the OTA, but before flashing the current version of TWRP.
I feel bad about it and I should've waited until these kinds of things were worked out.
I'm trying one last flash back to stock to make sure it isn't a user generated problem with flashing incorrectly.
Click to expand...
Click to collapse
So flashing back to pre-OTA doesn't clear the problem at all?
burningembers said:
So flashing back to pre-OTA doesn't clear the problem at all?
Click to expand...
Click to collapse
No, I just flashed to stock (yet again) and I got the weird wake-lock freeze thing within 30 minutes.
Super annoying.
lattiboy said:
No, I just flashed to stock (yet again) and I got the weird wake-lock freeze thing within 30 minutes.
Super annoying.
Click to expand...
Click to collapse
What's your Baseband and Kernel version in Software Information?
I know for a *fact* that the OTA changed the cpu scheduler. What I'm curious is if their scheduler changes have somehow caused service-level applications like the KnockOn APK to die/hibernate during a lengthy deep sleep. This makes way more sense to me than merely using Greenify causing a permanent breaking of software/kernel interactions.
burningembers said:
What's your Baseband and Kernel version in Software Information?.
Click to expand...
Click to collapse
This is it. No root, fresh stock 15 minutes ago.
I'm on a rooted Note 3 (Verizon), running 4.3
Recently I began experiencing the annoying auto rotation glitch. Seems to be completely random too. Restarting the phone removes the glitch - but it eventually comes back. I've tried pretty much everything but nothing gets rid of this glitch other than restarting the phone.
I did find this thread here: http://forum.xda-developers.com/showthread.php?p=53138619
...I'm new to rooting, I see that this solution is for 4.4 so I'm hesitant to try it.
Anyone run into this glitch and found a cure? Will the solution found in that thread work under 4.3? Is it worth a shot to try it (I haven't tried it 'cause I don't know if it'll cause problems since I'm on 4.3)?
You may want to let us know exactly what the glitch is. Does it not rotate? I know on my current build which is stock, it almost always rotates once when I open the browser no matter what orientation the phone is in.
Morkai Almandragon said:
You may want to let us know exactly what the glitch is. Does it not rotate? I know on my current build which is stock, it almost always rotates once when I open the browser no matter what orientation the phone is in.
Click to expand...
Click to collapse
The Note 3 will stop automatically rotating the screen. The thing is, it's totally random. Sometimes it'll stop right away, sometimes it might be fine 'til the end of the day and then it stops.
I've been closely monitoring what apps I'm running when it happens, can't seem to find a culprit.
Restarting the phone fixes the glitch, but it's just annoying to have to restart the phone to get auto rotation back.
I've poured through what seems like hundreds of threads trying to find a fix. I've turned auto rotation on then off of course along with so many other tips and tricks that folks have suggested.
EDIT: But that thread I linked to above was the first one to suggest modifying a file to restore auto rotation. I'm a noob so I just don't want to immediately do that without askin' if it should work for me or not though.
Hey guys
As most of you probably know, as soon as you select for instance a pin for your lock screen the S4 disables the possibility for lock screen widgets. I'm currently getting around it with xposed and SamsungMultipleWidgets KitKat.
Just curious if there's any way around this limitation without xposed, or maybe even without root? I'm guessing that it's not possible, still.. I'm curious.
Obscure Reference said:
Hey guys
As most of you probably know, as soon as you select for instance a pin for your lock screen the S4 disables the possibility for lock screen widgets. I'm currently getting around it with xposed and SamsungMultipleWidgets KitKat.
Just curious if there's any way around this limitation without xposed, or maybe even without root? I'm guessing that it's not possible, still.. I'm curious.
Click to expand...
Click to collapse
Some ROMs have this feature baked in. SlimKat for instance. I dont believe there is a way whilst using a stock rom without using xposed, at least i never found one, and I looked hard!
fivecheebs said:
Some ROMs have this feature baked in. SlimKat for instance. I dont believe there is a way whilst using a stock rom without using xposed, at least i never found one, and I looked hard!
Click to expand...
Click to collapse
Yeah, I know.. I had it built in while running CM. Just had an urge to go back to stock for a while and was just wondering what features I wanted actually required root (and xposed).
If anyone else knows of a way, please let us know.
Hi gys, slightly different issue here, but would appreciate any help.
basically the PIN lock does not activate until 30 seconds or so after the phone boots up. So there is no securuty on initial boot up.
Its there if I do a reboot. But not there if I do a startup from fully off.
It used to work but at some point a few ROMs ago t stopped working.
I was told it was the kernel but I have tried 4 and all with the same result and have tried several roms.,