Related
Well, if HTC won't do it, someone needs to... I want to see if it can be done. Can we create our own ATi Imageon Drivers for the MSM7200/7500?
step 1: Find out which Imageon is in there...
Here's the official list
I just hope it's not some custom job!
Think it's worth a go?
^^Bump^^
This definitely needs to be done. I wish I had the know how to develop this but unfortunately I don't.
you should really try posting this somewhere else, like maybe in the development and hacking forum, since the vogue is not the only device that suffers from this.
this is really a great idea in my opinion, and im sure there are those out there that know how to get it done!
Would be awesome, but it seems like it would be a huge undertaking. I'd imagine that Qualcomm has it locked in some way, preventing it's use if the license to use that component wasn't purchased as part of the hardware platform. I really have no idea though. I'll keep hoping : )
A journey of a thousand miles begins with one step... we have a ton of talent here, HTC and Qualcomm don't seem to want to release it... I think that it might be time to start building our own.
Post copied to development and hacking but I quoted first post of this thread to give proper credit for the idea.
I remember reading somewhere that there is actually a $2000 (and growing) cash prize for the msm 7xxx drivers. Totally support the idea.
yep... I think it's up to 7 grand now.
I'm going to wait until the end of March before I start anything.
Draiko said:
yep... I think it's up to 7 grand now.
I'm going to wait until the end of March before I start anything.
Click to expand...
Click to collapse
well if anyone could point me to link i willing to offer 200 to play quake on my phone
problem is that writing device drivers is the hardest program one can get into
the driver is limited to a very tiny mem footprint and must never be alowed to crash
even if the memory it's using is lost on the heap
and one needs access to alot of whitepapirs from the hardware maker
which is prob why htc did such a poor job writing then driver themselfs
because they were too cheap to pay qualcomm for it
Rudegar said:
problem is that writing device drivers is the hardest program one can get into
the driver is limited to a very tiny mem footprint and must never be alowed to crash
even if the memory it's using is lost on the heap
and one needs access to alot of whitepapirs from the hardware maker
which is prob why htc did such a poor job writing then driver themselfs
because they were too cheap to pay qualcomm for it
Click to expand...
Click to collapse
It's not supposed to rain on parade day...
I used to write assembly language device drivers for embedded real-time systems. Doing so requires a high level of knowledge, experience and documentation WRT:
1. Dev & testing tools and environment
2. The target hardware (detailed doc)
3. The target OS kernel and driver hooks
4. System-level programming mind-set (different from app dev)
Quite interesting and rewarding if you have the above - quite difficult, bordering on 'not gonna happen' if you don't.
Sincere best wishes to those who give it a shot!
My entire impetus for this thread was to start gathering people with the skills and talent needed to tackle driver construction. If open-source maniacs can do it, we can too. I have some experience with assembly... the tricky part is going to be finding out the specific commands, paths, and function calls for the embedded hardware. There's going to be a LOT of trial and error involved.
I'm starting to look for the Windows CE DDK right now. Come April 1st, if there is no word from HTC, Qualcomm, or Sprint on this driver issue, I'm going to round up as many capable people as I can and try to hammer this out.
Something that might shed some more light on the entire driver issue... Uh oh
Big Uh oh...
if this ever comes together fully it will be really cool but i still dont get why SE didnt include drivers in the first place??
comeradealexi said:
if this ever comes together fully it will be really cool but i still dont get why SE didnt include drivers in the first place??
Click to expand...
Click to collapse
As posted before, they probably bought it at a cheaper price by having the drivers restricted. If they were to pay full price then maybe the driver would have been included. It's kind of what Palm did back in the day when they could have spent the extra $.05 for a higher quality speaker but didn't on the Palm III series. I'm pretty sure this is a cost cutting technique used by most electronics manufacturers.
if im paying £500 for a device why not stick $0.5 on the bill! thats a shame
Damn right. I agree with all you guys.
The fact that I cannot get graphics hardware acceleration from a 500 USD+ device is absolutely ridiculous.
I love my Xperia X1, but in hindsight, I would've NEVER supported any product like this had I known it was the case.
Shame on HTC and Sony for swindling their customer from the "rich, multimedia experience" they promise so much.
Bastard Sony/HTC.
well boot android and youll have more qualcomm support..since they own the gpu chip msm7xxx devices uses now, thats what chipset all official android handsets use, even non htc android phones.
ajclai08 said:
well boot android and youll have more qualcomm support..since they own the gpu chip msm7xxx devices uses now, thats what chipset all official android handsets use, even non htc android phones.
Click to expand...
Click to collapse
and thus, there is driver support natively in android for us?
If that's true, what's stopping us from reverse-engineering the android driver and building a WinMo driver?
If we had a starting point, it's feasible--but without a starting point (or white papers), it's impossible.
i completely agree with this we have waited enough for the garbage companies to put out. Ive gone through three HTC phones already with graphics Acceleration turned OFF... WTF!!!
Hey,
I have 3 iPAQ 5450's sitting here, and I could probably spare one for development if anyone would actually be interested in it. Note that I only have one working cradle at the moment (might be able to get another if serious inquiries are made).
I'm fairly annoyed with a few aspects of WM2003, as I'm used to my HTC Herald (T-Mobile Wing). Simple things like no task manager like in WM5/6 (can't remember which is on the Herald), the the tray half-way working like I think it should, etc.
Here are the specs on the unit (shamelessly copy-pasted):
Processor: Intel XScale PXA250 400 MHz (I think this is actually faster than the Herald's OMAP 300MHz?)
* ROM 48 MB - Flash
* RAM 64 MB - SDRAM
* Installed RAM 64 MB
* Supported Flash Memory Cards SD Memory Card
* Max supported RAM 64 MB
* RAM technology SDRAM
* Installed ROM (48 MB max supported) , 48 MB Flash
* Display Type 3.8 in Color TFT active matrix ( Transflective )
* Display type 3.8 in TFT active matrix
* Image 16-bit (64K colors)
* Display Resolution 240 x 320
* Input device type Touch-screen , Stylus
* Type Touch-screen , Stylus
* Security Devices
# Wireless Connectivity IrDA , Bluetooth , IEEE 802.11b, Fingerprint reader
By the way, I just tried to edit this message, and have to wait just to edit? I'm not posting a new post or thread, so why does it make me wait?? Could I get my account reviewed and whatever flag set? The account might not be used a whole lot, but I've been registered since 5/28/09!!
Hi,
- Can you dump the rom of your device like here: http://www.a701.org/Forum/viewtopic.php?f=18&t=465 ?
Regards, ansar.
I might be able to do that... Would the ROM from BootBlaster (URL wont work, "To prevent spam to the forums, new users are not permitted to post outside links in their messages. All new user accounts will be verified by moderators before this restriction is removed." -- I've had the account over a YEAR now!!) work? I already have two of those as I tried Familiar (OPIE)
Hi,
Dump the three .raw files i.e. part00.raw, part01.raw, part02.raw (and /or part03.raw may be not needed if it is your storage card)
Then zip/rar them, upload to rapidshare and when logged in xda send me a private post with the link (in text mode).
If you already have the last hp rom upgrade file, if not download it, and upload this too.
Regards, ansar.
I'm not sure exactly where to get the utilities that are listed in the Mio thread you linked to. There were no links in the thread.
From what I understand, BootBlaster saves gzipped images of several areas: Boot, root, and [something else]. I already know how to use bootblaster, dd, and gzip. Hopefully it will have the information you need.
As far as uploading the HP WM2003 upgrade, I'm not too sure if I'm supposed to do that or not, as it is a paid upgrade? It is what is installed on all 3 devices, so I guess if someone will be getting the extra they might need it
WM5/6 needs at least 64MB ROM.
And porting device from WM2003 to WM5/6 is not an easy thing.
In past only 2 or 3 hTC phones did get custom ROM update from WM2003 to WM5/6.
I would suggest you to sell those iPAQs and buy something newer.
Doesn't really *have* to be a full upgrade to WM5/6... if there are ways to get some of the same functions over, I'd be happy. But WM5/6 would be kinda nice (though probably would be bloated).
One fo the other reasons not to just toss these units is that they are actually more powerful than some, if not most, of the cellphones being sold in the US right now. Hell, my Wing isn't *that* old... and it only has a 200MHz CPU. These iPAQs have double the CPU power. They might not have the greatest amount of memory, but if I'm right, the bootloader installed by bootblaster supports booting from a CF/SD. So the flash memory may not be an issue. (Not to mention that the filestore on the iPAQ will actually go poof if the main/backup batteries die, so sd/cf might be a better overall option).
You can't really compare 400MHz CPU made in 2002 and 200MHz CPU made in 2005.
If iPAQ CPU does have more MHz it dosen't mean it's faster.
BootBlaster is for Linux and Windows Mobile CAN'T boot from SD/CF card.
Not even to mention that iPAQ does have slow NOR-flash, instead of fast NAND-flash used in all new devices.
For point 1 & 2, that does make sense, but isn't there a standard to how MHz are measured? I guess I could see if there is a program to calculate the mips on both, though really mips isn't exactly perfect measurement either. But... the iPAQ actually runs many things I've much smoother than the Herald, which is why I assume that the iPAQ hardware may be a bit more robust. I could be wrong, as I'm a computer guy, not really handheld-savvy.
For 3, "Note that the Linux Bootloader will also boot PocketPC". Its just a bootloader. Much as GRUB will load linux and windows, the bootloader here seems to not care what it loads.
One thing I didn't know is that the bootloader couldn't boot from the SD/CF into another OS. I could swear I'd heard of someone doing so somewhere, though I can't find the page now. I figured the hald-held would have some form of BIOS, and that it perhaps could see the SD slot, similar to how a PC can boot from USB (or grub can as well).
Not sure how the NOR and NAND flash would affect it other than in read/write times. Again, this is something I'm pretty new to.
Anyhow, the point of my posting this thread was to see if anyone wanted to do some ROM work, perhaps some things could be used in WM2003 as well as WM5/6. I'm sure there are some things that could be done, and improvements made, with the machine, as it isn't 'bad' hardware. Granted, it's not a cell-phone, but more of a PDA with wireless and bluetooth capability. But it is something that can be made useful, instead of collecting dust in a closet, or perhaps an exhibit case I do have an old working Commodore 128D that is more an 'exhibit' than anything else... talk about a blast from the past!
I hate to see things set to the way-side just because there is something new and shiny out. Heck, I even re-purpose old-as-dirt PCs into useful things... I have a 500MHz BSD router that kicks the pants off any consumer router that costs $200+. I have another old 1.7GHz machine that acts as a CCTV/DVR. So it is natural for me to find useful things to do with the old iPAQs. Doesn't help that the Herald eats batteries
So, if I can get the old dog to learn some new tricks... it would be nice. I'm just trying to see if there is someone out there that knows *how* to teach the thing some new tricks.
What I want to say to you is that most likely no one will do any ROM cooking for h5450, WM2003 ROM modification was to hard for most users and never got any easy-to-use tools. Questions like yours pop up from time to time and no one has made any progress so far.
I cook ROMs for hx4700 and hx2000 series iPAQs they come from 2004 and 2005. Keeping them up-to-date with WM6.5 ROMs now was only possible because they did receive WM5 update.
ps not all old dogs can learn new tricks.
So I guess I'm kicking a dead dog? Wish there was a way to get WM5/6 on these things then... I wonder how much RAM the cellphone drivers/software use... if it is enough to get it below 48MB (tall order)... but yeah, I'll shaddup now
Duplicated post, delete me
From other side, I've heard that some ipaqs on the very beggining were sold with PPC Phone Edition OS (when you insert sim card to this "non working" slot under battery, you'll see gsm icon). If somebody has got such, and can post a rom dump (using bootblaster) to me, i'll be grateful.
Why?
I found a prototype motherboard, probably from iPaq h56xx (h5610), and it is to be identical to 54xx one, only rf module seems to be different.
Here is a thought.. Wonder if Android would run on these things...
Sent from my LG-VM670 using XDA
If you still have one to spare I would love developing a rom for it. If you can tell me what your looking for from the rom then I could work on one.
Yeah, still got 2 of these, could easily spare one. Right now the only things I've really been using the one for is a remote control for my TV. Lost my universal.
Would love to be able to get something going for it though. Something my kid could play with, perhaps a reader app. Just not sure if any exist for something as old as wm2003.
Right now the cash is tight, but once i get some to spare for shipping, I'll update ya, so you can tell me where to mail the thing.
Sent from my LG-VM670 using XDA
Is there a chance you could send one my way? I would love to work on and develope a rom for it!
Sure. Just need to get out of the financial nightmare I'm in so i can afford shipping.
Sent from my LG-VM670 using XDA
I will foot the shipping bill for you no problem. Thank you so much for this opprotunity I have never developed for this device before. Where are you shipping it from? Send me a private message with any info you need from me and ill reply with my address and any of the info. Thanks again!
Let me know
Let me know how this goes as I have a h5450 and was looking for something to do with it as it is at me mothers and been on charge for some time lol as well if you have any stable runs I will test
Someone already created an application for running PSgroove on Nokia N900(android). Is it possible for us to have this on HTC diamond or other windows mobile phones.
It's basically emulating a dongle inside our phones. Does anyone have any idea how to do this?
hello,
the N900 port is not the same as Android, Nokia N900 have a Linux based OS but it's not Android, I have an Xperia X1 myself, and today I already downloaded Android for X1 and prepared it on my X1 just to test with it when the Android port is out soon....
in case it works, i will post all needed steps
You're right. N900 is pure Linux, but still the developer said it will be ported to android too. Damn, The only group that will miss this nice program will be us, windows mobile users, at least in the high end mobile category anyways.
it's a good idea for you now to download Android for Xperia x1 and get the feel of it, u can revert back to WM simply by restarting, this way u can be ready when the android release is out, and let's hope it can run on this emulated Android/Xperia,the Guy working on the Android port said it has to be rooted (Super User privilege) and i think this Android release is rooted, because when i run Terminal Emulator in Android and switch to su, then type id, i got id=0 ( and 0 is root ) so let's keep our fingers crossed
Source code for linux phone released
The author has already released the source for the N900 port - linux.
http://github.com/kakaroto/PSFreedom
I looked briefly in the code and it seems pretty simple actually, except for coding the Hub stuff (there I lost it)...
I think it is not that hard to code a simple app that could do it on Windows Mobile directly, considering that our devices are capable of emulating a USB hub...
Maybe some experienced coder could give it a go??
mihaiolimpiu said:
The author has already released the source for the N900 port - linux.
http://github.com/kakaroto/PSFreedom
I looked briefly in the code and it seems pretty simple actually, except for coding the Hub stuff (there I lost it)...
I think it is not that hard to code a simple app that could do it on Windows Mobile directly, considering that our devices are capable of emulating a USB hub...
Maybe some experienced coder could give it a go??
Click to expand...
Click to collapse
Yeah, that's the catch. How to program USB in windows mobile?
this project has my support. Sorry, cannot contribute to coding, but am free to test!
I am also interested in this project and I am waiting impatiently to test the PSGroove on Windows mobile
Cseb87 said:
I am also interested in this project and I am waiting impatiently to test the PSGroove on Windows mobile
Click to expand...
Click to collapse
me too i want it on my kaiser
touch pro2 user wanting this also, i know nothing about porting code but i am willing to test it!
Using Android to do this should be possible
Sorry everybody, I'm hedging my bets that there will not be a windows mobile port of PSGROOVE.
The reason ports have been landing on Linux/Android devices so quickly is because Linux/Android is open source and toying with drivers, controllers and the kernel is very easy. Windows Mobile is a very closed platform and even though the hardware might pose a problem, the OS is likely to be the deciding factor in the viability of something like a PSGROOVE port. Some operating systems such as Unix-based ones are designed to be easy to develop on at low level, others are not.
This is why we can have Android on WinMo devices and not iOS. This is why Linux and TI-84 already have ports of PSGROOVE but the iPhone port is as yet unreleased.
Far more likely is a version for an Android port on our devices. I'm not guaranteeing anything, and I'm not ruling anything out. Just a heads up.
I would like to understand how the code works, anybody knows a good documentation of that exploit?
maybe im missing something, but why is psgroove being ported (mainly) to phones ... wouldnt a laptop be a better choice? ... Someone please help a noob
lufcmattylad said:
maybe im missing something, but why is psgroove being ported (mainly) to phones ... wouldnt a laptop be a better choice? ... Someone please help a noob
Click to expand...
Click to collapse
You have a double male usb-a cable 5meter laying around? Nearly anybody has. Your phone is much smaller and you have a fitting cable everywhere
scilor said:
You have a double male usb-a cable 5meter laying around? Nearly anybody has. Your phone is much smaller and you have a fitting cable everywhere
Click to expand...
Click to collapse
lol
That's not the reason. USB controllers for the PC don't have a USB host function, which is essential for this hack. That's why you can't use you PC for this hack.
You can use a computer for that they are an usb host, usb-sticks are normally not . Install linux and have fun
here it is HD2 android psgroove port
hXXp://psfreedom.com/wiki/index.php?title=HTC_HD2
scilor said:
I would like to understand how the code works, anybody knows a good documentation of that exploit?
Click to expand...
Click to collapse
the original psgroove files(they recently updated teh shellcode to give lvl2 peek/poke calls
hxxp://github.com/psgroove/psgroove[/URL]
Openpsjailbreak which allows bdvd emulation
its basically the same as the ps groove only 4 values where changes
(0x78 0x78 0x78 0x78 to 0x62 0x64 0x76 0x64)this one needs to be updated to add the lvl2 peek/poke calls
hxxp://github.com/openpsjailbreak/OpenPSJailbreak
PSfreedom linux version
hxxp://github.com/kakaroto/PSFreedom
Exploit reverse engineering
hxxp://ps3wiki.lan.st/index.php/PSJailbreak_Exploit_Reverse_Engineering[/URL]
payload reverse engineering
hxxp://ps3wiki.lan.st/index.php/PSJailbreak_Exploit_Payload_Reverse_Engineering[/URL]
This port would be so bad just need to be able to make a usb hub emulator that can change the device address of multiple devices at one.
The descriptor for it is really easy to make. and one the hub is created just need to implement the exploit in the order described(port1,port2,port3,dc port2,port4, port 5 ,dc port3)
and port 6 is not neccesary at all to run the exploit it had the original use of just acting as a test to make sure the exploit worked and made the dongle led turn green. cuased a lvl1 panic if the device was ever removed)
The main issue with a windows mobile version is making the usb hub as we dont have that much in terms of open source drivers. So if someone could emulate a usb hub through there device we could easily get this rolling.
Would be nice to see this on my i900
if no tthis the only way i coul dthink of is to try to put linux on phone and porting from the n900. an dno not andromnia android linux it would be ubuntu linux
stupid new user cant post links :rant:
Hey guys, Evo owner here , i posted in the evo section and got 2 replies via PM's. I have 4 chips that are flashable for sale. I bought 6 Xplain boards and am using 2 of them. The other 4 are up for grabs. Let me know, more you want the less money ill offer them for. i respond VERY quickly to messages, thanks.
Hi,
I need to make my Wave II S8530 the best it can be. I have obtained the Bada 2.0.1 SDK (although the offline installer reported an error in checking the Common archive I crowbarred it in ok anyway).
It is my understanding that apps developed on the 2.0.1 SDK will not work on 1.2 devices, such as mine is this correct and if so how can I get the 1.2 SDK?
On another note, I thought S8530 was identical to S8500 apart from the screen, but I just read that Android is not available (here) for it because of the different LCD controller. How long will be treated as poor relations? I'm starting to wish I bought the Sony Xperia Play. Words of reassurance would not go amiss
http://developer.bada.com/badaforum...ide-sdk&messageId=39096&startPage=1&curPage=2
I have no idea, why they remove older SDK... maybe to push 2.0
http://developer.bada.com/devtools/archives
Anyway. Normally you can develop in 2.x SDK your 1.x Apps... only use old Apis...
Here you can find older SDKs and more...
https://opensource.samsung.com/
Attention!
Maybe not the installer, but other opensource related sources included...
Best Regards
Enough help you find always on developer page, and badadev.com and in forums
dr. strangecode is also a good place to be.
Thanks,
all those links are awesome.
I guess the opensource sammy S8500 zipped ROM would be the place where you started your RevEng of the OS. To improve this I guess you are adding object code from the ROMs for other models and pre-releases. I still can't see any source code for the S8530 but I can accept it is the same as S8530 and S8550 except for the display hardware.
prepulsar said:
Thanks,
all those links are awesome.
I guess the opensource sammy S8500 zipped ROM would be the place where you started your RevEng of the OS. To improve this I guess you are adding object code from the ROMs for other models and pre-releases. I still can't see any source code for the S8530 but I can accept it is the same as S8530 and S8550 except for the display hardware.
Click to expand...
Click to collapse
There is no opensource releases for S8500/S8530 nor any Wave series. All Samsung does release as opensource are Android things, just because they must to do it following GPL license.
rebellos, I found a S8500/S8550 zip archive at the sammy opensource site, I will investigate later.
Would I be right in thinking the crux of your (nor specifically, but also, rebellos) work is reverse engineering the bootloader so that you can make a better, multiboot, or nandroid (clockwork-mod) recovery type?
I'd feel safer RE'ing if I had a good back up.
If so I would like to write an ARM dissassembler, being RISC it shouldn't be too hard if there isn't a library already freely available. I guess you're all using IDA for this. I'd appreciate feedback how I could make this better.
I'd link to my hex editor/dissassembler, but as I haven't (reasoning I'd need a re-compile to separate if from by mainstream releaser) in short: it's rather basic, fast and maintainable.
I guess it would be usable in RE'ing the compression of Bada files too, but from reading the Bada 2.0 thread (first 5 pages) yesterday, it seems to have been wasteful of memory (256+256/128Mb) which is one thing I'm rather fond of, so maybe Android _is_ the way forward for this.
prepulsar said:
rebellos, I found a S8500/S8550 zip archive at the sammy opensource site, I will investigate later.
Would I be right in thinking the crux of your (nor specifically, but also, rebellos) work is reverse engineering the bootloader so that you can make a better, multiboot, or nandroid (clockwork-mod) recovery type?
I'd feel safer RE'ing if I had a good back up.
If so I would like to write an ARM dissassembler, being RISC it shouldn't be too hard if there isn't a library already freely available. I guess you're all using IDA for this. I'd appreciate feedback how I could make this better.
I'd link to my hex editor/dissassembler, but as I haven't (reasoning I'd need a re-compile to separate if from by mainstream releaser) in short: it's rather basic, fast and maintainable.
I guess it would be usable in RE'ing the compression of Bada files too, but from reading the Bada 2.0 thread (first 5 pages) yesterday, it seems to have been wasteful of memory (256+256/128Mb) which is one thing I'm rather fond of, so maybe Android _is_ the way forward for this.
Click to expand...
Click to collapse
Can you link me to S8500 opensource binary? I'm incredibly curious about that. Can't find it by myself.
I can't imagine what functions are missing in IDA. The only one annyoing thing is no functionallity of editing/patching binaries. I'm using ARMu disassembler/hexeditor to do patches, planned in IDA before.
Basically, mijoma, b.kubica and I am reversing/modding bootloaders and bada kernel. If you want recovery - use bTerm by b.kubica and make full oneNAND image. Altought it wasn't tested practically yet but I'm sure if you damage whole oneNAND, we'd be able sooner or later to restore whole dumped image using UnBrickable Mod/JTAG.
I cant believe that maybe mistake with W8550 !!!
I know samsung camrecorder use Rtos kernel to and some camrecorder like Wave chipset !!
Investigate camrecorder firmware opensource told you what in.
Found it this is BADA OS !!!
http://www.smxrtos.com/
Sorry, I tried that S8500 ROM link and you're right it was W8500. Man is https://opensource.samsung.com/ slow!
I ran IDA free briefly, after spending weeks on my own hex editor, and it filled half my netbook's screen with toolbars. I guess its really much better than my software. And then ho1od has Wave Remaker for viewing Firmware which I'm still to try.
I've attached my hexeditor software which presently needs .NET2.0+ and VCRT9. It only interprets Windows PE and x86 at the moment but if you like I could add/branch Bada and ARM.
Does IDA Pro have an emulation feature?
I've read upto about page 15 of the Bada 2.0 unveiled thread today and am still uncertain how much RAM (potential) this phone has. Wikipedia said 512Mb and it was on that basis that I purchased it knowing that 512Mb is a good indicator that a device will be Android ICS compatible.
I forget who of you is interested in the S8530? I'd need to look at the ARM OpCodes before I could help with LCD converter. But with Bada 2.0 coming ever nearer, ah heck, you'll all still want a Droid dual booter of course!
Rebellos, you are very good and honest to display a 1mm rule next to the SMD resistors that need modding for the unbrickable mod. That is a great mod, but I can't help feeling that JTAG is still an option if only because hardly anyone has
a) the skill, steady hand and practise to solder 0.2 mm pads
b) the iron tip to do so, smallest I've seen was about 0.6mm and about three times the cost of a dirt-cheap £6 0.9mm one on eBay.
Had a look at your googlecode tree, you are all far too skilled for me, I'm going to go and draw some buttons on forms.
Hello, I'm looking to find "pure" OTG devices. One that would have no need of adaptor and if/when connected it would directly be recognized by the phone.
What I have in mind is mostly a tiny flash drive which -with the aid of a converter- it would plug to PCs as well, rendering the exchange of files a routine task (as it is between PCs).
To my dismay the only I have found thus far is this: http://www.usbfever.com/index_eproduct_view.php?products_id=2704 , which is quite big and ugly and kinda defeats the purpose.
Also the device does not necessarily have to be flash storage, it can also be micro-bluetooth, micro-gps, micro-tvtuner or what have you. A whole -new- family of external devices aimed firstly for the mobile and (through a converter) secondly for the desktop.
If you have any other such device that you know it would be a welcome addition to this thread... Thanks.
Sorry for bumping/resurrecting this thread but it feels as if no-one ever heard of OTG devices, bit of a pity because it rather means that they're not that popular; which to me is beyond comprehension given how widespread the tablet/smartphone use is and how much it would be benefited by direct-to-OTG devices...
Apparently to most it seems like a not very useful novelty ...