yashsingh1/xdaforums huggingface dataset:
[Gen9 Android Development] trevd:
Okay Folks.

I've push my sources to https://github.com/trevd/Archos-G9, This includes a modified hotplugd service which check for dongles which are already on start up.

I had a quick go with the Voice Dialing. I managed to place a call using a Huawei 1752Cu. I got my mobile answer phone (it was off at the time :) ) and I left a silent message.... I think enabling Voice is do-able whether it's worth the effort is another think altogether - It may be a fun "Hack".

I'll put together a "dirty-zip" update or something very soon for the non-dev types... :good: But right now I'm off to bed!
[Gen9 Android Development] wheresJClighting:
+1 for stuttering on screen changes. Planning on swapping to oc rom until cm9 stabilizes. I have it in my arc s and its pretty far along there. Lost panoramic pics tho...
[Gen9 Android Development] scholbert:
First of all thanks a lot for the impressive work you've done so far!

Have you read about letama increasing 3rd partition for root tree by using CWM?

I think this is the way to go... though it's little dangerous and might cause some bricks.

At least bricks would be recoverable by using u-boot :D

Fantastic work!!!

Sound like a real cool hack... thanks a lot for that so far!

Not 100% sure, but AFAIK the modem firmware is the limit for voice calls.

It's nice that the Huawei is supporting calls, but i guess the Archos 3G won't work in this mode...

Anyway, i love this kind of hacking ;)

Cheers,

scholbert
[Gen9 Android Development] Quallenauge:
Thanks for your great work!

I tried it out, but I don't get a connect with my archos stick :( Any idea what I'm doing wrong (Log attached) ?

Is it possible to show the "3G-Modem" radio buttons at the taskbar settings, like the stock firmware does (I have no clue where to adjust that setting.)?

Also it is possible to turn off the archos usb stick, to save energy in case of not using it?

On stock firmware the USBKey manager was responsible for that. Is it known, how it achieve that?

Many thanks!
[Gen9 Android Development] cajl:
How install the CM9 on Archos Gen9 ?
[Gen9 Android Development] omegaRED7:
Does your carrier require a username/password combo?

Also, if your talking about the notification drawer toggles, you can select what toggles are available, poke around the settings, i don't have my tab with me to tell you where exactly...
[Gen9 Android Development] Quallenauge:
Yes, I adjusted them in the Android APN settings. In my case simyo/simyo where values for user/password.

Yes exactly. I'm glad if you can post the location, if you have time.

Edit: Have found the settings on: System Settings -> System -> Notification Bar.
[Gen9 Android Development] omegaRED7:
Ok, have you previously had problems with e-plus internet? The error code is that the service is temporarily not available... Which, in my layman's understanding of what i've read about GSM error codes, would suggest issues on the carriers side of things. But i'm sure trevd will give a much more qualified explanation.

On a side note: Did you build & flash the whole CM9 again (with trevd's changes)? If possible, please upload the ROM somewhere (or if it's easier just the modified/additional files). I'm setting up my computer for building CM9, but as i'm very new to Linux/Android, it'll take a while before i produce anything usable :S

Regards,
[Gen9 Android Development] Quallenauge:
Internet over 3g stick seems to be okay. I'm verifying it currently over the stock firmware.

Yes I cloned the repository from jackpotclavin and merged the changes from trevd into it. I hope that I do it right, because trevd hasn't updated his repository for a while. Maybe we should wait until jackpotclavin has merged the changes from trevd before releasing a rom. I you have questions about building the cm9, you can contact me per PM. (jackpot clavin has a good&short howto on his readme: https://github.com/JackpotClavin/Archos-G9
[Gen9 Android Development] trevd:
My Tree should be up to date as I did a pull request before I put my changes in last night......Although I'm new to Github so I could have done something wrong :)

Part of USBKey Manager functionality is now managed through the hotplugd native service.

The power management is handled by rfkill which is Software Kill Switches something yet to be implement..... Remember Super Alpha! :D

I included hotplugd as a prebuilt in my build but you grab the code and drop it in the and source tree if you want to hack around, It also needs libusb-1 both are available in my gitthub

https://github.com/trevd/libusb-android
https://github.com/trevd/hotplugd

Just drop them into your cm9 source tree, I've found this very useful and not very well documented for building individual parts of the tree

source build/envsetup.sh
lunch
cd external/libusb # or whatever you want to build
mm

