Just recently got the Shift and so far its a big nice upgrade from the hero.
I don't currently have root access and am pretty much running stock everything, with the exception of Launcher Pro and some custom icons.
The issue I am running into is that occasionally my alarm clock goes off w/o the option to snooze or dismiss.
The only way to remedy this is to yank the battery... (at least thats how I deal with it at 6:am and I want to snooze)
Anyone else have this problem or know of a way to fix it?
Thanks.
I had the problem show up a few times on my Hero before the official 2.1 release, but I don't remember if anything I tried fixed it. Just letting you know it's not just you.
I know the alarm clock snooze/dismiss settings are tied to HTC Sense. Maybe launcher pro is messing with Sense somehow.
I think the controls to dismiss or snooze the alarm are tied to the lock screen. I don't use launcher pro, but I wonder, does launcher pro replace the stock lock screen?
Ive had similar problems...im stock rooted and still using sense and occasionally have this problem...i usually use audio manager widget to lower the volume so its not driving me crazy and then set a new alarm for like a min later...when the snooze/dismiss options appear for the new alarm i hit dismiss and all the alarms stop
Why not install DeskClock.apk?
Sent from my PG06100 using XDA App
shaunmt said:
I think the controls to dismiss or snooze the alarm are tied to the lock screen. I don't use launcher pro, but I wonder, does launcher pro replace the stock lock screen?
Click to expand...
Click to collapse
No, it doesn't.
^ Shift Faced
That's the same way I've been solving it Seems that if I turn off the phone (Kyocera Zio 2.2) whilst having an app on screen (ie turn it off from within an app or fxn) the incidence is quite high. If turned off from home screen, doesn't occur (or at least not very often - can't quite be sure, but 95% certainty) Just wanted to make someone aware of it. Glad to see it wasn't just me who noticed it. Having to take the case off, battery out, et al are annoying, and just seems a goofy fix for what is generally a nice piece of equipment! Someone else (Hero user?) is changing their vol setting and then setting another alarm for a min later to have the shut-off option appear. I may try that in the future. THANK YOU for the site!!
Related
Okay, so I've noticed that on both my lock screen and Clock app, that my alarm clocks don't show up as the Human Readable time format. For example, I have an alarm set for 6am tomororow (1/12/2010), and when the lock screen is showing it has the alarmclock icon and show "1263294000000" next to it, which is the epoch time for 1/12/2010 6:00:00 am. It also does this in the clock app on the app's home screen, but if I go into the alarms screen it shows up fine.
Anyone else experiencing this?
Weird. Mine shows up in a normal time. I've tried looking through the clock app, and system settings and couldn't find a way to replicate your issue.
Since yours is rooted it may have something to do with what youve flashed to it so far.
Or maybe not cause im rooted with cyan and just tried and it appeared fine
JoshHart said:
Or maybe not cause im rooted with cyan and just tried and it appeared fine
Click to expand...
Click to collapse
Lol. Yah. I've got a few friends around here that have basically the same setup. Not really an issue, more a nuisance. But I seriously don't get it. I'll probably try and reset later today and recreate it. I was just curious if any one else noticed this.
Strange.
I have another question for the clock app:
Is there a way to turn off the charging light and the backlight on the capacitive buttons when in the dimmed clock app mode? The screen is actually quite nice and readable in the dark but the bright lights next to it are annoying / wash the screen out some.
Maybe it's something in Locale settings? That's where I'd look.
bradyonly said:
Maybe it's something in Locale settings? That's where I'd look.
Click to expand...
Click to collapse
Trust me, I went through just about every possible 'setting' i could possibly think of. I'm assuming it has something to do with a program i have installed. I haven't had the time to do a reset yet, but plan on giving it a shot later.
Here's what I know though, its not normal, and its not because of root. Seems no one else is having this issue. lol, WTF.
Hi all. I've just been wondering... has anyone else besides me ran into countless problems using the Nexus Launcher/Launcher2 on their phone? I'm running Fresh 2.0d with the included .apk, and here are some bugs I've found:
Unresponsiveness
Screen turns black and stays black requiring a battery pull
Launcher will launch without displaying icons in the menu
Now, it is not only Flipz's ROM that has these problems either... it is EVERY ROM I've tried. I'm sure most of you will tell me to use Helix Launcher. I have tried it, but it doesn't have the same feel that the Nexus Launcher has.
Has anyone found a fix for these stability issues? If not, I'd like to start a project so we can get this working, because I'm sure it's completely possible. After all, Flipz was able to get the 2.1 lockscreen working!
mrinehart93 said:
Hi all. I've just been wondering... has anyone else besides me ran into countless problems using the Nexus Launcher/Launcher2 on their phone? I'm running Fresh 2.0d with the included .apk, and here are some bugs I've found:
Unresponsiveness
Screen turns black and stays black requiring a battery pull
Launcher will launch without displaying icons in the menu
Now, it is not only Flipz's ROM that has these problems either... it is EVERY ROM I've tried. I'm sure most of you will tell me to use Helix Launcher. I have tried it, but it doesn't have the same feel that the Nexus Launcher has.
Has anyone found a fix for these stability issues? If not, I'd like to start a project so we can get this working, because I'm sure it's completely possible. After all, Flipz was able to get the 2.1 lockscreen working!
Click to expand...
Click to collapse
I am running fresh2.0d and stock screen turns black and needs battery pull when I use camera app and hit back button or any button.
Launcher has been pretty responsive except here and there....
I do get to the mode where no icons on home screen for few seconds at times but it recovers pretty soon....
As far as the lock screen, I ran in to an issue while my corporate policy forced me to assign lock/unlock password! Soon I enable password and lock, phone stops responding!!! I have to either pull the battery or issue reboot command via prompt!!!
I hope this helps.... I am not a developer though....
I have been disappointed by the nexus launcher's performance as well.
The black screen requiring a reboot (or if you hold home and happen to have settings in the app switch menu you can force kill it and restart it) is a common occurrence with seemingly no pattern. Sometimes it after a long browsing session, other times its happens after deleting a single e-mail message and returning to the main screen. The only consistent way to make it happen is to hit back after launching camera from the app drawer.
Ive also noticed in every rom with launcher, that when coming out of the launch screen the app shortcuts and widgets on the home screen don't load instantly. Almost as if the launcher was killed while it was asleep and when unlocking it, it is reloaded.
It's disappointing because as you said, while helixlauncher is an OK alternative, nothing else has quite the same feel as nexus launcher. Unfortunately I think it will take a good bit of modification to make it a perfect match with the hero and I have absolutely 0 idea where to even begin .
Flipz, if you ever read this, could you offer some insight on this? You've worked your magic on the 2.1 lockscreen
The only rom i had it running great on was Darchlegend v4.1 i think it was, i finally said forget it and started using helix
Every one i have tried has been buggy as well. Things mught improve once we get the hero 2.1 source. Or once google decouples them.
I was in a phone call when my (stock) alarm went off, ended the phone call and had no way to get into my alarm to turn it off. I could get into the alarm settings etc. but there was no way to turn it off, just the settings for it.
This seems like it happens to me every time I use the alarm (which isn't often). I cant shut the damn thing off - and have to pull the battery. It doesn't matter what I am doing at the time the alarm rings. What is the trick to it?
If you guys are using a aosp Rom with cm7 lock screen sense clock alarms will not shut off when using them so either get the HTC lockscreen apk to use the sense alarms or just use desk clock apk u can find it on a few roms. Or in the forums works for me. Cm7 lockscreen will cause issues with sense alarms not shutting off.
i've only had that issue when using a sense rom with asop lockscreen... but i believe that is an old problem and i dunno about a resolution
i have used alarm droid in the past to by pass the normall alarm does all the same and even backs up ur settings alarms from rom to rom which is kind of nice
ben.nesheim said:
i've only had that issue when using a sense rom with asop lockscreen... but i believe that is an old problem and i dunno about a resolution
i have used alarm droid in the past to by pass the normall alarm does all the same and even backs up ur settings alarms from rom to rom which is kind of nice
Click to expand...
Click to collapse
Get desk clock apk from cm7 or find it on here use it instead of sense alarms works fine.
I have desk clock and thats the one that wouldnt turn off. any other suggestions?
I am on the official CM10.1 RC2. I didn't flash anything else other than a fix for Wi-Fi ARP when in sleep mode, as well as an older radio to enable LTE.
What has been going on every since I flashed my first CM10.1 nightly (got the phone on May 2) is that every other time I wake the phone, the lockscreen widgets disappear.
This is a 100% predictable and totally consistent pattern. If I wake the phone and my lockscreen widgets are visible, then the next time I lock the phone and wake it, the lockscreen widgets disappear. If I wake the phone and my lockscreen widgets are missing, I can guarantee they'll come back if I immediately lock and wake it again.
I know it's not an Android 4.2 problem, because my sister's HTC One S doesn't have this issue and it's set up the same way.
To illustrate what I mean, these are the two states my lockscreen always alternates between:
Been trying to find an answer for this... maybe I'm not using the right keywords :/
EDIT: SOLVED - Turns out Lockscreen Policy was the culprit. I disabled both widgets and camera and that was causing cLock to disappear every other time. Allowing widgets while disabling the camera eliminated the problem. Hope this helps others in the future!
Make sure you don't have two lockscreen clocks. If so, delete one.
Sent from my Nexus 4 using xda premium
El Daddy said:
Make sure you don't have two lockscreen clocks. If so, delete one.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I don't think I have two clocks. All I can find in the settings is the "Clock widget" in the Lock screen section which is what I want to use.
Any idea where I might have accidentally placed a second clock if that's the case? I didn't download any clock or calendar apps - I use the stock ones. I did restore a lot of stuff from Titanium backup on my old phone, but I clearly remember that system settings wasn't something I restored.
edit: I checked Titanium Backup and noticed that the "Clock" app (not the cLock app/widget) had been restored from my previous phone which ran CM10, not CM10.1. I remember that on CM10, the clock was right-justified, not centered, and that is what my 2nd screenshot (the scenario I want to get rid of) is showing.
Is it possible that I inadvertently restored the CM10 lockscreen clock from my old phone? I hope that doesn't mean having to wipe. I really can't find anything in the settings that might indicate the presence of more than one clock.
EDIT: SOLVED! It turns out that the Lockscreen Policy app was the culprit. I had disabled both widgets and the camera in Lockscreen Policy because I don't want people messing with my phone as a joke (otherwise what's the point of a PIN...). Re-enabling the widgets while keeping camera disabled solved everything. I confirmed that disabling widgets in Lockscreen Policy would immediately bring back this problem.
Tbh, I'd prefer having the old CM10 lockscreen, without those side widgets or the camera, and the ability to slide to a ring shortcut before bringing up the PIN
I have the Verizon LG G2. Not rooted all stock launcher etc.
I use the stock alarm clock app and for the last two days, it has been snoozing itself. I'll wake up without the alarm and it says, "snoozed until". That is what it says when you manually snooze it.
I did some testing this morning, and actually found it snoozing itself, screenshot attached.
I download a different alarm app and that one works just fine. I have looked through other posts regarding this but none are recent or in regards to the G2. If there is a solution that I am not seeing, let me know.
I have tried clearing app data and it still snoozes on its own.
Any help would be appreciated.
Now it is snoozing only the first attempt. The second, 5 min later, alarm is going off..
Bump
dudewithspots said:
I have the Verizon LG G2. Not rooted all stock launcher etc.
I use the stock alarm clock app and for the last two days, it has been snoozing itself. I'll wake up without the alarm and it says, "snoozed until". That is what it says when you manually snooze it.
I did some testing this morning, and actually found it snoozing itself, screenshot attached.
I download a different alarm app and that one works just fine. I have looked through other posts regarding this but none are recent or in regards to the G2. If there is a solution that I am not seeing, let me know.
I have tried clearing app data and it still snoozes on its own.
Any help would be appreciated.
Click to expand...
Click to collapse
Go into alarm settings and if you flip action or shake action enabled. If so then that's prob the culprit.
simon_lefisch said:
Go into alarm settings and if you flip action or shake action enabled. If so then that's prob the culprit.
Click to expand...
Click to collapse
Thanks for your help.
I looked into settings of the app, and there aren't any activated around flip or shake. However, there are a few around the back buttons (LG G2). Even still, I disabled those and it is still functioning this way. I downloaded an alarm clock app from Play Store and it works just fine.
Wondering if even trying to figure out what is going on is worth my time or effort.