yashsingh1/xdaforums huggingface dataset:
[Gen9 Android Development] stealthdave:
SO... I've got it booting, but it's hanging at the CyanogenMod spinning logo. It will load CWM, which is nice. I suspect that it's differences in my hardware, as I'm running an A80S with an OMAP4430 CPU. Processor details:

# cat /proc/cpuinfo
Processor	: ARMv7 Processor rev 3 (v7l)
processor	: 0
BogoMIPS	: 592.26

processor	: 1
BogoMIPS	: 594.77

Features	: swp half thumb fastmult vfp edsp thumbee neon vfpv3
CPU implementer	: 0x41
CPU architecture: 7
CPU variant	: 0x1
CPU part	: 0xc09
CPU revision	: 3

Hardware	: ARCHOS A80S board
Revision	: 0005
Serial	: 0000000000000000
OMAP revision	: OMAP4430 ES2.3
Boot	: 5.05.000009

Based on comments, I think I might have the slowest machine trying to run this. :) It boots and I can get an adb connection, but the UI never launches. Looking through the attached logcat (which is really long and so hopefully complete enough for you), nothing really stuck out as a "eureka!" moment as to why the desktop won't load, but I'm far from an expert in these matters.

BTW, I do have an Ubuntu dev machine available, but I'm a complete n00b when it comes to compiling for Android. However I'm willing to help out wherever I can.

- DaveS
[Gen9 Android Development] Quallenauge:
Had you completly wiped your system before using the image? Seems, that some packages are left from stock rom.

E/PackageManager( 5751): Package android has no signatures that match those in shared user android.uid.system; ignoring!

Please remove them via SDE Menu:

Format -> Reset Android & Storage

Then mount the data partition on you PC:

Developer Options -> Export Data Partition

Then copy the images as usual via

sudo mkdir -p $MOUNTPOINT/local
cp archos_image/archos.ext4.update $MOUNTPOINT/local/archos.ext4
sudo umount $MOUNTPOINT

Does it boots now?
[Gen9 Android Development] trevd:
Hi

My board is exactly the same

Processor	: ARMv7 Processor rev 3 (v7l)
processor	: 0
BogoMIPS	: 592.26

processor	: 1
BogoMIPS	: 594.77

Features	: swp half thumb fastmult vfp edsp thumbee neon vfpv3
CPU implementer	: 0x41
CPU architecture: 7
CPU variant	: 0x1
CPU part	: 0xc09
CPU revision	: 3

Hardware	: ARCHOS A80S board
Revision	: 0005
Serial	: 0000000000000000
OMAP revision	: OMAP4430 ES2.3
Boot	: 5.05.000009

Looking at your logs, at first it looks like you need to clear your data ... if you're feeling brave you could try it using CWM, It may hang however or alternatively follow the instructions at the start of thread.

If you've already done that, then I would do some sanity checks like comparing the hash on the archos.ext4.update file after you've copied it.

Failing that run "adb shell dumpstate > state.txt" and "adb shell dumpsys > sys.txt" these take a couple of minutes and will give us the full system info, but as you've got no data on there, there shouldn't be any personal information in them.
[Gen9 Android Development] stealthdave:
Right now, I'm stuck at this step. I'm on a Mac at work, and when I plugged in the USB cable at this step, it did not recognize a writable partition and asked me to format. I formatted as FAT32, but that didn't work.

I tried to format data through CWM, but so far it hangs on this step.

I did try this method:

Format -> Reset Android & Storage

Install zImage and initramfs.cpio.lzo

Reboot to CWM

mounts and storage -> mount /data

From terminal: adb push archos.ext4.update /data/media

Reboot

However, it's not looking good; I'm still waiting for it to boot. Would it be possible to construct a CWM restore zip from the archos.ext4.update file? I could try to sideload it to CWM from an sd card. I'll have to research the format which I think is primarily ext4 files in a zip container. Stay tuned.
[Gen9 Android Development] trevd:
There no need to create a zip at the minute because the image file is the installed system+rootfs, If you want to use adb through cwm do the following

1. use cwm to mount the data partition.

2. adb shell mount

you mount list should look like this

rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mmcblk0p1 on /mnt/rawfs type rawfs (rw,relatime)
/dev/block/mmcblk0p2 on /cache type ext4 (rw,nodev,noatime,nodiratime,user_xattr,barrier=1)
/dev/block/mmcblk0p4 on /data type ext4 (rw,nodev,noatime,nodiratime,user_xattr,barrier=1)

3. adb shell mkdir /data/local

4. adb push archos.ext4.update /data/local/archos.ext4
[Gen9 Android Development] stevemp:
local

