Related
Since SDE was released, who wants to build some fresh and shiny android which might be running someday side by side with AVOS (Archos Android)?
What do we need (openembedded?)?
Installation of Other OS:
root: /mnt/storage/rootfs.img
kernel:
Reboot into Recovery Mode (howto)
Recovery System -> Developer Edition Menu -> Flash Kernel and Initramfs
Connect USB and copy "zImage" and "initramfs.cpio.gz" to the Archos
Unmount Archos on PC (safe remove)
Press ok on Archos
Don't you think dev's are already working on this right now?
OpenAS is a site to look at, there are a few in fact and some even on XDA.
your instructions are sort of nothing anyone who has booted the angstrom distribution can see that?
this thread is a bit pointless. your asking for devs to create something they are already working on and you can't help as you don't know how?
no, you just missed the point. I AM (or want to be) a dev, see my other thread about dvb-t support
and now I'm looking for some help and informations.
this thread should be dedicated to building gen8 android (2.2 / 2.3 / ...) roms, I don't care much about angstrom.
I'm not one of those annoying guys who just complaining about others work, I want to get my hands dirty and do some work! I already checked openaos out, there a lot of informations about gen6 and gen7 but not gen8, this is why I started this thread here.
summarizing informations, that's the point.
ok fair enough
it's more likely though someone will do a port and use it over the current android system as apposed to using the SDE. Most dev's will be concentrating on other O/S's such as Ubuntu etc.
I can see why you want to do it but im not sure it will be done this way. We havent even managed to get perm root yet, sadly the archos wont get a lot of love I fear.
we have perm root, just use SDE and put an android in it we can decide everything
edit: either you hack the gen8 and get rid of SDE and archos' android and put whatever you want on it or you stay with SDE and dual boot (sounds a less "brickable" choice to me)
chulri said:
no, you just missed the point. I AM (or want to be) a dev, see my other thread about dvb-t support
and now I'm looking for some help and informations.
this thread should be dedicated to building gen8 android (2.2 / 2.3 / ...) roms, I don't care much about angstrom.
I'm not one of those annoying guys who just complaining about others work, I want to get my hands dirty and do some work! I already checked openaos out, there a lot of informations about gen6 and gen7 but not gen8, this is why I started this thread here.
summarizing informations, that's the point.
Click to expand...
Click to collapse
I have no idea what you're talking about, but I say go with your dreams and keep up the good work (whatever work that may be).
Don't let anyone tell you you can't do it (whatever "it" may be). Any contribution to making my A70 better is a + in my book.
chulri said:
we have perm root, just use SDE and put an android in it we can decide everything
edit: either you hack the gen8 and get rid of SDE and archos' android and put whatever you want on it or you stay with SDE and dual boot (sounds a less "brickable" choice to me)
Click to expand...
Click to collapse
But it's pointless having android 2.2 / 2.3 running alongside android 2.2 / 2.3
it would be a complete waste of time especially as archos are currently working on it anyway.
It would achieve nothing, the SDE would be much better used running ubuntu/winxp or other, running android as a secondary boot option is a waste of development time and I cant see anyone wanting to do it?
by all means join in getting a good distro to run but not another version of android when all we are missing is root anyway. I think your getting confused as to what SDE is used for.
why would someone want to run ubuntu on this hardware? winxp is out of scope as it doesn't support arm processors.
waz000000 said:
by all means join in getting a good distro to run but not another version of android when all we are missing is root anyway. I think your getting confused as to what SDE is used for.
Click to expand...
Click to collapse
why shouldn't we have root in SDE?? The SDE is the only way (so far, gen8 hasn't been hacked yet) to get perm root and custom roms.
why won't you just use SDE to run custom android roms? why it has to be ubuntu or any other bloated linux distribution?
waz000000 said:
But it's pointless having android 2.2 / 2.3 running alongside android 2.2 / 2.3
Click to expand...
Click to collapse
no it's not, because archos won't let us do customizations. it would be easy for archos to let us perm root everything but they won't. so what are you going to do to make android comfortablier and less buggy on gen8? a) hack it and flash custom roms and may brick it or b) use sde and flash custom roms without the possibility to brick it
chulri said:
no it's not, because archos won't let us do customizations. it would be easy for archos to let us perm root everything but they won't. so what are you going to do to make android comfortablier and less buggy on gen8? a) hack it and flash custom roms and may brick it or b) use sde and flash custom roms without the possibility to brick it
Click to expand...
Click to collapse
Agreed, who cares if you have more then one build of Android on a device? On other devices people have developed their own method of doing this exact thing. SDE is a great idea to let people load custom ROMs onto their device without fear of bricking. Now if someone would just get one developed....
chulri said:
no it's not, because archos won't let us do customizations. it would be easy for archos to let us perm root everything but they won't. so what are you going to do to make android comfortablier and less buggy on gen8? a) hack it and flash custom roms and may brick it or b) use sde and flash custom roms without the possibility to brick it
Click to expand...
Click to collapse
Archos have released the source code, the only thing that's missing is Root.
The distro is already pretty close to stock even the BT stack is android native allowing us to use wiimote etc.
Archos have done a pretty "pure" android release Cynogen's goal is get a pure android rom working. Stock it's not that far away now?
and what about ISO, windows 7 (mobile), tiny linux, yellow dog, many other great distro's. All im saying is wait until root is achieved (it's being worked on) nd see what happens to the default android then.
Your may be jumping the gun a bit developing something that's not needed
waz000000 said:
But it's pointless having android 2.2 / 2.3 running alongside android 2.2 / 2.3
it would be a complete waste of time especially as archos are currently working on it anyway.
It would achieve nothing, the SDE would be much better used running ubuntu/winxp or other, running android as a secondary boot option is a waste of development time and I cant see anyone wanting to do it?
by all means join in getting a good distro to run but not another version of android when all we are missing is root anyway. I think your getting confused as to what SDE is used for.
Click to expand...
Click to collapse
was agreeing with you until this post.
the point is that Archos have up until now done a bit of a shoddy job of their Android builds. We all want the archos tablet running smoothly and as best we can and also would like to have 2.3+ on our devices which is probably unlikely by any official means.
and saying archos are "currently working on it" is a little silly given what forum you are on! (whats the point in people making custom roms for HTC devices... HTC are working on it anyway?!)
@wazalotofzeros
oh come on, are you kidding me? why is it so hard to understand that a rooted android or even custom roms are wanted by a lot of archos users (see archosfans.com)
whats the point of installing any linux distribution instead of android?
why are you telling me its pointless to do custom roms for the Archos Gen8 while there are custom roms for a lot of other android devices?
I give up, please contribute something useful to this topic or stop posting offtopic.
@waz000000,
don't want to participate in this then don't. There is no reason to put down others work though just because you think it is pointless.
Grand Idea
Personally I think this is a grand idea. At first when I saw the SDE I thought that was its whole purpose and that archos would start us off with a basic android version. But when it was released and it came with a barely working linux distro, it turned me off to installing SDE until something better can happen. I wouldn't mind seeing a micro version of ubuntu running on this, but the main problem is going to be the ram. If we are having issues with the ram on android what makes you think we will have better luck on a OS that wasn't intended to run on the archos. But hey more power to you. But on the other hand if we can build our own android firmwares, then we won't be dependent on Archos to decide whether or not to update to the next firmware. And saying Archos is working on it is like saying well the end of the world is coming. When IDK, but its coming!
Seriously. The delayed the launch by 2 months and then didn't deliver on their promise of launching with 2.2. They did come through, but with the crappiest 2.2 firmware I have ever used. Constant crashing, no wifi N, 200 mhz decrease in speed, and only a promise to fix it... eventually.
So the the OP. Go for it. I will help with what I can, but I haven't build a firmware yet except for the easy cook it yourself ones.
laptopfreek0 said:
They did come through, but with the crappiest 2.2 firmware I have ever used. Constant crashing, no wifi N, 200 mhz decrease in speed, and only a promise to fix it... eventually.
Click to expand...
Click to collapse
new firmware came out today! works great on my A101, no crashes or freezes so far: http://forum.xda-developers.com/showthread.php?t=875393
laptopfreek0 said:
So the the OP. Go for it. I will help with what I can, but I haven't build a firmware yet except for the easy cook it yourself ones.
Click to expand...
Click to collapse
Me neither but I'm willing to do if nobody else does, simply because of my DVB-T project in the other thread
€dit I'll give cyanogenmod a try
thefunkygibbon said:
was agreeing with you until this post.
the point is that Archos have up until now done a bit of a shoddy job of their Android builds. We all want the archos tablet running smoothly and as best we can and also would like to have 2.3+ on our devices which is probably unlikely by any official means.
and saying archos are "currently working on it" is a little silly given what forum you are on! (whats the point in people making custom roms for HTC devices... HTC are working on it anyway?!)
Click to expand...
Click to collapse
ok fair enough so what would you rather?
a cynogen mod with archos firmware or linux distro (Whatever) and cynogenmod?
im not saying dont work on a custom rom, im saying work on a "proper" custom rom and use the dual boot option for something other than android.
1st step develop root
2nd step develop custom rom
3rd step install another distro
What im trying to say is, develop a "proper" custom rom and leave the dual boot option for something mind blowing!
as to blazingwolf im not trying to put anyone's work down (apart from the fact there isn't any yet this is pure concept)
I could very easily help you develop a working second rom for this but all im saying is wait a little while and see what happens I cant hint anymore than that!!!!!!!!
waz000000 said:
I could very easily help you develop a working second rom for this but all im saying is wait a little while and see what happens I cant hint anymore than that!!!!!!!!
Click to expand...
Click to collapse
who does what and when it gets released?
in the mean time have a look here:
http://forum.xda-developers.com/showthread.php?t=610303
i know its different hardware but use a cynogen beta like the I9000 as a base, and work from there, even try the original firmware and look to cook that one.
you will be surprised how almost stock the archos one is
laptopfreek0 said:
Personally I think this is a grand idea. At first when I saw the SDE I thought that was its whole purpose and that archos would start us off with a basic android version. But when it was released and it came with a barely working linux distro, it turned me off to installing SDE until something better can happen. I wouldn't mind seeing a micro version of ubuntu running on this, but the main problem is going to be the ram. If we are having issues with the ram on android what makes you think we will have better luck on a OS that wasn't intended to run on the archos. But hey more power to you. But on the other hand if we can build our own android firmwares, then we won't be dependent on Archos to decide whether or not to update to the next firmware. And saying Archos is working on it is like saying well the end of the world is coming. When IDK, but its coming!
Seriously. The delayed the launch by 2 months and then didn't deliver on their promise of launching with 2.2. They did come through, but with the crappiest 2.2 firmware I have ever used. Constant crashing, no wifi N, 200 mhz decrease in speed, and only a promise to fix it... eventually.
So the the OP. Go for it. I will help with what I can, but I haven't build a firmware yet except for the easy cook it yourself ones.
Click to expand...
Click to collapse
the purpose of SDE is to give users a way to dual boot and be able to load "another" operating system. The Angstrom image we provide is just a demo and nothing else. You are free to put anything else, like Android 4.0, Meego, Maemo or whatever else you want...
Hello all!!
I'm new to Android and i'm interested in learning a bit and maybe get involved with it but there are some things that i don't get about android and can't find the answers.
My main question is why Android which is based on Linux is so hard to get updates for all devices at once?
For example we got ICS lately why it's only available for Nexus S and not for all devices that support android?
In pcs if there is a new Ubuntu version every pc can get it no matter the hardware it uses as there are drivers for it.
Is it so hard to have drivers for all the android devices?
Why do we need to wait forever for the X company that makes the phone to build a new kernel?
Is it about the libaries?The drivers?
Say i got a device that is not supported by ICS what would i need to make it supported? I got my libs from 2.3.5 can i toss them to overlay compile and works? If not y not?
Thanks in advance for your answers and sorry if my questions are too noobish, everyone has to start from somewhere
Serafym said:
Hello all!!
I'm new to Android and i'm interested in learning a bit and maybe get involved with it but there are some things that i don't get about android and can't find the answers.
1. My main question is why Android which is based on Linux is so hard to get updates for all devices at once?
2. For example we got ICS lately why it's only available for Nexus S and not for all devices that support android?
- In pcs if there is a new Ubuntu version every pc can get it no matter the hardware it uses as there are drivers for it.
3. Is it so hard to have drivers for all the android devices?
4. Why do we need to wait forever for the X company that makes the phone to build a new kernel?
5. Is it about the libaries?The drivers?
6. Say i got a device that is not supported by ICS what would i need to make it supported? I got my libs from 2.3.5 can i toss them to overlay compile and works? If not y not?
Thanks in advance for your answers and sorry if my questions are too noobish, everyone has to start from somewhere
Click to expand...
Click to collapse
1. Manufacturers don't release updates for all their devices all at once (some not at all).
2. It's ready (most stable so far) for that device (SDK ports; (almost) official update)
- Not true. If you tried to place Ubuntu 12.04 LTS on a PC with a 368 MHz and 32mb ram, it would not run .
3. Yes. Android is on devices from many different manufacturers with many different designs and hardware.
4. See here: http://en.wikipedia.org/wiki/Linux_kernel (to know what it is). Different hardware will require different commands, etc. If the manufacturer doesn't release the kernel source, development cannot be done on that device (properly).
5. Yes and yes (much more too).
6. Create a working port from some other device (with similar hardware) which is supported. Sometimes. Some versions of android have backward compatibility of those files but ICS isn't really backward compatible which is why many ports of ICS (for various devices) don't have a working camera, etc. See the 2nd paragraph here: http://www.cyanogenmod.com/blog/cm9-progress-update.
Lemme get some things out of the way.. I am a noob. I have searched. I have read some of the results from the search. I am overwhelmed by the 20+ pages of results (lol). I am not 100% sure this is the correct forum for this (not sure where else would be ).. I believe this is one of those things where I need help based on my situation.. Ok, so here I go.
I wish to start porting ICS to my phone. That's my goal. I have general understanding of how linux works, but I do not know much about the android specifics of how they work, or what needs to be modified for this to work. I do not plan to use the kitchen tool as I wish to learn this the hard way. I believe this will help me become more understanding in what I am doing. However, at this point I don't and that's why I'm here. My phone model is irrelevant almost because its prepaid and usually the communities don't even recognize their existence.. at least that's how I feel about it. But I digress. My phone is the zte warp by boost mobile and I am here to learn hopefully the things that will get me started on porting ICS to this phone. I right now believe that the best thing for me to learn is how the android related files work because as it is, I only looked at guides on how linux works and I understand most of it. I'm not sure that's the best thing that will help me port ics, but I'm certain it is important.
Please help me figure out where I should start in learning how to port ICS to my phone basically.
Thanks XDA
anyone? I am quite serious about wanting to do and go into this but I have yet one thread that anyone's ever replied to.. (or post iirc) which puts a damper on me
Snake X said:
Lemme get some things out of the way.. I am a noob. I have searched. I have read some of the results from the search. I am overwhelmed by the 20+ pages of results (lol). I am not 100% sure this is the correct forum for this (not sure where else would be ).. I believe this is one of those things where I need help based on my situation.. Ok, so here I go.
I wish to start porting ICS to my phone. That's my goal. I have general understanding of how linux works, but I do not know much about the android specifics of how they work, or what needs to be modified for this to work. I do not plan to use the kitchen tool as I wish to learn this the hard way. I believe this will help me become more understanding in what I am doing. However, at this point I don't and that's why I'm here. My phone model is irrelevant almost because its prepaid and usually the communities don't even recognize their existence.. at least that's how I feel about it. But I digress. My phone is the zte warp by boost mobile and I am here to learn hopefully the things that will get me started on porting ICS to this phone. I right now believe that the best thing for me to learn is how the android related files work because as it is, I only looked at guides on how linux works and I understand most of it. I'm not sure that's the best thing that will help me port ics, but I'm certain it is important.
Please help me figure out where I should start in learning how to port ICS to my phone basically.
Thanks XDA
Click to expand...
Click to collapse
From my limited knowledge, I think it is a huge task undertaking, you can download Android source code from Google, the hard part will be the device driver development and porting for Linux kernel (and maybe portion of Android). If you are lucky, you can use the existing phone bootloader (or you have to port one). Understanding the inner of the phone (different chip set may need different device driver) will be another challenging task.
by the device driver development, you mean all the libs that go into the phone? Couldn't I just copy/paste the pre-existing libs that are already made for the phone? Also the phone im working with is a bit strange really.. noone has been able to compile the kernel from its source and get it to boot yet.. when it was compiled the zImage was different than that of the stock one.
And yeah, I have downloaded the aosp source.. I just need to know where to start at and the processes involved really
Snake X said:
by the device driver development, you mean all the libs that go into the phone? Couldn't I just copy/paste the pre-existing libs that are already made for the phone? Also the phone im working with is a bit strange really.. noone has been able to compile the kernel from its source and get it to boot yet.. when it was compiled the zImage was different than that of the stock one.
And yeah, I have downloaded the aosp source.. I just need to know where to start at and the processes involved really
Click to expand...
Click to collapse
To answer you question no the drivers and lib files are different for aosp based rooms then they are for the stock OEM from. The first step will be to get a working kernel. Without anything you do will be pointless
I'm somewhat interested in the same thing, and from what I've gathered, you'll need to do these things to begin ROM development:
1. Read every page on the AOSP site and grab a copy of the AOSP source. It probably wouldn't hurt to read the regular Android developer wiki as well.
2. Learn about Linux driver development:
http://lwn.net/Kernel/LDD3/ (this is apparently considered THE BOOK on Linux driver development)
http://www.freesoftwaremagazine.com/articles/drivers_linux
3. Learn pretty much every detail about your phone and its hardware, especially when it comes to how ROMs are installed on it. For example, my phone (the Droid X2) has a locked bootloader, so 2nd init has to be used to boot new ROMs, and this makes it so that we cannot update the kernel.
You can usually find this sort of information on your phone manufacturer's website. Sometimes they even post the source code to their phone's drivers, which is helpful.
4. Look at other ROMs (preferably for your phone) and see how they work. The source code is freely available for most popular ROMs.
For example: CyanogenMod keeps their source code in a public git repository: https://github.com/cyanogenmod
5. Get to work on porting!
I would highly recommend starting with something smaller, however, just as a start. One good jumping-off point is probably this guide: http://forum.xda-developers.com/showthread.php?t=1272270
If any part of this was wrong, or if I left something out, somebody feel free to correct me, I'm still a noob.
Thank you so much for your direction, however,, android kitchen.. im not sure about that because isnt that only ment for htc devices? My phone is made by zte
what device do you even have?
if it's stuck officialy on 2.1 or 2.2 there's no hope that if you even port it that it'll work
its the zte warp from boost mobile (prepaid). Btw if I compile an aosp ics launcher and put that on my phone whats the chances of that working?
edit: it uses 2.3.5
Well Sebastian responded on android forums, apparently zte is very bad at version control with their kernel sources. So when they complete one project, they use the same source for the next project, and what they release could be for anything. Apparently the blade source had the same issues, it took him a while to get them to correct the source
Sent from my N860 using Tapatalk
Yeah I noticed that there were ppl saying there were things similar but I'm not sure what will work or what won't.. guess its time to start a petition on zte to release the source code lol
edit: seems like zte's bein a bad company and violated the GNU GPL license for not providing a complete source code.. I compiled an email and sent it to someone who can proof read it and send it to the right person for this kinda thing.. danggit zte
I know it's not as simple as it looks, otherwise everybody could do it, but at least can someone point me in a vague direction?
Just out of interest, how do you upgrade a device tree to support newer Android versions? Anything in particular which might prevent Android from functioning correctly?
I've acknowledged SELinux as a problem already.
I'm new to running device trees and kernels but I do know my way around Linux (I know how toolchains works, and I can build Android and kernels, for example) and I know C++, C and Java.
I've 'Google-d' the matter, but to no avail – there appears no clear way to do it.
+1 this question
i want its answer too:good:
Hi everyone,
After a few hiccups, I successfully rooted my Leagoo T5c, thanks to the excellent tutorial posted here. The phone works fine, thank you, but now, I'd like to know how to proceed to, say, upgrade the phone from its current Android version (7.0) to a more recent version.
Where to start?
Since this phone has a Spreadtrum/Unisoc SC9853i SoC (Intel-based), I suppose the custom ROMs and upgrade possibilities are few and far between, but I'd like to give it a shot.
I'm open to ideas, tips, tricks, voodoo moves and Santeria incantations, but I'm still a noob when it comes to Android, so please, be patient, and methodical... :good:
@UglyStuff
If you can unlock phone's boot-loader then you should be able to flash any Custom Recovery and/or Custom ROM that's suitable to 100% to phone's CPU-architecture. Who is the supplier of phone's SoC isn't of any interest at all.
Hi,
Thing is, as I said, I'm a noob when it comes to Android, so I don't want to brick my phone by trying to make it ingest a ROM that's not suitable for it.
If my phone came with a MediaTek or Qualcomm SoC, I wouldn't worry, because there are plenty of ROMs out there, custom or not, to play with, but this Spreadtrum/Unisoc SoC is a thing of its own.
It's based on Intel's Airmont architecture, and few phones or tablets use it, at least this specific version (SC9853i). Maybe I just don't understand too well how a ROM is built.
UglyStuff said:
Hi,
Thing is, as I said, I'm a noob when it comes to Android, so I don't want to brick my phone by trying to make it ingest a ROM that's not suitable for it.
If my phone came with a MediaTek or Qualcomm SoC, I wouldn't worry, because there are plenty of ROMs out there, custom or not, to play with, but this Spreadtrum/Unisoc SoC is a thing of its own.
It's based on Intel's Airmont architecture, and few phones or tablets use it, at least this specific version (SC9853i). Maybe I just don't understand too well how a ROM is built.
Click to expand...
Click to collapse
For example, I found this article where they explain how to flash LineageOS 17 (based on Android 10) on a Panasonic Eluga Ray 800 that uses the same SoC as my Leagoo T5c.
The thing is, I don't know if this is transposable to my device, though the two share the same SoC. As I said earlier, I don't want to permanently brick my phone...
@UglyStuff
The mentioned Intel Airmount SoC's instruction set architecture is x86_64 , the also mentioned Intel Spreadtrum SC9853i SoC's instruction set architecture is x86_64, too. Hence in order to upgrade yor phone's Android you need a Custom ROM compiled for x86_64 architecture. GIYF ...
OK, but since this Panasonic and my Leagoo share the same SoC, they also share the same x64 instruction set, so do I get it right if I say that the custom ROM built for the Panasonic would fit on my Leagoo, or am I missing something?
In theory it should.
OK, I guess I'll have to chance it, and use recovery in case things so south. My phone isn't compatible with Treble, according to this app. Does it mean anything in terms of installing one of the generic system images found here or not?