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"?

Help with Nebula ROM ISSUES

After a few issues I was able to get Nebula ROM 1.0.7 up and running on my EPIC. I really like it so far. It is much faster then the other ROM I tried out, plus it doesn't have any of the cheesey sound efffects.
I have used it for a day with no problems. My battery was getting a bit low so I shut the phone down to change batteries. I put the new battery in and when I booted it up it just went into a loop with the Nebula animation, then the 1.0.7 screen would come up and then it would just loop.
I took the battery back out, reinstalled it, and this time it boots into the phone but everything FC's. Took the battery out again and booted it back up and now this time it loads up, some things run, but others FC...
I did the clearing of all caches and user data three times along with a dalevic wipe three times... What gives??
I consider myself a computer geek, but am definately new to the rooting/custom rom thing, so I am a Noob, be gentle!!

socos25 said:
After a few issues I was able to get Nebula ROM 1.0.7 up and running on my EPIC. I really like it so far. It is much faster then the other ROM I tried out, plus it doesn't have any of the cheesey sound efffects.
I have used it for a day with no problems. My battery was getting a bit low so I shut the phone down to change batteries. I put the new battery in and when I booted it up it just went into a loop with the Nebula animation, then the 1.0.7 screen would come up and then it would just loop.
I took the battery back out, reinstalled it, and this time it boots into the phone but everything FC's. Took the battery out again and booted it back up and now this time it loads up, some things run, but others FC...
I did the clearing of all caches and user data three times along with a dalevic wipe three times... What gives??
I consider myself a computer geek, but am definately new to the rooting/custom rom thing, so I am a Noob, be gentle!!
Click to expand...
Click to collapse
Firstly, I'm sorry for your troubles and welcome you to the ROM scene. But I would say posting this (or looking through) the Nebula ROM thread or posting this in the Q&A section would likely end up with better results.
Secondly, I also had experienced issues with Nebula ROM 1.0.7. My recommendation is to Odin all the way back to DK28, then work your way back up to Nebula. Also, try flashing Nebula twice onto the device to try to remedy any problems.
Another tip, it seems that if you are using things like Titanium Backup that there are instances of people running into problems of backed up apps causing problems. Starting new is probably the best bet.
Hope this was of some use!

Thank you for the help.. I posted this in General because every other day I see people getting ripped into for not posting in General, so to be honest I have been scared to post anywhere else... But I have read the Nebula thread, not all 110+ pages, but quite a few of them. I am going to Odin back to DK28, format my SD card, and start from scratch, then try reinstalling all of my Apps.
I just think it is wierd that it worked flawlessly for a whole day without one FC and then when I changed my battery it went to hell.
The even stranger thing is some apps work fine, and then others FC everytime. Seems to be no rhyme or reason..
Only other thing I am thinking is I installed a bunch of new apps today and wondered if that could be part of the problem...
Oh well, it has made me more aware of what is going on behind the scenes with my phone.

I could be totally wrong, but I think that's due to it being an ext4 with no journaling rom. Without that safety net its possble for data to be corrupted. sinse I switched to ext4 with no journaling I started letting the phone turn off instead of just pulling out the battery.
Like I said tho I could be wrong on this. Back when I was on the moment I had ext2 which doesn't have journaling either and if the data became currupted somehow, it would cause the symptoms you are explaining.
Sent from my SPH-D700 using Tapatalk

socos25 said:
Thank you for the help.. I posted this in General because every other day I see people getting ripped into for not posting in General, so to be honest I have been scared to post anywhere else... But I have read the Nebula thread, not all 110+ pages, but quite a few of them. I am going to Odin back to DK28, format my SD card, and start from scratch, then try reinstalling all of my Apps.
I just think it is wierd that it worked flawlessly for a whole day without one FC and then when I changed my battery it went to hell.
The even stranger thing is some apps work fine, and then others FC everytime. Seems to be no rhyme or reason..
Only other thing I am thinking is I installed a bunch of new apps today and wondered if that could be part of the problem...
Oh well, it has made me more aware of what is going on behind the scenes with my phone.
Click to expand...
Click to collapse
Ah, alright. I'm not too certain as I'm unaware of a good deal of the inner workings of Android, but I do hope things get straightened out for you. My phone still has some apps that act up sometimes, mostly JuicePlotter it seems.

Hanging arround... I forgot my last un and passwd(I had an htc tilt a while ago... now I can't post on dev forum...) to use 1.0.7 I think you need ext4 (at least I'm using it) some apps are giving troubles with ext4. So try one by one, and use the cwm3 backup system. At least for me is easier and safer than tit or backup pro.
Sent from my SPH-D700 using Tapatalk

I am so glad I didn't update to 1.0.7!

