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.

[Q] Tasker on MIUI/WajkIUI

Hi all.
Sorry if this is the wrong place to post, but this thread is regarding bugs on custom ROMs, so here I am.
A while back I switched from CM7 to WajkIUI, and I really have enjoyed this ROM since trying it. Recently however, I've noticed a couple of issues regarding MIUI/WajkIUI and Tasker. I've mentioned my problems in the relevant ROM thread here, and also on MIUIandroid.com, but nobody seems able/willing to help.
I have profiles configured within Tasker that will switch my phone to mute (Silent Mode) when I'm at work (based on WIFI near attribute, which is working fine). WajkIUI ROMs subsequent to 1.9.2 are unable to switch this, or indeed make any changes to volume.
I also have a profile that will switch on Bluetooth when I get an incoming call (using the Incoming Call option in Tasker). I've no idea when this stopped working, I'm on 1.9.2 at the moment, and it doesn't work here. I've tested the profile activates, and it does - but it doesn't switch on Bluetooth.
Finally, my third bug relates to the above, but not Tasker. If I switch Bluetooth on manually and pair with my headset - I can't get my headset to answer the call or to ring the last number (two things it has always done before).
Is there ANYONE who can help fix these? Are these issues solely on MIUI based ROMs, or does CM7 also have this issue - as I'm seriously considering switching back.
Thanks.

250+ views and not one response? Boy do I feel lonely now.
So, seeing as how nobody can offer any help on my actual problems - can someone give me a clue to how I go about decompiling a ROM to check the code out myself please?

simon211175 said:
250+ views and not one response? Boy do I feel lonely now.
So, seeing as how nobody can offer any help on my actual problems - can someone give me a clue to how I go about decompiling a ROM to check the code out myself please?
Click to expand...
Click to collapse
Try to update to 1.9.23

Will that work? I've tried all of them up to that, but every time had to downgrade due to the problems. I got fed up of installing a ROM only to have to uninstall it five minutes later.

simon211175 said:
Will that work? I've tried all of them up to that, but every time had to downgrade due to the problems. I got fed up of installing a ROM only to have to uninstall it five minutes later.
Click to expand...
Click to collapse
I think it's a bug in MIUI itself. If you check the app on market, there's a lot on Market who says so.

that's what I thought - I've an ignored thread in the bug forum on miuiandroid, hence my last question about decompiling the ROM so I can investigate myself.

[Q] HTC HD2 | Phone Apk Hanging and Buzzing Issue

Firstly, I have been searching this forum for about 2 hours. I have found a few threads with the same issues, but they are either not relevant or I have tried the solutions within the threads and they have not worked. Also, the threads I have found are a few months old. I have also searched the ROM thread seen below.
ROM: [06 Nov 2011][MAG/cLK] NexusHD2-Gingerbread V3.2a (GWK74)(Android 2.3.7)[tytung_r13]
Device: HTC HD2
ROM Installation Method: MAGLDR 1.13
SPL: 2.08.HSPL
When I accept an incoming call, the phone application hangs and after about 10 seconds I get a force close notification. Sometimes this is accompanied with a buzzing sound from my speaker. In some instances I have to remove the battery to restart the phone as it totally freezes.
This happened on Android 2.3.5 (of the ROM linked above) so I upgraded to 2.3.7 (of the ROM linked above) to see if it would fix the issue. It has not. I also wiped the phone and reinstalled the ROM, and again it hasn't fixed the issue.
Also, I do not have Skype installed so it's definetely not that.
I would have posted in the ROM thread but it wouldn't let me.
Any suggestions?
Many thanks in advance. I can provide additional information should it be required.

Benetration said:
Firstly, I have been searching this forum for about 2 hours. I have found a few threads with the same issues, but they are either not relevant or I have tried the solutions within the threads and they have not worked. Also, the threads I have found are a few months old. I have also searched the ROM thread seen below.
ROM: [06 Nov 2011][MAG/cLK] NexusHD2-Gingerbread V3.2a (GWK74)(Android 2.3.7)[tytung_r13]
Device: HTC HD2
ROM Installation Method: MAGLDR 1.13
SPL: 2.08.HSPL
When I accept an incoming call, the phone application hangs and after about 10 seconds I get a force close notification. Sometimes this is accompanied with a buzzing sound from my speaker. In some instances I have to remove the battery to restart the phone as it totally freezes.
This happened on Android 2.3.5 (of the ROM linked above) so I upgraded to 2.3.7 (of the ROM linked above) to see if it would fix the issue. It has not. I also wiped the phone and reinstalled the ROM, and again it hasn't fixed the issue.
Also, I do not have Skype installed so it's definetely not that.
I would have posted in the ROM thread but it wouldn't let me.
Any suggestions?
Many thanks in advance. I can provide additional information should it be required.
Click to expand...
Click to collapse
this isnt something about your phone so try another rom or tell the developers.

