[ROM] [4.3.1] CyanogenMod 10.2

Search This thread

bizcuite

Senior Member
Aug 11, 2010
1,180
764
Corbeil-Essonnes
No - You may risk a brick!

Don't install this on your tablet - it's completely different to the Archos G9 80s.
This is also the reason why this tablet will not get CM from me. Also Archos has digressed from releasing kernel sources and other things for other tablets than the G8 and G9 series, which can make it possible to create real custom images.
It seems not cool anymore for them to provide support. I really can only recommend to buy tablets where the manufacturer releases sources.
IMHO only with these consumer needs this will be changed.
Sorry to write this... :(

What is the differences between this 2 tabs? (Carbon-elements series and gen9 series)

Because i use actually on my a70s2 froyo the kernel for a70s2 HC. (Tab Brick if you try to install hc on a froyo version)
The hardware is similar but the board revision is not the same.

Bizcuite

Sent from my GT-N7100 using xda app-developers app
 

Quallenauge

Inactive Recognized Developer
May 10, 2012
269
598
What is the differences between this 2 tabs? (Carbon-elements series and gen9 series)

Because i use actually on my a70s2 froyo the kernel for a70s2 HC. (Tab Brick if you try to install hc on a froyo version)
The hardware is similar but the board revision is not the same.

Bizcuite

Sent from my GT-N7100 using xda app-developers app

It's a Rockchip RK3066 driven device. The G9 series is a TI OMAP driven device. So the kernel for the 80s isn't prepared for the Rockchip architecture.
 
  • Like
Reactions: bizcuite

Quallenauge

Inactive Recognized Developer
May 10, 2012
269
598
New version available

Hi!

I uploaded a new version if someone would like to install it (got to first post for links).

[*]A widget "Archos Control Center" where the user can activate the deep sleep behavior. Warning: If you use the archos as alarm clock you will oversleep! (It only will wake up, when pressing the power button).
Also the 3G port can be activated with this widget. I discovered some hangs, which can only solved by removing and re-adding the widget on the screen. If someone can help me with this widget, please have a look at: github It's my first app ever... so it is very ugly =)
[*] Initial A101s support. -> Please give some feedback (at best in case of errors with an logcat).
 
Hi!

I uploaded a new version if someone would like to install it (got to first post for links).

[*]A widget "Archos Control Center" where the user can activate the deep sleep behavior. Warning: If you use the archos as alarm clock you will oversleep! (It only will wake up, when pressing the power button).
Also the 3G port can be activated with this widget. I discovered some hangs, which can only solved by removing and re-adding the widget on the screen. If someone can help me with this widget, please have a look at: github It's my first app ever... so it is very ugly =)
[*] Initial A101s support. -> Please give some feedback (at best in case of errors with an logcat).

Couple of installation notes:
  • You don't need to wipe your device if you are coming from the previous version of 10.2 for Archos. That way you don't have to re-install all of your apps. (But do a backup first, anyway. Just in case.)
  • Despite being awesome for getting us an update so quickly, @Quallenauge forgot to rename kernel to zImage, so you'll need to do that before updating the kernel.
  • If you are coming from a previous version of 10.2, you can probably push the archos.ext4 file using adb instead of mounting the data partition, but I didn't test this.

That said, this is the fastest ROM I've had on this device, and I've tried most of them! This might just be ooh, shiny! syndrome, or even just the wipe/install making things run faster for a while, but this has been butter smooth for the week-and-a-half that I've had it installed. Well done, sir!

- Dave
 
  • Like
Reactions: hansi_schulz

mordesku

Inactive Recognized Developer
Jul 29, 2009
573
1,019
Toruń
Hi!

I uploaded a new version if someone would like to install it (got to first post for links).

[*]A widget "Archos Control Center" where the user can activate the deep sleep behavior. Warning: If you use the archos as alarm clock you will oversleep! (It only will wake up, when pressing the power button).
Also the 3G port can be activated with this widget. I discovered some hangs, which can only solved by removing and re-adding the widget on the screen. If someone can help me with this widget, please have a look at: github It's my first app ever... so it is very ugly =)
[*] Initial A101s support. -> Please give some feedback (at best in case of errors with an logcat).

Thanks for update. I have some dev experience so i can take a look at your code.

Wysłane z mojego HTC One V przy użyciu Tapatalka
 

Quallenauge

Inactive Recognized Developer
May 10, 2012
269
598
Couple of installation notes:
  • You don't need to wipe your device if you are coming from the previous version of 10.2 for Archos. That way you don't have to re-install all of your apps. (But do a backup first, anyway. Just in case.)
  • Despite being awesome for getting us an update so quickly, @Quallenauge forgot to rename kernel to zImage, so you'll need to do that before updating the kernel.
  • If you are coming from a previous version of 10.2, you can probably push the archos.ext4 file using adb instead of mounting the data partition, but I didn't test this.

Thanks for your suggestions. I really have to update the opening post. Also I should take a look on my build - script to rename the kernel image (generated by Android make) to zImage.
 

mordesku

Inactive Recognized Developer
Jul 29, 2009
573
1,019
Toruń
Hi!

I uploaded a new version if someone would like to install it (got to first post for links).

[*]A widget "Archos Control Center" where the user can activate the deep sleep behavior. Warning: If you use the archos as alarm clock you will oversleep! (It only will wake up, when pressing the power button).
Also the 3G port can be activated with this widget. I discovered some hangs, which can only solved by removing and re-adding the widget on the screen. If someone can help me with this widget, please have a look at: github It's my first app ever... so it is very ugly =)
[*] Initial A101s support. -> Please give some feedback (at best in case of errors with an logcat).

I loked in to your code it is dirty like you said. Why you chose to make a widget instead of standalone app? also figured out that widget forces close when tablet gets havy load like games. Maybe widget try to connect to service but service was killed by system to free some resources. Tomorow i'l try to provide logcat for that issue. Sorry for my bad english.

Sent from my ARCHOS 80G9 using Tapatalk 4
 
  • Like
Reactions: Quallenauge

ayushbh

Member
Oct 10, 2012
36
5
help to install this rom on my 80 g9 turbo

plz can someone explain in detail how to install this rom, i have the stock rom 4.0.28(4.0.4) and not rooted also..plz tell me how to root the device and to install this rom..i am really fed up of the lag and hang of the tablet which is face everyday..also plz explain according to windows 7 , i don't have linux(sorry)..thnx
 

Quallenauge

Inactive Recognized Developer
May 10, 2012
269
598
3G Stick is working (for me)

Hi,

the 3G Stick is working :)
Please try the new image in opening post.

