https://en.m.wikipedia.org/wiki/F2FS
I know most people don't believe in the filesystem. However I am not one of those. I've used F2FS on previous devices and it seemed to make a difference to me. I believe it to be a faster and more efficient filesystem. Most importantly I believe flash storage will last much longer due to the difference in the way the blocks are written.
I don't consider myself a genius so... Im sure someone else knows better than me.
Just wondering if anyone was interested in porting it over our way. IRRC the hard part is building twrp to work with it.
I haven't seen any talk about it on the Pixel XL subforums, no.
Would definitely like to see it happen though.
I think TWRP has to be modded to support it
Sent from my Pixel XL using Tapatalk
Correct me if I'm wrong but I believe it would have to be supported in the kernel and TWRP at the same time due to both being in the same partition.
Sent from my Pixel XL using Tapatalk
Supported in rom kernel and recovery. I've Used it on the nexus 6 and my galaxy nexus
I used it on the Nexus 5 and 5X and loved it. Would be nice if it comes to our phone.
Why would anyone give this thread one star?
Sheesh, I gave ya five stars to try and balance it out.
CZ Eddie said:
I haven't seen any talk about it on the Pixel XL subforums, no.
Would definitely like to see it happen though.
Click to expand...
Click to collapse
You can't mate. Cause it doesn't support hardware based FBE.
---------- Post added at 08:29 AM ---------- Previous post was at 08:28 AM ----------
Oh, and btw. If any of you do end up getting f2fs, adding "nobarrier" to the joint options speeds it up crazily. The increase from that is much more than just using f2fs.
Source: http://taras.glek.net/post/Moto-Z-has-10x-less-lag-than-pixel/
LazerL0rd said:
You can't mate. Cause it doesn't support hardware based FBE.
---------- Post added at 08:29 AM ---------- Previous post was at 08:28 AM ----------
Oh, and btw. If any of you do end up getting f2fs, adding "nobarrier" to the joint options speeds it up crazily. The increase from that is much more than just using f2fs.
Source: http://taras.glek.net/post/Moto-Z-has-10x-less-lag-than-pixel/
Click to expand...
Click to collapse
Pulled this from that link you posted.
"f2fs nets Moto-Z a 2x speed-up and 2x increase in NAND lifespan. Expect Moto-Z to age much better than Pixel"
DR3W5K1 said:
Pulled this from that link you posted.
"f2fs nets Moto-Z a 2x speed-up and 2x increase in NAND lifespan. Expect Moto-Z to age much better than Pixel"
Click to expand...
Click to collapse
The mount options make a massive difference too. Check it up, mate!
CZ Eddie said:
I haven't seen any talk about it on the Pixel XL subforums, no.
Would definitely like to see it happen though.
Click to expand...
Click to collapse
It's currently impossible. F2FS doesn't support hardware file-based encryption yet.
LazerL0rd said:
It's currently impossible. F2FS doesn't support hardware file-based encryption yet.
Click to expand...
Click to collapse
It does now.
Maybe someone can get something going when the Oreo hype cools down.
What none of you read was Google's response to that guy. First of all the mount options can cause your storage to become corrupted in the event of a power failure. Also they tested f2fs internally and in real world usage it didn't make a difference in the performance of the device.
Sent from my Nexus 6P using Tapatalk
91ludesit said:
What none of you read was Google's response to that guy. First of all the mount options can cause your storage to become corrupted in the event of a power failure. Also they tested f2fs internally and in real world usage it didn't make a difference in the performance of the device.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
It has been stated that most don't believe in the filesystem in the op. This equates no into almost no devs trying to implement it into ROMs/kernels+recoveries. It can be done and file structures stay intact. I've used it daily without any issues on my nexus 6(freewilly). Look at those or nexus 7 forums if you need proof. Everyone knows Google will never implement the fs.
DR3W5K1 said:
It has been stated that most don't believe in the filesystem in the op. This equates no into almost no devs trying to implement it into ROMs/kernels+recoveries. It can be done and file structures stay intact. I've used it daily without any issues on my nexus 6(freewilly). Look at those or nexus 7 forums if you need proof. Everyone knows Google will never implement the fs.
Click to expand...
Click to collapse
Kernel authors have added support for f2fs, NTFS and probably other file systems for ages. Then you need a TWRP build that can format to that fs.
I wouldn't take Google statement as cold hard fact. If they did everything "right" then there wouldn't be a mod community. They're is plenty of objective data showing f2fs outperforming ext4 in crucial areas like database operations.
Having said that, f2fs is not heavily utilized, a few Moto phones use it and it is pretty new fs. Samsung developed it and they don't use it. Ext4 has been around for.. 30 years? It's a nobraIner decision on their part to take the tried-and-true method rather than risk producing a million devices using a different file system that isn't nearly as developed or seasoned as ext4 is.
F2FS was definitely faster in its early days, but it had issues. As those issues were addressed, F2FS itself got slower. It no longer has a speed advantage. I'm sorry to tell you, but at this point F2FS is snake oil.
fizbanrapper said:
F2FS was definitely faster in its early days, but it had issues. As those issues were addressed, F2FS itself got slower. It no longer has a speed advantage. I'm sorry to tell you, but at this point F2FS is snake oil.
Click to expand...
Click to collapse
Just look at some motto x benchmarks you'll find your "snake oil" inside
DR3W5K1 said:
Just look at some motto x benchmarks you'll find your "snake oil" inside
Click to expand...
Click to collapse
I can't be bothered to find something I have no interest in, just to prove someone else's point for them. Lol
Having said that, I don't see any reason my F2FS shouldn't had been added to a recovery build yet if there's interest. If there are more than a handful of people interested, I can create a twrp build with F2FS support. It will take some time since I haven't synced omni repos and made my own recovery image in over six months.
DR3W5K1 said:
Just look at some motto x benchmarks you'll find your "snake oil" inside
Click to expand...
Click to collapse
Benchmarks don't mean anything when it comes to usability.
Sent from my Pixel XL using Tapatalk
Related
http://www.androidpolice.com/2010/12/11/data2ext-hack-blows-benchmarks-out-of-the-water/
Pretty big news out of the XDA-Forums today – forum member and resident genius Ownhere has come up with a ‘data2ext’ hack that allows users to enhance the way Android handles OS-specific data and memory. Put simply, this hack allows users to change some partition settings in order to greatly increase performance.
Originally created for the HTC Desire, the hack delivers some outstanding performance improvements and is a must have if you own the device. For more technical information, you can click here. A word of warning, though: this hack is not for the feint of heart as it is fairly difficult.
Interesting..
Pretty nice...3000 points in Quadrant is huge. Maybe we can get something similar to our devices as well...Santa Claus is approaching
not today's but they are great...if the hack doesn't destabilize the device or harm safety...
http://forum.xda-developers.com/showthread.php?t=859419
Wow, I hope someone will implement this for Legend!
qzem said:
Wow, I hope someone will implement this for Legend!
Click to expand...
Click to collapse
Same here...
I read the post howto for desire and it looked sooooooooooo complicated...
This will be fairly easy to implement... but things could go very bad using this mod. Like for instance if you make a sudden power-off... filesystem may stay in such state that it cannot be mounted on the next boot and for novice users this could mean that wipe should be made to resolve this situation.
Sent from my HTC Legend
BlaY0 said:
This will be fairly easy to implement... but things could go very bad using this mod. Like for instance if you make a sudden power-off... filesystem may stay in such state that it cannot be mounted on the next boot and for novice users this could mean that wipe should be made to resolve this situation.
Sent from my HTC Legend
Click to expand...
Click to collapse
This problem should only be there if you really disable journaling. From the original post:
As you see, the best speed is: mount real ext4 device with loop option, disable journaling. The best balance of performance and safe is mount real ext4 device with loop option, enable journaling! We don't need a loopfile but just change mount option.
Click to expand...
Click to collapse
As long as journaling is enabled this should be quite safe. At least thats what journaling is for
If someone will implement this, it would require microSD card class >= 4, to use this hack. Am I right?
Based on my own experience, as well as many requests in various ROM release threads, as well as many other comments in various ROM release threads...
RFS please.
Any speed gain from EXT4 with no journaling is made moot the first time one has to wipe and re-flash, even with backups (maybe especially with backups, which seem to cause some issues as well).
I like speed, I overclock my computer, my video card, and even my phone, but I need stability in my phone. I need the dependability that if my phone crashes it isn't going to force me to do a wipe and re-flash half the time. So... suppress your inner flash-happy geek enough to realize that stability and dependability are important aspects of a phone and at least give the option of an RFS file system.
You are in the minority my friend,90% or more that use EXT4 have no problems at all,,,I don't trust no journaling 100%,but I havnt had 1 problem running it for almost 3 months; And you can enable journaling...
Sent from my SPH-D700 using XDA Premium App
ecooce said:
You are in the minority my friend,90% or more that use EXT4 have no problems at all,,,I don't trust no journaling 100%,but I havnt had 1 problem running it for almost 3 months; And you can enable journaling...
Click to expand...
Click to collapse
Same here... I haven't had a single problem on any of the ROMs I have run here. I have been enjoying speed + reliability.
I understand what JMMusic is saying though...the whole premise of having a custom ROM is that you can modify it how you want. Maybe RFS should be an option for those that want it. I do think that EXT4 with journaling enabled is the best route though.
I personally agree with OP. I'd rather have stability over speed in my phone. I? Ok with just ext4 journalling over rfs, but I would rather have journalling on.
Sent from my SPH-D700 using XDA App
Epic experience is rfs
Sent from my SPH-D700 using XDA Premium App
I cosigned OP, this is the reason I'm not flashing anymore custom roms now. Everybody is on this ext4 banwagon. I'm good, they can miss me with that. I've never had problems out of the ordinary from RFS. I can go on for days about ext4. When I do flash a rom it will be CM7 before anything now.
I hate "Top Flight Security Mods"
Add me to the jouraling ON list. I need stability more than I need the highest quadrant score.. Re-flashing gets old when your supposedly great ROM decides to bork itself every couple days.
caspertodd said:
Same here... I haven't had a single problem on any of the ROMs I have run here. I have been enjoying speed + reliability.
Click to expand...
Click to collapse
Lucky you. I flashed a certain popular ROM. Everything was amazing...for a few days. Then it screwed up. Flashed it again. Everything cool. Couple days later it's crashing again. This process happened over and over. I NEVER had this problem with stock or stock minus bloat or stock minus bloat plus OC kernel. Only when using an EXT4 ROM with journaling turned off.
Coincidence? Not.
Guess one of u guys that want RFS better learn how to cook
ExT4 > RFS
Sent from my Epic 4G using XDA Premium app
..........
dchawk81 said:
Lucky you. I flashed a certain popular ROM. Everything was amazing...for a few days. Then it screwed up. Flashed it again. Everything cool. Couple days later it's crashing again. This process happened over and over. I NEVER had this problem with stock or stock minus bloat or stock minus bloat plus OC kernel. Only when using an EXT4 ROM with journaling turned off.
Coincidence? Not.
Click to expand...
Click to collapse
Why not just stay stock?
caspertodd said:
Why not just stay stock?
Click to expand...
Click to collapse
Well, that's my plan now that I've learned my lesson the hard way.
dchawk81 said:
Well, that's my plan now that I've learned my lesson the hard way.
Click to expand...
Click to collapse
Stock ran very well for me. The only reason I went with a custom rom is just because I could. If I do start having issues such as data corruption, then I probably would go back to stock. So far though I guess I am lucky...I just hope I stay lucky for another 15 months or so when I'm eligible for my next upgrade.
caspertodd said:
Stock ran very well for me. The only reason I went with a custom rom is just because I could. If I do start having issues such as data corruption, then I probably would go back to stock. So far though I guess I am lucky...I just hope I stay lucky for another 15 months or so when I'm eligible for my next upgrade.
Click to expand...
Click to collapse
That's why I gave it a go too. I didn't fare so well. Performance was amazing, but it never lasted. You could almost set your clock to the system failure. I'm not the only one, either.
No RFS for me but EXT4 with journaling enabled would be nice.
Sent from my SPH-D700 using Tapatalk
Anyone saying they want RFS after all the test we have done for stability is like saying Id rather not upgrade to FROYO, Eclair works just fine even though its gimped compared to it.
Sent from my SPH-D700 using XDA Premium App
ecooce said:
Anyone saying they want RFS after all the test we have done for stability is like saying Id rather not upgrade to FROYO, Eclair works just fine even though its gimped compared to it.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
I have to respectfully disagree here - apples and oranges. Huge differences between an OS and FS here. Yes RFS is older and slower but does seem to be less prone to corruption. Luckily I have 2 phones, the epic being for personal use so I don't mind the risk. But if this was my business use phone Id want the functionality of custom roms, and the slow but sturdy filesystem. Just my .02....
Sent from my SPH-D700 using XDA App
ecooce said:
Anyone saying they want RFS after all the test we have done for stability is like saying Id rather not upgrade to FROYO, Eclair works just fine even though its gimped compared to it.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
I don't know if I'd go that far. RFS is compatible with FAT so it can be read in windows. Not having to connect a USB cable to copy files from/to your SDCard is an advantage over EXT4.
Of course, while writing this post, I got curious, searched and found ext2fsd. Which might provide a solution to the ext4 'disadvantage'. Haven't tried it though.
foxBlade107 said:
I don't know if I'd go that far. RFS is compatible with FAT so it can be read in windows. Not having to connect a USB cable to copy files from/to your SDCard is an advantage over EXT4.
Of course, while writing this post, I got curious, searched and found ext2fsd. Which might provide a solution to the ext4 'disadvantage'. Haven't tried it though.
Click to expand...
Click to collapse
I don't understand. How could you transfer files on RFS without a USB cable? I did then, and now, with an FTP server. Was there another way?
I need stability over performance. That is why I've stayed with stock. I would be using SRF 1.0.1 right now if it had journaling enabled. Then again, I haven't had the time to do the research yet on how to enable it after the fact.
Sure it's nice to frequently backup to have a snapshot handy, but that should never be a requirement to maintain stability of a custom rom, IMO.
The lack of journaling still doesn't detract from the good job the ACS crew has done thus far with CIQ removal and whatnot.
http://www.reddit.com/r/nexus6/comments/2m49w1/the_encryption_issue/
http://www.reddit.com/r/Android/comments/2m49qd/psa_android_5x_encryption_cannot_be_disabled_if/
This is super disappointing.
i'm hoping (and confident) that custom kernels will be able to disable this.
vivanshah said:
i'm hoping (and confident) that custom kernels will be able to disable this.
Click to expand...
Click to collapse
Otherwise a fresh ROM image would do it.
Skripka said:
Otherwise a fresh ROM image would do it.
Click to expand...
Click to collapse
On what basis do you say that (honest question)?
Google says
Caution: Devices upgraded to Android 5.0 and then encrypted may be returned to an unencrypted state by factory data reset. New Android 5.0 devices encrypted at first boot cannot be returned to an unencrypted state.
mk262 said:
On what basis do you say that (honest question)?
Google says
Caution: Devices upgraded to Android 5.0 and then encrypted may be returned to an unencrypted state by factory data reset. New Android 5.0 devices encrypted at first boot cannot be returned to an unencrypted state.
Click to expand...
Click to collapse
Well then... Bye bye Nexus 6....
mk262 said:
This is super disappointing.
Click to expand...
Click to collapse
Well, it is less disappointing than the file system just being slow for no reason.
hitzand said:
Well, it is less disappointing than the file system just being slow for no reason.
Click to expand...
Click to collapse
AnandTech is of the opinion that the AndroBench tools are not yet functioning properly on Lollipop. It was the AndroBench toolset that Ars used to cook up their NAND comparison.
Once developers get their hands on it, they will figure out how to disable encryption. They could possibly use a hard flash method which replaces entire sectors of the NAND with new data. Simply flashing a ROM/kernel probably won't be enough.
Skripka said:
AnandTech is of the opinion that the AndroBench tools are not yet functioning properly on Lollipop. It was the AndroBench toolset that Ars used to cook up their NAND comparison.
Click to expand...
Click to collapse
Where did you read that?
mk262 said:
Where did you read that?
Click to expand...
Click to collapse
Ars's review openly labels the ssd benches as being androbench. Anand openly comments in their review that they think the numbers from Nexus 6 are so bad and weird that they cannot be correct...and therefore Anand doesn't include ssd benches in their review
Skripka said:
Ars's review openly labels the ssd benches as being androbench. Anand openly comments in their review that they think the numbers from Nexus 6 are so bad and weird that they cannot be correct...and therefore Anand doesn't include ssd benches in their review
Click to expand...
Click to collapse
http://www.anandtech.com/comments/8687/the-nexus-6-review/429491
that's interesting
Skripka said:
AnandTech is of the opinion that the AndroBench tools are not yet functioning properly on Lollipop. It was the AndroBench toolset that Ars used to cook up their NAND comparison.
Click to expand...
Click to collapse
Benchmarks don't matter. Are found in normal use the phone is slower than a N5, which is what a normal user will experience. That's what's so bad.
Also, encryption has nothing to do with this. You can enable encryption on Windows and it barely slows down disk access, if you have a modern cpu. The Nexus 6 chipset is plenty fast, so the slowdown is due to flash memory not being fast enough.
ECrispy said:
Benchmarks don't matter. Are found in normal use the phone is slower than a N5, which is what a normal user will experience. That's what's so bad.
Also, encryption has nothing to do with this. You can enable encryption on Windows and it barely slows down disk access, if you have a modern cpu. The Nexus 6 chipset is plenty fast, so the slowdown is due to flash memory not being fast enough.
Click to expand...
Click to collapse
Face palm...your modern desktop CPU has dedicated encryption instructions.
Skripka said:
Face palm...your modern desktop CPU has dedicated encryption instructions.
Click to expand...
Click to collapse
I'm not sure if the 805 has AES support, I know ARM v8 does. Regardless, since its enabled by default in L, it will hurt users.
ECrispy said:
Benchmarks don't matter. Are found in normal use the phone is slower than a N5, which is what a normal user will experience. That's what's so bad.
Also, encryption has nothing to do with this. You can enable encryption on Windows and it barely slows down disk access, if you have a modern cpu. The Nexus 6 chipset is plenty fast, so the slowdown is due to flash memory not being fast enough.
Click to expand...
Click to collapse
Wrong
ECrispy said:
I'm not sure if the 805 has AES support, I know ARM v8 does. Regardless, since its enabled by default in L, it will hurt users.
Click to expand...
Click to collapse
ARM v8 does.
805 is v7 and does not.
In which case encrypting everything by default is a bad decision. No one wants a phone slower than a N5. Did Ars get a bad unit? They are highly respected.
mk262 said:
On what basis do you say that (honest question)?
Google says
Caution: Devices upgraded to Android 5.0 and then encrypted may be returned to an unencrypted state by factory data reset. New Android 5.0 devices encrypted at first boot cannot be returned to an unencrypted state.
Click to expand...
Click to collapse
Is it possible to unencrypt things before first boot? That line has me a lil confused...
kinfolk248 said:
Is it possible to unencrypt things before first boot? That line has me a lil confused...
Click to expand...
Click to collapse
Its just a software flag that tells the firstboot process to encrypt the phone. It is described here: https://source.android.com/devices/tech/encryption/
*** quite trivial to disable.
More: Its just a parameter in the fstab, which is a plain text file that describes to vold, what to mount where. Changing the flag from forceencrypt to encryptable fixes it. Note that this file is in the root fs, which means that the boot image needs to be unpacked and repacked to modify it.
More2: They're doing it on Nexus 9, with apparently very positive results.... http://forum.xda-developers.com/nex...llipopalooza-flounder-volantis-t2933831/page2
doitright said:
Its just a software flag that tells the firstboot process to encrypt the phone. It is described here: https://source.android.com/devices/tech/encryption/
*** quite trivial to disable.
More: Its just a parameter in the fstab, which is a plain text file that describes to vold, what to mount where. Changing the flag from forceencrypt to encryptable fixes it. Note that this file is in the root fs, which means that the boot image needs to be unpacked and repacked to modify it.
More2: They're doing it on Nexus 9, with apparently very positive results.... http://forum.xda-developers.com/nex...llipopalooza-flounder-volantis-t2933831/page2
Click to expand...
Click to collapse
smh I need the hots wings and beer translation of that lol
Was able to get a ROM built and running based on LRX21V straight from source. Just trying to get a feel on how many people would want to run AOSP. There are some bugs present such as video recording causing the camera to stop working. I think there are binaries missing that Google didn't include in the binaries that are available. Same problem happened on the Nexus 5. Didn't test it much as I just purely wanted to see if it booted.
Also there is a lack of gapps available so I won't be rushing to get anything out. Let me know what y'all think and I'll try to tackle this to get some other options out for us.
Here is the test build for those that want to have a look. This is just a test build so bugs are to be expected. Video recording does not work. Haven't tested it completely as I need a fully working device this weekend. This is for those that have free time to just nit pick and find all bugs in this. Please report back after you are done and let me know what else you may have found that is broken or not working right.
Stock Google kernel (so if you flashed the kernel image to remove encryption your phone WILL be encrypted again)
Built off 5.0.0_r7 from AOSP
Flash ROM, flash gapps and flash SU that is linked below. This will allow root access on the stock kernel.
You can also optionally flash the custom boot image after flashing the ROM, gapps and SU by rebooting to bootloader and fastboot flash boot the custom encryption kernel. That is optional. Be sure to go back in to recovery after flashing the kernel to reflash the SU to make sure it was not overwritten.
Download Rom:AFH Mirror
Download Gapps for Lollipop:http://forum.xda-developers.com/showthread.php?p=56810851#post56810851
Download latest SU: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
I'm tuned in!
Sent from my Nexus 6 using XDA Free mobile app
The development section is kind of depressing me right now (no offense to devs) so bring it!
the.emilio said:
Was able to get a ROM built and running based on LRX21V straight from source. Just trying to get a feel on how many people would want to run AOSP. There are some bugs present such as video recording causing the camera to stop working. I think there are binaries missing that Google didn't include in the binaries that are available. Same problem happened on the Nexus 5. Didn't test it much as I just purely wanted to see if it booted.
Also there is a lack of gapps available so I won't be rushing to get anything out. Let me know what y'all think and I'll try to tackle this to get some other options out for us.
Click to expand...
Click to collapse
Any gapps should work. It can be downloaded from the nexus 5 section
---------- Post added at 09:37 AM ---------- Previous post was at 09:34 AM ----------
Its only been a couple days. And the phone is really scarce. Give it time
estallings15 said:
The development section is kind of depressing me right now (no offense to devs) so bring it!
Click to expand...
Click to collapse
That is pretty offensive. It is a new device and isn't in the developers hand so releasing work without testing their work leads to quality problems.
I don't see you doing any development work and developers don't owe anyone anything as they do all this work as a hobby pretty much.
Sent from my Nexus 6 using Tapatalk
zephiK said:
That is pretty offensive. It is a new device and isn't in the developers hand so releasing work without testing their work leads to quality problems.
I don't see you doing any development work and developers don't owe anyone anything as they do all this work as a hobby pretty much.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I know the reasons behind it, which was the point of the "no offense." I wasn't whining. I was trying to help motivate and encourage OP. He, as well as others, are working on making things happen and I'm excited for it and waiting eagerly for the kernel source to drop.
You took what I said the wrong way, so step off of your soap box, zephiK.
Edit: That reminds me. If any devs need testers, PM me. I'll be happy to help the community out.
Smallsmx3 said:
Any gapps should work. It can be downloaded from the nexus 5 section
---------- Post added at 09:37 AM ---------- Previous post was at 09:34 AM ----------
Its only been a couple days. And the phone is really scarce. Give it time
Click to expand...
Click to collapse
Lol. I know this. Just came from the N5 I guess what I meant is that there isn't a complete package yet. There's a minimal yes that does work. But I prefer the full. Just lazy and hate downloading apps or pushing apps lol
the.emilio said:
Lol. I know this. Just came from the N5 I guess what I meant is that there isn't a complete package yet. There's a minimal yes that does work. But I prefer the full. Just lazy and hate downloading apps or pushing apps lol
Click to expand...
Click to collapse
Ha! That's funny. does r 7 have any significant commits over our revision
Smallsmx3 said:
Ha! That's funny. does r 7 have any significant commits over our revision
Click to expand...
Click to collapse
No. Minor bug fixes for the particular device it was made for but that's it. I did notice on the N5 that there was a significant "miscellaneous" battery drain on r7. Might roll back to r3 if its present since r3 is the one for us (its also the same build for the N5).
zephiK said:
That is pretty offensive. It is a new device and isn't in the developers hand so releasing work without testing their work leads to quality problems.
I don't see you doing any development work and developers don't owe anyone anything as they do all this work as a hobby pretty much.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
We are working on something [emoji6]
the.emilio said:
No. Minor bug fixes for the particular device it was made for but that's it. I did notice on the N5 that there was a significant "miscellaneous" battery drain on r7. Might roll back to r3 if its present since r3 is the one for us (its also the same build for the N5).
Click to expand...
Click to collapse
Miscellaneous bug again? I wonder if they broke the same thing they already fixed, or if this is something else that is just falling into miscellaneous as well.
Thanks for the work on this!
In for the long haul! Tired of the plethora of gapps on this phone. Somehow I managed to break photos once by removing some google app... Weird.
Sent from my Nexus 6 using Tapatalk
I uploaded the ROM for testing purposes. Please re-read the OP for more info. :good:
the.emilio said:
I uploaded the ROM for testing purposes. Please re-read the OP for more info. :good:
Click to expand...
Click to collapse
Sweet, thanks.
What the Christ is this new file layout?! System.new.dat o.0
Sent from my Nexus 6 using Tapatalk
Rauch said:
Sweet, thanks.
What the Christ is this new file layout?! System.new.dat o.0
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
That's lollipop for ya..
the.emilio said:
That's lollipop for ya..
Click to expand...
Click to collapse
As I wanted to attempt to pre-root and make some changes... Ugh.
Simply installing the SuperSU apk is enough for root, correct? I don't have to re-run CF... Especially since I'm not near a PC
Sent from my Nexus 6 using Tapatalk
Rauch said:
As I wanted to attempt to pre-root and make some changes... Ugh.
Simply installing the SuperSU apk is enough for root, correct? I don't have to re-run CF... Especially since I'm not near a PC
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yes just use the one I linked to. Be sure to flash it in the same session so you don't lose the custom recovery.
Rauch said:
As I wanted to attempt to pre-root and make some changes... Ugh.
Simply installing the SuperSU apk is enough for root, correct? I don't have to re-run CF... Especially since I'm not near a PC
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Remember its just a test so I recommend waiting until you have access to a PC. Just in case lol
Well, I bit the bullet. Only lost a few downloads.... But anyway.
Sound quality seems.... Different? Also network says its connected to LTE, but its beyond slow. Not sure why exactly.
I'm on the correct APN.
Closing apps, I hear a slight buzz/tap three tomes when hitting the home button.
Sent from my AOSP on Shamu using Tapatalk
carloscibrian4 said:
Did anyone's storage decreased afterwards? My nexus says that there is only 23gb of storage despite being a 64 gb
Click to expand...
Click to collapse
I have a 32gb and that's what I have.... I didn't check before.... Anyone have any idea what storage should be out of the box?
Rauch said:
Well, I bit the bullet. Only lost a few downloads.... But anyway.
Sound quality seems.... Different? Also network says its connected to LTE, but its beyond slow. Not sure why exactly.
I'm on the correct APN.
Closing apps, I hear a slight buzz/tap three tomes when hitting the home button.
Sent from my AOSP on Shamu using Tapatalk
Click to expand...
Click to collapse
I was getting weird audio sounds at first... I don't know if it was the update when I got home that fixed it but it's been non existent since the first couple of hours I had the phone
I'm in the process of building a new phone configuration using a V20 (US996) running LineageOS. (14.1 at present, current nightly build)
I have a high-performance Samsung SDcard in it (128GB Evo Select) which is capable of about ~60MB/s write and 100MB/s or more read speed.
In my LG G4 (also running LOS but a late November 2017 build), using a 64GB version of the same card, I get around 45MB/s write speed based on a couple of benchmarking tools I have.
But the V20 only seems to achieve 15-18MB/s write speed.
Is this some kind of terrible hardware flaw with the V20, or ???
Exabyter said:
I'm in the process of building a new phone configuration using a V20 (US996) running LineageOS. (14.1 at present, current nightly build)
I have a high-performance Samsung SDcard in it (128GB Evo Select) which is capable of about ~60MB/s write and 100MB/s or more read speed.
In my LG G4 (also running LOS but a late November 2017 build), using a 64GB version of the same card, I get around 45MB/s write speed based on a couple of benchmarking tools I have.
But the V20 only seems to achieve 15-18MB/s write speed.
Is this some kind of terrible hardware flaw with the V20, or ???
Click to expand...
Click to collapse
You should probably ask this in the lineage thread
Sent from my LG-H910 using XDA Labs
cnjax said:
You should probably ask this in the lineage thread
Click to expand...
Click to collapse
Your comment makes little sense.
The OS in both examples I mentioned is mostly the same, the main difference is the phone hardware.
I am simply trying to ascertain whether this sort of performance is common for that device when using a high-speed card.
Exabyter said:
Your comment makes little sense.
Click to expand...
Click to collapse
No, it makes sense.
Lineage for V20 is not the same as for G4, or most other devices for that matter.
This might be some problem with the LOS lg msm8996 kernel, which of course LOS for the G4 does not use.
All I'm trying to ascertain is what kind of speed people are seeing with their V20's in general.
If' it's significantly better than what I'm seeing, I'll check the OS-specific forums. Thanks.
Exabyter said:
All I'm trying to ascertain is what kind of speed people are seeing with their V20's in general.
If' it's significantly better than what I'm seeing, I'll check the OS-specific forums. Thanks.
Click to expand...
Click to collapse
Get way faster than that but I'm on stock ROM so that doesn't help sorry. I'll try to find my other thread I had in here that has my results
I've never used lineage on v20 but that would be prime suspect considering all the roadblocks getting it to even run right that I've read about lol
---------- Post added at 04:31 AM ---------- Previous post was at 03:36 AM ----------
Exabyter said:
All I'm trying to ascertain is what kind of speed people are seeing with their V20's in general.
If' it's significantly better than what I'm seeing, I'll check the OS-specific forums. Thanks.
Click to expand...
Click to collapse
https://forum.xda-developers.com/v20/accessories/huge-micro-sd-cards-t3498278
That's the thread if you are interested there area free other benchmarks from other people.
Trying to attach the pictures of the card and results but it keeps saying network error on xda labs. I'll try later but I think they were on page 8
Using A1 SD Bench on Super V20 with MK2000 and a 200GB Sandisk A1 microSD I get
Read: 78.8mb/s
Write: 27.20mb/s
KUSOsan said:
Get way faster than that but I'm on stock ROM so that doesn't help sorry.
Click to expand...
Click to collapse
Actually that helps quite a bit, since it corroborates my initial conclusion that this is not a hardware issue, it's a software issue.
KUSOsan said:
I've never used lineage on v20 but that would be prime suspect considering all the roadblocks getting it to even run right that I've read about lol
Click to expand...
Click to collapse
Oh? Do tell. I haven't had the V20 for long yet but I did already get a response elsewhere that there were some unique things about it besides the "2nd screen" thingy and DACs.
KUSOsan said:
https://forum.xda-developers.com/v20/accessories/huge-micro-sd-cards-t3498278
That's the thread if you are interested there area free other benchmarks from other people.
Click to expand...
Click to collapse
Great resource, would probably have taken me a long time to find that on my own. Thanks much, I'll look at it a bit later.
XblackdemonX said:
Using A1 SD Bench on Super V20 with MK2000 and a 200GB Sandisk A1 microSD I get
Read: 78.8mb/s
Write: 27.20mb/s
Click to expand...
Click to collapse
Thanks much.
The write speed there is still a bit disappointing though, given that that card should be able to do, according to some reports, at least 2x if not 3x higher than that.
Exabyter said:
Thanks much.
The write speed there is still a bit disappointing though, given that that card should be able to do, according to some reports, at least 2x if not 3x higher than that.
Click to expand...
Click to collapse
Not really, in THIS test, you can see the SDSQUAR does 33.4mb/s write and 92.8mb/s read. I'm in the range.