Develop Bugs

[Q] MIUI ROMs - Problem with touchscreen randomly becoming unresponsive and rebooting

Hi All,
Been having a problem with the touchscreen randomly becoming unresponsive or the phone rebooting on its own ever since when I'm (trying) to run MIUI ROMs.
By "random" I mean that it sometimes occurs while typing, switching home screens, opening an app, or even just when the phone's idle.
Not experiencing any unexpected FCs throughout the MIUI ROMs that I've tried however... so at least that's a good thing?
I don't experience any of these problems at all when running a stock Sense ROM, so I'm hoping it's not the same rebooting problem described in another thread that requires sending it in for repairs as that would be very troublesome.
The phone's a HKCSL Desire that was rooted using unRevoked. The problems occur even when I don't install any apps onto the phone and when the phone's just idle with the screen off (for randomly rebooting).
Any suggestions would be greatly appreciated =) and I hope I'm not just SOL for MIUI ROMs since no one else seems to really be having these problems.
---
List of things I've tried:
1. Full wipe with Dalvik & cache before flashing a ROM (many, many times)
2. Updating to 32.48.00.32U_5.11.05.14 radio and downgrading to the suggested 32.44.00.32U_5.09.05.30_2 (Thought it might've been caused by WiFi connection as I always have it on... but doesn't seem like it)
3. Using different versions of Clockworkmod (2.5.0.7, 2.5.0.1, 2.5.0.1 modified by MIUI.cn)
4. Repartitioning/formatting SDCard before/after flashing a new ROM
5. RUU-ing the phone and redoing everything from scratch
6. Using an untranslated base MIUI-Desire ROM
7. "Upgrading" the ROM by flashing on top of the 10.15 build
Versions of MIUI ROMs I've tried:
Pretty much all the releases of 10.15 and 10.22. Currently fiddling around with eevek's stock 10.29 and mobiousdigital et al.'s 10.29 builds.

Hopeful bump =)

Reverting to a 3.30.651.3 based ROM

I want to preface this by apologizing if this has been covered, but I was unable to find anything with a search.
Every single 3.70 based ROM results in wakelock issues within 24-48 hours. I have tried everything, including flashing the stock rooted rom and no matter what, my phone stops sleeping after a day or so. I fully wipe, flash the rom, and I don't download a single app until the wakelock kicks in, at which point I grab spare parts and get no useful information.
I am currently alternating between CM7 and CM6 because AOSP roms work fine...they just aren't quite as solid as I would like them to be at this point. GPS bugs (I've tried the fixes), no HDMI (I've heard about the beta apps and I'll try those soon), no 4G (I realize this has been added to the nightlies for CM7, but the GPS issues are a deal breaker for now) and slow file transfers between my PC and my phone when using CM7 also kill the rom for me.
I figured I would simply flash the stock rooted 3.30.651.3 so that I could have a fully functional phone without wakelock issues if the need arose. But whenever I try to flash after a full wipe (including dalvik cache), I get stuck on the white HTC EVO screen. All 3.70 roms and AOSP roms flash fine so there must be something I'm missing...do I have to downgrade my radio or something? Any help would be greatly appreciated. And once again, I'm sorry for the post if this has been covered.

Yes the radio has to be downgraded first. I'm not sure which radio you need but you should check out one of Viruses rom threads since his roms are mostly 3.30 based.

[Q] CyanogenMod 7.0.0-RC2 (HTC Vision)

Had great success with CyanogenMod 7 RC1 and the #12 nightly (from 3/2/2011) on my G2.
Just wrapped up a quick flash to RC-2, but quickly started seeing weirdness, namely a continuous reboot to the CyanogenMod 7 bootup animation (blue skating android). Has anyone else ran into this on RC2 on the G2?
For now, restoring my nandroid backup from the #12 nightly which seemed pretty solid.
Also, fwiw, any US T-mobile users running into GPS issues (not locking) on the newest radio (26.06.02.27), I can confirm downgrading the radio back to 26.03.02.26 fixed this problem in my scenario.

Yes, same behavior. No idea about the radio and GPS. Just got my G2 today

I had the same issue when I went from RC1 to RC2, it kept rebooting so I just turned it off and it rebooted normal and has been working good ever since, maybe I just got lucky, idk.
_________________________________
Sent from my CM7 T-Mobile G2 using XDA app

If you're having bootloops try to do a reflash of the zip and reboot.
Many GPS issues have been fixed in the latest couple nightlies. For many people flashing the new radio doesn't work.
I've had GPS issues for a while on the stock T-mo radio, and it works fine now with the latest nightlies.
For detailed posts and info on the GPS, go read the nightly forum, there's 100000 posts on it.

