the CM, AOSP etc ROMs getting better and better... - G2 General

One of the main reasons for using the stock ROMs is for stability etc. I know, I tried the earlier custom (CM, AOSP AOKP etc. ones) and there was always something not right... my reason for wanting to use the custom ROMs was simple... size, the average stock ROM is between 1gig and 1.6 gig (with some levels of de-bloating) and a full stock ROM is about 2gig. and given we (on the 16gig versions of the G2) only have about 10gig to 'play with' means that with your nandroid backup and titanium backup you'll be lucky to have 2 or 3gig for stuff. with the CM based or AOSP ROMs etc. you are looking at a ROM size of about 250mb incl. GApps... so you save a LOT of space (nandroids, titanium etc are way smaller) and now you have about 5gig odd available, much better.
I've tried Nameless and ProBam (SlimKat RC2 is still buggy on 802) and they are both rock solid and have better battery life than any stock ROM (I was getting 40 to 55 hrs with stock and I easily get to 70 odd hours now with the custom ROMs). So I really just wanted to say a massive thanks to the developers, for taking the time and effort to get the customs ROMs to where they are, its much appreciated!

Make donation.

Jostian said:
One of the main reasons for using the stock ROMs is for stability etc. I know, I tried the earlier custom (CM, AOSP AOKP etc. ones) and there was always something not right... my reason for wanting to use the custom ROMs was simple... size, the average stock ROM is between 1gig and 1.6 gig (with some levels of de-bloating) and a full stock ROM is about 2gig. and given we (on the 16gig versions of the G2) only have about 10gig to 'play with' means that with your nandroid backup and titanium backup you'll be lucky to have 2 or 3gig for stuff. with the CM based or AOSP ROMs etc. you are looking at a ROM size of about 250mb incl. GApps... so you save a LOT of space (nandroids, titanium etc are way smaller) and now you have about 5gig odd available, much better.
I've tried Nameless and ProBam (SlimKat RC2 is still buggy on 802) and they are both rock solid and have better battery life than any stock ROM (I was getting 40 to 55 hrs with stock and I easily get to 70 odd hours now with the custom ROMs). So I really just wanted to say a massive thanks to the developers, for taking the time and effort to get the customs ROMs to where they are, its much appreciated!
Click to expand...
Click to collapse
I don't know how you are gaining that much space? The system partition is a fixed size of about 2.7gig. You're not going to gain any of that back.
Good to know the ROMS are stable though... I've only just got the device and set it up the way I like it on stock.. I thought I'd give the custom roms some time to let the bugs get ironed out

baileyjr said:
I don't know how you are gaining that much space? The system partition is a fixed size of about 2.7gig. You're not going to gain any of that back.
Click to expand...
Click to collapse
Aside from dalvik cache, yeah, this.. You get no space back if /system is full or empty..

What about gaming on aosp Roms? I tried to play granny Smith and angry birds go and I couldn't get to the game play without It FCing
Sent from my LG-D800 using Tapatalk

baileyjr said:
I don't know how you are gaining that much space? The system partition is a fixed size of about 2.7gig. You're not going to gain any of that back.
Click to expand...
Click to collapse
khaytsus said:
Aside from dalvik cache, yeah, this.. You get no space back if /system is full or empty..
Click to expand...
Click to collapse
Not so much on the reading comprehension. Emphasis added.
"your nandroid backup and titanium backup you'll be lucky to have 2 or 3gig for stuff. with the CM based or AOSP ROMs etc. you are looking at a ROM size of about 250mb incl. GApps... so you save a LOT of space (nandroids, titanium etc are way smaller)"

Stock camera is the reason I stick to stock ROMs
Sent from my LG-D802 using xda app-developers app

nagel said:
Stock camera is the reason I stick to stock ROMs
Sent from my LG-D802 using xda app-developers app
Click to expand...
Click to collapse
You can use the LG camera app on AOSP ROMs.
Sent from my Nexus 5

on the 16gig model we have access to about 10gig (for our stuff), so if I do a nandroid with a stock rom your nandroid is quite big (mine was 2.7gig), and if you keep a copy of the rom on your phone for emergencies (which I do thats another 1.5 gig odd, depending on which stock rom you use), so together those 2 = about 4gig, if I use a custom rom like nameless or probam, the rom incl. Gapps is 220mb vs 1.5gig and my nandroid is just over 1gig vs 2.5gig, thus I have at least 2gig more available space using a custom rom. my titanium backups are around 30% smaller too depending on what you backup. so instead of having 2.5 gig available after I have my phone setup like I want I now have just under 5 gig available...makes a difference for sure.

