Firmware 4.0.25 Live - Report Bugs!

[mls]

There's no real reason to change that setting unless you specifically never want to use an alarm. Instead you can just use the Power button as follows:

Short quick press = turns screen off* (stand-by mode that really just turns off power to the screen*)

Longer press (2 to 5 seconds) = causes a menu to pop up with the following options:

Deep Sleep = turns screen off* and throttles CPU way down (barely running) and disables alarms to save battery.
Reboot = restarts the device (takes a long time to start up again).
Power Off = this will totally shut down (really saves battery, but takes a long time to start up again).

*Note: The default (under Wi-Fi Advanced settings) is to also shut off Wi-Fi any time the screen turns off unless the device is plugged in (charging). There are also options for how the 3G Stick behaves (the default is to turn off 3G Stick 15 minutes after the screen screen turns off).

I guess not everyone knows the basics of how these devices operate.

[birdiezzz]

For users that have, or want to exchanged their internal Seagate HDD in the Archos 101 G9 250Gb for a SSD drive.
You can make the (Linux) hdd visible on a Mac with the programs: 'OSXFUSE' and 'fuse-ext2-0.0.7'
For this you have to take the HDD out of the case!
These programs bring the 250 Seagate drive total content to your Mac desktop screen, and you can make a full diskImage.
You than can easily copy this Image to the new SSD drive.
With the right SSD built in, the battery will last longer, and there will be less heat.

[mls]

The Xbox 360 USB controller buttons operate differently with this firmware. Don't know if it was a change by Google or Archos, but...

In some ways the buttons now make more sense for some things, BUT... the trigger button code is now wrong so most games no longer are playable.

Since it will be months before Archos ever gets a fully function new firmware update put out, and since they refuse to provide a way to revert back to 4.0.7, and since you can not install the official Archos SDE (to use a custom rooted ROM)...

Well, all I can say is SCREW IT!!!

Over a week ago I learned how to install an UN-official SDE and then installed a stock 4.0.7 rooted firmware. So, now both my 80 and 101 G9's now work like they used to before. I really feel sorry for all the rest of you that are stuck waiting for Archos to get around to fixing things.

[geemacd]

Over a week ago I learned how to install an UN-official SDE and then installed a stock 4.0.7 rooted firmware. So, now both my 80 and 101 G9's now work like they used to before. I really feel sorry for all the rest of you that are stuck waiting for Archos to get around to fixing things.

What guide if any did you use for this? Want to do the same

[alpenn]

