Related
hi guys,i'm wondering,what is the best and stable Android build that u haved tested? i see alot of builds here but i dont know witch one to choose
All builds are pretty good, it really depends on your personal taste, and what you're looking for.
I'm running Not So Super Froyo Latest RLS, with 2.6.25 kernel by l1q1d, so far pretty good build.
Had several crashes the last 2 weeks, but all kernel related to phone sleeping, but minor data corruption (fixed by reinstalling the corrupted app, unless it's a system file then I just reinstall the build)
Krazy-Killa said:
All builds are pretty good, it really depends on your personal taste, and what you're looking for.
I'm running Not So Super Froyo Latest RLS, with 2.6.25 kernel by l1q1d, so far pretty good build.
Had several crashes the last 2 weeks, but all kernel related to phone sleeping, but minor data corruption (fixed by reinstalling the corrupted app, unless it's a system file then I just reinstall the build)
Click to expand...
Click to collapse
exactly the same on polaris
phone
crashes on phone sleeping?
dany547 said:
crashes on phone sleeping?
Click to expand...
Click to collapse
Probably due to me tinkering so much.. Some people have the issue others don't. lol
Krazy-Killa said:
All builds are pretty good, it really depends on your personal taste, and what you're looking for.
I'm running Not So Super Froyo Latest RLS, with 2.6.25 kernel by l1q1d, so far pretty good build.
Had several crashes the last 2 weeks, but all kernel related to phone sleeping, but minor data corruption (fixed by reinstalling the corrupted app, unless it's a system file then I just reinstall the build)
Click to expand...
Click to collapse
your systems apps should not get corrupted, potentially minor data loss though because of the odexing process the classes.dex files are not kept in the dalvik cache. so the only thing that could have a problem is the launcher.
this is what the reboot protection was moving the dalvik to the sd so that way it wasnt kept on the system, since the sd does unmount when shutting down
for me the best is Fat Free Froyo with lastest 2.6.25 kernel from git.
The stability really comes from the .25 kernel as it is much more older and mature. My barebones build might work with .25? I haven't tested it but I recall someone saying it worked.
I don't think it will work since scooters cyanogen has a different libskia than other builds
aceoyame said:
The stability really comes from the .25 kernel as it is much more older and mature. My barebones build might work with .25? I haven't tested it but I recall someone saying it worked.
Click to expand...
Click to collapse
Sent from my HTC Hero using XDA App
Oh I know, was just saying that someone said they got it to work so just saying it might work lol
thoughtlesskyle said:
your systems apps should not get corrupted, potentially minor data loss though because of the odexing process the classes.dex files are not kept in the dalvik cache. so the only thing that could have a problem is the launcher.
this is what the reboot protection was moving the dalvik to the sd so that way it wasnt kept on the system, since the sd does unmount when shutting down
Click to expand...
Click to collapse
Apparently that doesn't work for me, especially with the 2.6.32 kernel. No matter how I reboot (button, battery, actual menu option), almost all apps get corrupted, and the Framework gets completely shot the **** (no lock screens, unable to silence phone or turn on Airplane mode).
The Dalvik move to SD apparently doesn't work for me either, unless it's only on a certain build? I'm using Not So Super Froyo RLS18.
I must reflash rom every one -two day, its crash, not workink proceses, system its very slow, after restart phone not remember settings and sometimes delete any data. i test very much roms,
Best Android build is Warbyte Donut for me, very stable and all works fine and quickly, but it is Donut and I Need Froyo..
i see
i got instaled a Donut build,but the white screen and the file system coruption made me to switch back to Wm i'll w8 untill a new build will appeare
fat free
I've got the fat free froyo on kaiser with .32 kernel downloaded with atools.
It works fine with an sd system install (class 6). Fast and stable.
You can olso try system on nand and data on sd! I could not do this because my nand is corrupt....but the result was really good.
The problem you were having was caused by your kernel not the build
dany547 said:
i got instaled a Donut build,but the white screen and the file system coruption made me to switch back to Wm i'll w8 untill a new build will appeare
Click to expand...
Click to collapse
Sent from my HTC Hero using XDA App
no
no,the karnel was for my device
dany547 said:
no,the karnel was for my device
Click to expand...
Click to collapse
Yes it was a kernel fault. Listen to people who are more knowledgeable than yourself. Next time install kernel from '25 branch which is stable and doesn,t suffer from white screens and data corruption. The kernel you used was experimental and it still doesnt work as well as we would want it to.
dany547 said:
no,the karnel was for my device
Click to expand...
Click to collapse
people like you the, i know everything because i manage to get android booting on my windows mobile phone even though i looked at maybe 1 tutorial and read it half way. the flash first read 2nd type. are pretty much the entire reason why there hasnt been a new Not so super or fat free froyo.
-Arturo- said:
Yes it was a kernel fault. Listen to people who are more knowledgeable than yourself. Next time install kernel from '25 branch which is stable and doesn,t suffer from white screens and data corruption. The kernel you used was experimental and it still doesnt work as well as we would want it to.
Click to expand...
Click to collapse
is u want to give me that Kernel i'll apreciate! my karnel was from l1q1d's page (2.6.32)
The Moto X (and more importantly, the Moto G) are using F2FS on their /data partitions and are seeing great I/O performance--even the Moto G, which is using essentially MicroSD eMMC is performing very well, and it's attributed to F2FS.
Is it possible to merge the patches required for F2FS support into the currently GNex kernel and produce a Recovery image built using that kernel that could clean /data and create a F2FS partition on it? Further, could that same kernel then be used in conjunction with an Android image to provide support for F2FS in Android, as the Moto X and G do?
The benchmarks for F2FS performance on NAND is incredible, and the GNex's is seeing new life with KitKat's memory and process optimizations. I'd like to start a discussion on bringing F2FS support to the GNex, in the interest of furthering it's potential.
Shidell said:
The Moto X (and more importantly, the Moto G) are using F2FS on their /data partitions and are seeing great I/O performance--even the Moto G, which is using essentially MicroSD eMMC is performing very well, and it's attributed to F2FS.
Is it possible to merge the patches required for F2FS support into the currently GNex kernel and produce a Recovery image built using that kernel that could clean /data and create a F2FS partition on it? Further, could that same kernel then be used in conjunction with an Android image to provide support for F2FS in Android, as the Moto X and G do?
The benchmarks for F2FS performance on NAND is incredible, and the GNex's is seeing new life with KitKat's memory and process optimizations. I'd like to start a discussion on bringing F2FS support to the GNex, in the interest of furthering it's potential.
Click to expand...
Click to collapse
I'm not sure but I'm very interested in this , if you can find these commits , I'll add this to my to do list . :thumbup:
Edit I found some , thanks for this topic I'll start seeing if it's possible
Sent from my Galaxy Nexus using Tapatalk
bsmitty83 said:
I'm not sure but I'm very interested in this , if you can find these commits , I'll add this to my to do list . :thumbup:
Edit I found some , thanks for this topic I'll start seeing if it's possible
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Awesome--thanks for investigating. I know you have the know-how to implement F2FS if it's feasible. It does appear to F2FS does offer about a 30% I/O perf improvement across the board, but in some cases, it can be as much as 300%, which is insane.
Here's a post I made on reddit with links to performance benchmarks of F2FS vs EXT3, EXT4, BTRFS, etc.
http://www.reddit.com/r/GalaxyNexus/comments/1t7a17/can_we_discuss_f2fs_on_the_galaxy_nexus_seems/
Did you have any luck looking for F2FS patches? Anything I can help with?
Shidell said:
Awesome--thanks for investigating. I know you have the know-how to implement F2FS if it's feasible. It does appear to F2FS does offer about a 30% I/O perf improvement across the board, but in some cases, it can be as much as 300%, which is insane.
Here's a post I made on reddit with links to performance benchmarks of F2FS vs EXT3, EXT4, BTRFS, etc.
http://www.reddit.com/r/GalaxyNexus/comments/1t7a17/can_we_discuss_f2fs_on_the_galaxy_nexus_seems/
Did you have any luck looking for F2FS patches? Anything I can help with?
Click to expand...
Click to collapse
Actually I did , I applied the patches necessary , the kernel supports f2fs , and now I'm in the process of getting the data partition formatted and mounted , which is ROM side in the fstabs , so hopefully I can build a ROM soon that's mounted f2fs , I've been all over this , it's definitely gonna work , just a matter of time before I get everything together
It was a patchset of 250 patches to the kernel .
Trying for some seat time tonight , :fingers-crossed:
Sent from my Galaxy Nexus using Tapatalk
Awesome! Your comments sound promising. Keep us posted!
Everything has its upside and downside. I'm not being a smarta$$ or something but just warning you guys...
I think f2fs has a more than 50 or so times slower average mounting time than that of ext4, so most of the flashaholics out there will simply come back to ext4. It requires partition formats and an f2fs kernel. If one flashes an f2fs kernel to a phone with ext4 partitions, the phone will simply hardbrick, and vice versa. Of course it is possible to be unbricked, but it will be difficult for anyone who hasn't dealt with partitions, especially NAND, before.
I'm just afraid this will brick thousands of gnex's. It will cause a serious confusion and eventually succeed or will just be ignored by everyone.
Edit:
I have seen two people successfully ported f2fs, one to Galaxy Nexus and the other to Nexus 5, but both of them said their phone literally mounted forever. Of course the benchmark provided by one of them with gnex showed a really good improvement, but even he forgot that he shouldn't flash an ext4 kernel, which he did and got bricked.
Zittoro said:
Everything has its upside and downside. I'm not being a smarta$$ or something but just warning you guys...
I think f2fs has a more than 50 or so times slower average mounting time than that of ext4, so most of the flashaholics out there will simply come back to ext4. It requires partition formats and an f2fs kernel. If one flashes an f2fs kernel to a phone with ext4 partitions, the phone will simply hardbrick, and vice versa. Of course it is possible to be unbricked, but it will be difficult for anyone who hasn't dealt with partitions, especially NAND, before.
I'm just afraid this will brick thousands of gnex's. It will cause a serious confusion and eventually succeed or will just be ignored by everyone.
Edit:
I have seen two people successfully ported f2fs, one to Galaxy Nexus and the other to Nexus 5, but both of them said their phone literally mounted forever. Of course the benchmark provided by one of them with gnex showed a really good improvement, but even he forgot that he shouldn't flash an ext4 kernel, which he did and got bricked.
Click to expand...
Click to collapse
I agree with you about this may or may not be worth it to the general public. But I was interested in this for the op as well as my curiosity .
That's also a great reason for this to stay in the dev support thread
The kernel supports both filesystem's , so flashing the f2fs kernel on a ext partition is OK , hell I'm running that combo now lol , I'm only using ( trying to ) f2fs for the userdata partition like the motoX .
I'm not doing this for recognition , weather its of value to anyone other than my curiosity or self is secondary , not saying I'm thinking only about me. But I would never put a ROM out that I didn't test on my phone first .
I'm compiling AOKP 4.4 now with hopefully everything I'm looking for . I'll post the eventual results .
Sent from my Galaxy Nexus using Tapatalk
bsmitty83 said:
I agree with you about this may or may not be worth it to the general public. But I was interested in this for the op as well as my curiosity .
That's also a great reason for this to stay in the dev support thread
The kernel supports both filesystem's , so flashing the f2fs kernel on a ext partition is OK , hell I'm running that combo now lol , I'm only using ( trying to ) f2fs for the userdata partition like the motoX .
I'm not doing this for recognition , weather its of value to anyone other than my curiosity or self is secondary , not saying I'm thinking only about me. But I would never put a ROM out that I didn't test on my phone first .
I'm compiling AOKP 4.4 now with hopefully everything I'm looking for . I'll post the eventual results .
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I know that you're not gonna do anything silly, but I was warning just in case In fact, I'm keen to see another development going on Gnex!!
But are you really doing it like that? If I were you, I would certainly go to the REAL HELL.
Don't be a bat, just make everything f2fs. It won't do any good with ext4 + f2fs combo.
Zittoro said:
I know that you're not gonna do anything silly, but I was warning just in case In fact, I'm keen to see another development going on Gnex!!
But are you really doing it like that? If I were you, I would certainly go to the REAL HELL.
Don't be a bat, just make everything f2fs. It won't do any good with ext4 + f2fs combo.
Click to expand...
Click to collapse
Once I get more comfortable with the filesystem's I'll try doing the sdcard as well . don't think I'll be messing with boot or radio fs anytime soon lol
Sent from my Galaxy Nexus using Tapatalk
Zittoro said:
I know that you're not gonna do anything silly, but I was warning just in case In fact, I'm keen to see another development going on Gnex!!
But are you really doing it like that? If I were you, I would certainly go to the REAL HELL.
Don't be a bat, just make everything f2fs. It won't do any good with ext4 + f2fs combo.
Click to expand...
Click to collapse
Does it really take that long to mount the FS? The Moto X and G are using F2FS, does it take them forever to boot/mount?h
Also, can you point us in the direction of the person who got F2FS running on the Gnex/benchmarks? That would help shed some light on what could be gained and if it's worth it. It should be noted that F2FS has a lot of planned changes coming in the linux kernel (soon) which are supposed to make it even faster.
Here are benchmarks from Samsung displaying F2FS vs. EXT4 on a Samsung Galaxy S3: http://lkml.indiana.edu/hypermail/linux/kernel/1210.2/00005.html
Some of those performance gains are insane--twice as fast in some cases. Mounting time does look to be much, much slower--but we are talking about milliseconds here; is 2.2 seconds to mount a big deal? Doesn't seem like it, if you can improve your storage I/O by that much.
Shidell said:
Here are benchmarks from Samsung displaying F2FS vs. EXT4 on a Samsung Galaxy S3: http://lkml.indiana.edu/hypermail/linux/kernel/1210.2/00005.html
Some of those performance gains are insane--twice as fast in some cases. Mounting time does look to be much, much slower--but we are talking about milliseconds here; is 2.2 seconds to mount a big deal? Doesn't seem like it, if you can improve your storage I/O by that much.
Click to expand...
Click to collapse
It is worth it according to the person who ported it to Galaxy Nexus and his benchmark. I can't tell you who he is and how he did it for some reason, but I think the benchmark (Antutu I think) showed I/O score improved from low 400s to high 500s, and all of the other fields except 2D, which decreased in score, improved at least 10-20% each.
Frankly speaking, I just referred to the mounting time in comarison to ext4, sorry for confusion, so I wasn't saying it's like ol' fashioned computer days. Though, according to the Nexus 5 dev, it took him about 9 seconds to mount system partition. Maybe the reason why it's so slower than the s3 is that it differs by devices or the Samsung developers did an alien job porting it to s3. (Samsung optimization, you know)
Oh, and by the way, the f2fs gnex kernel wasn't released anywhere because he was testing for weeks or months and eventually figured it could be too dangerous, so he created a thread-like thing and asked if anyone wants it and how people thought about releasing it. No one replied, and a few days later, he got bricked, came back to ext4, and another few days later, his computer's hard drive got screwed up without backup, and so he lost the kernel and source.
Hmm. Sucks that he lost his work, that's too bad.
Honestly though, if F2FS is as good as it appears to be, then it seems that it would be a paradigm shift in the ROM community for Android as a whole. For example, F2FS support would be added to each device's kernel (for simplicity's sake, let's imagine CyanogenMod) for each device they support. ClockworkMod Recovery would then be rebuilt for each device (probably snapping to a new main version), which would exclusively format partitions to use F2FS instead of EXT4.
With F2FS support in the kernel for Recovery and Android, all the components are essentially in place, and people could start enjoying the additional performance improvements.
There would be the initial hurdle of porting F2FS support, building Recovery images, and making it clear that the new Recoveries are using F2FS and that a "fresh wipe" would be required to migrate to the new system. Once done, though, everything else should be easy like it is now with ROM updates, backups, etc.
The only other aspect would be a Windows/Mac driver for F2FS.
F2FS is really, really looking good now. If Samsung has even more performance tucked away like they claim they do, it'll really be something.
A couple of things that I've got to say on this topic as I've been trying hard to make this fs work , I'm pretty close , got a few critical pointers from the mighty dhacker29 but still working on getting it all to work together .
A kernel that supports f2fs is the easiest part , it was a pain initially patching it , but it still works just like any other kernel , only it supports another fs . It could be applied to any existing kernel very easily . ( I made it into one single git commit )
As I understand from what I've read in the motoX threads and different sources , twrp adopted f2fs as of twrp 2.6 , so recovery supports it , twrp does anyways and I'm sure I could get cm to work too .
The f2fs mkfs tools are present in 4.3 ROM sources all you have to do is edit boardconfig.mk and device.mk to include said tools
I edited the fstab to use f2fs on /data but when I build a ROM and flash , it goes straight to storage crypto unlock , which my guess is because its still ext4 so the /data isn't being loaded and that's why it jumps straight to unlock storage .
That's pretty much as far as I've gotten .
I'm still working on this , I know its a matter of a combo of how the device formats and partitions the /data.
So far no bricks , I've made my sdcard unmountable , but I just side loaded a ROM and reboot recovery and alls well . I adb pulled my entire sdcard just in case tho lol
If ever this works and its worth people using , not my call , it would be quite painfree . it would require a format of your sdcard , but only once .
And the reason that this is only applied to data and not all partitions is because the only benefits are from the userdata partition , its been tested .
Just sitting here watching my laptop compile yet again .....
Also its more than just a kernel for the gnex. Once all ROMs and kernels support both , it its totally possible , to say in aroma , pick which fs you want formatted , again you would lose your sdcard each time you switch but there's no way around it . just thinking outloud but I need to find out how I can have the install script format the data partition and mount it f2fs. Thats where its at
Sent from my Galaxy Nexus using Tapatalk
I'm waiting to continue this when I buy a new phone in the next month or so , when I retire my nexus I'll throw everything at it without worry , I am only concerned about partitioning my storage to f2fs , then if my ROM recovery and kernel doesn't work , being stuck with no way to repartition back to ext4 , but I don't think that's a possibility anyways as long as I can get back to recovery or adb I'm OK
Sorry bout the delay , but there's only so much experimentations I can do on my main phone . hopfully I'll have an end product to test soon . everything's just sitting waiting to be flashed . its frustrating waiting so if I get brave this weekend I might just try anyways
Sent from my Galaxy Nexus using Tapatalk
Awesome progress man, you've accomplished a ton!
Is it necessary to partition Recovery as F2FS?
In my mind, it seems like you could stick with an EXT4 Recovery, and simply partition /System as F2FS, and flash a compatible ROM (as this is what the Moto X/G currently do), and that should be enough to see initial gains. Of course, if every partition is F2FS, there would be even more room for improvement--but /System should be enough at first.
Is there concern that partitioning /System could cause a brick? As long as you have a Recovery that can partition EXT4 or F2FS, you could always re-partition it easily from Recovery, right?
EDIT: I do understand your concern, though. It's possible to format via ADB, right? So, for example, if I wanted to be a guinea pig for you and flash my phone, I could do so--and if things go awry, I could repartition and restore from a NAND backup, right? As long as you can ADB in, and you can partition via ADB, seems like you can't really brick a device; that'd be like "bricking" a HDD by partitioning from FAT32 to NTFS to EXT4, wouldn't it?
From what I understand , the recovery can stay as is , twrp simply has the ability to recognize f2fs partitions , so once you are using f2fs , your data will be readable.
The actual partitioning tools are located within the ROM . it gets formatted upon flashing.
My concern is that if I repartition the entire /system partition , I could possibly lose the efs data , radio data too . from everything I've read on f2fs , its only beneficial on /userdata , and maybe /cache .
When I did flash an early build of twrp and the aokp ROM I made , when I booted to recovery I couldn't get my data to be read by twrp. So I sideloaded a ROM , then fastbooted a different recovery and all was good .
I don't really think I can brick my phone with what I have made now , its only being used on the data. I should be able to use adb or recovery or a combo to get it back from brick , but for now I really don't think it would be worth you trying just yet. I'll test it soon and if its good I'll post it , but I'm 99% sure it won't work lol . if it was an actual sdcard it would be so simple , but I know its gonna take a few more builds to figure it out . hang tight and I'll report what the outcome is asap ,
I'm still trying to figure out how to actually repartition the sdcard , I've tried modding the updater-script to do it but it status 7'ed on me .
I need to do some more trial and error but again all the pieces are there I think , just need to get it all working together . I'm gonna check out the motoG gits for some inspiration.
EDIT: i was looking in the motoX threads and i noticed that they were in fact formatting through twrp so im gonna explore that
Sent from my Galaxy Nexus using Tapatalk
how's the progress in this topic?
RcrdBrt said:
how's the progress in this topic?
Click to expand...
Click to collapse
As soon as I get a new phone and no long have to worry about damaging this one , I'll test my last build out and update this .
Sent from my Galaxy Nexus using Tapatalk
bsmitty83 said:
As soon as I get a new phone and no long have to worry about damaging this one , I'll test my last build out and update this .
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
If there is something you cant solve, feel free to pm me. I have patched my cwm based recovery to read and format f2fs. This way i can format one or the other easily.
CyanogenMod 11 KitKat for Optimus S/V
This is a basic CyanogenMod 11 rom for the Optimus S/V. It has NOT been tested extensively and I take NO responsibility for any bricked phones, data loss or damages that occur as a result of flashing any version of this rom. It requires ClockWorkMod 6.0.4.5 or later, or TWRP 2.6.3 or later, in order to flash.
What works:
Phone calling (ZVH and ZVJ radios require a patch)
Wifi
Mobile data (thanks to thekraven)
USB tethering
Camera
USB mass storage, MTP
What's broken:
Bluetooth
Wifi tethering
SELinux
You tell me
CWM 6.0.4.6 can be found in the rom directory. Flash Skinny_4.4_Gapps.zip after flashing the rom to get Play Store and Google Sync. Other Gapps will probably be too big to fit on /system.
https://www.mediafire.com/folder/nfgfef6qpril7/CM11
Contributors:
skinbark
bigsupersquid
thekraven
Special thanks to the CyanogenMod and androidarmv6 teams, also gu5t3r for GOptimize.
CM11 KitKat os2sd Version:
cm-11-20140116-thunderc-skinbark-sd.zip is a version of CM11 which is designed to run off your sd card.
To use this version:
1) create and format 3 ext4 partitions following the fat32 partition on your sd card (use gparted not a windows partitioning tool)
/data - at least 256 mb (512 mb or more recommended)
/system - at least 256 mb
/cache - at least 256 mb
2) format /boot in cwm
3) install cm-11-20140104-thunderc-sd.zip
4) install Skinny_4.4_Gapps-sd.zip and reboot
Known Issues (in addition to those in post #1):
formatting/backup/restore issues
possible reduced performance (older/slower sd cards)
reduced battery life (?)
Add wipe zips to a folder on your sd card and flash them from recovery to clear external /data, /system, /cache, or all three.
CWM_6.0.4.6-thunderc-sd.zip is a special version of CWM for os2sd that should only be used if you understand how it works.This version of CWM is not necessary to flash the os2sd rom. See this post for more info about recovery issues with this rom.
A Class 10 microSD card is recommended for best performance.
Power off or reboot to recovery before removing sd card.
os2sd mod courtesy of bigsupersquid
https://www.mediafire.com/folder/dj2d4vpp0hzvb/CM11sd
Warning: This is a highly experimental setup and a work-in-progress. You should have adb installed and know how to use it, along with the flash_image command, before attempting this install. If you have trouble installing this and are unsure how to resolve the problem ask for help on this thread. I take no responsibility for bricked devices, data loss or any other damages resulting from the use of this software. USE AT YOUR RISK.
New build with rild fix for ZVD/ZV5. You'll want to upgrade to this for stability and battery life even if you're not activated.
cm-11-20131225-thunderc-skinbark.zip
Link in OP.
Merry Christmas guys!
Sweet! Will flash once o find my ov...
Virgin fix uploaded.
Virgin.fix.CM11.0.zip
Link in OP.
I'll test. I still use this phone a bit. I don't use gapps anymore so I wouldn't be ale to ile any bugs against them. Is thereanything in particular you want tested?
captaincrook said:
I'll test. I still use this phone a bit. I don't use gapps anymore so I wouldn't be ale to ile any bugs against them. Is thereanything in particular you want tested?
Click to expand...
Click to collapse
Well the biggie right now is getting data going which is sort of difficult for me since my phone's not activated (next week I hope). I'm assuming you're not activated? I guess just general stability and performance, battery life, see what you can run on on it, put it through the wringer. All info is welcome since I really haven't had much feedback yet. It seems to be pretty stable. Let me know if you have any problems, thanks.
really works well...nice job. No chance to test 3g data yet, but everything else works very well...I had to install a keyboard manually, and the battery stats are wrong (fully charged, and stayed fully charged all day) but it is def a daily driver for me.
I uploaded a new 'OS2SD' rom with special recovery, gapps and virgin fix:
cm-11-20140101-thunderc-sd.zip
CWM_6.0.4.6-thunderc-sd.zip
Skinny_4.4_Gapps-sd.zip
Virgin-fix-CM11-sd.zip
Link in post #2. Happy New Year!
Got the order of the partitions wrong in post #2, sorry. Fixed now. 3G fix coming soon!
I uploaded new standard and os2sd builds with data fix.
cm-11-20140104-thunderc-skinbark.zip
Link in post #1
cm-11-20140104-thunderc-sd.zip
Link in post #2
After a crash fest with the build at the time of my last post, this newish one is alright so far. Things get choppy fast and the input is a real pain. That is about as good as I have it. Alternate market works, wifi is good, and its chugging along.
captaincrook said:
After a crash fest with the build at the time of my last post, this newish one is alright so far. Things get choppy fast and the input is a real pain. That is about as good as I have it. Alternate market works, wifi is good, and its chugging along.
Click to expand...
Click to collapse
long press home and press the three-bar onscreen button to close running apps.
also fast reboot off market is very handy to manually clear ram. heard about that one from andyopie150, like it.
Ya the main issue is just generally its a bit slow. I'm not trying to be one of those people who dog the ROM cause devs sibt human but this is just what I have experienced. I know our SOC came out when Moses was around so I'm not expecting miracles. I'm not sure if you guys have more planned or not but its really neat how efficient the phone is on 4.4 and if it was to get faster it'd be amazing.
The keyboard, can you guys adjust the size values? Its microscopic! Hacker's Keyboard fits the bill in the meantime.
captaincrook said:
Ya the main issue is just generally its a bit slow. I'm not trying to be one of those people who dog the ROM cause devs sibt human but this is just what I have experienced. I know our SOC came out when Moses was around so I'm not expecting miracles. I'm not sure if you guys have more planned or not but its really neat how efficient the phone is on 4.4 and if it was to get faster it'd be amazing.
The keyboard, can you guys adjust the size values? Its microscopic! Hacker's Keyboard fits the bill in the meantime.
Click to expand...
Click to collapse
For now I can just suggest the usual speed-up stuff - turn off animations, ksm, cpu/governor etc. There may be some build.prop tweaks you could use, and I'm expectiing zram support to be enabled soon. Crossbreeder might be something else to try. If we could get ART going it might help some but I don't know if that's likely. I probably won't try to tweak the stock keyboard, there's plenty of alternatives available.
tried flashing this on my optimus V and i got a error when i was flashing it, error 7 i think it was, i used the CWM you wanted us to use but it made it so that i couldnt boot into recovery.
Trozzul said:
tried flashing this on my optimus V and i got a error when i was flashing it, error 7 i think it was, i used the CWM you wanted us to use but it made it so that i couldnt boot into recovery.
Click to expand...
Click to collapse
regular rom or os2sd?
skinbark said:
regular rom or os2sd?
Click to expand...
Click to collapse
regular i tried a different CWM 6+ and that one gave me the error*
Trozzul said:
regular i tried a different CWM 6+ and that one gave me the error*
Click to expand...
Click to collapse
Here's another recovery you can try.
https://www.mediafire.com/?s8c94941y8kubdd
captaincrook said:
Ya the main issue is just generally its a bit slow. I'm not trying to be one of those people who dog the ROM cause devs sibt human but this is just what I have experienced. I know our SOC came out when Moses was around so I'm not expecting miracles. I'm not sure if you guys have more planned or not but its really neat how efficient the phone is on 4.4 and if it was to get faster it'd be amazing.
The keyboard, can you guys adjust the size values? Its microscopic! Hacker's Keyboard fits the bill in the meantime.
Click to expand...
Click to collapse
Any information is a good thing, positive or negative. Harmonia with the Xionia kernel fairly flies speed-wise, but everything since that seems to choke my phone somewhat. And Mirage is the best Gingerbread available... but I enjoy the extra features more than the speed, which is what keeps me trying for the bleeding edge.
(example: the double-tap-hold-and-slide to zoom is built in all over 4.4, in 4.2 I only saw that in Maps.)
ART may or may not happen. I have to learn more thumb assembly to fix it. My decent class for school this session (the easy one since I did 8088 back in 1991) is x86 assembly. Doesn't apply, but maybe I can get more parallell info from it. There's lots of good info out on the net with minimal searching as well, but not much if any on downconversion of thumb2 to thumb1 code. I found enough to fix a few files but there's still more to go. I'd be impressed with myself if I got that to run.
CrossBreeder seems to work.
Could someone tell me the differences between f2fs and ext4? And what's better?
I can be a smart a$$ and tell you to "google it", but I don't like that attitude
I came across f2fs when using devil kernel, and from readings, it seems f2fs is a new file system created by samsung to replace ext4 for mobile devices, as it is supposed to be faster, and a couple of articles claimed that it was when used on the motorola X (I think...) than standard ext4.
Basically it was a tradeoff between faster boot times (ext4) and a faster overall system (f2fs), and when I tested it on 4.3 stock roms with devil kernel, I can honestly say I saw improvement, but the whole process (special recovery, special kernel, modifying update scripts for roms not to format back to ext4 before flashing, or going through the whole ext4-2-f2fs cycle after every update) was hell, and I consider myself an above-average user.
So until it is made a bit easier or more user friendly, I'd stay away, as the performance boost is not worth the hassle for the normal-user.
just my 2cents
ticktock666 said:
I can be a smart a$$ and tell you to "google it", but I don't like that attitude
I came across f2fs when using devil kernel, and from readings, it seems f2fs is a new file system created by samsung to replace ext4 for mobile devices, as it is supposed to be faster, and a couple of articles claimed that it was when used on the motorola X (I think...) than standard ext4.
Basically it was a tradeoff between faster boot times (ext4) and a faster overall system (f2fs), and when I tested it on 4.3 stock roms with devil kernel, I can honestly say I saw improvement, but the whole process (special recovery, special kernel, modifying update scripts for roms not to format back to ext4 before flashing, or going through the whole ext4-2-f2fs cycle after every update) was hell, and I consider myself an above-average user.
So until it is made a bit easier or more user friendly, I'd stay away, as the performance boost is not worth the hassle for the normal-user.
just my 2cents
Click to expand...
Click to collapse
thank you very much
XSLdesire said:
thank you very much
Click to expand...
Click to collapse
Indeed. I've always stuck with ext4 on android, but wondered whether I should investigate. Was disillusioned by their dreadful RFS on my i9000. Will keep an open mind to trying it one day in the future.
What the title says
format data from TWRP
but why would you need it removed, if I may ask
gwolfu said:
format data from TWRP
but why would you need it removed, if I may ask
Click to expand...
Click to collapse
Formating data does not help, i'm thinking that by removing encryption there should be some speed improvement but want to test this for myself
Deadeye* said:
Formating data does not help, i'm thinking that by removing encryption there should be some speed improvement but want to test this for myself
Click to expand...
Click to collapse
I tested this on my OP5 and I did not see any noticeable difference. Since the 5T has the same specs, I'm pretty sure the results will be the same.
Personally, I don't think it's worth the hassle, especially because once ROMs start coming out, they will ask you to be encrypted anyway
Removing encryption used to allow the phone to perform better but that is no longer the case with the high end phones. Removing encryption is not going to provide any better performance and really compromises your data.
i believe disabling encryption, if not makes phone faster, at least makes battery time longer.
lyrebird said:
i believe disabling encryption, if not makes phone faster, at least makes battery time longer.
Click to expand...
Click to collapse
No its not true.
Decrypting doesn't do anything as far as battery or performance. Maybe a little performance in the old days but definitely not anymore. You notice zero difference. If u do format internal to keep it decrypted u have to flash no verity and a kernel that doesn't force encrypt. These r the correct steps
yung40oz84 said:
Decrypting doesn't do anything as far as battery or performance. Maybe a little performance in the old days but definitely not anymore. You notice zero difference. If u do format internal to keep it decrypted u have to flash no verity and a kernel that doesn't force encrypt. These r the correct steps
Click to expand...
Click to collapse
If I want to encrypt back how do I get it back on oneplus 5t.
Hi there I decrypted my 5t ,running Oreo Stock beta1, and performance but more battery life inproved
I wiped flashed beta1, formated data, reboot recovery, flashed magisk beta and no verity encryption v2 (https://www.google.de/amp/s/forum.x...-how-to-decrypt-data-partition-t3642144/amp/l
After booting I have strong impression performance is better, but for sure battery life..
Simonis said:
Hi there I decrypted my 5t ,running Oreo Stock beta1, and performance but more battery life inproved
I wiped flashed beta1, formated data, reboot recovery, flashed magisk beta and no verity encryption v2 (https://www.google.de/amp/s/forum.x...-how-to-decrypt-data-partition-t3642144/amp/l
After booting I have strong impression performance is better, but for sure battery life..
Click to expand...
Click to collapse
I've compared the two, there is no gain in battery life or performance of read/write speeds. Sorry, but this may be placebo effect.
xocomaox said:
I've compared the two, there is no gain in battery life or performance of read/write speeds. Sorry, but this may be placebo effect.
Click to expand...
Click to collapse
Hi there how did you measure this ,
Sorry but this doesn't sound logical, after all System has to de- and encrypt Data this can't be done without resources, meaning CPU and power,bits just physics, but I
Agree this might be not much relevant on this high end devices
, As in the older ones