yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] Arg0t:
As I've tried many variations trying to get to the bottom of the issue.

I've ruled out:

Phone hardware: It works in other roms and older versions of CM7

Radio: Tried 3, same result in all versions.

Me: Egan has the same issue so I'm not being special.

Kernel: Doesn't work with Coutts

Only common factor between working and not working is CM7 builds over #39, something changed that only effects a very small % of phones.
[Desire Android Development] coutts99:
Works fine for me too, on every recent nightly. I use GPS daily.
[Desire Android Development] Tuborg68:
Never had any issues with GPS and CM7. Neither on nightlies nor RC1.
[Desire Android Development] Arg0t:
Well aware that many people have no issues at all.

So far only myself and Egan have mentioned an issue. Hoping kali or someone more knowledgeable than me could work out what changed.
[Desire Android Development] nachtschicht:
I'm on today's Nightly #15 and just checked GPS:

- Switched it on and Google Maps could locate me in seconds (down to 6m)

- Switched it off and on again, and Copilot instantly found 8 satellites and could fix my location in seconds, again.

So I think that build #15 is alright. My radio is 32.54.00.32U_5.14.05.17 (if that helps).
[Desire Android Development] yukkio:
Sometimes I had problems with gps but I've fixed it with gps status.

BR.
[Desire Android Development] kibbsnk:
i flashed 15 over 14 and now have no gps it worked fine on 14 yesterday
[Desire Android Development] ziggy1001:
If you look at the CM forums and other phone threads seems like a minority of people are having the same issue which all the usual "fixes" doesn't solve :(
[Desire Android Development] Egan:
There is definitely something wrong with CM7, for the following reasons:

- I have tried all the possible solutions mentioned. Same as Arg0t.

- No problem with any other ROM, only CM7 starting Build #40 / RC1.

- It appears people with CM7 on HTC Desire HD have the same problem since RC1, so this can not be a coincident, can it? http://xdaforums.com/showpost.php?p=11966906&postcount=2117

I do not understand why other people do not have this issue, but I know it is CM7 related and hope it will be addressed :).
[Desire Android Development] yukkio:
Try gps status It will download a agps data to help your gps to find satelites.

BR.
[Desire Android Development] andQlimax:
Hey coutts99, put a changelong.txt in ur mirror :P
[Desire Android Development] kibbsnk:
thanks but have tried this but get nothing no gps icon flashing to say its looking nothing even when the notification icon is on and the gps box is ticked in locations
[Desire Android Development] Egan:
So now Arg0t, kibbsnk and myself have this GPS issue. Anyone else having this (please dont reply just to say you dont have the issue)?
[Desire Android Development] kibbsnk:
i did a reboot the gps worked and found sats really quickly but when i turned off gps and switched it back on i was back to no icon in staus bar and no gps :confused:
[Desire Android Development] coutts99:
I did but forgot about it :)

Follow twitter ;)
[Desire Android Development] mastersjef:
you have radio: 32.44.00.32U_5.09.05.30_2? and another thing wich kernel are you using?

Furthermore check how much /system space you do have. Maybe issues with memory.

Ps,

Never had the GPS, Radio or GSM problems with all Oxygen builds, CM 7.x builds and Aurax Reflex (HD) builds with any random config.

Including all sorts off kernels and radio's.
[Desire Android Development] Arg0t:
Tried radios:

32.44.00.32U_5.09.05.30_2

32.49.00.32U_5.11.05.27

32.54.00.32U_5.14.05.17

All with same results.

Using CM7 rom kernel.

The issue occurs on a virgin install with only the Rom and Maps installed. So unless its something to do with cache it's not space.
[Desire Android Development] kibbsnk:
i too not had a problem til now

radio:32.54.0032u_5.14.05.17

kernel:2.6.37.2-cm-g8cdf03e android@giulio-desktop#9

mem:181mb avail 405mb total
[Desire Android Development] mastersjef:
That sucks! but you did wipe all the partitions except sdcard offcourse?
[Desire Android Development] kibbsnk:
yes off course
[Desire Android Development] mastersjef:
Another thing maybe it's stupid but i see that Egan and Argot has both CWM 3.0.0.5 try flash with CWM 2.1.5.x?
[Desire Android Development] kibbsnk:
in rom manager i get an error occurred while downloading your recovery with CWM

2.5.1.x? but worked on CWM 2.5.0.7

FYI i flashed my rom through recovery not through rom manager
[Desire Android Development] mastersjef:
Last option i could think of is download the Nighly #15 again and in the zip you go to /system folder and then you delete all folders,

