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...
As I understand it, there is a linux kernel that android sits on. I thought the ROM was like a virtual machine running inside of android and then we loaded apps onto that. I read something that indicated that each custom ROM comes with a kernel. Then we can replace that kernel with another one if we wish. I understand that the kernel must be compatible (although I don't know how to tell) but that seems confusing. It would seem that if the ROM is running in android then as long as the kernel can run android, any kernel should suffice. Clearly that is not the case so what exactly is a ROM and why does it interact directly with the kernel?
A ROM in this case is a system image (full or partial) containing the Android operating system, drivers, applications, and/or kernel.
Like with regular PC OS not all kernels are compatible with the larger OS, primarily across major versions.
check this link
http://www.xda-developers.com/android/understanding-android-fr
Rom futures
does anyone know where roms are going? read somewhere 2.3 and 3.0 are forks. that makes sense if 2.3 continues focus on phones, small devices etc and 3.0 continues down the larger tablet track. I am currently running 2.3.3 on gtab and it runs great. it seems to be very tablet friendly. does 2.3 provide much of the functionality of 3.0 for the small screen. can we expect 3.0 to bring additional utility to tabs like the gtab? just curious where we might be headed. keep up the great work. i stay excited about the next build!
Rumbleweed said:
check this link
http://www.xda-developers.com/android/understanding-android-fr
Click to expand...
Click to collapse
This is a GREAT link! Thanks.
I'm NOT EXPERT, I'm ONLY TRING TO HELP and SORRY IF I MADE SOME MISTAKES!
I have some ideas for porting android 3.2 to Folio 100 but I can't do all myself - I need some help.
My first idea is:
To add changes made in android 3.2 system(framework, apps etc.) to our Honeycomb from SDK or Xoom and decompile zlmage inside HC kernel(if that tool existe or find it's kernel source, add changes from android 3.2 kernel and recompile it).
---------------------------------------------------------------------------------------------------------
1. This idea is really hard to realise because kernel(I don't think that tool existe) but it's convinient(we'll finish it in short period with little work).
2. For this idea first we need to add changes from android 3.1 and after that from android 3.2.
3. I NEED YOUR HELP to find WHAT ARE CHANGES and TO DOWNLOAD
THEM for adding them to OUR build(First android 3.1 changes and after android 3.2).
For system that isn't problem but for kernel it is. The most detiled list of changes can
be find at Android SDK site but I think that we can't download them.
4. I think that mblaster know a lot of kernels and compiling it won't be problem for him.
----------------------------------------------------------------------------------------------------------
My second idea is similar to first one:
To add changes made in android 3.2 system(framework, apps etc.) to our Honeycomb from SDK or Xoom and compile android 3.2 tegra kernel from
Android Git or from other sources.
----------------------------------------------------------------------------------------------------------
1. I think that this idea is the best if mblaster help us or some one else that know a lot
of kernels.
2. Google won't relise full source of android 3.2 before pushing up android 4.0 aka
Ice Cream Sandwich to shops.
----------------------------------------------------------------------------------------------------------
I can port system itself(it will be faster if someone make a list of changes) but kernel is
a problem. I don't know much about kernels and because it I post first idea.
If you have new ideas or you don't agree with me or want to help me, please, post here!
EDIT: Android 3.2 might work with our HC kernel.
Sent from my Folio3x using Tapatalk
good idea +1
Thanks.
Sent from my Folio3x using Tapatalk
Not interested?
Sent from my Folio3x using Tapatalk
nice idea..
if u write drivers and kernel change, some other developer can use your work alot.
anyone writing all the drivers for folio will make toshiba happy, as they did not do it..
so if you make all this happen and write the drivers , i am sure folio will once again be a good tablet.
the development is something that takes companies 3-6 months to do, so you will be back in december 2011 or maybe early 2012 with your release?
Can someone compile Tegra 3.2 kernel from here? I tried but without success. I'm porting system now.
I tried to unyaffs FolioComb 3xx v2.0 image bu I got 'Segmentation fault'???
I succefully unyaffsed Android 3.1 and 3.1 SDK images.
I'll try to backup it from my tablet(I have FolioComb on it)
Nice to see someone trying to update folio 100, thanks to you and people in CM7 thead.
I don´t know about compiling so I cant help. But i keep an eye in this post.
Do you know anything about system?
EDIT:Nothing
Any one had same experience? It may be something missing or HTC problem?
warnings in and of itself are not problematic
but does it compile ?
does the example actually run in the emulator ?
see this thread i initiated:
http://forum.xda-developers.com/showthread.php?t=1210770
i can't get the sdk examples to run
i really wonder if anybody can ?
Many warnings in "Official Demos" are unacceptable. I tested and only one demo can complied and worked - it is "PenEventCompatibiilityDemo". The demo solve compatibility issues for Android 2.3 and 3.1. IMHO, they wanted to push all developer to develop Android 3.1 (Honeycomb) but their source mixed with Android 2.3 (Gingerbread).
I think they must upgrade flyer to Honeycomb first, because even I make the apps but I can't test it in actual device....
Included is the PenEventCompatibilty jar library to be packaged with your application should you want to write a low level PenEvent application that supports both Android 3.1 and Android 2.3.
Click to expand...
Click to collapse
sc3sc3 said:
warnings in and of itself are not problematic
but does it compile ?
does the example actually run in the emulator ?
see this thread i initiated:
http://forum.xda-developers.com/showthread.php?t=1210770
i can't get the sdk examples to run
i really wonder if anybody can ?
Click to expand...
Click to collapse
so you are actually saying:
it is a mess
I made an app for Android targeting phones. I am working with Eclipse and using "Android Virtual Devices" (developer.android.com/guide/developing/devices/index.html) to test the app on all sorts of phones.
Is it possible to use the CM7 Alpha12 ROM and load it into an Android Virtual device?
I know this is hardly NOOK specific but then again, I'd like to test my app as close as possible to the CM7 ROM for the NOOK.
Cheers
Do Not Post Questions In The General Section - All Must Read -
Moved To Q&A
Thanks aerosign for contacting me asking for this to be moved
aerosign said:
I made an app for Android targeting phones. I am working with Eclipse and using "Android Virtual Devices" (developer.android.com/guide/developing/devices/index.html) to test the app on all sorts of phones.
Is it possible to use the CM7 Alpha12 ROM and load it into an Android Virtual device?
I know this is hardly NOOK specific but then again, I'd like to test my app as close as possible to the CM7 ROM for the NOOK.
Cheers
Click to expand...
Click to collapse
It's based on the same version of Android as any other CM 7 build, including phone versions; that is, it's based on Gingerbread. So.. probably.
I recommend a "try first" attitude with this sort of thing. There's no harm in attempting it first and then asking if it's doable if you have trouble getting it done.