Eris rebooting spontaneously - Droid Eris Android Development

I am running Aloysius v12. I have removed most of the rosie stuff. I am using JIT. Installed ADW but running Launcher Pro.
My phone reboots itself about 4 times a day. It doesnt matter if it is charging, or if I am running an app of some kind, or on the phone. It will just reboot. First it started while running ADW and oc'd to 786. So, I switched to LP and slowed it down to 748. Still reboots.
What can be causing this?

The most likely culprit is overclocking.
Keep moving your maximum down.

BigBeefy said:
I am running Aloysius v12. I have removed most of the rosie stuff. I am using JIT. Installed ADW but running Launcher Pro.
My phone reboots itself about 4 times a day. It doesnt matter if it is charging, or if I am running an app of some kind, or on the phone. It will just reboot. First it started while running ADW and oc'd to 786. So, I switched to LP and slowed it down to 748. Still reboots.
What can be causing this?
Click to expand...
Click to collapse
slow down oc to 710, but the reboots are going to keep happening until you remove JIT. It is very unstable and WILL cause spontaneous reboots.

OK, thanks,

I read over in another forum another reason for random rebooting.
"Only MOD from there that gave me issues was the battery removal from task bar. It would make the phone random reboot. Others had the same issue."
I am using Droidkevlar's MOD:
v.03 Removed time from task bar (thanks to jschisurf for this)
Multiupload.com - upload your files to multiple file hosting sites!
I wonder if this is why my phone is rebooting? I didnt do the battery removal mod, but the time removal. Battery icon changed to the round battery indicator. Any thoughts on this? Or is it more likely it is due to the JIT? I have removed JIT and slowed down to 710

I have disabled JIT.
Phone just rebooted itself again. Indication LED was flashing green while rebooting. I got a text message right before it rebooted. Didnt start at the green skaters, just went straight to the nexus boot animations.
This is getting really annoying now.

I would suggest a reflash of your rom. Seems like maybe one of your apps or customizations is messing around with the phone.

If you don't get the green skaters boot screen on your crash reboot, it's not totally rebooting. It sounds like your Home may be crashing. Does this happen when running other homes?

nimdae said:
If you don't get the green skaters boot screen on your crash reboot, it's not totally rebooting. It sounds like your Home may be crashing. Does this happen when running other homes?
Click to expand...
Click to collapse
It started happening with ADW home. So, I switched to Launcher Pro. It has only done it once with LP.
I havent added any new apps before this all started.
I have added a MOD to my notification bar. That is the only thing different. I have been using Aloysius v12 since it was posted. I do have Rosie deleted tho. I deleted Rosie when I added my JIT. Now that I have disabled JIT, I wonder if reflashing v12 will help out.
Can I reflash v12 without doing a full wipe and retain all my apps and settings?

I have Eris lighting 2.5 and I have the same thing happing with ADW as the home scree. n

Clear dalvik again.

Nanajoth said:
Clear dalvik again.
Click to expand...
Click to collapse
Do I do a nand first?

It would not hurt.

didnt work. But thanks.

I had the same problem and worked for me, what applications do you have?

Actually, I just posted another thread about my desk clock app posting celsius temp instead of fahrenheit and thought you were responding to that one. I did however do a nand back up and delvick wipe. I will watch to see if I reboot at all tomorrow. Sorry, I got confused on which thread I was reading.
-------------------------------------
Sent via the XDA Tapatalk App

