Database Users

Universal Crashes A LOT ! Help :S

hello Everybody
returning Universal user, just bought one used from a store, then a just whent on trying a lot of different Wm6 roms but they all had the same problem on my Uni, they ALL crashed by either freezing or just "turn off itself".
then after some time using the rom it crashes hard that it cant be turned on then it crashes at the boot screen.
i would like to get the original Wm5 rom back but where to go for finding it?
Regards
Prosasan

There are more mobile providers which sold Uni, so there are more factory WM5 versions. Personally I'd recommend the TMobile one. I'm sorry, but at the moment im using my notebook, and i dont have the ROM here, but i'll upload it somewhere ASAP

THX !
That would be absolutely GREAT !
i've been "forced" to use my Kaizer instead of my uni these last couple of days
but mine is from denmark, which was branded by Sonofon, but i would rather have some kind of "clean" unbranded version, by the way are there any difference between a branded and one that isn't ?

Found a Version of wm5 that is clean
so i think that i wont need the one from t-mobile, but we will se how it evolves
anyways how to support 4gb in wm5 ?

Prosasan said:
hello Everybody
returning Universal user, just bought one used from a store, then a just whent on trying a lot of different Wm6 roms but they all had the same problem on my Uni, they ALL crashed by either freezing or just "turn off itself".
then after some time using the rom it crashes hard that it cant be turned on then it crashes at the boot screen.
i would like to get the original Wm5 rom back but where to go for finding it?
Regards
Prosasan
Click to expand...
Click to collapse
Welcome to the forum
I don´t think that the problem is caised by a 6 or 6.1 ROM, however try a wm5 and if not corrects try to read the Wiki
And don´t forget to vote!!
Good luck,

orb3000
thx for the welcome, the wm5 rom didn't help it still just shuts down randomly.
wth is wrong with my device argh, i've tried the universal wiki but didn't find anything about my problem.
i've already voted for the Universal

Prosasan said:
thx for the welcome, the wm5 rom didn't help it still just shuts down randomly.
wth is wrong with my device argh, i've tried the universal wiki but didn't find anything about my problem.
i've already voted for the Universal
Click to expand...
Click to collapse
Could be a battery problem issue, test connected to wall charger and see if behaives the same, also remove your sd card and sim to test
Doing this we can try to identify the problem
Good luck,

orb3000 said:
Could be a battery problem issue, test connected to wall charger and see if behaives the same, also remove your sd card and sim to test
Doing this we can try to identify the problem
Good luck,
Click to expand...
Click to collapse
thx for that i have two batteries one that is brand new that make it crash the other one is the original that wont charge more than 50%, but the problem isn't there when it is connectet with my cradle or my charger
the problem isn't there while using the old batteri...

Prosasan said:
thx for that i have two batteries one that is brand new that make it crash the other one is the original that wont charge more than 50%, but the problem isn't there when it is connectet with my cradle or my charger
the problem isn't there while using the old batteri...
Click to expand...
Click to collapse
So that´s it!
There are some problems with your new battery, perhaps not the original
Here on Universal forum there is a member called duke nukem, he claims he sells the original ones, try to buy another battery
Good luck,
And all Uni members!
let´s vote!!!

i see
but the new batteri is Original ? from qtek/Htc

2400mAh battery is not recognised, does not charge

Hi there!
I just got a new 2400mAh battery for my charmer (PM16A; 3.7VDC) and turned the device off to completely charge the new batt. For 3h there was no light indicating a charging progress so I turned the charmer on (no LED signal at all) and the OS booted. The system runs extremely slow and the battery status is not being recognised.
Has anybody made some experience with the bigger batteries or any idea why the system runs but no charging is being done? The battery is explicitly displayed to be fully compatible with the MDA Compact II...
Thanks in advance,
Gore

I called the dealer today and he told me that this battery is well known for causing troubles. I sent it back and told the dealer to keep me informed if any improvements are made by the manufacturer. He also told me that this (chinese) manufacturer seems to be the only one building those 2400mAh batteries, so if you're suggesting to buy one, think it over at the moment...
If I get any information about the issue I'll post it here.
So long,
Gore

