Sorry for my poor English. With mattc Leo + Froyo w/Sense RC1.3a on my hd2, the compass works, but I found there has 90 degrees offset. Could someone can fix this problem ?
gdc1 said:
Sorry for my poor English. With mattc Leo + Froyo w/Sense RC1.3a on my hd2, the compass works, but I found there has 90 degrees offset. Could someone can fix this problem ?
Click to expand...
Click to collapse
Is a known bug. Something with the automatic calibration...
any news for this??
gdc1 said:
Sorry for my poor English. With mattc Leo + Froyo w/Sense RC1.3a on my hd2, the compass works, but I found there has 90 degrees offset. Could someone can fix this problem ?
Click to expand...
Click to collapse
you need to calibrate your compass , move your hand like that about 10 times and it is done http://www.youtube.com/watch?v=BoxpSK7i1vM
After calibration, compass still has 90 degree offset.
I think maybe the METAL DETECOR's author could help for this.
bump
Bump...still an issue, and no activity for a few weeks now...
TX-Nick said:
Bump...still an issue, and no activity for a few weeks now...
Click to expand...
Click to collapse
i agree, this is a fairly annoying issue as navigation/maps/streetview/ and skymap all rely on this to function.
Anyone figured this out yet???
Still no fix for the compass? I know this is minor overall but it would be nice....lol Mine is still exactly 90 degrees off i.e. saying west when pointing due north. Any hep on this would be HUGELY appreciated!
jaws197 said:
Still no fix for the compass? I know this is minor overall but it would be nice....lol Mine is still exactly 90 degrees off i.e. saying west when pointing due north. Any hep on this would be HUGELY appreciated!
Click to expand...
Click to collapse
It's now fixed in some builds, like this one:
http://forum.xda-developers.com/showthread.php?t=796889
Latest kernels fix compass.
Use hastarin 7.2 kernel from http://forum.xda-developers.com/showthread.php?t=787588
same prob for me guys...
nkos719 said:
same prob for me guys...
Click to expand...
Click to collapse
The answer was just 1 post before yours... you missed it somehow.
----
Latest kernels fix compass.
Use hastarin 7.2 kernel from http://forum.xda-developers.com/showthread.php?t=787588
From changelog:
rajko - Working compass!! (yes Google Sky Maps works)
Its because the magnetic poles are shifting. The end of the world is at hand...
dubie76 said:
Its because the magnetic poles are shifting. The end of the world is at hand...
Click to expand...
Click to collapse
Lol......
Anyways...
1. This is not a developer thread.
2. The question has been answered. See post #10 of THIS thread.
Moving this out of Development forum...
dude, u didn't need to calibrate at all, It is you screen rotation orentation.
Related
fixed the camera on the 3D gallery. rotation bug is also fixed on 2.1v3+ based roms.
Download Archive-signed.apk from FileFactory.com
Andrizoid said:
fixed the camera on the 3D gallery. rotation bug is also fixed on 2.1v3+ based roms.
Download Archive-signed.apk from FileFactory.com
Click to expand...
Click to collapse
Nice work; but I thought hoban fixed all of it and it was part of his tainted rom. I could be wrong, but I haven't had any issues using it.
havent used it yet, saw that the zen exp rom was using the one with the broken camera button so i figured id post it here for anyone to grab.
quick question...
Andrizoid said:
havent used it yet, saw that the zen exp rom was using the one with the broken camera button so i figured id post it here for anyone to grab.
Click to expand...
Click to collapse
Will this work with all roms? Sprint, Eris, Zen etc?
2.1 roms
and apparently it was the 2.1.3 build that got the rotation bug worked out. so any rom based off the 2.1.3 or ota build will work perfectly with it
yeah you just had to edit the hudlayer1 smali
thanks this works great!
capychimp said:
yeah you just had to edit the hudlayer1 smali
Click to expand...
Click to collapse
right. i think it was because the camera icon was trying to call up nexus hardware and since we obviously dont have it, it was causing the FC. i just linked in the correct intent code
Andrizoid said:
right. i think it was because the camera icon was trying to call up nexus hardware and since we obviously dont have it, it was causing the FC. i just linked in the correct intent code
Click to expand...
Click to collapse
Rotation bug? Is that when you rotate it and it splits into like 12 tiny screens, all displaying what should be displayed as one large screen? That bug is present with your fixed Gallery3D apk and ZenEXP-Eris.
-mak
.mak said:
Rotation bug? Is that when you rotate it and it splits into like 12 tiny screens, all displaying what should be displayed as one large screen? That bug is present with your fixed Gallery3D apk and ZenEXP-Eris.
-mak
Click to expand...
Click to collapse
hmm, well for ze EXP since its a port im not sure, i do know that for roms based on eris leak 2.1.3 and up there is no rotation bug. no idea where the fix happened though.
Andrizoid said:
hmm, well for ze EXP since its a port im not sure, i do know that for roms based on eris leak 2.1.3 and up there is no rotation but. no idea where the fix happened though.
Click to expand...
Click to collapse
No worries, thanks either way
.mak said:
No worries, thanks either way
Click to expand...
Click to collapse
the camera button is still fixed though
feel free to use it for that if you want.
Andrizoid said:
the camera button is still fixed though
feel free to use it for that if you want.
Click to expand...
Click to collapse
I would but people will complain a lot more about the rotation issue.. At least they have the option to get it here and install it if they want it.
-mak
.mak said:
I would but people will complain a lot more about the rotation issue.. At least they have the option to get it here and install it if they want it.
-mak
Click to expand...
Click to collapse
too bad i dont actually know what im doing with all this, otherwise im sure i could find what in v3 made it work. maybe someone a little more wise in the way of the droid could figure out what causes the fix so it can be added to the ported roms.
and im sure you already know this, but a work around for the rotation bug is just to switch orientation before you open the app. the only time there is an issue is when the orientation is changed within the app itself
I've tried a lot of android builds whilst the development has been going on and found that Bangster's 1.4 coupled with Michy's R11 was the best for me with regard to screen sensitivity and keyboard accuracy.
I recently had a dabble with m-deejay's next-gen builds Desire HD/Z etc (which are excellent by the way, credit to him), and found that I was getting a lot of screen bounce, missed button presses and a very frustating keyboard experience (Hastarin R7.1). Pressing and holding the delete key for example would result in keypresses bouncing all over the place, sometimes several keys removed from the delete key. I tried a plain Froyo Sense build and found the same thing, although not quite as bad.
So, I decided to try the bare kernel from Michyprima's R11 (AXI, Desire, OC) on my current Froyo Desire build just to see if it was down to the kernal 100%. Instant bounce removal... keyboard is accurate and now when I press & hold on the home screen, I don't get the screen wobbling from side to side as the software thinks that I'm moving my finger around rapidly.
To recap; it seems like I was getting more bounce with Hastarin's R7.1 than any other, but certainly Michy's R11 (Desire based) is making my phone usable again. It really was bad before.
More messing required methinks... I may re-load the Desire Z build on to my SD card and try R11 to see what it's like. One thing I remember is whilst trying m-deejay's Desire HD 3.1 (which had an Evo kernel IIRC), keyboard bounce was almost non-existant. It wasn't until I changed to D-HD 3.3 that the keyboard became a pain to use (Hastarin R7.1).
Hastarin if you read this, please note this is by no means a dig, I have the greatest respect for all the guys posting builds here, these are just my obvservations.
As with all things Android/HD2 related, YMMV. Your thoughts are welcome.
---------------------------------------------------------------------
---------------------------------------------------------------------
Edit: I've taken a couple of quick videos of m-deejay's brand new 3.4 Desire HD build showing this phenomenon (kernal is huanyu's #21). Replacing the zImage with Michy's R11 virtually eliminates it.
Video 1 - homescreen
Video 2 - keyboard
Could this be Windows ROM related? Might flash another WinMo ROM to see if it's any different.
Edit 2 Sent my HD2 back to HTC today, hopefully for TS replacement... see relevant post here.
Edit 3 Received my HD2 back from HTC's repair department. Problem fixed. No more bouncing Relevant post here.
No-one else with similar experiences?
Me too!
previously was using M-deejay's froyo sense 2.2 and the keyboard was a great improvement from my old stock HD2 Windows keyboard, which was oversensitive and jumps alot, making typing a hassle. I did not have any problems with the froyo sense 2.2 keyboard, it was accurate and sufficiently responsive, and even have my essential chinese input.
However, after the 2.4 version was released, i updated it, and noted that the browser's bookmark crashes. So i though, why not give EVO Sense 1.6 a try?
Btw, i did not realise any problems with the 2.4 keyboard, so it's probably as good as the 2.2 version.
Then i ran EVO sense 1.6, and i feel that the keyboard is different. Firstly it's the additional arrow buttons below, which is useful, and more like the original HD2's keyboard. Then it also has chinese input.
BUT i experience alot of the "bouncing" problems, if not more than my original HD2 windows rom. tried calibrating a few times, and deleting the calibration, but it doesn't help.
i want to emphasize again i am very grateful to all the developers like M-deejay, Hastarin, for developing all these builds that are effectively working. this is likewise, just my observation.
Anyone else? I can't believe it's just us two!
Videos added to 1st post.
I tried to replicate your problem (m-deejay's Desire HD 3.4) but I coulnd't. I also thinkg that the keyboarad its not as accurate as some of the builds but its not that bad as yours.
I'm sorry to say but the lag with the keyboard kinda looks funny
My keyboard isn't very accurate too. Sometimes it just takes the wrong key. I mean when I press the backslash it takes "m" or something although i was pressing backslash. This was on Hastarin 4.1.
But it really seems to be kernel related. With the r11 my keyboard is okay.
I don't think is caused by the WM ROM, but which one do you use?
have the same prob!
yep...and I get phantom touches also.
jaka.erc said:
I tried to replicate your problem (m-deejay's Desire HD 3.4) but I coulnd't. I also thinkg that the keyboarad its not as accurate as some of the builds but its not that bad as yours.
Click to expand...
Click to collapse
What WinMo ROM are you running?
JanssoN said:
I'm sorry to say but the lag with the keyboard kinda looks funny
My keyboard isn't very accurate too. Sometimes it just takes the wrong key. I mean when I press the backslash it takes "m" or something although i was pressing backslash. This was on Hastarin 4.1.
But it really seems to be kernel related. With the r11 my keyboard is okay.
I don't think is caused by the WM ROM, but which one do you use?
Click to expand...
Click to collapse
CleanEx DsE GTX 6.5.x
anoschka666 said:
have the same prob!
Click to expand...
Click to collapse
muzicman0 said:
yep...and I get phantom touches also.
Click to expand...
Click to collapse
Try changing your zImage to Michyprima's R11 and post your findings
Major_Sarcasm said:
No-one else with similar experiences?
Click to expand...
Click to collapse
OK ! very common HD2 touchscreen failure! ...ur touchscreen is defective ....there are many threads already on xda regarding this ...but could not be solved because this is a hardware problem ...this even happens in winmo ! here are the youtube videos having same problem
http://www.youtube.com/watch?v=DhhrA3u4rcI
http://www.youtube.com/watch?v=3rJJ1eyM9FM&feature=related
http://www.youtube.com/watch?v=QEHn9CaHFpk&feature=related
http://www.youtube.com/watch?v=hY60I9Z0RU0&feature=related
http://www.youtube.com/watch?v=TSvAlqw6HJw&feature=more_related
http://www.youtube.com/watch?v=6hIE_wV4djs&feature=more_related
and here is my thread about this in detail - http://forum.xda-developers.com/showthread.php?t=745255
so , the conclusion is ...u have to get ur screen replaced under warranty ....i had the same problem with my hd2 ...and i got so pissed ...so get ur screen changed and that is the only solution !
hope that helps -
cheers
coolbeer1990
Got it to but not in my homescreen. When I am typing with swype ... When I try to delete a word it will write 10 :X nice feature but its really anoying. But lets wait I thing dev know about it let wait for nand and the bother them with this. I heard It is a long way to nand
coolbeer1990 said:
so , the conclusion is ...u have to get ur screen replaced under warranty ....i had the same problem with my hd2 ...and i got so pissed ...so get ur screen changed and that is the only solution !
hope that helps -
cheers
coolbeer1990
Click to expand...
Click to collapse
Thanks for your reply. However, my screen isn't defective as I don't have this problem in Windows and using a different kernel fixes it.
major_sarcasm said:
thanks for your reply. However, my screen isn't defective as i don't have this problem in windows and using a different kernel fixes it.
Click to expand...
Click to collapse
that's great my friend
Well.. i have the same thing in hastarins latest kernel
I dont have this on DesireZ out the box.
I have MDeejay's latest Desire HD build and have this problem, how do I fix it? If I need to replace the Kernel how do I do it? What side effects will it have?
Thanks in advance
keyboard bounce also experienced by me when i am trying to type fast, using hastrin r7.1 as well, maybe is caused by the touchscreen delay?
have you tried keyboard calibration?
in the setting menu ..
it ask you to type that ..lazy brown fox jumps..
it helps me alot.. well some of it i guess
and also try the schrub bartome build. the keyboard is perfect-iphone like. im using this build for day use
I experience the same issue with the new kernel releases. But with hastarin #3 the touchscreen works normally.
Sent from my HTC Vision using XDA App
Here new Radio for LEO and LEO 1.5 from shipped HTC_WWE 3.14.405.2 ROM
http://www.multiupload.com/QP0IWGY42F
Enjoy!
All other radio versions (including this one) can be found in the Master Radio Thread
anyone tested on t8585 eu leo? is it any good?
tnx football for your always great uploads!
I tested everything is fine. But I don't have much info about battery consumption due to I got this rom few hours ago...
Thanks.
I just flash it on my HD2 and now i'm going to test it on Android.
what u fell about 2.15
i'm trying too right now
Yeah tell us how is it it if its better than 2.14 i will flash today.....
Thanks
Thx - ...i´ve flashed it, works fine! I´ll hope, the battery-consumption is lower than 2.12.xx and 2.14.xx...
HeinBloed5259 said:
Thx - ...i´ve flashed it, works fine! I´ll hope, the battery-consumption is lower than 2.12.xx and 2.14.xx...
Click to expand...
Click to collapse
Really how you tested it?
jirka607 said:
Really how you tested it?
Click to expand...
Click to collapse
he just said he hopes that it'll be better concerning the battery drain
Testing....
just flashed 2.14.50.04 about 2 minutes ago...
waiting for some feedback till i flash again.
jirka607 said:
Really how you tested it?
Click to expand...
Click to collapse
3G = no difference to 2.12.xx (no wonder, the transceiver is 100 mtr. away from my home, i´ll test it tomorrow ! ;-) )
GPS = 10 satellites found (but 8 with 2.12.xx)
-...my once sorrow is the battery-drain, was worse with 2.12.xx and 2.14.xx
Ah i didnt saw the hope so i hope it is better....
HeinBloed5259 said:
3G = no difference to 2.12.xx (no wonder, the transceiver is 100 mtr. away from my home, i´ll test it tomorrow ! ;-) )
GPS = 10 satellites found (but 8 with 2.12.xx)
-...my once sorrow is the battery-drain, was worse with 2.12.xx and 2.14.xx
Click to expand...
Click to collapse
youre saying that battery drain is not good with this radio ?
Laynee1 said:
youre saying that battery drain is not good with this radio ?
Click to expand...
Click to collapse
Hey guys learn to read!
He just said that he had just flashed!
Give the guy some time to breath!
BTW I am flashing right now...
WM6.5 Everything working as expected. Battery drain test will take at least a couple of days.
ANDROID Everything working as expected. Cristal clear sound in call, wifi etc working flawlessy.
(Froyostone 3.1)
I will keep it. I am confident on new radio upgrades...
JJKameR said:
WM6.5 Everything working as expected. Battery drain test will take at least a couple of days.
ANDROID Everything working as expected. Cristal clear sound in call, wifi etc working flawlessy.
(Froyostone 3.1)
I will keep it. I am confident on new radio upgrades...
Click to expand...
Click to collapse
please inform us as soon as possible about the battery drain, would be interesting, especially compared to 2.12.xx and 2.14.xx
JJKameR said:
ANDROID Everything working as expected. Cristal clear sound in call, wifi etc working flawlessy.
Click to expand...
Click to collapse
Well wifi worked but suddenly, after restarting is not working anymore. I think I have screwed up something on my android filesystem.
Here I posted full RUU http://forum.xda-developers.com/showthread.php?t=801312
I tested again with JP6 now and my results are very disappointing! Before with Eclair it was all much better!
JP6: almost impossible to get a fix and always inaccurate
JF3, JM5: fix in 15 seconds and very accurate!
JM7 was slightly worse then JM5 and JF3 in my experiences.
How the hell is that possible? I thought / read that JP6 / JPM is much better with GPS :S
FYI: We say "Worst"
And the title is biaised, you "tell" that the GPS is worst, and ask if we agree... you can only assume that the result will tend in that dirrection.
On the topic, well, since none of those release are "official", I can't realy judge on speculations and pre-release!
But then, I don't have massive issue running JH2... On a 6km run I got about 200m of "distortion", so it's only about 3% margin of error.
t1mman said:
FYI: We say "Worst"
And the title is biaised, you "tell" that the GPS is worst, and ask if we agree... you can only assume that the result will tend in that dirrection.
Click to expand...
Click to collapse
In the context OP is using it, it's actually just "worse"
Motjida said:
In the context OP is using it, it's actually just "worse"
Click to expand...
Click to collapse
http://wiki.answers.com/Q/Is_worser_a_word
My GPS seems better and locks on more or less straight away
I'm in the car now and it's magnificent for once! can't text much lol.
MY gps is more worse. please fix it
aarisaanig said:
MY gps is more worse. please fix it
Click to expand...
Click to collapse
And now a double infinitive..
I hate bad GranDma
Mine is the worstest.
Hey
I installed this rom yesterday, my applications are much smoother, but i have a huge problem, which makes almost every game unplayable. When i try to play the game with 2 fingers, it doesnt respond well. Is there any way to fix this?
Rucsok said:
Hey
I installed this rom yesterday, my applications are much smoother, but i have a huge problem, which makes almost every game unplayable. When i try to play the game with 2 fingers, it doesnt respond well. Is there any way to fix this?
Click to expand...
Click to collapse
That's not a problem with the ROM as much as it is a general problem with the HD2 unfortunately. It only supports 2 points on the screen, and I've found it does that terribly as well.
Nigeldg said:
That's not a problem with the ROM as much as it is a general problem with the HD2 unfortunately. It only supports 2 points on the screen, and I've found it does that terribly as well.
Click to expand...
Click to collapse
I dont think so, in my previous rom (Typhoon CM7) multitouch worked flawlessly in the games. After all these updates, how isnt it a priority to fix this?
Rucsok said:
I dont think so, in my previous rom (Typhoon CM7) multitouch worked flawlessly in the games. After all these updates, how isnt it a priority to fix this?
Click to expand...
Click to collapse
Because it's working for almost everyone, so it isn't really a 'known problem' as such. What version of the ROM are you on? If you're on 2.1 it'll be a bit shady, but multitouch works as well as it did on Typhoon for me on v2.2 (haven't got round to the 2.3 update yet).
Nigeldg said:
Because it's working for almost everyone, so it isn't really a 'known problem' as such. What version of the ROM are you on? If you're on 2.1 it'll be a bit shady, but multitouch works as well as it did on Typhoon for me on v2.2 (haven't got round to the 2.3 update yet).
Click to expand...
Click to collapse
2.2
I'll reinstall the rom (now the 2.3 version) hopefully this will fix the problem.
Rucsok said:
2.2
I'll reinstall the rom (now the 2.3 version) hopefully this will fix the problem.
Click to expand...
Click to collapse
Hmm, try going into the settings>developer options and enabling 'pointer location', then see if both the points are detected. Don't worry if the two points sometimes 'lock together', this is normal for the HD2's outdated screen
Nigeldg said:
Hmm, try going into the settings>developer options and enabling 'pointer location', then see if both the points are detected. Don't worry if the two points sometimes 'lock together', this is normal for the HD2's outdated screen
Click to expand...
Click to collapse
I tried this, i can certainly feel the "lock together"-effect. Is that supposed to be normal? If thats a HD2 related problem, how come i havent experienced this before?
Rucsok said:
I tried this, i can certainly feel the "lock together"-effect. Is that supposed to be normal? If thats a HD2 related problem, how come i havent experienced this before?
Click to expand...
Click to collapse
As far as I know that's a HD2 problem, yes. You probably have experienced it before, but haven't noticed it because you don't have the visual feedback to show you that it's happening. It doesn't have much of an effect during gaming (surprisingly)
omethek
it is a problem, because any game with a joystick is unplayable.
edit: besides the 'lock together', sometimes when the touch points are close to eachother, they are detected "inversed". is that normal too?
I agree that our device is outdated, but I've never experienced such issues.
I played multitouch games on WP7, Android GB & (Currently) ICS .. Even GTA 3, the movements are precise.
Not sure what you two are facing, but it's definitely not "too-old" related.
The only thing that the HD2 can't do is handling more than two finger points, other than that, everything seems to be fine for me.
There are lockups, but they are rare.
Rucsok said:
it is a problem, because any game with a joystick is unplayable.
Click to expand...
Click to collapse
Rucsok said:
edit: besides the 'lock together', sometimes when the touch points are close to eachother, they are detected "inversed". is that normal too?
Click to expand...
Click to collapse
I'm beginning to agree with Marvlesz here, these issues aren't that normal. I've never had the points becoming inversed and I can play games with onscreen 'joysticks' (i.e. GTA3) fine, so I think you might need to take a look at some of those threads with the digitizer issue and check if others are experiencing the same issues.