removed trevd answered first. :)
[Gen9 Android Development] trevd:
Makes a change for me! :p
[Gen9 Android Development] stealthdave:
And BOOM! goes the dynamite! Thanks everyone, this is AWESOME!!!

:highfive:

So far, very smooth!

I also took a moment to test the Bluetooth connectivity with my Apple Magic Trackpad. I was able to pair it successfully and it was recognized as an input device, but unlike stock firmware it did not act as a "mouse" when connected. However, connecting a USB trackball through my OTG adapter did work as a regular mouse and pointing device. Not sure if this is a bug or not; I've never tried connecting it to a CM device before, so this may be as expected. I'll try to test my Bluetooth keyboard between now and Monday. Let me know if you want a logcat.

- DaveS
[Gen9 Android Development] trevd:
Do us a logcat and a dmesg, I think It might need a kernel driver , their maybe one already built in /system/lib/modules that you can insmod.

Pull the Dmesg just after you've plugged the Trackpad in :)
[Gen9 Android Development] trevd:
[MENTION=4636351]Quallenauge[/MENTION] Can you mark the zygote service as critical, Although it won't stop boot loops , It will help because after a service marked as critical has restart 4 ( or 6, I can't remember ) it restarts the system in recovery mode.

At least it will save ppl sitting, staring at Boot animation for 45 minutes should a boot loop occur

[RANT]

I F*king hate boot animations, they're the most pointless thing ever, they tell you absolutely F'all about what the system is doing.

Obviously ChainFire's live dmesg/logcat is the exception that proves the rule. But who has that installed?

[/RANT]
[Gen9 Android Development] stealthdave:
Can't install purchased apps

I've come across an interesting bug: I can't install purchased apps. Free apps install just fine, but ones that I've purchased fail with the following error:

Error
Couldn't install on USB storage or SD card

I've gotten this error with and without an SD Card mounted. After I got the error, I updated to the latest gapps from goo.im (hooray for CWM!), but the error persisted. As ever, a logcat is attached!

- Dave

P.S. - It may be a while before I can get a log for the trackpad; I've got to get some real work done before the weekend. ;)
[Gen9 Android Development] Quinny899:
Make a folder called app-asec in /data. That's the culprit. I believe my PA versions that I released had this fixed in the init, it's pretty simple to add
[Gen9 Android Development] stealthdave:
Yep, that did it. Paid apps are streaming to my device as we speak! :good:
[Gen9 Android Development] realismo:
First of all guys awesome work! Do we have any chance to improve the kernel a bit? I mean as in stock roms the I/O seems much better. I know Quadrant a'nd stuffs like that doesn't really matter in this case, but it shows extremly low score. One more thing the CPU governor is always ineractive as default. Is it okay? I hope we can get a bit improvement but absolutely nice work! Thank you guys!
[Gen9 Android Development] trevd:
Dude, Chill out with the benchmarks, The kernel has a lot a debugging code so benchmarks are pointless at the minute and that Quadrant nonsense is exactly that, If you're going to do benchmarks we need real numbers like mb/s throughput and I/O response times in milliseconds not some meaningless number.

You have a chance to improve the kernel. just grab the code and build yourself one with the settings you want, easy!

https://github.com/Quallenauge/kernel-archos

use the linux-ics-3.0.21 branch, You can pull the config from the device.
[Gen9 Android Development] Quinny899:
Face unlock works in 0.1.0, you just need to install it. Anyone want a flashable zip?
[Gen9 Android Development] trevd:
[MENTION=3563640]Quinny899[/MENTION]

If you're making flashable zip make sure you mount the right partitions especially when adding stuff to the system image becuase you need to set it up as a loop device using losetup and then mount it. Also the recovey.fstab in the current version is not correct and you require an external sdcard for installing from SD.

So just PROCEED WITH CAUTION at the moment.
[Gen9 Android Development] Quinny899:
I'll wait a bit then, I noticed the system mount issue when installing the old emoji font
[Gen9 Android Development] trevd:
Hi Folks,

And now the moment you've all been waiting for, I'd like to present a CWM Flashable Version of the #0101 Rom.

Changes / Fixes:

[B]CWM:[/B]
Updated to 6.0.3.1
Fixed System image mount
SDCard now references internal media
External SDCard mounting option added

[B]Android:[/B]
1. Removed Unused Archos Services from init files ( avos , djmount , proftpd , audiomixer + many more)
This actually made my device a lot more responsive. It was very laggy before that.
The services that have been removed formed the backbone of the Archos Media Sharing Framework.

