Database Info

[ROM] [Ville][AOSP] [4.3] [cfX-Toolchain 4.8.y+] codefireXperiment OFFICIAL NIGHTLIES

Introducing codefireXperiment for your device! This OP is going to stay slim and bloat free, just like codefireXperiment. No marketing buzzwords either. We take such confidence in the speed and performance of this distribution, we challenge you to find a faster and more stable one!
Warning: we only support anykernel methods of custom kernel installation.
Here's a bit of info you may want on this project for how we do things differently:
CLICK HERE to find out more about the new team working on this project since our TeamEOS merger.
No features you don't need which slow the device down, or put your data at risk of being stolen. If you want to give it away, it should be your decision.
A fast and clean install with no UX decisions made for you. You make the ROM whatever you would like.
A team constantly exploring totally new feature sets and optimizations geared toward you, the user
We utilize a plethora of optimizations in a build system unlike any other:
Each build has a toolchain built for your device at the time of build. No more generic toolchain android builds.
Consistently updated upstream toolchain module source with our custom backports, fixes, and optimizations applied in a patch at build time.
Fully built utilizing Link Time Optimization (another custom ROM first). Feel free to google this one a bit to get an idea of the performance gain.
Many repositories have code fixes, cleanups, and many minor optimizations which are too generous to even speak of here.
Optimizations are toggled on and off based on device for the best experience we can acheive for your device without sacrificing any stability
Many Qcom optimizations and AOSP master (upstream) optimizations and fixes using device specifications to determine usage.
Fully built utilizing strict aliasing and isognu++11 mode.
Full "-O3" build. To those who don't know, this is the highest "optimization level" available in gcc that sets many other flags.
Important Links:
Download Nightlies - We have a very in depth review system, so these should be considered stable.
Download Weeklies - These are built once a week on Monday.
Download GApps
Download SuperSU Zip
Kernel Source
Interactive and Rolling Changelog
Bug Tracker
Instructions:
**This uses the 3.4 cm kernel tweaked for gcc-4.8 builds and as such,
follows all the same requirements as CM-10.2. NEWEST FIRMWARE/HBOOT are required. **
In the same recovery session, flash the following:
Flash rom
Flash GApps
Flash SuperSU zip
Reboot
Thank you for choosing codefireXperiment - See more at: http://www.codefirex.com/index.php?...htc-one-xl-codefirexperiment-nightlies#latest
CHAT on IRC Freenode #codefirex
PHABRICATOR - review system
GITHUB
Thanks to the CM team for all thier work on this family of devices, especiallly h8rift for his work on evita for all of us to enjoy.
Also thanks to my beta testers for experimenting with me.
DISCLAIMER: I will not be held responsible for any damages caused to your device by flashing this ROM. Your warranty is now void.
By proceeding you accept the risks involved with flashing ROMS. While I test everything on my own device, I cannot garauntee yours will not explode into kittens and rainbows.

KNOWN ISSUES:
ROOT ACCESS : On-going disscusion within the team but as of right now root is not available to userspace. Root currently works over adb only. Flash the superSU.zip and carry on if you need root access for apps like TiBu or root file explorers. Otherwise you really don't need it
BOOT ANIMATION : i'ts just full of struggle, it's an old animation made for smaller screens. It freezes and goes blank screen on first boot. Don't be alarmed, it'll be OK. New custom boot ani is being designed now by a fellow team member
BROWSER : Ocassional FC on embedded browser streaming video. You tube and links that open a video player are fine, just embedded video.
ROM is still under construction so i'm sure more will surface but this should be more than ready to be a daily driver.

mine too

jrior001 said:
KNOWN ISSUES:
ROOT ACCESS : On-going disscusion within the team but as of right now root is not available to userspace. Root currently works over adb only. Flash the superSU.zip and carry on if you need root access for apps like TiBu or root file explorers. Otherwise you really don't need it
BOOT ANIMATION : i'ts just full of struggle, it's an old animation made for smaller screens. It freezes and goes blank screen on first boot. Don't be alarmed, it'll be OK. New custom boot ani is being designed now by a fellow team member
BROWSER : Ocassional FC on embedded browser streaming video. You tube and links that open a video player are fine, just embedded video.
ROM is still under construction so i'm sure more will surface but this should be more than ready to be a daily driver.
Click to expand...
Click to collapse
Forgot to say that I didn't get the boot animation bug.

