Related
Help me please!! The 'Phone Pad' input method will not work for my xda exec. When selecting it, it stays on keyboard method (or reverts to it if it was on, say, transcriber or block recognizer mothod) Does anyone else have the same problem? My hunch is that it's a bug which will affect some but not all, depending on the ROM version you are running. Could anyone who owns one do a quick test and let me know. I tried both soft and hard reset, no solution with either. Thanks.
Just tried it...wouldn't change to phonepad as well. But after a soft reset, it worked.
its a bug,
workaround , if all else fails soft reset.
change to portrait.
select a different keyboard option not phone one. exit app. goto app and now try - it works 6/10.
I have the same problem...
Don't want to go off on a rant here, but I have pretty strong feelings about a device that gets released with such an obvious bug with such a key piece of functionality. I'm pretty sure it's a memory issue - with a fresh personal install (i.e. with O2 active running - O2's recommended install), the phonepad works until I soft-reset the device ONCE. Then it fails to open and I can't get the work-around to work. I can reproduce this again and again.
Are there others, or is it just me who gets offended when I get charged money for something that is so obviously broken?
@daveb1976, I'm with you on this. I suspect I paid even more as I have a JJ and they are more expensive than the O2 Execs. Having used Nokia, SE and Palm devices I've got a good idea of what one should expect of new devices and I have to say the JJ reminds of the SE P800 - this was an innovative and high profile product three years ago but it was not complete in many areas (but most s/w issues were fixed after about 6 months)
Yup. I appreciate that it's a new device, and I do expect that there will be kinks. But one of 5 input methods simply not working is not a "kink". Besides, unless I'm wrong this is part of WM2005 which is version FIVE of the OS. Oh well, I bought one, so I guess I'm as guilty as the next guy when it comes to putting up with MS's rediculously low quality standards.
The workaround worked once but now I can't get it to work again. I've also noticed another strange bug. Try this....When downloading a couple of new today page themes (from the microsoft pocket pc site) and copying them into my windows folder, I was pleased to see they were available when I went to settings/today menu. However, choose any of them and the things slows up ridiculously, fails to display any contacts at all and won't select task manager (I was going there to try and shut some things down because of the speed problem).
Only a soft reset will bring things back to normal. I agree with the posts by daveb and jah, it's not acceptable to charge top notch prices for new contracts and upgrades (I was the latter incidentally, at a cool £229.99 to upgrade)
Anyway, I'm not prepared to live with it for that price so I'm calling them now. I'm on 8 days since I received it but the 14 day thing is irrelevant if the goods aren't working right? What do you guys think?
I'm looking for a hefty credit to my account to offset the upgrade price or a different handset and my 229.99 back. It's a shame as I love the 3G and wireless capabilities but it may be a case of releasing it a few months too soon, for O2 at least. They have probably been concentrating their efforts on yesterdays takeover!
Anyway, I'll post back with my result.
I got the same problem,
Beside, I can't change today backgronf theme in this Exec.
Any new upgrade for O2 Exec ?
Somebody said that "Phonepad" problem for O2 Exec is a bug and a new version will be out soon and the problem should be gone.
Anybody get the upgrade yet ?
Any new upgrade for O2 Exec ?
Somebody said that "Phonepad" problem for O2 Exec is a bug and a new version will be out soon and the problem should be gone.
Anybody get the upgrade yet ?
If you'd be so kind, just to clarify the following.
I've got an Orbit II, with Copilot. Yes it does feel as if one is part of a club, but there's the topset and the thick kids... I'm the latter.
As I understand it, the Hard SPL unlocks the phone, from it being tied to a mobile network, right?
The O2 II isn't locked so then I don't need it, yes?
Therefore, I can either install all the tweaks and tips thus keeping Copilot, or put another ROM, (is this a type of disk image?), with all the tweaks and tips built in, on it.
In which case I'd lose CoPilot, for I'd have written over the device and voided the warranty, to boot, right?
What actually is the difference between a ROM and all the 'tweaks and tips'.
Is it because if you need to Hard SPL (ie unlock a phone from the network), then you don't have any built in functions left, so you couldn't install the Tweaks and Tips, which would in effect bring all the same advantages.
Look, I know Bebe has managed to do a version of WM6.1 which features threaded SMS and everthing, but I'm still not quite with it, I'm afraid.
The wiki entry for "What is a Hard SPL", just says it's one way of not trashing your phone. Not trashing your phone before you attempt what though?
For I've seen mention of the SIM/CID unlocker as if it's a separate entity, indicating they are two distinct things, created for two different tasks.
I like the idea of the phone looking funkier and working better (God knows what the AMMD is for the Video, but I know there are issues with the video, so having that sounds like a good idea as well. Right?)
Whatever it all is, it sounds like it's been a mammoth job/labour of love and has involved the purchase of two new Polaris phones, but beyond that, I'm all at sea.
(Dons bullet proof vest and climbs into protective Pope Mobile)
I think the fact you are asking all these questions juxtaposes that you should not flash your ROM. I myself am in your class and just look on with admiration. With that said, there are many things that you can do to your phone to "spice" things up. I have bought a couple of programs, Astronavigator II, (tells you what the sky at night is above you, My Girlfriend loves it), Fun contact, much more finger friendly than wm6. I also have PZP program. It automatically sets my phone to do things at certain times of the day, i.e at night it switches off, emails and phone calls then do not wake me and GF up, much to her relief! So there you have it, oh btw I have tomtom as have the TC.
The phone works quickly, efficiently and never have to soft reset. 5 years of using WM devices, I have found that idiots like me should just live and let be and use the phone as it is.
This should anser none and all of your questions
Kind Regards,
Will
unfortunately you have discovered HTC
Hey,
I hear ya. I am fat boy too. lol
I can't keep up and these forums use a form o speak, and implications that are not clear. I have no idea of why one of the cubes is called a bunch of letters for instance. unfortunately, we want our phones up to date, and the fastest they can be. But it is not that simple. I agree, I am lost on the spl thing and the sim, but then ??? it is not that clear to me.
Here is how I understand it. It may not be right, but it is an analogy that seems to work. A soft reset is reboot, a hard reset in a wipe/reinstall. As I understand it, the rom is the basic operating system, meaning when you hard reset, that is what loads into memory. Once it is loaded, it can be soft reset ie rebooted without harm. The rom is kept on the device, so when you hard reset, it can reload/reinstall itself without needing to be connected to anything. Disk Image? I guess. If your original rom, from the manufacturer installs copilot with a hard reset, then you will keep copilot. When they cook a rom, they change those installation files permanently. They adjust things, and remove things. they alter hardware drivers per say ie the radio patches you get. If Copilot is not in the cooked rom, then you would lose Copilot. You would need to buy it or download it and install it yourselft. You would have to use a restore disc, hooked to a computer and mobile center, to overwrite a cooked rom back to the original rom in this cases wm6. ROMS are much more of a big deal, as there are bugs and some things don't work as expected. They are faster tho, imho. Tips and tweaks are just that, certain replacements and other alterations. I woul think most tweaks I have seen generally do stay with the device thru soft resets, some don't if you have to hard reset. I keep my tweaks and settings/programs on the storage card incase I have to hard reset. Hope that helps, it may not be correct, but it works for me as a basic understanding level. There is a way to chose what you install as the rom (ie operating system permanently on the phone for hard resets), and i think the term they use is the kitchen. Using the kitchen, you chose this piece of a rom, and that one, etc....all that goes to the permanent part where a hard reset tell it what to read and install. I am not too clear on that one myself. I find using a kitchen fightening and wrought with risk at bricking.
Will has summed it up pretty well.
We buy these phones for what they can do, and they are just not supported by manufacturing like they should be. Our expectations are flavored by the continual upgrades from things like MS and windows upgrades fixing and patching things. I have had two pda (one previous phone). Either manufacturer was the same, limited upgrades and basically no further development on the devices.
It was a harrowing experience to upgrade my phone/pda to wm6 out of fear of bricking it. My phone came with wm2003. Bricking if you don't know, is leaving your device in an usable state...it is caught in limbo somewhere, and will not work.
Advice, wait a while, keep reading. Since things are hard to understand, keep reading and don't be in a hurry. Eventually someone will ask a question, in one forum or another, that inadvertanly answers one of yours. Check out the hacking forums, nice tweaks in there. And yes, they kinda of leave out steps. Keep Pocket Controller, it lets you tweak the registry, and see your device on your desktop. Even MS was impressed, troubleshooting a bluetooth issue. MS loved they could control the pda themselves using remote desktop. MS sent the name of that progie up the chain of command. They loved it. You can screen shot and all sorts of things. It come in handy trying to explain things. Once you feel you can risk losing the phone/device, then consider upgrading to new rom and try some of the tricks/tweaks. I know I don't want to waste 700.00 or more dollars to brick something. I think most of the time, they can get the bricked phone back, but not 100% certain of that. I study the reset and etc procedures and print them out, before I muck with the rom. I consider what I do to the phone very carefully. I was so scared I would ruin my phone.
And the other thing i say, is if you tell people you are a noob at this stuff and have a hard time understanding, they generally won't flame you too hard. Really. Just explain yourself, and give your disclaimer, and they won't be too hard on you. As you have seen, they may not fully explain things as clearly as you like, due think that is just the nature of the people and the way they think, not a personal attack or lack of anything, but they won't be rude.
As you said, this forum is run by the topset, and we are thick ones. They do astounding work and some of us just look up at them and admire. But they will help you. Keep reading, and keep trying to understand, it gets better with time. And don't be in hurry either. I see two post already of people bricking their devices already. And one guy seriously bricked his to the point of no return it seems.
ukdutypaid said:
Therefore, I can either install all the tweaks and tips thus keeping Copilot, or put another ROM, (is this a type of disk image?), with all the tweaks and tips built in, on it.
In which case I'd lose CoPilot, for I'd have written over the device and voided the warranty, to boot, right?
For I've seen mention of the SIM/CID unlocker as if it's a separate entity, indicating they are two distinct things, created for two different tasks.
Click to expand...
Click to collapse
As I understand it (and I've loaded HardSPL + a modified ROM on my Polaris), the SIM/CID unlocker is for those devices that were purchased from a telco and therefore locked to that company (pernicious behaviour, btw, but they offer low purchase prices to tie customers in). If your device was unlocked at purchase, then this issue doesn't bother you.
The HardSPL load is designed to prevent you bricking your device with a crook modified ROM - this obviously pre-supposes that you will load modified ROM's. If you want to do this (ie. try modified ROM's), then loading HardSPL 1st is a no-brainer.
Why would you want to load a modified ROM ? The short answer is that the marketing depts of the manufacturers load the devices with all sorts of fluffy software crap. They do this in the released ROM. So to remove this junk - and have the device fast, responsive and with enough room left to do what you want - the gurus here modify these ROM's. [Of course, some people like the fluff]. The manufacturers also occasionally release ROM upgrades, but development is done mostly in forums like this.
CoPilot 7 ? Yes, flashing a new ROM will kill this, because the DeviceID changes when a new ROM is loaded. But if you visit the CoPilot website before loading a new ROM, you can deactivate your current license and then reactivate it after installing on a "new" device. In fact, CoPilot is one of the few commercial apps to cater for ROM upgrades with honour. CoPilot doesn't care how many devices you install on, just that only one at a time is actually capable of running.
Here are your acronyms to understand what they are doing and talking about. This may not be right, but alot of this came from the Hermes. It seems someone was looking to run linux on his hermes i think. I am still kind of digesting this information now. Remember I told you look around?
Here are your definitions to help you understand.
AKU - Adaptation Kit Update: they usually patch up existing bugs and enable several new features. Each newly released AKU pack retains fixes found in previous versions of AKU
CID lock (aka vendor lock): put on your device by the manufacturer to prevent installation of a ROM not released by them. CID is a vender lock, the post above talks about that. It is placed on you phone to deliberately prevent you from changing the rom. It is vender specific it seems. I assume the Super CID tells the device to ignore that lock or overwrite the vender lock all together, or it might just tell it to ignore the error code. That is what I am seeing. This seems basically related to full administrator priviledges account for the device. it seems the CID was located on a secure area on the radio. People had bad flashing to the radio upgrade and corrupted their CiD essentially bricking some of their phones.
RIL - Radio Interface Layer.
RUU - ROM Upgrade Utility: Its the s/w used on your PC to do a ROM upgrade for your PPC. I assume this can be the default utlity or a kitchen program. The default you can find pictures of, it is generic and just tell you are flashing. The kitchen program, i canceled once, had options to choose.
IPL - Initial Program Loader: Its the bootloader for PPC. It boots up SPL. Bootloader. Basic operations.
SPL - Secondary Program Loader: By inferenece only? Hard SPL then stands for a forced control over the secondary Program layer. You can make it load something else when it boots. It seems the newer factory SLP would want to reference the CID or only properly signed files, thus limiting what you could actually do with your phones.
WWE Edition - World Wide English Edition
XIP - Execute-in-Place
It seems while trying to unlock the Hermes, they were using a radio upgrade and somehow got this Super CID. See above about CID. So it seems there was a reverse engineer done with a legitmate unlocker program. This unlocker program was installing certifcates and changing the device to a lower bootloader it seems. That bootloader ignored the CID or converted it to full priviledges. they also figured out, some bad flashing can be undone....the CID was stored in a secure area on the radio. A bad radio flash corrupted part of the CID. Once they converted to a different bootloader, they could reflash radios...thus unbrick some phones. They have replaced the bootloader with this Hard SLP. The new SLP converts or tells the phone to ignore the CID when upgrading a ROM or other things. It appears HSPL v1.13 also keeps track of bad blocks of memory. That version also reflashes bad blocks or corrupted files with fresh versions as well. It also respecs completely bad blocks, i am thinking that means, the os is not allowed to write there. The you can reflash anything to the device. Or so it seems. But again, depending on how bad you muck up your phone, some things are not repairable.
That is what I am seeing right now. Still reading. It is all out there. Just google the terms above, and slowly you will find the threads and start piecing it together.
Seems this Hard SLP is important for ROM ugrades. Still reading about it. I am post like 500, out of 1000, and trying to keep track of it is difficult. Lots of interjections of what people did wrong. Very confusing.
I did tell you read, read read, and you will find the answers to your questions, it just takes awhile and it hard to understand becuase of the lingo.
v nice. u guys need to read som basic stuffs. it will help u, & u don't have to worry about u,r phone. u can upgrade, u can change things with full confidence. xda-developers have wiki pages, i think it will help much. keep readingggggggg. soru 4 my english
You won't lose your copilot if you use the original HTC ROM....I put the original HTC ROM (which is much better than the O2 ROM)...added a few standard registry tweaks..runs NICE..reinstalled Copilot7 (from the 2577 folder on the SD card) reactivated it..(did not need to deactivate it) and everything is fine. If you need to got back to the original ROM for whatever reason...reflash it and then flash with originalSPL file.
You can reactivate copilot as many times as you like (the only thing I do before reflashing...mor as a precautionary measure...is backup the SD card)
If you use a cooked ROM ..then I think you have to deactivate Copilot and reactivate it on the new install.....but I'm sure the experts will know better.
pistonripper said:
If you use a cooked ROM ..then I think you have to deactivate Copilot and reactivate it on the new install.....but I'm sure the experts will know better.
Click to expand...
Click to collapse
Agreed - I've had to do that a number of times, from both modified ROM changes and device changes, but it's easy and painless.
Thanks for the indulgence...
People, I'd like to thank you for taking the time and trouble to provide your very useful responses. One does read of course and things like lego bricks begin to click into place. I don't even have a car, so quite why I'm so obsessed with CoPilot, I don't know. Okay I giggle when listening to one of the ladies (through headphones), on the bus, but other than that.. lol.
I didn't know you could actually download CoPilot from the site though, I'll check that out. I've 'funked it up' a bit using the HTC Home cab and Slideunlock. Tempted to play with one of the Cube .cabs...(The one it comes with is pretty rubbish if you can't change what the cubes link to and the icons)
Yes, Yes I'll search for the original O2 rom, before I play anymore...
The actual HTC rom, sounds like a safe bet though, cos then you get the proper funky screen..
Don't want to clutter (anywhere actually) the hard core threads with stupido questions. I'll look, I'll read, I'll learn...
As one of you has said, these things aren't toys (lol) and I don't want to be left looking at a $700 £350 quid (non contract Orbit), that I can't use...
I think Bebe wm6.1 is going to stay undownloaded for the time being!
I'll leave the topset, to carry on.. Wouldn't mind getting rid of the "Streaming Media", program mind. Errr, it does/streams what exactly, anything at all?
Hello - I've been searching these forums and the wiki and Google too looking for a solution to this but so far, can't find a solution so hope members here can help:
I recently got another XDA Exec and a week ago, the phone mic stopped working. I know its not a hardware problem as the phone can record my voice for notes.
I've done a few hard resets and each time, nothing changes, so am truly baffled.
I'd be very grateful for any answers to this, and apologise in advance if I have missed an answer that has already been posted - I have tried searching, honest!
Cheers,
JB
Jon Brown said:
Hello - I've been searching these forums and the wiki and Google too looking for a solution to this but so far, can't find a solution so hope members here can help:
I recently got another XDA Exec and a week ago, the phone mic stopped working. I know its not a hardware problem as the phone can record my voice for notes.
I've done a few hard resets and each time, nothing changes, so am truly baffled.
I'd be very grateful for any answers to this, and apologise in advance if I have missed an answer that has already been posted - I have tried searching, honest!
Cheers,
JB
Click to expand...
Click to collapse
Try another ROM...perhaps?
I could do, but before I attempt anything like that - something I've not done before - I wanted to figure out how to remedy it with the existing ROM, which is the O2 one installed without all of O2's own stuff.
It was working perfectly well with this ROM before....in fact the only thing I can think of that might somehow have caused this was me pairing the XDA with a bluetooth handsfree set the same day. It might just be coincidence, it might not - I can't tell.
I suppose what I'm hoping for is some guidance re any settings on the device that I don't know about that have caused this, or the necessary registry edit to remedy the problem. Its odd that the phone mic worked before then stopped working, despite hard resets with the same ROM. Forgive my naivety, but I thought ordinary user-level tweaks didn't affect the core settings of the ROM....or am I wrong?
Cheers,
JB
PS - Lower Hutt! I remember seeing it through the mist one day after catching the ferry from the South Island before heading off to Cuba Street for a boozy afternoon...
Yup, got exactly the same problem before buying my HD.
I thinked that my micro was dead and didn't try to fix it before.
Just now i got here to search another rom to test and i saw this thread highlighted
The rom on my universal is TOMAL 8.0 or more i don't exactly remember the version, what's yours ?
I will download another version to check if the micro will be alright and give some feedback
Jon Brown said:
I could do, but before I attempt anything like that - something I've not done before - I wanted to figure out how to remedy it with the existing ROM, which is the O2 one installed without all of O2's own stuff.
It was working perfectly well with this ROM before....in fact the only thing I can think of that might somehow have caused this was me pairing the XDA with a bluetooth handsfree set the same day. It might just be coincidence, it might not - I can't tell.
I suppose what I'm hoping for is some guidance re any settings on the device that I don't know about that have caused this, or the necessary registry edit to remedy the problem. Its odd that the phone mic worked before then stopped working, despite hard resets with the same ROM. Forgive my naivety, but I thought ordinary user-level tweaks didn't affect the core settings of the ROM....or am I wrong?
Cheers,
JB
PS - Lower Hutt! I remember seeing it through the mist one day after catching the ferry from the South Island before heading off to Cuba Street for a boozy afternoon...
Click to expand...
Click to collapse
Could be a range of reasons, from some program install or addition to the software set to files going missing. Trying a new ROM or reflashing with the original (but believe me, once you try new WM6.1 You'll probably never go back) might be one of the solutions. Flashing of ROM is a piece of cake, however, I recommend reading as much as possible on the procedure and ways to remedy the unexpected situations before you begin. Everything you may possibly need and answers to all your questions is contained in a Wiki - have a look and ask questions if you cannot find answers and are completely stuck.
Heh, Lower Hutt is on the opposite side of the harbour, coming from SI.
I reflashed with TOMAL 8.9 and micro works very well now
i readed too fast yesterday and didn't see that you're using the original rom, like enigma1nz suggest you, i suggest you too to try a 6.1 rom, it's really great and improve a lot the speed/touch felling/etc for the universal.
Plus it's really easy to flash a rom, it's not necessery to read a lot of documentation,
you just need to connect your universal to pc with activesync (4.5)
and launch the exe file from the rom
Hi everyone,
I have a Imate Jasjam, which has served me well over the last few years. It was running Windows Mobile 5 with the Telstra upgrade that was sent out a while ago. A few days ago, however, I dropped it a short distance, and suddenly the phone function stopped working. Initially I wasn't even able to open up the phone application, but a few soft resets later, that now works. Unfortunately when I start it up, it says "No GSM". There is nothing written in the Device information about Radio version, Protocol Version of IMEI.
I did a hard reset - no joy.
I thought it might be to do with my rom version, so I installed HardSPL, flashed to Black Satin (as I'd always wanted to try that one), but still no luck. The same problems persist.
Does anyone have any ideas what I can do, or am I stuck with a PDA instead of a phone?
Thanks so much for your help!
Paul
My apologies for bumping my own message, but I wondered if anyone had any further suggestions. To clarify, I have tried the various wiki answers, but I'm assuming that because this was caused by trauma rather than flashing that it may well be a hardware issue. Is that a fair assessment?
Thanks again,
Paul
I think thats a fair assessment, its possible the radio may have popped out of its connection. Might be an idea to open up the hermes and check.
If flashing a stock ROM and radio doesn't fix it, then sorry to say but it's busted (unless you can fix the hardware part of it). Have an 8525 with the same problem.
Thank you for the responses. I'm game to have a play with the hardware, but wondered if there was a good guide to getting to know the inside of my phone anywhere. I'd appreciate it if someone could point me in the right direction!
Check mikechennon's guide he provided to deassemble the phones.
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.