Develop Bugs

[ROM][UNOFFICIAL][4.4.4] CyanogenMod 11 + crDroid for Xiaomi MiPad

CyanogenMod 11 with crDroid additions for Xiaomi MiPad
!! IMPORTANT !!
xep.8800.org will be temporarely down from 29.03.15 for couple of weeks so it would be great if somebody do mirror of latest buld and post link here. Thx!
About:
Source built CM except proprietary blobs and binary kernel from stock MIUI rom.
This is not a port from another binary rom.
Click to expand...
Click to collapse
What's working:
It seems everything working for now..
Click to expand...
Click to collapse
Not working/Bugs:
"Wi-Fi region code" setting is broken. Do not touch it or it will break your wi-fi.
you tell me.. testing in progess..
Click to expand...
Click to collapse
Instructions:
1. Install CWM Recovery
2. Do Full Wipe If coming from another ROM
3. Flash ROM
4. Flash Google Apps (my recommendation is to install minipal gapps due to /system partition size limits)
5. Reboot
Click to expand...
Click to collapse
Multirom Instructions:
1. Install TWRP Multirom Recovery
2. Reboot into TWRP and install multirom-20150205-v30-UNOFFICIAL-mocha.zip
3. Click "Advanced->Multirom" and flash your desired second rom.
4. Return to the installed roms listing, click fresh installed rom and click "Remove boot.img" (Due to closed kernel sources kexec-hardboot is not implemented so we need to remove boot.img)
5. Reboot. Select your desired rom from multirom menu
Click to expand...
Click to collapse
Downloads:
cm-11-20150327-UNOFFICIAL-mocha.zip
CWM
Multirom:
TWRP_multirom-v2.8.4-mocha.zip
multirom-20150205-v30-UNOFFICIAL-mocha.zip
I don't know if it is actually compiled with TEGRA optimizations but have created CWM flashable zip with stock bionic libraries. You can flash it on top of CM installation:
tegra_bionic.zip
Changelog:
15.02.15
* apply qcom bionic optimization
* build.prop dalvik etc tweaks
02.02.15
* Reboot to recovery fixed
* Recents view proportion fixed
26.01.15
* Synced with CM repo
* have enabled Display mirroring (miracast) though it does not work with my EZ dongle, sound is ok but screen is black. May be it'll work with another dongles...
21.01.15
* Update to the latest kernel from stock MIUI
20.01.15
* Sleep issue fixed
* Adopt nvcplsvc for CM & implement Performance Profile selection
18.01.15
* Synced up with CM repo.
* Added USB Mass Storage mode for external sd. Though it does not work along with ADB Debug enabled, need to be switched off when using UMS mode.
17.01.15
* Switch to CM's audio_effects and make Dirac plugin work. Equalizer crash fixed.
Click to expand...
Click to collapse
Links:
http://github.com/cyanogenmod
http://github.com/cristianomatos
https://github.com/faust93
Click to expand...
Click to collapse
I take no responsibility for what this may or may not do to your device.
Do not forget to click Donate button! It makes me work harder!

Thanks Pumbaster for your work!

My device doesn't seem to go to sleep...
WakeLockDetector shows Android System --> ConnectivityService as the main issue. BetterBatteryStats shows the same...
I tried turning location services off, froze Mobile Data and Mobile Network Configuration in Titanium Backup but that doesn't help. No checking if the same wakelock appears with wifi off...
Anyone with any clue? Or the same problem?

Will check the ROM and tell you dagrim.
But first thing first, I have to install it. And I have 2 questions, to avoid screwing things.
- Does it works with TWRP instead of CWM?
- Is there a reason to have a June version of minimal gapps where a version of December exist?
Thanks to everyone in the process (romers, informers, helpers)

Krystanos said:
Will check the ROM and tell you dagrim.
But first thing first, I have to install it. And I have 2 questions, to avoid screwing things.
- Does it works with TWRP instead of CWM?
- Is there a reason to have a June version of minimal gapps where a version of December exist?
Thanks to everyone in the process (romers, informers, helpers)
Click to expand...
Click to collapse
I used pico gapps myself and the june version is way smaller then the december version, then again I actually did try the december version as well and it seemed to work fine. So not sure, apart from the size...
About TWRP vs CWM, not sure. Guess it also should work with TWRP but haven't tried... CWM is needed for True Dual Boot, but that seems bugged anyway.

By me too. Battery drain is to much, device don't go to sleep...

zolikaDB said:
By me too. Battery drain is to much, device don't go to sleep...
Click to expand...
Click to collapse
Yeah, seems to be a common issue.
My device only goes to sleep when wifi is turned completely off. When I have it set to turn off when display is off I still get the wakelocks. I also have set the scanning for open wifi to off, location services turned off, etc.
For now I flashed back to the 0114 version as that one is working fine here...
If I can share some logs or anything, I'd be more then happy to!

@dagrim1: I hope, Pumbaster make new, fixed build

I Encounter Graphical Glitches with 3rd Party Browsers (Opera and UC Browser)
Chrome works fine so far. Also heavy Battery drain an 17/1

@faust93: what is with battery drain?

Did a very dirty try or replacing frameworks.jar but that didn't work...
Saw some wifiStateTracker errors and that and ConnectivityService seemed to be part of the framework, that's why I gave it a shot. 0118 still has the deespleep/wakelock issue btw...

I don't really care about dual boot. MIUI has so much limits. Once I go to CM, I don't think I'll be able to come back to MIUI...
But I'll stick to CWM, just in case...

