[FIXED] Compass not working in GingerBread rom's - Desire General

Hello,
I have been trying out some GB roms lately and during the testing i saw that the compass was not showing north anymore.
If i turn the phone a little, the compass is swaying somewhere between NE and NW, but it never points north.
So i went back to FroYo roms, but now i have it there also.
I have been reading several messages fro different GB roms that people are having the same problem.
I also used the recommended radio's for the GB roms.
Since my AuraxTSense (FroYo) rom now also has this problem, it looks like a radio problem.
Can someone confirm this problem and tell me the solution or tell me the radio that is working?
Eric
Edit: See my post on page 2. There is a snq kernel fix for this problem.

Well, i have been testing some further.
Radios (old or new) make no difference.
Froyo rom (Aurax 8.4) and recalibrating the compass the old way, did make it work again.
Installing a new rom (GingerBread that is) and everything was wrong again. The radio version did not make any difference.
So i'm going back to Aurax and hope that i can recalibrate it again to let it work.
For other's with this problem:
Try the old way of calibrating the compass.
Make at least 2 figures 8, but do it slowly. It should take at least 2 seconds for every 8 you make.
Then turn the phone around 360 degrees along the length axe of the phone, also at least 2 times and 2 seconds per turn
Then turn 360 degrees along the sides axe (width), also at least 2 times and 2 seconds per turn.
If this did not work, repeat the last 2 ways of turning (length and width axe) but do it faster and about 6 to 8 times per direction.
This worked for me (and i hope it will work again in a few minutes).
Eric

Looks like North is up and South is down. The compass is now a "bubble" app.

MrXimi said:
Looks like North is up and South is down. The compass is now a "bubble" app.
Click to expand...
Click to collapse
I read a few days back that some Chinese Rom's had fixed it (HiAPK or something like that), but i just read that they also still have this problem.
So i will have to wait untill this is really fixed, because i need the compass for finding directions etc.

it seems to be a general gingerbread problem, other devices are affected too:
http://www.youtube.com/watch?v=l-9lehX8u2U
http://www.google.pn/support/forum/p/Google Mobile/thread?tid=07d4eaf9686b664e&hl=en

It is a general Ginger problem..we can nothing do about it but...waiting for fix

I opened a bug report on android's bug tracker, I encourage everyone who has this issue to confirm it so it will be fixed.
http://code.google.com/p/android/issues/detail?id=16741

I added my comments also.
Sent from my HTC Desire using XDA App

supposedly this fixes the problem on GbB as well but I havent tried it yet and don't feel much like flashing a GB rom and having to go back again to froyo if ot doesnt work:
http://forum.xda-developers.com/attachment.php?attachmentid=425776&d=1287930092

godutch said:
supposedly this fixes the problem on GbB as well but I havent tried it yet and don't feel much like flashing a GB rom and having to go back again to froyo if ot doesnt work:
http://forum.xda-developers.com/attachment.php?attachmentid=425776&d=1287930092
Click to expand...
Click to collapse
In the RCmix S thread there was somebody who had tried it.
In GB most of the files are not found.
The fix is for Froyo and not GB.
The guy (i think) reported that it did not work at all.
We will have to wait for some other solution.

godutch said:
I opened a bug report on android's bug tracker, I encourage everyone who has this issue to confirm it so it will be fixed.
http://code.google.com/p/android/issues/detail?id=16741
Click to expand...
Click to collapse
Confirmed

godutch said:
i opened a bug report on android's bug tracker, i encourage everyone who has this issue to confirm it so it will be fixed.
confirmed... Thnx
Click to expand...
Click to collapse