What ROM is on your device? The batdriver.dll can cause such problems. What is shown? -1%? And what size is said? Does it say 0mA or 2400mA?
Give me infos I'll try to help you with my "how drivers are" skils.
Edit: Seen post now. Can you remember any answers on my questions. Cuase I think it would help others too.

I have cYBERDEls WM6.1 Manila 2d German Ed. installed. It runs perfectly with my old battery, fast and stable, but the battery turns off at 60% (4 years old - no surprise I guess). With the new one it seems to charge, although no orange light present. When entering the battery status in the OS, it said something like status unavailable or battery unavailable. And it runs extremely slow which it does not with the old one.
I'm sorry I cannot say anything about the current size, as the battery status driver of that WM6.1 version is unable to display...
I tried the Battfix.cab as well just to make sure but no change.
Thanks for helping,
Gore

OK that is a batdriver.dll problem. I'll upload some versions later or tomorow. Just try them.
And if you installed batfix.cab it will charge without the light, But the power you're using can also be the power with witch it came. (They are charged to 50%-80% to live long without being used)

-> "I'll upload some versions later or tomorrow"
That would be just great. Lucky me, I didn't actually send the package away yet, but will rip it open again
Which problem is solved by the batdriver.dll?
Btw, good luck with your 6.5 development, I'm really looking forward to it!

