24 replies to this topic

[gac]

I've noticed that the GApps packages are updated every so often, should Iflash these onto my CM6.0.2 handset when they're released? I'm guessing that these packages are updated whenever Google Apps are updated so that people who are new to CM can always start with the latest available versions, but what about existing users? Can I flash the latest GApps package and get the latest .apk files into /system and free up space on /data, or am I misunderstanding how these packages work and interact?

[nnnoooooo]

Yes, you can flash newer google apps packages, they will overwrite any existing gapps package apps you have flashed.

If you mean flashing gapps instead of downloading updated gapps apps through the market, this might be a little tricky since I think downloaded apps (data folder) take priority over system apps (system folder, flashed), even if the system ones are newer. You'd have to delete the offending apps, then flash the replacements.

However, that said, this'll condemn you to a life of reflashing gapps on a constant basis. If what you really want is more space for downloading, use rom manager to partition your sd card, then install darktremor a2sd from xda-developers forum. It allows you to fully install apps to your sd instead of only partially. I have, ah, 113 apps installed at the moment, lots of room to spare, too!

Edit: for some perspective!

Size - Used - Avail. - % Free - Mount As
145.0M 98.6M 46.4M 68% /system
197.6M 122.1M 75.5M 62% /data
456.7M 267.7M 164.7M 62% /sd-ext

That last one is my sd card partition, the one with 113 apps installed at present. Data partition is still being used for cache, etc.

If you can hold off, apparently this is a baked-in feature for a near-future CM release... So I've heard.

My app list: http://www.appbrain....-the-htc-desire

Edited by nawoa, 19 October 2010 - 06:40 AM.

[gac]

I did wonder about the priorities, whether it was fixed that anything on the user-updatable parts of the ROM automatically "wins" because that would be the correct thing to do in 99% of cases (i.e. stock ROMs where you can't easily change /system apps, users who haven't rooted/flashed, that sort of thing) or whether versions were compared as each .apk is versioned and the highest version wins.

I don't really *need* the space, I'm down to about 107mb of my 147mb standard /data partition used after I threw out a handful of things I don't use, but I'm concious of this inherent limit and the fact that I might hit it at some point. I haven't looked too much into Apps2SD stuff as I'm somewhat confused by the different versions (CM6 has support for the standard Google system offered in Froyo I believe, then there's Apps2SD+, DarkTremor, etc). If DarkTremor is the one that's going to be included in future Cyanogens then I may well give that one a try as I think I'll be sticking to this ROM for a while, the only other ROM I've used and liked was OpenDesire but I dunno whether AdamG is developing or not atm, to my knowledge he's so far "quit" the ROM scene three times before re-appearing again straight away, so long-term I don't think OpenDesire is a sustainable ROM with just one developer, I feel a lot safer with CM with a view to making my phone usable for as long as possible even when it's been dropped by HTC.

[Kali-]

for now the only way to live without old school a2sd on Desire is going s-off with alpharev then install their hboot variant with n1 partition layout, it give u 203MB free after a fresh install (u have to use a recent nightlies) and with google a2sd u have a lot of space for your app

[gac]

I was just looking at the Alpharev stuff, but I don't think I need any of the S-off features really. I'm not doing my own Android development (just installing other peoples ROMs), and I'm not that short of space right now but just thinking that if I do some of this stuff now I won't suddenly find all my space gone in the future. I'm actually at 118mb used right now, so about 80% of my application space used according to Adao File Manager.

I assume that if I install Alpharev, I'll need to reinstall my ROM as all my partitions will be wiped? Can I do this with Nandroid (as I understand it Nandroid just works on a file by file basis, anything backed up from /system will just be restored to /system even if this is on a different device, different size, etc)?

[Kali-]

Require S-OFF (alpharev) and stock Clockworkmod/AmonRA recovery flashed on phone (unrevoked)

 1) Boot into Recovery
 2) Nandroid Backup
 3) Reoot into Fastboot: 
 * adb reboot bootloader
 * or manually with vol down
 4) Flash Alpharev N1 mod hboot (download from http://alpharev.nl and verify md5 checksum)
 * fastboot flash hboot bravo_alphaspl-n1table.img
 5) Reboot into Recovery
 6) Restore Nandroid
 7) Wipe Cache (not data)
 8) Fix system dalvik cache position:
 * adb shell
 * mount /system
 * sed -i /dalvik.vm.dexopt-data-only=1/d /system/build.prop
 * umount /system
 9) cleanup old cache files:
 * adb shell
 * mount /data
 * rm /data/dalvik-cache/system*
 * umount /data