@mordesku
I loked in to your code it is dirty like you said. Why you chose to make a widget instead of standalone app? also figured out that widget forces close when tablet gets havy load like games. Maybe widget try to connect to service but service was killed by system to free some resources. Tomorow i'l try to provide logcat for that issue. Sorry for my bad english.

I found a widget is useful for me, because first I wanted to write an (classical) app, but it seems to not so comfortable. Correctly, this settings has to be in the android settings page. @Quinny899 provided a solution on the 4.2.2 rom via the xposed framework.
(It's free for everyone to integrate this in the firmware).
So If you have hints how to make things better, I want it. Also, if you have some free time please write a new better one (widget? :) ) I'd like to learn.... :)
 

livy

Member
im trying to install this on my 101 g9

ive booted my laptop into puppy linux, followed the commands.
but after rebooting after copying over zimage and initrams the machine still boots into the orginal archos firmware.

not sure whats going wrong.

any help would be great
 

mordesku

Inactive Recognized Developer
Jul 29, 2009
573
1,019
Toruń
Here is logcat for FC issue on your widget, also contains strange error
Code:
11-09 09:12:03.277: ERROR/TI OMAP PowerHAL(877): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
11-09 09:12:03.277: ERROR/TI OMAP PowerHAL(877): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
11-09 09:12:03.293: ERROR/TI OMAP PowerHAL(877): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
11-09 09:12:03.293: ERROR/TI OMAP PowerHAL(877): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
11-09 09:12:03.316: ERROR/TI OMAP PowerHAL(877): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
11-09 09:12:03.316: ERROR/TI OMAP PowerHAL(877): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
11-09 09:12:03.332: ERROR/TI OMAP PowerHAL(877): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
11-09 09:12:03.332: ERROR/TI OMAP PowerHAL(877): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
11-09 09:12:03.348: ERROR/TI OMAP PowerHAL(877): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
11-09 09:12:03.348: ERROR/TI OMAP PowerHAL(877): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
11-09 09:12:03.371: ERROR/TI OMAP PowerHAL(877): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
11-09 09:12:03.371: ERROR/TI OMAP PowerHAL(877): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
11-09 09:12:03.387: ERROR/TI OMAP PowerHAL(877): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
11-09 09:12:03.387: ERROR/TI OMAP PowerHAL(877): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
11-09 09:12:03.410: ERROR/TI OMAP PowerHAL(877): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
11-09 09:12:03.410: ERROR/TI OMAP PowerHAL(877): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
11-09 09:12:03.426: ERROR/TI OMAP PowerHAL(877): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
11-09 09:12:03.426: ERROR/TI OMAP PowerHAL(877): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
11-09 09:12:03.441: ERROR/TI OMAP PowerHAL(877): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
11-09 09:12:03.441: ERROR/TI OMAP PowerHAL(877): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
11-09 09:12:03.465: ERROR/TI OMAP PowerHAL(877): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
11-09 09:12:03.465: ERROR/TI OMAP PowerHAL(877): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
11-09 09:12:03.496: ERROR/TI OMAP PowerHAL(877): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
11-09 09:12:03.496: ERROR/TI OMAP PowerHAL(877): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
11-09 09:12:05.027: INFO/cat(611): <3>[57508.151611] init: No dynamic_args: Try to execve('/system/bin/watchdog_daemon'): args: �
11-09 09:12:05.027: ERROR/WatchdogDaemon(1270): ERROR opening temp sensor: No such file or directory
11-09 09:12:05.371: ERROR/TI OMAP PowerHAL(877): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
11-09 09:12:05.371: ERROR/TI OMAP PowerHAL(877): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
11-09 09:12:05.426: ERROR/TI OMAP PowerHAL(877): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
11-09 09:12:05.426: ERROR/TI OMAP PowerHAL(877): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device
11-09 09:12:05.684: INFO/cat(611): <7>[57508.810607] select 31495 (llenauge.widget), adj 5, size 4076, to kill
11-09 09:12:05.684: INFO/cat(611): <7>[57508.810729] send sigkill to 31495 (llenauge.widget), adj 5, size 4076
11-09 09:12:05.684: INFO/ActivityManager(877): Process com.quallenauge.widget (pid 31495) has died.
11-09 09:12:05.691: WARN/ActivityManager(877): Scheduling restart of crashed service com.quallenauge.widget/com.quallenauge.service.ArchosControlService in 5000ms
11-09 09:12:08.410: INFO/GCoreUlr(1202): Successfully inserted location
11-09 09:12:08.418: INFO/GCoreUlr(1202): Not calling LocationReportingService, hasMoved: false, elapsed millis: 2223080, request: Tablet
11-09 09:12:10.035: ERROR/WatchdogDaemon(1275): ERROR opening temp sensor: No such file or directory
11-09 09:12:10.043: INFO/cat(611): <3>[57513.167633] init: No dynamic_args: Try to execve('/system/bin/watchdog_daemon'): args: �
11-09 09:12:10.699: INFO/ActivityManager(877): Start proc com.quallenauge.widget for service com.quallenauge.widget/com.quallenauge.service.ArchosControlService: pid=1278 uid=1000 gids={41000, 1015, 1028, 3002, 3001, 3003, 3007}
11-09 09:12:10.809: VERBOSE/ArchosControlService(1278): Service is started...0
11-09 09:12:10.824: VERBOSE/ArchosControlService(1278): 3G Port state <false>.
11-09 09:12:10.848: DEBUG/AndroidRuntime(1278): Shutting down VM
11-09 09:12:10.848: WARN/dalvikvm(1278): threadid=1: thread exiting with uncaught exception (group=0x418b9700)
11-09 09:12:10.856: ERROR/AndroidRuntime(1278): FATAL EXCEPTION: main
        java.lang.RuntimeException: Unable to start service com.quallenauge.service.ArchosControlService@41b3ce70 with null: java.lang.NullPointerException
        at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:2849)
        at android.app.ActivityThread.access$1900(ActivityThread.java:153)
        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1366)
        at android.os.Handler.dispatchMessage(Handler.java:99)
        at android.os.Looper.loop(Looper.java:137)
        at android.app.ActivityThread.main(ActivityThread.java:5289)
        at java.lang.reflect.Method.invokeNative(Native Method)
        at java.lang.reflect.Method.invoke(Method.java:525)
        at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:739)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:555)
        at dalvik.system.NativeStart.main(Native Method)
        Caused by: java.lang.NullPointerException
        at com.quallenauge.service.ArchosControlService.onStartCommand(ArchosControlService.java:47)
        at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:2832)
        ... 10 more