socos25 said:
After a few issues I was able to get Nebula ROM 1.0.7 up and running on my EPIC. I really like it so far. It is much faster then the other ROM I tried out, plus it doesn't have any of the cheesey sound efffects.
I have used it for a day with no problems. My battery was getting a bit low so I shut the phone down to change batteries. I put the new battery in and when I booted it up it just went into a loop with the Nebula animation, then the 1.0.7 screen would come up and then it would just loop.
I took the battery back out, reinstalled it, and this time it boots into the phone but everything FC's. Took the battery out again and booted it back up and now this time it loads up, some things run, but others FC...
I did the clearing of all caches and user data three times along with a dalevic wipe three times... What gives??
I consider myself a computer geek, but am definately new to the rooting/custom rom thing, so I am a Noob, be gentle!!
Click to expand...
Click to collapse
Sorry I missed this yesterday, but I wanted to say that I had the same problem updating to 1.07 and I had already gone back to DK28 stock w/ CWM3 before the upgrade. I also restored some apps and settings selectively using titanium. One thing that we may have in common is that I ran my battery ALL the way down accidentally after this upgrade, tried turning it on a couple times (and it would shut down right away) and when I plugged the phone back in I got the repetitive force closes when I tried to turn it on.
Anyhow, I recharged completely, started from stock DK28 again (and wiped the battery stats) and even with restoring the same settings from Titanium I have been running it for about a week now and it is rock solid. So, give it another shot and see how it goes...

The short version is I got everything working!! And Nebula 1.0.7 is the fastest rom I have used yet... But don't get too excited because this is only the third I've tried, and one of the other two is stock DK28.
What I ended up doing was Odin'ing back to DK28, installing CW3, and then doing the 3x3 clears. Then I also formated everything I could find in CW. Installed the Nebula Rom and still had an issue. Rebooted back into CW3 and then reinstalled the ROM again, and whalla.. It works.
I think for some reason you have to install it twice.. Strange I know..

I had force close issues as well, and all I did to fix it was go into CWM, and format/clear cache partition, and format/clear the dalvik-cache. Did this cache clear and dalvik clear 3 times.

coryshad said:
I could be totally wrong, but I think that's due to it being an ext4 with no journaling rom. Without that safety net its possble for data to be corrupted. sinse I switched to ext4 with no journaling I started letting the phone turn off instead of just pulling out the battery.
Like I said tho I could be wrong on this. Back when I was on the moment I had ext2 which doesn't have journaling either and if the data became currupted somehow, it would cause the symptoms you are explaining.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
I second this as a possible problem. Shut the phone off 100% before removing the battery. On the moment that I also had if you removed the battery or used quick boot with ext2 you faced possible data corruption, but there were kernels that would check and fix data. You'd end up in a boot loop though if it didn't repair.
Sent from my SPH-D700 using XDA App

I've been making sure to shut it off before removing the battery, so far so good. I'm really liking this much better than stock.
Want to try a speedtest with the wifi tethering while going down th road.
I did a speedtest yesterday in my house and got 1.5mb DL, .5mb up. That was on my airrave though.
Sent from my SPH-D700 using XDA App

[Q] DX constant restarting

I've been searching for the last few days and have yet to really find anything to help me fix my problem.
the story:
Phone was rooted, back in Jan and I was running GummyJar 2.5, no problems, went to Apex V 1.3, no problems, but it ran a little slow. Today I decided to switch to something else to attempt and fix the speed problems, first I tried Incredibly Re Engineered v1.0, the phone ran well, but every 2-3 minutes it was rebooting me and sending me to the clockwork screen. So then I figured it had something to do with the ROM, so I went to Fission 2.5.7. Same problem, the phone runs great when it's on, but the constant restarted is unreal. I've done a factory reset, unrooted then rerooted the phone, then reinstalled the ROM, same problem.
Anyone ever have this issue and have a solution?
Thank you,
Eric
edit: Phone acts fine while plugged in to the computer or wall charger. Also made and attempt with SBF, to no avail.

Try an sbf....then go back to fission.
Just my thoughts. No overclock at first.

Running the SBF restore again...we will see what happens.

Hopefully someone else will stop by with thoughts.
Fission for me is real stable, ran it for long time now.
Worried it may be hardware problem....?
Might want to only install important apps at first also.

Try wiping data from Clockwork several times.
If that doesn't work you should definitely try SBFing and wiping data several times afterward.
Sent from my DROIDX using XDA App

I agree, I also loaded several ROM's and had a growing list of issues, SBF took care of everything for me.

Mine reboots when I pause video playback when connected with hdmi. But only since gingerbread, and I'm on my fourth version of gb. They have all done it so far, hoping official .596 will fix.
DX 2.3.3

Did the SBF'd it. Phone works flawlessly. I am now running Fission and Launcher 7, all without a hitch. Guess the phone just had to much going on and needed a fresh start.
Thank you all for the input. After I get a few more posts, I will post links and a DIY on how to do what I did. It was difficult for me to find anything with all of the steps and links in one spot, I want to make it easier for the next person experiencing this problem.

Yay! ....

Hey I been having the same problem with my droid x mines runnin stock 2.2.1 tho but it just keeps restarting and I don't know how to fix it lol. Im kinda new to this phone so does anybodyy have any suggestions?
Sent from my DROIDX using XDA App

