Related
Hello,
for a few days now i have something strange going on with my galaxy s. When i reboot the device, somewhere around the moment you can enter the pincode for the sim, the phone shakes one time first and and then two times as if there is something crashing.
After that all seems to be working fine... That is, until i notice up to two times now, an app went missing, from which i can't remember i removed it. After i reinstall the app, all settings i configured before for that app where there in place...
I am not sure if these two issues have something to do with each other...
I am running the stock Froyo rom 2.2.1 with the speedmod kernel (k12t)...
Is there someone out there who has an idea?
Thanks in advance.
Regards,
Mart
Did you recently change to the froyo 2.2.1 rom, and did problems only occur after changing?
Did you do a full wipe when changing?
Thanks you for the reply...
well no, i am running the 2.2.1 for a few weeks... As far as i am able to point to the moment it started it was just after i removed the battery when the phone was locked (i mistakenly thought it was off). After i placed back the battery and started the phone, i started noticing the possible crashing...
A day or 2 later i noticed an app was lost, the icon was still on the desktop, but it was a green android (like that from the market) and won't start. Because i didn't remember removing the app i looks strange to me. After reinstalling the app all settings i configured before where in place, as if wasn't gone for a while... That's why i notice it, because when i remove an app, i normally make sure everything is removed including settings...
Up until now i have found two of these in a strange way lost apps...
Because there was some time between the removing of the battery with the start of the first issue and noticing these lost apps, i am not really sure they are connected...
It seems that you have any kind of data corruption. If the phone shakes 1 and then 3 times, it is saying that some process has stopped. Also if you lost some app without your intervention... looks like I said. Consider backup your data, wipe and reinstall.
Good luck
Hi all,
for the last 5 or 6 days, my phone has crashed every single night. :-(
When I go to bed, I just leave it on the table, not charging, but with enough battery left to easily last for the night. The next morning, the phone is switched off and I cannot switch it back on, because the battery is completey drained.
When I charge and then turn the phone back on, it has done a "partial reset", meaning that all settings are back to factory defaults, contacts are gone, ... All accounts, apps, ... are still there, though. The worst part is that I cannot receive calls anymore either, in this case. Callers are immediately redirected to my mailbox, even though the phone has a signal and I can make outgoing calls without problems. The only way to fix this is a factory reset.
The next night, the same happens again.
Has anybody had a similar problem? Does anybody have an idea how to fix it?
Thanks and regards,
Andy
Andy.WP7 said:
Hi all,
for the last 5 or 6 days, my phone has crashed every single night. :-(
When I go to bed, I just leave it on the table, not charging, but with enough battery left to easily last for the night. The next morning, the phone is switched off and I cannot switch it back on, because the battery is completey drained.
When I charge and then turn the phone back on, it has done a "partial reset", meaning that all settings are back to factory defaults, contacts are gone, ... All accounts, apps, ... are still there, though. The worst part is that I cannot receive calls anymore either, in this case. Callers are immediately redirected to my mailbox, even though the phone has a signal and I can make outgoing calls without problems. The only way to fix this is a factory reset.
The next night, the same happens again.
Has anybody had a similar problem? Does anybody have an idea how to fix it?
Thanks and regards,
Andy
Click to expand...
Click to collapse
I'm sorry that I have no advice for you Andy, but I'm interested in hearing any solutions you may find.
What firmware/ROM are you using?
What firmware/ROM are you using?
Click to expand...
Click to collapse
I am still using the stock Froyo ROM that the phone came with. The phone is rooted and I've installed a SpeedMod Kernel. However, both (rooting and new kernel) have happened months ago, so I doubt that they have anything to do with the problem.
(partial) solution found
Since a phone that crashes every night, using all settings in the process, is fairly useless, I decided that I might just as well trash it completely by trying (and maybe failling ) to install a custom firmware. So I downloaded Darky 10.1 and thanks to an excellent installation guide, I actually managed to install it.
Since then, my phone does no longer crash every night - it now reboots a couple of times a day The good thing is, though that after the reboot, the phone is back "in action" after maybe two minutes and it does not lose any data, setting or anything. So, it's not ideal, but much better than before ...
I was going to recommend trying a new ROM, but I found that as a workaround rather than a solution to your problem.
Did you perform a wipe or no-wipe install?
Kops said:
Did you perform a wipe or no-wipe install?
Click to expand...
Click to collapse
As I had pointed out in my first post, the crash that happens every night breaks something so that I can no longer receive calls and have to do a factory reset. Thus, the phone was basically wiped, already, before I did the installation and I then did a no-wipe install.
You are right, of course that this is more of a work around than a solution, but since I was thinking about putting on a new ROM for a while, already, anyways, it is a fairly good work around for me - and I really like Gingerbread and DarkyROM so far.
Kops said:
I'm sorry that I have no advice for you Andy, but I'm interested in hearing any solutions you may find.
Click to expand...
Click to collapse
In the end it turned out to be a hardware problem and I needed to get the phone replaced.
My first day with the Droid bionic... it's my first non-Samsung Android phone, so I'm not sure what to think.
In the midst of trying to figure it out and get it all setup (rooted, Titanium Backup restore, apps only), and my data drops out. Apparently for good.
I had solid 4G data when I first opened up the phone this afternoon. I ran some speed tests and switched to WiFi. I left the house a bit later and realized I couldn't open a webpage. I noticed the WiFi was still on, so I shut it off, but the cellular data never came back.
Tried putting it in airplane mode and back, rebooted (several times), tried the data toggle on the power control widget, I even forced the phone into CDMA only mode (and back).
I'm stumped. Has anyone else seen this? Is there any kind of possibility that restoring apps or rooting could have anything to do with it? I have not seen this problem over many a ROM on the Vibrant, and then the Droid Charge. I even loaded a GB ROM on the Charge and restored all my apps without issue.
Any help would be appreciated. I'd really not like to have to wipe the phone and start over.
I had something similar happen although I'm not rooted yet. For 3 days I was golden. Then I installed switchpro widget to see how the 3G/4G toggle worked with the Bionic and it made my mobile connectivity wonky. I uninstalled it. It still is wonky today.
LTE is there then goes away a reboot corrects it until it goes away. 3G is exactly the same. Turn on WIFI and the LTE disappears. It's supposed to stay up just turn white like it did for 3 days prior to installing then uninstalling switchpro. It could just be coincidence with the switchpro thing idk. I'm not all that knowledgeable with APN's, but after some research somehow I believe mine got mixed up via switchpro. Getting a new Bionic tomorrow.
Well, no data at all. If I'm outof wifi area, I have no data access. Only phone calls and text.
Sent from my Android using Tapatalk
Flapjack said:
Well, no data at all. If I'm outof wifi area, I have no data access. Only phone calls and text.
Sent from my Android using Tapatalk
Click to expand...
Click to collapse
I'd get another one then. Or if you don't want to do that get a different brand
I think I'll just try a hard reset. I'm sure it was something I did with Titanium backup... I'll just have to figure out what.
Or you could try a factory reset to see if that solves it
EDIT: I see you thought of that 1st
Something similar happened to me. The only way I could fix it was by restarting the phone until the data crashed again. I solved this problem (or I think I did, still testing it) by removing all my widgets. I have a strong suspicion it was a widget doing this (specifically the AIX weather widget, but I am not sure yet).
So, I suggest that you remove all of your widgets and restart your phone and see what happens.
The hard reset did the trick. I think maybe it was me restoring the [SMS/.../APN] setting (can't remember the middle setting) in TB. I didn't do it this time and all seems well. It was green, so I thought 'why not'.
I'll see how it goes from here on out.
I'm thinking its got to be something related to wifi. every time I disconnect from wifi I can't connect to data unless I reset my phone.
Sent from my DROID BIONIC using XDA App
Flapjack said:
The hard reset did the trick. I think maybe it was me restoring the [SMS/.../APN] setting (can't remember the middle setting) in TB. I didn't do it this time and all seems well. It was green, so I thought 'why not'.
I'll see how it goes from here on out.
Click to expand...
Click to collapse
Glad to hear that. Factory reset did not fix it for me. Will have a new tomorrow
I am also having this problem. If Motorola still used vanilla android this wouldn't be an issue. I hate when manufacturers feel it necessary to fix something that isn't broke. I am sad to see how many people are experiencing this problem because if it was isolated to my phone and a few others then a warranty replacement would do the trick. I now feel like I wasted 380 on phone and accessories. I placed a call to Verizon tech support and their as clueless as usual. I hope an update is released soon that fixes this issue (or a custom rom). I remain hopeful that we start seeing good things on our Motorola devices now that google owns moto.
NOTE: I wish people would start reading through existing threads before starting new ones. I started a thread to this effect back on day 3. Several others have started threads to this effect as well. I think there are now 4 or 5 on this very same subject.
Sent from my DROID BIONIC using xda premium
I complained about this issue originally in the MavRom thread but was advised this isn’t a known issue with the ROM, so after more troubleshooting, here I am. This is the chain of events:
- Bought the Droid 3 unlocked so I could use it on Rogers
- Instantly flashed CM9, lived with the various issues hoping they’d be resolved soon
- They weren’t, so I started looking for a permanent GB rom. Tried MavRom
- Noticed a day or two later the following issue:
Wifi will just randomly encounter an error and turn off. It typically happens without me noticing, and then I’ll be at home and notice I’m on data when I should be on wi-fi. If I try to turn it on using the power widget it will briefly light up as though it’s trying to turn on, but eventually give up. If I try to turn it on through settings, where it normally would say “wifi is on” or “wifi is off”, it just says error. I used to reboot the phone to fix it, but just realized a few weeks ago that I just need to turn airplane mode on and off, then turn wifi back on.
This isn’t the worst thing in the world but it should not happen. There is also no pattern to it, or any apparent triggering event. It can happen half an hour after the last time, or it can go a whole day without happening. My phone is in essentially the same state all night while I am sleeping, so the same thing should happen every time. But sometimes I wake up and the error has occurred, other times it hasn’t.
So as I said, I complained in the MavRom thread, they insisted it wasn’t related to Maverick. So I flashed Eclipse to try it out. Right away I realized that this error was happening in Eclipse too. So, somewhere in all the clearing data and cache and flashing of ROMs, etc, I managed to wreck the wifi in a way that reflashing doesn’t appear to fix.
Realizing this, I tried to go all the way back to stock to see if that would work. I used the .906 to .890 patch (since it’s the only way to go back to .890 or at least mostly), then had to use quick unbrick to fix it when it wouldn’t start up. Everything was fine; it was a stock motobloat Droid 3 again. After a few hours of usage I was pretty convinced that the wifi error was gone.
So I installed Eclipse again. For most of the day everything seemed fine but the same problem reared its ugly head last night just like it used to. It sounds like I need to somehow update the part of the Gingerbread OS specifically related to wifi but I have no idea where to go from here. Has anyone else seen a problem like this before? Any troubleshooting advice?
seventieslord said:
I complained about this issue originally in the MavRom thread but was advised this isn’t a known issue with the ROM, so after more troubleshooting, here I am. This is the chain of events:
- Bought the Droid 3 unlocked so I could use it on Rogers
- Instantly flashed CM9, lived with the various issues hoping they’d be resolved soon
- They weren’t, so I started looking for a permanent GB rom. Tried MavRom
- Noticed a day or two later the following issue:
Wifi will just randomly encounter an error and turn off. It typically happens without me noticing, and then I’ll be at home and notice I’m on data when I should be on wi-fi. If I try to turn it on using the power widget it will briefly light up as though it’s trying to turn on, but eventually give up. If I try to turn it on through settings, where it normally would say “wifi is on” or “wifi is off”, it just says error. I used to reboot the phone to fix it, but just realized a few weeks ago that I just need to turn airplane mode on and off, then turn wifi back on.
This isn’t the worst thing in the world but it should not happen. There is also no pattern to it, or any apparent triggering event. It can happen half an hour after the last time, or it can go a whole day without happening. My phone is in essentially the same state all night while I am sleeping, so the same thing should happen every time. But sometimes I wake up and the error has occurred, other times it hasn’t.
So as I said, I complained in the MavRom thread, they insisted it wasn’t related to Maverick. So I flashed Eclipse to try it out. Right away I realized that this error was happening in Eclipse too. So, somewhere in all the clearing data and cache and flashing of ROMs, etc, I managed to wreck the wifi in a way that reflashing doesn’t appear to fix.
Realizing this, I tried to go all the way back to stock to see if that would work. I used the .906 to .890 patch (since it’s the only way to go back to .890 or at least mostly), then had to use quick unbrick to fix it when it wouldn’t start up. Everything was fine; it was a stock motobloat Droid 3 again. After a few hours of usage I was pretty convinced that the wifi error was gone.
So I installed Eclipse again. For most of the day everything seemed fine but the same problem reared its ugly head last night just like it used to. It sounds like I need to somehow update the part of the Gingerbread OS specifically related to wifi but I have no idea where to go from here. Has anyone else seen a problem like this before? Any troubleshooting advice?
Click to expand...
Click to collapse
I would sbf and stay on stock, if it reappears, bring it to verizon. Im afraid I've never heard of this problem before. Since it happened with 2 separate roms, it seems more like hardware. Otherwise the sbf should have fixed it.
Sent from my XT860 using xda premium
Odd. I know that this was a problem on most ICS roms. Haven't heard of it happening on a GB rom. This happens to me on Gummy 1.2. Same symptopms: wifi kills with no cause and no pattern. I toggle airplane and keep browsing as I only turn on wifi when I am actively using it.
Sent from my DROID3 using xda premium
After updating my htc one to 4.3, my notifications led is not working. It comes on when I plug it on charge, but doesn't work for anything else. Anyone else have this problem?
Same here , red only when charging, green led not working ?
Sent from my HTC One using xda app-developers app
Yep, same here, feature?
Sent from my HTC One using Tapatalk
Did you guys factory reset after upgrading? Its most likely that the LED will work after a factory reset, I didn't as it all worked lovely without this time and with kit Kat round the corner I will factory reset for that upgrade. Maybe some one knows what process drives the LED that we can try clearing and force closing? might help
Sent from my HTC One using xda app-developers app
manmikey said:
Did you guys factory reset after upgrading? Its most likely that the LED will work after a factory reset, I didn't as it all worked lovely without this time and with kit Kat round the corner I will factory reset for that upgrade. Maybe some one knows what process drives the LED that we can try clearing and force closing? might help
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Yes, I actually rooted my phone, and installed 4.3 before it was even available ota, and the notification led would not work. I then went back to stock, and received the ota update, then did a factory reset, still cant get notifications to work. It seems to be affecting a minority of handsets which I find strange.
honda1979 said:
Yes, I actually rooted my phone, and installed 4.3 before it was even available ota, and the notification led would not work. I then went back to stock, and received the ota update, then did a factory reset, still cant get notifications to work. It seems to be affecting a minority of handsets which I find strange.
Click to expand...
Click to collapse
I think we may well be a minority with this problem, there's not a lot of noise on this forum the internet in general about it, it could be a combination of apps that are causing the problem, or maybe the new Do Not Disturb feature is not running properly as that shuts down the notification Led when activated.
We know a factory reset doesn't help.
Apps I have that use the notification LED other than the stock system notification are only WhatsApp and Missed Call Reminder, I am going to try uninstalling them and see if it frees the LED up, other than that I am at a loss.
I am having the same problem after recently updating to 4.3 / 5.5 (stock Scandinavian int. unlocked version) so I will be keeping an eye on this thread and any others to see what the possible solution is.
As manmikey has said, factory reset doesn't solve it - at least a regular reset and re-install. I may reset again and set it up without importing my apps, to see if one of them is screwing it up but I don't have anything out of the ordinary which accesses the LED - only stock Messaging and Gmail. I tried LightFlow, to see if that would somehow kick it back to life and override what was causing the problem by using its testing tools, but still nothing...
So yeah, must be a combination of updates and apps which knock it out. It's not a huge issue as I still have audio notifications but it is super-handy being able to glance at my phone and see if anything has arrived. Might be fixed with 4.4, who knows...
nateema said:
I am having the same problem after recently updating to 4.3 / 5.5 (stock Scandinavian int. unlocked version) so I will be keeping an eye on this thread and any others to see what the possible solution is.
As manmikey has said, factory reset doesn't solve it - at least a regular reset and re-install. I may reset again and set it up without importing my apps, to see if one of them is screwing it up but I don't have anything out of the ordinary which accesses the LED - only stock Messaging and Gmail. I tried LightFlow, to see if that would somehow kick it back to life and override what was causing the problem by using its testing tools, but still nothing...
So yeah, must be a combination of updates and apps which knock it out. It's not a huge issue as I still have audio notifications but it is super-handy being able to glance at my phone and see if anything has arrived. Might be fixed with 4.4, who knows...
Click to expand...
Click to collapse
Finally got to the bottom of this problem which has been bugging me for weeks. If anyone is having problems with there notification led not working, do a factory reset. During the install process after resetting, DO NOT log into your google account and let it restore your apps and settings. Lo in once pone has fully booted up and manuallyrestore apps, bit of a pain if you have loads of apps, but the light is now working normal for messages, emails etc etc as it should
honda1979 said:
Finally got to the bottom of this problem which has been bugging me for weeks. If anyone is having problems with there notification led not working, do a factory reset. During the install process after resetting, DO NOT log into your google account and let it restore your apps and settings. Lo in once pone has fully booted up and manuallyrestore apps, bit of a pain if you have loads of apps, but the light is now working normal for messages, emails etc etc as it should
Click to expand...
Click to collapse
YES! Thank you so much for this! I did the reset, without restoring using my Google account and then logged in after the set up had finished. Sent a test email from another account and *BAM* the green LED flashes away. Such a nice feeling to have it back - it feels like my phone is now complete. Strange how such a small thing can make a difference to the overall user experience.
Having to reinstall and set up my apps from scratch is a small price to pay for having everything work properly.
Thanks again
honda1979 said:
Finally got to the bottom of this problem which has been bugging me for weeks. If anyone is having problems with there notification led not working, do a factory reset. During the install process after resetting, DO NOT log into your google account and let it restore your apps and settings. Lo in once pone has fully booted up and manuallyrestore apps, bit of a pain if you have loads of apps, but the light is now working normal for messages, emails etc etc as it should
Click to expand...
Click to collapse
No easy solution but a more info for those with this problem...
Seeing on this forum that restoring using Google back up did not cure the problem I thought I would try using HTC back up. I did a factory reset and then a restore from my HTC back up to try and get the notification lamp working. Unfortunately the Led still does not work after this so it looks like Honda1979s method is the only way
As a footnote I have now returned my HTC One (to Carphone Warehouse) for warranty repairs as the device has microphone/noise cancelling issues (another seemingly common problem of the HTC one) So I reported the LED not notifying as well, so lets see what comes back in 6 days..... I have a horrible feeling that HTC will shirk the repair and quote "moisture damage" even tho it has never been wet. watch this space
manmikey said:
No easy solution but a more info for those with this problem...
Seeing on this forum that restoring using Google back up did not cure the problem I thought I would try using HTC back up. I did a factory reset and then a restore from my HTC back up to try and get the notification lamp working. Unfortunately the Led still does not work after this so it looks like Honda1979s method is the only way
As a footnote I have now returned my HTC One (to Carphone Warehouse) for warranty repairs as the device has microphone/noise cancelling issues (another seemingly common problem of the HTC one) So I reported the LED not notifying as well, so lets see what comes back in 6 days..... I have a horrible feeling that HTC will shirk the repair and quote "moisture damage" even tho it has never been wet. watch this space
Click to expand...
Click to collapse
Okay still no solution but further information....
I received a replacement HTC One as the microphone issue was not repairable, the replacement device was a factory reconditioned unit with sense 5.0 & Android 4.2.2 installed. The notification LED was working when I put my sim in and subsequently after I ran HTC restore. Then I downloaded the OTA sense 5.5/4.3 update and ran it. After that update the notification LED was no longer working. At this point I am leaving it as I don't want to spend too much more of my life chasing a flashing green light, after the KitKat update I will follow Honda1979s methods and rebuild the phone from scratch and not restore from backup.
Hey guys I am the owner of a new HTC One phone
My feeling is that Swiftkey is messing up green led notification
Do you have installed Swiftkey. Because for me notification does not work after the installation of this application
Also an uninstall of it does not help. For the moment only honda solution seems working
Sent from my HTC One using Tapatalk
Solved - Notification LED not working
Just to update the post....
After the OTA update to KitKat 4.4.2 I did not restore from backups but rebuilt my HTC One as a brand new device, I can confirm the green notification LED is now working again :good:
Okay having just updated OTA to sense 6 I find yet again that the notification Led has stopped working again as a result of updating. I was expecting to have to rebuild my phone from scratch as before to get the Led working. But I discovered another way to get it working whilst installing another app.
The app is "Missed Message Flasher" and when setting it up it requires turning on in the Settings/Accessibility/Services menu. Once installed and turned on the Led works as entirely as intended
I confirmed this by uninstalling the app at which point the Led stopped working again, reinstalled and the Led works again.
I have no idea why this solves it, but I hope it helps others with this frustrating issue.
Sent from my HTC One using XDA Free mobile app
manmikey said:
Okay having just updated OTA to sense 6 I find yet again that the notification Led has stopped working again as a result of updating. I was expecting to have to rebuild my phone from scratch as before to get the Led working. But I discovered another way to get it working whilst installing another app.
The app is "Missed Message Flasher" and when setting it up it requires turning on in the Settings/Accessibility/Services menu. Once installed and turned on the Led works as entirely as intended
I confirmed this by uninstalling the app at which point the Led stopped working again, reinstalled and the Led works again.
I have no idea why this solves it, but I hope it helps others with this frustrating issue.
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
How it configures?
Enviado desde mi HTC One mediante Tapatalk
So I had the same issue.tested my led in safe mode it worked fine. Downloaded the led notifier on app in market because some reported this fixed it.disabled Google hangouts and Verizon messaging still nothing.but what did work and I'm not sure if its a combination of all the steps I took but all I simply did was cycle the do not disturb button on and then off from the top pull down bar. Hope this works for you guys.
swsd818 said:
So I had the same issue.tested my led in safe mode it worked fine. Downloaded the led notifier on app in market because some reported this fixed it.disabled Google hangouts and Verizon messaging still nothing.but what did work and I'm not sure if its a combination of all the steps I took but all I simply did was cycle the do not disturb button on and then off from the top pull down bar. Hope this works for you guys.
Click to expand...
Click to collapse
Old thread but ran into this problem a week ago on my Desire HD. Tried all kind of apps and removed all my widgets and a bunch of apps but couldn't get it fixed. I knew my LED still worked cause when I completely turned off the phone and connected it to the charger it worked. However as soon as I booted the phone the LED turned off and it only started flashing again when my battery level dropped below 14%. Notifications or charging the phone when it was on did not turn on the LED.
After I read your 'do not disturb' comment I pulled down the notification bar and noticed my quiet hours (Android 4.4.4) was switched on even though I never changed the setting (on from 11pm to 7am). Switched it off and now the light is working fine again.
Sometimes solutions are so easy ...