Jump to content

[ROM] CM7 Liquid (kang) 1.2.18 -CM7RC1-


Recommended Posts

Guest the red blue blur
Posted (edited)
just to know, also DATA to sd is supported with this a2sd:

Program Data Commands:

----------------------------------------------------

datasd

Moves /data/data to the SD card.

nodata

Restores /data/data to the internal storage.

okay okay, try it.

tried by myself. thought that it will be laggy (FC, reboots) like on previos versions, but ITS NOT!

happy)

btw, in 1.2.8 in a2sd.hlp there were no strings about data2sd, so i didnt knew... sry

Edited by the red blue blur
Guest The Duke of Hazard
Posted
anyone using chompsms did notice that led notification doesn't work? it happens on 1.2.6 also, i don't know about stock messaging since i don't use it :D

Try to use gosms, for me it works perfectly and no problem with the ledlights. I always used chomp till I found gosms!!it's amazing and in HD

a2sd cachesd worked like a charm for me

+1

Posted

Strange :D

Compcache 18% is OK, Compcache 26% has terrible battery drain :D

Posted

Having issues with data-connectivity.

It seems to crash pretty soon after bootup.

How do I fetch logs?

Posted

# a2sd datasd

a2sd datasd

[ ] GREP: Using ROM Busybox.

[!] REBOOT: Using Darktremor Busybox.

[ ] FDISK: Using ROM Busybox.

[ ] CAT: Using ROM Busybox.

[ ] MKDIR: Using ROM Busybox.

[ ] RMDIR: Using ROM Busybox.

[ ] CHMOD: Using ROM Busybox.

[ ] MOUNT: Using ROM Busybox.

[ ] UMOUNT: Using ROM Busybox.

[ ] CP: Using ROM Busybox.

[ ] RM: Using ROM Busybox.

[ ] MV: Using ROM Busybox.

[ ] LN: Using ROM Busybox.

[ ] MORE: Using ROM Busybox.

[ ] MKNOD: Using ROM Busybox.

[ ] AWK: Using ROM Busybox.

[ ] SLEEP: Using ROM Busybox.

[ ] SYNC: Using ROM Busybox.

[ ] TEE: Using ROM Busybox.

__ _____

| \ |

| | |

|__/ | Darktremor Apps2SD 2.7.5.3 Beta 4a (2011-01-30)

[-] Checkpoint 1: Check for SD Card Fix and Implement.

[!] Read Ahead Buffer is greater than threshold.

Threshold is: 128

Current setting is: 128

[!] No changes will be made.

[-] Checkpoint 2: Run Dalvik Heap Program (if exists).

[-] Checkpoint 3: Run Set Low Memory Killer Program (if exists).

[-] Checkpoint 4: Determine Mount Point.

[-] Checkpoint 5: Set Parameter Variables.

[ ] Startup Boot Sequence

[ ] GetProp Command = /system/bin/toolbox getprop

[ ] SetProp Command = /system/bin/toolbox setprop

[ ] Mount Point = /sd-ext

[-] Checkpoint 6: Insert CyanogenMod patch.

[-] Checkpoint 7: Complete Dalvik Cache Move (if applicable).

[-] Checkpoint 8: Resetting Dalvik Cache Partition

[-] Checkpoint 9: Switching Davlik Cache to Cache Partition (if applicable)

[ ] Mounting /data/dalvik-cache

[ ] Mounting Dalvik-Cache to /cache partition successful.

[-] Checkpoint 10: Checking for existence of command parameter

[-] Checkpoint 11: Check for a2sd help command

[-] Checkpoint 12: Check for a2sd check command

[-] Checkpoint 13: Display version information.

[ ] Starting Darktremor Apps2SD Version 2.7.5.3 Beta 4a

[-] Checkpoint 14: Check for filesystem support.

[ ] Listing /proc/filesystems

nodev sysfs

nodev rootfs

nodev bdev

nodev proc

nodev cgroup

nodev debugfs

nodev sockfs

nodev pipefs

nodev anon_inodefs

nodev tmpfs

nodev inotifyfs

