Database Develop

[DEV][G925F] CyanogenMod 12.1 Development

Hello there, it's time to get this rolling somewhere.
This is a Development-Thread. Please don't post if you aren't a developer.
What this IS
This is a Development thread, a platform for developers to discuss the development of CyanogenMod for the G925F. It's made so that we can get this working, fix up the problems - because there will be severe ones - and achieve a working official Rom at some point.
At the moment it's @OldDroid and me with help, but it would be awesome if interested devs would join in so that we can make this a team effort.
In short, it's a Dev-Thread in a dev section.
Right now it doesn't work and I'm not sure that it will work.
What this IS NOT
This is NOT a working Rom. Not even close. I can only link you to the kernel repo and soon to device and vendor, as they are almost completed for a first try.
And yes, there is no download link for the Rom. Because there isn't anything you could download yet.
This is also NOT intended as a Q&A thread. Please don't ask if your variant will be supported, I will respond by trolling. Firstand only priority is to get this running, then we'll talk about variants.
And ETA is an evil word with no meaning here. I work slowly, deal with it
Where are we currently?
Much further than a day ago
Thanks to @OldDroid, we've teamed up
All the links you want (minus the download link :angel
device: (soon, almost complete)
https://gitlab.com/mythos234/device_samsung_zeroltexx
vendor:
https://gitlab.com/mythos234/vendor_samsung_zerolte
kernel:
https://gitlab.com/mythos234/zerolte-kernel-CM
Once available, buggy alpha builds will be posted here
///
vendor and device will soon be pushed to my github
​

Reserved

i'll join you ... also started working on cm12.1 for s6 edge 5 days ago (currently in england with my school class)

vendor is setup
OldDroid said:
i'll join you ... also started working on cm12.1 for s6 edge 5 days ago (currently in england with my school class)
Click to expand...
Click to collapse
Welcome aboard then
vendor is finally setup and good to go!
https://github.com/mythos234/vendor_samsung_zerolte
It's apparently not without some minor casualties, but we got it. Huge thanks to @RaymanFX, he's helping me, since I'm not that much into CM building yet and I'm also basing this project on his CM for the N910C, which's 5433 is darn similar to our 7420, so we got a pretty good base to begin with.

add me as participant to the repos ^^
https://github.com/OldDroid

OldDroid said:
add me as participant to the repos ^^
https://github.com/OldDroid
Click to expand...
Click to collapse
Done for all the 3 of them

Looks like I killed Bluetooth for now (lol). Other than that it's slow but steady progress.

mythos234 said:
Looks like I killed Bluetooth for now (lol). Other than that it's slow but steady progress.
Click to expand...
Click to collapse
What do you mean "killed"? Killed the chip or wiped the MAC addr. or something?

nasko_spasko said:
What do you mean "killed"? Killed the chip or wiped the MAC addr. or something?
Click to expand...
Click to collapse
I'm currently building the Rom with completely removed Bluetooth support

First Build is compiled and ready for a test.. But I can't install the zip. This would be hillarious if it wasn't so annoying

mythos234 said:
Besides I said it can't be installed Hard to test something you can't even install
Click to expand...
Click to collapse
I think that there was a mistake in the partition sizes.. /system was declared as 4.1GB, but it's only 3.6GB. Recompiling with a new value, should be able to flash it then

Good luck develop without documentation for exynos chipset.
But can you tell us more in details how porting works and what are the challenges with it.
Is it hard to develop a rom without samsung binary files and drivers? I know they are proprietary and closed soruce.
If just Samsung could be more developer friendly like Sony.
We can request source for closed binaries here, http://opensource.samsung.com/reception/receptionSub.do?method=inquiryView, most likely they wont answer

Aircondition said:
Good luck develop without documentation for exynos chipset.
Click to expand...
Click to collapse
The lack of drivers makes this a fun exercise almost Where's be the challenge if everything was easy...?

Aircondition said:
Good luck develop without documentation for exynos chipset.
But can you tell us more in details how porting works and what are the challenges with it.
Is it hard to develop a rom without samsung binary files and drivers? I know they are proprietary and closed soruce.
If just Samsung could be more developer friendly like Sony.
We can request source for closed binaries here, http://opensource.samsung.com/reception/receptionSub.do?method=inquiryView, most likely they wont answer
Click to expand...
Click to collapse
I can't say what the challenges here will be, since I couldn't manage to even flash it yet - Second build is compiling since hours now. For now it's using all the proprietrary stuff we managed to grab and some additional stuff from the 5433 CM. But without booting it's hard to tell what won't work and might present a challenge ^^ From what I saw it'll be tough to just get the modem running. The hard part is to write the drivers yourself

mythos234 said:
I can't say what the challenges here will be, since I couldn't manage to even flash it yet - Second build is compiling since hours now. For now it's using all the proprietrary stuff we managed to grab and some additional stuff from the 5433 CM. But without booting it's hard to tell what won't work and might present a challenge ^^ From what I saw it'll be tough to just get the modem running. The hard part is to write the drivers yourself
Click to expand...
Click to collapse
It's interesting that you can use drivers from 5433, which is a 32bit platform. Most drivers are not compatible when you switch from 32bit to 64bit if I am right?
Sent from my SM-G920F using Tapatalk

lch920619x said:
It's interesting that you can use drivers from 5433, which is a 32bit platform. Most drivers are not compatible when you switch from 32bit to 64bit if I am right?
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
As a base to know how to do it, obviously we can't just use drivers for a different chipset

Updated the /system size in the BoardConfig and at least it flashes. But it doesn't want to boot for some reason yet.

mythos234 said:
Updated the /system size in the BoardConfig and at least it flashes. But it doesn't want to boot for some reason yet.
Click to expand...
Click to collapse
If you have the 5.1.1 boot loader and are using 5.0.2 as a base. Sboot will not boot it. As a fyi. It checks Linux versions.

-Mr. X- said:
If you have the 5.1.1 boot loader and are using 5.0.2 as a base. Sboot will not boot it. As a fyi. It checks Linux versions.
Click to expand...
Click to collapse
Both is 5.1.1 and Sboot seems to clear the boot as well, everything seems to go fine, it just doesn't boot. :/ Trying with building the kernel during the build itself instead of using a prebuilt one and see how that goes

mythos234 said:
Both is 5.1.1 and Sboot seems to clear the boot as well, everything seems to go fine, it just doesn't boot. :/ Trying with building the kernel during the build itself instead of using a prebuilt one and see how that goes
Click to expand...
Click to collapse
I would personally flash an Engineering boot loader while doing this, to ensure version checking is not the issue.

Any new stuff?

It has been a long time since i had messed with this device. Any updates? IS marshmallow coming soon?

Pix12 said:
IS marshmallow coming soon?
Click to expand...
Click to collapse
How to know if marshmallow is possible yet:
1. Check the Kexec thread
http://forum.xda-developers.com/amazon-fire/orig-development/kexec-module-ford-t3270272
2. Check bootloader unlock threads
http://forum.xda-developers.com/amazon-fire/development/bootloader-unlock-ideas-t3289721
http://forum.xda-developers.com/amazon-fire/general/lk-analysis-bootloader-checking-t3304401/
Those are the two paths to marshmallow. There will be no marshmallow unless / until there is success with kexec or bootloader.

blueberry.sky said:
How to know if marshmallow is possible yet:
1. Check the Kexec thread
http://forum.xda-developers.com/amazon-fire/orig-development/kexec-module-ford-t3270272
2. Check bootloader unlock threads
http://forum.xda-developers.com/amazon-fire/development/bootloader-unlock-ideas-t3289721
http://forum.xda-developers.com/amazon-fire/general/lk-analysis-bootloader-checking-t3304401/
Those are the two paths to marshmallow. There will be no marshmallow unless / until there is success with kexec or bootloader.
Click to expand...
Click to collapse
Okay thanks

Pix12 said:
Okay thanks
Click to expand...
Click to collapse
Marshmallow is soo yesterday. Android N, baby! Because newer is always better. I'm holding out for Android ZZZ++. Heard the UX is friggin' awesome.

Davey126 said:
Marshmallow is soo yesterday. Android N, baby! Because newer is always better. I'm holding out for Android ZZZ++. Heard the UX is friggin' awesome.
Click to expand...
Click to collapse
In fairness marshmallow would have serious impact on this tablet with the sd integration, especially for the original 8 GB version that most of us have. It's not just a version number bump

Pond-life said:
In fairness marshmallow would have serious impact on this tablet with the sd integration, especially for the original 8 GB version that most of us have. It's not just a version number bump
Click to expand...
Click to collapse
True - along with other innovations such as doze (Greenify lite), a rethought presentation of recents and a nifty new icon pak. Each major feature comes with its own set of liabilities including restrictions on SD card use when used to extend internal storage. Doze wreaks havoc with some apps that prefer to use their own timing and wake up mechanisms. Each successive major Android release reduces developer flexibility and strengthens dependency on Google's invasive framework. Point is newer isn't always better although in general I think Google is probably on the right track given consumer expectations and the need to monetize future development.

[DISCUSSION] Nougat AOSP for ZE500KL ?

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

Oreo project for Moto G5S.

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??

This phone dead already?

Not even a year old and I feel like there is nothing going on with this phone not even from Motorola themselves, haven't had any updates since April 1st, and no custom roms or anything really.
I know Josh has worked very hard at getting TWRP on this phone and credit to him, just a shame the community is almost non existent

tigsandmitch said:
Not even a year old and I feel like there is nothing going on with this phone not even from Motorola themselves, haven't had any updates since April 1st, and no custom roms or anything really.
I know Josh has worked very hard at getting TWRP on this phone and credit to him, just a shame the community is almost non existent
Click to expand...
Click to collapse
Seeing as how this phone already has TWRP, and can be rooted. I'm downloading the source code for Lineage OS 16 right now. I'll be building it for the G7 Plus when it's finished downloading. However, I'm on my laptop which isn't exactly powerful, so it will take a while.

Never has been anything going on with this device! That's why I got myself a Poco F1 for messing about with :+) (and this device is just too slow in any case)
Sent from my POCOPHONE F1 using Tapatalk

lmulli said:
Never has been anything going on with this device! That's why I got myself a Poco F1 for messing about with :+) (and this device is just too slow in any case)
Sent from my POCOPHONE F1 using Tapatalk
Click to expand...
Click to collapse
Which is why I'm building Lineage OS for the phone. Give me about a week or 2 and I'l have lineage OS 16 working.

Thanks! I'm eager to try it out!

serris-chan said:
Which is why I'm building Lineage OS for the phone. Give me about a week or 2 and I'l have lineage OS 16 working.
Click to expand...
Click to collapse
Can't wait to try Lineage on this phone.

tigsandmitch said:
Not even a year old and I feel like there is nothing going on with this phone not even from Motorola themselves, haven't had any updates since April 1st, and no custom roms or anything really.
I know Josh has worked very hard at getting TWRP on this phone and credit to him, just a shame the community is almost non existent
Click to expand...
Click to collapse
Check out our new G7 - River Development & Discussion Group. Most if not ALL Custom work will be released for testing : @MotoG7RiverDiscussion
In my last Group I created for the Essential PH-1 took off and is still running strong with over 500 members.
Don't forget, this device is still very new and let's say Un-Developed, but give it a little time...
---------- Post added at 02:53 PM ---------- Previous post was at 02:51 PM ----------
serris-chan said:
Which is why I'm building Lineage OS for the phone. Give me about a week or 2 and I'l have lineage OS 16 working.
Click to expand...
Click to collapse
Don't forget to Join our TG Group!

HUEguy said:
Thanks! I'm eager to try it out!
Click to expand...
Click to collapse
Andolss said:
Can't wait to try Lineage on this phone.
Click to expand...
Click to collapse
Thanks! I'm waiting on the kernel to be finished. It only compiles to about 99%, then it fails. I'm waiting on someone to finish! Then I'll have lineage compiled within a day or so after they're done.

serris-chan said:
Seeing as how this phone already has TWRP, and can be rooted. I'm downloading the source code for Lineage OS 16 right now. I'll be building it for the G7 Plus when it's finished downloading. However, I'm on my laptop which isn't exactly powerful, so it will take a while.
Click to expand...
Click to collapse
Do you have any guides for building or porting a ROM? All the ones I found are at least 3 years old.
I want to try building ROM's for the 2017 Galaxy A3 though.