Related
Sucessfully downloaded and installed the WWE imate ROM on their web site and reinstalled all apps without any problem.
Maybe I am too quick to conclusions, but I noticed NO CHANGE AT ALL!!!
Bluetooth is exactly as before, call quality is unchanged, the *&^%* Jam still cannot send anything by Infrared and worse, the Camera quality is now worse than pre patch!
Overall not a bad upgrade really, just a waste of time and effort!
I finally got all my apps installed as well. Wasn't easy. And to sum it all up, I didn't notice any discernable differences. Sound quality is the same. Stability is the same.
Anyone know what fixes and updates were supposed to be included in the update? Or did anyone find anything at all to be any different?
The only thing I can tell that it did was make my mp3's sound horrible. Very muddy sounding. I'm about to odwnload pocket music and see if the eq on there can fix it. Also looking for a way to downgrade.
Question for you imaters:
I had an imate for 3 weeks and sent it back to Amazon, bought the MDA Compact instead.
T_mobile has no support for this phone : they built correctly the first time
BT Active Sync with PC, no problem, but I never managed this with Imate
BT with GPS, worked with both IMATE & MDA
The MDA rom is stable, has good sound, photo's are ok, like all HTC devices.
So why not just leave Imate and change to the MDA UK Rom??
Re: Question for you imaters:
mikeycollins13 said:
So why not just leave Imate and change to the MDA UK Rom??
Click to expand...
Click to collapse
This makes sense as the operators often do a fair amount of the own device QA, change requests, etc. when they look at any new device. If they don't, they pay for it in customer support. Imate being a relatively new company has yet to prove whether or not it has the same structured approach to their product management. I tell you one thing, Imate will certainly not have the same amount of resources available to them nor will they have as much attention from HTC. That said there is a lot to be said for not being an operator when it comes to efficiency (but that is a different story). Enough editorial...
Does anyone know what the major differences are between the new imate ROM and the current MDA UK ROM? Has anyone used both and/or done a side by side comparison? Does it work on other networks? I'd be interested to hear more.
Ian Wood
I had both
I had both and the major difference lay in the sound and the Bluetooth. Which is why I sent the Imate back.
Besides that, I have had an XDA1, XDA2, and the mda is the most stable rom yet (though the 2003 SE was pretty good on XDA2)
Also price, Imate =389GBP, Amazon, MDA=240GBP, given that it works better, it was a no brainer here.
M
Re: I had both
mikeycollins13 said:
I had both and the major difference lay in the sound and the Bluetooth.
Click to expand...
Click to collapse
Is that with regards to stability and quality or are there more features as well? In your estimation, is the difference worth a full reinstall? Thanks for the feedback btw.
Ian
imho the new rom is NOT worth a hard reset and all the reinstalling/reconfiguring/resyncing that goes with it.
to be blunt, I cannot see the difference unless I REALLY go looking for it.
I did the upgrade no problems, and my sound quality is a bit better. (less tinny) I recommend that if you do the upgrade use a quality backup program like sprite backup. I simply restored my previous backup over this upgrade and it went smoothly. I understand a fresh start is also sometimes preferable for for testing and If no problems, then I stick with this. If I start having difficuties then I'll reboot. The reduced hassles makes the 20-30 bucks for sprite backup worth it.
Mike
where is the ROM for JAM WWE???
Click here to download the Arabic ma_cdlsku2_arb_10300_141_10100_ship.exe (29 MB) or
Click here to download the Italian ma_cdlsku10_ita_10304_151_10100_ship.exe (26 MB) or
Select HTTP or FTP link to download the USA ROM ma_cdl_10600_150_11000_ship.exe (46 MB)
--------------------------------------------------------------------
Ok my iMate JAM has this under device info:
ROM: 1.03.00 WWE
Radio: 1.01.00
ExtROM: 1.03.143WWE
But looking at the iMate website I cannot see a WWE ROM... can I use the USA ROM or should I wait for the WWE ROM?
Cannot get a ROM
I have tried following the link that everyone has for the ROM at:
ClubIMate . . .
ma_cdlsku1_wwe_10300_143_10100_ship.exe
ma_cdlsku2_arb_10300_141_10100_ship.exe
But I get Page Cannot Be Displayed.
My previous experience with I-Mate, having bought a used JAM, was that I now had to buy a membership and get an ID and Password to get anything.
Does anyone have the file OFF SITE from the club, or does anyone have a password, yada yada?
Barring all that, has anyone built a better ROM than that? Is there a kitchen available for it?
And anyone looking for themes I am selling a collection of mine on eBay and offer to sell 6 for the price of 3 to anyone that references xda-developers . . . I hope you like.
http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&rd=1&item=190106886535&ssPageName=STRK:MESE:IT&ih=009
Thanks
galt: thanks for all your help. As I said, I applied Pocket Hack Master 2005 to both my Jasjar (with the latest ROM) and to my wifes' MDA Pro, but with totally different results.
1) My Jasjar struggled to pass the test to overclock to 624Mhz, but did eventually. Once achieved, it would lock up within seconds and had to be soft-reset and clocked back to 520Mhz where its pretty content and somewhat an improvement on the Jasjar without HackMaster!
In contrast:
2) My wifes MDA Pro, passed the 624Mhz stress test 1st time and rockets along comfortably all day, with no probs.
I can't help but wonder if us Jasjar owners may have a software problem with our Roms, unless another Jasjar owner had the exact same positive response that the MDA had.
*Point of interest: Although the MDA overclocks and runs happily at 624Mhz (haven't tried beyond - have only used safe settings) both the Jasjar @ 520Mhz and the Pro @624Mhz are pretty indistinguishable in performance. I'm talking about refresh rates, access to or loading times of programs and video playback @ 640x480 resolution.
Feedback appreciated guys.
My Jasjar seems to run ok at 624. Tried the test 5 times and ran for several days without issues. Not much difference noticed, except pocket informant seems to run better and faster.
hi mackaby007,
can you please post the rom, radio and external rom version information from your wifes mda pro.
i think that this may be a rom issue - need to clarify
thanks
Hi quazzi76. here you are.
MDA PRO Jasjar
ROM version:-------1.12.42 WWE ROM version:------1.13.53 WWE
ROM date:-----------08/23/05 ROM date:----------09/23/05
Radio version:------1.00.02 Radio version:-----1.03.01
Protocol version:---42.33.P8 Protocol version:---42.36.P8
ExtROM version:-1.12.126 WWE ExtROM version:---1.13.137 WWE
sorry. that went a bit skewiff!
MDA PRO
ROM version: 1.12.42 WWE
ROM date: 08/23/05
Radio version: 1.00.02
Protocol version: 42.33.P8
ExtROM version: 1.12.126 WWE
Jasjar
ROM version: 1.13.53 WWE
ROM date: 09/23/05
Radio version: 1.03.01
Protocol version: 42.36.P8
ExtROM version: 1.13.137 WWE
sorry. that went a bit skewiff!
MDA PRO
ROM version: 1.12.42 WWE
ROM date: 08/23/05
Radio version: 1.00.02
Protocol version: 42.33.P8
ExtROM version: 1.12.126 WWE
Jasjar
ROM version: 1.13.53 WWE
ROM date: 09/23/05
Radio version: 1.03.01
Protocol version: 42.36.P8
ExtROM version: 1.13.137 WWE
Ok, I've done the overclocking to 624Mhz and it seems to be running well. (only been half an hour since I did it though!)
Everything is working well. Can't say I've noticed a massive difference in performance although my Citrix client seems to be running a little smoother. Even the camera seems to be working well (and that's usually the first thing that's gone wrong when I've tried overclocking on previous devices!)
God knows how the battery will be affected, but we'll see...
My details are as follows:
Jasjar
ROM version: 1.13.53 WWE
ROM date: 09/23/05
Radio version: 1.03.01
Protocol version: 42.36.P8
ExtROM version:
(I hit the soft reset button before the ExtROM loaded...)
Your keeping me up now sub69!
Tell me, if you would, as you seem to have the same ROM version as myself and also a jasjar, wouldn't you agree that it is probably some 3rd party software I've got installed on mine that is causing the problem? Or you have something on yours which is helping yours!
Mine is almost down to a skeleton Jasjar! I've only really got Spb 3.0.1 left installed accompanied by hackmaster & TCPMP (obviously) and Resco Radio. That's it! any ideas? My wifes Pro has the same software installed, as I mentioned earlier and she too flies along at 624Mhz.
I had SPB Pocket Plus installed for a while too. I did a hard reset a couple of days ago, and left that out when I re-installed everything (because I was only really using it for the 'proper 'X' button function) and my JasJar seems to be running a lot smoother now.
I'd hate to place the blame on one piece of software, especially as I love the idea of Pocket Plus, but I really think I'll be waiting a while until they release a WM5-specific version from now on. I know I'm not the only one who thinks it slows down my JasJar (can't remember if it was this particular forum where I heard that though)
(Oh, and I should be asleep by now too!)
mackaby007: Sorry about going a little offtopic, but since you have access to both devices, which one do you like the most? MDA PRO or JasJar? And what are the reasons? Just curious
thanks mackaby007,
i've got to concur with the general consensus.
i'm beginning to feel that there might be a third party app that causes the jasjar to crash when you try to overclock it to 624mhz.
i dont need any of the software in the external rom so i intend to hard reset my jasjar and do a soft reset before the external rom loads like Sub69.
then i'm going to install phm 2005 and see if it overclocks to 624mhz and remains at that speed without crashing/freezing up.
on my JASJAR:
I pass the tests several times at 624mhz, all succeded.
But asap I switch to 624 I get it crashed.
Best Regards
Rosario
P.S.
the only software loaded on background is MS voice command
Time for a Hard Reset!
Hi guys. Thanks for your feedback, it all helps!
Sl9: I for some raeson still prefer the Jasjar! I can't put my finger on it, but it's probably that you can install newer ROMs and stuff like that from i-mate, without voiding warranty. I have also come to like the colour. The silver MDA Pro is nice to look at and everything, but the jasjar is somewhat discreet when i pull it out in public and I don't like to advertise what I'm carrying around with me. Just my preference I suppose.
Sub69 & qazzi76:
Ok I'm going to try a hard reset witha soft reset right now and try re-installing only Hackmaster and TCMP thingy. I'll let you know.
And sub69, I must say I concur with your decision to hold back anything not written for WM5.0. It looks like that obvious thing we all knew about in the beginning has come back to the forefront of our discussions and problems. If it isn't WM5.0 specific, then it isn't truly compatible, even if it does appear to work! :wink:
Hard reset soft reset, I need my head reset!
Memory Configurations after hard + soft reset just as backgammon tried to install (Time now 23:40) :
Storage
Total: 43.72 MB
In Use: 4.22 MB
Free: 39.50 MB
Program
Total: 50.16 MB
In use: 20.79 MB
Free: 29.37 MB
Space available at point of installing pocket hack Master: 40448 KB (installed to device)!
Run HackMaster and go stright to speed config util and select 416, 520 & 624 MHz settings then test!
All Passed! Then click close and evrything locks up!
Soft reset!! Time Now 23:56
Go straight in to PHM2005 and under scal config, select all 3 passd speed settings and click close/exit.
Then I minimise the app 8 through the PMH icon in taskbar, select 520MHz setting and go check my memory amongst testing speed performance (feel of browsing the O/S). All's well!
Memory util reads:
Storage
Total: 43.72 MB
In Use: 4.71 MB
Free: 39.01 MB
Program
Total: 50.16 MB
In use: 20.13 MB
Free: 30.03 MB (What?)
Check Running Programs: pocket hack master 2005 (only!)
Anyway....go back to PHM and select 624Mhz setting, done!
Click on start menu then settings and voila the MotherF....er locks up again! Needs a reset again! I haven't even gotten around to installing Activesync and TCMP yet to try videos!
Any suggestions guys, other than giving up? Well at least i have more program and storage on the jasjar now, but my issue with o/c to 624Mhz remains unresolved. i'll post this now. Time: 00:10
I'll be up a little while yet, but will probably check back tomorrow. Cheers for the tips anyhow, guess I'm just 'bad lucked'.
Hi mackaby007,
I'm sorry to hear that - very dissapointed in fact - i wonder whats causing it to lock up like that...
I wonder if this issue can be tied to the Rom revisions the devices ship with
It's quite possible that this is a ROM issue...
Another strange factor is the your wife's mda pro has an older rom revision than both of our JasJars (Radio Stack, ROM, External Rom, Protocol version)
This is admittedly highly frustrating...
qazzi76 said:
I wonder if this issue can be tied to the Rom revisions the devices ship with
It's quite possible that this is a ROM issue...
Another strange factor is the your wife's mda pro has an older rom revision than both of our JasJars (Radio Stack, ROM, External Rom, Protocol version)
This is admittedly highly frustrating...
Click to expand...
Click to collapse
Tell me about it! Well such is life. Funny thing though, is that sub69 also has a jasjar and same ROM (i think - Ext ROM details never confirmed due to soft reset at the time) and he seems to be flying along at 624 MHz! Confusing more like! Will let you all know if and when developments take place. Night all.
This could simply be due to different chip batches.
I beta tested PHM2004 before its release on my O2XdaII and managed to get as high as 1658MHz (stable too), the next speed up caused a hard reset.
I currently scale to a max. of 592MHz (which is L=40, M=2, N=1 for those in the know) and have no stability issues at all, whereas a number of colleagues who had identical devices & ROMs (at the time) were unable to use the L=40 setting, having to limit themselves to 528MHz (L=36) as the best performing CPU speed.
According to Anton, the L=40 setting was generally considered unstable for my device which is why I have to choose the Ultra Fast RAM settings rather than going for the PHM defaults. It appears that I'm just lucky and my device has better spec. RAM than most and which tolerates the higher speeds - the same could be true for your devices, one could simply have higher grade RAM (or whatever) than the other.
mtbsoft said:
This could simply be due to different chip batches.
I beta tested PHM2004 before its release on my O2XdaII and managed to get as high as 1658MHz (stable too), the next speed up caused a hard reset.
I currently scale to a max. of 592MHz (which is L=40, M=2, N=1 for those in the know) and have no stability issues at all, whereas a number of colleagues who had identical devices & ROMs (at the time) were unable to use the L=40 setting, having to limit themselves to 528MHz (L=36) as the best performing CPU speed.
According to Anton, the L=40 setting was generally considered unstable for my device which is why I have to choose the Ultra Fast RAM settings rather than going for the PHM defaults. It appears that I'm just lucky and my device has better spec. RAM than most and which tolerates the higher speeds - the same could be true for your devices, one could simply have higher grade RAM (or whatever) than the other.
Click to expand...
Click to collapse
1658MHz (stable too)!!! Flippin 'eck!!
Interesting comments about the different chipsets, that seems like a plausible scenario, given my circumstances and the unexplained differences between supposedly sames specced hardware and same ROMs.
mackaby007 said:
1658MHz (stable too)!!! Flippin 'eck!!
Click to expand...
Click to collapse
That would be the polite translation of what I said!
The more interesting part (though expected to some degree) was that this delivered far worse performance than many of the lower speeds, since it required the N multiplier to be at 0.5x which bottle-necked the whole device. Still, it's nice to have been there!
Hi,
I've just been reading for the last 4 hours, searching for a solution to my problem of the Hermes not working with my bluetooth nokia car kit.
Specifically, I'm getting serious breakup in areas with perfect reception.
People on the other end of the connection are hearing serious ghosting of their and my voice. Other times, the phone is crystal clear.
The phone doesn't seem to be losing sync and has always paired as soon as I get in the car and turn it on.
I bought this as a business tool and at the moment it isn't worth squat to me.
I have read as much as I can and implore someone to tell me if this issue can be fixed, and if so, point me in the direction of what I need to upgrade without all the acronyms. And yes I have read the wiki
Below are my spec on the unit.
Thanks in advance.
ROM; 1.31.305.2
Rom Date: 09/08/06
Radio Version: 1.38.30.10
Protocol: 32.71.7020.12h
Extrom: 1.31.305.106
Anyone have any thoughts?
i have the same problem with my dopod d810 and the nokia car kit. It connects fine over bluetooth and I can hear everyone else clearly, but no-one else can hear me properly - mainly the ghosting problems and static.
I've been looking at the following registry entries, but have not had any luck as yet..
HKCU\controlpanel|AudioAdvContrl
And as yet have had no luck...
I'll keep trying
sanquar said:
Anyone have any thoughts?
Click to expand...
Click to collapse
Have you tried this software? it has additional support for the nokia HS-12W and a 30 day trial.
http://www.jetwaremobile.com
worked for my bmw x5 BT when nothing else would.
Other options would be to upgrade the radio to 1.40 and/or OS to one of the wm6 variants excluding black 3.0 and 3.1
i noticed big hands free improvements with the BT stack on wm6, to the point where I didn't need jetware anymore.
good luck!
The point of this thread is that 1.64.08.21 is compatible for some and incompatible for others; hence what I'm trying to express here is that the bug/issues caused are due to the Radio and NOT the ROM itself.
Since quite sometime I've been testing miscellaneous ROM's over various Radio versions. Also have been closely monitoring every single BUG pointed out in bepe and other chef's thread. The same bug issue has been also brought up in ASerg ROM. I personally feel his ROM is bug free as I haven't come across any issues.
My speculation has narrowed down towards one common problem giver i.e. the Radio v1.64.08.21 which is now used by 90% of the Polaris users.
I strongly feel that v1.64.08.21 is incompatible with the latest ROM version 19209 & Protocol 25.69.30.05 and even the earlier ROM versions i.e. 1920x.
To be sure of my study I've tested ALL possible ROM's in this forum using the factory radio 1.54.25.14 and till date haven't faced a single bug issue which has been repeatedly brought up by misc members on this forum.
To clear this problem, request some of you to help me test some things out:
- Can I request you to re-flash your radio to 1.54.25.14 and then test the same ROM for the bug's you have been facing
- All NEW Polaris owners, please DO NOT flash your Radio rather just the ROM.
- Existing Polaris owners on a non-1.64.08.21 radio, please test whether the bugs exist on your ROM's.
After all 1.6.4.08.21 is a Radio extracted originally from a Russian Kaiser ROM, it doesn't make it 100% compatible as the factory Radio for Polaris.
Strongly looking for some views and feedback from everyone
What are your noted bugs?
what the actual bug is?
@taiseer999:
I'ven't faced the same issues which other members on the forum have been mentioning, even using the same ROM which they are on as well.
@windirt:
I personaly feel that using a Kaiser Radio on a Polaris is "possibly" causing the BT to remain on and other miscellanous issues that have been brought up.
I'm using a self-cooked taiwan cht rom (wm6 18129) with radio 1.64.08.21. works very well for one more week, never encouter the BT issue as you described.
windirt said:
I'm using a self-cooked taiwan cht rom (wm6 18129) with radio 1.64.08.21. works very well for one more week, never encouter the BT issue as you described.
Click to expand...
Click to collapse
I also never faced any problems with Bepe 0.67 WWE release and 1.64.08.21. I can turn my bluetooth on or off, the blue light isn't flashing if my bluetooth is off, and I never had any problems connecting to a device or what so ever. Maybe there are revisions of the hardware...
I have been using 1.64.08.21 from
http://forum.xda-developers.com/showpost.php?p=2051354&postcount=1
and no problems with Bebe's ROM. WiFi, Bluetooth, and 3G work fine, only problem I am having is using Windows Live with 3G, which cant connect all the time. But this also happened with the original radio and ROM.
PB of BT
Hi,
very intersting post Jibreil. I think your right when you recomand not to change the original radio of polaris. Since I change my radio, I definitively loose my BT and my FM Radio. Both was working before I make the "update". now I have to send my polaris back to the seller and its a very very disturbing situation
So I confirm: do not change your radio if you want to be sure of kipping your BT. Another thing about that: maybe Im wrong but I think that the battery drain is much better with the last radio (1.64....) it's a shame !
nooms
067 bepe
nooms said:
Hi,
very intersting post Jibreil. I think your right when you recomand not to change the original radio of polaris. Since I change my radio, I definitively loose my BT and my FM Radio. Both was working before I make the "update". now I have to send my polaris back to the seller and its a very very disturbing situation
So I confirm: do not change your radio if you want to be sure of kipping your BT. Another thing about that: maybe Im wrong but I think that the battery drain is much better with the last radio (1.64....) it's a shame !
nooms
067 bepe
Click to expand...
Click to collapse
After flashing I noticed a drastic loss in my signal, may be it doesn't work well in this part of the world. I have replaced three phones, imagine how frustrating it must be for me
The point of this thread is that 1.64.08.21 is compatible for some and incompatible for others; hence what I'm trying to express here is that the bug/issues caused are due to the Radio and NOT the ROM itself.
so, i remember that I changed various roms and the mic worked fine and then I remember I did a radio update and now its not working... can it be that?
i dont want to have to roll back if it isnt?
my desire hd's current radio is: 12.54.60.25U_26.09.04.11_M2
AND when it was working fine the radio was:
12.28e.60.140fU_26.04.02.17_M2
Can someone please help me, thanks..
personally i dont think it is the radio, the radio is for the wireless stuff gprs/wifi etc (afaik)
you can always be sure by rolling back as you said, but it sounds like hardware to me.
as far as i know,
every ROM has their own radio preferences...
and radio used for the signal receiver, and something like that..
but one of m friends said that, he read something somewhere, unmatch radio caused someone stayed in a loop boot condition..
so maybe you wanna look up again to the ROM that you used, and match the perfect radio for it
or you can just rollback...
Hello
Radio has nothing to do with mic
Definetely not the radio. Either ROM / Hardware / Reception.
Radio only deals with all the wireless stuff (bluetooth wifi etc.)
I think you may have got a kernel problem. Try and reflash the kernel.