Database Info

Blueplayer could = better A2DP sound

If anyone here has tried to use an i.tech stereo headset (like the R35 or S35) or other A2DP headset and has been dissapointed with the sound quality (commonly referred to as a "ringing" distortion or hissing over the sound) using the A2DP for tornado hack, its because the MS Bluetooth Stack isn't 100% compatible with all (most) headsets. Its particularly noticeable on i.tech, but the reduced quality is true on many others as well.
In case you didn't know, Blueplayer is a standalone app that streams music to A2DP headphones even if the phone doesn't support A2DP in its own stack! That means any phone with bluetooth (some even claim older 1.1 devices as well) can bypass the usual MS stack in our devices and stream stereo sound directly to a compatible headset!
The software was written for Nokia S60 devices initially, but there have been Pocket PC and java versions (only compatible with specific phones) released since then as well.
I'm very annoyed by the sound quality of my itech R35 paired with my imate SP5. I'm 100% sure that software such as blueplayer would solve this problem. However, the PPC and java versions don't seem to work on my device.
Can anyone help me figure out how to make this work? I tried extracting the files from the PPC cab file, but its complaining about missing libraries. The install may add some things to the registry that I'm missing.
Better yet, does anyone have anything like this for WM Smartphone?

what are you missing? I got blueplayer running with my S35 and the quality is excellent and range good(for me)...
Unfortunately I am using a Wizard...

I wish I could get it working!
I can't figure out what it is, but I'm having trouble.
Normally I can make any app work (even if its for PPC) by pulling the files off of a PPC installation, and run the .exe on my smartphone and it just works.
But I keep get errors about libraries not existing or being in the wrong place. I need to figure out exactly what happens when the app is installed- what files go where, any registry changes, etc... There's gotta be a way to make it work on smartphone!

From memory,
There are a few files and registry settings that I can remember but barely, but if you want I can try to install it again. I removed it because I don't use MP3s anymore..

Yeah, if you don't mind helping me out, that'd be amazing (also for the smartphone community as a whole).
Why don't u use mp3's anymore?

I can just look up the settings for you, you got to do the work ;-)...
I find them too large for my 1Gb MiniSD, using AAC+ now... nice quality and file size.
Just PM me what you want to know...

Well, I don't know what kind of entries this will place in the registry. To be honest, I'm not sure how to check myself either. Is there a way to tell EXACTLY what a .cab does?

Found it!
Interesting program for those in my situation:
http://thinkabdul.com/2006/12/20/ms...nformation-from-windows-mobile-cab-xml-files/
lets you see exactly what steps a cab installation goes through. Any reg. items, what the actual filenames are, what directories they are placed in, etc...
Amazing little tool.
However, I still haven't gotten blueplayer to work on my sp5... I wonder why?

thanks for the link, I needed something like that as well, going to compare the differences in the Widcomm bluetooth hacks...
BTW, how do you get blueplayer to work on a smartphone anyway without the touch screen?

Oh, simulating a touchscreen is easy... most apps let you navigate using the joystick, but it gets annoying and sometimes a touch is needed to click (for example an ok button).
There's a great little app call SPhelper that places a mouse pointer on your screen that can be navigated using the directional joystick, and "clicked" like a screen tap.
Its pretty cool.
Anyway, the problem is that I can't get Blueplayer to operate, even with all the .dll files in the right places. It says its missing something.

new2city said:
I can just look up the settings for you, you got to do the work ;-)...
I find them too large for my 1Gb MiniSD, using AAC+ now... nice quality and file size.
Just PM me what you want to know...
Click to expand...
Click to collapse
Here's all I know:
I poked around in the .cab installation and found that there are 4 .dll's that go in the \windows dir (msibtstk.dll, msibtapi.dll, CHS.dll and TW.dll), and two .exe program files that go in program files\msi\blueplayer (STLoader.exe, and MPOBCE.exe). AFAIK, there don't seem to be any registry entries that it inserts.
Now, I've done this with PPC apps before, normally all I have to do is run the .exe after all files are in place, and it will work (obviously with some minor annoyances due to missing the touch screen).
However, every time I hit MPOBCE.exe, all I get is:
"Alert
Can't find MPOBCE or one of its components. Make sure the path and filename are correct and that all the required libraries are available."
There's gotta be something I'm overlooking... Anyone?

