yashsingh1/xdaforums huggingface dataset:
[Gen9 Android Development] stevemp:
I'm back with ParanoidAndroid too, found out why it wouldn't build last time. They had removed support for mdpi, so got it from ICS version and it builds but now having problems with tool chains and TIWLAN_MODULES not building, get error about mismatch with kernel. Guess I need to update to 3.0 and try again. :)
[Gen9 Android Development] Quinny899:
Re: [VOTE IN POLL PLEASE!][DEV][4.2][16/1/13] CyanogenMod 10.1

It's a start :)

Aaand that's as far as it gets. No PA from me for now guys
[Gen9 Android Development] Quinny899:
So I need to symlink hwcomposer.omap4460.so to hwcomposer.omap4.so ?
[Gen9 Android Development] stevemp:
link

system/vendor/lib/hw

rm gralloc.archos.so

ln -s gralloc.omap4460.so gralloc.archos.so

Worked for me. :)
[Gen9 Android Development] stevemp:
I was having problems too, easy work around is to add this to BoardConfig.mk :)

# use toolchain 4.4.3 for kernel compile

TARGET_KERNEL_CUSTOM_TOOLCHAIN := arm-eabi-4.4.3
[Gen9 Android Development] Quinny899:
Nope. Still same error. My device won't boot at all with the new kernel though, stuck at Archos screen D:
[Gen9 Android Development] Quallenauge:
Quinny,

can you please provide a complete boot log? Also perform an lsmod show us the output.

It has to work! ;) gralloc4430.so and gralloc4460.so should be the same files.

They are pushed by the TI or PVR team for compatibility reasons.

The archos/ti/hwcomposer is not used - we use the default hwcomposer for the archos, which is not the fastest....
[Gen9 Android Development] stevemp:
I did a complete wipe and reinstalled, booted fine. Must have forgotten to install new kernel the first time. :o
[Gen9 Android Development] pmartin:
Archos 101 G9 UMTS

Hello!

Did the Surf-Stick (Archos) work with the new cyanogenmod?

Regards
[Gen9 Android Development] cajl:
impossible to Extract the zImage and initramfs to /data/

permission denied ...

Ok i flashing with the SDE option and now i reboot on Developper Edition

The CM animation running.... but how many time ?
[Gen9 Android Development] Quinny899:
Re: [DEV][4.2][16/1/13] CyanogenMod 10.1

Did you wipe Android first?
[Gen9 Android Development] cajl:
How to do wipe ?
[Gen9 Android Development] Quinny899:
Re-push the ext4.update file, then power off, and power on whilst holding volume down. Then go to Recovery > Format System > Reset Android. Then reboot.
[Gen9 Android Development] down4life:
Hello, have a little problem :D Tried to flash this rom, but stuck on archos splash screen ( my mistake, didnt run zimage and init from emulator).

Ive tried to go back on stock by reflashing firmware firmware_archos_it4 from recovery, but Im getting error 221. Help, please :)

edit:download firmware from archos site.
[Gen9 Android Development] Quinny899:
Re: [DEV][4.2][16/1/13] CyanogenMod 10.1

You can flash the initramfs and zImage in recovery, in Developer Edition > Flash kernel & initramfs
[Gen9 Android Development] down4life:
Did it, thank you, tired to type commands in terminal, but no luck... wil recheck everything :) (re:install)
[Gen9 Android Development] Quinny899:
Re: [DEV][4.2][16/1/13] CyanogenMod 10.1

You don't use the terminal, it will appear as a drive, just copy the two files to there and hit power on the device
[Gen9 Android Development] down4life:
Thanks for paitence :) Copied archos.ext4 file, rebooted in recovery, format android, removed android kernel, flash new ones, reboot, and im stuck on archos splash screen?

Did I miss something? Thanks
[Gen9 Android Development] muti642:
10.1

no format android just reset android in menu format android ;)

---------- Post added at 01:02 PM ---------- Previous post was at 01:00 PM ----------

