Database Develop

[ROM] Stock Archos Firmware 4.0.28 (file version of 2nd Mach 2013) | Root version !

Hi all,
This is the rooted version of the stock firmware 4.0.28 published the 2nd Mach 2013 on Archos website.
As you know, Archos release 3 versions of the last firmware 4.0.28:
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
surdu_petru rooted the first file version and had no time to root the last file version.
With this version, there was a bug during the boot: black screen and boot logo Archos for 3 sec just before the loock screen.
This issue is corrected in the firmware of the 2nd March.
So, with surdu_petru help, and with letama's scripts, i built a rooted firmware based on the 2nd March file.
Download :
please download from here all necessary files :
archos.ext4.update
zImage
initramfs.cpio.lzo
Archos_4.0.28_20130302.zip
Mirror:
Archos_4.0.28_20130302.zip
Installation :
connect USB cable ;
unzip Archos_4.0.28_20130302.zip into Archos_4.0.28_20130302 directory
copy archos.ext4.update in your device, or > adb push archos.ext4.update /mnt/storage
go to recovery SDE and Remove android kernel if you have already installed any official firmware !
go to Flash kernel & Initramfs and copy here zImage and initramfs.cpio.lzo from ( Archos_4.0.28_20130302)
Ok ! ... & wait to boot !
Now you have rooted the last Archos Firmware 4.0.28 - Android 4.0.4 !!!
Important :
1)Busybox 1.20.2r2 from linusyang is installed in /system/bin/
2)I used SuperSU from Chainfire for this release instead of Superuser.
So, after the first boot, you need to launch SuperSU in order to complete its installation.
The application will popup "SuperSU need to be upgraded. Continue?"
Click YES
On the new window, choose "NORMAL", and then click "YES" when the installation is succeed.
Best Regards.
SirOch

Hello.
Great job. I will replace my rom to this build.
Thanks.

freezenook said:
Hello.
Great job. I will replace my rom to this build.
Thanks.
Click to expand...
Click to collapse
You are welcome
Good luck for your ROM :good:

download impossible
SirOch said:
Hi all,
This is the rooted version of the stock firmware 4.0.28 published the 2nd Mach 2013 on Archos website.
http://uptobox.com/2rsli69gi9sy
SirOch
Click to expand...
Click to collapse
Hi,
i cannot download the firmware from your file hoster. Any other way to get the file? Can anybody share with me?
regards

4carlos said:
Hi,
i cannot download the firmware from your file hoster. Any other way to get the file? Can anybody share with me?
regards
Click to expand...
Click to collapse
Hi,
I added a mirror to hotfile :good:
Regards.
David

Nice
SirOch said:
I added a mirror to hotfile :good:
Click to expand...
Click to collapse
I got it.
Thanks!
Carlos

4carlos said:
I got it.
Thanks!
Carlos
Click to expand...
Click to collapse
good :good:
happy for you

Someone put file @ dropbox or else...
Very unpleasure those lame hotfile.com and other.!!!!

third revision is much better!
SirOch said:
good :good:
happy for you
Click to expand...
Click to collapse
firmware 4.0.28 / Mar. 02 fixes for me
- boot animation work again
- wifi is stable again - random disconnects are gone
- indexing of files during start up is much shorter
use 4.0.28 / Mar. 02 instead of 4.0.28 / Feb. 25 if you have the same problems from above :good:
in general it's nearly by my favorite 4.0.7.
regards
4carlos

4carlos said:
firmware 4.0.28 / Mar. 02 fixes for me
- boot animation work again
- wifi is stable again - random disconnects are gone
- indexing of files during start up is much shorter
use 4.0.28 / Mar. 02 instead of 4.0.28 / Feb. 25 if you have the same problems from above :good:
in general it's nearly by my favorite 4.0.7.
regards
4carlos
Click to expand...
Click to collapse
Hi,
Thank you for your feedback :good:
David