2. Added a service to mknod /dev/omaplfb
I think this is needed for HDMI

3. Removed The Emedded Linux Installation from the Root ( /bin /usr /lib + others ) ]
Kudos To Quallenauge for making that a fairly painless task as all the firmware and kernel objects where
in their correct Android homes :good:

4. Split the Rootfs and System Partition
As the Embedded Linux Installation has been removed, the rootfs is no longer 50MB+
We can now use a normal android ramdisk to boot the system which only contains the init files and
the sbin directory. In the background the System still resides on the /data/local/archos.ext4 image which
is loop mount by Android's Init process.

It should be good for flashing zips however , speaking of which http://tinyw.in/tfFZ , Have Fun! :silly:
[Gen9 Android Development] freezenook:
Trevd, looks great :rolleyes:! ! Does it replase stock Archos recovery?

Does backup/restore functitional work?
[Gen9 Android Development] trevd:
No, Archos Recovery is left in place..... that's the failsafe for when we break it. :laugh:

The backup, I thought I had fixed for this release but I've just tried it and No Dice, Give it a go.

So I answer to your questions No and No! Not at the moment anyway!
[Gen9 Android Development] freezenook:
But how it boots? Like early CWM after press power only (like usual boot without CWM)?

And can I install CWM for stock 4.0.28 and based roms? I want to use install from zip feature for my 4.0.28 based rom :p
[Gen9 Android Development] trevd:
On a Technical Level, The Linux kernel allows you the embed another ramdisk inside the kernel aswell as check for an external one, so that's where the recovery lives, Also TI OMAP 4xxx Boards have "Scratch Ram" which is not cleared on Reboot that is where we stash the reboot reason ( recovery or android ) .

Not quite sure I follow you,:confused: but I've set this to boot into CWM from cold for Development Purposes, I expect that to change once I find the correct way of catching the early GPIO events.

You Can for me, That's what It's there for, You'll just end up mounting the ext4 which contains both the root+System. Might be a bit hacky tho. Also obviously it's compiled in this kernel at the moment be it's a small patch to put it in a less "Experimental" kernel.

You can split standard archos roms into separate android ramdisks and system images. I did it myself right before I bricked my last Tab :laugh: There's just a bit more symlinking involved.

You just need to get a feel for how the Rom is laid out, then you can do what you like, :cyclops:
[Gen9 Android Development] stealthdave:
Boot and Re-Boot were in a boat...

So, the Flashable CM10.1 image works, but I'm now getting a reboot every 5 minutes. It's not your standard boot-loop; everything comes up and I can use the tablet normally for a very limited time. This could be unrelated to the "flashable" backup version; I actually tried the flashable backup because the original install stopped working, so there could be some residual issues there. The logcat is attached; from boot to re-boot!

Thanks!

- Dave

P.S. - What's up with the forums style sheets? Did XDA give up CSS for Earth Day or something?
[Gen9 Android Development] trevd:
Hi Seems you're missing the abcbox binary as create_nvs and create_sysid are symlink sof abcbox

--------- beginning of /dev/log/main
E/logwrapper( 127): executing /system/bin/create_sysid failed: No such file or directory
I/logwrapper( 111): /system/bin/create_sysid terminated by exit(255)
E/logwrapper( 135): executing /system/bin/create_nvs failed: No such file or directory
I/logwrapper( 133): /system/bin/create_nvs terminated by exit(255)
E/WatchdogDaemon( 116): ERROR opening temp sensor: No such file or directory

Seems I am as well, which must mean I missed it out of the update , B*llocks!! i'll fix and upload a new zip when I get chance.

In the mean time this should sort you out

Start in CWM Recovery Mode
adb shell cp /sbin/abcbox /system/bin/abcbox
adb reboot

:good:
[Gen9 Android Development] Quallenauge:
To confuse all readers... ;)

Hey!

I had an idea! My goal was to get the latest kernel 3.0.31 from omapzoom running on our platform.

My approaches last year was only partly successful....I collected at least some knowledge.

Now I tried it again. I knew, archos has done a split of the omapzoom reference kernel. I searched (or better: let a script do the dirty work) this split revision by comparing each revision in the history with the gitorious rom revision. Then I searched the one with the lowest diff count. So, this were the first steps...and this give at least a direction but not the real goal, because Archos has not taken a revision and modified it, but add another cherry-picks to the kernel.

So my last attempt was to extend the search of diffs for each file in our latest kernel 2.0.21.

Starting from newest revision, search for each revision at the history and make diff.

If the diff is zero, then a best match is found.

If not, write this commit data and diff count into the pipe and go further.

