Lost Lockscreen sounds wiped, formatted, ad reflashed no luck. - AT&T Samsung Galaxy Note II

I have been using CleanRom SE ATT 1.2 on my rooted Galaxy Note 2 for a while now. But something recently happened...
When I unlocked my screen with a swipe there was no sound, only the graphics of the water refraction. I first checked the volume and it was up. So I played some music it worked. I think that there used to be keyboard sounds also... Something just seems missing when I am typing.
So I thought what the heck I will just reflash. I reflashed and wiped everything except the "format data" (only because the TWRP 2.4.1.0 mentioned "most of the time you do not need to do this", Well that didnt work. New fresh rom and no sounds of the water again. So this time I wiped everything: cache, dalvik cache, factory reset, system, internal storage, and format data. All!
Still no sound in those particular areas. I have flashed this rom at least 5 times before this ever happened.Now I flashed 3 times trying different wiping and formatting methods and it is not working. What could have possibly happened?
note: The last thing I was doing was using rom toolbox to disable widgets from loading (so apps have like 20 widgets FN ridiculous!) That is the farthest I have ever gone with messing with system files and delving deep into my phone.
Any suggestions?

Well I found the problem... settings > sounds > locks screen sounds. This should have been a simple fix but I never thought to scroll to the bottom of the sound options to find a lockscreen sound check box.
The reason I never checked is because it was always default on and I have flashed quite a few times and never had to check or uncheck this box. But all of the sudden one day the sound is gone. And I reflash (LOL) and the default is not there.
SO I have a more technical questions. Why would this setting not go back to default even after flashing? Where exactly is this option stored? Google!?

Related

Constant Rebooting

Everything has been fine until yesterday morning, when at work I realised my phone was rebooting every 3 or 4 minutes.
I hadn't changed anything, I hadn't flashed anything, I don't O/C my phone. I'm usins AOKP Milestone 3 with Immoysen Kernel.
I've tried -
Reflashing AOKP with no custom kernel
Wipe & flashing CM9 Kang
Wipe & flashing MCR
When I tried to make a Nandroid of MCR (as it seemed to be okay for an hour or so) it gave an error when it got to backing up the data partition. Could their be a corrupt bit of memory there?
Also, at one point I think it might have reset while in recovery, which makes me think it's hardware, not software.
Today I've tried -
locking and unlocking the bootloader
Android_Revolution_HD_Super_Wipe_Lite
Wipe and flash AOKP B23
Generally it seems to be better after a wipe and a fresh install, for a little while, but then seems to start rebooting again later.
I locked and unlocked again around an hour and a half ago and all seems good at the moment, but I thought I'd post still to see if anyone else has had this happen or see if anyone has ideas of how to de-bug it should it come back?
I had this problem after upgraded to 4.0.2. Fresh install did solved this somehow but last week it came back again when dial starts...
Tho it seems un-checked all options in location services would not reboot during or after the call
Hope this info could help u
Thanks. Well, 6 hours since I locked the bootloader and unlocked it again (to wipe everything, including the SD storage) and it's not rebooted once. Looks like it's fixed *touch wood*
I have random turn offs... dunno if it relates. Its a little unnerving...and annoying. No roots, no unlocks, just vanilla 4.0.2.
Sent from my Galaxy Nexus using XDA App

Sound profile set to 'normal' again after (re)start

Hi all,
every time when I start or restart (normal or hot) my DHD the sound profile will be set to 'normal' independent from the selected sound profile before. I select the 'just vibrate' sound profile, shut down and restart or just restart my DHD again. At the beginning the previous selected sound profile is active but suddenly it changes to 'normal' again.
The day before yesterday I have flashed LeeDroid 5.1.1. Thus I assume the issue has to do with LeeDroid (not sure if this is really the case). I was not able to find anything in the settings and don't have an app installed which could do that. Furthermore I was not able to find anything regarding this topic via Google or forum searches.
Maybe some of you have or had the same issue and know how to fix it?
Many thanks in advance.
lelli1906 said:
Hi all,
every time when I start or restart (normal or hot) my DHD the sound profile will be set to 'normal' independent from the selected sound profile before. I select the 'just vibrate' sound profile, shut down and restart or just restart my DHD again. At the beginning the previous selected sound profile is active but suddenly it changes to 'normal' again.
The day before yesterday I have flashed LeeDroid 5.1.1. Thus I assume the issue has to do with LeeDroid (not sure if this is really the case). I was not able to find anything in the settings and don't have an app installed which could do that. Furthermore I was not able to find anything regarding this topic via Google or forum searches.
Maybe some of you have or had the same issue and know how to fix it?
Many thanks in advance.
Click to expand...
Click to collapse
Did you clear cache and dalvik cache before flashing? and did you fully wipe data?
It shouldn't be happening because the rom i'm on (sense 3.5), it doesn't give that sort of issue and i don't think leedroid should give you any issue like that since it is one of those old roms which are bug free...try what i told you to do and if it still gives you problem then your best bet is to flash a new rom...
Thanks for your reply.
I have flashed LeeDroid 5.1.0 via Rom Manager and selected the options for clearing cache and dalvik cache. After that I flashed the 5.1.1 patch to solve the 'no signal' issue (without wiping again). Which data do I have to wipe fully? I have also tried to use the wipe/factory reset functionality in the recovery mode but without flashing the ROM again (I have restored the created backup of LeeDroid - maybe that's what I shouldn't do?).
I'll give it another try with full data wipe before.

Strange occurence of phone constantly restarting.

Hello,
I have owned a Sprint Galaxy S III since August of 2012 and have been using it pretty much flawlessly until this week.
To give some history, I rooted it once it became a common thing to do and have CWM-based Recovery v5.5.0.4.
I have loaded many different roms - cyanogenmods, m.o.a.r., wicked, miui to try out and many others and have never had an issue.
I recently upgraded to M.O.A.R. v 6.0 at home and everything seemed great - loaded apps, settings, etc. The next day on the way to work, the phone restarted by itself. I thought was strange but chalked it up to a new rom issue. When I got to work, the frequency of the issue increased to the point that the phone was no longer usable as it would just continue to restart, boot, etc.
Restoring the rom I previously had did nothing to help the issue.
I looked up online at possibilities and came across the SD card issue. I replaced it, but still occurs. I've tried a few different roms and no matter what, it seems to continuously boot and restart based on certain locations that I am in or am passing through.
Today, I turned off 4G LTE as preferred mobile network and it seemed to keep the phone on. I have not done extensive testing, but could this be an issue? I am able to use 4G LTE at home with no problem as well as other areas, but it seems that once I am in or pass through certain locations, that it is crashing my phone? Maybe the GPS?
Are there any tips or suggestions of what I can do or try? I am at a loss as to how to fix this when it has not been an issue up until this week after flashing to MOAR v6.0. I've wiped data, cache, dalvik, many times and retried but still is happening.
Any feedback would be much appreciated.
At first it sounded like sudden death syndrome (a power button failure) but when you said turning off 4G fixed it that is very weird. Have you tried asking in the M.O.A.R thread?
------------------------
Sprint Galaxy S3
Stock - Whiplashh Rom - MIUI - Wicked Sensations
Sprint Evo 4G "OG"
Stock - Cyanogenmod 7 - MIUI - Swagged Out Stock
Hit That "Thanks" Button if I Helped You!
Could be your kernel. Or any kernel tweaks you are using
joebeem said:
Hello,
I have owned a Sprint Galaxy S III since August of 2012 and have been using it pretty much flawlessly until this week.
To give some history, I rooted it once it became a common thing to do and have CWM-based Recovery v5.5.0.4.
I have loaded many different roms - cyanogenmods, m.o.a.r., wicked, miui to try out and many others and have never had an issue.
I recently upgraded to M.O.A.R. v 6.0 at home and everything seemed great - loaded apps, settings, etc. The next day on the way to work, the phone restarted by itself. I thought was strange but chalked it up to a new rom issue. When I got to work, the frequency of the issue increased to the point that the phone was no longer usable as it would just continue to restart, boot, etc.
Restoring the rom I previously had did nothing to help the issue.
I looked up online at possibilities and came across the SD card issue. I replaced it, but still occurs. I've tried a few different roms and no matter what, it seems to continuously boot and restart based on certain locations that I am in or am passing through.
Today, I turned off 4G LTE as preferred mobile network and it seemed to keep the phone on. I have not done extensive testing, but could this be an issue? I am able to use 4G LTE at home with no problem as well as other areas, but it seems that once I am in or pass through certain locations, that it is crashing my phone? Maybe the GPS?
Are there any tips or suggestions of what I can do or try? I am at a loss as to how to fix this when it has not been an issue up until this week after flashing to MOAR v6.0. I've wiped data, cache, dalvik, many times and retried but still is happening.
Any feedback would be much appreciated.
Click to expand...
Click to collapse
Are you restoring any System Data ? I would suggest doing a Clean install. Meaning a FULL Wipe : System - Data - Dalvik - Dalvik Cache - Factory Reset ( 3x's ) . I also like to wipe Internal Storage. But that's up to you. Then Flash the Rom, and let it Boot. Do not load anything, or tweak anything. Just leave the device alone for the first 5min. Then test it to be sure everything is working correctly before loading apps, or doing any settings.
Just to update...
I clean installed MOAR 6 again - this time I upgraded CWM to latest version. I clean wiped data/cache, cache, dalvik about 3 or 4 times. Once it reinstalled, I noticed the data wasn't working at all so I did that ##72786# (forgot numbers off top of head) that reactivated phone. The data came back and I thought this was going to solve all the issues...keep in mind I did all this in the evening from home last night.
On the way to work this morning, sure enough once I got in the vicinity of work, phone restarted a few times. I was quick enough to catch it one time to turn preferred mobile networks to 3G first and disable 4G... my phone has not restarted for the rest of the day.
It's great that it seems the issue is isolated to 4G, but I don't understand how it can be fine in some areas and not in others. For instance, at home, 4G works just fine.
I think I will try to go back to stock or try an aosp rom. I've seen in some places talk of MB1 and MD4...is there a way to tell which I have or is that related to anything?
prboy1969 said:
Are you restoring any System Data ? I would suggest doing a Clean install. Meaning a FULL Wipe : System - Data - Dalvik - Dalvik Cache - Factory Reset ( 3x's ) . I also like to wipe Internal Storage. But that's up to you. Then Flash the Rom, and let it Boot. Do not load anything, or tweak anything. Just leave the device alone for the first 5min. Then test it to be sure everything is working correctly before loading apps, or doing any settings.
Click to expand...
Click to collapse
Actually, yes - I have been putting my gmail account information in and it has been syncing the apps. It's just so odd because I haven't had issues for over a year and I don't recall installing any new stuff.
well, now it happened at home when turning on 4g... damn.
joebeem said:
Just to update...
I clean installed MOAR 6 again - this time I upgraded CWM to latest version. I clean wiped data/cache, cache, dalvik about 3 or 4 times. Once it reinstalled, I noticed the data wasn't working at all so I did that ##72786# (forgot numbers off top of head) that reactivated phone. The data came back and I thought this was going to solve all the issues...keep in mind I did all this in the evening from home last night.
On the way to work this morning, sure enough once I got in the vicinity of work, phone restarted a few times. I was quick enough to catch it one time to turn preferred mobile networks to 3G first and disable 4G... my phone has not restarted for the rest of the day.
It's great that it seems the issue is isolated to 4G, but I don't understand how it can be fine in some areas and not in others. For instance, at home, 4G works just fine.
I think I will try to go back to stock or try an aosp rom. I've seen in some places talk of MB1 and MD4...is there a way to tell which I have or is that related to anything?
Click to expand...
Click to collapse
joebeem said:
Actually, yes - I have been putting my gmail account information in and it has been syncing the apps. It's just so odd because I haven't had issues for over a year and I don't recall installing any new stuff.
Click to expand...
Click to collapse
You did not mention wiping system. If you do not Wipe system, and also Factory Reset then it's really not a Clean install. I would still suggest a FULL Wipe, and Clean install. Then run the Device for a while without adding anything. See how it performs.
I ended up just flashing this - http://forum.xda-developers.com/showthread.php?t=1904099 to stock with flash reset.
I am not sure about wiping system - I always just follow the steps of the rom wipe data/cache/dalvik. I will have to research on how to wipe system.
If you never wipe system you are definitely going to run into problems.
joebeem said:
I ended up just flashing this - http://forum.xda-developers.com/showthread.php?t=1904099 to stock with flash reset.
I am not sure about wiping system - I always just follow the steps of the rom wipe data/cache/dalvik. I will have to research on how to wipe system.
Click to expand...
Click to collapse
You just do it in Recovery before you flash. If you look at my Sig on a PC / Internet Mode there is a link on how to do Full Wipe before flashing a Rom.
TEAM MiK
MikROMs Since 3/13/11

Menu Capacitive Button Issue

My wife's phone is having issues with the capacitive menu button.
It doesn't matter what ROM is installed, it will work for a little while and then it stops working completely.
What I have done already:
Wipe in cache and davlik cache in TWRP.
-No change
Wipe/Factory reset in TWRP
-Works for a little while and then stops
(nothing crazy installed, can't find anything that would be disabling it)
Flash different ROM
-Works for a little while and then stops
(nothing crazy installed, can't find anything that would be disabling it)
This began about 2 months ago and she just lives with it. I cannot, too many things she does not have access to without it.
Any ideas? If not, I may just bring it to sprint and see if there is a physical issue with it. Strange that it works for a little while though.
We both had the same phone for a while, just upgraded mine, but she does not have anything installed that was different from mine or different from what she used for the first few months of owning it. Everything was working fine for a while.
Thanks for the help.

My GPS is screwed after playing around.

I recently rooted and flashed a recovery on my M8.
I was experimenting with the Fake GPS Free app, and mock locations. Worked great.
But when I turned it off (developer settings, mock location-->None), Actual GPS doesn't work right.
Turned it off, removed mock location setting, deleted app, re-installed app, made sure it was turned off, deleted again.
'High Accuracy' sorta works. It gives an approx position. But using something like google maps navigation gives the message 'Searching for GPS...' and never finds it.
I tried a couple of apps 'GPS Status' and 'GPS Reset Com' which reset A-GPS, but it hasn't worked.
'Device Only' fails completely.
Tried clearing cache.
I even flashed a new ROM (Android Revolution HD (6.0)) but no luck.
I do have a factory reset option - but I'd rather avoid it if possible.
Anyone have any ideas of what else I can try?
Restore the nandroid backup you made (you made one right?) before flashing a new ROM or playing with apps from /system
I actually did not make one. I've just been reading up what it is and what I should have done and now I feel a bit silly.
When it said 'backup your phone' I thought it was just the contents (messages, data, media, etc).
Oops!
It's still all a bit new to me..
Anything else I can try?
Backup your data and sdcard content then flash appropriate RUU, if it's not gonna work it's probably an hardware issue.
I have exactly the same problem with my M8. I tried exactly the same steps and still have the GPS issue. I also restored a previously made backup and did a clean flash of CM13... this couldn't solve the problem.
It can't be a hardware issue
UPDATE: I don't know if it would have worked before, but after reflashing I placed my phone on the ground outside, started GPS Status & Toolbox and waited for a GPS signal. after ~1 minute GPS signal was found and it works fine since then. Maybe I was just too impatient before.
jamesb457 said:
Tried clearing cache.
I even flashed a new ROM (Android Revolution HD (6.0)) but no luck.
I do have a factory reset option - but I'd rather avoid it if possible.
Click to expand...
Click to collapse
Looks like you are new to the modding world. But if you are modding the phone (root, custom ROMs), you should always be prepared to recover from a factory reset (have your data backed up).
And if fact, if you are flashing ROMs without doing a factory reset (within TWRP) you are inviting all sorts of random bugs. In other words, the default wipe in TWRP (data, cache, Dalvik) is always recommended when flashing a new ROM.

Categories

Resources