yashsingh1/xdaforums huggingface dataset:
[Gen9 Android Development] stealthdave:
Just wondering if anyone has taken a look at what fellow developers are doing on the original Kindle Fire? I know that at least it has the same processor and memory as the G9 Classic (OMAP4430 w/ 512MB RAM), and I believe that there are some other hardware similarities, though I can't recall what. (I bought my wife a Kindle Fire shortly after I bought my Archos and I remember coming across some hardware comparisons at the time, but I can't find them now.)

Obviously this won't help with the Bluetooth, Camera or HDMI issues, but perhaps it could provide some insights into the HD video (this ROM mentions hwcomposer specifically) or other issues?

- Dave
[Gen9 Android Development] solrakk6:
Hi Quinny :)

Have your custom the Camera and bluethoot solved?! Or continue not working :(

I hope you solve this. My archos is not the same with you arround him. thank you for that:good:
[Gen9 Android Development] Quallenauge:
Maybe this can help about bluetooth integration: Bluetooth support on Jelly Bean 4.2.2 (Device: Sony Smultron ST15i) on the e2e.ti forums.

I will try that soon.

Camera seems not too easy, because we think, that archos is using an own way to support that device.
[Gen9 Android Development] solrakk6:
Nice to ear that!

Since i read the reply by archos for jelly bean... That's my esperance and hope this will result in this PA Rom.

Fast and customizable.

PA RULEZZZZZz
[Gen9 Android Development] stevemp:
status

Guess I should update. PA 3.15 is working with a some optimizations:

TI_ENHANCED_DOMX and MULTIGPU

CodeAurora Optimizations: msm8960: Improve performance of memmove, bcopy, and memmove_words

Seems to improve AnTuTu benchmarks scores.

Camera driver is built in kernel now, need an app to use it.

Bluetooth is loading and searching for other devices but I don't have any way to test.

GPS is loading, no way for me to test.

HDMI loads and recognizes monitor, missing app again.

Archos used their own apps and framework so problem now is finding some way for them to work with open source apps.

I am using a rom based on 4.0.28, that's the reason so much is working, files are already there for bluetooth, gps, hdmi, and wifi.
[Gen9 Android Development] trevd:
Nice, Very Nice in fact, That's pretty much the lot isn't it? .... Did you go down the V4L route for the camera or stick with the OMX Implementation?

Looking forward to getting a peek at this beast! :good:
[Gen9 Android Development] stevemp:
camera

Added linux driver mt9m114 to the kernel, now need to add it to omx camera. Not going to be easy for me. :eek:

Archos uses the linux bluez for bluetooth, more info can be found here --> http://people.csail.mit.edu/albert/bluez-intro/

Bluetooth is working in ubuntu-12.04 for the g9 so not a big deal for it to work in android, need to integrate in settings.

Time to decompile some of the archos apps and search for strings to try find out what they did. :good:

Linux kernel patch if anyone else wants to work on it. :)
[Gen9 Android Development] trevd:
Trusty old strings! :D dexdump is pretty useful I found the output is nice and verbose. It is in the out/host/linux-x86/bin directory along with a collection of other interesting tools.

Bluetooth wise, up until 4.2.2 Android used bluez aswell before moving over the broadcom provided bluedroid stack. The link that Quallenauge posted seems pretty useful. Info is a little thin on the ground still but it I think bluedroid breaks down into a kernel module and a libBTvendor library which is an Android HAL Library. There is of course nothing to stop us ( you ;) ) from continuing to use the bluez solution. A ( simple :D ) case of forward porting that part of the stack from the previous version.... I think!

I suppose the same applies with the camera, if the linux side is working happily wih a V4L implementation......

Hopefully I'll get chance to play around with the archos stuff this weekend...... Sleep First however. Then I might stand a fighting chance of understanding things a little better.
[Gen9 Android Development] stevemp:
ti

TI is still using bluez for blaze tablet 4.2.2. Is bluedroid broadcom better in some way? From blaze_tablet 4.2.2 BoardConfig.mk.

# TI's Bluetooth stack based on BlueZ

BLUETI_ENHANCEMENT := true

Does compat.ko build for you? Needed for backward compatibility with bluetooth modules for our old kernel.