Darknites said:
Forgot to say that I didn't get the boot animation bug.
Click to expand...
Click to collapse
Its possible it's just the larger boot animation, I choose a smaller one for this device as it has a smaller screen than evita/jewel. the m7 devices were having the same struggles with it. It's a minor issues at this point, it will be fixed soon. I just don't want people to panic over it if they see it freeze up.

jrior001 said:
Its possible it's just the larger boot animation, I choose a smaller one for this device as it has a smaller screen than evita/jewel. the m7 devices were having the same struggles with it. It's a minor issues at this point, it will be fixed soon. I just don't want people to panic over it if they see it freeze up.
Click to expand...
Click to collapse
Oh right, oh and is this newer than the one I got already?

Darknites said:
Oh right, oh and is this newer than the one I got already?[/QUOTE
Check the time on it but I think it's the same build I set you yesterday.
Click to expand...
Click to collapse

jrior001 said:
Check the time on it but I think it's the same build I set you yesterday.
Click to expand...
Click to collapse
Ya same one so no need to flash anything lol.

Source?
Sent from my SCH-R970 using XDA Premium 4 mobile app

Zarboz said:
Source?
Sent from my SCH-R970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Added link to OP

Bootloop city
Wiped cache / dalvik / data / system.
HBOOT 2.15
S-ON

yooouuri said:
Bootloop city
Wiped cache / dalvik / data / system.
HBOOT 2.15
S-ON
Click to expand...
Click to collapse
S-on? Did you fastboot flash the boot.IMG?
This is required if you are still s-ON
Edit: added this instruction to the OP.
Sent from my One Xl using Tapatalk 2

jrior001 said:
S-on? Did you fastboot flash the boot.IMG?
This is required if you are still s-ON
Edit: added this instruction to the OP.
Sent from my One Xl using Tapatalk 2
Click to expand...
Click to collapse
Yes i fastboot the boot.img

yooouuri said:
Yes i fastboot the boot.img
Click to expand...
Click to collapse
Have you been able to run other 4.3 roms ? are you sure you are on the latest firmware?
There have been a few other people that downloaded has anyone else had any bootloop issues like this?
This build was tested and confirmed working by Darknites, not that that means it's without any isues, just surprising. Hopefully we can get a few other to confirm if theres an issue as I do not have a One S to test with.

Yes i run the last CM nightly. And some other 4.3 roms ran without problems.

yooouuri said:
Yes i run the last CM nightly. And some other 4.3 roms ran without problems.
Click to expand...
Click to collapse
Sounds like you've done everything right so far so im not entirely sure whats up. Did you attempt to reflash or just jump bacl to another rom after the issue? I'd like to see some more feedback from a few other users as well before I start digging into anything.
Sent from my One Xl using Tapatalk 2

yooouuri said:
Bootloop city
Wiped cache / dalvik / data / system.
HBOOT 2.15
S-ON
Click to expand...
Click to collapse
Did you restore any app data? Also did you triple wipe
Sent from my HTC VLE_U using xda app-developers app

jrior001 said:
Sounds like you've done everything right so far so im not entirely sure whats up. Did you attempt to reflash or just jump bacl to another rom after the issue? I'd like to see some more feedback from a few other users as well before I start digging into anything.
Sent from my One Xl using Tapatalk 2
Click to expand...
Click to collapse
Now im runnig the nightly from 08/30. With no problems.
Just wiped cache dalvik system and data. If you can tell me how to make a logcat from the boot. I can help you tomorrow?

yooouuri said:
Now im runnig the nightly from 08/30. With no problems.
Just wiped cache dalvik system and data. If you can tell me how to make a logcat from the boot. I can help you tomorrow?
Click to expand...
Click to collapse
Your running which nightly from 8/30? You got this ROM up and running or another like carbon or cm?
Sent from my One Xl using Tapatalk 2

yooouuri said:
Bootloop city
Wiped cache / dalvik / data / system.
HBOOT 2.15
S-ON
Click to expand...
Click to collapse
Save some time using factory reset in twrp which will wipe all that is need other than system which roms already wipe anyway so try like that instead and also flash the boot.img before the rom.

[Q] TF101 lost sound. Using KatKiss-4.3

Hello All,
I want to raise a question here because I don't seem to find any help about it.
I am using a nice TF101 tablet with great joy. Now with less as yesterday while watching youtube the sound has gone and did not return after a reboot or using the DSP Reinit in the Kat Tools.
Now this has happened with me already a week before. Then I was using Jousteink's unofficial room. Then I've changed to KatKiss 4.2.2 and the sound reappeared again. Later to give it a whirl I have then upgraded to KatKiss 4.3 and everything was wokring like charm for 3 days then the sound went to Honolulu again.
Does anyone have any idea how can I get the sound working again or what can be the cause? Or simple share the same experience?
Thanks for the help.

Hate to ask, but is your volume up?
I had issues with the hangouts/talk notifications muting my volume when using the cascade option in the KAT tool.

frederuco said:
Hate to ask, but is your volume up?
I had issues with the hangouts/talk notifications muting my volume when using the cascade option in the KAT tool.
Click to expand...
Click to collapse
Thanks for the reply.
Yup, the volume is as high as it can go

szilasz said:
Thanks for the reply.
Yup, the volume is as high as it can go
Click to expand...
Click to collapse
So, you are saying that the sound works sometimes and then cuts out. Intermittently? Maybe hardware related - but I'd leave a proper diagnosis to the experts here.
I know that I have the volume toolkit installed on my TF101 and to be honest - it doesn't seem to make a whole lot of difference when listening thought the tablet's speakers.
Ziggy

Theziggy said:
So, you are saying that the sound works sometimes and then cuts out. Intermittently? Maybe hardware related - but I'd leave a proper diagnosis to the experts here.
I know that I have the volume toolkit installed on my TF101 and to be honest - it doesn't seem to make a whole lot of difference when listening thought the tablet's speakers.
Ziggy
Click to expand...
Click to collapse
Nope, it is gone. Totally. It is OK on bluetooth and through jack but the speakers are deaf. From one point to another and remains so even after reboot and reflashing with a /system format.
On ICS based roms there was a problem similar to this where restarting the tab fixed it for some time and you could have save this reboot with the KAT tool. You could just reinitalize the sound. I agree on the quality part though
I hope it is not HW related, this was always a popular problem with the TF101. I just hope to find someone who encountered this and can give a fresh idea of a fix.

Which build are you using? The latest one I have the same issue, but if I go back a few it's working fine.

Lethe6 said:
Which build are you using? The latest one I have the same issue, but if I go back a few it's working fine.
Click to expand...
Click to collapse
Hello there,
I am using the latest #020 build. Which one are you on? I would like to give it a whirl to see if will I get my sound back.
Thanks in advance!

szilasz said:
Hello there,
I am using the latest #020 build. Which one are you on? I would like to give it a whirl to see if will I get my sound back.
Thanks in advance!
Click to expand...
Click to collapse
I'm using 018 right now because with 019 and 020 the back button stops working. I was also unable to control the sound through the device itself but if I would start, say, a movie on MX Player then I could hear and adjust volume.

Lethe6 said:
I'm using 018 right now because with 019 and 020 the back button stops working.
Click to expand...
Click to collapse
That's because you forgot to flash the gapps after the rom zip.
Follow exactly the instructions from the 1st post and it'll work fine.

timduru said:
That's because you forgot to flash the gapps after the rom zip.
Follow exactly the instructions from the 1st post and it'll work fine.
Click to expand...
Click to collapse
I'll take your word for it, but I'm fairly sure I did, twice.

Lethe6 said:
I'll take your word for it, but I'm fairly sure I did, twice.
Click to expand...
Click to collapse
I know I had no sound, or GPS when I 1st flashed this. I had flashed it from TWRP 2.5.00, and I got it updated to TWRP 2.6.100, and reflashed it, and now everything is working. I would make sure your TWRP is up to date.

C0BRA01 said:
I know I had no sound, or GPS when I 1st flashed this. I had flashed it from TWRP 2.5.00, and I got it updated to TWRP 2.6.100, and reflashed it, and now everything is working. I would make sure your TWRP is up to date.
Click to expand...
Click to collapse
There is no 2.6 for the tf101 ... what did you install exactly? The title says 2.6 but the files are 2.3. http://www.teamw.in/project/twrp2/109
It was fixed after just flashing the newer one.
Edit: Yeah, not touching unofficial cooked recoveries with a 1000 foot pole.

Then you will be waiting a long time, as there have been no new "Official" TWRP recoveries for a long time now for the tf101.. His is working fine.
You take similar risks every time you flash a ROM.
Lethe6 said:
There is no 2.6 for the tf101 ... what did you install exactly? The title says 2.6 but the files are 2.3. http://www.teamw.in/project/twrp2/109
It was fixed after just flashing the newer one.
Edit: Yeah, not touching unofficial cooked recoveries with a 1000 foot pole.
Click to expand...
Click to collapse

Lethe6 said:
There is no 2.6 for the tf101 ... what did you install exactly? The title says 2.6 but the files are 2.3. http://www.teamw.in/project/twrp2/109
It was fixed after just flashing the newer one.
Edit: Yeah, not touching unofficial cooked recoveries with a 1000 foot pole.
Click to expand...
Click to collapse
I agree with @C0BRA01. The only reason that joesteink's build were not official is because no one from the TWRP team approved them. I have not heard of any issues of anyone bricking or having issues caused by any of the 2.5 or 2.6 builds for the TF101. I am running sidneyk's 2.6.1.0-c build right now and have had zero issues, other than the superuser nag screen at reboot when running KatKiss 021. It has to do with the supersu app even though root is working fine in the ROM.

[ROM][6.0][ALPHA/WIP][UNOFFICIAL] CM 13.0 and TWRP for Sony Xperia X Compact (kugo)

Now with LineageOS 14.1 Nougat
builds
sources (github) PATCHES STRONGLY ENCOURAGED
local_manifests for building
current branch is cm-14.1 (LineageOS 14.1 with Linux 3.10.x)
Instructions:
Unlock bootloader
Flash TWRP from kugo/twrp/recovery.img or from https://forum.xda-developers.com/x-compact/development/recovery-twrp-t3522249
Do not use AndroPlus's, it does not handle /system writing very well (in my experience)
Do not use my recovery build for stock, it does not handle /data encryption
Flash zip in recovery
SELinux: Permissive (I haven't updated the sepolicy in a while, enforcing makes the camera panic which causes bootloop. I may fix this later.)
Lineage 14.1
WORKING:
WiFi
Data/Cellular (you may want to jot down APN settings from stock before flashing)
Fingerprint reader (a bit unreliable, will fail sometimes)
FMRadio
Camera
NOT WORKING:
AudioFX (the built in equalizer thing; just disable it from the apps menu)
SELinux (sepolicy needs update)
Bluetooth (system seems to crash when turning it off)
Whatever isn't working in AOSP/Omnirom (e.g. in-call volume control)
UNTESTED:
NFC (it turns on, but I have no NFC devices)
Keep in mind that I am not really a developer but will do what I can to help with issues
Special thanks to the Sony-Kitakami team for serving as a base to port changes from suzuran/kitakami to kugo/loire
Additional thanks to humberos for porting omnirom to kugo and serving as a base to port to kugo
...and thanks to Sony for allowing us to unlock our bootloaders and for porting AOSP to their phones (unlike some other manufacturers)
Recent Changes:
Rebased device trees off of omnirom trees, updated everything

I'll go first and say thank you for developing for this device.
Hope that this encourages other devs to build their ROMs too.
Great job! :good:

Nice

as soon as audio playback is fixed i will flash and try to post logcats !

A little love for the XC

Keep up with the good work! Now that TA backup is also possible, it's just a matter of fixes until this is good to go!

ardylemon said:
Keep up with the good work! Now that TA backup is also possible, it's just a matter of fixes until this is good to go!
Click to expand...
Click to collapse
Not to mention greater adoption of ROM flashing now that we have a way to get back to stock.

thanks for the update!

Looking forward to testing cm14.1. Has anyone already flashed it and can give some feedback and impressions?

Micka84 said:
Looking forward to testing cm14.1. Has anyone already flashed it and can give some feedback and impressions?
Click to expand...
Click to collapse
I would go with cm-13.0 honestly unless bluetooth is that important (which is next on the to-do list for cm-13).
CM-14.1 is pretty incomplete upstream, so it's missing some features (like theming).
It's also still running the marshmallow kernel, so things like vulkan probably won't work either, and
I don't plan on releasing a build with the nougat kernel until we at least get prebuilts for it.

howdid said:
as soon as audio playback is fixed i will flash and try to post logcats !
Click to expand...
Click to collapse
Audio playback should be "fixed" now, for both 13 and 14.1

How is camera quality and battery life?

Looking for a little bit of clarification. After unlocking the bootloader, what is the process for installing TWRP? Does it require a modified boot.img to boot recovery as outlined in AndroPlus's thread? Thanks.

ammarr said:
Looking for a little bit of clarification. After unlocking the bootloader, what is the process for installing TWRP? Does it require a modified boot.img to boot recovery as outlined in AndroPlus's thread? Thanks.
Click to expand...
Click to collapse
I don't think I ever needed to flash a modified boot.img, so just flash recovery in fastboot, power off the phone, and then boot into it with volup+power
If for some reason that doesn't work, you can flash AndroPlus's boot.img and try again
tlxxxsracer said:
How is camera quality and battery life?
Click to expand...
Click to collapse
I can't really comment on the camera (it seems fine to me, but that isn't my area of expertise), but the battery is admittedly not where I want it to be after disabling audio offloading and rolling back the kernel for bluetooth.
Kind of waiting for CM-14.1 to be more ready to fix both of those

EliWallace said:
I don't think I ever needed to flash a modified boot.img, so just flash recovery in fastboot, power off the phone, and then boot into it with volup+power
If for some reason that doesn't work, you can flash AndroPlus's boot.img and try again
I can't really comment on the camera (it seems fine to me, but that isn't my area of expertise), but the battery is admittedly not where I want it to be after disabling audio offloading and rolling back the kernel for bluetooth.
Kind of waiting for CM-14.1 to be more ready to fix both of those
Click to expand...
Click to collapse
Thanks for the reply and for bringing CM to the XC.
Comparatively how much worse is the battery life compared to stock? Obviously depends on usage but are you still able to make it through the day?

