Database Users

[Q] Lockscreen Reboot Issues

I've been having lockscreen reboot issues with the last few Fission roms, and a couple of Matt's. Has anyone else had this problem and resolved it?
I followed the installation instructions and even formatted my SD card. I'm going to try to SBF before I install the next Fission, is there anything else I can do to completely clean out my phone? Such as wiping some system files in recovery or something.
The only data I have left over from other ROMs is backups I made of a few games like Angry Birds.
Any suggestions are appreciated, I've been trying to fix this issue for awhile!

Are you doing a hard reset after flashing roms? Resetting the phone in applications>privacy, at the bottom of privacy?

mikeyinid said:
Are you doing a hard reset after flashing roms? Resetting the phone in applications>privacy, at the bottom of privacy?
Click to expand...
Click to collapse
Yup, after installing the ROM and rebooting I do a hard reset through the privacy menu. Would it make a difference if I sign into my google account on first reboot before doing the hard reset?

kdog349 said:
Yup, after installing the ROM and rebooting I do a hard reset through the privacy menu. Would it make a difference if I sign into my google account on first reboot before doing the hard reset?
Click to expand...
Click to collapse
I never sign into google until after the hard reset. But I dont know if that matters. Next time you flash a rom, try wiping data and cache in recovery, after flashing, but before you reboot. And, are you overclocking or undervolting?

I'll try wiping data and cache before my first reboot. I know I used to do this but not sure if I've done it recently.
I haven't messed with overclocking or underclocking. Do you know if any widgets are known to cause problems? I run Launcher Pro, but I went a day or two with the stock launcher and still had some reboot issue.

kdog349 said:
I'll try wiping data and cache before my first reboot. I know I used to do this but not sure if I've done it recently.
I haven't messed with overclocking or underclocking. Do you know if any widgets are known to cause problems? I run Launcher Pro, but I went a day or two with the stock launcher and still had some reboot issue.
Click to expand...
Click to collapse
Launcherpro wouldnt cause it. I would sbf if i were you, and just keep doing what your doing. After so many flashes there is bound to be some residual bs left behind.
*Fission 2.2.1 will be hitting the forum soon so an sbf is in your best interest Im running it now and its VERY good...

mikeyinid said:
Launcherpro wouldnt cause it. I would sbf if i were you, and just keep doing what your doing. After so many flashes there is bound to be some residual bs left behind.
*Fission 2.2.1 will be hitting the forum soon so an sbf is in your best interest Im running it now and its VERY good...
Click to expand...
Click to collapse
I'll give SBF a try. I've been loving everything about the fission ROMs, can't wait to get 2.2.1
Thanks so much for the help!

mikeyinid said:
Launcherpro wouldnt cause it. I would sbf if i were you, and just keep doing what your doing. After so many flashes there is bound to be some residual bs left behind.
*Fission 2.2.1 will be hitting the forum soon so an sbf is in your best interest Im running it now and its VERY good...
Click to expand...
Click to collapse
I'll give SBF a try. I've been loving everything about the fission ROMs, can't wait to get 2.2.1
Thanks so much for the help!

Lock Screen Reboots are something that seem to be present in all these Moto Droid phones. I always always always get them on both D1 and Dx and D2, with any ROM, theme, etc. Just seems to be a common problem Motorola has, along with their insane fascination with their Motoblur UI which is also a complete mystery.

mjones1052 said:
Lock Screen Reboots are something that seem to be present in all these Moto Droid phones. I always always always get them on both D1 and Dx and D2, with any ROM, theme, etc. Just seems to be a common problem Motorola has, along with their insane fascination with their Motoblur UI which is also a complete mystery.
Click to expand...
Click to collapse
Personally I had a Droid 1 for 6 months and don't remember having any lockscreen reboots, at least not at the frequency of 2-3 a day that I'm having now. Could run the phone for a week without rebooting.
There were a couple of D2 roms that didn't have the reboot issue for me, but most do so maybe it is an issue with the phone like you say. I Don't understand their persistance with motoblur either At least take out eFuse if you're going to throw on motoblur

I've been trying lockbot free to solve my reboot issues. You can basically set it to be exactly the same the normal lockscreen, and so far it seems to be working for me.