i need good ext4 and good zimage and initramfs for test 10.1 installation thx for good link to dl good version and kernel
[Gen9 Android Development] solrakk6:
Re: [DEV][4.2][16/1/13] CyanogenMod 10.1

deleted
[Gen9 Android Development] Quinny899:
So yesterday Stevemp sent me an early alpha of ParanoidAndroid that he built, based on 3.00

I pushed some libs to get stuff working, still trying stuff now

What works:

All the PA stuff I've tried so far, including the tablet UI in 4.2

WiFi

Sound

Video (HQ & LQ)

Internal Storage

SD Card

USB OTG via MicroUSB port

Voice

What doesn't work/is buggy

The navbar/bit at the bottom is cropped (might just be a dimension/dpi issue) Setting it to 130% by force in Paranoid Properties solves this, included by default

Back OTG port (Mine is broken maybe, might need testing)

It's a bit laggy
[Gen9 Android Development] ergoen:
In case you have got the pvr working correctly please ignore this, but otherwise, have you seen

https://github.com/CyanogenMod/android_device_samsung_omap4-common ? there seems to be some nice code working for other omap4-devices for cm10.1.
[Gen9 Android Development] cajl:
i "wipe" the 8" and .....

-The reboot in Dev mode OK

-The animation Cm is very very long.....
[Gen9 Android Development] freezenook:
What about build with fixed storage, but bricked camera and voice search?
[Gen9 Android Development] Quallenauge:
Updated image

Hi!

I've uploaded my current working snapshot of the Archos CM10.1 port:

CM10.1 - Version 0.0.7

Major changes of the last snapshot are:

Bluetooth support (not really tested).

uim-sysfs was modified to load up the btwilink.ko kernel module from /system/lib/modules/bluetooth folder. (Default was to load from "/" (root folder)). Bluetooth drivers where used from the linux backports package.

Omapzoom HWComposer modified software vsync routines, copied from Hashcodes (Thanks!) implementation.

Kernel modified to use ti_st drivers from current omapzoom kernel.

Kernel config updated to allow ipv6. With this option, the interface doesn't crash when showing traffic stats panel.

Important note: Only for archosa80sboard!!! Other ones will not boot! If someone would try that on another board, try to modify vold and uevent.*.rc and init.*.rc files. Also, keep this in mind: It's an alpha version (But for me it works).
[Gen9 Android Development] trevd:
Nice one. D/Ling now before all the Kids start DDOSing 4shared :) All your modules are in /system/lib/modules ? Well they were previously. It was fairly easy to split this up into a boot and system I think i'll have a go at that today now that my tab is alive :good:
[Gen9 Android Development] Quallenauge:
Oh, I remember the last time :)

Yes...at least, they where loaded from there. Maybe I should start spring-cleaning and remove some unneeded files...but I'm too lazy :o Split up should be very easy! Also the firmware is loaded from /system/etc/firmware folder.

Keep in mind that if you want to build the image by yourself, you can use my build environment and my sources (You already know that...) which are hosted on github.

I'm looking forward for the new archos device layout =)
[Gen9 Android Development] Quinny899:
So what is used to load Bluetooth? I'll try to port it across to PA if I have some time between this damned Latin revision D:
[Gen9 Android Development] freezenook:
Quallenauge what about Storage works?
[Gen9 Android Development] Quallenauge:
I'm not shure if my kernel is needed. But try to

Insmod the hci_tty driver (located in /system/lib/modules/) to provide the needed device node for the libbt-vendor.

Add bluetooth permissions in uevent.*.rc

Use /vendor/lib/libbt-vendor.so.

Use only my provided (wireless/bluetooth) modules or only the ones inside the /system/lib/modules/bluetooth directory.

If you choose the latter, be sure to use also the compat.ko driver. Take a look inside the init.archos_init.rc file, where I insmodded these driver modules.

Make sure that the modules are not writable, because init would be refused to load "unsecure" modules.

