Database Develop

New firmware 4.0.28 (4.0.4) realeased!

New firmware released! :laugh:
Now It's only minor update for 4.0.4.
Code:
Version 4.0.28 - February 18th, 2012
HDMI: avoid interference of CEC detected as DPAD with some games such as Max Payne
Video: fix playback of some MP4 files
Video: fix aspect ratio on some H264 files
Touchscreen panel: ensure on some devices a proper wakeup when powering screen back on
You can get update by OTA (Settings --> About Tablet --> Update firmware (Check Updates)) Or by this link (by use *.aos file).
Download links:
Yandex Disc

Hello !
I'll release soon root version, and later root-deodex version !
So, stay tuned ! :good:

Ok I wait it!

surdu_petru said:
Hello !
I'll release soon root version, and later root-deodex version !
So, stay tuned ! :good:
Click to expand...
Click to collapse
Hmmm root de odex sounds sexy
TrOjAn

I tested it in sitetic benchmark.
Quadrant ~ 4145 marks
Antutu benchmark 3.x ~ 8740 marks
It's more than 4.0.26 firmware, but it's only sintetic tests!

Is this a sign that Archos 101 G9 will not get Jelly Bean?
XS version gets even 4.1.2...

when archos gve us 4.1? when the 5 is out?.. or nevr for g9?
Sent from my ARCHOS 80G9 using xda app-developers app

Here is a quote taken from the Archos Facebook website:
"""
Archos Worldwide Marco Antunes - Unfortunately after many months of analysis and
testing it has been decided that, due to the multiple hardware configurations
available on our G9 range and the complexities these add, we will not release an
Android 4.1 “Jelly Bean” update to the G9 range tablets. The G9 Range, originally
released in the autumn of 2011, running Honeycomb, saw 15 firmware updates taking
it across many versions of Honeycomb and Ice Cream Sandwich, making 4.0.26 the
final firmware that will be provided to this device range.
"""
I assume that the 4.0.26 was a typo because 4.0.28 was released at about the exact same time as the above was posted.
Personally, I'm glad all this nonsense about Jelly Bean is finally over! Since new devices come out just about every 6 months these days now... why would anybody have actually expected Archos to update their (now several years old) G9 tablets? Just about all electronic devices are now considered as "throw away" devices and not expected to even be in use 2 years after they first come out.

55mls said:
(now several years old) G9 tablets?
Click to expand...
Click to collapse
More like a year and a half. At least 4.0.28 seems to work pretty well. It's the first 4.0.x version I'll stick with I think.
You are certainly correct in saying that consumer electronics are EOLed very quickly because the consumer hive mind moves on to the next exciting barely-supported junk without much delay. Thankfully these are open-source devices and so can be improved further, perhaps beyond incompetent Archos abilities.

surdu_petru said:
Hello !
I'll release soon root version, and later root-deodex version !
So, stay tuned ! :good:
Click to expand...
Click to collapse
And a [email protected] v05.... ???????

MrMmmkay after deodex realese, I wiil build my rom with mods.
Mods are ready, and you can install it manualy (go to PM, I upload it for you)

swaaye said:
More like a year and a half. At least 4.0.28 seems to work pretty well. It's the first 4.0.x version I'll stick with I think.
You are certainly correct in saying that consumer electronics are EOLed very quickly because the consumer hive mind moves on to the next exciting barely-supported junk without much delay. Thankfully these are open-source devices and so can be improved further, perhaps beyond incompetent Archos abilities.
Click to expand...
Click to collapse
I just wish my touchscreen worked on my $250 tablet I bought 9 months ago. Archos has been pathetic through this process. I could have bought a nexus 7 and had cash leftover. And the damn thing would work correctly.
Sent from my Galaxy Nexus using xda premium

I had sideloaded flash player after upgrading to ICS and although it is not officially supported by google, it was working great for viewing flash content (e.g. Amazon Instant videos) in certain browsers (Firefox, Opera Mobile, Dolphin). After upgrading to the latest firmware on Wednesday night, I am no longer able to play these videos using the flash player. Things I have tried:
1. Rebooted tablet several times after firmware upgrade (read somewhere that doing so can help clear up any post upgrade playback/plugin issues).
2. Uninstalled and re-installed Adobe Flash using the same apk I had downloaded onto the tablet and used with prior versions of the official ICS on this tablet. (Rebooted couple times between uninstalling and reinstalling for same reason as above - couldnt hurt):
a) Uninstalled Adobe Flash, rebooted (couldnt hurt), cleared cache and data for various browsers, rebooted and re-installed Adobe flash.
However, I am still unable to get flash video (specifically Amazon Instant Videos) working on the table with any of the browsers listed above. Would appreciate if anyone could confirm whether or not this might be due to the new firmware or if there are other browsers that are confirmed working with flash videos on this new firmware.
Thanks,
-Topper