ammarr said:
Thanks for the reply and for bringing CM to the XC.
Comparatively how much worse is the battery life compared to stock? Obviously depends on usage but are you still able to make it through the day?
Click to expand...
Click to collapse
It was enough to get through a day, but I would end up with 30-50% instead of 60-75% (I have mail checking constantly, so that was a big drain)
Thats in comparison to a CM build with a newer kernel and audio offloading not disabled,
I haven't used stock at all so I don't know how the battery life is on it

Why not use an existing msm8956 tree for kenzo and hydrogen and make Sony additions to a car kernel source and boot cm. It will bring much lesser issues.

Rom looks good!
But I only have 2 problems:
1) I have a changing mac adress. Every time I reboot my device, I get another mac adress. It always starts with 00:90:4c but the remaining part changes.
I found some solutions on google, but nevertheless they didn't work... Maybe because the solution is not for X compact or CM 13/14.1....
2) The phone doesn't charge when I connect it to the wall socket. Just for half a second the led turned yellow, but after that it stops charging. The cable and battery are fine (I went to stock and it charges immediately).
Hopefully does anybody have a solution or idea how I could fix these problems!

NL_henk said:
Rom looks good!
But I only have 2 problems:
1) I have a changing mac adress. Every time I reboot my device, I get another mac adress. It always starts with 00:90:4c but the remaining part changes.
I found some solutions on google, but nevertheless they didn't work... Maybe because the solution is not for X compact or CM 13/14.1....
2) The phone doesn't charge when I connect it to the wall socket. Just for half a second the led turned yellow, but after that it stops charging. The cable and battery are fine (I went to stock and it charges immediately).
Hopefully does anybody have a solution or idea how I could fix these problems!
Click to expand...
Click to collapse
I think it has something to do with the kernel. Could someone let me know which kernel-version is used?