Place the bluetooth firmware TIInit_7.2.31.bts into /system/etc/firmware.

Use my uim-sysfs binary, which loads the btwilink.ko module from /system/lib/modules.

As a sidenode: Bluetooth seems to work, I uploaded some files from my phone... (Yeah!).

---------- Post added at 01:03 PM ---------- Previous post was at 12:59 PM ----------

Yes...I thought it worked since my provided version 0.0.5 (http://xdaforums.com/showpost.php?p=37750911&postcount=110) ....

Oh, I saw, that you asked for...sorry for the late answer, but storage works (for me :) ) (Internal memory and external sdcard).
[Gen9 Android Development] Quinny899:
I'll try and get it working on PA then.

In other news, this new Firefox download panel is nice :)
[Gen9 Android Development] Quallenauge:
Quinny, I clicked on the "Show All Downloads" button, but nothing happens. :p

[Offtopic] But, yes the new interface is really interesting, but It has a disadvantage if you close the window...the download will be stopped, with no confirmation dialog (at least on my installation).
[Gen9 Android Development] trevd:
Halpz Plzzzzzzz, My Tablet is Bricked.

Actually that statement is quite believable coming from me :D It's still working. @Quallenauge Your kernel doesn't want to boot :( Probably my dodgy partition layout tho.....
[Gen9 Android Development] freezenook:
Can you load in recovery? If yes, you should reformat and flash official FW with use *.aos file.
[Gen9 Android Development] Quallenauge:
Does the stock kernel boots up?
[Gen9 Android Development] trevd:
My Kernel boots which is your kernel with my config and CWM in the kernel ramdisk. I'll just merge your bluetooth changes in and rebuild it and use that.
[Gen9 Android Development] trevd:
When I Say boots, I got it loading CWM by default off a coldstart, It loads that.

EDIT: Weird It let me reply to my own post. It normally just tacks it on the end.
[Gen9 Android Development] Quallenauge:
CM10.1 Linaro build

Hi there,

just to be short: ...and if someone want to try out the last version, compiled with the linaro compiler...here it is:

Version 0.0.8

Mainly the compile process was successfull by using the LOCAL_CFLAGS="-fno-strict-aliasing".

(By using the source files provided by linaro there where remaining compile errors... So I modfied mainly the Android.mk files.)

The build was mainly inspired by this thread:

[ROM][4.2.2 | CM10.1][APR 8] LINARO-BEAN + Linaro/Bionic Unofficial Nightlies+OTA

So big, big thanks to tackleberry_crash !!!!
[Gen9 Android Development] edeharo:
Hi Quallenauge, this build works in archos 101G9?

thanks for your hard work
[Gen9 Android Development] Quallenauge:
Unfortunately not, because I don't own that device. But it should be not difficult to enable this build for the 101G9.

I think only the init.A101S.rc file should be moved to the root folder and must be renamed to init.archosa101sboard.rc (If I remember correctly).

In the archosa101sboard take a look at the sdcard daemon. I think I've modified some settings there (the new sdcard daemon takes 2 arguments).

(This must be done on the archos.ext4.update image before updating....).

If I have time, I can do that for the next release, but I can't test this...And without proper logfiles, I'm afraid I can't do anyting if the build doesn't boot.

Maybe we have to wait for trevd, which consolidates the init files.
[Gen9 Android Development] stealthdave:
Just tried installing this on my G9 80S with OMAP4430 and 512MB of RAM, and all I get is a blank screen. :( I wiped data (aka "Reset Android") and installed the kernel both through the Developer Menu and using the PA installation method found here. Is my poor 512MB tablet just too feeble for this ROM?

Thanks!

- Dave
[Gen9 Android Development] Quallenauge:
Camera is basically working!

Hi!

After looking inside the OMX code and to take the kernel messages more seriously, I found out that the clock select rate was given with the wrong multiplier. Maybe archos has choosen a more readable value, which sadly breaks the common definition of TI (Archos engineers wanted to read a rate of 192 instead of 192000000...) See my corrsponding kernel commit for details.

Then I got one step further. Next thing was to load the camera module. But it doesn't wanted to load: http://pastebin.com/7AZ3TJU7.

D/DOMX ( 631): hardware/ti/domx/domx/omx_proxy_common/src/omx_proxy_common.c:1406	__PROXY_SetParameter()
D/DOMX ( 631): ERROR: failed check:(eError == OMX_ErrorNone) || (eError == OMX_ErrorNoMore) - returning error: 0x80001001 - Error returned from OMX API in ducati
D/DOMX ( 631): hardware/ti/domx/omx_proxy_component/omx_camera/src/omx_proxy_camera.c:476	CameraSetParam()
D/DOMX ( 631): ERROR: CameraSetParam: Error in SetParam 0x80001001
E/CameraHal( 631): (40146400) hardware/ti/omap4xxx/camera/OMXCameraAdapter/OMXCameraAdapter.cpp:4320 fetchCapabiltiesForMode - Error while configuring camera mode in CameraAdapter_Capabilities 0x80001001
D/dalvikvm( 629): Added shared lib libjavacore.so 0x0
E/CameraHal( 631): (40146400) hardware/ti/omap4xxx/camera/BaseCameraAdapter.cpp:2681 CameraAdapter_Capabilities - supportedCameras= 0
E/CameraHal( 631): (40146400) hardware/ti/omap4xxx/camera/CameraProperties.cpp:108 loadProperties - camera busy. properties not loaded. num_cameras = 0
E/CameraHal( 631): (40146400) hardware/ti/omap4xxx/camera/CameraHal_Module.cpp:770 camera_get_number_of_cameras - Unable to create or initialize CameraProperties

After enabling some debug output (see my Boardconfig for details) it turns out, that the cpcam was the bad guy. After disabling it,

by using a dedicated #ifdef the camera module comes up and was usable from an app, which uses the camera module. - Btw. Where's the camera app?

Update: Currently we use the sensor config from S5K4E1GA, because of the same sensor id 305. Another glitch is the last output

D/DOMX ( 642): hardware/ti/domx/domx/omx_proxy_common/src/omx_proxy_common.c:1671 __PROXY_SetConfig()
D/DOMX ( 642): ERROR: failed check:(eError == OMX_ErrorNone) || (eError == OMX_ErrorNoMore) - returning error: 0x80001009 - Error returned from OMX API in ducati

which will tell us: Hey, clean up your stuff!

For those who want to test it, here is the image (compiled with the linaro toolchain method of 0.0.8): 0.0.9.

Btw. Can someone explain me, how to enable tethering in my overlay folder?

---------- Post added at 11:10 PM ---------- Previous post was at 10:57 PM ----------

If no archos logo appears, then the kernel can't initialize the initramfs image. So there is something, which blocks the kernel initializing. Such errors are very difficult to solve. Due the fact, I own a 1GByte model I'm not able to see what's going wrong there.

@Quinny, do you own a 512MByte version of the tablet?
[Gen9 Android Development] surdu_petru:
Hello !

For your device, you can check these useful sources on github !

If you have the last repo for CM10.1 just take a look in device/motorola/omap4-common !

Also you can take a look here CM10.1 kernel for omap4-common ! and device !

- sure you will find how to enable usb, wifi & bluetooth tethering !

( is the same platform - omap4 ! )

Good luck !
[Gen9 Android Development] stevemp:
log

Good job on this. :good:

I have a 512 MB version and here is where it freezes on boot.

I/DEBUG ( 492): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 492): Build fingerprint: 'Android/cm_archos_g9/archos_g9:4.2.2/JDQ39/eng.mueller.20130411.222722:userdebug/test-keys'
I/DEBUG ( 492): Revision: '5'
I/DEBUG ( 492): pid: 493, tid: 628, name: SurfaceFlinger >>> /system/bin/surfaceflinger <<<
I/DEBUG ( 492): signal 8 (SIGFPE), code -6 (?), fault addr 000001ed
I/cat ( 486): <6>[ 13.399475] PVR_K:(Error): PVRSRVOpenDCDeviceKM: no devnode matching index 0 [0, ]

config.xml from blaze tablet for tethering.

<!-- List of regexpressions describing the interface (if any) that represent tetherable
USB interfaces. If the device doesn't want to support tething over USB this should
be empty. An example would be "usb.*" -->
<string-array translatable="false" name="config_tether_usb_regexs">
<item>"rndis0"</item>
</string-array>

<!-- List of regexpressions describing the interface (if any) that represent tetherable
Wifi interfaces. If the device doesn't want to support tethering over Wifi this
should be empty. An example would be "softap.*" -->
<string-array translatable="false" name="config_tether_wifi_regexs">
<item>"wlan\\d"</item>
</string-array>

<!-- List of regexpressions describing the interface (if any) that represent tetherable
bluetooth interfaces. If the device doesn't want to support tethering over bluetooth this
should be empty. -->
<string-array translatable="false" name="config_tether_bluetooth_regexs">
<item>"bnep\\d"</item>
</string-array>
[Gen9 Android Development] Quallenauge:
Thanks for the hints with tethering!!! I will try that out soon :) !