Compass fixed with new kernel
Since yesterday there is a fix for the Compass problem in the GB rom's
It is a new kernel from snq and works for (at least) most GB rom's and probably all GB rom's.
I have not had time to try it, but in most rom threads there are people who have tried it and it works!!!!!
The fix can be found here:
http://forum.xda-developers.com/showthread.php?t=1039004
If you want the flashable version, you can find it on the line with this text (on the previous page link):
download: zImage-v05 (flashable v04-to-v05 kernel image update package here)
Click to expand...
Click to collapse
or click on the link below:
http://api.viglink.com/api/click?format=go&drKey=1359&loc=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D1039004&v=1&libid=1306265553578&out=http%3A%2F%2Fdl.dropbox.com%2Fu%2F13432479%2Fmsm-2.6.35-bravo-GB%2Fg308ba26%2Fv04_to_v05-img-upd-flash.zip&ref=http%3A%2F%2Fforum.xda-developers.com%2Fforumdisplay.php%3Ff%3D628%26order%3Ddesc%26page%3D2&title=%5BKERNEL%5D%5BGB%2FSENSE%5D%202.6.35.10%20%5Bv05%5D%20%7C%20OC1152%20%7C%20LZMA%20%7C%20COMPASS%20%7C%20fixes%20%2Baddtl%20modules%20-%20xda-developers&txt=here
Have fun with it. I will when i have time to flash it

Confirmed working btw, got it in my ROM and it's fine

Yeah, works for me too. Using latest leedroid.

sorry. wrong post.
~renzs

Working on Nexus S
Hello,
is this fix working on Nexus S, too?

So, is this fix going to be incorporated into the official Acer releases (prob not)?
I guess we have to root and flash after market roms to fix their fubars...

Related

Black Shadow doesn't work well!

