Related
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
TWRP 2.7.1.0 , stock revovery (v1.2), unlocked recovery (original by wmjan)
hope there will be some custom roms for this LCD soon...
tonyjih said:
TWRP 2.7.1.0 , stock revovery (v1.2), unlocked recovery (original by wmjan)
hope there will be some custom roms for this LCD soon...
Click to expand...
Click to collapse
Could you please explain the difference between these 3 recoveries?
GaroRobe said:
Could you please explain the difference between these 3 recoveries?
Click to expand...
Click to collapse
they both for newer model of find7 comes with a newer screen
You'll need these recoveries ONLY if you own a R63419+ LCD model
reference:
http://www.oppoforums.com/threads/r63419-cannot-install-3rd-party-rec-rom.24924/
tonyjih said:
they both for newer model of find7 comes with a newer screen
You'll need these recoveries ONLY if you own a R63419+ LCD model
reference:
http://www.oppoforums.com/threads/r63419-cannot-install-3rd-party-rec-rom.24924/
Click to expand...
Click to collapse
1. The "*##*37847#" method doesn't work for me since I'm on 1.2.8i , thus cannot verify the screen model
2. My phone is x9076 int'l, manufactured in december 2014
3. I have the "bleached screen" bug on 3rd party ROMs and namelessTWRPs
4. The twrp-x9076 takes only half of a screen area (it does work though, but still identifies my phone as find7a which is incorrect)
5. you still didn't describe the difference between the other two
I tried flashing CM12 nightly with twrp-x9076 (had to remove assert from update script). No good - same as before, bleached screen and such. So this particular recovery seems to be useless for anything other than backup/restore and rooting (which is awesome, but still not what I'd like to have access to).
GaroRobe said:
I tried flashing CM12 nightly with twrp-x9076 (had to remove assert from update script). No good - same as before, bleached screen and such. So this particular recovery seems to be useless for anything other than backup/restore and rooting (which is awesome, but still not what I'd like to have access to).
Click to expand...
Click to collapse
you have to wait CM update their drivers , otherwise it just .... don't work.
I also have an issue with this and have installed this recovery and its fixed the problem. Now we wait for custom ROM developers to catch on.... I'm going to keep myself glued to cyanogen to see if they change anything!
sof006 said:
I also have an issue with this and have installed this recovery and its fixed the problem. Now we wait for custom ROM developers to catch on.... I'm going to keep myself glued to cyanogen to see if they change anything!
Click to expand...
Click to collapse
Same here. Other than the official beta rom there seems to be nothing available for us. I am seriously considering returning the Oppo since I can't even get hold of 1.2.8i (only stable version which ships with the phone).
So sad... I really want to use 5.0 on my OPPO Find 7. I've reached out to Cyanogen but had no replies, reached out to other ROM developers only to either be ignored or have my question washed away by a sea of people complaining that they can't get a game to work on their phone.
Just found out that cyanogen is working on the new oppo find 7 with new lcd panel issue. So anyone disappointed they'll have it sorted soon hopefully!
Does the offical TWRP and CM support this find7 with new LCD????
Any updates on this? I have managed to get the official AOSP ROM working but nothing else unfortunately.
Double the question. Lack of working TWRP is just fatal to any tinkering.
GaroRobe said:
1. The "*##*37847#" method doesn't work for me since I'm on 1.2.8i , thus cannot verify the screen model [...]
Click to expand...
Click to collapse
Test with adb (requires root):
Code:
adb devices
adb shell
su
cat /proc/devinfo/lcd
the answer for me (X9006 with COS 2.0.8i) is
Code:
Device version: R63417
Device manufacture: JDI
close the shell
Code:
exit
exit
Maybe if the ROM is compiled from source, the extra driver could be included? I am noob to this so if someone experienced could take a look that'd be great!
Just found this thread and didn't read much.
I am on unified storage (stock 2.0.8I). Are these recoveries compatible (unified partition)?
And yes, I have the new LCD screen...
Thanks
betoNL said:
Just found this thread and didn't read much.
I am on unified storage (stock 2.0.8I). Are these recoveries compatible (unified partition)?
And yes, I have the new LCD screen...
Thanks
Click to expand...
Click to collapse
Yes they are compatible with LVM, using it with the official AOSP rom since it's been the only way for me to get Lollipop so far, will probably test out the new beta ColorOS 2.1 Lollipop ROM as well.
EDIT: Actually just noticed some issues with it, can't mount internal_sd or data partitions and thus can't back up, avoid. I thought I'd backed up on LVM but clearly not.
Speaking of ROMs... I've taken the screen driver of the original Oppo kernel from the github and added it to the cm12.1 kernel (ie overwritten the cm12 driver with the Oppo one), I'm now compiling it from source and will report back if this works. If so, this will mean working Cyanogenmod for the new panel!
djzic said:
Yes they are compatible with LVM, using it with the official AOSP rom since it's been the only way for me to get Lollipop so far, will probably test out the new beta ColorOS 2.1 Lollipop ROM as well.
EDIT: Actually just noticed some issues with it, can't mount internal_sd or data partitions and thus can't back up, avoid. I thought I'd backed up on LVM but clearly not.
Speaking of ROMs... I've taken the screen driver of the original Oppo kernel from the github and added it to the cm12.1 kernel (ie overwritten the cm12 driver with the Oppo one), I'm now compiling it from source and will report back if this works. If so, this will mean working Cyanogenmod for the new panel!
Click to expand...
Click to collapse
Ok thanks,
I am on stock 2.0.8i with unified storage and gonna have a look on some CM / AOSP based roms soon ...
.
betoNL said:
Ok thanks,
I am on stock 2.0.8i with unified storage and gonna have a look on some CM / AOSP based roms soon ...
.
Click to expand...
Click to collapse
Edit I did a backup of the stock recovery (2.0.8i) with Flashify app for instance so I think I am going to try this out anyway ....
Twrp cant seen to find my internal storage. Im using unified storage setting on colorOS 2.1
it was funny how I realized mine was the new version now
I made this thread here so you guys can discuss, this is for information to others who have gotten the new elephone
1) How do we get root ?
No, there isnt any proper recovery last @Emileh ported it did not work very well you are able to flash it the recovery but you are unable to boot back into the system it just stuck at the elephone logo.
2) as of now we only have one rom that has been up here and running K06TE-A.A.vR14.E1.160707 (2016 Version)
K05TS-A.A.vR1E.E2.160217 (2015 Version)
3) cosmetic mixed up (happens alot on chinese phone)
my front is the old 2015 version cover but my back is the new fingerprint cover (possible you can confirm with that is the new elephone you have if you are not sure.
4) so no root and no cyanogenmod and no recovery ?
as of now Im not sure about root, cause I did tried to flash recovery from @Emileh but I could not boot back to android os, so we cant flash supersu,
kingroot and others dont work !
also there some memory layout changed, so it will render the android 5.1 roms useless, please dont try unless you know what you are doing and know how to recover from mediatek usb port
5) will CyanogenMod 13 work ?
to be honest we need a fully working recovery.
maybe there can explain and clear anything more that I left out, I have just gotten the phone
@skeleton1911 @BlueFlame4 @Emileh @Deepflex
somehelp would be nice. thanks would be nice to get cm13 for both the 2015 and 2016 working
Hey,
well the 2015 and 2016 versions are basically two different devices - despite having the same name they share very little. A unified CM 13 build is thus not only difficult to establish but I would even say that it makes things more complex than developing two single versions. That said, CM 13 for the 2016 should be rather easy to bring up because it ships with 6.0. Basically you could take Deepflex's P9000 tree, change it according to the 2016_P8000 and boom - should work. With that you can then of course also compile a working recovery to achieve root That's the theory at least
Is that so but we have yet to achive root and figure out what is the internal changes between those two? Maybe @Deepflux can lend a helping hand in this wish you could help out @BlueFlame4, cause I finally had the money to get this phone possible if you could look into the recovery issue on why it does not boot after flashing it aka bootloop at elephone logo
** Attempted to Port and it does not work. did repack twice.
Hey. Just saw this topic.
I made a better version of the recovery (but forgot to post it), which is actually able to flash roms. It now also mounts everything properly. Flashing root on stock rom works 100%. (only thing not working in ADB, I think).
I will upload it later.
Problem is, there are no roms (expect stock, which you flash using SP Flash Tools). You can't flash the roms that other have made for the old version of the phone. Doesn't work like that.
Emileh said:
Hey. Just saw this topic.
I made a better version of the recovery (but forgot to post it), which is actually able to flash roms. It now also mounts everything properly. Flashing root on stock rom works 100%. (only thing not working in ADB, I think).
I will upload it later.
Problem is, there are no roms (expect stock, which you flash using SP Flash Tools). You can't flash the roms that other have made for the old version of the phone. Doesn't work like that.
Click to expand...
Click to collapse
yeah @BlueFlame4
mention something about cyanogenmod from @Deepflex, could it be this ?
https://github.com/Deepflex/android_device_elephone_p8000/commits/master
hopefully we can get cyanogenmod working, possible if you release the recovery ? is it TWRP ?
Zenns said:
yeah @BlueFlame4
mention something about cyanogenmod from @Deepflex, could it be this ?
https://github.com/Deepflex/android_device_elephone_p8000/commits/master
hopefully we can get cyanogenmod working, possible if you release the recovery ? is it TWRP ?
Click to expand...
Click to collapse
I was talking about this. You have to adapt it to the P8000 and have to use a 3.18 kernel (+ M blobs) though.
there isnt any 3.18 kernel that was released right ? m blobs can be extracted question is why won't your cm13.1 work on the new elephone ? memory changes ? it is still same soc right or there is something different quite confused.
Bump
Hi, I'm not sure if it's the right section where to post such a thread but I didn't found a better one for my problem.
I flashed lineage-14.1-20170213-nightly-find7s-signed.zip on my rooted Find 7 (2k version so Find 7s) with TWRP following all the standard steps (full wipe, ROM and gapps install, wipe cache/dalvik and than reboot).
Than when the ROM flash was finished (it took not as much as I thought) I rebooted and my screen become white with a grey OPPO logo in the middle and purple "powered by android" at the bottom (the usual power up screen but with inverted colors) and when I touch the screen it makes quick flashes with flashing black horizontal lines and it keeps being stuck in that way for minutes (way too much and it keeps doing that also after many reboots). The only way to recover the phone is to flash again Color OS (Android 5.0).
So i was wondering what's the problem with that ROM? How can i upgrade my old Android 5.0 to a newer 6.x or 7.x? Is there any rock solid ROM compatible with my F7s that I can flas with no such problems ?
Thankyou all for help!
OmniROM 6 is a mature and solid daily driver with the option to try OmniROM 7 which is still being improved regularly. Arguably the best ROM for Find 7.
RobboW said:
OmniROM 6 is a mature and solid daily driver with the option to try OmniROM 7 which is still being improved regularly. Arguably the best ROM for Find 7.
Click to expand...
Click to collapse
It also has LVM support which allows you to merge your partitions so you will have more than 3gb of space for apps.
I've been running it for months, there are a few things that I miss from previous roms but is very stable and since this phone is getting old the ROM choices are getting slim. It's also the only one I can find that still supports LVM.
RobboW said:
OmniROM 6 is a mature and solid daily driver with the option to try OmniROM 7 which is still being improved regularly. Arguably the best ROM for Find 7.
Click to expand...
Click to collapse
_Clint-Beastwood_ said:
It also has LVM support which allows you to merge your partitions so you will have more than 3gb of space for apps.
I've been running it for months, there are a few things that I miss from previous roms but is very stable and since this phone is getting old the ROM choices are getting slim. It's also the only one I can find that still supports LVM.
Click to expand...
Click to collapse
Thankyou both for helping me I found a list of omnirom ROMs in this thread https://forum.xda-developers.com/find-7/orig-development/omni-testbuilds-7a-7s-t3237065 , can i choose one of the last 6.0.1 to be sure it will work or can I trust the 7.1.1 updates?
You can trust both! And im not a hyper flashholic....
Just another few questions, LVM means that i can unify partitions in order to have more than 3 GB on device memory, right? I found that thread https://forum.xda-developers.com/showpost.php?p=55187001&postcount=558 is it better to use the .iso or the .zip to apply LVM? And when do I have to apply the LVM setup, before or after flashing the new ROM/Gapps?
Thanks again
Frank_Z said:
Just another few questions, LVM means that i can unify partitions in order to have more than 3 GB on device memory, right? I found that thread https://forum.xda-developers.com/showpost.php?p=55187001&postcount=558 is it better to use the .iso or the .zip to apply LVM? And when do I have to apply the LVM setup, before or after flashing the new ROM/Gapps?
Thanks again
Click to expand...
Click to collapse
Flash the setuplvm zip file in twrp BEFORE flashing ROM and gapps
Guys, thanks to all of you! Really, you all made my day with all your advices
With past ROMs i was desperate because none of them worked but now i got rooted android 7.1.1 with merged partitions on my dear Find 7 so thanks again for helping me!
I am looking for a ROM that runs android nougat. I have a rooted device but have never installed a custom rom on it. Right now, it is just running 6.0.1 MOB30X, the latest update on stock. I want to upgrade to Nougat, but I don't really know what options are available. I want to keep my device close to stock android, like it already is. So, if someone could tell me what ROMs are available and which ones are the most popular and best?
DavidMTMaster said:
I am looking for a ROM that runs android nougat. I have a rooted device but have never installed a custom rom on it. Right now, it is just running 6.0.1 MOB30X, the latest update on stock. I want to upgrade to Nougat, but I don't really know what options are available. I want to keep my device close to stock android, like it already is. So, if someone could tell me what ROMs are available and which ones are the most popular and best?
Click to expand...
Click to collapse
If you want to keep close to the stock android the closest is the official lineageos build. All others have added features which may or maynot affect batterylife and performance.
LineageOS or AOSP will get you what you want.
crDroid 7.1.2 v3.3
Just fantastic! Add the elementalX kernal and buttersmoth experience!
DavidMTMaster said:
I am looking for a ROM that runs android nougat. I have a rooted device but have never installed a custom rom on it. Right now, it is just running 6.0.1 MOB30X, the latest update on stock. I want to upgrade to Nougat, but I don't really know what options are available. I want to keep my device close to stock android, like it already is. So, if someone could tell me what ROMs are available and which ones are the most popular and best?
Click to expand...
Click to collapse
In my experience no version superior to "Android 6" works well "out of the box" with full working applications of estreaming like youtube, netflix, etc .. and sometimes problems with root, my recommendation if it will be "Android 6" is still better Stock rom. Neither lineage nor much less AOSP and any derivative.
Newbies to all these updates and ROMs releases. I spent a good amount of time dumping various ROM.
I tried Lineages, Droid, Resurrection Remix. I think ASOP is Lineage?
All the ROMs above works well but I could not get gapp to going. Keep saying wizard error when starting up. Gapp is basically play store.
I tried that mini gapp bean and the open gapp 7.1 pico. They both fail during start up. It was trying to run the google apps wizard and keeps failing.
I ended up with Nitrogen-OS-flo-20170316 ROM. Let this ROM flash first than, reboot, go back in recovery mode and flash the Gapp 7.1 pico. This was the only way I can avoid the wizard failing during startup. Everything works except Latest netflix app failing. Get the apk from mirror apk and make sure you get the older apk version 4.2. Don't get the newest 5.x netflix release.
Resurrection Remix ROM looks cool. It's suppose to be faster than Linage.
Since everything is work for me with Nitrogen. I'll stick with nexus 6 Nitrogen for now.
or until someone prove me wrong. Or know why I am having all sort of issue installing Gapp pico on Resurrection Remix, Linage, or that Droid version.
---------- Post added at 06:38 AM ---------- Previous post was at 06:34 AM ----------
I am not sure if Android 6 or marsh mellow is the best. After I flash with Nougot. It's a lot faster. Loving it.
Hi guys, I just bought a Nexus 7 and i updated to latest official 6. Then i find out OTG Support doesnt have support for exFat, only FAT32. If i try to do Nougat, will it gain exFat support for OTG?
Also can anyone take my nexus 7 and do it for me for like $20-$30 as i am completely illiterate on all of this...
vartanarsen said:
Hi guys, I just bought a Nexus 7 and i updated to latest official 6. Then i find out OTG Support doesnt have support for exFat, only FAT32. If i try to do Nougat, will it gain exFat support for OTG?
Also can anyone take my nexus 7 and do it for me for like $20-$30 as i am completely illiterate on all of this...
Click to expand...
Click to collapse
This depends on the rom or kernel as much as whether it is Nougat. LineageOS supports exfat and has clear instructions on how to install it.
Wifi only Nexus 7 (2013) (Flo) https://wiki.lineageos.org/devices/flo/install.
4G and Wifi Nexus 7 (2013) (Deb) https://wiki.lineageos.org/devices/deb/install