Related
Hi, I'll try to keep it short, between yesterday and today, I have been researching CM13, I thought it was a really hard project, but the results look promising so far, I am not ready to release anything at the moment, but I'll let you see some screenshots. This is just a side project, and I'll keep working on AOSP. I'll update this post whenever I feel like the ROM is kind of finished.
PS: This is Android 6.0.1, EMUI is just on 6.0.0 Isn't that exciting?
http://imgur.com/a/kbybk
See you!
PS2: No PMs about this please, you'll have it as soon as it's finished
CM 13 For HUAWEI P8 Lite?
I solve art/runtime error
wow this is great,i wish you all the best in these projects !
When will be this finished? I can't wait!??❤
Sent from my ALE-L21 using XDA-Developers mobile app
just wondering something, how much space uses system from CM13 and AOSP? for example, on stock Huawei roms almost always they use 2GB+
EDIT: and anyways im asking because, i use Honor 4X/Gplay, and its the same phone that the P8 lite, except internal storage, so that's why im wondering, anyways i think i used your AOSP, that had some bugs like no signal, no wifi, etc (im not sure if you made it), the thing is that rom worked it in my phone too lol
You're just awesome dude! We are all very excited about this project. This is just awesome!
Finally someone who is making ROMs for this phone (and unlike someone doesn't say he'll delete everything "because of noobs")
Sent from my ALE-L21 using XDA-Developers mobile app
Sounds great! If you want someone who can help you testing, i can do that!
Yay, i bought p8lite 2 days ago and i love it!
Great work btw
dude this is awesome !!! so there is no more ril problem this is just great thank you very much !!!!
Hi @XePeleato first of all Good Job and second as i can see into the screenshots the RIL problem is persistent or you didn't insert the SIM . I'm following your work on github if u need someone who test the ROM call me
Spineshankumb said:
Hi @XePeleato first of all Good Job and second as i can see into the screenshots the RIL problem is persistent or you didn't insert the SIM . I'm following your work on github if u need someone who test the ROM call me
Click to expand...
Click to collapse
Hi, The SIM is there, the thing is that I need to patch the framework in order to include the Huawei Java classes that enable the RIL stack. I'll release a testing version soon, since I want to include things to test, it wouldn't make sense to upload a rom with 1 or 2 features working, there would be nothing to test
XePeleato said:
Hi, The SIM is there, the thing is that I need to patch the framework in order to include the Huawei Java classes that enable the RIL stack. I'll release a testing version soon, since I want to include things to test, it wouldn't make sense to upload a rom with 1 or 2 features working, there would be nothing to test
Click to expand...
Click to collapse
Sure! what about the camera? i think is not possible to port the Snap camera feature on HiSi
panchovix said:
just wondering something, how much space uses system from CM13 and AOSP? for example, on stock Huawei roms almost always they use 2GB+
EDIT: and anyways im asking because, i use Honor 4X/Gplay, and its the same phone that the P8 lite, except internal storage, so that's why im wondering, anyways i think i used your AOSP, that had some bugs like no signal, no wifi, etc (im not sure if you made it), the thing is that rom worked it in my phone too lol
Click to expand...
Click to collapse
Wifi worked fine on my 5.1 AOSP version, The system.img weighs roughly 800MB, I don't know exactly how much will it take, since CM13 didn't erase my internal storage.
NeedleGames said:
Finally someone who is making ROMs for this phone (and unlike someone doesn't say he'll delete everything "because of noobs")
Sent from my ALE-L21 using XDA-Developers mobile app
Click to expand...
Click to collapse
Well, sokkoban recieved a LOT of input about his roms, there were a lot of questions and stuff, it can get really annoying, these open source projects come "As is, without warranty of any kind" - quoting the GPL so actually, trying to give some decent support on this forums is really kind.
Spineshankumb said:
Sure! what about the camera? i think is not possible to port the Snap camera feature on HiSi
Click to expand...
Click to collapse
The Snap app is included, however since I haven't included the camera HAL yet, I don't know for sure if it will work.
--
I'll be off like a week or so, I have compiled my own kernel, with some CPU governors to try, and I have fixed the screen DPI so far, there's still some serious patching needed.
@XePeleato yeah it worked, but if im not mistaken, with static wifi, but interesting, if the system is 800MB i think i will be fine, thanks for all about this
This is just my mind. But i would be more happier if i got fully working cm13 marshmallow than aosp lollipop. If i was you. I would take cm as a primary mission. But do as you want. Aosp is great news too
Keep it up man!
Vika__ said:
This is just my mind. But i would be more happier if i got fully working cm13 marshmallow than aosp lollipop. If i was you. I would take cm as a primary mission. But do as you want. Aosp is great news too
Keep it up man!
Click to expand...
Click to collapse
Sure, your opinion matters. Luckily, if I apply a patch to CM, it's also valid on AOSP, the same applies for the kernel.
XePeleato said:
Hold on I said nothing about the RIL stack, I don't know if it will work or not, but that's the last thing I am going to try to fix since I don't know if I am going to be able to fix it at all.
Click to expand...
Click to collapse
holly crap I thought this problem is finally solved :/ , okey I hope it can be fixed then , good luck !!!
Great!If I port this for Honor 4C,will it work?Sorry for my bad English.
来自华为荣耀畅玩4C CHM-TL00H -天生急性子 Android 小楼阁
I was thinking: since we have an unlocked bootloader and custom roms, how hard would be to port AOSP Nougat?
There is any tecnical difficulty, like kernel version, that can block us?
Not much, I would imagine.
As far as I can tell, it'd just take a dev that's interested in putting in the effort.
Yes, this counts as my "yes, please" vote for Z00T.
I am votting with yes
I was thinking about do a try and compile it straight away, but i fear i'm not experienced enough to make something bootable
I don't think that the kernel or other thing will block it, but we got a custom ROM so late and I don't think we'll have a CM14 very soon
Cm14 should be prettt easy since we have cm 13, the point is that right now is not worth it because it's still in early stage, so a fully fledged cm13 would be more usefull.
AOSP is another talk because it's so barebone
Jhyrachy said:
Cm14 should be prettt easy since we have cm 13, the point is that right now is not worth it because it's still in early stage, so a fully fledged cm13 would be more usefull.
AOSP is another talk because it's so barebone
Click to expand...
Click to collapse
Umm, thanks for your thoughts about trying to bring N, it seem you got the answer yourself
from what i look at Z00L/T source, other than some fix and caf one, they could bring N to L/T with some borrowed libs. And looking from our source, I still found some line with L/T on it, so, yes, dev may bring N to this device, just hope that libs going to work with this devices.
But as you said, a fully fledged cm13 would be useful, using RR build for 3 days, and got the problem as they says. Plus, for me, front camera isn't working (called arclib or something, front camera effect when using asus camera, it's working fine with other camera because they didn't load that lib). Constant lag when using GPS other than "gps only" (might RR only problem). etc..
Either way, I hope that you could join the team (or, is he a one man army?) maintaining this device, fixing things come first, upgrade when everything is fine. At least "ok".
I don't know about AOSP, but many say choose CM because of CM broad compatibility layer. If that's true, then AOSP might slightly harder...
or... not really.
Sent from my ASUS_Z00RD using XDA Labs
Interesting, I'm not developer but I think this is possibke, Android 7.0 supports S410, maybe CM14 will better than AOSP.
yeah i still waiting ??
Sent from my ASUS_Z00ED using Tapatalk
Who wants to test BeanStalk 6.25 for Z00RD/Z00E?
imjohncarlo9 said:
Who wants to test BeanStalk 6.25 for Z00RD/Z00E?
Click to expand...
Click to collapse
I, but it will be possible tonight because now i working , phone at home
imjohncarlo9 said:
Who wants to test BeanStalk 6.25 for Z00RD/Z00E?
Click to expand...
Click to collapse
i will try tomorrow ...good for this ??
Sent from my ASUS_Z00ED using Tapatalk
Some news?
waiting :victory:
Waiting for some USEFUL news.
Today I try to compile it, but do not know if I aim, because I'm not a developer and I have no experience, but I try the same, stay connected, sorry for my bad english
I can't download the sources because it me give an errore i can't compile a ROM,sorry
Still waiting for news.
I tried to compile it myself, I downloaded all the sources, but since the Z00ED / RD is not officially supported by CyanogenMod, and then the repository and everything else must be manually added, I tried but I get error during compilation. Now we must wait for some developer is able to have time to complete it, because basically if you have created for the Z00L / Z00T do not see why you can not fill because they have the same processor. Sorry for my bad English
kurnalcool said:
I tried to compile it myself, I downloaded all the sources, but since the Z00ED / RD is not officially supported by CyanogenMod, and then the repository and everything else must be manually added, I tried but I get error during compilation. Now we must wait for some developer is able to have time to complete it, because basically if you have created for the Z00L / Z00T do not see why you can not fill because they have the same processor. Sorry for my bad English
Click to expand...
Click to collapse
Hi! Could this help you in some way? I don't know how, but I hope there is something usefull. This is a link to a russian forum where CM13 for ZE500KL was first posted by his original creator. Is in russian but I think you can use google translate to read the forum http://4pda.ru/forum/index.php?showtopic=766921
Good day lads,
Disclaimer:
Code:
I don't know if you noticed a thread in the Q&A section that was closed by Matt. While I respect Matt's decision to close it, I find it a very relevant topic... The future of LineageOS for the P9 Lite. Please note that I do respect meticulous' wishes to charge for his work because I know how time consuming it is I wish to firmly express that I do not condone this mentality when it comes to Linux based operating systems.
I decided to make this thread with my little Dev knowledge in order to attract more devs who's willing to put in work on a stable device tree for free in spirit of community and for all to enjoy.
I do not have the Lineage source code at the moment but I will start downloading soon, I do know that I will need help and I encourage more devs/beginners to lend a hand for the benefit of us all.
Please, to begin, post links to relevant tarballs/links/downloads for development purposes, device tree and kernels, anything you've worked on so perhaps we can all work together.
Cheers
Sent from my HUAWEI VNS-L31 using Tapatalk
Hmmm... The fact that building android ROMs is time consuming is not a good enough reason to request money for OPEN SOURCE SOFTWARE. Yes, LineageOS and android in general are open source, so that's an infraction.
About the collective effort, that's a good idea, but there are no sources from Huawei right now. You need to wait for the Nougat sources if Huawei really gives a dime about releasing them. From that point, it is easier to develop and get stuff working. Until then, good luck working without sources and experimenting stuff. Not to mention that there's no official TWRP as well, and TWRPs posted here on XDA for our devices have specific requirements to get them flashed on your device.
Asphyxiate666 said:
Hmmm... The fact that building android ROMs is time consuming is not a good enough reason to request money for OPEN SOURCE SOFTWARE. Yes, LineageOS and android in general are open source, so that's an infraction.
About the collective effort, that's a good idea, but there are no sources from Huawei right now. You need to wait for the Nougat sources if Huawei really gives a dime about releasing them. From that point, it is easier to develop and get stuff working. Until then, good luck working without sources and experimenting stuff. Not to mention that there's no official TWRP as well, and TWRPs posted here on XDA for our devices have specific requirements to get them flashed on your device.
Click to expand...
Click to collapse
Why do you need to come here with negativity? I don't support meticulous but he can do what he wants with the device sources he took the time to build, heck, he doesn't need to release those sources so I don't know what you're talking about, firstly. Secondly, a device tree can be built, Q.E.D we as a community can work on it together, if they release it we'll just have it much easier.
Note also; I've asked for relevant input and help from the community.
Thanks for your time though.
EDIT: P.S Professional Flasher, have you ever built a ROM before? Because that's my target here, finding people who knows how to fix error and put the tree together
Sent from my HUAWEI VNS-L31 using Tapatalk
Carlyle_f said:
Why do you need to come here with negativity? I don't support meticulous but he can do what he wants with the device sources he took the time to build, heck, he doesn't need to release those sources so I don't know what you're talking about, firstly. Secondly, a device tree can be built, Q.E.D we as a community can work on it together, if they release it we'll just have it much easier.
Note also; I've asked for relevant input and help from the community.
Thanks for your time though.
EDIT: P.S Professional Flasher, have you ever built a ROM before? Because that's my target here, finding people who knows how to fix error and put the tree together
Sent from my HUAWEI VNS-L31 using Tapatalk
Click to expand...
Click to collapse
Ignore it's just a critic custom rom user....[emoji12]
Hipom said:
Ignore it's just a critic custom rom user....[emoji12]
Click to expand...
Click to collapse
My words are razor sharp but honest and realistic.
Sent from my VNS-L21 using Tapatalk
Asphyxiate666 said:
Hmmm... The fact that building android ROMs is time consuming is not a good enough reason to request money for OPEN SOURCE SOFTWARE. Yes, LineageOS and android in general are open source, so that's an infraction.
About the collective effort, that's a good idea, but there are no sources from Huawei right now. You need to wait for the Nougat sources if Huawei really gives a dime about releasing them. From that point, it is easier to develop and get stuff working. Until then, good luck working without sources and experimenting stuff. Not to mention that there's no official TWRP as well, and TWRPs posted here on XDA for our devices have specific requirements to get them flashed on your device.
Click to expand...
Click to collapse
Open source does not mean free, period.
pilgrim011 said:
On xda, it does mean free, period. People that think that they should be paid for contributing here are not welcome on XDA.
Click to expand...
Click to collapse
you are totally right
Just finish already. If you want to discuss all that situation just create some g+ group or telegram for this.
XDA dev thread is not for that king of discussion.
Also it should be in QA SECTION.
You start xda dev thread when you have something made already. Not just with idea.
lsander said:
If you want to discuss all that situation just create some g+ group or telegram for this.
XDA dev thread is not for that king of discussion.
Click to expand...
Click to collapse
This disussions are undesired here. I know a board where you can discuss that. If you want, feel free to have a look at it. This little Board is very pleased about every enlivenment. Opened a thread over there.
Well, developers do not grow on trees. I guess there are not enough devs here who have the P9 Lite device.
However I like the intention of the thread author. For that reason please try to discuss in a human way.
In the end: I am vers interested in learning how to build custom roms but I can't find a way how to learn it. Does anyone have some good advice?
Updated kernel
Hello everyone, I've recently been working on updating the Honor 5c kernel to 3.10.105 and so far it seems to be working fine on my P9lite, LineageOS 14.1. It's based purely on stock, with one or two commits borrowed from Meticulus' kernel repo, so it compiles without errors.
Since this is a new account, I can't link my repo directly, you can find it on my github profile, Avsky.
I'll be making my own additions to master branch, while stocklike branch will contain only fixes and kernel updates.
If somebody would like to test them, you can get the boot image from releases tab on github. Stock kernel hasn't been tested, mind you, always keep a backup!
Also depending on how much time I have, I might get started on bringing OmniROM to our device (I'm really missing it). I'm just a college student though, so it might never see the light of day, any help is much appreciated.
Avsky0 said:
Hello everyone, I've recently been working on updating the Honor 5c kernel to 3.10.105 and so far it seems to be working fine on my P9lite, LineageOS 14.1. It's based purely on stock, with one or two commits borrowed from Meticulus' kernel repo, so it compiles without errors.
Since this is a new account, I can't link my repo directly, you can find it on my github profile, Avsky.
I'll be making my own additions to master branch, while stocklike branch will contain only fixes and kernel updates.
If somebody would like to test them, you can get the boot image from releases tab on github. Stock kernel hasn't been tested, mind you, always keep a backup!
Also depending on how much time I have, I might get started on bringing OmniROM to our device (I'm really missing it). I'm just a college student though, so it might never see the light of day, any help is much appreciated.
Click to expand...
Click to collapse
Hello, I tried your kernel on AOSPA MM but I couldn't get the proper unpacked zImage. I got only 9.7 MB gzip which contains the 22 MB Image but I couldn't extract it.
Could you provide the zImage?
dady000 said:
Hello, I tried your kernel on AOSPA MM but I couldn't get the proper unpacked zImage. I got only 9.7 MB gzip which contains the 22 MB Image but I couldn't extract it.
Could you provide the zImage?
Click to expand...
Click to collapse
Strange, I can extract it without problem using abootimg. Anyway, zImage now included on releases page.
Avsky0 said:
Strange, I can extract it without problem using abootimg. Anyway, zImage now included on releases page.
Click to expand...
Click to collapse
That zImage looks like the same I got from unpack. For some reason it won't boot when I repack it with my ramdisk.
dady000 said:
That zImage looks like the same I got from unpack. For some reason it won't boot when I repack it with my ramdisk.
Click to expand...
Click to collapse
I repacked and uploaded my image with ramdisk from your latest AOSPA, could you try it? Sizes varied a bit, I've used my abootimg config with SELinux changed to permissive, as that is the case in your image.
EDIT: I'm uploading extracted zImage as well.
Avsky0 said:
I repacked and uploaded my image with ramdisk from your latest AOSPA, could you try it? Sizes varied a bit, I've used my abootimg config with SELinux changed to permissive, as that is the case in your image.
EDIT: I'm uploading extracted zImage as well.
Click to expand...
Click to collapse
Yeah of course it works :silly:. Looks like my boot-packing skills are pretty low. Good job :fingers-crossed:
dady000 said:
Yeah of course it works :silly:. Looks like my boot-packing skills are pretty low. Good job :fingers-crossed:
Click to expand...
Click to collapse
Glad to hear it! Your images seem to be using uncompressed zImages, while in stock ROMs they're gzipped, seems like unintentional change somewhere in your build process.
Avsky0 said:
Glad to hear it! Your images seem to be using uncompressed zImages, while in stock ROMs they're gzipped, seems like unintentional change somewhere in your build process.
Click to expand...
Click to collapse
Yeah you're right. I just checked it and I am copying Image instead of Image.gz. Seems like it's only a 'cosmetic' issue because it runs anyways.
Great news guys, my sources now compile with latest Linaro toolchain. The kernel actually barely needed any fixes, but I'm not releasing anything prebuilt yet, since I have no idea what impact on stability my hacks might have.
Screenshot
ndroid1562 said:
Well, developers do not grow on trees. I guess there are not enough devs here who have the P9 Lite device.
However I like the intention of the thread author. For that reason please try to discuss in a human way.
In the end: I am vers interested in learning how to build custom roms but I can't find a way how to learn it. Does anyone have some good advice?
Click to expand...
Click to collapse
Perhaps reading through GitHub commits, checking the code and see whether or not you're really interested. If you're using a Linux distribution which I strongly advise, learn bash scripts first - it's easy and self explanatory and from there you will get basics of directories and calling up files.
Goodluck
Sent from my HUAWEI VNS-L31 using Tapatalk
Hi, i have this, i need check this information.
Here the screenshots.
Are you signed up to the Motorola Feedback Network? If so, that looks like the soak test for the G5S (as reported here as well: https://forum.xda-developers.com/moto-g5s/how-to/android-oreo-soak-test-brazil-t3803812 )
EDIT - hmm, looking at that email posted in the other link, it says the soak test is for G5 devices, yet the opening poster has a G5S from what I can see. The build matches up with your post, so unless Motorola is pushing the same build to G5 and G5S devices, I think this build is for G5S?
At least they're moving the G5S to Android 8.1 from the looks of things.
If you are on the soak test/signed up to the MFN, as per the soak test agreement, please report any bugs to Motorola, and be aware of any device breaking bugs that may occur. Have fun, but please be responsible too.
echo92 said:
Are you signed up to the Motorola Feedback Network? If so, that looks like the soak test for the G5S (as reported here as well: https://forum.xda-developers.com/moto-g5s/how-to/android-oreo-soak-test-brazil-t3803812 )
EDIT - hmm, looking at that email posted in the other link, it says the soak test is for G5 devices, yet the opening poster has a G5S from what I can see. The build matches up with your post, so unless Motorola is pushing the same build to G5 and G5S devices, I think this build is for G5S?
At least they're moving the G5S to Android 8.1 from the looks of things.
If you are on the soak test/signed up to the MFN, as per the soak test agreement, please report any bugs to Motorola, and be aware of any device breaking bugs that may occur. Have fun, but please be responsible too.
Click to expand...
Click to collapse
I faild to register in Soak Test :/
EmiAndroid said:
I faild to register in Soak Test :/
Click to expand...
Click to collapse
Unfortunate - I guess they've got plenty of soak testers for these soak updates. I imagine there may be a leak of the Oreo soak test at some point, though be careful with flashing said leak. Any bugs or issues you won't have Motorola support (as you're not on the soak test) and downgrading back to Nougat is a potentially risky procedure. It won't be the downgrade back to Nougat that is problematic, but using Nougat OTA updates on a device updated to Oreo may hard brick your device.
Seems that they're soak testing the G5S Plus as well from the screenshots: https://www.techdroider.com/2018/06/moto-g5s-plus-android-8-1-oreo-beta-screenshots.html (looks like it's OPS28.49-2?)
If it is the soak test, then all being well, the update should be rolling out in the next 1-2 months.
. Gdfhjjh
jesemalave1 said:
I got mine 2 days ago I love it
Click to expand...
Click to collapse
Nice, could you download DevCheck by flar2 https://play.google.com/store/apps/details?id=flar2.devcheck&hl=en_GB and in the app, under the System tab, post a screenshot of the architecture please? The app is free and should work without root.
I'm a mtf tester but it's confidential as parbagreementbwishbibcouldnshare more
jesemalave1 said:
I'm a mtf tester but it's confidential as parbagreementbwishbibcouldnshare more
Click to expand...
Click to collapse
Not a problem - good to see you're respecting the NDA Hoping there aren't too many bugs to report.
It looks like the Oreo update is a 32 bit update anyhoo: https://forum.xda-developers.com/showpost.php?p=76813739&postcount=121 That's not surprising given the migration to 64 bit might require a wipe and the drivers re-written for the 64 bit architecture.
Moto g5s plus Oreo 8.1 Soak test
Watch this video for features
can someone share a photo of the 8.1 lockscreen? i wanna know if the ugly font changed..
also does it uses the G6 bootanimation or keeps the 7.1 one?
Keeps the same boot animation, no changes to fonts
Beneduzi said:
Keeps the same boot animation, no changes to fonts
Click to expand...
Click to collapse
thank you
I don't like that font but since oreo makes the clock a bit smaller maybe it looks better in comparison to 7.1
echo92 said:
Not a problem - good to see you're respecting the NDA Hoping there aren't too many bugs to report.
It looks like the Oreo update is a 32 bit update anyhoo: https://forum.xda-developers.com/showpost.php?p=76813739&postcount=121 That's not surprising given the migration to 64 bit might require a wipe and the drivers re-written for the 64 bit architecture.
Click to expand...
Click to collapse
Then there is nothing to look after, only our xda dev can use the default camera in custom rom otherwise this 32 bit Oreo is nothing less than a ****.(tati)
Extremely disappointed with moto will never buy in future
jesemalave1 said:
I'm a mtf tester but it's confidential as parbagreementbwishbibcouldnshare more
Click to expand...
Click to collapse
Breaking - there are serious bugs in the oreo 8.1 keyboard handler.
---------- Post added at 09:56 AM ---------- Previous post was at 09:50 AM ----------
Rush94 said:
Then there is nothing to look after, only our xda dev can use the default camera in custom rom otherwise this 32 bit Oreo is nothing less than a ****.(tati)
Extremely disappointed with moto will never buy in future
Click to expand...
Click to collapse
A tati?
He means fecal matter
Rush94 said:
Then there is nothing to look after, only our xda dev can use the default camera in custom rom otherwise this 32 bit Oreo is nothing less than a ****.(tati)
Extremely disappointed with moto will never buy in future
Click to expand...
Click to collapse
On a counterpoint, the camera drivers and blobs would be updated to Oreo, so may be easier for the developers to work with. If you really want a Moto device that's 64 bit, I think the X4 and the G6 Plus are 64 bit, else I wish you luck finding a 64 bit device that you like and can afford.
echo92 said:
On a counterpoint, the camera drivers and blobs would be updated to Oreo, so may be easier for the developers to work with. If you really want a Moto device that's 64 bit, I think the X4 and the G6 Plus are 64 bit, else I wish you luck finding a 64 bit device that you like and can afford.
Click to expand...
Click to collapse
Mi A1 is a 64bit device cheapest than g5s plus
ATENTION! OTA OREO IS CAPTURED
https://drive.google.com/uc?id=14nWazUMHTyk-od6SF3KJOXVTOWZoC_Do&export=download
Here is the OTA captured from Android Oreo, they must install it from the stock recovery.
Rush94 said:
Mi A1 is a 64bit device cheapest than g5s plus
Click to expand...
Click to collapse
Man, you really have some deep knowledge abt all this.
I wonder, are you also aware of Mi A1's SAR value.
Important announcement:
If you have used the Persist G4 to recover the IMEI this update will eliminate the same, they must be in android stock, without TWRP, without root, and with the Persist of the corresponding G5s Plus, otherwise, they will have errors.
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