Does your phone run hot? This was happening to my phone constantly (like I couldn't even get past skateboards sometimes) so I did a rollback to stock 1.5 then ota and vzw replaced it in store only to get home and have it happen again. I had them replace the battery after and it hasn't happened since.

sickbox said:
Does your phone run hot? This was happening to my phone constantly (like I couldn't even get past skateboards sometimes) so I did a rollback to stock 1.5 then ota and vzw replaced it in store only to get home and have it happen again. I had them replace the battery after and it hasn't happened since.
Click to expand...
Click to collapse
My phone never runs hot. I am only clocked to 710. No JIT.

Make sure you are using the Passive SetCPU widget, not the Active.
Try disabling A2SD.

I too had this same problem and after having the battery replaced and flashing a fresh rom all is fine.

Related

phone randomly reboot / force close

I picked my Nexus S up this am as the store opened at 9am. I powered it on and away it went it had all of my apps dl in minutes.I had to go into work so I just let it charge on my car charger. Got to work and went to start Cardio trainer ( which is an app I use daily for about 3-5 hours per day) it immediately force closed. Force closes each time I try and use it. So i sent message to dev. The next thing I know I get a message saying that Beautiful Widgets geolocation is getting false reading from the GPS and it force closes. The GPS has been spotty. When first initiated it took over 10 minutes to get a lock. Turned it off and tried again and it took 7 minutes. The third time it was about 15 seconds and since then it alternates back and forth from almost instant to minutes again. What concerns me is that the accuracy just bounces back and forth from 32.6 ft to 16.3 ft and anywhere in between and really never stabilizes. This may be normal for this type GPS systems(I don't know) Also I have the old market and cannot find a link for the new market.Wasn't Gingerbread suppose to come with the new market? So far I am impressed with the smoothness of the system but not with the GPS. Also the lInpack scores are lower than on the Vibrant. Appears to be very solid. Anyone else have any of these problems?
tenbeau said:
I picked my Nexus S up this am as the store opened at 9am. I powered it on and away it went it had all of my apps dl in minutes.I had to go into work so I just let it charge on my car charger. Got to work and went to start Cardio trainer ( which is an app I use daily for about 3-5 hours per day) it immediately force closed. Force closes each time I try and use it. So i sent message to dev. The next thing I know I get a message saying that Beautiful Widgets geolocation is getting false reading from the GPS and it force closes. The GPS has been spotty. When first initiated it took over 10 minutes to get a lock. Turned it off and tried again and it took 7 minutes. The third time it was about 15 seconds and since then it alternates back and forth from almost instant to minutes again. What concerns me is that the accuracy just bounces back and forth from 32.6 ft to 16.3 ft and anywhere in between and really never stabilizes. This may be normal for this type GPS systems(I don't know) Also I have the old market and cannot find a link for the new market.Wasn't Gingerbread suppose to come with the new market? So far I am impressed with the smoothness of the system but not with the GPS. Also the lInpack scores are lower than on the Vibrant. Appears to be very solid. Anyone else have any of these problems?
Click to expand...
Click to collapse
It sounds like a GPS problem with your device, Just get it swapped mate
JD
I've only had FCs using the new google maps so far.
Random FC for me in maps, market and gallery :-/
ive yet to experience a FC
Cardio trainer is not working for me either, I am wondering if the dev's need to update it for 2.3, I also can't get vlingo to work.
JupiterDroid said:
It sounds like a GPS problem with your device, Just get it swapped mate
JD
Click to expand...
Click to collapse
I don't think it's a gps thing, I can't even get into cardio without it FC, my GPS locks without a problem.
phone randomly goes to boot animation screen
Ok, so it appears something is wrong with my phone. Every once in a while, i'll look down on my phone or in the middle of doing something, and it will go to the boot animation screen. Most of the time, the boot animation screen is dimmer than on normal start up. It will eventually go back to the ui, which I will then have to restart my phone because it won't connect to wifi or 3g.
Anyone else had this problem? Think it's worthy of getting a replacement from bestbuy or a glitch that should be fixed with an ota?
I haven't seen anything like this yet, though I suppose I don't keep my eye on my phone constantly, so I suppose it could have happened while I wasn't looking. No WiFi or 3G problems, either.
Sounds like you've got a serious issue there if you're seeing it a lot, though. I would get it replaced. Unless you're running a third-party ROM or some other non-stock mod, in which case dump it first and see if the problem is being caused by that.
Yea I had this happen twice. At gym was changing a track with Bluetooth headphones and went to dimmer bootscreen had to pull battery. And another time I had to reapply all my Widgets on my homescreen. I'm on CM7 rom
Sent from my Nexus S using XDA App
Are you using a custom ROM/kernel/SetCPU? Those problems sound like the ones the D1 has when it's clocked past a stable speed.
Sent from my Nexus S using XDA App
rocketragz said:
Ok, so it appears something is wrong with my phone. Every once in a while, i'll look down on my phone or in the middle of doing something, and it will go to the boot animation screen. Most of the time, the boot animation screen is dimmer than on normal start up. It will eventually go back to the ui, which I will then have to restart my phone because it won't connect to wifi or 3g.
Anyone else had this problem? Think it's worthy of getting a replacement from bestbuy or a glitch that should be fixed with an ota?
Click to expand...
Click to collapse
I'd look at the software you've added since the phone was purchased as the first primary suspect. Weird widgets, background services, live wallpapers, background syncing app, something like that...
You'd want to wipe/reset the phone before a return anyways, so why not do a factory wipe/reset from the settings/privacy menu, then start off with a fresh phone (software wise)? Be conservative in what apps you install at first, and check for stability; then slowly add back the stuff you'd have one by one and see which app from the Market causes the glitch.
I think that's a bit more fair to Samsung, Best Buy, and whoever ends up with the device as a refurb, than returning what is probably not bad hardware to the store.
demo23019 said:
Yea I had this happen twice. At gym was changing a track with Bluetooth headphones and went to dimmer bootscreen had to pull battery. And another time I had to reapply all my Widgets on my homescreen. I'm on CM7 rom
Click to expand...
Click to collapse
Hmmm...and you don't think the fact that you're using ALPHA level firmware that is known to have some bugs in it, might be your problem?
I'd expect that kind of thing with CM as long as it's alpha, and even beta. I wouldn't be surprised with it even on the RC versions. It's experimental until Team Douche releases an actual ready-for-prime-time version.
Are you using a custom ROM/kernel/SetCPU?
Click to expand...
Click to collapse
Nope, I'm not even rooted. I am however running ADW ex launcher. As far as widgets, the only widget i have running is the weather/news that came stock on the phone. As far as apps, I really don't have anything crazy downloaded or running.
rocketragz said:
Nope, I'm not even rooted. I am however running ADW ex launcher. As far as widgets, the only widget i have running is the weather/news that came stock on the phone. As far as apps, I really don't have anything crazy downloaded or running.
Click to expand...
Click to collapse
I've been running ADW.Launcher without problems up to now. I just upgraded to ADWLauncher EX last night; I'll post here again if I start seeing this issue.
this is similar to the other topic.
Random Reboots, we call it on the SGS (samsung galaxy s) side
hoping for the best, it is not the same deadly problem we found on some of the 16GB SGS phones, that eventually lead to the corruption / destruction of the internal SD
but those were the signs.
so i'm really hoping that is not the same problem, else i'll really be pissed with Samsung to produce yet another crappy phone with cheap internal parts.
it should not be, as i saw pictures of the innards of the SNS (samsung nexus s) and it was clearly showing SandDisk for the 16GB internal SD
Random Reboots
A couple of times I've had the Nexus S reboot, once when I was in the middle of a call and once again as I was messing around with the settings.
I'm running 2.3.1, th latest build GRH78, does anyone have an idea as to why the random reboots are occurring?
Thanks in advance for your help
Sent from my Nexus S using XDA App
Let's please keep it friendly and on topic here. Thank you
reception bar is stable but on active call it gets disconnected and i have to turn the phone off and on right away thia happens pretty often. I called samsung and they have no solution but to tell to go get it exchanged. This is already a second device.
Sent from my Nexus S using XDA App
Same thing happens to me.. now 4 times its happened to me
Sent from my Nexus S using XDA App

Odd problem across all ROMs I've installed

So, I've tried a number of major ROMs available for the Epic. ACE ROM, Midnight ROM, and now Bonsai 4.1.1.
I have a very odd issue with particular programs.
The programs are:
Backbreaker Football - gets stuck at loading screen
Chalk Ball - FCs after launching
Plants vs. Zombies - freezes at loading screen (only used this one on bonsai)
Doggcatcher - Works fine, except for when I try to switch between podcasts (listening to one after listening to another) it freezes. I close and re-open and it works fine again until I switch tracks
The first three are Amazon app purchases, so I could see a common issue, but Doggcatcher is a market purchase.
I thought it might be an SD card issue, but I've reformated twice now.
Any ideas?
I should also mention it worked for the first two days I had bonsai installed. Weird.....
Sent from my SPH-D700 using XDA Premium App
Did you have journaling on or off? If you had journaling off and you have a freeze, you have to pull the battery and data corruption starts and usually continues to get worse. Best thing to do until you find out what is causing freezes is to enable journaling for the ROM you are on or going to be on, do all wipes, reflash the ROM, then put these apps on fresh with no data (backup and restore from Titanium the app only if you can't redownload). If you are running a Overclocking or undervolting app, you may want to uninstall it until you resolve these issues.
kennyglass123 said:
Did you have journaling on or off? If you had journaling off and you have a freeze, you have to pull the battery and data corruption starts and usually continues to get worse. Best thing to do until you find out what is causing freezes is to enable journaling for the ROM you are on or going to be on, do all wipes, reflash the ROM, then put these apps on fresh with no data (backup and restore from Titanium the app only if you can't redownload). If you are running a Overclocking or undervolting app, you may want to uninstall it until you resolve these issues.
Click to expand...
Click to collapse
Kennyglass is right. It could very well be an Overclocking or Undervolting app. I can run at 1400 all day when messing with my phone but if I go to watch a movie or play a game, I have to back off of the overclock or it will freeze after a certain amount of time
Sent from my SPH-D700 using XDA Premium App
Thanks Kenny.
I was running Mighnight and ACE with journaling ON, so I don't think that was it. And I didn't use an UV or OC apps with Bonsai.
It's really puzzling as I now have Frankenstein installed and everything seems to be working fine.
Perhaps I just have a flakey phone?
lattiboy said:
Perhaps I just have a flakey phone?
Click to expand...
Click to collapse
this is a possibility itself. I've noticed a wide range of 'what these phones can do' that's not the same from one device to the next.. for example, when SRF 1.1.0 came out, lots of people had lots of problems flashing it, and others worked perfectly the first flash.. very strange why some phones like it while others didnt.
For over clocking, some phones will sscream along at 1.4 ghz, and others will puke at even 1.3 ... it's all a matter of what your phone will allow to play nicely with and what it just won't allow.
lattiboy said:
Thanks Kenny.
I was running Mighnight and ACE with journaling ON, so I don't think that was it. And I didn't use an UV or OC apps with Bonsai.
It's really puzzling as I now have Frankenstein installed and everything seems to be working fine.
Perhaps I just have a flakey phone?
Click to expand...
Click to collapse
It is possible. Bonsai OC's to 1120 and maybe even that is too much for your phone and causes a freeze here and there.
ARRRGGG!
Okay, everything was fine and dandy UNTIL I REBOOT. Frankenstein was working gloriously, and now these same apps are acting crazy.
Doesn't seem to matter what kernel or ROM I'm running.
Is this an EXT4 thing? I've had no FCs, so I don't think journaling is doing it either?
I'm running on the clean kernel now.
Ugh....
PS I've been able to run 1400 Mhz stable on Genocide, so it's not that either....
lattiboy said:
ARRRGGG!
Okay, everything was fine and dandy UNTIL I REBOOT. Frankenstein was working gloriously, and now these same apps are acting crazy.
Doesn't seem to matter what kernel or ROM I'm running.
Is this an EXT4 thing? I've had no FCs, so I don't think journaling is doing it either?
I'm running on the clean kernel now.
Ugh....
PS I've been able to run 1400 Mhz stable on Genocide, so it's not that either....
Click to expand...
Click to collapse
Are you sure you have journaling enabled.

Alliance 7.7

OK, so I'm a noob (to evo) and can't post on the dev thread for the Alliance 7.7 ROM so I'm going to throw this out here and hope for a response.
I tried RLS1 and didn't like it, there was some functions that irritated me so I went back to 7.7.
I like 7.7, I've got it stable, no sense reloads and I love the functionality.
However, my battery life is atrocious!!! I thought this was supposed to help save batt life??? I burned about 50% batt life in less than 3 hours in sleep mode!??
What did I do wrong??
I've been experimenting with Task Killer, Juice Defender and other supposedly power "saving" apps and settings but I haven't found the "holy grail" yet.
I'd really like someone to point me in the right direction if at all possible..Thanks!
Did you try calibrating your battery when you first flashed the rom?
Try downloading the battery calibration app by nema from the market.
https://market.android.com/details?id=com.nema.batterycalibration
What PRI do u have? If you go into settings and about phone (I'm not exactly sure if that's the correct path) it should tell you. If your running something newer than 1.77 some phones have a wake issue where it wont let the phone sleep with newer PRI's. Try downgrading to 1.77, the wake issue should then be gone.
You can get PRI 1.77 from here just make sure you backup your WiMax keys before you flash, you know just in case something goes wrong. : http://forum.xda-developers.com/showthread.php?t=715485
Maybe its one of the apps that your using that's not letting your phone sleep hence your battery drain. Spare parts on the market should show you if any apps are keeping your phone awake.
https://market.android.com/details?id=com.androidapps.spare_parts
Or your battery is going bad? I was having such horrible battery life with my Evo that after a while it just couldn't hold a charge anymore. I purchased a new one and all is well now.
Try an AOSP rom? AOSP roms tend to have better battery life than Sense roms. They don't have many services running in the background eating up memory.
I can't think of anything else anymore but hope this helps!
tony0691 said:
Did you try calibrating your battery when you first flashed the rom?
Try downloading the battery calibration app by nema from the market.
https://market.android.com/details?id=com.nema.batterycalibration
What PRI do u have? If you go into settings and about phone (I'm not exactly sure if that's the correct path) it should tell you. If your running something newer than 1.77 some phones have a wake issue where it wont let the phone sleep with newer PRI's. Try downgrading to 1.77, the wake issue should then be gone.
You can get PRI 1.77 from here just make sure you backup your WiMax keys before you flash, you know just in case something goes wrong. : http://forum.xda-developers.com/showthread.php?t=715485
Maybe its one of the apps that your using that's not letting your phone sleep hence your battery drain. Spare parts on the market should show you if any apps are keeping your phone awake.
https://market.android.com/details?id=com.androidapps.spare_parts
Or your battery is going bad? I was having such horrible battery life with my Evo that after a while it just couldn't hold a charge anymore. I purchased a new one and all is well now.
Try an AOSP rom? AOSP roms tend to have better battery life than Sense roms. They don't have many services running in the background eating up memory.
I can't think of anything else anymore but hope this helps!
Click to expand...
Click to collapse
Our of stupidity but, how exactly can you back up your WiMax Keys? Where can you go? Lol sorry, feel free to troll on me for asking that
Sent from my PC36100 using XDA Premium App
Lol Oh no none of that. I don't troll on anyone for not knowing something, we've all been there. Are you using amon ra recovery 2.3? If so, boot into recovery, go to backup/restore, nandroid backup and then it'll give u a list of things you might want to select to backup. Just unselect everything, select wimax and then select perform backup. It should take a couple of mins and then your done.
Actually I'm using ClockWork Mod 2.6 just seemed easier to me than AmonRa. (weird I know). but ok, nand back up and just select the WiMax info??
Also, v7.7 had an undervolt script built into it that some phones, mine included don't like. Might try flashing alliance rls2. Had the script removed.
tony0691 said:
Did you try calibrating your battery when you first flashed the rom?
Try downloading the battery calibration app by nema from the market.
https://market.android.com/details?id=com.nema.batterycalibration
What PRI do u have? If you go into settings and about phone (I'm not exactly sure if that's the correct path) it should tell you. If your running something newer than 1.77 some phones have a wake issue where it wont let the phone sleep with newer PRI's. Try downgrading to 1.77, the wake issue should then be gone.
You can get PRI 1.77 from here just make sure you backup your WiMax keys before you flash, you know just in case something goes wrong. : http://forum.xda-developers.com/showthread.php?t=715485
Maybe its one of the apps that your using that's not letting your phone sleep hence your battery drain. Spare parts on the market should show you if any apps are keeping your phone awake.
https://market.android.com/details?id=com.androidapps.spare_parts
Or your battery is going bad? I was having such horrible battery life with my Evo that after a while it just couldn't hold a charge anymore. I purchased a new one and all is well now.
Try an AOSP rom? AOSP roms tend to have better battery life than Sense roms. They don't have many services running in the background eating up memory.
I can't think of anything else anymore but hope this helps!
Click to expand...
Click to collapse
thanks for the info, I think the battery calibration helped a little, only 30% depleted after about 8 hours with moderate use.
I found I do have a newer PRI, version 1.90_003
Before I go messing with it, what is the PRI and what does it do?
billbowers said:
Also, v7.7 had an undervolt script built into it that some phones, mine included don't like. Might try flashing alliance rls2. Had the script removed.
Click to expand...
Click to collapse
one of the reasons I didn't like RLS1 was the way they had the personalize button set to open the Kingsrom website. Did they change that, or is there a way to change it?
oi, I had things going pretty well with 7.7 but it started getting glitchy and slow. Don't know why because once I had everything running smooth I didn't mess with it anymore. Reboot helped for a little while but started glitching again shortly after.
I decided to go to RLS2, it's running smooth but my lockscreen shortcuts have dissapeared and I can't get them back, any ideas on that??
shaw_2112 said:
oi, I had things going pretty well with 7.7 but it started getting glitchy and slow. Don't know why because once I had everything running smooth I didn't mess with it anymore. Reboot helped for a little while but started glitching again shortly after.
I decided to go to RLS2, it's running smooth but my lockscreen shortcuts have dissapeared and I can't get them back, any ideas on that??
Click to expand...
Click to collapse
You might try going into your personalize settings and select a different lock screen, I know there are a couple that take that certain option away LOL I use the weather one with the app selector or the wallpaper with the app selector. Hope it helps
Sent from my PC36100 using XDA Premium App
dgomez720 said:
You might try going into your personalize settings and select a different lock screen, I know there are a couple that take that certain option away LOL I use the weather one with the app selector or the wallpaper with the app selector. Hope it helps
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
no good, lock screen isn't displaying the way it should, tried several and nothing changes.
Did a factory reset and the lock screen is working correctly again. There must have been something that glitched when I restored my settings.
Tried restoring my backups and it the lock screen isn't right again. So I guess I either live with it or start from scratch again..

[Q] Random lock ups freeze

I keep getting random lockups, at least more than once a day, and sometimes several reboots in a row.
It appears that i can happen almost any time, whether it be at a lock screen, while titanium is asking for root, or opening twitter or facebook, even the gmail app. It simply freezes, and requires me to long press the off button and reboot.
Unfortunately, i can't get adb via usb to work on the nook, so i can't get a reliable logcat.
Is this common? I have had two nook devices so far, tranferred the rom over through nandroid and have had lock ups on both, I am flashing regular cm7 nightlies now (emmc), but it occured using phiremod too.
Help?
I never had one, maybe I'm lucky
Have you tried fixing permissions in clockwork?
Sent from my LG Optimus V using Tapatalk
I am having the same problem. I loaded CM7 to my emmc yesterday and I have had it freeze on me a couple of times now. All have been random. I do have performance set to 1.1 and on demand gov set.
So I can just go to ROM manager to fix permissions? Hopefully that works.
EDIT**
Did not work. Was fine, then I uninstalled market updates, connected to wifi, opened the old market, searched for flash and it froze up. Any ideas?
EDIT 2**
uninstalled beautiful widgets (read that somewhere), so far no lockups (fingers crossed).
i had mine lock-up twice last night
i was in dolphinHD and i had just installed swype beta
i have only had 1 time that it has locked up before then in the last 1-2 months that i have had it.
im blaming swype, since i havent had the problem in the past
perhaps not your problem, if you dont have it installed.
I get lockups pretty regularly. It's irritating. Not sure what the cause is. I thought overclocking had something to do with it but everyone else is overclocked and this problem doesn't seem to be common.
How low do you have the voltage settings in tweaks? Having a voltage just barely too low for your CPU can cause a lot of weirdness. Also, it could be any one of the stepping voltage settings, not necessarily either the min/max frequency.
Folks, playing with the voltage settings in nook tweeks is not for the average user. These settings can really bork your nook. That's why you get a warning when you open those settings.
That being said, I have been running cm7 on eMMC for months and have never had a lockup. I am overclocked to 1200 mHz but have left the voltages alone.(cm7.1 nightly 160).
If you are running on eMMC,try fix permissions first. If that does not help, start looking at the apps you are running to determine if one of them might be the problem. Several people have reported issues running beautiful widgets. There are other apps that can cause issues. If you have good backups of all your apps, try removing apps one at a time. In the process, you might learn something about your system.
Worst case, reinstall cm7, wipe data, cache, and dalvic cache. Start over with a clean system and add your apps (apps only, not apps+data) one at a time. This will ensure that a possibly currupt data set was not causing the issue.
The key to a fast, well functioning nook is to start slowly and ensure each change works well before moving on to the next step.
While it's true I have more time than most to play (retired), my nook can run circles around most competitors but only because I took the time to set it up right the first time and I am not afraid to wipe everything and start over.
Sent from my NookColor using Tapatalk
I fixed permissions some time ago, seemed to help a bit, but i still get the odd lock up or two. I am running Swype and Beautiful widgets(anyone know a good alternative?)
I had been getting irritated by these these random locks up for a while. It seems that uninstalling beautiful widgets fixed the problem for me. I thought it might be that BW was trying to access the GPS, but it still locked up after disabling geo location in BW.
liam.lah said:
I fixed permissions some time ago, seemed to help a bit, but i still get the odd lock up or two. I am running Swype and Beautiful widgets(anyone know a good alternative?)
Click to expand...
Click to collapse
In case you're still interested, BeWeather is a great substitute for BW and FlexT9 in place of Swype.
Also, I had issues with lockups no matter my overclocking and formatting the eMMC and possibly reseating the SD card fixed it.

CM7 B2TF w/Faux Kernel & Launcher Pro issues

Anyone running this combination?
CM7 B2TF, Faux kernel (any version, overclocked or not) and Launcher pro?
I seem to get a ton of force closes of launcher pro all throughout the day, and a 3 or 4 times a week I'll look at my phone and notice it has randomly shut off.
I'm not undervolting and the phone does not run hot.
Thoughts?
i've had that before but i think it was due to a kernel or radio. I have cm7 with faux
1.30 and haven't had any problems. Maybe a random reboot everyweek but i can live with it.
waktasz said:
Anyone running this combination?
CM7 B2TF, Faux kernel (any version, overclocked or not) and Launcher pro?
I seem to get a ton of force closes of launcher pro all throughout the day, and a 3 or 4 times a week I'll look at my phone and notice it has randomly shut off.
I'm not undervolting and the phone does not run hot.
Thoughts?
Click to expand...
Click to collapse
I had the same configuration as you and after installation i had a lot of FCs. I rebooted the phone and fixed the permissions and problem was solved.
I'm using ADW EX (which I don't like as much as Launcher Pro) but no FCs in the last day and a half.
I was running this combo for a while, LP never force closed but if you are running launcher pro with the LP Widgets such as the twitter or friends you may have a couple.
I used to have the Facebook/twitter widget on one home screen and it would force close all the time, once I removed the widget I never get a force close, this problem goes back to moto builds for me.
Sent from my Motorola Atrix 4G MB860 using Tapatalk
Thanks. I was actually thinking that might have something to do with it because the facebook widget would seem to hang from time to time. I did end up getting rid of that but I still use the calendar widget because I use it all the time.
Yup that's why I left LP+ for ADW EX. LP+ just went crazy on me and started force closing constantly, I tried changing every setting I could but nothing made a difference. ADW hardly ever force closes. Like you I had preferred LP to ADW, but not anymore! ADW pros far outweighs LP pros imo.
Sent from my MB860 using xda premium
waktasz said:
Anyone running this combination?
CM7 B2TF, Faux kernel (any version, overclocked or not) and Launcher pro?
I seem to get a ton of force closes of launcher pro all throughout the day, and a 3 or 4 times a week I'll look at my phone and notice it has randomly shut off.
I'm not undervolting and the phone does not run hot.
Thoughts?
Click to expand...
Click to collapse
Same here. Switched to Go Launcher and no problems now. Also fixed permissions.
Preaching to the choir my dude.
FC's everywhere, random reboots, GPS blows.
Sadly, I think it's the best we have so I'm just dealing with it now.
my best advice? don't run cm7 b2tf....
run weekly 4.

Categories

Resources