Related
Modifying your nand adress space is okay, but that means that you have to modify your recovery along with the new rom each time you want to flash a new one.
What I propose is a new, flexibile approach (mainly for devs).
This is just a placeholder atm, but once I get some free time, I'll write about making compressed partitions (mainly static data) using squashfs (this has been done to a certain extent in the past for /system/lib/modules), but adding a bit of flexibility with unionfs/aufs.
The advantages are numerous, as are the uses.
For example: no need for complex apps2sd scripts!
Just mount your unionfs in /data and mount-bind that to another folder on the SD partition of your choice, and voila, apps2sd.
;]
This is of course synonymous to modifying the initrd, but a few lines of really simple script and it's done.
I have successfully tested that with /system, and have to further test with /data
I also have to test unionfs / aufs and make a choice. The ideal one without hesitation is aufs, which has practically superseeded unionfs, but there are a few stability issues involved in the 2.6.29 patches.
There are a few knowledgeable (real) devs around (dunno about any in the Hero forum though), so they probably know what I'm writing about.
You know who you are, so just drop in a post in this thread in case you you would have some ideas regarding the implementation.
n.b. I might have to rewrite that post. It's 01:40 and I'm really tired after my training and work.
placeholder and a note:
I have patched the reverse-patched kernel (desirec) for this.
I've run into trouble building the official htc-release 2.6.29 kernel with aufs.
>edit 201008181214<
I've successfully patched the tattoo 3G/Slide kernel to build a healthy Hero kernel with aufs.
It kindda hangs in the beginning, but runs just fine afterwards.
Prolly due to my OC settings.
>leak<
I am also playing around with kernel hacking, since I want to get 2.6.32 on the Hero. Epic wip.
good concept. I'm curious about performance - this would compress read/write on the fly, right? cpu resources etc, no problem there? no major lag issues in real use (startup doesn't matter much which you mentioned).
No I'm not a rom dev, but I AM a full time career developer.
by the way - I never found a workaround for the audio issue I had with your froyo rom. But it was a good project and I'm happy it's working well for you.
dkelley said:
good concept. I'm curious about performance - this would compress read/write on the fly, right? cpu resources etc, no problem there? no major lag issues in real use (startup doesn't matter much which you mentioned).
No I'm not a rom dev, but I AM a full time career developer.
by the way - I never found a workaround for the audio issue I had with your froyo rom. But it was a good project and I'm happy it's working well for you.
Click to expand...
Click to collapse
I am puzzled as well (audio issue).
You might've noticed that I'm no longer as active in the Hero forum.
I'm done with mdpi devices.
;]
In any case:
I have been working these past few days on optimising the kernel (I have based my work on the tattoo kernel) and aufs is working atm.
adwinp said:
placeholder and a note:
I have patched the reverse-patched kernel (desirec) for this.
I've run into trouble building the official htc-release 2.6.29 kernel with aufs.
Click to expand...
Click to collapse
you should use ninpo's repo, most uptodate kernel sources with a lot of fixes/patches included (http://github.com/Ninpo/kernel-hero/). aufs compilation worked at the first try.
I am also playing around with kernel hacking, since I want to get 2.6.32 on the Hero. Epic wip.
Click to expand...
Click to collapse
ninpo works with elemag on porting 2.6.34, they already made a lot in porting the board files.
btw nice idea with overlaying the file system, I think a lot of nand protected device use that already? (Desire, Wildfire..) http://forum.xda-developers.com/showthread.php?t=748025
unfortunately I have nearly no spare time to play around, but I'm very interested to see how the compressed squashfs affects cpu load and thus the overall phone performance.
found an old but still interesting thread, so even cyanogen experimented with it, maybe there are unresolved issues?
http://forum.xda-developers.com/showthread.php?t=523662
http://groups.google.com/group/andr...36603d429a/646a017892783e2b?#646a017892783e2b
As a matter of fact, Elemag PM'd me about his work.
To be frank, I am only playing around with this out of boredom, till I buy myself a hdpi device (I am waiting for the Glacier, hopefully)
;]
Thx for the links.
I can see that I was not the only one. lol
Despite a totally different approach, Maxisma's posts about a bigger data partition got me thinking, and ultimately reminded me of some work I did in the past with linux livecd's, which gave me the idea to try it on android.
To answer your question: decompressing squashfs is very fast, with little additional load/overhead (although, running a lot of running apps/widgets on our poor 528MHz/729MHz cpu in addition to a compressed system is generally a bad
idea)
I have another idea (from my linux administrating experience as well ;]) I would like to implement, but that would only work on newer devices, which have a lot of RAM.
My idea is to modify the init.rc in order to copy over the SYSTEM: partition ENTIRELY into RAM (essentially create a tmpfs mount point), do a switch_root, and let android take it from there.
This would of course also mean redefining the ANDROID_ROOT env variable to point to the new location.
A further modification would be to mount the WHOLE /system and /data into RAM (provided it fits and leaves enough for runtimes), and THEN further mount aufs in order to write to disk - or write to tmps, but, in the case of aufs, no further work is required, but in the case of tmpfs, you just have to #find all newer files than $uptime (taken from uptime, obviously), and recompress it to the original compressed fs.
That WORKS on a few linux systems I tried.
whew. a lot of ideas, but no device to test on.
;]
Now found this at the HTC Desire forum,but don`t tested
at the moment and don`t know if this works on Desire Z/G2
too!
It seems to be a good solution.
Features:
- Supports: Ext2, Ext3, Ext4 (and if kernel supports it: ) btrfs, ReiserFS
- Supports loop device as optional addon (as siberes data2sd)
- Flashable zip for many app2sd ROMs (no long setup required)
- It does a e2fsck (disk check) on every boot and creates a logfile on the sdcard (/sdcard/e2fscklog.txt)
- looks nice if you do a logcat on boot
- no "settings lost on reboot" bug like in my old or siberes script
- changes the scheduler for the sd-card and internal to noop for better performance on sd.
- Nandroid Backup of EXT2/3/4 external with AmonRa 2.0.0.1 or any clockwork recovery.
- Removes the common app2sd scripts on its own
More info and downloads:
DATA2whatever-Flashable All-in-one-data2sd-Solution v0.2e + v0.4 test
http://forum.xda-developers.com/showthread.php?t=867049
Hey mate..Thanks for the contribution..I just wanted to ask if there could be any bennefits to using this on a device as DZ..internal memory is more than suufcient and our nand I/O are pretty huge..Back when i had a HTC Desire i used this hack, but i am not sure if this could result in any kind of benefit..Please share ur knowledge/point of view i am interested.
Awesome I might test later... Although like what Chris said, The I/O speeds are pretty fast already
did anyone test this out
chris2busy said:
Hey mate..Thanks for the contribution..I just wanted to ask if there could be any bennefits to using this on a device as DZ..internal memory is more than suufcient and our nand I/O are pretty huge..Back when i had a HTC Desire i used this hack, but i am not sure if this could result in any kind of benefit..Please share ur knowledge/point of view i am interested.
Click to expand...
Click to collapse
Well if you have a class 6 or better sdcard then it will be faster then internal memory that's the only real benefit that I could think of!
Sent from my HTC Vision
Sorry to ask, but i really don't understand this..? what is this about? creating more virtual memory or what is it?
thx
I tried this and it kept causing a boot loop for me.... but I realized later that I think if I had mounted data and cache, like you do for GB gaps it probly would have worked.... just a suggestion. Also there is another all in one data/cache/dalvikcache to sd-ext option that I am testing now.... but I can't remeber were I found it. I think it is called dtappstosd or something like that. And is from the developer dark something...........
EDIT ok he is called dark tremer and it can be found by searching for apps2sd or datasd
EDIT: I should have said mount system/and data.....
Sent from my HTC Vision using XDA App
This is a good idea and good find however, since we have Darktremors a2ext for the G2 and it does data2sd I don't see a huge need for this.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
FAQ
What is apps2ext?
Code:
Apps2ext (previously called apps2SD) moved all user installed apps to a secondary ext partition on your sdcard.
This method had the advantage of being straight forward and simple, However, it had the drawback of being difficult to set up.
This method is no longer officially supported by CyanogenMod.
Please see the forum for device specific work-arounds if you really want apps2EXT on CyanogenMod.
Why did I include a apps2ext script to the rom?
Code:
Even though we have 1GB space of internal memory and a lot of the G2 users believe that is enough.
The more apps that are installed, the slower our phones can get after time.
Apps2ext takes all of that stress from our internal storage and diverts it to our sd-ext partition if there's any.
This results in our phones never have to worry about slowing down just because of the number of apps that we have installed.
What is swap?
Quoted from Cyanogenmod Wiki
Code:
Swap is, in short, virtual RAM. With swap, a small portion of the hard drive is set aside and used like RAM.
The computer will attempt to keep as much information as possible in RAM until the RAM is full.
At that point, the computer will begin moving inactive blocks of memory (called pages) to the hard disk, freeing up RAM for active processes.
If one of the pages on the hard disk needs to be accessed again, it will be moved back into RAM, and a different inactive page in RAM will be moved onto the hard disk ('swapped').
The trade off is disks and SD cards are considerably slower than physical RAM, so when something needs to be swapped, there is a noticeable performance hit.
Unlike traditional swap, Android's Memory Manager kills inactive processes to free up memory.
Android signals to the process, then the process will usually write out a small bit of specific information about its state (for example, Google Maps may write out the map view coordinates; Browser might write the URL of the page being viewed) and then the process exits.
When you next access that application, it is restarted: the application is loaded from storage, and retrieves the state information that it saved when it last closed.
In some applications, this makes it seem as if the application never closed at all.
This is not much different from traditional swap, except that Android apps are specially programed to write out very specific information, making Android's Memory Manager more efficient that swap.
Requirements:
- HTC G2 / HTC Desire Z
- S-OFF
- SDCard
Recommended Requirements:
*Only need this is you plan to use sd-ext and swap*
- Sd-ext partition at least 1024MB
- Swap partition at least 256MB
I DO NOT RECOMMEND USING ANY KIND OF SUPERWIPE
The rom has it's own built in wipe
Installing Process
- Backup your previous rom
- Repartition your sdcard ONLY if you want sd-ext and/or swap enabled
- Download the rom
- Wipe everything (data, cache, dalvik-cache, battery stats)
- Flash the rom
- Once flashing process is complete it will auto reboot!
Working
- Everything should be
Not Working
- Nothing, but tell me if anything is broken
Issues
- None at the moment
REGARDING ISSUES
Post the issues on http://pastebin.com/
- Please give me a logcat if you have an error, I can not help you if there's no logcat of the issue
Credits:
- HTC (Making HTC G2/Desire Z)
- Google (Android OS)
- Cyanogenmod (Source)
- SparksCo (Sd-ext, swap, kernel, cycling bootanimation, symlink scripts and sysctl tweaks)
- SparksCo (Kernel)
- Rambooster script (Credits to Darkky)
- Sdcard increase script (Credits to brainmaster)
If I missed anyone, let me know and I'll add you to here
Download link:
CM7-PyroMod-Stable-V2.3.7
checksums md5: I will provide one later
If you love my roms, donate and hit that thanks button!
Much appreciated!
Great stuff. Congrats on your first ROM! Just i dont think its ok that you have GAAPS installed already. Just a heads up.
Changelog
Version 2.3.7:
Rom
- Compiled from CM Source (Credits to SparksCo)
- Added kernel script (Credits to SparksCo)
- Added sysctl tweaks (Credits to SparksCo)
- Added cycling bootanimation (Credits to SparksCo)
- Working audio (Credits to SparksCo)
Theme
- Stock theme
- Stock font
- Stock audio tones
- Nice FOUR looking bootanimation (Credits to SparksCo)
Kernel
- Custom kernel (Credits to SparksCo)
EDIT: badass dude. Keep it up!
travisd4est said:
Any screenies??
Click to expand...
Click to collapse
Like I said in the OP, it's stock themed for right now
Okay blah I'm downloading and will give a spin this morning. I'll update you on what I think.
Update: This rom is pretty stable. Everything is working perfectly even the wireless tether. No FC's now its time to test the battery life. For just the begin this rom is great. Now its time for some themes! lol
313dash said:
Okay blah I'm downloading and will give a spin this morning. I'll update you on what I think.
Click to expand...
Click to collapse
Thanks, let me know what you think about it
Congrats on your first rom.
siulmagic said:
Congrats on your first rom.
Click to expand...
Click to collapse
Thanks, also thanks for helping me a little
Cause Myjbarr is being a complete douche about me forgetting to asking for his permission to use his rom as a base, he has to remember did he even ask cyanogen to use his rom as a base?
I don't think so
So for everyone, blame him for killing my rom
blahbl4hblah said:
Cause Myjbarr is being a complete douche about me forgetting to asking for his permission to use his rom as a base, he has to remember did he even ask cyanogen to use his rom as a base?
I don't think so
So for everyone, blame him for killing my rom
Click to expand...
Click to collapse
Lol...
Sent from my Desire HD using Tapatalk
blahbl4hblah said:
Cause Myjbarr is being a complete douche about me forgetting to asking for his permission to use his rom as a base, he has to remember did he even ask cyanogen to use his rom as a base?
I don't think so
So for everyone, blame him for killing my rom
Click to expand...
Click to collapse
Why do I always have to take the blame....??? Its never anyone elses fault. Its always my mistake. Shame on me, for not handing over my rom to you so you can call it yours. Also it "mjybarr" and not "myjbarr".
meXdroidMod GingerMex Ghost Chile TEST
mjybarr said:
Why do I always have to take the blame....??? Its never anyone elses fault. Its always my mistake. Shame on me, for not handing over my rom to you so you can call it yours. Also it "mjybarr" and not "myjbarr".
meXdroidMod GingerMex Ghost Chile TEST
Click to expand...
Click to collapse
blahbl4hblah said:
Cause Myjbarr is being a complete douche about me forgetting to asking for his permission to use his rom as a base, he has to remember did he even ask cyanogen to use his rom as a base?
I don't think so
So for everyone, blame him for killing my rom
Click to expand...
Click to collapse
why does it have to be a blame game at all, guys? Seriously, we are all big boys and girls. If someone makes a mistake, they need to own up to it and fix it, not blame anyone else. All that does is cause bad feelings in the community. You guys are both awesome, and I believe we can all get along in peace, and learn from and help one another, to the benefit of the whole community. Sound like a plan, guys?
mjybarr said:
Why do I always have to take the blame....??? Its never anyone elses fault. Its always my mistake. Shame on me, for not handing over my rom to you so you can call it yours. Also it "mjybarr" and not "myjbarr".
meXdroidMod GingerMex Ghost Chile TEST
Click to expand...
Click to collapse
Question... is your rom based off of CM? If it is, why shouldn't he be able to say the same thing you just did... The best way to get great roms is by sharing and expanding. That is why CM is so great, it is a contribution from many people!
Durkbeef said:
Question... is your rom based off of CM? If it is, why shouldn't he be able to say the same thing you just did... The best way to get great roms is by sharing and expanding. That is why CM is so great, it is a contribution from many people!
Click to expand...
Click to collapse
Yeah he's rom is based off of CM, but it doesn't matter anymore actually. I'm already working on a new release based off CM#17, along with the chance of better things
blahbl4hblah said:
Yeah he's rom is based off of CM, but it doesn't matter anymore actually. I'm already working on a new release based off CM#17, along with the chance of better things
Click to expand...
Click to collapse
sounds like a great plan good luck, bro, and cant wait to see where this will go from here. Still keeping the increased vm and apps2sd, I hope?
jmwils3 said:
sounds like a great plan good luck, bro, and cant wait to see where this will go from here. Still keeping the increased vm and apps2sd, I hope?
Click to expand...
Click to collapse
vm yes, but apps2sd of course but different haha
blahbl4hblah said:
vm yes, but apps2sd of course but different haha
Click to expand...
Click to collapse
ok, cool means one less zip to flash for CM, sounds like a definite plus to me.
jmwils3 said:
ok, cool means one less zip to flash for CM, sounds like a definite plus to me.
Click to expand...
Click to collapse
I'll leave it at this, you'll flash ONE thing and that's it
No need to worry about going into terminal for apps2sd
blahbl4hblah said:
I'll leave it at this, you'll flash ONE thing and that's it
No need to worry about going into terminal for apps2sd
Click to expand...
Click to collapse
wow... if that works, thatll be quite the feat indeed. We will still need to go into terminal emulator to move the apps though, i assume?
Background....
I used swapper2 and bricked my device.
Still I can't stop myself.
We all SGW I8150 users have low ram just 351MB.
Creating a startup script that adress swap partition on EXTERNAL SD card ( Preferred Class10) can be usefull for us to inrease our devices speed and responsiveness.
mkswap /dev/block/mmcblk1p2
The script can also include I/O tweaks for external SD card...
Inspired from: ( Don'nt flash this. It is not compatible. Also it targets main sd card.)
http://forum.cyanogenmod.com/topic/208-swap-enabledisable/page__st__10
http://www.igottadroid.com/ModMarket/Listings/Yank5551630095.html
V2:
Also another idea to swap SD0 to SD1 and the idea above.
Solved.
http://www.igottadroid.com/ModMarket/Listings/Yank5551630095.html
the best choice for now..try use turbo boost..it's not increase your ram,but it will free more ram..and your phone become smooth and responsive
Sent from my GT-I8150 using Tapatalk 4
i want to ask as i didn't understand
you provide us a script for expanding Ram or asking about a script to increase ram?
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.