NL_henk said:
I think it has something to do with the kernel. Could someone let me know which kernel-version is used?
Click to expand...
Click to collapse
I also noticed that the mobile does not charge however at the laptop over USB load it
Ps. i use not Costum Kernel

AOSP 7.1.* Z5 Premium

Present you with a 7.1 .1 Nougat AOSP!
Tested on E6853, released a build for Dual E6883 "NOT TESTED" try at your own risk
Install trough ADB as usual by flashing boot.img system img and userdata.img
(detailed how to in post no.2)
Note:
If you are updating from previous release, flash only system.img if you wanna keep your userdata (you will only loose gapps)
This is pure AOSP.
have tried most of it and everything has been working fine.
Improvments from 7.0:
Camera is working (Not inverted anymore)
Fingerprint is working
Auto brightness works as intended
Known bugs:
AC 5GHz wifi might not work for all.
Fingerprint might bug out for some people.
Download Here
GApps
(Use arm64 7.1)
Updated 2017-04-14
AOSP 7.1.1 rev 38
Cheers
XDA:DevDB Information
AOSP 7.1.*, ROM for the Sony Xperia Z5 Premium
Contributors
Elfmirth
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: _r7
Stable Release Date: 2016-12-18
Created 2016-12-14
Last Updated 2017-04-17

