Oh,,, hell yeah, i want it badly. :victory:
+1
No. No sources are released, and you'll have to find someone to port it when the sources are released in the fall.
SGWUser said:
No. No sources are released, and you'll have to find someone to port it when the sources are released in the fall.
Click to expand...
Click to collapse
Maybe sir arco will save us again when the sources are released You never know..
a port may come soon but we have to wait until it is final so they release cm 12
eri000 said:
a port may come soon but we have to wait until it is final so they release cm 12
Click to expand...
Click to collapse
That isn't necessarily true, for example CM 10.1 released by arco still in beta4 version
dqsnunes said:
That isn't necessarily true, for example CM 10.1 released by arco still in beta4 version
Click to expand...
Click to collapse
the CM team announced that there will be NO CM version until the google releases the final image of android L on AOSP.This doesn't mean we will have a final stable version of cm immediately BUT we will only see a cm12 build when final android L gets merged into aosp.
^That is for other phones that get CM OFFICIAL.For ancora we have to wait a little bit more for unofficial cm, which is based on official cm.So no official--- no unofficial (arco if he has time to mess with it,or others)
BTW, Android L is currently being ported to the Nexus 4 and Nexus 7 2012 right now. Both are almost functional.
I think even if we were to have Android L here, i don't think it will be responsive. Google said, Animation transitions run at 60fps, Im not sure if overall perfomance can run at the same fps because i bet our processor is not powerful enuff or smth. CMIIW.
Android L Port For Nexus 4
Newest Android L Port For Nexus 4 Is Now Fully Operational And Ready For Download
INFO
I strongly doubt that our device could get an Android L update.
The default runtime of android l is ART runtime.Our device does'nt hold that much of system memory for apps.
The only chance is to make a switchable runtime like in Kitkat (Dalvik/Art) or creating a new partition .
Anyway these are all guess and lets see what magic our Great devs can bring to our small beloved device.:good::fingers-crossed:
theloneseeker said:
I strongly doubt that our device could get an Android L update.
The default runtime of android l is ART runtime.Our device does'nt hold that much of system memory for apps.
The only chance is to make a switchable runtime like in Kitkat (Dalvik/Art) or creating a new partition .
Anyway these are all guess and lets see what magic our Great devs can bring to our small beloved device.:good::fingers-crossed:
Click to expand...
Click to collapse
A swap partition for art can't help?
theloneseeker said:
I strongly doubt that our device could get an Android L update.
The default runtime of android l is ART runtime.Our device does'nt hold that much of system memory for apps.
The only chance is to make a switchable runtime like in Kitkat (Dalvik/Art) or creating a new partition .
Anyway these are all guess and lets see what magic our Great devs can bring to our small beloved device.:good::fingers-crossed:
Click to expand...
Click to collapse
Problem is not a system partition because system partition size(550mb) should be enough because at the moment with latest cm11+gapps i have a 150 mb free space on my system partition so i think our phone can/will handle next android release but we cant know at the moment so im not sure
But main problem is small cache partition
İt is just 60 mb
For that reason we are using some dirty workarounds(in my opinion) like this https://github.com/arco/android_device_samsung_ancora/commit/3455d7837c951e297335295a36cd2202a9f629f3 with that workaround apps is using /data partition instead of /cache partition for dalvik-caching operations
Why im saying this is dirty workaround? Because i think each operation should use its own partition
Repartition is a real fix for that kind of problems but this way is a very dangerous and have brick risk
İm planning to make some experiments like this:
-With fdisk im planning to split out my internat sdcard(1.7 GB ,mmcblk0p28) to 2 new partitions(first partition will be mmcblk0p28 and have 1.3 GB size and second partition will be mmcblk0p29 and have 400 MB size)
Then we will use mmcblk0p29 as cache partition
-For that firstly we need to format the partition as ext4(because internal sd is vfat but cache partition must be ext4 fs type formatted)
-After converting from vfat to ext4 of new mmcblk0p29 partition, we will change cache partition from mmcblk0p16 to 29 through fstab.qcom
-and last thing we need to do is removing/disabling previous workaround so we will change the following build.prop line dalvik.vm.dexopt-data-only=1 to dalvik.vm.dexopt-data-only=0
This is the cleanest way i think because we arent touching to main partitions(system,data and cache)
We just need to split it internal sd(1.7 GB)
Regards
sir mordred said:
Problem is not a system partition because system partition size(550mb) should be enough because at the moment with latest cm11+gapps i have a 150 mb free space on my system partition so i think our phone can/will handle next android release but we cant know at the moment so im not sure
But main problem is small cache partition
İt is just 60 mb
For that reason we are using some dirty workarounds(in my opinion) like this https://github.com/arco/android_device_samsung_ancora/commit/3455d7837c951e297335295a36cd2202a9f629f3 with that workaround apps is using /data partition instead of /cache partition for dalvik-caching operations
Why im saying this is dirty workaround? Because i think each operation should use its own partition
Repartition is a real fix for that kind of problems but this way is a very dangerous and have brick risk
İm planning to make some experiments like this:
-With fdisk im planning to split out my internat sdcard(1.7 GB ,mmcblk0p28) to 2 new partitions(first partition will be mmcblk0p28 and have 1.3 GB size and second partition will be mmcblk0p29 and have 400 MB size)
Then we will use mmcblk0p29 as cache partition
-For that firstly we need to format the partition as ext4(because internal sd is vfat but cache partition must be ext4 fs type formatted)
-After converting from vfat to ext4 of new mmcblk0p29 partition, we will change cache partition from mmcblk0p16 to 29 through fstab.qcom
-and last thing we need to do is removing/disabling previous workaround so we will change the following build.prop line dalvik.vm.dexopt-data-only=1 to dalvik.vm.dexopt-data-only=0
This is the cleanest way i think because we arent touching to main partitions(system,data and cache)
We just need to split it internal sd(1.7 GB)
Regards
Click to expand...
Click to collapse
Nice thinking and good luck :good:
sir mordred said:
Problem is not a system partition because system partition size(550mb) should be enough because at the moment with latest cm11+gapps i have a 150 mb free space on my system partition so i think our phone can/will handle next android release but we cant know at the moment so im not sure
But main problem is small cache partition
İt is just 60 mb
For that reason we are using some dirty workarounds(in my opinion) like this https://github.com/arco/android_device_samsung_ancora/commit/3455d7837c951e297335295a36cd2202a9f629f3 with that workaround apps is using /data partition instead of /cache partition for dalvik-caching operations
Why im saying this is dirty workaround? Because i think each operation should use its own partition
Repartition is a real fix for that kind of problems but this way is a very dangerous and have brick risk
İm planning to make some experiments like this:
-With fdisk im planning to split out my internat sdcard(1.7 GB ,mmcblk0p28) to 2 new partitions(first partition will be mmcblk0p28 and have 1.3 GB size and second partition will be mmcblk0p29 and have 400 MB size)
Then we will use mmcblk0p29 as cache partition
-For that firstly we need to format the partition as ext4(because internal sd is vfat but cache partition must be ext4 fs type formatted)
-After converting from vfat to ext4 of new mmcblk0p29 partition, we will change cache partition from mmcblk0p16 to 29 through fstab.qcom
-and last thing we need to do is removing/disabling previous workaround so we will change the following build.prop line dalvik.vm.dexopt-data-only=1 to dalvik.vm.dexopt-data-only=0
This is the cleanest way i think because we arent touching to main partitions(system,data and cache)
We just need to split it internal sd(1.7 GB)
Regards
Click to expand...
Click to collapse
Umm very interesting if you want some testers,i'm here.
If you have cm11 theme chooser:
http://forum.xda-developers.com/android/themes/theme-l-ready-t2802979
https://play.google.com/store/apps/details?id=nexbit.icons.moonshine
Settings>Performance>Force high-end graphics>check
AND YOU HAVE L IN YOUR WONDER(I LOVE MY WONDER)
what is android L? can someone tell me about it please?
smartiescoke said:
what is android L? can someone tell me about it please?
Click to expand...
Click to collapse
The upcoming Android version. About it...there are many things to say. You could search YouTube for "Google I/O 2014". There are a lot of new things about it. If you've got time to spend and curiosity, it might be very interesting to watch. This way, you will also answer your own question (and more).
arsradu said:
The upcoming Android version. About it...there are many things to say. You could search YouTube for "Google I/O 2014". There are a lot of new things about it. If you've got time to spend and curiosity, it might be very interesting to watch. This way, you will also answer your own question (and more).
Click to expand...
Click to collapse
whoa! really? awesome! i always been waiting google to update different kind of android version. ui and etc, hope it will come to our wonder soon! XD
oh man i love android L ui and statusbar. Hoping our Great Developer can bring this to our Wonder.
#sorry for my bad english.
Related
First: Have Alquez's CM7.2 installed
Second: Flash his new kernel that supports linux swap partitions
Third: Read my tutorial on creating a Ext partition and a third Linux swap partition
Fourth: Read this post by me on how to enable swap persistantly and adjust swappiness.
Does it make any sense to use a swap partition?
I think, no. Why not? Read about in the official cm wiki: http://wiki.cyanogenmod.com/wiki/Swap_and_Compcache
Android has a very good built-in memory management. Apps not used any more will be closed and memory released. Swap does change that behavior, because RAM now (virtually) is much bigger. There's no sense anymore in cleaning parts of the RAM.
Androids mem management is much more efficient.
The only reason to use swap would be 1st generation phones (G1, Dream, Magic). Wildfire S would have no advantage of swap! Rather the opposite.
Using swap should require at least class 6 SD for not slowing down the device. Plus, the additional write accesses will wear down your sd much quicker.
Everyone has to decide if he wants this. I decided, not to do.
theq86 said:
does it make any sense to use a swap partition?
Click to expand...
Click to collapse
I'm just telling you how. You'll have to decide that for yourself.
Personally I'm just playing around with it...cause I can.
d33ps1x said:
I'm just telling you how. You'll have to decide that for yourself.
Personally I'm just playing around with it...cause I can.
Click to expand...
Click to collapse
Well, I read a little bout that topic and consider it more harming than useful. (read my edited post above)
Consider setting /proc/sys/vm/swappiness to 10 or even lower for android ?
what on earth is swap anyway?
swap is taking apart of your sd card or internal memory as ram memory like pageing file in windows
About CM12
Please Post all your Feedback, Fixes or Discovery of new Bugs and Discussion about Mike's CM12 here.
Its compiled by me and released here for some public testing. It was and is Mike's CM !! its his Hardwork !
Thanks to Mikeionniia for his Hardwork and ROM , Langes for helping in the Guide and @Men_in_black007 for helping me in compiling.
Downloads and Build's History
1. 4 Jan 2015 (Initial Build) http://d-h.st/vMXg
*Calls not Going Through but Calls are being Received
*Internet/Data Plan Not Working
*Camera is Working
*Video camera is not 100% stable, sometimes it restart phone. 480p recording work mostly without problems
2. 22 Jan 2015 (Wifi Started Working) http://d-h.st/4Ii
*Wifi Working
*Bluetooth Working
*SMS Working
*Randomly Reboots alot
3. 5 Feb 2015 (Calls/Data work randomly) http://d-h.st/34om
4. 12 Feb 2015 (Calls/Data much Stable. Less Random Reboots Much Stable) Kernel not working so Not uploading this.
5. 17 Feb 2015 (Many Changes inside the Settings. Overclock Built in the Settings and many minor changes. Smoother/Stable) [B]http://d-h.st/AcDk[/B]
6. 7 March (Stable than any other build. Smoother/Faster. Loving it. Some changes in Settings) [B]http://d-h.st/2KHx[/B]
FOR ALL LATEST AND NEW BUILDS PLEASE GO TO THE OFFICIAL THREADS HERE !! Plz hold your Q&A and Discussion in their respective Discussion Threads only !! Don't spam the Dev Threads !!
CM12 For all LegacyXperia Devices http://forum.xda-developers.com/xperia-arc/development/dev-2011-unofficial-cyanogenmod-12-0-t3053950
AOSP Lollipop For all LegacyXperia Devices http://forum.xda-developers.com/xpe...v-2011-android-source-project-builds-t3053170
Gapps
DOwnload Pico,Nano or Micro Gapps Only.. no Bigger than this. !!
from here http://forum.xda-developers.com/par...apps-official-to-date-pa-google-apps-t2943900
Install Instructions
You should have an Ext4 Partition on your sd card to install properly. I have a 4gb Ext4 Partition on my 32gb card.
Be Warned the process of creating an Ext4 Partition can/maybe wipe your SD card.. So Back Up appropriately
1. Flash .79 FTF in Flash tool
2. Flash Boot.img from Fastboot.
3. Staying in fastboot, erase system and userdata
fastboot erase system
fastboot erase userdata
4. Boot Device, Enter Recovery and (Factory Reset) and then (Wipe Cache)
5. Go to Apply Update, Scroll to the Location of you Zip file of the ROM and Install the ROM !
6. Boot ROM.
Detailed Installation Instructions here for Newbies
http://forum.xda-developers.com/showpost.php?p=58830270&postcount=110
How to Root The ROM or Activate Root on the ROM ?
Go to Settings / About Phone / Build Number and (Press this Continuously for 7+ times until it shows u
that Development Options is Activated.
Go Back to Settings, Click on Development Options and Enable Root Access For Apps/ADB or Both.
Review Video
Installation Video
Thank you for this. From the quick testing I did the D-Pad and buttons work fine but the D-Pad has incorrect directions like it's been rotated anti clockwise up is right, left is up, down is left, right is down. Although you probably know that already directions for installing are slightly incorrect. There is no CWM with this boot.img its CyanogenRecovery so we can't mount /system to wipe it, but it still seems to install and boot fine. System is erased with Fastboot in a previous step anyway
Camera is upside down, but again obvious one you probably know about Well done to everyone involved in getting this device on the cutting edge! Performance is really really good, its like lollipop was made for this
What about Phone, Wifi, BT, Camera, Sound, GPS, Auto-Rotate when slider is out, prox. Sensor, light sensor - is all that working? What yes what not?
hello guys
What rom base should I use? the same as 4.4.4
stou curious to test 5.0 thanks
DocMAX said:
What about Phone, Wifi, BT, Camera, Sound, GPS, Auto-Rotate when slider is out, prox. Sensor, light sensor - is all that working? What yes what not?
Click to expand...
Click to collapse
Phone (Calls u mean) - Not Working
Wifi - Not Working
GPS - I didn't Test
Prox. Sensor - I didn't Test
Light Sensor - I didn't Test
Auto Rotate - Was working I think so, I don't remember
Sound - Working
BT - Working
Camera - Working
DocMAX said:
What about Phone, Wifi, BT, Camera, Sound, GPS, Auto-Rotate when slider is out, prox. Sensor, light sensor - is all that working? What yes what not?
Click to expand...
Click to collapse
Owriço Winchester said:
hello guys
What rom base should I use? the same as 4.4.4
stou curious to test 5.0 thanks
Click to expand...
Click to collapse
what do you mean by ROM base you should use.. ??
did you mean KErnel ?? explain your question plz.
saqibkhan said:
what do you mean by ROM base you should use.. ??
did you mean KErnel ?? explain your question plz.
Click to expand...
Click to collapse
need to flash stock MT25i (Neo L) ftf
Installation guide?
I need to flash the same boot.img of KitKat and mt25.ftf or something new?
You not said nothing about how to install this special ROM 5.0.2
Please put an installation guide in the post
Thanks and great work
OK guys, i'm leaving. CM12, CM11 and all Android 4.x stuff is simply crap. Functions are missing, the UI is nochy. Overall not feeling good. And probably nobody will ever release a superb CM1x ROM. So i'm back at Ginger Bread - the original. Bye.
javix1997 said:
Installation guide?
I need to flash the same boot.img of KitKat and mt25.ftf or something new?
You not said nothing about how to install this special ROM 5.0.2
Please put an installation guide in the post
Thanks and great work
Click to expand...
Click to collapse
all I can say is.. I have a 32gb memory card.. a Ext4 4 gb Partition.. and when I installed the ROM .. it showed me everything as One large 1gb Partition.. not 1gb.. something 900mb ..
So make a partition and then Install the ROm !! it should work like it did work for me.. I Wiped everything from ADB .. and Installed from the Recovery by Cyanogen only.
javix1997 said:
Installation guide?
I need to flash the same boot.img of KitKat and mt25.ftf or something new?
You not said nothing about how to install this special ROM 5.0.2
Please put an installation guide in the post
Thanks and great work
Click to expand...
Click to collapse
DocMAX said:
OK guys, i'm leaving. CM12, CM11 and all Android 4.x stuff is simply crap. Functions are missing, the UI is nochy. Overall not feeling good. And probably nobody will ever release a superb CM1x ROM. So i'm back at Ginger Bread - the original. Bye.
Click to expand...
Click to collapse
true that.. when ever I return to ginger bread from all the other ROMS I feel so relieved !! its soo fast and easy and special.. if you can help me.. help in building a cm 200/700mb Kernel.. cuz cm7.3 runs like hell fast.
but yeah.. we need newer ROMS as well and I was loving everybit of Lollipop .. but once the Bugs are done.. i will be back on that..
hello !! I wonder if you could help me to port for xperia neo v
What would it take?
There is cm12 for neo v. Just look for it on Yours phone forum
saqibkhan said:
true that.. when ever I return to ginger bread from all the other ROMS I feel so relieved !! its soo fast and easy and special.. if you can help me.. help in building a cm 200/700mb Kernel.. cuz cm7.3 runs like hell fast.
but yeah.. we need newer ROMS as well and I was loving everybit of Lollipop .. but once the Bugs are done.. i will be back on that..
Click to expand...
Click to collapse
I had compiled cm12, but i don't have time right now to reformat my 32gb card to make 2nd partition.
Btw, in what format is that 2nd partition? Ext2 or ext4?
As i see from source code, system is 900MB, so i guess data partition is on 2nd partition on sdcard?
Just asking, so to flash cm12 i need:
Flash any .62+ firmware (to unlock custom partitioning)
Flash kernel from zip
Erase system and userdata from fastboot
Flash rom from recovery
?
Ps: as for cm7, i can't help much, because i don't have harddisk space in virtualbox (cm12 source took all avaiable space)
If you can compile cm7 kernel, try with values from my thread (the 220/700 ones)
I can recalculate values again if you need more space. As i recall, official cm7 for zeus is around 130 MB and gaaps is around 7MB, so maybe 149.5/770 partitions size is ok?
Sent from my R800i using XDA Free mobile app
Bakisha said:
I had compiled cm12, but i don't have time right now to reformat my 32gb card to make 2nd partition.
Btw, in what format is that 2nd partition? Ext2 or ext4?
As i see from source code, system is 900MB, so i guess data partition is on 2nd partition on sdcard?
Just asking, so to flash cm12 i need:
Flash any .62+ firmware (to unlock custom partitioning)
Flash kernel from zip
Erase system and userdata from fastboot
Flash rom from recovery
?
Ps: as for cm7, i can't help much, because i don't have harddisk space in virtualbox (cm12 source took all avaiable space)
If you can compile cm7 kernel, try with values from my thread (the 220/700 ones)
I can recalculate values again if you need more space. As i recall, official cm7 for zeus is around 130 MB and gaaps is around 7MB, so maybe 149.5/770 partitions size is ok?
Sent from my R800i using XDA Free mobile app
Click to expand...
Click to collapse
Hi that's nice that you compiled again.. cuz Mike might have made some changes and some bugs might be done with..
yes system was 900mb+ etc.. and I had a 4gb partition on my card for Link2SD .. its Ext4 !! as far as i remember.
Step 1...i flashed the .79 FTF for Xperia Play..
Step 2...then i Wiped System and userdata by fastboot as listen in Mikes CM11 OP !
Step 3...Then i flashed Kernel.. (or you can switch these steps 2 or 3)
Step 4... Install ROM by Using Cyanogen Recovery. i can we need to go to Install Update.zip option ..
Edit : i think 210/700mb is more than enough.. values are already calculated by you so thanks for that.. its always nice to have some space in system else it keeps showing (System Low on Memory Error)
i can compile as well. but im confused.. i have already the cm12 source downloaded and compiled.. will the cm7 take the same space on top of that.. or how will i differentiate the folder for both.
is their a step by step guide i can follow.. and at which step do i need to change the Kernel Values ! and where.. i have no clue of that ! can you rite a quick step guide for me.. lead me into the right direction and i can ask you my doubts along the way.
saqibkhan said:
i can compile as well. but im confused.. i have already the cm12 source downloaded and compiled.. will the cm7 take the same space on top of that.. or how will i differentiate the folder for both.
is their a step by step guide i can follow.. and at which step do i need to change the Kernel Values ! and where.. i have no clue of that ! can you rite a quick step guide for me.. lead me into the right direction and i can ask you my doubts along the way.
Click to expand...
Click to collapse
To be honest, i don't know. My guess is that you need to delete cm12 source, then from ~android/system folder do the repo init for cm7
There is a guide for building CM here but use
Code:
repo init -u https://github.com/CyanogenMod/android.git -b gingerbread
instead of ics
Editing partition should be easy, as you only need to edit file semc_zeus_defconfig (it should be in ~android/system/kernel/arch/arm/configs/ folder or just search where is that file when you download source)
Then build as a guide say.
I am not 100% sure about building CM from source, so i'm only guessing, maybe someone else with better knowledge about compiling could say
As for CM12, i'll compile it again in few days, and hopefully i'll have time to test it for weekend
saqibkhan said:
true that.. when ever I return to ginger bread from all the other ROMS I feel so relieved !! its soo fast and easy and special.. if you can help me.. help in building a cm 200/700mb Kernel.. cuz cm7.3 runs like hell fast.
but yeah.. we need newer ROMS as well and I was loving everybit of Lollipop .. but once the Bugs are done.. i will be back on that..
Click to expand...
Click to collapse
cm 7.3? i only see cm 7.2 on official site. is EVERYTHING working? (including touchpads?)
DocMAX said:
cm 7.3? i only see cm 7.2 on official site. is EVERYTHING working? (including touchpads?)
Click to expand...
Click to collapse
yes cm7.3 .. DEv of cm7.2 ended a long time back.. then the FXP team compiled cm gingerbread again late in 2013 December I think .. and started calling it cm7.3 . kinda like the EOL version.. its amazing .. only change I want is a 210/700mb Kernel.. that would make it even more useful
IDK about the Touchpads though.
you should look here at my post in this thread !!
http://forum.xda-developers.com/showpost.php?p=57610312&postcount=3038
Does the second partition have to be 4GB in order to install CM12 or what size?
P.S. Tested Dead Space on CM7.3, Touchpads not working. I have found Doom Kernel + ICS, without heavy apps, to deliver the best overall performance for the Xplay. Overclocking to 1.8GHz makes even Reicast playable.
saqibkhan said:
yes cm7.3 .. DEv of cm7.2 ended a long time back.. then the FXP team compiled cm gingerbread again late in 2013 December I think .. and started calling it cm7.3 . kinda like the EOL version.. its amazing .. only change I want is a 210/700mb Kernel.. that would make it even more useful
IDK about the Touchpads though.
you should look here at my post in this thread !!
http://forum.xda-developers.com/showpost.php?p=57610312&postcount=3038
Click to expand...
Click to collapse
i dont see light sensor working?
ok i have a samsung galaxy SM-T700 what rom and kernal has F2FS support i have searched the forms but nothing for this model came up with a answer.....
thanks very much in advance..
Monster212 said:
ok i have a samsung galaxy SM-T700 what rom and kernal has F2FS support i have searched the forms but nothing for this model came up with a answer.....
thanks very much in advance..
Click to expand...
Click to collapse
Probably none of them do. Developers usually only implement F2FS if the device has slow write speeds on its built in eMMC, such as the original Nexus 7 (and a few others). Some devices have native F2FS support such as the Nexus 9 (which is why it gets its extremely high bench scores). However for this device, it has plenty fast storage already, so the benefit would be almost impossible for the human senses to notice. With all that said, I too would love to use F2FS on at least the cache partition.
SkOrPn said:
Probably none of them do. Developers usually only implement F2FS if the device has slow write speeds on its built in eMMC, such as the original Nexus 7 (and a few others). Some devices have native F2FS support such as the Nexus 9 (which is why it gets its extremely high bench scores). However for this device, it has plenty fast storage already, so the benefit would be almost impossible for the human senses to notice. With all that said, I too would love to use F2FS on at least the cache partition.
Click to expand...
Click to collapse
thank you very much for the reply.. i learned something new...
Monster212 said:
thank you very much for the reply.. i learned something new...
Click to expand...
Click to collapse
Actually, if you install TWRP recovery from here http://forum.xda-developers.com/gal...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633
Then you can have F2FS support. You then just need to look for a rom that supports F2FS, or a kernel that does. I'm still looking myself, so not sure if any ROMs actually do support F2FS yet, but at least you already have F2FS format support. :good:
SkOrPn said:
Actually, if you install TWRP recovery from here http://forum.xda-developers.com/gal...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633
Then you can have F2FS support. You then just need to look for a rom that supports F2FS, or a kernel that does. I'm still looking myself, so not sure if any ROMs actually do support F2FS yet, but at least you already have F2FS format support. :good:
Click to expand...
Click to collapse
Thank you for the info, I will now be looking for a good rom or kernal.....
Sent from my SM-T700 using Tapatalk
You can test my kernel here: http://forum.xda-developers.com/showthread.php?t=3139716
ashyx said:
You can test my kernel here: http://forum.xda-developers.com/showthread.php?t=3139716
Click to expand...
Click to collapse
thank you i will install it now and see how it goes...
I would like to do benchmark test results for before and after F2FS. Curious how it compares to my Nexus 7. On cache it was a good performance increase, but on system it did nothing better. EXT4 seems to be the better file system for the system partition, at least on my Nexus 7.
Sent from my SM-T700 using Tapatalk
SkOrPn said:
I would like to do benchmark test results for before and after F2FS. Curious how it compares to my Nexus 7. On cache it was a good performance increase, but on system it did nothing better. EXT4 seems to be the better file system for the system partition, at least on my Nexus 7.
Sent from my SM-T700 using Tapatalk
Click to expand...
Click to collapse
The kernel I posted doesn't support f2fs on the system partition nor does my guide include it.
As you rightly stated the system partition does not benefit from f2fs as its read only. Ext4 is capable of high read speed.
ashyx said:
The kernel I posted doesn't support f2fs on the system partition nor does my guide include it.
As you rightly stated the system partition does not benefit from f2fs as its read only. Ext4 is capable of high read speed.
Click to expand...
Click to collapse
Yeah agreed, EXT4 is slightly faster at reading, but just by a hair on my N7. However, on partitions that have write permissions, it can "sometimes" be three times faster at random writes. I been using F2FS since feb 2014 "religiously" on my Nexus 7 (and wont run a non-f2fs setup on it), so I am very well versed in its use. Legolas was the first one to bring it to custom Android (I know because I was one of his support techs helping users convert to it, until he disappeared that is lol. Then I started helping USBhost with CarbonROM), and was the first to release a F2FS app in the play store. He was also the first, and only individual, to have a Conversion app to convert your ROM to f2fs, which gave new life to my N7 and any ROM I tried back in 2014 (it did not support 5.0 though). Without F2FS, sadly my Nexus 7 is almost worthless.
If only I can find the many screenshot test results we've done with F2FS, it would come in handy here too. On the N7 its a night and day difference, but here this device is already plenty fast. Id love to see some insane results though.... If only Jaegeuk would develop a Windows driver already. I would like to use it for my Linux box, Windows and Android tbh, and format the sdcards with it, and maybe even USB storage drives to try and pick up on the write speeds a bit. Well see I guess...
My SkyHigh TW LL 5.0.2 kernels support both EXT4 and F2FS for DATA and CACHE partitions.
Note: You need to have supported base firmware for successful flash.
Deathly Aosp Kernel supports Ext4 and f2fs on cache and data
Rom support for it is included on aicp, slim, carbon, liquid
deadman96385 said:
Deathly Aosp Kernel supports Ext4 and f2fs on cache and data
Rom support for it is included on aicp, slim, carbon, liquid
Click to expand...
Click to collapse
ANY ROM can support F2FS. Its just the Kernel that needs to be built with support.
It's possible to convert any partition using various scripts (adjusted to suit device) that are about. But the easiest way is to use ashyx F2FS recovery. It saves a lot of pain.
UpInTheAir said:
ANY ROM can support F2FS. Its just the Kernel that needs to be built with support.
It's possible to convert any partition using various scripts (adjusted to suit device) that are about. But the easiest way is to use ashyx F2FS recovery. It saves a lot of pain.
Click to expand...
Click to collapse
Yeah the roms i listed already have native support no scripts or anything because the f2fs lines have been added too the fstab. So all you need to do is format cache and data in twrp and your done.
deadman96385 said:
Yeah the roms i listed already have native support no scripts or anything because the f2fs lines have been added too the fstab. So all you need to do is format cache and data in twrp and your done.
Click to expand...
Click to collapse
Those ROMs probably use a kernel which has already been patched for F2FS and compiled in-line with the ROM.
Same goes for my SkyHigh kernel, but compiled on its own. All you need to do is format your relevant ROM partitions via script or supported F2FS TWRP. No difference to method except having to flash the kernel separately.
UpInTheAir said:
Those ROMs probably use a kernel which has already been patched for F2FS and compiled in-line with the ROM.
Same goes for my SkyHigh kernel, but compiled on its own. All you need to do is format your relevant ROM partitions via script or supported F2FS TWRP. No difference to method except having to flash the kernel separately.
Click to expand...
Click to collapse
Yep they include my deathly kernel which has f2fs, but without that fstab changes it wont boot on aosp if you convert it unless the tab s is different
deadman96385 said:
Yep they include my deathly kernel which has f2fs, but without that fstab changes it wont boot on aosp if you convert it unless the tab s is different
Click to expand...
Click to collapse
It's the same (similar) ramdisk fstab changes for Samsung based kernel as well, not just source. Edit: As I said, all you need to do to actual "ROM" is just format the relevant partitions.
The Unlegacy-Android ProjectIntroduction
Unlegacy-Android started out as the OMAP4-AOSP Project. It was created in late 2015 in order to maintain a clean and organized place for pure AOSP support for various OMAP4 devices, such as the Galaxy Nexus and the Samsung Galaxy Tab 2 series. Over time this evolved to support more than just these devices, but still maintains its roots of supporting "legacy" devices that no longer receive "official" updates: hence Unlegacy-Android was born.
This organization's goal is not to create feature packed ROMs, but to create a base ROM in such a way that custom ROM developers can easily adapt the changes. We're good at (properly) fixing compatibility issues between newer Android versions and older devices, among other core things. The "bells and whistles" like themes we leave to others.
The first public build here had something exclusive for the Galaxy Nexus, yet unseen on any other OMAP4 device: all RAM carveouts reserved for Ducati (the multimedia subsystem of OMAP4, responsible for hardware-accelerated video decoding, encoding and camera functionality) have been switched over to CMA.
A few words for those who see CMA for the first time:
The Contiguous Memory Allocator (CMA) makes it possible for device drivers to allocate big contiguous chunks of memory after the system has booted.
The main difference from the similar frameworks is the fact that CMA allows to transparently reuse memory region reserved for the big chunk allocation as a system memory, so no memory is wasted when no big chunk is allocated. Once the alloc request is issued, the framework will migrate system pages to create a required big chunk of physically contiguous memory.
Click to expand...
Click to collapse
This means that a total of 996 MB physical memory is available to the system, while keeping Ducati fully working - this is a huge step forward, coming from the 694 MB available in the last factory image released by Google (Android 4.3). This gives the OS access to an additional 300MB of RAM.
While CMA was just recently implemented for this device, thanks to one of our developers (let's just call him Luden), it's quite stable: even under heavy memory pressure, the system manages to free up the required memory in order to start up Ducati and launch the requested multimedia functionality in a few seconds at most.
Installation
For Marshmallow (6.0) and below, It's important that /system needs to be unmounted before installing the ROM - some recoveries tend to leave it mounted after performing operations on it.
If you're planning to install GApps, be sure to read the second post!
Aside from these, installation and upgrading is no different than on other ROMs.
Problems
While we weren't able reproduce any CMA-related problems, hidden ones can still arise. In most cases, these problems will be either lost Ducati functionality (no multimedia capabilities) until rebooting, or a kernel panic (hard reboot) - upon noticing any of these, be sure to grab a logcat/dmesg and/or last_kmsg and send it to us (preferably by attaching it to a post in this thread).
Other than that, these are bugs we're aware of in the current build:
- The RIL on LTE devices (toro, toroplus) isn't fully working; calls and texts should be OK, but expect no data.
- Sound pops can be observed, mostly when using touch sounds (this is being investigated)
- Some exotic video formats or camera modes might not be perfect - if you notice any artifacts or green spots (the issue that happened in the past), report the details in this thread
- Inverted colors mode not working
- Tricky connection to some 5 GHz Wi-Fi networks
- SELinux is in Permissive mode (this isn't a problem for most people, just mentioned it here as extra information)
If you notice anything else, be sure to report it in this thread. While we're kind of busy, we usually read the thread and acknowledge the bug reports, even if I don't reply directly to them.
Downloads
See: http://builds.unlegacy-android.org.
As usual, feedback is appreciated
Want to support development? You can consider donating, we've spent countless of hours with this
XDA:DevDB Information
Unlegacy Android Project, ROM for the Samsung Galaxy Nexus
Contributors
Ziyan, MWisBest, Android-Andi
Source Code: https://github.com/Unlegacy-Android/
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
Version Information
Status: Stable
Created 2016-03-12
Last Updated 2017-04-07
GApps
If you want to install GApps, we recommend Open GApps Nano or BaNkS GApps.
An important note: as this is a pure AOSP ROM, installing GApps tends to be problematic: in order to try to avoid installation issues, be sure to install GApps immediately after installing the ROM, before booting the system for the first time. After the initial bootup finished, be sure to go into Settings -> Apps, and grant every permission to every Google application - most importantly, Google Play services.
In the case of an upgrade, be sure to re-install the GApps package, as upgrading wipes /system. You shouldn't need to re-set the permissions afterwards.
siealex said:
One more note. DO NOT set up your Google account until you grant all permissions, otherwise you will be stuck on the initial setup.
Click to expand...
Click to collapse
Rooting
You can flash either the latest SuperSU or OpenSource SuperUser to get rooted.
Incredible work! Thank you to ALL the volunteer developers for making this FREE and OPEN SOURCE progress possible! The code is free, but your time is not! Thank you!!!
Out of curiosity, is aosp_mm_tuna_2016-03-12 running DDK1.9 or DDK1.8? I feel like it's 1.9 from your mention of recording artifacts, but I'm not an android developer, so I can't tell.
I'm running this right now, and it's awesome. Marshmallow in general seems to have much better performance than Lollipop on our device. I do miss some custom kernel flags, but I'm sure that'll come with time.
@Ziyan Which recovery do you recommend ?
DRM services not working means also Netflix doesn't work?
PythonNut said:
Out of curiosity, is aosp_mm_tuna_2016-03-12 running DDK1.9 or DDK1.8? I feel like it's 1.9 from your mention of recording artifacts, but I'm not an android developer, so I can't tell.
Click to expand...
Click to collapse
DDK 1.9 of course
Master94ga said:
@Ziyan Which recovery do you recommend ?
Click to expand...
Click to collapse
The latest TWRP should be fine. I might have not mentioned it in the OP, but the ROM supports F2FS as well.
Master94ga said:
DRM services not working means also Netflix doesn't work?
Click to expand...
Click to collapse
Possibly.
Ziyan said:
DDK 1.9 of course
The latest TWRP should be fine. I might have not mentioned it in the OP, but the ROM supports F2FS as well.
Possibly.
Click to expand...
Click to collapse
Thanks, 3.0 unofficial or your last recovery?
You are a god!
I'm downloading and will be testing this, I'm super excited about this work.
EDIT: So, first thing I've noticed is that the phone is struggling with the configuration in the first boot. Either in the "checking connection" or in the "just a sec..." loading frame, it freezes and doesn't get past it. Is it because of google play services?
diogofd8 said:
So, first thing I've noticed is that the phone is struggling with the configuration in the first boot. Either in the "checking connection" or in the "just a sec..." loading frame, it freezes and doesn't get past it. Is it because of google play services?
Click to expand...
Click to collapse
Yes Google Play Services can mess it up - I don't recall how, but I managed to press a skip button or something to easily get past it when it started looping. I guess we should add a mini how-to to the OP about it, as I really don't want to hack the framework for this.
Yep, I'm stuck in "just a sec..."
Edit: I restarted the Phone and now it works.
Netflix works too
Big thanks to @Ziyan and all OMAP4 dev for all your contribution so far ! I'll test this immediately [emoji106]
Sent from my Galaxy Nexus using Tapatalk
Ah, another thing!
When I flash the rom .zip file with all the partitions in f2fs, it auto changes to ext4 and installs. Maybe I'm being noob using TWRP so I'll say what I did here:
1) Full wipe
2) Convert system to f2fs, convert data to f2fs, convert cache to f2fs
3) Adb push rom zip file
4) Flash it
5) Check partition format, it's all on ext4
diogofd8 said:
Ah, another thing!
When I flash the rom .zip file with all the partitions in f2fs, it auto changes to ext4 and installs. Maybe I'm being noob using TWRP so I'll say what I did here:
1) Full wipe
2) Convert system to f2fs, convert data to f2fs, convert cache to f2fs
3) Adb push rom zip file
4) Flash it
5) Check partition format, it's all on ext4
Click to expand...
Click to collapse
There are a couple things going on here. The system ROM is an ext4 image, so it doesn't matter what you format it to, because it'll always become whatever is in the image.
Furthermore, only /data benefits from being F2FS, but it's not you fault for not knowing this because it wasn't mentioned in the documentation!
The other thing is that I don't know of a TWRP build that isn't buggy. When I tried to format to F2FS, it didn't work because my particular version of TWRP had a bug. So maybe your /data format failed for the same reason. I personally do not know what version of TWRP will reliably work for this. But this is a discussion for the TWRP thread.
2) Convert system to f2fs
Click to expand...
Click to collapse
Don't do this! F2FS is not supported on /system.
Wifi is extremely slow.
I can't do anything.
Google Play store can't install apps.
vipelp said:
Wifi is extremely slow.
I can't do anything.
Google Play store can't install apps.
Click to expand...
Click to collapse
Wifi works perfectly fine here ....with 2.4ghz
you using 5ghz or 2.4 ghz ?
I already tried both and it doesn't matter.
Browser times out opening google.com.
Play store doesn't load images and can't download apps
Wifi automatically disconnects....
rohitchouhan07 said:
Wifi works perfectly fine here ....with 2.4ghz
you using 5ghz or 2.4 ghz ?
Click to expand...
Click to collapse
WiFi working fine for me on 5GHz as well.
To other people: when this ROM boots, you may see the Google splash screen, then the screen will go black, and the device will act like it has died. It hasn't. Just give it a minute and the regular Android boot animation will appear.
OK i'm trying a reflash now. Complete wipe.
For me all work correctly, no problem with google play store or wifi
Hello everybody
Currently my system partition has 2113 MB (it is default size), I have CM 13.0 installed with OpenGapps Pico package on it and only 988 MB is used so it's means that 1125 MB is free. I wonder if it is a good idea to resize this partition to e.g 1113 MB and shift all free 1000 MB to data partition? What's your opinion? Does anyone tried this?
best regards,
The question is "can it be done"? Usually resizing partitions is quite difficult and may brick your device.
hmmm... I didn't think about it like that. I thought that I can resize as I want but I have to keep big enough to put ROM on in.