except! the folder called Framework. After that go in recovery mode and flash the zipfile.
[Desire Android Development] kibbsnk:
do u not think it worth waiting for next nightly to see if that fixes the problem

did as you suggested just got the pink circle in middle of screen nothing happened thanks for your assistance will leave it alone and hope next nightly will fix the problem
[Desire Android Development] janvandusschoten:
GPS works for me, just had a few hickups while using it with Google Nav, had to switch GPS off and one again once to get it to work, the other times it had a new fix fast on his own.
[Desire Android Development] kibbsnk:
ive decided to try RC2 seems to have resolved the gps issues as everything working just fine
[Desire Android Development] Egan:
Didnt solve it for me. Also tried the things mastersjef mentioned. Still no GPS whatsoever.

EDIT:

Build #1 after the RC1 is also giving me a good working GPS. So what is different between build #39 and #40, and RC1 and build #1?

EDIT 2: Build #5 after RC1 also works. Lets try more...
[Desire Android Development] janvandusschoten:
Strange, we have the same radio version, Hboot etc. The only thing I do after I flash a new ROM is use Fasterfix and set it to "Nederland" , but that is just for a faster fix.

Do you modify your ROM before you flash it or do you just flash it like it is?
[Desire Android Development] Egan:
Just flash it like it is m8. Nothing special.
[Desire Android Development] janvandusschoten:
Just flashed the latest Nightly's this morning, just with the LatinIME.apk from Ginger Villian (for Dutch language, with 7-ZIP). No problems with GPS, it's constantly "on", and when I activate Google Navigate it pops on and stays on.

Did you check the MD5 before flashing and did you try to flash your radio again?
[Desire Android Development] Egan:
It has nothing to do with you, but I'm tired of answering such questions over and over again. I tried everything mentioned and I know pretty much what I'm doing :cool:.

So please take me for my word, when I say there is something wrong in some CM7 builds which cause GPS not to work anymore (on some devices).
[Desire Android Development] DomFel:
Don't know if you tried, but you might want to flash an official RUU, than root and S-OFF again. Usually it solves all the issues.
[Desire Android Development] Egan:
Thanks for the idea, but I'm not going to flash the RUU and doing my rooting, etc all over again. I doubt it will change anything, I can not see how this can change anything (correct me if i'm wrong), but only causing me lots of work for nothing.

It is not happening with other ROMs and older builds of CM7. So far I can tell you it happens at least with all CM7 builds after build #39 (before RC1) except for:

Before RC1

#39

After RC1

#1

#2

#3

#4

#5

#6

So at least after RC1 it goes bad from build #7. So what has changed since build #7?
[Desire Android Development] coolbits:
I get GPS driver crash too...

When gps turned on and reboot, it works ok and get a fix... if i turn gps of and then back on it will not work... it shows its on but not working... till next reboot.

If i leave it always on, no problem.

Checked ddms and its crashing every few seconds.

Flashed vorkkernel... and now i get this:

03-10 16:00:04.530: ERROR/GpsLocationProvider(161): set_position_mode failed in startNavigating()

03-10 16:00:46.910: WARN/GpsLocationProvider(161): Failed to enable location provider
[Desire Android Development] quertiy:
Problem

SO, because kaly apparently can't help me with this problem I decided to post it here. I'll post all the steps I think are relevant:

1. Two weeks ago, I wiped everything, formated everything, created a 1 GB ext3.

2. I installed RC1 and "Legacy App2SD Addon" that enables apps 2 sd, by default, and I used "/sd-ext/userinit.d/11data2sdext-binds enable" for data 2 sd.

3. I installed all my programs (200 or 250), settings, restored my sms calls callendar contacts etc etc.

4. After everything was completed and I didn't need anything else, I made a full nandroid backup.

5. For two weeks everything worked well, but a few days ago i decided to upgrade to RC2, so I did, but after installing I entered a bootloop.

6. So, i wiped everything, formated everything, and restored my GOOD and ONLY nandroid backup, but to my surprise, after restart i was in a bootloop. WTF!!!!!!!!! After a boot of 5 minutes, it enteres android for 3 seconds and then bootloops.

For 3 days I'm trying to find out what the heck is happening and how is that possible. The md5 of the backup is good, everything is apparently good. But I guess that's not quite right.

SO, what to do... what to do... I'm almost sure it has to do with this apps2sd, because when it boots for 3 seconds in android, i quickly unlock the device but everything force closes.