nodev devpts

ext2

nodev ramfs

vfat

nodev fuse

fuseblk

nodev fusectl

yaffs

yaffs2

[-] Checkpoint 15: Mount partition.

[ ] Directory Listing of /dev/block

brw------- 1 root root 7, 0 Feb 20 23:35 /dev/block/loop0

brw------- 1 root root 7, 1 Feb 20 23:35 /dev/block/loop1

brw------- 1 root root 7, 2 Feb 20 23:35 /dev/block/loop2

brw------- 1 root root 7, 3 Feb 20 23:35 /dev/block/loop3

brw------- 1 root root 7, 4 Feb 20 23:35 /dev/block/loop4

brw------- 1 root root 7, 5 Feb 20 23:35 /dev/block/loop5

brw------- 1 root root 7, 6 Feb 20 23:35 /dev/block/loop6

brw------- 1 root root 7, 7 Feb 20 23:35 /dev/block/loop7

brw------- 1 root root 179, 0 Feb 20 23:35 /dev/block/mmcblk0

brw------- 1 root root 179, 1 Feb 20 23:35 /dev/block/mmcblk0p1

brw------- 1 root root 179, 2 Feb 20 23:35 /dev/block/mmcblk0p2

brw------- 1 root root 179, 3 Feb 20 23:35 /dev/block/mmcblk0p3

brw------- 1 root root 31, 0 Feb 20 23:35 /dev/block/mtdblock0

brw------- 1 root root 31, 1 Feb 20 23:35 /dev/block/mtdblock1

brw------- 1 root root 31, 10 Feb 20 23:35 /dev/block/mtdblock10

brw------- 1 root root 31, 2 Feb 20 23:35 /dev/block/mtdblock2

brw------- 1 root root 31, 3 Feb 20 23:35 /dev/block/mtdblock3

brw------- 1 root root 31, 4 Feb 20 23:35 /dev/block/mtdblock4

brw------- 1 root root 31, 5 Feb 20 23:35 /dev/block/mtdblock5

brw------- 1 root root 31, 6 Feb 20 23:35 /dev/block/mtdblock6

brw------- 1 root root 31, 7 Feb 20 23:35 /dev/block/mtdblock7

brw------- 1 root root 31, 8 Feb 20 23:35 /dev/block/mtdblock8

brw------- 1 root root 31, 9 Feb 20 23:35 /dev/block/mtdblock9

brw------- 1 root root 1, 0 Feb 20 23:35 /dev/block/ram0

brw------- 1 root root 1, 1 Feb 20 23:35 /dev/block/ram1

brw------- 1 root root 1, 2 Feb 20 23:35 /dev/block/ram2

brw------- 1 root root 1, 3 Feb 20 23:35 /dev/block/ram3

brw------- 1 root root 1, 4 Feb 20 23:35 /dev/block/ram4

brw------- 1 root root 1, 5 Feb 20 23:35 /dev/block/ram5

brw------- 1 root root 1, 6 Feb 20 23:35 /dev/block/ram6

brw------- 1 root root 1, 7 Feb 20 23:35 /dev/block/ram7

/dev/block/platform:

drwxr-xr-x 2 root root 120 Feb 20 23:35 msm_sdcc.1

/dev/block/vold:

brw-rw---- 1 root root 179, 0 Feb 20 23:35 179:0

lrwxrwxrwx 1 root root 25 Feb 20 23:35 179:1 -> /dev/block/vol

d/179:3_bck

brw-rw---- 1 root root 179, 1 Feb 20 23:36 179:1_bck

brw-rw---- 1 root root 179, 2 Feb 20 23:35 179:2

lrwxrwxrwx 1 root root 25 Feb 20 23:35 179:3 -> /dev/block/vol

d/179:1_bck

brw-rw---- 1 root root 179, 3 Feb 20 23:35 179:3_bck

[ ] Listing of partitions on /dev/block/mmcblk0

Disk /dev/block/mmcblk0: 8017 MB, 8017412096 bytes

4 heads, 16 sectors/track, 244672 cylinders

