[ROM][e610][UBER TC][AOSP-CAF] GlazeOS | Experimental Build (02/04/2017) - Optimus L3, L5, L7 Original Android Development

[ROM][e610][UBER TC][AOSP-CAF] GlazeOS | Experimental Build (02/04/2017) - Optimus L3, L5, L7 Original Android Development

L7? u.u

Hugo Salce said:
L7? u.u
Click to expand...
Click to collapse
Can you be a tester?

Thanks for the ROM

create for e615? Pls

ROM-PacMe said:
BUGS
Camera
Wi-Fi
You tell me more bugs :3
Click to expand...
Click to collapse
As I can see from screenshots, another bug is RIL and as far as I remember audio doesn't work as well.

SlimShady's said:
As I can see from screenshots, another bug is RIL and as far as I remember audio doesn't work as well.
Click to expand...
Click to collapse
Hehe ... since I did not have a SIM inserted in the pone x3

I finished compiling GlazeOS (android 7.1.2_r8) for LG L7 II (Vee7).
https://www.androidfilehost.com/?fid=745425885120732876 Anyone want to try?!
NOTE: Do not flash recovery from this ROM, it will not work and maybe damage /recovery partition!
My main job is to make nougat rom for Huawei Y300/G510 since there is none till today, but first to made working rom for LG L7 II, because of more resources and because of similar specifications (same CPU, GPU, RAM).

adeii said:
I finished compiling GlazeOS (android 7.1.2_r8) for LG L7 II (Vee7).
https://www.androidfilehost.com/?fid=745425885120732876 Anyone want to try?!
NOTE: Do not flash recovery from this ROM, it will not work and maybe damage /recovery partition!
My main job is to make nougat rom for Huawei Y300/G510 since there is none till today, but first to made working rom for LG L7 II, because of more resources and because of similar specifications (same CPU, GPU, RAM).
Click to expand...
Click to collapse
Hi. I am not able to flash the rom. I am getting 'signal 4 error' right at the start.
It failed even after removing assert() functions and otasigcheck. Maybe the updater-script is corrupted.
Kindly fix this issue.
Can't wait to try this one.

@adeii
Maybe the logs will help???
I modified the boot.img (ro.secure=1 ---> 0)
Can't get past the boot LOGO/LG Logo (not to be confused with bootanimation).

XDA-00 said:
@adeii
Maybe the logs will help???
I modified the boot.img (ro.secure=1 ---> 0)
Can't get past the boot LOGO/LG Logo (not to be confused with bootanimation).
Click to expand...
Click to collapse
Thank you for trying. I do not know why is not booting.
Device tree is from: https://github.com/LegacyLG
I also got flashing error 4, on TWRP 3.1.0.0, on Y300, use update-binaries fro 6.0.1 rom to finish installing.
Also do not boot, keeps restarting on Huawei logo screen.
In your log, there are errors like:
0.000000] smem_find(137, 80): wrong size 64
0.000000] smem_find(137, 72): wrong size 64
0.094871] vddx_c2: 750 <--> 1500 mV at 1150 mV normal
0.094999] Error-Bad Function Input
0.187663] CRASH LOG START ADDR : 0x1ff3e000
0.187854] CRASH LOG END ADDR : 0x1ff3efff
0.225056] qup_i2c qup_i2c.1: I2C slave addr:0x3e not connected
0.225269] sx150x 1-003e: i2c write fail: can't write 01 to 1f: -107
0.225624] sx150x: probe of 1-003e failed with error -107
0.447166] get_nand_partitions: no flash partition table in shared memory
0.456164] rpcrouter: Server create rejected, version = 0, program = 3000003b
Do you know what could make them?

adeii said:
Thank you for trying. I do not know why is not booting.
Device tree is from: https://github.com/LegacyLG
I also got flashing error 4, on TWRP 3.1.0.0, on Y300, use update-binaries fro 6.0.1 rom to finish installing.
Also do not boot, keeps restarting on Huawei logo screen.
In your log, there are errors like:
0.000000] smem_find(137, 80): wrong size 64
0.000000] smem_find(137, 72): wrong size 64
0.094871] vddx_c2: 750 <--> 1500 mV at 1150 mV normal
0.094999] Error-Bad Function Input
0.187663] CRASH LOG START ADDR : 0x1ff3e000
0.187854] CRASH LOG END ADDR : 0x1ff3efff
0.225056] qup_i2c qup_i2c.1: I2C slave addr:0x3e not connected
0.225269] sx150x 1-003e: i2c write fail: can't write 01 to 1f: -107
0.225624] sx150x: probe of 1-003e failed with error -107
0.447166] get_nand_partitions: no flash partition table in shared memory
0.456164] rpcrouter: Server create rejected, version = 0, program = 3000003b
Do you know what could make them?
Click to expand...
Click to collapse
https://github.com/search?utf8=✓&q=vee7&type=
Some of the links are from nicknitewolf. Just Saying.
I tried TWRP 3.1.1-0 made by him and it did not work. Wasn't able to boot into recovery.
You should recheck the kernel.
Maybe, you can try this source=https://github.com/weritos666/Vee7
OR THIS :- https://github.com/TeamHackLG/android_device_lge_msm7x27a-common
I really can't help much, but you can ask neutrondev or weritos for help, they might solve the issue and if you recompile the rom, just change the value of ro.secure to 0 (in default.prop of kernel)
OR Maybe you can ask for help at modaco too.
Do you know what could make them?
Click to expand...
Click to collapse
Maybe the file_contexts.bin is corrupt? Isin't it supposed to be just file_contexts (without .bin extension)?
Thats all I can say.
Lets hope someone fixes the issue and we'll have nougat for our devices.
Edit :- just realized that the fork should be from msm7x27 not msm7x30 (see attachment)
and re-check fstab.vee7, there might be some error regarding partitions/blocks.

@adeii
Try this boot.img (see attachments)