Here is my logcat (I stopped it 2 seconds after the bootloop happened): http://dl.dropbox.com/u/12632761/logcat.txt

Other info: I use clockworkmod 3.0.0.5.

If I don't solve this problem, everything on my phone is lost, sms, contacts, calendar, notes, programs, etc etc etc etc. So, please, help :)

Thanks.

ps.1: Things I tried:

- I tried installing legacy apps2sd again after restore, but the same thing happens

- I tried installing legacy apps2sd and enabling data2sd (/sd-ext/userinit.d/11data2sdext-binds enable) but the same bootloop and force closes happen
[Desire Android Development] ziggy1001:
@Egan

In one of the threads i saw about this problem it was stated as being "bad data on GPS chip" that was the cause which i think was the logic in flashing a different rom (not CM7) then resetting the GPS with Type ##gpsclrx# in dialer then ur msl

Sorry if you have already tried this but maybe a full wipe, factory reset, wipe everthing apart from sd card then install CM7 anew might work;) presumably if you nandroid the problem will remain
[Desire Android Development] Egan:
Thanks for thinking with me m8. I'll try that tonight, resetting the GPS with the dailer, which I havent tried yet. I however have tried a full wipe and factory reset. Erasing the sd-card I havent tried yet, but will try when everything else fails.
[Desire Android Development] ziggy1001:
You have the MSL code?
[Desire Android Development] Egan:
No and it says "Connection problem or invalid MMI code". Any ideas?

EDIT: I probably need to type my MSL right after the MMI code, right?

EDIT2: I didnt buy the phone through a carrier. I bought it without a contract. Still need MSL code?
[Desire Android Development] ziggy1001:
Yes i believe so

That's when you type ##gpsclrx# you get "Connection problem or invalid MMI code"

Does *#*#4636#*#* work for you?
[Desire Android Development] Egan:
Yes, that does work.

FYI: My phone is brand free. So I didnt buy it through a carrier. Do I still need the MSL code?
[Desire Android Development] ziggy1001:
Not sure never had to use the ##gpsclrx# command :o
[Desire Android Development] Egan:
Okay, but anyway ##gpsclrx# isnt working for me since I get that error. You get that error too when you enter it right? So this may just not work on the HTC Desire.
[Desire Android Development] Tuborg68:
#15 and still no search in my exchange inbox. Bummer!
[Desire Android Development] ziggy1001:
Not even sure how to type letters into dialer:o

Post i saw i think was talking about CDMA
[Desire Android Development] Egan:
Type it with the numbers representing the letters :).
[Desire Android Development] DomFel:
Whatever. By the way RUUs are not intended for users, but just for service labs.

Flashing an original RUU restore the phone to full working condition, and this has been covered many times in the forum, even for other HTC devices.

Using unrevoked to root, and Alpharev to get s-offed, will take 10 mins of your time, much less than the time spent here trying different procedures.. ;)

P.S.: Just noticed your radio in your sig... You might also want to use the latest official one, 32.49. Have a strange feeling that older radio with newer ROMs just don't go nice with each other..
[Desire Android Development] Egan:
I do not agree with you. Flashing a RUU will not do anything I can't do manually with ADB. Thanks anyway though.

I will stick with build #6 (after RC1) until this is resolved or someone comes along with true know-how of what can cause this issue.
[Desire Android Development] andQlimax:
Flast the latest radio, it worth a try if u have problem with the gps..Ur radio is very very old..come on..update it lol :D

Maybe after build 6 they updated some gps libs that are not compatible with ur radio or ur configuration..So your gps will never work untill u update it..Maybe there is nothing to fix
[Desire Android Development] Egan:
Already tried few weeks ago, no GPS. Went back to this one since it gives me better battery life.

As said many times, already I tried everything mentioned. Although I do appreciate you all take the time to help, I do not feel like repeating over and over again.

I'll try to find the solution by having a look at the commits between build #6 and #7.
[Desire Android Development] DomFel:
Kinda don't get what you're looking for then. You're using a radio that is not even compatible with most latest rom.

You are just refusing pretty much everything that is being suggested to you.

Issues with GPS have been covered tooo many times, it mainly depends by the manufacturing date of your phone, and components that have slightly changed in different hardware releases (PVT1, 2, etc..).

Don't ask more, just deep dive into the forum, you'll find all the answers you might need; but I'll tell you, they'll be pretty much the same posted here for you. ;)

HINT: Wanna solve that? Flash an official RUU (2.29 for example), root, s-off, keep 2.29 radio (32.49 is fine), flash clockwork 3.0.0.5, ALL wipes, flash CM7, and you'll be just fine.

