yashsingh1/xdaforums huggingface dataset:
[Gen9 Android Development] trevd:
The main trason is because you've used the archos init binary you need to dump the s**t because it's just so wrong...... It breaks down like this

init .includes and header call android_filesystem_config.h which does exactly what the name suggest obviously because the archos init is ics if it missing some users and group definitions namely

"#define AID_SDCARD_R 1028 /* external storage read access */"

which should be the group of /storage, and /storage/emulated however "our" gid is set at root. I've just recreated the same behaviour on a nexus 7 as a test.

I'll fix up the .rc's to use the new init, not going do anything special just bring them into the root from that stupid f***king directory /etc/init, why init.archos.rc another init.rc needs to be a seperate is something I'll never understand. the init.A80S.rc etc can be properly referenced as init.archos80sboard.rc if memory serves.... ueventd.archos.rc can just be merged with main ueventd because all devices access it and the only piece of init script functionality lost by the change will be the mknod which archos use somewhere ..... I can just readd it as a builtin function of the new init... that's kinda how google designed it to work..

Hopefully I figured this out correctly :laugh:

Oh yeah , I noticed we are missing the users option from the Device Section of the Settings App, I thought It was going to be something to do with that at firs be it doesn't really matter it just means adding additional users is impossible
[Gen9 Android Development] Quallenauge:
Cool!

I moved the suggested files into root and set the import statements at the beginning of init.rc:

import init.archos.rc
import init.A80S.rc

I also added the contents of ueventd.archos.rc at the end of uevent.rc and finaly added the init binary from cyanogenmod.

But (as usual) it doesn't boot. Maybe because of the missing command for mknod. (But this is only for setting up tvout?!)

But there are also other commands...

I used my serial adapter to

[ 7.527740] init: /init.rc: 245: invalid command 'touch'
[ 7.533966] init: /init.rc: 280: invalid command 'mknod'
[ 7.540222] init: /init.rc: 287: invalid command 'echo'
[ 7.547241] init: /init.rc: 566: invalid command 'rmmod'

Complete log: http://pastebin.com/EXLYg5Gn

On the stock init it ends with:

http://pastebin.com/XHLAzrDR

Maybe I've done all the beginner mistakes ;)
[Gen9 Android Development] trevd:
Nice one, I was starting to see the same result. errmm so have you got a booter then?

EDIT: can you buy those serial cables??.... I want one!! :D
[Gen9 Android Development] Quallenauge:
No sadly not. The output of init is not really "verbose". Maybe I need to adjust the ouput settings to see where it really hangs.

Edit: Oh, I see, we can add some log output via the "log" command.

I started from here to search for serial cables. Then I ordered one from here:

http://uk.rs-online.com/web/p/interface-development-kits/7158525/?searchTerm=715-8525

