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

Top of screen and capacitive buttons unresponsive!

Hey everyone, I woke up this morning to find a surprise! My Atrix screen was unresponsive. It took me a couple reboots to figure out that the top part of the screen doesn't respond to touch. Worse yet, none of the capacitive buttons work. So if I get into an app, most of the time, there's no real way for me to get out of it, thus requiring a reboot and more careful selections.
The weird part is, it happened within a span of about 2 hours. I woke up around 5:30AM, checked some emails and texts, and woke back up around 7AM with a buggy screen. It did drop from about 18 inches off the couch last night. But everything was in working order...
Right now I'm in the process of backing up my text messages, because I might have to use a set of them to prove my case in court.
What's the first steps to try to get it back working? Or do you think its a hardware problem(maybe a cable loose)? As far as returning it under warranty goes, I'm rooted and unlocked on Kenn's GB ROM, so that's a no-go.

bigb252 said:
Hey everyone, I woke up this morning to find a surprise! My Atrix screen was unresponsive. It took me a couple reboots to figure out that the top part of the screen doesn't respond to touch. Worse yet, none of the capacitive buttons work. So if I get into an app, most of the time, there's no real way for me to get out of it, thus requiring a reboot and more careful selections.
The weird part is, it happened within a span of about 2 hours. I woke up around 5:30AM, checked some emails and texts, and woke back up around 7AM with a buggy screen. It did drop from about 18 inches off the couch last night. But everything was in working order...
Right now I'm in the process of backing up my text messages, because I might have to use a set of them to prove my case in court.
What's the first steps to try to get it back working? Or do you think its a hardware problem(maybe a cable loose)? As far as returning it under warranty goes, I'm rooted and unlocked on Kenn's GB ROM, so that's a no-go.
Click to expand...
Click to collapse
you are unlocked/rooted/custom rom = no warranty
anyways backup and maybe reflash the rom and see how that goes.

Hopefully you don't need to replace the digitizer... But if you do, there are lots of videos and it's reported to be one of the easier phones to do. Keep that in your back pocket as an alternative to a lengthy and costly court fight over a phone with no warranty!
Sent

Thanks guys, I already knew the risks associated with rooting and unlocking. I used an app called SMS Backup+ that allowed me to backup all my sms/mms and it also linked and sent copies to my Gmail.
I'll go ahead and try a reflash
*EDIT*
Did a quick wipe of the phone, and during setup, everything was OK! When blur came back, it was back to the same thing.

Bump...
Still lost

I would suggest backup all you apps and do a complete wipe of data. I had a similar problem when I first installed Alien. This fixed the issue.

bigb252 said:
Thanks guys, I already knew the risks associated with rooting and unlocking. I used an app called SMS Backup+ that allowed me to backup all my sms/mms and it also linked and sent copies to my Gmail.
I'll go ahead and try a reflash
*EDIT*
Did a quick wipe of the phone, and during setup, everything was OK! When blur came back, it was back to the same thing.
Click to expand...
Click to collapse
I would do a wipe and reinstall. You could also fix your permissions through rom manager or cwm.
Sent from my MB860 using XDA Premium App

I had a simillar problem: WIPE through CWM solved this problem

hi, guys i had the same problem... I remember getting it shortly after updating it to the leak version of gingerbread. Since then I have flash Alien built #3 but the problem remains...
I'm currently doing a Nandroid backup of my phone so i could try flashing to cherrypie hopefully this will solve my problem cuz I'm seriously feed up with it...
do you guy's think this will help? if so any suggestions before i flash? thanks in advance...

I had this problem brand new out of the box. I just took it to the store and they gave me a new one. One other thing i noticed was the FP sensor/button was almost like loose and i had to push it in real far for it to work. Maybe its a stuck FP button...
Sent from my MB860 using XDA App

im having the same issue, i cant make the buttons work, i have wiped everything in CWM, and using fastboot also and nothing, also tried flashing different roms but the problem persists, if anyone know how to solve will be great
thanks

I think you have one file corrupted... I'll try to remember which
Sent from my MB860 using XDA App

I think it may be touchpad.cfg. try Googling that and see if you can find a clue.
Sent from my MB860 using XDA App

Try here: http://www.kandroid.org/online-pdk/guide/keymaps_keyboard_input.html#androidKeymapKeyLayoutMapTitle
Sent from my MB860 using XDA App

thnaks for the answear, i flashed the 10 point multitouch patch to see if solved the problem but it didnt, yesterday i reproduced the error but idk how to solve ir, im gonna make a thread to show what i did

