Related
Does anybody experience problem with the g-sensor?
I had my Magic changed (after brick for a wrong spl) and I realized lately why auto orientation change is not working,
the g-sensor is giving crazy values (20g), auto-calibration does not work, it stops since it sense strange values.
My guess is a hardware problem. But since I have a Q-Technology Hero-port firmware I would like to know if anybody ecperience this with this firmware.
I don't remember if it was working immediately after taking it from Vodafone shop since I flashed the new firmware straight away.
Question: where can I get the original Vodafone firmware?
Thanks
Byron
It occurs to me that I might be having a similar problem. I reported it against the Cyanogen ROM I'm using, thinking it was a Donut + 32A problem. I did, as it happens, get mine "serviced" after I bricked it earlier and I can't remember the orientation stuff working since then.
Here's what I reported, I assume you are getting very similar results:
http://forum.xda-developers.com/showpost.php?p=4536450&postcount=923
After some further searching I came across this thread:
http://forum.xda-developers.com/showthread.php?t=545345&highlight=sensor
I assume that deleting these files causes the automatic calibration to occur, which is probably what you've referred to as trying without success. I deleted those files myself and it has not fixed my problem.
Using the Sensor Debug application on the Market, I'm noticing that with my phone sitting idle on my very stationary desk I get the following values:
azimuth ~= 303
pitch ~=123
roll = 32
force on x-axis = 17.95...
force on y-axis = 28.19...
force on z-axis ~= 1
magnetic field ~= (-21, -12, -23)
where I'm using the "~=" notation to indicate constantly fluctuating approximations. Are those measures forces normal?
Also, I can't help you with a Vodafone ROM, but if you go to the HTC website there are a few factory ROMs in the support section for the Magic. Check them out, but obviously choose very carefully.
I've sent a help request to the folks at HTC about this issue.
After Googling the subject, I've discovered that the HTC Hero comes with a user-accessible sensor calibration tool. HTC will likely not release for their other handsets, but the fact they've released it into the wild means they somewhat acknowledge that there is actually a problem with the sensors.
Well, the folks at HTC are a strange bunch. They seem to have completely misunderstood the reason I contacted them.
I contacted someone with a perfectly functioning rooted 32A and was able to procure their akmd_set.txt file. Thanks bcrook.
My original akmd_set.txt file causes the handset to have only left-to-right roll detection in portrait, or up-and-down roll detection in landscape.
Plugging bcrook's akmd_set.txt file straight in reverses the situation. I now have left-to-right roll detection in landscape, and up-and-down roll detection in portrait.
I have no idea exactly where to begin, but I suppose it's possible that merging the files will bring me to the desired resolution. Now I just need to figure out what the good settings from my file are, and identify the similarly good settings from bcrook. /sigh
I just flashed the MyHero ROM to my phone in order to get access to the G-Sensor Calibration tool found in the Sound & Display settings. This looked very promising but I kept getting the "Calibration aborted" message. Why me?
not able to load rom
while flashing rom..m getting error...No signature(731 files). plz help
ultimaterakesh said:
while flashing rom..m getting error...No signature(731 files). plz help
Click to expand...
Click to collapse
Really off-topic, you'll probably find answers elsewhere. This thread is specifically about G-Sensor Calibration difficulties.
In the meantime, I'd suggest getting your files directly from the source, and reading all the instructions carefully. If the files are distributed here on these forums, then make sure you definitely read the entire first page of posts, since they'll usually have lots of important information.
Every few weeks I try out a new Hero-based ROM and see if the Calibration Tool works. I checked out Evil Hero yesterday. Still no dice. The Calibration Tool does not abort prematurely, however, and the /system/bin/ssd_bma15_usr file is definitely there.
I can confirm, however, that if the /data/misc/akmd_set.txt is missing, then it is generated using fixed tags somewhere. And running the Calibration Tool does not appear to even alter the calibration, it just doesn't visibly fail anymore. I had "adb logcat" running during a calibration run, and I noticed the sensors being opened and closed but no errors reported.
I don't know the specifics, but it's possible that the ssd_bma150_usr is just a stub. So my options to get my phone 100% functional are still:
A - wait for official HTC Sense UI release for Sapphire
B - send phone back to HTC's support team
I tried out MyHero 2.0.2 today. No dice. This ROM is apparently based off the official HTC SenseUI for Magic, and there does not appear to be any G-Sensor Calibration available anywhere.
It's still a little too early to tell, but I have a feeling that the official HTC SenseUI for Magic simply lacks the tool. I'll wait for the release for my region before giving up. /sigh I suppose only the Hero has a calibration driver HTC can be bothered with supporting.
This likely means, though, that my list of available options shrinks to a single option: send my phone back for repairs. And since this hardware fault only presented itself when I last did that, I'm just not entirely confident.
any solution found?
kirkusss said:
any solution found?
Click to expand...
Click to collapse
Not yet, I'm afraid.
If you'd like to help, you can search the internet for a leak of the Diagnostic SD Card image. If you boot your phone while holding the Volume Down key, you will quickly see it try to load one the SAPPDIAG.* files. That's the file we need. I was on the trail for a little while, but I hit a dead-end when I got to an unlisted HTC website that required a password.
Another way you can help is by doing a nandroid backup of your phone. Then go and try out one of the Sense UI ROM releases found on these forums and see if there is an option anywhere to calibrate the sensors. Once you've checked out the ROM, post your results here and then you can restore your nandroid backup so your phone is back to normal (or keep the new ROM if you like it better). I've already checked MyHero 2.0.2 and an older version of Evil Hero, but there are a few more to check.
A word of warning to everyone, it is very important that you do a nandroid backup of your phone fresh out of the box and BEFORE you do anything else. If only I had done this, I would still have my original akmd_set.txt file and my phone's sensors would not be misbehaving.
Today's adventures with official HTC update 2.17.861.3
Okay, so I decided to take the plunge and try out the official ROM update for my Sapphire 32A. I found it here at HTC's support page, version 2.17.861.3. I figured there was a chance an official ROM would have drivers that the cooked ones floating around here don't, and it was worth checking to see if I could fix my G-Sensors once and for all.
I struggled for a while to get the ROM update to even work. Eventually I learned to enable USB debugging, delete the ADB device and drivers from Windows 7's device manager, grab a copy of the Vista64 drivers and install them. So the ROM update finally worked, yay!
I'm going to put this in large bold letters as a warning to others right now:
HTC Magic ROM update 2.17.861.3 installs a perfect SPL!
That is to say that if you install this ROM, you won't be able to fastboot a new recovery or system ROM.
I can also confirm that the official ROM does not fix my problem, it is just as clueless about true calibration as any of the 3rd party cooked ROMs. The closest I ever got to this sort of solution was a Hero-based ROM and it never worked either. /sigh
So I figured I was completely stuck at this point, unable to install AmonRA's recovery and therefore unable to restore my nandroid backup to this morning's snapshot.
However, it dawned on me after a few hours of struggling to create a goldcard, the old bluetooth vulnerability exploited by flashrec might be present in this official ROM. As it turns out:
HTC Magic ROM update 2.17.861.3 is vulnerable to flashrec!
So here I am back with CyanogenMod 4.2.3.1 and RA-v1.2.3, but with a perfect SPL. A significant step backwards, in that it'll now be difficult or impossible to update my recovery,seeing as CM is immune to the bluetooth bug and you need a non-perfect SPL in order to fastboot a new recovery. Oh well. Lessons learnt.
[duplicate post]
Okay, so on Monday my phone was shipped back to the technicians for repair regarding sensor calibration. As you can tell by reading this thread, trying to fix this myself was impossible without somehow getting access to the Diagnostic SD card image for Sapphire, which as far as I know as not been leaked and only resides on HTC's (password-protected) technicians' website.
I got it back today, and the issue was still there. So I sent it back immediately with quotes from the leaked service manual detailing exactly what they need to do. And I also mentioned factory-installed applications they can use to determine if the problem persists, namely HTC's Teeter and simply trying to get the phone to notice a transition from portrait to landscape. /sigh
Anyhow, I don't know what I'm expecting or even hoping for. Is it better to have technicians who were previously incompetent but can fix my phone with my instructions? Or is there a chance my phone really is broken and the technicians are indeed competent and trying everything they can to no avail? /shrug
Mine is also at the local htc repair center. As far as I know they are waiting for the calibration image.
Do you have a link to the leaked service manual?
I'll keep you posted
http://phandroid.com/htc-magic-manual.pdf
I pretty much just Googled it.
Okay, my phone got back from the service centre today and it is all fixed!
I noticed that they installed a newer version of the basic Android 1.5 HTC ROM without SenseUI: 2.17.861.5 (only .3 is available for download) and the SPL was a non-perfect version, which is very nice. The technicians apparently had to replace the motherboard.
Judging by how few people seem to have this persistently broken sensor issue, I would say it is a very rare manufacturing defect. I am guessing that when the phone is built, the sensors are calibrated and this data is stored on a flash ROM somewhere on the motherboard. When there is no /data/misc/akmd_set.txt file, the kernel goes and fetches the data from this sensor flash.
Because this data is not part of the usual wipe-and-flash area where user and system data is stored, it is not able to be fixed with any consumer-accessible software.
The Diagnostic SD card that was my Holy Grail for so long was also probably unable to fix this problem, although it certainly narrowed it down enough for the technicians to know that only a new motherboard would solve it.
Can you please upload the SD card image somewhere?
Thanks
I never at any time had access to the Diagnostic SD card. It can only be retrieved from HTC's website, and only if you have been given a password-protected technician / service account.
Hi All
Was using SD versions of Android in my HD2 which worked quite well .....decided to make the jump to NAND recently but I'm having a problem with phone calls.
When I make a call out, everything works fine, but when I hang up on the call, the hard buttons on the bottom of the phone all light up but the screen doesn't turn back on.... Only way to get the screen back on is to plug in the USB cable or power adapter or pull the battery and do a reboot!
Have tried a couple of different builds from different chefs and a couple of Radios just in case.
At the moment I've got the following on it:
Radio is 2.12.50.02_2
Android version is 2.2.1
Build is DL DesireZ v3.4 Final (but this problem also happens with CleanDROID V1.31)
Also tried an MTTY Task 29, reload of MAGLDR then re-flash of the NAND in case traces of my previous ROM were still around but that hasn't helped either.
Any ideas?
I seen many threads about same situation. Actually i itself use daily gpc hd2 gingerbread v1.5 with same problem. Sometime help back button (when call ended not at me). Sometime just more light to proximity (or it light) sensor (when inside and put phone with face to some light). Outside i just must turn phone with face to sun or good light then screen wakes up.
I tested many many nand roms. All have same problem.
Tested win 6.5, win 7 and sd version, they works well. That gives confirmation that my proximity (or it light) sensor works well. And finally that something wrong with nand.
Here was discussion that MAGLDR does that. NO.
I started run over net and find solution. Here seems no help for this right now. Maybe just problem ignored because cookers itself dont have this and cant do anything. If you dont have problem then how you can fix it.
On web i found some discussion about kernel problem or smth about this proximity sensor. I cant find it right now again. There was talking about this problem, but no solution.
I thinked about open new thread and invite kernel chiefs to discussion to solve this problem. But today i find your ask. I opened for any test and help that i can give. I dont be afraid to lose my phone if something must go wrong. Phone is just piece of electronic and you can replace parts. But knowledge and experience you cant buy.
Any ideas how to resolve this little bad thing?
Thanks for the reply.
Yes it's a real problem but mine won't wake up no matter how much light.
The only way I can get it to wake up is to plug it in to power, then the screen wakes up.
Is that the same as yours?
I i remember it right i was suprised once too if this happened. I just put my "again dead" phone to charging and its waked up.
If screen is dead and same time connected to pc (i use for managing inside phone androidcommander) then moving over dirs wake screen back too.
But lets look how long my nerves will be good. Today i thinked to move back win 6.5 and sell this bastard.
No don't sell we need to resolve! I'm hoping someone will look at this thread and help us figure out why this is happening. I can't believe we are the only 2 people who have this issue.
Anyone else have any ideas as to why this is happening?
This issue was also on sd versions. So I see nand has not fixxed it. I am running MDJ HD 4.6 and have this issue. Sometimes the light sensor works properly and other times it goes to black screen and gets stuck.
I read somewhere that it might be the hardware itself. Saw a video on youtube also. Seems the european T8585 and telstra T9193 might have poor light sensors. The T-mobile light sensor supposedly does not have this problem.
So I am guessing anyone with this problem does not have the T-mobile USA version??
It could just be drivers too. It is a pain and sometimes I wish I could just disable the light sensor.
Also NAND roms are no better than sd versions as far as bugs. If the sd version has the bugs then so will the NAND version. The build is just installed at a different location.
Yes good point.... the bug will be replicated as it's just where the OS is stored that's different.
I'm thinking it's the hardware as I have this problem on WinMo6.5 too and I have tried various WinMo roms but had the same problem.
Mine is a UK HD2 supplied by O2. Wish there was a fix for it :-( It's a real problem.
PS I ran PhireMOD's Skinny EVO SD Android for a while and didn't have as much as a problem as I have had with the 2 NAND roms I've tried..... if that's any clue? At least with that rom I was able to make calls and hang up and still get the screen back after I hung up (except for the screen going white and washed out which could only be resolved by a reboot). There was still the problem with the screen being on all the time during a call or the screen being black and not coming back on during a call though.
I have these sort of problems too. It's really annoying when you're in a phonecall and you take the phone away from your ear and it takes a few secs to turn on. Also when I'm unlocking it.
Sent from my HTC HD2 using XDA App
At least yours comes back on lol mine stays off for ages and ages and sometimes doesn't come back on at all!
Noticed that if I shine a torch into the proximity sensor that's the only way I can get the thing to turn back on :-( Also noticed the 2 little holes where the prox sensor sits appear dirty/cloudy... not sure how that happened.
I wonder if the prox sensor is busted or if it's just dirty or something? Going to get a T5 Torx and take my phone apart to find out if it's something I can resolve.
Well i had this with rafpignas kernel...i changed to markinuX today and tested it with over 10 calls and it works flawlessly right now
Hmm, are you sure g9650? Seems my guess about kernel was then true. I use gpc pure gingerbread 1.6 with gpc itself made kernel. I go right now replace kernel and test. Results tomorrow.
Took the phone apart yesterday night and uncovered the proximity sensor. Even out of the case it needs a torch/flashlight to shine on it to bring the screen back on :-( I honestly think the proximity sensor hardware isn't working anymore.
I'll try the kernal you suggested though just in case that's what's causing the problem.
Datas0ft let me know if it works for you?
Latz, actually i taked to test markinus extra clean 1.7.1 (right now on it itype this). Had one call before and no changes.
Also i stuck on taking out kernel at this version. Low knowledge. Dont find any help yet on xda. I work on it. If you have hints dont hestitate say.
Sent from my HTC HD2 using XDA App
:-( I was hoping we found a miracle cure! Ok let me flash mine tonight and try it to see if mine behaves any different. Will post back with results... let me know fi anything changes with your phone datas0ft.
q9650 said:
Well i had this with rafpignas kernel...i changed to markinuX today and tested it with over 10 calls and it works flawlessly right now
Click to expand...
Click to collapse
Can anyone upload MarkinuX Kernel please? Thanks
Ok. Searched forum. Finded way how to get kernel at some nand. Got MarkinuX kernel and now test. Test will be during whole day tomorrow on different conditions.
For kernel extract and install is this thread very good. Helped and teached me.
marcosxd i taked needed files for you and attached.
datas0ft said:
Ok. Searched forum. Finded way how to get kernel at some nand. Got MarkinuX kernel and now test. Test will be during whole day tomorrow on different conditions.
For kernel extract and install is this thread very good. Helped and teached me.
marcosxd i taked needed files for you and attached.
Click to expand...
Click to collapse
Thanks, I just finished downloading the whole Markinus rom to extract kernel haha but you saved me... will test and report, thanks
datas0ft said:
Ok. Searched forum. Finded way how to get kernel at some nand. Got MarkinuX kernel and now test. Test will be during whole day tomorrow on different conditions.
For kernel extract and install is this thread very good. Helped and teached me.
marcosxd i taked needed files for you and attached.
Click to expand...
Click to collapse
Quick question, the zip file you gave me only has two .ko files and zImage while the original rafdroid kernel has like 5 .ko files... what should I do? copy raf's kernel .ko files missing into markinux ones?
Or just pack the zip file using two .ko files? Thanks
I cant ansver. Dont have much knowledge on this. I followed instructions. This taked to me these three files. I installed these.
I finded some problems right now (wifi and gps dont work and my 3g too). This may not happen at kernel side. I have made some changes on rom side. I go replace whole rom and then again kernel. Then i go make final decisions.
I'm having the same problems, you two are not the only ones. This has been really frustrating me lately, and I thought it might have been a problem for only me because I just had the screen replaced. It worked fine in winmo 6.5, now in NAND I'm having some issues. I text a lot more than I actually call, however so it's not that big of a problem for me right now
Hi this is my first post to xda, even though i have been following for quite a while and have learned alot.
the issue i am having is, my camera button has stopped working. i cant use it to take pictures or open the camera, but it does seem to work with the vol. down and power to boot into boot loader.
with that said, i am thinking the button itself is not broken. I mean the button feels fine when you push it, it has the soft touch for focus and then the final push to take the picture. I have flashed tons of roms and it used to work. I cant really pinpont exactly when it stopped working.
i would live with this problem if there was a way around using the camera button in clockwork recovery, but from what i have read, there is not.
i want to install rooted GB. to do this, i need to sbf back to froyo (which i can do now), then flash the leaked GB .595 or .596 which you are probably aware of (without the camera button, i cannot perform the 2 part install).
Has anyone else ran into this problem? I read in another forum that someone else had a unresponsive camera button, they installed the Verizon OTA GB and the button worked again. I have tried this, it did not work for me. But if it worked for someone, there must be a way to fix it. I just have no idea myself. Hopefully someone will be able to point me in the right direction. Maybe even create an update.zip to correct the issue (i know this might be asking a lot).
Thank you.
i have the same issue. i can use it to boot into boot loader, but then it doesn't work. I can't use it in the CM recovery menu nor to activate the camera or snap pictures.
I called verizon and of course they said its defective that it needs to be replaced. But if somebody knows how to deal with it without replacing the unit please feel free to post your ideas.......please?
This is a hardware issue, and to my knowledge, there's nothing to do to fix it.
I'm sorry to say, but I believe you need a replacement
I had to do the same thing too. There are lots of reports of defective camera buttons on the X. And, there is no way to use CM Recovery with a broken camera button since you have to use it to make your selections. Believe me, I looked for workarounds and found none. Fortunately, there is a year warranty and I received a replacement the next day after calling Verizon. The replacement was already on GB, so I just SBFed it back to .340 and went through the P3Droid upgrade process. Finished up by restoring my apps I made with Titanium Backup (the replacement X doesn't come with an SD card or batter, you use your old one). Now I have an X with a working camera button.
I have a Viewsonic Viewpad 10s and some problems with the screen, I flashed at first the version Vegacomb 9n + Update 3. At the beginning it was wonderful but then the screen does not work properly. Even after a reboot did not care much. I went to ClockworkmodRecovery and flashes Honey Ice, it was back to normal. Some time later came the same problem, can someone tell me what it is?
The other question is, what ROM is to recommend the best? The tab is a Christmas present, I do not want to have again after 2 days because it is not reasonable ...
I am in a German forum, but there are not really someone who has the problem with the screen ...
Megamanwwh said:
I have a Viewsonic Viewpad 10s and some problems with the screen, I flashed at first the version Vegacomb 9n + Update 3. At the beginning it was wonderful but then the screen does not work properly. Even after a reboot did not care much. I went to ClockworkmodRecovery and flashes Honey Ice, it was back to normal. Some time later came the same problem, can someone tell me what it is?
The other question is, what ROM is to recommend the best? The tab is a Christmas present, I do not want to have again after 2 days because it is not reasonable ...
I am in a German forum, but there are not really someone who has the problem with the screen ...
Click to expand...
Click to collapse
I had the same problem with my Viewpad 10s with Vegacomb, HoneyIce and newer roms. One of the original issues was using it while it was plugged into the charger the screen became either unresponsive, or would randomly apply keystrokes that were not touched. Two people posted solutions, heating the outside of the tab with a hair dryer, and putting more pressure on the tab (squeezing the case) as you were touching the screen. I did find the extra pressure did help, but it was crazy trying to get the pressure just right. also noticed that screen worked differently in portrait and landscape mode. I often had to use portrait mode to slide the unlock across, while landscape would not allow the tab to unlock.
I decided to "downgrade" the rom to stock, it worked, then to modified stock, it worked but had some touchscreen inconsistencies, then to Corvus 5 rom, which I read somewhere solved other peeps touchscreen problems. Once I got Corvus 5 up and unlocked, I used his screen recalibration tool in apps and everything works perfect. I've been up and running for a month with no touchscreen problems. I even backed up Corvus 5, and tried Vegacomb and HoneyIce again. They worked for a couple of days, and then tab went back to touchscreen issues. I'm thinking it's a kernel sensitivity issue, but I'm know expert, and it's not happening on enough tabs for devs to take as a serious issue.
Hope this helps!!
you are one of the lucky ones man..i tried Corvus 5, true the method you described and still have the issues, well..actually i tried every single Rom and no luck.
I know it's mostly a hardware problem, the only differences in Rom's is the heating they produce, some more, some less..so depending on how bad your case is, you might find a balance and make it work for some time..or no time..
By the way, anyone knows if it's possible to disable the touchscreen inputs, from terminal, adb commands or maybe some app?
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..