Hi to everyone.
I just found out this forum and searched a lot my problem. My roblem is this: I need to install android on Toradex calibri T20 (toradex.com/Products/Colibri/Modules/Colibri-T20) of course this just a module but I will add other peripheriel devices such as touchscreen, radio, GPS etc. This module comes with WinCE 6 and company provides linux driver also.
I have a background about linux driver development and I wonder if porting android is possible? Can I use linux drivers which provided by company and what other difficulties will I face?
If you can help I will be really happy, thanks.
I am also interested in hearing how this works out. I was looking at building a tablet based on the T20, but was apprehensive to do so until there was a port of Android. I contacted Toradex about a port and they said that it could be done with the drivers, but that they weren't going to do it until ICS at the earliest, and only if the legal situation with Android were a bit more clear. They did confirm Win8 support, however.
Related work (sort of)
Well, I haven't had a lot of time to look at it, but perhaps you could see how the BeagleBoard people went about integrating the BeagleBoard Linux drivers to build Android for their devices? One of the more promising projects is Android Row Boat (can't post a link as I'm new to posting, although I've been lurking for years). Perhaps some of their work would get you pointed in the right direction as they had a somewhat similar situation. The T20 does have Linux drivers, so there should be a way to integrate them into Android unless I'm totally off-base here.
Update!
I was just talking to Toradex, and they let me know they have an Android image available now. If you are still looking for the solution this is the link: developer.toradex.com/files/toradex-dev/uploads/media/Colibri/Linux/Images. Sorry for the lack of hyperlink, but I'm still a forum newb.
Related
Good news guys!
Jerpelea announced the eminent release of Cyanogen RC2 for the X10.
http://forum.xda-developers.com/showpost.php?p=7370940&postcount=91
So to keep the dev only thread clean, please post your questions, problems or comments here.
Update 2010-07-28:
jerpelea said:
with actual state of spl it boots then crashes
you can play a lil with the new kernel included into package
build 0005
http://hotfile.com/dl/57983756/408a452/0005.rar.html
Click to expand...
Click to collapse
Great news and great work by the devs!
I think that this release will be internal i.e. devs only. We never got RC1 so why should we expect RC2?
you got that wrong guys
Froyo is ready in RC2 for X10 this is not equal to : "the bootloader is finally hacked"
So stay calm please
Regards
Bin4ry
Man i got excited for a minute there. Looks like back to waiting.
Sent from my X10i using the XDA mobile application powered by Tapatalk
Damn it!
Still good news that it'll be ready for when it does get hacked.
no more wet dreams.
ill stick it once it gets useful fr all...
its nice to see progress at least, I thought they hit a brick wall a couple days ago as they stopped posting in the dev thread. It may be a while till we see a bootloader hack thats friendly for us but its hard to determine since we're not devs. As I understand it, the actual ROM is partly ready but it'll have a number of bugs etc still and only devs who can actually load it on through manual code will be able to test it out I think. It may be that its actually just a virtual rom to be loaded onto the SDK under the same conditions as the x10 to be tested by the developers. I THINK. As I said I'm not a developer so take my words with a huge grain of salt because I might be completely wrong.
PLS Can we get a little more detailed information.
instigator008 said:
I think that this release will be internal i.e. devs only. We never got RC1 so why should we expect RC2?
Click to expand...
Click to collapse
PLS Can we get a little more detailed information.
If the RC2 will be ready tomorrow then it means that RC1 was launched on the device?
irkkso said:
PLS Can we get a little more detailed information.
If the RC2 will be ready tomorrow then it means that RC1 was launched on the device?
Click to expand...
Click to collapse
what is the meaning of rc1 and rc2
RC = Release Candidate
irkkso said:
PLS Can we get a little more detailed information.
If the RC2 will be ready tomorrow then it means that RC1 was launched on the device?
Click to expand...
Click to collapse
No no no... you got it all wrong.
RC2 is the latest release of CyanogenMod and work has been carried out on this to "Port" it over to the x10. There wasnt any point in working on RC1 if CM RC2 was out.
rc = release candidate
a software enters rc usually after testing phase(alpha-beta-etc...)....
j4mm3r said:
Good news guys!
Jerpelea announced the eminent release of Cyanogen RC2 for the X10.
http://forum.xda-developers.com/showpost.php?p=7370940&postcount=91
Click to expand...
Click to collapse
So Jerpelea made a edit on the post... which is something pretty much expected as the bootloader is not cracked. So my guess is that this is going to use the spl loader module to boot into the CM kernel which has been ported for X10? Just a guess...
Can somebody explain to people like me who are new on android what does the cyanogen mod, is it just a firmware ?
What is called "kernel" in android and is it "modable" and if yes, why would it be ?
The answers...
Vilam said:
Can somebody explain to people like me who are new on android what does the cyanogen mod, is it just a firmware ?
What is called "kernel" in android and is it "modable" and if yes, why would it be ?
Click to expand...
Click to collapse
Hi Vilam, those are interesting questions, let me see if I can address those to your satisfaction.
The term "firmware" being distinct from "software", in my view is rapidly loosing its ability to be distinguishable from the latter. Essentially it refers to those parts of the executable code on a computing machine which remains unmodifiable or rather "burned in" to the circuitry. With the advent of modern flash memory storage, which is rather malleable compared to the earlier variants which existed, it is rather easy to change and update the machine code which is stored therein.
In other words, you might still refer to firmware to be part of the "software" which runs on a computing device which is not modifiable at run-time. In terms of a smart phone (which are rapidly becoming general purpose computing devices anyways), the firmware forms the basis of the software execution environment which affords the so called "apps" to run and provide either ever so innovative and useful functions.
Coming around to the point about Cyanogen mod... its a combination of firmware and software (if you still want to make that distinction that is). It in conjunction with helper pieces of code like the bootloader et. all. can completely replace the components that your phone was originally shipped with. Since these are Android phones that we are talking about, Cyanogen is derived from the same code base that Google officially uses for their various releases of Android. It is important to note that Android is a mobile application and phone platform rather than something which can easily be classified as "firmware" or "software"
Next question of yours about the "kernel". Not knowing what your level of familiarity of Linux or its derivatives is... let just say that Android is essentially like a distribution (or distro) of Linux designed specifically to run on mobile devices. As is the case with other Linux distros, they are formed around a core known as the "kernel". The "kernel" forms the core of the operating system which provides a homogeneous execution environment for the execution of various applications, which are in-turn pieces of software which are designed to provide the functionality which can be useful to the end-user. So all the so-called "apps" require the kernel to provide some services which are abstracted out enough so that the application programmer does not need to care about the really really low level stuff that actually has to go down if you actually want your device to do something. Hence the application programmer concentrates on the "high level" stuff, which is the functions that are actually going to be useful to the end-user!!
Like all modern computing platform, Android is a layered architecture and the "kernel" forms one of the most inner most parts of it (hence the name "kernel").
The linux kernel running Android for the X10 is already modifiable. People have been successful in compiling software modules called "kernel modules" which can be added to a running kernel and add functionality to it (this of course requires super user privileges or "root" access on the phone).
With the future pointing towards the capability of running mods like Cyanogen and the likes, the possibilities of modding and hacking are endless. Cyanogen, like the original releases of Android from Google are completely open source, so one can tweak almost all aspects of the phone functions. The possibilities are only limited by ones own imagination.
PS: I think I had too much beer and it makes me practice my English composition skills... hic!
Thank you very much for this clear explaination !
Please let me explain in newbie wordings. This is for ppl who can't understand what's going on at all.
1. A firmware likes an OS, if not exactly is. Windows, Linux, DOS, OS X are all OS. In android phone, there is merely one OS, which is Android.
2. Android is Linux.
3. Linux has a kernel, which is the main program. Without this, your machine can't run. On top of kernel, there is other software (movie player/web browser). Kernel + other software = distro (distribution).
4. Windows has different distro like Home, Professional, Ultimate... Linux has also different distro, so does android. One of them is CyanogenMod. The other could be Xperia X10 original.
5. Android is open source, so everyone can mod it. But that does also means someone can remove functions from it, one of them is Sony Ericsson, which locks your Xperia X10 for professional use.
6. While it is easy for us to upgrade Windows XP to Windows 7. It is difficult to install OS X from Windows XP. This is the same case for Android, it is easy to upgrade our Xperia X10, but it is not that easy to install CyanogenMod. There are honorable person working on this issue.
7. Why CyanogenMod? Because it is faster or it does not lock function like original Sony distro.
8. Just like installing OS X on regular PC, installing CyanogenMod may brick your machine. Much worse, Sony will definitely don't get your X10 repaired. So think if you need that extra function.
My Atrix got it's case cracked and the touch-screen display died, and given I already got a replacement phone I feel a bit adventurous. I wanted to see if I could build my own computer with what remains, so I wanted to run Linux natively (no Android). Given that there's a Linux 4 Tegra from Nvidia:
Is there a chance that I could build my own distro based on that?
Should I use another kernel (like the one currently used in gingerbread or CM7)?
Please note that I'm not trying to do webtop.
I thought of building my own handheld with the Atrix, or what remains of it. So any tips on how to get started would be great.
Cheers!
wrong section
ovitz said:
wrong section
Click to expand...
Click to collapse
Umm... what section would you suggest other than Q&A?
It was moved. Sorry 'bout that. I was under the impression that development questions were on the other forum...
"Android development" is in the description. I think they keep that forum just for Android-specific things, even though Android is just a flavor of linux.
tonglebeak said:
"Android development" is in the description. I think they keep that forum just for Android-specific things, even though Android is just a flavor of linux.
Click to expand...
Click to collapse
You're being way too literal. It's been used for all sorts of non-Android dev multiple times. Right now, Boot2Gecko is right there. The fact of the matter is that when it pertains to dev questions, this post would most likely be answered there. I'm pretty sure it'll die here on this forum with barely any useful answer, if at all.
The development section is mostly for things that are "in progress", ie. with "something to show". Questions, discussions and ideas go elsewhere.
As for your question, I believe I've seen a thread about this already, and quite recently too.
ravilov said:
The development section is mostly for things that are "in progress", ie. with "something to show". Questions, discussions and ideas go elsewhere.
As for your question, I believe I've seen a thread about this already, and quite recently too.
Click to expand...
Click to collapse
I've checked a few that I've found on the forum, but most had no answer and were about other devices. With regards to the Atrix or the Tegra, I've only found threads about webtop.
Not to argue too much about this too much, but I've seen threads that started with nothing in the dev section. Like the Kernel porting project that started as a mere placeholder for the project. Point is, I've done my research and found no pointers to the questions I have. I made it in case another dev had an idea about it. I may have missed something, but that's why I asked in the first place. If I believed I had covered all grounds by myself, I wouldn't have asked in the first place.
Lugaidster said:
I've checked a few that I've found on the forum, but most had no answer and were about other devices. With regards to the Atrix or the Tegra, I've only found threads about webtop.
Not to argue too much about this too much, but I've seen threads that started with nothing in the dev section. Like the Kernel porting project that started as a mere placeholder for the project. Point is, I've done my research and found no pointers to the questions I have. I made it in case another dev had an idea about it. I may have missed something, but that's why I asked in the first place. If I believed I had covered all grounds by myself, I wouldn't have asked in the first place.
Click to expand...
Click to collapse
What you're looking to do seems similar to this question: http://forum.xda-developers.com/showthread.php?t=2110161
The difference between the webtop and a stand alone installation of Linux won't be that different, mainly it would just be where on the device the OS is installed and how video is handled. That said, I'm not sure about the kernel, specifically the video drivers, since they're intended for Android and may not be compatible with X. AFAIK, Wayland is closer to Android than X is, but Wayland isn't quite ready.
Anyway, assuming you did succeed, what you would end up with would be less like a true desktop (as you'd be pretty much locked into a specific kernel, and therefor any packages limited by it, but it doesn't invalidate the effort), and more like a persistent live CD, since the OS would be installed to an area mounted as read-only (to prevent flash wear), with access to an area that has read/write access, like in Android where you store apps and user files. Overall, it could be fun if you enjoy a challenge and aren't intimidated by soldering and using the JTAG connector.
lehjr said:
What you're looking to do seems similar to this question: http://forum.xda-developers.com/showthread.php?t=2110161
The difference between the webtop and a stand alone installation of Linux won't be that different, mainly it would just be where on the device the OS is installed and how video is handled. That said, I'm not sure about the kernel, specifically the video drivers, since they're intended for Android and may not be compatible with X. AFAIK, Wayland is closer to Android than X is, but Wayland isn't quite ready.
Anyway, assuming you did succeed, what you would end up with would be less like a true desktop (as you'd be pretty much locked into a specific kernel, and therefor any packages limited by it, but it doesn't invalidate the effort), and more like a persistent live CD, since the OS would be installed to an area mounted as read-only (to prevent flash wear), with access to an area that has read/write access, like in Android where you store apps and user files. Overall, it could be fun if you enjoy a challenge and aren't intimidated by soldering and using the JTAG connector.
Click to expand...
Click to collapse
Actually, I might have to do soldering anyway. I'm not really intimidated by it and don't really care all that much for phone functionality and such. I'm not even interested all that much in X as my project is more towards transforming it into a handheld gaming (more like emu) device. I don't mind compiling software specifically for the system. The question is pretty low-level in that regard for me. I want to know if I have to do anything with regards to the kernel since it's specific to Android. Given that most emus I know that would run acceptably in a tegra 2 don't really need the GPU, I don't mind just using framebuffer so HW doesn't really interest me.
Lugaidster said:
Actually, I might have to do soldering anyway. I'm not really intimidated by it and don't really care all that much for phone functionality and such. I'm not even interested all that much in X as my project is more towards transforming it into a handheld gaming (more like emu) device. I don't mind compiling software specifically for the system. The question is pretty low-level in that regard for me. I want to know if I have to do anything with regards to the kernel since it's specific to Android. Given that most emus I know that would run acceptably in a tegra 2 don't really need the GPU, I don't mind just using framebuffer so HW doesn't really interest me.
Click to expand...
Click to collapse
Unfortunately, it's going to be one of those areas where you'll have to make an educated guess, since as far as we know, no one has successfully pulled off a straight Linux implementation on the device.
That said, nVidia does have both Android and Linux images for the Ventana dev kit, so it should be possible. In my case, I would compare the source code for their Linux kernel vs the stock Linux kernel vs their closest Android kernel vs the stock Android kernel. The biggest thing is how the the device specific files translate from one kernel to another, because you'll likely need to translate the device specific files for the Atrix in the same manner. The changes may be subtle or they may be drastic. The main thing is to just be able to set the pins properly so you don't release any "magic smoke". Unfortunately, I see no source code for any of nVidia's kernels.
Anyway, that's how I would do it, but I do suspect that someone with more knowledge could find a much simpler approach and hopefully they'll chime in, but this part of the forums isn't the thriving hub of activity it used to be, so I don't know if that will happen any time soon or at all.
lehjr said:
nVidia does have both Android and Linux images for the Ventana dev kit
Click to expand...
Click to collapse
Atrix is a Whistler, not a Ventana.
http://forum.xda-developers.com/showthread.php?p=33289027#post33289027
ravilov said:
Atrix is a Whistler, not a Ventana.
http://forum.xda-developers.com/showthread.php?p=33289027#post33289027
Click to expand...
Click to collapse
Thanks for the heads up and the link! :highfive:
I was thinking in try to port Ubuntu Touch to my Android Device (Razr D3).
I've saw Ubuntu running on some devices, but only devices that developers give attention (Nexus series per example). I've saw once Ubuntu Touch running in a Xperia Mini Pro, but did not understand how that guy ported the SO to the Xperia series.
Well, my doubt is: Where do I start this job? Where do I get the files to try something? How do I create compatibility for my device?
I really don't understand anything about this, I want to learn. And, if success, try to port Ubuntu to all Razr series.
Satorious said:
I was thinking in try to port Ubuntu Touch to my Android Device (Razr D3).
I've saw Ubuntu running on some devices, but only devices that developers give attention (Nexus series per example). I've saw once Ubuntu Touch running in a Xperia Mini Pro, but did not understand how that guy ported the SO to the Xperia series.
Well, my doubt is: Where do I start this job? Where do I get the files to try something? How do I create compatibility for my device?
I really don't understand anything about this, I want to learn. And, if success, try to port Ubuntu to all Razr series.
Click to expand...
Click to collapse
(apologies for crap urls, still a new member here........)
Best place atm is wiki dot ubuntu.com/Touch/PortingFlippedInProgress but it's still kind of a mess given the ubuntu team hasn't given it many updates recently to reflect the flipped images. Unless you're well experienced in messing android with both android and ubuntu I'd give a miss until someone rewrites it.
I've been trying to get my tf201 working for months now to no avail but good luck to you!
p.s. the irc log from a porting day has good info as well irclogs dot ubuntu.com/2013/08/01/%23ubuntu-touch.html
splinterx7 said:
(apologies for crap urls, still a new member here........)
Best place atm is wiki dot ubuntu.com/Touch/PortingFlippedInProgress but it's still kind of a mess given the ubuntu team hasn't given it many updates recently to reflect the flipped images. Unless you're well experienced in messing android with both android and ubuntu I'd give a miss until someone rewrites it.
I've been trying to get my tf201 working for months now to no avail but good luck to you!
p.s. the irc log from a porting day has good info as well irclogs dot ubuntu.com/2013/08/01/%23ubuntu-touch.html
Click to expand...
Click to collapse
Thanks, but, the links do not work. Can you post a functional link?
Also, I have been searching for something in official Ubuntu page, but a didn't find anything! Dude, is there another forum or ftp severs that stores at least generical images to download? The official comunity seems to do not give a minimal help or importance to work to do ports made by amateurs developers, I cannot understand how Ubuntu Phone be open source if any source is available.
Sent from my XT920 using xda app-developers app
are you including the sub domain when you're entering the urls?
wiki.ubuntu.com/Touch/PortingFlippedInProgress
irclogs.ubuntu.com/2013/08/01/%23ubuntu-touch.html
I'm looking into building a custom android device to be embedded in a project I'm working on. I won't need GSM/cell service, so this would be more of a 'tablet' with wifi that's the size of a phone. The first version of this project used some lower level embedded controllers, but for a better user experience (capacitive touch screen, full featured app, etc), I'm looking into using an embedded android device and having a friend (who told me to post here about this) write an app to run on it for me. This project is starting to scale, so buying a cheap tablet and tearing it apart isn't really a good option; I'll need to build something from the ground up. My problem is that I'm more of a microprocessors guy, so I don't really know where to start with this kind of hardware.
I found this thread which was a good start, but the info is like 3 years old now.
Has anyone tried to do something like this? Should I be trying to find a manufacturer who already does this type of thing to work with? If so, how do I find someone like that? If I am going to do the design myself, what kind of processors can run an Android OS? Where's a good place for learning that type of info? Are there any reference designs out there I can use to get started? Is running Android on RaspberryPi a good starting spot, or is that simply not scalable?
Thanks for the help, I hope I'm in the right spot. Apologies if not!
I hope this is the right forum. I have a generic A13 Chinese tablet but I'm having difficulty tracking down the firmware I need to flash it. There are no markings on the back to indicate manufacturer and the space on the board where the ID is supposed to be found is blank. I took some pictures of the main board, maybe you guys will see an identifying marker that I missed.
http://i.imgur.com/YPRnVDx.jpg
http://i.imgur.com/axRkExe.jpg
http://i.imgur.com/YD7a8za.jpg
http://i.imgur.com/fzrzS7s.jpg
CriticalComposer said:
I hope this is the right forum. I have a generic A13 Chinese tablet but I'm having difficulty tracking down the firmware I need to flash it. There are no markings on the back to indicate manufacturer and the space on the board where the ID is supposed to be found is blank. I took some pictures of the main board, maybe you guys will see an identifying marker that I missed.
http://i.imgur.com/YPRnVDx.jpg
http://i.imgur.com/axRkExe.jpg
http://i.imgur.com/YD7a8za.jpg
http://i.imgur.com/fzrzS7s.jpg
Click to expand...
Click to collapse
The issue you will find is that there isn't a way to get the firmware. These types of devices are hacked together devices. Half of them are set up to lie about the hardware and source code and default firmware are almost never released.
Are you experienced at all with TOM building? Perhaps you could start out with the android source code and start from scratch building a ROM that has the drivers necessary for the components that you can find.
Sent from my Super Computer (1976) with Tap Tap Talkolution
This is a bit disheartening to hear. I haven't done any work with TOM building. The closest I've ever done is modifying a stock rom and making it installable in recovery. I have been trying random Q88 firmwares with the Phoenix Card Utility. I have the device booting now at least but none that I have tested thus far have the proper touchscreen driver. I guess I could use one of these firmwares as a starting point. What would be a good resource for learning how to build a ROM and how to discover which drivers I need?
CriticalComposer said:
This is a bit disheartening to hear. I haven't done any work with TOM building. The closest I've ever done is modifying a stock rom and making it installable in recovery. I have been trying random Q88 firmwares with the Phoenix Card Utility. I have the device booting now at least but none that I have tested thus far have the proper touchscreen driver. I guess I could use one of these firmwares as a starting point. What would be a good resource for learning how to build a ROM and how to discover which drivers I need?
Click to expand...
Click to collapse
Google has its own building community and there are some great tut in this site as well.
The issue most roms are facing is that the drivers to these devices are almost never available. They tend to be hacked drivers that violate one copyright or another so they are never available to the public.
You might be able to find something on a China based site where they deal more with knock offs then we do here.
zelendel said:
Google has its own building community and there are some great tut in this site as well.
The issue most roms are facing is that the drivers to these devices are almost never available. They tend to be hacked drivers that violate one copyright or another so they are never available to the public.
You might be able to find something on a China based site where they deal more with knock offs then we do here.
Click to expand...
Click to collapse
Thanks for the quick replies. Guess it's time to do some research.