this will build the current directories Android.mk ( apologises if I'm preaching to the choir :) )

With regards conection issues, There a couple of extra property to check when dealing with this stuff as we

adb shell getprop

If you're using the Archos 3G Stick look the following properties should of these values

[ril.pppd_tty]: [ttyHS4]
[rild.libargs]: [-d /dev/ttyHS3]
[rild.libpath]: [/system/lib/libtcl-ril.so]
[init.svc.ril-daemon]: [running]

Also make sure your apn is setup andmanually register on the network through the network operators settings

You can also restart you're radio daemon and try restarting the tablet in case Usb has suspended,

adb shell stop ril-daemon
adb shell start ril-daemon

If you're still having issue grab the full log next time aswell and grab you property list ;)

adb logcat -b radio -b events -b system -b main
adb shell getprop

Check your property list before posting for any personal data

Thanks
[Gen9 Android Development] Shano56:
You flash it like any other rom on the G9
[Gen9 Android Development] JackpotClavin:
I couldn't see the actual files he used to do it. I think he sent them out in a few PMs
[Gen9 Android Development] Quallenauge:
On github, the last changes from jackpotclavin where from 2012-07-08.

Interesting, thanks for explaining it. And yes, I'm aware of the alpha status, and I really like your work! Sadly I personally haven't enough knowledge to help out with hacking the rfkill functionality.

Once this is implemented (or another way to disable the power of the usb stick (without plug out the stick)) I would like testing further CM9. (Only because of the battery drain... )

It seem's that it was really a temporary failure of my provider... :eek: Now it seems to be ok.

That was a really good tip on filtering the logcat output. It turns out, that I must have some errors on merging, because write-secrets where not at the right place. My fault - sorry. After I moved it to the right location (/etc/ppp/write_secrets) it worked. I also had to create an etc symlink to /system/etc for ppp.

Thanks for your work! :cyclops:

Edit: Will use cyanogen mod because after googling around I found out how to disable the usb stick via:

echo "0" >/sys/class/rfkill/rfkill0/state
[Gen9 Android Development] letama:
Hi JackpotClavin,

I'm sending you a PM with the link, check my post for the how-to. Be careful though, I still consider this dangerous even though many did it successfully.

You can also unpack the cpio and take a look at the way I launch cwm with a separate init if you want... Feel free to re-use whatever you want. The recovery is nearly functional, erase data / erase dalvik-cache need extra work.

If you need anything, let me know!

Cheers,

LeTama
[Gen9 Android Development] tdefiant:
USB stick update.zip

Hello Trevd,

first of all thank you and JackpotClavin for the awesome work you guys are doing.. :good:

Then on the ""dirty-zip" update" issue: you had time to put it together?

I'm one of those "non-dev" types who'd be v/grateful for it as I also have a HUAWEY stick

I (we)'ll be waiting eagerly!

Tdef
[Gen9 Android Development] Rmaier14:
interested to test CM9

hi JackpotClavin, sorry for my english,

my device (G9 101, OMAP4460 ES1.1 1,5GHz, 1GB Ram, 250GB HDD)

is ready to test, at this time ICS@Blue_V03 is installed.

Regards, Rmaier14
[Gen9 Android Development] omegaRED7:
You can already test it, everything works as it should, I haven't noticed any significant bugs. Although you might take a look at this post by nicktastique about the issues with the HDD version. I don't know if those issues were addressed in the second build by JackpotClavin.
[Gen9 Android Development] nicktastique:
I use an init script to set the HDD spin-down timeout at boot. Put the following in /system/etc/init.d/99hdd:

#!/system/bin/sh

echo 120000 >/sys/devices/platform/jm20329/timeout

If you spend a lot of time on battery power, you might want to set it to 60000 ms instead of 120000 ms. Of course, you'll have to recreate this file each time you install a new filesystem image.

In other news, I'm having a few issues which could be related to my tinkering with the image. I need to wipe and test with JackpotClavin's build, but here's what I'm seeing if anyone can confirm.

If the USB cable is plugged in at boot, /mnt/storage is not mounted.

When I try to shutdown or reboot, the system image on loop0 is remounted read-only, and the device must be power-cycled.

Things that access volume state via MountService, like android.process.media and Settings -> Storage are asking for state on /mnt/sdcard instead of /mnt/storage, which makes them crash with the following exception (this one is from Settings, but android.process.media is similar):

W/MountService( 686): getVolumeState(/mnt/sdcard): Unknown volume
E/AndroidRuntime( 836): FATAL EXCEPTION: main
E/AndroidRuntime( 836): java.lang.IllegalArgumentException
E/AndroidRuntime( 836):	at android.os.Parcel.readException(Parcel.java:1331)
E/AndroidRuntime( 836):	at android.os.Parcel.readException(Parcel.java:1281)
E/AndroidRuntime( 836):	at android.os.storage.IMountService$Stub$Proxy.getVolumeState(IMountService.java:241)
E/AndroidRuntime( 836):	at android.os.storage.StorageManager.getVolumeState(StorageManager.java:538)
E/AndroidRuntime( 836):	at com.android.settings.deviceinfo.StorageVolumePreferenceCategory.updatePreferencesFromState(StorageVolumePreferenceCategory.java:244)
E/AndroidRuntime( 836):	at com.android.settings.deviceinfo.StorageVolumePreferenceCategory.updateApproximate(StorageVolumePreferenceCategory.java:301)
E/AndroidRuntime( 836):	at com.android.settings.deviceinfo.StorageVolumePreferenceCategory$1.handleMessage(StorageVolumePreferenceCategory.java:140)
E/AndroidRuntime( 836):	at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 836):	at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 836):	at android.app.ActivityThread.main(ActivityThread.java:4575)
E/AndroidRuntime( 836):	at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 836):	at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 836):	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:789)
E/AndroidRuntime( 836):	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:556)
E/AndroidRuntime( 836):	at dalvik.system.NativeStart.main(Native Method)