@stevemp

Can you please provide a complete logcat log? Maybe there's some output before the surfaceflinger dies....

Also what is worth to try out: Can you try the pvrsrvkm.ko module from 0.0.7 (and when this not works the kernel from 0.0.7)? Maybe there is an incompatibility, when compiling with the linaro toolchain.
[Gen9 Android Development] stevemp:
log 0.0.9

0.0.7 doesn't boot either so probably not the linaro toolchain. Here's the log from 0.0.9.

http://pastebin.com/XK9ZJSP6
[Gen9 Android Development] Quallenauge:
Stevemp, does deactivating the hwcomposer help? (Just rename it to hwcomposer.so.bak - then the default android composer should start).

Also you can do the following:

At init.rc comment out surfaceflinger service:

#service surfaceflinger /system/bin/surfaceflinger
# class main
# user system
# group graphics
# onrestart restart zygote

Then check whats done when pvrsrvinit is initialized.

After that, start the /system/bin/surfaceflinger manually. Maybe it is a concurrency problem. Let me see please the logfile.

The crash output is also existent on my installation, but it's more an info at my system. I've to tweak the hwcomposer sw_init routines a little bit.

@All: As a side node, does an other kernel/system from me boots up for 512MByte 4430 devices - at least shows up the bootanimation?
[Gen9 Android Development] stevemp:
freeze

