Database Users

Sorry for Cryin out loud but need your help guys

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.

Acer F1 system successfully run Android 2.2

Turn：mikeyangly（Come from：pdafans.com）
Touch screen, and drive signals are not supported, I hope the faithful machine can solve this problem
System Download:rayfile.com/zh-cn/files/4e80a502-973c-11df-abb4-0015c55db73d/

GREat news !! hope its just a question of time for the others drivers!

On my neotouch android doesn't boot. It stays on this:
EDIT (22:05): now it boot. I haven't got in the root of Storage Card .

s200 froyo 2.2
O ye,this is a very great news,incredible ,we jump directly to Froyo 2.2,as you say it is a matter of time and developers now.The waiting has began!
Otherwise phone boots very quck:
-no touch
-no sound
-no keys
-no gsm ...
we hope all will be on soon

good start. hope problems are possible to be solved....

Oh very goog!!
Does tsamolotoff's TS driver works?
its drivers work with ubuntu!

Wow great news!I am waiting for a full working version(rom)

Android just has more free apps than windows..
that would be the only reason i would want android

free apps... oh well
The only reason i would want android is a bunch of games ported for this system. Android for games and WinMob for everything else. and all this stuff in one device. that would be nice

very good.

Why do I have blue screen after 10 seconds working of it?

Because there are many problems to resolve to use android on our s200...The os is not alredy usable like in htc hd2,and our device is not supported like the htc one.So maybe the project for s200 is end.I wish i could use android in my phone,but maybe i will never see a usable interface

This is an exciting good news. Soon we can use the Android system has. Thank you for your efforts.

Sadly theres no kernel/android dev that has an s200, so android partly working on it might never happen, unless a dev picks it up and starts making patches/fixes for the kernel.

Not so good if you think that s200 and hd2 project started togheter,but hd2 after 1 month has a usable android or ubuntu release and our s200 has only a not usable android "desktop".Our device is not supported by comunity as hd2,so correct me if i m wrong,but i think no one still working on android s200 release

Ok guys it has been a month since first post, anyone reckon this is going somewhere? who was developing this in the first place? I am willing and ready to help in any way I can (I have stated this before) if necessary. I have a working s200, but no experience in linux programming, although I could learn some basics if needed.
Maybe we could send some android devs a pm? I mean how hard can it be if our hardware is so similar to the Liquid, AND we already have it running on our processor...?
I have seriously considered leaving the s200 and getting an HD2 by now...
Greets

no news of any progress for a while now...
anyway i never expected a fully working android on our neotouch. theres just not enough guys working on it like on the HD2...

can someone mirror this file please?
i dont want to download & install rayfile's client...
Thanks.

It s a really hard porting job...Hd2 owner has a good partialy stable android port,but as you all know there's 20 times hd2 then s200.The problem on our phone is the restricted comunity support

