Hi,
My Wizard works fine except for one problem: when using it as a phone, the little top center speaker doesn't work; I hear nothing.
(no, changing the volume level doesn't help.)
I can now only use it as a phone by either activating the speaker phone function (which lets everone else around me hear what's being said), or use a bluetooth headset.
Both are not really convenient.
Is there any way to test the center speaker without first disassembling the whole thing? activate it with another program besides 'telephone'?
Maybe such a test shows the speaker itself is OK, so no disassembling needed (but what then...).
Any help is welcome.
Tovarim
System data:
OS 5.1.195 (buiold 15605.3.2.0)
ROM version 3.0.0.0 WWE
ROM date 6/7/06
Radio version 02.47.11
Protocol version 4.1.13.24
ExtRom 3.0.0.0 Molski.Biz
Simlock and CIDlock free.
It has also run the original and updates T-Mobile ROMS with the same problem: no center speaker.
Please check this thread http://forum.xda-developers.com/showthread.php?t=261573&page=2&highlight=wizard+headset+plug
Bluetooth switches off on our imate jasjam's we have at least 10 of them with this issue. When paired with a car kit they may receive a call through the kit then the next call through the device and when they check the device they find Bluetooth has turned off. To get it to re-enable they need to soft reset the device 3 times out of 5.
They are using 2 different brands of car kits.
After researching my bluetooth issues I found the 3518_09 fix for the imates bluetooth issues.
I have installed this patch on 6 or more imates and had mixed results. All of them were the latest official telstra jasjam rom. Some devices now have better connections to car kits with no bluetooth connection issues and a couple of them are now worse. The bluetooth radio switches off and then won't turn back on. If you reset the device then bluetooth will work again. Basically with or without this patch Bluetooth will switch off randomly on the imates. Some devices behaved better after the install and some worse. Frustrating.
Is anybody else having this issue?
Does Radio 1.41 help bluetooth issues at all?
Thanks
Radio 1.41 will not fix my bluetooth issues. I have read that much in the wiki
I also have this issue.
However it seems to be a problem either when I switch off the ignition with the phone in the car kit or remove / replace the phone on the car kit.
I didnt seem to have noticed an issue in the past month or so but since then its getting to be quite a pain. I have to go back into the comms manager and re-enable it most of the time.
I have an M3100
Operator Version 14.123.1.614
Rom Version 1.23.61.4
Rom Date 07/13/06
Radio Version 1.16.00.00
Protocol version 32.53.7018.01H
Thanks
Have updated my phone
Since running the latest Orange Updater file:
SPV_M3100_ROMUpdate_0407.exe from Orange website.
www.orange.co.uk/business/downloads/SPV_M3100_ROMUpdate_0407.exe
This updated the firmware to:
Operator Version 14.211.1.611
Rom Version 2.11.61.1
Rom Date 03/23/07
Radio Version 1.38.00.01
Protocol version 32.71.7020.12H
This seems to have fixed my bluetooth issues. Also the phone is running much faster.
thanks for the info. is it possible just to take the bluetooth drivers from one rom and use them in another? I see that the 3518_09.cab has a bluetooth driver in it (i assume that's what it is) so maybe that is one of the files to look for. any help?
I have extracted the files from the rom posted above. I am going to try replacing btagext.dll, bthuart.dll & serial_btur.dll.
Hi ,
I have a Wizard (Qtek 9100) with WM5 and I wanted to upgrade to WM6.
So I followed the tutorial from Wiki, and managed to upgrade to BlackDiamond 3.1 Touch, I was happy and then very sad when I found out that there is no sound from speaker, but it works with earphones.
I searched the forum and found that
There's a little connector in the earphone slot which bends in the way its not supposed to bend which in fact causes the effect that the phone thinks the earphones are plugged in.
Click to expand...
Click to collapse
but I never used the earphones before.
The sound went off in the update process, but I didn't notice at which step.
Initially my Wizard had
WM5
ROM : 2.17.7.2
RADIO : 02.07.10
IPL : 2.17
SPL : 2.17
The step I followed from the Wiki :
1. Install "Button ROM"
IPL become 1.01
SPL become 1.01
RADIO become 1.12.10.0
OS 1.5.4.2
PROTOCOL 4.0.13.23
2. I used "Lokiwiz 0.2b" Tool to SIM Unlock and CID Unlock
IPL remain 1.01
SPL become 1.01.0000
3. Install "T-mobile Official WM5 ROM"
IPL become 2.26
SPL become 2.26
RADIO become 02.25.11
OS 2.26.10.2
PROTOCOL 4.1.13.12
4. Upgrade to IPL/SPL 3.08
IPL become 3.08
SPL become 3.08
RADIO remain 02.25.11
OS remain 2.26.10.2
PROTOCOL remain 4.1.13.12
5. Install "BlackDiamond 3.1 Touch"
IPL remain 3.08
SPL remain 3.08
RADIO remain 02.25.11
OS became 11.0.0.1
PROTOCOL remain 4.1.13.12
Since I did not move (dropped, disturbed) the Wizard from it's place during the upgrade procedure, I think that the sound problem is software related.
And another question, I noticed that RADIO version remain the same from WM5 to WM6, it's normal or should I upgrade the Radio ?
Edit: I upgrade to Radio 02.47.11, still no sound!
Edit: I tried to call my brother, the mic works and also I can hear him loud and clear from small receiver. But when choose "Speaker On" still no sound!
Does someone has the "Diagnostic Program", so I can run speaker test.
Any help and suggestions appreciated!
Speaker sound lost also
Sadly, the same happened to me with my HTC x7500. I still have not found a solution, but will keep you posted if I do.http://forum.xda-developers.com/images/smilies/frown.gif
speaker sound lost 2
I have a dopod 383pro (i think the same as a HTC Hermes) upgraded to wm6; sound was fine. I then did 2 things in a row & lost normal speaker sound.
I tried about 4 different Blue Tooth (BT) enabling protocols or hacks to allow me to listen to music through my mono BT headset, & dropped it from waist height. the speaker didn't work after that, & I assumed the drop did it. But recently I realized that the Hacks like BT Audio & Navaudio etc may have affected the registry in such a way as to disable the speaker. The BT audio works well. I then found by "accident" that the speaker actually works if I (continue to) push down hard the "connections" button under the On/Off button. This is quite touchy & difficult to maintain. Any ideas?
hermes soooo. why are you posting???
twice... the same answer.... dont duplicate threads!!!! this was asked twice!
I wish you to make a little experiment! please make somebody calls you if the speaker dont works and in the earphone it did so blow up in the hole... maybe you have a little trash inside many people has this issue blow up with power... maybe you can get a preasure air can. so... if not maybe the rom is upgraded an loaded bad re upgrade the OS... if not.... open up your wizard and be sure your speaker are conected to the motherboard... if not you are screw up!!!
Hello buddies,
this thread is about some strange behavior of bluetooth with current energy roms. details follow...
why a new thread?
I decided to start a new thread, because it leads to nothing to discussing this topic in the main thread ... found some people who shares my sorrow, never the less there was a lot of users who hit the answer button on page 1 and report "problem xy" or "hell yeah what a nice rom"
what is the problem?
I'm not able to pair my TouchHD with my car's Hands Free system. A2DP works fine, but when I turn on the Radio Unit a small blue headphone symbol blinks in the statusbar of the phone - no pairing succeeds. If I switch to BT audio, a black headphone symbol stays resident and the media player opens for playback, so A2DP works. Installing SIM access profile on roms without built in rSAP or other various tools in addition doesn't make it work. [see "what have been done" section!]
Just used the latest MIRI-Roms (discontinued) and it works like a charm for me. After initial setup, Hands Free (version 1.5) and Wireless Stereo where installed and activated - Serial Port left out unchecked. Then a popup message informs me, that a BT-Device is trying to access phones phonebook remotly - all went fine.
as reported by other users, this behavior occurs since ~may versions of energy roms...
about the environment
Using energy's rom on TouchHD [Blackstone] T8282 [BLAC100 32M]
flashing with USPL
phone's SPL: stock SPL-1.54.0000
radio: 1.12.25.16D3 - don't see a reason to update
protocoll: 52.60.25.33U
carrier: O2 GERMAN
what have been done so far?
I've tested the pairing of my device in various cars
tested with my Renault Megane 3 integrated car kit (arkamys audio / parrot)
tested with a 2010 Toyota Prius car kit
tested with a subaru 2010 car kit
tested with Blaupunkt Toronto 400 BT head unit by phitsc
I've tried programs, suggested by the xda community
installed Bluetooth_SAP_Profile.CAB
installed BT_SAP.cab
installed Gooru_Sense_BT_A2DP_Fix_Cab_by_JVH3.CAB
installed HeadsetFix.cab
installed JetBTHFExt_1.40.CAB
reg-tweaks on "HKLM\Software\Microsoft\Obex\ObexServiceMask"
roms tried
Miri_WM65_21891_Premium_Manila_2.5_V20.0_NoHtcMessaging.rar
Miri_WM65_21893_Premium_Manila_2.5_REV22.0.rar
Energy.BLACKSTONE.23563.Sense2.5.Cookie.HomeTab.Apr.23.7z
Energy.BLACKSTONE.23566.Sense2.5.Cookie.HomeTab.May.01.7z
Energy.BLACKSTONE.23569.Sense2.5.Cookie.May.16.7z
Energy.BLACKSTONE.21903.Sense2.5.Cookie.May.16.7z
HD_Miri_6.5.X_23541_SENSE25.rar
Miri_WM65_21893_V38.0_Premium.rar
Energy.BLACKSTONE.23569.Sense2.5.Cookie.May.22.7z
(green indicates a working rom)
dear community...
please use this thread wisely for recommendations or suggestions on this topic. keep this thread a productive discussion. if you have a contact to NRGZ, feel free to report this thread, cause my afford to reach him fails.
So I hope we can figure out, why it does'nt work as it should to...
kindly regards, FS
Hi,
I have the same problem with my Touch Pro and my Megane 3.
I have to switch back to an older version of the rom then..
Hi,
I'm using Energy ROM Titanium 18may.
Radio 1.17.xxxx
No problem here with BT of my car stereo.
I had this problem untill I delete the old pairing on the car BT.
After this, the phone pair great
firespawn said:
Hello buddies,
this thread is about some strange behavior of bluetooth with current energy roms. details follow...
why a new thread?
I decided to start a new thread, because it leads to nothing to discussing this topic in the main thread ... found some people who shares my sorrow, never the less there was a lot of users who hit the answer button on page 1 and report "problem xy" or "hell yeah what a nice rom"
what is the problem?
I'm not able to pair my TouchHD with my car's Hands Free system. A2DP works fine, but when I turn on the Radio Unit a small blue headphone symbol blinks in the statusbar of the phone - no pairing succeeds. If I switch to BT audio, a black headphone symbol stays resident and the media player opens for playback, so A2DP works. Installing SIM access profile on roms without built in rSAP or other various tools in addition doesn't make it work. [see "what have been done" section!]
Just used the latest MIRI-Roms (discontinued) and it works like a charm for me. After initial setup, Hands Free (version 1.5) and Wireless Stereo where installed and activated - Serial Port left out unchecked. Then a popup message informs me, that a BT-Device is trying to access phones phonebook remotly - all went fine.
as reported by other users, this behavior occurs since ~may versions of energy roms...
about the environment
Using energy's rom on TouchHD [Blackstone] T8282 [BLAC100 32M]
flashing with USPL
phone's SPL: stock SPL-1.54.0000
radio: 1.12.25.16D3 - don't see a reason to update
protocoll: 52.60.25.33U
carrier: O2 GERMAN
what have been done so far?
I've tested the pairing of my device in various cars
tested with my Renault Megane 3 integrated car kit (arkamys audio / parrot)
tested with a 2010 Toyota Prius car kit
tested with a subaru 2010 car kit
tested with Blaupunkt Toronto 400 BT head unit by phitsc
I've tried programs, suggested by the xda community
installed Bluetooth_SAP_Profile.CAB
installed BT_SAP.cab
installed Gooru_Sense_BT_A2DP_Fix_Cab_by_JVH3.CAB
installed HeadsetFix.cab
installed JetBTHFExt_1.40.CAB
reg-tweaks on "HKLM\Software\Microsoft\Obex\ObexServiceMask"
roms tried
Miri_WM65_21891_Premium_Manila_2.5_V20.0_NoHtcMessaging.rar
Miri_WM65_21893_Premium_Manila_2.5_REV22.0.rar
Energy.BLACKSTONE.23563.Sense2.5.Cookie.HomeTab.Apr.23.7z
Energy.BLACKSTONE.23566.Sense2.5.Cookie.HomeTab.May.01.7z
Energy.BLACKSTONE.23569.Sense2.5.Cookie.May.16.7z
Energy.BLACKSTONE.21903.Sense2.5.Cookie.May.16.7z
HD_Miri_6.5.X_23541_SENSE25.rar
Miri_WM65_21893_V38.0_Premium.rar
Energy.BLACKSTONE.23569.Sense2.5.Cookie.May.22.7z
(green indicates a working rom)
dear community...
please use this thread wisely for recommendations or suggestions on this topic. keep this thread a productive discussion. if you have a contact to NRGZ, feel free to report this thread, cause my afford to reach him fails.
So I hope we can figure out, why it does'nt work as it should to...
kindly regards, FS
Click to expand...
Click to collapse
Mine works fine without any cab fix.. your pda must search 4 a car kit as a bleutotth headset! comm manager /bluetooth/ set up BT headset turn your cars BT on and there you go!! i tell yo the energy roms work fine 4 me
+ 1 here
Don-Maco said:
Mine works fine without any cab fix.. your pda must search 4 a car kit as a bleutotth headset! comm manager /bluetooth/ set up BT headset turn your cars BT on and there you go!! i tell yo the energy roms work fine 4 me
Click to expand...
Click to collapse
sorry dude, not much help but i have the same experience; all energy roms (and i do mean all of them) work perfectly with my parot CK3100 but then i do task 29 before every flash & hard reset a few times after initial setup.
in addition, i also flash the latest stock rom from htc every so often.
i know this seems a bit ott but i rarely seem to suffer the buggy issues that many others do.
hope you get it sorted
It is not about Task 29.
I had problems with access through the original multi-functional touch panel in the Ford Mondeo. When I went to CLEAN ROM, all troubles are gone. The problem is that you must agree with access on the phone. This question is not on Energy ROMs displayed. I can pair phone but can not be used for handsfree calling.
Now I have a CLEAN ROM and everything is bugfree.
To be honest, no ROM to date consistently works with the in-car bluetooth kit in our Zafira. It works flawlessly with my old phone (K800i) and my wife's phone (W950i) but it's just not stable for the HD.
If it works, it'll drop the bluetooth connection after about 15mins. It's as if there is a time-out, but I've hunted the registry and both HD Tweak and Adv. Config for anything related to this but with no joy.
My current ROM seems to be about the best so far (kwbr's WM6.5 and Manila 2.1) but it still drops the connection randomly yet other times it may keep the connection for over an hour no problems.
Seems very very strange to me, but from what I've read, it's a common issue with the bluetooth kits in GM's euro cars (Vauxhall, Saab, Chevrolet etc.)
|WWE|BLACKSTONE|¯`·.¸¸.- Energy -.¸¸.·´¯ |BlueTooth CarKit ISSUE|`·.¸¸.·´¯`·.¸¸.·´¯)
@DaRulah
what kind of rilphone / radio rom do you use - pointing my research in this direction, may that's the reason... does bluetooth depends on the used radio rom?
@raistlin74 / @Don-Maco
tried all ways possible
car to phone
htc comm mgr to car
windows BT settings to car
@superseagull
having the latest carrier rom flashed before (comes with SPL 1.54 to enable flashing of 6.5+ roms)
what kind of rilphone / radio rom do you use? [EDIT: saw it in your signature ]
@malson
well, sounds logic ... the pairing won't succeed cause the phone's dialog to allow access doesn't appear. will try it with energy's titanium rom. never the less, the outdated MIRI roms /w sense 2.5 and windows mobile 6.5 works for me
@jonifen
as mentioned, the phone is compatible with my car - in basic. simply doesn't work with energy roms.
therefore I tried it with various other systems to exclude a mismatch with my car kit
well, thanks for you participation so far - may we get the clue with my problem
regards - FS
2 options?
Why only two options yes and yes? Why not a no option in the poll? I don't have a problem with nrg roms.
firespawn said:
@DaRulah
what kind of rilphone / radio rom do you use - pointing my research in this direction, may that's the reason... does bluetooth depends on the used radio rom?
Click to expand...
Click to collapse
Radio: 1.14.25.35 with the matching rilphone
Rom: Energy.RAPHAEL.23569.Sense2.5.GTX.Themed.May.13
i don't think it's a radio problem since i used that one with older energy roms, and had no problems with my car kit.
no problems here
I tried my phone with a bluetooth carkit in a BMW X5 and found no problems with it. I use latest NRG rom 21905 with CHT and latest Radio (1.17) with Rilphone 1.15. i suggest u upgrade to those as well.
GL
As this is about a genaral pairing problem I don't know if it will help u as u seem to be able to pair but just have Handsfree problems...
But as u didn't mention how u tested out the fixes I will post this here.
Remember i had a problem once when trying to pair my HD.
Base:
- Touch HD with some newer Sense 2.5
- A2DP wasn't working or Windows Mediaplayer hooked A2DP keys
AFTER I tried to fix A2DP problem (installed some "fix" cabs u mentioned above) I wasn't able to pair anymore.
Here is what i figured out:
- To get it working again it didn't help to over-install another fix - don't know why but seems that some fixes do reg changes wich break other ones.
- I had to hard reset the device
- so never try to install 1 fix after another to figure it out
- always do 1 hardreset + 1 fix then hardreset again
- only really good working fix for me was HeadsetFix.cab I posted in NRG thread - many other fixes broke my pairing capability
Now im on:
- actual NRG 2. June MaxSense 23xxx
- HeadsetFix.cab installed (otherwise Windows Mediaplayer pops up or it doesn't work for me)
- haven't had problem with pairing since several month with any NRG Rom (before it wasn't depending on NRG but on Sense 2.5 / but just had A2DP issue - pairing issue just with wrong fixes installed)
Radios I tested were .12 and .14
Tested BT Headsets/Caraudios:
- Motorola HT820
- some Sony MEX BT xxxx Caraudio
BTW for all who are interested in - i always install "AutoA2DP" or "AutoActiveSync" cause A2DP doesn't pair automaticaly in my car - just the Handsfree pairs by default.
Mimic NRG style ROM Thread !!!!!!!!!!!!
eddyve said:
Why only two options yes and yes? Why not a no option in the poll? I don't have a problem with nrg roms.
Click to expand...
Click to collapse
Yes + 1
Why only YES and YES option ...
No problems with any BT. Myy HD conects on any BT device that i have with no problems...
*****************************************************
PS: its not nice to use for your thread title the same format and characters that NRG use for all of his roms !!!!!!!!!!!!
Its a bit confusing for regular users and misleading....
And if i was you i will change the title not to mimic NRG ROM threads !!!!!!!!!!!!!!!!!!!!!!!!!!!!
colossus
|WWE|BLACKSTONE|¯`·.¸¸.- Energy -.¸¸.·´¯ |BlueTooth CarKit ISSUE|`·.¸¸.·´¯`·.¸¸.·´¯)
@eddyve
it is a yes poll (or call it simply a counter), because I want to know how many people have a problem like me
@DaRulah
well, good to know
@TheOne741
updating my radio rom asap, just to confirm that the radio version is not the source of my problem ... I will report on this
@FrEcP
thank you very much for your detailed explaination! I also do hard resets between the fixes. I will try HeadsetFix.cab in combination with AutoA2DP on a clean rom
@colossus_r
do you have anything useful to contribute? stay on topic please!
Well, thank you all so far, I will report my progress when the mentioned tips have finished... regards - FS
mimic NRG ROM thread
firespawn said:
@colossus_r do you have anything useful to contribute? stay on topic please!
Click to expand...
Click to collapse
@firespawn: Whats the matter with you? colossus_r is on the right way. Why only "Yes or Yes" in poll. And whats about mimic NRG ROM threads?
Please choose your own style for this thread.
On topic: No problem with Siemens HKW 720 Bluetooth Car Kit at all. Im using Handsfree-Profile and rSAP-Profile.
Issues with bluetooth ...
aleskow said:
@firespawn: Whats the matter with you? colossus_r is on the right way. Why only "Yes or Yes" in poll. And whats about mimic NRG ROM threads?
Please choose your own style for this thread.
On topic: No problem with Siemens HKW 720 Bluetooth Car Kit at all. Im using Handsfree-Profile and rSAP-Profile.
Click to expand...
Click to collapse
Again, it is used as a counter aaand again: stay on topic and stop cryin' like a baby about the choosen subject! I couldn't change it anymore!!!
Please do not post things like: Oh boy, mine is working fine *smiley*, cause this is worth nothing!
Sorry, I'm a bit frustrated, because a productive research on this problem seems to be impossible...
superseagull said:
sorry dude, not much help but i have the same experience; all energy roms (and i do mean all of them) work perfectly with my parot CK3100 but then i do task 29 before every flash & hard reset a few times after initial setup.
in addition, i also flash the latest stock rom from htc every so often.
i know this seems a bit ott but i rarely seem to suffer the buggy issues that many others do.
hope you get it sorted
Click to expand...
Click to collapse
Right is right i also never had bugs since energy roms march 2010
and the opera 10 never gave issues! so some flashers are doing somthing wrong! when using titanium the rom is superbly fast i also spice things up with the htc-performance.cab.
firespawn said:
Again, it is used as a counter aaand again: stay on topic and stop cryin' like a baby about the choosen subject! I couldn't change it anymore!!!
Please do not post things like: Oh boy, mine is working fine *smiley*, cause this is worth nothing!
Sorry, I'm a bit frustrated, because a productive research on this problem seems to be impossible...
Click to expand...
Click to collapse
We cant do any research if we dont have the problem
i think you should swich the the car bluetooth on and keep it pressed till the device finds it! thats what i did on other cars
or you will have to reset the cars bluetooth as shown in the manual
firespawn said:
@eddyve
it is a yes poll (or call it simply a counter), because I want to know how many people have a problem like me
@DaRulah
well, good to know
@TheOne741
updating my radio rom asap, just to confirm that the radio version is not the source of my problem ... I will report on this
@FrEcP
thank you very much for your detailed explaination! I also do hard resets between the fixes. I will try HeadsetFix.cab in combination with AutoA2DP on a clean rom
@colossus_r
do you have anything useful to contribute? stay on topic please!
Well, thank you all so far, I will report my progress when the mentioned tips have finished... regards - FS
Click to expand...
Click to collapse
set up you bT via comm.manager. dont turn Bt on just choose set up bluetooth hdset device etc/ turn you cars bt on an make shure it is visible etc by keeping the on button pressed in while searching with your gsm and thats it i think thats how it worked 4 me and will work 4 every one too!!!
study your old rom be4 you use a new one and you will know how to recognize the differenzesss amen
I've experienced something similar with my volvo. In my case it paired sometimes and usually in a call it disconnected. This happened with all kind of roms. It all disappeared after a radio update.
Somebody mentioned 1.17... with rillphone 1.15... works like a charm!
Hope it helps
(else you can try to let a mechanic update the bluetooth software in your car)
Got the HD2 last summer (June 2010) and made a few tweeks early on to get it working with my 2010 Volvo XC70 BT. BT works, but when connected the system is SLOW, like slower than slow. Controlled through the car things work alright, control on the phone is useless. It also hangs and freezes.
I regularly get major freezes when sending and receiving text, though usually worse receiving. Usually I have to pop the battery and restart.
Bone stock other than CHT and the BT fix:
1. Modify the HandsFree plug-in:
HKLM\Software\WIDCOMM\Plugin\HandsFree
i. Change SupportedFeatures to 45 (default is 1135)
ii. Add value HFBDA binary, set to same value as LastConnectedBda
iii. Add value HFDeviceType decimal 2
2. Modify the WIDCOMM bluetooth general settings:
HKLM\Software\WIDCOMM\BtConfig\General
i. Change bdaddr to (no value)
ii. Change DisableReopenAudio to 0 (default is 1)
3. Reboot device
Click to expand...
Click to collapse
I've not really done anything. No ROM updates (including the one TMO suggested)
So my stats:
Wm 6.5
CEOS 5.2.21892
Manilla 2.5.20121412.2
ROM 2.13.531.1 (90963) 4/28/10
Radio 2.10.50.26
So what direction do I go? Dump WM6.5 and head to 7 or Andriod? Update the ROM and keep loving 6.5?
Tasks I want to be able to do
GPS (prefer/use Garmin XT)
BT (Volvo is picky)
FM radio
Stream TV (would LOVE LOVE LOVE but currently can't figure out how)
Other than that just the usual internet searching and text/phone.
Thanks ahead of time.
M
This type of freezing is more than likely from your stock ROM. I would go with a custom one, they are seriously light years ahead of the old T-Mobile stock one. NRG ROMs are about your best bet.