Hello,
My phone has been doing this weird thing where my system time would go back about 20 days. This would occur randomly and for some reason would only occur in the morning around 7-9am(pacific time). Eventually it would revert back to normal. It is extremely annoying when it happens because:
- My morning alarms create about 20 instances of themselves.
- Games dependent on system time(Happy Street, Farmville, etc.) think I'm cheating and I can't play them anymore.
- My android tasker resets and causes my phone turn off silent mode while I'm at work.
My phone specs are:
Verizon Galaxy S3(SCH-I535)
Synergy Rom v1.7(Android 4.0.4)
There are some things that may need to be considered such as:
- I upgraded from Synergy 1.6 to 1.7 w/o doing a full wipe. Just your typical cache wipes.
- I have android tasker v1.3.1m
- I tried doing the GPS fix on the android development forum. Since then, I have had trouble with syncing to my google account. Random disconnects, etc.
I'm trying to figure out if any one of these may be the cause, but I vaguely remember the exact date I updated to 1.7 or when I tried doing the GPS fix. Any ideas out there?
Thanks in advance.
So I turned off android tasker to see if this incident would happen again and it did occur again. I can mark off android tasker as the cause of this.
lawpnoy1 said:
So I turned off android tasker to see if this incident would happen again and it did occur again. I can mark off android tasker as the cause of this.
Click to expand...
Click to collapse
I would revert back (you did make a backup , right?) if you have a nandroid backup restore it if no backup factory reset and flash the old 1.6.
Then if you still have the problem you've ruled out just about everything you've said you did and you may have some bad HW.
Did you try to fix permissions? It is a long shot, but, you never know.....
Sent from my SCH-I535 using xda premium
Thanks for the suggestions, though I would like to try and not have to revert to my backup.
However, I did find that after uninstalling the alarm app I use(alarm droid), my system time did not malfunction so far. I will keep the post up to date on this for the next week or so to see if that may have been the cause.
I'm thinking that when I upgraded to 1.7, my alarm profiles in the alarm droid app may have malfunctioned and thought there was an alarm on a date prior to upgrading. When the alarm would activate, it would change my system time, but after a few seconds would revert to the correct time since it's getting pulled automatically from the network. We shall see.
lawpnoy1 said:
Thanks for the suggestions, though I would like to try and not have to revert to my backup.
However, I did find that after uninstalling the alarm app I use(alarm droid), my system time did not malfunction so far. I will keep the post up to date on this for the next week or so to see if that may have been the cause.
I'm thinking that when I upgraded to 1.7, my alarm profiles in the alarm droid app may have malfunctioned and thought there was an alarm on a date prior to upgrading. When the alarm would activate, it would change my system time, but after a few seconds would revert to the correct time since it's getting pulled automatically from the network. We shall see.
Click to expand...
Click to collapse
Don't know why an alarm clock would ever need to change your time but good luck.
If not you can make a backup and then revert. If that doesn't fix you can revert back to the broken one. But going back is the fastest way to figure out if it was your changes or even the ROM that caused the problem.
Piiman you're right, the alarm clock has nothing to do with it. It went back in time this morning again to September 3rd. I will go ahead and try backing up and restoring an older instance of the ROM when I have some extra time on my hands. Thanks for the support and I'll keep everyone up to date on this issue.
lawpnoy1 said:
Piiman you're right, the alarm clock has nothing to do with it. It went back in time this morning again to September 3rd. I will go ahead and try backing up and restoring an older instance of the ROM when I have some extra time on my hands. Thanks for the support and I'll keep everyone up to date on this issue.
Click to expand...
Click to collapse
That's to bad but good luck with the next step.
It may well be something is broken though HW rise. Normally you would have several reports of the problem if its was a ROM. I can't remember what else you said you changed but if that's un- doable you may want to start there. However like I said previously I'd just revert back. You may even consider going all the way back to Stock, if it happens then you can just call VZW for your replacement.
Related
I've been having a weird issue for the past few weeks where my phone will lock up and the screen won't turn on anymore. Often, it happens with the phone in standby in my pocket. I'll feel a vibration (sometimes just 1 vibration, sometimes followed by the usual 3 fast vibrations of a force close) and then the phone is gone. I have to hold all 3 buttons to reset it and then it boots up fine like nothing is wrong. I've had this same issue on various roms I've used lately (Serendipity, Firefly, Cog4, etc.) and on my last flash I've even done the full flash to stock and master clear. Is anyone else having any issues like this?
I'm guessing this is 1 of 3 things:
1) I have a hardware problem with my phone and need a new one.
2) This is an issue with custom kernels with lagfix and I have to live with it or use a stock kernel. I know some custom kernels have had charging death issues (I've seen that happen to me also but idk if its from charging or the same thing as when its in my pocket)
3) Some app I installed is causing this. I have a hard time believing this can be the problem only because any app issues I've seen in the past just show up as a FC and don't take out the entire phone. If this is in fact an app issue, IDK how I'll ever figure out which one is causing it since it just dies and I don't get a chance to see a FC message or anything like that.
Any thoughts or suggestions are appreciated as I really don't know what to do at this point. My next step is probably going to run pure stock froyo for a few days to see if I still have the issue but I suspect I will since its been present on every rom config I've used. Whats even worse is, if it happens and I don't notice for a while, when I finally reboot it the battery is severely drained. Its like something gets in an infinite loop and kills the battery depending on how long I leave it like that (the phone also warms up when its been in this state for a while).
Thanks in advance for any help!
Sounds like a warranty replavement to me.
Caution swyping! Read at your own risk.
TheSopranos16 said:
I've been having a weird issue for the past few weeks where my phone will lock up and the screen won't turn on anymore. Often, it happens with the phone in standby in my pocket. I'll feel a vibration (sometimes just 1 vibration, sometimes followed by the usual 3 fast vibrations of a force close) and then the phone is gone. I have to hold all 3 buttons to reset it and then it boots up fine like nothing is wrong. I've had this same issue on various roms I've used lately (Serendipity, Firefly, Cog4, etc.) and on my last flash I've even done the full flash to stock and master clear. Is anyone else having any issues like this?
I'm guessing this is 1 of 3 things:
1) I have a hardware problem with my phone and need a new one.
2) This is an issue with custom kernels with lagfix and I have to live with it or use a stock kernel. I know some custom kernels have had charging death issues (I've seen that happen to me also but idk if its from charging or the same thing as when its in my pocket)
3) Some app I installed is causing this. I have a hard time believing this can be the problem only because any app issues I've seen in the past just show up as a FC and don't take out the entire phone. If this is in fact an app issue, IDK how I'll ever figure out which one is causing it since it just dies and I don't get a chance to see a FC message or anything like that.
Any thoughts or suggestions are appreciated as I really don't know what to do at this point. My next step is probably going to run pure stock froyo for a few days to see if I still have the issue but I suspect I will since its been present on every rom config I've used. Whats even worse is, if it happens and I don't notice for a while, when I finally reboot it the battery is severely drained. Its like something gets in an infinite loop and kills the battery depending on how long I leave it like that (the phone also warms up when its been in this state for a while).
Thanks in advance for any help!
Click to expand...
Click to collapse
What kernel are you running? And are you OC/UV?
If so, try a different kernel (like speedmod k13e) that doesn't have OC/UV option. Black screen is usually a UV setting problem.
If it's not the case, warranty?
EDIT: Have you flashed over different ROM with lagfix/ OC/UV enabled?
Right now I'm running lastest Cog 4 with the included kernel (which doesn't support UV). I was OC but once I had this issue I reset the clocks to stock but then it happened again. Before I installed Cog 4 I flashed stock and master cleared...
1. Did u restore any data using TiBu when u flashed the ROM? Did u happen to restore any system data?
2. Did u put on any kind of under volting?
Flash any ROM, say Firefly, and use it for a day or two without restoring any of ur apps, and see if the issue is coming up again.
If yes, try changing kernel, say to onix, and keep on for a day or two see if the issue is recurring.
Just to be sure, can u do this:
1. Revert to stock
2. Format internal SD (similar to master clear to clear out SD card; I never did a master clear so far, only this)
3. Copy the ROM u want to use to SD
4. Flash Firefly 3.0 (this formats all system partitions, so no need to master clear)
Firefly has hardcore's kernel by default, and this kernel does not apply lagfix by default. Same with onix kernel too, and this is the reason I am recommending this combination of ROM and kernels. I use onix cos I have some wifi issues on hardcore's kernel.
5. Do NOT restore of ur data or apps
I did restore data using TiBu but only app data. The only system stuff I restored was bluetooth pairings and wifi access points. Other than that only app data. I don't have any UV right now...
TheSopranos16 said:
I did restore data using TiBu but only app data. The only system stuff I restored was bluetooth pairings and wifi access points. Other than that only app data. I don't have any UV right now...
Click to expand...
Click to collapse
I would NOT recommend ANY system data, except for contacts storage. This is the only one system data I personally found not to cause any issues.
Its easier to connect BT and wifi again, than go through the pain restoring this data sometimes creates. I faced issues with my phone not being paired to my car when I tried to restore bluetooth settings. It shows my car, but doesn't pair. I had to restart phone, delete the connection, and then reconnect. I found it easier to add back, than restore and go through all this trouble.
This time, pls try to refrain from restoring any of ur data from TiBu and a day's run for the ROM and see how it goes. If it goes well, u can restore data. But, before u restore data, I would recommend taking a nandroid backup just in case restoring apps starts creating issues again. This could save some time by getting u back to current state with no apps, instead of flashing all over again.
Before doing any of those things, I would check out your IMEI number and compare it to the one in this link,
http://www.captivateforums.com/sams...random-shutdown-issues-on-att-captivate-1272/
I dont pay for any warranty through AT&T, but I brought my phone in to a device replacement center and they replaced mine with a brand new phone!
Its worth a shot if you ask me.
What the hell is going on. I tried resetting and everything, even exchanged the device and the new one is doing the same thing! Also vibrating and force closing it is getting on my nerves! The followig seems to happen after a while I am TIRED of having to turn of my phone and turn it back on! ~ I go to play a .mp3 it says " FIle type not supported"...My .mp3 ringtone does not work the phone just vibrates the selected ringtone doesnt work. I got too take a picture or record video it says "Camera Failed"....I get a visual voicemail....the "play" button is grayed out and I have to turn off phone turn it BACK On just to check my voicemail. Also occassioally my sms wont work either. I turn my phone off and on every morning and throughout day I notice this and its getting REAL annoying !
Well first off, this isn't a software flaw, this is specific to you, as we have many users here including myself who are using these phones daily without the issues you are describing.
You had said that the issue was with an mp3, can you upload that somewhere for us to test on our phones?
As far as the camera and visual voicemail, I've never heard of that issue before, perhaps you ended up with a bad phone again?
I am getting the frequent force close with messaging. I also have had problems with the camera and idk about the mp3 stuff I haven't put any ringtones on the phone yet. This is getting really annoying I agree.
I don't have any issues with mine? Have you guys done anything like rooting or flashing anything?
Nope, completely stock. The most I have done is take a screen shot lol.
hmm maybe some have a defect? It's not all SK4g's though, as some of us have no issues at all. I would suggest getting it replaced by T-Mobile, as this is a factory defect. not sure why that happened to you guys. has anyone else had these issues and found any fixes?
That's kinda tough the hearest t-mobile is like 4 hours from here /:
One of my friends who went with me on the trip to get the SK also got one and he says he's never gotten a force close so you may be right. But could it have anything to do with the amount of texts I send/receive? Because I have to admit it is pretty excessive. The failing to send messages when I am receiving one simultaneously is expected, but not the force closes in my opinion.
It shouldn't force close on you. I know mine fails to send every once in a while too, as I text a lot (kinda the reason I got the phone). failing to send isn't as big of a deal, as it notifies you and you just have to click resend. Not entirely sure why it's force closing though? I wonder if a logcat might help? if you have adb installed, you can try adb logcat and see what shows up when you force close? if we can find the issue there, it might be fixable from our end. all depends on where the flaw lies/if it's just a bad apk somehow or if there's an actual hardware issue or something.
I'll do a log next time there is a fc, I'm having another issue or it may be related, but this one is with WidgetLocker I believe. Sometimes when I go to unlock the phone it'll freeze up and then I dont know how to explain it, but it almost seems like it resets but it really doesnt. The phone will blackout for a little then the homescreen will pop up and service will gone for a while until the cards are read just like if I rebooted.
That might be a function of WidgetLocker, I used it on my old G1 and it always hung and black screened at me.
sduvick said:
That might be a function of WidgetLocker, I used it on my old G1 and it always hung and black screened at me.
Click to expand...
Click to collapse
Yeah I know it does that from time to time, but on my previous phone it wouldn't do that reboot thing where it would lose connection then resend my latest text messages once it reconnected.
I'm not sure why it's doing that. My guess would be that the issues are caused because the SK4G doesn't use a normal lock screen. widgetlocker uses some modification of the system file for the lock screen, and perhaps it's not sure what to modify? just my 2 cents.
sduvick said:
I'm not sure why it's doing that. My guess would be that the issues are caused because the SK4G doesn't use a normal lock screen. widgetlocker uses some modification of the system file for the lock screen, and perhaps it's not sure what to modify? just my 2 cents.
Click to expand...
Click to collapse
That's what I was thinking too, I'm gonna uninstall it for a bit and see if anything changes.
is anyone else having an issue with notification volume? everytime i reboot my SK, my notification volume gets pushed all the way down to nothing, so i don't get a sound notification for texts, emails, etc, until i move the notif. volume back up in my settings. i did root with the one-click for the Epic 4G.
This is a new UI so alot of the apps i.e. widgets you may put on will cause issues. If you like certain apps contact the dev so your device is supported correctly. Still to new to get mad at it till sum of the bugs get worked out. I did notice a couple of times when I left screen on in pocket on accident that when I go to use it again it doesn't respond to any touch but can move courser around till rebooted then its ok. If some don't already know the sk4g is almost the same as the epic. The sk4g is still a badass phone for 100bucks.
Same as the OP
I know this is a little old, but I've experienced the same problem as the OP so it seems they are not alone with this problem.
I actually tried two different newly formatted SD cards (because I thought it may have been the SD card), and still would have the problem. Then I actually did swap phones about a month ago and it seemed the problem would now take several days to resurface instead of several hours. And I could deal with that.
Since the OTA update about 2 weeks ago, the phone has been back on it's original BS as the OP posted and it's driving me nuts. I actually missed some emergency calls last night because the mp3 ringtone didn't work so I'm finding a solution to this issue today or trashing this phone.
My belief is that there is something interfering with the phone's ability to read the SD card for media. Because other apps I have that save to the SD card or read from it work fine. So I'm going to master reset it and not download any of my apps and see what happens when I set an mp3 ringtone. If it makes it through the day with no hiccups, I'll slowly add back one app at a time until hopefully I can find the culprit.
bipoler if you'd like, we can exchange via PM what apps we both have downloaded and see if we have some in common that may be problems.
I'll post back with any progress.
I've been having the problem with ringtones not working, just getting silence when I get a call. for me it seems to happen when I set a ringtone from the app Zedge, I don't think it happens when I use ringtones from the Android System, which would make sense if the issue is related to reading the sdcard. gonna go back to a system ringtone and see what happens today.
Yeah my phone had all those problems, but I installed the Lightning rom and all those problems went away, except for the ones about messages failing...I text A LOT
Lightning ROM
Thanks for that info on the Lightning Rom. I will check that out. Phone has been working flawlessly all day with the mp3 ringtone and no extra apps besides the master reset. I might give it until the morning before I start putting them back on.
On stock id install so many apps that ran on the background that id get delay from opening closing swiping and turning onthe phone.. so I wiped it installed a custom rom and just kept the essentials.. havnt had a problem since... well.. occasionly ill have to odi but that's on purpose
Sent from my SK4G
So, about 2 or 3 days ago I downgraded back to Froyo from the latest Gingerbread leak (too many bugs.) I did so with GTG's Ulimate unbrick, and then I flashed the pre-rooted/ pre-CWM stock ROM to it. I updated to the latest UCKH1 to be up to date, and then I restored a backup I made in ROM Manager a few weeks back. After that, I restored all my apps with Titanium backup. Now on to the issues. First time around my phone literally crapped out software-wise. It was literally force closing everything, texting wouldn't work, the Advanced power menu was gone except for Power Off. That only started after a full day of use with no issues whatsoever. It was completely random. Well late last night, I factory reset and put my apps back on again. Well I woke up this morning to find that my phone's suddenly being dumb again. Except this time the only issues that I know of are, the Advanced power menu's gone except for Power Off, and the home button will not function AT ALL. If anyone has any idea what's going on, or how I can resolve this, please lend a hand.
Kevinr678 said:
So, about 2 or 3 days ago I downgraded back to Froyo from the latest Gingerbread leak (too many bugs.) I did so with GTG's Ulimate unbrick, and then I flashed the pre-rooted/ pre-CWM stock ROM to it. I updated to the latest UCKH1 to be up to date, and then I restored a backup I made in ROM Manager a few weeks back. After that, I restored all my apps with Titanium backup. Now on to the issues. First time around my phone literally crapped out software-wise. It was literally force closing everything, texting wouldn't work, the Advanced power menu was gone except for Power Off. That only started after a full day of use with no issues whatsoever. It was completely random. Well late last night, I factory reset and put my apps back on again. Well I woke up this morning to find that my phone's suddenly being dumb again. Except this time the only issues that I know of are, the Advanced power menu's gone except for Power Off, and the home button will not function AT ALL. If anyone has any idea what's going on, or how I can resolve this, please lend a hand.
Click to expand...
Click to collapse
It sound like every time you encountered a problem it was after restoring your app with TiBu. Are you just restoring apps or apps&data? See how your phone runs without restoring apps. Try restoring apps(without data) and see what happens, or just manually download apps again. Could be a problem with data from the apps.
bigfau said:
It sound like every time you encountered a problem it was after restoring your app with TiBu. Are you just restoring apps or apps&data? See how your phone runs without restoring apps. Try restoring apps(without data) and see what happens, or just manually download apps again. Could be a problem with data from the apps.
Click to expand...
Click to collapse
I was wondering the same. I have indeed been restoring apps with data. Didn't want to lose my Cut the Rope progress But, they may end up being my problem. I've always gotten away without issues, so I guess it's about time for one to happen, haha. I'll try it out after work today and post how it goes.
Kevinr678 said:
I was wondering the same. I have indeed been restoring apps with data. Didn't want to lose my Cut the Rope progress But, they may end up being my problem. I've always gotten away without issues, so I guess it's about time for one to happen, haha. I'll try it out after work today and post how it goes.
Click to expand...
Click to collapse
Most likely the problem lies with the backups being from a GB rom and now you are trying to put them an a Froyo rom. Probably saves it differently or something.
They tell you "Not" to use the backups from Titanium as they can cause issues, I reinstalled back to Stock Froyo as well running the latest UCKH1, When you do the Update to UCKH1 my advice is to go to Settings: Privacy: and do a Factory reset to fix the clock problem The clock will appear screwed up and will correct itself even when it's on Automatic Mode. Otherwise all is fine downgrading from GB Rom. Install all normal apps as usual, Screw Titanium my advice is just save the .apk file for the app in a Folder on your External SD Card, that's my quick way of reinstalling all my apps back regardless of losing settings.
you can also use tibu to restore single apps with data, you can try the ones you want to save progress and see if it causes issues. just stay away from system apps
I've never ha a problem with TitBU, as long as I restored "missing apps & data" ONLY!
same here, regardless of android version or even restoring on a different device. the only time i have seen issues is when i accidentally hit restore all apps with data, including system apps. thats when i got the constant fc and crashing
bigfau said:
Most likely the problem lies with the backups being from a GB rom and now you are trying to put them an a Froyo rom. Probably saves it differently or something.
Click to expand...
Click to collapse
You know, now that I think about it I actually made a backup from UCKJ2. That's more than likely my problem. Funny how I'm looking for all these complicated things and it ends up being something easy. Haven't restored anything, so I'll wait a day or two and see if everything stays like it should, and then I'll restore only what's needed to ensure it stays that way. Sorry it took so long to respond, had work, haha. Thanks guys all the responses were much appreciated.
Kevinr678 said:
You know, now that I think about it I actually made a backup from UCKJ2. That's more than likely my problem. Funny how I'm looking for all these complicated things and it ends up being something easy. Haven't restored anything, so I'll wait a day or two and see if everything stays like it should, and then I'll restore only what's needed to ensure it stays that way. Sorry it took so long to respond, had work, haha. Thanks guys all the responses were much appreciated.
Click to expand...
Click to collapse
You should be alright as long as you don't restore data. I think. Lol
Sent from my SAMSUNG-SGH-I997 using Tapatalk
Soo.... I'm guessing there's no good solution, but posting anyway..
Suddenly, whenever I do a battery pull (frozen device or just swapping batteries) .... when I boot the phone back up, the date/time has reset to sometime in 2006 at 6:00pm...
I have the checkbox to automatically update date/time checked in Settings... this happened with CM7 and is also happening with MIUI now..
I downloaded an app to auto-sync date and time, but it doesn't kick in until several minutes after bootup if at all... so whenever the clock is fixed, all sorts of apps are affected - anything that tracks by date thinks 7 years just passed! Alarms go off, app alerts go off, etc..
I suspect this may be a capacitor/small battery used for keeping the time, inside the phone going bad ... anyone else had this happen to their g2x? Am I wrong in suspecting there's no fix?
lotherius said:
Soo.... I'm guessing there's no good solution, but posting anyway..
Suddenly, whenever I do a battery pull (frozen device or just swapping batteries) .... when I boot the phone back up, the date/time has reset to sometime in 2006 at 6:00pm...
I have the checkbox to automatically update date/time checked in Settings... this happened with CM7 and is also happening with MIUI now..
I downloaded an app to auto-sync date and time, but it doesn't kick in until several minutes after bootup if at all... so whenever the clock is fixed, all sorts of apps are affected - anything that tracks by date thinks 7 years just passed! Alarms go off, app alerts go off, etc..
I suspect this may be a capacitor/small battery used for keeping the time, inside the phone going bad ... anyone else had this happen to their g2x? Am I wrong in suspecting there's no fix?
Click to expand...
Click to collapse
Actually this happens to me everytime I swap my batteries, but date and time always correct themselves once the sync with a network, for me usually under a minute. I don't have any app issues though because of the incorrect time at start up. Very odd.
Sent via Sosei "III" BakedBean Iconia A100/4.1.2 AOKP/AOSP Hybrid
Hello, i have my nexus 5 for 2 weeks now and I noticed a problem my friend with a N5 doesn't have.(or anyone else) At night, right before I sleep i put my phone on silent so i dont get awakened by calls or anything else . But if i set it on silent the alarm volume gets on silent as well.
Seriously, i didn't have this problem on any other device and everyone sets his phone on silent for obvious reason. I had android 4.2.2 on my older device and even there you could tick "Alarm on silent".
What's causing this bug?
Stock Android 4.4.2
Edit: this is a basic feature every phone has, please dont suggest me getting 3rd party alarms from the google play store, thanks.
Try checking the alarm volume in settings and see if it changes when you put the phone in silent/vibrate.
It shouldn't.
Yes, when i put it on vibrate/silent i cant even scroll the alarm's volume in settings , it goes straight to no volume.
There's a post with users complaining about the exact opposite. They want to know why the phone isn't 100% silent when in silent mode. This would contradict what's happening to you.
Sent from my Nexus 5 using Tapatalk
bblzd said:
There's a post with users complaining about the exact opposite. They want to know why the phone isn't 100% silent when in silent mode. This would contradict what's happening to you.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Ok, what can i do to repair this bug?
I just tested this on my Nexus 5, and I can confirm that this is NOT happening on mine. Setting the phone to vibrate or even silent has no effect on my alarm setting whatsoever. (See the attached image. Note the vibrate icon in the notification bar.)
Do you possibly have a third-party alarm or other sound-controlling app installed? You say your phone is stock, but do you have anything such as Xposed, that can affect system settings?
I know it's probably the last thing you want to do, but you might try doing a hard-reset, and seeing if the conditions persist BEFORE installing any 3rd party apps. If it's working normally at that point, then keep checking it as you reinstall your apps to see if you can narrow down the culprit. If it DOES persist with a freshly wiped device, then you may want to call Google support, as that would be considered a defect.
Oh! Also, make sure you're on the latest build (KOT49H). If you're on an earlier build for some reason, it could be why your device is acting differently than everyone else's.
jt3 said:
I just tested this on my Nexus 5, and I can confirm that this is NOT happening on mine. Setting the phone to vibrate or even silent has no effect on my alarm setting whatsoever. (See the attached image. Note the vibrate icon in the notification bar.)
Do you possibly have a third-party alarm or other sound-controlling app installed? You say your phone is stock, but do you have anything such as Xposed, that can affect system settings?
I know it's probably the last thing you want to do, but you might try doing a hard-reset, and seeing if the conditions persist BEFORE installing any 3rd party apps. If it's working normally at that point, then keep checking it as you reinstall your apps to see if you can narrow down the culprit. If it DOES persist with a freshly wiped device, then you may want to call Google support, as that would be considered a defect.
Oh! Also, make sure you're on the latest build (KOT49H). If you're on an earlier build for some reason, it could be why your device is acting differently than everyone else's.
Click to expand...
Click to collapse
Hard restted once with the apps being restored and it was the same, then i hard resetted the last time without signing in my google account and everything works fine now, thanks!
did you ever find out which app caused this? i have the same problem
it might be a late answer, but it may help anyone who happens to find this post with this issue (as i did)...
I was having the exact same problem with my alarm, but I noticed that it happened after installing "Alarmy (Sleep if you can)" app from play store. It somehow overrides system volumes, and locks it after uninstall.
I reinstalled it and set the alarm volume from inside that app, and now it works as expected to do (silient ringer with alarm on).
This might happen with other Alarm apps, remember if you did install any.
Hopefully it helps someone, as this happened even on 4.4.4
I was having the exact same problem
joaquin.mik said:
it might be a late answer, but it may help anyone who happens to find this post with this issue (as i did)...
I was having the exact same problem with my alarm, but I noticed that it happened after installing "Alarmy (Sleep if you can)" app from play store. It somehow overrides system volumes, and locks it after uninstall.
I reinstalled it and set the alarm volume from inside that app, and now it works as expected to do (silient ringer with alarm on).
This might happen with other Alarm apps, remember if you did install any.
Hopefully it helps someone, as this happened even on 4.4.4
Click to expand...
Click to collapse
I have figured out that problem happened after installing "Xtreme alarm clock."
And I solved this problem with "Alarmy(Sleep If U Can)."
Thanks for your information.