HINT2: Don't flash RIL for any AOSP rom, like CM7! You might mess up GPS and GSM signal.
[Desire Android Development] RedSkyRoad:
Btw, when will the stock CM7 clock have access to all the ringtones that are shipped with it and 2) when will we be able to select Accuweather as a weather option?
[Desire Android Development] Egan:
DomFel,

I'm not refusing something when I actually tried it already or when I know that what you are suggesting won't resolve anything.

- Tell me what a RUU does more than a full wipe and flashing hboot, radio, rom and recover.

- Tell me which ROMs are not working with my radio, since I tried all Gingerbread (devnull, oxygen, Ginger Villain, CM7, etc) and only GPS on CM7 stopped working from build 7.

- Tell me why it is that AdamG advices to use my radio for Oxygen. Also others prefer my radio over all newer ones. Kali- even said you can use any radio with CM7.

PS. I didn't flash RIL.

PS2. I say it once more, to be clear, I tried all radios in AdamG thread and all give the GPS issue.
[Desire Android Development] mastersjef:
Have u tried RC2?
[Desire Android Development] mkolonko:
hey egan,

as i dont know if you know what a ruu is, i explain it for the record: when you flash a ruu (ROM Update Utility), you just revert your device to the original state. it is something whole different then a full wipe. in the process you loose naturally everything root/rom/hboot/recovery related.

so, here are some original htc desire ruu i actually have no idea witch one you should take with a 0.93 hboot so try it out. it will tell you if the update can be done or not.

so, after your desire is in original state, you still can deside if you want to root/flash cm on it again or leave it that way.

have fun!
[Desire Android Development] mastersjef:
First of all, CM 7 has not yet accompliced the Final stage so it's a test thread so for now deal with the rom.

Second, Accuweather is not A part of Google/Android so there are and is a weather bug elite in the market there will be no 3rd party apps in the Rom except modded ones what the Dev's think is a + for the Rom or if they like them themselves....
[Desire Android Development] RedSkyRoad:
Then why is there a "Weather Channel" logo next to the weather in the clock app? Im referring to accuweather as a source of weather data,not the full app...
[Desire Android Development] Egan:
Thats what I meant when I said: "Tell me what a RUU does more than a full wipe and flashing hboot, radio, rom and recover."

Flashing a RUU, as far as I know, is exactly that. A full wipe and a flash of the official hboot, radio, recovery and ROM. Thats why I asked him to tell me what it does more, cause if it doesnt do more than just that, flashing a RUU wont solve the GPS issue I am having when using CM7 from build #7.
[Desire Android Development] cyclon1978:
i can confirm the gps issue Egan reported.

I use CM Nigthlies every day (building myself, so really everyday :D) and didnt used gps since RC1.

Radio: 32.44.00.32U_5.09.05.30_2

(Fix was always < 1 minute)

I use GpsStatus to fetch sattelite data and normaly get instant at least one sattelite, at the moment i never get a sattelite.

I now changed to newest radio and newest build and will test next time outdoor...

greetings,

Andreas
[Desire Android Development] Egan:
Great to hear I'm not almost alone in this. I tried the latest radio with no luck. Hope you have better luck. Let me know m8 :).
[Desire Android Development] mkolonko:
Egan, are you 100% positiv the stock rom didn't have the problem?

but even when you are, that's what i would do in your situation (like nobody's providing a solution to your problem):

1) revert to stock

2) confirm everything is running as it should

3) root it, flash recovery -> check gps

4) flash cm7, boot to cm7 but don't connect to google -> check gps

6) reboot, connect to google -> check gps

as i read in your earlier posts, you had a error msg.

just imagine, there's more then 150k people using cm7 rc2. and as far as i know your the only one with actually an error msg.

the post form cyclon1978 is not quite the same case you have. he didn't mention anything bout an error.

cheers
[Desire Android Development] RedSkyRoad:
This whole GPS debacle is interesting...

I get a lock on 7 satellites INDOOR within 20 sec...

(I DID change my gps.conf to my country, though)...
[Desire Android Development] Egan:
I'm 100% sure the stock ROM doesnt have this problem. No other ROMs have this problem either. Only CM7 starting build #7.

That was a common error message which has nothing to do with this problem.

You type ##GPSCLRX# in your dailer and press call, you will get an error too.

It is exactly the same issue, as I said the error has nothing to do with it.