Jostian said:
on the 16gig model we have access to about 10gig (for our stuff), so if I do a nandroid with a stock rom your nandroid is quite big (mine was 2.7gig), and if you keep a copy of the rom on your phone for emergencies (which I do thats another 1.5 gig odd, depending on which stock rom you use), so together those 2 = about 4gig, if I use a custom rom like nameless or probam, the rom incl. Gapps is 220mb vs 1.5gig and my nandroid is just over 1gig vs 2.5gig, thus I have at least 2gig more available space using a custom rom. my titanium backups are around 30% smaller too depending on what you backup. so instead of having 2.5 gig available after I have my phone setup like I want I now have just under 5 gig available...makes a difference for sure.
Click to expand...
Click to collapse
OK now I understand, its because you are keeping a copy of the system partition contents, as a nandroid, on the data partition :good:

baileyjr said:
OK now I understand, its because you are keeping a copy of the system partition contents, as a nandroid, on the data partition :good:
Click to expand...
Click to collapse
I guess there is no way (yet) to get access to any of the 'locked' 6 gig? is there another option(s) to minimize the loss of space, just curious in case someone is doing something better, more efficient in terms of available space, thanks

dallashigh said:
Not so much on the reading comprehension. Emphasis added.
"your nandroid backup and titanium backup you'll be lucky to have 2 or 3gig for stuff. with the CM based or AOSP ROMs etc. you are looking at a ROM size of about 250mb incl. GApps... so you save a LOT of space (nandroids, titanium etc are way smaller)"
Click to expand...
Click to collapse
Nandroid will be smaller yes. Tibu, not at all. Who backs up system apps in tibu?

Jostian said:
I guess there is no way (yet) to get access to any of the 'locked' 6 gig? is there another option(s) to minimize the loss of space, just curious in case someone is doing something better, more efficient in terms of available space, thanks
Click to expand...
Click to collapse
Some of that 6gig is lost in the formatting, 16Gb is the unformatted space. The system partition will remain the same size. However if you use something like "Nandroid manager" from the play store you can restore apps from the nandroid so you shouldn't need to back them up in TB, you could save space by just backing up the most recent data for your user apps
You do have the option to convert user apps to system apps in TB so you may want to play around with that. I'm "assuming" that will move them from the data partition to the system partition. Im not 100% on that but you could always just move one and check.... Having said that the apk's themselves are usually relatively small, its the data stored in Android/Data that usually account for most of the install size.
Few ideas there for you anyway, other that that your obviously better off with a 32gig version. After my apps installed, 1 Nandroid, some local music, and user apps backed up in TB I have approx 15gb free.

Here a comparison between CM10.2 and stock rom, I have about 2gb more free space for data.
I think partitions are dynamic and not fixed.

Related

Idea: ZFS for app2sd