In other news, builds from current CM9 git do not boot for me since Monday or so with either of the available device trees.

Again, this might all be due to me breaking something. Please speak up if you have had similar experiences. Otherwise, don't worry about it.
[Gen9 Android Development] Quinny899:
Sorry to boycot our CM9 thread, but have you tried compiling a CM10 ROM JackpotClavin?
[Gen9 Android Development] trevd:
Now then Folks,

Here's a "very dirty zip" for updating to 3g support

3g-archos-g9-3_0_8_plus.zip

It contains a system folder and couple of files require in the root folder, main updates are in /system/etc /system/framework /system/app and /system/bin and /system/xbin ( for chat ).

you might have to chmod 6755 /system/bin/pppd if you plan on using a huawei modem/dongle with it but it should be just fine with the archos 3g stick

To update either mount an existing cm9 ext4 and copy the files over the top of the existing ones or if you want to be really dirty from the folder you unzip to

adb push system /system
adb push lib /lib
adb push init.rc /
adb push init.dongle.rc /

This will Force Close pretty much everything but after a reboot everything should be good. :D

Have Fun!
[Gen9 Android Development] Rmaier14:
Bootloop on Archos 101 G9 250 GB HDD

i'm back wit problems,

i have wiped with the adb shell and pushed it to the storage, the rebooted.

The table starts with the Archos Logo and Loop..

What goes wrong, can anyone help me..thanks
[Gen9 Android Development] omegaRED7:
Do you have SDE enabled? If yes, have you deleted everything in your /data/ folder/partition before you pushed the file?
[Gen9 Android Development] Rmaier14:
Bootloop

thanks for your reply, yes i have SDE enabled and all deleted.

I solved this problem, installed Ext2Fsd on my Windows7 maschine,

connected to the archos and changed the CM9(archos.ext4) to the ICS@BLUE_V03, installed the Kernel Files and reboot....

and voila, thanks.
[Gen9 Android Development] nicktastique:
I wiped /data and made sure I was using version 2 of JackpotClavin's CM9 image. At the "Welcome" screen, android.process.media crashes. Logcat attached.
[Gen9 Android Development] escrivel:
Hi,

are there any news regarding a CM9 oder CM10?
[Gen9 Android Development] skicavs:
Titanium

Fantastic work, it is really a cool rom. Unfortunately I installed Titanium Backup and it force closes instantly. Anyone else had this problem yet or know of any fix? It would be great to be able to use the backup when flashing around ROMS quickly.

The error in logcat is :

W/ApplicationContext( 1328): Unable to create files directory /data/data/com.keramidas.TitaniumBackup/files

E/com.keramidas.TitaniumBackup.o.r( 1328): OOPS! We were unable to load "libtitanium.so" even though we're not a system app. Something is wrong here.
[Gen9 Android Development] Quinny899:
For some reason your /data partition is unavailable. Install a Root file browser and see if you can access it
[Gen9 Android Development] omegaRED7:
Ok, so I've been trying to get this blasted Huawei E173s-1 to play nicely with CM9, but still no luck. Still getting that "SIM not loaded" error in the logcat. Anyone with a working Huawei 3g dongle willing to post a logcat (-b radio -b main)?

Sent from my GT-I9001
[Gen9 Android Development] nicktastique:
Another intermittent problem: after a while (hours, days?), the HDD stops responding. When this I hit this bug, attempts to read any file on /mnt/storage will wake up the HDD:

I/cat ( 578): <4>[84684.666076] jm20329_wakeup

...but then whatever process is doing the reading sits forever in uninterruptible IO wait. logcat shows nothing out of the ordinary. After rebooting, all is well.
[Gen9 Android Development] nicktastique:
A new build with fixes for HDD models can be found here:

https://hotfile.com/dl/168131179/9f02e3e/archos.ext4.bz2.html

Changes:

Fixed Settings -> Stroage crash.

Fixed android.process.media crashes.

Fixed MTP.

Set the HDD spin-down timeout to 2 minutes at boot. Edit /system/etc/init.d/99hdd to change the timeout.

Remove 'Recovery' and 'Bootloader' options from 'Reboot tablet' menu.

Issues:

Power off/Reboot sometimes sits forever in an infinite loop.

Currently breaks sdcard models, but will be fixed soon.

The changes are in my git repositories. To make your own build, you'll probably want to use my local manifest since multiple repositories are involved. I also simplified the device tree and added some extra packages. Click here for instructions.
[Gen9 Android Development] nashi20002003:
Tested the new image.....wow..excellent job. MTP works, Storage...works...I will have to play with hdd spindonw settings...

Thanks for improving this ROM..
[Gen9 Android Development] nicktastique:
Happy to hear it's working!

I'm planning to add an entry for HDD spindown to the settings app, hopefully by the end of the week.
[Gen9 Android Development] cajl:
How install this ?
[Gen9 Android Development] nicktastique:
If you're already using JackpotClavin's CM9, just:

$ adb push archos.ext4 /data/local

...and reboot the device.

If you're using something else (the following is what I do, but there are other instructions earlier in this thread):

$ adb push archos.ext4 /data/local

$ adb shell

(now in a root shell on the device)

# cd /data

# stop

# mv local .local

# rm -rf *

# mv .local local

# exit

Power-off the device by holding the power button for 10 seconds, power back on, and boot into SDE.
[Gen9 Android Development] surdu_petru:
Hi!

...also you can use the same way from AOKP ( Installation step ! ).

..if you have already installed CM9 , for reinstal ...just do > adb push archos.ext4 /mnt/storage ( also work for hdd model ) & flash zImage and initramfs in SDE !

Good luck !

( If you push direct archos.ext4 to /data/local - work for all models but you can not benefit from wipe dalvik-cache !!! - so it is preferable to push always archos.ext4(.update) to /mnt/storage !!!!!!! )
[Gen9 Android Development] cajl:
It is not simple.....
[Gen9 Android Development] gen_scheisskopf:
Well, for wiping dalvik you can

touch /mnt/storage/wipe-dalvik.update

as this is also included in init :)
[Gen9 Android Development] ducatisto:
...so to the experts: WHAT is the difference between these two versions "archos.ext4" and "archos.ext4.update" - is it necessary to always add this ".update" or do they work differently or why do you use () ?

THX - just curious... :confused:
[Gen9 Android Development] nicktastique:
Pushing a new build of the same Android version shouldn't require a dalvik wipe. Also, dalvik will remove invalid entries from its own cache, so I'm not sure why it's ever necessary. ;)

---------- Post added at 10:05 AM ---------- Previous post was at 09:46 AM ----------

There is no difference. initramfs does the exact same thing whether it's called archos.ext4 or archos.ext4.update.

if [ -e /mnt/storage/archos.ext4 ] ; then
rm /data/local/archos.ext4
rm /data/local/archos.squashfs
rm /mnt/storage/archos.ext4.backup
cp /mnt/storage/archos.ext4 /data/local/archos.ext4
mv /mnt/storage/archos.ext4 /mnt/storage/archos.ext4.backup
rm -r /data/dalvik-cache
fi

if [ -e /mnt/storage/archos.ext4.update ] ; then
rm /data/local/archos.ext4
rm /data/local/archos.squashfs
rm /mnt/storage/archos.ext4.backup
cp /mnt/storage/archos.ext4.update /data/local/archos.ext4
mv /mnt/storage/archos.ext4.update /mnt/storage/archos.ext4.backup
rm -r /data/dalvik-cache
fi
[Gen9 Android Development] gen_scheisskopf:
archos.ext4 is used as main system image located in /data/local