No man, there are some(I found some) entries, but I thought you were set and removed them already..
will reinstall and get back to you again...
BTW do you do a full backup of your phone? I use SPB backup and it is good..

oh, cool, I couldn't find any... let me know!

entries but not sure if working...
Here are the two registry inputs(rename to *.txt) I found on my system.. Unfortunately, I couldn't get it to work this time as I am using Widcomm bluetooth stack... wonder why.... Last time I used this was with MS Stack on...

new2city said:
Here are the two registry inputs(rename to *.txt) I found on my system.. Unfortunately, I couldn't get it to work this time as I am using Widcomm bluetooth stack... wonder why.... Last time I used this was with MS Stack on...
Click to expand...
Click to collapse
No, that makes sense. The Nokia one is designed to operated by tunnelling through the s60 stack, and the WinCE version was most likely designed assuming the MS one.

No go... I entered all this stuff exactly like you said, and I get the same errors.
Interesting to note is the drivers reg keys already existed!
It appears that the other exe (stloader.exe) did run and I think entered those keys. The actual program tho, seems to not run (and therefore never entered the proper keys, I'm guessing).

Sorry man.. to get your hopes up..
Right now, I got Axim Widcomm Stack running on my Wizard, but still get the memory issue after a long time powering off bluetooth.
oh well, back to waiting and testing new stacks..

Hey, I've got another idea if you wouldn't mind helping me some more...
Could you try to manually install it the way I've been doing on your pocket PC device?
The reason I ask is because it will determine if there's some sort of PPC-specific code (which I don't think I've ever encountered or even heard of before).
I attached the files and directory structure that I extracted from the cab. If you could, please try uninstalling BluePlayer and tell me if you can get this to run by manually copying the files here.
If it doesn't work for you either, than its because my method is flawed and I'm missing something here... and I shouldn't give up yet!

ok, I will give it a go, but most probably I can only go as far as getting the program to run... Feel comfortable with the widcomm stack, don't feel like disabling it..
just give me a few hours.. my stupid SD USB card reader not working properly... got to look for my cable.. damn!!

good news is, the program starts with the exceptions
1)at first start after putting the files in place, the program starts a few times with the L2Cap error...
2)After a few failed restarts, followed by a softreset, the registry settings in drivers(L2Cap..) are in place and the program runs without error.
3)Now it's up to you to test it with MS stack bluetooth on, as I cannot confirmed this for you.. good luck buddy...

Flashing ROM question.

Question about ROM flashes.
I'm actually an IT professional in the work related field, so any basics need not be explained. I am still new to Windows Mobile devices and would like to know what this means for my phone.
The way I view a "ROM" is as a firmware, or static programming on a chip. Maybe even a CMOS imprint. In this field, such things are semi-permanent at a component level. For instance, you don't download a .cab file to upgrade your bios (as many "ROMS" seem to come in .cab files), you boot your system on a floppy and run an application that flashes your CMOS with the new image.
What would we assume the "ROM" is on Windows mobile phones? Is it a chip hidden inside of the phone, separate from the primary memory? Is it simply considered all that is in the \windows directory? I don't see why .cab files can flash the ROM.
This leads me to the question, if you do a hard-reset, I assume there's secondary memory on the phone with the \windows folder and all the factory defaults. The memory must serve no other purpose other than to harbor these defaults in the need of a hard-reset. Does flashing your "ROM" also apply changes to this chip containing the default OS image?

Hi, here a short description:
ROM:
The ROM is quite similar to a computers harddisk AND RAM (All-In-One), but the OS has to and additional software can be integrated via flashing and is therefor fixed. All data you flash will stay in the ROM after a Hard-Reset.
Some ROMs also contain a Bootloader-ROM and/or a Radio-ROM
Bootloader-ROM:
This is quite similar to a computer's BIOS
Radio-ROM:
The firmware to your PDA's built-in connection devices (e.g. GSM, Bluetooth, WLAN,...)
Hard-Reset:
A Hard-Reset is similar to a comlete reinstallation. Some computer vendors add a recovery CD/DVD to their products. On a Windows Mobile Device the Recovery-disc is integrated in the ROM and will be automatically installed during a hard reset.
And to complete this one ;-)...
Soft-Reset:
A Soft-Reset is similar to a cold restart of your computer. By the way, there's no possibility to "shutdown" Windows Mobile like you are used to with Windows XP or Vista.
Oh, and you cannot install a ROM using a cab-file. Cab-files are "executables" to install additional software. They can only be installed on the device. ROM's have to be installed from a connected computer (There's also a resolution to install a ROM from a Storage Card, but i am not used to it and cannot give you more information about this. But you'll find it, searching in the forum).

