Database Info

[Q] Phone very unstable following "stable" CyanogenMod install

Hi, I recently purchased an HTC Desire with Telus in Ontario, Canada. Following a few days of regular service I got bored and decided to root the phone and install a custom mod. I am in no way blaming CyanogenMod for what has become of the phone, but it is nothing short of a frustrating nightmare these days.
The phone behaves extremely unstable, starting with random reboots, or inability to turn the screen back on following standby (having to pop the battery prior to powering the phone back on), down to constantly losing signal, inability to connect to WiFi, inability to send SMS messages. In fact, right this minute I am in dire need of sending an SMS and I am completely unable to get the phone to get a signal or send the message (the message either fails without telling me why, or gives me error 332). Aside from these problems, applications crash constantly, often simply unable to start-up.
I following the instructions in this wiki to the brim:
wiki.cyanogenmod.com/index.php?title=Full_Update_Guide_-_HTC_Desire
verifying versions (straight from the phone):
Baseband: 32.44.00.32U_5.09.05.30_2
Android: 2.2
Kernel: 2.6.34.5-cyanogenmod
Mod: CyanogenMod-6.0.1-Desire
Build: FRF91
I am at a complete loss here, and very frustrated. Any help or suggestions are HIGHLY appreciated...

I'll be the guy to make the 'obvious reply' since this forum seems to avoid making that sort of post =)
I'm a winmo user but from what I read, cyanogenmod android 2.2 with some modifications? Were you just bored of 2.1 and wanted to get to 2.2? Because there's an official update on the HTC site for that.
Otherwise, there is probably no setting or combination of settings that will act as a magic bullet and make the phone stable. If it's possible to overclock the phone you could try that, but even if that's an option it might make things worse. It sounds like strange advice since overclocking can also cause sleep of death and freezes, but I found my phone actually got more stable after. If you reach a point where you decide to get rid of cyanogen and flash a new rom, and there's some way to try OC first, you could give it a whirl.

LG Nitro HD HO!NO! v8.2 rebooting problem

Not sure if this is the correct place to post, but I am having a rebooting issue with the ROM. The phone seems to reboot while using Google Talk, specifically while typing, the phone just locks up for a few seconds and reboots. It seems to also always be when I'm either typing on the keyboard, or getting focus on a box that requires the keyboard for input. I thought it might be an issue with the gApps that I have installed, but I flashed back to my backup of v7.1, and the issue no longer persists.
Also, a general problem with HO!NO!, on both v7.1 and 8.2, the camera app crashes my phone quite a lot. It is random, so I can't say exactly what's causing it.
Also, is it normal for a phone to have completely incorrect time after rebooting (from a crash by the camera app, I should add) without a data signal? (This was a problem for v7.1. It updates fine within a second with a data signal, but the time seems to default to 00:00 without data.) I was in a place with no signal and all the pictures I took ended up with time stamps of something like December of 2002.
I'm currently using HO!NO! v7.1 with kernel version 3.0.8-HO!NO!_Mod-cyanogenmod+ and Cyanogen Mod version 9-20120721-UNOFFICIAL-p930.

I have the same issue. Same trouble with Jellybean too. I think it's something to do with the Kernel. we need a custom kernel soon!

Blaze Signal Keeps Going Out Problem(On Any ROM!)