I had this problem. Random, intermitten soft reboots during slide to unlock. Ran multiple roms, always had the problem. But I was always removing the same things after sbf. I had found one Dev to seem to find this to follow the music.apk file. So this time I left it on. On my last sbf, I left that in there. Havent had a problem since. Before that I had tried what I thought to be everything, multiple sbfs, multiple roms, completely formatted sd card, and re-sbf'd again. But I always deleted music.apk. Because it always seems to start running, using memory that I thought was unnecessary. Since I dont play music from my phone, other then streaming music. Hope that helps someone. Saved a ton of frustration for me!

But I always deleted music.apk. Because it always seems to start running, using memory that I thought was unnecessary. Since I dont play music from my phone, other then streaming music. Hope that helps someone. Saved a ton of frustration for me!
Click to expand...
Click to collapse
Which music.apk is this? Is it the D2's original application or the google music app? Because I've never taken the music app that's been on the phone or came with any ROM and I've had a few not a big number but a few.
Sent from my DROID2 using XDA App

Not sure what the google music one is, but the file is named music.apk

Please clarify this lol. Mine was working great until I installed that damn black theme for fission rom.

I've had a droid1 and I have never had reboot issues with roms before. I think it may just be a d2/x problem
Sent from my DROID2 using XDA App

Yeah the same thing happens to me. I'm pretty sure the dev's for Fission know about it, so hopefully 2.2.1 from them fixes it.
Sent from my DROID2 using XDA App

I had this same problem until yesterday. I installed the Music.zip that came with fission. Now I haven't had a single problem. (I also installed the 10 percent framework and the Camera.zip) I can't remember who posted it but once I installed the Music.zip everything works great.

Im just curious, are you guys only experiencing these reboots with the non-blur roms, or have you experienced them with other roms also? I have only had one reboot, and that was running fission 2.2.1.

tonorice said:
I had this same problem until yesterday. I installed the Music.zip that came with fission. Now I haven't had a single problem. (I also installed the 10 percent framework and the Camera.zip) I can't remember who posted it but once I installed the Music.zip everything works great.
Click to expand...
Click to collapse
Was it the "Android_Music.zip" or "D2_Music.zip"?

Most annoying glitch issue in my phone

Wtf is wrong with the youtube app it always ssays problen with network and only thing to fix it is to reboot phone?
Sent from my SPH-D700 using XDA Premium App

Side note u have to reboot this bitcj all tje time recently ____?ec05.
sent using my cup phone nukka

deisel said:
Side note u have to reboot this bitcj all tje time recently ____?ec05.
sent using my cup phone nukka
Click to expand...
Click to collapse
If you are having problems, boot into CWM and reflash the rom right over what you are running. It will backup the apps and everything for you and you will be back up and running in under a half hour.
You might want to try this before doing that though:
Settings>Applications>Manage Applications>All
Scroll down to Youtube and select it. Hit "Clear Data" and then exit out and try Youtube again.

Are you running stock or a custom ROM? It has been so long since I have run stock that I wouldn't be able to help you out with that. I am currently running SyndicateROM Frozen. It's sold as a rock, fast, and I can go days without rebooting.

Getting the same EXACT issue as the OP. Running stock and rooted EC05. I think it started recently with the latest YouTube update. It didn't do that when I first got EC05.

Yes, me too. Stock EC05. I also noticed that the video camera and stock video player stop working when the youtube app fails.

elrey75 said:
Yes, me too. Stock EC05. I also noticed that the video camera and stock video player stop working when the youtube app fails.
Click to expand...
Click to collapse
Have you considered trying a custom ROM? I tried the scenario you described and didn't have a problem. I am running SyndicateROM Frozen, but there are others to choose from.
Just a thought.

Thanks, I'm sure that would help but I don't want to root.

I read the reviews in the Market for our current version of YouTube and apparently a lot of other users on different phones are getting the same problem. Many 1 star reviews lately because of it. As I stated earlier, this didn't start occurring until recently, which I attribute to the latest upgrade of the app.

Mine is the inability for the phone to roam on the PCS band. Really Samsung? Fix the bug!

Yes, this happened a lot to me when I was running EC05. So annoying.

Sounds like it's an EC05 bug. I refuse to power cycle 3 times a day for luxurious mutimedia. My Flash works, that's all I need. But wait, now the same error occurs when checking Voicemail, taking video, using the stock player... what's next? But I will not power cycle.
Sent from my Stock Unrooted Epic 4G running EC05

I think the Youtube glitch was due to a problem Google was having. If you've noticed, Gmail also had an insane lag and fail to send rate during that time too. Might actually just be Google servers.
I had the same issue but it stopped after so long and I'm back to normal.