https://backports.wiki.kernel.org/index.php/Documentation/compat

Seems like the more I learn the less I know. :D

EDIT: Never mind, I am building straight AOSPA and you guys are doing something else. :D Tired and sleepy, time for a break and maybe a new project.
[Gen9 Android Development] Quallenauge:
Hi stevemp!

I'm using the backports packages from compat-drivers-3.8-rc7-1.tar.xz for the WLAN modules. Newer ones (3.9.2) does not work currently.
[Gen9 Android Development] freezenook:
Can you make post with all modules and addons and fixes?
[Gen9 Android Development] stevemp:
changes

WIP, every day something new. :)

Code for the camera is already in the kernel, don't have to add any thing.

arch/arm/mach-omap2/archos-camera-mt9m114.c
[Gen9 Android Development] Quallenauge:
Bluetooth (not yet working)

Hi there!

Yesterday I tried to include the hardware/ti/wpan makefile tree to build up the libbt-vendor lib. It seems that it tries to initialize, but due the missing

/dev/hci_tty node it was not successful. Then I added an entry in uevent.archos.rc

# for Bluetooth
/dev/hci_tty 0666 root root

Next step was to integrate the new driver module hci_tty from the omapzoom kernel inside the st_ti package.

It loads up, initializes the firmware but then it comes to timeouts while initializing ldisc device?! (What's this?)

So bluetooth is not working yet.... but if someone give me some hints....

(Logfile will be attached later to this post, if some one cares about =) )

Edit: Here the logfile: http://pastebin.com/irzuRtrY

Note this:

I/cat ( 626): <6>[ 6.523468] init: Try to execute command 'insmod' with params '/system/lib/modules/btwilink.ko'.
I/cat ( 626): <6>[ 6.524047] Bluetooth: Bluetooth Driver for TI WiLink - Version 1.0
I/cat ( 626): <6>[ 6.525115] init: command 'insmod' r=0
I/cat ( 626): <6>[ 6.525238] init: Try to execute command 'chmod' with params '0777' '/dev/hci_tty'.
I/cat ( 626): <6>[ 6.525329] (hci_tty): inside hci_tty_open (eee75748, eed71900)
I/cat ( 626): <6>[ 6.525817] (stc): st_register(4)
I/cat ( 626): <6>[ 6.525878] (stc): chnl_id list empty :4
I/cat ( 626): <6>[ 6.525939] (stk) : st_kim_start
I/cat ( 626): <6>[ 6.526031] plat_kim_chip_enable
I/cat ( 626): <6>[ 6.526580] (stc): st_register(2)
I/cat ( 626): <6>[ 6.526641] (stc): ST_REG_IN_PROGRESS:2
I/cat ( 626): <6>[ 6.526733] (stc): add_channel_to_table: id 2
I/cat ( 626): <6>[ 6.635894] (stk) :ldisc_install = 1
I/cat ( 626): <3>[ 7.636047] (stk) :ldisc installation timeout
I/cat ( 626): <6>[ 7.636657] (stk) :ldisc_install = 0
....
I/cat ( 626): <6>[ 28.801422] (stk) :ldisc_install = 0
I/cat ( 626): <3>[ 29.800872] (stk) : timed out waiting for ldisc to be un-installed
I/cat ( 626): <6>[ 29.802978] plat_kim_chip_disable
I/cat ( 626): <6>[ 29.803588] plat_kim_chip_enable
I/cat ( 626): <6>[ 29.918090] (stk) :ldisc_install = 1
I/cat ( 626): <3>[ 30.918121] (stk) :ldisc installation timeout
I/cat ( 626): <6>[ 30.918701] (stk) :ldisc_install = 0
I/cat ( 626): <3>[ 31.918121] (stk) : timed out waiting for ldisc to be un-installed
I/cat ( 626): <6>[ 31.920227] plat_kim_chip_disable
I/cat ( 626): <3>[ 31.920867] (hci_tty): st_register failed -22

This may the reason why the libbt-vendor stack can't connect to /dev/hci_tty:

I/bluedroid( 1339): enable
I/bt_hci_bdroid( 1339): init
I/ ( 1339): vendor Init
I/ ( 1339): vendor op - 5
I/ ( 1339): vendor op - 0
I/ ( 1339): vendor op - 0
I/GKI_LINUX( 1339): gki_task_entry: gki_task_entry task_id=0 [BTU] starting
I/bt_hci_bdroid( 1339): bt_hc_worker_thread started
I/ ( 1339): vendor op - 3
E/ ( 1339): Can't open hci_tty
E/bt_userial( 1339): userial_open: wrong numbers of open fd in vendor lib [-1]!
E/bt_userial( 1339): userial_open: HCI UART expects only one open fd

Strange, it seems, that the modules load up, if If I insmod them manually later within the adb shell....
[Gen9 Android Development] stevemp:
cm-10.1

Are you building AOSPA or cm? Finished up my cm-9.1 (ICS) project and thinking about working on 4.2.2 again. :rolleyes:
[Gen9 Android Development] Quallenauge:
I'm on the CM10.1 train. But this issue is the same for the current and next android versions, so I posted it here.
[Gen9 Android Development] stevemp:
guide

TI-Android-JB-PortingGuide. What I have been using to understand how things work in JB, hope it helps. :)

http://processors.wiki.ti.com/index.php/TI-Android-JB-PortingGuide
[Gen9 Android Development] trevd:
Personally I've been playing with the omapzoom aosp so it's good to see we've formed a cohesive team all focused on the same goal LOL :laugh:

@Quallenauge.

I've been playing with the blaze tablet build and noticed a couple of things which might help because it sounds like you are close to cracking the bluetooth problem

In ueventd.omap44xxtabletboard.rc the hci_tty is defined as follows

/dev/hci_tty 0666 bluetooth bluetooth

also the init.rc creates a bluedroid directory,which we've never had to do in the archos inits.

mkdir /data/misc/bluedroid 0770 bluetooth net_bt_stack

Thanks
[Gen9 Android Development] solrakk6:
so now just need bluethoot and we have a aosp for flash on our g9?! thx for your support
[Gen9 Android Development] Quallenauge:
Bluetooth is working! (Partly... =)

Hi Trevd!

Thanks for the motivation and the hints! And yes, I get it running as prototype!

First of all, this post was very interesting: Bluetooth not coming up

It says, that the uim-sysfs daemon has to be running, in front when the modules should be intializing.

That was also the main problem! But back to start:

Added hardware/ti/wpan packages to the build system and included them into the archos device build files.

Added the hci_tty.c driver and the whole ti_st from current omapzoom kernel. (Changes are available inside my repo).

The daemon uim-sysfs is located at the wpan package. I included them, but doesn't realize, that I'm using the prebuilded one of the archos stock rom.

Loaded the following modules on boot (which comes mostly from the backports package):

# bluetooth
insmod /system/lib/modules/compat.ko
insmod /system/lib/modules/bluetooth/bluetooth.ko
insmod /system/lib/modules/bluetooth/rfcomm.ko
insmod /system/lib/modules/bluetooth/hidp.ko
insmod /system/lib/modules/bluetooth/hci_uart.ko
insmod /system/lib/modules/bluetooth/bnep.ko
insmod /system/lib/modules/tty_hci.ko

Added one script which loads the btwilink.ko module:

root@android:/ # cat /system/bin/load_bt-module
#!/bin/sh
umask 000
/system/bin/insmod /system/lib/modules/bluetooth/btwilink.ko

and started this as service (with oneshot option) after the uim-sysfs daemon:

service uim-module /system/bin/load_bt-module
class core
oneshot
user root
group bluetooth net_bt_admin

The uevent.archos.rc seems to completely useless. Moving the bluetooth definition of /dev/hci_tty to the uevent.rc was needed, to change the permissions to the right ones.

As result of these actions, the firmware is loaded and the libbt-vendor lib is able to connect to the bluetooth chip (which communicates over the internal UART ports).

First, I'm happy because it works with small effort with our tablet. But it's weird to load the btwilink.ko module in a separate service. Why we can't load the module later? Maybe there is an option for the module, which initializes only after uim-sysfs is started? Any ideas?
[Gen9 Android Development] trevd:
Ahhh, I thought you knew, otherwise I'd of mentioned it, :o The ueventd.archos.rc will be useless because normal ueventd looks for the ueventd.{ro.hardware}.rc so it will be looking for ueventd.archosa80sboard.rc . I had a ueventd.*.rc for each hardware type supported by the rom A101S , A101H, A80S and A80H but It's not required really as all the files were the same, hence archos having a generic "archos.rc". As you probably noticed the ueventd.rc in you last CM build 0.0.0.5 has the contents of ueventd.archos.rc catted to the end