In general:
The problem with app2SD, in general, is slow SD card speeds.
Solution:
Hybrid storage pools, using the inbuilt applicaiton directory as the cache and the microSD directory as the main storage.
blogs.sun.com/ahl/entry/shadow_of_hsp explains some of the conceptual stuff
Issues:
ZFS is only available via FUSE
...
Thoughts?
.milFox said:
In general:
The problem with app2SD, in general, is slow SD card speeds.
Solution:
Hybrid storage pools, using the inbuilt applicaiton directory as the cache and the microSD directory as the main storage.
blogs.sun.com/ahl/entry/shadow_of_hsp explains some of the conceptual stuff
Issues:
ZFS is only available via FUSE
...
Thoughts?
Click to expand...
Click to collapse
While I think having snapshot, replication, 100% consistency, and dedup capability would be the coolest thing on a phone, I think the ZIL would burn up the sd quicker and the resource utilization would eat battery and memory for the transactional caches to make it practical
.milFox said:
In general:
The problem with app2SD, in general, is slow SD card speeds.
Solution:
Hybrid storage pools, using the inbuilt applicaiton directory as the cache and the microSD directory as the main storage.
blogs.sun.com/ahl/entry/shadow_of_hsp explains some of the conceptual stuff
Issues:
ZFS is only available via FUSE
...
Thoughts?
Click to expand...
Click to collapse
My only thought is: "why?". I have every app I want installed and still have 102MB available. Given just how much more memory this has than the G1's of yore, I don't really see much of a reason for AppstoSD, especially since Google is releasing their own implementation *soon*.
I was already down to 29 Meg on my internal memory.
I'll be happy when Google implements a2sd. I can't see it being any different than what a2sd us doing though.
Just make sure you have a class 6 card.
Down to fairly minimal memory as well, here.
as to 'why' over conventional a2sd ... the in-built memory is faster than even a class 6 card. A hybrid zpool will allow the faster memory to cache the slower memory (normally, a hybrid zpool combines a SSD with a hard drive pool).
Ah, didn't realize people were having problems with it. Even so, Google has announced that they're working on it themselves and since it will be an actual part of the Android OS, rather than something hacked on, I imagine it'll be a better implementation that whatever we can do. I'll be waiting for that up and coming android release.
People who are running out of memory have way too many apps installed.
Anyway, I think you will find it very difficult to use the MTD block for this purpose.
miketaylor00 said:
People who are running out of memory have way too many apps installed.
Click to expand...
Click to collapse
I disagree, I only have 50 apps in total but have used 107Mb of my 196Mb used.
I lost 33Mb just flashing a theme.
Does anyone know if TA utility will work on the Nexus to move all the Caches?
Which memory are we talking about, primary or storage memory? If memory serves me correctly, the current os can only 256MB of primary memory but that will be increased to the full 512 in a later OTA update. I thought I saw some thread flying around here about that.
Amdathlonuk said:
I disagree, I only have 50 apps in total but have used 107Mb of my 196Mb used.
I lost 33Mb just flashing a theme.
Does anyone know if TA utility will work on the Nexus to move all the Caches?
Click to expand...
Click to collapse
You almost proved his point. 33MB is a ****ty size for a theme - get a better Themerto follow. Hell, most themes for Windows aren't that big.
-bZj
miketaylor00 said:
People who are running out of memory have way too many apps installed.
Anyway, I think you will find it very difficult to use the MTD block for this purpose.
Click to expand...
Click to collapse
How on earth can you possibly make this judgment? Have you ever hear of cache? What about app data? Not to tout my own app (see sig), but the reason I created it was because my myTouch, with all of its storage, would run very low the regular basis. Besides, I like to download apps, both free and paid. Why should I be limited? Personally, I never even came close to filling up my 500MB ext partition on my myTouch but could easily have 50-100MB of cache in just a few days. I think having a GB of internal would suffice. It would allow me to comfortably add as many apps as I please and at the same time, not think about cache and data on the daily basis. $575 and I'm still going to have to hack a2sd on to this. I hate that. I'd much rather use internal storage.
Personally, I'm all for it. If nothing else, it would be one hell of a proof of concept and would likely be useful especially to those who like to run their devices lean and fast. There are too many nice things to say about ZFS, so I'll just say this: it's only a matter of time and what better time than now?
But I don't think it would happen, for the same reason ZFS hasn't been ported to linux, incompatible licenses.
http://zfs-fuse.net/
Can we get the ball rolling on this?
dont worry boys
A king nexus build is coming VERY soon with OPTIONAL a2sd and kingnexus kernel #1
SOON!
kingklick said:
dont worry boys
A king nexus build is coming VERY soon with OPTIONAL a2sd and kingnexus kernel #1
SOON!
Click to expand...
Click to collapse
So what's the Kingnexus kernel have?
cyanogen said:
So what's the Kingnexus kernel have?
Click to expand...
Click to collapse
+1 .... and how does it relate to ZFS (y on earth) and apps2sd?
~enom~
lmao you pissed of cyanogen ! xD
miketaylor00 said:
People who are running out of memory have way too many apps installed.
Anyway, I think you will find it very difficult to use the MTD block for this purpose.
Click to expand...
Click to collapse
Ever hear of games? Seriously, making a statement like this is just plain ridiculous. Homerun Battle 3D is over 30MB in and of itself. Yes, believe it or not, people actually use their nearly $600 3.7" screen for something other than reading email, of which I do plenty. So yes, I hacked apps2sd onto my Cyan ROM and it runs beautifully. I can't even tell the difference between this and internal it's so smooth. By the time Google releases a viable apps2sd the N1 will be yesterday's news. Internal storage and capacitive buttons = fail on the N1. Otherwise, kick ass device.
I never touched the kernal on alpha7 just added a s.d>placeholder in system int.d folder got apps2sd and the rest was set. Did not know kernal was part.
Hope the kernal is good.

Enlarge CM7 partition