linkin_p said:
this isnt something about your phone so try another rom or tell the developers.
Click to expand...
Click to collapse
thanks a lot, i have same issue...maybe i'll try another ROM

buzzing HD2
Sometimes it happens on my HD2 on diferent rooms: NexusHD2 3.2, NexusHD2 ICS 1.1, MIUI 1.12.30, MIUI 2.2.17. It is not often. Any sollution?

It's same here! I am starting to think that the problem is with my phone! I tryed meny different ROM and settings...it always the same!
It doing it 2-3 times per day.
How to fix it ?

same problem
I'm using CM9 (v2.8) android 4.0.4 and facing the same problem. I tried many ROMs but can't fix the problem. Also tried some solution on this 4rum but no help until now.
I'm going to throw my HD2.

Same here
I have the same issues with different rom using nand or nativeSD.
1 on 2 receiving call, the phone freezes with a buzzing sound. I must to take the battery out to restart the phone.

same problem
I have the same problem with my HD2!
The phone freezes after I receive an incoming call with a buzzing sound/no sound. Sometimes it shows the error message of com.android.phone process, in other cases I need to remove the battery and restart the phone.
I have tried different kind and version of ROM(for e.g. NexusHD2, MIUI, TouchWizMod v3.0) but the freezing issue is still not solved.
As far as I checked the freezing is not related to any kind of installed software.
If anybody has a solution to this problem please share with me/us. I really do not want to get rid of my HD2.
Thanks in advance.
------------------------------------------------------------------------------------------------------------------------------------------------------------
I have found the solution. The reason why the phone did not work is the Viber application. I uninstalled it a moth ago and thence everything works well. I use the WeChat app instead of Viber and my phone works like a charm.
By the way, a member of the Viber team has commented on this forum that their application does not support any kind of custom ROM currently.

Im facing the same problem,its killing me, its been worst recently ! I cant answer any call on my HD2
this problem happend first time on android 4+ roms,
I tried diffrent roms after that, but still not fixed, anyone can help us to find a solution?!
-----
anyone using CLk has this problem?!
Im using Magldr

Im having the same problem here. Found no sulition currently. ROM - tytung NexusHD2 2.5

The phone freezes after I receive an incoming call with a buzzing sound/no sound. Sometimes it shows the error message of com.android.phone process, in other cases I need to remove the battery and restart the phone.
Click to expand...
Click to collapse
hmm same here, tried some different ROMS - SD (froyo) and NANDs (2 gingerbreads, now ICS), tried these on both of my HD2s, also changed RADIO from 2.15.50.14 to 2.08.50.05 - nothing helps.
sometimes when im getting a call (usually it happens twice a week, some weeks more often, some less), i press the button and the phone/app freezes, sometimes with a buzzing sound.
after that, system doesnt respond normally, on GB sometimes it autorebooted....
also tried without viber AND tried directly after reinstalling the different ROMS with no contacts, original ringtones - also happens there sometimes!
i dont think that could be a hardware problem, because both of my hd2 phones act the same way.....
any solution since that time?

At the moment I have latest Jelly Bean by cotulla, with Cyanogenmod, and when I make a call, the screen is black (turned off) even though I don't have it close to my head and sensor is not covered. When I abort the call, it doesn't respond and stays dark with button panel highlighted for several seconds, and only after I press power button for several times it awakens. The same happens for incoming calls. The phone is not usable as phone with such things happening... That's frustrating.
So, let me sum up what people (and I) have had on the subject:
1. Various Android ROMs were tried and issue is always present.
2. In my case, stock Windows 6.5 has a very similar issue - incoming calls are even ignored! At least I had the described problem after I decided to have an "old" but working phone and reverted to the stock ROM instead of Android. Alas, the phone was still having glitches when answering.
3. We don't know exactly how many HD2 are affected by the issue but it looks like more than 1% which is pretty much to be a serious issue.
I might assume we faced an intermittent hardware issue, that does not always reveal itself, and can only be reproduced after a certain "failure". I think it's hardware dependent because my phone was working fine but suddenly ceased to do that.
I'm very sceptical about fixing this issue for me or other users. It's an obsolete phone and any mass hardware issues that is not reported by manufacturer (btw, could this be checked out?) will scarcely be considered. The whole thing makes me think we just have to switch to our phones are gaming/browsing accessories, since it just doesn't work and the issue is apparently non-trivial to be examined. I would be though glad to provide any information and logs... but who cares? Even cotulla doesn't think HD2 is worth developing any more....

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

