Related
Hello XDA forumers,
This is my first post, so be gentle
I was sick and tired of poor signal and performance of my sx56 phone for about 2 years. I ran into this forum over past weekend, was amazed and started to fiddle around with various ROM images.
I tried several but beleive it or not, Special Edition ROM put together by these people was the best. Right now my device has a RSU from ATT upgrade of WM2003. I didn't touch it. And with the SER i get an awsome performance and signal strength. So first of all, great job guys.
I would just live with this ROM forever, but curosity has gotten the best of me.
So the question for the fathers of SER is: how did you do it? Did you simply take O2 ROM and cooked it with some other applications. Did you make any coding changes to the RIL? I cooked several versions of PPC 2003 ROM from stefan's kitchen, but couldn't get my phone perf to get quiet there. Was that, that 2002 was just a better OS? Microsoft screwed something up in 2003?
I have got quiet a few questions on my mind!! as you can tell!!
I would like to develop a similar special room that is based on 2003 system. my reasons for insisting on 2003 is that .net applications work with it (e.g. voice command).
Thanks for all your work. love you guys!!
err, damn newbies.. I thought the information about my phone would populate from my profile: Here is what i got now on my phone:
SX56, ATT, ROM 3.17.03 (Special Edition ROM 1.2) RSU A.33.03
I hate WM2003, too! The SER by XDA-developers was a marvellous thing! But there are a few reasons to give 2002 up:
- it is VERY slow with application handling comparing to WM2003 :!:
- as you mentioned, no .NET there...
- IE supports older versions of JS
- worse Phone, SMS interfaces. No new "connecrion/phone status" bubble, that allows to connect to GPRS, for example.
- in general, most programmers today aim the WM2003 (even though some of their apps work with PPC2002PE, too)
On the other side:
- it takes less space (both RAM and ROM) :!:
- some people (like me) like older interfaces (especially "connections" tab in settings!)
- it was not this buggy (multiple windows in IE didn't close itself without my permission, could turn off LCD to play music with less battery consumption)...
- I expected few more things to be supported in WM2003...
bob, thanks for your reply and insightful thoughts.
My question still remains, why do i see better signal strength with Special Edition Rom 1.2 compared to WM2003. It is puzzling me. This is a questions directly for SER developers? What did you do to get a better signal reception? or WM2002 was a better os for radio reception?? Is the antena graphic signal is bit magnified than what it is?
I mean you guys wont beleive, i actually have my phone back after 2 years of mucking around with it. I can actually make calls and recieve calls in the area that i live. Now it still roams over to cingular, but even get a full bar signal with cingular. I was ready to drop the whoe pocket pc phone thing and now .. well.
I request and hope attention from the SER guys. I would like to make or participate in making Special Edition for WM2003. I love the OS; hate the signal that i get with it.
I don't think they changed anything in OS code, possibly tweakers, included in SER did. There was GPRSconnection thing, that allowed not to disconnect from GPRS on power off...
Concerning signal strength, do you feel you loose signal more often or it is all about how many lines it shows on taskbar? In addition, did you change PDA's ROM only or GSM ROM, too? (in these machines there are three ROMs: PDA, GSM/GPRS and bootloader)
SER2003: I think there will be no SER2003 - noone needs it. You can get whatever you personally need in ROM kitchens. If you want to help, you can suggest something LumpiStefan should add.
I have only been playing with the OS part. Didn't touch bootloader or RSU.
that is somewhat correct that i have been measuring the signal strength by the number of bars shown. It is now confirmed that the delta of bars between Special Editition ROM and WM2003 is at-least 2 bars, with device sitting at exact same spot.
BUT I put SER on and used the phone for 1 whole day. It had a great performance. As I said, i was able to make calls from ares where i have never been able to before. I am today trying a phone with a well cooked version of wm2003 from stephan's kitchen, and i am have issues so far!!
question remains: What is it in SER that improved signal so greatly. :?
I'm from Toronto Canada and use my SX56 on the Fido network here. I'm also receiving very poor signal strength, even in downtown Toronto. Should I drive outside the city, forget it. I still carry around my Nokia 3390 just in case I need to make a call while driving home.
I'm using the A.30.09 ENG rom, along with A.33.03 radio version. I'm wondering if anyone has knowledge of a better radio version than this. I've gotten quite good at bootloading my new roms into place, but I'm wondering if there's an easy way of just doing the radio version?
Lastly, and I have to ask this question because of my lack of knowledge, but in respect to the bands (800/900 - 1800/1900), is there a way to force the phone to use any certain band for it's connectivity to the network? Which one is generally stronger? Does the phone automatically seek out the strongest signal from any of the bands and then use that?
I just wanna push my phone to the limit and get the best reception possible.
Thanks for any and all replies!
I had A.30.09 from ATT RS 3.25 (i had 4.21 before but i've changed it to improve radio performance. Unfortunatelly reception remained the same) and i had no reason to comply. All indicators shows poor reception but i had no problems with using my MDA (good voice quality and no dropped calls).
using this software http://www.pocketgear.com/software_detail.asp?id=14491
i checked reception and I had about 95 dBm indoor and 80 dBm outdoor (for MDA minimum strength is 113 and max is 51).
After month or 2 i have changed ROM into 4.1.16 from T-mobile and all seems to works much better!
No i have 80 dBm indoor and 70 outdoor!!! That's what I call great improvement. Unfortunatelly I faced another problem now - today my MDA 2 times (one during measurements ) lost reception at all and I had to restart radio modul to get signal again. I have totaly no idea why this had happend but I'm affraid i cant use this rom anymore Offcourse this new problem may be caused by something diffrent (like strange software form lumpistefan kitchen ) so I'll try to deactivate as much software as possible and use my unit for several days from now on.
If U can try software mensioned above and share with me some conclusions I'll be greatfull. Thx in advance.
Hello everybody
I have been reading on this forum for some time now, and I understand the update process, including unlocking, its all great.
However, Im at a loss - I have no idea what I have to gain from upgrading my ROM.
I currently have an untouched T-Mobile Vario II with bootloader 1.04, hardware vesion (?) 634.
My friend has just recieved his Vario II, v646.
Everyones talking about using ROMs from other providers, but I've yet to read anything substantial about whats to be gained from switching or upgrading ROMs.
What CAN actually be changed by changing ROMs? For example, T-Mobile have been kind enough to bundle my device with a free registered version of 'Spb GPRS Monitor' - it monitors GPRS/3G and battery power, plus providing a useful bar on the today screen. it's very useful and I wouldn't want to lose it should I decide to gamble on a ROM update that provides nothing nearly as useful.
I have identified several short comings of my devide, not the least of which is the fact that it intermittantly skips every 30+ seconds when playing music through my stereo bluetooth earphones. I imagine that some kind of update will be required to fix this, as it seems to be a problem for only certain version of the device - the Vario II being the obvious.
I have also decided that I would like to try other graphic themes. Before I have a go at making my own I thought it might be nice to try some existing ones...
There are lots of hardware/radio versions published, but unless I've missed it theres very little talk about what the ROMs provide.
Cheers very much for all your help thus far, and in advance for anything else you might be able to help me with!
lets make this a simple one.. if you are happy with the device the way it is then there is nothing to change... kinda like the old saying, "If it aint broke then dont fix it"
If there are things you are looking to change then maybe post your problems here and we can tell you if you would benefit from changing roms!
I have the universal and purchased the hermes for size and HSDPA / UMTS improvements.
The universal was upgraded and hacked many times.
However, I cant see an upgrade rom hack that is available at all here for the hermes yet.
Can anybody confirm a WWE 3.x Rom upgrade being available? Mine is Imate, but I am not particularly loyal in any way, but would like more reliable Push Email, and the speed improvements that occur with 3.x
To the moderator, you cant really say if it aint broke dont fix it, cause quite often, you dont know if it is broken until you start to fix something, and you dont know if something is faster, better, more efficient, more effective, or provides improvements in functionality until a question is asked.
Its a bit like me taking my car to a mechanic, they always ask if everything is fine, it always is, but they always call me up and tell me that this isnt working, this needs fixing, and this is about to broke... You can triple the cost if you would like us to fix it.
You didnt know until somebody points out the improvements and benefits.
So, I would like the initial question answered as well, if somebody is prepared to give an explanation and some guidance.
Here's some upgrading facts for you:
There is no AKU 3.x ROM available for the Hermes yet.
Due to a new encryption strategy, ROMS take 25 minutes to flash. Any interruptions during this time may brick your device.
Also due to the above encryption strategy, we are not yet able to cook our own custom ROMS for the Hermes.
Boot Loader v1.04 which shipped with most of the early ROMs contains a bug which allows easy bypassing of CID lock. However subsequent bootloaders fix this problem and will CID lock you to your original vendor. The only crossgrade solution is to first downgrade to a BL1.04 version of your vendor's ROM then exploit the bug to load another. Device owners without a 1.04BL version of their ROM have consequently been unable to crossgrade/unlock their Hermes.
There is a bootleg solution that will flash BL1.04 on any Hermes while leaving the rest of the ROM untouched. However, it isn't available here. In fact the original owner of it's copyrighted code actively pursues anybody who posts this solution on the internet. Consequently, it's worldwide availability is constantly changing
There is a CID/SIM unlock solution by pof that is posted here which works with the 1.04 Bootloader only
The more current ROMS for the DoPod, TyTN and 8525 contain measured performance improvements
The most current radio rom (v1.20) improves battery performance
Most of the newer roms fix a media player audio stutter bug
Getting a combination of the most current radio ROM and the most current device ROM involves 40-60 minutes of flashing time and the use of the bootleg BL1.04 solution described above.
HTH!
Thanks sleuth255 for taking the time to answer comprehensively.
I am really only interested in upgrading to 3.x and will wait and see how things transpire. There was major benefits to the universal upgrade to 3.x however, the hermes doesnt appear to suffer the speed issues of the universal and I am so far very happy with the device.
jubbbird said:
Hello everybody
I have identified several short comings of my devide, not the least of which is the fact that it intermittantly skips every 30+ seconds when playing music through my stereo bluetooth earphones. I imagine that some kind of update will be required to fix this, as it seems to be a problem for only certain version of the device - the Vario II being the obvious.
Click to expand...
Click to collapse
I tested all the WWE ROM here (not the one with 1.09 bootloader, because since today is a one way only road, no way to flash back the original ROM)
About music skip: not sure if upgrade will solve it (since today) but there is a good patch here. http://forum.xda-developers.com/showthread.php?t=284974
Other well known problems (lost storage card in windows media player, overnight and in-call freeze, poor efficiency (short battery life in UMTS coverage, slow performances if compared to processor speed promise, ...) are still unsolved
I will suggest: play if you want, but having in mind that HERMES ROM flashing today is just for play, have a look, testing, not for really solving anything
Supercid ( http://forum.xda-developers.com/showthread.php?t=282073 ) your device to play with ROMs, now, because you have the 1.04 bootloader version. Once SUPERCIDed you can play with all ROM
Well thats my primary issue at the moment and it sounds a lot like your fix may work for me.
I am using an original ROM im guessing, with bootloader 1.04 so all the doors are open for me. I'm in nor rush, strictly speaking, because I love this device and it generally works wonders for me. I listen to music for long periods of time once in a while (long car journeys alone with my SE ds970 - plugs the ears well providing awsome noise removal from external sources, can't even hear the engine on my crappy Vauxhall Corsa with those in...) but it is during those periods that I suffer with the skipping. fixing it will be wonderful.
I have a question about your fix though, but I worry that having read the first few pages of your other thread, and the last few, I may have missed the answer so I apologise if I'm asking questions you have already answered - but I remember reading the original thread a while ago from the guy who discovered the Task Manager app that fixed the issue and he mentioned that because the software seems to prevent any CPU speed scaling (not sure if thats actually what its doing) he observed that CPU battery consumption while running that specific app + audio decreased noticably. Is this still an issue with your patch? I plan to purchase a working in-car power adapter so it won't really be a problem, but im curious
I'm gonna take my time with regards to ROM upgrades because as has been mentioned above - I have only a few issues which after reading this thread now seem to be standing issues which won't be fixed whatever I decide to do right now. Ultimately, I have the stuff I detailed above adn thus far no steadfast information about which ROMs are good for what. I don't even know anything about this 3.x business noted above...
What I'd like to know now, before I try your fix, is - if i were to install a TyTn ROM (which right now Im assuming is an original HTC TyTn ROM as oposed to a yet-to-be-released T-Mobile ROM...?) will that effectively brand it back to HTC, wipe the onboard flash, give me the original TyTn green theme, remove all the software and settings T-Mobile gave me (they were kind enough to give me a licensed copy of Spb GPRS Monitor which is quite an advantage for me - my friend has a more recent T-Mobile Vario II and they seem to have retracted the offer ... ) and leave me at square one with any fixes/improvements/new-issues that ROM provides?
I also seem to remember reading that because as yet T-Mobile have not released an original ROM, changing now is a one way trip.
I think what I need is for someone to set me in the right direction from the perspective of a early Vario II user. I really enjoy my gadgets, and the best thing about them is "fixing things that aint broke" I love upgrading and trying to squeeze it for all its worth. Better yet, updating my device and gloating to those who have no idea what that means! It's all good...
Anyway, cheers very much for your help thus far - greatly appreciated.
I noticed that Bluetooth was listed as a fix in the new rom. That's actually a problem I've been having. I have a Garmin GPS with Bluetooth that I use when I'm driving (speakerphone). I loved it with my old 8125, but I just got the mogul and speaker volume has been so low with it. Has anybody else experience this problem? What are the thoughts on bluetooth with the new rom for users who have tried it?
I had the same Bluetooth problems on older ROMs, but it works great on the unofficial 6.0 and 6.1 ROMs. I expect it to work as well, if not better on the official version.
Well, I tried it out on my way to work today. It was only my voicemail, but it sounded much better. Hopefully that will be the case when I get a phone call.
Well, when I just got Mogul and bought BT prepped car (never used BT before), I thought BT sucked reaaaly bad, since EVERYONE complained if I called from my car. Now, since unofficial ROMs, I get occasional complain here and there, but it is obvously tolearble to most of people I call. I also reduced volume on BT in my car after upgrade, so I think it should solve the problem.
I think part of it was that I was upgrading from 2.17 (not sure what has come since). But, it does seem pretty good now.
Hello everyone,
I'm starting this thread following my replacement of the standard radio (1.02.25.19) that comes with the UK Touch Pro with the Cingular Rom (1.02.25.31), thanks to MrVanx for the suggestion and to Olinex for the great HardSPL 1.90 (all these in Raphael Wiki here http://forum.xda-developers.com/showthread.php?t=419746, except MrVanx of course).
EDIT: By the way, if you're new to this radio game, replacing the radio only DOESN'T erase your memory (as long as it's extracted of course, and despite what updateRUU will tell you), so you can go back and forth very easily, no fastidious reinstall needed.
Following some questions by Athanaso77 in the HardSPL thread, I thought we could share our experiences here about the different radios we try, give feedback and try to see if problems / improvements are general or specific to each phone.
MrVanx has started a more general thread somewhere for feedback about different ROMs/Radios/Protocols (link needed!), so if you're not specifically interested in finding the ultimate T-Mobile UK radio, please post there!
As most (EDIT:many) T-Mobile UK users, I've experienced dropped calls when on 3G and not so good reception in 2G/3G (at least compared to my Vario III/Tytn II), which has prompted the quest [EDIT: along with bad Wifi performance)...
I haven't been able to fully test the 1.02.25.31 radio yet, but here are my first impressions:
- Slightly improved 2G/3G reception
- Not tested yet the dropped calls issue
- Slightly degraded data speed (around 10%) but not sure yet
- Had a problem initially with GPS fix (became longer with TT7) and I'm still testing this. I initially got better results by setting the GPS to Other NMEA GPS, 56700bps, COM4, but it's not consitent so I'm not happy yet.
For those (like Athenaso77) who want to play with the GPS settings in TT7:
from your main TT7 screen, click on the GPS signal strength on the lower right corner, then on the signal strength again on the right (below battery), then configure. You can chose Internal GPS, Other BT GPS or Other NMEA GPS (all three should work and can affect the strength of the signal/lag issue/time needed to get a fix). When asked for speed, select 4800 (default) or 57600. When asked for Com Port, always select COM4 (these should be the default settings in the External GPS app in EDIT:settings/system/external GPS), you can have a look there but don't m*** up with the parameters there, it's the shortest way to a hard reset!).
Please don't ask generic questions about TT7 in this thread (there are plenty on this subject), unless it's related to the performance of the GPS with a new/different Radio.
I'll post a more detailed report in a little while after more testing.
Please let us know about your specific experience. Also before any feedback/question, please give your radio number at the time, as your signature may change....
PS: Any suggestions to make this thread more useful are welcome!
To be honest I am still using the radio that my device was supplied with (1.02.25.19) because I haven't had any problems. Nearly always got H in my bar where ever I go in my local area (bearing in mind I live in the bottom of a valley), only had one or two dropped calls at the most in the month I have been using it, GPS works fine for me, always get a lock quickly and never noticed lag that is out of the ordinary (even going at questionable speeds on the motorway )
It may just be that I am in a great signal area (North Kent btw, if your interested) but I am more than happy with the radio in my phone!
EDIT: It may also be pertinant for people to oost what ROM they are using, as it could be a combination of ROM and Radio that produce a good result! Mine is currently DCSTouchPro-v13 WWE
Great to hear that at least it worked out of the box for you!
As I said, I'm comparing with my Tytn II/Vario III (same area, Salisbury/Wiltshire).
Although the 3G signal was good (not as good as my Vario III), I missed 2 or 3 calls the first day so promptly switched to forced 2G.
The Wifi reception (is it the Touch Pro or the shipped ROM, I don't know) was appalling with the initial ROM, which is also what prompted my quest for a better radio, as I hope the TP can do better than that!
I compared it with my Vario III (before I sold it!) in real time, and I couldn't connect in some rooms where the Vario III had always been absolutely fine (and still was until its last day).
Haven't tested Wifi coverage with the new radio yet, but I will report....
Only have a long fix problem with TT7 since I changed the radio. Not tested the lag yet to see if it's still there, but I think this is more a TT7 software issue as I believe it's fine with TT6 (although not tested on the TP yet).
Out of interest as as everything seems to work for you with stock radio
1) which version of TT7 are you using (I'm using Black VGA repack 3)
2) what are your GPS parameters (in TT7 and in the External GPS app)?
3) do you use QuickGPS or not?
4) are you happy with wifi cover/signal strength and stability?
It may help us less lucky people to improve our experience...
Manni01 said:
Great to hear that at least it worked out of the box for you!
As I said, I'm comparing with my Tytn II/Vario III (same area, Salisbury/Wiltshire).
Although the 3G signal was good (not as good as my Vario III, I missed 2 or 3 calls the first day so promptly switched to forced 2G).
The Wifi reception (is it the Touch Pro or the shipped ROM, I don't know) was appalling with the initial ROM, which is also what prompted my quest for a better radio, as I hope the TP can do better than that!
I compared it with my Vario III (before I sold it!) in real time, and I couldn't connect in some rooms where the Vario III had always been absolutely fine (and still was until its last day).
Haven't tested Wifi coverage with the new radio yet, but I will report....
Only have a long fix problem with TT7 since I changed the radio. Not tested the lag yet to see if it's still there, but I think this is more a TT7 software issue as I believe it's fine with TT6 (although not tested on the TP yet).
Out of interest as as everything seems to work for you with stock radio
1) which version of TT7 are you using (I'm using Black VGA repack 3)
2) what are your GPS parameters (in TT7 and in the External GPS app)?
3) do you use QuickGPS or not?
4) are you happy with wifi cover/signal strength and stability?
It may help us less lucky people to improve our experience...
Click to expand...
Click to collapse
I do use QuickGPS and I have made sure A_GPS is turned on (by default it was disabled), but I haven't been able to try TT7 yet because I haven't got any maps! iGO8 seams to work fine but the only real testing I did was with google maps, just making sure I kept up, and I let it auto detect the settings.
As for WiFi I don't really use it extensivly, as my office doen't have it and if I am at home I just use my computer but it seamed to be quick enough. I did use it in a pub for a good hour (checking film times, restraurants in the area, general browsing stuff really) and it never dropped out on me, although it did slow down on occasion.
As for dropped calls (i.e straight to answermachine) I can honestly say I haven't had any, the first couple of weeks I still had my old contract running so only 3 people had the new number, so I would have known if someone had
tried to contact me and been unable to. According to T-Mobile I am in the highest level of coverage so maybe I am just lucky in that respect. Like I say it could also be a combination of the ROM, DCS's stuff is very quick and I am very impressed with it
This makes more sense then. The GPS Fix / Lag is only an issue with TT7 on the TP. Google Maps fixes in about 10s (and can be used to improve your fix with TT7) but I'm trying to improve TT7 native response.
The Wifi is specifically a COVERAGE issue. If you're next to the router, or away with no walls, no problems. But I used to be able to get a good signal with my Vario III one or two floors down (I stream TV on my Touch Pro with my Slingbox Pro), and I'm really struggling with the TP (doesn't connect, or loses the connection constantly). I'm not telling you in which room I'm using it most but it's really annoying to suffer such lack of performance compared to the Vario III. Again, this was tested with same router, and simultaneously with Vario III, so I know it's a TP issue.
I may give a new ROM a try once I've decided on the radio...
Manni01 said:
This makes more sense then. The GPS Fix / Lag is only an issue with TT7 on the TP. Google Maps fixes in about 10s (and can be used to improve your fix with TT7) but I'm trying to improve TT7 native response.
The Wifi is specifically a COVERAGE issue. If you're next to the router, or away with no walls, no problems. But I used to be able to get a good signal with my Vario III one or two floors down (I stream TV on my Touch Pro with my Slingbox Pro), and I'm really struggling with the TP (doesn't connect, or loses the connection constantly). I'm not telling you in which room I'm using it most but it's really annoying to suffer such lack of performance compared to the Vario III. Again, this was tested with same router, and simultaneously with Vario III, so I know it's a TP issue.
I may give a new ROM a try once I've decided on the radio...
Click to expand...
Click to collapse
Fair enough, I thought it was a general GPS issue as opposed to a program specific issue. As for wi-fi I was in the pu so I have no idea where the signal was broadcast from, athough I can say it was a traditional building with incredably thick stone walls by todays standars, so even one room over would have had an effect.
Good luck with your search, if I ever take the plunge for the TT7 maps I will let you knwo how I get on!
Okay, I've done more tests, and here are my first conclusions for1.02.25.31 with stock WWE ROM:
- 3G dropped calls doesn't seem to be an issue anymore, although I need more time - more calls! - to see if it's definitely gone (I usually have 3/4 bars in 3G, and almost all 3G calls were dropped with stock radio).
- 3G data seems to be 10% slower than with stock, but that could be T-mob's mood
- Wifi seems definitely more stable. I used to have trouble connection right next to the router, the new radio is rock stable. From further away (weak signal like 1/2 wifi bars, router in loft , TP in ground floor), it also seems to connect more easily and keep the connecting for longer, where stock used to lose connection every few seconds. It doesn't displays more bars by the way, it's just more stable in borderline locations.
- I have setup my GPS for 4800bps/COM4 in both TomTom and in the external GPS app in settings/system, using "other NMEA GPS" in TT7, and with A-GPS switched on (using Schapps ACT) I get a hot fix in 10-30s consistently, which is good enough for me. I'll have to wait until tomorrow to find out about a cold fix!
So all in all, quite happy with the new radio, which is for me a definite improvement over stock. Now I need to check if the lag in TT7 is still there...
well, I think I'll go for it. I haven't so much had an issue with dropped calls....it's being able to receive the calls in the first place!!.
I also wonder if this will address the data connection issue I've had (push email works fine 90% of the time, if I try to collect my pop mail it connects immediately, but no internet until I do a soft reset.!!)
are there some simple instructions in the wiki about doing the Radio upgrade from the SD card?
Re the data connection, did you uncheck the proxy in your t-mobile connection settings? I had a problem with exchange initially, which was related to a wrong proxy being used by default.
yup..the proxy is unchecked.
it just seems odd that I can't connect to the internet using GPRS etc, but if I connect to my pop3 account ot check email..it works imediately....back to internet explorer...no connection. yet push email works fine too.
surely if my pop3 email connction works when required, and push email works, then connecting to the web via IE should work too??...but no...sometimes it will, sometimes it wont.
well, I now have all the bits I need to update my radio....but....I don't think I will!!
all the instructions I've read are aimed at people who have done it all before and understand the terminology. One day I'm going to sit and write some idiot proof ones.
twisted-pixel said:
well, I now have all the bits I need to update my radio....but....I don't think I will!!
all the instructions I've read are aimed at people who have done it all before and understand the terminology. One day I'm going to sit and write some idiot proof ones.
Click to expand...
Click to collapse
i dont think there will ever be a more idiot proof one than "install hard-spl first!!!!" the rest is just download blah blah blah and run customRUU
theclueless said:
i dont think there will ever be a more idiot proof one than "install hard-spl first!!!!" the rest is just download blah blah blah and run customRUU
Click to expand...
Click to collapse
perhaps, but the wiki mentions 'flashing' to hardSPL....to me 'flashing' implies ROM replacement!!
twisted-pixel said:
perhaps, but the wiki mentions 'flashing' to hardSPL....to me 'flashing' implies ROM replacement!!
Click to expand...
Click to collapse
the procedure is fairly harmless... as long as you follow the instruction (download, extract, click, run, wait)
ok..getting VERY nervous...connected my device...waited for it to finish it's sync, ran the HardSPL exe, it asked me on my device if I wanted to enter bootloader mode, I clicked yes....the screen faded and now it's been sitting with a blank screen for 25 mins!! the backlight is slightly on, but nothing on the screen and although it's connected to my pc still...the sync light is out, and it's not charging...what's gone wrong???
strange, when i ran it, it was actually disconnected via active sync, as i cant browse the device in my computer anymore
I found out that certain combinations of ROMS and Kernels work better with my CAR Bluetooth then other combinations. For instance CM6 is not working perfect and is uncertain to reconnect to my Car system. On the other hand most Sense ROMS work better with my Car system.
So in this project I wanna track down first which components have influence on the bluetooth stack, and more important which specific parts of the kernel, software and other things are related.
This to improve the BT Car system of at least my Scenic but I have the feeling more Car systems have issues.
Please if you have info about this put it in this treath so we can make it better.
Nice initiative. My BT system in my car works flawlessly with WinMo, but as soon as I connect my nexus, my speakers begin shrieking like all hell breaks loose. Also, My Nexus the seems to lock up and I need to pull the battery for all misery to end.
LOL.
That was the first time I connected the bugger, so I wasprobably still running Eclair when I tried it.
6.1.1 works well for me, both bluetooth calling and a2dp.
Theres a little fuzziness going on when nothing is playing, like white noise, but that's pretty much my only problem. No wait, there is one more thing actually, every now and then while music is playing it'll skip more or less a second
Just to add... I have to repair and disable/enable by every time I get in the car or the sound will drop out every 15-30s on any rom that uses froyo. GB seems to help where I only need to disable / enable bt. Kenwood x-993 with parrot bt. Using latest bt firmware.
Sent from my Nexus One using XDA App
PhantomRampage said:
Theres a little fuzziness going on when nothing is playing, like white noise, but that's pretty much my only problem. No wait, there is one more thing actually, every now and then while music is playing it'll skip more or less a second
Click to expand...
Click to collapse
This happens to me too once every three or four songs, but it's such a small thing it doesn't bother me much. On the other hand, for the short while I was using MIUI, I felt it was happening much less, but I may have been imagining that
Heres my setup, and it works flawlessly every time i start the car.
Car Deck: JVC KD-R900 (Using the small bluetooth adapter that came with the unit mounted in the back USB port)
ROM: Enomthers TheOfficial Nexus1 v2.14.3
Kernel: 2.6.32.35-TheOfficial-AudioMOD-720p
Radio: 32.41.00.32U_5.08.00.04
OS Version: 2.2.1
Like i said earlier i have no problems with the audio quality or connecting to my unit. As soon as i turn my Bluetooth on it connects within about a minute.
Calling quality is good, audio quality is good and AVRCP works also (play/pause/next/prev)
If you need anymore info just let me know.
Its good to see there is some reaction on the start of this.....
My goal is to achieve and to find out which components are involved in the Bluetooth experience:
F.I. :
* Kernel modules and libs
* Application in the rom to actually making the connection
* Bluez configuration and settings
I have done some searching but found that even with the same Bluez settings there can be a difference between some roms in combination with kernel.
jscat1 said:
Just to add... I have to repair and disable/enable by every time I get in the car or the sound will drop out every 15-30s on any rom that uses froyo. GB seems to help where I only need to disable / enable bt. Kenwood x-993 with parrot bt. Using latest bt firmware.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I have the same issue on my Kenwood system.
jscat1 said:
Just to add... I have to repair and disable/enable by every time I get in the car or the sound will drop out every 15-30s on any rom that uses froyo. GB seems to help where I only need to disable / enable bt. Kenwood x-993 with parrot bt. Using latest bt firmware.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Me too, same model. I've updated the firmware on the X993 and it seemed to help.
elfblackdeath said:
I have the same issue on my Kenwood system.
Click to expand...
Click to collapse
Same here on my DDX-812. Almost everything "works", I just get the drop-out when streaming music if it's not a fresh pairing.
The bluez stack was updated with Gingerbread...I'm hoping against hope that that fixes some things.
i have to use a no-audio-boost kernel with my jabra headset, otherwise the call quality is abysmal. lots of metallic clicking and other strange effects going on.
but i have seen no differences in the overall connection stability otherwise.
hmm i have a problem with my car dock and bluetooth i think. when using the navigation the voice plays via the phones speaker not the dock speaker. is this similar to the problem in the 1st post? if so, would love a fix!
I'm on CyanogenMod Nightlies with the included Kernel and have a Kenwood DDX8024BT with built in bluetooth. It connects up perfectly when I turn the ignition on and seems fine when in call. I don't use the A2DP much but when I have I've not had any problems.
Slightly OT, the only problem I have is with reading contacts from the phone. I have two phones paired. I usually have the Nexus connected but occasionally switch to my work phone (a Tocco Lite). At some point it took the contacts from my work phone and then wouldn't redownload the Nexus contacts when it was reconnected. It's now done it at some point but there's a handful of contacts that still won't transfer no matter what I try.
On a side note, I have a Clarion CZ500 rig in my car, and the N1 is incompatible with the microphone boost firmwares they offer on their site. All I hear is crackling when I try to make or receive a call.
What's odd is that the HTC Desire works fine with those firmware. Even Blackberry Pearl.
I ordered the N1 dock on eBay. I guess I'll see if the dock can handle the firmware.
i have a n1 and im still running cm 5.0.8 with android 2.1
my phone pairs with my car without any problems and i am able to talk to people and whatnot. Now as far as music, i use a blackberry music gateway bluetooth device that i plug into my car's 3.5mm jack and then i pair that device with my phones bluetooth. It pretty much connects automatically all the time and sound quality is awsome however as someone mentioned earlier in this thread, i get the occasional 1 second skip every so often. Does anyone have any idea whats causing this and how can i fix it? It is extremely annoying!!! I paired the blackberry gateway device with my gf's mytouch and there was no such problem, which leads me to believe that the problem is in my n1 :/
My $02: I cannot use a2dp and hands free at the same time. If both are connected the the a2dp drops out all the time.
This is not an issue with my HD7.
A workaround would be awesome.
Sent from my Nexus One using XDA App
I suspect the main difference, hardware combinations aside, between Stock/CM and Sense roms is that they use different bluetooth stacks.
Differences in the bluetooth stack that have caused issue for the FM radio on stock roms, an issues for bluetooth file transfer on Sense roms as far as I know.
Like iphone fanboys would say: fragmentation
On a related note the behavior of my N1 with the Parrot handsfree has vastly improved in GB.
i have the kensington liquidaux bt adapter in the car and cm7 rc4 with stock kernel skipped constantly. rc2 was better, but still unbearable.
i am currently on intersectraven's 4/3/2011 kernel and from limited use, has not skipped on me yet.
have people tried bt music streaming with other kernels with cm7 rc4? wildmonk? pershoot? etc.. thanks.
Try CM7 Issue 3233 fix
d1mitrov said:
It pretty much connects automatically all the time and sound quality is awsome however as someone mentioned earlier in this thread, i get the occasional 1 second skip every so often. Does anyone have any idea whats causing this and how can i fix it? It is extremely annoying!!!
Click to expand...
Click to collapse
Can you try the fix in Issue #3233 on the CM7 bug tracker? http://code.google.com/p/cyanogenmo...on Model Network Owner Summary Stars Priority
scotte9999 said:
Can you try the fix in Issue #3233 on the CM7 bug tracker? http://code.google.com/p/cyanogenmo...on Model Network Owner Summary Stars Priority
Click to expand...
Click to collapse
i think thats exactly what my problem is, when the phone is connected to the car and the music gateway is connected as well i get the intermittent connection and it skips every so often but if i disconnect the phone part then the music never skips...however im not on CM7 so i dont know if that fix applies to me and i dont know how to begin changing those settings