Units = cylinders of 64 * 512 = 32768 bytes

Device Boot Start End Blocks Id System

/dev/block/mmcblk0p1 1 196797 6297448+ b Win95 FAT32

Partition 1 does not end on cylinder boundary

/dev/block/mmcblk0p2 196797 235871 1250372 83 Linux

Partition 2 does not end on cylinder boundary

/dev/block/mmcblk0p3 235871 244672 281652 82 Linux swap

Partition 3 does not end on cylinder boundary

[ ] EXT partition found at /dev/block/mmcblk0p2.

[ ] Checking volume /dev/block/mmcblk0p2.

e2fsck 1.41.6 (30-May-2009)

/dev/block/mmcblk0p2 is mounted.

WARNING!!! Running e2fsck on a mounted filesystem may cause

SEVERE filesystem damage.

Do you really want to continue (y/n)?

GUYS HELP, what should I do?? Is it safe??

Posted (edited)
# a2sd datasd

a2sd datasd

[ ] GREP: Using ROM Busybox.

[!] REBOOT: Using Darktremor Busybox.

[ ] FDISK: Using ROM Busybox.

[ ] CAT: Using ROM Busybox.

[ ] MKDIR: Using ROM Busybox.

[ ] RMDIR: Using ROM Busybox.

[ ] CHMOD: Using ROM Busybox.

[ ] MOUNT: Using ROM Busybox.

[ ] UMOUNT: Using ROM Busybox.

[ ] CP: Using ROM Busybox.

[ ] RM: Using ROM Busybox.

[ ] MV: Using ROM Busybox.

[ ] LN: Using ROM Busybox.

[ ] MORE: Using ROM Busybox.

[ ] MKNOD: Using ROM Busybox.

[ ] AWK: Using ROM Busybox.

[ ] SLEEP: Using ROM Busybox.

[ ] SYNC: Using ROM Busybox.

[ ] TEE: Using ROM Busybox.

__ _____

| \ |

| | |

|__/ | Darktremor Apps2SD 2.7.5.3 Beta 4a (2011-01-30)

[-] Checkpoint 1: Check for SD Card Fix and Implement.

[!] Read Ahead Buffer is greater than threshold.

Threshold is: 128

Current setting is: 128

[!] No changes will be made.

[-] Checkpoint 2: Run Dalvik Heap Program (if exists).

[-] Checkpoint 3: Run Set Low Memory Killer Program (if exists).

[-] Checkpoint 4: Determine Mount Point.

[-] Checkpoint 5: Set Parameter Variables.

[ ] Startup Boot Sequence

[ ] GetProp Command = /system/bin/toolbox getprop

[ ] SetProp Command = /system/bin/toolbox setprop

[ ] Mount Point = /sd-ext

[-] Checkpoint 6: Insert CyanogenMod patch.

[-] Checkpoint 7: Complete Dalvik Cache Move (if applicable).

[-] Checkpoint 8: Resetting Dalvik Cache Partition

[-] Checkpoint 9: Switching Davlik Cache to Cache Partition (if applicable)

[ ] Mounting /data/dalvik-cache

[ ] Mounting Dalvik-Cache to /cache partition successful.

[-] Checkpoint 10: Checking for existence of command parameter

[-] Checkpoint 11: Check for a2sd help command

[-] Checkpoint 12: Check for a2sd check command

[-] Checkpoint 13: Display version information.

[ ] Starting Darktremor Apps2SD Version 2.7.5.3 Beta 4a

[-] Checkpoint 14: Check for filesystem support.

[ ] Listing /proc/filesystems

nodev sysfs

nodev rootfs

nodev bdev

nodev proc

nodev cgroup

nodev debugfs

nodev sockfs

nodev pipefs

nodev anon_inodefs

nodev tmpfs

nodev inotifyfs

nodev devpts

ext2

nodev ramfs

vfat

nodev fuse

fuseblk

nodev fusectl

yaffs

yaffs2

[-] Checkpoint 15: Mount partition.

[ ] Directory Listing of /dev/block