Hi guys,
My friends and me tried Black Shahow( black 4.0) today. It really got big memory as previous black version, free ROM 53M and RAM 30.4M, noticed that TOTAL RAM showing near 50M instead of 48M. The HTC home looks quite ok but for the weather panel the cities are limited for selection. THE BIGGEST BUG IS that sometime it CAN'T START PROPERLY and ALWAYS HANG during the re-starting period. You may need to reset it for several time just to start the phone.
Long time expectation but still encountered major bug.
Hope JJ can solve these bugs.
Perhaps this would be better off in the official thread? There was no need to start a new one.
Anyway, just FYI:
the original one was ok but jj added a file to fix HSDPA - this cuased a comflict with the current version of the ROM.
Apparently, if you disabled HSDPA things are better.
That's a workaround until jj releases a fixed ROM a bit later on.
try turn to landscape will be better but still need wait for new one..
most issues has been already resolved on www.4winmobile.com . if you need help, go to jasjamming forum and ask there. it was his request, and he did not answering question on two places. bye.
randomelements said:
Anyway, just FYI:
the original one was ok but jj added a file to fix HSDPA - this cuased a comflict with the current version of the ROM.
Apparently, if you disabled HSDPA things are better.
That's a workaround until jj releases a fixed ROM a bit later on.
Click to expand...
Click to collapse
Thanks your guy. I think it will be better to wait for new rom..
Anyone still keep the "First release version"?
My X01HT cannot wake up after slept each time...
I cant wait...
rom has been updated
Should this be a seperate thread here or just put it with the black shadow thread?
wu_ybao said:
Hi guys,
My friends and me tried Black Shahow( black 4.0) today. It really got big memory as previous black version, free ROM 53M and RAM 30.4M, noticed that TOTAL RAM showing near 50M instead of 48M. The HTC home looks quite ok but for the weather panel the cities are limited for selection. THE BIGGEST BUG IS that sometime it CAN'T START PROPERLY and ALWAYS HANG during the re-starting period. You may need to reset it for several time just to start the phone.
Long time expectation but still encountered major bug.
Hope JJ can solve these bugs.
Click to expand...
Click to collapse
No. For you maybe, but on my 8525 it's fast as hell and haven't had ANY problems or this "hang" problem either. The ROM is awesome!
I've run the rom also...I'm having no problems either. I experienced a hang during the install but after that I've been smooth and I'm HSDPA.
randomelements said:
Anyway, just FYI:
the original one was ok but jj added a file to fix HSDPA - this cuased a comflict with the current version of the ROM.
Apparently, if you disabled HSDPA things are better.
That's a workaround until jj releases a fixed ROM a bit later on.
Click to expand...
Click to collapse
I tried it but it still doesn't work, previously i installed official wm5.0 rom / qtek 2.11.255.2. It works quite well and stable. Do anyone have idea how to fix the bug?
Could someone please start a new thread Entitled: 'Black Shadow Works Great'
And then another one: 'Black Shadow Works So-So.'
Infact, everytime someone wants to say something, just start a New Thread.
berdinkerdickle said:
Could someone please start a new thread Entitled: 'Black Shadow Works Great'
And then another one: 'Black Shadow Works So-So.'
Infact, everytime someone wants to say something, just start a New Thread.
Click to expand...
Click to collapse
Seriously, there is a Hermes fans chatting room. In the chatting room, it is complainted as well that they got same experience as me. There is one similarity that we performed complete flash using Qtek 2.11.255.2 before updating to Black Shadow (4.0). I am thinking if there are conflictions between Black Shadow and Qtek latest WM5.0 ROM. However, we don't experience such bugs using Black Diamond which i regarded it as more stable one and faster than Shadow and some other cooked roms. Unfortunately, i can't access 4winmobile.com and can't comment this to JJ.
Should JJ read this may he give us a solution.
Anyhow, thanks for his great works and best regards.
For anyone seeing this thread now - there is an updated rom called shadow.rar already posted on wmblack.info and it fixes the problems from this morning.
wu_ybao said:
Seriously, there is a Hermes fans chatting room. In the chatting room, it is complainted as well that they got same experience as me. There is one similarity that we performed complete flash using Qtek 2.11.255.2 before updating to Black Shadow (4.0). I am thinking if there are conflictions between Black Shadow and Qtek latest WM5.0 ROM. However, we don't experience such bugs using Black Diamond which i regarded it as more stable one and faster than Shadow and some other cooked roms. Unfortunately, i can't access 4winmobile.com and can't comment this to JJ.
Should JJ read this may he give us a solution.
Anyhow, thanks for his great works and best regards.
Click to expand...
Click to collapse
your best bet then would be to post at 4winmobile than here as that is where he supports it.
berdinkerdickle said:
Could someone please start a new thread Entitled: 'Black Shadow Works Great'
And then another one: 'Black Shadow Works So-So.'
Infact, everytime someone wants to say something, just start a New Thread.
Click to expand...
Click to collapse
I was gonna make a new thread to discuss the making of new threads.
unwired4 said:
For anyone seeing this thread now - there is an updated rom called shadow.rar already posted on wmblack.info and it fixes the problems from this morning.
Click to expand...
Click to collapse
Hi, i just downloaded and tried the shadow.rar. After flashed it is still the same, can't start properly. Is it possible because of Radio? Someone with radio 1.38 told me his phone working well. By the way, i installed CE-star.
wu_ybao said:
Hi, i just downloaded and tried the shadow.rar. After flashed it is still the same, can't start properly. Is it possible because of Radio? Someone with radio 1.38 told me his phone working well. By the way, i installed CE-star.
Click to expand...
Click to collapse
ey, works great for me with 1.38 right now...so seems your issues aren't related to Radio version.
Try without CE-star (perhaps not compatible), and post results.
I find it thoroughly ammusing! all these posts dissing the rom creator and booing if the f**k up the install or the rom isn't perfect! when will you guys realise that we are in the thick of beta land! everything is a gamble! you don't put your head in the ovan just because someone else did and got away with it!
i'm pretty new to this rom business and only tried a few. I *****ed once but then came to my stark realisation. IT'S ALWAYS A GAMBLE! read the notes that come with the rom!
these guys are clued up enough to work at M$ (or Apple. imagine mobile OSX on a tytn!).
I think you guys need to chill and take it as it comes! that's the deal!
that's my 2 pence worth anyway!
I think some members of this forum just need to get laid.