[Q&A] [ROM][4.4.4] OmniROM - Stingray/Stingray_CDMA - bigPart

Q&A for [ROM][4.4.4] OmniROM - Stingray/Stingray_CDMA - bigPart
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][4.4.4] OmniROM - Stingray/Stingray_CDMA - bigPart. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

no sound, no auto-rotate
I am fairly new to Rooting and updating my Xoom to the newest Kitkat system. I am having 2 issues as of right now. The sound has never worked no matter what the settings say, and initially the auto-rotate was functioning and suddenly it stopped.
I have checked all options/setting and see nothing that should explain either of these 2 issues. I also didnt add any new apps in the time from initial update to the auto-rotate not working so if anyone has any suggestions or ideas, it would be greatly appreciated.
Again I am fairly new to all this, so the simpler or more detailed the potential solution the more likely I will understand it.
Thanks.

No sound on Omni 4.4 cmda version
I love the rom, only problem is I have no sound on the cmda version. I read the comments and saw people suggest install the top rom version over the bottom and then reflashing gapps. Should have sound. When I do this tablet boots but keeps giving me error "Unfortunately, the process com.android.phone has stopped" I say ok but it keeps coming up and wont let me get any further. Any suggestions?

volume issue
Anyone know how to fix the no sound issue in omni rom 4.4.4 stingray cdma? I cant get any sound at all. Help would be appreciated.

Took a couple go's but now up and running 4.4.2!
Thank you!
First time I've moved from the standard stock implementation, never even rooted the device before, but a couple attempts and following your instructions I managed to install BigPart, Flash omni-4.4.2-201XXXXX-everest-HOMEMADE_XXXX.zip, gapps-xxxx.zip & UPDATE-SuperSU-v1.86.zip.
I was about to give up on the Xoom and buy something newer, Tab S or something, but this appears to have put new life back into the old Xoom!
Followed the instructions above, but could not get it to clear Dalvik, failed every time. In the end I bit the bullet and formatted the internal drive, then flashed again - worked like a charm - figured since I was going to pass it over for a new one or this was going to work I had little to lose. As it happens I now seem to have it back & working well.
Now have bunch of apps back installed and trying them all out, so far most appear to be fine; though Google maps crashes whenever I zoom in too far.... less than a country level, I don't mean excessively far - thoughts?

Blackdogn3 said:
Now have bunch of apps back installed and trying them all out, so far most appear to be fine; though Google maps crashes whenever I zoom in too far.... less than a country level, I don't mean excessively far - thoughts?
Click to expand...
Click to collapse
Google Maps v9+ has problems on the Xoom with all the different custom ROMS (Omni, CWM, EOS, etc). You need to downgrade to Maps v8.4.1 to get it to work.

slow1234 said:
Google Maps v9+ has problems on the Xoom with all the different custom ROMS (Omni, CWM, EOS, etc). You need to downgrade to Maps v8.4.1 to get it to work.
Click to expand...
Click to collapse
Thanks as said a newbie! Downgraded and working fine - thanks for quick reply

Blackdogn3 said:
Thanks as said a newbie! Downgraded and working fine - thanks for quick reply
Click to expand...
Click to collapse
It has also been noted that 9.2.0 is rolling out and that it works on the Xoom. I updated yesterday and did a quick check - it does appear to work fine!

No Sound
After I flashed "[ROM][4.4.4] OmniROM - Stingray/Stingray_CDMA - bigPart." onto my Verizon Motorola Xoom 4G Tablet,
I have no sound at all and also the auto-rotate feature does not work (stays locked in portrait mode until reboot).
A number of other forum members have posted the same problem. Can we get a solution from someone on the forum?

have all but twrp v 2.6.3 big part
I have every thing I need except big part v2.6.3, none of the links I've found work? Does it have to be v2.6..3. ? There seem to be updated versions?