brw------- 1 root root 7, 0 Feb 20 23:35 /dev/block/loop0

brw------- 1 root root 7, 1 Feb 20 23:35 /dev/block/loop1

brw------- 1 root root 7, 2 Feb 20 23:35 /dev/block/loop2

brw------- 1 root root 7, 3 Feb 20 23:35 /dev/block/loop3

brw------- 1 root root 7, 4 Feb 20 23:35 /dev/block/loop4

brw------- 1 root root 7, 5 Feb 20 23:35 /dev/block/loop5

brw------- 1 root root 7, 6 Feb 20 23:35 /dev/block/loop6

brw------- 1 root root 7, 7 Feb 20 23:35 /dev/block/loop7

brw------- 1 root root 179, 0 Feb 20 23:35 /dev/block/mmcblk0

brw------- 1 root root 179, 1 Feb 20 23:35 /dev/block/mmcblk0p1

brw------- 1 root root 179, 2 Feb 20 23:35 /dev/block/mmcblk0p2

brw------- 1 root root 179, 3 Feb 20 23:35 /dev/block/mmcblk0p3

brw------- 1 root root 31, 0 Feb 20 23:35 /dev/block/mtdblock0

brw------- 1 root root 31, 1 Feb 20 23:35 /dev/block/mtdblock1

brw------- 1 root root 31, 10 Feb 20 23:35 /dev/block/mtdblock10

brw------- 1 root root 31, 2 Feb 20 23:35 /dev/block/mtdblock2

brw------- 1 root root 31, 3 Feb 20 23:35 /dev/block/mtdblock3

brw------- 1 root root 31, 4 Feb 20 23:35 /dev/block/mtdblock4

brw------- 1 root root 31, 5 Feb 20 23:35 /dev/block/mtdblock5

brw------- 1 root root 31, 6 Feb 20 23:35 /dev/block/mtdblock6

brw------- 1 root root 31, 7 Feb 20 23:35 /dev/block/mtdblock7

brw------- 1 root root 31, 8 Feb 20 23:35 /dev/block/mtdblock8

brw------- 1 root root 31, 9 Feb 20 23:35 /dev/block/mtdblock9

brw------- 1 root root 1, 0 Feb 20 23:35 /dev/block/ram0

brw------- 1 root root 1, 1 Feb 20 23:35 /dev/block/ram1

brw------- 1 root root 1, 2 Feb 20 23:35 /dev/block/ram2

brw------- 1 root root 1, 3 Feb 20 23:35 /dev/block/ram3

brw------- 1 root root 1, 4 Feb 20 23:35 /dev/block/ram4

brw------- 1 root root 1, 5 Feb 20 23:35 /dev/block/ram5

brw------- 1 root root 1, 6 Feb 20 23:35 /dev/block/ram6

brw------- 1 root root 1, 7 Feb 20 23:35 /dev/block/ram7

/dev/block/platform:

drwxr-xr-x 2 root root 120 Feb 20 23:35 msm_sdcc.1

/dev/block/vold:

brw-rw---- 1 root root 179, 0 Feb 20 23:35 179:0

lrwxrwxrwx 1 root root 25 Feb 20 23:35 179:1 -> /dev/block/vol

d/179:3_bck

brw-rw---- 1 root root 179, 1 Feb 20 23:36 179:1_bck

brw-rw---- 1 root root 179, 2 Feb 20 23:35 179:2

lrwxrwxrwx 1 root root 25 Feb 20 23:35 179:3 -> /dev/block/vol

d/179:1_bck

brw-rw---- 1 root root 179, 3 Feb 20 23:35 179:3_bck

[ ] Listing of partitions on /dev/block/mmcblk0

Disk /dev/block/mmcblk0: 8017 MB, 8017412096 bytes

4 heads, 16 sectors/track, 244672 cylinders

Units = cylinders of 64 * 512 = 32768 bytes

Device Boot Start End Blocks Id System

/dev/block/mmcblk0p1 1 196797 6297448+ b Win95 FAT32

Partition 1 does not end on cylinder boundary

/dev/block/mmcblk0p2 196797 235871 1250372 83 Linux