11-09 09:12:11.590: DEBUG/audio_hw_primary(627): Set output volume: 0.000000, gain -Inf
11-09 09:12:11.715: DEBUG/audio_hw_primary(627): Set output volume: 0.000000, gain -Inf
11-09 09:12:14.418: DEBUG/audio_hw_primary(627): Closing output
11-09 09:12:15.051: INFO/cat(611): <3>[57518.181427] init: No dynamic_args: Try to execve('/system/bin/watchdog_daemon'): args: �
11-09 09:12:15.051: ERROR/WatchdogDaemon(1296): ERROR opening temp sensor: No such file or directory
11-09 09:12:20.066: INFO/cat(611): <3>[57523.194335] init: No dynamic_args: Try to execve('/system/bin/watchdog_daemon'): args: �
I think that system is restarting the service without proper intent wich causes nullpointer in that line:
Code:
if (ArchosControlService.EXTRA_MODE_3G_PORT.equals( intent.getExtras().get(ArchosControlService.EXTRA_MODE))){

I have not much experience in Android development, has writen some little apps. Acording to http://developer.android.com/guide/components/services.html you should stop service using your method which starts service again when some values are changed. In my opinion it is bad solution. I think you should write service working in background and bind him to widget. When you bind service to widget you can call service methods directly from widget http://developer.android.com/guide/components/bound-services.html. And now comment for your code. I't is very hard to read and understand. Thera are some good practices writing code to keep it easy to read and easy to develop. First of all method should have one responsibility. I explain on example using Yours ArchosControlWidget class.

On update method is oversized. Before my refactor it's look like this:
Code:
public class ArchosControlWidget extends AppWidgetProvider {
	private static final String TAG = "ArchosControlWidget";
	
	@Override
	public void onUpdate(Context context, AppWidgetManager appWidgetManager, int[] appWidgetIds) {
		Log.v(TAG, "onUpdate...");
        final int N = appWidgetIds.length;

        
        ComponentName thisWidget = new ComponentName(context,ArchosControlWidget.class);
        int[] allWidgetIds = appWidgetManager.getAppWidgetIds(thisWidget);
        
        // Perform this loop procedure for each App Widget that belongs to this provider
        for (int i=0; i<N; i++) {
        	int appWidgetId = appWidgetIds[i];
        	
        	Log.v(TAG, "Install listeners for widget <"+appWidgetId+">...");	
        	
			// Create an Intent to launch ExampleActivity
	        Intent intent = new Intent(context, ArchosControlService.class);
	        intent.putExtra(ArchosControlService.EXTRA_MODE, ArchosControlService.EXTRA_MODE_DEEP_SLEEP);
	        intent.putExtra(ArchosControlService.EXTRA_MODE_VALUE, false);
	        PendingIntent pendingIntent = PendingIntent.getService(context, 1, intent, PendingIntent.FLAG_UPDATE_CURRENT);
	        
	        // Get the layout for the App Widget and attach an on-click listener to the button
	        RemoteViews views = new RemoteViews(context.getPackageName(), R.layout.main);
	        views.setOnClickPendingIntent(R.id.btnDeepSleep, pendingIntent);
	        
	        intent = new Intent(context, ArchosControlService.class);
	        intent.putExtra(ArchosControlService.EXTRA_MODE, ArchosControlService.EXTRA_MODE_3G_PORT);
	        intent.putExtra(ArchosControlService.EXTRA_MODE_VALUE, false);
	        intent.putExtra(AppWidgetManager.EXTRA_APPWIDGET_IDS, allWidgetIds);
	        
	        pendingIntent = PendingIntent.getService(context, 2, intent, PendingIntent.FLAG_UPDATE_CURRENT);
	        views.setOnClickPendingIntent(R.id.btn3GPortSwitch, pendingIntent);
	
	        // Tell the AppWidgetManager to perform an update on the current App Widget
	        appWidgetManager.updateAppWidget(appWidgetId, views);
        }
        
        Intent intent = new Intent(context, ArchosControlService.class);
        intent.putExtra(ArchosControlService.EXTRA_MODE, ArchosControlService.EXTRA_MODE_UPDATE);
        context.startService(intent);
        
	}
	   @Override
	    public void onReceive(Context context, Intent intent) {
	        super.onReceive(context, intent);
	        Log.v(TAG, "onReceive..."+intent.getAction()+"|"+intent.toString());
	   }
}


After my refactorisation it looks like this:
Code:
public class ArchosControlWidget extends AppWidgetProvider {
	private static final String TAG = "ArchosControlWidget";
	
	@Override
	public void onUpdate(Context context, AppWidgetManager appWidgetManager, int[] appWidgetIds) {
		Log.v(TAG, "onUpdate...");

        ComponentName thisWidget = new ComponentName(context, ArchosControlWidget.class);
        RemoteViews views = new RemoteViews(context.getPackageName(), R.layout.main);
        int[] allWidgetIds = appWidgetManager.getAppWidgetIds(thisWidget);

        for (int appWidgetId : appWidgetIds) {
        	Log.v(TAG, "Install listeners for widget <"+appWidgetId+">...");	
            initDeepSleepButton(context, views);
            init3gStickButton(context, allWidgetIds, views);
	        appWidgetManager.updateAppWidget(appWidgetId, views);
        }
        startService(context);
	}

    private void startService(Context context) {
        Intent intent = new Intent(context, ArchosControlService.class);
        intent.putExtra(ArchosControlService.EXTRA_MODE, ArchosControlService.EXTRA_MODE_UPDATE);
        context.startService(intent);
    }

    private void init3gStickButton(Context context, int[] allWidgetIds, RemoteViews views) {
        Intent intent = createIntentFor(context, ArchosControlService.EXTRA_MODE_3G_PORT);
        intent.putExtra(AppWidgetManager.EXTRA_APPWIDGET_IDS, allWidgetIds);
        PendingIntent init3gStickIntent = PendingIntent.getService(context, 2, intent, PendingIntent.FLAG_UPDATE_CURRENT);
        views.setOnClickPendingIntent(R.id.btn3GPortSwitch, init3gStickIntent);
    }

    private void initDeepSleepButton(Context context, RemoteViews views) {
        PendingIntent deepSleepIntent = PendingIntent.getService(context, 1, createIntentFor(context, ArchosControlService.EXTRA_MODE_DEEP_SLEEP), PendingIntent.FLAG_UPDATE_CURRENT);
        views.setOnClickPendingIntent(R.id.btnDeepSleep, deepSleepIntent);
    }

    private Intent createIntentFor(Context context, String serviceType) {
        Intent intent = new Intent(context, ArchosControlService.class);
        intent.putExtra(ArchosControlService.EXTRA_MODE, serviceType);
        intent.putExtra(ArchosControlService.EXTRA_MODE_VALUE, false);
        return intent;
    }
    @Override
    public void onReceive(Context context, Intent intent) {
        super.onReceive(context, intent);
        Log.v(TAG, "onReceive..."+intent.getAction()+"|"+intent.toString());
    }
}
As you can see it's easier to read, there's no need to comment the code. In my whole experience, bad code is hard to develop by third persons, and for developer after some time. I'm ready to help with developing the app/widget. So feel free to ask questions.
 
  • Like
Reactions: hamertor

hansi_schulz

Member
Feb 9, 2011
36
6
plz can someone explain in detail how to install this rom, i have the stock rom 4.0.28(4.0.4) and not rooted also..plz tell me how to root the device and to install this rom..i am really fed up of the lag and hang of the tablet which is face everyday..also plz explain according to windows 7 , i don't have linux(sorry)..thnx

You Need to install SDE first.
Pls. have a look to some of the other G9 threads where this step is explained in detail.
The rest of the installation is already explained in this thread (also how to do this with Win7) !

If you get this ROM installed you are also rooted.

Cheers
hansi

---------- Post added at 01:18 PM ---------- Previous post was at 12:48 PM ----------

:victory:
Couple of installation notes:
  • You don't need to wipe your device if you are coming from the previous version of 10.2 for Archos. That way you don't have to re-install all of your apps. (But do a backup first, anyway. Just in case.)
  • Despite being awesome for getting us an update so quickly, @Quallenauge forgot to rename kernel to zImage, so you'll need to do that before updating the kernel.
  • If you are coming from a previous version of 10.2, you can probably push the archos.ext4 file using adb instead of mounting the data partition, but I didn't test this.

That said, this is the fastest ROM I've had on this device, and I've tried most of them! This might just be ooh, shiny! syndrome, or even just the wipe/install making things run faster for a while, but this has been butter smooth for the week-and-a-half that I've had it installed. Well done, sir!

- Dave


Coming from earlier CM 10.2 Version and just replaced the "archos.ext4" in /data/local with Archos and the integrated filemanager from SDcard. After that just rebooted to SDE and copied the init & zimage via Win7 to the appearing recovery drive. After rebooting all Apps were updated and Kernel/OS stated a build date of 8.11.2013.
All apps and date are still there.
 
Last edited:

ayushbh

Member
Oct 10, 2012
36
5
You Need to install SDE first.
Pls. have a look to some of the other G9 threads where this step is explained in detail.
The rest of the installation is already explained in this thread (also how to do this with Win7) !

If you get this ROM installed you are also rooted.

Cheers
hansi



one last thing..i have installed sde..tell me how to boot into sde and do i need to root also or should i directly install the rom given on this post...btw this rom will get installed on archos g9 turbo 8gb version..thnx
 
Last edited:

hansi_schulz

Member
Feb 9, 2011
36
6
one last thing..i have installed sde..tell me how to boot into sde and do i need to root also or should i directly install the rom given on this post...thnx

You"ll get into the SDE by powering on the G9 on and having the speaker volume rocker down pressed all the time.
Then follow the process described earlier in this thread.

No need to root in between...

Good luck.

You are responsible if you brick your device :)