SirOch said:
As you know, Archos release 3 versions of the last firmware 4.0.28:
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
surdu_petru rooted the first file version and had no time to root the last file version.
With this version, there was a bug during the boot: black screen and boot logo Archos for 3 sec just before the loock screen.
This issue is corrected in the firmware of the 2nd March.
Click to expand...
Click to collapse
Let's clarify things here... "as you know" is bogus crap... **I AM THE PERSON** that first posted any info about there being 3 different versions with the SAME firmware number (both here and over on archosfans.com). Very few people would actually know about it otherwise.
Second, you are also wrong about the boot screen fix. That WAS already in the Feb. 28 Archos firmware. I really do not know what the heck they changed between that one and the last release (I could not find anything at all that worked different other than the file size).
As such, the ONLY thing you got right is the fact that surdu_petru (as always) rushed out a firmware far to quickly and (since he no longer even has an Archos G9, can't even test it).
I DO appreciate your effort in making a more 'current' rooted version available for those people that 'think' it is worth having though. So, one thumb up, and one thumb down LOL.

i wonder
55mls said:
I really do not know what the heck they changed between that one and the last release (I could not find anything at all that worked different other than the file size).
Click to expand...
Click to collapse
Hmm, nobody said that surdu_petru did a bad job.
Maybe you could not find differences between the first and the third version of firmware, but the result is different (for me).
The firmware of 2nd march fixes 2 issues on my Archos 101 G9 that comes with the 1st rev. and i never had before and 1 older problem :
- Bootanimation,
- WiFi-Disconnections (faced up with 1st revision, always stable in the past),
- Endless file indexing after reboot since 4.0.26 (decreases from about 4 minutes to few seconds) and my tablet is now much faster ready to work.
I had/have no pictures, videos, music or other media files on my tablet.
I'm happy now to have my tablet back without (small) issues.
regards and thanks to all for the work
4carlos

Thanks for posting this rom. I went from the latest stock to the rooted 4.0.7, than to this rooted 4.0.28.
I will now see how things run rooted. Thanks again. :good:

4carlos said:
Hmm, nobody said that surdu_petru did a bad job.
Click to expand...
Click to collapse
I did not say, nor did I ever mean to imply that surdu_petru did a bad job (with any firmware he has released). What I WAS saying though is that he rushes out new releases within hours of any official Archos firmware release WITHOUT knowing what flaws are in the official firmware first. And, now he no longer even has a G9, so he can not even check problems in the official firmware anymore.
Just never made much sense to be spitting out new rooted versions BEFORE people even had a chance to report the flaws and problems with the official stock Archo version first. Anyway...
Maybe you could not find differences between the first and the third version of firmware, but the result is different (for me).
Click to expand...
Click to collapse
I did not say between the 1st and the 3rd. What I did say is that the 2nd one fixed the boot animation and I could not find anything else that worked any differently between the 2nd and the 3rd (other than the file size being different).
If anyone knows what else Archos changed/fixed in the 3rd one I'd love to hear about it? Of course, it WOULD be much nicer if Archos would be more honest and actually post that information in their change log to start with.

I am having some issues with this rom. Wi-fi is unable to connect if I used my Inet at work unless I did a reboot. When I returned home, it auto connected just fine. Some apps are dropping out unexpectedly like Asphalt 6 and Nook. I will have to keep playing with it and see what else happens.

Tweakurr said:
I am having some issues with this rom. Wi-fi is unable to connect if I used my Inet at work unless I did a reboot. When I returned home, it auto connected just fine. Some apps are dropping out unexpectedly like Asphalt 6 and Nook. I will have to keep playing with it and see what else happens.
Click to expand...
Click to collapse
Oh cheese I'm really sorry to hear that... NOT. I may come off sounding rude and obnoxious, but the fact of the matter is that ANY firmware after 4.0.7 is just horrible GARBAGE. Many people do not notice all the very little tiny flaws in the newer 4.0.2x firmware versions, but if you are seriously using you device for MANY things, well....
Various games do not run correctly, or the graphics do not display correctly... or the sound sometimes works, sometimes it doesn't, other times just quits somewhere in the middle.
Sometimes, even playing a video file is messed up... plays slightly faster than it should. There ARE a number of other things, but I won't list them all here... anyway...
I will not say that 4.0.7 was ever 100% perfect, but it did NOT have all the little idiot annoying flaws that are in the 4.0.2x firmware. Guess SOME PEOPLE don't do much more than web surffing, e-mail, or reading e-books. For those of us that do OTHER THINGS the flaws start showing up rather quickly.
I assume at some point the MOD's here will just start deleting my posts, but until they do I am going to keep repeating what I have said... any firmware above 4.0.7 is just PURE GARBAGE! Don't know why anyone would want it (official or rooted versions).

back to 4.0.7
i'm back on 4.0.7!
tired with nightly reboots, reboots during work. reboot within anywhere. my next tablet comes from anywhere but not from archos.i agree with @55mls and 4.0.7 should be the last firmware for my archos until it dies.
a disapointed customer

The problem with these devices is said to be that there are many hardware revisions. So some people see bugs that others do not. It's probably something to with hardware drivers not behaving identically across all revisions, or that some revisions simply have hardware problems. I've been on 4.0.28 for months and have been fine with it. 4.0.7 has annoying wifi problems on my 80 G9.
I would give Archos another chance but only after carefully reading the forums for the device. My 80G9 experience really hasn't been that bad, but that's mostly because I just got it 4 months ago and so didn't have to deal with the initial year of total **** firmware releases. I waited because 1) I had a Nook Color 2) I had read the forums early in 80G9 release days and saw it was a disaster.

swaaye said:
The problem with these devices is said to be that there are many hardware revisions. So some people see bugs that others do not. It's probably something to with hardware drivers not behaving identically across all revisions, or that some revisions simply have hardware problems. I've been on 4.0.28 for months and have been fine with it. 4.0.7 has annoying wifi problems on my 80 G9.
Click to expand...
Click to collapse
Maybe you are right, but 4.0.7 was the best for my 101G9 (first Generation, delivered with HC). Torture starts with 4.0.25 and 4.0.28 was much better, but it's not STABLE on my device. Unusable for me.
swaaye said:
I would give Archos another chance but only after carefully reading the forums for the device. My 80G9 experience really hasn't been that bad, but that's mostly because I just got it 4 months ago and so didn't have to deal with the initial year of total **** firmware releases. I waited because 1) I had a Nook Color 2) I had read the forums early in 80G9 release days and saw it was a disaster.
Click to expand...
Click to collapse
The 101G9 was'nt my first device. I had a 101G8 before and changed 3 times(!) because the USB-Connector did not work. Allways broken after view weeks and the second device did not charge properly. Bad hardware design i guess and I hoped the G9 was better, but it is not really! GPS did not work from the first day on until now, WiFi was problematic too (with Honeycomb) and the firmware? Some problems seems fixed, but i got new trouble every time with other things. I can accept small glitches but not reboot orgies even the device is untouched or is charging over night. My G9 lives a life of its own.
That's my experience. I surrender after 4 years. Archos, take my money and run.

Cyanogenmod 10.1 is looking really good. There are a few bugs left yet though. It could turn out to be the best firmware available. It's ridiculous that Archos said 4.2 on G9 was impossible.

[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.

[N910F][COH4/POI4][KNOX 0x0] Unofficial, re-packed Lollipop firmwares (multi CSC OXA)

I have decided to create this thread due to extraordinary success of my unofficial builds that I recently put in this thread
Main properties:
- PC Odin flashable (*.tar.md5 file)
- pure stock, NOT rooted, the only change is replaced CSC pack (unbranded multi CSC OXA package instead of original)
- contains CSC: BTU, CPW, DBT, ITV, KOR, XEF, XEO
- can be flashed on ANY N910F without a pit file
- it will NOT trip KNOX if you still have 0x0
Downloads:
>> N910FXXU1COH4_N910FOXA1BOC3_alexndr.7z << (Android 5.1.1)
>> N910FXXU1POI4_N910FOXA1BOC3_alexndr.7z << (Android 5.0.1)
>> Recent unofficial builds for SM-N910F <<
Important notes:
- I do not have much time to expand this thread, so only multi CSC OXA builds will be available here
- I am not able to fix any bugs as all builds contains only ORIGINAL, unmodified partition images (to let you keep KNOX 0x0)
- Unofficial builds means => no OTA updates available (to restore OTA updates you just need to fash OFFICIAL firmware from Sammobile)
- In theory it is not possible to brick your phone or trip KNOX using these builds, but I have to write it (just in case) - I am not responsible for anything that will happen to your phone

_alexndr said:
I have decided to create separate thread due to the extraordinary success of my unofficial compilation that I recently put in this thread
Main properties:
- PC Odin flashable (*.tar.md5 file)
- pure stock, NOT rooted, the only change is replaced multi CSC pack (putted multi CSC OXA package instead of original)
- contains CSC: BTU, CPW, DBT, ITV, KOR, XEF, XEO
- can be flashed on ANY N910F without a pit file
- it will NOT trip KNOX if you still have 0x0
Downloads:
>> Recent unofficial builds for SM-N910F <<
Important notes:
- I do not have too much time to expand this thread, so only multi CSC OXA builds will be available here
- I am not able to fix any bug as all builds contains only ORIGINAL, unmodified partition images (to let you keep KNOX 0x0)
- Unofficial builds means => no OTA updates available (to restore OTA updates you just need to fash OFFICIAL firmware from Sammobile)
- In theory it is not possible to brick your phone or trip KNOX using these builds, but I have to write it (just in case) - I am not responsible for anything that will happen to your phone
Click to expand...
Click to collapse
thanks! it works perfectly

I'm glad you decided to start a new thread. The other one is just TOOO LONG! Great work, keep it up You rock!

i dont understand it... why would we flash this instead of the original firmwares on sammible ?
just asking

Racinghart91 said:
i dont understand it... why would we flash this instead of the original firmwares on sammible ?
just asking
Click to expand...
Click to collapse
because it can happen that in your country the latest firmware is available 1 month after another lucky country (or operator)

Racinghart91 said:
i dont understand it... why would we flash this instead of the original firmwares on sammible ?
just asking
Click to expand...
Click to collapse
Another thing is that you probably just can't flash original BOD2 firmware due to different partition layout than in case of typical, unbranded phone. Read here for more info:
http://forum.xda-developers.com/showthread.php?p=60603630

Great work, tried to install the BOD2 from Sammobile yesterday but obviously ran into the EXT4 error.

How does a person go about a repack? As I still don't know if the EE BOD2 build includes wifi calling. If it does, then I'll be needing to flash it, but it won't be repacked as it isn't Multi-CSC - but won't flash on my phone due to the large /preload partition.

Flashing now. Interested to see if this firmware fixes the problems with the BBC Media Player. Samsung have fixed it on the S5 and S6, according to the Play store page.

RandyKaoss said:
Flashing now. Interested to see if this firmware fixes the problems with the BBC Media Player. Samsung have fixed it on the S5 and S6, according to the Play store page.
Click to expand...
Click to collapse
Didn't work for me despite B0C7 appearing to be earlier than B0D2.

StevePritchard said:
Didn't work for me despite B0C7 appearing to be earlier than B0D2.
Click to expand...
Click to collapse
Yeah, just tried iPlayer on BOD2 - still broken Serious PITA not having access to BBC content on the move. Even radio streaming is glitchy.
Was trying to listen to the football at the weekend, and even with full 4G+ signal the sound kept breaking up. Switched to TuneIn Radio Pro - flawless! Crazy.

RandyKaoss said:
Yeah, just tried iPlayer on BOD2 - still broken Serious PITA not having access to BBC content on the move. Even radio streaming is glitchy.
Was trying to listen to the football at the weekend, and even with full 4G+ signal the sound kept breaking up. Switched to TuneIn Radio Pro - flawless! Crazy.
Click to expand...
Click to collapse
I'm struggling to see how it can be Samsung's fault when all the other players seem to work just fine.

StevePritchard said:
I'm struggling to see how it can be Samsung's fault when all the other players seem to work just fine.
Click to expand...
Click to collapse
That was also my view (i.e. the BBC are at fault) but if you read the info on the Google Play store for the BBC Media Player, it says:
"Users of Samsung Galaxy devices - especially the S5 and Note 4 - may be unable to play content after the upgrade to Android Lollipop (5.x), and may find that the BBC Media Player app crashes after a few seconds. This was due to a bug in the Samsung firmware which has now been fixed. Please ensure you update to the latest version of firmware (G900FXXU1BOC7) for your device."
G900FXXU1BOC7 is a Galaxy S5 firmware though. I wonder what version of the Note 4 firmware will have the same fix?

RandyKaoss said:
That was also my view (i.e. the BBC are at fault) but if you read the info on the Google Play store for the BBC Media Player, it says:
"Users of Samsung Galaxy devices - especially the S5 and Note 4 - may be unable to play content after the upgrade to Android Lollipop (5.x), and may find that the BBC Media Player app crashes after a few seconds. This was due to a bug in the Samsung firmware which has now been fixed. Please ensure you update to the latest version of firmware (G900FXXU1BOC7) for your device."
G900FXXU1BOC7 is a Galaxy S5 firmware though. I wonder what version of the Note 4 firmware will have the same fix?
Click to expand...
Click to collapse
Yeah, I had read that, but it does make you wonder how every other media player managed to avoid the "Samsung bug", but the BBC fell foul of it.

StevePritchard said:
Yeah, I had read that, but it does make you wonder how every other media player managed to avoid the "Samsung bug", but the BBC fell foul of it.
Click to expand...
Click to collapse
Indeed! I mean even Sky Go still works!
I just emailed the Media Player dev team and suprisingly got an almost immediate response from the Product Manager:
"We've been trying to get an estimate for a fix from Samsung for some time, and contacted them again yesterday. We'll keep pushing – I'm sorry it's taking so long for this to get fixed. We're also looking into whether we might be able to create a workaround to resolve the issue. In the long-term, of course, the goal is to remove the need for the separate Media Player app entirely; we hope to have achieved this in the native BBC iPlayer app within a few months."
<Apologies to the OP for veering off topic!!>

Hi Alex,
Any chance of a N910FXXU1BOE2 (0x0) Repacked Firmware?
This is exciting, all these NEW firmware being released.

luckyluis said:
Hi Alex,
Any chance of a N910FXXU1BOE2 (0x0) Repacked Firmware?
This is exciting, all these NEW firmware being released.
Click to expand...
Click to collapse
BOE2 is an earlier build than BOD2, the changelist is less than BOD2. The BOE2 seems to be just a naming convention.

Batfink33 said:
BOE2 is an earlier build than BOD2, the changelist is less than BOD2. The BOE2 seems to be just a naming convention.
Click to expand...
Click to collapse
You are right that the changelist seems the same as B0C5, but the build date is much later - I'm wondering if the changelist for B0E2 is just a typo, and it is a newer release?

When we flash this rom then we have official update over OTA?
EDIT-I found answer sorry.

OP,
have you plans to repack with BOC4 instead of BOC3?
Cheers.

Android N Preview 1

How has it? I can not download it because I have root... And there is no way to download otas before MMB29O in Turkey now. If anyone have N already plase share system images
ops.. here is my thread (I forget this thread before posting):
http://forum.xda-developers.com/cro...ent/7-0-android-n-official-preview-1-t3333931

is there an indication that nexus devices have received ota update for april? i have not heard one either for the seed phones. forgotten by google? hope not...:fingers-crossed:

ondoy1943 said:
is there an indication that nexus devices have received ota update for april? i have not heard one either for the seed phones. forgotten by google? hope not...:fingers-crossed:
Click to expand...
Click to collapse
@ondoy1943. Update arrived for april here on 13th, I was glad to see that ota worked in my G1, you probably received it about that time too.. Have you noticed android N preview 2 is now shown available for GM4G,? . Suppose that means our G1 H220 is eligible too?.Any replies appreciated.

IQ-II (with GM OEM.prop) has received Android N Preview 2 via OTA.
But it seems, that 1GB RAM (GM has 2GB) is not enough for N. (at least with the Preview).
Slow (first) App start, Settings menu a little bit jerky, etc.
Even the telephone app needs 5-6 seconds to start
Additionally the file system has changed to "squashfs", so neither a working TWRP nor root.
ATM, MM is the better choice, at least for the 1GB RAM devices.

vel_tins said:
IQ-II (with GM OEM.prop) has received Android N Preview 2 via OTA.
But it seems, that 1GB RAM (GM has 2GB) is not enough for N. (at least with the Preview).
 @vel_tins. Understand you vel. But as you prob know, The cherry mobile one G1 (H220) has 2gb Ram, This squashfs thingy you mentioned will probably be a sword in our side till twrp or other recovery gets round it?. Thanks for your view.
Click to expand...
Click to collapse

The Android N Preview 2 is officially only released for the
General Mobile 4G
I think, for a good reason...Will be interesting to see what happens with the 1GB RAM devices.
They use squashfs, because the image is fully bloated with useless Google crap apps, which could be installed from the Store anyway.
/system is now almost 3GB(!) uncompressed and doesn't fit into the system partition (when using ext4 fs).