so when you two checked your alarm, did you guys let screen off or on ? Mine works fine as long as screen is on. but when setting alarm with screen off, it doesn't work.
Bug is replicable on my end. Tried it 3x. First time cut off the alarm (but turned on the screen and the snooze/dismiss pop up was there), second time, alarm worked fine (but screen didnt turn on), 3rd time (same as the first)....suffice to say, behavior is inconsistent (i also use a PIN accessed lockscreen, which might be partly to blame for the wonky wake up, but not the alarm cutting off)
(confirmed, the PIN lock screen interferes with the snooze/dismiss pop up)
Thanks for all the feedback
...
Like other have stated while browsing most noticeable on chrome, sometimes while i try to type on the address bar it gets stuck, or i cant backspace to delete.
This is not the first place I've heard complaints of Chrome being less than ideal (in terms of performance). I switched to DolphinHD before the update to JB as i was dissatisfied with Chrome's performance under ICS too. FWIW. the short version of the explanation that i was given, is that chrome is still beta (technically) and has a bit of generational/iterative work to do to catch up with the (relative) stability of the stock android browser. I really like Chrome for the Google Account sync, but the performance was a little lacking, imho.
"Sleep of death" issues here as well.
I have SetCPU on my tf300, and the slowest frequency in the stock kernel is 51MHz(!) (my phone runs in the 200s minimum), so i wonder if the ultra low frequency on rest/screen-off/sleep (interactive governor with noop scheduler) has something to do with that....testing......
tested it 5x (crap for sample size, but i have work to do, haha) - and 4 times, the alarm woke up the tablet successfully, 1x it did the 1/2 second alarm and cut off sound (but the snooze/dismiss popup was in the notifications bar). (this was with the minimum frequency between 200ish and 400ish MHz). so even with the min-freq jacked up, it still messed up, but was better, maybe(?). I will probably tweak the governor settings as well, as now i'm curious, but that will have to wait a bit.
Obviously there are some issues here, but I wonder if some of them might be kernel related (which would help explain why some custom ROM users are having zero problems)
I can handle a few quirks, but an alarm that isnt 100% is unacceptable. Not ready to lay the blame on the JB update yet (i never ran the same tests under ICS), but hopefully this is just a growing pain that is fixed in the next update. If not for warranty, i'd just unlock and try different kernels, but for now, i want that safety net.
---------- Post added at 03:05 PM ---------- Previous post was at 02:55 PM ----------
ok - because i cant help myself, i turned off the lockscreen (set to none, instead of PIN or anything else), and the alarm wakes the tablet, turns the screen on, and pops up the snooze/dismiss dialogue every time (so far, small sample size).
i take back my comment about kernels...seems to be some sort of friction between the alarm/wake routine and the lockscreen routine. at least till one of you who is also having the issue chimes in that you have no security settings either, and it still doesnt work... heh heh.
