I am building Lineage OS 20 on an i9100.
The development environment is Ubuntu 22.04 LTS and the device source code is from @ rINanDO.
So, I am facing this problem. I have everything ready and when I type "brunch i9100" I get the error in the image.
I have tried everything and keep getting the error so I am posting this.
Please help and advice me.
{
"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"
}
yonekome said:
I am building Lineage OS 20 on an i9100.
The development environment is Ubuntu 22.04 LTS and the device source code is from rINanDO.
So, I am facing this problem. I have everything ready and when I type "brunch i9100" I get the error in the image.
I have tried everything and keep getting the error so I am posting this.
Please help and advice me.View attachment 5724229
Click to expand...
Click to collapse
Ask @rINanDO bro
Concept48 said:
Ask @rINanDO bro
Click to expand...
Click to collapse
I thought perhaps this was not an error due to his device source code, so I wrote here
yonekome said:
I am building Lineage OS 20 on an i9100.
The development environment is Ubuntu 22.04 LTS and the device source code is from @ rINanDO.
So, I am facing this problem. I have everything ready and when I type "brunch i9100" I get the error in the image.
I have tried everything and keep getting the error so I am posting this.
Please help and advice me.View attachment 5724229
Click to expand...
Click to collapse
I have the same issue when compiling Awaken A13. It's something related to clang, you should switch to clang proton. Let me know if you fixed it and how.
Nem1x said:
I have the same issue when compiling Awaken A13. It's something related to clang, you should switch to clang proton. Let me know if you fixed it and how.
Click to expand...
Click to collapse
Good job Nemix !!
yonekome said:
I thought perhaps this was not an error due to his device source code, so I wrote here
Click to expand...
Click to collapse
I fixed it by cloning Proton Clang and adding these lines to BoardConfig in device:
TARGET_KERNEL_CLANG_VERSION := proton
TARGET_KERNEL_CLANG_PATH := $(shell pwd)/prebuilts/clang/host/linux-x86/clang-proton
To clone proton clang run:
git clone --depth=1 https://github.com/kdrag0n/proton-clang.git prebuilts/clang/host/linux-x86/clang-proton
Nem1x said:
I fixed it by cloning Proton Clang and adding these lines to BoardConfig in device:
TARGET_KERNEL_CLANG_VERSION := proton
TARGET_KERNEL_CLANG_PATH := $(shell pwd)/prebuilts/clang/host/linux-x86/clang-proton
To clone proton clang run:
git clone --depth=1 https://github.com/kdrag0n/proton-clang.git prebuilts/clang/host/linux-x86/clang-proton
Click to expand...
Click to collapse
Nice bro , so soon Android 13 in the test bank
Nem1x said:
I fixed it by cloning Proton Clang and adding these lines to BoardConfig in device:
TARGET_KERNEL_CLANG_VERSION := proton
TARGET_KERNEL_CLANG_PATH := $(shell pwd)/prebuilts/clang/host/linux-x86/clang-proton
To clone proton clang run:
git clone --depth=1 https://github.com/kdrag0n/proton-clang.git prebuilts/clang/host/linux-x86/clang-proton
Click to expand...
Click to collapse
Thanks for the advice.
I have a question about a script to add to BoardConfig.
The place to add it is in my case
android/lineage/device/samsung/i9100/BoardConfig.mk
Click to expand...
Click to collapse
and
android/lineage/device/samsug/galaxys2-common/BoardCommonConfig.mk
Click to expand...
Click to collapse
at the bottom?
I ran clone proton clang command first and added the script to the above location, but the error did not go away.
Nem1x said:
TARGET_KERNEL_CLANG_VERSION := proton
TARGET_KERNEL_CLANG_PATH := $(shell pwd)/prebuilts/clang/host/linux-x86/clang-proton
Click to expand...
Click to collapse
Yeah it goes at. android/lineage/device/samsung/i9100/BoardConfig.mk
I think that it doesn't matter where you put it. Bottom of the file should work.
Nem1x said:
Yeah it goes at. android/lineage/device/samsung/i9100/BoardConfig.mk
I think that it doesn't matter where you put it. Bottom of the file should work.
Click to expand...
Click to collapse
Hmmm.
I apply them and still get an error.
I'm stumped.
Try to add these lines as well in BoardConfig:
KERNEL_LD := LD=ld.lld
TARGET_KERNEL_ADDITIONAL_FLAGS := DTC_EXT=$(shell pwd)/prebuilts/misc/linux-x86/dtc/dtc LLVM=1
Nem1x said:
Try to add these lines as well in BoardConfig:
KERNEL_LD := LD=ld.lld
TARGET_KERNEL_ADDITIONAL_FLAGS := DTC_EXT=$(shell pwd)/prebuilts/misc/linux-x86/dtc/dtc LLVM=1
Click to expand...
Click to collapse
I added them, but I get an error…
I think I found the solution.
kbuild: use HOSTLDFLAGS for single .c executables · PixelExperience-Devices/[email protected]
When compiling executables from a single .c file, the linker is also invoked. Pass the HOSTLDFLAGS like for other linker commands. Signed-off-by: Robin Jarry <[email protected]> Cc: Josh...
github.com
lavender: Disable LLVM_BINUTILS · PixelExperience-Devices/[email protected]
• LLVM is now enabled by default as google is moving away from GCC. • Kernel side patches are required and as of now our kernel isn't compaitable. • Refs- https://gerrit.pixelexperience.org/c/v...
github.com
I hope you can find paths.
Remove previous patches as well.
Nem1x said:
kbuild: use HOSTLDFLAGS for single .c executables · PixelExperience-Devices/[email protected]
When compiling executables from a single .c file, the linker is also invoked. Pass the HOSTLDFLAGS like for other linker commands. Signed-off-by: Robin Jarry <[email protected]> Cc: Josh...
github.com
lavender: Disable LLVM_BINUTILS · PixelExperience-Devices/[email protected]
• LLVM is now enabled by default as google is moving away from GCC. • Kernel side patches are required and as of now our kernel isn't compaitable. • Refs- https://gerrit.pixelexperience.org/c/v...
github.com
I hope you can find pataths.
Click to expand...
Click to collapse
It worked fine!
I added these.
~/android/lineage/kernel/samsung/smdk4412/scripts/Makefile.host
# Create executable from a single .c file
# host-csingle -> Executable
quiet_cmd_host-csingle = HOSTCC [email protected]
cmd_host-csingle = $(HOSTCC) $(hostc_flags) -o [email protected] $< \
cmd_host-csingle = $(HOSTCC) $(hostc_flags) $(HOSTLDFLAGS) -o [email protected] $< \
$(HOST_LOADLIBES) $(HOSTLOADLIBES_$(@F))
$(host-csingle): $(obj)/%: $(src)/%.c FORCE
$(call if_changed_dep,host-csingle)
Click to expand...
Click to collapse
and
~/android/lineage/device/samsung/i9100/BoardConfig.mk
# Kernel
TARGET_KERNEL_SOURCE := kernel/samsung/smdk4412
TARGET_KERNEL_LLVM_BINUTILS := false
BOARD_KERNEL_SEPARATED_DTBO := true
Click to expand...
Click to collapse
Thanks for the great support.
so did you manage to build lineage 20.0?
notnoelchannel said:
so did you manage to build lineage 20.0?
Click to expand...
Click to collapse
I did. I don't know about him.
notnoelchannel said:
so did you manage to build lineage 20.0?
Click to expand...
Click to collapse
50% complete, but new error.
Related
{
"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"
}
Device: m7 (HTC One)
All I've done is compiled sources to bring you these builds. All the heavy lifting is done over at https://github.com/htc-msm8960 - thank those guys, they are working incredibly hard to bring AOSP to this device. I think the list of developers goes something like this: h8rift, intervigil, toastcfh, deck, Flinny, Flemmard, Codeworkx, birdman
That means that any bugs that exist in other AOSP builds will probablacy exist in these builds.
Click to expand...
Click to collapse
» Installation is simple:
If coming from another ROM or another major AOKP version, wipe data in recovery
Make sure you're using the latest CWM or TWRP
Flash ROM
Flash Google Apps (GAPPS)
Reboot
Code:
May 22
- included test call audio fix
- included xxhdpi device commits
May 21
- latest AOKP sources
- latest CM m7 sources
from gerrit:
- updated ribbons
- LockScreen: Fix crash when unlocking twice
- Add transparency settings for lockscreen (2/2)
- Smooth Spinners: Makes the loading "spinner" animation smoother in non-holo apps
sorry for the delay for those who waited :)
» Check merged commits on AOKP's Gerrit
build: http://goo.im/devs/roman/aokp_m7 - my nightlies will be in this folder. I'll also probably push them through AOKPush
gapps: http://goo.im/gapps/gapps-jb-20130301-signed.zip - b7e53e96e1c8b1a1c4865bf29418c8e0
» Building AOKP for your m7
First, create file .repo/local_manifests/m7.xml with the following contents: https://gist.github.com/romanbb/5517890
repo sync
Cherry pick this: http://gerrit.aokp.co/#/c/8320/
Cherry pick this: http://gerrit.aokp.co/#/c/8159/
Cherry pick this: http://gerrit.aokp.co/#/c/8321/
Build aokp_m7:
Code:
. build/envsetup.sh && brunch aokp_m7-userdebug
» AOKP Gerrit
» AOKP on Github
» SOURCE on AOKP.co
We greatly appreciate your contribution in the form of code, or PayPal donations.
» Donation options on AOKP.co
Enjoy!
for science
Whhhhhhhat?!?!?! Awesome sauce, great to see you here Roman!!
Did you get the one Roman? My wife got it and I'm debating selling my s3 for it. Any thoughts on the phone or are you gonna dev for it? Thanks
Sent from my SGH-T999 using Tapatalk 2
eliasadrian said:
Did you get the one Roman? My wife got it and I'm debating selling my s3 for it. Any thoughts on the phone or are you gonna dev for it? Thanks
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
He's got the HTC One on T-Mobile
https://twitter.com/romanbb/status/330053433702887425
eliasadrian said:
Did you get the one Roman? My wife got it and I'm debating selling my s3 for it. Any thoughts on the phone or are you gonna dev for it? Thanks
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Yeah, Amazon hardware. I'm not going to dev so much "for" it, even though I might try... but I think I'll dev with it?
Sent from my Nexus 7 using Tapatalk HD
new build up http://goo.im/devs/roman/aokp_m7/
coming from the s3, any word on what works and what does not work?
nicksmizzle said:
coming from the s3, any word on what works and what does not work?
Click to expand...
Click to collapse
Camera doesn't work
Sent from my HTC One using xda app-developers app
Camera Bummer
Once camera works, this will be my daily driver! can hardly wait!!!:highfive:
Roman,
Good to see you around, I think something is up with AOSP with the GFX. If you download the live wallpaper below you will see it has some strange effects that do not happen on the stock rom. My Nexus 10 tablet on 4.2.2 does not have the artifacts so I do not believe this is a 4.2.2 issue with the phone but both your rom and the ALPHA for Cyanogen 10.1 both display the issue.
https://play.google.com/store/apps/details?id=com.tribok.android.livewallpaper.springtideshower.lite
Its a great wallpaper BTW but wanted to bring it to your attention because maybe something is off with the GFX driver being used? I understand that major work is done by https://github.com/htc-msm8960 but thought I would let you know if you could help pass along.
Thanks,
1WayJonny
Roman, good to have you on the one.
I sure hope you all can get the camera working....
I get this on compiling from the new .xml and instructions today
device/htc/m7-common/overlay/packages/apps/Settings/res/values/arrays.xml:8: error: Error: No resource found that matches the given name (at '^index_0' with value '@string/pulse_length_always_on').
make: *** [/home/joey/aokp/out/target/common/obj/APPS/Settings_intermediates/src/R.stamp] Error 1
make: *** Waiting for unfinished jobs....
warning: no entries written for dimen/password_keyboard_height
warning: no entries written for drawable/sym_keyboard_delete_holo
any suggestions?
superg81 said:
I get this on compiling from the new .xml and instructions today
device/htc/m7-common/overlay/packages/apps/Settings/res/values/arrays.xml:8: error: Error: No resource found that matches the given name (at '^index_0' with value '@string/pulse_length_always_on').
make: *** [/home/joey/aokp/out/target/common/obj/APPS/Settings_intermediates/src/R.stamp] Error 1
make: *** Waiting for unfinished jobs....
warning: no entries written for dimen/password_keyboard_height
warning: no entries written for drawable/sym_keyboard_delete_holo
any suggestions?
Click to expand...
Click to collapse
check the op. there are new build instructions. it's specifically the overlay commit that will fix that for you
Romanbb said:
check the op. there are new build instructions. it's specifically the overlay commit that will fix that for you
Click to expand...
Click to collapse
just did and get this now
From http://gerrit.aokp.co/AOKP/device_htc_m7-common
* branch refs/changes/81/8481/1 -> FETCH_HEAD
error: Your local changes to the following files would be overwritten by merge:
overlay/frameworks/base/core/res/res/values/config.xml
Please, commit your changes or stash them before you can merge.
Aborting
let me re post here
From http://gerrit.aokp.co/AOKP/device_htc_m7-common
* branch refs/changes/20/8320/4 -> FETCH_HEAD
error: Your local changes to the following files would be overwritten by merge:
overlay/frameworks/base/core/res/res/values/config.xml
Please, commit your changes or stash them before you can merge.
Aborting
superg81 said:
just did and get this now
From http://gerrit.aokp.co/AOKP/device_htc_m7-common
* branch refs/changes/81/8481/1 -> FETCH_HEAD
error: Your local changes to the following files would be overwritten by merge:
overlay/frameworks/base/core/res/res/values/config.xml
Please, commit your changes or stash them before you can merge.
Aborting
let me re post here
From http://gerrit.aokp.co/AOKP/device_htc_m7-common
* branch refs/changes/20/8320/4 -> FETCH_HEAD
error: Your local changes to the following files would be overwritten by merge:
overlay/frameworks/base/core/res/res/values/config.xml
Please, commit your changes or stash them before you can merge.
Aborting
Click to expand...
Click to collapse
in each of those dirs, you could do a "git reset --hard HEAD" to clear out any changes you may have made
Romanbb said:
in each of those dirs, you could do a "git reset --hard HEAD" to clear out any changes you may have made
Click to expand...
Click to collapse
gotcha,shall try that
did you realize 4 and 5 in op for picks are same?
superg81 said:
gotcha,shall try that
did you realize 4 and 5 in op for picks are same?
Click to expand...
Click to collapse
i did not
Romanbb said:
i did not
Click to expand...
Click to collapse
:silly:
are you guys using the tmo htc one having any issues with call audio?
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
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
{
"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"
}
Project: Exynos-Linux-Stable- Exynos-Linux-Stable is an organisation on GitLab & GitHub containing upstreamed linux for some of the latest flagship handset from SAMSUNG like the S7, S7E, S8, S8+, Note 8, S9, S9+, Note 9 kernel upstreamed to be inline with respective linux branches.
What does this bring?
- All of the devices mentioned above uses Long Term Support (LTS) releases, they are like old softwares.
- LTS releases are supported through their specified support duration by security updates, bug fixes, backports, and new device drivers, just like a regular release.
So updating or up-streaming your device's kernel brings many improvements talking security, performance wise etc...
How do I use?
If you are a developer, the reference tree is located in the exynos-linux-stable organization: https://github.com/exynos-linux-stable
This can either be merged into your existing kernel tree if you have one or be used as a fresh base. You do not need my permission to use it nor do you need to give me credit (although it would be appreciated).
If you are a user, ask your kernel developer KINDLY to use this source for his kernel that has all the changes added in!
Getting notified about updates
There are a few ways to get notified of linux-stable updates:
The exynos-linux-stable Telegram channel: https://t.me/exynos_linux_stable
Subscribe to this thread
XDA:DevDB Information
ELS - exynos-linux-stable, Kernel for the Samsung Galaxy Note 9
Contributors
farovitus
Source Code: https://github.com/exynos-linux-stable/crownlte
Kernel Special Features:
Version Information
Status: Stable
Stable Release Date: 2019-05-18
Created 2018-08-24
Last Updated 2019-09-17
Reserved
Reserved
This source appears to be broken (apparently now differently to when I tried a few days ago):
Code:
~$ mkdir note-9
~$ cd note-9
~/note-9$ git clone https://bitbucket.org/UBERTC/aarch64-linux-android-4.9-kernel
~/note-9$ git clone https://github.com/exynos-linux-stable/crownlte
~/note-9$ cd crownlte
~/note-9/crownlte$ export ARCH=arm64 CROSS_COMPILE=aarch64-linux-android- PATH=$PWD/aarch64-linux-android-4.9-kernel/bin:$PATH
~/note-9/crownlte$ make exynos9810-crownlte_defconfig
~/note-9/crownlte$ make -j1
CHK include/config/kernel.release
CHK include/generated/uapi/linux/version.h
CHK include/generated/utsrelease.h
CHK include/generated/bounds.h
CHK include/generated/timeconst.h
CHK include/generated/asm-offsets.h
CALL scripts/checksyscalls.sh
CHK include/generated/compile.h
CC init/version.o
LD init/mounts.o
AS init/_uh.o
init/_uh.S: Assembler messages:
init/_uh.S:40: Error: file not found: init/uh.8g.elf
scripts/Makefile.build:393: recipe for target 'init/_uh.o' failed
make[1]: *** [init/_uh.o] Error 1
Makefile:1036: recipe for target 'init' failed
make: *** [init] Error 2
stock source builds in the same environment.
Phoenix09 said:
This source appears to be broken (apparently now differently to when I tried a few days ago):
stock source builds in the same environment.
Click to expand...
Click to collapse
Well i did compile the source before i pushed it to GitHub and it was totally fine... but i will double check tomorrow.
farovitus said:
Well i did compile the source before i pushed it to GitHub and it was totally fine... but i will double check tomorrow.
Click to expand...
Click to collapse
did you manage to check?
Sent from my SM-N960F using Tapatalk
Phoenix09 said:
did you manage to check?
Click to expand...
Click to collapse
No, i am quiet busy these days. Send me a link of your source so i can check it out from my phone.
Again, i am sure the ELS source will compile just fine.
farovitus said:
No, i am quiet busy these days. Send me a link of your source so i can check it out from my phone.
Again, i am sure the ELS source will compile just fine.
Click to expand...
Click to collapse
https://github.com/exynos-linux-stable/crownlte
I made zero changes, what I posted is exactly what I did, it does not compile.
Edit: what OS are you compiling on?
Sent from my SM-N960F using Tapatalk
Phoenix09 said:
This source appears to be broken (apparently now differently to when I tried a few days ago):
stock source builds in the same environment.
Click to expand...
Click to collapse
Source compile just fine. Please do a proper clone to the source to avoid any issue.
4.9.140 has been merged.
farovitus said:
4.9.140 has been merged.
Click to expand...
Click to collapse
that now builds for me.. in the exact same environment, Ubuntu 14.04 in vagrant with a script:
Code:
#!/bin/sh
set -e
sudo apt-get update
sudo apt-get install -y git build-essential bc
cd $HOME
[ -d aarch64-linux-android-4.9-kernel ] || git clone --depth=1 https://bitbucket.org/UBERTC/aarch64-linux-android-4.9-kernel
[ -d crownlte ] || git clone --depth=1 https://github.com/exynos-linux-stable/crownlte
export ARCH=arm64 CROSS_COMPILE=aarch64-linux-android- PATH=$HOME/aarch64-linux-android-4.9-kernel/bin:$PATH
cd crownlte
make exynos9810-crownlte_defconfig
make -j8
4.9.141 has been released.
hi, i need a stock note 9 pie kernel (CSB3), i flashed another kernel and it wont allow me to go past my login, can you please direct me to a stock pie kernel so i can flassh and get in?
mafioso345 said:
hi, i need a stock note 9 pie kernel (CSB3), i flashed another kernel and it wont allow me to go past my login, can you please direct me to a stock pie kernel so i can flassh and get in?
Click to expand...
Click to collapse
Don't ask here.. Just take a Rom like ketan and flash only kernel via aroma. Done
Ketan p06 has CSB3 base so that kernel will work no problem.
- 4.9.177 merged in.
- Merged CSDE OSRC into crownlte exynos-linux-stable tree.
https://github.com/exynos-linux-stable/crownlte
As always, join https://t.me/exynos_linux_stable to get instantly notified of every ELS update.
I know it's a stupid question but how to pack kernel inside IMG? I want to get image for heimdall.
I've honestly googled but it looks like everybody just knows how to do this. And nobody discuss it
-W_O_L_F- said:
I know it's a stupid question but how to pack kernel inside IMG? I want to get image for heimdall.
I've honestly googled but it looks like everybody just knows how to do this. And nobody discuss it
Click to expand...
Click to collapse
You'll want to use Android Image Kitchen to unpack and repack kernels inside images. You can diff the unpacked boot.img provided in devbase with mine to see the basic ramdisk modifications to prevent forced encryption or various other issues. Or you can just unpack my image, it's relatively basic with it's modifications. Hope this helps.
EDIT: You can also look at my make9810.sh script on GitHub to see the various steps I take for repacking my images.
Can someone explain what this is for? Is this purely for use with linux on DEX or are you guys flashing linux direct to your Note9 somehow? Or updating the kernel that android is running on?
bandario said:
Can someone explain what this is for? Is this purely for use with linux on DEX or are you guys flashing linux direct to your Note9 somehow? Or updating the kernel that android is running on?
Click to expand...
Click to collapse
It's a reference kernel source with all recent patches from vanilla kernel applied to Samsung stock one. Some developers use this source as a base for their custom kernels. This is what it's for.
ELS is for Android. But I'm developing a kernel that can boot Linux (GNU/Linux) on Note9. And yes, it's based on ELS sources.
4.9.193 has been merged into the exynos-linux-stable tree.
https://github.com/exynos-linux-stable/crownlte
What is KernelSU?
KernelSU is a root solution for Android GKI devices, it works in kernel mode and grant root permission to userspace application directly in kernel space.
Click to expand...
Click to collapse
Warning
Please do some research if you have any concerns about features included in the products you find here before flashing it! YOU are choosing to make these modifications.
Kernel-Assisted SuperUser is an awful idea! If you're silly, and then very bad things will happen. This here probably is not for you! If you're reading this sentence, start backing away slowly! Out, damned spot!
Click to expand...
Click to collapse
Features
The main feature of KernelSU is it is Kernel-based. KernelSU works in kernel mode, so it can provide kernel interface we never had before. For example, we can add hardware breakpoint to any process in kernel mode; We can access physical memory of any process without anybody being aware of; We can intercept any syscall in kernel space; etc.
And also, KernelSU provides a module system via overlayfs, which allows you to load your custom plugin into system. It also provides a mechanism to modify files in /system partition.
Click to expand...
Click to collapse
Issues
For now, nothing.
Click to expand...
Click to collapse
Installation
Flash the zip via any custom recovery, wait until it finishes the flashing process and reboot to System.
Download the KernelSU manager app from github releases or github actions.
Click to expand...
Click to collapse
Sources
Custom Kernel Source - https://github.com/DevZillion/android_kernel_samsung_gta7litexx
KernelSU Source - https://github.com/tiann/KernelSU
Click to expand...
Click to collapse
Screenshots
Spoiler: View
View attachment 5889063
View attachment 5889069
View attachment 5889071
Info
Telegram Support Group - https://t.me/gta7litegroup
Click to expand...
Click to collapse
FROM SM-T225 A13 PQR-1 FW: T225XXU1CWA2 , T225XXS3CWC2
[ OneUI 5.1]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MODULES:
1. ZYGISK FOR KERNELSU : https://github.com/Dr-TSNG/ZygiskOnKernelSU/releases
2. R/W super partition.
Release v3.0.3 · HuskyDG/magic_overlayfs
Minor refine overlayfs mount
github.com
Code:
$ su
:/data/data/com.termux/files/home # nsenter -t 1 -m sh
:/ # overlayfs_system --unmount-ksu
umount: /system
:/ # su -mm -c magic_remount_rw
remounted [/odm_dlkm] (overlay)
remounted [/vendor_dlkm] (overlay)
skipped [/system/etc/permissions/android.hardware.fingerprint.xml] (ext4)
remounted [/system/usr/keylayout] (overlay)
remounted [/system] (overlay)
remounted [/odm] (overlay)
skipped [/vendor/etc/usb_audio_policy_configuration.xml] (ext4)
skipped [/vendor/bin/install-recovery.sh] (ext4)
remounted [/vendor/lib64/libmtk-ril.so] (tmpfs)
remounted [/vendor] (overlay)
:/ #
Ok , i am using android 13 from Bl 11
I can flash this kernel ???
tom.android said:
FROM SM-T225 A13 PQR-1 FW: T225XXU1CWA2
View attachment 5924187
Click to expand...
Click to collapse
This work for android 13 from Bl 11
Difficul said:
This work for android 13 from Bl 11
Click to expand...
Click to collapse
For A13 Based ROM
tom.android said:
For A13 Based ROM
Click to expand...
Click to collapse
i am using bananadroid 13 in Bl 11
May be not have problem with Bootloader
told me some benefits
boot.img of A11 can't changes to kernelSu A13.
tom.android said:
boot.img of A11 can't changes to kernelSu A13.
Click to expand...
Click to collapse
so , i need upgrade BL 11 to BL 13 to use this kernel ?
Difficul said:
so , i need upgrade BL 11 to BL 13 to use this kernel ?
Click to expand...
Click to collapse
Absolutely yes
tom.android said:
Absolutely yes
Click to expand...
Click to collapse
Ok , do you know some module busybox for magisk working for android 13
I don't know why i can't search module from magisk
Difficul said:
Ok , do you know some module busybox for magisk working for android 13
I don't know why i can't search module from magisk
Click to expand...
Click to collapse
kernelsu had built-in busybox.
tom.android said:
kernelsu had built-in busybox.
Click to expand...
Click to collapse
Sorry , i don't want upgrade to Bl 13 to reinstall this rom and try this kernel
Difficul said:
Sorry , i don't want upgrade to Bl 13 to reinstall this rom and try this kernel
Click to expand...
Click to collapse
Magisk is ok for you.
tom.android said:
Magisk is ok for you.
Click to expand...
Click to collapse
I know , but i can't search module from internet
the module available is so long and may be you can test first because my Tab have broken volume up
Try to compile kernel with Ubuntu Sub-system in win 10, and no-need to changes for new kernelSU-patch version.?
*try to new kernelSU v.0.6.0 but not success. ( not supported kernelsu)
Thank you
tom.android said:
Try to compile kernel with Ubuntu Sub-system in win 10, and no-need to changes for new kernelSU-patch version.?
*try to new kernelSU v.0.6.0 but not success. ( not supported kernelsu)
Thank you
Click to expand...
Click to collapse
I don't see any issue in that build, you should find the Image.gz at /gta7lite/arch/arm64/boot/Image.gz
Zillion said:
I don't see any issue in that build, you should find the Image.gz at /gta7lite/arch/arm64/boot/Image.gz
Click to expand...
Click to collapse
Found it but it don't support ksu but boot , I try to " sudo bash build.sh " Are there build parameter or not. Thank you.
tom.android said:
Found it but it don't support ksu but boot , I try to " sudo bash build.sh " Are there build parameter or not. Thank you.
Click to expand...
Click to collapse
Oh, you missed to
Code:
export BUILD_KSU=true
KernelSU update v.0.6.0
Thank to Dev Zillion for Excellent Custom Kernel Script.
NOTE: Attachment
*.img. for flash with Odin at AP Slot.
*.zip. for flash with TWRP.
☆ Everythings all about new update KSU (kernelsu) and modules will posted here.
☆ New how2 from me.
☆☆☆ Run Windows Subsystem For Android on your Windows 11 using prebuilt binaries with Google Play Store (OpenGApps/ MindTheGapps) and/KernelSU (root solutions) built in.
GitHub - MustardChef/WSABuilds at Windows_11_2302.40000.6.0
Run Windows Subsystem For Android on your Windows 10 and Windows 11 PC using prebuilt binaries with Google Play Store (OpenGApps/ MindTheGapps) and/or Magisk or KernelSU (root solutions) built in. ...
github.com
Hack the system
GitHub - Tornaco/Thanox: I am thanos! 😈 👌
I am thanos! 😈 👌. Contribute to Tornaco/Thanox development by creating an account on GitHub.
github.com