Related
I've been following the development of so-called ROMs for the Vibrant (and other SGS devices), but I have yet to see a single AOSP ROM. Even when Samsung released the original kernel sources for 2.1, there were no AOSP 2.1 ROMs. Why not? Is it because they don't know which BLOBs to pull for insertion or the proper vendor overlays?
Some developers have done great work with SGS kernels (especially supercurio and his Voodoo kernels ... eugene373's tend to always wipe the internal SD card unnecessarily ...). But, a kernel does not a ROM make ... therefore I ask, what is truly missing to build an AOSP ROM. I've gone through the sources, but I don't follow makefiles too well.
I know we have another month or so before Samsung is obligated to release their 2.2 kernel sources, but that should have no impact on 2.1 AOSP ROMs. Therefore, I ask "what is the hold up?" What is missing, and what might I contribute ...
Need 2.2 source code...
2.1 is a dead horse--why bother when 2.2/2.3 are out?
The reason to bother is to at least get AOSP running. Once its on 2.1, it'll be easier to get 2.2 AOSP running on it. But claiming 2.1 is a "dead horse" is the wrong path ... the real question still stands: after 9 months on the market their still are no AOSP ROMs.
MIUI
Now that vibrant 2.2 source is released ... we finally have a REAL AOSP port and my all time favorite from my old HD2 the MIUI.... so keep your heads up and wait for it to get finished.
Get a custom rom. There are so many good devs doing them don't waste your time on AOSP....... until they release the actual source code...... on April 22
sarim.ali said:
Now that vibrant 2.2 source is released ... we finally have a REAL AOSP port and my all time favorite from my old HD2 the MIUI.... so keep your heads up and wait for it to get finished.
Click to expand...
Click to collapse
Except, the 2.2 source for the Vibrant has not been released. The SGH-T959D that shows Froyo sources on Samsung's site is for the Canadian Fascinate, not the US T-Mobile Vibrant. Samsung has yet to release the 2.2 sources.
oka1 said:
Get a custom rom. There are so many good devs doing them don't waste your time on AOSP....... until they release the actual source code...... on April 22
Click to expand...
Click to collapse
Except the so-called "custom ROMs" are just modifications on the stock theme, a replacement kernel and a change of some of the supplied applications.
There is nothing close to a full "custom ROM" such as CyanogenMod or MIUI because we don't have Samsung's sources. What is passing for a "custom ROM" for the Vibrant are just repackaged files. It is akin to the "ROM cooking" that took place for the WinMo phones, not a truly ground-up build from source that is possible with Android.
EDT/Devs4Android has the MIUI build. From Source.
TW has a 2.2.1 in testing.
EDT has a 2.2.1 Beta released.
TW has a 2.3 AOSP in testing. From Source.
EDT has 2.2 AOSP in testing. From Source.
What you want is out there for you.
Watch the forums and reply when a call for Alpha testers is posted.
Hopefully it won't be long before you see a full TW/EDT/Devs4Android collaboration!
I think what the original poster is trying to ask (and I have the same question) is why were there never any real 2.1 AOSP, cyanogen5 for the vibrant. The source for 2.1 has been around for many months. Were some other proprietary bits missing, was the released source code such a mess that it was unbuildable, something else? With those questions in mind, why will things be any different when the 2.2 source comes out?
mattb3 said:
I think what the original poster is trying to ask (and I have the same question) is why were there never any real 2.1 AOSP, cyanogen5 for the vibrant. The source for 2.1 has been around for many months. Were some other proprietary bits missing, was the released source code such a mess that it was unbuildable, something else? With those questions in mind, why will things be any different when the 2.2 source comes out?
Click to expand...
Click to collapse
Yes, this is more towards what I was getting at. We do not have Samsung's kernel sources for 2.2. And, we do not have a Samsung provided vendor overlay.
When we receive these two pieces, then a true AOSP build will be possible. However, we do have the 2.1 kernel sources, so why wasn't a true AOSP build possible then? What was missing, and can we actually expect Samsung to release the overlay that's needed?
Actually, that's true. I know it was old but why didn't anyone build a 2.1 cyanogen or aosp rom? (Not to say its easy.)
Sent from my SGH-T959 using XDA App
A noob question, kindly can someone explain what is the vendor overlay stuff?
Many thanks!
Where have you been?
rpcameron said:
I've been following the development of so-called ROMs for the Vibrant (and other SGS devices), but I have yet to see a single AOSP ROM. Even when Samsung released the original kernel sources for 2.1, there were no AOSP 2.1 ROMs. Why not? Is it because they don't know which BLOBs to pull for insertion or the proper vendor overlays?
Some developers have done great work with SGS kernels (especially supercurio and his Voodoo kernels ... eugene373's tend to always wipe the internal SD card unnecessarily ...). But, a kernel does not a ROM make ... therefore I ask, what is truly missing to build an AOSP ROM. I've gone through the sources, but I don't follow makefiles too well.
I know we have another month or so before Samsung is obligated to release their 2.2 kernel sources, but that should have no impact on 2.1 AOSP ROMs. Therefore, I ask "what is the hold up?" What is missing, and what might I contribute ...
Click to expand...
Click to collapse
Dude theres been a true AOSP ROM for the Vibrant since like december and thats CM 6.1
Im running it now
rpcameron said:
I've been following the development of so-called ROMs for the Vibrant (and other SGS devices), but I have yet to see a single AOSP ROM. Even when Samsung released the original kernel sources for 2.1, there were no AOSP 2.1 ROMs. Why not? Is it because they don't know which BLOBs to pull for insertion or the proper vendor overlays?
Some developers have done great work with SGS kernels (especially supercurio and his Voodoo kernels ... eugene373's tend to always wipe the internal SD card unnecessarily ...). But, a kernel does not a ROM make ... therefore I ask, what is truly missing to build an AOSP ROM. I've gone through the sources, but I don't follow makefiles too well.
I know we have another month or so before Samsung is obligated to release their 2.2 kernel sources, but that should have no impact on 2.1 AOSP ROMs. Therefore, I ask "what is the hold up?" What is missing, and what might I contribute ...
Click to expand...
Click to collapse
For probably the same reason that many phones with non AOSP firmware running 1.5/1.6 did not bother with AOSP 1.5/1.6 when they were released around the time 2.1 source hit. Why bother developing at all for what is essentially an "out of date" OS.
The only people it seems who actively continue to develop for existing (as opposed to new) firmware are manufacturers and carriers. This stupidity should be left to the manufacturers who still do this.
One of the larger snags way back then (sits in his rocking chair on the porch) was a lack of understanding of the phones proprietary aspects and how to work around them. But we have a fairly clear understanding of Samsung's boot process now, and RFS can now easily be turned into a distant memory.
I would wager a guess that the apathy towards 2.1 will not repeat itself once we have 2.2 source widely available and the low level similarities between 2.2 and 2.3 should have Gingerbread being more than the experiment it currently is. It's been barely more than a week since Eugene's little present manifested and there are already proper and stable kernels available.
Keep in mind that the devs we do have, have done a phenomenal job of cleaning up, speeding up, and drastically enhancing our existing 2.2 release. And perhaps to the point where many will not really care, though I know many would still like to see CyanogenMod6/7 properly on this phone.
Master&Slave™ said:
Dude theres been a true AOSP ROM for the Vibrant since like december and thats CM 6.1
Im running it now
Click to expand...
Click to collapse
Um, that's not quite true. The CyanogenMod.com website lists 0 files available for download for either experimental or stable files. The CM6.1 you must be running is not a true CM build.
Also, CM is not AOSP, but rather AOSP with modifications.
phrozenflame said:
A noob question, kindly can someone explain what is the vendor overlay stuff?
Many thanks!
Click to expand...
Click to collapse
The vendor overlay tells the AOSP build system which proprietary files are needed from the device that are not available in source form. This includes things like GPS and video drivers, baseband firmware for wireless radios, &c.
hi everybody !
a month age i decided to compile a new rom for my Galaxy S absolutely from AOSP source ( branch 2.2.1_r1 ) after some compile-time problem and many painful steps to resolve ,eventually the rom successfully built and can boot it up flawlessly on emulator.
i create a nandroid backup of current rom and installed the compiled one. but i am facing new problem :
1- the phone successfully boots but after short while screen began
flicking several time and the phone go in deep sleep and never wakeup
( power button or menu button does not do any thing )
2- touch screen works only for some second that I can unlock the
phone
3- there is no network available
4- I have downloaded samsung opesource package for GT-I9000. it
contains a folder named 'platform' but when i merge these files to
AOSP , the compile process stops and fails again. if there any one can
help me which files from samsung source should i merge and how ? if
you now the answer and dont have spare time then some internet link or
online document is really useful .i have no problem studding and
reading and searching . reaching to target is my only hope .
I am really disappointed why there is not a good and complete step2step tutorial to compile an AOSP rom for galaxy s (GT-I9000) !!
such docs is available for phones like dell streak , desire , dream , magic , .... . i really want to to active these aspect on XDA forum and with help of all you ( mods and masters ) try to create such tutorial that any one in world can use to refer . i think XDA is the only reference on net to collect and create such help and document. please help me and leave PM or comment to agree ot disagree and from where can i start ?!! thank in advanced .
edit :
there is a google groups post that i send my question in Android-platform . if you prefer please join this group and active that post to ask any question related to 'galaxy s compile from source ' .
post located at http://groups.google.com/group/android-platform/browse_thread/thread/da5d6f18f3bd3c9b
Hi all,
i'm a noob to android, but i have nit of experience on other unix based systems.
I was wondering, why there is no custom roms for GT-S5690?
What's the problem?
Is bootloader locked some other way or is it somehow different from example Gio/GT-S5660?
There is a bunch of roms for gio..
I have one xcover, wich has no screen and covers, i thought i could use it for testing.
I think there are too less people who have a xcover, and I was actually pretty disappointed when I say there is a successor to the xcover available only in the US (Rugby Smart / Pro <-- with ICS!).
From the technical side, I don't know. Even the source code of the firmware is available at opensource.samsung.com. The Bootloader seems pretty much unlocked.
For me, the xcover is the best phone ever, it takes so much abuse. Maybe someday someone will port a newer ROM from the Ace/Gio/idk. It's a shame Samsung abandons their old phones :crying:
xkawer said:
I think there are too less people who have a xcover, and I was actually pretty disappointed when I say there is a successor to the xcover available only in the US (Rugby Smart / Pro <-- with ICS!).
From the technical side, I don't know. Even the source code of the firmware is available at opensource.samsung.com. The Bootloader seems pretty much unlocked.
For me, the xcover is the best phone ever, it takes so much abuse. Maybe someday someone will port a newer ROM from the Ace/Gio/idk. It's a shame Samsung abandons their old phones :crying:
Click to expand...
Click to collapse
I didn't were aware of successor models, now i'm very dissappointed.
I'm downloading these source codes at the moment, i'll check these out.
I'm not a developer, atleast YET..
AFAIK, hardware of s5690 is way different from any other samsung phones,
correct me if i'm wrong..
jonezy82 said:
AFAIK, hardware of s5690 is way different from any other samsung phones,
correct me if i'm wrong..
Click to expand...
Click to collapse
Seems like it's the only one with a Marvell MG2.
Let me know if you do anything interesting with the sources
Just flashed my xcover to XXLJ2 yesterday. At least it seems a bit faster now, but I have a weird bug when scrolling. If I give a list (for example settings) momentum, it doesn't stop when I put my finger on it again. But it does stop if I release the finger the second time.
jonezy82 said:
I'm downloading these source codes at the moment, i'll check these out.
Click to expand...
Click to collapse
Did the same. The GT-S5690_Platform.txt says:
Code:
How to build platform
1. Get android open source.
: version info - Android gingerbread 2.3.6
( Download site : http://source.android.com )
2. Remove external\webkit module in android open source which you got.
And then execute "clean build"
2. Copy files and modules to original Gingerbread source tree (overwrite)
3. build
- ./build.sh user
So wouldn't it be possible to download the JB sources, and compile them with the original kernel? Would be so cool.
Edit: It seems you need device specific binaries (drivers) since ICS. see: http://www.freeyourandroid.com/guide/compile-ics
Found a git https://github.com/manakeri/android_device_samsung_xcover, there is a
Code:
cyanogen_xcover.mk
file, this seems interesting. Apparently someone is trying to port it.
Edit2: In this git, there is also a "extract-files.sh"-file, which is neccessary to pull the proprietary files from the phone! With this I think we actually have everything we need to compile ICS/JB, like in the "freeyourandroid" tutorial.
I have never done this before, but someone must try it lol.
Oh look, there are more people who care about it!
http://www.droidevelopers.com/f338/14412-gt-s5690-opensource-kernel-available.html
Someone discovered my link and made a overclock kernel from the sources! This is so cool.
I hope we are going to see more :good:
xkawer said:
Oh look, there are more people who care about it!
http://www.droidevelopers.com/f338/14412-gt-s5690-opensource-kernel-available.html
Someone discovered my link and made a overclock kernel from the sources! This is so cool.
I hope we are going to see more :good:[/QUOTE
I own an xcover too a developer on another forum looked at some files i pulled using adb to try to port clockworkmod but no success. Told me the files i sent weren't standard android img but he would continue to look into it. Apparently the teamhacksungs goal is to port cyanogenmod for every Samsung device surely they can get it done. I've been waiting a long time to see some development for the awesome xcover
Click to expand...
Click to collapse
If its possible on the galaxy mini its got to be possible on xcover!. Ive tried to get involved and learn to port cyanogenmod but when it comes to git, repo, source tree, source code e.t.c e.t.c its a bit behond me for now.
Step in the right direction it seems. Fingers crossed
Since everyone kept asking and I myself wanted it, I decided to start this project. The main reason why I didn't do it earlier was because I needed Asus to release the Oreo build already so I could get the required files. So for now I leave you with this, hope I made your day a bit better and have a great day!
Note: the build you see here is just so I could get the compiler working.
Sweet!! Looking forward to seeing the progress on this.
Nice. Do you think the build will have camera quality issues though?
kekley said:
Nice. Do you think the build will have camera quality issues though?
Click to expand...
Click to collapse
We'll see once I get a debuggable build running. I hope it's smooth sailing, but I can't guarantee anything.
First build?
Is this the first build?
If you want tester I am always available.
Naman Vashishth said:
Is this the first build?
If you want tester I am always available.
Click to expand...
Click to collapse
Nice to hear that you want to test the rom, but unfortunately I still don't have a flashable build. I try to work on it whenever I can to get one out as soon as possible. Do keep in mind I do this in my free time when I'm not busy with school. When I do get a debuggable build out, I'll let this forum know so I can get some testers to test it out (other than myself).
+)KEV1N(+ you are a savior , please help us get rid this sick twisted ASUS stock firmware , it's a mess in every aspect , heat, poor battery life, muffled sound via headphones, enormous amount of services running in the background (loses 20% overnight), complete failure in both firmware and kernel wise cause they massively overclocked that S625 , i can live with a rom without the main camera app , OpenCam will do just fine , just take care of that power consumption please cause on paper it should deliver 12-16h SOT , it's 5000mah with s625 and AMOLED screen for god sake !
Thank you in advance for your effort.
Kevin,
Thanks so much for taking on this project!
Not many have the skills or time to do a project like this. I think I can speak for all Z3Z owners when I say that your work will not go unappreciated.
I am simply observing the work of the gentlemen, let us continue in this to create a lineage.
rinampa said:
I am simply observing the work of the gentlemen, let us continue in this to create a lineage.
Click to expand...
Click to collapse
It is a slow process, especially since this is my daily driver. I just came back from holidays back home and now I'll continue to work on it whenever I get the chance. I'll get a working test build running eventually. Can't guarantee when, just know that as a new developer it'll take time to fix things and put them in place since porting is also not easiest of projects.
I visit this thread multiple times a day, it gives me hope)
Thank u Sir
I'm grateful that you are working on this project.
Take your time & carry on.
I want do downgrade form Oreo to MM, Q: will i need to extract recovery.img form MM zip and flash it separately or the stock Oreo recovery will work with all raw asus builds ?
Build# : ww-11.41.87.2 this is the latest MM update before Nougat update, i'm a little confused cause every build has it's own method so any advice for the safest fastest way to :
1-Downgrade to MM from Oreo
2-Flash Magisk to root and install greenify , viper4android cause i'm done with this Oreo.
3-Do i need to unlock the bootloader ?
4-Do i need twrp to flash migisk?
5-Does twrp work with all versions of android ?
3-What are the cons of this procedure if a custom ROM would fall from heaven and i would want to flash it after i flash MM?
sam.fisher190 said:
I want do downgrade form Oreo to MM, Q: will i need to extract recovery.img form MM zip and flash it separately or the stock Oreo recovery will work with all raw asus builds ?
Build# : ww-11.41.87.2 this is the latest MM update before Nougat update, i'm a little confused cause every build has it's own method so any advice for the safest fastest way to :
1-Downgrade to MM from Oreo
2-Flash Magisk to root and install greenify , viper4android cause i'm done with this Oreo.
3-Do i need to unlock the bootloader ?
4-Do i need twrp to flash migisk?
5-Does twrp work with all versions of android ?
3-What are the cons of this procedure if a custom ROM would fall from heaven and i would want to flash it after i flash MM?
Click to expand...
Click to collapse
Guess what !!!
https://forum.xda-developers.com/ze...nbrick-flash-stock-mm-asus-zenfone-3-t3840702
Its more than 100days now since this "little something" post.
Is there any progress dear KEVIN?
or shall I switch to some other device?
Aditya Tiple said:
Its more than 100days now since this "little something" post.
Is there any progress dear KEVIN?
or shall I switch to some other device?
Click to expand...
Click to collapse
I started at the end of my school year a couple of months back. I had a month-long hiatus in July due to me going back to my family back home. I came back in August and am working on it as a side project. Naman's helping me with this right now and so far we got till the boot animation. And then you have those times when we fix something and you go one step back. It's a slow process since the two of us aren't like 24/7 busy on the project. I usually work on it during weekends, but lately I've been needing my phone more and more since I'm very very busy with other priorities. Again, this is a side project I'm doing because I like coding and I like learning new things. So, I can't say for certainty when we can get a release out, but I work eagerly every time hoping it gets past the boot animation or even gets there if I fix something.
I hope this clears out any misconceptions you may have of me and this project. Have a further great day sir
It's nice to hear from you.
That's d very reason I visit this thread.
Keep ur good work going.
Keep us updating.
All d best
Hello mate, you know the whole world is waiting for this build from xda to 4pda to every other android community so what's the news my friend? can you post the bugs maybe we can help with some of them and learn about the Lineage route you chose.
The midterm examination is about to start and you'll be too busy with the study!
My full appreciation to your work.
Instead of quenching our thirst, op made it worse... Shame no developer decided to code for this device.
Mrkblo said:
Instead of quenching our thirst, op made it worse... Shame no developer decided to code for this device.
Click to expand...
Click to collapse
There is a developer who is willing to port lineage if people will crowdfund the purchase of a Z3Z for them.
https://forum.xda-developers.com/zenfone-3-zoom/help/search-developer-custom-rom-t3793680/page2
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....
Hello everyone.
Im new here.
I just want to ask something.
When porting roms can my base ROM and my port ROM have different android version?
Looking forward to having responses
P/s: sorry for bad engrisk )
XdaNeko said:
Hello everyone.
Im new here.
I just want to ask something.
When porting roms can my base ROM and my port ROM have different android version?
Looking forward to having responses
P/s: sorry for bad engrisk )
Click to expand...
Click to collapse
It has been a looong time since I knew about those things but if I remember your base ROM should have that same Android version as your port ROM.
And if you want an advice, please consider building a ROM from source. Troubleshooting is hell with ported ROMs. Building ROM is scary because it has commands that you don't know yet, but it's way more easy than porting. Trust me.
Here is a guide on how to build ROM from source :
https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
@XdaNeko
It's NOT the version of Android what does matter. If that would be the case then an upgrade via OTA never would be possible.
A Stock ROM always at 100% matches phone's hardware ( CPU, GPU, RAM, storage memory, etc.pp ) - it's built by OEM's / Carrier's R&D department, the guys who know best of.
Whereas a Custom ROM necessarily does NOT because it gets built by 3rd-party companies/programmers associations - who think they can do it better, but don't always have the specific Android device at hand.