jon_k said:
Question about ROM flashes.
I'm actually an IT professional in the work related field, so any basics need not be explained. I am still new to Windows Mobile devices and would like to know what this means for my phone.
Click to expand...
Click to collapse
Me Too.
jon_k said:
The way I view a "ROM" is as a firmware, or static programming on a chip. Maybe even a CMOS imprint. In this field, such things are semi-permanent at a component level. For instance, you don't download a .cab file to upgrade your bios (as many "ROMS" seem to come in .cab files), you boot your system on a floppy and run an application that flashes your CMOS with the new image.
Click to expand...
Click to collapse
Yes, it is firmware on the chip, but like a BIOS, it exists after the phone is off, the battery removed, etc. The stuff in the cab files that you install doesn't. Well, let me retract that. The stuff in the cabs and your data stays there after a soft reset, and removing the battery (at least for a short while, YMMV), but my experience has not been that the data stays there after the battery is out for a while (again, YMMV).
jon_k said:
What would we assume the "ROM" is on Windows mobile phones? Is it a chip hidden inside of the phone, separate from the primary memory? Is it simply considered all that is in the \windows directory? I don't see why .cab files can flash the ROM.
Click to expand...
Click to collapse
Yes, it is a chip. Most of the time, they don't use discreet transistors for these time of things. They are prohibitively large and expensive to solder together to make the memory, not to mention power hungry.
To answer your second question, if you peruse the various ROMs here, you will see the following:
Base operating system: This is a common denominator. This is Windows CE/ Mobile edition, WM6, whatever you want to call it.
Additional CABs: This is the flavor the chef uses in his/her kitchen to make the ROM do what appeals to them (and their audience). These can techniclaly be split out and individually installed if the cook puts them as a cab file that you copy to the phone and install from that file downloaded.
jon_k said:
This leads me to the question, if you do a hard-reset, I assume there's secondary memory on the phone with the \windows folder and all the factory defaults. The memory must serve no other purpose other than to harbor these defaults in the need of a hard-reset. Does flashing your "ROM" also apply changes to this chip containing the default OS image?
Click to expand...
Click to collapse
What will happen when you hard reset is the ROM that was flashed to the phone will be as it was when you first burned it to the phone. Here's an example: You buy the Kaiser marketed as an AT&T Tilt on 1/1/08, use if for 6 months, and on 7/1/08, you hard reset it. It will be the same as when you turned it on for the first time.
Another case: You buy the phone on 1/1/08, and download a ROM from Dutty, or whomever, and you carefully follow the noob instructions (like I did), and flash it on 1/2/08. You do a hard reset on 7/1/08, and now the phone is the same as when it was last upgraded, so it will be the 1/2/08 version that it goes to.
Clear?
Hope this helps, and if there are others that want to correct me, please do so.

