Database Users

GPS issue (Solution found but reason is unkown) Please read and post your knowlege

Hello everyone. I've beeing seying alot of people saying that before a ROM worked with a radio edition , wich GPS worked perfectly and later stoped working, and i decided to study the case in order to know, why is it working.
I've been testing diferent ROMs and Radios.
We've got the radio editions:
Radio_HTC_PVT_32A_6.35.10.18
Radio_HTC_PVT_32A_6.35.08.29
Radio_HTC_PVT_32A_6.35.07.29
And according to an article wich i read here on the forum, teoricly we can use any radio, and the phone wont brickitself.
So i've been using a radio 6.35.08.29, and tested on a ROM wich required the radio 6.35.10.18. As predicted nothing bad happened, worked perfectly . But when i tried the GPS it didnt work. Anyways i decided to test a ROM wich required a 6.35.07.29 radio. Happened the same thing. GPS didnt work.
I Flashed 6.35.07.29 radio on that rom. GPS worked without any problem. I changed radio again to 6.35.08.29 GPS didnt work again.
Once again i went back to my original ROM, and happened that my GPS didnt work, wich before have worked, like the situation most of us encounter here at the forum.
What can we conclude from this?
In my opinion, there are files from the radio wich when we make a backup or even install a new rom, wich wont complete the system instalation of the radio, and you'll have to reflash the radio edition compatible with the ROM you just instaled.
Another theory is that after installing an incompatible ROM, GPS is turned off automaticly .
Anyways, i would like to know your experience and your opinion, i'm sure here are people wich know more about this then i do
Thank you. Best regards everyone!

anyone?

This would be very interesting stuff if it could be proven correct.
Sent from my HTC Magic running Smoki using the XDA mobile application powered by Tapatalk

Thanks for the reply. i know. Also this would help to avoid bricks and unecessary procedures. The porpuse of this threat is to understand what makes this happen in orther to avoid, and make everything functional.

I have no idea whether this makes sense or not. I also don't agree that "Solution found" (as in the topic) - rom cooks usually don't state the required radio version beyond 6.35.whatever or the equivalent for old radio, I don't know about any of them being aware of such a (hypothetical) requirement.
My understanding was that the different 6.35 variants are regional editions, and that using the wrong one for your part of the world might make your cellular telephony and/or networking operate suboptimally. Not that I have seen any proof that this actually happens. I guess nobody knows whether the radio stores persistent state of any sort, but I suppose somebody familiar with the kernel source might know whether anything the kernel does depends on the radio version (or minor version). Otherwise the radio requirement would stem only from the origin of the RIL libs and libgps, right?
I don't know much about any of this, so the above is just guesswork. Hopefully someone more informed will contribute to this thread.

drbobb said:
I have no idea whether this makes sense or not. I also don't agree that "Solution found" (as in the topic) - rom cooks usually don't state the required radio version beyond 6.35.whatever or the equivalent for old radio, I don't know about any of them being aware of such a (hypothetical) requirement.
My understanding was that the different 6.35 variants are regional editions, and that using the wrong one for your part of the world might make your cellular telephony and/or networking operate suboptimally. Not that I have seen any proof that this actually happens. I guess nobody knows whether the radio stores persistent state of any sort, but I suppose somebody familiar with the kernel source might know whether anything the kernel does depends on the radio version (or minor version). Otherwise the radio requirement would stem only from the origin of the RIL libs and libgps, right?
I don't know much about any of this, so the above is just guesswork. Hopefully someone more informed will contribute to this thread.
Click to expand...
Click to collapse
I think you are right. Each version is about the region i didnt remember we had diferent GSM frequency around the globe.
what confuded me was that there was ROMS wich Devs said that in order to work we should have their Radio edition. Is this a real problem if we use other radio?

please I would request more cooperation on this post . Thank you!

The same thing happened to me today. I had tried a 2.1 ROM and returned to my 1,5 CursorSense and my GPS would not work. I found that reflashing the Radio cleared up the problem. There are several posts in the CursorSense thread that describe the problem and fix.

wjsturgis3 said:
The same thing happened to me today. I had tried a 2.1 ROM and returned to my 1,5 CursorSense and my GPS would not work. I found that reflashing the Radio cleared up the problem. There are several posts in the CursorSense thread that describe the problem and fix.
Click to expand...
Click to collapse
whats the fix provided? Could you please redirect me to that fix? Thank you

jgcaap said:
whats the fix provided? Could you please redirect me to that fix? Thank you
Click to expand...
Click to collapse
Do a search on the CursorSense ROM Thread for GPS:http://forum.xda-developers.com/showthread.php?t=592856

thanks i didnt know there was a button search for thread. Very helpfull, i've been searching i found no fix. But if there is i must find out to see if is related.
Just confirmed something, this patch is not related to the GPS fix. GPS wont find location unless you reflash the rom of the location wich the rom was made for. Wich respects again this teory. I would request if possible someone to assist in this ! thanks

anyone? Big please?

i request again more knowlege please

It worked for me!
I went to 2.1 roms, then switched back to Cursorsense and lost GPS, so I reflashed Radio_HTC_PVT_32A_6.35.10.18 and it works!

Mod. edit: not dev related, moved to general