After reaching the last revision, sort the list to get the "best" match (even the diffcount is not zero, means: modified by vendor)

For example:

Best match found (0 diffs):

00000 changes 2012-06-13 20:13:39 +0300 - USB: musb: check input parameter in dma_controller_destroy for commit ---- b23e377bff1d2feac5e19f11edc5182d40aa2aad ---- ./arch/arm/common/fiq_debugger.c

Best match found (45 diffs):

00045 changes 2011-10-17 19:19:17 -0500 - omap: remoteproc: add a notification for loading error for commit ---- 7a07bb8bed013d51bd291f1b9d50da506727146b ---- ./arch/arm/include/asm/setup.h

The commit is irrelevant, because it was the last revision in the search list.

At the end I wrote the revisions in a list.

Some hours later (on a eight core machine...) the search scripts were finished.

The I checked out only these commits. After that, I overwrote all files from our latest kernel 2.0.21.

Then I made a reverse patch - which contains only the changes from Archos (mostly :) ).

After that I checked out the latest revision from omap zoom and applied these patches. I was surprised how easy the conflict resolving was - only a few files! I compiled the kernel and and tried the first boot: Bam! No sign ;)

Then after checking out what's the cause I was using the wrong initramfs.cpio which gets somehow corrupted at the merge process... After adding them from kernel 2.0.21 - the kernel was booting :) And the drivers where also loading :)

So the sound is the only thing, where I did a workaround. I used the files from the latest kernel 2.0.21....then it worked.

So here it works, but I'm afraid that this kernel would be running on another machine than Archos 80S with 1Gbyte RAM.

But....who knows?

If someone want's to test it out here is the version 0.2.0.

Changes:
Updated to kernel 3.0.31

So, now I'm looking forward to my holidays :)

EDIT: Added the used patches:

archos_patch.txt.gz - Patch against 3.0.21 stock rom.

archos_patch_latest.txt.gz - Patch against patched 3.0.21 rom (new graphics drivers).
[Gen9 Android Development] trevd:
Once again, Amazing and dedicated as well. I'll give it a go on the 512MB and patch it up if anything needs doing when I get chance,

My 3.0.31 repo contains an A101S board file that I got booting when we worked on it last year although I have no 101 to test it with now.

Is it CWM Flashable or did you go archos classic for the ramdisk? I'll make a CWM one if needed, again when I get chance.

Surprised you didn't go straight for the jugular and grab the 3.4 branch ;) LOL,
[Gen9 Android Development] stealthdave:
YEEEEESSSS!!!! :good:

Good news, everyone! It works great in my OMAP4430 w/512MB! Enabling ADB required a reboot, but everything installed and ran very smoothly! So far, no reboots. Very well done!
[Gen9 Android Development] Quallenauge:
Old fashion! I will try to update/convert when I'm back from holidays. In the meantime your are welcome to update my repo init files to not load the archos stuff (avos,...) , you mentioned.

No, I tried that sometimes, but with no luck! To much changes there in the structures. For example, the serial adapter works in a completely different matter. Without some deep knowledge in starting the kernel -and without a proper serial console- I'm lost when the basic kernel init routines fails. So, I decided for me to not try it again (in the next weeks).

But merging the aosp kernel 3.x.x line seems to be an easy part, checkout the version 0.3.0 which makes use of the 3.0.58+ kernel.
[Gen9 Android Development] stealthdave:
Works nicely on OMAP4430/512MB, installed over 0.2.0.

I'm also playing around with nandroid backups, specifically using the Orange Backup Root tool which allows live nandroid backups. (This is indispensable to me on my Galaxy S3.) I did this for a couple of reasons:

I prefer the live backups so that I can keep using my device!

More importantly, there was a mention earilier in this thread stating that CWM backup wasn't working properly, so I thought this might be a reasonable work-around.

However, this fails as well. The main error I'm seeing is:

mount: can't find /system in /proc/mounts

Now I'm not trying to get tech support for Orange Backup or ONandroid here (totally the wrong forum), but I thought this might be useful information for debugging the current CWM backup process.
[Gen9 Android Development] trevd:
Hi

It's because the new release from Quallenauge uses the old style format where the rootfs+system are in one image. They need splitting ( again ) well I actually need to update the Source Code so that's how the images get built. Just a bit busy this week tho.
[Gen9 Android Development] realismo:
Excelent news! :) 0.2.0 and 0.3.0 is very good however I can't enable init.d support because it stuck on the Archos logo after the restart. I didn't have same problem with the 0.1.1 maybe it casued by the different structure. I hope the new version will fix it. BTW awesome work guys, keep it up.
[Gen9 Android Development] Quinny899:
Just got around to installing the cwm version, after installing 0.2.0 from my phone (PC was installing Ubuntu 13 :D ) and it all works well with less lag, as reported
[Gen9 Android Development] trevd:
As usual folks this is a test, Please attach logcats & dmesg when reporting issues/bugs.