Is there a way to enlarge CM7's sdcard partition?
Since CM7 i dont use WebOS at all and dont plan to use it in the future.
Im hoping once everything is stable there will be a utility to blow out the while webos I really don't need to os's too
Sent from my Nexus S 4G using Tapatalk
http://forum.xda-developers.com/showthread.php?t=1312049
The sdcard partition is shared between the two OSes so you have access to everything from both. The WebOS boot partition is small and doesn't take up much space. And with 3.0.4 it seems to be running smoother without OC, and battery lasts longer (for me at least) than CM7.
Plus, from CyanogenMod original FAQ:
WILL YOU TELL ME HOW TO REMOVE WEBOS ENTIRELY?
Nah. We like WebOS. Furthermore, we don't recommend removing it. In future it may be needed for updates and such. Plus it doesn't take up much space, and you may find yourself wanting to give it a second look some day
I dont want to remove WebOS, i just want to have more space for CM7
Do you _really_ need the extra ~500MB?
I think WebOS is marvellous. If it wasn't for the fact that a couple of apps I want to use are only on Android, I'd stick with it, largely for the fact that the battery lasts for ages and the cards system is so nice to use.
Thats all 500MB? I've got the 16Gb version and the virtual sdcard has like 6-7Gb total space. Where did the rest go?

[Q] Q]does installing roms reduce internal storage capacity

i know that this is a rather foolish question.but i am 13 years old and i really want an answer.this is the only place i think to find an answer.
i know that our android phone has a specified amount of internal storage.part of it is for storing apk,datas etc.another part is for rom image and all all those stuff.what i want to know is when i am installing a new rom,is it actually overwritting the existing rom.or is it installed alongside it.cause my phone is getting slower each time i install a new custom rom in my htc hero.it has 600 mhz processor.but even angry birds lag in my phone but it works smooth on my nokia 5233 xpress music touch phone.both these games are are of similar size and have same graphics quality.
No the previous rom is over written or in most cases deleted when you carry out the full wipe/delete.
The hero is an old phone and as time goes on and software evolves ect.. it also become larger in size in most cases, if you are after speed, keep away from sense roms, and generally the older the rom the better in terms of performance/free space ect..
I used to own a hero and "eleinux" (i think his name is) had a good rom called speedmachine which was a pretty good rom for the hero while still having some ports from cyanogen, if you really want a sense rom the maybe look up villainrom as they are pretty good at gutting out all the crap within sense. You could always try over-clock your CPU as-well with setCPU or if you have a cyanogen based rom there is a function within there that will allow you to over-clock.
Other than that the hero is a very dated phone, might be time to consider a new one or newer one.
no. your internal memory never ever gets reduced. if u are rooted. u can use apps like setcpu to increase speed by overclocking(at the cost of lil battery life)
you can virtually increase yout internal memory by partition ur sdcard with ext4,3
Sent from my Nexus One using Tapatalk
...and I thought my phone was old.
Your phone is outdated, it will slow down with age. Be sure to fully wipe when flashing roms. At the minimum, wipe caches. If you haven't in a while, you should wipe everything before flashing your next rom. Really you should do a full wipe with each rom flash unless flashing an update.
Try out the V6 Supercharger script for a bit more speed, that should help some. You can buy used phones for less than $50 that are better than yours, like the Evo 4G.
I've heard good things about villianrom as well, so I did some searching for you and found this link
http://forum.xda-developers.com/showthread.php?t=654030
hope it helps, it's very important to do a full wipe of your phone before you install new roms.

[Q] Size of ROM:slots in Safestrap

If I just use one ekstra rom slot to the Stock:Slot
How big should this be? What is the benefits or drawbacks to a bigger Rom:slot to a smaller?
If I choose the maximum size of a Rom slot wich is 3Gb, does this mean that 3 GB is all I have to install my apps, store pictures and everything else?
Also wondering about the stock Rom slot?
Does this take up the up the same amout of space always? Even if choose rom slot one and do a system format on it?
I always leave the stock slot as-is and test out different ROMs on slot one as 1GB. Haven't seen any performance differences or otherwise problems with increased slot size. 1GB seems to be fine for every ROM I've tested.
Sent from my DROID RAZR using Tapatalk 2
mr.lysgaard said:
If I just use one ekstra rom slot to the Stock:Slot
How big should this be? What is the benefits or drawbacks to a bigger Rom:slot to a smaller?
If I choose the maximum size of a Rom slot wich is 3Gb, does this mean that 3 GB is all I have to install my apps, store pictures and everything else?
Also wondering about the stock Rom slot?
Does this take up the up the same amout of space always? Even if choose rom slot one and do a system format on it?
Click to expand...
Click to collapse
I'm not 100%, but I'm pretty sure its only for your apps and app data. You will lose approximately 3GB from your internal storage or whatever amount you chose.

