Related
FEEL FREE TO DONATE US FOR ALL WE'RE DOING FOR YOU!
For general discussions, bug reports and FAQ, write HERE!
Credits:
P880-dev sources
MoltenMotherBoard!
Downloads:
MoltenMotherBoard mirror | AndroidFileHost
Full sources:
MoltenMotherBoard sources: MoltenMotherBoard | Github
Device: platform_device_lge_p880 | Github
Kernel: lge-kernel-p880 | Github
Changelog:
20150101
telephony: SignalStrength: hotfix GSM and TD-SCDMA
imgdiff: search the magic number 1f8b0800 starting from the ramdisk page
build: no more needed make 4.X support
p880: lights: disable backlights for notifications and power supply
p880: re-include missing GPS configuration files
AOSP updates
20141204
system/extras: exclude Google SU binaries
p880: include CM SU binaries by default
p880: force-build libemoji module
p880: force-build e2fsck module
hardware/broadcom/wlan: dhd: add missing fini interface command
p880: restore old manual density parameter
p880: restore old WiFi firmwares path
AOSP updates
20141203
init: add a mechanism to extend the property service in device configs
p880: sources up-to-date with CyanogenMod
build: allow build with make 4.1
kernel/lge/x3: corrected patch "disable setting security contexts on rootfs inodes"
build: switch to custom apns-conf.xml
manifest: update to android-4.4.4_r2.0.1
manifest: switch to CyanogenMod kernel (branch cm-12.0)
vendor/mmb: add MMB banner
vendor/mmb: add support for init.d scripts
vendor/mmb: add APNs up-to-date with OMNI
vendor/mmb: add support for ADB over the network
p880: inherit MMB vendor
p880: device_perms: add device perms for LCD density
p880: ril: remove deprecated rmnet scripts
p880: prop: disable LTE (it's not supported on P880)
p880: init: update TCP buffer sizes and thresholds
p880: init: add miscellaneous updates from CM's branch
p880: fstab: usb: detect filesystem instead of hardcoding
p880: ril: add SIM state change string
p880: ril: fix LGE recovery with new TS0710_mux driver
p880: fstab: enable /data encryptionon FOTA partition
p880: init: add TCP delayed and autotuning settings to init
p880: overlay: disable fading marquee
p880: init: enable OTG host
p880: init: small adjustements for optimal effectiveness
p880: init: restructure x3 init to accomodate kernel changes
AOSP updates
20140928
packages/apps/Camera2: fix camcorder access
frameworks/native: miscellaneous OMNI updates
hardware/libhardware: add missing declarations needed by native
manifest: update to android-4.4.4_r2
p880: gps: update GPS configuration to current standards
p880: fstab: update mount options
p880: audio_policy: use only one sampling rate on submix
p880: correct PRODUCT_MODEL string
p880: init.rc: fix DHCP permissions
p880: correct partitions sizes
p880: bluetooth: add BLE flags
p880: selinux: add a sensor and smartdimmer sepolicy
p880: init.rc: adjusted GPS permissions
p880: init.rc: additions for better battery life
p880: relaxed cpu.speeds and cpu.active consumption adjustments
p880: camera: improve AAC audio codec
p880: camera: increase Image encoding quality
p880: camera: add 720p recording in front camera
p880: camera: switch to MP4 instead of 3GP for recordings
p880: camera: add ffmpeg Audio & Video decoders
build: Prevent zip to replace /recovery partition
p880: device cleanup
AOSP updates
20140704:
hardware/broadcom/libbt: bluetooth: add support for board-specific configuration
p880: camera: add HAVE_ISO flag support
frameworks/av: camera: add HAVE_ISO flag support
frameworks/base: backlights: reintroduce button-backlight (and respective inactivity timeout)
kernel: selinux: fix /cache partition mounting (and /cal, /persist-lg, /mpt and /mnt/shell/emulated along with it)
frameworks/native: audio: register Tegra audio devices as service
p880: bluetooth: enable BLE peripheral mode
p880: use P880-dev's RIL
manifest: updates to 4.4.4_r1
AOSP updates
TB-20140527
First build
Issues:
-----
Do you want to report an issue? Do it here!
In order to do it, create a new issue, choosing correct labels corrisponding to: Device/OS which you're using, ROM/project you're on, kind of issue.
Also, please, be sure you're running the ROM/project in the exact way we've provided it to you (do not create issues if you're using different
kernel, mod, plugins and dependencies we didn't tell to use).
General Questions: MoltenMotherBoard Projects | General Questions and Info
XDA:DevDB Information
AOSP KitKat 4.4.X, ROM for the LG Optimus 4X HD
Contributors
MoltenMotherBoard, streambinder
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.1.x
Version Information
Status: Stable
Created 2014-06-11
Last Updated 2014-08-27
Hey. I'm the project mantainer.
First of all, it's my first thread here: then, I don't want to be overbearing in offering my work, never.
If I would ever result like that, please tell me.
About the project: my team has always followed AOSP projects, even with ARMv6.
This time I decided to work on it, for this phone, as I need bugfree sources even for it, as for all the others custom ROMs.
The build shared is only the result of the first compilation, quickly tested by me.
I would like to ask you to test and report any bug you experience, so that we can reach as soon as possible a bugfree release.
Obviously, planning to update manifest to 4.4.3.
Very fast ! Tho I have issues with signal, its very low and when you try to download something from browser it crashes. Cant turn off NFC. Gallery not mounted. This ROM is going to be amazing !
ex0rt said:
Cant turn off NFC.
Click to expand...
Click to collapse
Reboot.
Any screenshot?
Thanks
ex0rt said:
Very fast ! Tho I have issues with signal, its very low and when you try to download something from browser it crashes. Cant turn off NFC. Gallery not mounted. This ROM is going to be amazing !
Click to expand...
Click to collapse
Thanks for the report.
For gallery 'not-mounting', what do you mean?
For NFC, as Adam said, you need to reboot.
Everytime you experience an issue and report it, please, add a log.
Gonna work on 4.4.3 this afternoon.
I Think On This Rom Does Not Have Reboot?
Sent from my LG-P880 using Tapatalk
streambinder said:
Thanks for the report.
For gallery 'not-mounting', what do you mean?
For NFC, as Adam said, you need to reboot.
Everytime you experience an issue and report it, please, add a log.
Gonna work on 4.4.3 this afternoon.
Click to expand...
Click to collapse
When I open it, I just couldn't access, it says storage not mounted or something similar. Looking forward for new version
Thanks @streambinder and @Adam77Root
ex0rt said:
When I open it, I just couldn't access, it says storage not mounted or something similar. Looking forward for new version
Thanks @streambinder and @Adam77Root
Click to expand...
Click to collapse
Ok, that should be easy to be fixed, I think, as I have a fix in mind!
Will make a 4.4.3 build and check it.
Would it be possible to upload your sources (I mean those repos you have altered, like frameworks/base, frameworks/av, frameworks/native, hardware/libhardware,...) so others can use it as a base for their project?
and would you mind adding a proper commit history to the p880 device tree?
laufersteppenwolf said:
Would it be possible to upload your sources (I mean those repos you have altered, like frameworks/base, frameworks/av, frameworks/native, hardware/libhardware,...) so others can use it as a base for their project?
and would you mind adding a proper commit history to the p880 device tree?
Click to expand...
Click to collapse
Yep, it would be possible and I'll do it at the same moment I publish a build using different/altered sources.
The build shared is using stock AOSP sources, plus stock P880-Dev device tree and kernel.
Obviously, will need some alterations to make everything working, then, I'll do it, of course!
streambinder said:
The build shared is using stock AOSP sources, plus stock P880-Dev device tree and kernel.
Click to expand...
Click to collapse
That means at least the following stuff doesn't work: camera, audio, sensors, Bluetooth, mobile data. I say at least as these are whose come to my mind right now.
Sent from my OmniROM-powered LG Optimus 4X HD
Adam77Root said:
That means at least the following stuff doesn't work: camera, audio, sensors, Bluetooth, mobile data. I say at least as these are whose come to my mind right now.
Sent from my OmniROM-powered LG Optimus 4X HD
Click to expand...
Click to collapse
You can add button backlight to the list as well, but BT might even work, at least it did when I ported APSP 4.3
Adam77Root said:
That means at least the following stuff doesn't work: camera, audio, sensors, Bluetooth, mobile data. I say at least as these are whose come to my mind right now.
Sent from my OmniROM-powered LG Optimus 4X HD
Click to expand...
Click to collapse
laufersteppenwolf said:
You can add button backlight to the list as well, but BT might even work, at least it did when I ported APSP 4.3
Click to expand...
Click to collapse
Didn't test every function: maybe all of them are not properly working, that's why I shared a TB (Test Build).
Obviously, will do everything needed and asked by @laufersteppenwolf for next release.
Thank you for an AOSP taste for our p880! Was about time :b
MidnightDevil said:
Thank you for an AOSP taste for our p880! Was about time :b
Click to expand...
Click to collapse
You have to thank P880-dev, I did nothing but mounted correct sources, the most superficial part the whole job!
streambinder said:
You have to thank P880-dev, I did nothing but mounted correct sources, the most superficial part the whole job!
Click to expand...
Click to collapse
Thank you p880-dev :b
Aka wolf, Tetris, Adam, and all the dev fellows!
And you, 'cause I asked wolf for a aosp release but he's one lazy bum no offense stef
Some bug?
Thanks
Okay, guys. Correctly made a new 4.4.3-code based build: it's useless now to release it, as, as told by @Adam77Root and @laufersteppenwolf, many things aren't correctly working.
Used the same - updated - sources used for the first build, just re-adapted to make them compiling for AOSP.
@laufersteppenwolf: going to upload them, also because need to apply some important patches - as you know, to fix whatever is not working on AOSP.
Atleast thank you for your time for our device! I was looking forward for this. Thanks!
Sent from my LG-P880 using XDA Premium 4 mobile app
Hey Guys,
Apparently the Nexus 5 is going to have mainline linux kernel support from 4.9 and onwards.
Any idea what this could mean for developer support apart from possibly running actual Linux on the thing?
Link: http://www.phoronix.com/scan.php?page=news_item&px=Linux-4.9-ARM-Pull
That means nothing, we would need more time to addapt and fix stuff that improving new ones. Yes Nexus 5 will support it, but it will mean nothing, some kernel devs already talked about it too.
But will qualcomm blobs work on 4.9 kernel?
Jaizu said:
That means nothing, we would need more time to addapt and fix stuff that improving new ones. Yes Nexus 5 will support it, but it will mean nothing, some kernel devs already talked about it too.
Click to expand...
Click to collapse
Yes I understand that obviously, it just gives me some hype for the future. A bit of a Nokia N9 like phone on the android side of things.
GR0S said:
But will qualcomm blobs work on 4.9 kernel?
Click to expand...
Click to collapse
Probably not, although Freedreno has support for the Nexus 5, other stuff may not work.
It seems just added device tree configurations.
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/?qt=grep&q=hammerhead
ganachoco said:
It seems just added device tree configurations.
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/?qt=grep&q=hammerhead
Click to expand...
Click to collapse
And now there's some new stuff! Could you comment on it?
how can we break secure boot?
Pure CAF @ crLOS 14.1
Vulkan Graphics API
The Android platform includes an Android-specific implementation of the Vulkan API specification from the Khronos Group. Vulkan is a low-overhead, cross-platform API for high-performance, 3D graphics. It provides tools for creating high-quality, real-time graphics in applications. Vulkan also provides advantages such as reducing CPU overhead and providing support for the SPIR-V Binary Intermediate language.
It also provides a new generation graphics and compute API that provides high-efficiency, cross-platform access to modern GPUs used in a wide variety of devices from PCs and consoles to mobile phones and embedded platforms.
Installation:
# Download the Vukan api zip
# Install it using TWRP recovery
# Reboot
Disclaimer:
I'm not responsible for any harm you do to your device, Proceed at our own risk. Few Roms have Vulkan api inbuilt in it. hit like if you like my work.
Developers are allowed to merge this with their Rom.
Credits
Me + @Er Ic Ks
Download Link:
https://mega.nz/#!YDpBDT4D!YThKq6uoYW02QEMXz0TUfs4_n4UF9AzhjHtvLQfTapM
Thank you man
Sushant515 said:
Thank you man
Click to expand...
Click to collapse
my pleasure
Nothing to offend I installed the api but still can find the vulkans api games like galaxy on fire 3 on play store any idea why that's happening
Sushant515 said:
Nothing to offend I installed the api but still can find the vulkans api games like galaxy on fire 3 on play store any idea why that's happening
Click to expand...
Click to collapse
Not all apps are available in Play store, just Google it and download it.
hey dude Vulkan api - where API means Application Program Interface.
you can play any game With the Vulkan api - difference can be compared with mobile which does not have Vulkan api installed.
Wonder Wicked Witch said:
Vulkan Graphics API
The Android platform includes an Android-specific implementation of the Vulkan API specification from the Khronos Group. Vulkan is a low-overhead, cross-platform API for high-performance, 3D graphics. It provides tools for creating high-quality, real-time graphics in applications. Vulkan also provides advantages such as reducing CPU overhead and providing support for the SPIR-V Binary Intermediate language.
It also provides a new generation graphics and compute API that provides high-efficiency, cross-platform access to modern GPUs used in a wide variety of devices from PCs and consoles to mobile phones and embedded platforms.
Installation:
# Download the Vukan api zip
# Install it using TWRP recovery
# Reboot
Disclaimer:
I'm not responsible for any harm you do to your device, Proceed at our own risk. Few Roms have Vulkan api inbuilt in it. hit like if you like my work.
Download Link:
https://mega.nz/#!YDpBDT4D!YThKq6uoYW02QEMXz0TUfs4_n4UF9AzhjHtvLQfTapM
Click to expand...
Click to collapse
Will it work on another Lenovo device running MM?
Va2c said:
Will it work on another Lenovo device running MM?
Click to expand...
Click to collapse
yes
Does it change the device name to SM-G955F ?
Pranay 7 said:
Does it change the device name to SM-G955F ?
Click to expand...
Click to collapse
No dude. if you want you can check it out.
After a full wipe these API remains on the device or have I to flash it everytime?
matteo0026 said:
After a full wipe these API remains on the device or have I to flash it everytime?
Click to expand...
Click to collapse
You want to flash it everytime when you change the rom, cuz the api is stored in device "system"
Attention guys,
Request any app, theme or Mod thread moved to guides and discussion page.
Doesn't Android 7 get vulkan natively ?
I am on stock 7 nougat I do have vulkan right ?
Ayman ae said:
Doesn't Android 7 get vulkan natively ?
I am on stock 7 nougat I do have vulkan right ?
Click to expand...
Click to collapse
OpenGL is in-built in all roms, but Vulkan api is not in-built in few roms, Maybe stock rom has it - I have not checked it in stock rom.
HAY
Does this mod active always if i don't play game. Or does it drain battery. Sorry for bad english?
Tarif.tk said:
Does this mod active always if i don't play game. Or does it drain battery. Sorry for bad english?
Click to expand...
Click to collapse
This is like Open GL - so there will no battery drain like an app.
Wonder Wicked Witch said:
yes
Click to expand...
Click to collapse
No, it does not.
Va2c said:
No, it does not.
Click to expand...
Click to collapse
It works with any dev.
Wonder Wicked Witch said:
It works with any dev.
Click to expand...
Click to collapse
It did not work. You can try on a Lenovo device with MM. Chances were slim anyways . Just informing you that it won't work with MM builds.
Va2c said:
It did not work. You can try on a Lenovo device with MM. Chances were slim anyways . Just informing you that it won't work with MM builds.
Click to expand...
Click to collapse
Share the screenshot. Anyway the main target is 7.x-8.x
This has reached a point that those who don't depend BT calling may be able to use it as a daily driver. Just be sure to backup first!
The flashing on first boot during setup may cause issues for those with epilepsy. This is due to how to disable the second screen.
Working:
Camera! https://www.celsoazevedo.com/files/android/google-camera/f/GCam5.1.018-Arnova8G2-V1.7Beta2.apk is recommended with Nexus 6 HDR config in advanced settings.
Bluetooth (skips with wifi, and doesn't work in call)
NFC
Wifi -- two users have reported issues on their devices, while it works for others.
GPS
Sensors
Sound
Calls
Fingerprint
Data
WiFi tethering
Second screen disable hack
Not working and issues:
Screen glitches on first boot. Reboot and will be good after (part of hack to disable 2nd screen)
Tap to wake
Flashlight tile: install flashlight tile for kenzo in play store with root to workaround.
Slight animation glitch when switching activities due to second screen hack.
BT issues above, and doesn't work in call.
If you use camera immediately after turning on, it may not work. You must wait about a minute after powering for it to work (it will always work after).
Probably more.
TODO
BT fixes
Tap to wake
flashlight tile
get a proper 2nd screen fix like v20 working without additional issues. v20 dtsi hack doesn't work for us due to dual panel depending on partial update (most likely).
Repos (kernel is lineage-15.1 branch):
Kernel
v10-common
h901
blobs
Changes from AOSCP
Using Ruthless launcher instead of Luna
Two reverts to support substratum themes in addition to CypherOS' color manager.
Use opengapps for gapps, magisk for superuser (may have issues with modules).
Download
Buy me a beer with Bitcoin: 1h9o1Ei9thLd8JKRz3z7PUGhX6dtfnktY
Bugs with workarounds:
Wifi doesn't connect and MAC address is all zeroes (only some users):
This is a misc partition that has MAC address hardcoded to a randomly generated address. This should work permanently on any device with the issue so long as two aren't on the same network. If anyone would like instructions on how to modify with a new MAC address, let me know.
Image https://www.androidfilehost.com/?fid=818222786056033811
Instructions:
Place on /sdcard
Reboot to recovery (for advanced reboot in CypherOS hold reboot button for full menu)
From twrp terminal or adb shell, run: dd if=/sdcard/misc.img of=/dev/block/bootdevice/by-name/misc
Reboot and enjoy fixed wifi
No charging indicator (but still charges):
Boot device plugged into power or USB and the indicator will work the entire power cycle. Working on a fix but not as trivial as I'd hoped.
Bootloop bug:
I recently got hit by the infinite bootloop bug, with the only workaround of disabling the big cluster. Here's a modified TWRP that only uses the little cluster (used Eliminator74's image):
https://www.androidfilehost.com/?fid=818222786056035329
And here's a little cluster only boot image from the titan kernel (our CAF kernel has msm_thermal issues with booting with disabled big cores, needs modifications):
https://www.androidfilehost.com/?fid=674106145207491774
nvm, fixed in current build
Just uploaded a new build. Changes:
Tweaked touch offset
Synced CypherOS to 6.0.0 (fixes navbar on first boot and some others)
Fixed init script to set display res (part of the second screen disable hack)
Updated Ruthless Launcher
two questions: the kernel you mention in repo is the original one or is a Lineage Kernel for LG V10? it for all variants of V10?
thanks
sun_is_shinning said:
two questions: the kernel you mention in repo is the original one or is a Lineage Kernel for LG V10? it for all variants of V10?
thanks
Click to expand...
Click to collapse
That lineage-15.1 branch that is being used is based on the lineage 14.1 g4 kernel. I added a h901 defconfig, three commits needed for v10 (incl 2nd screen hack), fast charging, all commits needed for Oreo (since g4 isn't supported on los 15.1), then merged in CAF.
Regarding the other variants (which are now all unlockable thanks to g4 guys), I added a commit by ehem which added the panel dtsi for other variants, but as of yet only h901 builds have been tested on the kernel. Other variants should work with the correct defconfigs and device repos adapted from their g4 counterparts.
Hope I answered fully.
johngalt1 said:
That lineage-15.1 branch that is being used is based on the lineage 14.1 g4 kernel. I added a h901 defconfig, three commits needed for v10 (incl 2nd screen hack), fast charging, all commits needed for Oreo (since g4 isn't supported on los 15.1), then merged in CAF.
Regarding the other variants (which are now all unlockable thanks to g4 guys), I added a commit by ehem which added the panel dtsi for other variants, but as of yet only h901 builds have been tested on the kernel. Other variants should work with the correct defconfigs and device repos adapted from their g4 counterparts.
Hope I answered fully.
Click to expand...
Click to collapse
Will you add the other version? For H960, H960TR vs.
Kasimpasali1921 said:
Will you add the other version? For H960, H960TR vs.
Click to expand...
Click to collapse
It's planned.
Hey, I just have a question, I'm sorry probably borrowing your thread to ask, but how'd you get the ROM to build using 15.1/14.1? I've been working on a port horrible the h901, but for the life of me I can't get the ROM to build.
Also, when I get a chance I'll check out your ROM, haven't gotten to play with oreo much as of yet.
TheEnekaign said:
Hey, I just have a question, I'm sorry probably borrowing your thread to ask, but how'd you get the ROM to build using 15.1/14.1? I've been working on a port horrible the h901, but for the life of me I can't get the ROM to build.
Also, when I get a chance I'll check out your ROM, haven't gotten to play with oreo much as of yet.
Click to expand...
Click to collapse
Ask any question you want here! I'm not sure specifically what issue you ran into while attempting to build, but the repo links in OP are fully up to date (incl the lineage-15.1 branches).
Unfortunately los 15.1 has the graphical glitches (due to 2nd screen hack) after the second boot as well, so I'll be sticking with cypheros for testing for now.
I'll make a project manifest shortly to further simplify building.
johngalt1 said:
Ask any question you want here! I'm not sure specifically what issue you ran into while attempting to build, but the repo links in OP are fully up to date (incl the lineage-15.1 branches).
Unfortunately los 15.1 has the graphical glitches (due to 2nd screen hack) after the second boot as well, so I'll be sticking with cypheros for testing for now.
I'll make a project manifest shortly to further simplify building.
Click to expand...
Click to collapse
Sweet, I'll have to have a look at those repos. Only ones I could find before were cm 13.1. I was working on a RR 14.1 port, since that's one of my fav roms, but basically the error I got was a brunch error as it couldn't find the needed files (maybe the manifest? It's been about a week since I poked it). It kept looking at the lineage servers and couldn't find the right cm versions. It also couldn't find other things as well, but I'll have to poke it again to remember what exactly.
Thank you though!
(I also just realized that my auto correct called the h901 horrible. It's def not horrible. xD)
TheEnekaign said:
Sweet, I'll have to have a look at those repos. Only ones I could find before were cm 13.1. I was working on a RR 14.1 port, since that's one of my fav roms, but basically the error I got was a brunch error as it couldn't find the needed files (maybe the manifest? It's been about a week since I poked it). It kept looking at the lineage servers and couldn't find the right cm versions. It also couldn't find other things as well, but I'll have to poke it again to remember what exactly.
Thank you though!
(I also just realized that my auto correct called the h901 horrible. It's def not horrible. xD)
Click to expand...
Click to collapse
For building without the manifest, clone the device and vendor repos to their correct folders, check aoscp.dependencies to clone additional repos to their correct folders, then just run . build/envsetup.sh ; breakfast aoscp_h901-userdebug, and then you can make bacon ?
I based the device repos off the g4 repos for aoscp, which are just los 14.1 with Oreo and now v10 changes. The kernel is based on the los 14.1 lge msm8992 kernel with changes necessary for Oreo, CAF merged in, fast charging support, the second screen disable hack, a commit for building properly with a lge display flag, the dtsi for other v10 variants (thanks to ehem), and a defconfig for h901.
Edit: keep in mind RR may have the same display corruption issue with our second screen hack that LOS has for us.
New build uploaded. Changes:
- Fixed touchscreen alignment. Bottom of navbar now works.
- Synced with upstream CypherOS
- Testing navbar theme settings from gerrit.
New build uploaded. Changes:
- Possibly fixed occasional no sim on boot (ty kessaras/steadfasterx)
- Synced with CypherOS
- A few upstream ALSA kernel changes
- Ruthless launcher updated
- Two upstream reverts to fix substratum themes.
There's now also a local_manifest for users who would like to build themselves https://github.com/amillogical/local_manifest
Is this compatible to my lg v10 h962 (from taiwan)?
ViciousDiplomat said:
Is this compatible to my lg v10 h962 (from taiwan)?
Click to expand...
Click to collapse
No, but it can be. Is your device bootloader unlocked? If so, I'll do a build from h815 (g4 equiv) you can test. If not, I can help bootloader unlock it with USU.
I'm not sure how many know, but all v10 variants are now bootloader unlockable with USU. I just haven't had a chance to build for them or post details.
well, will this Kernel of this ROM compatible with H960A variant? and what really changes in this Kernel?
Thank u.
sun_is_shinning said:
well, will this Kernel of this ROM compatible with H960A variant? and what really changes in this Kernel?
Thank u.
Click to expand...
Click to collapse
Yes, it only needs a config for h960 at this point. Ehem imported the panels for all the other variants so we can use a unified kernel between all g4 and v10 variants.
Will done sir i'll buy you a bear on your bitcoin wallet for sure.. Gr8 job
An old user for v10 (p20 pro now) but still love this beast
New build uploaded. This won't fix wifi issues for those that have them. This build needs a dalvik-cache wipe after dirty flash due to memory override changes (last bullet). I've also started using AndroidFileHost for uploads.
Changes:
- Synced with upstream CypherOS (bumped to april security bulletin and a few new features).
- NFC should be fixed. This needs more testing, as I don't have anything to test the functionality but it turns on/off.
- Corrected STM laser permissions (autofocus seems to be like in stock rom now).
- Changed link to modified google camera in OP since the previous version didn't have functional HDR+.
- Dalvik heap and hwui memory overrides updated for our device's 4G ram and high res display.
And thank you @sherif2222222
Thread template from Flex1911's thread.
Info:
Based on Flex1911 treble related commits
Q-based vendor up to date with Lineage 17.1 device trees and kernel
Instructions:
I'm not going to provide them, just head here instead: https://forum.xda-developers.com/mi-a1/how-to/treble-stock-to-treble-everything-to-t3793734
As usual, it requires repartitioning.
Downloads:
vendor_vndk29_LOS17.1_20210427.img and boot_vndk29_LOS17.1_20210427.img
Source code:
Kernel Patch
Common MSM8953 tree
Device tree
Great, I'll test these images as soon as I can!
Have you tested them in any GSI?
Note: Although the ROM is from 2021, the boot and vendor images were named as from 2020. Is it right?
santosst said:
Have you tested them in any GSI?
Click to expand...
Click to collapse
Only on Android 10 Phh AOSP
santosst said:
Although the ROM is from 2021, the boot and vendor images were named as from 2020. Is it right?
Click to expand...
Click to collapse
Thanks, didn't notice that
Already corrected dates, all from 2021.
zignas said:
Only on Android 10 Phh AOSP
Click to expand...
Click to collapse
Hmm, ok, I'll probably try them on eremitein's LiR, that's the GSI I'm daily driving for some weeks.
zignas said:
Thanks, didn't notice that
Already corrected dates, all from 2021.
Click to expand...
Click to collapse
Oh, no problem lol, thanks for correcting the dates
santosst said:
I'll probably try them on eremitein's LiR
Click to expand...
Click to collapse
Bluetooth is dead on android 11 GSI's
Temporary solution (untill i make update):
Delete "Bluetooth__auto_generated_rro_vendor.apk" in /vendor/overlay
zignas said:
Bluetooth is dead on android 11 GSI's
Temporary solution (untill i make update):
Delete "Bluetooth__auto_generated_rro_vendor.apk" in /vendor/overlay
Click to expand...
Click to collapse
Oh, thanks!! I'll install your vendor tonight and try to use Bluetooth.
I'm using the vndk-lite version, so maybe Bluetooth works ok, but I'll try and report to you
Edit: In fact, Bluetooth doesn't work out-of-the-box, so I needed to delete the Bluetooth overlay as you said, and after that, it worked well.
thank you for your work, i'm currently using ExpressLuke's PixelExperience 10 GSI with your boot & vendor, it has great performance with ondemand governor (although it hurts battery life a bit). Also everything works without a problem
thanks for you work!
as a new treble user, I have one doubt: what is the difference between this vendor implementation and the ones released by other developers? I've been using sooti's vendor for a while and did not have a single problem but it seems old looking at filename (don't really know if date is relevant btw)
portox said:
what is the difference between this vendor implementation and the ones released by other developers? I've been using sooti's vendor
Click to expand...
Click to collapse
I didn't check his sources, but as i know he using old pie vendor (with pie blobs, etc, etc).
And if ROM ( semiGSI as example, builded not from sources) doesn't contain VNDK28 (pie "level") compability layer it simply doesn't boot at all.