Fairly good explanations.
It makes a bit more sense now.
I'll post my new understanding of the control structure and functionality based on everyones post above. If you want to confirm, deny, or alter any of my perceived facts I'd appreciate it! I just like to know a basic understanding of the device functions internally so I can be educated when tinkering with things.
The radio ROM = ROM that controls the radio. Contains frequency ranges/broadcast tweaks for different locales, probably if tweaked can also allow illegal higher wattage transmission power. Some interesting (and surely FCC illegal) hacks are probably available here.
The device ROM - the upper level functions of the phone. Probably has support for the type of WIFI and bluetooth adapter you have. Has to have compatibility to interface with the radio ROM for phone functionality to be supported. Also is what interfaces with the GPS radio, probably the phone, links the keyboard to the OS, etc. Probably handles API between radio ROM and Windows mobile?
The Windows Mobile OS, which is the operating system itself. It communicates with the ROM, and is limited by what the ROM is limited by. Any .cab's or software retrieved here will enhance the OS, nothing more. A hard reset will bring the OS back to it's original state. (Though ROM upgrades remain.) Any cabs installed or changes to \windows in general made will be lost during a hard reset. It restores all content under \windows to it's default state.
Sounds about right with my new understanding. I think for now I'll avoid flashing the ROM. I'm pretty content with modifying the Windows registry hive since it can easily be restored with a hard reset if I bork up a registry key. Unlike the registry, a ROM if a member here misses something (I doubt they're working with much device documentation) a small coding mistake by them could ruin the phone.
Maybe I'll be more prone to start flashing ROM's if there's a way to extract the current ROM for my phone. Perhaps I can update the ROM through ATT or HTC, and use a packet sniffer to sniff the location (likely http URL) of the ROM file.

One further question though,
Until several minutes ago I thought the ROM simply contained device drivers, etc. Stumbled upon this post however.
rkorzuch said:
Tool worked perfect on my AT&T Tilt. Just installed the HTC ROM. Much nicer than the AT&T ROM.
Click to expand...
Click to collapse
I'm now assuming the ROM contains the OS that is flashed on to the internal storage card as well, with it's own custom branding on the OS, own default application set, etc. As well as it's normal functioning with device communication etc. Is this safe to say this is how it works?

jon_k said:
One further question though,
Until several minutes ago I thought the ROM simply contained device drivers, etc. Stumbled upon this post however.
I'm now assuming the ROM contains the OS that is flashed on to the internal storage card as well, with it's own custom branding on the OS, own default application set, etc. As well as it's normal functioning with device communication etc. Is this safe to say this is how it works?
Click to expand...
Click to collapse
Yes jon_k,
The ROM contains the WM OS. That is what the cooks are changing primarily (more specifically, most of them change/add/delete the bundled apps that come as part of the shipped OSes). Most now are also expanding the RAM/storage portion of the ROM to allow for more usable storage. More and more cooks are also ripping out some of the MS bloat .
You should do a hard reset and then force a soft reset before it does the device customization part. You will end up with a Tilt with none of the AT&T bloat (game demos and such). If you don't like it, hard reset again and let it finish.
If you get real adventurous you can install HardSPL and one of the cooked ROMs (or the HTC one).

Possible to Replace a System File without Rooting?

I am a NOOB, but I like myself just fine. The video for NOOBs is funny, but IMHO, should be a bit more serious.
I'm one of those people experiencing issues with GPS and TTFF being excessively long on the MT. Cry.
If I run MyPhoneExplorer, I can see the system file structure, and I believe I can move files to the phone. I believe I can do the same with SwiFTP.
Can one drop replacement GPS libraries for example into the SYSTEM and SYSTEM/HW sub-directories using a program like MPE, or an FTP program like SwiFTP without rooting, and would they be honored on the next reboot?
Would I be mangling some check-sum or other that determines the integrity of the system loaded?
I'm one of those users that doesn't really want to root if not necessary, but I wonder if doing some mod like the above - would doing so lay subsequent update pushes from VMUSA to waste?
Also, I'd really like if possible to flag some programs not to load, unless I explicitly ask them to load via the U.I. with intent. I suppose I'd have to root to do something like that. Perhaps with Ginger-Break? Would doing this make subsequent updates problematic?
Any information regarding my constraints and options to effect both of the above would be very appreciated. Thanks.

There are ways to mount the various partitions from a host machine (e.g. Linux) while it is in the "emergency" flash mode, which would permit what you want to do. Doing this is quite dangerous - at least as much as rooting the device and perhaps more-so.

I appreciate the response.
OK, if I were to root via Gingerbreak and install the files that way, then un-root, would my system then appear to be (to an update provided by Motorola or VMUSA) as something which couldn't be updated?
In other-words would rooting put me on a path to having to use specially modified updates?
Thanks.

Depends on what you change.
In GENERAL no, the update will come through. The major risk is that it crashes on install as some part of what you changed is a dependency but is not reloaded. This is rare, but can happen.
So.... root, install Clockwork, and make an immediate Nandroid backup BEFORE you screw with anything. That SHOULD allow you to un-hose yourself if you get in trouble.

[Q] Opening zune wp7 backup file

hi all,
i've backed up my wp7 and i'm curious about the backup file's content and it's opener. does anyone have a zune backup opener?

Not possible, backup is encoded encrypted.

sensboston said:
Not possible, backup is encoded.
Click to expand...
Click to collapse
if the backup was encoded, then how wp dibr opens it

What's wp dibr?
aramadsanar said:
if the backup was encoded, then how wp dibr opens it
Click to expand...
Click to collapse
What's "wp dibr"?

@aramadsanar: I'd like to know too; a quick web search didn't turn up anything useful. If somebody has managed to crack the backups, that would be incredible.
@sensboston: "Encrypted" please, all text on a PC is encoded (for example, your browser probably received this text in ASCII + some extension that uses the high bit, but it could be UTF-16 or something...) If the backup was just in some encoding, for example Base64, this would be a lot easier. Technically, encryption is a kind of encoding, but "encoding" by itself implies simply needing to know the algorithm is enough to easily decode it.

GoodDayToDie, of course I know difference between "encrypted" and "encoded"; I just wanted to say "encrypted" not "encoded" I'm working on the project with some issues with Cyrillic encoding so I've typed it automatically LOL

rbrunner7 said:
What's "wp dibr"?
Click to expand...
Click to collapse
wp dibr = an sldr thingy, which i don't actually know
GoodDayToDie said:
@aramadsanar: I'd like to know too; a quick web search didn't turn up anything useful. If somebody has managed to crack the backups, that would be incredible.
@sensboston: "Encrypted" please, all text on a PC is encoded (for example, your browser probably received this text in ASCII + some extension that uses the high bit, but it could be UTF-16 or something...) If the backup was just in some encoding, for example Base64, this would be a lot easier. Technically, encryption is a kind of encoding, but "encoding" by itself implies simply needing to know the algorithm is enough to easily decode it.
Click to expand...
Click to collapse
yea, it would be very useful to crack them up, i got many datas on the 'dead' (read: unrestorable) backup. what about starting with disasming the dibr system or maybe, ask someone here to leak wp7 pb

Is there any news about encryption of wp7 backup data?
I researched a little bit WPUpdate.exe tool and found interesting thing. For making backup we should tell device to update itself from fake update file.(but it's a simplest part of research.)
It looks like update agent on device encrypts backup data and provides possibility to copy it to PC. But i'm not sure. I didn't find information about encryption on wp7.
Maybe somebody has some information about backup process or encryption of backup. I will be grateful.
I'm sure it should be interesting and very useful to implement parser for this file's type.

Does anybody know what is Dibr? I can't find any information about this component in google and its very strange.
I researched backup and tried to found a way to decrypt it. I found DibrPlugin in folder with UpdateApp on device's Rom. I think it is very interesting component, because it contains some internal components like DibrCrypter, DibrDeviceReader, ... I believe it should contain information about keys for encrypting. But of course i'm not sure about it. Maybe someone researches this and can answer some questions about backup?
p.s. unfortunately for me this library was implemented for working on device. And of course it's ARM-based, but i have not enough experience with ARM. But it's a great opportunity to learn ARM. :good:

Wow, I would have thought that after all this time someone would have found a way to decode this.
Anyone know any informations about what the restoration is limited to? Can you restore onto a different device? (meaning a universal key for the AES encryption) Can you only use it on the same device but even after messing around with it's internals/rom/...(meaning there is a rule to get the key from some hardware id) or does it not even survive a really strong reset (meaning it's a random key stored in the system)

Restoration is limited to the exact device the backup was made from. Same model different device does not work. Hard-reset doesn't override the ability to restore, although I've heard that some custom ROMs might.

[Q] wince/android headunit hack

Hi guys.
been reading alot about hacking the wince part of these units. When the gps is on the wince too. By exploiting a autorun file on the sd card. But my unit has gps on an adroid partition. So if I remove the sd car android still boots. Is it possible to hack these?
my unit is an allwinner a10 device. What I would like to do is get to the bluetooth software and see if I can fix an issue with the phonebook.
it doesn't put my contacts in alphabetical order. Also I seen some nice shells out there so maybe a change of shell.
I have only one real issue with the android side of the unit and that is lack of bluetooth support. I would like to correct this too. As far as I can see the android side is rooted. I ran software that says it is anyway.
First post so applogise if it falls short of requirements let me know I will update it if need be.
Thanks in advance

Bump.

Yeah mate, I have the exact same issue.
Phonebook is pretty terrible, only real thing that the unit lets me down on