Related
I have been using this file to overclock(2.3GHz) my zuk in every rom without any problems. But with latest ViperOS I am facing a lag in fingerprint scanning.
Can anyone help me with understanding how this file (init.qcom.post_boot.sh) works?
And is it possible to overclock to 2.4GHz as I have read everyline of this file but there is nowhere the maximum clock is mentioned.
Thanks In advance.
Kuch_Bhi said:
I have been using this file to overclock(2.3GHz) my zuk in every rom without any problems. But with latest ViperOS I am facing a lag in fingerprint scanning.
Can anyone help me with understanding how this file (init.qcom.post_boot.sh) works?
And is it possible to overclock to 2.4GHz as I have read everyline of this file but there is nowhere the maximum clock is mentioned.
Thanks In advance.
Click to expand...
Click to collapse
that is because the purpose of the file is to enable the "overfreq" feature present in the original ZUI rom, which is through this command
"echo 1 > /sys/module/msm_performance/parameters/overfreq"
now because it's a set feature, and zuk had 1.7ghz & 2.3ghz already in the kernel, that we are able to "overclock" the phone. other cpu frequencies need to be manually added via the kernel sources.
as for how the file works, I think it just execute a bunch of command at boot. It might cause conflict with the one currently using by viper, so instead of replacing the whole file, you can simply insert the required command so that it would looks like this
Code:
# input boost configuration
echo "0:1324800 2:1324800" > /sys/module/cpu_boost/parameters/input_boost_freq
echo 40 > /sys/module/cpu_boost/parameters/input_boost_ms
echo "0:4294967295 1:4294967295 2:4294967295 3:4294967295" > /sys/module/msm_performance/parameters/cpu_max_freq;chmod 444 /sys/module/msm_performance/parameters/cpu_max_freq
echo 1 > /sys/module/msm_performance/parameters/overfreq
echo 1 > /sys/devices/system/cpu/cpu0/rq-stats/mpctl
Im not sure if it works, but you can give it a try, just backup before editing
ViperOS has no such file, I simply copied the modified one without replacing anything. As for the code you suggested it is not working, that is if I replace everything in the file with this code alone.
Kuch_Bhi said:
ViperOS has no such file, I simply copied the modified one without replacing anything. As for the code you suggested it is not working, that is if I replace everything in the file with this code alone.
Click to expand...
Click to collapse
Then it doesnt work with viper's kernel. That file only works on roms that dont heavily modified the kernel source from zui stock. Some dev even outright remove overclock like in EAS AEX 4.6
pipyakas said:
Then it doesnt work with viper's kernel. That file only works on roms that dont heavily modified the kernel source from zui stock. Some dev even outright remove overclock like in EAS AEX 4.6
Click to expand...
Click to collapse
Ok. Thanks for helping.
Introduction
LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.
Requirements
Your device need to be unlocked either officially (h815 international or h811) or by UsU
Your bootloader stack should be on MM 20p (20x for H811) or higher! (see FAQ #20 for how to upgrade your bootloader stack).
.... and for your convenience I have even created TWRP flashable files for that here
in particular that means this thread is for:
F500 (UsU'd)
H810 (UsU'd)
H811
H812 (UsU'd)
H815 (official unlocked or UsU'd)
H819 (UsU'd)
LS991 (UsU'd)
US991 (UsU'd)
VS986 (UsU'd)
Latest TWRP - PREVIEW build: click
Do a full Nandroid backup before doing anything!
Installation Instructions
This single very first step is for UsU'd devices only:
If you have ever flashed the UsU baseband package: Clean flash the modem partition from your backup in TWRP.
If you do not know if you ever flashed it simply flash your modem partition again and you can be sure. This can't do any harm.
If you have no backup:
- TWRP flashable MM modems (N might not work)
Full clean install as described here (FAQ "#2") is highly recommended. DO NOT REPORT ISSUES when you have skipped that step!
Flash LOS
Optional: Flash GApps (8.1 - ARM64 for LOS 15.1, 7.1 - ARM64 for LOS 14.1) if you like
Optional (if you want root): Flash the official LOS root-addon (addonsu-15.1-arm64-signed.zip or addonsu-14.1-arm64-signed.zip) or Magisk (do not report issues if you have Magisk installed though!)
Boot (will take a bit on first boot!!!)
Enjoy
For more detailed instructions, please see my website (thepiguy0.github.io/installing)
Update Instructions
To update from a previous version of my rom:
If it is an old version of the rom, it is recommended to do a clean flash - Be aware that your data will be deleted
If it is a relatively recent version, a dirty flash should be ok - wipe cache and dalvik cache and then flash on top of your current installation - This keeps all your files
Current Issues
For a current list of all issues including possible workarounds:
Open issues
Issues with workarounds available
Summary (again check out the above linked issue tracker for a current state):
Bluetooth calling FIXED!
Flashlight icon on quick toggles FIXED!
SIM pin unlocking (Ril works, better to use an unlocked sim card for now) FIXED!
Magisk when encrypted - state UNKNOWN
Permissive SELinux FIXED!
Probably more undiscovered bugs
Downloads
Get the latest builds from steadfasterX's server
Get the legacy builds from my Google drive
Building from source
If you want to build this from source, follow the LG H815 build guide (replace H815 with H811 if needed). Immediately before the "repo sync" step, copy our local manifest (https://github.com/Suicide-Squirrel/local_manifests/blob/los-15.1/roomservice.xml) into the .repo/local_manifests/ folder. Now run repo sync.
Then miss out breakfast and proprietary files steps before continuing with Jack memory optimisations
Changelog
Go through the results here: click
older ones click here:
20/05/2018
WiFi Hotspot is now fixed
H811 audio is fixed
More audio enhancements behind the scenes
Increased performance in Titan Kernel
28/04/2018
Audio is now fully working (with the exception of bluetooth calling)
Camera and screen recorder are now both fully fixed and work
Latest Lineage and Titan updates
FAQ
Will be added as the time goes.
Credits
@kessaras, @steadfasterX and the LineageOS team
Sources
Lineage source code - https://github.com/LineageOS/
Device trees and kernel (forked from cypheros) - https://github.com/suicide-squirrel/
Proprietary files - https://github.com/CypherOS/
PREVIOUS OP (for historical reasons)
Introduction
LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.
Requirements
LG G4 H815/H811
Latest MM firmware for H811 and latest Nougat/MM firmware for H815
Latest official TWRP or the latest TWRP preview from steadfasterX's server - This prevents the error 7 from appearing
For UsU devices, follow @steadfasterX's instructions for TWRP
Installation Instructions
Download appropriate zip for your device along with any additional modules such as gapps (arm64 android 8.1 needed)
Recommended - Create a full nandroid backup to allow you to restore to your previous OS if needed
Wipe system, data, cache and dalvik cache - Be aware that this WILL remove your currently installed OS and wipe your apps and most data
Flash the lineage zip, followed immediately by gapps if applicable
Reboot into system and wait for boot
For more detailed instructions, please see my website (thepiguy0.github.io/installing)
Update Instructions
To update from a previous version of my rom:
If it is an old version of the rom, it is recommended to do a clean flash - Be aware that your data will be deleted
If it is a relatively recent version, a dirty flash should be ok - wipe cache and dalvik cache and then flash on top of your current installation - This keeps all your files
Current Issues
For a current list of all issues including possible workarounds:
Open issues
Issues with workarounds available
Summary (again check out the above linked issue tracker for a current state):
Bluetooth calling
Flashlight icon on quick toggles
SIM pin unlocking (Ril works, better to use an unlocked sim card for now)
Magisk when encrypted
Permissive SELinux
Probably more undiscovered bugs
Downloads
Get the latest builds from steadfasterX's server
Get the legacy builds from my Google drive
Building from source
If you want to build this from source, follow the LG H815 build guide (replace H815 with H811 if needed). Immediately before the "repo sync" step, copy our local manifest (https://github.com/Suicide-Squirrel/local_manifests/blob/los-15.1/roomservice.xml) into the .repo/local_manifests/ folder. Now run repo sync.
Then miss out breakfast and proprietary files steps before continuing with Jack memory optimisations
Changelog
20/05/2018
WiFi Hotspot is now fixed
H811 audio is fixed
More audio enhancements behind the scenes
Increased performance in Titan Kernel
28/04/2018
Audio is now fully working (with the exception of bluetooth calling)
Camera and screen recorder are now both fully fixed and work
Latest Lineage and Titan updates
FAQ
Will be added as the time goes.
Credits
@kessaras, @steadfasterX and the LineageOS team
Sources
Lineage source code - https://github.com/LineageOS/
Device trees and kernel (forked from cypheros) - https://github.com/suicide-squirrel/
Proprietary files - https://github.com/CypherOS/
XDA:DevDB Information
LineageOS 14.1/15.1 for LG G4, ROM for the LG G4
Contributors
ThePiGuy, steadfasterX, kessaras, berkantkz and LineageOS
Source Code: https://github.com/LineageOS/
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
ROM Firmware Required: v20 (or higher for H815) bootloader and modem
Based On: Lineage OS
Version Information
Status: Stable
Current Beta Version: 20180428
Beta Release Date: 2018-04-28
Created 2018-04-26
Last Updated 2019-12-22
Reserved
Reserved
Great work!
Need more stability to have a try but following it closely!
Thanks a lot.
Good job!
I missed Lineage OS.
Is encryption working?
YOU, @ThePiGuy, built this (with help from others)? Well done man.
Good luck and Godspeed man
zeduck said:
Good job!
I missed Lineage OS.
Is encryption working?
Click to expand...
Click to collapse
Yes it is
ThePiGuy said:
Yes it is
Click to expand...
Click to collapse
Is it trimming working with encryption ( fstrim -v /data ) without the error transport endpoint not connected?
Thanks!
talk to @codeworkx.
if your commits you added are clean and crystal clear of what you did and you kept authorship, maybe you should update the official and get some logs to them to also help you.
Minor bugs of audio and maybe some props to make the camera function correctly are not hard bugs. Me i do not have the time sorry. I do not even have the time with AOSCP now that im working so much :/
Great job keeping LOS on this device. I'm holding on to it as I still find it fast and useful.
While there is a lens on the audio configuration it would be awesome to see this phone enabled for hires audio (up to 24bit / 192KHz) under LOS. I know people are skeptical of the difference but DAC is able to do this and it should simply be an edit of the relevant audio_policy_configuration.xml(?) file to enable the extra sound profiles above 16/48.
hteles said:
Is it trimming working with encryption ( fstrim -v /data ) without the error transport endpoint not connected?
Thanks!
Click to expand...
Click to collapse
I have no idea (give it a go if you want )
belrik said:
Great job keeping LOS on this device. I'm holding on to it as I still find it fast and useful.
While there is a lens on the audio configuration it would be awesome to see this phone enabled for hires audio (up to 24bit / 192KHz) under LOS. I know people are skeptical of the difference but DAC is able to do this and it should simply be an edit of the relevant audio_policy_configuration.xml(?) file to enable the extra sound profiles above 16/48.
Click to expand...
Click to collapse
First things first, got to get the audio working in the first place . And also, nobody seems to have seen the error that it kicks out in the logcat, so it might take a while to get it working - I'll try porting the cm-14.1 trees to lineage-15.1 rather than porting oreo cypheros trees to see if that makes a difference
@ThePiGuy what are the known bugs for this rom?
NummerEinsNerd said:
@ThePiGuy what are the known bugs for this rom?
Click to expand...
Click to collapse
All in the title post above (under Current Issues). Basically audio is fully broken (so this is purely testing at the moment - not suitable for a daily driver), camera is broken along with the lineage voice and screen recorder crashing.
ThePiGuy said:
All in the title post above (under Current Issues). Basically audio is fully broken (so this is purely testing at the moment - not suitable for a daily driver), camera is broken along with the lineage voice and screen recorder crashing.
Click to expand...
Click to collapse
All camera apps ? Even Google s ?
If Google's work, then it's just a prop.
Also yes that's normal since Los uses snap and maybe it needs different props , it may needs a couple different things to call for build and some overlay settings in a config.
The other Los developers should already know how to make this work since they have ported many phones.
Me I never developed in los, I don't know.
kessaras said:
All camera apps ? Even Google s ?
If Google's work, then it's just a prop.
Also yes that's normal since Los uses snap and maybe it needs different props , it may needs a couple different things to call for build and some overlay settings in a config.
The other Los developers should already know how to make this work since they have ported many phones.
Me I never developed in los, I don't know.
Click to expand...
Click to collapse
I haven't tested any others yet. I'm mainly focusing on the audio at the moment
Great job bringing LOS back to life for the G4!
Thanks for your effort! I will monitor this Thread closely and hope you soon find the audio issues
Hi,
Even though I'm not quite experienced, I'd like to join the development of this rom. Right after installing it on my device and reading the logcat, I've partially fixed the audio problem. I've also created a pull request and given enough information on GitHub repository.
Edit: Full message from GitHub
These missing files which had to be under "/system/vendor/etc" folder lead to crashes on the apps which use sound. By placing them to where they have to be, crashes on music player when trying to play any music and video recording are fixed. Although there has been no sound yet, these changes are required in order to prevent crashes.
Also, there may be another way in order to fix crashes instead of doing these changes. It is to edit the paths to "/system/etc/" as the files are already placed there.
I guess the lines for "/system/etc" can be removed as well but I am not sure if there are any system part that uses this directory. It's better to let them stay under "/system/etc" as well.
Additional message:
These changes also fixed handset and earphones. The handset is working on calls and earphones work on video/music now. However, the speaker still doesn't work. Video recording works as well as the built-in microphone does.
Additional message 2:
From now on, neither audio nor screen recorder crash. Both work well.
Click to expand...
Click to collapse
berkantkz said:
Hi,
Even though I'm not quite experienced, I'd like to join development of this rom. Right after installing it on my device and reading the logcat, I've partially fixed the audio problem. I've also created a pull request and given enough information on GitHub repository.
Click to expand...
Click to collapse
Brilliant!!! Thanks Don't worry about not being experienced - this is my first proper project at getting a rom going, so I'm learning as well
New H815 build out (20180428) with fixed audio, camera and screen/audio recorder. This has given rise to the fact that BT calling is indeed broken like it is on AOSCP
H811 build coming out soon.
Massive thanks to @berkantkz, without whom I wouldn't have been able to do it
Edit: H811 build is up as well now
Based on Demetris' LOS 14.1, with :
Android security patch level updates, currently 2020-02-05
tracking LA.BR.1.2.9 from CAF, currently 1.2.9_rb1.44
WIP upstream with linux-stable, currently upgraded from 3.10.49 to 3.10.68 3.10.75
SELinux enabled (better security, SafetyNet & PlayStore should be ok, if not check @tess1 clear caches post )
2018 fixes : MTP, battery consumption, camrecorder crash, wifi, OpenGL ES version, dualsim 6045K (update to MM first), lid & proximity sensor
known problems :
camrecording low brightness
mobile internet connectivity loss and battery drain after a while (days) : toggle airplane mode and back, or reboot
new problems : none known at the moment, but the ROM is not so thoroughly tested before publication
How to investigate and report problems :
sudo adb shell dmesg > dmesg.txt
sudo adb logcat > logcat.txt
sudo adb logcat -b radio > radio.txt
Credits : @FireLord, @Demetris, @Unjustified Dev and all the giants whose shoulders we stand upon !
Source code : Kernel | Device | Vendor trees | Local manifest : View attachment idol3.xml
Changes since previous build : see the build release post
Downloads : lineage-14.1-20200226-UNOFFICIAL-idol3.zip | other releases
Kernel alternative (cam might not work since 20190619 build) : overclocked kernel by @DepressedHedgehog
Reserved
Thanks a lot for sharing this build. Now that the method for restoring our phones to stock has been taken away from us, I'm hoping that more people will jump in and try to solve some of the few remaining issues with this ROM.
Personally I'd like to figure out why the Play Store is installing old versions of certain apps and listing other apps as being incompatible while they can be still sideloaded without any problem. I've found many threads on XDA with people complaining about the same issue but no solution that worked so far. Is this an issue with opengapps, or bad entries in the build.prop? I've compared with the original build.prop from stock 6.0.1 and tried changing values around but no success.
Also battery life seems a lot shorter with Nougat, and there is no way to find out which apps/processes are being power hungry as you have already pointed out.
Issues aside this ROM still makes this phone quite usable and stable compared with other ROM's I have tried so good job and I'm looking forward to testing out new builds.
new thread - we're open for business!
@vknecht once again, thanks for your continued efforts... I tried your Sept 12 release with opengapps Sept. 12 as well - the Play store continues to thwart our efforts in the same manner.
@upyisfar I found that the battery drain during sleep could be reduced to almost nil with the following settings:
- turn off WIFI during sleep - Settings-> WIFI -> Gear Icon -> Keep WIFI on during sleep -> change to....
- turn off Emergency Broadcasts - Settings -> ...More ->Emergency Broadcasts -> Uncheck all
20180918 build : add ptt_socket_app for better wifi and battery
This was a complain in the logs, so added it from MM.
There are still batterystats related problems but there's a lead...:
Code:
09-19 15:14:35.466 1192 1344 E BatteryStatsService: no controller energy info supplied
09-19 15:14:35.748 1192 1212 E BatteryStatsService: power: Missing API
09-19 15:14:35.762 1192 1344 E BatteryStatsService: modem info is invalid: ModemActivityInfo{ mTimestamp=0 mSleepTimeMs=0 mIdleTimeMs=0 mTxTimeMs[]=[0, 0, 0, 0, 0] mRxTimeMs=0 mEnergyUsed=0}
Thanks @upyisfar @tess1 for the feedback, keep us posted with your findings...
@vknecht
1. Just tried something... reinstalled 7/18 build where all of the play store program installations were working and then overlayed it with OTA 9/18 which then led to PLay Store blocking installation of many apps ("device isn't compatable" error) - I recall that the build after 7/18 included 25 fixes/commits. Not easy to track it down but could the problem be from one of those fixes/commits?
2. The proximity sensor (tsl2772-ps) error was earlier reported as either missing a driver or needing a shim. Is this a file that can be pulled from Marshmallow and put into this ROM?
Battery updates to follow
vknecht said:
This was a complain in the logs, so added it from MM.
There are still batterystats related problems but there's a lead...:
Click to expand...
Click to collapse
Interesting. How do we know if those changes were merged into the LineageOS's code repo?
vknecht said:
[*]SELinux enabled (helps with safetynet basicIntegrity test ; also better security, but some glitches here and there)
[*]new problems : probably due to SELinux now in "enforce" mode, like battery stats
Click to expand...
Click to collapse
I've installed your new build last night and I've set my kernel to run in permissive mode (Magisk SELinux Manager module) and safetynet basicIntegrity test still passes just so you know. Battery life now feels more comparable to what I get in stock MM. Not sure if this due to SELinux being switched to permissive or the the changes that you have made.
What build environment are you using to build your ROM's, I'm trying to build on Debian stable following your instructions here and keep getting compilation errors.
tess1 said:
@vknecht
1. Just tried something... reinstalled 7/18 build where all of the play store program installations were working and then overlayed it with OTA 9/18 which then led to PLay Store blocking installation of many apps ("device isn't compatable" error) - I recall that the build after 7/18 included 25 fixes/commits. Not easy to track it down but could the problem be from one of those fixes/commits?
Click to expand...
Click to collapse
I thought the 20180905 build ruled out the august kernel updates as the breaker but in fact I should and will retry kernel from july with SELinux enabled ; if it's still not OK then I guess the cause is LOS august update...
tess1 said:
2. The proximity sensor (tsl2772-ps) error was earlier reported as either missing a driver or needing a shim. Is this a file that can be pulled from Marshmallow and put into this ROM?
Click to expand...
Click to collapse
iiuc the hint is that we need either a HAL/framework wrapper OR reuse stock Lollipop driver+shim.
I'm sorry I don't know much about this low-level androidy stuff yet and don't have much time atm to focus on it.
upyisfar said:
Interesting. How do we know if those changes were merged into the LineageOS's code repo?
Click to expand...
Click to collapse
I think if it was in LOS it should appear here : https://github.com/LineageOS/android_system_extras/commits/cm-14.1/ext4_utils
upyisfar said:
I've installed your new build last night and I've set my kernel to run in permissive mode (Magisk SELinux Manager module) and safetynet basicIntegrity test still passes just so you know. Battery life now feels more comparable to what I get in stock MM. Not sure if this due to SELinux being switched to permissive or the the changes that you have made.
What build environment are you using to build your ROM's, I'm trying to build on Debian stable following your instructions here and keep getting compilation errors.
Click to expand...
Click to collapse
I'm using Fedora 28 ; note that you'd have to update the local manifest ($ANDROID_ROOT/.repo/local_manifests/idol3.xml) using given kernel/device/vendor trees as linked in OP, so at the moment it should look like :
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="vknecht/android_device_alcatel_idol3" path="device/alcatel/idol3" remote="github" revision="fix-ptt_socket_app" />
<project name="vknecht/android_kernel_alcatel_msm8916" path="kernel/alcatel/msm8916" remote="github" revision="upstream-lxstable-cafrb144" />
<project name="vknecht/proprietary_vendor_alcatel" path="vendor/alcatel" remote="github" revision="fix-ptt_socket_app" />
<project name="LineageOS/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-14.1" />
</manifest>
(to use july kernel change revision to "upstream-lxstable").
For idol3 build environment setup help, feel free to send me private messages or join #idol3 on Freenode, or maybe even create a thread, for the more we are able to build, the better...
vknecht said:
I thought the 20180905 build ruled out the august kernel updates as the breaker but in fact I should and will retry kernel from july with SELinux enabled ; if it's still not OK then I guess the cause is LOS august update...
iiuc the hint is that we need either a HAL/framework wrapper OR reuse stock Lollipop driver+shim.
I'm sorry I don't know much about this low-level androidy stuff yet and don't have much time atm to focus on it.
Click to expand...
Click to collapse
1 Just tried the 9/05 build --> same play store issue --> August updates maybe problematic
2 Fair enough... I don't know enough but am willing to beta test along the way
It is all in progress...
tess1 said:
1 Just tried the 9/05 build --> same play store issue --> August updates maybe problematic
2 Fair enough... I don't know enough but am willing to beta test along the way
It is all in progress...
Click to expand...
Click to collapse
I've tried the july 3.10.68 kernel (used in 20180718 and 20180905 builds) with current device/vendor trees, and still G compat problems, so it leaves the Android/LineageOS diffs from 2018-06-05 to 2018-08-05 patch levels (afaik there was no 2018-07-05 for LOS 14.1 and there's no 2018-09-05 yet).
20180924 build : 2018-09-05 android security patch level
Only change is Android/LineageOS framework (repo sync) for 2018-09-05 update
Too sad, it doesn't seem to solve the some-apps-in-proeminent-vendor-store incompatibility problem...
@upyisfar : I've wondered about "the method for restoring our phones to stock has been taken away from us", what did you mean ?
While, too bad, the Sugar utility (which had my preference) now fails on a "site not found" error (maybe should try a fresh install, why not in Wine), I still could reset by using the "Panasonic Eluga Switch" utility then the "Mobile Q upgrade" (~1 hour total, with 100Mbs connection) to go back to stock.
lineage-14.1-20180924-UNOFFICIAL-idol3.zip | or OTA zip
Q
vknecht said:
I've wondered about "the method for restoring our phones to stock has been taken away from us", what did you mean ?
While, too bad, the Sugar utility (which had my preference) now fails on a "site not found" error (maybe should try a fresh install, why not in Wine), I still could reset by using the "Panasonic Eluga Switch" utility then the "Mobile Q upgrade" (~1 hour total, with 100Mbs connection) to go back to stock.
Click to expand...
Click to collapse
The Sugar utility was what I was referring to. Haven't had any success with the Mobile Q though, I always get a "check your internet connection" message or something like that. The MM 6.0.1 ROM posted by The Marionette is close enough though. I don't expect Alcatel to push more OTA updates for this device anyway.
I'm sticking with your build of Nougat now that the battery drain issue has gone away. I don't mind manually transfering the APK's from another device to my phone, for now at least. I have managed to set up my build environment (was missing a dependency) and will be producing a test build soon to see if I can fix a thing or two. In the mean time I will happily upgrade to the new build that you have just posted. Thanks!
upyisfar said:
The Sugar utility was what I was referring to. Haven't had any success with the Mobile Q though, I always get a "check your internet connection" message or something like that. The MM 6.0.1 ROM posted by The Marionette is close enough though. I don't expect Alcatel to push more OTA updates for this device anyway.
I'm sticking with your build of Nougat now that the battery drain issue has gone away. I don't mind manually transfering the APK's from another device to my phone, for now at least. I have managed to set up my build environment (was missing a dependency) and will be producing a test build soon to see if I can fix a thing or two. In the mean time I will happily upgrade to the new build that you have just posted. Thanks!
Click to expand...
Click to collapse
@upyisfar
Just 3 weeks ago, I was able to restore (in Canada) my Idol 3 to stock MM using Mobile Upgrade (I think it was version 5.1.7 as 5.1.8 would not do anything).
Here is an upload link:
5.1.7:
https://mega.nz/#!KmogkYAa!e5y6ZSM987quN6bTYRNWnZuNQSBnCjANMglrhB4rtHo
5.1.8:
https://mega.nz/#!OuhEGaaQ!g6mH6RE7v7MEGSI5-uWsr_t4MZCX3qh1fmCtHzhHptI
I put the phone into download mode and it took about 30 minutes.
---------- Post added at 10:45 PM ---------- Previous post was at 10:39 PM ----------
@vknecht
vknecht said:
This was a complain in the logs, so added it from MM.
There are still batterystats related problems but there's a lead...:
Code:
09-19 15:14:35.466 1192 1344 E BatteryStatsService: no controller energy info supplied
09-19 15:14:35.748 1192 1212 E BatteryStatsService: power: Missing API
09-19 15:14:35.762 1192 1344 E BatteryStatsService: modem info is invalid: ModemActivityInfo{ mTimestamp=0 mSleepTimeMs=0 mIdleTimeMs=0 mTxTimeMs[]=[0, 0, 0, 0, 0] mRxTimeMs=0 mEnergyUsed=0}
Thanks @upyisfar @tess1 for the feedback, keep us posted with your findings...
Click to expand...
Click to collapse
re: add ptt_socket_app for better wifi and battery
Would it be possible for you to list the (hopefully few) files and any edited files that you put into this build and the corresponding locations so that I can graft them onto my 7/18 build?
tess1 said:
Just 3 weeks ago, I was able to restore (in Canada) my Idol 3 to stock MM using Mobile Upgrade (I think it was version 5.1.7 as 5.1.8 would not do anything).
Here is an upload link:
5.1.7:
https://mega.nz/#!KmogkYAa!e5y6ZSM987quN6bTYRNWnZuNQSBnCjANMglrhB4rtHo
5.1.8:
https://mega.nz/#!OuhEGaaQ!g6mH6RE7v7MEGSI5-uWsr_t4MZCX3qh1fmCtHzhHptI
I put the phone into download mode and it took about 30 minutes.
Click to expand...
Click to collapse
OK. I was wondering if Alcatel was geo-blocking some countries seeing how some people have success and others don't. I'm in Canada too so I guess that isn't the issue. For now I'm more interested in trying to find a solution to the opengapps compatibility problem.
---------- Post added at 11:04 PM ---------- Previous post was at 10:51 PM ----------
tess1 said:
[MENTION=9435528]
re: add ptt_socket_app for better wifi and battery
Would it be possible for you to list the (hopefully few) files and any edited files that you put into this build and the corresponding locations so that I can graft them onto my 7/18 build?
Click to expand...
Click to collapse
See these commits https://github.com/vknecht/propriet...mmit/f84888778905c179e0d49d7587bc5467248e4b01 and https://github.com/vknecht/android_...mmit/dc64e2c79616e33640a2680451e2fe5ab0152d89
... and the workaround for disabling the bogus 3rd camera mode
https://github.com/vknecht/propriet...mmit/b57afd7960943e0dc8f0c593ae25cb74b5351a3f
6045K / dualsim / multisim
Code:
idol3:/ # setprop ctl.start ril-daemon1
Does it make it better for you too ? (dunno if there's a non-root or GUI equivalent...)
Good news!
I have found the fix for the opengapps store compatibility issue.
I noticed in CPU-z that the reported OpenGL ES version was 1.0 so I added a line to my build.prop:
Code:
ro.opengles.version=196609
And now CPU-z reports version OpenGL ES version 3.1 and all my apps are available for download in the G store.
the value "196609" is decimal for hexadecimal 30001 (OpenGL ES 3.1). Ive seen a commit on github that says support for 3.2 was added but when I change the value to "196610", CPU-z still reports 3.1 not sure why..
vknecht said:
new problems : probablymaybe due to SELinux now in "enforce" mode, like battery stats
Click to expand...
Click to collapse
Appears to be working since the 2 latest builds, with SELinux set to enforce:
[/COLOR]
upyisfar said:
Good news!
I have found the fix for the opengapps store compatibility issue.
I noticed in CPU-z that the reported OpenGL ES version was 1.0 so I added a line to my build.prop:
Code:
ro.opengles.version=196609
And now CPU-z reports version OpenGL ES version 3.1 and all my apps are available for download in the G store.
the value "196609" is decimal for hexadecimal 30001 (OpenGL ES 3.1). Ive seen a commit on github that says support for 3.2 was added but when I change the value to "196610", CPU-z still reports 3.1 not sure why..
Click to expand...
Click to collapse
SECONDED - Confirmed fixed! and the Play Store also reports that my Device is Certified under Play Protect Certification.
Thank you upyisfar
vknecht said:
Code:
idol3:/ # setprop ctl.start ril-daemon1
Does it make it better for you too ? (dunno if there's a non-root or GUI equivalent...)
Click to expand...
Click to collapse
6045I single-sim here, can't test this, sorry.
BTW can you add "low brightness in camera video capture mode" to list of known issues in the op? thx
The few A12 AOSP-based ROMs that I tried were all generating echo during a Whatsapp video call (or similar loudspeaker VoIP scenario).
Has anyone else tried an A12 AOSP-based ROM where the echo cancelation is working properly in loudspeaker VoIP scenarios?
If so, could you please tell us about the ROM (and firmware used)?
Fix:
1. Edit /vendor/etc/audio_effects.xml by adding these values:
<preprocess>
<stream type="voice_communication">
<apply effect="aec"/>
<apply effect="ns"/>
</stream>
</preprocess>
2. Edit file /vendor/build.prop: remove the following line (or set to false)
vendor.audio.feature.compr_voip.enable=true
Source: https://forum.xda-developers.com/t/...-redmi-note-8-8t-stable.4207101/post-84438085
After a month or so of testing it as a daily driver, I'll post my self built rom. It's been built just following my building guide, I didn't touch the code in any other way (and it's quite noticeable regarding the loudspeaker). It's still got a few bugs (and a few newer ones), but this is the first stable-ish rom I've managed to build since April. Tested on the US version only.
-- DISCLAIMER --
It is highly advised to backup all your phone data, as it will be PERMANENTLY LOST during the upgrade process. Keep in mind that will be needed for future updates as well, as all self built Lineage 19 roms from source needed a hard reset to work properly. This is a highly experimental build, so EVERYTHING IS AT YOUR RISK. I take to responsibility whatsoever.
Also, FOLLOW THE INSTRUCTIONS BELOW as repartitioning the device is NECESSARY for the success of the operation.
---> DOWNLOAD LINK HERE: https://androidfilehost.com/?w=files&flid=335748 <---
-- REQUIREMENTS --
- a computer with adb and fastboot installed. For further information and downloads go to https://developer.android.com/studio/releases/platform-tools
- a minimal comfort using a command line interface. For reference, a complete guide for the moto g7 play can be found here: https://wiki.lineageos.org/devices/channel/install
-- INSTRUCTIONS --
- download the regular Moto g7 partitioning file: https://androidfilehost.com/?fid=14655340768118450531 (thanks SyberHexen ). Remember this is STRICLY NECESSARY.
- connect your Moto g7 play in fastboot mode to a computer with adb and fastboot installed
- from the folder where the file has been downloaded, flash the Moto g7 partitioning file using this command:
fastboot flash boot ocean_gpt.bin
- from the moto g7 play, wipe the memory and the dalvik cache, go into recovery mode, allow sideloading and then sideload the lineage-19.1-20220721-UNOFFICIAL-channel file using the following command:
adb sideload lineage-19.1-20220721-UNOFFICIAL-channel.zip
- OPTIONAL: if you desire to install the Google apps, reboot your phone into Recovery Mode and sideload the respective package (MindTheGapps-12.1.0-arm64-20220416_174313 worked great for me)
- reboot.
-- SOURCE --
- base Lineage OS 19.1: https://github.com/LineageOS/android/tree/lineage-19.1 . This includes the standard sm6150 kernel found here: https://github.com/sm6150-motorola/android_kernel_motorola_sm6150
- SyberHexen's Motorola Channel specific settings: https://github.com/SyberHexen/android_device_motorola_channel/tree/lineage-19.1
- Proprietary blobs extracted through this guide from SyberHexen's April build (Android File Host)
-- KNOWN BUGS --
- the Lineage and the Whatsapp camera don't work well, in particular they don't always shoot photos when the button is pressed. Google Camera does work great tho.
- the backlight doesn't always turn up when calls are received (putting a finger on the fingerprint sensor with the phone ringing will turn it on)
- screen on on notifications does not work
- loudspeaker can be tinny at high volume (may be due to the loudspeaker's poor quality and to the common settings of the mixer_paths.xml file, for more info on the topic: https://forum.xda-developers.com/t/anyone-have-fix-for-low-volume-from-speaker.4054283/ )
Thank you all for this ROM, also there are LineageOS 20 builds (Android 13) on official LineageOS site, i want to ask if there is an way to fix ambient display on LineageOS 19, LineageOS 20 sadly gives me way too low RAM to use it, and SWAP memory is not working on Lineage 20
Edit: many apps do restart extremely often, but it's understandable since it's only an 2 GB RAM device running an ARM64 ROMs
@feder86co @chuy19312 Tell me please, does 4K video recording works on this particular ROM? Or is it possible at least?
kreksoverzum said:
@feder86co @chuy19312 Tell me please, does 4K video recording works on this particular ROM? Or is it possible at least?
Click to expand...
Click to collapse
Well, i didn't test that but sadly, Moto Camera doesn't even have enough permissions to save pictures to SD Card
please help..
I don't got a OS bc i was installing a ROM but it didn't work..
I was trying to install this but it says "No devices found"
newbierooter said:
please help..
I don't got a OS bc i was installing a ROM but it didn't work..
I was trying to install this but it says "No devices found"
Click to expand...
Click to collapse
Try to install Fastboot/ADB Driver
feder86co said:
After a month or so of testing it as a daily driver, I'll post my self built rom. It's been built just following my building guide, I didn't touch the code in any other way (and it's quite noticeable regarding the loudspeaker). It's still got a few bugs (and a few newer ones), but this is the first stable-ish rom I've managed to build since April. Tested on the US version only.
-- DISCLAIMER --
It is highly advised to backup all your phone data, as it will be PERMANENTLY LOST during the upgrade process. Keep in mind that will be needed for future updates as well, as all self built Lineage 19 roms from source needed a hard reset to work properly. This is a highly experimental build, so EVERYTHING IS AT YOUR RISK. I take to responsibility whatsoever.
Also, FOLLOW THE INSTRUCTIONS BELOW as repartitioning the device is NECESSARY for the success of the operation.
---> DOWNLOAD LINK HERE: https://androidfilehost.com/?w=files&flid=335748 <---
-- REQUIREMENTS --
- a computer with adb and fastboot installed. For further information and downloads go to https://developer.android.com/studio/releases/platform-tools
- a minimal comfort using a command line interface. For reference, a complete guide for the moto g7 play can be found here: https://wiki.lineageos.org/devices/channel/install
-- INSTRUCTIONS --
- download the regular Moto g7 partitioning file: https://androidfilehost.com/?fid=14655340768118450531 (thanks SyberHexen ). Remember this is STRICLY NECESSARY.
- connect your Moto g7 play in fastboot mode to a computer with adb and fastboot installed
- from the folder where the file has been downloaded, flash the Moto g7 partitioning file using this command:
fastboot flash boot ocean_gpt.bin
- from the moto g7 play, wipe the memory and the dalvik cache, go into recovery mode, allow sideloading and then sideload the lineage-19.1-20220721-UNOFFICIAL-channel file using the following command:
adb sideload lineage-19.1-20220721-UNOFFICIAL-channel.zip
- OPTIONAL: if you desire to install the Google apps, reboot your phone into Recovery Mode and sideload the respective package (MindTheGapps-12.1.0-arm64-20220416_174313 worked great for me)
- reboot.
-- SOURCE --
- base Lineage OS 19.1: https://github.com/LineageOS/android/tree/lineage-19.1 . This includes the standard sm6150 kernel found here: https://github.com/sm6150-motorola/android_kernel_motorola_sm6150
- SyberHexen's Motorola Channel specific settings: https://github.com/SyberHexen/android_device_motorola_channel/tree/lineage-19.1
- Proprietary blobs extracted through this guide from SyberHexen's April build (Android File Host)
-- KNOWN BUGS --
- the Lineage and the Whatsapp camera don't work well, in particular they don't always shoot photos when the button is pressed. Google Camera does work great tho.
- the backlight doesn't always turn up when calls are received (putting a finger on the fingerprint sensor with the phone ringing will turn it on)
- screen on on notifications does not work
- loudspeaker can be tinny at high volume (may be due to the loudspeaker's poor quality and to the common settings of the mixer_paths.xml file, for more info on the topic: https://forum.xda-developers.com/t/anyone-have-fix-for-low-volume-from-speaker.4054283/ )
Click to expand...
Click to collapse
when will we have new updates?
Androi100 said:
when will we have new updates?
Click to expand...
Click to collapse
Here, in the official site, there is an 2023-05-07 update
LineageOS Downloads
download.lineageos.org
chuy19312 said:
Here, in the official site, there is an 2023-05-07 update
LineageOS Downloads
download.lineageos.org
Click to expand...
Click to collapse
more on the site there is only one lineage 20
Androi100 said:
more on the site there is only one lineage 20
Click to expand...
Click to collapse
Well, sadly, LineageOS 19 zips were deleted, even LineageOS 18 zips some time ago, and i never understood why, there are only LineageOS 20 builds today
Androi100 said:
more on the site there is only one lineage 20
Click to expand...
Click to collapse
I just remembered, i have the last official LineageOS 19 for Moto G7 Play, i uploaded it to my Google Drive, here you have an link
lineage-19.1-20221225-nightly-channel-signed.zip
drive.google.com
The only bug it have is that ambient display doesn't work, at least, is the only one i found
Note to official developer of this ROM. if there is an problem to share this old version ROM, please tell me , but please, don't report my link in case there is an problem, i can remove the link but not the ROM since i have it because LineageOS 20 restarts almost all of the apps, multitasking on that rom doesn't exist because when switching on apps, they get restarted, even system ones
Edit: if someone have an build of LineageOS 18 or 18.1, please, give me an link for it