Related
If there aren't any, how can I convert a 6.0.x EXT4 ROM into a F2FS one? I found some guides but only kitkat is mentioned there.
Thank you.
Pure Nexus Project:
http://forum.xda-developers.com/nexus-4/development/rom-pure-nexus-project-layers-t3237366
Chroma:
http://forum.xda-developers.com/nexus-4/development/rom-chroma-03-31-2015-layers-t3069936
The Roms are F2FS compatible, but with the stock kernel included, you'll get a nice and shinny bootloop. For that, you need a custom kernel that supports F2FS. "Taurus kernel" and "Quanta kernel" work perfectly with the new file system. I suggest "Taurus" cause it's got more features and it has almost the same battery and performance as Quanta. And I also suggest "Pure Nexus Project" as ROM, cause it's got pretty much every feature you want, it's "polished", no bugs, and overall it gives you a very nice and smooth experience.
Taurus kernel:
http://forum.xda-developers.com/nexus-4/general/kernel-taurus-mr1-r13-t3145519 (choose AOSP when you download it)
Quanta:
http://forum.xda-developers.com/nexus-4/development/kernel-sabermod-franco-kernel-r211-t2858561
You should migrate to F2FS only the "cache" and "data" partitions, cause only those are used the most. Formatting the "system" to f2fs won't give any improvements except for maybe a bootloop if you're "lucky".
Follow this tutorial:
http://forum.xda-developers.com/nexus-4/help/guide-detailed-f2fs-manual-format-guide-t3264185
Thank you, but the first ROM you linked has cast function broken, as I see in the comments. I'll try Chroma with Taurus!
I'm still not able to understand why I couldn't find by myself that f2fs guide you linked
Also, how can you tell that those two ROMs are F2FS compatible? I didn't find any information in their topics. For example: is MinimalOS compatible too?
http://forum.xda-developers.com/nexus-4/help/guide-detailed-f2fs-manual-format-guide-t3264185 take a look
ROMs just work and don't ask for password on first boot.
Yeah, I read that. I mean how to know if a ROM is compatible before flashing it and realizing it asks for a password or whatever.
I guess, you just ask the developer. It's the simplest way to know whether the ROM supports f2fs or not. A "mention" (eg: @TheArt. ) should draw his attention and you could get an answer quicker than you'd expect.
Cheers !
Hi... I've been reading some news about Project Treble, and how it helps with the custom ROM development and software updates. But I want to ask. Is this working on phones like the Galaxy S5? Because it would be helpful considering the potential of this phone and how stable it is running on Nougat, and an Oreo update would be easier to Port.
Unfortunately, it's not. It is only compatible with phones that were initially shipped with Android 8.0.
camellirite said:
Unfortunately, it's not. It is only compatible with phones that were initially shipped with Android 8.0.
Click to expand...
Click to collapse
But Huawei Mate 9 got an AOSP build of Oreo in one day thanks to this. And it has never gotten updated since Nougat. It used Treble as the blog said.
Raynelfss said:
But Huawei Mate 9 got an AOSP build of Oreo in one day thanks to this. And it has never gotten updated since Nougat. It used Treble as the blog said.
Click to expand...
Click to collapse
After reading that article, you're right. I read a news article that said only phones shipped with 8.0 will be compatible with treble, my mistake.
Raynelfss said:
But Huawei Mate 9 got an AOSP build of Oreo in one day thanks to this. And it has never gotten updated since Nougat. It used Treble as the blog said.
Click to expand...
Click to collapse
Mate 9 have 4.4 kernel with android Oreo. S5 have 3.4 kernel always. And treble is compatible by phones with 4.4 kernel and above. So no treble for s5.
djgigi94 said:
Mate 9 have 4.4 kernel with android Oreo. S5 have 3.4 kernel always. And treble is compatible by phones with 4.4 kernel and above. So no treble for s5.
Click to expand...
Click to collapse
Ok... That's sad but ok. At least we are having Oreo anyway! Thanks for clarifying. Close thread please!
djgigi94 said:
Mate 9 have 4.4 kernel with android Oreo. S5 have 3.4 kernel always. And treble is compatible by phones with 4.4 kernel and above. So no treble for s5.
Click to expand...
Click to collapse
I heard something about repartitioning, so it doesn't necessarily has to do with the Kernel, it's more like partitioning the device storage, with A/B partitions and stuff with vendor. I heard about a tool that can do that job called REPIT but I didn't do so much of a research of it.
Mi3 with snapdragon 800 on kernel v 3.10 got android p today so is there any hope for our s5s ,can it be ported to our phones like the redmi devs did
https://www.xda-developers.com/xiaomi-mi-3-xiaomi-mi-4-xiaomi-redmi-4x-android-pie-ports/
I looked into it.
In order to get Project Treble working on our Samsung Galaxy S5, we would have to :
- Repartition device to have 2 partitions, Vendor & AOSP
1. All vendor-specific blobs should be moved to /vendor
2. Some blobs load config files from /system/etc. Just hex-edit them to load from /vendor/etc instead
3. Label and format that unused new partition as /vendor - this should be automatically done with an OTA script
4. The kernel should mount the new partition as /vendor as well
OR
https://forum.xda-developers.com/pr.../tool-capire-le-treble-terble-vendor-t3774629
Without repartitioning?
- Have a 'Treblified' ROM already installed. (I believe we have Oreo ported..)
- Have 8.1 Vendor Blobs? I don't know much about this.
Any dev willing to make this dream a reality, please, step forward!
Rhioun said:
I looked into it.
In order to get Project Treble working on our Samsung Galaxy S5, we would have to :
- Repartition device to have 2 partitions, Vendor & AOSP
1. All vendor-specific blobs should be moved to /vendor
2. Some blobs load config files from /system/etc. Just hex-edit them to load from /vendor/etc instead
3. Label and format that unused new partition as /vendor - this should be automatically done with an OTA script
4. The kernel should mount the new partition as /vendor as well
OR
https://forum.xda-developers.com/pr.../tool-capire-le-treble-terble-vendor-t3774629
Without repartitioning?
- Have a 'Treblified' ROM already installed. (I believe we have Oreo ported..)
- Have 8.1 Vendor Blobs? I don't know much about this.
Any dev willing to make this dream a reality, please, step forward!
Click to expand...
Click to collapse
Looks nice. It would be great to try. If someone does try please post your experience here!
clockstoper said:
Mi3 with snapdragon 800 on kernel v 3.10 got android p today so is there any hope for our s5s ,can it be ported to our phones like the redmi devs did
https://www.xda-developers.com/xiaomi-mi-3-xiaomi-mi-4-xiaomi-redmi-4x-android-pie-ports/
Click to expand...
Click to collapse
Xiaomi have a terribke habbit of skipping android versions
Take the MiBox for example, from what i hear it never got an official 7.1.2 only leaked builds, they went from 6.0 to 8.0 and still face quite alot of bugs.
don't know if this is the right place for this but my old moto g 2014 with 3.4 kernel version just got android pi port its very smooth as per the reports, i have not installed it yet as i gave that phone to my mom. the phone runs on with a lowly snapdragon 400 chip and 1gb ram also its kernel version is 3.4 which is the same as our s5s so there might be a good chance android pie can be ported to our device
LINK
https://forum.xda-developers.com/moto-g-2014/development/titan-xperience-13-0-t3830834
did some further searching and found that lenovo zuk z1 also got Pie and it has SD 801 chip like our S5 so things looking quite promising tbh.....
LINK
https://forum.xda-developers.com/zuk-z1/orig-development/rom-pixel-experience-t3830494
clockstoper said:
don't know if this is the right place for this but my old moto g 2014 with 3.4 kernel version just got android pi port its very smooth as per the reports, i have not installed it yet as i gave that phone to my mom. the phone runs on with a lowly snapdragon 400 chip and 1gb ram also its kernel version is 3.4 which is the same as our s5s so there might be a good chance android pie can be ported to our device
LINK
https://forum.xda-developers.com/moto-g-2014/development/titan-xperience-13-0-t3830834
did some further searching and found that lenovo zuk z1 also got Pie and it has SD 801 chip like our S5 so things looking quite promising tbh.....
LINK
https://forum.xda-developers.com/zuk-z1/orig-development/rom-pixel-experience-t3830494
Click to expand...
Click to collapse
Anyone working on 9.0 for S5?
Official Aex devices will get 9.0 soon so yes I presume
The Galaxy S5 (klte) Kernel source on LOS has reportedly submitted comments about LineageOS 16. So we're having our pie soon.
LineageOS 16.0 teaser trailer by haggertk.
Rhioun said:
I looked into it.
In order to get Project Treble working on our Samsung Galaxy S5, we would have to :
- Repartition device to have 2 partitions, Vendor & AOSP
1. All vendor-specific blobs should be moved to /vendor
2. Some blobs load config files from /system/etc. Just hex-edit them to load from /vendor/etc instead
3. Label and format that unused new partition as /vendor - this should be automatically done with an OTA script
4. The kernel should mount the new partition as /vendor as well
OR
https://forum.xda-developers.com/pr.../tool-capire-le-treble-terble-vendor-t3774629
Without repartitioning?
- Have a 'Treblified' ROM already installed. (I believe we have Oreo ported..)
- Have 8.1 Vendor Blobs? I don't know much about this.
Any dev willing to make this dream a reality, please, step forward!
Click to expand...
Click to collapse
I've heard from the official website of lineage os that they can turn a device into an A/B device, but I am not sure that whether the A/B device is the one that have 2 partitions, here it is (https://lineageos.org/Changelog-19/)
Frank Telescope said:
I've heard from the official website of lineage os that they can turn a device into an A/B device, but I am not sure that whether the A/B device is the one that have 2 partitions, here it is (https://lineageos.org/Changelog-19/)
Click to expand...
Click to collapse
Its not as simple as having a/b partitions , there is a kernel issue. a simple google search wich show you guys that there is a minimum kernel version required for treble which the s5 is far and i mean far behind that minimum requirement for treble.
I know this is like off-topic but there is now a project WIP going on for Samsung Galaxy S3 Neo, since it's using 3.4 kernel, we using S5 have luck to support treble. At least if someone willing to do it.
For the AB partition it might be impossible to do so.
Now with pascua28's Intelli-Kernel we're even closer to the dream. This guy has managed to do wonders with this device... The last thing that may happen is him being able to update our Kernel version. I don't know how the A/B partition things work, but from what I've heard it requires a higher Kernel version. The S5 runs 3.4 right now, but with @pascua28 work it may get a higher version soon.
In this Article by Mishaal Rahman , we can understand why OnePlus and Nokia doesn't have treble support to their devices.
I open this thread to discuss about your opinions about how danger can be to create vendor partition outside system partition.
Tell us your opinion and how we can do it safely!
/vendor
FSadino said:
In this Article by Mishaal Rahman , we can understand why OnePlus and Nokia doesn't have treble support to their devices.
I open this thread to discuss about your opinions about how danger can be to create vendor partition outside system partition.
Tell us your opinion and how we can do it safely!
Click to expand...
Click to collapse
That partition is not accessible by the user or anyone else unless the phone is rooted, and it's no more dangerous than having the drivers and libraries in the system partition, OnePlus, as nothing more than a rebranded oppo, as well as Nokia, just don't want to put in the effort, Google has made it perfectly clear that treble is not optional, it is mandatory for devices shipping with Oreo and later, Nokia and OnePlus can do what they want with existing phones, but even they have no real choice that to support treble, unless of course that want to be stuck on phones shipping with nougat and maybe upgrading to Oreo, both of them will see the Android world passing them by and their implementations of Android will become more and more fragmented. Each to their own I suppose
Repartitioning a phone carries a certain risk, especially if it is done via OTA Update, but there are ways to do it and make it relatively safe...if you are willing to put in the work. I think that's the main point.
To me, it's much more interesting to see right now, how OEMs actually use Treble. They no longer have the excuses they used to, so someone like Sony should now be able to provide the Update to Android 8.1 within Days instead of Months...but will they actually do it?
The reasoning behind OnePlus deliberately not using Oreo on the 5T and not preplanning the extra partition...well, that tells it's own story. Not really that unexpected. Nokia though...I would have expected more from them, since they started with big promises about Stock Android and fast Updates, but so far very little has materialised...
I really think people are blowing this up far more then it needs to be. In the Google article it stated that even after the treble code is sent, the oems will still have to make their changes. So as far as I can see this will only matter to oems.
I expect to see many devices with day one 8.0 updates for a while.
Well, like I said, this will be the benchmark for Updates in the future. Since a new OS version can now boot on a phone without any big changes to the UI, Drivers or Apps, it SHOULD be far quicker. How much quicker will be interesting to see. Custom ROMs already show how fast the process can be...so... interesting times!
CommanderROR said:
Well, like I said, this will be the benchmark for Updates in the future. Since a new OS version can now boot on a phone without any big changes to the UI, Drivers or Apps, it SHOULD be far quicker. How much quicker will be interesting to see. Custom ROMs already show how fast the process can be...so... interesting times!
Click to expand...
Click to collapse
Yeah if you don't want any of the main features from the oem. Like Samsung cameras on aosp. Things like that.
As for faster updates. I doubt it. As now the oems will, have to do twice the work. Instead of adding their code to the stock frameworks. Now they will have to make completely new framework files to over write the default. Downloads will be a lot bigger now as well.
Hmm... that's not the way I understand Treble!
From what I've read, the OEM can basically exchange the OS Version without really touching much of their OEM UI...
The fact that Custom Roms are limited is mostly due to the fact, that devs don't have access to the OEM Sources, so they can only compile AOSP versions of Android...
CommanderROR said:
Hmm... that's not the way I understand Treble!
From what I've read, the OEM can basically exchange the OS Version without really touching much of their OEM UI...
The fact that Custom Roms are limited is mostly due to the fact, that devs don't have access to the OEM Sources, so they can only compile AOSP versions of Android...
Click to expand...
Click to collapse
And see that is why XDA articles are crap. The way OEMS roms have worked for years is that they replace and/or recode all of googles files. Now they will have to make even more. To over write them.
That is what you will get. Either AOSP or OEM. The aosp will not have access to the OEM code. Nor will OEM push their code to aosp for google to make things work right. This comes from the fact that OEMS dont write the drivers and code for alot of the hardware. They get that from others.
Just checked, my us997 LG G6 has a symlink for 'vendor', it points to 'system/vendor'... so no separate partition on the G6 either... I was hoping! alas.
Not unexpected...the G6 launched way before Treble was announced and hasn't been Updated to Oreo yet...
They should build a tool and require a wired connection to a pc to repartition and fallback just in case.
FWIW, I made patches to AOSP to be able to have a vendor partition WITHOUT needing to repartition, here:
https://github.com/phhusson/treble_experimentations/tree/master/no-vendor
The way it works, is it tells the kernel to look at the "system" partition, as if it was an hard-drive, to look for partition table, and then use partitions inside this fake hard-drive
Clever. Sell that idea to Oneplus and Nokia please...?
CommanderROR said:
Clever. Sell that idea to Oneplus and Nokia please...
Click to expand...
Click to collapse
I might be a good coder, but definitely not a good seller
phhusson said:
FWIW, I made patches to AOSP to be able to have a vendor partition WITHOUT needing to repartition, here:
https://github.com/phhusson/treble_experimentations/tree/master/no-vendor
The way it works, is it tells the kernel to look at the "system" partition, as if it was an hard-drive, to look for partition table, and then use partitions inside this fake hard-drive
Click to expand...
Click to collapse
Did you already tried this? I mean, I'm not developer and I can't understand the pros/cons about your patch but is extremely interesting!
@franciscofranco @eng.stk @Sultanxda @flar2 can you guys share your opinion about this? Thanks in advance
FSadino said:
Did you already tried this? I mean, I'm not developer and I can't understand the pros/cons about your patch but is extremely interesting!
Click to expand...
Click to collapse
Yup, actually my main testing device for my Treble ROM is a device using this.
Pros:
- doesn't need to repartition
- Easy to integrate
Cons are only for community rom devs:
- /system and /vendor are in read-only, even if dm-verity is disabled, the only way
- some TWRP change is required
- fastboot flashing will require to launch a s cript to merge system.img and vendor.img and flash both at the same time
Frankly, I'd guess OEMs had better to repartition. If you don't move partitions, only split system into system/vendor, and write the script with error-checking in mind, I really can't see how you would brick your device.
But this patch makes it possible to answer to OEMs saying they can't because of missing vendor partition
It will be interesting to see what happens, if a Device with strong XDA Community support like the OnePlus lineup can be "Trebleized" by the community and then supported more easily without help from the OEM that made it.
Following up here, very curious about where this is going.
Not a developer, but willing to test, my device is OP3T.
In light of a dev getting Treble support on the Redmi Note 4X, is it possible to get it on our devices too? I'm willing to test.
phhusson said:
FWIW, I made patches to AOSP to be able to have a vendor partition WITHOUT needing to repartition, here:
https://github.com/phhusson/treble_experimentations/tree/master/no-vendor
The way it works, is it tells the kernel to look at the "system" partition, as if it was an hard-drive, to look for partition table, and then use partitions inside this fake hard-drive
Click to expand...
Click to collapse
Does the Zenfone 4 use your patch actually? (didn't checked if sources are available yet)
I read a while back that first devices (or just one device?) is now project treble ready without vendor partition, not knowing you might have anything to do with it...
For reference:
https://www.androidpolice.com/2017/11/26/phones-updated-support-project-treble-continuously-updated/
Sent from my OnePlus 3T using XDA Labs
Hello to al. first let say me, excuse my bad english. Currently from Argentina and got this new phone. I Really like it and because i'm a real careful-guy with cellphones, i like yo transform it to f2fs filesystem...
My early cellphones, an S1 and S4 Mini deaths by emmc problems. really use them and i think that ext4 FS killed them...
well. thanks a lot already
Don't try it. Flashing stock rom over F2FS file system may result in hard brick. The rom may not support F2FS.
hope anyone reseased it.. f2fs is more faster responsive but also more experimental
since arter97 has fixed GC performance issue i would have f2fs on my mi a1
Hi all,
I am searching and wondering for any guides/ experience/ instructions about:
Can Project Treble be ported to a device where the support is not introduced by the official vendor?
What would be required to do so? I wonder if it would be possible to use the information provided from a released kernel source in combination with some re-partitioning (?), but these are just guesstimates.
So can anyone share some insight please? I think the possibilities such a project could introduce for custom rom developments would be even much more noticeable than right now. But that's just my 2 cents.
Looking forward to hear your thoughts and productive input.
P.S.: Please keep it friendly and productive as I know this is a topic with high chances for very different point of views and that is a good thing as long as everyone is not judging, polite and fine with co-existing opinions.
---
Update: 9th May 2018
I found an interesting lead for enabling treble on devices which current partition layout would not allow it otherwise:
https://github.com/Lanchon/REPIT
Given my understanding of project treble, I would say no. This is due to the fact that you would have to have the individual drivers and their own partitions. So I believe you would have to have those drivers and the partitioning set up from the vendor in order to do it. Then again, this is xda...someone may figure out a way to do all this and make some magic!
@BakedTator Do you reckon an open-source Treble-compatible alternative could be made?
We could call it "Bass".
majamee said:
Hi all,
I am searching and wondering for any guides/ experience/ instructions about:
Can Project Treble be ported to a device where the support is not introduced by the official vendor?
What would be required to do so? I wonder if it would be possible to use the information provided from a released kernel source in combination with some re-partitioning (?), but these are just guesstimates.
So can anyone share some insight please? I think the possibilities such a project could introduce for custom rom developments would be even much more noticeable than right now. But that's just my 2 cents.
Looking forward to hear your thoughts and productive input.
P.S.: Please keep it friendly and productive as I know this is a topic with high chances for very different point of views and that is a good thing as long as everyone is not judging, polite and fine with co-existing opinions.
Click to expand...
Click to collapse
I'd say it's possible.
There are some good tentatives on the way on some devices, and it seem to have nicely progressed.
It is still not able to boot GSI, but I'm quite confident.
FWIW, this has basically nothing to do with kernel sources, and not with partitioning either.
phhusson said:
I'd say it's possible.
There are some good tentatives on the way on some devices, and it seem to have nicely progressed.
It is still not able to boot GSI, but I'm quite confident.
FWIW, this has basically nothing to do with kernel sources, and not with partitioning either.
Click to expand...
Click to collapse
Thank you for the info, especially for the FWIW part. Nevertheless, could you please be so nice to share what you know what is neccessary instead? I'm not finding any good leads/ information sources about this topic so far. Would be appreciated
zoomer296 said:
@BakedTator Do you reckon an open-source Treble-compatible alternative could be made?
We could call it "Bass".
Click to expand...
Click to collapse
You heard the man...he says it's possible...I would listen to him over me any day! Lol. Would be nice to see it happen...make more rooms reach more devices
mi5devs are porting Treble to Xiaomi MSM8996 devices (Mi5, Mi5S, mi5S plus, Mi Mix, Mi Note 2)
https://review.lineageos.org/#/q/topic:xiaomi8996-treblize-all-the-things
Nice... the avalanche is starting
Codeworkx is working on bringing treble to Oneplus 5/5T.
https://review.lineageos.org/#/c/205186/
Yes: https://forum.xda-developers.com/re...other-development/rom-lineageos-15-0-t3690465
Another device with Treble ported, Redmi 3S (Land)... @TeamMex has brought in initial Treble support to Redmi 3S just like it was done on Redmi Note 4, using Cust as the Vendor partition... Hope He has great success in it...
Source: https://plus.google.com/u/0/+klozzjesus/posts/5REcrMxfq67
Correct me if I'm wrong. To use Treble device must have /vendor partition right? So if device have this partition by default it will be easier to implement it?
Sent from my Nexus 5X using XDA Labs
Banan PL said:
Correct me if I'm wrong. To use Treble device must have /vendor partition right? So if device have this partition by default it will be easier to implement it?
Click to expand...
Click to collapse
Yes, but devices that have extra AOSP unused partitions, such as the Xiaomi /cust and Motorola /oem can have those partitions mounted as /vendor for treble ports. I'm guessing what's most important is that the partition has enough space for all the vendor blobs
I'm wondering about why they can make their devices (like xiaomi redmi 4 .Etc) adapt to treble.
The vendor code is close-source isn't it? So they write the code completely by them selves????
KuwaLee said:
I'm wondering about why they can make their devices (like xiaomi redmi 4 .Etc) adapt to treble.
The vendor code is close-source isn't it? So they write the code completely by them selves????
Click to expand...
Click to collapse
No. There were HALs before Treble, they just connect the old HALs to binderized HALs, Google even wrote several such converters.
(That's a big simplification, they still had to do a lot of work for that, that's not easy)
phhusson said:
No. There were HALs before Treble, they just connect the old HALs to binderized HALs, Google even wrote several such converters.
(That's a big simplification, they still had to do a lot of work for that, that's not easy)
Click to expand...
Click to collapse
I didn't thought it was possible without rewriting the blobs...are you willing to share some more details/resources to help other people do the same with other terminals?
For example, the whole Xperia X line has an oem partition which can be used as vendor (in the aosp version is used to store the blobs, and they also have some HALs binderized https://github.com/sonyxperiadev/device-sony-common/blob/master/manifest.xml)...but there is still something missing for full treble support.
Thank you
@phhusson when we get Android P dev preview images can we extract/make something to get them work on every treble device or do devs need sources released?
stunned said:
@phhusson when we get Android P dev preview images can we extract/make something to get them work on every treble device or do devs need sources released?
Click to expand...
Click to collapse
Hard to say. I'd say we'll need the sources.
That means that unsupported MTK devices that are still stuck on 6.0 would be able to use treble?
Then if kernel source are necessary for treble would it be possible for devices using MTK Helio Cpus to be finally updated to 8.1 as Kernel Sources are only available for a couple devices using Helio X SOCs?
For instance Helio X20 source are available from Vernee that helped developers building a semi-stable 7.1 ROM for LeEco X62x devices while the Redmi Note 4 MTK is stuck on AOSP 6.0
I think there is a way. We need to explain how Treble Works (I think anybody know's but casual users)
Devices with Treble Support had a /vendor partition with vendor, kernel and all things needed to boot, Before treble all these things will be on /system partition. Now what we can do ?
We can:
- add /vendor partition by adb
What developers need to know to port Treble sucessfully
- Developers need to know how to mount all drivers to be visible for android in /vendor partition