XDA-00 said:
https://github.com/search?utf8=✓&q=vee7&type=
Some of the links are from nicknitewolf. Just Saying.
I tried TWRP 3.1.1-0 made by him and it did not work. Wasn't able to boot into recovery.
You should recheck the kernel.
Maybe, you can try this source=https://github.com/weritos666/Vee7
OR THIS :- https://github.com/TeamHackLG/android_device_lge_msm7x27a-common
I really can't help much, but you can ask neutrondev or weritos for help, they might solve the issue and if you recompile the rom, just change the value of ro.secure to 0 (in default.prop of kernel)
OR Maybe you can ask for help at modaco too.
Maybe the file_contexts.bin is corrupt? Isin't it supposed to be just file_contexts (without .bin extension)?
Thats all I can say.
Lets hope someone fixes the issue and we'll have nougat for our devices.
Edit :- just realized that the fork should be from msm7x27 not msm7x30 (see attachment)
and re-check fstab.vee7, there might be some error regarding partitions/blocks.
Click to expand...
Click to collapse
Thanks a lot for reply. I hope I'll find errors. Have you tried to boot with newboot.img ? Somewhere is written that TWRP 3.0.3.0 should be enough to boot 7.1.1...but this is 7.1.2.

adeii said:
Thanks a lot for reply. I hope I'll find errors. Have you tried to boot with newboot.img ? Somewhere is written that TWRP 3.0.3.0 should be enough to boot 7.1.1...but this is 7.1.2.
Click to expand...
Click to collapse
You're welcome. And no I did not try, I'm done.. for now.
I have TWRP 3.0.2-0. Its the only working recovery.
Try contacting weritos or neutrondev.

XDA-00 said:
@adeii
Maybe the logs will help???
I modified the boot.img (ro.secure=1 ---> 0)
Can't get past the boot LOGO/LG Logo (not to be confused with bootanimation).
Click to expand...
Click to collapse
How did you manage to make logs while booting the device?I cant figure out how to do that.
I set persist.sys.usb=adb and ro secure=0 but adb says device unauthorized.
Thanks.

Gent' said:
How did you manage to make logs while booting the device?I cant figure out how to do that.
I set persist.sys.usb=adb and ro secure=0 but adb says device unauthorized.
Thanks.
Click to expand...
Click to collapse
After kernel crash/bootloop, goto twrp > advanced > terminal and type :
For kernel log :-
cat /proc/last_kmsg > /sdcard/last_kmsg.text
For dmesg :-
dmesg > /sdcard/dmesg.txt
Edit :- set persist.adb.debugging to 1 if not done already.

XDA-00 said:
https://github.com/search?utf8=✓&q=vee7&type=
You should recheck the kernel.
Maybe, you can try this source=https://github.com/weritos666/Vee7
Maybe the file_contexts.bin is corrupt? Isin't it supposed to be just file_contexts (without .bin extension)?
Click to expand...
Click to collapse
Kernel is changed to weritos' Vee7.
https://www.androidfilehost.com/?fid=817550096634773143 try this kernel.
From 7.0 it is changed to file_contexts.bin, no more textual file contexts.
Newer kernel, with updated fstub.qcom and ro.secure and ro.adb.secure=0 at https://www.androidfilehost.com/?fid=961840155545568953

adeii said:
Kernel is changed to weritos' Vee7.
https://www.androidfilehost.com/?fid=817550096634773143 try this kernel.
From 7.0 it is changed to file_contexts.bin, no more textual file contexts.
Newer kernel, with updated fstub.qcom and ro.secure and ro.adb.secure=0 at https://www.androidfilehost.com/?fid=961840155545568953
Click to expand...
Click to collapse
Did not boot man. I tried both kernels but did not succeed.
See logcat.
KMSG :- https://pastebin.com/dvDjz6S6
DMESG :- https://pastebin.com/ppNiHVFX
Try changing SELINUX to permissive default and upload fixed rom zip.
Are you sure that the file inside is fstAb.qcom and NOT fstUb.qcom
Don't lose hope.:fingers-crossed:

Good work man !

Related