Your way out in front on the bluedroid knowledge so there's nothing i can suggest there, but here's some more interesting stuff from init.omap44xxtabletboard.rc

at the end of post-fs-data

#for Bluetooth HID
chmod 0666 /dev/uhid

# change permissions for Bluetooth/FM/GPS
chmod 0600 /sys/class/rfkill/rfkill0/state
chown bluetooth bluetooth /sys/class/rfkill/rfkill0/state
chmod 0600 /dev/ttyO1
chown bluetooth bluetooth /dev/ttyO1

I've gotta get my tablet into a booting state before I can look into it further.

EDIT: android.hardware.bluetooth.xml needs adding to permissions although that doesn't effect native services ( I don't think )
[Gen9 Android Development] stevemp:
camera

Just a little info about the camera, archos-camera-mt9m114

device_initcall(archos_camera_mt9m114_init);

Maybe we just need to initalize the camera for it to work?

# Archos OMAP4 products
obj-$(CONFIG_MACH_ARCHOS_A80S)	+= board-archos-a80s.o \
hsmmc.o \
omap_phy_internal.o \
archos-lcd-cpt-xga8.o \
archos-audio-twl6040.o \
archos-accel-mma8453q.o \
archos-compass.o \
archos-nl5550.o \
archos-touchscreen-tma340.o \
archos-touchscreen-tr16c0-8.o \
archos-camera-mt9m114.o \
omap4_apps_brd_id.o \
archos-usb-musb.o \
archos-usb-ehci.o \
archos-usb-3g-rfkill.o

obj-$(CONFIG_MACH_ARCHOS_A80H)	+= board-archos-a80h.o \
hsmmc.o \
omap_phy_internal.o \
archos-lcd-cpt-xga8.o \
archos-audio-twl6040.o \
archos-accel-mma8453q.o \
archos-compass.o \
archos-nl5550.o \
archos-touchscreen-tma340.o \
archos-touchscreen-tr16c0-8.o \
archos-camera-mt9m114.o \
omap4_apps_brd_id.o \
archos-usb-musb.o \
archos-usb-ehci.o \
archos-usb-3g-rfkill.o \
archos-jm20329.o

obj-$(CONFIG_MACH_ARCHOS_A101S)	+= board-archos-a101s.o \
hsmmc.o \
omap_phy_internal.o \
archos-camera-mt9m114.o \
archos-audio-twl6040.o \
archos-accel-mma8453q.o \
archos-compass.o \
archos-touchscreen-pixcir-10.o \
archos-touchscreen-tr16c0-8.o \
archos-touchscreen-cpt-10.o \
archos-lcd-auo-wxga10.o \
omap4_apps_brd_id.o \
archos-usb-musb.o \
archos-usb-ehci.o \
archos-usb-3g-rfkill.o

obj-$(CONFIG_MACH_ARCHOS_A101H)	+= board-archos-a101h.o \
hsmmc.o \
omap_phy_internal.o \
archos-lcd-auo-wxga10.o \
archos-audio-twl6040.o \
archos-accel-mma8453q.o \
archos-compass.o \
archos-nl5550.o \
archos-touchscreen-tma340.o \
archos-touchscreen-tr16c0-8.o \
archos-touchscreen-cpt-10.o \
archos-camera-mt9m114.o \
omap4_apps_brd_id.o \
archos-usb-musb.o \
archos-usb-ehci.o \
archos-usb-3g-rfkill.o \
archos-jm20329.o

obj-$(CONFIG_MACH_ARCHOS)	+= archos-fixup.o \
archos-battery.o \
archos-leds.o \
archos-memory.o \
archos-die_id.o \
board-archos-identity.o
[Gen9 Android Development] trevd:
Is that a rhetorical question? :D Is it not called in the initialization process. the initialization calls are based on groups ( you probably already knew that ).. or maybe camera_init is called before the ducati firmware/rp_msg drivers have been installed... If the HDMI Framebuffer stuff is anything to go by, who knows what archos have missed out/removed from the gpl kerrnel compared to their internal tree.