---------- Post added at 01:44 PM ---------- Previous post was at 01:39 PM ----------

Hi,

the 3G Stick is working :)
Please try the new image in opening post.

@mordesku


I found a widget is useful for me, because first I wanted to write an (classical) app, but it seems to not so comfortable. Correctly, this settings has to be in the android settings page. @Quinny899 provided a solution on the 4.2.2 rom via the xposed framework.
(It's free for everyone to integrate this in the firmware).
So If you have hints how to make things better, I want it. Also, if you have some free time please write a new better one (widget? :) ) I'd like to learn.... :)

Thanks also the version of 8th nov still works great.
Are there any other improvements except the widget stuff ?

I hoped to get the USB memory stick available with setting 3G on.
Unfortunately there is nothing in the mounted USB directory...
Any idea how to get it working ?
 

ayushbh

Member
Oct 10, 2012
36
5
You"ll get into the SDE by powering on the G9 on and having the speaker volume rocker down pressed all the time.
Then follow the process described earlier in this thread.

No need to root in between...

Good luck.

You are responsible if you brick your device :)



sorry to bother you again..i booted into sde but their was no option of format system their were 3 options 1)Android,2)Devepoper and 3)Recovery..can u plz tell me which option to choose to format system..thnx
 

hansi_schulz

Member
Feb 9, 2011
36
6
sorry to bother you again..i booted into sde but their was no option of format system their were 3 options 1)Android,2)Devepoper and 3)Recovery..can u plz tell me which option to choose to format system..thnx

