So, I get kinda busy, and don't check the Juicy thread for a couple weeks, and there are about a billion new posts, *TWO* new builds, and apparently Juicy is leaving or something?!?! Um, WTF?!!?
Anyway, I have to leave, but I will try to read the over 100 pages since the first J8 build came out and attempt to understand the madness.
Before I go, I wanted to ask a quick question though, I already searched not only this thread, but the entire site about this, and only found this one post about it:
Quote:
Originally Posted by BrianPAdams
When I switched to Windows Classic lock style, then it would continuously switch back and forth between the silver lock screen and the TF3D home screen. Even if I was fast enough to catch the unlock soft key, it was unresponsive. I soft reset and it started over again. I had to catch the unlock screen before TF3D started loading before I could get to the unlock button.
|
And no replies or answers to the problem at all.
Personally, I feel this is a reasonably serious issue, as the new lock screen gives no feedback other than a clock (which is less functional, and less aesthetically pleasing than the TF3D one, especially if customized) and is not as reliable.
I normally will just put the device in suspend when I want to protect it from input, however there are certain programs which I like to be able to sit the device down and monitor without worrying about my cat walking on the TP and accidentally screwing something up.
Also, there are a few programs, for example the last.fm player, that will suspend function if you turn the screen off. (Personally, I think this makes absolutely NO sense for a music player, but meh, I didn't write the thing)
Anyway, I am quite surprised that more ppl have not reported this, I guess that ppl care more about finger candy than actual functionality, idk, whatever.
I have not had time to test this bug thouroughly, as I just flashed to the new Juicy, however, I can confirm that it happens with, or without TF3D enabled, with any app I have tried so far in the foreground, and directly after a hard reset (with my SDconfig disabled, of course)
I have never experienced the problem before with any previous build, however, I skipped from the first J8 to this one, as I have been busy, and didnt keep up to date on the site.
I also tried hard resetting, then reflashing, then hard resetting again, just to be safe, with the same results. I will try flashing back to stock Sprint rom, and then back again to J8090704 when I get back, but I hope someone has some idea what could possibly be causing this.
Oh, BTW BrianPAdams, you *can* actually disable it without resetting, and catching it while TF3D is loading, you just have to time the tap of the "unlock" softkey, and the unlock onscreen button that comes up afterward *just* right, or else it just goes back to the "press cancel, then unlock" error message as if there was screen input without tapping unlock first.