Hi everyone,
I just build successfully Android 9 Pie for the X compact from the Sony repo.
I have not test it yet but it boot.
If you want to try I can give you the files.
Lots of bugs?
Some screenshot?
Is it good for daily?
Thx!
luomei said:
Lots of bugs?
Some screenshot?
Is it good for daily?
Thx!
Click to expand...
Click to collapse
It works but not for daily as Gapps aren't available yet...
I try some unofficials ones but it causes the phone not to boot
{
"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"
}
Please give more details on whats working and whats not
Bluetooth
Wifi
Hotspot
Calling
3g/4g connectivity
Camera
Etc...
I didn't test all features but network works
I can't test it for now because I need my phone (I only have one Xperia compatible), but I'll try to test all features later this week :victory:
compilation attempt
Hi @nervousapp,
I'm attempting a build myself using the guide published by Sony recently, but I'm stuck at some errors:
system/sepolicy/Android.mk:79: warning: BOARD_SEPOLICY_VERS not specified, assuming current platform version
[948/948] including vendor/qcom/opensource/wlan/wcnss-service/Android.mk ...
vendor/qcom/opensource/location/loc_api/ds_api/Android.mk: error: libloc_ds_api (SHARED_LIBRARIES android-arm64) missing libloc_pla (SHARED_LIBRARIES android-arm64)
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.
vendor/qcom/opensource/location/loc_api/ds_api/Android.mk: error: libloc_ds_api (SHARED_LIBRARIES android-arm) missing libloc_pla (SHARED_LIBRARIES android-arm)
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.
vendor/qcom/opensource/location/loc_api/loc_api_v02/Android.mk: error: libloc_api_v02 (SHARED_LIBRARIES android-arm64) missing libloc_pla (SHARED_LIBRARIES android-arm64)
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.
vendor/qcom/opensource/location/loc_api/loc_api_v02/Android.mk: error: libloc_api_v02 (SHARED_LIBRARIES android-arm) missing libloc_pla (SHARED_LIBRARIES android-arm)
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.
build/make/core/main.mk:833: error: exiting from previous errors.
Click to expand...
Click to collapse
If I set ALLOW_MISSING_DEPENDENCIES=true I don't get much further:
[1/1] out/soong/.bootstrap/bin/soong_build out/soong/build.ninja
Environment variable ALLOW_MISSING_DEPENDENCIES was modified (false => true), regenerating...
No need to regenerate ninja file
ninja: error: 'kernel/sony/msm-4.9/common-kernel/kernel-dtb-kugo', needed by 'out/target/product/kugo/kernel', missing and no known rule to make it
23:43:22 ninja failed with: exit status 1
#### failed to build some targets (28 seconds) ####
Click to expand...
Click to collapse
Did you also encounter these/could you give me a pointer how to complete the compilation successfully ? (I don't want to sound stereotypical, but I think it warrants mentioning I'm on Arch (maybe something's fukcy with my environment))
harryharryharry said:
Hi @nervousapp,
I'm attempting a build myself using the guide published by Sony recently, but I'm stuck at some errors:
If I set ALLOW_MISSING_DEPENDENCIES=true I don't get much further:
Did you also encounter these/could you give me a pointer how to complete the compilation successfully ? (I don't want to sound stereotypical, but I think it warrants mentioning I'm on Arch (maybe something's fukcy with my environment))
Click to expand...
Click to collapse
You have to get the file here https://github.com/sonyxperiadev/vendor-sony-kernel and put it in kernel/sony/msm-4.9/common-kernel/ and all will be fine.
You may experienced another error, see https://talk.sonymobile.com/t5/Android-9-x-Pie/Compilation-error/td-p/1339265
I have also experienced no boot with the aosp-eng but the userdebug boot like a charm ?
Thanks for the heads up! I am building userdebug now from a xubuntu livecd because I kept getting the libloc_pla dependency error. On the livecd I'm not getting the error. So probably some environment issue on Arch, if I find a solution I'll post it here for future google passersby.
harryharryharry said:
Thanks for the heads up! I am building userdebug now from a xubuntu livecd because I kept getting the libloc_pla dependency error. On the livecd I'm not getting the error. So probably some environment issue on Arch, if I find a solution I'll post it here for future google passersby.
Click to expand...
Click to collapse
Sorry for the noob question, but what dit you choose at the following step?
Code:
source build/envsetup.sh && lunch
And another question. Which version of Ubuntu did you use for the successfull build?
Thanks a lot!
I chose option: 64. aosp_f5321-userdebug
and the livecd I compiled with is: xubuntu 18.04.1
As nervousapp already mentioned, as of yet flashing (unofficial) 9.0 gapps is not possible as it will cause a boot hang.
harryharryharry said:
I chose option: 64. aosp_f5321-userdebug
and the livecd I compiled with is: xubuntu 18.04.1
As nervousapp already mentioned, as of yet flashing (unofficial) 9.0 gapps is not possible as it will cause a boot hang.
Click to expand...
Click to collapse
Thanks for your answear.
nervousapp said:
Hi everyone,
I just build successfully Android 9 Pie for the X compact from the Sony repo.
I have not test it yet but it boot.
If you want to try I can give you the files.
Click to expand...
Click to collapse
If you want someone to comment on your build then please upload it. I guess quite many can test it.
Small update: Sony updated their guide and manifests to android-9.0.0_r6 and opengapps officially released 9.0 gapps. So I attempted another pie build to see if meanwhile the 'gapps bootloop' issue was addressed. Sadly this is not yet the case.
harryharryharry said:
Small update: Sony updated their guide and manifests to android-9.0.0_r6 and opengapps officially released 9.0 gapps. So I attempted another pie build to see if meanwhile the 'gapps bootloop' issue was addressed. Sadly this is not yet the case.
Click to expand...
Click to collapse
I build a new one also but in my case it was stuck at sony logo instead of bootloop.
Did you build userdebug or eng ? Because eng hangs on boot still.
Nope. It was userdebug.
Today I built again. This time I removed kernel files completely from both 4.4 and 4.9 folders, and synced. Build was successful. At first boots it gives an error saying device failed verification or something like that and powers off. But next time boots up. Basic things seems like working. Camera works but Video recording doesn't. WiFi works. Fingerprint sensor doesn't work. Bigger problem is gapps also doesn't work . Twrp flashes it successfully but when it boots up you see Google apps is not actually there. I couldn't see any error messages in gapps log neither. I didn't test it extensively so there may be other problems but these are the ones noticed at first glance.
Same here with the verification issue on boot, @oshmoun already reported it as a bug:
https://github.com/sonyxperiadev/bug_tracker/issues/177
Meanwhile I've been able to build omnirom 9.0 with some minor compiling-hindrances. It boots and almost everything seems to be working quite neatly! A couple of issues I've encountered thus far:
- The wifi module bcmdhd needs some firmware files placed in the correct location (they're in the process of switching kernel modules from bcmdhd to brcmfmac.)
- The video recording crash issue @maluus described also occurs on omnirom 9.0.
- The screen won't go off (this can be circumvented by switching 'Display -> Advanced -> Ambient display -> Always on' off)
(- my pet peeve: 'volume rocker next/previous track control during screen off'-feature missing)
Main plus for me is gapps can be installed to omnirom 9.0. So I'll try to make it my daily driver, report me some bugs
Related
[ROM][EOL][7.1.2][OFFICIAL] LineageOS for T0LTE
{
"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"
}
Code:
/*
* 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.
*/
This rom has reached end-of-life state. There will be no new builds, updates or support for LineageOS 14.1 version.
If you still find this useful the last build was on 20190126 and you can find it in download section.
Working
Graphics
Wifi
Data
RIL
Bluetooth
GPS
Sensors
Vibration
Camera
NFC
Audio
Video Playback
Miracast
Not working/Bugs/Unknown
Data doesn't work until after first boot.
MHL/HDMI doesn't work
Bluetooth audio (may or may not work for you)
MTP crashes when uninstalling an app
LED flashlight doesn't work on SC-02E
Installation
Read the FAQ to familiarize yourself with any issues that may come up
Make sure you are using the latest TWRP version.
Download the latest build and google apps
Copy it to the phone
Factory reset in TWRP (Very important! Do not skip)
Flash LineageOS 14.1
Flash Gapps
Optional: Flash root package
Reboot
Be patient. The first boot will take between 5 - 15 minutes.
Set up everything and reboot again to get radio working
See the FAQ to avoid common issues
Supported Variants
t0lte
GT-N7105/N7105T
SGH-i317/i317M
SGH-T889/T889V
SHV-E250S/E250K/E250L
SC-02E (SGH-N025)
Download
ROM: https://www.androidfilehost.com/?fid=1395089523397906488
TWRP: https://www.androidfilehost.com/?w=files&flid=173497
Gapps: http://opengapps.org
Root: https://download.lineageos.org/extras or Magisk
Changelog
For official builds: cmxlog.com or lineageoslog.com
Below are the changelogs for unofficial builds:
3/18/2017
Moved smdk4x12 RIL class upstream to smdk4412-qcom-common
03/10/2017
Enabled wakelock for flashlight (prevents flashlight from turning off when screen is turned off)
03/07/2017
Updated SELinux for tethering
Enabled RPFILTER for tethering
Remapped menu button to app switcher
03/06/2017
Fix Bluetooth
Better CDMA support
Removed unnecessary RIL shim
03/05/2017
Note: These are the differences from the last official build, not experimental builds.
SELinux now enforcing (policies completely rewritten)
Fixed data issues
Fixed sensors issues
Fix sdcard (internal and external) writing issues
Switched to open source RIL
Enabled ambient display
02/20/2017
Synced with upstream
SELinux updates
Fixed sensors
16.02.2017
Synced with upstream
SELinux updates
RAF bringup and update
Patched radio libs to fix audio
01/14/2017
Initial build
XDA:DevDB Information
[ROM][EOL][7.1.2][OFFICIAL] LineageOS for T0LTE, ROM for the Samsung Galaxy Note II
Contributors
Option58, PoisonNinja, LineageOS team
Source Code: https://github.com/LineageOS/android_device_samsung_t0lte
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
Version Information
Status: Nightly
Created 2017-12-13
Last Updated 2019-07-24
FAQ:
Root
LineageOS removed builtin root, so you need to flash the root package linked above.
Data doesn't work
Reboot. Data doesn't work on the first try
Can't send MMS messages
Reboot. Then, make sure your APN settings are correct.
Dialer not responding during calls/calls not launching dialer
Credits to @paulq75
Settings -> Apps -> tap the cog icons up to the right -> and the set the default Phone app.
A lot of apps force close on system start
Usually happens when switching to/from TouchWiz roms. Solution would be to backup your data to PC and format internal storage. Sometimes even multiple times.
SDCard access denied in app even though I click 'allow'
Known bug. Happens only on first attempt. Solution would be to close the app, remove from recents and start again.
Rom fails to flash or OTA doesn't work
Make sure you are using the latest TWRP version from this thread.
I have some other issue!
See Reporting Bugs below
Reporting Bugs
When reporting an issue, please provide the following information:
Device (N7105, i317, 889, etc.)
Build Date
Logcat when the issue occurs (http://forum.xda-developers.com/showthread.php?t=1726238)
If it's a random reboot, also provide the following information:
Kernel logs. Run "adb shell su -c cat /proc/last_kmsg > /sdcard/Download/kernel.txt" and grab kernel.txt from the Download folder on your phone
Building LineageOS
Follow the instructions at https://source.android.com/source/initializing.html and https://source.android.com/source/downloading.html.
When you get to repo init, use the url https://github.com/LineageOS/android.git -b cm-14.1
repo sync
Edit roomservice.xml in .repo/local_manifests/ and edit it so it looks like this
repo sync
. build/envsetup.sh
brunch t0lte
OH SNAP!!
Wow. You're Comeback! I will try.
Here we go !
Looks like gapps link is down ATM.
Thank you for this new build !
Sent from my SGH-I317 using XDA-Developers Legacy app
Thanks for the new toy to play with bro. Rom boots, takes forever but none the less it boots into the os (so give it a few) which runs like butter. Unfortunately data doesn't connect at all just stays saying connecting. Looking forward to future updates for this bad boy...
Nice to see you come back to this device :good: Too late to mess with it tonight, but I'll flash in the A.M.
I was just trying to build this myself today, but kept getting errors during the build. New to building CM/Lineage, but I'll keep plugging away. Glad to see it's possible to get it to work. I still have hope lol
thanks so much!
Sent from my E6653 using Tapatalk
Is this marked as "unofficial" because it is self build from the LineageOS Sources or are there changes to the sourcecode? And if so what are they?
Will give this one a go once i'm home.
Wowwww thanks Dev.
dzee206 said:
Thanks for the new toy to play with bro. Rom boots, takes forever but none the less it boots into the os (so give it a few) which runs like butter. Unfortunately data doesn't connect at all just stays saying connecting. Looking forward to future updates for this bad boy...
Click to expand...
Click to collapse
Can you at least make and receive calls and texts?
kozmo21 said:
Nice to see you come back to this device :good: Too late to mess with it tonight, but I'll flash in the A.M.
I was just trying to build this myself today, but kept getting errors during the build. New to building CM/Lineage, but I'll keep plugging away. Glad to see it's possible to get it to work. I still have hope lol
Click to expand...
Click to collapse
Sync the sources and try again, as I've upstreamed a bunch of build fixes. Also, cherry-pick https://review.lineageos.org/#/c/156547/, as that fixes the SELinux build errors. Finally, you'll probably want to add androidboot.selinux=permissive to CONFIG_CMDLINE in arch/arm/configs/cyanogenmod_t0lte_defconfig, because otherwise it won't boot with SELinux enforcing.
peterhugelberg said:
Is this marked as "unofficial" because it is self build from the LineageOS Sources or are there changes to the sourcecode? And if so what are they?
Will give this one a go once i'm home.
Click to expand...
Click to collapse
This is unofficial because it is self built, although the code is directly from upstream. I've been commiting patches the past few days to get t0lte to build, which you can see at https://review.lineageos.org/#/q/project:LineageOS/android_device_samsung_t0lte. The only other change that I haven't uploaded to Gerrit is setting SELinux to permissive (because LineageOS developers don't allow SELinux to be set to permissive on official builds)
PoisonNinja said:
Can you at least make and receive calls and texts?
Click to expand...
Click to collapse
No I wasn't able to. I'll try again later on.
PoisonNinja said:
Can you at least make and receive calls and texts?
Sync the sources and try again, as I've upstreamed a bunch of build fixes. Also, cherry-pick https://review.lineageos.org/#/c/156547/, as that fixes the SELinux build errors. Finally, you'll probably want to add androidboot.selinux=permissive to CONFIG_CMDLINE in arch/arm/configs/cyanogenmod_t0lte_defconfig, because otherwise it won't boot with SELinux enforcing.
This is unofficial because it is self built, although the code is directly from upstream. I've been commiting patches the past few days to get t0lte to build, which you can see at https://review.lineageos.org/#/q/project:LineageOS/android_device_samsung_t0lte. The only other change that I haven't uploaded to Gerrit is setting SELinux to permissive (because LineageOS developers don't allow SELinux to be set to permissive on official builds)
Click to expand...
Click to collapse
Little feedback:
I can make receive calls, but no sound
Data doesn't work for me either
GPS does work on even on "device only"
Video works on YouTube
MTP error with stock file manager, no problem with 3rd party ones
I don't have arch/arm/configs/cyanogenmod_t0lte_defconfig, In mine it's arch/arm/configs/lineageos_t0lte_defconfig, I don't have any cyanogen anything there... but I'll change it there. Actually, think that was the error I had an hour into the build. It had something to do with libselinux, then... ninja: build stopped: subcommand failed. Hope that fixes it and I can build :fingers-crossed:
Thanks for the tip :good:
I can call. But no sound sending and receiving call.
Data connection is not established.
Same here... No data and no calls.
kozmo21 said:
Little feedback:
I can make receive calls, but no sound
Data doesn't work for me either
GPS does work on even on "device only"
Video works on YouTube
MTP error with stock file manager, no problem with 3rd party ones
I don't have arch/arm/configs/cyanogenmod_t0lte_defconfig, In mine it's arch/arm/configs/lineageos_t0lte_defconfig, I don't have any cyanogen anything there... but I'll change it there. Actually, think that was the error I had an hour into the build. It had something to do with libselinux, then... ninja: build stopped: subcommand failed. Hope that fixes it and I can build :fingers-crossed:
Thanks for the tip :good:
Click to expand...
Click to collapse
Whoops, you're right. I mean lineageos_t0lte_defconfig. Don't forget to cherry-pick the commit I linked earlier, which should fix the libselinux error.
Jetiman said:
I can call. But no sound sending and receiving call.
Data connection is not established.
Click to expand...
Click to collapse
prbs1982 said:
Same here... No data and no calls.
Click to expand...
Click to collapse
Have you checked the mute settings? Try toggling it.
PoisonNinja said:
Have you checked the mute settings? Try toggling it.
Click to expand...
Click to collapse
Yes, Speaker on-off / mic on-off, does not change anything. No speech outgoing and reaching.
It appears that i9305 has the same radio hardware as the N7105. Roberto Gibellini has been doing a lot of work, I'll see if I can port some of the stuff over.
This reminds of the early CM13 days, when we had to use a chroot to get the radio to work
PoisonNinja said:
It appears that i9305 has the same radio hardware as the N7105. Roberto Gibellini has been doing a lot of work, I'll see if I can port some of the stuff over.
This reminds of the early CM13 days, when we had to use a chroot to get the radio to work
Click to expand...
Click to collapse
thanks for the hard work, we all owning a n7105 thank you :good:
I'm so sorry about this thread.
Today, I tried to build this rom from source but I faced with a lot of problem because no dev do this rom so I try to it by myself.
Here is there steps I did:
download source code with repo.
- Prepare kernel: I use some guide in AOSP to build this kernel.
- Repair software binaries: Im just download it from Xperia dev.
the first big thing I got is when I use command breafast to build, I didn't not find anything about my device althought I create some folder and place the material on this as same as the guide in AOSP.
So can someone help me rewrite these code to make it work ?
max26292 said:
I'm so sorry about this thread.
Today, I tried to build this rom from source but I faced with a lot of problem because no dev do this rom so I try to it by myself.
Here is there steps I did:
download source code with repo.
- Prepare kernel: I use some guide in AOSP to build this kernel.
- Repair software binaries: Im just download it from Xperia dev.
the first big thing I got is when I use command breafast to build, I didn't not find anything about my device althought I create some folder and place the material on this as same as the guide in AOSP.
So can someone help me rewrite these code to make it work ?
Click to expand...
Click to collapse
You can use OmniROM as a source. Re-writing the sources to compile should not be a big thing. Can you share your sources?
eagleeyetom said:
You can use OmniROM as a source. Re-writing the sources to compile should not be a big thing. Can you share your sources?
Click to expand...
Click to collapse
first i Follow this guide: https://wiki.lineageos.org/devices/nicki/build
and change these thing on this step with something under this line: Prepare the device-specific code
after that I use this guide to build suzu kernel: https://developer.sonymobile.com/op.../#how-to-automatically-build-the-linux-kernel
And I download binaries from source: https://developer.sonymobile.com/op.../#how-to-automatically-build-the-linux-kernel
and I store these thing on google cloud engine, so how to share it to you?
max26292 said:
first i Follow this guide: https://wiki.lineageos.org/devices/nicki/build
and change these thing on this step with something under this line: Prepare the device-specific code
after that I use this guide to build suzu kernel: https://developer.sonymobile.com/op.../#how-to-automatically-build-the-linux-kernel
And I download binaries from source: https://developer.sonymobile.com/op.../#how-to-automatically-build-the-linux-kernel
and I store these thing on google cloud engine, so how to share it to you?
Click to expand...
Click to collapse
I recommend Github
eagleeyetom said:
I recommend Github
Click to expand...
Click to collapse
I read that limit bandwidth is 1gb per month and storage is 5gb, isn't it?
I didn't rewrite any code, just build everything from the source
https://github.com/max26292/lineageos_suzu
Hold on. I'm planning to start working on a custom ROM after fixing the encryption in TWRP. Github has almost unlimited storage, so you shouldn't be worried. You need to fork the OmniROM tree for suzu and loire-common and adapt it to work with LOS.
eagleeyetom said:
Hold on. I'm planning to start working on a custom ROM after fixing the encryption in TWRP. Github has almost unlimited storage, so you shouldn't be worried. You need to fork the OmniROM tree for suzu and loire-common and adapt it to work with LOS.
Click to expand...
Click to collapse
ok i will try :3 I read some guide but It didn't give me enough knowledge to build
eagleeyetom said:
Hold on. I'm planning to start working on a custom ROM after fixing the encryption in TWRP. Github has almost unlimited storage, so you shouldn't be worried. You need to fork the OmniROM tree for suzu and loire-common and adapt it to work with LOS.
Click to expand...
Click to collapse
I'm waiting for great News about your custom rom Projekt, Are there progresses?
rec0re said:
I'm waiting for great News about your custom rom Projekt, Are there progresses?
Click to expand...
Click to collapse
Not yet. I need to sort out my health issues first.
Have you any news about LineageOS for Xperia X?
At this time, no develop build this rom for our device
Maybe had better to wait Android O with vendor layer and LOS 15, will be much easier to update.
@eagleeyetom
As I wanted to get into android rom development/building, I started today syncing the LOS source an forking the omnirom device tree for suzu and loire-common and adapted already some stuff a little bit.
But you probably know more than me about this, so when forking the device tree, loire-commen, etc... for suzu from omnirom, there are these omni.dependencies files, I somehow don't have a plan what to do with those.
Do they need some adapting too or something else?
I would be very grateful if you could point me into the right direction what do with them.
Greetings.
SahilCrazy said:
@eagleeyetom
As I wanted to get into android rom development/building, I started today syncing the LOS source an forking the omnirom device tree for suzu and loire-common and adapted already some stuff a little bit.
But you probably know more than me about this, so when forking the device tree, loire-commen, etc... for suzu from omnirom, there are these omni.dependencies files, I somehow don't have a plan what to do with those.
Do they need some adapting too or something else?
I would be very grateful if you could point me into the right direction what do with them.
Greetings.
Click to expand...
Click to collapse
You need to clone all the repos mentioned in that file. If you are porting LOS, just leave it blank until it gets official.
eagleeyetom said:
You need to clone all the repos mentioned in that file. If you are porting LOS, just leave it blank until it gets official.
Click to expand...
Click to collapse
Yeah I cloned them all and created a manifest where I included them all to sync them all with "repo sync" and to place them in the correct folders etc.
But it looks like theres something wrong with the sepolicy in loire-common:
Code:
device/sony/loire-common/sepolicy/device.te:4:ERROR 'duplicate declaration of type/attribute' at token ';' on line 39737:
type trim_area_partition_device, dev_type;
type persist_block_device, dev_type;
checkpolicy: error(s) encountered while parsing configuration
/root/android/system/out/host/linux-x86/bin/checkpolicy: loading policy configuration from /root/android/system/out/target/product/suzu/obj/ETC/sepolicy_intermediates/policy.conf
[ 28% 16734/57899] Import includes file: /root/android/system/out/target/product/suzu/obj/EXECUTABLES/init_intermediates/import_includes
ninja: build stopped: subcommand failed.
make: *** [ninja_wrapper] Error 1
This happens later also with init.te and tad.te, not only device.te. I tried commenting those lines out but this resulted in an error saying that theres no type declaration.
SahilCrazy said:
Yeah I cloned them all and created a manifest where I included them all to sync them all with "repo sync" and to place them in the correct folders etc.
But it looks like theres something wrong with the sepolicy in loire-common:
Code:
device/sony/loire-common/sepolicy/device.te:4:ERROR 'duplicate declaration of type/attribute' at token ';' on line 39737:
type trim_area_partition_device, dev_type;
type persist_block_device, dev_type;
checkpolicy: error(s) encountered while parsing configuration
/root/android/system/out/host/linux-x86/bin/checkpolicy: loading policy configuration from /root/android/system/out/target/product/suzu/obj/ETC/sepolicy_intermediates/policy.conf
[ 28% 16734/57899] Import includes file: /root/android/system/out/target/product/suzu/obj/EXECUTABLES/init_intermediates/import_includes
ninja: build stopped: subcommand failed.
make: *** [ninja_wrapper] Error 1
This happens later also with init.te and tad.te, not only device.te. I tried commenting those lines out but this resulted in an error saying that theres no type declaration.
Click to expand...
Click to collapse
You can try to build permissive first and try to fix sepolicy later.
eagleeyetom said:
Yeah I cloned them all and created a manifest where I included them all to sync them all with "repo sync" and to place them in the correct folders etc.
But it looks like theres something wrong with the sepolicy in loire-common:
You can try to build permissive first and try to fix sepolicy later.
Click to expand...
Click to collapse
Okey, how do you build permissive? There needs to be something done in the kernel/.../security/selinux/makefile or am I wrong?
SahilCrazy said:
Okey, how do you build permissive? There needs to be something done in the kernel/.../security/selinux/makefile or am I wrong?
Click to expand...
Click to collapse
Take this line as a reference: https://github.com/OrdenKrieger/android_device_zuk_ham/blob/cm-14.1/BoardConfig.mk#L51
eagleeyetom said:
Take this line as a reference: https://github.com/OrdenKrieger/android_device_zuk_ham/blob/cm-14.1/BoardConfig.mk#L51
Click to expand...
Click to collapse
So here's the first boot:
{
"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"
}
I switched the sources, I used now the repos from sonyxperiadev instead of omnirom as I kept getting the sepolicy errors even when I tried building permissive.
There are a few things that still need work, like the sim is not recognized etc.
Will release it here on xda when most of stuff is working fine.
Thanks for your great help!:good:
SahilCrazy said:
So here's the first boot:
I switched the sources, I used now the repos from sonyxperiadev instead of omnirom as I kept getting the sepolicy errors even when I tried building permissive.
There are a few things that still need work, like the sim is not recognized etc.
Will release it here on xda when most of stuff is working fine.
Thanks for your great help!:good:
Click to expand...
Click to collapse
Congratulations! I hope that you will make it stable soon
{
"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"
}
Background:
We've been offered LOS 16 GSIs in the past (here, and here), but they haven't been updated in quite a while, so as a LineageOS lover, I decided to step up and do it myself. Turns out it wasn't so easy - there were a number of hurdles that prevented it from building properly, booting or being feature-complete. But here I am, having figured out most if not all what's needed, and verified booting on an arm64 ab device I own, I'm ready to share my findings as well as some builds with you.
Disclaimer:
This is still mostly a LineageOS team / PHH @phhusson effort, credits to them and all associated for making all this possible.
No instructions will be offered. If you're here in this forum, you should know what you're doing.
No guarantees that everything would work. This is a GSI, bugs are bound to happen.
Do not report hardware-related bugs in this thread. I am selfish and only care about getting it running on my device with whatever features I need working. Plus I'm not PHH and can't solve any either.
Download:
https://sourceforge.net/projects/andyyan-gsi/files/
Compressed as .xz archives - extract first.
Vanilla except for these changes:
Modifications needed to make it build/boot/feature-complete, see below
Disabled "vendor mismatch" warning on boot
Re-enabled lockscreen shortcuts
Default stretch-to-fullscreen (force apps to render in 18:9)
Extra tip:
If you have a relatively low-end device and experience UI stutters, try this simple build.prop trick (technically a debug property, so use at your own risk). Thanks @SnapTheRipper for bringing it up!
Modifications needed (builders-only):
Now for the juicy part. On top of PHH's already fantastic build script, you'll need these:
device/phh/treble:
Revert Update lineage.mk for LineageOS 16.0 - add back LOS sepolicy, so that LOS-specific features like Profiles, LiveDisplay, Styles, Trust would work
Revert exfat fsck/mkfs selinux label - fix a conflict in doing so
build/make:
Revert Enable dyanmic image size for GSI - fix building
external/tinycompress:
Revert tinycompress: Use generated kernel headers - remove dependency on generated kernel headers
frameworks/base:
Revert Initial support for in-display fingerprint sensors - use PHH's implementation
vendor/lineage:
Apply build/soong/Android.bp: Disable generated_kernel_* - disable generating kernel headers, since GSIs don't have a kernel
Revert lineage: Enforce privapp-permissions whitelist, or change it to log
vendor/qcom/opensource/cryptfs_hw:
Revert cryptfs_hw: Use generated kernel headers - remove dependency on generated kernel headers
Apply [TEMP]: Header hack to compile for 8974 - fix a missing header
And that's it. Doesn't look like much, but most are pretty hacky solutions, and I don't expect them to be merged anywhere. As I said, I'm only interested in getting it running, I don't care what it takes.
Stuff on GitHub (builders-only):
I've also collected necessary scripts/patches and uploaded them: treble_build_los, treble_patches (PHH's treble_patches adjusted for LOS). Not the cleanest code, but should help if you still need more clues.
Donate?
https://paypal.me/AndyCGYan
Thanks for reading - I hope this could be of use to fellow LineageOS lovers / home builders.
Is there any chance for A-only 64 build?
Lecterr said:
Is there any chance for A-only 64 build?
Click to expand...
Click to collapse
I hope will be for A-only too.. many people would welcome it . :silly:
Lecterr said:
Is there any chance for A-only 64 build?
Click to expand...
Click to collapse
Dejvid50 said:
I hope will be for A-only too.. many people would welcome it . :silly:
Click to expand...
Click to collapse
Done, check OP. I can't spare an A-only device to test it though, try at your own risk.
EDIT: might have to wait for SF to mirror the file...
AndyYan said:
Done, check OP. I can't spare an A-only device to test it though, try at your own risk.
EDIT: might have to wait for SF to mirror the file...
Click to expand...
Click to collapse
Thank you very much!!! Will test and give feedback....ist it build on latest Phhs V111?
Cool, which one is the a-only? ...it's not clearly writen
odysseus84 said:
Cool, which one is the a-only? ...it's not clearly writen
Click to expand...
Click to collapse
I thought it's the avN one. (Didn't boot on my phone.)
As of now I've received 1 report of A-only booting up alright. Although I don't take hardware-related bug reports, it's advised to post whether it boots on your device so as to let other users know.
Lecterr said:
Thank you very much!!! Will test and give feedback....ist it build on latest Phhs V111?
Click to expand...
Click to collapse
Not sure how I could determine that, but it's fresh synced.
odysseus84 said:
Cool, which one is the a-only? ...it's not clearly writen
Click to expand...
Click to collapse
avN, bvN - not clear enough?
Thanks again for A-only build...tested and works great on MiMax3 with stock PIE vendor!!!
Only thing not working is equalizer for audio, opens a empty screen but no FC or error message...but ringtone, music etc. working.
Just tested this on a Nokia 7 Plus (B2N) with the bvN images. Everything seems to work just fine, except for VoLTE/VoWiFi (which I don't care that much about anyways...).
Voice calls, Camera, MusicFX, Fingerprint, Bluetooth, LTE, all work as expected. Will come back after some usage with more info about battery life and such.
@AndyYan Awesome stuff, Andy! Thank you for this guide--will try to build it myself soon enough after I run your build for a few days to test.
By the way, do you think this will get OTA updates from LineageOS? The updater seems to work as expected, but haven't seen any new options there yet.
Thanks again!
MadalinC said:
By the way, do you think this will get OTA updates from LineageOS? The updater seems to work as expected, but haven't seen any new options there yet.
Click to expand...
Click to collapse
Nope, LOS team even stated explicitly they won't be making any official GSIs.
AndyYan said:
Nope, LOS team even stated explicitly they won't be making any official GSIs.
Click to expand...
Click to collapse
Oh, that is very unfortunate. It is running really smooth as a GSI
So that means that each security patch comes out, I will need to start from scratch and reflash the image? That would make it a bit a pain each month
Anyways, thanks for the quick reply!
On the Galaxy S9: I dirty flashed it over vanilla phh 111 to see if it boots. It did with the usual force close of course.
Then I wiped and reflashed. But stuck at the boot animation. The splash screen was there for a half century too... my guess is the ramdisk stoff from the kernel. there are some other Kernel version I will try those later.
MadalinC said:
So that means that each security patch comes out, I will need to start from scratch and reflash the image?
Click to expand...
Click to collapse
Just flash the image on top (along with whatever mods you're using), no wipe needed. It works like flashing ROMs on a regular A-only device.
AndyYan said:
Just flash the image on top (along with whatever mods you're using), no wipe needed. It works like flashing ROMs on a regular A-only device.
Click to expand...
Click to collapse
Any chance of arm-a LOS16 build?
AndyYan said:
Done, check OP. I can't spare an A-only device to test it though, try at your own risk.
EDIT: might have to wait for SF to mirror the file...
Click to expand...
Click to collapse
Now I'm busy, at night I will try to flash and will report. Thanks for your work
EDIT: Ok, so I was try to flash on Huawei P10 Lite with OpenGapps, and can't boot, no logo, just goes to recovery, that's all.. I was WIPE system, data, cache, dalvik cache
Lecterr said:
Thanks again for A-only build...tested and works great on MiMax3 with stock PIE vendor!!!
Only thing not working is equalizer for audio, opens a empty screen but no FC or error message...but ringtone, music etc. working.
Click to expand...
Click to collapse
do you mind sharing the instructions for flashing the gsi? im on the latest pie beta on my max3.
drxllxffxct said:
do you mind sharing the instructions for flashing the gsi? im on the latest pie beta on my max3.
Click to expand...
Click to collapse
Do u have TWRP recovery?
Finally there's a LOS 16 GSI! I have been looking to try to compile my own with phh build script.
Sorry which one should I use _avN or _bvN if I have an A Only Arm64 (Wayne).
I tried to flash the _avN and got stuck at the Mi logo.
Thank you very much to do the work.
Sent from my Mi MIX 2 using XDA Labs
Boots on Razer phone 1 but no wifi or data. Everything else seems to work. Thank you for the rom (no wifi or data razer phone problem).
{
"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"
}
Background:
This is a natural continuation/extension of the LineageOS 18.x GSIs I've been making since 2020.
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.
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. 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 Gerrit Code Review.
Click to expand...
Click to collapse
Disclaimer:
This is still mostly a LineageOS team / PHH @phhusson effort, credits to them and all associated for making all this possible.
No flashing instructions will be offered. If you're here in this forum, you should know what you're doing.
No guarantees that everything would work. This is a GSI, bugs are bound to happen.
Must-read:
You are STRONGLY ADVISED to try PHH's AOSP of equivalent version FIRST and identify/report issues there, before moving onto other GSIs that are based on his work, including this one.
If you do find bugs on this GSI and want to report, then you MUST try reproducing on AOSP, and ONLY proceed to report here when it's specific to this GSI. This filters out bugs common to all PHH-based GSIs, which you should let PHH know, not me. I might silently ignore your report if you skip this.
Download:
https://sourceforge.net/projects/andyyan-gsi/files/
Compressed as .xz archives - extract first.
Stuff on GitHub (builders-only):
Since builders' stuff aren't really interesting to end users, I decided not to separately document the modifications needed in this post; instead just check out these repos, where most things should be self-explanatory. Not the cleanest code, but should help if you need some clues.
lineage_build_unified - my unified script for building
lineage_patches_unified - my unified patches for building, including patches from PHH
sas-creator - generates VNDKLite and secure variants, can be used without a building environment
Donate?
https://paypal.me/AndyCGYan
Reserved
Notes:
I now have a rather taxing day job, and can't devote nearly as much time/effort into this as I did as a student.
GAPPS builds are offered as-is without guarantees. Read #10 for more.
/system is RO on regular builds and RW on VNDKLite builds. VNDKLite builds can be used on most non-VNDKLite devices as well.
ADB is intentionally insecure, even on first boot (turned on by default and no authentication needed). GSIs are more fragile compared to device-specific custom ROMs, both on first boot (no-boot issues) and on subsequent boots (after tuning certain Treble settings), and I insist that no-auth ADB is a must-have for debugging and general fail-safe.
Signature spoofing (MicroG) is supported, but only for priv-apps. This is a security consideration from PHH.
Magisk support should be on par with A11 (thanks @eremitein). The "abnormal state / unsupported SU" warning can be ignored. For devices that still don't play well with Magisk (e.g. kernel restrictions implemented by OEM), use PHH-SU instead. Install the app and you'll get root for apps.
Initial builds are based on PHH v400.c and November security patches.
Sigh, I don't really want to make a thread this early...
BTW, 32-bit and A-only users, you should really move on.
Big work thank You
Hey How to flash this Gsi Guys can someone answer me????
Thank you so much. Are gapps included ?
walid77dz said:
Thank you so much. Are gapps included ?
Click to expand...
Click to collapse
From an earlier post...
AndyYan said:
32*/A32* users, I'm not stopping your monthly builds just yet, but 32-bit is getting phased out, and you should upgrade soon. Similar goes for A-only. Ideally in the future we'll only have 64B, making room for other much needed variants such as GAPPS.
Click to expand...
Click to collapse
Their deprecation does seem likely now, so I'll try a GAPPS build or two when I have time.
Do you consider this alpha usable as daily driver?
And, does it require clean installation from LOS 18 GSI?
Avraham Tsaban said:
Do you consider this alpha usable as daily driver?
And, does it require clean installation from LOS 18 GSI?
Click to expand...
Click to collapse
I am using it as my daily driver - I enabled Gallery and LiveDisplay for just that purpose.
Out of curiosity I did try a dirty install from 18.1. It booted and most apps work, to my surprise, but Messaging won't allow me to select contacts properly no matter what, and that was a blocker, so don't.
People who love LOS, insist on using GAPPS with it, and had been asking me for such builds all this time - I now have a lil something for you, a test LOS19 build with GAPPS built-in. It's intentionally in the "personal" flavor to discourage use as your daily driver, but also shared-blocks (unlike previous "personal" builds) to save some space.
It was more trivial to build than I thought, but that doesn't mean I'll build it alongside vanilla yet...
Every variant takes disk space and build time
The image itself is huge and won't fit in even slightly older devices
Too many archs/variants confuse users
I cannot make any guarantees about it
I've seldom mentioned the last point, yet it's critical - I'm in China and I don't use GAPPS at all, so I have little idea about what counts as "properly working" for GAPPS and how to troubleshoot them. Even if I do eventually build with GAPPS, I can only provide builds as-is, and you'll have to help each other out on GAPPS-related/-induced issues. At the end of the day, I still recommend using other ROMs that are built around GAPPS, e.g. @ponces ' PE, for a more cohesive experience and better support.
For now, all I know is this test build logs in (after registering the device here), can open Play Store and download apps, nothing beyond that.
Huawei P20L mobile data doesn't work
confirmed working on huawei mediapad m5 (cmr-w09 model name)
thx so much AndyYan
first degoogled android 12
su working via phh su app - magisk wasn't working proper
I do the installation through fastboot, because I don't have twrp, The installation is successful, but when I start to start the installation it gives an error: Invalid sparse file format at header magic, and after that it installs normally, but when I start the system, it gets stuck in the logo of the manufacturer of my device, Any solution?
Flashed this ROM on my Oneplus 9 Pro and was surprised how great and smooth it is.
I read on a thread how to fix fingerprint issue on GSI ROM by editing /vendor/build.prop, tried it and ended up in bootloop and I have to start all over.
What's the right way to do this?
Thanks in advance.
Geoz said:
fix fingerprint issue on GSI ROM
Click to expand...
Click to collapse
You don't - no A12 GSIs support UDFPS yet.
AndyYan said:
You don't - no A12 GSIs support UDFPS yet.
Click to expand...
Click to collapse
Good to know. I appreciate you taking the time to explain this.
Thanks.
Geoz said:
Good to know. I appreciate you taking the time to explain this.
Thanks.
Click to expand...
Click to collapse
BTW, I believe most OPlus devices have read-only vendor, so even in the future you probably shouldn't head down that road.
AndyYan said:
BTW, I believe most OPlus devices have read-only vendor, so even in the future you probably shouldn't head down that road.
Click to expand...
Click to collapse
What of if I use Lineage OS as the base?
Thanks again.
Geoz said:
What of if I use Lineage OS as the base?
Thanks again.
Click to expand...
Click to collapse
That depends on your maintainer (LuK), and also PHH only deals with issues with stock vendors.
Speaking of which, looks like someone else also can't wait for LuK's 19.0, hehe...
AndyYan said:
That depends on your maintainer (LuK), and also PHH only deals with issues with stock vendors.
Speaking of which, looks like someone else also can't wait for LuK's 19.0, hehe...
Click to expand...
Click to collapse
First time on GSI ROM but I'm really impressed. I've learned a lot from you in a very short time. All information I read on the internet is not valid rather from a developer like you.
I appreciate you.
{
"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 12 (S), 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. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.
GPL compliance:
Device tree source code: LineageOS/android_device_motorola_harpia
Kernel source code: LineageOS/android_kernel_motorola_msm8916
Working:
Camera (and flashlight)
WiFi
Battery LED
Bluetooth
Telephony (Calls) & Data
Audio (Record and Playback)
Video Playback
Sensors
GPS
VoLTE
Bugs:
Encryption
SELinux enforcing
UI is laggy
Nothing (?)
Downloads:
Rom
Gapps
Notice:
No custom kernels are supported in this thread. Only stock kernel and official builds will be supported. No bug reports if that's not the case.
Installation:
Reboot to recovery
Format /system, /data and /cache
Install LineageOS zip package
Important notes:
* Required * firmware version must be based on Nougat
GApps can only be flashed on clean installs.
Formatting data (all user data is wiped, including internal storage) is a must if Stockrom was previously installed and device was encrypted.
Credits & collaborations:
All LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
DONATIONS : Paypal
Contributors
althafvly, chil360, squid2, jeferson1979, Alberto97
Source Code: https://github.com/MOTO-M8916
Reserved
On my device (XT 1602) I do not face any lag in UI. will you fix the other problems like mobile data? Great work BTW.
Just curious, where are you getting the vendor blobs to build this? I'm trying to build from the source, but when I try to build, I get:
Code:
In file included from build/make/core/envsetup.mk:312:
vendor/lineage/config/telephony.mk:20: error: _nic.PRODUCTS.[[device/motorola/harpia/lineage_harpia.mk]]: "vendor/motorola/msm8916-common/msm8916-common-vendor.mk" does not exist.
14:32:49 dumpvars failed with: exit status 1
In file included from build/make/core/config.mk:313:
In file included from build/make/core/envsetup.mk:312:
vendor/lineage/config/telephony.mk:20: error: _nic.PRODUCTS.[[device/motorola/harpia/lineage_harpia.mk]]: "vendor/motorola/msm8916-common/msm8916-common-vendor.mk" does not exist.
14:32:50 dumpvars failed with: exit status 1
** Don't have a product spec for: 'lineage_harpia'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
I also am unable to find a repo for proprietary_motorola_msm8916-common anywhere either.
my god I can't believe that today 02/17/2022 my harpia is running android 12 (S) I swear to God that today I was looking at the forum and I found this I was speechless just today I had done a review of Lineage OS (11) sincerely, you deserve a lot of recognition for continuing to do this and continue to maintain a cell phone that is years old, it is my daily phone now that I found out about this, I did not sit idly by and flash it, I congratulate you, it is a rom very stable and fast, I want to comment on something and it is that with android 11 it took me 2 minutes to start the launcher, here it only takes me 17-18 seconds to start the system I can tell you that this system can become the most stable and quickly for this mobile I will continue waiting for more updates of this version of android and thank you very much for allowing me to continue using my cell phone I have had the opportunity to obtain high-end cell phones but I love my harpia and as a friend told me If something works well for you, don't change it for anything. thankful to all the maintainers who work hard to get updates out.
I want to say that I have only had a small mistake and it is that when I lower the notification bar the cell phone becomes very slow and it takes a few seconds to lower it, I hope they correct the rest, it is perfectly fine, thank you very much! for everything soon a review for this rom so that more people see and appreciate your work.
Booting and installing the image works like a charm and pretty easy.
I tried different GApps but none of them did install. They fail with
Code:
“! Unable to find installation layout. Aboriting...” ?
as shown
in FAQ Point 25 for BiTGApps https://github-wiki-see.page/m/BiTGApps/BiTGApps/wiki/Frequently-Asked-Questions-(FAQ)
w/a does not work. I tried arm (not arm64).
Tested one arm64 NikGApps, this one did install but as expected did not show up.
Can anyone recommend gapps for arm and LOS 19.0?
Thanks
Christian
On my device (XT 1602) I do not face any lag in UI. will you fix the other problems like mobile data? Great work BTW.
visit :
Daftar situs judi slot online terbaik dengan permainan judi online terlengkap dapat dimainkan di MGO303 yang terpercaya sebagai agen slot gacor terbaik
chi70 said:
Booting and installing the image works like a charm and pretty easy.
I tried different GApps but none of them did install. They fail with
Code:
“! Unable to find installation layout. Aboriting...” ?
as shown
in FAQ Point 25 for BiTGApps https://github-wiki-see.page/m/BiTGApps/BiTGApps/wiki/Frequently-Asked-Questions-(FAQ)
w/a does not work. I tried arm (not arm64).
Tested one arm64 NikGApps, this one did install but as expected did not show up.
Can anyone recommend gapps for arm and LOS 19.0?
Thanks
Christian
Click to expand...
Click to collapse
I used BiTGapps but not with Lineage recovery. I was able to install with the latest version of TWRP.
Indiawallah71 said:
I used BiTGapps but not with Lineage recovery. I was able to install with the latest version of TWRP.
Click to expand...
Click to collapse
:+1 That's it.
Now my nearly oldest HW runs the newest Android Version.
So far no lag at all, it feels really fast
Camera does work, but inside Apps like QRCOde scanner nothing is shown so far.
Christian
I was very happy to see that someone made android 12 run on harpia, great job by the way.
I had the problems of ui lag and mobile data but nothing that bothers me, I hope you bring more updates
Will it come officially one day?
Updated to 12L (check OP for links)
althafvly said:
Updated to 12L (check OP for links)
Click to expand...
Click to collapse
is monet already working in this version?
I just installed this ROM twice on my harpy, first impression I found quite fluid even for this model. Then when lowering the notification bar the system would slow down too slow and bug, then give interface error dai or the screen would go dark and erase, after that it gave bootloop. Despite this it seems to be a good ROM hopefully improve this so I can use. Monet's not working.
althafvly said:
Updated to 12L (check OP for links)
Click to expand...
Click to collapse
Hello dear @althafvly. First of all, thank you very much for this awesome ROM based on Android 12L (LineageOS 19.1).
It's very stable, fast and battery-friendly. Please dear friend, continue improving this ROM. I really hope the Encryption, SELinux enforcing and UI Lag can be fixed.
One week ago, I had AICP ROM (Android 11) ( @jeferson1979 ), and It is a very stable ROM, but it has two big problems: It's kinda slow and everytime I try to install an weekly update, the whole system is damaged. I really don't know why this happen. I only boot to Recovery and flash the updated ROM, after that I cannot boot.
Tired of that, I tried this Android 12 ROM and wow it's amazing.
Please althafvly, can you add the Security Features that Disable the Quick Settings (Notification Bar) and Disable the Power Menu from Lockscreen???
Thanks again both developers.
Wait....
Testing on my XT1607. I'm getting "System UI isn't responding" once the pulldown menu finally loads (very laggy). One idea is this could be happening whenever the camera & flashlight options aren't working? When the camera and flashlight started working after a few reboots, the pulldown menu stopped being laggy.
The ability to connect to a Wi-Fi hidden SSID has now become fully broken in harpia with 19.1. For some reason, the initial setup wizard *can* connect to a hidden SSID, but, after that, if you ever disconnect from it, you can't connect to it ever again, nor can you ever add it fresh and connect to it. This is further deterioration of the following bug: https://gitlab.com/LineageOS/issues/android/-/issues/2678
Btw, I was able to get data and SMS to work, but not calling, for whatever reason.
mmortal03 said:
Testing on my XT1607. I'm getting "System UI isn't responding" once the pulldown menu finally loads (very laggy). One idea is this could be happening whenever the camera & flashlight options aren't working? When the camera and flashlight started working after a few reboots, the pulldown menu stopped being laggy.
The ability to connect to a Wi-Fi hidden SSID has now become fully broken in harpia with 19.1. For some reason, the initial setup wizard *can* connect to a hidden SSID, but, after that, if you ever disconnect from it, you can't connect to it ever again, nor can you ever add it fresh and connect to it. This is further deterioration of the following bug: https://gitlab.com/LineageOS/issues/android/-/issues/2678
Btw, I was able to get data and SMS to work, but not calling, for whatever reason.
Click to expand...
Click to collapse
the same thing happened to me "System UI isn't responding" once the pulldown menu finally loads (very laggy)." and after that it goes into bootloop. It looks like a good rom, but maybe the ram consumption will be less than the other rons ? | Which rom do you think has the lowest ram usage/light for the moto g4 play ?
Victoraguiart said:
Which rom do you think has the lowest ram usage/light for the moto g4 play ?
Click to expand...
Click to collapse
Good question. Unfortunately, I haven't done that test.
mmortal03 said:
Good question. Unfortunately, I haven't done that test.
Click to expand...
Click to collapse
I think there is the cornerstone