Reserved
How to:
In the ADB folder press shift key and right klick with your mouse, choose "Open Command prompt here"
Power off your phone, once it's off, press and hold volume key up, and plugg it in to your PC, now the indicator on the phone sould turn blue, that shows that the phone is in Fastboot mode.
(Check in your device manager that the sony fastboot drivers are installed)
when all that is done, in the command promt type:
Code:
fastboot flash boot "drag and drop the boot.img file"
when that is done type:
Code:
fastboot flash system "drag and drop the system.img file"
after that:
Code:
fastboot flash recovery "drag and drop the recovery.img file"
when all is done type:
Code:
fastboot reboot
and your phone will reboot, it might take longer than usual.
If you wanna install gapps and root READ!! and follow this to boot up TWRP.
When phone is booted up, turn it off again enter fastboot mode then:
1.
Code:
fastboot [U]boot[/U] TWRP.img
2. On your phone press volume up until you see that you're booting in to TWRP

Thanks a lot! I've been meaning to try building this myself. Thanks for giving me hope again for the Z5P!

e6833
thank you.
is it working for z5p Dual?

faraheed said:
thank you.
is it working for z5p Dual?
Click to expand...
Click to collapse
No so far I have only done a build for E6853, since I have One of those, but ill see if I can give Dual a try this weekend ?