There are multiple variations of 4.0.28
Are you people aware of the fact that Archos has changed their official 4.0.28 firmware file released on their website several times already?
Listed below are the dates I downloaded what was listed as the 4.0.28 firmware, the size that was listed on the website at that time, and the true downloaded file size.
Feb. 25 -- Listed on site: 210,030 Kb -- Actual size: 215,070,152 bytes
Feb. 28 -- Listed on site: 210,040 Kb -- Actual size: 215,080,008 bytes
Mar. 02 -- Listed on site: 210,046 Kb -- Actual size: 215,086,104 bytes
And who knows just which one surdu_petru has been using for his rooted and custom ROM's?
Don't much matter to me anymore though because I've already found out that NO firmware (official from Archos, rooted, or custom ROM's) after 4.0.7 work correctly on my devices anyway.

My tablet not recognizing the aos file anywhere I put it

I downloaded the update this morning , at least they pushed out an update at all ...
Sent from my R800at

nswana said:
My tablet not recognizing the aos file anywhere I put it
Click to expand...
Click to collapse
Hi !
Yes, I know ...you need to reset your device to be able to put .aos file !

216Monster said:
I downloaded the update this morning , at least they pushed out an update at all ...
Sent from my R800at
Click to expand...
Click to collapse
Were did you place the update coz I have tried everywhere nothing is happening and I think i am missing aosupdate APk

55mls said:
Are you people aware of the fact that Archos has changed their official 4.0.28 firmware file released on their website several times already?
Listed below are the dates I downloaded what was listed as the 4.0.28 firmware, the size that was listed on the website at that time, and the true downloaded file size.
Feb. 25 -- Listed on site: 210,030 Kb -- Actual size: 215,070,152 bytes
Feb. 28 -- Listed on site: 210,040 Kb -- Actual size: 215,080,008 bytes
Mar. 02 -- Listed on site: 210,046 Kb -- Actual size: 215,086,104 bytes
And who knows just which one surdu_petru has been using for his rooted and custom ROM's?
Don't much matter to me anymore though because I've already found out that NO firmware (official from Archos, rooted, or custom ROM's) after 4.0.7 work correctly on my devices anyway.
Click to expand...
Click to collapse
Hi !
Root Firmware 4.0.28 was : 215,070,152 bytes :good:
Downloaded right now and you are right : 215.1 MB (215,086,104 bytes)

surdu_petru said:
Hi !
Yes, I know ...you need to reset your device to be able to put .aos file !
Click to expand...
Click to collapse
I just did the reset and still no luck and i cant even go in recovery mode when i press power and + volume

[ROM][P6800][OnHold]Ubuntu-touch dev preview(18.03.2013)

I have put this project on hold for now. I flashed latest Austrian ICS build to my device and continue using it as my Kindle reader on my travels. IF somone manages to fix the two issues with kernel, send me a message and I'll continue working with the repository. But for now I'm not thinking nor touching the subject before Easter. Thank you for participating for now
I've started porting Ubuntu-touch dev-preview to the Galaxy Tab 7.7 (3g). If you do not understand it already, you flash this at your own risk. There is now also a Ubuntu-touch specific device page here: https://wiki.ubuntu.com/Touch/Devices/p6800. I'll try to keep this thread and the Ubuntu devices page as close to each other as possible.
Big thanks to Daniel_hk for helping with boot.img Now It can be booted, but the screen is still black
Also, without working wifi and display, the preview is basically unusable... Next steps should be these:
1. Get wifi drivers working.
2. Get display drivers working.
Code:
[email protected]:/# uname -a
Linux localhost 3.0.15-CM-g1dc3074 #2 SMP PREEMPT Wed Mar 13 00:43:37 EET 2013 armv7l armv7l armv7l GNU/Linux
Repositories:
Latest release tagged with: "v0.3", not tested!
https://github.com/dun1982/android_device_samsung_p6800
https://github.com/dun1982/android_kernel_samsung_p6800
Download
cm-10.1-20130312-UNOFFICIAL-p6800.zip
Daily Ubuntu image: http://cdimage.ubuntu.com/ubuntu-touch-preview/daily-preinstalled/current/
Installation
Install CWM 6.0.2.8
Wipe data/factory reset
Wipe cache partition
Flash cm-10.1-20130312-UNOFFICIAL-p6800.zip to device
Flash quantal-preinstalled-phablet-armhf.zip to device
Reboot
Starting to use
Then it gets interesting (Black sreen for now now Run the following commands in your desktop system:
Code:
adb root
adb shell
ubuntu_chroot shell
You should have now root access inside your tabled. Continue with this wiki next
What works
Ubuntu-touch dev-preview is flashable.
It boots!
Known Issues
Kernel is based to the CyanogenMod/android_kernel_samsung_smdk4210, but it is a mess. So forked it, took code here and there (mostly from locerra's JB build).
Kernel is based 3.0.15 and no newer one available (yet).
Most of the drivers in kernel had to be turned off, because build was not succeeding...
bluetooth: Doesn't work
audio: Dock audio doesn't work.
hwcomposer: HDMI dongle doesn't work.
wifi: Doesn't work.
camera: Doesn't work.
.. and lot of kernel level bugs for sure.
Displaydrivers are not working (yet).
Release notes
Version 0.2 (13.03.2013) - Now it boots, see release notes
Version 0.1 (07.03.2013) - Intial release, nothing works
Credits
BIG THANKS to daniel_hk for solving the boot.img problem for me.
Anyone who has worked previously with the device/kernel source.
locerra (for getting CM10.1 to flashable state).

wowww!!! thank you !test now:victory::victory:

Placeholder for future.

Re: [ROM][P6800]Ubuntu-touch dev preview(02.03.2013)
Not 6810 versión?
AUs

el_campi said:
Not 6810 versión?
AUs
Click to expand...
Click to collapse
I cannot test it for anything else. The kernel sources are from CM10.1 that was in use from locerra, so in theory it should work with i815 and with p6810 as well. But I cannot give you any guarantees...
And also before I get this build to even start with my device, I do not think that sharing image would help anyone. But if you are a developer, I would like to talk with you on issues that I might have missed or done wrong. So contact me

Re: [ROM][P6800]Ubuntu-touch dev preview(02.03.2013)
any update?
Sent from my GT-P6800 using xda premium

Not much. The generated image is missing /data/ubuntu completely and that is the reason why the image does not boot. I got also flu and fewer, so I have had not that much time after the weekend to look on the issues on that.
I'm also waiting if I get any answers from Ubuntu touch emailing list regarding the problem and where to look for answers, but my quess is that it has something to do with the devices fstab file...

Good news everyone!
Just got a very good answer the problem I had with the /data/ubuntu-folder missing from the image. There was no image provided for the actual Ubuntu at all by the build-process...
When I get home from work, I'll try to find time to look into the build process if I can include the actual Ubuntu image to the ready made image and then release it after I get my device to boot. But it seems that I got the right nudge forward for this now :highfive:

Hmpf, still not booting. Now the /data/ubuntu logs are unmodified, which would point towards kernel or fstab-issue (ie. /data/ubuntu is never used...).

Re: [ROM][P6800]Ubuntu-touch dev preview(02.03.2013)
Good job :thumbup::thumbup::thumbup::thumbup::thumbup::thumbup:
Sent from my GT-p6800 using xda premium

Doh... still not working... Any ideas anyone?

Ok, new version build from different repositories (thx, danile_hk for tip).
I'll test the new image this evening when I get back to home, and I have my fingers crossed that I can get the device to boot up and even display something useful. After that I can start looking for ubuntu developemnt

New version did not work, but then Daniel_hk gave me working boot.img. So now I need to find out what the heck is wrong with my repository and fix it so that I can get working boot.img from start and also the device configuration has issues. Both repositories are currently out of sync I'm afraid

dun1982 said:
New version did not work, but then Daniel_hk gave me working boot.img. So now I need to find out what the heck is wrong with my repository and fix it so that I can get working boot.img from start and also the device configuration has issues. Both repositories are currently out of sync I'm afraid
Click to expand...
Click to collapse
Also, without working wifi and display, the preview is basically unusable... Next steps should be these:
1. Get wifi drivers working.
2. Get display drivers working.

It seems that I hit the wall (again) with the mentioned big issues.
For now, I keep some sabbatical from Ubuntu Touch things (ie. I flashed ICS Austria to my device) and use it as my Kindle reader again.
If by miracle I get more info regarding how to get the Kernel working with Ubuntu Touch, then by allmeans I continue working with this project. So far it just seems that making a working image, is out of my hands currently.

At least you had a go. Thanks for your efforts, and hope you might have another crack at it later on.
I'm feeling a little bit that way right now too, and put my ICS kernel on the back burner. I think I'm trying to multitask a little too much at times....
Yep, a break is what you need, maybe some clarity will come after you've had a chance to recharge.
Sent from my GT-I9300 using xda premium

It's very nice to see you took up the big responsibility to make this superb device to be usable again! it has great specs, really. KUDOS bro!!

Any update on this development?

ZhenMing said:
Any update on this development?
Click to expand...
Click to collapse
Not much, I have had no interest to spend time with this topic because I have been very busy IRL. After I get my new house renovated fully and get my job tasks done, I wont be spending much time with this project. Feel free to use any sources provided in this thread to further advance the subject.
But this wont go forward that much, if the GT-P6800 wont get official CM10.1 update...

It works?

l2_hsic fix P4 (GT-P7500, GT-P7501) running CM10.1

===============================================================
Issue closed, read:
http://forum.xda-developers.com/showpost.php?p=42638124&postcount=17
===============================================================
l2_hsic issue
l2_hsic running amok (GT-P7500, GT-P7501) is ONE considerable reason for abnormal battery drain.
The so far known counter measures (HC, Stiffmeister + its xda derivate, WiFi-ROM) do not comply to my requests:
- CM10.1 nightlies
- 3G usage
- no l2_hsic hassle
l2_hsic root cause
Analysis of kmsg files provide a consistent pattern. Function if_usb_suspend(..) from modem_link_device_hsic.c does not call wake_lock_timeout(..) in wakelock.c in case of l2_hsic is running amok.
The missed call to wake_lock_timeout is obviously caused by a non cancellable USB-connection.
It is a single non expiring wakelock, what makes trouble.
Inside of modem_link_device_hsic.c I lost track on further explanations.
Candidate to fix the issue
Since I cannot correct the root cause, I tried to fix its consequence.
Basis is the current pershoot P4 CM10.1 kernel.
There are a few spots in its source code, where one could obtain the so called prevent_suspend_time of a l2_hsic wakelock.
A monitor is installed in such place. It triggers, when a l2_hsic wakelock’s individual prevent_suspend_time exceeds >10s (empirical value).
In this case the function wake_lock_timeout is called, which ignites the wakelock’s expiration.
Next the trigger is reset and the monitoring becomes active again.
As a second and measure of last resort the tab is shutdown, once l2_hsic’s total prevent_suspend_time exceeds >1h (never happened so far).
All these events are logged:
--> /proc/grzwolf shows current status
--> /proc/kmsg is extended by a couple of messages
Verification
The described modified kernel was installed on my Tab months ago.
Since then DS works perfect to me.
Furthermore I did not experience any side effects.
This kernel-mod had been announced at
http://www.android-hilfe.de/samsung...s-10-1n-mit-stock-4-0-4-a-69.html#post5550736
Meanwhile the kernelmod is integrated:
BeeGee(Ganbarou), AAccount(A1 Kernel), kasper_h(Team Infamous/AOKP) and twa_priv(CM10.1/SGT7)
Preconditions for installation
- the kernelmod applies only for P4 devices (GT-P7500, GT-P7501)
- no need to contiue, if you don’t have a l2_hsic issue
- if you continue, you should know what you are doing
- I don’t take any warranty
- after flashing a Nightly ROM, the kernelmod needs to be installed again
- CM10.1 is installed on P4 according to the OP of thread http://forum.xda-developers.com/showpost.php?p=36077123&postcount=1
Kernelmod installation
- comply to the preconditions above
- within CWM make a Nandroid backup of a running isntallation
- copy 'P4 kernel' (see downloads below) to your Tab
- install 'P4 kernel modified' within CWM and check functionality after booting up
- if not ok, restore in CWM your Nandroid backup
Credits
- pershoot (Kernel)
- MapleSyrup (Kernel build)
- nakedninja42 (CM10.1 Installation)
Changelog
Rev. 2013.04.10-19.44
first release
Downloads
- CWM flashable kernel zip, Rev. 2013.04.10-19.44
- md5 sum of kernel zip
- source code
- readme source code

All hail grzwolf! Thank you so freaking much for finally finding the fix that no one could. I now don't need to flash a WiFi ROM to get rid of the l2_hsic issue.
Sent from my GT-P7500 using XDA Premium HD app

Great work, grzwolf!
Did you find the root cause of the wakelock based on your extended logging?
Is it OK for you if I take your code, streamline it a bit (remove logging, renaming methods, ...) and integrate it in the CM kernel?

C-o-M said:
Great work, grzwolf!
Did you find the root cause of the wakelock based on your extended logging?
Is it OK for you if I take your code, streamline it a bit (remove logging, renaming methods, ...) and integrate it in the CM kernel?
Click to expand...
Click to collapse
Root Cause
According to my current testing (next revision kernelmod), I'm almost convinced it's caused by a race condition
between modem and modem interface (most likely the "kill_urb stuff").
Just by adding the extended logging in "if_usb_suspend" seem to have wiped the issue with the missing "wake_lock_timeout".
As next I'm going to switch back to the erroneous behaviour, verifying this theory.
If this approach would stand, the extended logging could be replaced by reasonable delays.
Not impossible, that the whole silly detection & triggering in wakelock.c is not needed.
Usage
That would be fine to me, so no problems at all with code re use.

You mean the issue is fixed by just adding some delays in if_usb_suspend? So you do not enter your wake lock fix at all with the current patch?

C-o-M said:
You mean the issue is fixed by just adding some delays in if_usb_suspend? So you do not enter your wake lock fix at all with the current patch?
Click to expand...
Click to collapse
That's what I'm currently trying out.
I would never had come up with this assumption, without the wish to understand the logic behind.
Since the nature of this presumable race condition is a fickle ***** (if my assumption is correct),
it may take a while to have solid evidence.
Although, it sounds tempting.

Thank YOU!!!
Thanks for this fix grzwolf, works as it should. Now my P7500 is great with cm10.1 and good battery life. :good:
theone

Question ! Do i have to flash source code or just only p4_kernel_2013.04.10-19.44.zip ? Thanks

saigon66 said:
Question ! Do i have to flash source code or just only p4_kernel_2013.04.10-19.44.zip ? Thanks
Click to expand...
Click to collapse
Just the one you mentioned --> p4_kernel_2013.04.10-19.44.zip

CHN Kernel
grzwolf said:
Just the one you mentioned --> p4_kernel_2013.04.10-19.44.zip
Click to expand...
Click to collapse
Since the Chinese Kernel solo, solves the problem why don't you compare the kernels. Hope i'm not ofending you with probably a stupid question. I'm saying this because when i found Stifmeister zip file and solution, i installed the chinese kernel directly via odin, and just overwrited some network files (i presume), and since then, 8 months ago, never seen a wakelock and a battery drain. Some my humble assumption was that the Chinese Kernel has no l2_hsic wakelock, except, when you connect a USB sd card and unmount it without passing through settings.
Hope it helps.
PS: I should have said this first, i'm still on stock...
Great Job anyway..
Thanks

Phibs said:
Since the Chinese Kernel solo, solves the problem why don't you compare the kernels. Hope i'm not ofending you with probably a stupid question. I'm saying this because when i found Stifmeister zip file and solution, i installed the chinese kernel directly via odin, and just overwrited some network files (i presume), and since then, 8 months ago, never seen a wakelock and a battery drain. Some my humble assumption was that the Chinese Kernel has no l2_hsic wakelock, except, when you connect a USB sd card and unmount it without passing through settings.
Hope it helps.
PS: I should have said this first, i'm still on stock...
Great Job anyway..
Thanks
Click to expand...
Click to collapse
Your suggestion is absolutely conclusive and would be definitely worth a follow up.
Afaik only Samsung knows, what sources and settings were used to build this specific Chinese Kernel,
Means, they are very unlikely available. Otherwise the magic would have been unveiled long time ago.

I suppose disassembling the kernel and looking for the specific code where the wakelock is set would be too difficult?
Sent from my GT-P7100 using Tapatalk 4 Beta

doctorow said:
I suppose disassembling the kernel and looking for the specific code where the wakelock is set would be too difficult?
Sent from my GT-P7100 using Tapatalk 4 Beta
Click to expand...
Click to collapse
At least for me.
Afaik it would end up with machine code / assembler language.
Another tool were required to translate it into C.
Even then, there were no really meaningful function and variable names.
Means, one couldn't easily compare this with existing sources.
Finally the whole exercise could result in already known source code.
Not impossible, that the "magic of the China-Kernel" is caused by very specific compiler or optimization settings, which cannot reverse engineered.
Too many if and may be ...

Comparing kernel sources is a very good idea.
Pershoot's p4 kernel is based on Samsungs kernel sources for GT-P7510, Opensource Update 2, released in April 2012 (AFAIR).
For the p5 kernel, I always rebased pershoot's kernel to the latest sources (to GT-P7300_HK_ICS_Opensource_Update1.zip in September, to GT-P7300_ICS_Opensource_Update1.zip in December). No one has ever reported the l2_hsic bug on CM for p5. Neither on CM10 (where I used the chinese kernel sources), nor on CM10.1 (updated to the official ICS sources). But the bug occured for example on AAcount's kernel which isn't rebased. So Samsung seems to fixed the issue in the kernel instead of doing some "magic hacks".
I commited a lot of different p4/p5 kernels to github to make it easier to compare them. I guess you'd like to take a look on those changes:https://github.com/cmorlok/android_kernel_samsung_p5/tree/P7300_ICS_U1/drivers/misc/modem_if

Great, of course I would. Thanks.
Just kdiffed modem_link_device_hsic from your recent P5 against P4, there are non trivial differences.
I'll give it a try right away.

hi c-o-m and grzwolf.
can you please furnish the latest code to this implementation?
any SOD as a result? any other weird behavior?
i'd like to get this in to mainline, if no issue.
thx

pershoot said:
hi c-o-m and grzwolf.
can you please furnish the latest code to this implementation?
any SOD as a result? any other weird behavior?
i'd like to get this in to mainline, if no issue.
thx
Click to expand...
Click to collapse
Following C-o-M's advise with the code review between P4 and P5 modem interface was the breakthru.
The P5 modem interface has a number of non trivial changes compared to its P4 counterpart (--> git format-patch attached).
Although I didn't understand the details, I gave them a try and replaced the P4 modem interface from your github repo completely with the one coming from P5.
Non of the usual test cases made any problem regarding l2_hsic or anything else.
- long time operation
- charging w/o reboot
- USB-drive operation
- Wifi
- 3G
Currently I'm on the 20130604 CM nightly + KernelMod, means 12 days in sequence since last reboot.
BTW: Neither a single SOD, nor any other weird behavior.
To my opinion, the l2_hsic amok issue could be finally closed.
Hail to C-o-M.

Do you think this will get merged into where ever it is that the cm team get their kernals from?

grzwolf said:
Following C-o-M's advise with the code review between P4 and P5 modem interface was the breakthru.
The P5 modem interface has a number of non trivial changes compared to its P4 counterpart (--> git format-patch attached).
Although I didn't understand the details, I gave them a try and replaced the P4 modem interface from your github repo completely with the one coming from P5.
Non of the usual test cases made any problem regarding l2_hsic or anything else.
- long time operation
- charging w/o reboot
- USB-drive operation
- Wifi
- 3G
Currently I'm on the 20130604 CM nightly + KernelMod, means 12 days in sequence since last reboot.
BTW: Neither a single SOD, nor any other weird behavior.
To my opinion, the l2_hsic amok issue could be finally closed.
Hail to C-o-M.
Click to expand...
Click to collapse
cool thx grzwolf.

Lol, shows how much I pay attention. I completely missed pershoots post.
Edit:
Ok, looks like this should be in the nightlies now....
http://forum.xda-developers.com/showpost.php?p=42680093&postcount=1875

[Q] New official JB release?

Has anybody taken a look at the new official JB release that popped up at http://sbf.droid-developers.org/cdma_maserati/list.php ? (Although, I can't access it currently)
It's been mentioned on another thread (http://forum.xda-developers.com/showthread.php?t=2277830 ) regarding the ability to root, but it doesn't look like it's been looked at in any depth whether it includes any fixes, etc. The build date has changed to the 5th April, and the version is 9.8.20-72_VZW-18-2.
Cheers,
Steve.

This should probably be in q&a section... but yeah I wonder what is in it too... either way, I'm pretty happy sitting on eclipse 1.0.6 right now
Xoom'd using the XDA-Developers Android app

alex94kumar said:
This should probably be in q&a section... but yeah I wonder what is in it too... either way, I'm pretty happy sitting on eclipse 1.0.6 right now
Xoom'd using the XDA-Developers Android app
Click to expand...
Click to collapse
You could be right regarding the location, apologies if people object - I just thought the ROM guys would probably be the ones most likely to be all over it.

File Mirror
FWIW - I found that droid-developers.org seemed a little hit and miss, so I've set up a private file mirror for this new release. If somebody wants access to it, then just PM me. I'm trying to sort out a public mirror too, and will update this post when/if I get that sorted out.
Cheers,
Steve,

I am uploading cdma_maserati/cdma_maserati_9.8.2O-72_VZW-18-2_1ff.xml.zip
to my http://d-h.st/users/sd_shadow/?fld_id=12041#files
via remote url upload, usually doesn't take very long, quite a bit faster than uploading from my pc

This same version upgrade for XT926 HD appeared and was said to be a bugfix for the 4.1.2 OTA and that another more significant update would appear shortly for all devices but still remain 4.1.2 and would include Isis.
So we should expect to see a couple of OTAs pushed out on accelerated schedule that will match this XML file and the subsequent update.

sd_shadow said:
I am uploading cdma_maserati/cdma_maserati_9.8.2O-72_VZW-18-2_1ff.xml.zip
to my http://d-h.st/users/sd_shadow/?fld_id=12041#files
via remote url upload, usually doesn't take very long, quite a bit faster than uploading from my pc
Click to expand...
Click to collapse
Nice one - I'm currently 66% of the way through uploading to FileDropper (which I've never used before, but it was free, and didn't require sign up).
cellzealot said:
This same version upgrade for XT926 HD appeared and was said to be a bugfix for the 4.1.2 OTA and that another more significant update would appear shortly for all devices but still remain 4.1.2 and would include Isis.
So we should expect to see a couple of OTAs pushed out on accelerated schedule that will match this XML file and the subsequent update.
Click to expand...
Click to collapse
So is the "more significant update" meant to be coming after this April 5th release?
Cheers,
Steve.

It's safe for now...
StevePritchard said:
Nice one - I'm currently 66% of the way through uploading to FileDropper (which I've never used before, but it was free, and didn't require sign up).
So is the "more significant update" meant to be coming after this April 5th release?
Cheers,
Steve.
Click to expand...
Click to collapse
Yes, and I just flashed the boot, system and radio images from the MR2 XML and then rerooted using razr_blade.
So, we are safe to use this file to upgrade the firmware without any loss of root or any other issues.
The secure version did not increment so it is also possible to revert to the prior -18 release without risk of soft bricking.
This follows the pattern of the update for the HD and will likely be the same for the other devices that just recieved 4.1.2 in this cycle.
The next update is the one the will include ISIS and may also have security enhancements that will need to be carefully scrutinized.
That is conjecture on my part, at this stage, we don't know.

It would be nice to know what changes the release addresses. My hope is that it sorts out the hardware keyboard problem of unsticky shift keys in some applications.
Cheers,
Steve

[ROM] 5.0.* CyanogenMod 12.0

Hi, if anyone would like to run a 5.0.1 Google OS on a Archos G9 80S device (and currently basically verified only with this), download and extract the file
18_03_2015-20_58_50.7z
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 for the first installation. Updating a existing installation (same major version) doesn't require this step !).
- 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 at least ~20 minutes for the first run!
What's new ?
------------ since 18_03_2015-20_58_50 -------------
tiler size modifications within kernel, suggested by stevemp (thanks!)
CM updates.
------------ since 15_03_2015-22_26_59 -------------
Netflix and widevine fixes from stargo (thanks!)
CM updates.
------------ since 09_02_2015-22_26_59 -------------
Only CM updates.
------------ since 12_12_2014-21_41_41 -------------
Initial release.
Kernel got some zram optimizations.
Rebuild: All used revisions for this release are stored in a separate folder in the archive.
Additions:
Archos Control Panel App from @mordesku: http://forum.xda-developers.com/showpost.php?p=47789812&postcount=88
Thanks: @stargo @Hashcode @trevd
@CM community @all the cool omap4 hackers where I taken some code and inspirations !!!
Without these peoples, It would not so easy to make some (working) builds of the CM-12.0.
Archive:
15_03_2015-22_26_59.7z
12_12_2014-21_41_41 / 12_12_2014-21_41_41 (devHost)
09_02_2015-22_26_59.7z
XDA:DevDB Information
Archos G9 CyanogenMod 12.0, ROM for the Archos Gen9
Contributors
Quallenauge
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: Cyanogenmod
Version Information
Status: Alpha
Current Beta Version: 12_12_2014-21_41_41
Created 2014-12-12
Last Updated 2015-03-18

Dankeschön
I now understand why TI exited the mobile SOC market - How can they expect to sell new stuff when the OMAP4xxx just won't die!
I shall give this one a whirl, It'll be good to get my archos off of the stock ICS.
I'm assuming you've dropped the recovery nonsense for that moment then?
is selinux off?
Is adb on a first boot? as I would recommend that folks leave it hooked up the computer after flashing that
way you can run adb logcat so you know what is going on. It sure beats watching a boot animation for ~20 minutes.
IIRC the 2012 nexus 7 took about 10 Minutes to boot so it's not far off.
I see you forked hotplugd! Let me apologize for the code quality, I was young and foolish and didn't know what I was doing ..
I think I might revisit it at some point or at least delete it lol
Anyway If I've got a bit of time / motivation I might have to have a cheeky hack on this , now that you've done all the hard work! .
I hope you don't mind but I've also given the file some re-hosting love just uploading it to devhost and androidfilehost too. I figured the space might aswell get used for something useful.. I'lll post the links when it's complete.:good:
Hack On! :good:
trevd
@Quallenauge dev-host link. If you want to add it to the first post. http://d-h.st/96J

Installed and i must say it's working really good :good:

schwatter said:
Installed and i must say it's working really good :good:
Click to expand...
Click to collapse
Hahahah! BI ZAR! I check the forum for my Archos 101 Gen9 Turbo once every X months, and checked it today and see LOLLIPOP / CM12?! GREAT!
And whats the status? I use the tablet a lot still, so what is NOT working?
Edit: Flashed it to a Archos 101 Gen9 Turbo, and all is working, and fast as hell. GREAT!

I came from Freezenook's ROM BUILD7 (VERY happy user) but now tried this:
A MA ZING!
How fast and cool this Lollipop is on our (old) Archos (101) Gen9 (Turbo) tablet!!!
For now only compliments and almost everything seems to work, and this is a major and recommended step! Great OS this Lollipop!
Tested
Speed: Good (17.106 AnTuTu 5.3)
Sound/Video: Yes
Touch: Very good
Camera: Yes
Battery: Good
Size: Lot of free space (3 - 4 GB free!)
Memcard: NOT TESTED YET
USB: Yes (with Archos Panel app (USB & deep sleep))(USB storage works)
MicroUSB: Only charging (no devices?)
HDMI: NOT TESTED YET
Headphone: Yes (low volume though)
Apps: Some apps I normally use on my tablet and phones (KitKat or older) are not (yet?) compatible, and cannot install. I really miss some, like Archos Video (Free)(MediaCenter.apk). Is it possible to port this APK to our new Lollipop, I would love that. And the other apps are just not there yet I guess (busy making them Lollipop compat)?

Thanks a lot !!

Supergeil!!!
Still amazing to see that you're still at it @Quallenauge
I will definitely flash it as soon as I have time.
The only concern I have is the USB Port. Does it stil work in 5.0 ? For me it didnt in 4.4, so I flashed back as I needed my Archos to read my Media USB-HDD. I have a 101S btw.
Well as soon as I have flashed it, I am going to test it and try a few things, hope I'll get it working :fingers-crossed:

Hi trevd!
trevd said:
I'm assuming you've dropped the recovery nonsense for that moment then?
Click to expand...
Click to collapse
This is not a "nonsense". But it doesn't reflect my current needs. It would be cool to have a standard recovery image to format the data partition with f2fs (The kernel should support it right now!).
trevd said:
is selinux off?
Click to expand...
Click to collapse
Yes. Currently I doesn't know how to enable selinux rules, because "rootfs" isn't the mounted loop device but the "real" root. So the file nods are forced to "ubject_r:unlabeled:s0" which doesn't fits.
trevd said:
Is adb on a first boot? as I would recommend that folks leave it hooked up the computer after flashing that
way you can run adb logcat so you know what is going on. It sure beats watching a boot animation for ~20 minutes.
Click to expand...
Click to collapse
Yes, ADB is turned on by default. I don't like it, when my device doesn't be verbose
trevd said:
I see you forked hotplugd! Let me apologize for the code quality, I was young and foolish and didn't know what I was doing ..
I think I might revisit it at some point or at least delete it lol
Click to expand...
Click to collapse
Yes, the old binary is bound to an older libsigchain.so. So I had to recompile it. The code quality is far better than my output So thanks for your work!
I have an issue with the ril implementation. Mobile signal is turned on, but the datakey pppd stuff is not called. Do you have an idea whats going wrong - where can I look.
Should I use your implementation from android_hardware_ril_libarchos_ril ?
trevd said:
@Quallenauge dev-host link. If you want to add it to the first post. http://d-h.st/96J
Click to expand...
Click to collapse
[/QUOTE]
Done. Thanks!

trevd said:
Dankeschön
I now understand why TI exited the mobile SOC market - How can they expect to sell new stuff when the OMAP4xxx just won't die!
I shall give this one a whirl, It'll be good to get my archos off of the stock ICS.
I'm assuming you've dropped the recovery nonsense for that moment then?
is selinux off?
Is adb on a first boot? as I would recommend that folks leave it hooked up the computer after flashing that
way you can run adb logcat so you know what is going on. It sure beats watching a boot animation for ~20 minutes.
IIRC the 2012 nexus 7 took about 10 Minutes to boot so it's not far off.
I see you forked hotplugd! Let me apologize for the code quality, I was young and foolish and didn't know what I was doing ..
I think I might revisit it at some point or at least delete it lol
Anyway If I've got a bit of time / motivation I might have to have a cheeky hack on this , now that you've done all the hard work! .
I hope you don't mind but I've also given the file some re-hosting love just uploading it to devhost and androidfilehost too. I figured the space might aswell get used for something useful.. I'lll post the links when it's complete.:good:
Hack On! :good:
trevd
@Quallenauge dev-host link. If you want to add it to the first post. http://d-h.st/96J
Click to expand...
Click to collapse
nilse said:
Supergeil!!!
Still amazing to see that you're still at it @Quallenauge
I will definitely flash it as soon as I have time.
The only concern I have is the USB Port. Does it stil work in 5.0 ? For me it didnt in 4.4, so I flashed back as I needed my Archos to read my Media USB-HDD. I have a 101S btw.
Well as soon as I have flashed it, I am going to test it and try a few things, hope I'll get it working :fingers-crossed:
Click to expand...
Click to collapse
External USB drive isn't supported right now. I will have a look, when I have some free time ( and after fixing the RIL mobile data connection stuff ).

Quallenauge said:
Hi, if anyone would like to run a 5.0.1 Google OS on a Archos G9 80S device (and currently basically verified only with this),
Click to expand...
Click to collapse
Wow, excellent! Thank you!
Could you please, write what you know that definitely doesn't and does work, as you did for older CMs?
Does ART work? Could CM 10.2 be updated to 12, or should we erase everything like with clean CM installation? HDMI?

@nilse: Yes USB (inc drives/storage) works (via Archos Panel app)!
@Bor-ka: Always do a full format/erase/factory settings etc, for SURE with a major leap like CM11 > CM12 or MORE!!
See my older post for a test of all hardware etc!
And again: Some apps I normally use on my tablet and phones (KitKat or older) are not (yet?) compatible, and cannot install. These apps are just not there yet I guess (busy making them Lollipop compat)?
I really miss some, like Archos Video (Free)(MediaCenter.apk). Is it possible to port this APK to our new Lollipop, I would love that!

thank you again for your great work.
Works on 80g9H 512 mb ram.
will test more functions and edit this post later.

@hackwerk, thanks!
For some reason unknown to me, there is no "export partition" in my SDE, so reformatting and copying to the /local/ is a little bit painful to me - should do it with adb shell.
But anyway, Archos Video Player is a show stopper for me. Since it is the only player that can natively play 720p/1080p movies on this tablet via DLNA/Samba. Tried MX player with latest codecs - no luck.
All
Did anybody compare deep sleep in CM with the stock ROM?
IIRC deep sleeped tablet with a stock ROM (4.*, 3.*) could lose only about 10 battery _a_week_ if not used. May be my memory deceives me, of course. But with CM 10.2 and no background tasks it drops by ~ 10% a night. (Didn't try Wakelock and Greenify though)

Bor-ka said:
@hackwerk, thanks!
For some reason unknown to me, there is no "export partition" in my SDE, so reformatting and copying to the /local/ is a little bit painful to me - should do it with adb shell.
But anyway, Archos Video Player is a show stopper for me. Since it is the only player that can natively play 720p/1080p movies on this tablet via DLNA/Samba. Tried MX player with latest codecs - no luck.
All
Did anybody compare deep sleep in CM with the stock ROM?
IIRC deep sleeped tablet with a stock ROM (4.*, 3.*) could lose only about 10 battery _a_week_ if not used. May be my memory deceives me, of course. But with CM 10.2 and no background tasks it drops by ~ 10% a night. (Didn't try Wakelock and Greenify though)
Click to expand...
Click to collapse
SDE: This ia an easy alternative way of installing the ROM (which I used)!
Video: Have you tried Skifta (good for network!) or other majors, like GoodPlayer, MediaPlayer Classic or the brand new official VLC Player (and thus MX Player))?
Maybe in combination with the "All Codecs for Archos Video" app?? Must be possible!
And maybe / I hope we can 'port' the MediaCenter.apk to Lollipop!
Battery: Is already good, but everyone talks about an app called Lux! And Greenify.
But yes Deep Sleep can be enabled in this ROM in the Archos Panel app too.
And maybe these famous mods can help too ( @Quallenauge: Checked them already I think?)?

hackwerk said:
SDE: This ia an easy alternative way of installing the ROM (which I used)!
Click to expand...
Click to collapse
Unfortunately I do not have "Enter the SDE menu on your device and select export data partition," in SDE.
See here, with screenshot http://forum.xda-developers.com/showpost.php?p=57243821&postcount=2
For video thanks, I'll try. Completely forgot about VLC. Tried MX already, it plays Ok from the internal memory/SD but gloriously fails over the network.
What Lux does is automagically lowers screen brightness, Yes, it is very useful app, but it will lower battery drain in the active mode, not in sleep when the screen is off. And it has a bad habit on my current cm10 installation - sometimes it restarts when I'm reading a pdf book at night (low memory?) and I get some two seconds of full brightness in my eyes. Ouch.. I think I'd revert back to manual "dimmer" or "blue light filter" and manual brightness adjustment.
What is strange, users at our local forum report that 5.0 is slower than the stock (?!) ROM on 80S 1.5 Turbo (4460) / 1GB RAM. I wonder what it will be like on my 1.2 (4430) / 512 RAM..

Thanks Quallange and all of you who helped him I saw your progress with 5.0 on github and I wanted to compile it myself but yeah I didn't had space for that sadly, I wanted to ask you flr it but then I see now that you got a cm12 thread when I am tomorrow home from school I will flash this :good:
Edit:
This song describes my 5.0 feeling:
http://youtu.be/p8sZcmQr6KY
It works till now pretty good. I am having the 512mb turbo version but after disabling things that I don't use it runs all smooth :good: o

I installed this Rom on my 101 g9 with 512 MB RAM.
It s like a new device. A lot less lagging and better ui response.
Only thing i found is that the keybord hides every now and then when i want to type some text.
Thanks a lot for this masterpiece of work *like*
Sent from my SM-N7505 using XDA Free mobile app

biggoof75 said:
I installed this Rom on my 101 g9 with 512 MB RAM.
It s like a new device. A lot less lagging and better ui response.
Only thing i found is that the keybord hides every now and then when i want to type some text.
Thanks a lot for this masterpiece of work *like*
Sent from my SM-N7505 using XDA Free mobile app
Click to expand...
Click to collapse
I agree, much more snappy than CM11. I've also had the keyboard hiding issue (stock and Swype). Thanks for keeping the G9 alive Quallenauge :good::good:

G9 80H
i installed the rom but it places data on internal storage. hard drive is placed at /storage/sdcard1 and is read-only
how can i place data on the hard drive?
Note: besides the internal storage issue, the rom runs nicely.

Hi Quallenauge.
Realy magic this ROM, many thanks.
If with JB sometime I have only 80 MB RAM free and with KK 145, now I have over 200 !!!
But I have a problem, app ( iGO ) can't write on external card.
Tried with 3 different SDFix and manually in system/etc/permissions/platform.xml
With Root Explorer I can copy, but can't modify permision.
There is a solution to this problem ?
Thanks in advance.