10) Reboot

[gac]

Thanks for the instructions, I might give that a try tonight if I can sort out adb running on my laptop (had a lot of issues with the SDK and bootloader drivers in the past as I'm running x64)

edit - just to confirm...

I should already have the standard Alpharev bootloader flashed (with S-off) and ClockwordMod flashed to my phone, not fakeflash? Then I do the backup and flash the already S-off bootloader with a second S-off version with different partition layouts? Is that correct?

Edited by gac, 19 October 2010 - 02:27 PM.

[nnnoooooo]

There's a complete tutorial posted on xda, I'd go by it if I were you. Worked great for me.

[Glotzeulor]

Thanks Kali- ! Alpharev N1 hboot mod flashed fine. Finally more space on my desire

[gac]

Well, this morning with a quiet half hour at work, I've unrEVOked my Desire for a permanent flash of ClockworkMod 2.5.0.7, and also installed the Alpharev HBOOT bootloader (standard one, then when I confirmed that was working, the Nexus One version). One problem is that I missed the key press after step 5 so I didn't get chance to restore my Nandroid backup, however I didn't seem to need one and CM6 booted up perfectly happily. Just for piece of mind I've gone back and restored my Nandroid anyway to avoid problems (last thing I want would be partition boundaries being moved and a piece of flash ROM which did belong to /system now providing gibberish blocks in /data or similar).

According to Adao File Manager my Applications "folder" is now using 80mb out of 197mb (40%), I don't know where the other ~38Mb of stuff has gone (was 118 used before I did this) but I guess that was probably the dalvik-cache data which has now been moved to /cache? Either way, it's done now so I should (probably) never hit the limit and I don't need to mess around with Apps2SD at all, thanks for the advice Kali

Edited by gac, 20 October 2010 - 07:59 AM.

[nnnoooooo]

Kali, when you said a recent nightly is required, is that to mean that CM will auto-detect altered partition sizes in the future? Or am I way off base?

[Kali-]

installer detect /cache size, if is too small /system cache will be forced to /data

[marcink]

how much internal memory do you have after flushing n1table?
i only have like 73mb free after moving apps on sd (froyo style). hboot shows me that n1table is flushed, i went through kali's instructions but still 73mb.

[ngkwdaniel]

1) Boot into Recovery
2) Nandroid Backup
3) Reoot into Fastboot
4) Flash Alpharev N1 mod hboot
5) Reboot into Recovery
6) Restore Nandroid
7) Wipe Cache (not data)
8) Fix system dalvik cache position:
* adb shell
* mount /system
* sed -i /dalvik.vm.dexopt-data-only=1/d /system/build.prop
* umount /system
9) Reboot
10) After system boot, cleanup duplicated cache files
* adb shell
* for file in $(ls /cache/dalvik-cache/); do rm /data/dalvik-cache/$file; done;


For

Fix system dalvik cache position:
* adb shell
* mount /system
* sed -i /dalvik.vm.dexopt-data-only=1/d /system/build.prop
* umount /system

After system boot, cleanup duplicated cache files
* adb shell
* for file in $(ls /cache/dalvik-cache/); do rm /data/dalvik-cache/$file; done;[/quote]


Where should I do those steps in recovery or terminal? sorry I a new user. Just in case I'm using ClockWorkMod Recovery.

[mister_wavey]

Those instructions you ask about use the adb tool you get with the android development kit. Download that, and set it up. Google provides plenty of info out there for doing it on windows, linux and mac.

[ngkwdaniel]

I have them installed. To be on the safe side I should be typing those stuff in a command prompt?

[Glotzeulor]

ngkwdaniel, on 30 October 2010 - 10:02 AM, said:

I have them installed. To be on the safe side I should be typing those stuff in a command prompt?

Yes. you do this stuff via adb.

[elmaco]

Sorry, nOOb question again:

How do I do the steps 3, 4 and 5? When I boot in recovery mode, I navigate to the Fastboot, but then what? I also read in the wiki that I could manually type the fastboot command, but it's not clear to me how it should be written for this specific file.

Any help appreciated!

[elmaco]

Never mind, I finally found out (and learned a little bit more about what I'm doing...) Cool stuff! Now I have 120Mb free to install!

[chippy]

I think you're meant to get about 200mb free aren't you? I have around 120mb free on a fresh install of CM6 even with the stock partition tables. Are you sure it worked?