Related
Hi there!
Is anybody working on porting linux to xda now ? Is any info about project's state available ?
I found this idea very interesting, and I'm interested in porting Linux on my cell phone - SONY CMD-J5. Internally xda & j5 is very similar(!) - both have hercrom100 cpu, twl3011 chip, and there is absolutely no docs on hardware, excluding firmware hackers' info (r00t.host.sk, http://hyperion.sp.unipg.it/bodhi3/), but there is still nothing that seems like datasheet.
HI
No help to give I'm afraid but am having a similar linux problem. Mainly connecting to a linux based wireless LAN and using telnet facilities on linux systems.
No progress
Hi,
As far as I'm aware no-one is working on it. Mostly because everyone is too busy with other stuff and it doesn't have priority. Maybe because people are too busy finding out what can be done with the current software.
One note though: when running Linux on an XDA you have nothing todo (or hardly) with the hercom chipset etc. The ARM that would run Linux is completely separate and would communicate with the GSM modem through a serial AT command interface.
OK, thank you.
And then a new question: if two devices both using hercrom100 & twl3011 chips, they must (?) have similar hardware IO ports. For example, it was concluded that on Sony J5 on-chip com port data register is accessible via 0xFFFF5800 port, and first timer's control registers are accsible via 0xFFFFF800, 0xFFFFF802, 0xFFFFF804 ports. I didn't find any info about this ports on the site's pages. What's the matter ? I know that they are busy people, and cannot spend a lot of time disposing XDAs. More politely, I want to ask - is any sort of similar info is available to anybody ?
In the XDA all or almost all I/O with the end-user is taken care of by the StrongARM chip. This chip communicates through GPIO lines and a serial port with the GSM ARM chip. This part is the custom ARM/DSP combo. I suspect that there will be great similarities between things like hardware ports on the processors themselves. I doubt that the are used in the same way as on the XDA. For the XDA port it is not needed to touch the hercom chipset at all.
Porting linux to something like such a Sony sounds like a very big and uncertain effort. With the XDA at least there is the iPaq, which is similar and has a linux port. Still for that port Compaq used a lot of internal specs that are not available on the XDA. I suspect the Sony to be quite different from the XDA because I don't think it will have and additional strongARM for starters. Do you know if the thing was manufacutered by HTC for Sony? Because if it is a Sony design than even if the chipsets are identical there is no comparison possible.
Hmm. I expected that you have a bit info about hercrom chipset.
Also I expected that hercrom chip plays a more significant role in the xda, than a gsm modem. But the firmware loaded to hercrom cpu might be useful - possibly it converts AT commands to the output on some ports to drive the gsm hardware; may be it quite plain for reverse-engeneering than Sony firmware, where gsm hardware driving routines mixed up with lot of other stuff. Hmm. May be, it is possibe to find a guy from, for example, HTC software development team, who can help us. Dreams, dreams..
"Porting Linux" is sounds quite good, but now it's no more than brave idea, you right.
There is no additional chip in the Sony that drives LCD, takes care of user input and so on. Also, I don't know who is real manufacturer of the device. It is almost certainly known that hercrom is the one and main cpu in the device. There are 32Mbit flash chip, in which resides the firmware. And this firmware is disassembled by ~10-20 volunteers.
Thank you very much.
And where is my Interactive Disassembler ?
Hello all...
Just some quick questions with xda and linux...
- What's the current status of linux support? Like, what works, what doesn't?
- How many people (or maybe also who) are actually working on porting linux onto the xda?
- What has to be done for xda linux support?
Thanks.
Pigeon.
Staus of porting Linux to XDA
Status of porting Familiar Linux to the XDA:
a) Lots of people think it would be totally cool
b) Nobody's doing it
We here at XDA-developers would love to help out and share our experience with the device and we can invest quite a bit of time. But we're not diving into this one on our own (just yet).
Given that Familiar Linux runs on an iPaq the job wouldn't be too great. Getting the kernel to run would be doable. Getting it to talk to the screen, modem and buttons may be a little more tricky. And there issues with the flash chips not being supported by Bootblaster (?). Probably the lack of a sleeve-interface and/or CF-card slot would make development a little bit more tricky.
All in all, it would be a Good Thing (tm) if some people that are really familiar with familiar would spend a secluded weekend with some of our gurus, sometime later this summer. Maybe do this as a project at CCC Camp?
Familiar and etc...
I've been using Linux/Familiar on my Ipaq for quite a while (2+ years). I'm also a developer for Familiar and GPE (not actively right now though, "busy" you know I have a fair bit of knowledge how it works as a distro. However I'm not really a Linux kernel/drivers hacker. I'm willing to help porting Linux onto xda for sure, though I don't really own a xda yet, which is even more tricky. Been looking around ebay for xda but haven't started really getting/biding one yet.
Anyway... I'm basically one of those i-am-not-buying-a-device-unless-it-can-run-linux person.
Cheers.
Lots of recruits
Looking like there are a lot of us on this site just gagging for Linux on our XDA. Hopefully by the end of the summer this will have emerged in some way then.
Perhaps now would be an appropriate time for somebody here, or elsewhere to take charge? Of course it has to be somebody who has time, and knowledge. Me personally am one of the many people who are eager to test, but don'y have a clue!
Many thanks. And heres to something getting underway very soon.
w w w . l i n u x . x d a - d e v e l o p e r s . c o m
here we come !!!
Martin
Maybe we could have a bit more detail list of what steps are needed to be done/discovered in order to have a usable (or full) linux port on the xda?
Something like...
- JTAG
---- locating JTAG pins(?)
- bootloader
- drivers(?)
- etc(?)
Someone who really knows about the xda can come up a comprehensive one and people can slowly work on them?
Pigeon.
Hi
Now that I made some progress, we can look at this.
pigeon said:
Maybe we could have a bit more detail list of what steps are needed to be done/discovered in order to have a usable (or full) linux port on the xda?
Something like...
- JTAG
---- locating JTAG pins(?)
- bootloader
- drivers(?)
- etc(?)
Click to expand...
Click to collapse
Currently I finished the JTAG part and a bootloader can be flashed in this way. More details can be found at the following page, but it has not been finished completely yet: http://xda-developers.com/jtag/
To port Linux, I think the following steps are needed:
- reverse engineer the hardware mapping to registers, pins and addresses
- port a bootloader with this information
- port the kernel with this information
Now the first two parts would be an iterative loop, starting with a basic set of hardware features such as screen, touch screen and buttons. For this it is necessary to understand how the bootloader (for example bootldr at http://cvs.handhelds.org/cgi-bin/viewcvs.cgi/bootldr/) works and how it can be limited to basic functionality.
When the bootloader has been ported with the basic hardware features than this information can be pretty much directly used for porting the kernel.
Question is:
Who has experience with coding in the bootldr or BootBlaster for iPaq?
Who has experience reversing the Wallaby bootloader to figure out how hardware is controlled from software?
Who can create a basic build for running the bootloader in RAM on the XDA from Windows CE?
Any volunteers can mail me, but I don't have much time to instruct. People should have the ability to take a 'Figure out how the LCD is controlled' and proceed from there with something like IDA Pro.
XDA developer W4XY said:
Question is:
Who has experience with coding in the bootldr or BootBlaster for iPaq?
Who has experience reversing the Wallaby bootloader to figure out how hardware is controlled from software?
Who can create a basic build for running the bootloader in RAM on the XDA from Windows CE?
Any volunteers can mail me, but I don't have much time to instruct. People should have the ability to take a 'Figure out how the LCD is controlled' and proceed from there with something like IDA Pro.
Click to expand...
Click to collapse
Ok, I took it upon myself to at least create a basic port and procedure for getting bootldr running on the XDA in RAM (without flashing). When that is working, I'll post more details on where to get it etc.
Good Luck
We appreciatte the effort that you all make on this site. As I have no experience in any of the things that you mentioned I can be of little assistance for the moment. But as one of the few here that are interested in this Linux port, I look forward to testing and giving feedback.
Looking forward to the XDA Special Edition Linuc ROM ! ! ! v0.01
Martin
Available to work
I have a couple of years experience coding under Linux on desktop PCs, and some experience coding kernel modules, although no specific experience of Familiar.
I don't have an XDA yet (quite a big obstacle except at CCC), but I want to get one soon; I saw one a friend of mine had, and I fell in love with it.
I have quite a lot of time to work on stuff like this, and I'm thinking of going to CCC if a couple of other people are who are interested in Linux on XDA.
I'll be on #xda-developers on IRCnet and #familiar and #handhelds.org on Freenode.net pretty much every evening (BST) and my email is [email protected]
Good deal. Thanks for the offer for assistance.
Can't come to CCC
I'm afraid I've decided that I can't come to the CCC. It's too short notice (only found out about it a couple of days ago), a long way to travel, I'd be coming alone, and I already have plans for that weekend.
Contributors sought
An old thread back to life! Linux porting has now started in full on http://xanadux.org. We're looking both at porting to Wallaby and Himalaya and do not want to stop after the kernel is done. Userland applications and maybe even a full distribution are our goal.
Check it out.
I wish to know:
1. What is the status of the project now?
2. How to join? (I tryed to send to the email there but couldn't)
regards,
Hi,
AlBaraSoft said:
I wish to know:
1. What is the status of the project now?
Click to expand...
Click to collapse
Currently there are two developments going on:
XDA 1 or Wallaby: http://wiki.xda-developers.com/wiki/WallabyProgress
XDA 2 or Himalaya: http://wiki.xda-developers.com/wiki/HimalayaProgress
Progress and information can be found in the respective Xanadux pages: http://wiki.xda-developers.com/wiki/XanaduxDeveloperHome
2. How to join? (I tryed to send to the email there but couldn't)
Click to expand...
Click to collapse
Oh that is strange. Where did you send mail to and what was the result? The e-mail address is: [email protected]
Beware that the current state of linux is very primitive. But with both it is possible to boot Linux and start TCP/IP networking over USB.
If you want to join and try and implement a feature help is very welcome! We are looking at several features such as Touch screen, button support, GSM modem etc.
Check it out:
HTC Says Software Fix is Coming For Lousy Video Drivers
Is this real? I know it is only a software/driver fix, but it is better than not...
rumors, rumors and more rumors.
There are countless rumors for and against this claim. No one here knows for sure.
It looks to me like this thread will be yet another source of baseless rumors...
EDIT: Ah, that was supposed to be a link. Perhaps post the correct link to the article you are referring to, and we can discuss that. Right now, the link is http://HTC Says Software Fix is Coming For Lousy Video Drivers, which is obviously not a proper URL.
Dishe said:
rumors, rumors and more rumors.
There are countless rumors for and against this claim. No one here knows for sure.
It looks to me like this thread will be yet another source of baseless rumors...
EDIT: Ah, that was supposed to be a link. Perhaps post the correct link to the article you are referring to, and we can discuss that. Right now, the link is http://HTC Says Software Fix is Coming For Lousy Video Drivers, which is obviously not a proper URL.
Click to expand...
Click to collapse
Fixed... Here is the meat:
Some of our top engineers have investigated video performance on our devices and have discovered a fix that they claim will dramatically improve performance for common on-screen tasks like scrolling and the like. Their fix would help most of our recent touch-screen products including the Touch family of devices and TYTN II / Tilt, Mogul / XV6900. The update is in testing and we hope to release it soon. However this fix is not a new video driver to utilize hardware acceleration; it is a software optimization. Video drivers are a much more complicated issue that involves companies and engineers beyond HTC alone. We do not want to lead anyone to believe they should expect these. To explain why we are not releasing video acceleration instead of the optimization I offer you our official statement... "HTC DOES plan to offer software upgrades that will increase feature functionality, over the air wireless speeds and other enhancements for some of the phones being criticized, but we do not anticipate including any additional support for the video acceleration issues cited in customer complaints. It is important for customers to understand that bringing this functionality to market is not a trivial driver update and requires extensive software development and time. HTC will utilize hardware video acceleration like the ATI Imageon in many upcoming products. Our users have made it clear that they expect our products to offer an improved visual experience, and we have included this feedback into planning and development of future products. To address lingering questions about HTC's current MSM 7xxx devices, it is important to establish that a chipset like an MSM7xxx is a platform with a vast multitude of features that enable a wide range of devices with varied functionality. It is common that devices built on platforms like Qualcomm's will not enable every feature or function. In addition to making sure the required hardware is present, unlocking extended capabilities of chipsets like the MSM 7xxx requires in-depth and time consuming software development, complicated licensing negotiations, potential intellectual property negotiations, added licensing fees, and in the case of devices that are sold through operators, the desire of the operator to include the additional functionality. To make an informed decision about which handset suits them best, consumers should look at the product specification itself instead of using the underlying chipset specifications to define what the product could potentially become."
I was at this conference. Take a look at what is inside the Mogul, Vogue, etc (aka Convergennce platform) chipset: (The second half talks about the graphics capabilities)
http://brew.qualcomm.com/brew_bnry/pdf/events/brew_2005/t202_ligon_qualcomm.pdf
It is difficult to be angy at HTC, as just about every HW vendor does this: The retail channels and the manufacturers want product diversity, but Qualcomm can't design all that many chips (a full chip design is expenive), nor can they build a wide diversity of fab plants so they just disable parts or leave out drivers.
The question that no one can answer due to NDA's is who exactly is holding them back? I.e. it may be that Qualcomm didn't license the accelerator for this part from ATI or that HTC didn't license the rights to from Qualcomm.
Either way, a gdi/direct draw driver for the basics is not a massive undertaking. We aren't asking for DirectX 10 suport.
awandkk said:
To make an informed decision about which handset suits them best, consumers should look at the product specification itself instead of using the underlying chipset specifications to define what the product could potentially become."
Click to expand...
Click to collapse
Here is the thing.... when I looked at what specs were available to me when I bought my Mogul, they looked better than my Wing. I expected better video performance than a 2 year old phone. What they said sounds like back peddling.
Sounds to me like all they are going to do is a quick software optimization which they will call a video fix, when in reality, it has nothing to do with the video hardware inside the device.
They are just releasing this and calling it a "video fix" to get all the people like us who want full functionality to shut the .... up about it.
We has given up?
cstyle226 said:
We has given up?
Click to expand...
Click to collapse
Most likely. One of those "believe it when you see it".
that pdf is such a teaser so my phone is as powerful as ps2 and i cant use it thats just messed up and you know all the hardware their cause its integrated.This sucks cause i never play games cause they always play horrible. htc is so responsible for the iphone gui blowing away any other phones.
http://code.google.com/android/
incase anyones not familiar with android, check that site out.
im not sure why there isnt more development or developers that are going after this in terms of getting it working on all devices? im currently using it on my vogue and its amazing. definately better UI in terms of EVERYTHING. its open source, so i think developers should be all over this! has so much potential its kind of ridiculous
vogue thread
http://forum.xda-developers.com/showthread.php?t=382265
its working about 80% now thanks to amazing developer martin.
the browser and everything (overall UI) are so much better and smoother than windows mobile! and being that its open source with google ENCOURAGING development of apps and themes and skins and whatnot, i think this is the next best thing to happen to ppc's.
THIS is the actual iphone killer.
just some samples
on a vogue (very smooth)
http://www.youtube.com/watch?v=d0z9bWiAT44
just a demo of the browser (mine is actually a little smoother than this)
http://www.youtube.com/watch?v=B2FpDDEVWtk
the reason im posting this here is because i was the first one to post in this section with manilla2d (when udk first released it), asking whether we can get this on other devices, and look what happened with that. if we can get the amazing developers from here to work on this like they worked on m2d, then wow this will be amazing!
Yeah, even I'm suprised at the low level of excitement of porting this to all devices. Hoping for some real development . Btw, those videos are pretty impressive.
Akshay
Yeah... I'm a little surprised too.
I have a Vogue now, so I'm OK, but I'd love to see somebody pick this project up for the Touch Pro. It seems to be very similar to the G1, so the porting would be a lot more complete than the porting to the Vogue.
Hopefully somebody with the skills (read: not me) will undertake this.
it'll pick up. i say in 6 months to a year people will snap out of the apple app dev craze. but from a dev point of view, apple is where its at right now. the amount of money you could make is a driver by all means.
htc will also be a key part in this. when they start to release better looking hardware, perhaps something on par with the diamond....you'll see a user increase. and user increase translate into dev interest. so just hang in there....i think you'll get what you want soon.
A ppc that works only on 80 Percent ? And no additional Software, no outlook syncronisation? Thats at the moment somthing for freaks or people with a second device
If there would be a 100 Percent Android i would install it, believe me, because i´m not very happy with windows anymore.
So i think we must wait and hope.
My next Device in half a year will be hopefully the Touch HD with Android rolleyes
because it makes no sense to port androud to a phone that is not 3G with GPS.
the only advantage of the g phone that I saw was the service. 3G and free GPS! i'm like, how much for the puppy in the window?
I honestly think that porting it to my wizard would be senseless.
without the service the gphone is just a phone wothout service.
S.V.I said:
because it makes no sense to port androud to a phone that is not 3G with GPS.
the only advantage of the g phone that I saw was the service. 3G and free GPS! i'm like, how much for the puppy in the window?
I honestly think that porting it to my wizard would be senseless.
without the service the gphone is just a phone wothout service.
Click to expand...
Click to collapse
Of course it is always pointless. We do it because we can (and because we don't want to do anything while at work)
(and much like bluemetal, we are all tired of the same old look and functionality in our WM devices). Then again, it can always be worse....
we could all have iphones
Anyways, I am looking forward to someone porting this to the Blue Angel.
The bigest stumbling block for me is lack of Exchange support. GPS isn't really necessary with the cell tower triangulation available. The accuracy is getting better. It will never be as tight as GPS but close is good enough for me. I can do with out 3G (I wish I had it) I don't enjoy the experience with the little screen. It's like looking at the ocean through a porthole. A 5 inch screen with much better resolution would be great. I use it for quick info but surfing is not fun.
I do like the idea of going linux on the phone. It would be that much closer to having a truely mobile desktop. We wouldn't have to install resource hogging shells that ride on top of an already bloated today screen to get better customization.
I think the biggest problem overall though is the hardware needed will put a lot of older equipment like my little wizard out to pasture. I don't have the funds to rush out an purchase a new phone. And yes I think all the bugs will need to be shaken out for a while before I take the plunge. Maybe by the 2nd or third generation of Android things will be a little less "bleeding edge". It all looks great now but I rely on my phone too much to gamble on an untried system.
To be completely honest, I too am suprised by the lack of progress.
This is a complete replacement for Windows Mobile: something we've all only dreamed about up until now. It will have a wicked Dev community around it soon enough.
There were a hell of a lot of efforts to get the Beta running. But now... nothing?
*so confused
The worst part is, it'd be gorgeous on my LG KS20, but I doubt we'll see it anytime soon: no one loves us KS20 owners. Guess you were all just jealous of our drivers.
bluemetalaxe said:
A ppc that works only on 80 Percent ? And no additional Software, no outlook syncronisation? Thats at the moment somthing for freaks or people with a second device
If there would be a 100 Percent Android i would install it, believe me, because i´m not very happy with windows anymore.
So i think we must wait and hope.
My next Device in half a year will be hopefully the Touch HD with Android rolleyes
Click to expand...
Click to collapse
i don't know if you read my whole post, but i never said "hey everyone lets run something 80% finished on our ppcs."
waiting and hoping isnt going to do anything, thats why i started this thread. to get more attention instead of sitting and waiting for something we arent sure is going to ever happen.
im glad a lot of other people are on the same page as me, wondering why there is barely any development for this. thanks for the support guys
lets get some devs in here to weigh in on this!
Well, there's a number of quite simple reasons...
- Porting Android to another device isn't as simple as "Hey, it's Open Source, you just have to compile and install". First of all, you'd need to find a working cross compiler for ARM in the first place (one using Windows' API, like those used for PPC apps isn't much help). Then you'd need to write drivers for usually undocumented hardware with this cross compiler or in ARM assembler (reusing existing WM drivers, like in cooked ROMs, wouldn't work in Linux). Finally, you need to find a way to flash that system to your PPC (that's a bit more work than a patched/cooked variation of an already existing WM ROM), and so on. That's work for the kind of freaks who would do their taxes binary in mind...
- Writing apps for a system almost nobody own so far isn't that attractive. It's even less attractive if the potential developer doesn't own one - the real experience is always a bit different to an emulator, and usually would like some use for himself, too (what good is an mobile app for you if you'd need a laptop with emulator to use it? ). So far, there's only one official Android device out there, and aside from the fact it's still a bit "first try, for developers only" (no Outlook sync, ugly design, ...), you only get it in very few parts of the world or in overpriced eBay auctions. Inofficial ports with reduced functionality and maybe buggy or slow "beta" drivers aren't that great, too...
- While the Android API is quite close to common Java style, it's still something completely new, which requires some time to get into the framework's basic style, the available functions, the loopholes and small tricks, etc. With WM, the gap to common Windows (desktop) programming is way smaller, and I guess it's similar with the iPhone and Mac programming.
Or, in other words: Give Andoid some time to grow up. IMHO, G1 and the few existing ports are a playground for hackers and early adopters, so they can get startet with fixing (security holes, missing functionality, ...). Then, in some months, more devices with a "hacker improved" Android will be published, and when developers buy those, they also will start writing apps if they are missing something.
you'd think more people would be starting to port.. because god is that g1 terrible, you have to have sharpened pencils for fingers to type on that flush keyboard)
Mort said:
Well, there's a number of quite simple reasons...
- Porting Android to another device isn't as simple as "Hey, it's Open Source, you just have to compile and install". First of all, you'd need to find a working cross compiler for ARM in the first place (one using Windows' API, like those used for PPC apps isn't much help). Then you'd need to write drivers for usually undocumented hardware with this cross compiler or in ARM assembler (reusing existing WM drivers, like in cooked ROMs, wouldn't work in Linux). Finally, you need to find a way to flash that system to your PPC (that's a bit more work than a patched/cooked variation of an already existing WM ROM), and so on. That's work for the kind of freaks who would do their taxes binary in mind...
- Writing apps for a system almost nobody own so far isn't that attractive. It's even less attractive if the potential developer doesn't own one - the real experience is always a bit different to an emulator, and usually would like some use for himself, too (what good is an mobile app for you if you'd need a laptop with emulator to use it? ). So far, there's only one official Android device out there, and aside from the fact it's still a bit "first try, for developers only" (no Outlook sync, ugly design, ...), you only get it in very few parts of the world or in overpriced eBay auctions. Inofficial ports with reduced functionality and maybe buggy or slow "beta" drivers aren't that great, too...
- While the Android API is quite close to common Java style, it's still something completely new, which requires some time to get into the framework's basic style, the available functions, the loopholes and small tricks, etc. With WM, the gap to common Windows (desktop) programming is way smaller, and I guess it's similar with the iPhone and Mac programming.
Or, in other words: Give Andoid some time to grow up. IMHO, G1 and the few existing ports are a playground for hackers and early adopters, so they can get startet with fixing (security holes, missing functionality, ...). Then, in some months, more devices with a "hacker improved" Android will be published, and when developers buy those, they also will start writing apps if they are missing something.
Click to expand...
Click to collapse
ok now these reasons make a lot of sense. im just surprised that not as many people are trying to get it started so they can get started on fixing, like you said. but ok, all of your other reasons make complete sense. im sure the future releases of android will only get better.
android just seems like exactly what many of us have been looking for in wm devices, basically, a complete UI replacement endorsed/created by a large company (other than microsoft lol).
jakub_w said:
im just surprised that not as many people are trying to get it started so they can get started on fixing, like you said.
Click to expand...
Click to collapse
Who knows? AFAIK, the order numbers aren't that bad, and all those reviewers give some feedback, too. I mean, it's only a week since the G1 is available at all, and, as said, it's not very attractive so far. Not everybody wants to spend hundreds of dollars just to provide Google with requests and code changes and T-Mobile and HTC with money...
android just seems like exactly what many of us have been looking for in wm devices, basically, a complete UI replacement endorsed/created by a large company (other than microsoft lol).
Click to expand...
Click to collapse
I don't think the UI is the really big thing about Android. You can even replace it completely, and I don't know (yet) where the limits / design guides are for applications. I just hope it doesn't get as confusing as Linux on the desktop, where even a Gnome or KDE desktop can be modified so far that it's almost as hard to switch distros as switching from Windows to MacOS...
The important things about Android are more in the basic technology, imho, like
- A stable, timeless system core (*nix is older than me, so "modern" is not quite correct - that goes for MacOS X, too, btw...)
- Seamless integration of connection management and phone functions (opposed to WM, where it still acts like a makeshift patchwork, and with every update less APIs are working...)
- Portable application framework (Java, lots of system APIs)
- Simple application installation (no "is this EXE a PC setup or the PPC executable?", "How the hell do I install a CAB file?", ...)
However, I still wonder how/if Andoid will support direct PC synchronization (for shared files, contacts, appointments, music, ...) and how fast and memory consumptive the required Java VM is... (Well, at least none of the G1 reviews I read complained about that, so it seems to be faster than .NET on WM...)
i was just playing around with android and in the dev tools or api demos theres a section called opengl es. i have a vogue and i tried these, they ran extremely smoothly. isnt this something that everyone has been saying is impossible? (specifically for getting tf3d to run on the vogue) i think this proves that software driven 3d is more than capable of handling tf3d. just a thought.
jakub_w said:
i was just playing around with android and in the dev tools or api demos theres a section called opengl es. i have a vogue and i tried these, they ran extremely smoothly. isnt this something that everyone has been saying is impossible? (specifically for getting tf3d to run on the vogue) i think this proves that software driven 3d is more than capable of handling tf3d. just a thought.
Click to expand...
Click to collapse
I definitely agree with you on that. Thing is though is that this is a completely different environment with a different set of drivers (and rules) which makes (for example) modifying their parameters to allow for keys normally used for certain functions in WM to be used for something completely different. Also OpenGL (ES) is all that is used on *nix OSes whether or not they run on full or embedded hardware. All that's needed is the driver for the graphics chip. Microsoft wants you to use their proprietary D3D not OpenGL (ES) hence why it was impossible to have OpenGL (ES) before. Also TF3D uses DirectX and not OpenGL ES AFAIK.
Android is great. Only thing I need is a way to get the SDcard image working and a HTC Touch Pro to port Android, Angstrom and/or OpenMoko to, I'd be set.
why would you develop software for an operating system that isn't even fully ported yet?
joel2009 said:
why would you develop software for an operating system that isn't even fully ported yet?
Click to expand...
Click to collapse
Weeell....
- It's Linux and Open Source (some people wouldn't touch a closed system with a stick...)
- It's nice to be prepared when you get the running system
- There is a device with that OS
- The documentation is way better than Microsoft's
- There's a good chance the API will remain compatible, so it doesn't hurt to start early (opposed to WM, where some basic features can/could only be done with device dependant or inofficial APIs, which were dropped in newer updates...)
Hi every one,
I need help in a project i am doing.
I need to activate a camera module with an external controller.
The camera I want to operate is the rear cam of the Iphone 4s.
I searched a bit and found that it is Sony's camera and the name is IMX-145.
This was made by chipworks.
But I cant find any datasheet or some clues about this module or its structure.
Can you help me ?
Thanks
XDA is for android. Try an iPhone forum
I need documentation on 8 MegaPixel cam.
It does not matter to me if its IPhone or Samsung Galaxy S II.
I need a good camera (part of a smart phone) documenting, eg datasheet pinout or ICD.
Can anyone help ?
Where can I find this sort of documentation?
amirke said:
It does not matter to me if its IPhone or Samsung Galaxy S II.
I need a good camera (part of a smart phone) documenting, eg datasheet pinout or ICD.
Can anyone help ?
Where can I find this sort of documentation?
Click to expand...
Click to collapse
I think what the meant was that the majority of the people here specialize in Android based devices/parts/etc.
It would be more prudent to go to an iPhone web forum to find the information you are seeking, maybe an iPhone modding scene or something like that
... The fact that the OP is asking for a hardware datasheet it boggles my mind how the above responders think that it has anything to do with what software is accessing said controller/sensor. They must be complete Derp's to think it matters if its android or ios, and negate the fact that what is being asked for has nothing to do with it.
To the OP:
If its a new revision of said sensor, then getting a new datasheet will be extremely hard to come by. You'd probably be able to find said datasheet for earlier revisions unless its protected as a proprietary piece of hardware of Chipworks.
I would guess that maybe something would be found buried in the chipworks website on the matter. Generally though for newer hardware or revisions of existing hardware, datasheets are not released to public until they've been replaced with newer models/revisions.
As it stands It looks like they can only be bought.
https://chipworks.secure.force.com/catalog/ProductDetails?sku=SON-IMX145&viewState=DetailView&cartID=&g=&parentCategory=&navigationStr=CatalogSearchInc&searchText=circuit
XDA is for android
This forum (xda) just for ANDROID...
XDA is for Android, Windows Phone, Web OS, Meego, Bada, etc. And yes, there is even a link for iPhones on the main page.
Besides, Apple doesn't necessarily have an exclusivity deal on the camera sensors. The iPhone 4 used the same sensor that many HTC phones did, but the sensor itself can only do so much. The post processing and especially the optics are what makes or breaks a camera.
I'd find someone working for IT company and ask him to send request there - http://www.ovt.com/ and maybe to Toshiba asking for datasheet and samples of some sensor if you need only sensor. But, as xHausx said, you may need also camera-processor so you may want to look for ready sensor+processor fused modules. And these seems to me to have all very similiar interface (on ARM SoCs you can find camera handling modules - these are universal), though reversing ready device or getting datasheet for proper I2C/SPI communicating with such thing may be needed, which is rather model-specific.
iPhone from hardware level remains the very same device as all other Android devices and iPhone-developers doesn't have strictly hardware-modding forum as XDA does. So XDA is more appropriate place to ask for such things IMO.
//edit:
And check out this - http://www.mipi.org/specifications/camera-interface
I tried to get some help in the Q&A section, but it appears this is more technical/hardware seeking question than just generic "which phone" thread.
I have been suggested Samsung Galaxy Spica/i5700 by boofman (thank you), but the device is cost prohibitive.
I would very much appreciate anyone's suggestion.
I am planning a presentation to demonstrate the benefits of JTAG for data recovery on embedded systems. The audience has approx. 12th grade education, but higher than average computer understanding.
I have most of the equipment already, including a uLINK2, Bus Blaster, and Raspberry Pi for the UART-to-USB, and OpenOCD for the software.
What I am missing is the simplest cell phone (or other inexpensive embedded device) to make the demonstration.
I would like to connect to the device and list the devices on the JTAG chain, and recover the data from them.
What cell phone brand and model would work well for this presentation?
I would need to know the JTAG points, have access to the data sheets of the onboard chips, and since it is out of my own pocket, I hope to get the phones on eBay for a low price.
Any suggestions are welcome.
huperetes said:
I tried to get some help in the Q&A section, but it appears this is more technical/hardware seeking question than just generic "which phone" thread.
I have been suggested Samsung Galaxy Spica/i5700 by boofman (thank you), but the device is cost prohibitive.
I would very much appreciate anyone's suggestion.
I am planning a presentation to demonstrate the benefits of JTAG for data recovery on embedded systems. The audience has approx. 12th grade education, but higher than average computer understanding.
Click to expand...
Click to collapse
You'd be surprised what kids know these days.
huperetes said:
I have most of the equipment already, including a uLINK2, Bus Blaster, and Raspberry Pi for the UART-to-USB, and OpenOCD for the software.
What I am missing is the simplest cell phone (or other inexpensive embedded device) to make the demonstration.
I would like to connect to the device and list the devices on the JTAG chain, and recover the data from them.
What cell phone brand and model would work well for this presentation?
I would need to know the JTAG points, have access to the data sheets of the onboard chips, and since it is out of my own pocket, I hope to get the phones on eBay for a low price.
Any suggestions are welcome.
Click to expand...
Click to collapse
Check out gsm-forum, under the hardware repair section.
Googling for jtag pins and your phone model number usually works for me. I'd assume you might have to wait a little bit for brand new devices, unless you feel like scoping the pins to find out which is which or hope their labeled.
These individuals are not kids. :fingers-crossed:
Excellent resource at the other site. Thanks!
But, I think I do not think I made myself clear regarding what I am looking for:crying:. I am not looking for info on how to JTAG a specific phone.
I am looking for 3 or 4 of the same model of cell phone that
I can pick up on eBay or similar for reasonable price (<$30/phone),
the JTAG TAP is known on the motherboard, and
it would be a bonus if the JTAG command set was known (besides the basic requirement).
This would allow me to make test run on one of the phones, then demonstrate the use of JTAG on the others.
The Samsung Galaxy Spica is a good phone, but I do not have the budget at $100+/phone. I need to find something cheaper. It does not need to be fancy telephone, or even smart phone - just have sufficient JTAG documentation.
If anyone has any ideas on what to use for this demo, I am still in need of a good idea.
You can look into any of the older HTC phones for this. I think that would be your best bet. I've done plenty of hardware repair, disassembling, reassambling, flashing, etc... on Android, & non-Android phones, & from my experience, the older HTC phones are the best. Specifically, concentrate on the GSM ones, such as for T-Mobile. Look into HTC myTouch 3G Slide (awesome little thing) , HTC G2 (one of the best keyboard phones ever), myTouch 4g, myTouch 4G Slide (overheating, self-destructing piece of crap), even the HD2 & the HD7. These are all devices that you can get for around $30 or so with a cracked, but still working digitizer, or some other kind of problem. Screens & other parts for them are very cheap as well.
Also, these are all known to RIFF Box. Look it up. You can do JTAG repair with these, & RIFF Box have all the JTAG ports labeled & documented. They might have some of the documentation right on their site, but I'm not totally sure. Anyway, check it out & see. I think this will be exactly what you're looking for.
Excellent! Thank you very much.
I have looked at looked at many commercial products, including RIFF Box. I narrowed the selections down the RIFF and ORT, but they are both very expensive for demonstration purposes.
I do love the fact that one can buy "jigs", "clips" or "adapters" (names change depending on vendors) which removes the soldering requirements for some of the phones. Except, these are still very expensive. :cyclops:
Again, thanks. I will look into these.
3ndymion218 said:
You can look into any of the older HTC phones for this. I think that would be your best bet. I've done plenty of hardware repair, disassembling, reassambling, flashing, etc... on Android, & non-Android phones, & from my experience, the older HTC phones are the best. Specifically, concentrate on the GSM ones, such as for T-Mobile. Look into HTC myTouch 3G Slide (awesome little thing) , HTC G2 (one of the best keyboard phones ever), myTouch 4g, myTouch 4G Slide (overheating, self-destructing piece of crap), even the HD2 & the HD7. These are all devices that you can get for around $30 or so with a cracked, but still working digitizer, or some other kind of problem. Screens & other parts for them are very cheap as well.
Also, these are all known to RIFF Box. Look it up. You can do JTAG repair with these, & RIFF Box have all the JTAG ports labeled & documented. They might have some of the documentation right on their site, but I'm not totally sure. Anyway, check it out & see. I think this will be exactly what you're looking for.
Click to expand...
Click to collapse
I'd go with Galaxy S 1 as it's really cool to work on and relatively well documented and demonstration on such stuff always looks well. But if you want something low-budget. I've seen JTAG pads on Nokia E50'ish stuff. Or try with some Samsung S3000's, these are pretty cheap. But I don't know how's JTAG there.
as @3ndymion218 told you , search old HTc .. also some Samsung that I think cheap could help too .
Samsung F480 , F490 , U700 , U900 etc ... some news Corby model also .. I think cheap .
I could help if you were near to me . I have 3 phones that I could offer you ...
Thank you for the further info.
Definitely will try to track down the HTC and Nokia information.
Samsung is a bit pricy as you said, but maybe down the road.
Again, thank you all!