Related
UnityROM-2 v.2.5.0
*****Discontinued.... No way to test actively till I have a functional build.*****
HTC One M7 Sprint Edition ( m7spr )
Development Section...
Want to contribute to the project or become team member?
Contact Me by PM here or leave a post detailing what you can and are willing to do for the projects' advancement.
My Github: https://github.com/LiquidSmokeX64
All current project sources can be found there .
ALSO MY FOOL-PROOF BUILD GUIDE & SCRIPTS ARE THERE FOR THOSE TOO IMPATIENT TO WAIT FOR MY NEXT RELEASE .
**Sources current as of version 2.5.0**
**10/06/2014**
Direct link to guide:
https://github.com/LiquidSmokeX64/Guides-Scripts
Note: Noob Friendly. If you're new to building ROMs or have never done it at all. I will help for as long as you maintain civility and focus on the project goals.
Installation errors out. Here is a pastebin of log saved after error
http://pastebin.com/fz15gwwn
Edit: I was able to install after removing that set perm line from updater. I will let ya know how it goes.
gruesomewolf said:
Installation errors out. Here is a pastebin of log saved after error
http://pastebin.com/fz15gwwn
Edit: I was able to install after removing that set perm line from updater. I will let ya know how it goes.
Click to expand...
Click to collapse
Ok. I just removed it too. My bad adaptation from Evo LTE. Nothing too bad luckily.
Reuploading the fixed version now.
LiquidSmokeX64 said:
Ok. I just removed it too. My bad adaptation from Evo LTE. Nothing too bad luckily.
Reuploading the fixed version now.
Click to expand...
Click to collapse
Seems to be running very well, once I got past that installation error....
Nice and smooth, especially with my aosp kernel...
gruesomewolf said:
Seems to be running very well, once I got past that installation error....
Nice and smooth, especially with my aosp kernel...
Click to expand...
Click to collapse
So. You're a kernel dev... Got a question for you. How do I add more CFLAGS to the makefile without it not booting or whatever? I've tried adding -O3 to the 2 places I know to put CFLAGS. Same place I put the -w so it would work with GCC 4.8
gruesomewolf said:
Seems to be running very well, once I got past that installation error....
Nice and smooth, especially with my aosp kernel...
Click to expand...
Click to collapse
Will you be releasing this kernel for the Evo 4G? [emoji14] Evo4gnoob here
LiquidSmokeX64 said:
So. You're a kernel dev... Got a question for you. How do I add more CFLAGS to the makefile without it not booting or whatever? I've tried adding -O3 to the 2 places I know to put CFLAGS. Same place I put the -w so it would work with GCC 4.8
Click to expand...
Click to collapse
I wouldn't say Im a kernel dev....more of a dabler...lol. I sent you a pm with my makefile so you can see adjustments I made for my kernels latest build (not yet publicly released)
Notorious said:
Will you be releasing this kernel for the Evo 4G? [emoji14] Evo4gnoob here
Click to expand...
Click to collapse
Umm....no I dont have any plans for that ATM
gruesomewolf said:
I wouldn't say Im a kernel dev....more of a dabler...lol. I sent you a pm with my makefile so you can see adjustments I made for my kernels latest build (not yet publicly released)
Umm....no I dont have any plans for that ATM
Click to expand...
Click to collapse
Was joking lol
Notorious said:
Was joking lol
Click to expand...
Click to collapse
So you're allowing the integration of it? Just to be clear.
So I'm not sure why but the kernel borked again. Maybe I need to go through one flag at a time? Or maybe forgot something....?
gruesomewolf said:
Seems to be running very well, once I got past that installation error....
Nice and smooth, especially with my aosp kernel...
Click to expand...
Click to collapse
Hey. Im having nothing but issues building it in the ROM so I was curious if you could tell me what I need to do after copying the msm8960 folder to a new place and adding in the makefile changes? Ive never built a kernel independently before but would like it to be a boot.img like normal so I can just replace the one in the ROM zip with the new one. Im sure it's pretty easy, just figured I'd ask you rather than comb through 80 guides saying different stuff lol.
LiquidSmokeX64 said:
Hey. Im having nothing but issues building it in the ROM so I was curious if you could tell me what I need to do after copying the msm8960 folder to a new place and adding in the makefile changes? Ive never built a kernel independently before but would like it to be a boot.img like normal so I can just replace the one in the ROM zip with the new one. Im sure it's pretty easy, just figured I'd ask you rather than comb through 80 guides saying different stuff lol.
Click to expand...
Click to collapse
Could you pm me with more info. Exact process of building, errors during build, any changes made to source, etc.
I'm gonna download your source later, together we should be able to figure this out.
gruesomewolf said:
Could you pm me with more info. Exact process of building, errors during build, any changes made to source, etc.
I'm gonna download your source later, together we should be able to figure this out.
Click to expand...
Click to collapse
I'm not seeing errors. Hell I removed everything but the -O3 spots and it still refused to boot. I dont know what the deal is....
Anytim I do ANYTHING to the kernel its dead, no matter how stupid it is.
gruesomewolf said:
Could you pm me with more info. Exact process of building, errors during build, any changes made to source, etc.
I'm gonna download your source later, together we should be able to figure this out.
Click to expand...
Click to collapse
BTW. The makefile is borked. And was curious if you knew how to build AOSP for this device? CM was pretty easy, I'd figure AOSP isn't too different. Then I can try to get Android L running once I have a working Android K to cross-reference to and make the version specific changes in device, kernel, vendor, qcom-common, and s4-common
LiquidSmokeX64 said:
So. You're a kernel dev... Got a question for you. How do I add more CFLAGS to the makefile without it not booting or whatever? I've tried adding -O3 to the 2 places I know to put CFLAGS. Same place I put the -w so it would work with GCC 4.8
Click to expand...
Click to collapse
When certain flags or 03 is added it creates a larger zImage. In order to compensate the boot.img needs needs modified, either by kernel installer or if baked in the rom hex edited. To change the ramdiskaddr.
Sent from my HTCONE using Tapatalk
thicklizard said:
When certain flags or 03 is added it creates a larger zImage. In order to compensate the boot.img needs needs modified, either by kernel installer or if baked in the rom hex edited. To change the ramdiskaddr.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Absolutely correct. And to elaborate on this just a bit more. Since your source building here, you can actually adjust the ramdiskadd with the scripts, considering it uses mkbootimg commands to build the boot.img.
An additional line in your devices board config, to give it a new ramdiskaddr size. Then an additional line in the build folder factory_ramdisk.mk , to handle the command for a new ramdiskaddr size should do the trick.
As for your other question about building aosp. I'm afraid that would be beyond my area of expertise. You would have significantly modify aosp code to allow for caf. It would be much harder then building cm, cause cm already has all the adjustments needed for caf devices
thicklizard said:
When certain flags or 03 is added it creates a larger zImage. In order to compensate the boot.img needs needs modified, either by kernel installer or if baked in the rom hex edited. To change the ramdiskaddr.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
gruesomewolf said:
Absolutely correct. And to elaborate on this just a bit more. Since your source building here, you can actually adjust the ramdiskadd with the scripts, considering it uses mkbootimg commands to build the boot.img.
An additional line in your devices board config, to give it a new ramdiskaddr size. Then an additional line in the build folder factory_ramdisk.mk , to handle the command for a new ramdiskaddr size should do the trick.
As for your other question about building aosp. I'm afraid that would be beyond my area of expertise. You would have significantly modify aosp code to allow for caf. It would be much harder then building cm, cause cm already has all the adjustments needed for caf devices
Click to expand...
Click to collapse
I read this and my eyes glaze over. But you are in good hands with these two helping you. :highfive:
Yeah I'm working on it guys. Read the integrated kernel building guide and trying that. But if I could just get it to build me the boot.IMG and get my ramdisk sizes and whatever I'm looking at where to edit it in the device/BoardConfig changed the defconfig to a custom one I made based off the original one from the working boot.IMG but changed the I/O scheduler & CPU governed defaults. Gave it a local name (UnityKernel-x.x.x) and am fighting its last issues. So if nothing else help building it independently might be the most useful now. So if nothing else I can push a new boot.img
My bad. It just says the boot partition size so I think I might be almost there
Hi! I'm currently making a somewhat desperate attempt at porting cm12 to the d950. I know some basic things, I once tried to make a custom kernel. I have the device and vendor trees set up, with the cm12 source and the files from the flex source, and I've been making some changes. Can anyone help point me in some direction from here?
dongdong6968 said:
Hi! I'm currently making a somewhat desperate attempt at porting cm12 to the d950. I know some basic things, I once tried to make a custom kernel. I have the device and vendor trees set up, with the cm12 source and the files from the flex source, and I've been making some changes. Can anyone help point me in some direction from here?
Click to expand...
Click to collapse
Okay, so now I need to run extract-files.sh, only problem is it doesn't exist. and from my understanding, I have to already be running cm12 to do this, which obviously is not possible. Can anyone help me get the proprietary blobs?
You're better off looking at the g2 proprietary blobs as when I was trying I had the most success with them on CM11, its a good starting point
So should I take those, then make changes to suit the flex?
Yeah, its a good place to start, but it won't suddenly make it compile, it helped sort a couple of issues once we'd got it compiling in the first place....
Try msg playfulgod and see if he will point you in the right direction
Alright, I've got something that looks pretty good going, but I can't do anything without a working kernel. And as I don't know much about kernels, could Someone possibly try to make one for cm12? Also, I have the blobs from my boyfriend's g2, and I've made a lot of changes, but I might need a little more guidance. Any help is appreciated.
Do you have coding experience though thats the question.
Either Build a dummy kernel or modify the original kernel from cm11 roms that your device has and built it alongside the system images.
CyanogenMod doesnt allow Building of only the system.
Youll need to modify the following:
Kernel Source
Device Trees
Vendor Files
A good way to look at what is required for a cm12 bringup is to check other similar devices with the same architecture and compare the changes and the sources you have on your pc.
Regards
Sent from my Xperia SP using xda Forum
I took programming classes, and there were a few units on android.
So I just forked the blobs from playfulgods repo, and I've made a lot of changes to tbe devices folder, as well as 'POSSIBLY' do something good as for a kernel, but I doubt that will work. How does one build the kernel to test it? Using linux btw. I have all of the dependencies and everything, could someone explain breakfast/brunch/lunch?
HEY SO I THIN K I HAVE SOMETHING THAT MIGHT WORK AFTER HAVING SOME REALLY SMART PEOPLE HELP sorry for caps, but now I have something in the out folder for zee, what do i do with this, and how do i make it flashable? could someone do it for me? and also, kernels?
dongdong6968 said:
HEY SO I THIN K I HAVE SOMETHING THAT MIGHT WORK AFTER HAVING SOME REALLY SMART PEOPLE HELP sorry for caps, but now I have something in the out folder for zee, what do i do with this, and how do i make it flashable? could someone do it for me? and also, kernels?
Click to expand...
Click to collapse
I can write and add the meta-inf folders to make it flashable. But I don't do kernels
mattwheat said:
I can write and add the meta-inf folders to make it flashable. But I don't do kernels
Click to expand...
Click to collapse
I would really appreciate that! What means should I take of sending you the output?
dongdong6968 said:
I would really appreciate that! What means should I take of sending you the output?
Click to expand...
Click to collapse
I see 2 things with the Out Folder having problems.
1) What has the Build System Generate in the out folder?
2) CM12 will generate a pre configured Zip File if it doesn't, the build failed
Sent from my Huashan Device utilizing RR Milestone 1
Furrydaus said:
I see 2 things with the Out Folder having problems.
1) What has the Build System Generate in the out folder?
2) CM12 will generate a pre configured Zip File if it doesn't, the build failed
Sent from my Huashan Device utilizing RR Milestone 1
Click to expand...
Click to collapse
If anyone wants to take a look I zipped the out folder.
So you're going to tell us you zipped the folder but you're not going to tell us where it is? Lol
Sent from my Huashan Device utilizing RR Milestone 1
dongdong6968 said:
So I just forked the blobs from playfulgods repo, and I've made a lot of changes to tbe devices folder, as well as 'POSSIBLY' do something good as for a kernel, but I doubt that will work. How does one build the kernel to test it? Using linux btw. I have all of the dependencies and everything, could someone explain breakfast/brunch/lunch?
Click to expand...
Click to collapse
The device tree repos found in lg-devs github are the correct ones just change kernel source to our stock kernel and edit z.mk and verndor files can be extracted with the ./extract-fikes.sh script . But our kernel needs to be updated a little which i am working on mostly caf header need to be added to include/Linux for media and display. I trued using msm8974 kernel but our kernel has specific blobs we use which is easier to use stock kernel.
---------- Post added at 06:26 PM ---------- Previous post was at 06:16 PM ----------
dongdong6968 said:
HEY SO I THIN K I HAVE SOMETHING THAT MIGHT WORK AFTER HAVING SOME REALLY SMART PEOPLE HELP sorry for caps, but now I have something in the out folder for zee, what do i do with this, and how do i make it flashable? could someone do it for me? and also, kernels?
Click to expand...
Click to collapse
What you mean you got something lol. We just need to update our stock kernel which you can have a better understanding. Of what i mean visit lg-devs for z repos . we should stick to stock kernel doe.
dongdong6968 said:
I would really appreciate that! What means should I take of sending you the output?
Click to expand...
Click to collapse
Upload it to drive then message me with a link
mattwheat said:
Upload it to drive then message me with a link
Click to expand...
Click to collapse
https://www.dropbox.com/s/dx3sjp8bq720bkn/out.zip?dl=0
Furrydaus said:
So you're going to tell us you zipped the folder but you're not going to tell us where it is? Lol
Sent from my Huashan Device utilizing RR Milestone 1
Click to expand...
Click to collapse
Sorry, completely forgot. https://www.dropbox.com/s/dx3sjp8bq720bkn/out.zip?dl=0
Hello XDA,
As all of you may know there is a 4G LTE version of the Moto G 2nd Generation, better known under the model number XT1072 and XT1079. Unfortunately almost all ROMs are created for the titan. While the titan ROMs boot just fine because of the almost exact HW, when installing those ROMS we don't get 4G and the speakers and earpeace, especially while calling, get unusable.
So instead of sitting on my butt and asking LUK to develop a 4G patch, can anyone guide me ? I know how to setup the SDK and know the theory about compiling from source but have never done it. Do we have to recompile something or can I just replace certain files with some other files from the (one and only) CM12.1 port for the THEA ?
This must be doable I think.
soulaiman said:
Hello XDA,
As all of you may know there is a 4G LTE version of the Moto G 2nd Generation, better known under the model number XT1072 and XT1079. Unfortunately almost all ROMs are created for the titan. While the titan ROMs boot just fine because of the almost exact HW, when installing those ROMS we don't get 4G and the speakers and earpeace, especially while calling, get unusable.
So instead of sitting on my butt and asking LUK to develop a 4G patch, can anyone guide me ? I know how to setup the SDK and know the theory about compiling from source but have never done it. Do we have to recompile something or can I just replace certain files with some other files from the (one and only) CM12.1 port for the THEA ?
This must be doable I think.
Click to expand...
Click to collapse
It's easy but I'm not going to help in dirty ports. Build roms from source instead, this is my recommendation.
If you want to learn how to build roms from source I can help you but you'll need to have Linux machine to do that.
LuK1337 said:
It's easy but I'm not going to help in dirty ports. Build roms from source instead, this is my recommendation.
If you want to learn how to build roms from source I can help you but you'll need to have Linux machine to do that.
Click to expand...
Click to collapse
Thanks for the reply Luk, I also think that building from source is the same. I have followed many, many guides but somehow the part where I have to point to the thea specific HW blobs fails. The extract-files.sh points to ./../../$VENDOR/msm8226-common/setup-makefiles.sh [email protected] wich I understand is the motorola folder in the WORKING_DIRECTORY. Somehow I can't find the right repo on github to point it at.
Sorry for the noobish Q... There is a first time for everything.
EDIT: I wanted to say that I think that porting from source is better, not the same.
soulaiman said:
Thanks for the reply Luk, I also think that building from source is the same. I have followed many, many guides but somehow the part where I have to point to the thea specific HW blobs fails. The extract-files.sh points to ./../../$VENDOR/msm8226-common/setup-makefiles.sh [email protected] wich I understand is the motorola folder in the WORKING_DIRECTORY. Somehow I can't find the right repo on github to point it at.
Sorry for the noobish Q... There is a first time for everything.
EDIT: I wanted to say that I think that porting from source is better, not the same.
Click to expand...
Click to collapse
You could use blobs from TheMuppets instead: https://github.com/TheMuppets/proprietary_vendor_motorola
LuK1337 said:
You could use blobs from TheMuppets instead: https://github.com/TheMuppets/proprietary_vendor_motorola
Click to expand...
Click to collapse
Thanks !!
I was really confused and got the CM12 branch instead the first time. Lol now I feel like a noob haha (wich I am when it comes to developing).
Will post here if I have any Questions/errors (that google can't help me with).
:good:
soulaiman said:
Thanks !!
I was really confused and got the CM12 branch instead the first time. Lol now I feel like a noob haha (wich I am when it comes to developing).
Will post here if I have any Questions/errors (that google can't help me with).
:good:
Click to expand...
Click to collapse
Also don't use git clone manually, make your local_manifests xml instead.
LuK1337 said:
Also don't use git clone manually, make your local_manifests xml instead.
Click to expand...
Click to collapse
Oh okay, I will look into that in a minute.
Now I got an issue that really got my head hurting... When I do the lunch command, my Moto G isn't in the list of devices... What Am I doing wrong ?
I have got a directory called thea in WORKING_DIRECTORY/device/moto/thea
I have got also an old thea directory (cm12.1) in WORKING_DIRECTORY/thea and WORKING_DIRECTORY/thea2
All the blobs from TheMuppits repo are in de device/moto/thea dir
All the poperiatary blobs are also in the XT907 dir...
I've done the
Code:
cd /device/moto/thea
init android-5.1.1_rx
repo sync
and let it finish without errors.
Once I get over this I will be good to go.
Oh, and thanks for sharing the knowledge !
soulaiman said:
Oh okay, I will look into that in a minute.
Now I got an issue that really got my head hurting... When I do the lunch command, my Moto G isn't in the list of devices... What Am I doing wrong ?
I have got a directory called thea in WORKING_DIRECTORY/device/moto/thea
I have got also an old thea directory (cm12.1) in WORKING_DIRECTORY/thea and WORKING_DIRECTORY/thea2
All the blobs from TheMuppits repo are in de device/moto/thea dir
All the poperiatary blobs are also in the XT907 dir...
I've done the
Code:
cd /device/moto/thea
init android-5.1.1_rx
repo sync
and let it finish without errors.
Once I get over this I will be good to go.
Oh, and thanks for sharing the knowledge !
Click to expand...
Click to collapse
Your directories are bit off, it should be looking like this.
CM/device/motorola/msm8226-common
CM/device/motorola/thea
CM/device/qcom/sepolicy
CM/device/qcom/common
CM/kernel/mototola/msm8226
CM/vendor/motorola
Don't forget about rest of CM source :3
LuK1337 said:
Your directories are bit off, it should be looking like this.
CM/device/motorola/msm8226-common
CM/device/motorola/thea
CM/device/qcom/sepolicy
CM/device/qcom/common
CM/kernel/mototola/msm8226
CM/vendor/motorola
Don't forget about rest of CM source :3
Click to expand...
Click to collapse
Oh okay got ya. Do I have to do some kind of refresh command when I touch the folders ?
soulaiman said:
Oh okay got ya. Do I have to do some kind of refresh command when I touch the folders ?
Click to expand...
Click to collapse
If you're building CM then all you have to do is to get vendor, do envsetup.sh and just brunch thea.
LuK1337 said:
If you're building CM then all you have to do is to get vendor, do envsetup.sh and just brunch thea.
Click to expand...
Click to collapse
I'm trying to build an AOSP build like yours to learn. I'm following this guide:
http://forum.xda-developers.com/chef-central/android/tutorial-compile-lollipop-ubuntu-t2929410
I guess it is similar in steps as what you described ?
Even with all the files in the correct directories when I exec the lunch command it doesn't list the moto G. See screenshot.
soulaiman said:
I'm trying to build an AOSP build like yours to learn. I'm following this guide:
http://forum.xda-developers.com/chef-central/android/tutorial-compile-lollipop-ubuntu-t2929410
I guess it is similar in steps as what you described ?
Even with all the files in the correct directories when I exec the lunch command it doesn't list the moto G. See screenshot.
Click to expand...
Click to collapse
You won't get clean AOSP to build, also u messed up directories as you put vendor in device.
If you have hangouts you can add me ( https://plus.google.com/108108436166506337243 ) so I could help you live.
LuK1337 said:
You won't get clean AOSP to build, also u messed up directories as you put vendor in device.
If you have hangouts you can add me ( https://plus.google.com/108108436166506337243 ) so I could help you live.
Click to expand...
Click to collapse
Thanks for all the help man, really appreciate it !
Yeah stupid fault of my part. Will try it.
About Hangouts: My hangouts app allways FC's on me so that will be for another day. I'll add you asap ! Thanks!
Also it is 1:45AM here so
soulaiman said:
Thanks for all the help man, really appreciate it !
Yeah stupid fault of my part. Will try it.
About Hangouts: My hangouts app allways FC's on me so that will be for another day. I'll add you asap ! Thanks!
Also it is 1:45AM here so [emoji14]
Click to expand...
Click to collapse
K, I'm in the same time zone fyi.
According to Project Treble lead Iliyan Malchev,
Malchev says that Treble standardizes Android hardware support to such a degree that generic Android builds compiled from AOSP can boot and run on every Treble device. In fact, these “raw AOSP” builds are what will be used for some of the CTS testing Google requires all Android OEMs to pass in order to license the Google apps—it’s not just that things should work, they are required to work.
Click to expand...
Click to collapse
Now that there's an Oreo beta for the Essential Phone that supports Treble, perhaps this can be used to further development on the device.
/u/foremi on Reddit confirmed that simply flashing a Pixel 2 system and boot image to the device is not enough, as it fails to boot, so the question is what constitutes a generic AOSP build?
I don't have Linux installed right now or I'd build it myself, but I suspect that building it with the simple target device of "generic" might be what Malchev is referring to.
If any devs would like to test this theory or give their input as to how they think this actually works I think it'd be incredibly useful for not just Essential phone development, but Android development as a whole.
EDIT: @phhusson confirms that the target device should be aosp_arm64_ab
FWIW "generic AOSP build" is really what it says it is.
I have access to the "Google certification generic AOSP build" (that's weirdly not public, I don't know why), so I gave it a try. (Edit: So if the ROM was Treble-certified, it would work)
I get the Android bootanimation, but that's all (I have to say that's still a big step forward compared to other Android versions
Looking at the logs, I see a loop of crash because of: /vendor/bin/hw/[email protected]
Which I guess is the HAL for the accessories, but that doesn't seem to be the reason for the crash
The reason of the crash, seem to be this:
11-15 12:59:04.491 5331 5331 F MediaProfiles: frameworks/av/media/libmedia/MediaProfiles.cpp:329 CHECK(quality != -1) failed.
in CAF, frameworks/av/media/libmedia/MediaProfiles.cpp we see vendor-specific (i.e. not in AOSP) quality attributes, like "vga"
And it is defined by Essential's framework (in vendor/etc/media_profiles_V1_0.xml)
Considering there are media_profiles xml files, I'd guess that _V1_0 is supposed to only contain AOSP-capable qualities
Edit2: The fingerprint of "certification generic AOSP", is Android/aosp_arm64_ab/generic_arm64_ab:8.0.0/OTR1.171023.001/4412360:userdebug/test-keys
So my guess to build this is that lunch aosp_arm64_ab && make should work
Edit3: the generated fingerprint is too long to build, needs to do make BUILD_NUMBER=4412360
Edit4: To make the situation more clear:
- NO, current ROM is NOT Treble capable
- BUT, almost everything is available for that. Every HAL is using "hwbinder" which is the basis, and most work needed for Treble
Also, I've seen some reddit comment mentioning boot.img.
Current version of Treble only concerns system.img, and NOT boot.img!
Future version are supposed to have generic boot.img as well, but that's not to be expected before at the very least Android P.
phhusson said:
Edit2: The fingerprint of "certification generic AOSP", is Android/aosp_arm64_ab/generic_arm64_ab:8.0.0/OTR1.171023.001/4412360:userdebug/test-keys
So my guess to build this is that lunch aosp_arm64_ab && make should work
Click to expand...
Click to collapse
I was gonna link to the aosp_arm64 make file but it said it was specifically for the emulator so I wasn't sure, that's good to know though.
phhusson said:
Also, I've seen some reddit comment mentioning boot.img.
Current version of Treble only concerns system.img, and NOT boot.img!
Future version are supposed to have generic boot.img as well, but that's not to be expected before at the very least Android P.
Click to expand...
Click to collapse
Thanks for this, I suspected such but couldn't find a clear answer from Google on the matter so I suggested trying the boot.img as well just in case.
Now, someone has to test this on a different Treble device such as the Pixel or Pixel 2. I'm thinking MAYBE because the Oreo build for essential is just a beta its treble implementation isn't finished and hasn't passed Google's CTS requirements to boot the generic aosp image. Perhaps this will change in the final build.
For what it's worth I only have a LG V20 right now which currently doesn't support Treble, so I'm pretty useless as far as testing anything goes, but if this is figured out it'll greatly influence what device I go with when I eventually upgrade.
Now, someone has to test this on a different Treble device such as the Pixel or Pixel 2.
Click to expand...
Click to collapse
Yup. I feel like Treble deserves its own "device" section in XDA
I'm afraid I'm working on something that other people already did on other devices...
I'm thinking MAYBE because the Oreo build for essential is just a beta its treble implementation isn't finished and hasn't passed Google's CTS requirements to boot the generic aosp image. Perhaps this will change in the final build.
Click to expand...
Click to collapse
That's my guess as well.
Interesting stuff. Excited to hear updates on this. PM me if you make a breakthrough and want a feature
MishaalRahman said:
Interesting stuff. Excited to hear updates on this. PM me if you make a breakthrough and want a feature
Click to expand...
Click to collapse
There's not much I can do on my end sadly, without a Treble capable device, but if anyone is interested in trying this on another device with a mainline Treble-enabled Oreo build I'd install Linux and post the build up so just let me know
PhantomGamers said:
There's not much I can do on my end sadly, without a Treble capable device, but if anyone is interested in trying this on another device with a mainline Treble-enabled Oreo build I'd install Linux and post the build up so just let me know
Click to expand...
Click to collapse
Google Pixel/Pixel 2 will do, yes?
MishaalRahman said:
Google Pixel/Pixel 2 will do, yes?
Click to expand...
Click to collapse
Yeah they should be fine
PhantomGamers said:
Yeah they should be fine
Click to expand...
Click to collapse
Alright, I'll find you some testers
MishaalRahman said:
Alright, I'll find you some testers
Click to expand...
Click to collapse
Here's the system image if you find anyone, it's a straight fresh build of aosp branch 8.0.0r34
If it doesn't work it's possible that I messed the build up, but it should be fine.
Can someone running the Oreo beta post their results running this app?
If the beta isn't CTS compliant, we should know.
PhantomGamers said:
Can someone running the Oreo beta post their results running this app?
If the beta isn't CTS compliant, we should know.
Click to expand...
Click to collapse
Hero you go
TheDethEgineer said:
Hero you go
Click to expand...
Click to collapse
Thanks a lot!
This is interesting... according to Malchev, CTS testing REQUIRES a device to boot a generic AOSP image, and yet the Oreo build is CTS certified and doesn't boot the AOSP image...
PhantomGamers said:
Thanks a lot!
This is interesting... according to Malchev, CTS testing REQUIRES a device to boot a generic AOSP image, and yet the Oreo build is CTS certified and doesn't boot the AOSP image...
Click to expand...
Click to collapse
That's true only for new devices, not for devices upgrading for nougat to oreo.
I wasn't aware there was an AMA yesterday... Too bad we could have asked.
Tester with OG Pixel XL says it gives invalid zip file format error when trying to flash in TWRP
MishaalRahman said:
Tester with OG Pixel XL says it gives invalid zip file format error when trying to flash in TWRP
Click to expand...
Click to collapse
How about flashing the system image directly from a Pixel 2 XL?
MishaalRahman said:
Tester with OG Pixel XL says it gives invalid zip file format error when trying to flash in TWRP
Click to expand...
Click to collapse
It's not a TWRP flashable zip, you have to extract the system.img from the zip and flash it with fastboot in the bootloader.
Also as @PresidentMcCain said, seeing the results of flashing a pixel 2 xl system image would be interesting too.
Oh and make sure the tester's OG pixel is already running Oreo before trying. Just adding that in case they didn't upgrade yet.
PhantomGamers said:
It's not a TWRP flashable zip, you have to extract the system.img from the zip and flash it with fastboot in the bootloader.
Also as @PresidentMcCain said, seeing the results of flashing a pixel 2 xl system image would be interesting too.
Oh and make sure the tester's OG pixel is already running Oreo before trying. Just adding that in case they didn't upgrade yet.
Click to expand...
Click to collapse
Ah, I see.
Do you happen to know the exact command? I'm not that familiar with A/B partition devices and how that changes fastboot commands.
MishaalRahman said:
Ah, I see.
Do you happen to know the exact command? I'm not that familiar with A/B partition devices and how that changes fastboot commands.
Click to expand...
Click to collapse
I believe it should work as normal
fastboot flash system system.img
EDIT: Apparently with the A/B partitions you'd do fastboot flash system_b system_other.img to flash the b partition, but the aosp build didn't include a system_other.img so I'm assuming perhaps it's not necessary
So far I still can't find anyone willing to flash this on their Pixel haha. People are really hesitant to flash stuff on the Pixel it seems. Times are not like they used to be =\
I'm looking for brave souls with spare Moto g5s. I made build but i cannot test it because its my daily device.
I cannot give a warranty that this build will not hardbrick your device or even boot up.
So if u want to take a risk and try it, send me pm or write comment under this post and i will provide link for zip.
Thanks in advance
I have a G5S but it's my daily phone too...
Please someone be brave
My mother is using my g5s, I will post it on telegram group
Just for curiosity: How did you manage to port this ROM for G5S?
wiktorek140 said:
I'm looking for brave souls with spare Moto g5s. I made build but i cannot test it because its my daily device.
I cannot give a warranty that this build will not hardbrick your device or even boot up.
So if u want to take a risk and try it, send me pm or write comment under this post and i will provide link for zip.
Thanks in advance
Click to expand...
Click to collapse
Hi, can you talk with @rssxda1 on telegram?
Probably i can. What do you mean? I just take cedric device tree, rename what needed. Replace binaries and compile it
Mutcholoko said:
Just for curiosity: How did you manage to port this ROM for G5S?
Click to expand...
Click to collapse
And I didn't port for now. I just build rom for montana, and need someone for test it. I will name it "porting" when at least it boot
wiktorek140 said:
Probably i can. What do you mean? I just take cedric device tree, rename what needed. Replace binaries and compile it
Click to expand...
Click to collapse
Super cool. I always wanted to learn how to do it.
I actually understand the process itself, but I can't understand this binaries and kernel part. Do you recommend any place to learn this?
wiktorek140 said:
Probably i can. What do you mean? I just take cedric device tree, rename what needed. Replace binaries and compile it
Click to expand...
Click to collapse
FIY only camera blobs need to be replaced, and the sensors blobs (cedric uses motosh and montana uses sensors.qcom). i already made an treee for montana, but i had ****ed up the sensors. github.com/motorola-common . i think its best for you to make your tree based on the sanders tree, and use the common vendor i made on github.com/kalil-devices . for doing the bringup based on the sanders tree you will need to get the mixer paths, the media configs, the camera configs, and the sensor configs, and the camera blobs. thats pretty much it. good luck.
---------- Post added at 10:56 AM ---------- Previous post was at 10:54 AM ----------
wiktorek140 said:
And I didn't port for now. I just build rom for montana, and need someone for test it. I will name it "porting" when at least it boot
Click to expand...
Click to collapse
if you install an cedric build and an montana arm64 kernel, it will boot BTW. camera and sensors will be broken, but because motosh is initialized, sensors won't prevent the device from booting
KalilDev said:
FIY only camera blobs need to be replaced, and the sensors blobs (cedric uses motosh and montana uses sensors.qcom). i already made an treee for montana, but i had ****ed up the sensors. github.com/motorola-common . i think its best for you to make your tree based on the sanders tree, and use the common vendor i made on github.com/kalil-devices . for doing the bringup based on the sanders tree you will need to get the mixer paths, the media configs, the camera configs, and the sensor configs, and the camera blobs. thats pretty much it. good luck.
---------- Post added at 10:56 AM ---------- Previous post was at 10:54 AM ----------
if you install an cedric build and an montana arm64 kernel, it will boot BTW. camera and sensors will be broken, but because motosh is initialized, sensors won't prevent the device from booting
Click to expand...
Click to collapse
But i just ask about someone who will test it not how to fix something what i dont know it even work. And device tree from motorola-common don't even compile for me(wifi errors that something missing- i can't find solution)
Solved. My build dont even boot xD
Maybe next time
wiktorek140 said:
Solved. My build dont even boot xD
Maybe next time
Click to expand...
Click to collapse
Bad
I volunteer
wiktorek140 said:
I'm looking for brave souls with spare Moto g5s. I made build but i cannot test it because its my daily device.
I cannot give a warranty that this build will not hardbrick your device or even boot up.
So if u want to take a risk and try it, send me pm or write comment under this post and i will provide link for zip.
Thanks in advance
Click to expand...
Click to collapse
Give the link of the rom I happy ? to try in my phone ? now
Because I looking for 64 bit rom for moto g5s device
Send me the link I volunteer
KalilDev said:
FIY only camera blobs need to be replaced, and the sensors blobs (cedric uses motosh and montana uses sensors.qcom). i already made an treee for montana, but i had ****ed up the sensors. github.com/motorola-common . i think its best for you to make your tree based on the sanders tree, and use the common vendor i made on github.com/kalil-devices . for doing the bringup based on the sanders tree you will need to get the mixer paths, the media configs, the camera configs, and the sensor configs, and the camera blobs. thats pretty much it. good luck.
Click to expand...
Click to collapse
List me the blobs you need and I can pull them for you. My phone runs official Oreo 8.1.
Edit: You already made a list, lol. Just be more specific. Which files, exactly, need to be pulled?
Kamin4ri said:
List me the blobs you need and I can pull them for you. My phone runs official Oreo 8.1.
Edit: You already made a list, lol. Just be more specific. Which files, exactly, need to be pulled?
Click to expand...
Click to collapse
I think it require only files from /vendor to make camera work( i dont see any device specific file in /system), i have stock oreo too so i have all required files, and later i can push to github what i achieved
Kamin4ri said:
List me the blobs you need and I can pull them for you. My phone runs official Oreo 8.1.
Edit: You already made a list, lol. Just be more specific. Which files, exactly, need to be pulled?
Click to expand...
Click to collapse
i have montana stock for ages now. i have a montana vendor set up too.
KalilDev said:
i have montana stock for ages now. i have a montana vendor set up too.
Click to expand...
Click to collapse
Hmm, have u pushed it to github or it is a redo branch on motorola common?
Today will be new build, testers needed again