Forgive me if I'm being stupid but I was wondering if the nexus 7 used the new f2fs file system? I recently purchased a new deb version of the nexus 7 coming from the old 2012 variant (which I already forgot the code name of) but I remember the drastic performance improvement it received from the implement of f2fs. I've searched around the forum and found nothing on this which I found pretty strange considering the galaxy nexus, nexus 4, nexus 7 2013, and nexus 5 have already obtained it. So I was thinking that maybe it shipped like that by default? My question is just whether any devs are looking into it or have had it cross their mind. I bring this up because performance isn't bad or anything it's just that I like future proof my stuff I paid for and considering a new 2014 model might come out son I don't want to feel like if I should have waited a few extra months to get that new one. And considering implements such as this can make the moto x (which I have) perform better than most high end devices I'd feel like this would have me on check for quite some time. Thanks!
afaik no device outside the moto x/g use it by default, and that's only with the oem moto rom.
The play edition moto g does not use it either.
Definitely no nexii device does nor does the galaxy s's or htc one m7/m8.
There are mods to reformat and use f2fs on devices without it by default though,
I would imagine all you would need is a kernel with it enabled and the right support binaries for your rom.
I believe there is already an existing mod made for the n4/mako, but I do not actually use it so I could be mistaken
TheManii said:
afaik no device outside the moto x/g use it by default, and that's only with the oem moto rom.
The play edition moto g does not use it either.
Definitely no nexii device does nor does the galaxy s's or htc one m7/m8.
There are mods to reformat and use f2fs on devices without it by default though,
I would imagine all you would need is a kernel with it enabled and the right support binaries for your rom.
I believe there is already an existing mod made for the n4/mako, but I do not actually use it so I could be mistaken
Click to expand...
Click to collapse
Alright thanks for the info! it's really interesting to know that the gpe edition of the moto g doesn't have it either.
What I meant by those nexus devices having it is that devs here from xda have already ported it and claim to make the devices faster than fast. And I really want to get in that action lol
As far as support for that file system goes I believe CM is compatible with it by default without any modification, and I know that on the nexus 5 the elementalx kernel which we have already supports that and I'm guessing it wouldn't be difficult for the developer to support that here as well. So really it comes down to whether anyone takes a shot at actually creating a recovery to reformat the file system that way
abrahammmmmmm_ said:
So really it comes down to whether anyone takes a shot at actually creating a recovery to reformat the file system that way
Click to expand...
Click to collapse
https://github.com/CyanogenMod/android_bootable_recovery/blob/fd6b35cc09b64f21e66dcc8468228defcea75fe4/nandroid.c#L622 said:
Code:
const char *filesystems[] = { "yaffs2", "ext2", "ext3", "ext4", "vfat", "rfs", "f2fs", NULL };
Click to expand...
Click to collapse
It seems that CWM at least already supports f2fs, in that case it's simply telling it that it should be mounting that specific partition as f2fs.
If f2fs support is enabled by default in CM also, it's then simply a case of having that kernel with it enabled, setting the rom to mount as f2fs, and reformatting the partition to f2fs.
You would need to have a seperate varients of your recovery though since you need to unpack and repack them to tell them to use f2fs
(all this is really similar to enabling ext4 on older devices I did a few years ago)
TheManii said:
It seems that CWM at least already supports f2fs, in that case it's simply telling it that it should be mounting that specific partition as f2fs.
If f2fs support is enabled by default in CM also, it's then simply a case of having that kernel with it enabled, setting the rom to mount as f2fs, and reformatting the partition to f2fs.
You would need to have a seperate varients of your recovery though since you need to unpack and repack them to tell them to use f2fs
(all this is really similar to enabling ext4 on older devices I did a few years ago)
Click to expand...
Click to collapse
Interesting, I'd be willing to take a shot at it considering I've still got about ~20 days of best buy in store warranty just in case I'd get it into an irreparable state. But of course I'd need of some help and external knowledge since I don't know where I should get started really. Though before any of that happens the developer for elementalx should add support for f2fs, I really hate asking for things but I'll give it a try
abrahammmmmmm_ said:
Interesting, I'd be willing to take a shot at it considering I've still got about ~20 days of best buy in store warranty just in case I'd get it into an irreparable state. But of course I'd need of some help and external knowledge since I don't know where I should get started really.
Though before any of that happens the developer for elementalx should add support for f2fs, I really hate asking for things but I'll give it a try
Click to expand...
Click to collapse
ElementalX already has f2fs support.
mdamaged said:
ElementalX already has f2fs support.
Click to expand...
Click to collapse
*facepalm* I just ran the terminal command and indeed saw f2fs, I thought the kernel was device specific so it wasn't implemented here on the nexus. Now it's just whether I can figure out how to reformat the system onto what I want
Update: things are looking pretty complicated based on how other devices implement it such as the N5 so maybe only an experienced dev would be able to actually get this ball rolling. Aka I can't do it at least not alone. Shame since I fell like that would make our rock solid tablet turn into a diamond
Related
Howdy folks
I'd like to thank:
Dan Rosenberg (djrbliss) for Loki (the exploit that allows for custom boot images)
Dees_Troy (for TWRP)
Everybody who has contributed to the CyanogenMod Project
xiaolu for github tools used for unpacking and repacking boot images
I picked up my brand new LG G2 on Friday and I've been hard at work to get CM10.1 booting on it ever since yesterday; but a few hours ago I got my first boot -> http://imgur.com/a/1sZz2
I'm using a few proprietary files that I'd like to not use in the future (more than just the Adreno blobs)
But I'm looking to get a team together to get this working 100%
I will post device and vendor source as soon as I get back from cleaning gutters at my dad's house
What works:
Literally nothing, Android won't boot unless you have the necessary EGL libraries, so I just threw those in because I knew it would boot, and nothing else just to get a bare-bones (but booting) ROM. You can navigate throughout UI fine though (it's very smooth believe it or not).
I'll also upload a proof-of-concept build for those willing to see what CM10.1 will look like on our G2s. I'm currently unable to flash a zip in TWRP recovery, so I have to boot into recovery, wipe data, boot into fastboot, flash a system.img and a boot.img and reboot
If I were any person who likes to ROM but will like to remain stock until there's a stable ROM, I'd add a random "#" to any empty line in the file /system/build.prop which will throw off the sha1sum checker when the recovery goes to install an OTA update (this will block all OTAs from ever installing, thus keeping the current boot image exploit viable and it won't be patched up as the OTA won't be able to install. (root is required)
Edit: kernel, device and vendor sources are up!
https://github.com/JackpotClavin/android_device_lge_g2
https://github.com/JackpotClavin/android_kernel_lge_g2
https://github.com/JackpotClavin/android_vendor_lge_g2
10/17/13:
http://forum.xda-developers.com/showpost.php?p=46554268&postcount=271
10/12/13: alpha
http://forum.xda-developers.com/showpost.php?p=46407049&postcount=138
10/3/13: Super alpha
http://forum.xda-developers.com/showpost.php?p=46147336&postcount=74
I would love to help, but I admit I don't know much about Android development. I've got an AT&T G2 and I know C# and a bit of C++, so I'm sure I can figure out C. I think it's awesome that you're working on CM, if I can help out somehow I'd love to!
Not trying to be a **** because I can't wait for CM on this device, but why 10.1? Why not just go ahead to CM 10.2 and Android 4.3?
bose301s said:
Not trying to be a **** because I can't wait for CM on this device, but why 10.1? Why not just go ahead to CM 10.2 and Android 4.3?
Click to expand...
Click to collapse
Because our kernel, etc., are all set up for Android 4.2.2. Meaning, it is easier to get 4.2.2 running, and then move forward to get 10.2.
JackpotClavin: We already have a "few" devs prepping a device tree, though it still misses the proprietary blob references. You should take a look at them, all the device trees are on Github, under TeamLGOG.
fonix232 said:
Because our kernel, etc., are all set up for Android 4.2.2. Meaning, it is easier to get 4.2.2 running, and then move forward to get 10.2.
JackpotClavin: We already have a "few" devs prepping a device tree, though it still misses the proprietary blob references. You should take a look at them, all the device trees are on Github, under TeamLGOG.
Click to expand...
Click to collapse
Ok, that is what I was thinking but I have never done any dev work or anything so I figured I would ask.
I cant help but I sure want to thank you folks for trying to get this up and running. This phone is an absolute BEAST! Coming from the gnex I'm excited about the G2's potential.
Sent from my VS980 4G using Tapatalk 4
Thanks!
I just wanted to thank you very very much for working on this! I knew this was going to be a well developed phone and I bet before 4 months we will have a good amount of choice as far as roms go. Thanks again!
I've been trying to port beanstalk to the G2 but I need the same information you are trying for. I need device trees to sync with. I can PM you with what info I've came up with So far if you are interested.?
Edit: tress are up! Great work
Sent from my LG-D800 using xda app-developers app
If you lived in my town I'd probably help by cleaning the gutters for you hehe. Thanks for your work!
Sent from my EVO using xda app-developers app
I am definitely willing to help in any way I can.
I am willing to beta test and report bugs, dont know much about development but I want CM i have been using it forever...
grandmasterlarry said:
I am willing to beta test and report bugs, dont know much about development but I want CM i have been using it forever...
Click to expand...
Click to collapse
same goes for me, I have the Korean version.
Does CyanogenMod get rid of features like KnockON? I have grown accustomed to it and don't know if I could do without it (my device sits in a vehicle dock a lot of the time where the buttons on the back are 100% inaccessible unless I disconnect the charger, remove phone from dock/holder and find the buttons on the back.)
Is KnockON a Snapdragon 800 feature, or an LG UI feature (I think so, as it doesn't seem to work except in the notif bar, the stock browser, and the stock lock screen)? Can it be added to the AOSP/CM code perhaps?
mrbig012 said:
Does CyanogenMod get rid of features like KnockON? I have grown accustomed to it and don't know if I could do without it (my device sits in a vehicle dock a lot of the time where the buttons on the back are 100% inaccessible unless I disconnect the charger, remove phone from dock/holder and find the buttons on the back.)
Is KnockON a Snapdragon 800 feature, or an LG UI feature (I think so, as it doesn't seem to work except in the notif bar, the stock browser, and the stock lock screen)? Can it be added to the AOSP/CM code perhaps?
Click to expand...
Click to collapse
LG UI feature. I'm fairly sure it will be ported to an AOSP/CM10/LGUI hybrid ROM at some point. I believe part of the issue that devs are running into is that a lot of the custom LG software appears to be tied together.
Can you guys keep us updated on your progress, this is a make or break thing for me with this phone, CM is just so much better than any stock ROM that I don't know if I can deal with a phone that has no prospect of official support.
JackpotClavin said:
Howdy folks
I'd like to thank:
Dan Rosenberg (djrbliss) for Loki (the exploit that allows for custom boot images)
Dees_Troy (for TWRP)
Everybody who has contributed to the CyanogenMod Project
xiaolu for github tools used for unpacking and repacking boot images
I picked up my brand new LG G2 on Friday and I've been hard at work to get CM10.1 booting on it ever since yesterday; but a few hours ago I got my first boot -> http://imgur.com/a/1sZz2
I'm using a few proprietary files that I'd like to not use in the future (more than just the Adreno blobs)
But I'm looking to get a team together to get this working 100%
I will post device and vendor source as soon as I get back from cleaning gutters at my dad's house
What works:
Literally nothing, Android won't boot unless you have the necessary EGL libraries, so I just threw those in because I knew it would boot, and nothing else just to get a bare-bones (but booting) ROM. You can navigate throughout UI fine though (it's very smooth believe it or not).
I'll also upload a proof-of-concept build for those willing to see what CM10.1 will look like on our G2s. I'm currently unable to flash a zip in TWRP recovery, so I have to boot into recovery, wipe data, boot into fastboot, flash a system.img and a boot.img and reboot
If I were any person who likes to ROM but will like to remain stock until there's a stable ROM, I'd add a random "#" to any empty line in the file /system/build.prop which will throw off the sha1sum checker when the recovery goes to install an OTA update (this will block all OTAs from ever installing, thus keeping the current boot image exploit viable and it won't be patched up as the OTA won't be able to install. (root is required)
Edit: device and vendor sources are up!
https://github.com/JackpotClavin/android_device_lge_g2
https://github.com/JackpotClavin/android_vendor_lge_g2
Click to expand...
Click to collapse
Are we going to try getting mobile network and wifi working first? Is adb working?
droid_<3er said:
Are we going to try getting mobile network and wifi working first? Is adb working?
Click to expand...
Click to collapse
First is audio. It's proving to be a big problem. I can't get anything working using either prebuilt binaries from stock, or building from source
JackpotClavin said:
First is audio. It's proving to be a big problem. I can't get anything working using either prebuilt binaries from stock, or building from source
Click to expand...
Click to collapse
I am NOT a developer, but this could help perhaps?
http://opensource.wolfsonmicro.com/content/wm5110-linux-driver-released
Not sure if it really is open source or only available as binaries, but the WM5110 is the audio SoC in this phone... I am probably not helping.
Additionally, I think the S4 uses this SoC as well. It's a pretty new part but is gaining a lot of momentum.
Edit: My god that WM5110 is a hell of a part... quad-core, 600 MIPS... dayum!
Glad to hear an update, even if it's about issues. Seeing that there are people actively working on this to make it happen makes me much happier and less worried about keeping this phone vs. returning it tomorrow or Friday to see how the Nexus 5 plays out etc.
Have any of you tried talking to Ricardo Cerqueira? He is in fact the primary maintainer for all LG Devices with regards to Cyanogenmod. I am sure he is planning on supporting this device in the near future, I just don't know when. It will probably be when the device is more readily available since it was pretty much just released.
Hi,
So, cm-13 is very unlikely on our device, but i'll take a look anyway (a slow look as my time is very limited).
Here you'll find my "work" and "help requests".
First, for sure i didn't "worked" on a lot of device, but it's the first one i have with a dedicated partition to the kernel dts.
Code:
/dev/block/platform/hi_mci.0/by-name/dts /dts emmc defaults recoveryonly
+/dev/block/platform/hi_mci.0/by-name/boot /boot emmc defaults recoveryonly
+/dev/block/platform/hi_mci.0/by-name/recovery /recovery emmc defaults recoveryonly
+/dev/block/platform/hi_mci.0/by-name/misc /misc emmc defaults recoveryonly
+/dev/block/platform/hi_mci.0/by-name/modem /modem emmc defaults recoveryonly
+/dev/block/platform/hi_mci.0/by-name/modem_dsp /modem_dsp emmc defaults recoveryonly
+/dev/block/platform/hi_mci.0/by-name/sensorhub /sensorhub emmc defaults recoveryonly
- I wonder if the dts, which is kernel dependent, could be the major problem to get a custom rom version (kk, jb, mm), or even a stock huawei rom, to work from any base rom. I'll try to make some experiment soon.
- I did sync cm-13, and "of course" have cwm recovery working. But whatever i'm trying i can't get screen output on twrp 3.0. Does someone have a clue on this?
- @gabry3795 , do you still have the device ? I would be happy to get your hangout/google nickname if you have any to sometime talk about this device. @codeworkx is of course also welcome for any advice. By the way your cm12.0 github repo (codeworkx) doesn't seem's to be up to date, even if i understand that's it's in a non-working state.
Cpasjuste said:
@codeworkx is of course also welcome for any advice. By the way your cm12.0 github repo (codeworkx) doesn't seem's to be up to date, even if i understand that's it's in a non-working state.
Click to expand...
Click to collapse
You're looking at the wrong account.
https://github.com/honor6-dev
Start recovery and have a look at /tmp/recovery.log.
Hint:
https://github.com/honor6-dev/andro...common/blob/cm-12.1/BoardConfigCommon.mk#L150
https://github.com/CyanogenMod/andr...mmit/7273770a9fedff12ca80135356c52fee06c8aba0
Cpasjuste said:
- @gabry3795 , do you still have the device ? I would be happy to get your hangout/google nickname if you have any to sometime talk about this device. @codeworkx is of course also welcome for any advice. By the way your cm12.0 github repo (codeworkx) doesn't seem's to be up to date, even if i understand that's it's in a non-working state.
Click to expand...
Click to collapse
Yes, I still have this device! I'll write you via pm my nickname.
good luck you guys
i have really nothing to offer ..
but please make this happen ..
Unfortunately I really have no time to play with it this days, I'll try to take a look soon.
Envoyé de mon HUAWEI MT7-L09 en utilisant Tapatalk
Cpasjuste said:
Unfortunately I really have no time to play with it this days, I'll try to take a look soon.
Envoyé de mon HUAWEI MT7-L09 en utilisant Tapatalk
Click to expand...
Click to collapse
pls we wait for a long time:good:
It would be great to se cm no this device. Good luck and hope you make it. I would help if knew anything about programming but unfortanatly i dont
Cm we want... thank you for your interest!! ?
Kzyw said:
Cm we want... thank you for your interest!!
Click to expand...
Click to collapse
+1
why is there not one custom rom for this device?
Motawa88 said:
why is there not one custom rom for this device?
Click to expand...
Click to collapse
because huawei refuses to share their kernel source. suffice it to say, im done with huawei. its a good thing that there are many new phones being released soon. from now on its snapdragon or nothing!
Motawa88 said:
why is there not one custom rom for this device?
Click to expand...
Click to collapse
As I understand there are some crucial files / source codes that Huawei is refusing to release to the public. This alone sounds super dodgy, because isn't Android supposed to be open source? Or can companies "own" a custom version of Android and do this sort of thing?
These files are crucial for creating custom kernels and ROMs, as they have to do with (once again, this is how I interpreted it) how the device handles the CPU and GPU.
Basically, while it is possible to install other ROMs on the device, they'll have to be based on EMUI and its kernels, because it is the only thing that contains these files necessary to make the device run, which makes the entire exercise pointless because EMUI is s*** no matter what form it takes.
I wonder if it wouldn't be possible to simply "extract" this necessary code from the stock kernels / ROMs and implement it in a custom one? I do not know even the slightest thing about programming, so I could just be sounding like an idiot.
Scruffykid said:
I wonder if it wouldn't be possible to simply "extract" this necessary code from the stock kernels / ROMs and implement it in a custom one? I do not know even the slightest thing about programming, so I could just be sounding like an idiot.
Click to expand...
Click to collapse
i too have wondered about this. im sure its possible but it might be far to difficult an endeavor because if it weren't, someone would have attempted it by now. i really miss my nexus 5 with all its custom roms. i suggest that all mate 7 owners get in contact with huawei and demand they comply with the android user agreement. they are technically supposed to give up sources. we could fight, but not unless we unite.
Yes we can! Yes we can! Yes we can!
Scruffykid said:
As I understand there are some crucial files / source codes that Huawei is refusing to release to the public. This alone sounds super dodgy, because isn't Android supposed to be open source? Or can companies "own" a custom version of Android and do this sort of thing?
These files are crucial for creating custom kernels and ROMs, as they have to do with (once again, this is how I interpreted it) how the device handles the CPU and GPU.
Basically, while it is possible to install other ROMs on the device, they'll have to be based on EMUI and its kernels, because it is the only thing that contains these files necessary to make the device run, which makes the entire exercise pointless because EMUI is s*** no matter what form it takes.
I wonder if it wouldn't be possible to simply "extract" this necessary code from the stock kernels / ROMs and implement it in a custom one? I do not know even the slightest thing about programming, so I could just be sounding like an idiot.
Click to expand...
Click to collapse
You're right, extracting stock binary files is an essential part of roms porting but some important files can't be inherited because they are strictly hardware-related, therefore you have to compile the original android source and then "patch" that files for the specific GPU/CPU (starting from android 5 lollipop) with other files given by the vendor of the phone.
gabry3795 said:
...then "patch" that files for the specific GPU/CPU (starting from android 5 lollipop) with other files given by the vendor of the phone.
Click to expand...
Click to collapse
But isn't that the entire problem, the "other files" that have to be supplied by the vendor? Huawei is refusing to release them, and therefore making it impossible to develop custom ROM's.
Or are you saying that it is possible, but there just isn't enough interest in the phone for anyone with the necessary skills to actually go through the trouble?
Scruffykid said:
But isn't that the entire problem, the "other files" that have to be supplied by the vendor? Huawei is refusing to release them, and therefore making it impossible to develop custom ROM's.
Or are you saying that it is possible, but there just isn't enough interest in the phone for anyone with the necessary skills to actually go through the trouble?
Click to expand...
Click to collapse
I'm saying that Huawei must provide that 'patches' (as Qualcomm did, for example) otherwise is impossibile to build a working ROM, this is the problem. We cannot do anything without them.
gabry3795 said:
I'm saying that Huawei must provide that 'patches' (as Qualcomm did, for example) otherwise is impossibile to build a working ROM, this is the problem. We cannot do anything without them.
Click to expand...
Click to collapse
this is why we should all come together so as to put pressure on huawei to release these files. i have been trying for months now but its getting very tiresome. im going to start a twitter account that will hopefully get their attention. i think the problem is that the general public dont know much/anything about custom roms. there should be a custom rom psa for all android users that point out the benefits of custom roms.
droidbot1337 said:
this is why we should all come together so as to put pressure on huawei to release these files. i have been trying for months now but its getting very tiresome. im going to start a twitter account that will hopefully get their attention. i think the problem is that the general public dont know much/anything about custom roms. there should be a custom rom psa for all android users that point out the benefits of custom roms.
Click to expand...
Click to collapse
I agree. If you get that account running let us know here so that we can support it.
Cheers! :good:
---------- Post added at 12:03 PM ---------- Previous post was at 11:32 AM ----------
droidbot1337 said:
because huawei refuses to share their kernel source. suffice it to say, im done with huawei. its a good thing that there are many new phones being released soon. from now on its snapdragon or nothing!
Click to expand...
Click to collapse
Agreed.
Unfortunately I live in a place where just picking up a new phone is not as easy as 123, But I think I'll try and get my hands on a different phone this weekend. Huawei pisses me off.
No source release by Huawei.
No Kirin SOC support would be a huge problem to get it working I think.
As we all know our 1+5T doesn't support project treble,
so my question is,
is this hardware or software dependent?
In other words,
is it possible for devs to find a way to implement it in future custom roms or in a kernel for our dumpling?
Or would this just be impossible?
Thanks in advance
Mikxx said:
As we all know our 1+5T doesn't support project treble,
so my question is,
is this hardware or software dependent?
In other words,
is it possible for devs to find a way to implement it in future custom roms or in a kernel for our dumpling?
Or would this just be impossible?
Thanks in advance
Click to expand...
Click to collapse
Good question.
At least one would need to repartition internal card, if I understood. This alone is not impossible but a bit hard and not without risk.
That said often I wonder if it could be possible to boot, say, TWRP (or any other Linux) from USB and take full dd backup of internal card for all certainty (and then repartition). This is how many Android TV boxes can be backed up (they use u-boot infrastructure). So why not phones?
Dior DNA said:
Good question.
At least one would need to repartition internal card, if I understood. This alone is not impossible but a bit hard and not without risk.
That said often I wonder if it could be possible to boot, say, TWRP (or any other Linux) from USB and take full dd backup of internal card for all certainty (and then repartition). This is how many Android TV boxes can be backed up (they use u-boot infrastructure). So why not phones?
Click to expand...
Click to collapse
indeed and that is what made me think, because aftervall, android is build upon lnnux
Mikxx said:
As we all know our 1+5T doesn't support project treble,
so my question is,
is this hardware or software dependent?
In other words,
is it possible for devs to find a way to implement it in future custom roms or in a kernel for our dumpling?
Or would this just be impossible?
Thanks in advance
Click to expand...
Click to collapse
This question has been discussed lots before.
https://forum.xda-developers.com/oneplus-5t/how-to/change-org-project-treble-op5t-t3709841
Implementing Project Treble would require repartitioning storage. Also, it gives literally zero benefit to a custom ROM.
TL;DR: It's never going to happen.
the Doctor said:
[...]Also, it gives literally zero benefit to a custom ROM.[...]
Click to expand...
Click to collapse
I mark these words. Have a nice day.
update
Perhaps there is no functional benefit. But porting seems easier for some devices:
What about :
https://www.xda-developers.com/samsung-galaxy-s9-aosp-android-oreo-project-treble/
This is the Samsung Galaxy S9 running on AOSP Android Oreo thanks to Project Treble
the Doctor said:
This question has been discussed lots before.
https://forum.xda-developers.com/oneplus-5t/how-to/change-org-project-treble-op5t-t3709841
Implementing Project Treble would require repartitioning storage. Also, it gives literally zero benefit to a custom ROM.
TL;DR: It's never going to happen.
Click to expand...
Click to collapse
But it happened ?
cubandanger05 said:
But it happened ?
Click to expand...
Click to collapse
Yup, somebody saw a mountain and decided to climb it. We'll see what comes of it.
Yeah mokee ROM has treble working on the OnePlus One 5T. There's an unused partition that can be created without re-partition in the device and if you install a regular ROM it doesn't see it you install a treble ready ROM and you previously had mokee installed according to the mokee dev it works. It uses the ab style of treble. There is an "a" and "ab" and "a/b" versions from what I read. Mokee is releasing nightlies of their ROM
Haven't tried it on mine pretty happy with the aicp Oreo that I'm running so I can't tell you what bugs it has. Google it XDA has a discussion on mokee and treble with OnePlus 5t
hi guys,
i have a question about android. can i switch my rom to rolling release? thank you for your reply.
Need some more information here...
Unless I missed something idk what rolling release means?
"In software development, a rolling release, rolling update, or continuous delivery is the concept of frequently delivering updates to applications. This is in contrast to a standard or point release development model which uses software versions that must be reinstalled over the previous version."
sorry i dont know enough word to explain in english so i copied a bit and pasted. if you use a linux distro like arch linux, you just update packages like when you get play store updates and never get major updates like on ubuntu.
hajking said:
"In software development, a rolling release, rolling update, or continuous delivery is the concept of frequently delivering updates to applications. This is in contrast to a standard or point release development model which uses software versions that must be reinstalled over the previous version."
sorry i dont know enough word to explain in english so i copied a bit and pasted. if you use a linux distro like arch linux, you just update packages like when you get play store updates and never get major updates like on ubuntu.
Click to expand...
Click to collapse
Just install the alpha and beta version of the rom/firmware you would like for frequent updates.
But sadly it doesn't work like that on mobile, you get a huge update once a year and patches every month (if you are on "stable")
AWESOME1092387456 said:
Just install the alpha and beta version of the rom/firmware you would like for frequent updates.
But sadly it doesn't work like that on mobile, you get a huge update once a year and patches every month (if you are on "stable")
Click to expand...
Click to collapse
yeah im on latest miui tr and i get update every week but there must be a way i think.
hajking said:
yeah im on latest miui tr and i get update every week but there must be a way i think.
Click to expand...
Click to collapse
if our devices supported Project Treble we would be able to receive system-less updates, which are possible due to treble's A/B partition scheme (as far as i konw but i am not entirely sure)
AWESOME1092387456 said:
if our devices supported Project Treble we would be able to receive system-less updates, which are possible due to treble's A/B partition scheme (as far as i konw but i am not entirely sure)
Click to expand...
Click to collapse
thanx dude
AWESOME1092387456 said:
if our devices supported Project Treble we would be able to receive system-less updates, which are possible due to treble's A/B partition scheme (as far as i konw but i am not entirely sure)
Click to expand...
Click to collapse
Firstly, what's that "system-less" but still the updating of the "system"? Learn before talking and know what you're saying (no personal offense, btw).
Then again you're wrong as mi 6 doesn't have that a/b partition scheme (even though it's not that hard to repartition the device storage to have two boot and system partitions, you'll need to have or compile a new kernel that supports that partition and booting scheme - and we don't have that yet).
Treble will only let you to update your system without touching the separated vendor partition.
ccelik97 said:
Firstly, what's that "system-less" but still the updating of the "system"? Learn before talking and know what you're saying (no personal offense, btw).
Then again you're wrong as mi 6 doesn't have that a/b partition scheme (even though it's not that hard to repartition the device storage to have two boot and system partitions, you'll need to have or compile a new kernel that supports that partition and booting scheme - and we don't have that yet).
Treble will only let you to update your system without touching the separated vendor partition.
Click to expand...
Click to collapse
What i meant is we could update the phone without needing to do a full restart and i said "IF OUR DEVICE SUPPORTED PROJECT TREBLE" didn't you read the "IF"? And with "system-less" i meant mostly bugfixes that can be installed without the need of restarting the whole device as that particular service would for example shutdown and then start again and in this way we could receive security patches and minor stability updates, not full android releases or another version of miui (from v9 to v10) these kinds of upsates should still need to be performed through recovery, please next time read a response carefully before responding and i personally stated that i am not that sure either at the end of my response so don't just look for some keywords and then go bashing others for no reason.
AWESOME1092387456 said:
What i meant is we could update the phone without needing to do a full restart and i said "IF OUR DEVICE SUPPORTED PROJECT TREBLE" didn't you read the "IF"? And with "system-less" i meant mostly bugfixes that can be installed without the need of restarting the whole device as that particular service would for example shutdown and then start again and in this way we could receive security patches and minor stability updates, not full android releases or another version of miui (from v9 to v10) these kinds of upsates should still need to be performed through recovery, please next time read a response carefully before responding and i personally stated that i am not that sure either at the end of my response so don't just look for some keywords and then go bashing others for no reason.
Click to expand...
Click to collapse
Sorry my bad on that "if" part you're right.
But still, that's not a "system-less" solution but a "recovery-less" updating way as with the a/b partitioning what we get is not having to use anything other than the currently running system to apply the updates (and the ability to roll back to that very currently running system, is something goes wrong with the new)
hello everyone, i want to buy this devie but as i see i cant install twrp!
if i can ask why? is it bc of oneplus or no devs to do it? also thx for all devs
i buy the phone for customs and roms and twrp and rooting and this things, this is my priorities
and is this device fully supported for development? any twrp coming soon?
and what about customs here? is they easy to install?
is this device good for gaming and daily use?
Evon88 said:
hello everyone, i want to buy this devie but as i see i cant install twrp!
if i can ask why? is it bc of oneplus or no devs to do it? also thx for all devs
i buy the phone for customs and roms and twrp and rooting and this things, this is my priorities
and is this device fully supported for development? any twrp coming soon?
and what about customs here? is they easy to install?
is this device good for gaming and daily use?
Click to expand...
Click to collapse
What device and firmware?
TheGhost1951 said:
What device and firmware?
Click to expand...
Click to collapse
i want to buy normal OP9P
Evon88 said:
i want to buy normal OP9P
Click to expand...
Click to collapse
The OnePlus 9 pro is good for customizing!
@Evon88, the fact is, TWRP hasn't been updated to properly support Android 12, at least not on the 9 Pro, and I'm beginning to suspect that it never will be. IMHO, it looks to me like encryption and other issues introduced by Google have simply gotten the best of the TWRP team. I'll be happy to be proven wrong, and will be pleasantly surprised if TWRP is updated to work with Android 12 and above, but right now, that remains in the realm of wishful thinking.
The good news is that the recoveries included with most Android 12 ROMs (based on the AOSP recovery) are functional, and are capable of doing the minimum work of flashing new ROMs and upgrades (i.e. Magisk and Gapps) just like TWRP. They certainly don't have the wealth of features that TWRP has (such as the ability to wipe only the data partition without erasing the media partition; it's either all or nothing), but then, they weren't designed to have them. I keep hoping that someone will take the AOSP recovery and use it as a base for a recovery that includes more of TWRP's features. (I'd do it if I had the knowledge. I'm knowledgeable enough to poke at AOSP and cherry pick features to create a custom ROM, but the intimate knowledge required to work with the recovery code is something I don't have.)
Evon88 said:
hello everyone, i want to buy this devie but as i see i cant install twrp!
if i can ask why? is it bc of oneplus or no devs to do it? also thx for all devs
i buy the phone for customs and roms and twrp and rooting and this things, this is my priorities
and is this device fully supported for development? any twrp coming soon?
and what about customs here? is they easy to install?
is this device good for gaming and daily use?
Click to expand...
Click to collapse
You can in fact install and boot TWRP. But you can't do almost anything in it... But this isn't OP9P problem but every phone with Android 12 and encryprion enabled. But as other said, TWRP isn't needed for flashing custom ROMs.
Evon88 said:
i want to buy normal OP9P
Click to expand...
Click to collapse
Don't let lack of twrp hold you back. It's a fun phone. I use it for gaming (CODM) on Android 11.2.10.10 just fine. I may end up flashing an old build of crDroid for Android 11 but I'm pretty happy with how everything is set up on regular OOS now and don't want to lose L1 and start back over.
Unlocked bootloader✓
Root/Magisk✓
SafetyNet✓
Netflix, GPay, Banking apps✓
L1 Widevine✓
Real OOS✓
65w charging✓
120hz LTPO✓
No Dual Sim
The tmobile variant is still for sale on ebay at $469 brand new in the box or from OnePlus directly (also Tmo variant) for $499
MJPollard said:
@Evon88, the fact is, TWRP hasn't been updated to properly support Android 12, at least not on the 9 Pro, and I'm beginning to suspect that it never will be. IMHO, it looks to me like encryption and other issues introduced by Google have simply gotten the best of the TWRP team. I'll be happy to be proven wrong, and will be pleasantly surprised if TWRP is updated to work with Android 12 and above, but right now, that remains in the realm of wishful thinking.
The good news is that the recoveries included with most Android 12 ROMs (based on the AOSP recovery) are functional, and are capable of doing the minimum work of flashing new ROMs and upgrades (i.e. Magisk and Gapps) just like TWRP. They certainly don't have the wealth of features that TWRP has (such as the ability to wipe only the data partition without erasing the media partition; it's either all or nothing), but then, they weren't designed to have them. I keep hoping that someone will take the AOSP recovery and use it as a base for a recovery that includes more of TWRP's features. (I'd do it if I had the knowledge. I'm knowledgeable enough to poke at AOSP and cherry pick features to create a custom ROM, but the intimate knowledge required to work with the recovery code is something I don't have.)
Click to expand...
Click to collapse
Bugscze said:
You can in fact install and boot TWRP. But you can't do almost anything in it... But this isn't OP9P problem but every phone with Android 12 and encryprion enabled. But as other said, TWRP isn't needed for flashing custom ROMs.
Click to expand...
Click to collapse
There's a user/team on the >OnePlus 6 & 6T forums<, that has had success with Android 12 and 13 decrypt, I use it on my 6T, and decrypt works flawlessly, I use it to flash Magisk when changing/updating ROMs.
It's Unofficial however, I hope it trickles to other devices.
Appreciative said:
Don't let lack of twrp hold you back. It's a fun phone. I use it for gaming (CODM) on Android 11.2.10.10 just fine. I may end up flashing an old build of crDroid for Android 11 but I'm pretty happy with how everything is set up on regular OOS now and don't want to lose L1 and start back over.
Unlocked bootloader✓
Root/Magisk✓
SafetyNet✓
Netflix, GPay, Banking apps✓
L1 Widevine✓
Real OOS✓
65w charging✓
120hz LTPO✓
No Dual Sim
The tmobile variant is still for sale on ebay at $469 brand new in the box or from OnePlus directly (also Tmo variant) for $499
Click to expand...
Click to collapse
thank you sir, what about chinese version? u recommend it? im pro at rooting and customs and msm, if the problem is just roms, i see used chinese new mobile, u recommend me to buy?
deleted
MJPollard said:
@Evon88, the fact is, TWRP hasn't been updated to properly support Android 12, at least not on the 9 Pro, and I'm beginning to suspect that it never will be. IMHO, it looks to me like encryption and other issues introduced by Google have simply gotten the best of the TWRP team. I'll be happy to be proven wrong, and will be pleasantly surprised if TWRP is updated to work with Android 12 and above, but right now, that remains in the realm of wishful thinking.
The good news is that the recoveries included with most Android 12 ROMs (based on the AOSP recovery) are functional, and are capable of doing the minimum work of flashing new ROMs and upgrades (i.e. Magisk and Gapps) just like TWRP. They certainly don't have the wealth of features that TWRP has (such as the ability to wipe only the data partition without erasing the media partition; it's either all or nothing), but then, they weren't designed to have them. I keep hoping that someone will take the AOSP recovery and use it as a base for a recovery that includes more of TWRP's features. (I'd do it if I had the knowledge. I'm knowledgeable enough to poke at AOSP and cherry pick features to create a custom ROM, but the intimate knowledge required to work with the recovery code is something I don't have.)
Click to expand...
Click to collapse
thank you bro for explain, what do you think about chinese OP9P? i can change the rom, 5G i dont care that much, anthing else? is quality the same like hardware and plastic and fiber and this things? i mean phone body and screen
Bugscze said:
You can in fact install and boot TWRP. But you can't do almost anything in it... But this isn't OP9P problem but every phone with Android 12 and encryprion enabled. But as other said, TWRP isn't needed for flashing custom ROMs.
Click to expand...
Click to collapse
thanks, <3
Evon88 said:
thank you sir, what about chinese version? u recommend it? im pro at rooting and customs and msm, if the problem is just roms, i see used chinese new mobile, u recommend me to buy?
Click to expand...
Click to collapse
All of them are made in china and I think will be good quality OnePlus phone. I don't know if they use anything different (except rom). You can change from colorOS to oxygenOS
twrp not needed
vincemue said:
twrp not needed
Click to expand...
Click to collapse
Needed, maybe not. Desired, definitely. It can do a lot of things that the stock and AOSP recoveries simply can't (to name just one: it can wipe data without wiping storage, as I mentioned above; stock/AOSP recoveries' "factory reset" wipe destroys everything).
MJPollard said:
@Evon88, the fact is, TWRP hasn't been updated to properly support Android 12, at least not on the 9 Pro, and I'm beginning to suspect that it never will be. IMHO, it looks to me like encryption and other issues introduced by Google have simply gotten the best of the TWRP team. I'll be happy to be proven wrong, and will be pleasantly surprised if TWRP is updated to work with Android 12 and above, but right now, that remains in the realm of wishful thinking.
The good news is that the recoveries included with most Android 12 ROMs (based on the AOSP recovery) are functional, and are capable of doing the minimum work of flashing new ROMs and upgrades (i.e. Magisk and Gapps) just like TWRP. They certainly don't have the wealth of features that TWRP has (such as the ability to wipe only the data partition without erasing the media partition; it's either all or nothing), but then, they weren't designed to have them. I keep hoping that someone will take the AOSP recovery and use it as a base for a recovery that includes more of TWRP's features. (I'd do it if I had the knowledge. I'm knowledgeable enough to poke at AOSP and cherry pick features to create a custom ROM, but the intimate knowledge required to work with the recovery code is something I don't have.)
Click to expand...
Click to collapse
I was on LE2127_11_C20 A12 with tarp and root.......the mail reason it worked was no lock screen security. I did try with setting a password is be cause a script to try and make partitions R/W but that put me in a bootloader loop. Went back to 11.2.9.9..
Did you follow a YouTube tutorial step by step guide to see if you made any mistakes?
dartballs said:
Did you follow a YouTube tutorial step by step guide to see if you made any mistakes?
Click to expand...
Click to collapse
Who are you asking?
Appreciative said:
Don't let lack of twrp hold you back. It's a fun phone. I use it for gaming (CODM) on Android 11.2.10.10 just fine. I may end up flashing an old build of crDroid for Android 11 but I'm pretty happy with how everything is set up on regular OOS now and don't want to lose L1 and start back over.
Unlocked bootloader✓
Root/Magisk✓
SafetyNet✓
Netflix, GPay, Banking apps✓
L1 Widevine✓
Real OOS✓
65w charging✓
120hz LTPO✓
No Dual Sim
The tmobile variant is still for sale on ebay at $469 brand new in the box or from OnePlus directly (also Tmo variant) for $499
Click to expand...
Click to collapse
The Indian variant has dual SIM. Maybe some others variants, too.