I just tried the wpa_supplicant.bin file posted by pumbaster on 4pda and it seems to solve the deepsleep issues!
Post 351 of the custom mipad 4.4.4. rom thread there...
http://xep.8800.org/mipad/wpa_supplicant.bin
Place in system/bin and set permissions to rwxr-xr-x
@faust93: I hope you don't mind me posting this here but I saw you posted links to the same location in the topic start, if so my apologies and I will remove it asap (but I am going to sleep now, so won't be up until next morning...)
Also had some iussues with stuttering video playback, but setting 'disable hardware overlay' in developer settings fixed that for now...
Thanks for the awesome work!

dagrim1 said:
I just tried the wpa_supplicant.bin file posted by pumbaster on 4pda and it seems to solve the deepsleep issues!
Post 351 of the custom mipad 4.4.4. rom thread there...
http://xep.8800.org/mipad/wpa_supplicant.bin
Place in system/bin and set permissions to rwxr-xr-x
@faust93: I hope you don't mind me posting this here but I saw you posted links to the same location in the topic start, if so my apologies and I will remove it asap (but I am going to sleep now, so won't be up until next morning...)
Also had some iussues with stuttering video playback, but setting 'disable hardware overlay' in developer settings fixed that for now...
Thanks for the awesome work!
Click to expand...
Click to collapse
Is this bin file integrated in 2015.01.18 build? What do you know about this ROM? Did you test it?

zolikaDB said:
Is this bin file integrated in 2015.01.18 build? What do you know about this ROM? Did you test it?
Click to expand...
Click to collapse
I don't believe it's integrated in 0118, think that fixes some sd stuff...
I am currently running the 0118 build (with the wpa_supplicant.bin file replaced manually) and seems to be working pretty fine. Had some video issues with a certain app (video jumping a bit, stuttering) but think I fixed that with 'disable hardware overlay' in developer options.
Without the replaced .bin I also had a problem with turning off and on wifi. It would work when booting, but if I turned it off I couldn't turn it on again... The replaced .bin also fixes that. Now checking if antutu finishes it's run...

@dagrim1: hope, Pumbaster fix this problem!

Just another small question: full wipe will delete the /data partition too right ? So the ROM zip file will be deleted too ? Or am I missing something ?
Thanks.

I tried to install with TWRP and when I reboot, I get to MIUI v6 so I guess it rebooted in the wrong system.

jastonas said:
I tried to install with TWRP and when I reboot, I get to MIUI v6 so I guess it rebooted in the wrong system.
Click to expand...
Click to collapse
Unfortunately I tried to install CWM with fastboot and it failed to install... No specific error message.
I have seen a port of TWRP for MiPad. Have you tried this one, or the standard one?

How I wish I could just flash CM on my MiPad...

[ROM][MTK][STOCK] fairphone FP1 kitkat 4.4.4

