This thread is meant for discussions about LineageOS or other ROM development.
@derf elot and I got an S10e and we started to work on LineageOS for it. Before we maintained the Sony XZ1 Compact.
Could someone please provide the output of
Code:
getprop
from a Stock ROM on an S10e?
For example:
Code:
adb shell getprop > s10e_props.txt
Thanks!
modpunk said:
the output of
Code:
getprop
from a Stock ROM on an S10e?
Click to expand...
Click to collapse
Magisk rooted ....
DHGE said:
Magisk rooted ....
Click to expand...
Click to collapse
Awesome, thank you very much!
Could someone please provide the output of
Code:
dumpsys media.camera
from a Stock ROM on an S10e?
For example:
Code:
adb shell dumpsys media.camera > s10e_cam.txt
Thanks!
modpunk said:
output of
Code:
dumpsys media.camera
from a Stock ROM on an S10e
Click to expand...
Click to collapse
see attachment
@DHGE thanks for your help again!
Do you guys start your own fork, or do you join forces with existing Lineage 17.1 builds?
ichmyselfandi said:
Do you guys start your own fork, or do you join forces with existing Lineage 17.1 builds?
Click to expand...
Click to collapse
We've asked Ivan if he would share his source code, he didn't so we started from scratch on our own [1]. We would be very happy if Ivan would join our effort, then we don't have to figure out the stuff again. However we are making good progress. The most important services are running now. We're currently writing SELinux policies for radio and will share it with other devices once done. See the android_device_exynos_sepolicy repository.
What a Wurst!
[1] https://github.com/whatawurst
Hey guys! Awesome work!
I have been requesting Ivan for the device tree for ages. But he keeps on saying soon.
I am a flashoholic. I literally try any GSIs out there. Keen on trying new roms and GSIs as well.
I am a S10+ user here.
I know more or less about android and all. If you need help to pull any files, do lemme know.
How can I contact you guys?
Did you make a telegram group or discord group?
I would love to join in the fun.
Do give me the contact details. Cheers!
zunaid321 said:
How can I contact you guys?
Did you make a telegram group or discord group?
Click to expand...
Click to collapse
We are totally old school IRC users
The S10(+) will take a bit longer as it has some different hardware.
Would love to chat with you guys in IRC!
Can you give me the instructions?
I need a bit more help, with a stock ROM installed on S10e:
Please run the following commands while the screen is on and when it is off:
Code:
adb shell cat /sys/power/cpuhotplug/max_online_cpu
adb shell cat /sys/power/cpufreq_max_limit
adb shell cat /sys/power/cpufreq_min_limit
modpunk said:
stock ROM installed on S10e:
Please run the following commands while the screen is on and when it is off:
Code:
adb shell cat /sys/power/cpuhotplug/max_online_cpu
adb shell cat /sys/power/cpufreq_max_limit
adb shell cat /sys/power/cpufreq_min_limit
Click to expand...
Click to collapse
see attachement
the first command does not find directory cpuhotplug
there is no difference on my S10e between screen states
Hey guys!
Its really good to see you working on this. It would be so great to have LineageOS for S10 open source finally.
If you need help in testing, I'd be happy to support. Owing a S10e, running LOS 17.
A few words to this whole I-keep-my-work-closed situation with @Ivan_Meler. Its really disappointing to see that the work is kept closed as of now. And I think its a pity because this contradicts the whole idea of LineageOS. Its meant to be open source so people can contribute and modify and do their own thing. Now, like Ivan is doing, taking code that is open and free to all, modifying it to make it work on the S10 and keeping it closed doesn't seem right. Its not in the spirit LOS is based on.
Ivans github repo available
angela5246 said:
Its really disappointing to see that the work is kept closed as of now.
Click to expand...
Click to collapse
https://github.com/ivanmeler/android_kernel_samsung_beyondlte/tree/lineage-17.0
Does not look "closed" to me.
We should not speculate what is going on in private exchange between developers.
Looking at the commits in Ivans repository it looks like he is not very busy on this project recently.
At least he started early and delivered a working ROM.
DHGE said:
https://github.com/ivanmeler/android_kernel_samsung_beyondlte/tree/lineage-17.0
Does not look "closed" to me.
We should not speculate what is going on in private exchange between developers.
Looking at the commits in Ivans repository it looks like he is not very busy on this project recently.
At least he started early and delivered a working ROM.
Click to expand...
Click to collapse
That is the kernel not the rom source
I think we are entering BETA phase, finally the system is going into deep sleep. However there is one problem, with the CTC5 firmware update form Samsung, the camera stopped working. I guess it requires some kernel changes but there is not source code drop yet.
modpunk said:
I think we are entering BETA phase, finally the system is going into deep sleep. However there is one problem, with the CTC5 firmware update form Samsung, the camera stopped working. I guess it requires some kernel changes but there is not source code drop yet.
Click to expand...
Click to collapse
After the source drops out, rebase the kernel on new source
ROM released:
https://forum.xda-developers.com/ga...--s10--s10-5g-cross-device-development-exynos
Related
Hi Developer's,
It's really great to see a lot of great roms for Samsung Galaxy Ace releasing day by day.....Why don't you guys work together and bring up an AOSP rom for SGA....Please try concentrating on developing an AOSP rom...
THANKS
Somebody did it but decided not to share because the forum is full of thieves who take others' work and change a little to release it as their own.
He mentioned that he's got ASOP working with a week standby battery life. Don't know if it's true but I believe it's possible. But now we need a developer to do this, not just rom cookers. Still it seems like nobody is interested.
consegregate said:
Somebody did it but decided not to share because the forum is full of thieves who take others' work and change a little to release it as their own.
He mentioned that he's got ASOP working with a week standby battery life. Don't know if it's true but I believe it's possible. But now we need a developer to do this, not just rom cookers. Still it seems like nobody is interested.
Click to expand...
Click to collapse
ASOP stands for ? (I'm considered quite a new use LOL)
Sent from my Ultima Weapon using XDA App
EmoBoiix3 said:
ASOP stands for ? (I'm considered quite a new use LOL)
Sent from my Ultima Weapon using XDA App
Click to expand...
Click to collapse
It's supposed to be AOSP sorry. It's android open source project. Such roms have no bloatware nor brand additions. The rom package can be as small as 40 mb. But integrating the functions like touchscreen and lights and connectivity may be a problem so we need somebody willing to compile!
consegregate said:
It's supposed to be AOSP sorry. It's android open source project. Such roms have no bloatware nor brand additions. The rom package can be as small as 40 mb. But integrating the functions like touchscreen and lights and connectivity may be a problem so we need somebody willing to compile!
Click to expand...
Click to collapse
Wow that's a small package
That's the only advantage ?
EmoBoiix3 said:
Wow that's a small package
That's the only advantage ?
Click to expand...
Click to collapse
with AOSP, we'll have a pure google phone no touchwiz
EmoBoiix3 said:
Wow that's a small package
That's the only advantage ?
Click to expand...
Click to collapse
Small, but also extremely lightweight so I presume it'll be fast. With that as base custom roms should be better and faster.
If sod is really a firmware bug both AOSP and Cyanogenmod should stomp it off...
AOSP is android in its purest form without samsung's desecration. It is how android was meant to be. It is a base for ROMs like MIUI in many cases. Besides one can use the latest android sources(android 2.3.5) or the older stable sources to build it.
But building it is not easy. The android source code itself is like some 2 GB. Compiling and integrating the source code into a device is like building something from scratch. It would take a lot of time,effort and patience to build an AOSP rom.
skynet28 said:
AOSP is android in its purest form without samsung's desecration. It is how android was meant to be. It is a base for ROMs like MIUI in many cases. Besides one can use the latest android sources(android 2.3.5) or the older stable sources to build it.
But building it is not easy. The android source code itself is like some 2 GB. Compiling and integrating the source code into a device is like building something from scratch. It would take a lot of time,effort and patience to build an AOSP rom.
Click to expand...
Click to collapse
Wow.....THAT IS AWESOME !
Unfortunately I know nothing about code , otherwise I would've worked on it . LOL
skynet28 said:
AOSP is android in its purest form without samsung's desecration. It is how android was meant to be. It is a base for ROMs like MIUI in many cases. Besides one can use the latest android sources(android 2.3.5) or the older stable sources to build it.
But building it is not easy. The android source code itself is like some 2 GB. Compiling and integrating the source code into a device is like building something from scratch. It would take a lot of time,effort and patience to build an AOSP rom.
Click to expand...
Click to collapse
Though what i've heard of is that miui was based on cyanogenmod, which was also built from scratch.
I have Ubuntu....but I'm a fail at programming XD HAHAHAHA
Anyone wanna make an AOSP ROM with me ?
consegregate said:
Though what i've heard of is that miui was based on cyanogenmod, which was also built from scratch.
Click to expand...
Click to collapse
Of course both cyanogenmod and aosp have to be built from scratch. Cyanogenmod,pure AOSP and MIUI are all based on Original AOSP source code and so have the maximum speed and utilize the hardware to its fullest. This is unlike samsung stock which has incorporated some closed source code with the open source one which limits its development.
...and all AOSP ROM should have no SOD issue
I set to work on it....but I didn't go far . FML
Sent from my Ultima Weapon using XDA App
For anyone interested, here's a tutorial that might help...
http://forum.xda-developers.com/showthread.php?t=1183832
adiles said:
For anyone interested, here's a tutorial that might help...
http://forum.xda-developers.com/showthread.php?t=1183832
Click to expand...
Click to collapse
It helps , but how do I configure USB for Ace ??
Sent from my Ultima Weapon using XDA App
EmoBoiix3 said:
It helps , but how do I configure USB for Ace ??
Sent from my Ultima Weapon using XDA App
Click to expand...
Click to collapse
I guess you are using ubuntu..
Go to a terminal,connect the Galaxy ace via usb and type
$ lsusb
This will list various bus devices..Find Samsung electronics...mine is something like this...yours should be something like this-
Bus 002 Device 009: ID 04e8:689e Samsung Electronics Co., Ltd
Here "04e8" is vendor id and "689e" is product id.
Type in terminal-
Code:
$ gksudo gedit /etc/udev/rules.d/51-android.rules
In the blank file type
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="04e8", ATTRS{idProduct}=="689e", MODE="0666", OWNER=""
Save the file and type
Code:
$ sudo chmod a+r /etc/udev/rules.d/51-android.rules
and restart udev.
edit.. wrong forum
skynet28 said:
I guess you are using ubuntu..
Go to a terminal,connect the Galaxy ace via usb and type
$ lsusb
This will list various bus devices..Find Samsung electronics...mine is something like this...yours should be something like this-
Bus 002 Device 009: ID 04e8:689e Samsung Electronics Co., Ltd
Here "04e8" is vendor id and "689e" is product id.
Type in terminal-
Code:
$ gksudo gedit /etc/udev/rules.d/51-android.rules
In the blank file type
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="04e8", ATTRS{idProduct}=="689e", MODE="0666", OWNER=""
Save the file and type
Code:
$ sudo chmod a+r /etc/udev/rules.d/51-android.rules
and restart udev.
Click to expand...
Click to collapse
Thanks a bunch
It's hard t do such things on a VM , you know ><
Sent from my Ultima Weapon using XDA App
Hi folks,
I just started to port UbuntuTouch for the Sony Xperia Z Ultra and I think I should have a *.zip ready for testing in 2 weeks.
Until then, I will use this thread as a scrap book to document all the troubles I run into, all the things that needed my special attention and fixes that are not that obvious. I hope there will be some fellas brave enough to test everything and report back or even to join me with the development.
Best regards,
Kalle
First Update:
I found that the Ubuntu Touch version that ist based on CyanogenMod was not updated to a more recent version. This means that I have to either look into AOSP or backport everything to CM-10.1. I think backporting is kinda stupid because newer we are writing new software to improve things. Sadly I don't have much experiance with AOSP so I will have to find out how everything works and what the differences to CyanogenMod are.
The good news is, that I'm catching up with the mailing list, which means I'll have a place to call for help.
Also I'm in the progress to start a git repo, but I'm unsure what I will need to add, maybe some common stuff from sony does not need to be changed.
So long,
Kalle
Update!
There is a new porting guide! See here
I already freed some space for it and ordered a bit more ram so after my exam next week, I'll pick this up/Start all over.
Hope you are as excited as I am,
Kalle
XDA:DevDB Information
Ubuntu Touch for Sony Xperia Z Ultra, ROM for the Sony Xperia Z Ultra
Contributors
KalleEatingBrain, Kohelet
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader
Based On: AOSP
Version Information
Status: Testing
Created 2014-05-14
Last Updated 2015-02-24
freaking awesome!
freaking awesome!
i would like to test. maybe i can help with developing/porting
Thank you for your efforts. I will test if needed.
Sent from my C6806 using XDA Premium 4 mobile app
Great this would be awesome if you can make it happen. I'm here for testing if required.
Sent from my C6833 using XDA Premium 4 mobile app
In also here for testing... Ubuntu Touch has intruiged me, I would love to try it out.
Thx... (thread bookmarked)
Sent from my C6833 using Tapatalk
I keep meaning to reply to this thread... Thanks for putting the effort in to get this working. If you want any hints/tips etc from my experience in getting slim and carbon built for the ZU just ask, I'll be willing to test aswell
iBuzman said:
Thx... (thread bookmarked)
Sent from my C6833 using Tapatalk
Click to expand...
Click to collapse
+1
Nice.ill be watching out everyday
Sent from my C6833 using XDA Premium 4 mobile app
blueether said:
I keep meaning to reply to this thread... Thanks for putting the effort in to get this working. If you want any hints/tips etc from my experience in getting slim and carbon built for the ZU just ask, I'll be willing to test aswell
Click to expand...
Click to collapse
Cool, thanks can you give me a hint on how to deal with new targets in Aosp? I mean setting up the files in a way "lunch" is able to find the right target.
Sent from my C6833 using XDA Free mobile app
vendersetup.sh file in vender/ might be what you are looking for?
have a gander at this http://www.kandroid.org/online-pdk/guide/build_new_device.html
How are you doing on this? I've just started working on this as well and am curious to know how far along you've gotten/what issues you've run into.
Sent from my Nexus 7 using XDA Free mobile app
So I've gotten the build to start, but I'm running into issues with libhybris:
ubuntu/hybris/compat/media/media_codec_layer.cpp:51:40: fatal error: gui/IGraphicBufferProducer.h: No such file or directory
compilation terminated.
make: *** [out/target/product/togari/obj/SHARED_LIBRARIES/libmedia_compat_layer_intermediates/media_codec_layer.o] Error
I'll post here once I've found a solution.
Kohelet said:
So I've gotten the build to start, but I'm running into issues with libhybris:
ubuntu/hybris/compat/media/media_codec_layer.cpp:51:40: fatal error: gui/IGraphicBufferProducer.h: No such file or directory
compilation terminated.
make: *** [out/target/product/togari/obj/SHARED_LIBRARIES/libmedia_compat_layer_intermediates/media_codec_layer.o] Error
I'll post here once I've found a solution.
Click to expand...
Click to collapse
Yeah, thats as far as I got, too. :-/ I tried removing all different libs or compiling different parts and leaving others out but I couldn't get any futher. Also I saw your post to the mailing list but it seems like you wont get a helpful reply either. As far a I could track this problem is the incompatibility of togari CM-11 and the ubuntu AOSP source tree. On xda-university there is a guide for porting from CM to AOSP which I will try but maybe you should take a look, too. Anyways: Great to see there is someone else except lazy me working on this.
Best regards,
Kalle
KalleEatingBrain said:
Yeah, thats as far as I got, too. :-/ I tried removing all different libs or compiling different parts and leaving others out but I couldn't get any futher. Also I saw your post to the mailing list but it seems like you wont get a helpful reply either. As far a I could track this problem is the incompatibility of togari CM-11 and the ubuntu AOSP source tree. On xda-university there is a guide for porting from CM to AOSP which I will try but maybe you should take a look, too. Anyways: Great to see there is someone else except lazy me working on this.
Best regards,
Kalle
Click to expand...
Click to collapse
I actually got past the libhybris issue. The problem was that the porting guide is out of date. It's based on using cm-10.1 whereas the current source for Ubuntu is based on cm-11.0. So if you use 4.4.2 instead instead of 4.2.2 then it works. But there are so many other issues and the documentation for fixing them is so poor. I've kept a running list of problems I've come across and the solutions for them (it's below).
Also they dropped the whole UCM thing so you should be able to get sound working once you actually get a working build, but I couldn't get it to build. The error that is currently in my way has to do with "No rule to make target signapk.jar needed by com.qualcomm.location" or something or other. And I found nothing on how to solve that online.
At this point I've decided to take a short break from the whole thing because it's so frustrating.
Once I get motivated to work on it again, I'll probably start from scratch.
Issues List (I apologize for not being specific about the errors, I didn't write them down verbatim):
If you get an error about libelf you need to add CyanogenMod/android_external_elfutils to your local_manifests/roomservice.xml and also add external/elfutils under subdirs in build/core/main.mk
Don't forget to also add device/sony and vendor/sony to build/core/main.mk as well.
The build will complain about not having a rule to make android-boot.img. To fix you have to go to device/sony/fusion3-common/custombookimg.mk and change boot.img to android-boot.img. You need to make the same change in device/sony/rhine-common/custombootimg.mk
I got an error about android.hardware.bluetooth_le.xml. If you just restart the build it doesn't complain, but I didn't find a proper solution to that.
If you get the libhybris error you have the wrong version of the Ubuntu source. Make sure you're using 4.4.2 when you phablet-dev-botstrap. It should be phablet-dev-bootstrap --sources aosp --repo-branch phablet-4.4.2_r1 [target_directory]
You might get an error about a product_config.mk and how it's missing a makefile for togari. You have to make sure that in device/sony/togari Android.mk, cm.mk, full_togari.mk, and vendorsetup.sh PRODUCT_NAME is the same. I solved this by changing PRODUCT_NAME to cm_togari in all of them and then renamed full_togari.mk to cm_togari.mk
You might get an error like MODULE.TARGET.SHARED_LIBRARIES.libOmxCore already defined in hardware/qcom/media. You should have CyanogenMod/android_hardware_qcom_media-caf-new in your repo manifest with a path of android/qcom/media-caf-new so you can safely rm -rf the hardware/qcom/media directory to get past this error.
If you get an error about dtbToolCM, add /device/qcom/common/dtbtool to your subdirs in build/core/main.mk
You may get an error about mkbootimg, that's because Sony uses a different version of mkbootimg. The only option I found was to download it from the internet (Thanks DooMLorD!). Once you get that version edit device/sony/rhine-common/custombootimg.mk and replace $(MKBOOTIMG) with the path to your downloaded mkbootimg binary.
You might get an error about no rule to make target something/something/signapk.jar needed by something/something/com.qualcomm.location. I didn't find a solution to this error.
Click to expand...
Click to collapse
Thanks for that list, it's sure to help some one. I think I have had most of those errors in trying to get aosp to build.
Can I copy those errors to my [DEV]Random thoughts thread?
blueether said:
Thanks for that list, it's sure to help some one. I think I have had most of those errors in trying to get aosp to build.
Can I copy those errors to my [DEV]Random thoughts thread?
Click to expand...
Click to collapse
Sure, feel free. I built CM for all my devices and regretted not keeping such a list when I did that. So now every time I work on a build I keep lists like that. Eventually, when I have a working build, I'll post a guide for how to build following the same steps I took.
Kohelet said:
Sure, feel free. I built CM for all my devices and regretted not keeping such a list when I did that. So now every time I work on a build I keep lists like that. Eventually, when I have a working build, I'll post a guide for how to build following the same steps I took.
Click to expand...
Click to collapse
Yeh carbon and slim were easy to build, and simple fixes. AOSP on the other hand I wish I had kept a build log
Ah nice, when I last checked CM-11.0 was not working with the 4.4.2r2 branch. I think I know how to fix the problem with the *.apk. Basically you have to remove all java dependencies from all the makefiles. I will look it up, so I can tell you what to grep for. Do you have a git repo we can work on, or should I add you to mine (which is just a fork of the CM-repos)? I will take a look at the sound in the next days. Thanks for you list!
Keep it up,
Kalle
Sent from my C6833 using XDA Free mobile app
KalleEatingBrain said:
Ah nice, when I last checked CM-11.0 was not working with the 4.4.2r2 branch.
Click to expand...
Click to collapse
That could potentially be a major source of my problems. i wasn't aware of that.
I think I know how to fix the problem with the *.apk. Basically you have to remove all java dependencies from all the makefiles. I will look it up, so I can tell you what to grep for. Do you have a git repo we can work on, or should I add you to mine (which is just a fork of the CM-repos)? I will take a look at the sound in the next days. Thanks for you list!
Keep it up,
Kalle
Sent from my C6833 using XDA Free mobile app
Click to expand...
Click to collapse
All I have at the moment is a fork of the CM repos. Feel free to add me to your repo. My username on Github is Kohelet as well. I can start to look into removing java dependencies as well.
As for the sound, the mailing list made it appear as if it was a simple matter of running
Code:
$ sudo apt-add-repository ppa:ci-train-ppa-service/landing-018
$ sudo apt-get update
$ sudo apt-get dist-upgrade
$ sudo apt-get install pulseaudio-module-droid
I could be wrong though.
Hello there.
Here is device tree:
DOWNLOAD from My github.
It is in Alpha (developers) release as probably You will need to fix few errors by hand....but, anyway, someone must to start with something....
Kernel is in this moment not released by HTC, but We can do some things with prebuilt kernel.
PREPARATION:
Please, after You pull it inside cm-13 source, GET VENDOR FILES by cd into device/htc/htc_a51ul and
Code:
./extract-files.sh
(with connected phone in adb enabled mode)
Second, please comment out in BoardConfig.mk following line:
Code:
TW_THEME := pure4
and uncomment:
Code:
TW_THEME := portrait_hdpi
as I wasn't release yet pure4 design skin to github.
Third, if You cannot handle "BSP" (and it's about 99% that You can't ) comment out:
Code:
TARGET_USES_QCOM_BSP := true
and remove flag
Code:
-DQCOM_BSP
from COMMON_GLOBAL_CFLAGS
Then You are ready to build (until first error come)
PLEASE, don't take advantage with this if You really don't know how to handle errors as I will NOT help or respond on PM's regarding help about building this.
When something come up, will make post/and/or attach possible working image.
Cheers
EDIT1: dts is attached, so if someone like to play with kernel... Check it out. I will put changes to 64bit kernel on My github soon with this device tree.
EDIT2: kernel is updated. You can grab it on MY GITHUB
EDIT3: BoardConfig.mk is changed, so no need to change twrp skin and BSP (steps second and third).
Thank you, btw. great job!
Great beginning!
So, things changed... Kernel updated, device tree updated, read.me updated.
Please be free to pull Kernel and make changes so We can got it working. I was made first steps and don't have so much time to make all this together work but if few of dev's come aboard and take work, We can make it work soon.
So i am quite interested in this device, don't own it yet so @fergy would appriciate it, if you could push vendor (too much work to do it all manually, especially the makefile ).
Thanks.
List of vendor files are under my github device tree... When you extract files, makefile will be builded under vendor/htc/devicename
fergy said:
List of vendor files are under my github device tree... When you extract files, makefile will be builded under vendor/htc/devicename
Click to expand...
Click to collapse
I know that, but since i don't own the device i can't pull blobs using the script (obviously), so it would be awesome if you could create the vendor (run the script), git init and push
btw i remade the device tree based on the htc a5, looks much better now: https://github.com/Thecrazyskull/device_htc_a51ul
Thanks.
Thecrazyskull said:
I know that, but since i don't own the device i can't pull blobs using the script (obviously), so it would be awesome if you could create the vendor (run the script), git init and push
btw i remade the device tree based on the htc a5, looks much better now: https://github.com/Thecrazyskull/device_htc_a51ul
Thanks.
Click to expand...
Click to collapse
https://github.com/Skorupa123/vendor_htc_htc_a51ul
Recently I uploaded it, so, enjoy!
Skorupa123 said:
https://github.com/Skorupa123/vendor_htc_htc_a51ul
Recently I uploaded it, so, enjoy!
Click to expand...
Click to collapse
Thanks a damn lot!!!
@Thecrazyskull Do you make cyanogenmod?
@Thecrazyskull
I know that fergy aboneded our project.. But you.. Do you continue? Can i help you?
Dragonfail said:
@Thecrazyskull
I know that fergy aboneded our project.. But you.. Do you continue? Can i help you?
Click to expand...
Click to collapse
I pretty much lost interest, especially since i dont want to develop without owning the device.
Thecrazyskull said:
I pretty much lost interest, especially since i dont want to develop without owning the device.
Click to expand...
Click to collapse
I can help you.. please.. continue...
Sent from my HTC Desire 820 using XDA Free mobile app
Dragonfail said:
I can help you.. please.. continue...
Sent from my HTC Desire 820 using XDA Free mobile app
Click to expand...
Click to collapse
Its a pain for myself, and i don't wanna go through that so i won't be developing for this device anymore unless i can get my hands on one (very unlikely)
What is thts device tree not understanding
chitranjn_k said:
What is thts device tree not understanding
Click to expand...
Click to collapse
This is not really the place to ask...
chitranjn_k said:
What is thts device tree not understanding
Click to expand...
Click to collapse
If you don't understand it you don't need it.
Wysłano z Tapatalk / Sent with Tapatalk
Any idea about htc desire 826 dual sim i.e. a52_dtul device tree ?
So I have successfully built OmniRom 8.1 Oreo for Shamu the zip file is a little over 500mb. The package flashes correctly but fails to boot. I have already tried to change the BoardConfig.mk file to be SeLinux=Permissive but it still fails to boot. My device is decrypted as well. What could be a source of the non boot issue other than what I have mentioned. This project is taking quite some time to complete.
HELP!!!!!
Does omnirom even have a 8.1 branch for shamu? I can't see it.
Elektroschmock said:
Does omnirom even have a 8.1 branch for shamu? I can't see it.
Click to expand...
Click to collapse
No it doesn't I am trying to bring it up, I know they don't officially support it for Oreo. They don't have a device maintainer for Shamu anymore. I have been using other device trees and filling in the required files for building Omni. Like I said I can get a successful build but in won't boot.
Rondeau79 said:
No it doesn't I am trying to bring it up, I know they don't officially support it for Oreo. They don't have a device maintainer for Shamu anymore. I have been using other device trees and filling in the required files for building Omni. Like I said I can get a successful build but in won't boot.
Click to expand...
Click to collapse
Well thats not how a bringup works. You need a ****load oft kernel and device commits for shamu to Boot Oreo.
The easiest way would be forking a working device and kernel repository...e.g. LineageOS. Next step would be adapting some makefiles and overlays.
Not much to do, as we have already done the Oreo bringup months ago.
Elektroschmock said:
Does omnirom even have a 8.1 branch for shamu? I can't see it.
Click to expand...
Click to collapse
Elektroschmock said:
Well thats not how a bringup works. You need a ****load oft kernel and device commits for shamu to Boot Oreo.
The easiest way would be forking a working device and kernel repository...e.g. LineageOS. Next step would be adapting some makefiles and overlays.
Not much to do, as we have already done the Oreo bringup months ago.
Click to expand...
Click to collapse
Yeah that's what I did. When the build first starts something in the vendor folder isn't being globed. It's only 99% of that folder that is accounted for. The build is successful but it just won't boot. I don't have much coding experience so this is really hard.
Rondeau79 said:
Yeah that's what I did. When the build first starts something in the vendor folder isn't being globed. It's only 99% of that folder that is accounted for. The build is successful but it just won't boot. I don't have much coding experience so this is really hard.
Click to expand...
Click to collapse
Do an -eng build and read logcat and dmesg via ADB. Usually you see whats wrong.
Rondeau79 said:
Yeah that's what I did. When the build first starts something in the vendor folder isn't being globed. It's only 99% of that folder that is accounted for. The build is successful but it just won't boot. I don't have much coding experience so this is really hard.
Click to expand...
Click to collapse
Hey how's it going? I know you've been trying hard to get an 8.1 Omni build running. FYI, @bthorne79 put out an Omni 8.1 build for Shamu back in December of last year. I tried it at the time and it was a nice build but if I remember correctly, the theming didn't work. I tried changing to a dark theme but it just stayed on default light theme. I always use a dark or black theme on Shamu and I'd rather not have to use substratum. Other than that, the rom ran very well.
Maybe give him a shout, after all you both have 79 in your name. Good luck, I definitely wouldn't mind seeing an Omni 8.1 build.
Mike T
webdroidmt said:
Hey how's it going? I know you've been trying hard to get an 8.1 Omni build running. FYI, @bthorne79 put out an Omni 8.1 build for Shamu back in December of last year. I tried it at the time and it was a nice build but if I remember correctly, the theming didn't work. I tried changing to a dark theme but it just stayed on default light theme. I always use a dark or black theme on Shamu and I'd rather not have to use substratum. Other than that, the rom ran very well.
Maybe give him a shout, after all you both have 79 in your name. Good luck, I definitely wouldn't mind seeing an Omni 8.1 build.
Mike T
Click to expand...
Click to collapse
Yeah this project has been a real headache! Nothing like before were most of the files and programming has been done. I am not done yet, I don't give up too easy. This has been quite an undertaking.
Follow this thread: https://forum.xda-developers.com/showpost.php?p=54118631&postcount=4
That'll give you an idea about what all things to consider while building for a device :fingers-crossed:
Nitin
Rondeau79 said:
Yeah this project has been a real headache! Nothing like before were most of the files and programming has been done. I am not done yet, I don't give up too easy. This has been quite an undertaking.
Click to expand...
Click to collapse
If you push your sources somewhere where we can see it, it should be easier for us to help you.
nitin.chobhe said:
Follow this thread: https://forum.xda-developers.com/showpost.php?p=54118631&postcount=4
That'll give you an idea about what all things to consider while building for a device :fingers-crossed:
Nitin
Click to expand...
Click to collapse
Yeah that guide is so outdated! I followed that kind of stuff years ago when I couldn't build from source. I have done many builds that boot for 3 devices. This is a different problem.
Elektroschmock said:
If you push your sources somewhere where we can see it, it should be easier for us to help you.
Click to expand...
Click to collapse
Yeah I am using Omni ROM source with device trees and kernel source from Lineage Oreo. I have modified files and make sources. I have all up to date vendor blobs cloned. There is no build errors just an issue with the system not booting. Pushing my source upstream would be to my personal GitHub account which I have never had to do. Usually I repo/clone source build and upload to Android File Host for working zips. I have never pushed anything up from my laptop!
Rondeau79 said:
Yeah that guide is so outdated! I followed that kind of stuff years ago when I couldn't build from source. I have done many builds that boot for 3 devices. This is a different problem.
Click to expand...
Click to collapse
Even though it is outdated it is still very much applicable. I linked that thread because you mentioned this.
Good that you know the problem. All the best!
Nitin
Rondeau79 said:
Yeah I am using Omni ROM source with device trees and kernel source from Lineage Oreo. I have modified files and make sources. I have all up to date vendor blobs cloned. There is no build errors just an issue with the system not booting. Pushing my source upstream would be to my personal GitHub account which I have never had to do. Usually I repo/clone source build and upload to Android File Host for working zips. I have never pushed anything up from my laptop!
Click to expand...
Click to collapse
It's not that you need to push it somewhere to get working zips, it's just for us to see your modifications.
Otherwise it is just guessing what you did.
Making it compile is one thing...making it work is a whole different story. When I did the Lineage Oreo bringup I had many things to fix untill it bootet properly.
Lineage's device tree for shamu depends on several other Lineage repositories. For example:
android_hardware_lineage_interfaces
android_hardware_qcom_gps
android_vendor_lineage
android_device_lineage_sepolicy
So just cloning the device repo without examining the reason for your 'bootloop' will get you nowhere.
I'd suggest you to do an engineering build which is easier to debug. Altought I would make this build permissive as selinux denials are a common reason for a bootloop.
How about trying a known working kernel such as popcorn? If the kernel works, you might be able to get some logs. And if you know whether your kernel is the problem, you are one step closer.
runekock said:
How about trying a known working kernel such as popcorn? If the kernel works, you might be able to get some logs. And if you know whether your kernel is the problem, you are one step closer.
Click to expand...
Click to collapse
If he is based of lineage's device tree, then Lineage's kernel is the best choice.
You should always be able to grab a log, no matter which kernel you are using.
Yeah willing to help out put your stuff up on git and give links
My webhost is down right meow but I can post my Oreo build I had of Omni here I didn't use Los trees i used aosp trees from camcory , joryb and mine cleanos
---------- Post added at 08:47 PM ---------- Previous post was at 08:28 PM ----------
i found my build i had it on afh if you want it to try this was early oreo so some things not fully functional i think gps was iffy https://www.androidfilehost.com/?fid=889964283620775520 i am syncing up omni oreo again for sure will help out if you want please pm
---------- Post added at 08:47 PM ---------- Previous post was at 08:47 PM ----------
nougat builds in that root folder also
bthorne79 said:
Yeah willing to help out put your stuff up on git and give links
Click to expand...
Click to collapse
My device and kernel tree GitHub link.
https://github.com/Rondeau79
Rondeau79 said:
My device and kernel tree GitHub link.
https://github.com/Rondeau79
Click to expand...
Click to collapse
Your probably going to want to fork the toolchains over that was used with cleanaosp
<!-- Prebuilts --> <project path="prebuilts/gcc/linux-x86/arm/arm-eabi-4.9" name="joryb/arm-eabi-7.x" clone-depth="1" remote="bb" revision="master"/> <project path="prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.9" name="joryb/arm-linux-androideabi-7.x" clone-depth="1" remote="bb" revision="master"/>
are there any roms for the N200 5G that would give better performance?
let me know
Try a GSI for now. One specific individual had been cranking on getting a device tree together, and if you have any experience, he could use your help.
rinnycoop121 said:
are there any roms for the N200 5G that would give better performance?
let me know
Click to expand...
Click to collapse
I recommend the CherishOS 12 GSI. It's a good GSI to start with if you're new.
twomad said:
I recommend the CherishOS 12 GSI. It's a good GSI to start with if you're new.
Click to expand...
Click to collapse
ok How do we flash roms on the N200 5G?
rinnycoop121 said:
ok How do we flash roms on the N200 5G?
Click to expand...
Click to collapse
There are multiple tutorials on the internet. Here's an example https://www.droidwin.com/install-android-12-gsi-roms-on-oneplus-nord-n200-5g/
Here is my guide:
GSIs on N200
The process of flashing alone is conventional, shouldn't even need a thread to detail, but still leaving a thread here for search indexing. With an unlocked BL, flash an ARM64 AB GSI within fastbootd, reboot to recovery, format userdata, reboot...
forum.xda-developers.com
Note that I do not recommend GSI's as I cannot get Magisk or VoLTE to work with them.
Custom ROMs will be coming soon, trees have been figured out and kinks are being ironed. More to come in the following days. Stay tuned
elginsk8r said:
Custom ROMs will be coming soon, trees have been figured out and kinks are being ironed. More to come in the following days. Stay tuned
Click to expand...
Click to collapse
great
rinnycoop121 said:
are there any roms for the N200 5G that would give better performance?
let me know
Click to expand...
Click to collapse
There are a few projects in the works. I personally am waiting to sell my current laptop to fund a ryzen 5 5600 dev rig which will allow me to build a larger variety ROMs as I add storage. I have it worked out where the price of my laptop will give me enough to order everything but storage drives. Settling with a single 16GB dimm to maximize upgradability while maintaining the best price to performance ratio currently available.
elginsk8r said:
Custom ROMs will be coming soon, trees have been figured out and kinks are being ironed. More to come in the following days. Stay tuned
Click to expand...
Click to collapse
hey buddy, i seen your trees, looking good. i just got my n200 and am waiting for unlock code. i built your rom with your trees and will flash once i'm unlocked. Thanks for all your hard work! as far as i can see you"re the only one working on n200 (dre9). do you accept pull requests rom and/or device side?
You can submit patches via review.evervolv.com gerrit. I am also on telegram if you have questions (just no eta requests). Kernel has been purged of Linux stable merges to be closer to the caf tag used. Trees are lineage compatible via 2 reverts if anyone wishes to build for lineage
I have a device tree and a kernel tree that can be used to compile LineageOS for the Nord N200. In its current state, only Wi-Fi is not working, which I have not been able to fix.
Because OOS12 came out for this device last week, I have to wait until OP releases the A12 kernel code, which could take anywhere between two and five months.
andr01dfr3ak said:
I have a device tree and a kernel tree that can be used to compile LineageOS for the Nord N200. In its current state, only Wi-Fi is not working, which I have not been able to fix.
Because OOS12 came out for this device last week, I have to wait until OP releases the A12 kernel code, which could take anywhere between two and five months.
Click to expand...
Click to collapse
WiFi is working with @elginsk8r trees. I'll run a build with your trees once I get a chance. I haven't been able to build much as work is crazy busy right now.
rc420head said:
WiFi is working with @elginsk8r trees. I'll run a build with your trees once I get a chance. I haven't been able to build much as work is crazy busy right now.
Click to expand...
Click to collapse
I also have a bunch of stuff on gerrit cleaning up previous issues and further refinement. Message me on telegram @andr01dfr3ak and maybe we can work together to avoid reinventing the wheel.
Not sure, but I got the DL link for the Android 12 OTA update...: " https://android.googleapis.com/packages/ota-api/package/2ae18bc3e36cfe74ae7f1b65d0f817043c57707a.zip "
AboveTG said:
Not sure, but I got the DL link for the Android 12 OTA update...: " https://android.googleapis.com/packages/ota-api/package/2ae18bc3e36cfe74ae7f1b65d0f817043c57707a.zip "
Click to expand...
Click to collapse
I've already started on getting LineageOS to work with the firmware included with this update, but without the kernel source code for said update, I cannot start testing.
In the meantime, my device and kernel trees are on the LineageOS GitHub repository now, so feel free to do unofficial builds and submit changes to the LineageOS Gerrit. You must be on OOS 11 firmware for it to work.
andr01dfr3ak said:
I've already started on getting LineageOS to work with the firmware included with this update, but without the kernel source code for said update, I cannot start testing.
In the meantime, my device and kernel trees are on the LineageOS GitHub repository now, so feel free to do unofficial builds and submit changes to the LineageOS Gerrit. You must be on OOS 11 firmware for it to work.
Click to expand...
Click to collapse
Alright not gonna lie man, im kind of new to all this, but I downgrade with the msm tool and ill try to figure out how to build. I know I need to fork it, but after that I have no clue what to do.
andr01dfr3ak said:
I've already started on getting LineageOS to work with the firmware included with this update, but without the kernel source code for said update, I cannot start testing.
In the meantime, my device and kernel trees are on the LineageOS GitHub repository now, so feel free to do unofficial builds and submit changes to the LineageOS Gerrit. You must be on OOS 11 firmware for it to work.
Click to expand...
Click to collapse
I found a payload dumper on github that works well. I renamed it payloaddumper+ because I felt it fit the tool name better. should work as a portable app I believe. Just run the .exe. Hope this helps.