[DEV] ION 1.6 (Donut)

Disclaimer: For devs only. Updating to it will wipe your device. I am not responsible of any damage of any sort or data loss or anything.
Google Ion 1.6 for HTC Hero.
This project aims at getting the stock Google Ion Rom to run on HTC Hero. No Rosie or any HTC apps will be ever added to that rom. Once fully functional it could be used as a base for cookers.
Current release: Lox-ION-1.0b3 (logcat)
What works:
- place, receive calls
- wifi
- Market
- GPRS
What does not do far
- bluetooth (logcat seems it is relative to libc.so - Uncompatible with current kernel ?)
- trackball
- compass & accelerometer (with akmd > logcat - with ak8973 > logcat )
- GPS
- camera
Note: devs please test hack and share if you fix anything or have any idea
Great! I hope the rest will be fixed soon!
I second that!
Great to hear it.
are you working on the hardware that doesn't work? and whats the progress.
you forgot to mention that the camera doesnt work aswell
Just flashed it, gonna see what I can get working(if anything).
I'd like to try it - but can you go back by using Nandroid - or reflashing Modaco's ROM ( I'm on 2.3 )
J-Zeus said:
I'd like to try it - but can you go back by using Nandroid - or reflashing Modaco's ROM ( I'm on 2.3 )
Click to expand...
Click to collapse
yes you can
I dont know how gecka feels but could we try and keep this thread informative
Just did a bit of snooping around and the GPS does work, you sure you checked it right? I did a bit of tinkering but none of it was related to the GPS at all. Trackball I'm still not sure about, the keylayouts have the same keycodes but still doesn't seem to want to work. Accelerometer just needs the permission to be granted to execute, except I'm not to sure how to do that cause I'm a bit new to linux. As for the bluetooth, don't get me started, its giving me a headache lol xD
hey i m using this rom and its working beautiful...man nice job and the trackball blinks when a phone is ringing ....but doesnt blind at the time of reminders....but still great job...
What about headphone detection? I know with the other Ion ROMs, when you plugged in headphones, it went unnoticed unless you downloaded an app to manually switch the audio over.
For devs only!
Hi guys,
Please, consider the [DEV] in the subject: this thread is for devs only.
If you don't give any fix, just follow the thread by subscribing to it and don't polute it! Thanks.
For now this build is buggy, you'll certainly find more and more bugs, witch I don't care for now as I want main functionality to work first (bluetooth, gps etc...)
robertosandros said:
Just did a bit of snooping around and the GPS does work, you sure you checked it right?
Click to expand...
Click to collapse
Please read carrefully before posting. GPS in in the "not working" list....
robertosandros said:
Accelerometer just needs the permission to be granted to execute
Click to expand...
Click to collapse
Right! Wrong permissions on witch file ???
Good work gecka,
I'm downloading to have a lookie and install now, see if I can have a go at the trackball.
Can I ask a question though, whats actually involved in fixing these issues?? Is it blind luck playing with config settings and that, or are you getting debug output?
kwiksand said:
Can I ask a question though, whats actually involved in fixing these issues?? Is it blind luck playing with config settings and that, or are you getting debug output?
Click to expand...
Click to collapse
Well, both in fact. The only debug output I get is from logcat and device logs.
Some issues might also be tight to kernel version.
But please there is a how to cook thread
gecka said:
Please read carrefully before posting. GPS in in the "not working" list....
Right! Wrong permissions on witch file ???
Click to expand...
Click to collapse
Thats what I'm saying, you've listed GPS as not working but its working for me.
Still trying to figure that part out
robertosandros said:
Thats what I'm saying, you've listed GPS as not working but its working for me.
Still trying to figure that part out
Click to expand...
Click to collapse
You sure the phone is not locating you based just on nearby cell towers?
gecka said:
Well, both in fact. The only debug output I get is from logcat and device logs.
Some issues might also be tight to kernel version.
But please there is a how to cook thread
Click to expand...
Click to collapse
i dount known if this works but maybe, behnaam haw gotten Accelerometer (Screen rotation) Fixed!
http://forum.xda-developers.com/showthread.php?t=563772
haw u triad hes files? maybe works and maybe u using different kernel ver
Market Apps
Hey all.
We've got a problem with the Donut Market over in the Vogue forums. In Donut, when we load up the Market, there are only 20-30 apps available. Going back to Cupcake builds, the problem persists. However, logging in with a fresh Gmail account gets rid of the problem (in Cupcake.)
So far, my guess as to the cause of this is that Google's server have taken note of any "pirates" accessing the as-of-yet unreleased Donut market, and locked them out. However, I don't see any complaints along those lines here.
So, my question to all of you is, while you say the Donut Market is working, do you still seem to have access to all the applications you did in Cupcake?
craig0r said:
Hey all.
We've got a problem with the Donut Market over in the Vogue forums. In Donut, when we load up the Market, there are only 20-30 apps available. Going back to Cupcake builds, the problem persists. However, logging in with a fresh Gmail account gets rid of the problem (in Cupcake.)
So far, my guess as to the cause of this is that Google's server have taken note of any "pirates" accessing the as-of-yet unreleased Donut market, and locked them out. However, I don't see any complaints along those lines here.
So, my question to all of you is, while you say the Donut Market is working, do you still seem to have access to all the applications you did in Cupcake?
Click to expand...
Click to collapse
whats your build.prop?

Unable to speak with incoming calls/make outgoing calls

I've been having this issue since the begining of my use with XAndroid 2.2 froyo...
When an incoming call comes in the caller is unable to hear my speak...and at times I am unable to place out going calls
How do I fix it?
Sent from my MSM using XDA App
You're using a very old kernel aren't you...
Update it please. GlemSom's site (the autobuild service) is unfortunately behind, but there's a couple of testing kernels floating around if you're brave.
With that said, I believe the "newest" on GlemSom's site has this bug fixed... AFAIK it was fixed quite a while ago!
or press incall your volume switch one time down then one time up,... i figured this out when i testing that old kernel
You guys may give this thread a shot: http://forum.xda-developers.com/showthread.php?t=893207
arrrghhh said:
You're using a very old kernel aren't you...
Update it please. GlemSom's site (the autobuild service) is unfortunately behind, but there's a couple of testing kernels floating around if you're brave.
With that said, I believe the "newest" on GlemSom's site has this bug fixed... AFAIK it was fixed quite a while ago!
Click to expand...
Click to collapse
Any chance you could post a link to the page you're referring to? I just installed the latest blazin cab off of the project android site last night and I'm having this same issue constantly. Any help appreciated as I love android, but can't do much without this fix.
Autobuild
It's in the FAQ, and on the first page of the thread where you probably went to the download link from...
Try these Kernal and modules http://forum.xda-developers.com/showthread.php?t=869992
Has anyone tried the newer kernals a GSM phone? I have had a lot of difficulty with this problem in the Froyo builds however Eclair works good on my Tilt 2 GSM.
jfarm03s said:
Has anyone tried the newer kernals a GSM phone? I have had a lot of difficulty with this problem in the Froyo builds however Eclair works good on my Tilt 2 GSM.
Click to expand...
Click to collapse
You're mixing terms here... the kernel is different from Eclair/Froyo - those are system images, the kernel is a completely separate piece. In theory you can run these kernels on Eclair no problemo...
Heck if Eclair works for ya, use it! Pretty sure this same problem would exist in that system with these new kernels...
But perhaps not - maybe you guys are all running into that system_server bug that's causing call issues..? Not sure.
Oh, and just an FYI... the majority of the developers have GSM devices
emt2rescue said:
I've been having this issue since the begining of my use with XAndroid 2.2 froyo...
When an incoming call comes in the caller is unable to hear my speak...and at times I am unable to place out going calls
How do I fix it?
Sent from my MSM using XDA App
Click to expand...
Click to collapse
try using froyo X, calling and texting works 100% on my rhod-100 for me, also on some devices the camera works..
http://forum.xda-developers.com/showthread.php?t=904918

Camera working normaly on rhod-100?

i have tried some builds now, kernels etc. but i can't seem to get it to work, so my question is: is there someone here with an rhod-100 who got the camera to work. (with working i mean, are you able to make pictures without the camera crashing or freezing after 4-5 secs after u started the app >.<)
the newest 10/1 kernel made no difference and yes i tried the latest frx03 version (also some prev. versions) froyo x also did not worked for me. what should i do?
I can't get it working too....
Rhod100_de - Photos: yes - without crash hm - i think its related to autoexposure or whitebalance - as long as the image keeps somewhat static the app (Vignette from latest FroyoX in my case) works, if i change the image the screen gets distorted and the app or os crashes
I can make pictures in 1 out of 10 Android runs. But than it crashes after making 1-4 pics. So it works a little bit. Force Closes, freezes, crashes etc. are normal as for now on the rhod100 and it seems that there must be some debugging progress . But i think that will come along at some point! . I think it has to do with the stolen gpios that are used by the Keyboard (was it that or another module?) and are making more trouble on the rhod100's then the other rhod models.
Hope this will be fixed
same problem here... hope they'll find a way to fix it as soon as possible...
Geko90 said:
same problem here... hope they'll find a way to fix it as soon as possible...
Click to expand...
Click to collapse
Glad to see you're so committed to helping...
So Lets get it on. How can we/i/somebody help to get this working on rhod100 like it runs on the oder rhodiums?
Bieka said:
So Lets get it on. How can we/i/somebody help to get this working on rhod100 like it runs on the oder rhodiums?
Click to expand...
Click to collapse
Logs, as always. However, I don't think the RHOD100 camera is any worse off than the other RHOD's - my cam is far from perfect, I get FC's and the like as well.
The code is still very experimental - but the more logs that viruscrazy gets, the better - that's for sure.
As for the RHOD100 issues, those seem to all center around the panel - which hopefully WisTilt2 will resolve soon (haven't seen him in a week or so, but he said he'd be back around Sunday...)
Thanks ,
i thought camera is working better on all other rhodiums? All i read in the test thread (ok i didn't read EVERY Post ) was working, working, working. Only rhod100's had problems posted there i thougt. Good to know that it is that different . I will see if i can send him some logs. What you say about the hopefully soon solved panel problems sounds great.
cheers

[Q] ICS BCM 0.3.2 - GPS Troubles - Runkeeper app

Hi,
I'm currently running dk_zero-cool's ICS BCM-Rom for Desire - which seems very stable and usable to me. I love being abke to run ICS on my old Desire.
I'm having trouble with the runkeeper app though and was hoping somebody can help me out here: For some reason, the app (which works fine under the most recent GingerVillain Rom) stops using the GPS to track my runs after about 1.85 miles/ 18, 19 minutes. I've had this happen three times in a row, so I don't think it's a coincidence (I was using 0.2.5, 0.2.6 and 0.3.2 versions of the ROM, resp.). The app still reports "good" GPS quality, it simply stops tracking.
I've been trying to use the "FasterFix" tool to stop this from happening, but without success.
I have not tried if this problems persists with a different running app. I will do this, but I'd really rather not switch apps.
Any ideas? Runkeeper seems to work under ICS in general (at least, I can't find any reports of problems).
Thanks for your help!
Or, if nobody knows anything, could somebody maybe post my question in the dev-thread, please? I still haven't got my 10 posts ...
saxelfur said:
Or, if nobody knows anything, could somebody maybe post my question in the dev-thread, please? I still haven't got my 10 posts ...
Click to expand...
Click to collapse
Or you could PM me
Try THIS. If that fixes it, I can add it to the ROM later.

Categories

Resources