For The Love of God, Try It Already! :D LOL
[Gen9 Android Development] merikgvr4:
stuck in archos screen

Please help, I am stuck in the archos screen. I tried to follow the dierctions in the OP but it doesn't work. I tried to adb shell but it shows no device.:(

edit....reformatted and installed stock rom. good for now. almost had a heart attack.
[Gen9 Android Development] stevemp:
sleep needed

Shouldn't post when I'm sleep deprived. :D
[Gen9 Android Development] trevd:
LOL I know the feeling. Here's a Protip for you all. Don't over discharge your battery. ( yes that's a real thing ) I'm sat looking at a Solid Power light and no response at all. After about an hour it start doing the rapid flickering (very low power indicator ) then the light goes out.. I'm thinking at that point I shouldn't unplug it becuase then I get to look at the solid power light for an hour again....

I've not got my bricking boots on today so Normal Service should be resumed shortly..... :D LOL
[Gen9 Android Development] Quinny899:
Protip 2: Don't do it when your USB port is messed up AT ALL. Otherwise it's back to Archos for that device...

Just leave it to charge until it comes on and charges to 100%, preferably overnight
[Gen9 Android Development] Quallenauge:
Protip3: In case no working kernel is installed and the battery is empty, try to hold the Vol- Key to boot into the recovery boot loader menu, which also triggers battery charging. For me, I had to use TESA film, because I don't wanted to hold it for a couple of hours and the tablet was flickering until it had enough power to boot into the recovery.
[Gen9 Android Development] trevd:
Protip 4: if you want to derail a thread start offering Tips :D

My tablet is available again. :highfive: so the real protip 4 is to use a nexus 7 charger because the archos 1 isn't a snug fit!

Still gotta get it boot but I'm still in the Game LOL.
[Gen9 Android Development] jweir:
Question Where is the latest ROM

Hello all

I click the link to download the ROM and it not there..

Could someone post the new link for the ROM

thank
[Gen9 Android Development] pak1to:
join request,reupload mirror link pls
[Gen9 Android Development] Sargeue:
Link DEAD

Please update, repost link to Rom!
[Gen9 Android Development] Quinny899:
Didn't think I had the zip for this one anymore, found it in my downloads (no idea why I downloaded it on my new machine)

Anyway, it's going up:
[Gen9 Android Development] Quinny899:
Upload is complete, download as you like (link in second post)
[Gen9 Android Development] Sargeue:
Thanks, awesome!
[Gen9 Android Development] ophirb:
Hi.

Tried to install the rom as described by the op but got stuck on the first logo.

Yhen I tried to install it as other roms I installed by placing the update file on the root of the internal memory, flashed kernel and iniramfs and rebooted and got stuck on the paranoid boot animation.

What can I do to overcome this problem?
[Gen9 Android Development] stevemp:
This is a jellybean rom, you have to wipe and push archos.ext.update using adb.
[Gen9 Android Development] ophirb:
I tried the above and I get:

rm failed for -rf no such file or directory

When I type rm -rf data/*

Any ideas?
[Gen9 Android Development] stevemp:
Try busybox rm -rf data/*
[Gen9 Android Development] ophirb:
No success.

Any more ideas?
[Gen9 Android Development] stevemp:
It will only work if tablet boots using a rooted custom rom, might have to install a rom first.
[Gen9 Android Development] ophirb:
I have a custom rom installed that is rooted.

I searched the thread some more and found other methods. Every method is different in some ways .

Can someone please give me a step by step tested method of flashing this rom coming from an ICS rooted custom ROM?

Thanks
[Gen9 Android Development] stevemp:
leadtk said this worked for him http://xdaforums.com/showpost.php?p=50412125&postcount=7.
[Gen9 Android Development] ophirb:
Stevemp do I need to rename the update file first?
[Gen9 Android Development] stevemp:
If you push it to/data/local it needs to be named archos.ext4. If you push it to /data/media it needs to be named archos.ext4.update.

The script copies archos.ext4.update to /data/local and renames it archos.ext4, renames archos.ext4.update to archos.ext4.backup. The only reason I see for using archos.ext4.update is you can copy it using windows file manager for updating stock rom.
[Gen9 Android Development] ophirb:
Now I'm a bit confused as in the instructions you post it says to push it to mnt/storage.

So if I push it to mnt/storage do I need to rename it?

Thanks for you patience
[Gen9 Android Development] stevemp:
I tried to install it on my tablet and it is confusing. Rename to archos.ext4 and push to /data/local.

I use Linux and it's much better, mount g9 as drive and copy archos.ext4 to /data/local.
[Gen9 Android Development] ophirb:
Actually I got it to work but could not do anything since it occupied all the ram leaving only 24mb of ram free with nothing installed except for the apps that comes with the rom.

Is this normal?
[Gen9 Android Development] stevemp:
It was an alpha version, hw is not working very well. PA moved on to 4.3.1 and now 4.4.2 which is still not working very well. When PAC-man 4.4.2 is ready for release I might compile it for the g9.
[Gen9 Android Development] emmab2006:
Does anyone have a mirror for this ? keep having issues downloading from the goo ! xx
[Gen9 Android Development] Sargeue:
If you would compile it, I and a few others will be grateful. I will donate also as I did with many other Dev's here for all there hard work! Thx!
[Gen9 Android Development] winstonxl2:
Looks very nice The future of every android device is in the hands of the developers.

Well over about an hour i am going to flash that rom on my tablet for camera and bluetooth i have

my iphone(i got it for a while because i cant use my old lg optimus 2x. before i wil get Htc sensation)

Happy to see that a couple of people can make such an awesome work for a device where are not really rom makers are

Thanks to everybody who is helping on this project:good::p
[Gen9 Android Development] cypressious:
I followed the installation steps and it seems I'm stuck at the Archos logo. I've already waited about half an hour. Any tips?

The other ROMs required some files to be flashed from the recovery menu. Why isn't this the case for PA?
[Gen9 Android Development] julle131:
I was in the same situation. What i did was i booted to recovery and mounted the data partition to my ubuntu pc. Then i removed all files from there (sudo rm -rf *), made media folder again (mkdir media) and moved the image back (mv archos.ext4.update /media/data/media/archos.ext4) and then reinstalled zImage and initramfs from recovery. So iI redid everything after first try, which had resulted in bootloop.

Beucase the rewuired files are flashed directly from the device. Your device won't probably detect the archos.ext4.update. Try flashing initramfs from multiboot menu and zImage from the PA zip. If you can see the archos.ext4.update, i dont know what is wrong, but if you can't then the device is not detecting the image.
[Gen9 Android Development] stevemp:
install

The way I install is to go to format, reset android then export data and mount it. I run thunar as root so go to data and make dir local and then copy archos.ext4 there. You have to rename image because multi-boot only sees files with ext4 extension. The problem I'm having is the multi user issue, not making directory for user and external sdcard, reason for Play Store closing. :rolleyes: It was working before so am going to take a look and see what's wrong. :(

Ok, still need to fix MTP and adb
[Gen9 Android Development] TrOjAnUK:
How do you do that?

Im on linux now but still a n00b to it.. the rest of your way I can understand but not sure how I mount data.***

***OK scrub that, just looked, I can see export data but how do I mount it in Linux??

TrOjAn
[Gen9 Android Development] stevemp:
Linux

I have a dir named temp in my home directory, /home/smp/temp

My computer auto mounts data when I plug in the usb cable (xubuntu 12.10). Thunar is the file manager in xubuntu so open a terminal and type in sudo thunar yourpassword to be root. Go to /media/data/local, right click on desktop, open terminal (root) and type in mount archos.ext4 /home/smp/temp

Might have to click on view reload in menu at top tool bar in thunar to see files. archos.ext4 will be mounted as a drive, change whatever you want, go back to terminal open in local, type sync to be sure all changes are written to archos.ext4 image, type umount /home/smp/temp, close terminal and reboot G9. Of course use your name instead of smp. :) Google linux mount ext4 image for more info, lot of sites to read about linux commands. :)
[Gen9 Android Development] TrOjAnUK:
Thanks for the explanation, I do appreciate it... for some reason my archos dont mount on Linux Mint.

Ill need to look at it a bit more but at least I now have a start place.. thanks, TrOjAn