moneybagsxp said:
Also, fwiw, any US T-mobile users running into GPS issues (not locking) on the newest radio (26.06.02.27), I can confirm downgrading the radio back to 26.03.02.26 fixed this problem in my scenario.
Click to expand...
Click to collapse
Also can go other way. Fixed my GPS No Lock problem in CM7-RC1 going from 26.03.02.26 to 26.06.02.27
Perhaps it doesn't matter what radio you use, it just needs the radio to be flashed??? (YMMV, I'm still newb-ish)

[Q] Problem installing non SENSE ROM

Hi all
I've had me desire for almost a year, during which I had may ROM's - with and without SENSE.
About a month ago, something went haywire with my phone and it would only connect to Edge and not HSDPA. I formatted the sd-card, wiped everything and installed a SENSE ROM - everything went back to normal.
2 weeks ago I used alpharev to move from 0.75 s-on to 0.93 s-off. Still with a sense ROM.
Now, whenever I try to install a non SENSE ROM, I get com.android.phone FC. I see that the airplane mode is going berserk and that I think I glimpse that I can only connect to WCDMA networks (not GSM) which may explain the problem.
On any SENSE ROM, I don't have this issue. I tried different boot tables, CM7, Oxygen, MIUI - none of them work and all of them with the same message. The only ROMS which now work on my machine are SENSE (doesn't matter which version).
Any idea what's up or how I can fix it? To remind you, I was able to install non-sense ROMs in the past.
Thanks!!!

nirrub said:
Hi all
I've had me desire for almost a year, during which I had may ROM's - with and without SENSE.
About a month ago, something went haywire with my phone and it would only connect to Edge and not HSDPA. I formatted the sd-card, wiped everything and installed a SENSE ROM - everything went back to normal.
2 weeks ago I used alpharev to move from 0.75 s-on to 0.93 s-off. Still with a sense ROM.
Now, whenever I try to install a non SENSE ROM, I get com.android.phone FC. I see that the airplane mode is going berserk and that I think I glimpse that I can only connect to WCDMA networks (not GSM) which may explain the problem.
On any SENSE ROM, I don't have this issue. I tried different boot tables, CM7, Oxygen, MIUI - none of them work and all of them with the same message. The only ROMS which now work on my machine are SENSE (doesn't matter which version).
Any idea what's up or how I can fix it? To remind you, I was able to install non-sense ROMs in the past.
Thanks!!!
Click to expand...
Click to collapse
Would it be worth updating your radio and possibly RIL? I note the problems you mention above relate to connectivity so perhaps a new radio might help?
I know that certain roms come with the RIL packaged, and that this can cause problems if it conflicts with the radio version.
There is a good thread on radio here:
http://forum.xda-developers.com/showthread.php?t=687464
and on RIL here:
http://forum.xda-developers.com/showthread.php?t=902752

Yeh most likely the radio. Nottoo keen ok RIL's because when I flashes a RIL it made my text and call connection die, so not too keen on them and yes, I did get the right RIL.
Sent from RCMixS

Another GPS Problem

Hey guys,
Don't shoot me, I've already done the research and still can't seem to find an answer. Regardless of ROM I can't get GPS to find any satellite's, fresh root, SR4.2, Synergy RC2, CM7 nightly, MIUI, Virtuous. I unrooted to see if it was a possible hardware issue, which it isn't as an unrooted phone gives me fast locks onto whatever sat is near. GPS Status shows nothing in the sky even after a A-GPS reset and download, although I know there's always at least 3 that are visible. I've tried clearing cache for any gps based app, tried running fresh rom installs instead of backups all with no luck. Any ideas guys?
Currently I'm running:
ROM - SR 4.2
Baseband - 2.15.00.07.28
Kernel - Stock Kernel from SR4.2 (2.6.32.17-g9a2fc16 htc-kernel[email protected] #1
PRL - 52341
HW Version - 0002
CWM - 3.0.0.7
HBoot - 0.92.0000
Radio - 2.15.00.07.28

Looks like I'm stuck going back to stock unrooted until I can get this fixed.

I'm having the exact same problem. Tried multiple roms and doing A-GPS resets. I'm not sure what else to try, anyone have any other ideas? May have to unroot for now so I can use GPS while traveling.

nate23 said:
I'm having the exact same problem. Tried multiple roms and doing A-GPS resets. I'm not sure what else to try, anyone have any other ideas? May have to unroot for now so I can use GPS while traveling.
Click to expand...
Click to collapse
If you are in NY or other new 4g area it may be related to a problem others are having with AGPS upate VZW pushed. No ROM seems to work.

yep, it was an issue with New York. We drove to Boston on Sunday, I tried clearing my A-GPS in western Massachusetts and suddenly got a lock on GPS! Google maps then worked perfectly all the way to Boston.

Well there is no way I'm giving up root or custom roms, Google or Verizon need a better solution than that.

I actually fixed mine and never left NY, I dropped to stock then went back to SR 4.3 and haven't had a problem since, and I've flashed 3.0 roms and SR 4.3 multiple times with no problem. So if you're still having a problem unroot then reroot. It should fix it.