CM7.2 issues/Recommendations for Daily Driver ROM

Well, due to unexpected turn of events, I am using an HTC Aria as my daily driver phone on Net10, S-OFF and currently running the last CM7.2 Nightly ROM with the included kernel (Max clock 768/Min 245, OnDemand and tried Interactive) and I have been getting daily reboots, not really bad but annoying. Any thoughts on cleaning up the reboots, is the Official Stable version better? I am running at 25 MB free consistently after moving everything to the SD card that can be moved, could this be part of the reboot problem?
Is there a better daily driver ROM, perhaps one with more internal storage free or one that uses the external SD as it's primary storage (acts as internal storage)? Thoughts on MIUI or something else? What is everyone who is still using the Aria using as their daily driver ROM?
I know this is very much a legacy device, but for the next few months at least I need to make this work fairly solid and I really don't like the stock ROM with all it's bloat
I'm not using my Aria anymore, but I gave mine to a friend, and it had the latest CM10 rom(not CM10.1) on it by WinSuk. So far it hasn't been giving him any problems. Maybe you should give CM7.2 Stable a shot before trying CM10 out though, since there are some bugs on CM10. Have you tried using Links2sd or moving the dalvik cache to the sd card for more storage space?
aster190 said:
I'm not using my Aria anymore, but I gave mine to a friend, and it had the latest CM10 rom(not CM10.1) on it by WinSuk. So far it hasn't been giving him any problems. Maybe you should give CM7.2 Stable a shot before trying CM10 out though, since there are some bugs on CM10. Have you tried using Links2sd or moving the dalvik cache to the sd card for more storage space?
Click to expand...
Click to collapse
I have been using DroidSail's App2SD thinking it was the same thing, but I am learning it is very different. I will look into that, thanks. I was short on time yesterday so tried to dirty flash back to CM 7.2 Stable, but it was rather... umm... unsuccessful... Had to nandroid back, when I get some more time this weekend I will probably try again with a clean flash, maybe CM10, and perhaps MIUI as well. Thanks again!
EDIT: Interesting, last night around 7pm I changed the Max Clock speed to 787 MHz instead of 768, and dropped an app I didn't need freeing up 15MB of space (maintaining 41MB free on average), much smoother operation of the phone all around and no reboots in almost 24 hours. Note sure if the extra space helped or changing the clock speed, but seems to make a difference. I would assume that 787 uses a slightly different bus speed than 768 rather than a multiplier change so that alone could make a huge difference if I was at the edge of what the HW could take.
Edit 2: Nvm... it still reboots, back down to 600 MHz max for now.
acejavelin said:
I have been using DroidSail's App2SD thinking it was the same thing, but I am learning it is very different. I will look into that, thanks. I was short on time yesterday so tried to dirty flash back to CM 7.2 Stable, but it was rather... umm... unsuccessful... Had to nandroid back, when I get some more time this weekend I will probably try again with a clean flash, maybe CM10, and perhaps MIUI as well. Thanks again!
EDIT: Interesting, last night around 7pm I changed the Max Clock speed to 787 MHz instead of 768, and dropped an app I didn't need freeing up 15MB of space (maintaining 41MB free on average), much smoother operation of the phone all around and no reboots in almost 24 hours. Note sure if the extra space helped or changing the clock speed, but seems to make a difference. I would assume that 787 uses a slightly different bus speed than 768 rather than a multiplier change so that alone could make a huge difference if I was at the edge of what the HW could take.
Edit 2: Nvm... it still reboots, back down to 600 MHz max for now.
Click to expand...
Click to collapse
I still use my aria as a media player, and keep it as a spare phone. CM9 and 10 were both nicely stable for me, but at this point you pretty much have to run an apps to ext partition solution due to the current size of apps and lack of internal space on the device. In any case, mine has always had random reboot issues if I overclock past 768, on any ROM.
I have CM10.1 on there now... but I can't get s2e to work with it (my old standby for apps to ext) and link 2sd seems to be misbehaving, or I don't know how to use it correctly. I'm going to go back to either cm10, or maybe a stock based froyo rom if I can track one down, just for the heck of it. What I want is attn1's liberated fr008.
Good luck.
Sent from my Optimus G using Tapatalk 4

Categories

Resources