Related
HI EVERYONE
I HAVE BEEN READING A LOT ABOUT THE 1.11ROM
I JUST INSTALLED THE RADIO PART OF IT ...
BUT TO MY DISAPPOINTMENT ... NO CHANGE TO MY PREVIOUS 1.01
HAVENT INSTALLED THE COMPLETE ROM BUT WANNA KNOW IF THERE IS ANY ADVANTAGE AT ALL ??????
sigh
what was that for ??
@ morphosin
I suppose, it was his way to say "well, there are several threads in this forum about upgrading to 1.11. Please take a look at the search button".
If You are currently using radio 1.01, upgrading to 1.11 should be a major improvement. Wne I upgraded to 1.05 (or was it 1.06) it was a big step towards good sound (but I must admit that there is hardly a difference between 1.06 and 1.11 in terms of sound). Sound improvement will not depend on the installation of the other ROM-Files, the radio.nbf is enough.
with 1.11 there will be only a few performance features at my side ...
Too bad none of those several threads are able to conclusively identify any solid benefit from upgrading. I am still looking for posts that tell me why 1.11 is worth the bother. And he did say he was reading about it beforehand (presumably in this forum). So seems the question is valid in my opinion.
ROM upgrades are mostly used to fix bugs in older version. From time to time new capabilities are thrown in as well, but that is not the main concern of a ROM update. So the question is: do you want to live with these bugs, or do you want them fixed?
Don't expect all bugs to be fixed by doing a ROM upgrade, though. ROMS are made by humans, and we make mistakes. Of course new bugs can be introduced as well, but unless these new bugs are very bad and a lot of users are experiencing them, I see no reason to run an old buggy version.
Seems they've replaced the old tired bugs with new and improved ones! I have finally stabilised my JAM on the 1.06 ROM after much pain. I am still not convinced that the 1.11 is any better since some people claim its better and some claim its much worse. In other words, there is little consensus.
BTW, I don't accept the human factor as an excuse for lingering bugs. I am not a beta tester and I don't wish to use beta products. Once maybe, twice is pushing it, but three ROMs and still no sign of fixes for the fundamental problems is unacceptable. My phone is unreliable and if I don't get it sorted soon I will be back on a Nokia / Blackberry combination (quite a step backward in my opinion).
All I want is a stable working ROM that allows me to hear calls when I make them, to hang up when I hang up, and to connect and disconnect to GPRS when I need to and to put an end to soft reseting all the time! Unit and regression testing as part of a typical QA process should kill off 90% of bugs either new or old.
The problem is that in the rush to market HTC/Imate have obviously failed to complete a proper QA cycle prior to release. Their QA is terrible.
ianwood, what are these numerous bugs that you're referring to?
I'm heavily using my JAM on a daily basis. I was very cautious and selective on what 3rd party software I install. I had some 3rd party software that f*cks up my JAM completely (JGUI's for example), but now I have a list of software that WORKS WELL TOGETHER and don't have any problems. I never do a soft reset and the JAM behaves exactly how I want it.
We also have to distinguish between 3rd party software bugs, Windows bugs and HTC flaws.
The same bugs that everyone else refers to:
Intermittent:
GPRS not being able to resume after a call
Answering call fails with "unable to answer call" message
Hanging up fails with service command error message
ActiveSync becoming unresponsive when syncing
BT not installed errors
Unresolved items in ActiveSync when there is no conflict
Constant:
Heavy static on calls
Sound quality is crap (worse than the old T68s)
Speakerphone is also crap
Camera is slooooooow and picture quality is mediocre
BT headset drops after 15 minutes
Several reputable today plugins just don't work
BTW, I have very little installed on the thing. GPRS Monitor, a couple of simple games, Resco, Skype, TomTom. The rest are I-Mate default apps.
Let's face it; I am not the only one to have an issue with this thing.
MS, Imate, HTC, et all need to wake up and realise they will continue to be a footnote in mobile until they get this stuff sorted out! Let's hope WM5 will be better -- too bad we might not get it on our JAMs.
Some problems just not related to the Rom itself. I am using 1.11 rom
ianwood said:
The same bugs that everyone else refers to:
Intermittent:
GPRS not being able to resume after a call (I don't have GPRS)
Answering call fails with "unable to answer call" message (never happen to me)
Hanging up fails with service command error message (never happen to me)
ActiveSync becoming unresponsive when syncing (never happen to me too)
BT not installed errors (Yes! But not anymore after 1.11 rom)
Unresolved items in ActiveSync when there is no conflict (blame stupid MS)
Constant:
Heavy static on calls (sometimes)
Sound quality is crap (worse than the old T68s) (Ok for me)
Speakerphone is also crap (I agree)
Camera is slooooooow and picture quality is mediocre (I agree)
BT headset drops after 15 minutes (not in my case for my HBH 600, even 30+ mins still ok)
Several reputable today plugins just don't work <- This is the plugin's problem. All my plugins works without problem (SBSH's Pocket Breeze, Marware's Pocket Weather and PocketMax's Phone Alarm)
Click to expand...
Click to collapse
ianwood said:
The same bugs that everyone else refers to:
Click to expand...
Click to collapse
I had some of those when I first got my Magician, but haven't seen any of them since upgrading to 1.06.
Intermittent:
GPRS not being able to resume after a call - Constant, but fixed in the Norwegian.
Answering call fails with "unable to answer call" message - Never happened to me.
Hanging up fails with service command error message - Never happened to me.
ActiveSync becoming unresponsive when syncing - Agree.
BT not installed errors - Never in 1.11, but only in 1.06.
Unresolved items in ActiveSync when there is no conflict - Constant.
Constant:
Heavy static on calls - Never happened to me.
Sound quality is crap (worse than the old T68s) - No.
Speakerphone is also crap - No.
Camera is slooooooow and picture quality is mediocre - As in all ROMs.
BT headset drops after 15 minutes - Haven't got a headset, but BT GPS stays connected hour after hour.
Several reputable today plugins just don't work - Name one. I haven't had one single problem and I use many.
Let's face it; I am not the only one to have an issue with this thing. - And there are lots of users that think that it's more stable than 1.06.
MS, Imate, HTC, et all need to wake up and realise they will continue to be a footnote in mobile until they get this stuff sorted out! Let's hope WM5 will be better -- too bad we might not get it on our JAMs. - Oh yeah.. I've worked with QA and I woudn't have released even the 1.11 as 1.0! Terrible!
Yeah I have an SDA, the metal looking one with Wifi and the hump on it....and music control on it, a Tornado.
Anyway, just installed Windows Mobile 6 today, and that is a huge improvement on this phone. Main thing is the SPEAKERPHONE! It was way too quite with WM5...I was suprised after installing WM6, it improved markedly! Sounds about as good as the dash now, which is pretty good.
Also being able to use Pushmail without having to run the special SMS thing that would make you have to have unlimited messaging package or else pay for mass messages...I'm saying the Exchange email setup, you need wm6 if you don't have unlimited messaging.
It makes a big difference and it rocks on thisphone! Highly recomended.
UPDATE; but the camera seems to be worse then before..? Is it just me? The lighting adjustment has no effect..?
I was having the same problem with the speaker volume until I used the 'Clear Storage' option on the phone. After I cleared the storage on the phone and started from new it was fine..
I currently have an nokia e61. I use it primarily for maintaining my appointments list throughout the day, adding new appointments as they are called in. This is all syncronised through an Exchange Server 2003. The exchange aspect works very well, and reliable, however, the actual 'phone' part is quite poor, dropping calls, poor transfer from 3g to 2g during calles, poor reception, and the phone having a habit of just 'going off line' and not answering any calls, while appearing to be fine.
I recently got hold of a palm 500v jsut to try it out, the phone part is excellent, however the screen, and the cut down windows mobile 6 software is woefull compared to Nokia.
Both phones have the sem resolution screen 320x240, however on the home screen of the 500v, i get very little info of much use, i get one appointment, and notice of an email (not what the emails are), on the nokia, i get two nearest appointments and two newest emails.
When i go to the emails on the E61, i get a list of ten with address, title and date, on the palm i get four all very cluttered, in the appointments i get three on the palm on the nokia i get more detail and about five or six per screen.
It seems, if i am going to realistically make the switch to a windows phone, it needs to be vga screen, a keyboard would be nice, but not essential...
Looking around for pdas with vga screens seem to be full of disapointment. You find a phone that fits the bill, like the etin x800, and find that it is full of bugs, and because of its tiny 64mb of memory is mercilessly slow.
I did for a period of time have an o2 exec, and found it a bit of a brick... When it went through one of its slow periods you could miss the phone as it got around to loading the software.
So, what out there is going to be the E61 killer?
VGA screen
Fast to use
portable without need for a wheelbarrow
good reception
Truth is out, if the Iphone supported exchange server, i would be going with that, i understand that server sync is on its way....
must be going south for nokia because all the phone issues you describe is what people have been blaming htc phones for years
I've got a Kenwood BT-200 bluetooth handsfree car kit and have found the following issues with it;
1. Everytime a call is completed, the phone book downloads all over again and takes over 10 minutes, preventing making follow on calls till complete.
2. The received and dialed calls list doesn't work
3. Cannot initiate a call from the head unit unless the phone screen is on (was working perfectly on previous HTC Touch Cruise).
4. Unable to initiate voice dialing on Phone using Microsoft Voice Command whereas with previous HF kits it was as simple as pressing and holding the call button.
Anyone else use the same Touch Pro - BT200 combination? Or experience similar problems with other HF kits?
I have Pioneer BT unit. I can not connect, but I installed Hands-Free Config from JETware Mobile Software and it solved all my problems. There are many setting options which should help you...
Hi Pritman,
I just went through the same thing after upgrading to the Touch Pro from the Dopod 838Pro (Hermes).
There's a firmware update available for the KCA-BT200 which may well fix your issues (certainly did mine).
I created a post about this earlier today (didn't see your post here).
http://forum.xda-developers.com/showthread.php?t=440494
The firmware flash is very easy to do. You will just need a laptop with a bluetooth adaptor.
Codenix.
Kenwood have released another update.
See my other post at http://forum.xda-developers.com/showthread.php?t=440494 for details.
Codenix.
Wow, never thought I would fine anyone else with the combination of Kenwood DNX-7100, KCA-BT200 AND the touch pro. I am having similar issues.
DNX-7100 with BT100 worked fine with touch pro.
"upgraded" to BT200, and I have nothing but headaches.
I have tried two different BT200, and both have been flaky.
I have tried BT200 firmware 1.60 and 1.70, and both have been flaky.
My problem is similar to the ones you folks have been experiencing, mainly it is constantly downloading, and the interface is super sluggish when downloading. I can retrieve a name and phone number from the BT200's memory, but when I call out it will say downloading and do nothing. Sometimes it won't "pair" with the phone automatically unless I manually select my phone from the DNX-7100, and sometimes it will just drop the connection. I used the BT100 for about a year, and it was solid 95% of the time. I am running stock Telus rom, btw. I have also played around with the dip switch on the BT-200. From the shipped manual, DNX-7100 belongs in group F, which is off, off, on for dip switch 1, 2, 3. But when I searched online, some of Kenwood's info listed the DNX-7100 under group G, which has dip switch off, on, off, just to add to the confusion. I have also tried removing the "wireless stereo" profile as well as the "serial port" profile, but that fixed nothing. Lastly, just to kick me when I'm down, when it list the numbers, sometimes it list them as first name, then last name, but sometimes it list it as last name then first. This is super irritating as you can't be sure where anyone is listed ..... so far my experience with the BT200 has been nothing but horrible. I am on the verge of flashing my touch pro to a cooked ROM just to see if it is due to the stock Telus rom's bluetooth (I went back to stock as the juggalo rom I used became corrupt after a few weeks).
So, did you guys finally find a solution that worked 100% of the time?
Idea
Hi Guys, I'm glad there are more people out there with my combination.
Upgrading the BT 200 to 1.70 has improved things significantly but not as good as it would be with another handset like a Nokia N95. The download delay and sluggishness still exist.
I recall when I paired the TP, a notice came up on the TP that the BT 200 is requesting access to the phonebook or contacts and prompted me to allow or deny. I'm wondering what would happen if I deny? I do know that when I first paired the N95 with the older firmware, it wouldn't syncronise the contacts and I had to manually send the contacts to the BT 200. If this can be done with the TP, it may eliminate the constant downloading, perhaps.
Anyone else willing to try this. I may not be able to do this till later this weekend so if any of you do manage to test this before me, please post the results.
Good luck!
If you don't give it access to the phonebook, I suspect it can't download your phonebook automatically, and you would have to manually push the phonebook over, which defeats the purpose of the BT-200, effectively making it a BT-100. After trying a 2nd BT-200 for 3 days, I have given up and chalked up the BT-200 as extremely flaky, and is easily the worst purchase I have ever made as:
1) Half the time it won't pair with the phone automatically
2) The other half when it does pair, you can't dial out as half time time again when you want to make it call, it decides to do a download from your phone instead (never mind that it already "downloaded" when it paired already. Half x half = quarter.
3) Half the time when it does manage to make it call, it magically drops the bluetooth pairing and drops the call.
If you're keeping track, we are at half x half x half, which is 0.125, or this damn thing only works 12.5% of the time. This is not a time saver, nor a gadget of convenience/safety. It is the ultimate source of anxiety, danger (as you're trying to get the damn thing to work), and a big disappointment. Kenwood, shame on you for putting out such flaky products, and especially for not fixing it (look at the first post, it is from Oct 08).
I am going to return both of my BT-200 to Clutchfield, and am going back to my 99% stable BT-100. BT-100 actually is not as horrible with the TP as TP runs WinMo 6.1, which lets you push multiple phone book contacts at once (not like the older WinMo where you had to push contacts ONE BY ONE!!!). The only caveat with the BT-100 is if you need to delete or modify any contacts, you can't, and you have to delete all the entries for a particular phone and repair and push all contacts again, which takes 1 minute now as oppose to half an hour with pre-WinMo 6.1. When I buy a HU next time, I don't think I will consider Kenwood again due to:
1) Flaky software/interface.
2) Poor documentation.
3) Poor service support. Kenwood Canada actually NEVER REPLIED. I only received the auto-gen email notification indicating they received my email. Clutchfield Canada has been very supportive, and I will pay more to buy from them in the future solely due to their strong customer support.
Hi Johnnysks,
As far as the Touch Pro is concerned, I understand your frustration and totally support your argument.
On the other hand, I have tested the BT-200 with a Nokia 96 & my previous Touch Cruise, works like a dream! I've had good responses from Kenwood UK but whenever I contact HTC, I alway get vague responses, which to me suggests that Kenwood must have been making the effort but keep getting let down by HTC. Ultimately the BT-200 works with majority of the handsets out there.
I will still keep trying for a solution though as I really do like the TP and the BT-200!
I have no doubts the BT-200 works with other phones, and I know my TP works with my BT-100 flawlessly. I also know from prior personal dealings with Kenwood Canada's technical support that:
1) They're rude, have a bad attitude, and unprofessional (as my first inquiry for a different product from a year ago was met with a reply that was condescending, unhelpful, and was not even in proper English). I'll be more than happy to dig up my old email for you if you have any doubts.
2) They're not responsive. It's been over a week, and they never replied to my current inquiry regarding the BT-200 (funny. They used to be rude and unprofessional. Now they're missing in action)
Perhaps Kenwood USA, Kenwood UK, or Kenwood Japan are doing an awesome job. However, I can only go with what I have personally experienced.
Anyone find a fix for this? I have the same problems with my DNX8120. Tried Jetware, no luck, I would try BTRestore, but it won't work with .net 3. My biggest complaint is that even if it is connected via bluetooth, it won't start a call from th eheadset unless the phone is not in standby. Next biggest issue is that it drops the connection after hanging up from a call.
Very f*&%*g annoying!
FYI, worked with 2 different ETEN's
Please don't flame me .... I know about the search before asking.
Anyway...
Here is the issue: I am on call for a major data center every other week 24X7. We use e-mail as our alert system for infrastruce issues (power - HVAC - other). Until last Tuesday we used Blackberries with very good success. Then some brass in our upper mangement decided all corporate phones would be WinMo. Our mail system is Exchange so it makes sense right? I was on AT&T so I was issued a FUZE the next day. I kinda like the Winmo OS ... not so much the TouchFLO for e-mail atleast. But the big issue is the phone going to sleep (black screen) and dropping the network connection - no e-mail - no good. Turn off the sleep mode and the battery is dead by lunch. At other times for no apparent reason I simply do not get the mail until I manualy sync. I see lots of post regarding hacks/mods to fix these issues. However, I do not see myself hacking the phone to fix it as it is company owned. Question, is there an At&T phone on WinMo that does not do this? What about iPhone with exchange connector? Rock solid mobile e-mail delivery is all I am asking for. All suggestions welcomed .... Thanks !!!!
I just found the new HTC ROM update .... loading it now. Sure hope it makes life better.