Issue with apps after root

Hi all, I rooted my dell streak last night with superoneclick, it worked fine after a bit of messing around, but ever since if I d/l an app from the market or elsewhere, itll d/l but hangs on installing. Ive searched but to no avail, not much on google either. Is this a common issue? Ive tried reboots and clearong market cache, but even have the same issue when Installing from sdcard. Any thoughts? Cheers for any replies. Sanders

Also, just tried to play some music, loudspeaker aint working??

rooting shouldn't be causing an issue here as far as I know, I take it you are running stock rom? Do your headphones still work? Sounds like you may have bigger problems though unfortunately. You can always try unrooting to see if the problems go away or do a dell factory reset...

Funnily enough, speakers working fine now. Still no apps installing though, yes im on dells 2.2. Ill try unrooting.
Thanks
Sent from my Dell Streak using XDA App

Bizarre FCs

Ok, if anyone can help me out on this, I'd be really grateful.
So, it started something like a couple months ago.
I was on Cyber.GR and Matr1x kernel, all was fine, when suddenly the phone stopped being usable: everything FC'd at boot and rebooting was of no use. I was pissed off but luckily I had a NANDROID from a couple days before.
I restored it and all was fine again.
One week passes and BAM everything FCs again.
I tried to switch kernels, but nothing.
I decided to wipe everything and flash AOKP (faster updates and Cyber.GR dev was going in service) and AIR Kernel.
I restored my apps using Titanium and everything was fine again.
One month passes and all of a sudden, a friday night, FCs again.
I was in panic, tried reflashing kernel, fixing permissions, wiping cache and dalvik, no use.
So I googled a little bit and found out that reflashing the ROM usually fixed the problem.
I reflashed ROM and gapps and, as google said, everything was back to normal.
Except that once again, nothing's fixed.
The phone stays stable for a couple of weeks circa, then it starts again to force close everything.
Reflashing ROM and gapps seems to fix this, but as you can see it isn't a permanent solution.
I post a logcat I took when the FCs started, so it's like 2 months old.
If anyone knows the reason of all of this, I will gladly pay you a couple beers: this ****'s driving me nuts.
Here's the logcat: http://pastebin.com/C6hr0sDT
tl;dr: phone randomly start force closing everything at boot on different combos of kernels and ROMs. no ****ing idea. paying money for solution.

Have you tried using another ROM? Seems like the easiest route to take.
Sent by pocket technology

After you flash the rom when you install your apps again do you just install the app or do you install with data? Its better to install apps fresh cuz if the data's corrupted then your going to get FC! Try installing the CM9 Skank Rom & don't flash another kernel leave it as is then install all your apps fresh no data & run it for weeks or months see if your still having fc the CM9 skank kang Rom are really great & stable try it out here you go! :thumbup:
http://forum.xda-developers.com/showthread.php?t=1386869
°N€×U$ $⁴G°

Make sure not to include system apps when restoring backups using tb. That might be the issue
Sent from my Nexus S®

That as well. I saw you did use AOKP also. Hmmmm. In my personal experience, my phone likes stockish kernels. Matrix always froze up on me after 100+ hours of up time with the stock nexus voltages applied. Air Kernel always gave me FCs. My phone is picky. No idea why. Maybe try using another kernel, stockish this time and see what happens? I haven't had any lock ups using thalamus', Pete's or, Simple Kernel.
Sent by pocket technology

Ok, first, I tried two ROMS as I said, Cyber.GR MOD and AOKP (M5, b37, b38). Always errors.
On thing I did, however, is restoring apps with data. Well, next time I have a spare day I'll try this way (even if my heart cries a little at the thought of logging in and reconfiguring every single app I have ).
Fun thing is that it happens randomly. For example, last night I went to sleep and left the phone charging: this morning FCs. Nothing's changed during night, I think
Thanks for the replies, guys!

Ok, first, I tried two ROMS as I said, Cyber.GR MOD and AOKP (M5, b37, b38). Always errors.<br />
On thing I did, however, is restoring apps with data. Well, next time I have a spare day I'll try this way (even if my heart cries a little at the thought of logging in and reconfiguring every single app I have ).<br />
Fun thing is that it happens randomly. For example, last night I went to sleep and left the phone charging: this morning FCs. Nothing's changed during night, I think <br />
Thanks for the replies, guys!
Click to expand...
Click to collapse
Yeah starting from scratch will not hurt too much ;-)
Sent from my Nexus S®