I tried a fix I read in another thread and it seems to work. Uninstall the official twitter app and use another like tweetcaster. I have power cycled and haven't had that youtube problem anymore. Don't know why that worked.
Sent from my SPH-D700 using XDA App

Unmount your SD card and Mount it back again and that will fix the youtube app. I don't know why it fixes this problem for me. Let me know if it worked for you.

The only rom this happens to me on is ec05 plus.
sent from the ePc4gee yo

Camera inverted (upside down) with CM7.

Hey guys.
I've been using CM7 for about a month now, currently in the 010911 Nightly.
Everthing was fine until this past week, when the camera of my phone started to have strange freezes and lags. Then, one time, it FCed and when I turned it back on, the display was inverted, and colors were all strange and washed off.
I've rebooted, cleaned the data, etc, etc, and nothing fix the issue. Keep in mind that there's nothing with the tilt sensor. It's something software related.
I remember seeing a fix for a similar problem a while back, but I searched this hole forum and couldn't find anything, so, I beg for your help.
Thanks a lot!

Sorry for the bump, guys. But I really need some light with this problems.

Try clearing Camera app data or switch to another nightly.
Sent from my MB525 using Tapatalk

ryan8r said:
Try clearing Camera app data or switch to another nightly.
Sent from my MB525 using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply.
Unfortunately, I already tried both things you suggested, with no luck.

Not sure if it has anything to do with it, but is the boot mode set to 2nd init by default ?!
You can also try using other camera apps like Vignette.
Sent from my MB525 using Tapatalk

dude, we are on the same boat. Tell me when u find a solution.
A temporary fix which i m not sure till when its gonna last but is working for the moment.
open camera, leave it opened and pull the battery. put the battery again after 2 mins and see if it helps you. Its working for me at the moment but dont know the logic behind the process.
I already got my camera hardware replaced but this problem happened again just after rooting the phone.

I have the same problem and I'm almost sure it is a hardware failure. Maybe after a shock or drop. I'll open my unit this week and see what's wrong. Did some of you manage to fix it?
I've even tried flashing full stock sbf without success, so I'd blame the camera module.

Epic 4G Camera Broken!