CHip0,
SBF it...it's fairly easy and you can even find a youtube on how to do it....
http://www.youtube.com/watch?v=c58XaWnr6XE

Thank u very much! Lol
Sent from my DROIDX using XDA App

Safe Mode

Is there any way at all to disable the Fascinate from ever loading into safe mode again? It's really annoying when it happens because I have to reset all my widgets.
I've flashed my phone several times and it happens with every rom that I've had on it so is it part of the baseband kernel?

Get rid of the conflict that puts you in safemode. Safemode has to be better than your phone bricking.

johnnyplaid said:
Get rid of the conflict that puts you in safemode. Safemode has to be better than your phone bricking.
Click to expand...
Click to collapse
X2
List off the steps you used when flashing these last few roms (and what rom specifically) that you say are making you boot into safe mode...I've only seen it once on my phone and 1 reboot fixed it and I never seen it again, but that was months ago and I just chalked it up to me missing a step?! I have flashed many roms since and never see safe mode again.
Sent from my SCH-I500 using XDA App

Im starting to think that it's more a problem with my Fascinate than anything else. It usually happens when I have to pull the battery due to it locking up. Sometimes pulling the battery out a second time still doesn't get me out of safe mode and I have to continuously do it until it does.
For the past few months I've been using CM7 and updating with nightlies. On Monday I updated to the stable GLITCH kernel and so far it seems to be running much better. It's always had a problem with randomly bringing up my keyboard and backing out of apps and I have not had that problem yet since putting the GLITCH kernel on it.
Figured I'd also note in here that the GLITCH kernel is not currently working with the newest Cyanogen nightlies. It bootloops and I found that out the hard way.
For now im running GLITCH v11.1ML and CM7 Nightly 35 and it's been great so far.

so glad I havent run into safe mode

[Q] Play store breaks Cyanogenmod?

Hi everyone,
This morning when wake up I noticed a lot of applications were stopping ("XYZ has stopped") - including Google Keep. Also, many app/system settings were suddenly missing from the phone. I had to go through the whole process of reinstalling CM10, realizing that my Nandroid backup (made with OBackup) was in CWM format, rendering it unusable with TWRP (or this is what I, being pretty much a newb in the ROM world, understand from the situation).
A couple weeks ago something similar happened : my defy would bootloop at the CM logo.
This is starting to be exasperating a bit. But the only thing I can think of is that now I noticed I have Play Store 4.4.21 on the Defy - whereas on my Nexus 7 I have 4.3.11. Hence the version on my Defy seems to be the one that just came out. Could Play Store updating itself be causing the problems I'm having on my Defy? Why do I now have the new version if I just flashed CM10 a couple minutes ago, and why would it be working correctly now?
I already googled everything I could think of relating to this and couldn't come up with an answer. That is to say, I'm pretty much clueless about all this!
Thanks..

tb877 said:
Hi everyone,
This morning when wake up I noticed a lot of applications were stopping ("XYZ has stopped") - including Google Keep. Also, many app/system settings were suddenly missing from the phone. I had to go through the whole process of reinstalling CM10, realizing that my Nandroid backup (made with OBackup) was in CWM format, rendering it unusable with TWRP (or this is what I, being pretty much a newb in the ROM world, understand from the situation).
A couple weeks ago something similar happened : my defy would bootloop at the CM logo.
Thanks..
Click to expand...
Click to collapse
There are 2 possible things going on here:
problems with android's data sync with google's services. (this morning there was a diffused malfunction, at least here in Italy)
the infamous CM10's data corruption bug (see details in the bug list). it especially happens if you let completely discharge your phone. Symptoms match with yours
Since the data corruption bug is still under investigation, the best workaround is to keep a (weekly?) data backup.
After a data corruption, reformat in ext4 through the recovery's data tool and then:
reflash rom and gapps
restore your data

Well both times CM broke my phone's battery wasn't empty at all (the last time it was charging...)
When you refer to the sync problem I experienced it on my N7 yesterday, but it seems nowhere as dangerous as to be able to completely break the OS.
Oh well anyway, seems like CM10 isn't quite ready for being a daily driver.. I'll simply learn how to flash/restore backups correctly and as fast as possible it seems!
Sent from my Nexus 7 using Tapatalk 4

The only thing that really bothers me is that I never thought I'd lose so much time in rooting/modding my old defy.. I've spent countless hours on XDA/other forums, and yesterday I even had to restore the (almost bricked) defy with rsdlite after (incorrectly) trying to put CWM to restore my otherwise unusable backup. Then, when I had succeeded in putting CWM, it would totally refuse to restore, complaining about unmountable /system!
I do understand that its totally my choice to root/mod my devices, but with cell phones becoming more and more essential nowadays in everyday life, it seems to me that everyone almost has to become an android developer to survive!
/whine
Sent from my Nexus 7 using Tapatalk 4