(and also a comfortable usb plate: http://uk.rs-online.com/web/p/usb-cable-assemblies/2949474/?searchTerm=294-9474
[Gen9 Android Development] julle131:
Re: [DEV][4.2] CyanogenMod 10.1

I know you all own 80s, but please don't forget the 101s :D.

If you are also compiling the kernel for this ROM, maybe you could add extra governors and stuff like that.

And sorry for breaking your productive post combo. C-c-c-combobreaker.
[Gen9 Android Development] scholbert:
Hi guys,

wow... great stuff is happening here.

Unfortunately i am little lazy with hacking the Archos recently.

You never told me about the process with your bricked device... is it already working again?

I'm glad to see you back :D

Just a word on this... i once tried to guide letama to built his own adaptor (there's some description in my hardware hacking threads).

We ended with the same cable at RS-electronic though.

Keep on your nice work!!

Just a short question in general...

Right now i paused my work on fully fledged u-boot as a bootloader replacement.

I started to implement framebuffer for OMAP4430/60, but it's not finished yet.

As we go for more open source ROM's here, do you think it makes sense to start over with this project again?

I must admit, that my sparetime is still limited, but maybe i should think of putting all down at Gitorious or similar.

Sorry for writing little bit off-topic!

Anyway i really appreciate your progress over here :fingers-crossed:

Cheers,

scholbert
[Gen9 Android Development] Quallenauge:
Just a little sidenode,

We (trevd and I) managed it to domesticate that beast in kind of providing external storage.

We added the CM10.1 init implementation and added some corrections for the exec statements.

It is providing us the mount_all feature.

Then it turns out, that the sdcard daemon was not started correctly. (This must be solve, it's not clear why class "late_start" is not called. It should be done by the mount_all logic in init).

As workaround, I've added a class_start late_start command at the end of the post-fs section)

At least we need a kernel, which supports namespaces. Only a recompile is needed for that.

WLAN module is crashing for me. when android boots up - I've to look at it.

More soon.

@Scholbert: Give me a little bit time to answer ;)
[Gen9 Android Development] Quinny899:
Has anyone noticed camera works when you push the OMX libs? It just has no storage to save to, trying to get FaceLock working now

EDIT: Via the method on this thread: http://xdaforums.com/showthread.php?t=1405275 you can pull screenshots to a PC. Adding some to the OP
[Gen9 Android Development] Quinny899:
Face Unlock is working, I'll make a new version and upload it sometime today
[Gen9 Android Development] julle131:
Hello again!

I decided to download the source to my virtual server. The problem I faced seems kind of weird... I have no makefile/other CM files...:confused:

Here is the "ls -a":

jesse@rnd-cust1:~/ArchosG9-BuildEnv/cm-10.1$ ls -a
.
..
abi
android
android-toolchain-eabi-linaro-4.7-2013.03-2-2013-03-17_20-47-57-linux-x86.tar.bz2
bionic
bootable
build
cts
dalvik
development
device
docs
external
frameworks
gdk
hardware
kernel
libcore
libnativehelper
ndk
packages
pdk
prebuilt
prebuilts
README.md
.repo
sdk
system
tools
vendor

I used the steps in https://github.com/Quallenauge/ArchosG9-BuildEnv

Do you have any experience of this situation?

Now building the project...
including device/archos/archos_g9/vendorsetup.sh
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/armv7-a/vendorsetup.sh
including device/generic/mips/vendorsetup.sh
including device/generic/x86/vendorsetup.sh
including device/lge/mako/vendorsetup.sh
including device/ti/omap5sevm/vendorsetup.sh
including device/ti/panda5/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including sdk/bash_completion/adb.bash
Trying dependencies-only mode on a non-existing device tree?

============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.2.2
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.2.0-4-amd64-x86_64-with-debian-7.0
HOST_BUILD_TYPE=release
BUILD_ID=JDQ39
OUT_DIR=/home/jesse/ArchosG9-BuildEnv/cm-10.1/out
============================================

make: *** No targets specified and no makefile found. Stop.

[MENTION=4636351]Quallenauge[/MENTION] You might want to add remote="omap-mirror" to dmox project in local_manifest.xml ;)
[Gen9 Android Development] trevd:
Hi

The makefile does sometimes go missing during downloading. Fortunately the makefile in question is the one in the root of your sources and consists of one line, here's a link

http://androidxref.com/source/raw/Makefile

What other cm source are you expecting?
[Gen9 Android Development] julle131:
That fixed it. I have now downloaded everything and fixed java. Now it just waiting and hoping... With the awesome power of dual-core 3.2ghz and 700mb ram(2700mb swap) which one happens most likely?

1. Build succeeds(yeah... Right.) 2. Run out of ram 3. Dependency is missing, or 4. Just random error which none has ever heard of.

Edit: And the answer is error. It is too late for anything else. I will identify it tomorrow.

:D

By the way, what changes do I have to do to get 101s working? I'm wondering because it has its own build.
[Gen9 Android Development] therbom:
You could use trevd's device tree (the trevd_cleanup branch). Otherwise you could cherry-pick my pull request (https://github.com/Quallenauge/cm10-archos-g9/pull/3) in the cm-10.1 branch. I think, however, that trevd used a cleaner solution.
[Gen9 Android Development] swaaye:
There is a bug with charging. Sometimes a reboot is necessary for the charger to be detected.

3G USB can be enabled by command line. Search the thread.

micro USB file transfer is non-functional. There is something wrong with the MTP mode.
[Gen9 Android Development] Djirin:
I'm running and typing this in CWM right now on my 101! It's a 1.5ghz turbo with 512mb ram and 8gb flash. I forget which files I used as someone had posted a link to a test version for the 101 somewhere in the first few pages. I think I used the original files posted on the first page but now can't be sure as I did download both sets.

With the few other bugs people have mention it is otherwise running just fine.

Another bug In have noticed is that I can't pair my phone with the tablet without the wireless being turned on. I use Bluetooth tether and have to have wireless on for it to find the phone for the pairing.
[Gen9 Android Development] trevd:
Hi There.

As long as you stay clear of any build that uses the 3.0.58 kernel then you'll be fine for charging AFAIK

3G Dongles work but you have to switch both the usb power and the rfkill0 state manually through sysfs

I don't know to the last one! As we say in the trade "Try it yourself" ;) then you can report back any findings :good:
[Gen9 Android Development] trevd:
Hi I've pulled [MENTION=3279100]cobje[/MENTION] changes and created a branch called cm10.1-a101s [ https://github.com/Quallenauge/cm10-archos-g9/tree/cm10.1-a101s ] which should build as per [MENTION=4636351]Quallenauge[/MENTION] instructions. So you can just use that branch for now.
[Gen9 Android Development] Filatov.p:
Hmm... as I suppose CWM is integrated into ext4 file, right?

But it doesn't work for me. Everything was made by instructions but CWM seems just saying it is doing something. After all I don't see Cyan animation, I see my previouse rom logo instead. And it boots forever. After flashing wipe zip all my content still remains isn't it weird?

UPD: I've made it! Just installed from the clean rooted 28 rom. Thank you everyone and especially developers!
[Gen9 Android Development] Filatov.p:
don't know if such feedbacks are still needed, but anyway. Charging worked fine on the first boot, rebooted and it stopped. GPS doesn't come up, but no FC anywhere. For now I only saw two states of percentage battery indicator - 90 and 75, believe there is a problem in a related xml. Didn;t get how to enter Developer settings. Fortunately there was debugging turned on by default so I was able to enter through its notification
[Gen9 Android Development] trevd:
Hi There,

I think we're are alright for battery reports and gps now :D Are you talking about the power_stats xml ( or whatever it's called ) in the framework-res.

