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
Related
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
This is not my work this a reply i got from a guy when i posted in the sony developers forum ...I hope someone finds this useful:angel: .And since i m a new user i can post links for some stupid reasons...so i will get creative
by fzort
Kernel source for the Xperia E1 is available as a tarball on the "Xperia open source archives" site. I'm running a custom-built kernel on my Xperia E1 (D2114). I documented what I did here:
[https://
github.com
/mpersano
/xperia-e1-kernel-patches
/blob
/master
/README.md]
https://github.com/mpersano/xperia-e1-kernel-patches/blob/master/README.md
This is for KK or JB4.3?
Since im starting development for this device, idk much and i not read actual progress. @Kizoky you can resume progress for me?
Caio99BR said:
This is for KK or JB4.3?
Since im starting development for this device, idk much and i not read actual progress. @Kizoky you can resume progress for me?
Click to expand...
Click to collapse
This is for KK kernel, but I couldn't not build kernel because I'm still a rookie
Camera drivers exists for MSM8610(Xperia E1's chipset) on sonyxperiadev Github
Recovery exists (you can find PhilZ recovery in this forum)
what is still missing is a working Device tree, and vendor libs (and of course a cm compatible kernel)
Kizoky said:
This is for KK kernel, but I couldn't not build kernel because I'm still a rookie
Camera drivers exists for MSM8610(Xperia E1's chipset) on sonyxperiadev Github
Recovery exists (you can find PhilZ recovery in this forum)
what is still missing is a working Device tree, and vendor libs (and of course a cm compatible kernel)
Click to expand...
Click to collapse
Ok, but for now a kernel working in Stock is good, so how i can unpack boot.img?
Enviado de meu E435 (L3 II Dual) usando Tapatalk
Use this:
Zsenyka said:
Use this:
Click to expand...
Click to collapse
Edited: The Bootloader is locked, so the boot.img is "Encripted", and no way to unpack this, i will unlock this.
Ok, i changed boot.img, now i have CWM from boot, and bootsrap.
I tried to boot it, but this get bootloop, the bootanimation is loaded but bootloop, maybe dt.img.
I cant access dmesg command. @Kizoky any tip?
---------- Post added at 10:44 PM ---------- Previous post was at 10:44 PM ----------
https://github.com/Caio99BR/android_kernel_sony_falconss
Caio99BR said:
Ok, i changed boot.img, now i have CWM from boot, and bootsrap.
I tried to boot it, but this get bootloop, the bootanimation is loaded but bootloop, maybe dt.img.
I cant access dmesg command. @Kizoky any tip?
Click to expand...
Click to collapse
Hi! I'm the owner of the github repo mentioned at the top of this thread.
Getting a working ramdisk took me a while. I think that what finally worked was downloading an official firmware image with XperiFirm (you don't even need to wait for it to finish downloading the full image - one of the first files downloaded is the kernel one, containing boot.img), then I extracted boot.img with the unofficial XPERIA flash tool, then extracted the ramdisk. (The kernel command line I used is the same one in the official boot.img, by the way.) As for the device tree image, you can build it from the kernel sources.
Note that boot.img on this phone has a device tree blob appended to the end. I wrote a small script to unpack the official boot.img and compare it to the one that I built and check if I was doing everything right (can't post links as I'm a new user, but it's linked in the README.md file linked above).
I'll try to add more details to those instructions when I have some time (I didn't think anyone else would be interested in building a kernel for this cheap phone ). By the way, I use the E1 with a custom kernel as my main personal phone and it works fine (for a 512M phone), kudos to Sony for not compromising the quality of even their lowest end model.
I think everyone is interested in making this phone better
Since July 2014 we tried porting Cyanogenmod without success, now last year we modified a Moto E ROM and made it work with E1, only the ril is not working
So sad that Sony didn't made this phone even better
So the device tree is located in the ramdisk?
Kizoky said:
I think everyone is interested in making this phone better
Since July 2014 we tried porting Cyanogenmod without success, now last year we modified a Moto E ROM and made it work with E1, only the ril is not working
So sad that Sony didn't made this phone even better
So the device tree is located in the ramdisk?
Click to expand...
Click to collapse
The device tree is located after the ramdisk in boot.img, but you can build it from the kernel sources provided by Sony. The `msm8610-v2-mtp.dtb` make target will build the device tree blob. Then mkqcdtbootimg will build a boot.img containing kernel + ramdisk + device tree blob. The only thing that you need for this which is not provided by Sony (well, other than more detailed build instructions...) is a ramdisk image, I had to extract it from the stock firmware...
If you want to split boot.img into kernel / ramdisk / device tree, you can use this script: github.com/mpersano/bootimg-tools/blob/master/split-bootimage.py
Good luck!
fzort said:
The device tree is located after the ramdisk in boot.img, but you can build it from the kernel sources provided by Sony. The `msm8610-v2-mtp.dtb` make target will build the device tree blob. Then mkqcdtbootimg will build a boot.img containing kernel + ramdisk + device tree blob. The only thing that you need for this which is not provided by Sony (well, other than more detailed build instructions...) is a ramdisk image, I had to extract it from the stock firmware...
If you want to split boot.img into kernel / ramdisk / device tree, you can use this script: github.com/mpersano/bootimg-tools/blob/master/split-bootimage.py
Good luck!
Click to expand...
Click to collapse
I've been trying to get that script work like ages
Does it require Linux, or just Python?
EDIT: nvm, I figured it out
So is CM for E1 finally possible or just custom kernel?
@fzort @Kizoky i make this booting with the stock dt blob (device tree means the Android Device Tree, and this is totally diff, use "dt blob")
See my changes in https://github.com/Caio99BR/android_kernel_sony_falconss
Ah, only with msm8610-v2-mtp.dtb this works too, i tested after.
("I not reply more earlier because the phone is from my father and yesterday ran out of energy.")
The ramdisks works and dt blobs too.
The screenshot
Caio99BR said:
@fzort @Kizoky i make this booting with the stock dt blob (device tree means the Android Device Tree, and this is totally diff, use "dt blob")
See my changes in https://github.com/Caio99BR/android_kernel_sony_falconss
Ah, only with msm8610-v2-mtp.dtb this works too, i tested after.
("I not reply more earlier because the phone is from my father and yesterday ran out of energy.")
The ramdisks works and dt blobs too.
The screenshot
Click to expand...
Click to collapse
I saw you are doing the device part of E1 too
If you need any help just ask me (or tests)
Kizoky said:
I saw you are doing the device part of E1 too
If you need any help just ask me (or tests)
Click to expand...
Click to collapse
Ok man, im trying to do kernel fully working (solved problem of dt blobs. We cant pack qrd dt, so comment build of then), and zip easy flashing, but not working at moment, my father will get crazy when him try to play FM Radio.
After i will merge code to a CAF Linux Kernel, so this is more easy to update.
By last finish the Android Device Tree with a E1 Caf Kernel.
I will try to post the custom kernel.
Im thinking in VeeSSKernel (Since my kernel of L3II is VeeKernel), what do you think?
Enviado de meu E435 (L3 II Dual) usando Tapatalk
Caio99BR said:
Ok man, im trying to do kernel fully working (solved problem of dt blobs. We cant pack qrd dt, so comment build of then), and zip easy flashing, but not working at moment, my father will get crazy when him try to play FM Radio.
After i will merge code to a CAF Linux Kernel, so this is more easy to update.
By last finish the Android Device Tree with a E1 Caf Kernel.
I will try to post the custom kernel.
Im thinking in VeeSSKernel (Since my kernel of L3II is VeeKernel), what do you think?
Enviado de meu E435 (L3 II Dual) usando Tapatalk
Click to expand...
Click to collapse
Would be really great
We still don't have a custom kernel (only Stock kernel with PhilZ)
I can't wait to see it
Kizoky said:
Would be really great
We still don't have a custom kernel (only Stock kernel with PhilZ)
I can't wait to see it
Click to expand...
Click to collapse
We have a problem, the TV is not working anymore, idk why
I will check it, we need TV Support working, or i need it, since my father use it
EDIT: The problem is inside kernel or ramdisk.
it's amazing .. Very good work .. Congratulations friends??
racer.z said:
it's amazing .. Very good work .. Congratulations friends����
Click to expand...
Click to collapse
@Kizoky TV is fixed
Edit: THANKS, i forget ever
---------- Post added at 10:59 PM ---------- Previous post was at 10:19 PM ----------
I will try to release tomorrow, since i want to make a new banner, based on my old VeeKernel banner.
For CM i will need to redownload CAF Kernel MSM (since im stupid and overwrited .git in tests).
I will start building TWRP (V3), merging it to stock ramdisk and update to make cwm and twrp side-by-side.
So i have done this in two weeks for make a custom kernel, thanks @fzort
Enviado de meu E435 (L3 II Dual) usando Tapatalk
any want to make a new rom
get souce code: https://github.com/CyanogenMod/android_device_samsung_klte-common/tree/cm-14.0
Arjunfire said:
any want to make a new rom
get souce code: https://github.com/CyanogenMod/android_device_samsung_klte-common/tree/cm-14.0
Click to expand...
Click to collapse
you can make
I think he asked that because he cant do this. But I think it is only a matter of time until something will be released. At least I hope so.
I want it
Guys cm14 is under progress for klte.
We can have a high hopes for android 7 via cm14. We have devs like @albinoman887 and @haggertk and few others too. So for now let's just wait.
:good:
rayzen6 said:
Guys cm14 is under progress for klte.
We can have a high hopes for android 7 via cm14. We have devs like @albinoman887 and @haggertk and few others too. So for now let's just wait.
:good:
Click to expand...
Click to collapse
I think there will be no drivers for Spadragon 800/801...?
Athanatos81 said:
I think there will be no drivers for Spadragon 800/801...?
Click to expand...
Click to collapse
Yup looks like but for vulkan api only. I don't it'll be much problem with that. As u can see aosp 7 builds are already up for nexus5 , one plus one and few other devices which are 800 or 801 .
I hope stil working on s5 sm g900f
Can't wait for CM14, although qualcomm won't release new drivers for gpu. So I do not know, if it is worth to wait.. But our devs are geniuses, maybe the current driver packages will work, too.. But at first, I have to root my phone, what I don't like to do, because 0x1 is bad with warranty till January.. hmmmmmm... But Paranoid Android, CM14, ...
rayzen6 said:
Yup looks like but for vulkan api only. I don't it'll be much problem with that. As u can see aosp 7 builds are already up for nexus5 , one plus one and few other devices which are 800 or 801 .
Click to expand...
Click to collapse
Yup but i guess it can be done without vulkan api. As in nexus 4 port.
kardinal969 said:
Yup but i guess it can be done without vulkan api. As in nexus 4 port.
Click to expand...
Click to collapse
That's what I said brother
freibergisch said:
Can't wait for CM14, although qualcomm won't release new drivers for gpu. So I do not know, if it is worth to wait.. But our devs are geniuses, maybe the current driver packages will work, too.. But at first, I have to root my phone, what I don't like to do, because 0x1 is bad with warranty till January.. hmmmmmm... But Paranoid Android, CM14, ...
Click to expand...
Click to collapse
it is possible to update drivers for gpu if you have an unlocked bootloader and are on mm aosp rom
Ill take a stab at this. Installing ubuntu on my laptop now, any of you guys think its a good idea to follow this tutorial that was made for AOSP MM? Would the steps be the same? https://wiki.cyanogenmod.org/w/Build_for_klte
Please just set up a build, can't wait to use nougat
---------- Post added at 10:27 PM ---------- Previous post was at 10:27 PM ----------
chippinganimal said:
Ill take a stab at this. Installing ubuntu on my laptop now, any of you guys think its a good idea to follow this tutorial that was made for AOSP MM? Would the steps be the same? https://wiki.cyanogenmod.org/w/Build_for_klte
Click to expand...
Click to collapse
They should
Paoletti said:
Please just set up a build, can't wait to use nougat
---------- Post added at 10:27 PM ---------- Previous post was at 10:27 PM ----------
They should
Click to expand...
Click to collapse
Alright, got ubuntu installed (windows partition had a heart attack afterwards lmao) so now Ill do my best to follow that guide and see what happens i guess... Should build pretty fast since this machine has a i7 3770 and 16gb of ram and it seems the guide says 8gb of ram is fine.
Alright guys, i got to the part where I have to sync the repo, so i pasted the link in the cm device tree github page that is in the "clone or download" dropdown (ends with .git) and i get this error in the screenshot... got any ideas?
chippinganimal said:
Alright guys, i got to the part where I have to sync the repo, so i pasted the link in the cm device tree github page that is in the "clone or download" dropdown (ends with .git) and i get this error in the screenshot... got any ideas?
Click to expand...
Click to collapse
No idea.. I googled a bit but i didn't find anything exactly like that, maybe you can just try another time, I'm not an expert developer, so I just hope someone could help us.
Try checking here http://stackoverflow.com/questions/...-find-remote-ref-refs-heads-xxxx-and-hangs-up
Paoletti said:
No idea.. I googled a bit but i didn't find anything exactly like that, maybe you can just try another time, I'm not an expert developer, so I just hope someone could help us.
Try checking here http://stackoverflow.com/questions/...-find-remote-ref-refs-heads-xxxx-and-hangs-up
Click to expand...
Click to collapse
This is a git thing. Basically the branch name has changed. It's now in the staging branch so:
-b staging/cm-14.0
Hey guys just for us kind information we can hope cm14 aswell as ROMs based on it. Look this post by aicp developer/contributor . he has booting aicp n dev build. The awesome thing yo notice in this post is network indicators. Looks like ril is working also I think its usable too. But we have to wait a lil more to get public build.
Hit thanks button on his post.
http://forum.xda-developers.com/showpost.php?p=68899345&postcount=1613
rayzen6 said:
Hey guys just for us kind information we can hope cm14 aswell as ROMs based on it. Look this post by aicp developer/contributor . he has booting aicp n dev build. The awesome thing yo notice in this post is network indicators. Looks like ril is working also I think its usable too. But we have to wait a lil more to get public build.
Hit thanks button on his post.
http://forum.xda-developers.com/showpost.php?p=68899345&postcount=1613
Click to expand...
Click to collapse
We want to try that build, beta, alpha or wathever it is. We just want to try it, feel nougat in our hands, we want a download link for that build, even if it isn't stable, daily usable and public. We want that, we must have that.
Good evening, in recent days the project Oreo 15.1 for the G5S (montana) has begun. My friend Pedro Kalil was able to make a tree common that supports all motorola devices that use msm8937 or msm8953. The first compilation was started for testing, but we are facing major problems with the sensors and the camera.
At the moment the sensors and the camera are not working, we already made several compilations with the exchange of the libs. But it still does not work.
We need the help of you montana developers so that the Oreo project works.
I had to use xda to communicate this because I could not get the number of some dev's.
Contact me, telegram: therssxda
Lineage 15.1 - It works, but we have problems., ROM for the Moto G5S
Contributors: @rssxda -- @KalilDev
ROM OS Version: 8.1.0 Oreo
Version Information
Status: Testing
Created 2018-07-19
Last Updated 2018-07-18
Reserved
@lohanbarth @kaylansundhar @govind1233
Screenshots:
Good, waiting for news...
I hope the devs actually see this. I dont own montana, but i feel so sorry for the users that i had to do sommething about it. unfortunately i dont know anything about how montana handles sensors.
O Will wainting ...
When it will come out?
@rssxda If basic things like Wi-Fi, touchscreen (and maybe the fingerprint sensor) work, then I'd be very happy to test the ROM. PM me with any info
rssxda said:
@[email protected]@govind1233
Click to expand...
Click to collapse
Already working to fix stuff
Do you have any previews for downloading rom?
WandresJersey said:
Do you have any previews for downloading rom?
Click to expand...
Click to collapse
I won't release it until it's 100%. Look at some ss tho:
good, we waiting the best
The ROM is 64-Bit? Have support to Treble?
KalilDev said:
I hope the devs actually see this. I dont own montana, but i feel so sorry for the users that i had to do sommething about it. unfortunately i dont know anything about how montana handles sensors.
Click to expand...
Click to collapse
First of all I apologize for a too late reply.
Main problem is cedric sensor and camera libraries would not work with montana sensors and camera. Initially for LOS7, I tried this way of making a montana build using cedric libraries. Same problem I ended up with. Whatever change I do, there would be something preventing it from working. Try to use sensor and camera libraries from G5S stock.
Mainly,
system/bin/sensors.qcom
system/lib/hw/sensors.rp.so
system/lib/hw/sensors.montana.so
system/lib/lib_motsensorlistener.so
system/lib/hw/camera.msm8937.so
system/bin/mm-qcamera-daemon
system/lib/libcamerabgprocservice.so
And there is a whole bunch of libmmcamera*.so in vendor/lib directory of stock Nougat ROM.
But my gut feel is these libraries would not work as such in OREO build. We may require to write a SHIM layer.
Please don't take it as discouragement. I am just outlining what problems you would face using a mix of CEDRIC and MONTANA (STOCK) libraries.
Thanks
KS
kalyansundhar said:
First of all I apologize for a too late reply.
Main problem is cedric sensor and camera libraries would not work with montana sensors and camera. Initially for LOS7, I tried this way of making a montana build using cedric libraries. Same problem I ended up with. Whatever change I do, there would be something preventing it from working. Try to use sensor and camera libraries from G5S stock.
Mainly,
system/bin/sensors.qcom
system/lib/hw/sensors.rp.so
system/lib/hw/sensors.montana.so
system/lib/lib_motsensorlistener.so
system/lib/hw/camera.msm8937.so
system/bin/mm-qcamera-daemon
system/lib/libcamerabgprocservice.so
And there is a whole bunch of libmmcamera*.so in vendor/lib directory of stock Nougat ROM.
But my gut feel is these libraries would not work as such in OREO build. We may require to write a SHIM layer.
Please don't take it as discouragement. I am just outlining what problems you would face using a mix of CEDRIC and MONTANA (STOCK) libraries.
Thanks
KS
Click to expand...
Click to collapse
We could fetch these libraries from the 8.1 soak test firmware... If such firmware had been leaked to begin with.
I'm not criticizing the testers, they're doing what they're supposed to be doing, by not leaking anything. However, had someone done that, they would've made you guys' lives a bit easier.
Anyhow, I wish you luck. It's nice to see the G5S get the attention it deserves. It's a nice phone, actually. But it looks like it's the forgotten middle child of the G5 family. lol
Me too waiting..
For stable
Any rumors/news about this rom???
any news
nice to actually have 8.1 in moto g5s??
Hello, everyone.
I noticed, there are many custom roms, but not that many for the SM-T505. Is it because it's newly released, or are there other reasons?
Yes, this is a new device and many people are probably waiting for the Black Friday/Cyber Monday deals to grab one. I just grabbed one for $150 on Amazon, a steal compared to something like a Fire tablet IMO. This is a low-end tablet, so there won't be as much focus on it as say a flagship phone. But thankfully it's already been unlocked and rooted, so the next step will be to get TWRP on it, and then custom ROM development can start to pick up on it. Don't expect any updates before the end of the year for custom ROMs though, it will likely take time to have TWRP up and running on it, but I am hopeful that we will see good things on this tablet in 2021
Without kernel sources it won't happen. See https://opensource.samsung.com/uploadSearch?searchValue=sm-t505 and https://opensource.samsung.com/uploadSearch?searchValue=sm-t500.
You can request them on that page. I did it a few times but no response so far.
paziusss said:
Without kernel sources it won't happen. See https://opensource.samsung.com/uploadSearch?searchValue=sm-t505 and https://opensource.samsung.com/uploadSearch?searchValue=sm-t500.
You can request them on that page. I did it a few times but no response so far.
Click to expand...
Click to collapse
Interesting... is it just me or is there no button to start an inquiry?
EDIT: Found it... just posted an Inquiry.
Watching!! I just bought the T500.
jlang11 said:
Watching!! I just bought the T500.
Click to expand...
Click to collapse
Just got an answer from Samsung, but don't get to excited. It was just an automated answer, that they received my inquiry. So stay tuned...
https://opensource.samsung.com/uploadSearch?searchValue=t500 gives you a 514mb file with kernel and vencor files.
Maybe both 505 and 500 are similiar enough to get you started
Sources are available: https://opensource.samsung.com/uploadSearch?searchValue=sm-t500
They include a toolchain in kernel tree, broken KConfigs and a lot of junk. I will try to clean a bit a mess and update a lean kernel tree to github
paziusss said:
Sources are available: https://opensource.samsung.com/uploadSearch?searchValue=sm-t500
They include a toolchain in kernel tree, broken KConfigs and a lot of junk. I will try to clean a bit a mess and update a lean kernel tree to github
Click to expand...
Click to collapse
Will you also do a diff against the upstream version so we can see what they changed?
selemine said:
Will you also do a diff against the upstream version so we can see what they changed?
Click to expand...
Click to collapse
Sure, but I'm going to remove the toolchain from the kernel tree since the beginning. It takes About 1GB alone and I don't want to have it on git refs because it will still take a lot of space even if removed.
The rest of changes will be available on github.
paziusss said:
Sure, but I'm going to remove the toolchain from the kernel tree since the beginning. It takes About 1GB alone and I don't want to have it on git refs because it will still take a lot of space even if removed.
The rest of changes will be available on github.
Click to expand...
Click to collapse
It's been a long time, since i took up building custom roms and forgot about it for a while... if the kernel is cleansed from all the BS no one needs, that would be awesome.
There are a lot of small changes to comments and changes of 2 characters in a line. Wonder if they backported stuff there.
Kernel of the SM-T505 was just released...
If this is of any relevance, the download is 'just' 200MB... i wonder why.
The Platform Archive is mostly identical, just a few text files with notes and copyright were missing.
The Kernel Package as well, just small changes to netfilter and
a new defconfig file.
Defconfig for both devices also is more or less the same
gta4lwifi_eur_open_defconfig is missing one line compared to gta4l_eur_open_defconfig
CONFIG_SAMSUNG_FREECESS=y
Guess the difference comes from the toolchain mentioned above.
@paziusss
How far have you come?
Would be great if we had something clean to start a twrp and easier rooting
selemine said:
@paziusss
How far have you come?
Would be great if we had something clean to start a twrp and easier rooting
Click to expand...
Click to collapse
Sorry, I have a very bad internet connection (uplink it is ~50-100KiB/s)
I created the repo a month ago: https://github.com/pazos/android_kernel_samsung_gta4lwifi
,tried to push and failed. Never tried again until now, but it is still failing.
So, if somebody is nice enough to dump the contents of the SM-T500 kernel in a github repo, I can fork and submit the patches without having to upload the whole thing myself.
paziusss said:
Sorry, I have a very bad internet connection (uplink it is ~50-100KiB/s)
I created the repo a month ago: https://github.com/pazos/android_kernel_samsung_gta4lwifi
,tried to push and failed. Never tried again until now, but it is still failing.
So, if somebody is nice enough to dump the contents of the SM-T500 kernel in a github repo, I can fork and submit the patches without having to upload the whole thing myself.
Click to expand...
Click to collapse
Here you go
jayzarry84 said:
Here you go
Click to expand...
Click to collapse
Thank you! It helped.
I had to apply the patch manually, so everything is in a single commit, but should be easy for others to understand what each chunk of code does.
Here you go: https://github.com/pazos/android_kernel_samsung_gta4lwifi
paziusss said:
Thank you! It helped.
I had to apply the patch manually, so everything is in a single commit, but should be easy for others to understand what each chunk of code does.
Here you go: https://github.com/pazos/android_kernel_samsung_gta4lwifi
Click to expand...
Click to collapse
Just realized I didn't upload the Platform folder contents. It's uploading as we speak
jayzarry84 said:
Just realized I didn't upload the Platform folder contents. It's uploading as we speak
Click to expand...
Click to collapse
I really have to ask, can i use this to build a custom rom for the SM-T505 as well?