I'm looking into the possibility of getting Resurrection Remix Marshmallow AOSP ROM running on the Galaxy A5 2017 device of Model Number(s):
A520F (Single SIM Variant)
A520F/DS (Dual SIM Variant)
I've made time available on my hands as i'm a fan of the ROM and it would be great running it up and functional on this device.
I'm hoping this post increases popularity as to attract experienced developers so i can get all the help i need since building an AOSP ROM such as Resurrection Remix from sctrach is very challenging and time consuming.
The Official A5 2017 AOSP (Devs Only) Whatsapp Group is available for all of the developers who would like to join it in helping me bring this Project to life. If your interested in joining and helping, simply post down below your intention in doing so along with your International Contact Number.
Btw here's the Resurrection OS Marshmallow Source:
https://github.com/ResurrectionRemix/platform_manifest/blob/marshmallow/README.mkdn
And here's our device's kernel source which was released by Samsung:
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=A520F
I wanna too, for A3 2017
Wasn't there something on the Whatsapp group about collecting donations for an experienced dev to buy this phone so he could port the rom? I would love to see Resurrection Remix on my A520W. Maybe if a post was made on the forum about donating, more people would see it.
I think that it's will be never possible ,because "Exynox" cpu (drivers problems.....like others devices,like some galaxy note...) ...
But it was truth in the past ....and maybe i was wrong now ,i don't know the last development ...
Loulou-13 said:
I think that it's will be never possible ,because "Exynox" cpu (drivers problems.....like others devices,like some galaxy note...) ...
But it was truth in the past ....and maybe i was wrong now ,i don't know the last development ...
Click to expand...
Click to collapse
Samsung has released kernel source for A series, so it can be done..
But not many dev is intrested with this phone.. because with the same price u can get better specs on chinese phones op3 etc..
ponkz said:
Samsung has released kernel source for A series, so it can be done..
But not many dev is intrested with this phone.. because with the same price u can get better specs on chinese phones op3 etc..
Click to expand...
Click to collapse
Ha ok ,good new for source .:good:
And yes...pity...samsung (exept "s" series) is less and less interested ...
In the past i loved customs roms but now it's maybe good for low and some middle devices but i think that it's a good "regression" ,we loose some good stock options and functiins (like finger print...etc...)... don't have the full exploitation of photo ...less performance.....etc...(samsung stock patent !!!) But yes....with some customs we can change the size,position and color of the hour,battery...etc...lol ! And cm/lineage sourced is not as "stable" as stock firmware ...
Lineage OS in on the horizon. Maybe this will help inspire other developers to take up the Resurrection Remix project or develop their own custom ROMs. But good things are coming in the future.
+387603594331
Hi I am not a developer, but I would like you to add me in the WhatsApp group anyhow. Don't worry I wont be speaking or asking questions. I just would like to able to follow the progress. So if you are willing to add me I would very appreciate it. here is my phone nr. +32472974614
deaniebaby said:
Lineage OS in on the horizon. Maybe this will help inspire other developers to take up the Resurrection Remix project or develop their own custom ROMs. But good things are coming in the future.
Click to expand...
Click to collapse
How so? What tells you lineage os is on the horizon?
vinz244 said:
How so? What tells you lineage os is on the horizon?
Click to expand...
Click to collapse
A group of A5 2017 owners have hired a developer. Waiting on official nougat release for stable build.
deaniebaby said:
A group of A5 2017 owners have hired a developer. Waiting on official nougat release for stable build.
Click to expand...
Click to collapse
Nice! Can I get involved? I have private dedicated server that can be used for builds
vinz244 said:
Nice! Can I get involved? I have private dedicated server that can be used for builds
Click to expand...
Click to collapse
Well I'm in this group and it's been brought up a few times ⟶ https://forum.xda-developers.com/samsung-a-series-2017/how-to/galaxy-a5-2017-whatsapp-t3561455
Maybe hit up the OP and see if you could get in on the action.
deaniebaby said:
Well I'm in this group and it's been brought up a few times ⟶ https://forum.xda-developers.com/samsung-a-series-2017/how-to/galaxy-a5-2017-whatsapp-t3561455
Maybe hit up the OP and see if you could get in on the action.
Click to expand...
Click to collapse
I see the thread has been closed and no more users are being added to the group, how can we keep up to date? I'm very interested in this phone but I'm holding back until I can see that LineageOS has a developer/maintainer.
The_Darkfire said:
I see the thread has been closed and no more users are being added to the group, how can we keep up to date? I'm very interested in this phone but I'm holding back until I can see that LineageOS has a developer/maintainer.
Click to expand...
Click to collapse
If you hit me up on WhatsApp I can try and get the OP to add you to the group. I'll talk to him that you're interested in helping out with the development of Lineage. But once Nougat drops, I think the resources will be available on GitHub.
I hope install the rom too man. a5 a520f/ds.
deaniebaby said:
A group of A5 2017 owners have hired a developer. Waiting on official nougat release for stable build.
Click to expand...
Click to collapse
Nougat released.
Related
I am curious if anyone is currently working on getting CM (or any custom ROM) working for our devices. I'm not trying to bug anyone or get an ETA, but I was thinking about attempting to port CM with their tutorial.
If anyone is working on porting a ROM, or has any tips for me I'd love to talk. Thanks.
I've just started looking into porting CM over to the 5x. I've never built a port before and I'm a bit lost in the CM documentation for it. Feel free to PM me or post below with any tips or advice.
jmiller99 said:
I've just started looking into porting CM over to the 5x. I've never built a port before and I'm a bit lost in the CM documentation for it. Feel free to PM me or post below with any tips or advice.
Click to expand...
Click to collapse
I have only built unofficial builds before, but hopefully since we have source and other Huawei devices with CM, it should be fairly easy.
If you haven't built CM for a device that it's already been ported to, I'd recommend doing that before you attempt to port it.
Good luck. I'll post any progress I make.
Am too eagerly waiting for cm on 5x .fed up of bad performance from stock .heating up too much .I was really disappointed by the heating problem .
What else I had hopes On was the on cm12.1 or 13 .
I usually check for a thread if anyone build one cm ROM for our device but still the development haven't started !
gopinaidu77 said:
Am too eagerly waiting for cm on 5x .fed up of bad performance from stock .heating up too much .I was really disappointed by the heating problem .
What else I had hopes On was the on cm12.1 or 13 .
I usually check for a thread if anyone build one cm ROM for our device but still the development haven't started !
Click to expand...
Click to collapse
I'm *trying* to get CM 12.1 to work for our device, but I've never ported before so don't expect anything soon
gopinaidu77 said:
Am too eagerly waiting for cm on 5x .fed up of bad performance from stock .heating up too much .I was really disappointed by the heating problem .
What else I had hopes On was the on cm12.1 or 13 .
I usually check for a thread if anyone build one cm ROM for our device but still the development haven't started !
Click to expand...
Click to collapse
It's still early. The fact that Huawei makes bootloader unlock codes available and has provided the amount of source code for the kernel that they have has allowed development here to happen much more rapidly than many devices do (particularly devices that lie out side of "volume" interest -- like an S5 or S6). I'm pretty optimistic.
The flip side is that life is so busy for me at the moment that it makes patience pretty easy (as in, if a stable cm13 suddenly became available I still would take my sweet time in getting around to flashing it). If I had more time on my hands it would probably be different.
Yes lets see how long we need to wait !
Can someone (hopefully a dev like @deadman96385, @EarlyMon @cyrusalmighty) confirm/agree that the Honor 5X's (I have KIW-24, US ver.) vendor = HONOR and codename = HNKIW-Q. I'm a little perplexed by what the codename is since HNKIW-Q doesn't seem right. I got that name from the build.prop ro.product.device like CM recommends.
Can anyone confirm that I have the vendor and codename right? Thanks.
EDIT: After looking at similar Huawei devices (Ascend Mate 2) it looks like the codename should just be "kiw". The Mate 2's actual ro.product.device = hwMT2LO3, but it's CM codename is "mt2." Because of this, I think for the CM codename should be "kiw". Does that sound right?
Bandit Development said:
Can someone (hopefully a dev like @deadman96385, @EarlyMon @cyrusalmighty) confirm/agree that the Honor 5X's (I have KIW-24, US ver.) vendor = HONOR and codename = HNKIW-Q. I'm a little perplexed by what the codename is since HNKIW-Q doesn't seem right. I got that name from the build.prop ro.product.device like CM recommends.
Can anyone confirm that I have the vendor and codename right? Thanks.
EDIT: After looking at similar Huawei devices (Ascend Mate 2) it looks like the codename should just be "kiw". The Mate 2's actual ro.product.device = hwMT2LO3, but it's CM codename is "mt2." Because of this, I think for the CM codename should be "kiw". Does that sound right?
Click to expand...
Click to collapse
In theory but the kiw stands for kiwi this info is directly from Huawei and we all like Kiwi more lol. You also do have a L24 US variant
deadman96385 said:
In theory but the kiw stands for kiwi this info is directly from Huawei and we all like Kiwi more lol. You also do have a L24 US variant
Click to expand...
Click to collapse
Thanks. So any custom ROM development for this device will be like Huawei/kiwi? I'm just wondering, because I'd like to know how I should be naming my files specific to Honor 5X ROM development.
EDIT:
Also, @deadman96385 do you mind sharing the partition sizes you used for building TWRP?
Name it kiwi .it sounds really great ! Moreover i dont what others are thinking on naming this device ,but kiwi is maximum minds .Go for it !
Bandit Development said:
Thanks. So any custom ROM development for this device will be like Huawei/kiwi? I'm just wondering, because I'd like to know how I should be naming my files specific to Honor 5X ROM development.
EDIT:
Also, @deadman96385 do you mind sharing the partition sizes you used for building TWRP?
Click to expand...
Click to collapse
https://github.com/Huawei-Kiwi
deadman96385 said:
https://github.com/Huawei-Kiwi
Click to expand...
Click to collapse
I didn't realize you had already started working on a CM port. I guess I can't really help out then. :/
Don't get me wrong, I do really appreciate all the work you do for this device.
Bandit Development said:
I didn't realize you had already started working on a CM port. I guess I can't really help out then. :/
Don't get me wrong, I do really appreciate all the work you do for this device.
Click to expand...
Click to collapse
That cm tree was just to build cm recovery we are still in the very early stages of a full cm tree.
SlimRoms is a custom android operating system. Our main goal is to offer users a slimmed down yet feature rich alternative to other android operating systems.
The entire SlimTeam work together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code.
All of the sources can be publicly viewed through GitHub and you can stop by our public Gerrit to submit patches of any type.
Slim7 is the project name for SlimRoms based on Android 7.1.1 Nougat and offers the following original features:
Slim Navbar & Hardware key rebinding
Single tap action, long press action, double tap action!-We’ve got you covered.
Slim Actions & Chamber of secrets
Customise your device to the fullest -You’re a wizard!
SlimRecents
A Faster alternative to stock recents -Your device, your choice.
SlimLauncher
An Open source, feature filled launcher! -Make yourself at home
Status bar customisations
Clock and Date? Battery? -More fun than you can shake a stick at.
Important links:
slimroms.org - Our official website and your source for anything SlimRoms related.
Downloads - Slimify your device!
Unofficial Downloads J500F and M - Build0.13
Unofficial Downloads J500FN - Build0.13
For information on bugs, requirements, notes and more, read the second post.
Installation instructions - Follow these steps if you want SlimRoms on your device.
FAQ - Have a question? Consider reading our FAQ first, you might find your answer there!.
Report-bugs - Found a bug? Send it our way!
Kernel Source - The source of your device's kernel.
Get in touch! - You can contact SlimRoms at these places if you have questions, requests or feedback.
Google+
Twitter
Facebook
Disclaimer: We are not responsible for any damages to your device.
Can you pour me some coffee?
XDA:DevDB Information
SlimRoms Slim7 Android Nougat, ROM for the Samsung Galaxy J5
Contributors
EsromG5
Source Code: https://github.com/SlimRoms
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Bootloader LP and Modem MM (modem mm for FM works)
Based On: Aosp, Slim
Version Information
Status: Testing
Current Beta Version: Build0.13
Beta Release Date: 2017-02-15
Created 2017-02-15
Last Updated 2017-03-04
Reserved
What works?
RIL (Calls, sms, data)
Bluetooth (also with audio)
Camcorder
Camera general (1080p works fine)
Video Playback
Dados and RIL
Wifi
Audio
Sensors
LED
Flash
Hostpot
InCall
GPS
OTG
FM (use modem MM)
What does not work?
No, you tell me
Notice:
n/a
First
Good job, waiting for FN
second ....
good job bro.. i m so lucky that I own j5f :fingers-crossed:
wooow j5 developement is skyrocking this month, i will install it when theres the proper incall audio (im not crying for fix, just sayin)
Why don't you concentrate first resolving issues on the other roms? What is the sense of releasing every kind of roms but with the same issues?
Booted on FN, but System UI has stopped
Telepracity said:
Booted on FN, but System UI has stopped
Click to expand...
Click to collapse
Without patch?
Deleted
JosephDM said:
Why don't you concentrate first resolving issues on the other roms? What is the sense of releasing every kind of roms but with the same issues?
Click to expand...
Click to collapse
WelI think it is just as good making normal roms. The in-call isue and other bugs are related across all N roms so that means that if it gets fixed on one then you'll have all the other roms fixed in a small matter of time and now you have 3 working Nougat roms instead of one non functioning rom
EsromG5 said:
Without patch?
Click to expand...
Click to collapse
With a patch from lineage os
MM kernel
Amarius1 said:
WelI think it is just as good making normal roms. The in-call isue and other bugs are related across all N roms so that means that if it gets fixed on one then you'll have all the other roms fixed in a small matter of time and now you have 3 working Nougat roms instead of one non functioning rom
Click to expand...
Click to collapse
Not at all. At the moment you have a lot of not working ROM that are not going to work, because if you look at their github, you'll see that authors most likely lack knowledge needed to make them work. Building every ROM available using the same base is a waste of time (and distraction for users) if one can't even fix your issues in one of them. Plus moving to newer version of android without having the previous one fully working is a suicide run. Nougat has a lot of complex changes in it's sources and it doesn't even fully work on some officially supported devices, so don't expect a good ROM of Android 7.1.1 anytime soon and flooding forums with multiple ROMs having the same issues is not going to help it.
Koloses said:
Not at all. At the moment you have a lot of not working ROM that are not going to work, because if you look at their github, you'll see that authors most likely lack knowledge needed to make them work. Building every ROM available using the same base is a waste of time (and distraction for users) if one can't even fix your issues in one of them. Plus moving to newer version of android without having the previous one fully working is a suicide run. Nougat has a lot of complex changes in it's sources and it doesn't even fully work on some officially supported devices, so don't expect a good ROM of Android 7.1.1 anytime soon and flooding forums with multiple ROMs having the same issues is not going to help it.
Click to expand...
Click to collapse
Well... You are right sir. In-call audio is really really important and I wish someone knew why it was happening..
I didn't mean in call audio. I meant this ROM doesn't even boot normally and they have no clue why, yet instead of trying to debug they release bunch of not working builds. Camera doesn't work and it will not work since you'd either have to use updated open source HAL or revert Nougat media changes and it won't be a surprise if I'll tell you they have no idea how to do it. The only real devs, who knew what they were doing left because their work was posted by someone else and now he's making blind commits in hope that things will magically fix themself. They won't. I might as well tell you that development on J5 is dead unless someone new with actual knowledge steps in. Don't expect any significant changes. We can't even take patches from any other msm8916 devices, because they have more advanced development and use a lot of open source projects instead of prebuilt libs like we do. Even camera in CM13 is not fully fixed because open source cam doesn't work for us and after debugging it for 3 weeks I've still didn't come up with reliable solution to make it work (only made some errors dissapear).
Koloses said:
Not at all. At the moment you have a lot of not working ROM that are not going to work, because if you look at their github, you'll see that authors most likely lack knowledge needed to make them work. Building every ROM available using the same base is a waste of time (and distraction for users) if one can't even fix your issues in one of them. Plus moving to newer version of android without having the previous one fully working is a suicide run. Nougat has a lot of complex changes in it's sources and it doesn't even fully work on some officially supported devices, so don't expect a good ROM of Android 7.1.1 anytime soon and flooding forums with multiple ROMs having the same issues is not going to help it.
Click to expand...
Click to collapse
You're not totally sure.
Creating new roms is just to try to see if there are different results and not just to flood the forum with crap.
The name of the forum is XDA - DEVELOPERS, this means that it is of full use to developers, if the person does not know how to help, it just stays silent while someone else can do it. Your help in testing is much appreciated since we are trying to do something free for you, and still prefer to say things like that.
I thank you and respect your concept, but try to help instead.
Amarius1 said:
Well... You are right sir. In-call audio is really really important and I wish someone knew why it was happening..
Click to expand...
Click to collapse
The problem with incall and other stuff is already encountered by SoUnd001, but the big problem is that we're not hitting what it does so it's not booted, you're getting errors with incall and stuff because of the patch you're installing, not because of Rom or current kernel.
NOTICE:
I'm finishing a build for J500FN, we know it may not start properly, but I want to know the result for these users. I hope the sooner I have it all working.
Koloses said:
Not at all. At the moment you have a lot of not working ROM that are not going to work, because if you look at their github, you'll see that authors most likely lack knowledge needed to make them work. Building every ROM available using the same base is a waste of time (and distraction for users) if one can't even fix your issues in one of them. Plus moving to newer version of android without having the previous one fully working is a suicide run. Nougat has a lot of complex changes in it's sources and it doesn't even fully work on some officially supported devices, so don't expect a good ROM of Android 7.1.1 anytime soon and flooding forums with multiple ROMs having the same issues is not going to help it.
Click to expand...
Click to collapse
Considering our device only has Marshmallow we can afford to deal with some bugs. If i read correctly RR 6.0.1 only has the radio bug so we have a working Marshmallow rom. The next logical step is to make Nougat and they do not have a kernel thats Nougat based so thats why they are running into problems and why we have to use patches. Im almost 100% sure that once we get official Nougat to our device, 99% of the bugs in these roms will disappear
[email protected]@!3Z said:
Considering that they have built nougat from source when our device only has Marshmallow we can afford to deal with some bugs. If i read correctly RR 6.0.1 only has the radio bug so we have a working Marshmallow rom. The next logical step is to make Nougat and they do not have a kernel thats Nougat based so thats why they are running into problems and why we have to use patches. Im almost 100% sure that once we get official Nougat to our device, 99% of the bugs in these roms will disappear
Click to expand...
Click to collapse
I think there will not be an official nougat firmware from Samsung.
Gent' said:
I think there will not be an official nougat firmware from Samsung.
Click to expand...
Click to collapse
In the Skies telegram group there was confirmation for official Nougat
EsromG5 said:
You're not totally sure.
Creating new roms is just to try to see if there are different results and not just to flood the forum with crap.
Click to expand...
Click to collapse
FYI: ALL custom ROM are using the same hardware repo's maintained by CAF, CM(Lineage now) or AOSP. There won't be any different results. The most important repos are all the same. The fact that you don't know that and your friend's github sources show that there is nothing to be helped. You're just playing games with users pretending you could make things work. What for? In the end they will be the ones left with nothing but promises. People, who could actually do something left, because someone took their work and published it to take all the applause for it and now you're blindly trying changes hoping they would somehow fix things.
[email protected]@!3Z said:
Considering that they have built nougat from source
Click to expand...
Click to collapse
They built from the source already made by ganesh. Their own changes are blindly trying things that have no right to work in the first place. Builiding android from someone's ready sources is like walk in a park.
Gent' said:
I think there will not be an official nougat firmware from Samsung.
Click to expand...
Click to collapse
Certainly not for J5 2015, maybe 2016 but it could benefit us anyway since these devices are similiar.
I'm done, Moderator will probably soon come and delete my posts since all they care about is keeping forum clean. You may consider this device dead at the moment.
[email protected]@!3Z said:
Considering that they have built nougat from source when our device only has Marshmallow we can afford to deal with some bugs.
Click to expand...
Click to collapse
I understand from your post that Sound001 or EsromG5 did the hard work, but its not like that.
@Nick Verse and @ganesh varma were the ones who built cm12.1 and cm13 from source. They were also working on cm14 source while they were working on cm13.
So, please edit your post and dont mislead people.
Koloses said everything.
Since Nick and Ganesh left J5 development because their project which were working on was posted by someone else, the issues of Nougat CM/AOSP based roms wont be solved.
This:
I might as well tell you that development on J5 is dead unless someone new with actual knowledge steps in.
Click to expand...
Click to collapse
As we all know Xiaomi released KitKat source code for cancro last year, it certainly helped devs. But since the release of marshmallow there has been some significant changes in kernel. Due to Xiaomi not releasing latest source code, it has been a tough road for developers who work hard to bring out the best in our device. Even cm kernel is based on KitKat, it seems. So I decided to create this thread to get suggestions for moving forward with getting source code for our developers
Btw I created a poll in miui forum to get their user's opinion and numbers
Any suggestion on this issue is welcome
Agree with you. I rate the miui post.
The users with miui account have to comment it and rate.
Thanks
Link me please.
mdki1996 said:
Link me please.
Click to expand...
Click to collapse
http://en.miui.com/forum.php?mod=viewthread&tid=511676&extra=page=1&mobile=2
So is there a chance to have official roms for honor 9?
https://www.xda-developers.com/honor-9-kernel-source-released/
Maybe if you looked inside the thread you posted on, There is Lineage OS & Resurrection remix so far
We have some creativ and very good devs here. They need some time for building a stable AOSP base. I know its hard to wait but they do the best to improve our Device. Remember no eta and respect the Rules its a hard job, they do it for free. Donations are Welcome aswell for the Devs
Maybe.
Just keep this in mind, it doesn't matter that much if we get official state or not, what matters the most is getting all the hardware amd features working properly
MotoE2014 said:
So is there a chance to have official roms for honor 9?
https://www.xda-developers.com/honor-9-kernel-source-released/
Click to expand...
Click to collapse
No, it will take some ages(a year or more) to get offical
I have an idea to port Android 9.0 Pie to the Samsung Galaxy J5 Prime. This will most likely be able to be ported to all models of this device.
The idea is that we can port a rom from the Samsung Galaxy J3 (2017), since the specs of the device are *exactly* the same. (If you want to find out for yourself, click this link for the specs of the J5 Prime: https://www.gsmarena.com/samsung_galaxy_j5_prime-8342.php#g570y , and click this link for the J3 (2017): https://www.gsmarena.com/samsung_galaxy_j3_(2017)-8438.php )
The specs are exactly the same (at least on paper), so theoretically speaking, we should be able to port this device's new update, which is Android 9.0 Pie, with Samsung's One UI. First, we should try dirty flashing a rom (Using Odin, since all custom roms are just oreo roms, and most require a stock rom installed already), and see if it at least boots up. If not, we customize software, and try to help it become compatible with the hardware inside of the Galaxy J5 Prime.
Now, here are the problems we will be facing. First, the device tree might be slightly different, which could hinder the process of porting this rom. Second, modifying the stock software is really difficult, especially if you don"t have any experience in porting roms. Third, not all apps are going to be compatible, like the Camera app, unless modified with the data from the oreo Camera app we have in our roms now. And fourth, Wifi and Bluetooth may not work in the first few builds, but could be fixed with using the oreo Wifi and Bluetooth APKs and libs.
So, now that we have gotten all that info out of the way, which developers would like to help? I can do it myself, but I have never ported a rom before, but have done a good amount of research on it. I DO have a test device, which is my trusty old Galaxy J5 Prime (M model). But I would still appreciate some professional help. Anyone can pitch in, but you need some experience or some knowledge on porting roms. And that includes you, tutibreaker! You made so many good roms, and I think you can really help the community on this one!
reserved
I understand that tutibreaker is already working on a port. However, I'm sorry to be pessimistic, but I don't think it's going to be possible; mainly because Samsung still does not release the source code of some kernel M. Anyway you can enter to his Telegram group and try to speak directly with him.
* I am dev, but I am not interested in Android Pie. I prefer to stay in Oreo with root and my mods.
PD: Galaxy J2 Core (J260); J3 2017 (J330); J4 (J400); Xcover 4 (G390). Everyone has the same processor. I was investigating a little. Only for curiosity.
LUCiON3 said:
I understand that tutibreaker is already working on a port. However, I'm sorry to be pessimistic, but I don't think it's going to be possible; mainly because Samsung still does not release the source code of some kernel M. Anyway you can enter to his Telegram group and try to speak directly with him.
* I am dev, but I am not interested in Android Pie. I prefer to stay in Oreo with root and my mods.
PD: Galaxy J2 Core (J260); J3 2017 (J330); J4 (J400); Xcover 4 (G390). Everyone has the same processor. I was investigating a little. Only for curiosity.
Click to expand...
Click to collapse
Thanks for replying, LUCiON3! I understand that getting the source code is impossible, but we can still try. I mean, it's been done many times before. And most of those ports are mostly bugless, and work flawlessly. So if those ports can work, I bet that this port will work flawlessly, when put in front of the right person. And I also consider joining tutibreaker's Telegram group, and try to speak with him directly, of course without asking the ETA of the rom. Also say thanks to tutibreaker from me. (Or I can do it myself lol):good:
Edit: I did know that the Xcover and the J2 had the same SoCs, but did not know about the J4 having the same one too. The things you learn everyday!
LUCiON3 said:
I understand that tutibreaker is already working on a port. However, I'm sorry to be pessimistic, but I don't think it's going to be possible; mainly because Samsung still does not release the source code of some kernel M. Anyway you can enter to his Telegram group and try to speak directly with him.
* I am dev, but I am not interested in Android Pie. I prefer to stay in Oreo with root and my mods.
PD: Galaxy J2 Core (J260); J3 2017 (J330); J4 (J400); Xcover 4 (G390). Everyone has the same processor. I was investigating a little. Only for curiosity.
Click to expand...
Click to collapse
Well, let me show you something
untimateandroid1 said:
I have an idea to port Android 9.0 Pie to the Samsung Galaxy J5 Prime. This will most likely be able to be ported to all models of this device.
The idea is that we can port a rom from the Samsung Galaxy J3 (2017), since the specs of the device are *exactly* the same. (If you want to find out for yourself, click this link for the specs of the J5 Prime: https://www.gsmarena.com/samsung_galaxy_j5_prime-8342.php#g570y , and click this link for the J3 (2017): https://www.gsmarena.com/samsung_galaxy_j3_(2017)-8438.php )
The specs are exactly the same (at least on paper), so theoretically speaking, we should be able to port this device's new update, which is Android 9.0 Pie, with Samsung's One UI. First, we should try dirty flashing a rom (Using Odin, since all custom roms are just oreo roms, and most require a stock rom installed already), and see if it at least boots up. If not, we customize software, and try to help it become compatible with the hardware inside of the Galaxy J5 Prime.
Now, here are the problems we will be facing. First, the device tree might be slightly different, which could hinder the process of porting this rom. Second, modifying the stock software is really difficult, especially if you don"t have any experience in porting roms. Third, not all apps are going to be compatible, like the Camera app, unless modified with the data from the oreo Camera app we have in our roms now. And fourth, Wifi and Bluetooth may not work in the first few builds, but could be fixed with using the oreo Wifi and Bluetooth APKs and libs.
So, now that we have gotten all that info out of the way, which developers would like to help? I can do it myself, but I have never ported a rom before, but have done a good amount of research on it. I DO have a test device, which is my trusty old Galaxy J5 Prime (M model). But I would still appreciate some professional help. Anyone can pitch in, but you need some experience or some knowledge on porting roms. And that includes you, tutibreaker! You made so many good roms, and I think you can really help the community on this one!
Click to expand...
Click to collapse
Porting Pie to J5 Prime is already done and doesn't any kernel modification
To boot on M so it should for all model ...
The port has just some bug reason why it is not shared yet
tutibreaker said:
Well, let me show you something
Click to expand...
Click to collapse
THE MAN THE LEGEND DID IT
WE HAVE PIE
Ultimate thanks from me tutibreaker!
untimateandroid1 said:
THE MAN THE LEGEND DID IT
WE HAVE PIE
Ultimate thanks from me tutibreaker!
Click to expand...
Click to collapse
dude, dont get too happy for it, is far for a public release yet, wanna keep an eye on the dev? check out the telegram group Telegram Group
Telegram News letter
tutibreaker said:
Well, let me show you something
Click to expand...
Click to collapse
Hey I'm interested in this please....