0.0.5 works fine. Newer ones freeze at boot animation. Renaming hwcomposer and commenting out surfaceflinger service had no effect. I get not much from kmsg.

6>[ 6762](t) eoecanlfo_al:i
6[ 1.674 sc:rmv_hne_rmtbe d2<> 6768](t) eoecanlfo_al:i
6[ 1.674 sc: l hlisurgsee
6[ 1.685 sk licisal=0<> 6775](t) ttycoe<> 6789]pa_i_hpdsbe

I have a 4460 with 512 MB ram.
[Gen9 Android Development] Quallenauge:
Hm, after that version, I used the graphics subsystem from TI inside the kernel, maybe it's really an kernel issue.....

At first, the archos logo appears? (Then the basic display subsystem is working).
[Gen9 Android Development] stevemp:
boot

I get the cm boot animation for about ten seconds, then freezes up. No output from logcat and adb quits working also, seems like the kernel to me.
[Gen9 Android Development] Quallenauge:
:(

So we have do modify the kernel module and find out why the device ID was not added.

Can you add some debug statements in

./sgx_src/eurasia_km/services4/srvkm/common/deviceclass.c in function

static PVRSRV_ERROR PVRSRVRegisterDCDeviceKM (PVRSRV_DC_SRV2DISP_KMJTABLE *psFuncTable, IMG_UINT32 *pui32DeviceID)

like this:

PVR_DPF((PVR_DBG_ERROR,"PVRSRVRegisterBCDeviceKM: Registered device node %s!", pui32DeviceID));
/* and finally insert the device into the dev-list */
List_PVRSRV_DEVICE_NODE_Insert(&psSysData->psDeviceNodeList, psDeviceNode);

Maybe you can enable some more logging at this. Then we should get an appropriate output.

It may be also worth to compare the omaplfb provided by archos (gitorios-repo) with that in my kernel.
[Gen9 Android Development] Quallenauge:
OmapLFB Output

Sorry that didn't work, it is intended only for future use.

static int debug;
module_param(debug, int, 0644); /* For future use */

We have to enable it via #define macro at the file drivers/video/omap2/omaplfb/omaplfb_linux.c :

#define DEBUG
[Gen9 Android Development] stevemp:
Commented out wlan and bluetooth and here is the output from dmesg from error till it freezes.

<6>[ 36.532958] PVR_K:(Error): PVRSRVOpenDCDeviceKM: no devnode matching index 0 [0, ]
<3>[ 36.661834] tiler_alloc_block_area: Tiler FMT: 3, Width: 12193280, Height: 1
<7>[ 36.712799] panel_disable [xga8]
<4>[ 36.712799] misc dsscomp: [dd702000] ignoring set failure -22
<6>[ 36.712829] cannot apply mgr(lcd2) on inactive device
<3>[ 36.712860] misc dsscomp: failed while applying mgr[2] r:-19
<3>[ 36.739318] tiler_alloc_block_area: Tiler FMT: 3, Width: 4096, Height: 1
<7>[ 36.776733] panel_enable [xga8]
<3>[ 36.813934] tiler_alloc_block_area: Tiler FMT: 3, Width: 4096, Height: 1
<3>[ 36.836547] tiler_alloc_block_area: Tiler FMT: 3, Width: 5039360, Height: 1
<3>[ 36.918731] tiler_alloc_block_area: Tiler FMT: 3, Width: 4096, Height: 1
<3>[ 37.007781] tiler_alloc_block_area: Tiler FMT: 3, Width: 4096, Height: 1
<3>[ 37.054718] tiler_alloc_block_area: Tiler FMT: 3, Width: 12193280, Height: 1
<3>[ 37.123077] tiler_alloc_block_area: Tiler FMT: 3, Width: 4096, Height: 1
<3>[ 37.198303] tiler_alloc_block_area: Tiler FMT: 3, Width: 4096, Height: 1
<3>[ 37.220611] tiler_alloc_block_area: Tiler FMT: 3, Width: 5039360, Height: 1
<3>[ 37.278656] tiler_alloc_block_area: Tiler FMT: 3, Width: 4096, Height: 1
<3>[ 37.363342] tiler_alloc_block_area: Tiler FMT: 3, Width: 4096, Height: 1sm
[Gen9 Android Development] Quallenauge:
Another debugging idea

Hm, that doesn't really helps to find the cause :(

I have another idea:

Can you insert the follwing command inside the init.archos_init.rc file?

on init
[B] # Enable watchdog configuration
setprop ro.board.cpu_type OMAP4460 [/B]

# log "On init in archos_init..."
....

And then also re-enable the watchdog daemon service a few lines below:

service watchdog_daemon /system/bin/watchdog_daemon
class core
user root
group root
critical

(I had disabled it, because at the time of modifying the init scripts/rewrote the init binary, I don't know to enable this daemon - I was missing the setprop command).

Then, after the freeze you have to wait ~60Seconds and then the device should be reboot automatically. Then you should be hammering

adb shell cat /proc/kmsg

at the console before the device is freezing again.

(Or did you mean that kernel message buffer in post

)?

Maybe the kmsg is better filled in case the watchdog was initialized in the right manner.