e6833
Elfmirth said:
No so far I have only done a build for E6853, since I have One of those, but ill see if I can give Dual a try this weekend
Click to expand...
Click to collapse
thank you my friend, can i try it on my e6833?

faraheed said:
thank you my friend, can i try it on my e6833?
Click to expand...
Click to collapse
Ofc you can try, but to be safe wait until I have made a proper build for it ?

e6683能用吗，或者说e6653

I've noticed a bug, Wifi AC (5GHz band) doesn’t work with this ROM. i flashed the 3 imgs (Boot, system, userdata) with fastboot, then used the boot.to.TWRP to boot into TWRP and flashed GApps and SuperSU through that.

Tested and played with it for a couple hours. (E6853)
Everything seemed to work flawlessly minus performance being a little on the slow side in comparison to stock Sony Roms.
I didn't notice any issues with the 5ghz as it connected just fine and gave me 351mbps down and 26mbps up.
Im not sure if its 7.1 or an issue with the ROM but i couldn't get SU/Busybox to properly open. It kept FC even after clearing my caches.
(also, i couldnt find the asop.zip you referenced in the OP so i directly flashed all the .imgs directly)
Once we get the performance close to stock, and Camera up to par (its A LOT better, but still lacking features) this will definitely become a daily driver for me!
Lets hope Sony keeps pushing quality uploads to their aosp program!

WannaB101 said:
Tested and played with it for a couple hours. (E6853)
Everything seemed to work flawlessly minus performance being a little on the slow side in comparison to stock Sony Roms.
I didn't notice any issues with the 5ghz as it connected just fine and gave me 351mbps down and 26mbps up.
Im not sure if its 7.1 or an issue with the ROM but i couldn't get SU/Busybox to properly open. It kept FC even after clearing my caches.
(also, i couldnt find the asop.zip you referenced in the OP so i directly flashed all the .imgs directly)
Once we get the performance close to stock, and Camera up to par (its A LOT better, but still lacking features) this will definitely become a daily driver for me!
Lets hope Sony keeps pushing quality uploads to their aosp program!
Click to expand...
Click to collapse
The speed will improve over time, the first 2-3 hours and 2-3 reboots mine was a bit laggy to, but after installing pixel launcher and playing around for a few hours there is no lag at all and it's just as fast as my HTC 10 (if not faster)
FC on SU I havent had, but then again only used it for 3-4 apps but worked fine with those.
The asop.zip was a typo on my end, have removed it now (was a little to tired)
exvargos said:
I've noticed a bug, Wifi AC (5GHz band) doesn’t work with this ROM. i flashed the 3 imgs (Boot, system, userdata) with fastboot, then used the boot.to.TWRP to boot into TWRP and flashed GApps and SuperSU through that.
Click to expand...
Click to collapse
"Edit" I tried a couple of times now and the only issue I had was cus of bad reception. But then again I dont have AC router only N 5GHz