Partition 2 does not end on cylinder boundary

/dev/block/mmcblk0p3 235871 244672 281652 82 Linux swap

Partition 3 does not end on cylinder boundary

[ ] EXT partition found at /dev/block/mmcblk0p2.

[ ] Checking volume /dev/block/mmcblk0p2.

e2fsck 1.41.6 (30-May-2009)

/dev/block/mmcblk0p2 is mounted.

WARNING!!! Running e2fsck on a mounted filesystem may cause

SEVERE filesystem damage.

Do you really want to continue (y/n)?

GUYS HELP, what should I do?? Is it safe??

for the record, to move dalvik to ext2 I used command

a2sd cachepart

edit: I moved data to ext2.. everything is ok, I restore all my app, but when I rebooted my phone there was the beginning settings screen with the droid to touch.. and even touching it didn't goes on.. any solution?

Edited by gnlcp
Guest ranieri55
Posted

bluetooth handsfree don't work...

if I get a call the ringtone works, the second call, the ringer does not work and I have to reboot the phone...

sigic mobil maps 10 don't work...

solutions???

Guest koudelka
Posted

I tried using 2g with data off this night (6h sleep), and battery usage was only 1% :D

sleep.png

Guest fragmat
Posted
some users has problem with loosing data connection randomly, or after call (seems mostly for 2g mode)

I have this problem!

Maybe need to do patch, which will enable and disable fly mode every 15-20 minutes?

-Battery's life

+permanent Internet connection

Guest Peshkoff
Posted
I tried using 2g with data off this night (6h sleep), and battery usage was only 1% :D

sleep.png

Can you try to make some calls in 2G mode and see if you have problem with data connection?

Guest koudelka
Posted
Can you try to make some calls in 2G mode and see if you have problem with data connection?

yes, i have the same problem with losing data connection after call (although not randomly). actually just receiving call without answering will make it loose data (disable/enable data with powerwidget and it works again)

Posted (edited)
I tried using 2g with data off this night (6h sleep), and battery usage was only 1%

not sure that acers rom have same or better caracteristic. I think straight function is the best. Great job, guys!

Edited by tmp_do
Posted

Would anyone give me a short explanation (or give a link to a manual) about the whole ext2/3/4, compcache, a2sd, ... stuff? Sorry for this vague question but I'm quite confused at the moment.

So far, I was using LCR-F 2.0 in combination with the 2.2 acer bin. And of course, I was able to move apps to sd. And a week ago, I installed this great rom :-)

Are there partitions on my sd card? Or does the standard apps2sd work without an extra partition? Can I increase performance by creating some partitions for caching or something like that? What do you recommend to move on sd? And very important: How? :D

Thanks in advance for any help on this!

Posted
yes, i have the same problem with losing data connection after call (although not randomly). actually just receiving call without answering will make it loose data (disable/enable data with powerwidget and it works again)

problem solving hwen we go to apn settings and close it. seems phone manager loose apn settings after call. we just need reread it aftomatically :D

Guest mattdauntless
Posted

"CM7-RC1-Liquid-kang_v1.2.18_FULL_ed3" is stuffed up for me. took forever to boot then kept forcing close of every app.

i flashed over "CM7-RC1-Liquid-kang_v1.2.18_FULL"

did i need to wipe or anything before hand?

Guest Peshkoff
Posted
problem solving hwen we go to apn settings and close it. seems phone manager loose apn settings after call. we just need reread it aftomatically :D

any chance for fix? everything else is perfect =)

Posted
bluetooth handsfree don't work...

if I get a call the ringtone works, the second call, the ringer does not work and I have to reboot the phone...

sigic mobil maps 10 don't work...

solutions???

OMG, why even with command cachesdreset I have bootloop?? what's the problem? :S

Posted
anyone using chompsms did notice that led notification doesn't work? it happens on 1.2.6 also, i don't know about stock messaging since i don't use it :)

auto solved ^^'

green led is the mail led, blue is the missed call led but both a visible only if the screen is off :D

that's ok :D

Posted