Well, it seems that when I got my s200 broken nobody raised the banner from my cold hands
Now my device is up and running again, and maybe i'll try to do something more... don't expect ts to work in android, as it's completely functional via tslib, and i don't know droid's architecture to determine why this PoS of an OS can't use it... if you really want it guys, why don't you experiment with sequence of input_abs_* functions within ts worker thread in driver ? There're so many *experts* who make ROMs via kitchens or do fancy icons/pictures - take up your time and learn C / linux kernel... I started with barely basic knowledge of the first (and I was lucky with the fact that there're many pre-coded drivers that simply needed some testing, or with semi- or fully-compatible initialization (many thanks to dcordes, Cotulla and the team))

[Q] Nand Android accelerometer/g-sensor DOES NOT WORK?

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

Touchscreen not working

Installed IceCreamTosti HD2 ROM 0.9 worked well for a day or two then all of a sudden my screen would stop working when it went to sleep. I researched and found that there is an undervoltage script that could be causing this problem. So i deleted the script. Then it started happening again. Task29'ed, installed HyperDroid Gingerbread Xtreme to see if that would fix my problem, nope still happening. It works when it wants but the funny thing that if I get it to work, I can use it until I have to go back to the previous screen, then I would have to hit the power button to put it to sleep, unlock it for the screen to become responsive. I know it sound like a Digitizer problem but I was wondering if anyone has any other suggestions before I buy it.
Thanks!

read here http://forum.xda-developers.com/showthread.php?t=993787

I've already read that. Thanks
Im just seeing if it could be a Kernel problem or something of that sort.

I've had this problem on one of the ROMs i used, not sure which one since i didn't stay on it for to long.
After i flashed a different ROM it fixed it. This might seem like a lot of work but why not reinstall MAGLDR,
CWM & a new ROM. Maybe try RAFDROID HD. Yes i know its a really old ROM but its a goodie and this
would be for test purposes anyway. You can always switch back.
I read the mentioned thread before too and im sure it does sound like it happens but since it happened so
soon after you installed a new ROM it makes me think its the ROM, eventhough you tried to reinstall a
different one. Maybe you can make a backup of your SD card and repartition both your phone and SD.

PC10DaTruth said:
Installed IceCreamTosti HD2 ROM 0.9 worked well for a day or two then all of a sudden my screen would stop working when it went to sleep. I researched and found that there is an undervoltage script that could be causing this problem. So i deleted the script. Then it started happening again. Task29'ed, installed HyperDroid Gingerbread Xtreme to see if that would fix my problem, nope still happening. It works when it wants but the funny thing that if I get it to work, I can use it until I have to go back to the previous screen, then I would have to hit the power button to put it to sleep, unlock it for the screen to become responsive. I know it sound like a Digitizer problem but I was wondering if anyone has any other suggestions before I buy it.
Thanks!
Click to expand...
Click to collapse
After reading the other guys thread about the end key it does seem like a bad digitizer . i read other threads explaining your exact same issue . the only way to figure out if its ROM related is to flash the stock winmo 6.5 ROM . yes , i said it , winmo but thats the last resort before deeming something hardware related . if you tried the end key option , pressing really hard on the key , then i guess i would change tto winmo and try to see if it still happens then

I do have to admit it could just be coincidence and the digitizer went up but considering this happened
only a few short days after he installed a new ROM makes me feel that there is a possibility its the ROM,
or maybe even the partition he changed (if it applies) when flashing that ROM over. I still suggest to start
over from MAGLDR on, including repartitioning your phone to the proper needs of the new ROM to see
if it helps before doing something drastic like reverting back to winmo.

Thanks for the help everyone, opened the phone up. Was hard as hell! But I cleaned the dust on the contacts under the end button, still no luck. I bought a new phone. Going to get a digitizer down the road and fix this one, If anyone want to buy it just let me know.

You will get a lot more people to see your interested in selling the phone if you post it in the xda marketplace found here.
Just open a new thread there and post how much you would want for the phone. I'm sure people would be interested
especially when you can get a new digitizer off ebay for so cheap.

change an other rom,if the problem still exist,i am sorry to tell u that u should send it to fix the touch screen..

How to reset accelerometer?

Hey guys,
I just recently upgraded to the latest CM10 jellybean build on the forums here, but now my accelerometer is acting up. The only current way to make it appear properly portrait is to hold it straight out; parellel to the ground. If I hold it normally, it thinks I'm holding it sideways and flips the orientation accordingly.
Is there anyway to reset the accelerometer? I found this thread: http://forum.xda-developers.com/showthread.php?t=816131
But, the file they want you to delete(ms3c_yamaha.cfg in /system/bin) doesn't seem to be present on my phone. Is the file different under ICS/JB? My phone is a Vibrant from T-Mobile, if that matters.
Thanks for any idea on the situation.

That file only exists as far as a know in official roms.
As for a solution i believe you need to go back to an offcial rom as clear storage etc, has not worked for people with the same problem.

That's what I was afraid of. My phone seems to be possessed, it has so many issues when upgrading roms that no one else runs into. I'm just going to flash it back with Odin and leave it as is.
Thanks for the information!