To get into Developer settings. goto Settings About tablet and tap the build number box 7 times.
[Gen9 Android Development] revere521:
Hello - I am having a touch screen issue after flashing CM10.1 on my A101s turbo - I have made it to the welcome screen with the start button, but no touch input will register.

flashed the following from CWM:

cm_archos_g9-userdebug-4.2.2_JDQ39E-CWM_6.0.3.1-K3.0.58.zip

then

gapps-jb-20130301-signed.zip

then

update-boot-a101s.zip (wouldn't boot without this)

then

wipe-data.zip

Everything appears to load and boot correctly, just no touch input

i attached my logcat if it helps

Edit -

the output of :> adb shell getevent seems to indicate a mouse driver is not loaded?

add device 1: /dev/input/event3

name: "compass"

add device 2: /dev/input/event2

name: "MMA8453Q Accelerometer"

could not get driver version for /dev/input/mice, Not a typewriter

add device 3: /dev/input/event4

name: "ARCHOS-TWL6040 Headset Jack"

add device 4: /dev/input/event0

name: "gpio-keys"

add device 5: /dev/input/event1

name: "twl6030_pwrbutton"
[Gen9 Android Development] revere521:
Ok I think I fixed my own problem

flashed the following from CWM:

cm_archos_g9-userdebug-4.2.2_JDQ39E-CWM_6.0.3.1-K3.0.58.zip

update-a101s-test.zip

then

gapps-jb-20130301-signed.zip

then

update-boot-a101s.zip (wouldn't boot without this) -- dont need this with update-a101s-test.zip

then

wipe-data.zip

Everything appears to load and boot correctly - touch now works.
[Gen9 Android Development] ladalgigi:
Hi

I searched in trevd's goo.im tree, and I want to know if cm_archos_g9-userdebug-4.2.2_JDQ39E-CWM_6.0.3.1-K3.0.58 is newer than update.a101s.test.zip ?

Thanx

Envoyé depuis mon Archos G9 4.2.2 avec Tapatalk
[Gen9 Android Development] realismo:
Which is the latest build? Any suggestion to avoid battery and charging problem? Do we have any fix?
[Gen9 Android Development] revere521:
I'm not certain if what I did was necessarily correct - it just worked for me.

I can say the charging doesn't look like its working properly with the ROM i used. Settings->battery says stats are not available.

I have seen the charge percentage show 100% 90% and 75% only (which appears to have already been reported). It does appear to charge, but the reporting of battery status is partially incorrect?

The update-a101s-test.zip archive was uploaded after cm_archos_g9-userdebug-4.2.2_JDQ39E-CWM_6.0.3.1-K3.0.58 on 4/27 if that helps

Looking at the last modified dates in the archives, cm_archos_g9-userdebug-4.2.2_JDQ39E-CWM_6.0.3.1-K3.0.58 was last modified 2 hrs after the test version.
[Gen9 Android Development] TjaXanK:
I can't seem to get this booting, I flashed update-a101s-test.zip via CWM, flashed gapps via CWM, flashed wipe-data.zip via CWM, and when I restart I just get a black screen! I'm coming from stock archos rom...
[Gen9 Android Development] revere521:
I know I had to clear my data partition and clear the dalvik cache from cwm before i flashed each time before the first time it worked.

It took several hard reboots
[Gen9 Android Development] TjaXanK:
I've just tried like 50 times and it doesn't seem to work :(
[Gen9 Android Development] revere521:
I have a G9 the a101s, if you have a 80, the cm_archos_g9-userdebug-4.2.2_JDQ39E-CWM_6.0.3.1-K3.0.58.zip may be the right ROM for you?
[Gen9 Android Development] TjaXanK:
Oh, hadn't thought of that! I'll try it as soon as it's done downloading!
[Gen9 Android Development] revere521:
After reading the rest of this very long thread, i tried the other Kernel noted - the A101S from here- https://www.4shared.com/archive/YsYm6IL5/a101s.html

which works much much better on the G9 101, the battery issues i had were solved by reading :o

I noticed that the tablet also recognized my 5ghz network briefly?

Also Is there a deep sleep setting in Cyanogen Mod?
[Gen9 Android Development] therbom:
Not by default, but some devices have device-specific settings (a.k.a. 'device parts') that provide that option.
[Gen9 Android Development] mrbr0wn:
My Bluetooth external keyboard doesn't seems to work...i mean, i can associate the keyboard to the tablet but it doesn't work...

Inviato dal mio Archos G9 con Tapatalk 2
[Gen9 Android Development] Quallenauge:
Deep sleep...

Hi!

Can you please try to enable this for our device?

If this works, I would like to include a pull request. I really would like to have this feature enabled.... :)
[Gen9 Android Development] revere521:
Is this something we need to install? The device parts?
[Gen9 Android Development] therbom:
Hmmm... I can't find it anymore. I'll search further once the stable releases of CM 10.1 are out, it's a bit hectic around here...

Device Parts resides in the device tree and is built and added automatically, if available.
[Gen9 Android Development] Filatov.p:
Whose kernel is this? Is it comparable with 80 version? Cruz I'm tired a bit of tablet switching off by battery got low and I can't even see the real level of it.
[Gen9 Android Development] revere521:
I assumed that Kernel was the 010 version of the OP's kernel - its mentioned a few times earlier in the thread, around page 29.

I had been using the 030 version from the main page, but i was having battery issues, and some intermittent wireless issues when resuming from sleep.

It has been working properly with charge / discharge percentage reporting, and I am not having any other apparent "glitchy" issues
[Gen9 Android Development] revere521:
Here are some screen caps of battery screen, and about screen if they help

Edit - sorry thumbs are good enough, just started using the XDA app
[Gen9 Android Development] revere521:
after using for more than a day, i can say that once it reached 50% charged, it does jump back up to 75% for no reason.

Rebooting, will show that i'm down to 50%, then after a while it displays 75% again.

Thanks for clarifying, i saw it referred to as an app earlier and thought it might have been optional to install separately.
[Gen9 Android Development] Filatov.p:
So actually this kernel has the same problems
[Gen9 Android Development] revere521:
Yes, but it looks like i had still been using the 3.0.58+ version of the Kernel, the 3.0.21+ version is the one supposedly that does not have the battery bug.

I am currently starting over pushing the archos.ext4 file from https://www.4shared.com/archive/YsYm6IL5/010.html again

and flashing the zimage and initramfs from that file (which downloads as a101s.7z)

hopefully this will be the earlier kernel, and i can report back if it solves the problem.

EDIT - reporting back after a bit

I formatted the device from SDE, i had flashed this so many times, i was not sure what was what.

I downloaded the file from the link above again and over-wrote what i had - just to be absolutely sure that was what i was using.

I formatted the tablet from the SDE menu - so everything was gone, and pushed the archos.ext4 to /data/local, and flashed the matching zimage and initramfs.

When it booted up it showed my battery at 38% which was already a better sign, since then (amongst setting it all back up the way i wanted) i had it charging both by USB and the wall charger. Its currently at 48%, also a good sign.

The about screen shows i am now on kernel 3.0.21+

I will continue testing it to see if there are any other bugs

BTW - the MTP also mounts the tablet just like stock - it shows up as Archos g9101, and boththe internal sd and the extrenal sd are available from my computer in windows.
[Gen9 Android Development] Djirin:
As far as the battery % not showing correctly. I opened up a terminal window and ran:

batteryd

And left it running in the terminal window. All it says is:

Measuring battery level on A101S...

It does change the battery % though.. Whether it is an accurate % is a good question.

When plugging in my archos original wall charger I still see:

Unknown charger detected! 0

STATE_NONE - STATE_VBUS

charge_level set to 2

PHY ON

And I see the lightning symbol appear on the battery on the dock. I tried with a USB cable but it does not appear to think it is a charger as the lightning symbol never appeared. I have unplugged the original charger several times and the lightning symbol has reappeared each time I plugged it in. So it seems to recognize the power being plugged in.

The % is now changing on its own.. Perhaps the problem we are experiencing is that batteryd is not being run properly on bootup?
[Gen9 Android Development] revere521:
Which Kernel do you have installed? 3.0.58+ or 3.0.21+

on 3.0.21+ when i run batteryd i get:

Measuring battery level on A101S...

fatal error opening "sys/power/wake_lock"

fatal error opening "sys/android_power/acquire_partial_wake_lock"

batteryd: writing to /sys/busplatform/drivers/tw16030_bci/charge_level failed: Permission denied

batteryd: open /sys/class/leds/power/trigger failed: Permission denied

even though, I have been charging the tablet, with minor or no usage for the last half hour, and the percentage has climbed from 48% to 62%.

I will keep monitoring
[Gen9 Android Development] Djirin:
3.0.58+

And I forgot to mention that once I opened terminal I ran su to be superuser on the prompt
[Gen9 Android Development] revere521:
running as su just shows Measuring battery level on A101S...

i get no errors plugging in either the original wall charger or the USB->pc cable and the % of charge does not change.
[Gen9 Android Development] Djirin:
So far mine started off at 71% and has climbed through 72 to 73%. I will leave it plugged in to see if it keeps climbing up on its own.
[Gen9 Android Development] revere521:
While batteryd was running, the tablet charge has not changed, but killing the command and closing the terminal - the battery begins charging again % begins rising again.

i'm not terribly familiar with the batteryd command, but it seems to be used just to enumerate the capacity of the battery, what you may be experiencing is tablet measuring the actual charge the battery currently holds? That could be why it climbs, as it determines the correct level.

I am going to let it fully charge, the see what it looks like.
[Gen9 Android Development] Djirin:
I am not sure what batteryd does anyway. Just me playing around as I looked through the various /bin directories. :laugh:

Don't forget we are on 2 different kernels as well. That could also be a factor on the differences we are seeing. And as I don't remember if I used the original setup files from the start of this thread or the a101 test file someone else had posted.. That could also be a factor.

update:

And as an update to my testing the battery % is still continuing to climb by itself and not sporadically. This looks promising.
[Gen9 Android Development] revere521:
no doubt, but both running similar tests with the different kernels may prove helpful. i did find some options for batteryd:

usage: batteryd [-dn] [-i interval] [-f file] [-v voltage]

-d increase debug level,

-i specify a mesurement interval (in seconds),

-f output file for debug messages,

-n dry run mode,

-s no shutdown mode,

-v get the battery level for the specified idle voltage.

so i am attempting to pull some kind of a log with the command (under su) batteryd -d -i 10 -f /mnt/sdcard/battery.log

if i get some output, i'll post it.
[Gen9 Android Development] Filatov.p:
revere521,

How does your tablet behave running this kernel? GPS is still out?
[Gen9 Android Development] revere521:
Everything looks like it is working correctly, i have not been able to test the GPS yet - i will try to get outside and get a signal lock.

I haven't had the opportunity to test everything but charging / discharging works correctly (there is no log output in my test above for batteryd),

wifi seems to work well, and sleep / resume works well also. I am able to use MTP to mount the storage as a drive.

I don't have a Bluetooth device to test, maybe i can try to pair it with my phone.

if you guys want me to test something else, let me know - and I will report back in a while with an answer for GPS.

EDIT -

The GPS finds my location with google maps - or at least it appears to - I get the "accurate to 100 meters" marker on the map, and the gps icon/reticle flashes in the notification area in the upper left of the screen.
[Gen9 Android Development] revere521:
EDIT2 -

I can pair the tablet with my phone, but archos remote no longer works. I'm not sure i can actually do anything with the pairing.
[Gen9 Android Development] Filatov.p:
Hundred meters... Was WiFi enabled while testing? Accuracy seems like it was locked by WiFi spot. To make it clear use GPS Test app and see what it says and how many sattelites gets