archos.ext4.update- init checks if this file is present (/mnt/storage) and treats it as firmware update (rm /data/local/archos.ext4, mv /mnt/storage/archos.ext4.update /data/local/archos.ext4, rm -rf /data/dalvik-cache/*).

So if you want init to take care of system updates use /mnt/storage/archos.ext4.update

It is strongly advised to perform dalvik-cache wipe after any system update (even one system .apk) otherwise you can get bootloop or app FCs. If app "resources" in dalvik-cache are not exactly the same as required problems will occur.

---------- Post added at 04:19 PM ---------- Previous post was at 04:10 PM ----------

Why squashfs handling is included? This was abandoned quite some time ago (FW 3.2.80 or earlier)
[Gen9 Android Development] nicktastique:
I don't know. This is from surdu's initramfs.
[Gen9 Android Development] nicktastique:
This build should also work on sdcard models:

https://hotfile.com/dl/168401200/a31cef2/archos.ext4.bz2.html

No other changes.
[Gen9 Android Development] scholbert:
tres bien

Hey nicktastique,

C'est fantastique!!

I'll gonna test your image these days.

Really appreciate your progress!

Working on solution to leave these loop mounted images though.

...may take some time ;)

Thanks a lot for your effort.

Hack on,

scholbert
[Gen9 Android Development] surdu_petru:
Hi,

I included this option , because I wanted to make some Custom Rom in squashfs format !

...meanwhile I never made what I wanted to do ... so option remove/delete .squashfs no effect ! ....but I'm sure , that this option not affect the boot process !

Good luck ! :good:
[Gen9 Android Development] skyworxx:
Hi,

this file seems to be broken. I downloaded it several times, but when extracting it always says the file is broken. Tried with different browsers and on different computers.
[Gen9 Android Development] carefreeway:
[MENTION=3727492]JackpotClavin[/MENTION], can you clarify what is "/system/bin/thermaldaemon" service inside init.archos.rc file ( https://github.com/JackpotClavin/Ar...os/archos_g9/prebuilt/etc/init/init.archos.rc )? It was pulled in the latest 5.1.1 firmware and it can't find it during boot.

P.S. I found that it was from original Archos firmware, but there are no such file too. Sorry.
[Gen9 Android Development] JackpotClavin:
The kernel might be a problem, perhaps you can just pull the stock one and use that? Not sure. Getting back to work on it now, I'll upload a few screenshots too :-)
[Gen9 Android Development] alahkel:
Hi, I have a 101 g9 not-turbo tab, ready to test :p
[Gen9 Android Development] :
Ready to test! 101 G9 :)
[Gen9 Android Development] JackpotClavin:
Just got the camera and Netflix working, having an issue with the sdcard mounting though
[Gen9 Android Development] alahkel:
You mean external or internal one?
[Gen9 Android Development] JackpotClavin:
Oh, okay, so apparently it was working all along, I just didn't have a folder called /mnt/storage/DCIM for the camera to save pictures...

Gonna test out a physical sdcard next
[Gen9 Android Development] lonespeaker:
This is perfect timing as I was just setting up a build environment earlier today in the hope of porting CM9. I currently compile for my galaxy nexus and fancied the challenge of getting it working on the archos so I look forward to trying your port out.

How does it compare to stock ICS in terms of responsiveness? I have the 80G 1.2ghz version and find it can be quite laggy at times when moving around the launcher.
[Gen9 Android Development] trevd:
I can give it a blast. on a A101 G9 8GB OMAP4430 - One of the first batch

Is there any specific areas you want testing or are you looking for general stability/day to day use at first?

I've got the Archos 3G Stick as well which would be worth testing as well as numerous other bits of Usb Tat. :)
[Gen9 Android Development] eggyenergy:
Count me in, and maybe im able to help you ouy with a few;)

I have the 10.1 g9 dual 1ghz and 512 RAM(:
[Gen9 Android Development] JackpotClavin:
For some reason, the internal sdcard is being weird. On stock, /mnt/storage has premade folders like Pictures and crap like that, but when I do CM, they are gone. I wasnt able to test out the physical sdcard either. It feels pretty smooth overall, there are a few times where it may hang for a half second or leave a visual artifact for a split second but everything looks good. So far, all I can think of is the sdcard not working
[Gen9 Android Development] alahkel:
If you need someone to test it right now as the port is, I'm available :p I don't mind broken things :ppp
[Gen9 Android Development] JackpotClavin:
I gotta make it so you don't have to do anything to install it. Right now if you were to install it, you have to make a bunch of folders and push a few files or else it won't boot up :-) gimme a few days ;)
[Gen9 Android Development] alahkel:
Ok master, thank you so much and well done til now! :)
[Gen9 Android Development] VennGLC:
Archos 10.1

I have the original G9 10.1 that I rotate Ubuntu/ICS/ICS Blue on. This would be a welcome addition for tinkering.