Mine has 6 items.
Exactly as stated in the first thread of this xda section, you should repeat each step carefully again and maybe load a custom ROM once before trying to install this ROM.
 

ayushbh

Member
Oct 10, 2012
36
5
i followed all the steps as mentioned on page 3 of this forum but to my surprise after installation i did not see any cyanogenmod logo and also i was on stock rom only i.e 4.0.28(4.0.4)...can anyone tell me that what wrong did i do in the method..i downloaded the files as given on page 1 of this forum..thnx
 

Top Liked Posts

  • There are no posts matching your filters.
  • 37
    Hi, if anyone would like to run a 4.3.1 Google OS on a Archos G9 80S device (and currently only this), download and extract this file:
    19_01_2014-13_32_32

    Installation (tested only with linux) :

    - reboot into SDE menu and under "Format System" perform a "Reset Android & Storage" to clear all data of previous installations (this is really important!).
    - reboot into SDE menu and under Developer Edition Menu -> "Export Data Partition"
    - mount this usb drive
    Code:
    sudo mkdir <Mount_Path>/local
    sudo cp archos.ext4.update <Mount_Path>/local/archos.ext4
    sudo sync
    sudo umount <Mount_Path>
    - wait until the unmount process is done
    - reboot into SDE menu and under Developer Edition Mernu , Flash Kernel and Initramfs : copy zImage and initramfs.cpio.lzo on the new driver that appears on desktop/laptop
    - Wait for reboot your devices : after reboot you can see Android prepares the system for a while .....be patient !

    What's new ?
    • ------------ since 19_01_2014-13_32_32 -------------
    • Last attempt to satisfy "H" model users. Wrong fstab definition file was used.
    • ArchosControlCenter: Alternate command for enabling disabling 3G service activation/deactivation.
    • ------------ since 17_01_2014-20_17_32 -------------
    • KSM (Kernel samepage merging) support. (Enable it in CM performance options).
    • HDMI enable for 101 models too.
    • WLAN MAC address taken from device. Until now in my releases, the MAC address where the same for all devices. (gave some conflicts, when two devices are used in parallel).
    • ------------ since 22_12_2013-13_29_20 -------------
    • Deactivated PCB temperature sensor. It is not part of the devices, and (my) default setting gives the cpufreq
      module a wrong view of the situation. Now it should reduce the reboot which is caused by critical temp, by reducing core speed.
    • ------------ since 19_12_2013-23_43_36 -------------
    • Using CPUFreq from 3.0.31 omapzoom reference kernel
    • Included app from @mordesku (modified by me) -> 3G should work!
      Note that if you only pushed the image as update, please make sure to delete the /data/data/com.android.providers.telephony/databases/telephony.db
      (adb shell rm /data/data/com.android.providers.telephony/databases/telephony.db) and reboot the device to rebuild.
      I forgot to include the apns-conf.xml :eek: so there are no APN's available (as result no data connection can be established).
    • Removed my Widget to not affect the archos control center app
    • Some kernel changes.
    • Enabled zram and init.d
    • Initial support for H models (testing and patches are welcome).
    • Newest CM Updates: Changes since last release
    • ------------ since 02_12_2013-22_56_07 -------------
    • Removed clicks when audio driver is closed
    • Reduced the volume a little bit to avoid scratches
    • Removed default dpi setting on build
    • Newest CM Updates: Changes since last release
    • ------------ since 21_11_2013-21_45_53 -------------
    • Using new pvr library SGX-BIN: DDK binaries and KM source 1.9@2291151
    • HWComposer 1.1 interface
    • No ICS audio blob anymore. Adapted omap upstream audio HAL.
    • Some internal audio extensions by TI (omap_enhancement)
    • Kernel audio sources updated to 3.0.31 omap upstream release.[/INDENT]
    • ------------ since 08_11_2013-22_14_52 -------------
    • CM10.2
    • Upstream init.rc
    • TI Openlink WLAN driver R5.SP6.01
    • Temporary disabled ClockworkMod Recovery
    • A widget "Archos Control Center" where the user can activate the deep sleep behavior. Warning: If you use the archos as alarm clock you will oversleep! (It only will wake up, when pressing the power button).
      Also the 3G port can be activated with this widget. I discovered some hangs, which can only solved by removing and re-adding the widget on the screen. If someone can help me with this widget, please have a look at: github It's my first app ever... so it is very ugly =)
    • Initial A101s support.
    • Something I've not tried...
    • 3G USB Stick is working.

    Issues:
    - GPS not reliable (as usual for every release....) -> After complete new system ("Reset Android & Storage") the GPS is working very good. Subsequent boots later it gets worse at my device(s):
    My Workaround: Go into Settings->Apps->All->Google Service Framework and delete data and cache. Then reboot and GPS should e working. Also I get sufficient results with the GPS Toolbox App.
    21_11_2013-21_45_53:
    Microphone as degraded sound quality compared to the stock rom.
    Some sound clicks here and there when system sounds are turned on.
    Audio sound is a little bit quiet compared to the stock rom. (Needs to be adjusted by myself).

    Can't test HDMI (both audio/video). (It's also not an use case for me). If someone would like to help.... ;)
    HDMI scaling issues
    "H" models doesn't seem to work.

    Rebuild: All used revisions for this release are stored in a separate folder in the archive.

    Additions:
    Archos Control Panel App from @mordesku: http://xdaforums.com/showpost.php?p=47789812&postcount=88

    Archive:
    17_01_2014-20_17_32
    22_12_2013-13_29_20
    19_12_2013-23_43_36
    02_12_2013-22_56_07
    21_11_2013-21_45_53
    08_11_2013-22_14_52
    07_11_2013-22_53_33
    Archos CM10.2 - 26_10_2013-23_26_11
    11
    New version available

    Hi.

    I would like to mention that a new version is available! Changes are:
    • Using new pvr library SGX-BIN: DDK binaries and KM source 1.9@2291151
    • HWComposer 1.1 interface
    • No ICS audio blob anymore. Adapted omap upstream audio HAL.
    • Some internal audio extensions by TI (omap_enhancement)
    • Kernel audio sources updated to 3.0.31 omap upstream release.

    Warning: Can't test HDMI (audio/video) !! I give them a low chance that it works!
    Due changes to the HW Composer and the audio driver, the interfaces have changed
    and we can't use the archos audio blob for future android versions.
    Last two weeks I wanted to compile the audio HAL by myself. So I had to study how it works. Thanks to the very good documentation and my second Archos G9 device for comparing alsa values I get it running in a way that fits my needs.
    (Code) suggestions are welcome... :)

    I'm glad that the new SGX binary and the hwcomposer 1.1 interface is in place. Maybe this is a good sign to get KitKat running, but that's another story. I'm compiling since weeks in parallel...hopefully I get this also running. Stay tuned....
    9
    Hmm I downloaded that program but mine is a EXT3 partition is that wrong then? Hm I'm kinda confused what to do when I mount the partition though.. can you help me?

    I used ext2fsd.If u want to use it just install it and reboot your win7.
    After restart you go as followed

    1 reboot into SDE menu and under "Format System" perform a "Reset Android & Storage" to clear all data of previous installations (this is really important!).
    2 reboot into SDE menu and under Developer Edition Mernu -> "Export Data Partition"
    3 connect your Tablet with your Computer
    4 start ext2 Volume manager.You should see your local drives and a extra one which is the Linux partition.
    5 mark that partition and press F7.
    6 Start the service and be sure to check the "Enable writingsupport for ext3 volumes" and uncheck "Mount all volumes in read-only mode.Press apply.
    7 again mark your linux partition and press F3 and uncheck "Mount volume in readonly mode"
    8 Now you should see the partition under "myComputer".Open it and if u reseted "Reset Android & Storage" u should see 2 Folders(Media and Lost+found)
    9 make a new folder called "local".
    10 rename the archos.ext4.update to archos.ext4 and copy it into "local" folder
    11. Unmount the linux partition as you would do with any usb drive and then press ok on your tablet
    12 go to "Developer Edition Menu" and choose "Flash Kernel and Initramfs"
    13 A new drive will appear under "myComputer".Copy zImage and initramfs.cpio.lzo to it and press ok.
    14 Reboot your tablet and after a couple of seconds you should see the Archos logo and then Cyanogen logo

    TADA....
    9
    New version available

    Hi!

    I would like to mention that I uploaded a new version. Highlights are:
    KSM (Kernel samepage merging) support. (Enable it in CM performance options).
    HDMI enable for 101 models too.
    WLAN MAC address taken from device. Until now in my releases, the MAC address where the same for all devices. (gave some conflicts, when two devices are used in parallel).

    Sadly. no support for "H" models.
    7
    Yeah! I really hoped that someone jumped on the train ;)
    DeepSleep: I wrote an binary that calls an ioctl with an specific value.
    Usage:
    Code:
    #Enable DeepSleep
    /system/bin/deepsleeper 1
    #Disable DeepSleep
    /system/bin/deepsleeper 0

    Usb Port:
    This is done via RFKILL interface.
    Code:
    #Enable USB Key
    echo "1" >/sys/class/rfkill/rfkill0/state
    #Disable USB Key
    echo "0" >/sys/class/rfkill/rfkill0/state
    (This is only an example, my widget calls an specific service set3GPortState with value 1 or 0 because directly writing to the value via the java/dalvik interface was not allowed (permission denied)).

    You have to close the RIL in order to enable the 3G Stick. Don't worry it is restarted by @trevd great hotplug component.
    But if you don't do it, the 3G will not be initialized correctly!

    Hi there,

    Here is my app "Archos Control Panel" for now it is standalone app, tomorow i will ad widget and push sources to some public repo. App requires root for changing 3g stick mode. It remeber your settings and set it after device reboot. Here is preview bin apk.


    Sent from my ARCHOS 80G9 using Tapatalk 4