[ROM][4.4.4] CyanogenMod 11.0 for A3000-H [23/10/2015]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PREAMBLE
Here is my CM11 port for the Lenovo A3000-H, 100% unofficial. Contributions are welcome!
To be able to even flash it, you'll need to use my CWM Recovery.
NOTE: I have built and tested this on my Lenovo A3000-H (16 GB version with 3G). Before flashing, please make sure to be on Stock 4.2. Open up a terminal or an ADB shell and type the following:
Code:
getprop ro.product.board
.
Should you get a3000_prc_3gfull, you are good to go. Otherwise, you need to flash the right Stock ROM. The members @kupyxa4444 and @luckasfb have created such a Stock-based ROM, so if you are unable to find one - try to contact one of these two.
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4 (KitKat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
NOT WORKING
Camera
WORKING
GPS
WiFi
Audio
Boots
SELinux
Sensors
Vibration
Bluetooth
HWComposer
Offmode charging
sw video en/decoding (not hw)
Internal and external sdcards
RIL/radio (only on SIM1, SIM2 is still broken and therefore disabled, you can re-enable it by setting persist.radio.multisim.config=dsds in your build.prop)
NOTE
Should you ever face any issues (in the recovery or the ROM), provide logs (use Google to find out how to gather those). Additionally, I need to know what ROM you're on, hence you have to mention the build number.
Hint: "It doesn't work or I get error Status XY" are not bug reports and will be ignored. To keep the thread clean, use DevDB for real bug reports
DOWNLOAD
Instructions:
ordinarystar said:
Pre-equisites to flash:
1. Correct Firmware
1.1 First verify your build version by installing Terminal Emulator from Play Store and then type the following:
getprop ro.product.board
if the output is a3000_prc_3gfull, proceed to number 2.
1.2 if the output is not a3000_prc_3gfull, you will have to first flash another firmware which can be downloaded at:
https://drive.google.com/file/d/0B5yhZ9sXUH_GMWhCQllhbkZRbUk/edit
Firmware flashing instructions can be referred here:
http://forum.xda-developers.com/lenovo-a3000/development/rom-lenovo-ideatab-a3000-h-call-t2441135
2. My version of CWM installed
2.1 Now you should install the CWM. You need a rooted device to proceed. Assuming you followed 1.1 and 1.2, your device is already rooted.
You will need:
2.1.1 Install mobileuncle MTK Tools from PlayStore or download apk from thread below: http://forum.xda-developers.com/showthread.php?t=2697236
2.1.2 My CWM, download the zip file and extract the recovery.img. Put the recovery.img in your microSD card.
http://olivier.hubdroid.com/a3/cwm/cwm_a3-20141220.zip
2.2 Open up mobileuncle MTK Tools, and select install recovery. It will detect the recovery.img in your microSD card (top in the list).
Tap on it to install. DO NOT tap on others in the list. Just click OK to install. If you have already downloaded my rom with it placed in your microSD card,
you may proceed to boot into recovery, or you can press cancel and shut down your device.
The pre-equisites is now completed!
Steps to flash:
1. Download my rom from http://olivier.hubdroid.com/a3/cm-11.0/ - select a preferred release. latest release recommended.
2. Download gapps from http://forum.xda-developers.com/android/software/gapps-consolidated-gapps-thread-t3064693 - select gapps for kit kat 4.4.4
2. Boot up recovery: hold power button and volume up button, as it booted up release power button. Use volume up button to browse to "recovery mode" and press volume down to proceed recovery mode.
3. Do the following:
2.1 Factory reset
2.2 Clear cache
2.3 Clear dalvik cache (Advanced > clear dalvik cache)
2.4 install from zip, select the rom and install
2.5 install gapps.
2.6 when done, reboot to system
The installation is now completed!
Click to expand...
Click to collapse
I have spent a lot of time on this project and I still do - hence, donations would be highly appreciated.
My builds can be found here.
SOURCEs
Device tree (branch cm-11.0)
Kernel (branch cm-11.0)
OmniROM Gerrit (topic mt6589)
CREDITs
chrmhoffmann
kashifmin
Grarak
xplodwild
Dr-Shadow
superdragonpt
EnerJon
kupyxa4444
XDA:DevDB Information
CyanogenMod 11 for the Lenovo A3000-H, ROM for the Lenovo A3000
Contributors
Olivier
Source Code: https://github.com/lenovo-a3-dev
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Beta
Created 2014-11-26
Last Updated 2015-10-23

Changelog
BUILD STATUS
Willing to contribute? Just drop me a PM, send me pull requests on GitHub or join my IRC channel on freenode: #cm-a3!
Please don't clutter the thread, post your bug reports here instead. Thanks!
CHANGELOG
Code:
[B][U]29/07/2015:[/U][/B]
[list][*][B][COLOR="Blue"]kernel: [/COLOR][/B]Fixed automatic rotation
[*][B][COLOR="Blue"]kernel: [/COLOR][/B]Security patches/fixes
[*][B][COLOR="Blue"]kernel: [/COLOR][/B]Removed scsi_wait_scan module
[*][/list]
[B][U]02/02/2015:[/U][/B]
[list][*]Fixed sw encoding and decoding ([B][COLOR="Lime"]YouTube videos etc work now![/COLOR][/B])
[*][B][COLOR="Blue"]kernel: [/COLOR][/B]Reverted to LZMA compression (for TWRP)
[*][B][COLOR="Blue"]kernel: [/COLOR][/B]Security patches/fixes
[*][B][COLOR="Blue"]kernel: [/COLOR][/B]Misc patches for ext4, crypto
[*][B][COLOR="Blue"]kernel: [/COLOR][/B]Added support for kernel mode NEON
[*][/list]
[B][U]28/12/2014:[/U][/B]
[list][*][B][COLOR="Blue"]kernel: [/COLOR][/B]Switched to LZ4 compression (instead of LZMA)
[*][B][COLOR="Blue"]kernel: [/COLOR][/B]Added BFQ/SIO/FIOPS/ZEN/VR IO Schedulers
[*][B][COLOR="Blue"]kernel: [/COLOR][/B]Added overall stats for all available cores
[*]Fixed battery capacity (item in framework-res)
[*][/list]
[B][U]26/12/2014:[/U][/B]
[list][*]Switched back to deodexed build on community request
[*]Removed recovery-from-boot.p (we don't really want this)[/list]
[B][U]20/12/2014:[/U][/B]
[list][*]Fixed Internal sdcard[/list]
[B][U]17/12/2014:[/U][/B]
[list][*]Fixed HWComposer
[*]Odexed build for better performance[/list]
[B][U]16/12/2014:[/U][/B]
[list][*]Fixed NVRAM
[*]Fixed Bluetooth
[*]Fixed RIL[/list]
[B][U]26/11/2014:[/U][/B]
[list][*]Initial public release.[/list]

Successfully flashed over A3000_A422_013_25_140624.
Felt like holding a nexus 7!
Thanks a lot man!

Thanks
Thanks Olivier for your enormous efforts, you are working alone , You rock
successfully installed it over A3000_A422_013_025_140926_WW_CALL_FUSE
Using this build "cm-11-20141127-UNOFFICIAL-a3"
I'm testing it , and i'm going to report the bugs i find via the bug report
Again , thanks

This is the best post on XDA so far.
Thank you for your effort @Olivier

Think you Sir...is it support Call function ?
i will try it soon...

Hesham Sleem said:
Think you Sir...is it support Call function ?
i will try it soon...
Click to expand...
Click to collapse
No this rom not support Calling because NULL IMEI
***Backup NVRAM before try it***

nut27455 said:
No this rom not support Calling because NULL IMEI
***Backup NVRAM before try it***
Click to expand...
Click to collapse
Ok...So if i backup NVRAM and restore it after flash rom , Call function will work ??

Hesham Sleem said:
Ok...So if i backup NVRAM and restore it after flash rom , Call function will work ??
Click to expand...
Click to collapse
No. Guys, it's clearly stated in the OP that RIL/radio (and hence calls/SMS) is broken!

New user
I have a question..
If I install this room on my lenovo a3000. What is the things that will not working on my tablet. Sorry I'm not professional and I need to help to know what is the risk's that I will found??

Magiiic said:
I have a question..
If I install this room on my lenovo a3000. What is the things that will not working on my tablet. Sorry I'm not professional and I need to help to know what is the risk's that I will found??
Click to expand...
Click to collapse
As it was said in the first post..
Bluetooth
RIL/radio
Camera
(hw) video en/decoding and hwcomposer
Internal SD card
probably much more (haven't had much time to test everything)

MirXas said:
As it was said in the first post..
Bluetooth
RIL/radio
Camera
(hw) video en/decoding and hwcomposer
Internal SD card
probably much more (haven't had much time to test everything)
Click to expand...
Click to collapse
Any solve to this problem's?

Magiiic said:
Any solve to this problem's?
Click to expand...
Click to collapse
Wait for future builds.
Stop asking questions in this thread, there is a seperate Q&A thread especially for this.

Really great work
Only the camera to go and I'll use this I promise
Sent from my Lenovo IdeaPad A3000-H using XDA mobile app

Aren't u using hodor kernel?
Hodor kernel fir A3000 have not any radio/Bluetooth bug listed!! They why in this rom has bugs of radio?? http://forum.xda-developers.com/lenovo-a3000/orig-development/kernel-hodorkernel-t2952086
Sent from my Lenovo A3000-H
MOD EDIT: Not a great sense posting some other ROM LINK here

afridi.shahriar said:
Aren't u using hodor kernel?
Hodor kernel fir A3000 have not any radio/Bluetooth bug listed!! They why in this rom has bugs of radio?? http://forum.xda-developers.com/lenovo-a3000/orig-development/kernel-hodorkernel-t2952086
STOP spaming the same everywhere ! The RIL bug is not in the kernel, it's in the ROM itself.
Click to expand...
Click to collapse

Members,
It is not so difficult to be sensible and considerate.
1) Kindly stop asking questions here. Use the Q&A.
2) If you find something not to your liking, find something which you like or produce what you like by yourself
THREAD CLEANED.

OP thankyou for this works very well with my F version ,never seen HD video load so fast

afridi.shahriar said:
Aren't u using hodor kernel?
Hodor kernel fir A3000 have not any radio/Bluetooth bug listed!! They why in this rom has bugs of radio?? http://forum.xda-developers.com/lenovo-a3000/orig-development/kernel-hodorkernel-t2952086
Click to expand...
Click to collapse
Yes, the CM11 kernel is based off my HodorKernel. Apparently the kernel isn't the problem here - you could flash it on any fused Stock ROM and everything would work.
To those who wanted ETAs: At the moment, I'm a bit busy with exams and other devices. Bugfixing is progressing rather slowly, not only due to time constraints but also because I'm working on this alone and it's not easy to work on mtk devices.

keep up the good work.
you can make it buddy.

[Kernel]Reaper Reborn[LINARO-7.1.2][Zenfone Max/Z010D]

THE FIRST EVER CUSTOM KERNEL FOR ASUS ZENFONE MAX
HTML:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards, dead cats,
* thermonuclear war, or you getting fired because the alarm app failed.
* YOU are choosing to make these modifications, and no point
* in pointing the finger at me for messing up your device
*/
Lets get started
CHANGELOG
V1.0
Compiled with latest Linaro 7.1.2 toolchain.
KSM Enabled By Default
Added Thundercharge (Read this before enabling.).
KCAL support.
Upstreamed to latest 3.10.108 kernel version release.
More stable and secure than before.
Enabled Conservative governor.
INSTALLATION INSTRUCTIONS
I would highly recommend clearing data of your kernel adiutor/any other apps that you use to control features or better yet since this is a "FLASH AND FORGET" kernel uninstall them you don't need it now.
Download the .zip file from the downloads section.
Reboot into recovery.
Select the zip file and flash.
This kernel is a "FLASH AND FORGET" kernel meaning everything is set and optimized by default if you mess up by changing default settings.
DOWNLOADS
Custom Roms
V1.0 https://sourceforge.net/projects/aimsystem/files/roman/kernel/Reaper-Reborn-V1.0.zip/downloadhttps://sourceforge.net/projects/aimsystem/files/roman/kernel/Reaper-Reborn-V1.0.zip/download
Stock Rom
No build for stock rom as of now.
NOW TIME FOR SOME GROUND RULES :silly:
PLEASE USE ABOVE GIVEN SECTIONS TO SORT EVERYTHING YOU HAVE IN YOUR MIND.FOR EXAMPLE IF YOU WANT TO REPORT A BUG USE BUG REPORT SECTION ANY BUG REPORTS GIVEN IN THE COMMENT SECTIONS WILL BE IGNORED SAME GOES FOR EVERYTHING.
IF YOU WANT TO REPORT A BUG PLEASE EXPLAIN IT IN DETAILS AND STEPS OF HOW THAT BUG OCCURRED AND WITHOUT LOGCATS I CAN'T DO ANYTHING.
Wanna show your love and support by donating or planning to contribute to the project?
All of my work is open source and available on github.
You don't have to but if you want to donate me then send a private message. it'll only encourage me to keep working and help with some financial problems :victory: .
Be A Regular User And Give Feedbacks Every Week With Logs And Battery Stats.
Drop A Like.:fingers-crossed:
XDA:DevDB Information
Reaper-Reborn, Kernel for the Asus ZenFone 2
Contributors
ShadowReaper1, audahadi, commits i used from other developers repo's
Source Code: https://github.com/ShadowReaper1/android_kernel_asus_msm8916.git
Kernel Special Features: A Better And Feature Full Replacement For Stock Kernel.
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2017-12-09
Created 2016-09-25
Last Updated 2017-12-09

Reserved
Before enabling thundercharge read this first.
Must Read
Use it only when you are not planning to use your phone with the charger plugged in.I have kept it off as default because i do not recommend to use your phone while charging with Thundercharge enabled cause it might cause some hardware issues, break charging drivers or in the worst case scenario you'll have a Samsung Galaxy Note 7 experience yourself.
Got some problems with fastcharge not working or the values are not sticking?
If Thundercharge isn't working then navigate to Thermal tab in Kernel Adiutor and disable VDD Restriction then enable Core Control.
If the values are not sticking then use this kernel adiutor.
Charging Tests
Test 1
Tested percentage -> From 56 to 100
Average mA -> 1100
Battery temp -> 36 when plugged in and 39 when pulled out.
Cpu idle temp -> 46-49, 51 max.
Time Taken -> 1:20hrs
Test 2
Tested percentage -> From 25 to 100
Average mA -> 1200
Battery temp -> 36 when plugged in and 39 when pulled out.
Cpu idle temp -> 46-49 max.
Time Taken -> 2:15hrs
Kernel Settings?
I prefer to use stock kernel settings but if you want more battery then change the governor to conservative(That's what i use BTW because i am a very moderate user) it might lag so i will just ignore those whinny comments about lags.
How to use the features that are implemented in the kernel?
Download kernel adiutor from playstore or from given link and Explore!.
Having problems? Anything you wanna ask? Mention me on your comment or Send a message on Telegram at @ShadowReaper1 .

Reserved
This guide will be updated shortly.
How To Build Your Own Kernel?
*Each Step Is Very Important Be Sure To Follow Each Steps And Do As I Said.
*You Are Gonna A 64bit Linux OS Any Will Do I Use Ubuntu 16.04 LTS.
*Let's Setup Your Build Environment.
*Open Terminal(ctrl+alt+T).
*Now Type "sudo apt-get update" Then Hit Enter And Let It Complete.
*Refer To This Awesome Guide By @akhilnarang To Automatically Install All The Proprietary Things.
*Where "<name-of-script>" Type "ubuntu1604linuxmint18.sh" If You Have Ubuntu 16.04 Then Hit Enter And Let It Complete.
*You'll Need Kernel Sources Again Open Terminal And Type "git clone https://github.com/ShadowReaper1/android_kernel_asus_Z010D.git" And Let It Complete It'll Take A While Depends On Your Internet Speed.
*Now To Compile The Kernel Download A arm64/aarch64 Toolchain You Can Use Any Gcc 4.9 Toolchain I Prefer Google or UBER Toolchain.
*Open Kernel Directory It Should Be Named Like "android_kernel_asus_Z010D" And Open build.sh And Edit The Parts Where "change" Is Written According To Your Toolchain Path And Cpu Cores After Editing Save It.
*It's Time To Compile The Kernel Open Terminal Inside Kernel Directory And Type "bash build.sh" or "./build.sh" Then Sit Back And Wait For It To Complete And You'll Find Your Kernel.zip inside "base_files" Folder.
*What To Do Next? Flash It .
*Add Features As You Like And Fix Bugs.
*Don't Come To Me Crying How To Add This And That I Won't Help In That Matter See Other Kernel's Of Other Devices With Same Specifications Use That As Reference And Cherry Picks Features From Them Resolve The Conflicts For More Information Refer To This Excellent Guide By @eagleeyetom.
*One More Thing Leave A Like And Press That Thanks Button .

Gr8
★✩★ 7HD 17.0 ★✩★

Great job! Is the kernel compatible to Lollipop versions or just Marshmallow? Thanks!
Rooted Zenfone MAX

Will wait first for user feedbacks regarding this... Up!!! ^_^

mrichiem said:
Great job! Is the kernel compatible to Lollipop versions or just Marshmallow? Thanks!
Rooted Zenfone MAX
Click to expand...
Click to collapse
It's for marshmallow only but you can try if you are on lollipop so that the users know and they can use it on lollipop as well.

asukaragnaboy said:
Will wait first for user feedbacks regarding this... Up!!! ^_^
Click to expand...
Click to collapse
Why not be the first to give feedbacks instead of waiting for someone.

I try on lasted lollipop. It show boot image invalid!

Thanks, works fine. Don't know about the frequency, I just applied the patch.
Is it ok to use with L Speed? I use it since it got rooted.

just flash from fastboot(fastboot flash boot ***.img?)
just flash from fastboot(fastboot flash boot ***.img?) or any other procedure?

ShadowReaper1 said:
It's for marshmallow only but you can try if you are on lollipop so that the users know and they can use it on lollipop as well.
Click to expand...
Click to collapse
Flashed it on .82 lollipop build, got bootlooped so it's definitely not backwards compatible.
Rooted Zenfone MAX

mrichiem said:
Flashed it on .82 lollipop build, got bootlooped so it's definitely not backwards compatible.
Rooted Zenfone MAX
Click to expand...
Click to collapse
Ok Thanks for trying out i'll update the thread regarding lollipop support.

mrichiem said:
Flashed it on .82 lollipop build, got bootlooped so it's definitely not backwards compatible.
Rooted Zenfone MAX
Click to expand...
Click to collapse
It will bootloop.. You need lollipop ramdisk
Sent from my ASUS_Z010D using Tapatalk

hackergacon9x said:
I try on lasted lollipop. It show boot image invalid!
Click to expand...
Click to collapse
It won't work on lollipop its for marshmallow only.

ratan656 said:
just flash from fastboot(fastboot flash boot ***.img?) or any other procedure?
Click to expand...
Click to collapse
yes or you can use twrp to flash img

This version 2.0 can work on lollipop???

hackergacon9x said:
This version 2.0 can work on lollipop???
Click to expand...
Click to collapse
Make it a habit to read previous posts. We just said it wont work on lollipop....
Rooted Zenfone MAX

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nice
★✩★ 7HD 17.0 ★✩★

One question
This kernel for zenmax snap 615 or 410 sir?
*edited : upss, sorry I didn't see the tittle code above. Thanks in advance.

[Nougat] OmniROM [Unofficial] [7.1.2] [D6603/53/33] Z3 (Leo)

Logs:
This post will describe how to take logs.
If you are using the ROM and want to make development faster/ easier please simply take a log and post it here in the thread for us to check out.
Take logs when you notice bugs etc and try to reproduce them when taking the log and give us some description of the problem.
First you will need ADB:
Set up any adb environment on you PC (showing windows here for eg.- Linux/ Mac differs):
- For windows a minimal installation will be enough to take logs and takes 15 seconds.
15 second ADB Installer
Then open the folder it is installed to so you see "adb.exe" (obviously different on Linux/Mac).
Open and CMD window in the folder with adb and you can connect your phone.
Enable USB Debugging on the phone!:
Go to Settings - About Phone - Build Number (tap this until Developer options unlocks)
Go to Developer Options and enable "USB Debugging".
Now take the actual logs running adb logcat:
- Back to the PC CMD window.
- When you run the command a window will pop up on the phone asking for access. Say yes.
- Run the command - " adb logcat > logcat.txt "
- This will give you a text file with the log to post to us.
If possible take a dmseg /kmsg:
This is most useful for bootloops etc
You may need root on the device to access these:
- " adb shell su -c dmesg > dmesg.log "
- " adb shell su -c "cat /proc/last_kmsg" > last_kmsg.log "

Screenshots
Screenshots thanks to @Tux111. Find some of his comments and hit thanks for him!
Full showcase of screenshots here: MEGA

What working?

@Dobsgw When you will update missing informations, could you please share informations about changelogs, what works, whats not, special features and some screenshots?
All the users (me too) will appreciate a lot.

I'm gonna get the info on the changes and features etc at some point later this week.
For now all I know is the build is beta but working very well. You all know Nailyk has a very high standard of work.
The current version I have installed is working as normal and since this morning (when I installed) I've seen no issues.
If you have some time it's worth checking out.
For features etc see the Omni ROM website

Dobsgw said:
I'm gonna get the info on the changes and features etc at some point later this week.
For now all I know is the build is beta but working very well. You all know Nailyk has a very high standard of work.
The current version I have installed is working as normal and since this morning (when I installed) I've seen no issues.
If you have some time it's worth checking out.
For features etc see the Omni ROM website
Click to expand...
Click to collapse
Mobile Data don't work. Every time i try to set APN, it automatically disappear. No way to make SIM data work.
The rest of the ROM is kinda awesome, some little bugs but really nicely done. Ah, message app miss. Add it please.

You probably know already but there is no link to TWRP 3.1.x for Z3 and Z3 dual (can be found in xkeita thread of Lineage 14)

Tux111 said:
Mobile Data don't work. Every time i try to set APN, it automatically disappear. No way to make SIM data work.
The rest of the ROM is kinda awesome, some little bugs but really nicely done. Ah, message app miss. Add it please.
Click to expand...
Click to collapse
Please provide full rom log, dmesg & radio log.
What variant? This rom is not dual ready yet.

tiliarou said:
You probably know already but there is no link to TWRP 3.1.x for Z3 and Z3 dual (can be found in xkeita thread of Lineage 14)
Click to expand...
Click to collapse
Xkeita TWRP is fine.
Nailyk also has a brilliant TWRP version found here in the forum.
It is updated to latest just ignore the title. 3.1.1-3

nailyk said:
Please provide full rom log, dmesg & radio log.
What variant? This rom is not dual ready yet.
Click to expand...
Click to collapse
D6603 single SIM.
Can't provide right now, sorry.
EDIT: I'll provide it soon as possible!
How i have to make radio log?

nailyk said:
Please provide full rom log, dmesg & radio log.
What variant? This rom is not dual ready yet.
Click to expand...
Click to collapse
I figured out mobile data work. But there is a bug, inside APN configuration, that automatically delete the APN created if you modify a string inside and after save it.
This time i simply used default APN settings, without modifying anything a part APN "Name" and "APN" and it works.
Here there is the logcat of the bug (over 1 mb can't upload here).
https://mega.nz/#!YAUXUSaA!3w6IWURIGvsHU-Cm9IkFStOsmyj67Sxvt9tbqqD2mG8

Tux111 said:
I figured out mobile data work. But there is a bug, inside APN configuration, that automatically delete the APN created if you modify a string inside and after save it.
This time i simply used default APN settings, without modifying anything a part APN "Name" and "APN" and it works.
Here there is the logcat of the bug (over 1 mb can't uploader here).
https://mega.nz/#!YAUXUSaA!3w6IWURIGvsHU-Cm9IkFStOsmyj67Sxvt9tbqqD2mG8
Click to expand...
Click to collapse
Thank you for taking the time to look into this.
Hopefully not a big issue

Mobile data D6603 german working LTE
Sent from my unknown using XDA-Developers Legacy app

edit

New twrp works fine and omnirom build too! Thx for hard work! ? Greets from German
Sent from my unknown using XDA-Developers Legacy app

App not using SD card photo ecc
Inviato dal mio unknown utilizzando Tapatalk

my BL is unable to get unlocked. but im now on .291 rom and rooted and twrp installed. is there nothing i can do to taste the full working nougat?
what will happen if i flash it onto my device (in this case, the BL is still locked. bootloader unlock allowed : no )
thanks.

leo31 said:
my BL is unable to get unlocked. but im now on .291 rom and rooted and twrp installed. is there nothing i can do to taste the full working nougat?
what will happen if i flash it onto my device (in this case, the BL is still locked. bootloader unlock allowed : no )
thanks.
Click to expand...
Click to collapse
You will have a brick.
Nothing you can do when unlock allowed:no.
The only thing is to contact sony, it is illegal (in some countries) to have an unlockable bootloader.

The images and most of the files do not use the sd card and when you want to pass applications to the system it does not allow attachment screenshot.
You could also add the option to expand the desktop and resize the navigation bar.

[UNOFFICIAL][PRE-ALPHA][7.1.2][H930] LineageOS 14.1

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Code:
#include "std_disclaimer.h"
/*
* Your warranty is void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Working
Boot
Mobile data
Cam (pics only)
flashlight
fingerprint
sdcard is recognized/mounted
Unknown/Untested
GPS
NFC
calls/sms (should work i guess, because data works)
audio (cant test that in class )
Issues
USB
Wifi
Bluetooth
Recording
Brightness change
Everything i forgot probably
As you can see on the "Working" list, this is a highly experimental build, flash at your own risk, and don't come crying to me if it should brick anything (it didn't for me, but seeing from the TWRP Thread the V30 can be picky).
Dont forget to make a backup!!!
If you want to report any bugs, NEVER do it without providing logs. I can't try to fix things without logs.
Helpful log commands:
logcat (usage: e.g. logcat > /sdcard/logcat.txt )
dumpsys (usage: e.g. dumpsys SurfaceFlinger > /sdcard/dump_sf.txt)
dmesg (usage: e.g. dmesg > /sdcard/dmesg.txt , might need root)
for more examples on how to use the commands, either google (do that first) or ask (only do this if you already googled how to use those commands).
FAQ
USB isn't working. How do I get logs?
In the ramdisk theres a nice little script which will print the logcat to /data/ramoops/cm14.1_<number>_logcat_<date/time>.txt
The logcat is many many hundreds of MB in size, why?
Its currently spammed with something like this:
Code:
E/QMI_FW ( 674): xport_reg Failed for service_id=0x35 version=0x1001 on 15
Replace
Code:
[0-9][0-9]-[0-9][0-9] [0-9][0-9]:[0-9][0-9]:[0-9][0-9].[0-9][0-9][0-9] E/QMI_FW ( [0-9][0-9][0-9]): xport_reg Failed for service_id=0x35 version=0x1001 on [0-9]*[0-9]
in the log with your favorite editor which can use regex with nothing (or delete all those lines if you have that option)
Is there another way to get some logs?
In Developer Options, turn on "Local Terminal", and get a logcat or other logs with that.
The screen glitches, is there a way to fix this?
I hope so, working on this too.
After restoring my backup with TWRP, my phone won't recognize my PIN (not SIM PIN). What todo now?
Just follow the guide on here. Afterwards you have to setup your PIN again (also Fingerprints, and enable Trusted Agents in Settings -> Fingerprints & Security)
Download
Version 0.0.2: https://www.androidfilehost.com/?fid=962187416754470110
Version 0.0.1: https://www.androidfilehost.com/?fid=818070582850487924
XDA:DevDB Information
Unofficial LineageOS 14.1, ROM for the LG V30
Contributors
SGCMarkus
Source Code: https://github.com/SGCMarkus
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 4.x
Version Information
Status: Testing
Created 2018-01-25
Last Updated 2018-01-25

Changelog
v 0.0.1 Initial build
it boots
v 0.0.2
Mobile data works
Cam works (pictures only)
fixed graphics glitches
Fingerprint works
flashlight works
SDCard is recognized

If you are interested to contribute/help out/test, hit me up in PM, or join my Discord Server: https://discord.gg/DJRnTRC
I set it up to be a general server for all kinds of LG V30 things, but also for Developers to meet and talk to each other, and help each other out.

Downloading...
I'll try to flash it. I'm new on LG devices (come from Samsung...)

It BOOTS

Mike.YT said:
It BOOTS
Click to expand...
Click to collapse
I agree... FC everywhere
But I hope it's a first step...

Exam time here though, so i couldnt really work on this more :/
But i have hope now for actual Treble support (we have a partition called OP, idk how important the stuff in there is though, 344MB if im not wrong, gathered all the Oreo blobs from the V300S kdz (i hope i have all needed ones), and those take up 324MB xD)
But atleast already a working recovery (TWRP 3.2.1) which would recognize the /OP as /vendor
Will work on each project a bit more when exams are over

i don't know if can help someone to build lineage or aosp based rom, btw here are the link to source and kernel for v30:
h930: http://opensource.lge.com/osSch/list?types=ALL&search=h930
us998: http://opensource.lge.com/osSch/list?types=ALL&search=us998
v300: http://opensource.lge.com/osSch/list?types=ALL&search=v300
Here the content of readme:
1. Android build
- Download original android source code ( android-7.1.2_r4 ) from http://source.android.com
( $repo init -u https://android.googlesource.com/platform/manifest -b android-7.1.2_r4
$repo sync -cdq -j12 --no-tags
$repo start android-7.1.2_r4 --all
)
- Untar opensource packages of LGH930_Nougat_Android.tar.gz into downloaded android source directory
a) tar -xvzf LGH930_Nougat_Android.tar.gz
- And, merge the source into the android source code
- Run following scripts to build android
a) source build/envsetup.sh
b) lunch 1
c) make -j4
- When you compile the android source code, you have to add google original prebuilt source(toolchain) into the android directory.
- After build, you can find output at out/target/product/generic
2. Kernel Build
- Uncompress using following command at the android directory
a) tar -xvzf LGH930_Nougat_Kernel.tar.gz
- When you compile the kernel source code, you have to add google original "prebuilt" source(toolchain) into the android directory.
- Run following scripts to build kernel
a) cd kernel/msm-4.4
b) mkdir -p out
c) make ARCH=arm64 O=./out joan_global_com_defconfig
d) make ARCH=arm64 O=./out CROSS_COMPILE=$(pwd)/../../prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android- KERNEL_COMPRESSION_SUFFIX=gz -j4
* "-j4" : The number, 4, is the number of multiple jobs to be invoked simultaneously.
- After build, you can find the build image(Image.gz) at out/arch/arm64/boot
Click to expand...
Click to collapse

I always loved to know how to build Kernel or ROM.
I'm not a dev so i cannot solve any FC or any other problem, so I need to know where to get the sources.

Little update here, decided to fix LOS14.1 first as 15.1 didnt wanna work at all ?

SGCMarkus said:
Little update here, decided to fix LOS14.1 first as 15.1 didnt wanna work at all
Click to expand...
Click to collapse
heheh don't give up my little dev... We believe in your skill :good:

Also could someone with a US998 test this?
And check what works (and doesnt)? And then send me the logcat (from /data/ramoops) after copying to the sdcard in twrp or whereever before restoring a backup xD

SGCMarkus said:
Also could someone with a US998 test this?
And check what works (and doesnt)? And then send me the logcat (from /data/ramoops) after copying to the sdcard in twrp or whereever before restoring a backup xD
Click to expand...
Click to collapse
I was just getting ready to ask if this will work on US998. If I get a chance I will try it out but I'm not sure how to do the logcat thing sorry.

foamerman said:
I was just getting ready to ask if this will work on US998. If I get a chance I will try it out but I'm not sure how to do the logcat thing sorry.
Click to expand...
Click to collapse
The logcat is taken automatically, as for idk why it wont be recognized via USB... (same kernel as the TWRP, ramdisk and so should also work), just boot into recovery after you used it a bit (if it even boots, otherwise do the button dance), and there, before you wipe/restore a backup, go to advanced -> file manager, browse to /data/ramoops and copy the log in there to the sdcard or whatever else is safe

SGCMarkus said:
The logcat is taken automatically, as for idk why it wont be recognized via USB... (same kernel as the TWRP, ramdisk and so should also work), just boot into recovery after you used it a bit (if it even boots, otherwise do the button dance), and there, before you wipe/restore a backup, go to advanced -> file manager, browse to /data/ramoops and copy the log in there to the sdcard or whatever else is safe
Click to expand...
Click to collapse
OK but now I have another problem TWRP backup failed on me. So if I do install 14.1 and it doesn't boot I have WETA 1.5 I can do the button dance and go twrp and reinstall weta as soon as I get some time I'll will try it.
---------- Post added at 02:45 PM ---------- Previous post was at 02:26 PM ----------
Sorry one more question I'm guessing we need to download our own gapps too yes? so arm64 7.1 pico would be fine that's the least one

foamerman said:
OK but now I have another problem TWRP backup failed on me. So if I do install 14.1 and it doesn't boot I have WETA 1.5 I can do the button dance and go twrp and reinstall weta as soon as I get some time I'll will try it.
---------- Post added at 02:45 PM ---------- Previous post was at 02:26 PM ----------
Sorry one more question I'm guessing we need to download our own gapps too yes? so arm64 7.1 pico would be fine that's the least one
Click to expand...
Click to collapse
Try it without gapps, its not worth to setup all that, it isnt daily driver ready... and gapps would just add more (unneccessary) stuff to the log ^^

--snip--

Well I tryred it but I got error 7 thats all I got

foamerman said:
Well I tryred it but I got error 7 thats all I got
Click to expand...
Click to collapse
Probably because of wrong device, remove the assert line in the updater-script in side the .zip file
(.zip/META-INF/com/google/android/updater-script)

SGCMarkus said:
Probably because of wrong device, remove the assert line in the updater-script in side the .zip file
(.zip/META-INF/com/google/android/updater-script)
Click to expand...
Click to collapse
OK I unzipped the file and deleted the (.zip/META-INF/com/google/android/updater-script) OK now I need a little help I'm a little slow I'm not sure how to zip it back up

[ROM][Z00ED][BETA] Ubuntu Touch (UBports)

That's sooooo cool! Can't wait to test a stable version. Keep up the good work!

Banasura said:
That's sooooo cool! Can't wait to test a stable version. Keep up the good work!
Click to expand...
Click to collapse
Thanks
I'll upload the initial build today and add a link to the thread.
Anyway, I'm surprised that people still use this device. :laugh: It's pretty old and I thought that there are only a few people who use it.

Update - 11/28/2020
v0.1.0
Initial build has been uploaded. You can download it here.
Known bugs:
Camera app reboots to EDL
Sound doesn't work
Flashlight doesn't work
Bluetooth probably broken
SIM card not detected
WiFi has to be enabled manually using SSH.
Vibrator doesn't work
Pressing the power button will show the power menu.

Update - 11/28/2020
v0.1.1
Download
Optimized display settings

Nice!

Great...but please make it stable

nhASIF said:
Great...but please make it stable
Click to expand...
Click to collapse
I'm working on it. The next build should improve performance and fix WiFi.

looks great!
does usb tethering is working?
i would try it on z00rd
upd: bootloop =(

apostrof said:
looks great!
does usb tethering is working?
i would try it on z00rd
upd: bootloop =(
Click to expand...
Click to collapse
It's probably because of missing udev rules. I'll try to add them for Z00RD in the next builds.

Max Mesa said:
I've installed it. Nice job! The ROM is pretty interesting, but laggy, it looks like hw acceleration (gpu) is broken, but I am not sure. Also I've found some new bugs in addition to the listed ones. Navbar, DT2W (double tap to wake), MTP (connection to the PC) and Bluetooth are not working. APT can neither update sources list nor install anything. Offline charging (on powered off smartphone) shows ??/100%. Usual TWRP can't decrypt FBE and access Ubuntu files. So, that's all I've found. Luckily, SD card works, and WiFi needs only one command to be enabled (echo sta > /sys/module/wlan/parameters/fwpath). Pressing power button seems to work as intended. I'll watch this thread and try new versions when I have time. Here are some screenshots:
Spoiler: Screenshots
View attachment 5205977
View attachment 5205979
View attachment 5205981
View attachment 5205983
View attachment 5205985
View attachment 5205987
View attachment 5205989
View attachment 5205991
View attachment 5205993
View attachment 5205995
Click to expand...
Click to collapse
View attachment 5205997
Thanks for trying it out, I'll do some testing and add the bugs to the list. For apt update, this is normal. The root filesystem is mounted read-only by default. To install packages, you need to remount it read-write: sudo mount -o remount,rw /

I had a break for a few months, but will continue with the development again
I've set up the build system again, and I'm going to do some testing and make WiFi working on boot.

Update - 03/17/2021
Screenshots were added to the thread.
Next build is coming this or the next month.

Update - 03/27/2021
v0.1.2
Download
Fixed camera app rebooting to EDL. Camera still doesn't work, but at least the app doesn't crash the OS.
Applied AppArmor kernel patches
Fixed vibrator
Fixed WiFi, it now enables automatically at boot.
Initial support for Z00RD (untested)
Known issues in this build:
Hotspot works, but it breaks WiFi. Either reboot or run this command (as root, NOT using sudo) after using hotspot:
echo sta > /sys/module/wlan/parameters/fwpath
Notes:
Initial support for Z00RD is here. I can't test it as I don't have this device. Anyone who has got a Z00RD, please test this build and tell me if it's stuck in a bootloop. If it is, you'll need to connect the device using a USB cable and login using SSH as `[email protected]`. Then, execute these commands:
sudo -i # And enter your password
cat /var/lib/lxc/android/rootfs/ueventd*.rc|grep ^/dev|sed -e 's/^\/dev\///'|awk '{printf "ACTION==\"add\", KERNEL==\"%s\", OWNER=\"%s\", GROUP=\"%s\", MODE=\"%s\"\n",$1,$3,$4,$2}' | sed -e 's/\r//' >/usr/lib/lxc-android-config/70-Z00RD.rules
reboot
The device should reboot and boot to the Unity 8 screen. If this doesn't work, these builds will never be compatible with Z00RD, and I'd need to use the Z00RD's device tree instead. Again, I don't have this device, so I won't compile it for Z00RD.
I was trying to make modem working, but it crashes the device and reboots to emergency download mode. If you have some experience with this device (e. g. ROM building, especially Nougat ROMs), tell me if you've ever experienced this. PM me and I'll tell more about this issue.

apostrof said:
looks great!
does usb tethering is working?
i would try it on z00rd
upd: bootloop =(
Click to expand...
Click to collapse
I uploaded build v0.1.2. Can you test it on Z00RD? I don't have this device, so you have to add udev rules manually. Read the post above for more info.

i try to install 0.1.2 - it does not boot, then i to connect ssh, but i cant connect using SSH as `[email protected]`
upd: 1 thing: the package was installed too fast, but wrote that it is ok

apostrof said:
i try to install 0.1.2 - it does not boot, then i to connect ssh, but i cant connect using SSH as `[email protected]`
upd: 1 thing: the package was installed too fast, but wrote that it is ok
Click to expand...
Click to collapse
Do you see the splash screen?
If yes, you should be able to connect if you're on Linux.
ssh [email protected]

no, didn't see the splash screen

apostrof said:
no, didn't see the splash screen
Click to expand...
Click to collapse
What do you see when you boot? Is it stuck at Asus logo or a black screen? The kernel I built should work for Z00RD too, maybe something is wrong with the Android container.

on the boot i see only default asus logo, if i turn off the phone and connect the charger - i see "Charging ??\100"

apostrof said:
on the boot i see only default asus logo, if i turn off the phone and connect the charger - i see "Charging ??\100"
Click to expand...
Click to collapse
Yeah, that charging "animation" bug is known. I don't know why it doesn't boot, but what do you see in your computer when you connect the device? Connect it to a PC and hold the power button. If you see something like Halium initrd Failed to boot, it means it failed to mount the rootfs or it failed because of some weird kernel configs.

Develop Bugs

welcome