No 3g or 1x fallback
Install this today, everything went ok, execpt i could not get verizon 3g or 1x service. 4g works fine, when i have coverage. SBF back to stock again i guess.

e:unable to mount '/cache
The process for flashing the xoom (stingray model) seems somewhat straightforward. Yet I can't seem to get a working flash from the effort. Two problems:
1) during the "wipe this and that" stage while running in recovery, I get "FAILED" for each of the requisite areas to wipe, along with other messages such as that in the title. while i find a handful of other posts within this forum from folks experiencing the same problem, i find nothing in response with useful suggestions to fix what's apparently broken;
2) the tablet boots up to the OMNI splash-screen, and that's it.
I've repeated the steps at the head of this thread umpteen-zillion times. But the result is the same after each attempt. Either some critical step (or two) is/are missing from the initial (and horribly written) description, or I have the most stubborn tablet built.
i haven't bricked the thing... i can access it via adb, and i can get into recovery with no issues. what i can't seem to do is:
1) find a TWRP download using the links provided that doesn't trip quarantine due to virus detection; or,
2) find a coherent set of instructions that correctly describe the logical flow of the process of flashing a ROM on a Xoom.
Suggestions?

CDMA Voice and data programming
Hi,
Thanks for your effort and excellent work but I need some help, The main thing i want to try, is to get back my CDMA signal because since i tried the stock rom 4.1.2 i was not able to get any Data working there, my xoom is a just CDMA with no sim or LTE upgrade and i already tried 2 basebands on it the one with the last version of the stock room and the one that gets installed with the IMML update but no luck, if by any chance you have the first baseband it would be great i guess its something like 2.00.
Another question that I have is related to BP tools or programming the Cdma xoom, every time I try to start in bp tools I was not able to see the utility, just today i tried to connect to my PC and its not able to connect to CDMA Workshop or QPST, is there a way to do that? i need to activate something? any idea would be great!
And would be great if you have any MZ600 SBF where has included the first baseband 2.00 'cause probably it will help me to recover my 3g data (it's the only thing i didn't find and try).
Thanks!!!

is this have a default calling future like any mobile?

Thank You to OmniRom for xoom devolopers (all of you)
I just wanted to post a thank you to all of the developers of the omnirom for xoom. I was able to install it tonight, with a couple soft brick scares, but it is up and ruining. I love my xoom and am very appreciative.
Thanks....Steve

Xoom OnmiROM freezes
I've got a similar problem to the problem outlined in this post. My son also has seen it on his Xoom.
When it becomes unresponsive (either on the dock or not), the only way I can recover is to hold the volume up and the power button until the tablet reboots. To me, it appears it goes into a deep sleep that the power button alone can't wake it up from.
There seems to be no set time period that the tablet has to be up before it hangs. Sometimes I can set it down for an hour and other times it's still responsive the next day.

semi-anonymous said:
I've got a similar problem to the problem outlined in this post. My son also has seen it on his Xoom.
When it becomes unresponsive (either on the dock or not), the only way I can recover is to hold the volume up and the power button until the tablet reboots. To me, it appears it goes into a deep sleep that the power button alone can't wake it up from.
There seems to be no set time period that the tablet has to be up before it hangs. Sometimes I can set it down for an hour and other times it's still responsive the next day.
Click to expand...
Click to collapse
It's not real common for this to happen, but this same issue does occasionally happen on the CyanogenMod 11 Rom also. Other than this, and the workarounds to do a few other things in Android 4.4.4, the Xoom has been a real God send that is just amazing.

Non-Functioning Sensors post-flash w/Omni Stingray
Finished flashing XOOM 4G with (in order listed):
Xoom-Universal-Root
R.A.H._TWRPv2.6.3
omni-4.4.4-20141130-1816+0100-stingray_cdma-HOMEMADE
pa_gapps-modular-pico-4.4.4-20150215-signed
UPDATE-SuperSU-v2.45
After I noticed that the auto-rotate didn't work, I downloaded "My Android Sensors" from the Play Store. It shows the NO sensor is working. What gives..?

Looking for file EOS-Stingray-imm76l-radios-update.zip
Hi all,
Can someone help with the file ?
EOS-Stingray-imm76l-radios-update.zip
Thank you

The Rom works great.
I installed it month ago and it is working fine.
Batterylife is perfect and all things are working.
Thanks