[quote="mls"

*Note: The default (under Wi-Fi Advanced settings) is to also shut off Wi-Fi any time the screen turns off unless the device is plugged in (charging). There are also options for how the 3G Stick behaves (the default is to turn off 3G Stick 15 minutes after the screen screen turns off).

I guess not everyone knows the basics of how these devices operate.[/quote]


The only problem with setting the 3G stick to turn off when the screen turns off is that you have to reboot your device to get it to detect it again more often than not.

[birdiezzz]

Over a week ago I learned how to install an UN-official SDE and then installed a stock 4.0.7 rooted firmware.
So, now both my 80 and 101 G9's now work like they used to before.
I really feel sorry for all the rest of you that are stuck waiting for Archos to get around to fixing things.

This is probably the best solution if the owner has no warranty anymore.
Al those non-official FW are pretty good, with a very good response on bugs.
Those developers really know what they are doing!!
But if you are getting HW problems (and the changes are not imaginary) you'r in trouble.
No warranty repairs.
And it is not easy to install this software. (but a rooted FW will open new doors also, with better backup possibilities etc)
Maybe i will give it a try.

[Nightsurfer]

Not sure why "bragon" has not posted this yet, but there is a 3rd "test" version of the firmware available for download on the Archos server now, if somebody is desperate enough to try it out without an official announcement about what this version is supposed to change or fix:

http://update.archos.com/9/gen9/gen9_4. ... os_it4.aos

[bragon]

Please find this 4.0.26 test firmware that should address the sound glitches happening on some applications (that constantly change sample rate...) and the loss of hard drive or USB host port for 3G key happening sometimes. There is also a notification highlighting when the media scanning is occurring.
http://update.archos.com/9/gen9/gen9_4. ... os_it4.aos
This firmware is undergoing certification and should be pushed shortly.

[stouffa]

This test 3 firmware seems to have made my tablet(80 G9 HDD model), more responsive, but a new strange bug has crept in, trying to watch any flash videos through browsers makes them very juddery as if they're not being processed properly, anyone else experiencing this?

[robinhood]

This test 3 firmware seems to have made my tablet(80 G9 HDD model), more responsive, but a new strange bug has crept in, trying to watch any flash videos through browsers makes them very juddery as if they're not being processed properly, anyone else experiencing this?

I had this problem with .25. What I did was to reinstall Adobe flash from the adobe website - download archives -, as flash is not available in google play anymore. Since then this issue was not seen. .26 up until now not.. I will keep watching anyway..

[mls]

Please find this 4.0.26 test firmware that should address the sound glitches happening on some applications (that constantly change sample rate...) and the loss of hard drive or USB host port for 3G key happening sometimes. There is also a notification highlighting when the media scanning is occurring.
http://update.archos.com/9/gen9/gen9_4. ... os_it4.aos
This firmware is undergoing certification and should be pushed shortly.

@bragon

Results of my testing...

Mediacenter and HDMI out now seem to be working correctly again (at least for my setup).

Sound effects in games with background music also seems to now be working again (didn't get to check all my games though).

As I mentioned in a previous post, there seems to have been a change made for the Xbox 360 USB controller. I'm not sure if it was a change by Google or by Archos. I like how some of that was changec, but the trigger (mainly right trigger) button code seems to now be wrong (almost looks like mistakenly is now 8 instead of 6, so could just be a typing error in the programming code). Anyway, this makes a lot of games that did work now totally unplayable.

There is still something wrong with the video driver because the on-screen controls for Max Payne do not show up at all (and, of course, the Xbox USB controller does not work at all now with this game either).

And the #1 most major flaw still has not been fixed at all. One quick look at Settings => Apps => Running and it is very clear and obvious that the memory management is NOT working correctly! EVERYTHING in the list shows it uses/needs 0.00B (zero Bytes). There is no possible way the system can properly free up memory for other things if it does NOT know how much is already being used or how much something else will need to use to run in!

BTW: I took a quick look on my friends Motorolla RAZR MAXX after it was upgraded to Googles 4.0.4 and it DOES correctly show how much RAM is in use, and also shows much more free RAM as well.

So, PLEASE FIX THE MEMORY MANAGEMENT BEFORE messing around with trying to fix all kinds of other side problems that are being caused by the system constantly running itself out of RAM space! Don't know how you morons at Archos could have possibly not noticed this MAJOR flaw before ever releasing any of these upgrades to start with!

Also, PLEASE QUIT PUTTING OUT OTA UPGRADES UNTIL AFTER you've had a bunch of volunteers here (and over on xda-developers) actually test them and report problems. Since you people are apparently far to lazy to ever fully test anything yourselves (at Archos)... you would save a lot of headaches by just letting some of us do the beta testing... instead of screwing up everyone's devices all at once!

I've tried to be polite here, but I'm sure I speak for ALL the other people here in saying we are royally sick of the Archos B.S. with releasing totally botched firmware upgrades!

[mls]

This test 3 firmware seems to have made my tablet(80 G9 HDD model), more responsive, but a new strange bug has crept in, trying to watch any flash videos through browsers makes them very juddery as if they're not being processed properly, anyone else experiencing this?

I had this problem with .25. What I did was to reinstall Adobe flash from the adobe website - download archives -, as flash is not available in google play anymore. Since then this issue was not seen. .26 up until now not.. I will keep watching anyway..

Adobe Flash is still on Google Play for devices below Android 4.1. Just look in the Google Play app in the section of all the apps you have had installed before and it should be listed. Otherwise, just do a Google search with a web browser for the link to the Google Play page for Adobe Flash.

Of course, if you would have used an app (like Astro File Manager) to back up all of your apps and copied the backups to your computer or a microSD card... well, then even if Google does drop things from their Play store you could re-install them. (people with "rooted" devices often use Titanium Backup instead though). Anyway, there are plenty of backup apps to choose from out there.

[mls]

Over a week ago I learned how to install an UN-official SDE and then installed a stock 4.0.7 rooted firmware. So, now both my 80 and 101 G9's now work like they used to before. I really feel sorry for all the rest of you that are stuck waiting for Archos to get around to fixing things.

What guide if any did you use for this? Want to do the same

I'm a bit busy right now, but I'll try to send you a private message with some details sometime over the weekend.

I should WARN everyone though that it is rather complicated (thanks to Archos not allowing to install their own official SDE).

Normally I would NEVER recommend anyone root their devices (because you can royally screw things up and turn them into a brick quite easily if you don't know what you are doing). However, after all the screwed up Archos firmware upgrades over months in the past just to get from Honeycomb to a working 4.0.7 ICS firmware... I just was NOT going to wait months on end to get my devices working correctly again after this totally botched upgrade!

Those of us that started out with G9 devices that originally came with Honeycomb, and went thru all the hassles of multiple upgrades to get to a working 3.2.80 already know what a mess Archos made of things with multiple upgrades to eventually get to a working 4.0.7 (which still had a flaw with Wi-Fi). So, now I just test out any further new Archos upgrades as a side line. I figure by the time the release (as screwed up) version of Jelly Bean, then they MAY actually have at least a partially correctly version of this one LOL.

[bknight]

Still issues with this latest release.
I just reset the multimedia library in case that was a problem.

my piano by borce Trajkovski which worked perfectly on my g9 101 (512) on 4.0.7 managed 1 note immediately after installing the latest firmware and has since remained silent.

I'm also a little confused
I thought the cpu was dual core but currently only a single core appears to be working?
if that is the case wouldn't that explain why the tablet is performing so badly?

I would hope someone with more knowledge than me could check to see if the app that told me this is correct.

[stouffa]

Having used this test firmware a bit more now, I think in some ways it might be worse than the last one? I reinstalled flash, still didn't fix my video issue. My hard drive stops more than it did, lots of apps give me"not responding" warnings until I give the tablet a bit more time to spin up. The whole tablet has frozen several times, requiring a hard reset. Any ideas??

[ces001]

I still have not had my issues addressed. The constant random reboots are extremely annoying. I have also recently noticed that my notifications in the lower right task bar no longer work. Since the last update I no longer receive any notifications at all. Charging of my battery is still hit or miss since the last update too. Sometimes the charging light will start flashing even though the battery is mostly discharged.

Please address these issues. Media center is not the only problem with the current firmware!

OK, my notifications were mysteriously turned off, so I turned them back on ... problem solved. BUT the constant random reboots keep occuring daily. I received a reply from Archos tech support regarding my issue(s) instructing me to install their firmware update using a different method. This involved holding down the volume up button while rebooting, which led to a menu that included an option to update my firmware. This attempt resulted in an "update failed" message (twice). I still think the battery drains too fast, but I am almost always near my charger so I guess I can deal with it, but any suggestions on how to solve the reboot issue would be appreciated.

[hars73]

There's no real reason to change that setting unless you specifically never want to use an alarm. Instead you can just use the Power button as follows:

Short quick press = turns screen off* (stand-by mode that really just turns off power to the screen*)

Longer press (2 to 5 seconds) = causes a menu to pop up with the following options:

Deep Sleep = turns screen off* and throttles CPU way down (barely running) and disables alarms to save battery.
Reboot = restarts the device (takes a long time to start up again).
Power Off = this will totally shut down (really saves battery, but takes a long time to start up again).

*Note: The default (under Wi-Fi Advanced settings) is to also shut off Wi-Fi any time the screen turns off unless the device is plugged in (charging). There are also options for how the 3G Stick behaves (the default is to turn off 3G Stick 15 minutes after the screen screen turns off).

I guess not everyone knows the basics of how these devices operate.

For me there is a reason to set the default setting to deep sleep. Since 4.0.25 there is a battery drain that causes the battery to be empty in less then 3 days without using it. It is caused by a wakelock and because of that the tablet awakes every half hour or so. When it is put into deep sleep it will not wake up, so there is no battery drain for me right now anymore. And i don't use any alarms so that's okay to me.

[SvenC]

With the latest test-release 26, the boot time of my HDD-model is longer as before update. With the 25er update, I have a boot time nearly 2 min, now I have a boot time 2.15 min. Does Archos not optimize the code for HDD-models?

[lbocchio]

This is the fourth fw version I have tried after 4.07 and it is still causing Media Center to crash. I even uninstalled any album art downloader as iTag Pro, Album Art Grabber, Cover Art Download, etc to avoid any possible interference with MediaCenter. I also uninstalled Mobo Player and Mix ZIng that I have been trying as alternatives.

Now Media Center doesn't even start of stops after playing 10 secs of music or video. None of these problems happened with fw 4.07

This is the error log I am getting:

--------- beginning of /dev/log/main
--------- beginning of /dev/log/system
11-17 09:24:42.421 E/AlbumCover( 8939): getArtwork: Exception, fallback to generic album art
11-17 09:24:47.812 E/dalvikvm-heap( 8939): Out of memory on a 24-byte allocation.
11-17 09:24:48.335 E/dalvikvm-heap( 8939): Out of memory on a 48-byte allocation.
11-17 09:24:49.578 E/dalvikvm-heap( 8939): Out of memory on a 160-byte allocation.
11-17 09:24:50.031 E/dalvikvm-heap( 8939): Out of memory on a 184-byte allocation.
11-17 09:24:50.570 E/dalvikvm-heap( 8939): Out of memory on a 184-byte allocation.
11-17 09:24:51.093 E/dalvikvm-heap( 8939): Out of memory on a 28-byte allocation.
11-17 09:24:51.429 E/InputDispatcher( 615): channel '4150e048 com.archos.mediacenter/com.archos.mediacenter.music.browser.MusicBrowserActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
11-17 09:24:59.335 E/AlbumCover( 9080): getArtwork: Exception, fallback to generic album art
11-17 09:25:01.429 E/AlbumCover( 9080): getArtwork: Exception, fallback to generic album art
11-17 09:25:06.750 E/AlbumCover( 9080): getArtwork: Exception, fallback to generic album art
11-17 09:25:10.125 E/dalvikvm-heap( 9080): Out of memory on a 180016-byte allocation.
11-17 09:25:10.734 E/dalvikvm-heap( 9080): Out of memory on a 180016-byte allocation.
11-17 09:25:10.796 E/TextureRequest( 9080): No more memory!
11-17 09:25:10.796 E/TextureRequest( 9080): java.lang.OutOfMemoryError
11-17 09:25:10.796 E/TextureRequest( 9080): at android.graphics.BitmapFactory.nativeDecodeFileDescriptor(Native Method)
11-17 09:25:10.796 E/TextureRequest( 9080): at android.graphics.BitmapFactory.decodeFileDescriptor(BitmapFactory.java:568)
11-17 09:25:10.796 E/TextureRequest( 9080): at com.archos.mediacenter.music.cover.AlbumCover.getArtwork(AlbumCover.java:140)
11-17 09:25:10.796 E/TextureRequest( 9080): at com.archos.mediacenter.cover.Cover$CoverTextureRequest.makeBitmap(Cover.java:213)
11-17 09:25:10.796 E/TextureRequest( 9080): at com.archos.mediacenter.cover.TextureProvider$BuildTextureThread.run(TextureProvider.java:74)
11-17 09:25:11.968 E/AndroidRuntime( 9080): FATAL EXCEPTION: main
11-17 09:25:11.968 E/AndroidRuntime( 9080): java.lang.OutOfMemoryError
11-17 09:25:11.968 E/AndroidRuntime( 9080): at android.graphics.BitmapFactory.nativeDecodeStream(Native Method)
11-17 09:25:11.968 E/AndroidRuntime( 9080): at android.graphics.BitmapFactory.decodeStream(BitmapFactory.java:493)
11-17 09:25:11.968 E/AndroidRuntime( 9080): at com.archos.mediacenter.music.utils.MusicUtils.getArtwork(MusicUtils.java:1537)
11-17 09:25:11.968 E/AndroidRuntime( 9080): at com.archos.mediacenter.music.utils.MusicUtils.updateNowPlaying(MusicUtils.java:1762)
11-17 09:25:11.968 E/AndroidRuntime( 9080): at com.archos.mediacenter.music.browser.TrackBrowserFragment.onServiceConnected(TrackBrowserFragment.java:273)
11-17 09:25:11.968 E/AndroidRuntime( 9080): at com.archos.mediacenter.music.utils.MusicUtils$ServiceBinder.onServiceConnected(MusicUtils.java:246)
11-17 09:25:11.968 E/AndroidRuntime( 9080): at android.app.LoadedApk$ServiceDispatcher.doConnected(LoadedApk.java:1068)
11-17 09:25:11.968 E/AndroidRuntime( 9080): at android.app.LoadedApk$ServiceDispatcher$RunConnection.run(LoadedApk.java:1085)
11-17 09:25:11.968 E/AndroidRuntime( 9080): at android.os.Handler.handleCallback(Handler.java:605)
11-17 09:25:11.968 E/AndroidRuntime( 9080): at android.os.Handler.dispatchMessage(Handler.java:92)
11-17 09:25:11.968 E/AndroidRuntime( 9080): at android.os.Looper.loop(Looper.java:137)
11-17 09:25:11.968 E/AndroidRuntime( 9080): at android.app.ActivityThread.main(ActivityThread.java:4424)
11-17 09:25:11.968 E/AndroidRuntime( 9080): at java.lang.reflect.Method.invokeNative(Native Method)
11-17 09:25:11.968 E/AndroidRuntime( 9080): at java.lang.reflect.Method.invoke(Method.java:511)
11-17 09:25:11.968 E/AndroidRuntime( 9080): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:784)
11-17 09:25:11.968 E/AndroidRuntime( 9080): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:551)
11-17 09:25:11.968 E/AndroidRuntime( 9080): at dalvik.system.NativeStart.main(Native Method)
11-17 09:25:13.171 E/dalvikvm-heap( 9080): Out of memory on a 202-byte allocation.
11-17 09:25:13.703 E/dalvikvm-heap( 9080): Out of memory on a 2502-byte allocation.
11-17 09:25:13.789 E/InputDispatcher( 615): channel '416b3548 com.archos.mediacenter/com.archos.mediacenter.music.browser.MusicBrowserActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
11-17 09:25:22.531 E/AlbumCover( 9235): getArtwork: Exception, fallback to generic album art
11-17 09:25:24.156 E/AlbumCover( 9235): getArtwork: Exception, fallback to generic album art
11-17 09:25:28.140 E/AlbumCover( 9235): getArtwork: Exception, fallback to generic album art
11-17 09:25:34.953 E/dalvikvm-heap( 9235): Out of memory on a 202-byte allocation.
11-17 09:25:35.570 E/AndroidRuntime( 9235): FATAL EXCEPTION: ImportWorker
11-17 09:25:35.570 E/AndroidRuntime( 9235): java.lang.OutOfMemoryError
11-17 09:25:35.570 E/AndroidRuntime( 9235): at android.database.CursorWindow.nativeGetString(Native Method)
11-17 09:25:35.570 E/AndroidRuntime( 9235): at android.database.CursorWindow.getString(CursorWindow.java:442)
11-17 09:25:35.570 E/AndroidRuntime( 9235): at android.database.AbstractWindowedCursor.getString(AbstractWindowedCursor.java:51)
11-17 09:25:35.570 E/AndroidRuntime( 9235): at android.database.CursorWrapper.getString(CursorWrapper.java:114)
11-17 09:25:35.570 E/AndroidRuntime( 9235): at android.database.DatabaseUtils.cursorRowToContentValues(DatabaseUtils.java:724)
11-17 09:25:35.570 E/AndroidRuntime( 9235): at com.archos.mediaprovider.MediaStoreImporter.copyData(MediaStoreImporter.java:330)
11-17 09:25:35.570 E/AndroidRuntime( 9235): at com.archos.mediaprovider.MediaStoreImporter.doFullImport(MediaStoreImporter.java:57)
11-17 09:25:35.570 E/AndroidRuntime( 9235): at com.archos.mediaprovider.MediaStoreImportService.doImport(MediaStoreImportService.java:192)
11-17 09:25:35.570 E/AndroidRuntime( 9235): at com.archos.mediaprovider.MediaStoreImportService.handleMessage(MediaStoreImportService.java:163)
11-17 09:25:35.570 E/AndroidRuntime( 9235): at android.os.Handler.dispatchMessage(Handler.java:95)
11-17 09:25:35.570 E/AndroidRuntime( 9235): at android.os.Looper.loop(Looper.java:137)
11-17 09:25:35.570 E/AndroidRuntime( 9235): at android.os.HandlerThread.run(HandlerThread.java:60)
11-17 09:25:37.828 E/TextureProvider( 9235): pause: state error 0
11-17 09:25:37.859 E/libEGL ( 9235): call to OpenGL ES API with no current context (logged once per thread)
11-17 09:26:02.718 E/dalvikvm-heap( 9395): Out of memory on a 202-byte allocation.
11-17 09:26:03.328 E/dalvikvm-heap( 9395): Out of memory on a 112-byte allocation.
11-17 09:26:03.828 E/AndroidRuntime( 9395): FATAL EXCEPTION: ImportWorker
11-17 09:26:03.828 E/AndroidRuntime( 9395): java.lang.OutOfMemoryError: [memory exhausted]
11-17 09:26:03.828 E/AndroidRuntime( 9395): at dalvik.system.NativeStart.main(Native Method)

[SvenC]

@lbocchio
Can you tell me your booting time, please? I had a RMA and I installed at first the 25-release to my HDD-device and now I have a booting time ~2 min. With installing the 26-release, now I have a booting time ~2.15 min. I don't know if it's the HDD-device as this or the OS (incl. the last two updates).

In log-file, I can find two entries...

19:31:17 CPU1: shutdown
19:32:17 request_suspend_state: wakeup (3->0)

19:30:47 CPU1: shutdown
19:31:15 CPU1: booted secondary processo

~1 1/2 min for what? for nothing?