So here's my issue, my Galaxy S Blaze has been switched from ROM to ROM constantly, I have seen ROMS with modified build.props, other added features, and a bunch of other tweaks, you name it! I don't know what all those tweaks mean, I have no idea if it could affect the way my phone receives the signal but it got me so frustrated that I kept switching roms until finally then I went back to stock and am no longer am switching to another ROM.
Here's a history of the ROM switching I've made in the past couple of months:
1st - MIUI
2nd- Cyanogenmod
3rd- Gummy ROM
4th- Liquidsmooth ROM
5th- Cyanogenmod
6th- Dirty Unicorns (problems with signal started occurring right about here, and onwards)
7th- Stock ROM (hmm... nope nothing fixed.)
8th- Validus (still no, I didn't like the constant force-closing of many apps)
9th- Gummy ROM (nope, what's worse is my screen kept freezing if I had atleast 2 apps open and I slid down the notification drawer)
10th- Cyanogenmod (well, maybe switching to cyanogenmod will fix it)
11th- Gummy ROM (*sigh* switching back? Nope, still didn't help my signal)
12th- Stock ROM (you would expect it to be fixed right about here, but nope)
So what's up what is the exact problem with my signal? Here's the thing: My signal works! That's a start atleast. However, if I turn on my Wi-Fi while I'm home, I can still call/text people, all of that works. But after maybe 2 hours or so, the signal bar is still there, it's telling me it has signal and it's connected, SOMETIMES it will be empty meaning I have no signal(when I really do). But in reality, I can't receive texts, nor calls, none of that. So how do I fix it? By restarting my phone sadly, that has been the only solution for me for these past 2 months. People have complained to me because I don't answer my phone anymore, well I'm sorry my phone can't receive those calls due to this messed up signal. There are 3 other T-Mobile phones in the house that have no problem! The problem here is with my Blaze phone.
So what if I turn the Wi-Fi off for the whole day and see if it's the main thing causing the issue? Well, I did this. Turns out that the signal stays on longer than when I'm on Wi-Fi but it still goes out. I have switched SIM Cards, I have tried switching my APN: from "epc.tmobile.com" to "fast.t-mobile.com" but the problem appears to happen more quickly on the "epc" one than the "fast" one. Please help me with this, this has been frustrating me a lot lately. I'm not sure if anyone has even had the same exact problem that I'm having, I've searched online but haven't seen a similar problem.
Some of you might say, wow that is a lot of ROMS you've switched to, I'm sure there were more that I missed but that's as of recent. I can install ROMS correctly, I know how to use CWM when installing a .zip and using Odin when it's a .tar(or other supported file extensions). I've factory reset, wiped the cache, the dalvik cache, all before installing a new rom. After installing each rom, I've also factory reset and wiped the cache to make sure no other problems could affect the way the rom would work. Hopefully I did the procedure right, thanks for anyone who's willing to help me!
Right now I am running:
Baseband Version:
T769UVLH5
Kernel Version:
3.0.8-perf-T769UVLH5-CL990184
[email protected] #1
SMP PREEMPT Fri Aug 17 15:12:14 KST 2012
Android Version:
4.0.4
Another Issue is that I can't even transfer files to and from my phone when connected to my computer! This is another big issue, here are some images:
http :// i.imgur.com/xx699ss.png
http :// i.imgur.com/1wRzJpX.png
Here's what happens when I turn Wi-Fi Calling on but maybe it's just a built-in function that I forgot it had and it's probably normal:
http :// i.imgur.com/cTSqRci.png
By the way, sorry for the links just copy and paste them in a browser to and remove the spaces between the http :// and i.imgur, thanks! Unfortunately, I can't post links until I reach 10 posts. If the links don't work for you, I've also provided attachments.
Many thanks!!!

That last picture does show the proper function of Wi-Fi calling however I don't know what to say about the rest of your problems.
Sent from my SAMSUNG-SGH-T769 using XDA Free mobile app

There are two things I would recommend trying...
1. Use Blackhole System Wipe
I know you've been following all the proper steps in CWM (and I would say to keep doing so), but I've added using Blackhole, in addition to the first steps, and I always get great system performance on my phone, and my parent's phones (I put them on ProvisionMod after stock was being stupid). It works well for pre installation for ANY ROM and helps prevent pesky issues. However, chances are, your issue is baseband related and this probably won't solve it... But still! You never know! It's worth a shot!
2. Reroot your phone
I know this will be annoying and pesky... but sometimes the process goes wrong from the beginning and starts giving issues later on... When I first rooted my mom's blaze, something went wrong, despite my following all the directions, and one of her partitions was completely disabled, no matter the ROM. I redid the process of rooting her phone (not from GB though... From the ICS stock) and fixed the issue instantly! I would try these two steps first and see if they do anything! Good luck!
Sent from The Doctor's Blaze

[Completed] [Q] Constant rebooting: i9100 Samsung Galaxy S2 :(

Hi there-
My Galaxy S2 just last night started with some new weird behaviour. I had tried to use it for navigation earlier in the evening and left WiFi and GPS on accidentally... an hour or so later the phone was running hot and started rebooting (has never been super-stable, so I wasn't too concerned) - charging overnight and now the phone insists on rebooting after about 1-2 minutes.
Have rebooted into SAFE MODE, and things are relatively ok, until I open the SETTINGS> APPLICATION MANAGER... which triggers a crash/reboot almost immediately.
I've not installed any new apps for some time (nor bothered with any regular virus scanning) - and am not sure what's up with my phone.
I'd really like to avoid having to re-flash/factory reset... as getting one's phone back to "normal" can take months!
Any helpful input would be most appreciated.
Thanks in advance!!! =)
Running Android 4.3.3 JellySNAP ROm, Kernel version: 3.0.101-Apolo_4.13_Regular-gf40153f
[email protected] #603
Build number: JSRA K47|=|v7.0

Maybe found the culprit? How to remove it? :/
Just in case anyone actually cares, I may have found some useful info...
Facebook Messenger has been very resource hungry and unstable... In my culling of apps I'm noticing it is the most resistant to being uninstalled. No matter how I find the app (in Rom Toolbox, App manager etc) - it won't let me kill it fully.
Attempting an uninstall of Messenger triggers an immediate crash/reboot.
How can I completely obliterate it?
Loopster said:
Hi there-
My Galaxy S2 just last night started with some new weird behaviour. I had tried to use it for navigation earlier in the evening and left WiFi and GPS on accidentally... an hour or so later the phone was running hot and started rebooting (has never been super-stable, so I wasn't too concerned) - charging overnight and now the phone insists on rebooting after about 1-2 minutes.
Have rebooted into SAFE MODE, and things are relatively ok, until I open the SETTINGS> APPLICATION MANAGER... which triggers a crash/reboot almost immediately.
I've not installed any new apps for some time (nor bothered with any regular virus scanning) - and am not sure what's up with my phone.
I'd really like to avoid having to re-flash/factory reset... as getting one's phone back to "normal" can take months!
Any helpful input would be most appreciated.
Thanks in advance!!! =)
Running Android 4.3.3 JellySNAP ROm, Kernel version: 3.0.101-Apolo_4.13_Regular-gf40153f
[email protected] #603
Build number: JSRA K47|=|v7.0
Click to expand...
Click to collapse

I managed to "freeze" messenger with a lot of luck... though I can't remove it. Phone is kind-of ok... unless I open the Application Manager.
Seems Messenger doesn't want me even looking at it! (Instant reboot)
Any ideas how to remove this awful program?

Hi there,
You'd be best served asking for help from the experts who own your device here:
[Q&A][SGS2][Newbies][Experienced Users][RCs] New members friendly Q&A thread
Good luck

Original Shield Tablet Freezes When Connected to WiFi

Hi there!
I've contacted nvidia regarding this issue (reps seems oblivious) and posted it on their official forums to no avail, so I'll try and give it a shot here.
Basically whenever my tablet connects to WiFi after being disconnected for some time (a few hours to a few days), the tablet freezes when it downloads notifications. The freezes can be minimal (like a 5 second freeze) or be quiet substantial (it can lock up for as long as 10 mins). Once all notifications are downloaded and displayed, the tablet then performs like a charm. I even got my tablet replaced from nvidia and it has the same problem as the one I sent in. Uninstalling Facebook and Facebook Messenger improves performance drastically, but when my tablet checks for notifications it freezes still freezes for a few seconds (with Facebook installed, it could lock up for 10 mins and crash the launcher multiple times). Running on max performance did nothing. I'm really curious if this is a hardware or software issue since some people doesn't seem to have this problem.
I'm running on nvidia's stock firmware (4.2) unrooted.
So here is my question. Have any of you guys experienced this problem? Were you able to solve it? How did you solve it (did a custom rom solve this)?
The main reason why I haven't installed a custom rom yet is because I use the stylus frequently and I use the touch-block feature in nvidia's stock roms and couldn't find ports of it.
Here is a video of the issue. (youtube.com/watch?v=cJrUPV7mY6s) Now there are a lot of widgets on the video, but I assure you removing all of them does nothing. I tried.

Facebook Messenger. That says it all. What other apps have you running in the background?
This definitely sounds like a software issue to me.
Maybe you're being hijacked. Who knows.

I've had this same issues since I got the tablet (K1). System reset, no non-Google apps. Happens regardless of FW; I'm on the latest update. Don't be quick to blame the OP.
Basically, every time the tablet gets a new network connection, the system hangs and becomes unresponsive for 10 seconds to 2 minutes at a time. It's obvious that it's updating all the apps' network requests. However, the thread priority should make the system hang. I've only seen this issue on the K1; never on any other Android device. Either they're using a custom network stack, or they've messed with networking priorities.

I'm on the latest update
Click to expand...
Click to collapse
Of Facebook Messenger? Or OS? Or all apps?
Either way, it makes no matter no such issues on Lollipop. I am just saying.