The batdriver will hopefully recognize the battery. (I'll give you Prophet and Wizard ones cause they suppoert only the big batteries I think). And WM6.5 will first just be English. Cause I have to translate everything manually to German.
Hope I can fix your problem.

Hey anything new about the batdriver.dll? Did you upload it somewhere or could you post a link to a proper driver in the Prophet or Wizard section if there is one? Sorry for shoving you...
Gore

Soory now time till now. I'll try to get some today or tomorow and post them here.

Signal problem!

Helle xda
I have a signal problem on my Blackstone. Let me begin from the beginning. Firrst of all, my mom and dad had HTC HD aka. Blackstone, and I use Nokia N97. My moms HD stopped working (Touch screen issue), well she leaved it alone and now it is somewhere in the house. My dad bought Leo and gave the Blackstone to my mom. But the problem starts here, my fathers "old" phone, HD loses the signal when you are in a middle of call. First time, when my mom told me it I thinked that maybe was becouse of her SIM card, and she ordred a new one but the problem is still there. Today I got the HD from her, he bought her self a LEO Now, I have the Blackstone but it still haves the same issue, I called one of my friends and told him that I was going to try to find what the problem was with this phone so I sett him at loudspeaker and watched the phone while we was talking. So, I figured out the issue. The signal of phone studdenly falls down to zero (I mean the signal indicators) then it reases, and I can make a call again.
This phone has NEVER been modded or what you name that stuff with costum ROMs etc. I updated to the lastest official rom from HTC but the problem is still there. I use Norwegian rom, but if English one or Turkish one can fix this issue that's okay too. Sometimes it take 2 minutes before it happends other times I can talk up to 5-6 minutes. Acctualy, I have never hanged me on how long it takes my phone to "crash"
The thing is now, is this an physical or mental damage/error/issue ? (Of course, I mean the Blackstone)
And, I am sorry for my english, it is acctualy my 4th language.
I would be happy if someone here can help me about this, thanks for reading
Information:
ROM Information: 1.56.409.0 (43972) NOR
ROM date: 03/09/09
RadioVersion: 1.13.25.24

Hi there,
How old is your phone exactly? Have you considered having the device replaced if it's under warranty and insurance contract?
Other than that, you could try flashing to a different Radio version as this can resolve many issues with reception, battery consumption, call quality, GPS signal strength, heat issues, etc. You can try another radio version to compare and see if this makes a difference.
Please note: if your phone is under warranty, by flashing to a new Radio version that is different from your stock Radio version, this will invalidate your warranty. However, you can always flash back to your stock radio version of you need to send it to HTC repairs.
For more information on flashing to a new Radio version, please see this link.

Hey there, thank you for your answer!
I cannot remember when exactly I boght my phone but, it has only:
28h. 34m. and 56s. As incoming calls
and
30h. 48m. and 25s. As outgoing calls.
Maybe about 1 year old?
However, this is very low valuves, I got about 91h (Yes, I konw it sounds crazy) last month with my SE P1i.
I can try another Radio versions, can you prefer anyone ? Or is it like, I must test and find out what is best for my Blackstone ?

tuηay said:
I can try another Radio versions, can you prefer anyone ? Or is it like, I must test and find out what is best for my Blackstone ?
Click to expand...
Click to collapse
Just flash the newest radio first, and if that's no good... move down the list until you get one that works fine.

stuntdouble said:
Just flash the newest radio first, and if that's no good... move down the list until you get one that works fine.
Click to expand...
Click to collapse
....and don't forget to match rilphone to radio
Rick
p.s. ther is no rilphone for radio 1.7 so you'll need to use ril 1.4 as its the latest

Fallen Spartan said:
....and don't forget to match rilphone to radio
Rick
p.s. ther is no rilphone for radio 1.7 so you'll need to use ril 1.4 as its the latest
Click to expand...
Click to collapse
If they had read all the details in the radio thread and stickies before flashing a potential brick inducing file, they'd know all steps needed to be safer and flash correct files. Afraid i've stopped giving baby steps info to people when it's all in the stickies. I'm so jaded now...

stuntdouble said:
If they had read all the details in the radio thread and stickies before flashing a potential brick inducing file, they'd know all steps needed to be safer and flash correct files. Afraid i've stopped giving baby steps info to people when it's all in the stickies. I'm so jaded now...
Click to expand...
Click to collapse
Yeah, but mods have to be patient with all though I agree with 99% of your comments lol

tuηay said:
Hey there, thank you for your answer!
I cannot remember when exactly I boght my phone but, it has only:
28h. 34m. and 56s. As incoming calls
and
30h. 48m. and 25s. As outgoing calls.
Maybe about 1 year old?
However, this is very low valuves, I got about 91h (Yes, I konw it sounds crazy) last month with my SE P1i.
I can try another Radio versions, can you prefer anyone ? Or is it like, I must test and find out what is best for my Blackstone ?
Click to expand...
Click to collapse
no worries mate, as he guys have suggested above, try flashing to another Radio version with matching Rilphone version and stick with the Radio that hopefully works best for you.
If you have any other queries, just ask
Best Regards.

Thanks for the replies guys. I am going to try to flash my Radio a.s.a.p. and ofcourse let you know the result

[Q] Qtek 2020 (HTC Himalaya) Backup battery problem

has anyone esle experienced this, i have recently upgraded form sun dream's 21169 rom to aeroflylubry's 6.5.23420. Ever since upgrading, my fone keeps losign the time wne i remove the battery or reset with the reset button, always resets to 1 jan 2009 and 1200 for time, i never had this problem with the old roms, and the battery meter says my backup battery is 100% still good, have replaced with a new one and still i get the same thing. is it a rom problem or my himalaya is now for the rubbish dump?

i am using aeroflyboys ROM and have not had any problems at all. hope this helps
regards Jon

jonathan.gadget said:
i am using aeroflyboys ROM and have not had any problems at all. hope this helps
regards Jon
Click to expand...
Click to collapse
correction:
aeroflyluby
thanks

sorry my bad spelling didn't mean to offend anyone.

Definately something with the newer roms
I have rolled back to Sun dream's 21169 - (still the best ever rom for the hima IMHO) and i didn't have this issue, also tried the stock Hima rom (must be wm2003) i had time persistence in that rom, even C_Shekar's 6.1 (nostalgia) had time persistence. More recently have used Sun dream's 28205 from the kitchen - no time persistence there either, this one resets to 10am on i Jan 2010.

[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