Related
I'm sorry to report, but Orange will now be shipping out devices with an Orange ROM. No Google Earth, changed quick-app icons and who knows what other modifications... I couldn't find any... Well, there's a GPS Settings thing, but it only shows about Assisted GPS which I'm sure I saw in the other ROM.
Still comes with an 8GB Transcend memory card and nothing extra in the box. If you're getting one in the next few weeks, make sure the barcode at the top says GHTN. If it says OHTN, it's the Orange ROM.
google earth??
Why do orange ruin perfectly good phones? They also did it to S60 Nokia's which is why ive avoided orange for the last 6 years.
Orange are alright but their ROM-faffing is just an exercise in self-importance that is not appreciated.
so mess with the rom and terrible web browsing limits
I'm happy to report that I just received my orange HD (ordered the other day when they came back in stock on the web shop) and it's not got a messed up ROM (box has the GHTN code as described above). As far as I can tell there is no orange branding anywhere at all. Makes me think that the current batch might be with stock ROMs ... get your order in quick ???
Orange recieved 5000 new phones a week monday ago. about 3 days ago they were available for delivery. mine was one of them and its only orange branding is the rear cover. and TBH this in not an issue as i like the logo on the cover. the rom is standard with all the trimings....
Once again
Google Earth????
If you buy from CarPhoneWarehouse you will get unbranded and unlocked.
Even on an Orange contract.
I've no idea how long this will last though.
Ah yes, forgot about the little orange logo on the rear cover. So it's "no orange branding anywhere at all ... except for the logo", though I was actually thinking about the software rather than the hardware when I wrote that.
Info update
Don't worry about the hadset being Orange Battered... sorry, i mean branded (lol) to much folks. If you haven't been snooping aroung the development side of the forum that much, let me bring you up to speed.
The Hard SPL is out. I just change my ROM (as you'll see on my signature) without any worry whatsoever.
The odd thing is, i never had an Orange ROM on mine. I had a standard one and i HAD to change it for one simple reason... something i advise all people to do as a matter of fact.
Why? Well during texting, stylus or hand input, the thing would freeze more that a very sick penguin. It was AWFUL
Have a peek at other ROM's that are about and if you need advice, ask about. I'm no expert but if you ask me, i'll try my best. It really was very very easy following Oli's Hard SPL thread.
Anyway, i've said my bit now. The rest as they say... is up to you!
TheShowStopper
There's a hotfix on the HTC support site to fix the freezing problem on all ROMs < 1.19.
If you don't want to go the Hard SPL route, surely you can flash the older Orange ROM? (That's what I've got and it not been Orangized.)
Update
Fred23 said:
If you don't want to go the Hard SPL route, surely you can flash the older Orange ROM? (That's what I've got and it not been Orangized.)
Click to expand...
Click to collapse
I can confirm the following. As long as you have the Micorsoft Net Framework on your pc, yes, you can flash any HTC ROM to the HD. I have just done this. See the following post of mine.
http://forum.xda-developers.com/showpost.php?p=3060541&postcount=124
TheShowStopper
why
hi I am a complete nooby to WM (switched from an iphone).
My Orange box has the OHTN on so I guess I have the Orange Rom (as no google maps).
To be honest I find the HD to be quite slow when opening programs and seems a bit buggy as it seems to stutter on some operations
Whats the benefits for me of changing this ROM??
Garfoid said:
hi I am a complete nooby to WM (switched from an iphone).
My Orange box has the OHTN on so I guess I have the Orange Rom (as no google maps).
To be honest I find the HD to be quite slow when opening programs and seems a bit buggy as it seems to stutter on some operations
Whats the benefits for me of changing this ROM??
Click to expand...
Click to collapse
Hey there!
Havent you just answered your own question?
The benifts of changing the rom would be google maps (although a simple download could also fix that)
Also a handset that isnt buggy and stutters!
I have the orange ROM
didn't realise orange had been sending them out with HTC ROMs!
bluetooth is faulty
programs open slowly
blimmin opera has orange's naff front page
am loath to flash a proper ROM unless the bluetooth fault is
hardware and then I'd have to cover my tracks before sending it back
any help would be appreciated
( http://forum.xda-developers.com/showthread.php?t=476930 )
cheers
simon
Blackhorse said:
Hey there!
Havent you just answered your own question?
The benifts of changing the rom would be google maps (although a simple download could also fix that)
Also a handset that isnt buggy and stutters!
Click to expand...
Click to collapse
as being new to WM devices and not that knowledgeable what rom do i go for and if i install one will i lose everything i have installed on my phone so far?
i really like the HD but it just seems slow and stuttery compared to the iphone, hopefully a new ROM will fix this? right?
Garfoid said:
as being new to WM devices and not that knowledgeable what rom do i go for and if i install one will i lose everything i have installed on my phone so far?
i really like the HD but it just seems slow and stuttery compared to the iphone, hopefully a new ROM will fix this? right?
Click to expand...
Click to collapse
You need to have a little patience, trying new roms out and tweaking - my handset is very fast now, it plays most video files I throw at it and gui operation i.e touch flo 3d and windows is about twice the speed of the stock rom...
CutePinkSox said:
You need to have a little patience, trying new roms out and tweaking - my handset is very fast now, it plays most video files I throw at it and gui operation i.e touch flo 3d and windows is about twice the speed of the stock rom...
Click to expand...
Click to collapse
could you suggest one as i am completely in the dark to be honest
if i do try a few out will i loose everything every time i do this?
any advice is greatly appreciated thanks
CutePinkSox said:
You need to have a little patience, trying new roms out and tweaking - my handset is very fast now, it plays most video files I throw at it and gui operation i.e touch flo 3d and windows is about twice the speed of the stock rom...
Click to expand...
Click to collapse
Hi, What rom do you have flashed to yours and Is it possible to backup old rom just incase? Am not new to flashing actually, i just really need a fast device, maybe google map and some other little programs, pimbackup, etc.
Hello Guys,
I am from india and I got the HD2 few months back, well to sum up the experience, I have had with the device would be “love and hate” kind of. There are times when I am simple awe stuck by the awesomeness of the device and yet there are times when she acts like a complete ***** freezes for no particular reason. It got so frustrating at times that I even contemplated on selling it off but some thing always stopped me .I would like to thank all the wonderful developers out here who have come up with such amazing apps that at least has made my device usable to a great extend. I THANK YOU ALL from the bottom of my heart.
I am on my official ROM with which the device came shipped with and the version being 1.43 and it’s quite ironical that we haven’t had a single ROM update ever since it has been launched in our country. Any way to cut the whole story short I would humbly request you guys to please look in to my queries:-
1)I am a newbie in to windows OS, so the utter thought of flashing the device kind of scares me off cause I have heard that if not done properly it can brick the device ,But lately I am willing to take that risk only if the cooked rom can solve these 2 grave issues of mine.
a) the screen acts like a lunatic on the run .ghost presses ,hyper sensitivity etc the screen sensitivity tweak did help me a lot but still I am not 100% confident while typing ,So my question is does any of the cooked ROM takes care of this ? and if yes kindly let me the name of it.(this is one issue which I really cant get over)
b) The phone freezes for no particular reason at all , It just stops responding of its own .does the cooked ROM would take care of this as well?
2)Do the official ROM’s address the issues that I have mentioned above from what I know that HK got a new ROM update with the version being 1.72 (Sorry if I am wrong),So in 200 million years I would get to get the official ROM in my country as well and If I am not a prehistoric fossil by then I would rather wait for the it to come as its rather a safe bet for a newbie like me .So any ideas guys as to if the HTC official ROMS take care of these issues .
3)The erratic nature of the screen is it a generic problem ? I can not replace my device in the pretext of this behavior if this is a problem specific to my device, because we have no replacement policies out here. So can a ROM update (cooked or Official ) get rid of this completely .
So guys please do let me know the name of the roms both cooked and official which can help me get rid of these issues.
Cheers .
Flashing the phone is extremely straightforward and easy to do.
If you can follow instructions, you can do it.
I've HSPL'd 3 devices and haven't bricked any of them.
Once you've HSPL'd it's highly unlikely that anything else (within reason) you do will brick the device.
You may render your device temporarily unuseable, but the fact that HSPL allows you to flash without a USB connection off the microSD (!) means that it's nearly impossible to brick a successfully HSPL'd phone.
my suggestion is to dare for a custom rom. study very carefully the tutorials in the rom development forum and you'll be fine, it's not rocket science.
however, to avoid any issues, please remember to always clean your device between two custom flashes by any of the 3 methods:
- flash stock rom + hard reset
- mtty
- task 29
i've always used the 1st method without any issues. it's more time consuming then the others but i've got used to it.
about which rom, this is a matter of preference, there is no best rom for everybody.
you can see which is my favorite under my signature. it's very fast and stable and very close to stock.
i will end by saying that i had many issues in the first couple of month after buying this phone but now it works like a charm, i love it!
oh, and i'm never gonna go back to stock... ever.
cheers and good luck,
antaed
antaed said:
my suggestion is to dare for a custom rom. study very carefully the tutorials in the rom development forum and you'll be fine, it's not rocket science.
however, to avoid any issues, please remember to always clean your device between two custom flashes by any of the 3 methods:
- flash stock rom + hard reset
- mtty
- task 29
i've always used the 1st method without any issues. it's more time consuming then the others but i've got used to it.
about which rom, this is a matter of preference, there is no best rom for everybody.
you can see which is my favorite under my signature. it's very fast and stable and very close to stock.
i will end by saying that i had many issues in the first couple of month after buying this phone but now it works like a charm, i love it!
oh, and i'm never gonna go back to stock... ever.
cheers and good luck,
antaed
Click to expand...
Click to collapse
Mate did you have problems with the screen as well? If yes then did the ROM that you are suggesting took care of them all?
Cheers.
i'm not sure if this is what you mean but i remember it acting strange at some point, after continuous use for 2-3 weeks with the original stock onboard and especially in opera. for example, streams of small vibrations but no movement while trying to scroll or zoom pages.
i've never experienced anything like that since but i have to admit that i flash a new rom every second week or so. i always want to try the latest release, it's very addictive .
hey chakraa...
I have had similar probs...and did HSPL on my HD2 and have been satisfied, and have tried 30 different roms so far.... if you are looking for suggestions i would say "ROMeOS" makes some good roms... his latest 4.07 is good....suggest you try it.... after you do the HSPL your HD2.
challu said:
hey chakraa...
I have had similar probs...and did HSPL on my HD2 and have been satisfied, and have tried 30 different roms so far.... if you are looking for suggestions i would say "ROMeOS" makes some good roms... his latest 4.07 is good....suggest you try it.... after you do the HSPL your HD2.
Click to expand...
Click to collapse
Hey Bro ,Thanks a lot , I am finally mustering courage to go for THE big step(lol I am sounding as if I am about to get married or something), I would surely look in to the ROM which you have suggested,Would let you know about the outcome.
Finally did it.
Hey Guys,
Thanks a lot for your help I finally did flash the ROM all seems to be working fine now.
@CHALLU thanks buddy in the end I installed the rom suggested by you,seems quite stable as of now.Never been a big fan of SENSE so got SPB back ,the key board works like charm and some how I am getting this uncanny feeling that the battery life has improved as well.Do suggest me some other ROMS as well which would improve battery life ,take care of the screen sensitivity and enhance the over all stability.
Update: According to info from Cotulla, MAGLDR does not initialize the touch screen since it doesn't have touch input. WinMo or Android (linux kernel) initializes the touch screen. The failures I'm seeing in Android NAND builds must be due to bug in those builds. I've just downloaded 14 different NAND builds (clockwork and not) to test out again. I'll report results later.
See Cotulla's post on the matter here. Thanks for all the help on the matter to everyone.
Update 2: Here is the link to my post testing a handful of builds and what I found.
Note: Please take the insults elsewhere. I'm trying to actually get some help and offer it. I never said MAGLDR caused any damage to my device. It's a simple bug which once pointed out can be researched and fixed.
The work the DarkForcesTeam has done is amazing! We're talking thousands of hours of work collectively. Some commercially available products don't receive such dedication. I just want to try to help out as best as possible to make it an even better product.
When I use MAGLDR, my touch screen becomes over-sensative. It'll randomly select parts of the screen as having been touched when they're not, like a "ghost hand" was using the device..
It is not a bad digitizer. It is not a hardware defect. It is a problem with MAGLDR. I've confirmed this existing with versions 1.11 to 1.13. The problem only exists when using MAGLDR. If WinMo is used, problem goes away.
Here's what I did:
1) Task 29
2) WinMo 6.5
3) Ran an Android ROM from SD (Copes AOSP SD HD2 GB232/CM7 A2SD at
http://forum.xda-developers.com/showthread.php?t=898831
Everything is fine. Screen is incredibly precise.
4) Task 29
5) MAGLDR 1.13
6) Change SD build to boot from MAGLDR instead of HARET
7) Boot up, everything comes up fine.
8) Screen goes crazy.
Since I didn't change the build I was booting, and only changed MAGLDR, there should have not been any touch screen issues.
9) Task 29
10) WinMo 6.5 reinstalled
11) Change SD build back to boot from HARET
12) Boot the Android SD build
13) Screen is very precise once again.
Does anyone know if the DarkForcesTeam (DFT) has commented on this issue before? Are they working on it? Are they even aware of it?
Has anyone else had any issue like this?
I'm using one of the first HD2s to come out for T-Mobile in the US.
FreakyFerret said:
When I use MAGLDR, my touch screen becomes over-sensative. It'll randomly select parts of the screen as having been touched when they're not, like a "ghost hand" was using the device..
It is not a bad digitizer. It is not a hardware defect. It is a problem with MAGLDR. I've confirmed this existing with versions 1.11 to 1.13. The problem only exists when using MAGLDR. If WinMo is used, problem goes away.
Here's what I did:
1) Task 29
2) WinMo 6.5
3) Ran an Android ROM from SD (Copes AOSP SD HD2 GB232/CM7 A2SD at
http://forum.xda-developers.com/showthread.php?t=898831
Everything is fine. Screen is incredibly precise.
4) Task 29
5) MAGLDR 1.13
6) Change SD build to boot from MAGLDR instead of HARET
7) Boot up, everything comes up fine.
8) Screen goes crazy.
Since I didn't change the build I was booting, and only changed MAGLDR, there should have not been any touch screen issues.
9) Task 29
10) WinMo 6.5 reinstalled
11) Change SD build back to boot from HARET
12) Boot the Android SD build
13) Screen is very precise once again.
Does anyone know if the DarkForcesTeam (DFT) has commented on this issue before? Are they working on it? Are they even aware of it?
Has anyone else had any issue like this?
I'm using one of the first HD2s to come out for T-Mobile in the US.
Click to expand...
Click to collapse
I do not know whether this will work or not. But try a NAND build with SENSE in it. Sense has a function of "Calibrate your Screen". Try and recalibrate your screen.
I know for sure the build "imilka's Vision Sense v3.0 (HD2Z)" has this feature. The link for this build is http://forum.xda-developers.com/showthread.php?t=898708
I hope that resolves your issue.
My touch screen stopped working during windows phone 7 and i cant figure out a reason why. Im running magldr 1.12
It might be a mgldr booting SD build issue, I've been using cyanogenmod 7 android 2.3 nand for a month without a single issue..
Sent from my HTC HD2 using XDA App
roloracer said:
It might be a mgldr booting SD build issue, I've been using cyanogenmod 7 android 2.3 nand for a month without a single issue..
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Same here
Sent from my HTC HD2 using XDA App
When I use a pure NAND build, the problem is there too.
Anytime I use MAGLDR, it happens.
I don't like Sense, but I'll give the one you recommended a try later tonight.
havent had the issue either.. BUT!!! cause its winter here whenever i come from outside and i use my phone i get random presses on the screen cause its wet, when i wipe it off it just behaves..
Alright... my phone just died
Had the setup that you can see on my signature, and touchscreen just stopped responding randomly. First it was once or twice a day, now its like every other time that the screen is sleeping and I try to wake it up.
I did Task29, flashed official WinMo radio, and now the problem still exists. Every other time that the phone goes to sleep - i press any button, the screen lights up, but like the touchscreen function just wont work.
I know for sure that I am not the first, second or even tenth person that has this problem after running NAND-android. Maybe this should be put on the android development thread, so people wont break their phones.
I have no idea why is this happening, but I know that its time for a new phone. Hopefully T-Mobile will give me a new phone, which I can sell and get a native android phone. I hate windows, the reason that I got this phone was the screen size, which no other android phone had on t-mobile back when I got it.
So, one more time
PEOPLE, MAGLDR WILL CORRUPT YOUR TOUCHSCREEN IF YOU USE IT
With that said - I would like to thank everyone that made android on HD2 possible, and specially cotulla, his team, mdj and hastarin, I had a blast using it You guys ROCK!!
Edit: After flashing winmo - I kept getting problems for the first 1hr.
Now it seems that freezing is gone on Win Mo.
Will update later.
t0ny0 said:
Alright... my phone just died
Had the setup that you can see on my signature, and touchscreen just stopped responding randomly. First it was once or twice a day, now its like every other time that the screen is sleeping and I try to wake it up.
I did Task29, flashed official WinMo radio, and now the problem still exists. Every other time that the phone goes to sleep - i press any button, the screen lights up, but like the touchscreen function just wont work.
I know for sure that I am not the first, second or even tenth person that has this problem after running NAND-android. Maybe this should be put on the android development thread, so people wont break their phones.
I have no idea why is this happening, but I know that its time for a new phone. Hopefully T-Mobile will give me a new phone, which I can sell and get a native android phone. I hate windows, the reason that I got this phone was the screen size, which no other android phone had on t-mobile back when I got it.
So, one more time
PEOPLE, MAGLDR WILL CORRUPT YOUR TOUCHSCREEN IF YOU USE IT
With that said - I would like to thank everyone that made android on HD2 possible, and specially cotulla, his team, mdj and hastarin, I had a blast using it You guys ROCK!!
Click to expand...
Click to collapse
I had my touchscreen do that and just stop working BEFORE magldr even came out. A person I know who never hacked or did anything to his phone had this problem. It's a hardware defect and it's just coincidence that it broke while you had magldr on your phone.
not again...
if MAGLDR makes those weird things to your phone then DON'T USE IT!!!
I have been using MAGLDR since it came out. EVen flashing a lot of builds everyday to test but never had any issues with the touchscreen.
jose makalolot said:
not again...
if MAGLDR makes those weird things to your phone then DON'T USE IT!!!
I have been using MAGLDR since it came out. EVen flashing a lot of builds everyday to test but never had any issues with the touchscreen.
Click to expand...
Click to collapse
Same, I've flashed well over 25 times and my Touchscreen hasn't had any problems.
MAGLDR is safe, end of story.
Confirmed? Really? Because you think it happened to you?
This is anecdotal, and it is definitely not concrete in any way. This is pure FUD, nothing more. You should consider thinking before you post ridiculous claims that something has been "confirmed."
This has happened to ONE person on ONE phone, and pretty much everybody else is telling you that you are wrong. Does that sound confirmed to you?
It annoys me that you would smear somebody else's fantastic work because your phone had a freak accident. Go blame the government or something, just stop blaming magldr. Thanks.
Buy a WinMO 6.5 phone stick to WinMO6.5 if you want it to work as intended by manufacturer.
If you want to tinker, then be prepared to tinker it to its death.
If you can't afford a new phone, don't mess with it.
If you can't be without a phone for even 1 day, don't mess with it.
If you want to blame, then blame yourself. You are just messed up.
Danation and hd2k10, I'm not smearing anyone. My phone is fine. There is a bug in MAGLDR. One I'm sure the DarkForces Team can fix if someone can provide some good feedback. Read what I posted again. I'm asking to help DFT solve this software bug. Not saying it's bad.
And I did confirm the problem only exists when using MAGLDR. It runs fine on most of the phones, but there are others aside from myself who have had problems with it. We would love to see MAGLDR working perfectly and I personally encourage anyone who it works for to continue using it. I wish I could use it and want to do everything I can to make that a reality.
psykick5, did you try flashing a WinMo ROM or Android SD build to see if your screen returns to normal?
Danation said:
Confirmed? Really? Because you think it happened to you?
This is anecdotal, and it is definitely not concrete in any way. This is pure FUD, nothing more. You should consider thinking before you post ridiculous claims that something has been "confirmed."
This has happened to ONE person on ONE phone, and pretty much everybody else is telling you that you are wrong. Does that sound confirmed to you?
It annoys me that you would smear somebody else's fantastic work because your phone had a freak accident. Go blame the government or something, just stop blaming magldr. Thanks.
Click to expand...
Click to collapse
Maybe you should read around and see that its not ONE person on ONE phone?
Also, I have flashed many many times, on HD2 and other devices, the fact of the matter is that it happened. Its not just the OP, its not just me, there are plenty of posts in here, saying that exactly the same thing happened to them /just search and you will see/.
Also, I would hate if someone is talking bad about someone elses fantastic work, and this is why I thanked everyone that helped getting android on our HD2s. There is no disrespect, I was just trying to warn other people that this has happened, and not once or twice. The fact that it didnt happen to you - means nothing It wasn't happening to me either, and I even wrote an angry comment to one of the people that was complaining a while back, and ha, guess what happened today
I agree, that probably "confirmed" is not the write word in here, but what we are trying to do, is just warn other users, AND DEVELOPERS so they can look into it, what if the problem is with MAGLDR? Hopefully its not, but thats a big coincidence. What if by some way its overheating a chip or something? You never know, since you are not a developer, I'm don't think that you can be 100% sure about something that is not open source, and you can't see how its made or what it does to the device.
So cool down, and if you can't help - there is absolutely no need to post negative comments.
Thank you,
Tony.
Edit: This is not for you only, its for all the other negative comments that are before yours. And after yours Y'all need to chill out, we are here asking for help. I have donated to a good amount of developers in here, and I am not trying to disrespect any of them, as I said in my previous post. I appreciate their work, but as far as I'm concerned, and the few other guys before me - there is a bug in MAGLDR, and it would be nice if Cotullas team can take a look at it.
Must be a T-Mobile problem. I don't have it. Sorry for you tho, wish I could help.
I have EU HD2 and noticed same problems. Not all time and can say that i think its not MAGLDR problem. More NAND roms side. You ask why.
Tested many roms, not one. No, i dont go say these are bad. just tryed find wich works best for me.
With win 6.5 and win 7 roms i dont seen this problem but with android nand roms yes. Tested custom win 6.5 + android sd too. With that siutation dont had these problems.
Why i try here too is that i think its clued with another problem too, described on this hd2 forum on diffrent places. One is this thread.
Also i have read on some NAND roms thread that rom cooker are increased screen sensitivy or smth. Cant find right now it but if i remember it then i go back and post link.
Not all this sh1t again.
IF there was a "bug" in magldr for TS then it would affect the MAJORITY not the MINORITY.
Also the title of this thread is retarded, you havent "confirmed" a bloody thing other then your ability to presume something and then jump to a wrong conclusion.
EVEN if there is a bug would be a very small one and not one that DFT should waste their time on atm.
your understanding of a bug is that it shows up on the majority of a system? that's utter bull****! sorry.
HectiQ said:
Must be a T-Mobile problem. I don't have it. Sorry for you tho, wish I could help.
Click to expand...
Click to collapse
I have a tmous HD2 and don't experience that crap at all!
Sent from my HD2 Droid HD using XDA App
Hello!,
After trying a numerous NAND roms for my HD2, on every of them the accelerometer is not working. But flashing back to winmo everything is OK and accelerometer works.
Problems having : No screen rotation, no games work which need accelerometer, no bubble meters and so on.
I saw lots of threads here, but none of them were answered. Also some fixes out there from january, but its is said that new kernels include that fix.. Being really desperate about the accelerometer to start working tryed everything , all those fixes - none of them worked.
I really would appreciate if somebody would say a 100% answer if they had same problem and is it for EVERYONE that you are chilling around without accelerometer with NAND roms?
Or, a nicely explained , or some new fixes around there, to fix that..?
I have European HD2, Bought in Estonia. 2.15 radio, and RAFDroid build atm 4.02
Before teyed all cyagenmod build from MDJ, imilka builds, Coredroid, etc.
Waiting for a adequate anwer!, and Thank you in advance!
Daniil.
No pb for me with each Nand i tested. (prj Clean Desire, typhoon, Hyperdroid)
i had this to on my sd build i used to have but when i went to NAND everything was fixed
maybe you can try to recalibrate it in android?
Auralol said:
Hello!,
After trying a numerous NAND roms for my HD2, on every of them the accelerometer is not working. But flashing back to winmo everything is OK and accelerometer works.
Problems having : No screen rotation, no games work which need accelerometer, no bubble meters and so on.
I saw lots of threads here, but none of them were answered. Also some fixes out there from january, but its is said that new kernels include that fix.. Being really desperate about the accelerometer to start working tryed everything , all those fixes - none of them worked.
I really would appreciate if somebody would say a 100% answer if they had same problem and is it for EVERYONE that you are chilling around without accelerometer with NAND roms?
Or, a nicely explained , or some new fixes around there, to fix that..?
I have European HD2, Bought in Estonia. 2.15 radio, and RAFDroid build atm 4.02
Before teyed all cyagenmod build from MDJ, imilka builds, Coredroid, etc.
Waiting for a adequate anwer!, and Thank you in advance!
Daniil.
Click to expand...
Click to collapse
Usually d G-Sensor/Accelerometer has been pre-calibrated while cooking d android build...I've never had such a problem on SD, NAND or RAM builds....Perform a Task 29 on ur device and try flashing the build contained in my signature....CMY's work has always been great...
Done task29, done recalibration in android, everything... same. There is numerous people having the same prob , as i have seen from questions subforum.
Auralol said:
Done task29, done recalibration in android, everything... same. There is numerous people having the same prob , as i have seen from questions subforum.
Click to expand...
Click to collapse
Hmmm...Since it works on WinMo, try recalibrating it there and then run an android sd build (i just tried "Desire_DL" series and all was ok....on d other hand, have u tried d NAND build in my sig?
I have tryed everything, including your builds in the signature.... Nothing helps
Help!
Try the post that is in my sig, there is alot of info in there that might be of use to you. What definitely controls the G-Sensor is the bma150_usr file. If nothing in my post helps you at all, then I am unable to help you further since I dont have a Eu HD2. But I still believe that there might have been a revision which might explain your troubles as well as some other people.
Tryed that also, no help at all.
Auralol said:
Tryed that also, no help at all.
Click to expand...
Click to collapse
Hmm, dats quite a dilemma....I tk it u can't return n request for another device seeing as u got it 4rom Estonia...or can u?
Android is not supposed to run on HD2 anyways, so why should i have an opportunity to return my device for another one?
Auralol said:
Android is not supposed to run on HD2 anyways, so why should i have an opportunity to return my device for another one?
Click to expand...
Click to collapse
True it wasn't but IT IS...I and several others are proof it works beautifully on the HD2, even better than some native android devices...I offered a suggestion n its ur call 2 tk it or leave it...I on d other hand, love my current android build on my HD2.
Have u tried this workaround?
P.S. Oh yeah, and my accelerometer/g-sensor works perfectly in apps n games.
I mean, yeah it is working, but... not working for my device. And the point was that i can't take it to my local shop for a return, as the g-sensor works for the WinMo, and they will say that its your fault that it isn't working in android. Yeah i know that accelerometer works on androids on the Tmobile HD2-s
And yeah, i have tryed
Different type of g-sensor
I understand that some newer builds of the HD2 have a different type of g-sensor. I have x4 HD2's. 3 are working perfectly with HyperDroid CM7 cheerful cheetah. The forth is used by my company co-director which I recently tried to move over to the HyperDroid CM7 cheerful cheetah from WM6.5. This is when I came across the problem. Very annoying. The fact is that this device went back to HTC to repair/replace a cracked screen (I dropped the device last June). I suspect they gave me a reconditioned or replacement unit with the "updated" sensor.
Please advise me if there are any new developments. I can confirm that the HD2 (with the working g-sensor) has incredible battery life and is only my no.2 device because of the 8mp camera on the DesireHD.
Regards,
Jay
[email protected] said:
I understand that some newer builds of the HD2 have a different type of g-sensor. I have x4 HD2's. 3 are working perfectly with HyperDroid CM7 cheerful cheetah. The forth is used by my company co-director which I recently tried to move over to the HyperDroid CM7 cheerful cheetah from WM6.5. This is when I came across the problem. Very annoying. The fact is that this device went back to HTC to repair/replace a cracked screen (I dropped the device last June). I suspect they gave me a reconditioned or replacement unit with the "updated" sensor.
Please advise me if there are any new developments. I can confirm that the HD2 (with the working g-sensor) has incredible battery life and is only my no.2 device because of the 8mp camera on the DesireHD.
Regards,
Jay
Click to expand...
Click to collapse
Hi Jay, I've got a similar problem.
Actually, I've got (or had) an EU model, and my screen cracked, so it has been out for repair. So both descriptions in this post (yours and Auralol's) fit my problem. I have been looking for a fix for a while now, did you find anything?
I would love it to work, it really is the only thing that doesn't. If this is fixed, my HD2 would be perfect and irreplaceable.
If you find anything that helps, keep me posted?
Kind regards,
Bas
Hey Bas,
I contacted vfuk & simply said that there was a problem with the g-sensor on my HD2... The helpful telephone attendant asked me to remove the battery, memory and sim cards and a replacement device would be with me the next day. The following day the courier took the troubled HD2 and handed me a new Desire HD albeit without the antenna and battery covers. I have a spare battery and ordered the covers from expansys.
I did explain to vfuk what happened - they said I wasn't to worry.
At the time of writing I now have x4 dhd's and a working HD2 with HyperDroid which I am going to give to a pal to lure him away from Nokia...
I now have no way of helping you further. Sorry bout that.
Best,
Jay
[email protected] said:
Hey Bas,
I contacted vfuk & simply said that there was a problem with the g-sensor on my HD2... The helpful telephone attendant asked me to remove the battery, memory and sim cards and a replacement device would be with me the next day. The following day the courier took the troubled HD2 and handed me a new Desire HD albeit without the antenna and battery covers. I have a spare battery and ordered the covers from expansys.
I did explain to vfuk what happened - they said I wasn't to worry.
At the time of writing I now have x4 dhd's and a working HD2 with HyperDroid which I am going to give to a pal to lure him away from Nokia...
I now have no way of helping you further. Sorry bout that.
Best,
Jay
Click to expand...
Click to collapse
Heyy Jay,
Thanks for the reply. So, you kind of worked around the issue Sounds like great customer service. Too bad my provider does not work like that.
Just being curious if you had the same problem as I am facing now, did you try to retrieve / read data from the sensor (i.e. with "sensor debug")? I tried yesterday, didn't get any data at all. Probably means Android doesn't see the sensor, or it is indeed a different sensor and therefore needs other drivers.
I just downloaded some e-books about android and java, just to see how it works with hardware. Maybe it is possible to implement my 'own' drivers in a ROM to make sure the sensor can be detected at least. I guess it is going to be my pet project to find a solution, and when I do, I'll probably try to get it posted on xda. But then again, my programming skills are minimal at this point (just some Basic, html and Step 7), so it might take me a while...
Anyway, thanks for the reply. Too bad your solution does not work for me (I would not mind that either).
Kind regards,
Bas
Bas2ct said:
Heyy Jay,
Thanks for the reply. So, you kind of worked around the issue Sounds like great customer service. Too bad my provider does not work like that.
Just being curious if you had the same problem as I am facing now, did you try to retrieve / read data from the sensor (i.e. with "sensor debug")? I tried yesterday, didn't get any data at all. Probably means Android doesn't see the sensor, or it is indeed a different sensor and therefore needs other drivers.
I just downloaded some e-books about android and java, just to see how it works with hardware. Maybe it is possible to implement my 'own' drivers in a ROM to make sure the sensor can be detected at least. I guess it is going to be my pet project to find a solution, and when I do, I'll probably try to get it posted on xda. But then again, my programming skills are minimal at this point (just some Basic, html and Step 7), so it might take me a while...
Anyway, thanks for the reply. Too bad your solution does not work for me (I would not mind that either).
Kind regards,
Bas
Click to expand...
Click to collapse
Hi,
I'm having the same issue as you and was wondering if you had made any progress or if there is anything I could help you with although my programming knowledge is probably more limited than yours. Anyway this issue seriously needs to be looked at! :'(
Still no fix?
Hello, I know it is old thread, but I see there are more people than only me having this issue. Same thing happens to me. Accelerometer isnt working on Android, but it works great on WinMo. I tried a lot of ROMs, "fixes", but nothing helped at all. I used apps like Sensor debug, and sensor list, seems that they dont see my g sensor at all, like someone said before. As I know, g sensor is connected with bma150_usr file, but I used my Root Explorer to search for that file and there is no such a file at all. Shouldnt it come to my device with other ROM files? Yes, I tried to put it where it should be, but the same s**t again... Is there anyone who solved this thing? Because I dont see any solutions mentioned in the whole xda forum.
Looking forward for answers which REALLY helps.
Hi,
I have this same problem, My g-sensor didin't work on AMeriCan Android.
I was reading a topic http://forum.xda-developers.com/showthread.php?t=902129, and my question for this: How I can delete files
Before installing the file above, go to System/Bin and delete the bma150_usr, then navigate to Data/Misc, and delete the following files:
AK8973Prms.txt
AK8973.Prms.txt.tmp (If there)
bma150_usr.txt (If there)
After navigate to the above file and add it to System/BIN and then your calibrating will function correctly and adjust the values properly.
Click to expand...
Click to collapse
hello all, first let me just say yeah im a noob and yeah i tried searching.
so like the rest of the world i hated win 6.5 more than anything. seriously. probably something like 1. hitler 2. win 6.5 3. snakes
finally i managed to install win 7, but however the battery is just way to short, some numbers wont be recognized, marketplace isnt open in my country, etc. frankly im ****ing tired of all of this. now i want to remove it and again try to install android on NAND. if not maybe just settle for win 6.5 i dont know.
EDIT
to clarify:
-basically ive searhed everywhere
-i have the offical rom and i want to install that
-i cant connect my phone to zune,
-so when i run the offical htc rom, it just says connect your phone
You need to either flash a stock ROM via sd card method or via bootloader (hold vol down key during power-on, then flash with normal exe from windows).
so, just to be clear,
you got a device with Win mobile on it which you seem to have a massive dislike for and wrongly make an assumption that everyone else doesnt like it, then in a hugely disrespectful manor you compare it to hitler, quite what you are thinking is anyones guess but it might be worth considering a change of manor is perhaps in need
Then attempted to install WP7 without fully reading everything.
Then try and install an original ROM without Fully reading everything
I think That about sums it up
So, in the intrest of sanity, go here
http://forum.xda-developers.com/showthread.php?t=1074233
read it all, and if you have an issue reply in that thread
Couple of pointers to help your days on XDA dev out, if there is a thead open on an issue use it, dont make a new one because it makes it harder for people who actually search for things to find what they are loooking for and its a pain for people who try an help because we are forever repeating ourselves
Secondly, when you make a tread it gave you a list of threads already out here with a similar name, if you didnt see anything relivent its because your use of title is pretty poor, Its windows phone 7 or WP7, Noob isnt a word most of us use
Thirdly, if you can not use the XDA search then use google, (i find it much more accurate) i just searched google using this string
XDA DEV LEO WP7 FLASH ORIGINAL
and the third one down took me straight to that thread above
XDA DEV is pretty obvious, LEO is the listed device name thats on this site WP7 is the OS then FLASH ORIGINAL is the subject matter im searching for
Keep it short, like bullet points, not a long story
So, head over there an folk will be happy to help you out, including myself
I hope i didnt sound rude and off hand, im simply nudging you in the right direction
Neo84 You need to either flash a stock ROM via sd card method or via bootloader (hold vol down key during power-on, then flash with normal exe from windows).
ok, thanks for you reply. sorry to ask but what is a stock ROM? is that like an official ROM from HTC?
also tried to hold down the volume key, get the coloured screen, but then cant do anything. where would one find the "normal exe"? thanks for your willingness to help out someone not as experienced as yourself
and dazza, my good man i do appreciate the nugde, but do find it a bit harsh.
you got a device with Win mobile on it which you seem to have a massive dislike for and wrongly make an assumption that everyone else doesnt like it,
-everyone i spoke to agrees, including the guy who sold it to me for almost nothing (bought for 1100 US 6 months before) because he hated it like no other
then in a hugely disrespectful manor you compare it to hitler, quite what you are thinking is anyones guess but it might be worth considering a change of manor is perhaps in need
-well irony doenst work online my bad, haha seriously noone in ther right mind would compare the 2 and/or accuse someone of doing so
Then attempted to install WP7 without fully reading everything.
-i did, it works almost perfectly, reading on these forums ive seen plenty of ppl having issues, so yeah its close to perfect, except the battery drain (which still works for a full day so i can charge at night)
ive searched google, xda and god knows what. and after trying all, my good old hd2 still wont connect maybe in the end its not worth the time and effort, just leave WP7 on there (it is in fact pretty sweet) and buy an offical android next time! however i do feel i have the right to be a bit angry. winmo 6.5 isnt worthy of selling for a high price in 2010.
anyways, thanks for your help, i will check out those links and see where it takes me just remember that not everyone is as experienced as yourself, a friendly heads up works wonders sometimes
I appologise, it was not supposed to come across rude, harsh is perhaps an accurate way of putting it, remember that some of us take a lot of time out of our lives to go over these things, infact some have even added entries in to the Wiki for just such issues (check leo wiki section) and im sure you can imagin that repeating yourself over and over can be quite frustrating!
I completely agree that a "heads up" is always needed, which is why ive nudged (perhaps with a prod or two ) you in the right direction, those few tips can save you a lot of hassle in the future, the google one especially as i know only too well that the XDA search is crap