Here's a CWM Flashable Version built from the latest CM Sources ( 2013-04-27 )

============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.2.2
CM_VERSION=10.1-20130427-UNOFFICIAL-archos_g9
TARGET_PRODUCT=cm_archos_g9
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.5.0-27-generic-x86_64-with-Ubuntu-12.10-quantal
HOST_BUILD_TYPE=release
BUILD_ID=JDQ39E
OUT_DIR=/media/android/build/android-cm-10/out
============================================

Change Log:

Kernel Version: 3.0.58+

Standardized the rootfs init files
==================================
This brings our init files inline with the standard android/cm file. This should make it easier to incorporate any further changes made
upstream

init.rc - now boots using a standard init.rc file, device specific settings have been moved into init.archosa80rcboard.rc
I've also merged init.archos_init.rc into init.archos.a80sboard.rc .

init.usb.rc - added generic usb setup file
init.trace.rc - added generic kernel tracing setup file
init.archosa80sboard.usb.rc - new file containing device specific usb setup
ueventd.rc - updated to use the CM standard file.

adb always on
===============
adb now remains active throughout booting. persist.sys.usb.config gets set =none,
previously this would disable adb, this is now ignored and you should be able to reconnect to adb after a first load initial cut off

reboot recovery option
======================
Reboot Recovery Reboot option is now available by activating Developer Options/Advanced Reboot

Download:

Goo.im : cm_archos_g9-userdebug-4.2.2_JDQ39E-CWM_6.0.3.1-K3.0.58.zip

Devhost Mirror : http://d-h.st/ABW

gapps are installed separately:

http://goo.im/gapps/gapps-jb-20130301-signed.zip

Additional Files:

As an stop-gap while I get CWM working properly here is a flashable zip that will delete the user data from the data partition /dev/block/mmcblk0p4 - this will leave intact /data/local , which is where our system partition image is stored ( /data/local/archos.ext4 ) and /data/media which is the location of the multi-user storage directories.

http://goo.im/devs/trevd/archosg9/cm10.1/wipe-data.zip

Install via CWM.

Thanks.
[Gen9 Android Development] Quinny899:
@trevd

Seeing as how we're using zips now this might be useful:

And then just include the GooManager app as a system app

Simple enough for future ease of use
[Gen9 Android Development] realismo:
I'm very curious, but goo.im seems like a snail maybe if you can upload to an other host. 12h left thats very slow :(
[Gen9 Android Development] trevd:
Devhost link for you ( and everyone ) http://d-h.st/ABW
[Gen9 Android Development] trevd:
Cheers Quinny,

Well this version leaves the ro.device intact so it's set as archos_g9 , If I install GooManager I can see your PA Builds, I suppose I should add some goo version details to this one then :D

[MENTION=3563640]Quinny899[/MENTION] Can you get delete that Poll off the thread please or is it here to stay! :D and maybe get the first post updated at some point ;)
[Gen9 Android Development] therbom:
Builds for A101S

Build 0.1.0:

http://www.4shared.com/archive/YsYm6IL5/a101s.html

Build 0.3.0:

http://www.4shared.com/archive/gJCe3xZi/a101s_030.html

It might take a while before Wi-Fi is enabled.

Have fun!
[Gen9 Android Development] trevd:
Hi Folks

Here's a CWM flashable version ( 3.0.58+ Kernel ) with A101S Support

update-a101s-test.zip - 177.10 MB

Big Thanks to [MENTION=3279100]cobje[/MENTION] for testing and basically get this working. :good:

As an additional test, this one is compiled with libjpeg-turbo and the bionic library from linaro.

As always please attach logs and dmesg when reporting issues
[Gen9 Android Development] Quinny899:
I think it's time to edit the OP :)
[Gen9 Android Development] Quinny899:
Also, would it be possible to get an ext4 with just the newest CWM? So you don't have to download a massive ext4 just to install a zip half the size
[Gen9 Android Development] trevd:
It's built into the kernel zImage, "Don't need no ext4 for CWM" :D

I might look into an update.zip for people coming from stock, one that data wipes , removes stock android and creates a new ext4 image file before flash, that way they only need to flash a zImage+ramdisk through archos recovery and then flash a zip....... or would that make it just too easy? :silly:

I'll see what the remove stock android option is doing in the Rom.