so... if i understand... we must flash each of those versions to see witch works?
mine works but only after using gps status aplication to get a fix

Draken Korin said:
Mod. edit: not dev related, moved to general
Click to expand...
Click to collapse
How in the world is this not dev related???

Dont know ask the mods lol
Sent from my HTC Magic using Tapatalk

HD2 Android Camera not working

Hi, I am using energy latest wm rom with matt froyo sense. Recently, I notice my camera in android has stopped working. When i on camera, the screen is just blank. Cant take and see any pictures. However, when in WM, camera function works ? Anyone here has this issue before and any possible solutions ? Btw, I am using hastarin r8.5 kernel. thanks for ur advice !!!
edited : radio is 2.15

Did you read hastarin's warning and the readme.txt? There's an adivce how to get rid of this problem.

how can i fix the problem for the camera in my android hd2??? please provide steps

I got the same problem, can any one point to the warning and the readme?
Thanks

CM7 Final - missing bouncycastle library?

I have an app called thinkorswim that force closed and gave me an error
from stack trace:
java.lang.NoClassDefFoundError: org.bouncycastle.crypto.engines.rsaengine
This didn't happen before with enomther's ROM .. anyway I can find the fix for this?

Nevermind ... the developer said it's a known issue with Gingerbread. Sorry if I cause any confusion. Closing thread.

excuse if im wrong im working on a desire and advent vega little knowledge of nexus but whilst porting roms ive only seen bouncycastle.jar in honeycomb roms

This used to work in Android 2.2 .. it's a problem on TD Ameritrade/Thinkorswim and they acknoweldged the issue.

[Q] Problem with g sensor

Hi,
G sensor in my HD2 didin't work, I have a NAND ROM from AmeriCanAndroid AOSP HD2 GB2.3.5 CM7 | bk2sdext [KERNEL:ACA823].
I reading this topic, I try this metod
-*GSensor-Calibration tool: To use it
In terminal emulator type, su (return)
bma150_usr( lay phone flat on back and hit return )
exit(return), exit(return and close
Click to expand...
Click to collapse
But still is not working, I download from market app Buble for calibrating,- dosen't work.
Do you have any answers for fix it?
I checking sensor three SD rom, still not working, and this NAND rom, but in WM g sensor works great.
Brothers help me

I had that problem happen to me when i first released SuperCM(WP)7. It was a converted sd build from isaiah12345 and there was problems. Thats why i had to compile from scratch with my build cause certain builds are perfect in winmo because the build uses all the calibration from winmo but straight nand it has to be built differently. I would read the thread to see if anyone else complained about the same problem than see what the solution is. if not than try another CM 7 build. They have the nightly CM 7 and TYPHOONS CM 7 which are both good roms. I would recommend my builds but they have a slight bug when i compiled it. the usb wont mount unless you use multi mount lite or pro if you decide to support the developer and it mounts it. Hope that helps.

Unless the problem was fixed and I missed the info, we can't calibrate the g sensor in Android rom. It didn't work last time I tried.
You will need to reflash the rom again and don't touch the calibration routine. The sensor will use calibration file provided from within the rom.

Thanks for any answers. I flashed this NAND rom http://forum.xda-developers.com/showthread.php?t=769026
I don't touch calibration routine.
G sensor still not work, meybe my HD2 it's not compatibile with Android? I mean work G sensor.
Nobody can help in any way, I do not know what to do.
Wait for the rest of the answers.

You will get more and better answers when you ask in the right forum/thread
This is the DEV forum. Ask in the Q&A or in the ROM-thread.

Who help me?
Sent from my HTC HD2 using Tapatalk

Hd2 g sensor

Hi. I have a hd2. When I install windows mobile my accelerometer and gsensor works fine but, when I flash Android ROM, my accelerometer doesn't work. I try with task 29, reflash everything, I try calibration with bubble app. And nothing happens. Please I need help. Thanks.

I use AmericanAndroid (sd build, so I can swap back to WinMo if I want to use TomTom or iGo) and haven't ever had a problem with mine.
Have you tried various builds?

ramonalbertov said:
Hi. I have a hd2. When I install windows mobile my accelerometer and gsensor works fine but, when I flash Android ROM, my accelerometer doesn't work. I try with task 29, reflash everything, I try calibration with bubble app. And nothing happens. Please I need help. Thanks.
Click to expand...
Click to collapse
Some ROMs do not support accelerometer/have issues with it I think.
Try asking in your ROMs thread if it is not a known bug.
And try different roms, to eliminate the fact that it might be hardware, not OS issue.

g sensor
It is a problem with different hardware revisions. In simple therms there is no driver for your board. Thre are a lot of people out here(my self included) with the same problem and until someone, and by someone i mean some of the devs write the new driver we are stuck. I dont think it wil happen as they now write new stuff for the ICS and maybe then the bloody thing will work.

Try new kernal or rom. In my miui( version in my sig) its working. There are fixes for it. Read thread named compilation in hd2 forums.
send from my hd2 @ miui 1.12.2

Used a different firmware - the result is the same

Need to keep this and threds like this up in hope that someone notices our problems. My hd2 got repaired and the board changed and since then no g sensor. It is strange even taking a picture. It works fin with windows but i dont want freaking windows.