WannaB101 said:
I didn't notice any issues with the 5ghz as it connected just fine and gave me 351mbps down and 26mbps up.
Im not sure if its 7.1 or an issue with the ROM but i couldn't get SU/Busybox to properly open. It kept FC even after clearing my caches.
Click to expand...
Click to collapse
How did you flash? I tried again, fastboot flashing all 3 images then flashing gapps through the provided twrp, but still no 5G wifi.

It's a lot better than the current 6.0.1 ROM I was previously using. RAM usage was cut down by half, battery life is pretty phenomenal and everything is butter smooth. I had some camera issues in the past where the z5p could never focus on anything.
All fixed with AOSP 7.1, making it my daily driver

Great ROM, but I have some issues with fingerprint. I added them during the initial setup and now they don't work after I rebooted once, so I tried to remove and add new fingerprints but the system freezes when I try to delete them. anybody else with same issues?

KbaB.BroS said:
Great ROM, but I have some issues with fingerprint. I added them during the initial setup and now they don't work after I rebooted once, so I tried to remove and add new fingerprints but the system freezes when I try to delete them. anybody else with same issues?
Click to expand...
Click to collapse
Hmm, haven't had that issue, but I never added fingerprint during setup, only added it after setup.
exvargos said:
How did you flash? I tried again, fastboot flashing all 3 images then flashing gapps through the provided twrp, but still no 5G wifi.
Click to expand...
Click to collapse
Hmm that is wierd.
Im building a new rom atm, updated to 7.1_rev7 (from rev6) so hopefully it will fix some issues. Will be uploaded tonight if all goes well, and will upload for e6883 as well.
How is battery life for everyone? I had some massive drain on 7.0 but have had almost 3 days on one charge here (mostly standby)

Elfmirth said:
Hmm, haven't had that issue, but I never added fingerprint during setup, only added it after setup.
Hmm that is wierd.
Im building a new rom atm, updated to 7.1_rev7 (from rev6) so hopefully it will fix some issues. Will be uploaded tonight if all goes well, and will upload for e6883 as well.
How is battery life for everyone? I had some massive drain on 7.0 but have had almost 3 days on one charge here (mostly standby)
Click to expand...
Click to collapse
Battery life is much better than Sony stock ROM and everything based on it, easily lasts me one day which is what I need. Light usage keeps the phone alive for more than two days.

@Elfmirth from which stock FW version did you come from? from my experience fingerprint and other issues happens when I try flashing ROMX over a different FW than it was based of so the 5G WiFi and fingerprint might be a cause of this.

KbaB.BroS said:
@Elfmirth from which stock FW version did you come from? from my experience fingerprint and other issues happens when I try flashing ROMX over a different FW than it was based of so the 5G WiFi and fingerprint might be a cause of this.
Click to expand...
Click to collapse
The first FW I started out flashing from was 32.1.A.1.163. Then I flashed AOSP 7.0 and after that AOSP 7.1

OP Updated with rev7 for both e6853 & e6883
enjoy

Hi Elfmirth,
Thanks for your work.
Hope you keep support for the dual sim devices too. Thanks
Best Regards,
Ashray
Elfmirth said:
OP Updated with rev7 for both e6853 & e6883
enjoy
Click to expand...
Click to collapse

Successfully able to boot Project Treble/AOSP rom