Hi guys,

does the audio fix work well also for the latest update?

On my liquid ring volume is very very low even if I pushed it high.

Guest L0cu7us
Posted
bluetooth handsfree don't work...

if I get a call the ringtone works, the second call, the ringer does not work and I have to reboot the phone...

sigic mobil maps 10 don't work...

solutions???

just tested, no problem for me, the phone ring always as expected

Posted
just tested, no problem for me, the phone ring always as expected

hi, what's the difference between

a2sd cachesd

and a2sd cachepart?

if I get cachesd or cachesdreset the phone bootloops.. with cachepart don't..

Guest the red blue blur
Posted
hi, what's the difference between

a2sd cachesd

and a2sd cachepart?

if I get cachesd or cachesdreset the phone bootloops.. with cachepart don't..

Dalvik Cache Commands:

-------------------------------------------------- 

cachesd

  Moves Dalvik cache files to the ext2/ext3/ext4

  partition on your secure digital card. Creates

  Dalvik Cache to SD flag.


  File created: /data/.dalvikcacahe

  File removed: /data/.dcpartition


cachesdreset

  Performs the same function as cachesd, plus 

  erases the contents of Dalvik-Cache, forcing

  a rebuild on reboot.


  File created: /data/.dalvikcache

  File removed: /data/.dcpartition


cachepart

  Moves Dalvik cache files to the /cache partition

  in your phone.  Creates Dalvik Cache to Cache

  Partition flag.


  File created: /data/.dcpartition

  File removed: /data/.dalvikcache


cachepartreset

  Performs the same function as cachepart, plus

  erases the contents of Dalvik-Cache, forcing

  a rebuild on reboot.


  File created: /data/.dcpartition

  File removed: /data/.dalvikcache


nocache

  Moves Dalvik cache files to the internal phone

  storage.  Removes all Dalvik Cache flags.


  File removed: /data/.dcpartition

				/data/.dalvikcache


nocachereset

  Performs the same function as nocache, plus

  erases the contents of Dalvik-Cache, forcing

  a rebuild on reboot.


  File removed: /data/.dcpartition

				/data/.dalvikcache


resetcache

  Clears the dalvik cache and restarts phone.

Posted
Dalvik Cache Commands:

-------------------------------------------------- 

cachesd

  Moves Dalvik cache files to the ext2/ext3/ext4

  partition on your secure digital card. Creates

  Dalvik Cache to SD flag.


  File created: /data/.dalvikcacahe

  File removed: /data/.dcpartition


cachesdreset

  Performs the same function as cachesd, plus 

  erases the contents of Dalvik-Cache, forcing

  a rebuild on reboot.


  File created: /data/.dalvikcache

  File removed: /data/.dcpartition


cachepart

  Moves Dalvik cache files to the /cache partition

  in your phone.  Creates Dalvik Cache to Cache

  Partition flag.


  File created: /data/.dcpartition

  File removed: /data/.dalvikcache


cachepartreset

  Performs the same function as cachepart, plus

  erases the contents of Dalvik-Cache, forcing

  a rebuild on reboot.


  File created: /data/.dcpartition

  File removed: /data/.dalvikcache


nocache

  Moves Dalvik cache files to the internal phone

  storage.  Removes all Dalvik Cache flags.


  File removed: /data/.dcpartition

				/data/.dalvikcache


nocachereset

  Performs the same function as nocache, plus

  erases the contents of Dalvik-Cache, forcing

  a rebuild on reboot.


  File removed: /data/.dcpartition

				/data/.dalvikcache


resetcache

  Clears the dalvik cache and restarts phone.

I read it, but I'd like to know the difference between "partition" and "ext2". aren't they the same??

Guest the red blue blur
Posted (edited)
I read it, but I'd like to know the difference between "partition" and "ext2". aren't they the same??

cachepart

Moves Dalvik cache files to the /cache partition in your phone.

cachesd

Moves Dalvik cache files to the ext2/ext3/ext4 partition on your secure digital card.

and you dont see the differences???

Partition

EXT

Edited by the red blue blur

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.