This is Android 4.4.4 kitkat compiled from scratch from some other device sources that you find on the web. Adapted to fairphone FP1(U).
It includes various security fixes on top of 4.4.4 - but most likely not all. Major security hole detectors are green now (VTS, Bluebox, Zimperium).
NOTE: PHONES CAN BE LIFE SAVERS. DON'T RELY ON THIS PHONE AS YOUR SOLE COMMUNICATION MEANS. I HAVE NOT TESTED EMERGENCY CALLS, NOR CAN I GUARANTEE THAT THIS PHONE WILL WORK IF YOU ARE IN DANGER. CARRY ANOTHER PHONE WITH YOU. DON'T GO FOR A 3 DAY HIKE ONLY WITH THIS PHONE!
Without much ado...
To install...
- Flash the recovery from here: https://basketbuild.com/filedl/devs?dev=chrmhoffmann&dl=chrmhoffmann/fp1-kk-stock/recovery.img
- Boot into recovery and flash the rom, eg. with adb sideload. Download here: https://basketbuild.com/filedl/devs...mhoffmann/fp1-kk-stock/fp1-kk444-CH-0.9.7.zip MD5sum: 9140c93ff8f2b8327fdd330d2448c16f
- I guess you also want to flash some KK gapps that can be found somewhere (e.g http://opengapps.org/?api=4.4&variant=nano)
- You might also lose your IMEI like me? Don't PANIC! The IMEI's are noted on your FP. Remove the battery and write down the numbers. Then once you have booted the phone, follow this simple tutorial to fix this: https://www.facebook.com/fXDAdev/posts/448292925303711
Bugs:
- IMEI loss when flashing from stock FP1. No clue why this happens. Are we somehow overriding some NVRAM?
- CTS is complaining about some issues. https://christianhoffmann.info/2015.11.29_16.17.03/testResult.xml
- As this is a merge of 4.4.4 into the MTK stuff, watch out for more bugs than the previous release. Not merged: the new 4.4.4 dialer screen (we stick with 4.4.2 dialer as the modifications are too heavy), chromium does not support wml anymore (who cares?).
- You most likely need to wipe to install this when coming from the previous KK version to 4.4.4. Email app e.g. seems to crash without.
- Playstore version of Google Authenticator does not work (see https://github.com/google/google-authenticator-android/pull/4). Use the OSS version https://github.com/google/google-authenticator-android/releases - this is not specific to FP1 but seems an MTK issue.
- A dirty update (without wipe) from 0.8 on an encrypted device seems to reboot once during the "Android is upgrading" dialog
- Sometimes the lower part of the homescreen launcher seems to lose transparency.
Changelog fp1-kk444-CH-0.9.7 (you might want to check if there are new gapps here as you need to flash them again at same time: http://opengapps.org/):
- Android Security Updates from Google bulletin 1-MAY-2016 (https://source.android.com/security/bulletin/2016-05-01.html)
- Kernel CVEs including the mediatek wifi ones from https://source.android.com/security/advisory/2016-03-18.html, CVE-2016-2549, CVE-2016-2847, CVE-2016-2547, CVE-2016-2546, CVE-2016-2545, CVE-2016-2384
Changelog fp1-kk444-CH-0.9.6 (you might want to check if there are new gapps here as you need to flash them again at same time: http://opengapps.org/):
- Android Security Updates from Google bulletin 2-APR-2016 (https://source.android.com/security/bulletin/2016-04-02.html)
- Kernel CVEs including the one from https://source.android.com/security/advisory/2016-03-18.html, CVE-2015-7550, CVE-2016-0774, CVE-2016-0821, CVE-2016-0723.
Changelog fp1-kk444-CH-0.9.5 (you might want to check if there are new gapps here as you need to flash them again at same time: http://opengapps.org/):
- Android Security Updates from Google bulletin 1-MAR-2016 (https://source.android.com/security/bulletin/2016-03-01.html)
(incl. the kernel fixes that Google only publishes for Google One / Sprout - ported to MT6589)
Changelog fp1-kk444-CH-0.9.4 (you might want to check if there are new gapps here as you need to flash them again at same time: http://opengapps.org/):
- Android Security Updates from Google bulletin 1-FEB-2016 (http://source.android.com/security/b...016-02-01.html)
- Kernel CVE CVE-2015-8785
Changelog fp1-kk444-CH-0.9.3:
- Android Security Updates from Google bulletin 1-JAN-2015 (http://source.android.com/security/bulletin/2016-01-01.html)
- Some kernel CVEs (CVE2015-8543, CVE2015-8575, CVE2015-7509)
- Attempt to fix German's E-PLUS on O2 roaming
Changelog fp1-kk444-CH-0.9.2:
- Fix that you can now call funny numbers like *143# without phone application crash
- Fix to be able to add contacts to SIM card
Changelog fp1-kk444-CH-0.9.1:
- several kernel CVEs (CVE-2015-5697, CVE-2015-8539, CVE-2015-8215, and a few more without CVE yet)
- the december 1st security advisory bulletin skia issue introduced in 0.9.0 - aka as the dilbert bug - is fixed now
Changelog fp1-kk444-CH-0.9:
- android security bulletin https://source.android.com/security/bulletin/2015-12-01.html
- also update gapps if you install them: http://opengapps.org/?api=4.4&variant=nano
Changelog fp1-kk444-CH-0.8:
- google location providers are used now, which should enable network location provider (in case you installed google apps).
Changelog fp1-kk444-CH-0.7:
- National roaming should be fixed (at least as good as CM). If you still have issue with national roaming, send me your mmc/mmn data.
- Use original FP1 lens parameters for fm50af lens - does this improve the auto/manual focus issues that some people reported compared to stock FP jellybean?
- Attempt to fix the problem where sometimes the scrollbar and recents screen stopped working and screen locked despite having higher screen timeouts.
- Full CTS result: https://christianhoffmann.info/2015.11.29_16.17.03/testResult.xml
Changelog fp1-kk444-CH-0.5:
- SELinux enforcing
- Camera app now shows all resolutions
- adb now requires acceptance of adb key
Changelog fp1-kk444-CH-0.4:
- ro.adb.secure set
- browser default pages revisited (removed wrong thumbnail).
- removed MTK root CAs that are not in AOSP
- fixed remaining security false-positives in VTS and Bluebox Trustable - all green now
- USB default setting should be MTP now
Changelog fp1-kk444-CH-0.3:
- More CVE fixes (e.g CVE-2015-3845). VTS and Bluebox Trustable are almost green. For some reasons they still think "Stagefright" is not fixed. Zimperium nevertheless shows all stagefright OK. Edit: found out why. It's false positive as MTK reports errors in MPEG4Extractor differently than stock.
Changelog fp1-kk444-CH-0.2:
- Netflix issue fixed with new blob from E3
- Some CTS issues fixed
- More security fixes CVE-2014-7911
Changelog fp1-kk444-CH-0.1:
- Upgraded to 4.4.4_r2.0.1: Yay! That was an insane amount of work. The following "shortcuts" were taken:
-- Chromium sources taken from AOSP - MTK added wml but it was too much work to merge this back in
-- Email app sources taken from aosp - MTK customized something there esp. exchange sync, is that really giving someone problems?
-- Dialer app taken from MTK without 4.4.4 updates - that stuff is too heavily customized also for dual sim, and 4.4.4 revamped the UI, so this was just too much work for now.
- Latest security fixes up to November 2015. Security fixes also for wpa_supplicant_8 (thanks to Michael Bestas for collecting them for CM)
- Kernel sec fixes
- FP1 power profile xml (does this actually change anything)
As usual some credits:
- @Santhosh M : for some advice on the modem/baseband
- @keesj and fairphone for ___providing___ me a fairphone that replaced my own broken one (never figured out why it doesn't boot anymore)
- @CyanogenMod and koush for superuser stuff that I kanged into the MTK stock
- @CyanogenMod for the stagefright fixes
Let me know if
- it works also on older FP1 (without U).
- you have problems with your IMEI, too
- if you find other major issues
- if you think I am missing some security updates
- i had some issues getting the "phone" part of it work. Somehow it started working - not sure what it was. If you don't get the phone (call, etc.) to work, check your IMEIs first.

Reserved - why do all people do this?

chrmhoffmann said:
This is Android 4.4.2 kitkat compiled from scratch from some other device sources that you find on the web. Adapted to fairphone FP1(U).
It includes various security fixes on top of 4.4.2 - but most likely not all.
NOTE: PHONES CAN BE LIFE SAVERS. DON'T RELY ON THIS PHONE AS YOUR SOLE COMMUNICATION MEANS. I HAVE NOT TESTED EMERGENCY CALLS, NOR CAN I GUARANTEE THAT THIS PHONE WILL WORK IF YOU ARE IN DANGER. CARRY ANOTHER PHONE WITH YOU. DON'T GO FOR A 3 DAY HIKE ONLY WITH THIS PHONE!
Without much ado...
To install...
- Flash the recovery from here: https://basketbuild.com/filedl/devs?dev=chrmhoffmann&dl=chrmhoffmann/fp1-kk-stock/recovery.img
- Boot into recovery and flash the rom, eg. with adb sideload. Download here: https://basketbuild.com/devs/chrmhoffmann/fp1-kk-stock
- I guess you also want to flash some KK gapps that can be found somewhere (e.g http://opengapps.org/?api=4.4&variant=nano)
- You might also lose your IMEI like me? Don't PANIC! The IMEI's are noted on your FP. Remove the battery and write down the numbers. Then once you have booted the phone, follow this simple tutorial to fix this: https://www.facebook.com/fXDAdev/posts/448292925303711
Bugs:
- IMEI loss when flashing from stock FP1. No clue why this happens. Are we somehow overriding some NVRAM?
As usual some credits:
- @Santhosh M : for some advice on the modem/baseband
- @keesj and fairphone for ___providing___ me a fairphone that replaced my own broken one (never figured out why it doesn't boot anymore)
- @CyanogenMod and koush for superuser stuff that I kanged into the MTK stock
- @CyanogenMod for the stagefright fixes
Let me know if
- it works also on older FP1 (without U).
- you have problems with your IMEI, too
- if you find other major issues
- if you think I am missing some security updates
- i had some issues getting the "phone" part of it work. Somehow it started working - not sure what it was. If you don't get the phone (call, etc.) to work, check your IMEIs first.
Click to expand...
Click to collapse
so far it works on my fp1 (without U), no Problems with my IMEI-Numbers. Thank you very very much, great!

Just flashed it and it works! Thank you so much! (although instructions how to create such a rom would be nice for me )
EDIT: some answers to your question:
I am using the FP1u.
No problems with my IMEI.
Other major issues: none noticed, and this actually fixed the transparency bug in the Play Store
Missing security patches: Stagefright CVE-2015-6602 is not fixed.
Thank you very much!

How do i flash the recovery? the typicall fastboot method does not work for me (says "flash not supported")

fredflegel said:
How do i flash the recovery? the typicall fastboot method does not work for me (says "flash not supported")
Click to expand...
Click to collapse
There's an old thread about it: http://forum.xda-developers.com/showthread.php?t=2615613
So in this case:
Code:
adb push recovery.img /sdcard/
adb shell
su
dd if=/sdcard/recovery.img of=/dev/recovery
And because I can never remember if it's volume up or down when powering on: "Hold the Volume Up button, while at the same time press and hold the Power button. Hold these two buttons at the same time for about 10 seconds until the screen changes."
Then install from sideload, etc. and
Code:
adb sideload fp1-kk-stock-0.1.zip
Takes quite a while to update. I did NOT disable rom recovery, I don't think this one reverts the recovery, right?
aaaand
Sound and bluetooth seem to work fine, didn't test more so far.
Edit: By the way, are you going to do a Lollipop rom? That would be even more awesome than this. Meanwhile: Good job for raising the FP1 software to the minimum requirements for today.

Great Work! Thanks alot!
I will check this rom thoroughly. On little cosmetic issue that was fixed in Fairphones official rom is the issue with national roaming in german 02/E-Plus networks. I now allowed data roaming as a workaround, but this can get pretty expensive pretty soon. Any chance you can fix that in a future build?

fredflegel said:
Great Work! Thanks alot!
I will check this rom thoroughly. On little cosmetic issue that was fixed in Fairphones official rom is the issue with national roaming in german 02/E-Plus networks. I now allowed data roaming as a workaround, but this can get pretty expensive pretty soon. Any chance you can fix that in a future build?
Click to expand...
Click to collapse
You can enable "National data roaming" with GravityBox, which you can install via the Xposed installer. Helped in Austria with bob (and A1)

You forgot to mount the "external" storage:
Code:
tmpfs /storage/emulated tmpfs rw,seclabel,relatime,mode=755,uid=1023,gid=1023 0 0
Workaround for getting the correct one for now:
Code:
umount /storage/emulated
mount -t vfat /dev/block/mmcblk0p8 /storage/emulated
But there are still symlinks to /storage/emulated/legacy.
So that needs some kind of fix up.

ccxxx said:
You forgot to mount the "external" storage:
Code:
tmpfs /storage/emulated tmpfs rw,seclabel,relatime,mode=755,uid=1023,gid=1023 0 0
Workaround for getting the correct one for now:
Code:
umount /storage/emulated
mount -t vfat /dev/block/mmcblk0p8 /storage/emulated
But there are still symlinks to /storage/emulated/legacy.
So that needs some kind of fix up.
Click to expand...
Click to collapse
I think that you are using the old non-repartitioned fp1?
There's no such thing as /dev/block/mmcblk0p8 anymore on the repartitioned devices.
Chris

chrmhoffmann said:
I think that you are using the old non-repartitioned fp1?
There's no such thing as /dev/block/mmcblk0p8 anymore on the repartitioned devices.
Chris
Click to expand...
Click to collapse
Uhm, yes, I guess.
TIL https://fairphone.zendesk.com/hc/en-us/articles/201327645-What-is-Fairphone-s-storage-layout-

ccxxx said:
Uhm, yes, I guess.
TIL https://fairphone.zendesk.com/hc/en-us/articles/201327645-What-is-Fairphone-s-storage-layout-
Click to expand...
Click to collapse
You should then upgrade. It's much nicer with a single partition... And as you can see, I don't support the old storage layout any more
Chris

Upgrade to 4.4.4. available
See OP. Please test this. It's an update to android 4.4.4 and lots of additional security fixes.
Oh, and yeah, I recommend to wipe. Email (e.g. and maybe others) will crash without.
Chris

It wasn't obvious, how to do that, so I downloaded the "Storage Upgrader 1.8.7 * (~200MB)" from https://fairphone.zendesk.com/hc/en-us/articles/201189497-Fairphone-OS-multiple-versions-
It doesn't update the partitions when flashing, it does so on the first boot. It also overwrites the recovery.
After that I installed the 4.4.4 image and it boot loops: https://gist.github.com/ChristophHaag/64da8b31533d2c562c92
edit: And so does the 4.4.2 image that has worked before.
*sigh*
edit 2: Formatted a few partitions and tried again - now 4.4.4 works.

0.2 released.
It should fix Netflix (will confirm when all apps are installed after wipe) and should also squash a security problem that bluebox reported (CVE-2014-7911).
It should also make less CTS tests fails.
Still uploading... Edit: Uploaded.
Chris

Hallo, nach dem neuesten update funktioniert xposed-aktivierung nicht mehr. Sonst alles bestens
Sorry, in english:
After the newest update to 4.4.4 no chance to activate xposed-framework. Anyway, thanks a lot
for your hard work

btw Google Authenticator doesn't seem to work correctly on the 4.4.2 version. Authy works though.

jogri said:
Hallo, nach dem neuesten update funktioniert xposed-aktivierung nicht mehr. Sonst alles bestens
Sorry, in english:
After the newest update to 4.4.4 no chance to activate xposed-framework. Anyway, thanks a lot
for your hard work
Click to expand...
Click to collapse
Yes, the last security patches break xposed. https://android.googlesource.com/pl...+/d4d3181d013f8d9b96de8e396b029f8a418894a7^!/
See e.g. here: https://plus.google.com/114407246718577124209/posts/BwiPxSu84bD
Chris

z3ntu said:
btw Google Authenticator doesn't seem to work correctly on the 4.4.2 version. Authy works though.
Click to expand...
Click to collapse
This is most likely related to this issue: https://github.com/google/google-authenticator-android/pull/4
It is most likely an MTK issue with problematic math library (or something like that).
Anyway, it works for me when I use the open source version of the google authenticator: https://github.com/google/google-authenticator-android/releases
Chris

Jeah, I used the Play Store version, but this is also mentionable in "known bugs" (and that they should use the open-source version)

[CLOSED][Overlay] Dil3mm4's Overlays for Prague Series devices (all variants)

This overlay APK it's "born" because of the necessity to overcome missing overlays (thanks Huawei, love ya xoxo) under /vendor/overlay .
What it does exactly?
Nothing more than adding AOSP overlay matching our device capabilities and also, inherits Prague power profile.
Do I need it?
Well, better having than don't.
This will conisderably enhance your experience on every GSI ROM giving better functionality overall.
Why you did that?
Because I'm sick of inheriting stuff that belongs to /vendor, in system.
Project Treble it's all about separating vendor implementation from system.
So why we should keep adding OEM stuff in there, if it doesn't belong no more in /system?
I have XYZ device with ZYX firmware can I use it?
As long as you're on a PRA-*** device (with a non-EMUI firmware), you're good to go.
Otherwise DO NOT USE IT FOR THE LOVE OF MANKIND.
I don't have PRA, but I want it on my Huawei device !
Well, that's fine, join the Telegram group @GSI_HI6250, so that you could help me with stock files grabbing to make an overlay for your device.
Overlay configs (aka "what does dis do, ser tell pl0x"):
Allows all rotations;
Configs autobrightness levels;
Configs autobrightness Lcd values;
Configs BLE;
Sets Doze Component;
Sets Doze After screen off;
Configs autopowermodes (doze related);
Configs power management on:
screen off due to proximity sensor interaction;
decouple on suspend state;​
Configs brightness doze value;
Configs Intrusive led;
Configs dual band wifi support (where available);
Configs hotswap (where available);
Configs Color Transform on HWC;
Configs VoLTE available (even tho it needs support on GSI side);
Configs WFC over IMS;
Configs wifi background scanning support.
Installation Instructions
Download the overlay from the Downloads session.
With root, push the overlay to /vendor/overlay. Create the folder if it doesn't exist.
Run the following command in a rooted terminal or ADB shell:
Code:
chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay;chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay/dil3mm4-overlay-PRA.apk
XDA:DevDB Information
[Overlay] Dil3mm4's Overlays for Prague Series devices (all variants), Device Specific App for the Huawei P8lite/P8 Lite
Contributors
Dil3mm4
Version Information
Status: Stable
Created 2018-06-26
Last Updated 2018-06-26

Definitely will be useful. Thanks a lot, Dil3mm4!

Hi Dil3mm4,
Thanks for your work, but I'm not sure what this app does exactly, will it help me for example with substratum themes? Thanks

Hi @Dil3mm4 let me understand correctly:
- i'm under LineageOS 14.1 (Haky86 version). Am i concerned with your fixes ?
- i plan to go to LOS 15.1. Should i flash LOS 15.1 before, then install your fixes ?
- if i can go to LOS15.1 from Prject Treble, what device should i choose ? A or A/B ? I assume this is ARM64.
Thank you VM back in the ROM selection after 1 year, and i have things to understand

Graveen said:
Hi @Dil3mm4 let me understand correctly:
- i'm under LineageOS 14.1 (Haky86 version). Am i concerned with your fixes ?
- i plan to go to LOS 15.1. Should i flash LOS 15.1 before, then install your fixes ?
- if i can go to LOS15.1 from Prject Treble, what device should i choose ? A or A/B ? I assume this is ARM64.
Thank you VM back in the ROM selection after 1 year, and i have things to understand
Click to expand...
Click to collapse
Our device is arm64 A only (PRA-LX1 is my device)
If the APK is included in the rom u want to flash just run the command below, if not, after flashing just install the overlay according to the instructions. Have a nice day!

I will probably make a question that doesn't make sense since it's probably hardware related. But will this overlay add 5ghz support to our devices?

mannas said:
I will probably make a question that doesn't make sense since it's probably hardware related. But will this overlay add 5ghz support to our devices?
Click to expand...
Click to collapse
Nope

UPDATE
-P compatibility
-Improved brightness levels
DOWNLOAD

Hey Dilemma! I have an issue with all the Treble Roms. After listening to music for a while, the playback stops and I have to restart it, or when I plug a headphone in and then out, sound usually doesnt come out of the speaker. Will this overlay fix the issues I have with treble Roms? Thanks in advance

Please help with a little overlay
Dil3mm4 said:
This overlay APK it's "born" because of the necessity to overcome missing overlays (thanks Huawei, love ya xoxo) under /vendor/overlay .
I don't have PRA, but I want it on my Huawei device !
Well, that's fine, join the Telegram group @GSI_HI6250, so that you could help me with stock files grabbing to make an overlay for your device.
Click to expand...
Click to collapse
Hello Dil3mm4.
Sorry to send you PM, i see after sending that's not ok. I really want to solve Overlay issue for my Huawei Fig-LX1.
I try to join Telegram group indicated by you but could not find it. Maybe is not existing anymore. So - my last chance is you to respond here.
I just want you to make an overlay for my phone to work better with Phusson Treble 8.1. Just tell me what files do you need and i will do it.
Maybe you answer me.
Thanks!

Hi, by fixing BLE, you mean bluetooth low energy, like huawei band, fossil Q ?
thanks

Thanks! U did great!

Hi
I've tried to install this file but after I've enter the code, it says system is readable only.
I've tried with adb shell and terminal(booth of them rooted) and it didn't work
I've even tried to mount system as rewritable but it didn't work.
I'm on Aex 6.6 latest version(and I was on PRA-LA1 8.0.0.370 C185 before i flashed this custom rom)
What should I do to fix this error?

Traceur017 said:
Hi
I've tried to install this file but after I've enter the code, it says system is readable only.
I've tried with adb shell and terminal(booth of them rooted) and it didn't work
I've even tried to mount system as rewritable but it didn't work.
I'm on Aex 6.6 latest version(and I was on PRA-LA1 8.0.0.370 C185 before i flashed this custom rom)
What should I do to fix this error?
Click to expand...
Click to collapse
install terminal emulator , put the .APK (be sure to rename the last build taking the -P ) in the mencioned directory but first run the following command:
su
mount -o remount,rw /vendor
after this you can run the command for the apk.
It worked for me. or at least.. didnt gave an error... so.. lolol

I think I've installed it correctly but How can I see changes? Nothing added!

Hello, I have a PAR-AL00 device. Can you make an overlay for me.and Telegram group @GSI_HI6250, I can't find it.Thank you verymuch.

I don't understand, where is the overlay link?
Edit : Sorry, I didn't know it was in the download tab.

I can't find it where is it?
artus777 said:
I don't understand, where is the overlay link?
Edit : Sorry, I didn't know it was in the download tab.
Click to expand...
Click to collapse

Is this overlay necessary under Lineage 18.1 (PRAGUE device and EMUI 8.0.0.390)?

@Dil3mm4 Thread closed! Please advise the moderators team (best via the report function) to re-open the thread when ready to provide a download link for this former DevDB thread.
Regards
Oswald Boelcke
Senior Moderator

[ROM][ALPHA] Unofficial Lineageos15.1

LINEAGE OS
This is an Alpha build of lineageos15.1
Working:
-RIL
-Bluetooth
-Camera (at least 1 of them)
Not Working:
-Probably selinux (did not try enforcing kernel yet)
-Probably encryption (logcat says it works...)
-Wlan (maybe bcs some files from vendor/vendor_system in /system are missing)
-2nd camera (fix could be to use micamera app)
-Probably more
Instructions:
-Download V9.6.11.0.ODLMIFF_8.1 original rom
-go to V9.6.11.0.ODLMIFF/images
-Replace boot.img, with boot.img
-Replace system.img and system_other.img with system.img
-use the flash_all script. THIS WILL WIPE ALL YOUR DATA, EVERYTHING! if you want to go back now (or later) just put the original images back again and use flash_all_except_storage
-Directly after the device reboots by itself, press vol up + power (u might have to hold it until device reboots again) to enter los recovery
-"factory reset--> wipe data"
-If you want TWRP "advanced-->reboot bootloader" and flash TWRP accordingly to thread, then u can flash gapps/mods.
-reboot
-give it time to boot
Source:
ROM
Device branch "los15"
msm8953-device
Kernel
To finish, I WON'T CONTINUE THIS ROM the trees are working, P vendor is there, an adaption to los16 should be possible based on that. Also, i prefer OMNIROM (which i will try to build next).
Thanks goes to:
-Google for the search engine as well as for the source code
-Cozzmi13 for taking some time to show me the basics.
-Lineageos
-Github
-ada12 for offering his help

thankssss

im wait until wlan fix, but thanks for your effort

CreateYourDream said:
im wait until wlan fix, but thanks for your effort
Click to expand...
Click to collapse
I NEED TESTERS
I am building omni now, so cant go back to los and test but if someone can test i might be able to fix it.
TEST:
-download attached zip
-open on pc or device
-copy the files to the corresponding folder (the folder they are in) in "/system" with a root file manager or adb. CAREFUL do not overwrite files already existing. PLEASE only copy the things in etc (especially etc/firmware/wlan/prima/WCNSS_cfg.dat) first, reboot, check if working, if doesnt work, copy other things.
-set permissions accordingly to other files in same folder
-reboot and check if wifi works

It would be nice to have logs, then I could help.

If you ever need help with your omnirom build i would love to help out with everything that i can. Daisy really needs more support to be a very good device.

hi!
anyone know, is this build of LOS 15.1 support correct notch area?
and what about Onmi build?
i want give possible help if need)

Thanks for your work, I hope soon More roms for this great device

ok, installed)
not work:
sound jack (and fm-radio because headset not detected);
notch not apply;
charger led;
wi-fi
bug: sometimes after tapping screen blink with red border
other thing worked in first try. quick and stable but it's very outdated)
.

wertus33333 said:
I NEED TESTERS
I am building omni now, so cant go back to los and test but if someone can test i might be able to fix it.
TEST:
-download attached zip
-open on pc or device
-copy the files to the corresponding folder (the folder they are in) in "/system" with a root file manager or adb. CAREFUL do not overwrite files already existing. PLEASE only copy the things in etc (especially etc/firmware/wlan/prima/WCNSS_cfg.dat) first, reboot, check if working, if doesnt work, copy other things.
-set permissions accordingly to other files in same folder
-reboot and check if wifi works
Click to expand...
Click to collapse
not worked
and usb-tethering too

eremitein said:
sometimes after tapping screen blink with red border
Click to expand...
Click to collapse
I understood why this is happening
I saw the same behavior in the AEX build, which
used the build type "eng"
you also

Can anyone give me the logs for the bugs?

Is this Rom abandoned?

ghanipradita said:
Is this Rom abandoned?
Click to expand...
Click to collapse
Yup. This phone is abandoned in general, which is a shame

eremitein said:
ok, installed)
not work:
sound jack (and fm-radio because headset not detected);
notch not apply;
charger led;
wi-fi
bug: sometimes after tapping screen blink with red border
other thing worked in first try. quick and stable but it's very outdated)
.
Click to expand...
Click to collapse
Thanks for testing. saksham is working on a new build (with updated vendor, etc), will let you know if we need testers.
Nice to know: The blinking red borders show layout updates, they flash in all eng (=developer) builds. If changing the build variant to userdebug (debuging enabled) or user (oem/production builds with few debuging enabled) they vanish.

ghanipradita said:
Is this Rom abandoned?
Click to expand...
Click to collapse
kftX said:
Yup. This phone is abandoned in general, which is a shame
Click to expand...
Click to collapse
Nope, it is not abandoned but we are very few people working on it and none of us has great android experience. Also, all of us do this in our spare time and therefore it can take time. If you want to speed up the build, supply logs (clean install rom, install adb on pc, execute
Code:
adb bugreport > bugreportDATE.txt
or
Code:
adb logcat > logcatDATE.txt
, share the reports), error descriptions (like @eremitein) and/or read on how to build a rom for a device yourself.
eremitein said:
I understood why this is happening
I saw the same behavior in the AEX build, which
used the build type "eng"
you also
Click to expand...
Click to collapse
oh, you already saw this xD

wertus33333 said:
Nope, it is not abandoned but we are very few people working on it and none of us has great android experience.
Click to expand...
Click to collapse
Editing this out of respect even though none was shown.
Also, I would love to help but with the lack of a proper working TWRP (encryption, restore backup issues) I really can't give it the time needed with all the stuff I'd have to reinstall every time, since I need my phone up and working nearly 100% of the time. If a decent version TWRP is released, I'll gladly help.
Glad you're still working on this though, just don't act like we should've known that you still where when the thread was dead for months. Good luck.

wertus33333 said:
Thanks for testing. saksham is working on a new build (with updated vendor, etc), will let you know if we need testers.
Click to expand...
Click to collapse
successful build, always happy to help

is there any reason you build los 15.1 instead of 16?

skyline91 said:
is there any reason you build los 15.1 instead of 16?
Click to expand...
Click to collapse
At the time i built the rom only 8.1 vendor (8.1 official rom) was avaiable. as i'm not really experienced with android it was easier to build 8.1 rom instead of trying to port vendor to 9.0 (while 9.0 vendor would have defenitely be officially out in a month or 2 ) and build los16. porting the device tree from 15.1 to 16.0 should be easy. Also, i don't like los, i want omni .

[ROM][A515F/DS][OneUI 3.1 - S20 Port] Just4Fun v1

HELLo everyone...
After several weeks, months and before Android 12 released, i decided to share this ROM to this A51 community. Hopefully you guys enjoy it and don't offend me if the ROM is bad, so....let's get it ON.
Things to do before flashing:
1. Make sure you're on binary 5 (this ROM tested and using binary 5 vendor, so to avoid any broken or whatever error flash your device with latest firmware).
2. Backup your IMEI (highly recommended).
Flashing:
1. Clean flash is recommended. Flash kernel, flash J4F vendor and system.img, flash multy disabler (if necessary) then full wipe and also you can perform "typing YES" format. Reboot to recovery again, then flash as usual you guys always do (Magisk etc.).
ROM Features from S20 and Note 20 line up:
1. Samsung Dex (not full features coz need fix at kernel level).
2. Flagship live blur
3. Flagship edge lighting style
4. AirCommand (S pen)
5. LiveDrawing
6. Multy screen resolutions (HD+ - FHD+ - WQHD+)
7. 1000++ system fonts
8. Flagship sound quality and effects
9. Camera features unlocked (pro video etc.)
10. All original A51 features
11. Common tweaks here and there and so many possibility to unlock another S20 features
Bugs:
Minor glitch in pro mode video, and not really remember and deep testing everything, but hopefully still acceptable (hopefully ) but yeah..nothing's perfect, if you found one let's discuss together in A51 telegram group: https://t.me/samsunga51
Hall of Fame:
@MrWaehere for his awesome CRB kitchen
@VDavid003 and his rom TreeUI for my inspiration and countless help
@Yillié and his OFox recovery and also countless help and advise and ideas
@BlassGO and his Dynamic Installer, patches, advise and countless contributions (thanks for making AirCommand even greater lol)
@manudinath and his projects.
@Winb33 for fonts mod
@topjohnwu for Magisk
@ianmacd for multy disabler and TWRP
Stock Kernel Source
PM me if i forgot to mention someone.
Advise and Tips:
- It's normal during first boot if lags occurs, give the ROM some times to settle, finish your setup, update your apps and you good to go..
- It's better to avoid update in Galaxy store related to system app, such as MDE Service Framework, Samsung Core Services etc. It might causing conflict due to mixed up firmware. But anyway it's up to you.
- Please do not complain regarding app missing (getting debloated) and related to debloat. Because it's very hard to acomodate every person's taste. Bloatware is very Objective and absurd for each person and I know it's supposed to be using Aroma installer or any script but i don't have time that much to do that.
Download link:
**when you click this link and downloading, that's mean you're agree to all the consequences and i'm not responsible to anything - do with your own risk**
LINK

Pero peeps. Sorry for not being able to test all the stuff properly xD.

Yillié said:
Pero peeps. Sorry for not being able to test all the stuff properly xD.
Click to expand...
Click to collapse
nah, you have doing so great/ thank you s much for everything.

Testing .

perro

Ole its already, nice

Quick question, what am i supposed to select while flashing J4F.img in TWRP, boot, recovery, optics img, prism img or super.

@jagpanzer Please check your PM inbox. Thank you.
-Regards: Badger50

BlassGO said:
Ole its already, nice
Click to expand...
Click to collapse
Ia possible wirh This vendor run fingerprint perfectly in havoc

Badger50 said:
@jagpanzer Please check your PM inbox. Thank you.
-Regards: Badger50
Click to expand...
Click to collapse
If run for You send details my friend

Someone knows how to pass CTSprofile in magisk with this rom?

gobblefunk said:
Quick question, what am i supposed to select while flashing J4F.img in TWRP, boot, recovery, optics img, prism img or super.
Click to expand...
Click to collapse
system and vendor.

BlassGO said:
Ole its already, nice
Click to expand...
Click to collapse
mhm...thanks for everything

jagpanzer said:
system and vendor.
Click to expand...
Click to collapse
Kernel 11 support this ROM?

Magisk 23.1
Download Magisk 706a4922 alpha apk
Download File Magisk 706a4922 alpha apk
apkadmin.com

Changelog magisk 23.1
DOWNLOAD VERSion ALPHA:
Magisk v23.1 (706a4922-alpha)
Changelog:
• Switch to zygisk to execute the deny list,
• Magiskhide has been completely removed
• Denylist Added
• Restart to take effect after changing the switch state of zygisk
• Major changes, some problems may occur, temporarily not pushed to the update channel
Others changes in APK:
[General] supports pure 64-bit devices
-[General] Support Android 12 emulator
-[Zygisk] code injection framework
-[General] Remove MagiskHide
-[General] Support simulator loading module
-[MagiskBoot] supports zImage format
-[MagiskBoot] Add zopfli encoder
-[MagiskInit] supports boot configuration
-[App] Repair installation function will now check whether the script under /data/adb/magisk/ is not updated
-[MagiskInit] supports some Meizu devices
-[MagiskSU] If supported by the kernel, use isolated devpts
-[MagiskSU] Fix pts configuration code, no additional sepolicy rules are now required
-[MagiskBoot] supports v4 boot image header format
-[MagiskInit] Support some OnePlus and Opal devices Oplus.fstab
-[App] The update module needs to be restarted, mark deletion is not allowed
-[App] Delete online warehouse
-[App] Add mount information to the saved log file
-[App] Adapt to Android 12 API level
-[App] Display running waiting pop-up window when hiding/resuming the application
-[Stub] Open source obfuscation function
-[Script] View and display the sepolicy rule folder of the module
-【App】Hide the screen overlay when you need to pop up the window. Android 12+
-[App] Delete the floating bottom bar and change it to a general bottom operation bar
-[General] Support compilation cache
-[General] Added rejection list function
-[App] Delete DoH
-[App] Delete SafetyNet

Can you please also make this rom for M30s ??
Because both have similar specs and same soc !

Bluetooth connect error

hacker812c said:
Kernel 11 support this ROM?
Click to expand...
Click to collapse
during testing i only test with BF2. you can try
Arya1999 said:
Can you please also make this rom for M30s ??
Because both have similar specs and same soc !
Click to expand...
Click to collapse
sorry, no time.
Inomjon6940🇺🇿 said:
Bluetooth connect error
Click to expand...
Click to collapse
last time i try with old BT 4.0 earphone was fine and also BT call. will test again, on last build i've made changes and could be broke something