This is not a guide as such but more of direction to other peoples hard work and effort. I am not a developer, just an experimenter!
Main Credits - @MishaalRahman and @phhusson.
For me one of the main selling points of the Mediapad M5 was being Project Treble enabled. Being a big Nexus/Pixel fan I am not particularly fond of EMUI.
So after reading this detailed and clear guide by Mishaal Rahman http://www.xda-developers.com/flash-generic-system-image-project-treble-device/, I was able to successfully install an AOSP Generic System Image by phhusion http://forum.xda-developers.com/project-treble/trebleenabled-device-development/experimental-phh-treble-t3709659
My device - CMR-W09 (10.8" non pro wifi).
I flashed v17 with Gapps and SU and apart from an Android System error upon boot it seems to work ok. I have not had much time to play with it but so far Wifi, Bluetooth, sound, camera, fingerprint sensor, MTP and SD card appear to be working. I had issues with google play not downloading apps but worked after clearing data/cache on google play and google play services. Also have issues with superuser force closing.
For the nervous and unsure, you can easily return to stock Huawei firmware by flashing your devices stock system.img in fastboot.
Obviously bootloader needs to be unlocked see guide - https://forum.xda-developers.com/mediapad-m5/how-to/bootloader-unlock-guide-t3781275 by @Apo11on. You can use Apo11on's root guide to download your firmware to get your stock system.img.
OEM needs to be disabled in developer options.
It is best to factory reset via recovery mode and then boot straight into bootloader to keep FRP unlocked.
Do this at your own risk but please read all the available information and guides on XDA.
pphusion has made other Project Treble roms but I have yet to try them. Hopefully it would be nice if someone could fully develop Lineage for this device.

which rom did you use ? the A/B one or A only ?

It's an A-only device.
I tried AOSP with GAPPS and SU but SuperSU shows the su binary as being occupied through several reboots. Getting the Lineage GSI now and will root with magisk.
Edit:
Blah... Lineage is not an option until we have twrp :/ (at least for me) No way to install GAPPS.
Edit:
SU works with phh's super user available from the play store.

Yes i have the AOSP one now on my AL-09 and it works fine till now. Bugs : home Button not working but fingerprint works, supersu with the phhs one works. Bluetooth sometimes gives an error message. Battery drain is a little bit high. I installed the Huawei camera apk from treble forum and This works also good.
Another Bug is Apps sometimes force closing but Not often.
How is Lineage performing?

A little bit off topic, but how did you unlock the bootloader on the Wifi only version since the website for the code is offline for a few weeks now?
Thanks in advance.
Fantastic to see that Treble works.

On my AL09(ASOP with gapps and su) bluetooth never connects to any of my devices and fc on pairing.
Lineage was a non-starter, since I was unable to get gapps running. I was also getting a vendor mismatch toast. I'm back on the stock .125(C00), no working tether is infinitely more useable than no BT.
It was nice to be able to flash something that didn't brick it and was partially useable.

fargonaz said:
On my AL09(ASOP with gapps and su) bluetooth never connects to any of my devices and fc on pairing.
Lineage was a non-starter, since I was unable to get gapps running. I was also getting a vendor mismatch toast. I'm back on the stock .125(C00), no working tether is infinitely more useable than no BT.
It was nice to be able to flash something that didn't brick it and was partially useable.
Click to expand...
Click to collapse
I understand, Do you think it gets more stable for our device in the future?

florian-m19 said:
I understand, Do you think it gets more stable for our device in the future?
Click to expand...
Click to collapse
I think so, if you look at the github comments there is a huawei phone having the same problem, so as long as a phone is having problems it should get fixed

We would like some screenshots to see if this is real @AndDiSa @rcstar6696 @phhusson @MishaalRahman

Just installed it, attached a few screenshots. Haven't tested it a lot, but it boots.

Wie are Not joking, its real ??

Delete, double post

I will be getting my Mediapad M5 8.4 tomorrow and will be flashing the AOSP treble build straight away. Just a heads up a updated build has just been posted with some Huawei related fixes.

i flash it now, and give feedback tomorrow

I flashed the new one with gapps and su, and for the sht-l09 there is no working bluetooth, so that's as far as I go. It will be nice when the BT is fixed for this device.

Works good with dirty flash, Home Button is working now and also Automatic Brightness, but battery draining is really high and it gets hot.

florian-m19 said:
Works good with dirty flash, Home Button is working now and also Automatic Brightness, but battery draining is really high and it gets hot.
Click to expand...
Click to collapse
Have you tried changing the cpu governor? Is it set to something like interactive? I got my Mediapad today but I am waiting for the bootloader unlock code from Huawei.

darren1 said:
Have you tried changing the cpu governor? Is it set to something like interactive? I got my Mediapad today but I am waiting for the bootloader unlock code from Huawei.
Click to expand...
Click to collapse
yes it is on interactive, should i change this ?

florian-m19 said:
yes it is on interactive, should i change this ?
Click to expand...
Click to collapse
Might be worth experimenting with. Try conservative or ondemand if they are available. You can always change back if it doesn't make any difference.

darren1 said:
Might be worth experimenting with. Try conservative or ondemand if they are available. You can always change back if it doesn't make any difference.
Click to expand...
Click to collapse
okay i change it in helix engine to ondemand and the suspend engine is now on powersafe.