Why do so many people think they know it all, while in fact they know nothing. I can imagine developers (I'm a Software Engineer for living too) leave XDA because there is so much noise on the forums.

PS. All the help people try to give is truly appreciated, but do not take me for a fool or underestimate my knowledge.
[Desire Android Development] coolbits:
Works here too, but only until i turn off gps... after i turn it back on is no go, no satelites.

Try to turn gps off and back on.
[Desire Android Development] Egan:
The thing I havent tried, is flashing a sense rom, perform ##GPSCLRX# and flash back to CM7.

Users are discussing it over here: http://forum.cyanogenmod.com/topic/14453-cm7-discussion-of-nightlies/page__st__1140

It appears ##GPSCLRX# isnt working on CM7 but is on a sense rom. I'll try that tonight.
[Desire Android Development] mastersjef:
I don't think you are a fool i'm a ICT Projectmanager myself but when 98 % don't have the same problem then you know with your background that it's frustrating enough

to answer 1 problem with 4 pages and no solution....... You have already mentioned that within Nightly #5 there wasn't a problem stick with that!

If you know what i mean? And i advice that to all the 2% of the people with this problem test the future roms if it's working then problem solved but again stick with the working Rom it's a phone for crying out loud.

Gr,

MS
[Desire Android Development] Egan:
I know what you're saying, it is frustrating. We have customers who say a feature isnt working while for 98% of the customers it is working and we cant find the cause for that 2%, at least not at our end.

Since yesterday I am sticking with build #6 which is working and good for daily use. However every 2 days I check a new build and try again, since CM7 RC2 has some nice new features ;).

Thanks m8!
[Desire Android Development] bemymonkey:
If something is broken for you on the latest RC (not just nightly!) release, make sure you let the CyanogenMod team know! Post it as an issue on the bugtracker (http://code.google.com/p/cyanogenmod/issues/list).
[Desire Android Development] Egan:
I will do that, thanks!
[Desire Android Development] coolbits:
Already reported by someone.

http://code.google.com/p/cyanogenmo...on Model Network Owner Summary Stars Priority
[Desire Android Development] Egan:
With the only difference that I never have GPS working, but close enough. I'll star it then.
[Desire Android Development] ziggy1001:
Seems like some phones are worse than others

But definitely on the radar ;)

http://xdaforums.com/showpost.php?p=11943021&postcount=2699
[Desire Android Development] JCB_Digger:
But if you DO put issues on the bugtracker it's only meant for the Release Candidates, NOT the Nightlies.
[Desire Android Development] bemymonkey:
That's what I wrote.

Only report the bug if it's present on the latest RC, and not just some odd nightly.
[Desire Android Development] cyclon1978:
you can try to replace system/lib/hw/gps.goldfish.so with the one from an older nightly with working gps.

From my point of view worth a shot - but no time to try it this weekend.

(this solved similar problems on different devices)
[Desire Android Development] Egan:
Just tried it with no luck. I hope I can try the sense and ##GPSCLRX# fix tonight.
[Desire Android Development] df9517:
I can't get neither USB or WIFI tether to work.

Known issue?
[Desire Android Development] ziggy1001:
Which nightly are you on? works fine for me on RC2
[Desire Android Development] df9517:
I am on latest nightly. Strange!
[Desire Android Development] Sandertenty:
I'm on nightly #17. No GPS problems anymore... came from #15 with GPS problems
[Desire Android Development] Egan:
Just flashed build #17 coming from #15 and still no GPS. Will try the sense ##gpsclrx# fix later today.
[Desire Android Development] bemymonkey:
I just reproduced your GPS issue... it just won't turn on in GPS Status or Maps. will flash B17 as soon as I get home to see if it's fixed.
[Desire Android Development] Egan:
Tried the sense ##GPSCLRX# fix with no success. On both AOSP and Sense I get the error/bug described in this issue: http://code.google.com/p/android/issues/detail?id=2226

ps. Of course I had GPS on that Sense ROM (LeeDroid) :rolleyes:.
[Desire Android Development] devcager:
LEDs

Hey,

I came from LeeDroid ROM and I noticed one thing on my Desire. LeeDroid provided me in option to choose from several colors of LED for my notifications. There was green, orange, blue + pink and something like white/purple in combination of all LED colors. CM7 gives me green, orange, blue + red, cyan and magneta while the last three do not work. Is it just my issue or CM still can't work with that??

Thanks
[Desire Android Development] expl0de:
It's in CM settings/Interface/LED
[Desire Android Development] nachtschicht:
I only have red and green (and none) as available colors...?