I have a Samsung Epic 4G, I got it in March of 2011. About 6 months ago the camera started acting up. It would work once (take one picture), then the next time I took a picture or opened the app it would say there was a error with com.android.camera. I could restart the phone and the camera would work again, but break after one use.
I took it to the Sprint store, they did a quick test and said it was not the hardware (I think he tested the wiring)
I did a factory reset, it worked for a day then went back to the same pattern
Then I installed CM7, the camera worked for a day then it completely stopped working (the app wouldn't load).
I installed other camera applications. Retro camera worked some of the time (one shot then break). I think "Fun Camera" loaded, and I could use the front facing camera but the main camera was dark.
I added the camera.zip and camerafirmware.zip to the system/app folder, but couldn't install them (after changing the ext to .apk).
http://forum.xda-developers.com/showthread.php?t=814998
I feel like I'm running out of options, so I wanted to post this up on XDA and see if anyone else has had issues like this, and see what additional steps I could take to fix the camera. I don't know too much about Android but I think I'm tech savvy enough to try anything with the right links to tutorials. Thanks all.

Have you tried going back to stock el30?
See if it works on stock if it continues to force close... take it back to sprint and show them, and they usually give you a replacement if of course it still force closes, and you have TEP you could get one for 35$ I think.
http://forum.xda-developers.com/showthread.php?t=1501424
For stock el30
Sent from my SPH-D700 using xda premium

Generalzhou said:
I have a Samsung Epic 4G, I got it in March of 2011. About 6 months ago the camera started acting up. It would work once (take one picture), then the next time I took a picture or opened the app it would say there was a error with com.android.camera. I could restart the phone and the camera would work again, but break after one use.........I feel like I'm running out of options, so I wanted to post this up on XDA and see if anyone else has had issues like this, and see what additional steps I could take to fix the camera. I don't know too much about Android but I think I'm tech savvy enough to try anything with the right links to tutorials. Thanks all.
Click to expand...
Click to collapse
Have you ever updated your camera firmware (from BML Stock?), I know that this has benefited me in the past..........however, once you are on CM9, it' a new camera from ICS .......sounds like your issue follows your firmware.........Not a fix, but have you considered a 3rd party camera app?
Sent from my SPH-D700 using xda premium

Thanks guys. I factory reset my phone before and it still had the issue, I will definitely keep the Samsung warranty as a backup (don't want to send in my phone if I dont have to).
How do I update the camera firmware? I've tried other cameras, retro camera works but only sort of, another camera app works for the front facing cam but not the main rear facing one.

Generalzhou said:
Thanks guys. I factory reset my phone before and it still had the issue, I will definitely keep the Samsung warranty as a backup (don't want to send in my phone if I dont have to).
How do I update the camera firmware? I've tried other cameras, retro camera works but only sort of, another camera app works for the front facing cam but not the main rear facing one.
Click to expand...
Click to collapse
When your in the camera app go into the settings of it and look for firmware update i dont know where it is exactly and am not on stock otherwise id tell you exactly

Generalzhou said:
Thanks guys. I factory reset my phone before and it still had the issue, I will definitely keep the Samsung warranty as a backup (don't want to send in my phone if I dont have to).
How do I update the camera firmware? I've tried other cameras, retro camera works but only sort of, another camera app works for the front facing cam but not the main rear facing one.
Click to expand...
Click to collapse
Factory Reset?.......you mean at the sprint store?...........or do you mean you did a factory reset, wiping your data (but leaving your firmware + bad camera untouched)............you can re-install a fresh version of your firmware w/out voiding your warranty, from the sprint website..........or else, as stated above, take your device to the store + let them do it...........that said, camera ZOOM FX has a dandy of a camera that you can DL from the market...........if it works, one more clue where your problem is coming from.
Sent from my SPH-D700 using xda premium

Nevermind, it seems like the camerafirmware.apk file did work (or something else did...). While the camera app didnt install, after I put the camerafirmware.apk file into the system/app folder 3rd party cameras started working again. Anyways, I hope this thread could be a useful reference for others who have this issue. Thanks.

Generalzhou said:
Nevermind, it seems like the camerafirmware.apk file did work (or something else did...). While the camera app didnt install, after I put the camerafirmware.apk file into the system/app folder 3rd party cameras started working again. Anyways, I hope this thread could be a useful reference for others who have this issue. Thanks.
Click to expand...
Click to collapse
1. Redownload cm7
2. Wipe data /factory reset
3. Flash the cm7 you just downloaded
4. Reboot
Everything should work fine now.
Sent from my SPH-D700 using XDA

Reboots, can't call, no sound!

My nexus 6p has worked fine for months however I woke up yesterday morning to find it would not play a video on YouTube. Continuing to use it I noticed the following symptoms:
Wont play videos of any kind (youtube, Facebook etc)
Speakers do not work at all
phone hangs and will not connect during incoming or outgoing calls. The call may connect after several minutes of the screen hanging on the blue calling screen however speakers don't work anyway.
Phone restarts itself randomly
I have tried a hard reset from recovery, wiped cache, booted to safe mode etc with no change.
The phone is bone stock and has not been rooted.
Any suggestions?

At this point I'd try rooting and just flashing stock ROM, don't install anything and see where it goes. If it survives, then maybe it was a rogue app, but that's a lot for an app to do - so it could be a hardware issue.

Same problem here.
teh roxxorz said:
At this point I'd try rooting and just flashing stock ROM, don't install anything and see where it goes. If it survives, then maybe it was a rogue app, but that's a lot for an app to do - so it could be a hardware issue.
Click to expand...
Click to collapse
I've got the same problem, but it happens only on stock, when I've got Chroma installed, everything is fine. One time it happened under Chroma. I don't know what causes it. Reinstalling factory images or even 7.0 doesn't help. Custom kernels didn't bring any improvement either.
Maybe there are some music drivers or something.

Yakksiek said:
I've got the same problem, but it happens only on stock, when I've got Chroma installed, everything is fine. One time it happened under Chroma. I don't know what causes it. Reinstalling factory images or even 7.0 doesn't help. Custom kernels didn't bring any improvement either.
Maybe there are some music drivers or something.
Click to expand...
Click to collapse
It could be a driver thing. Didn't look like a device issue, as it'd be constant. I would go back to stock and note when it happens and then flash a custom ROM and repeat the steps, to perform a controlled test. While doing so, take logcats so Beans / others can review them.

Gone to the service becuase even on a custom ROM I couldn't get any sound. They said that it was a hardware problem (I don't agree but we will see).