Develop Bugs

CWM Porting Help [Completed]

I have a found a developer that is willing to help port CWM to this device. He doesn't have this device. He needs the following files.
UPDATE
Got everything we needed so far. Thanks to all that helped! Consider sending the developer utkanos a little something if this is useful to you.
Initial testing is done. He has posted the official release thread. Hope see some cool stuff soon.
Feel free to join #utkanos on freednode as a tester or watch the progress.
...and we have liftoff!
I got CWMR booting on the 927r and thus far it appears stable. Very early stages right now so I'm testing it deeply thanks to a helpful owner as we speak. More details as they come.
Click to expand...
Click to collapse
Hi.
I need the following:
1) A boot.img or zImage
2) A dump of /proc/partitions
3) A dump of /proc/emmc or /proc/mtd (if they exist)
4) A dump of the 'mount' command
Click to expand...
Click to collapse
You need to be rooted to dump the files and I am not rooted. So the faster we get these files, the faster CWM can be ported. Attach or link to the files in your post and thanks.

vil33 said:
I have a found a dev that is willing to help port CWM to this device. He doesn't have this device and isn't on xda as far as I know. He needs the follwing files.
You need to be rooted to dump the files and I am not rooted. So the faster we get these files, the faster CWM can be ported. Attach or link to the files in your post and thanks.
Click to expand...
Click to collapse
Here:
cat /proc/partitions
major minor #blocks name
7 0 12506 loop0
7 1 2111 loop1
7 2 5229 loop2
7 3 3150 loop3
179 0 7552000 mmcblk0
179 1 12288 mmcblk0p1
179 2 614400 mmcblk0p2
179 3 319488 mmcblk0p3
179 4 3932672 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 2097152 mmcblk0p6
179 7 16384 mmcblk0p7
259 0 5120 mmcblk0p8
259 1 8192 mmcblk0p9
259 2 8192 mmcblk0p10
259 3 524288 mmcblk0p11
179 8 7782400 mmcblk1
179 9 7781376 mmcblk1p1
254 0 12505 dm-0
254 1 2110 dm-1
254 2 5229 dm-2
254 3 3150 dm-3
/proc/emmc doesn't exist
cat /proc/mtd
dev: size erasesize name
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=111 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/usb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /app-cache tmpfs rw,relatime,size=8192k 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p2 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p1 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,journal_checksum,data=ordered 0 0
/dev/block/mmcblk0p6 /data ext4 rw,nosuid,nodev,noatime,barrier=1,journal_checksum,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p3 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/vold/179:4 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime
=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro,discard 0 0
/dev/block/vold/179:9 /mnt/sdcard/external_sd vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002
,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:9 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_
utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/external_sd/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/net.skyscanner.android.main-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,
iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/com.flightradar24free-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iochar
set=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-2 /mnt/asec/org.scummvm.scummvm-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharse
t=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-3 /mnt/asec/org.scummvm.scummvm.plugin.scumm-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=c
p437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

tcfx44 said:
Here:
Click to expand...
Click to collapse
Thanks for the quick response, I passed it on to the Dev and hopefully he can do this. Do you have the boot.img as well?

vil33 said:
Thanks for the quick response, I passed it on to the Dev and hopefully he can do this. Do you have the boot.img as well?
Click to expand...
Click to collapse
I'm still new to Android and cannot find boot.img. Can you help me with the location of the file?

tcfx44 said:
I'm still new to Android and cannot find boot.img. Can you help me with the location of the file?
Click to expand...
Click to collapse
okay, go ahead and laugh, i'm no dev or linux guy, but there is a boot.img file ready for download on the Rooting the captivate glide thread right? I believe it is on the step 2 of the process (with a link on CarrierIQ Free). When I download that file and extracted, I got boot.img in tar file. Can they use that?
I don't want to upload, unsure about it.

gabby131 said:
okay, go ahead and laugh, i'm no dev or linux guy, but there is a boot.img file ready for download on the Rooting the captivate glide thread right? I believe it is on the step 2 of the process (with a link on CarrierIQ Free). When I download that file and extracted, I got boot.img in tar file. Can they use that?
I don't want to upload, unsure about it.
Click to expand...
Click to collapse
Thanks I forgot about that. Sent him it and hopefully it's the right one.

It would be nice if your friend release CWM to prepare a guide on how he did it, I am learning myself, successfully compiled the kernel but I dont really understand the proccess for CWM, should it is included in the kernel like it is the case for a lot of samsung devices or should it be a recovery...
Thanks for the details

CarpeNoctem said:
It would be nice if your friend release CWM to prepare a guide on how he did it, I am learning myself, successfully compiled the kernel but I dont really understand the proccess for CWM, should it is included in the kernel like it is the case for a lot of samsung devices or should it be a recovery...
Thanks for the details
Click to expand...
Click to collapse
Hey you can meet him on the freenode irc network on channel #koush by the name utkanos, he's usually there 9-5 central. Also it would help if we had a rooted user to help the process out. He just emailed me that he wanted this:
Can you get into stock recovery and get me the recovery.log? Should be in cache or tmp.
Click to expand...
Click to collapse

Hi.
In addition to the recovery.log from stock recovery, I would like to see a build.prop (from system) please.
I do not post on XDA very much, usually over on rootzwiki or on freenode.

Here is the build.prop
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=GINGERBREAD
ro.build.display.id=GINGERBREAD.RUXKJ5
ro.build.version.incremental=RUXKJ5
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.5
ro.build.date=Fri Oct 14 15:36:02 KST 2011
ro.build.date.utc=1318574162
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEI-28
ro.build.tags=release-keys
ro.product.model=SAMSUNG-SGH-I927R
ro.product.brand=samsung
ro.product.name=SGH-I927R
ro.product.device=SGH-I927R
ro.product.board=SGH-I927R
ro.product.cpu.abi=armeabi-v7a
# Samsung Specific Properties
ro.build.PDA=I927RUXKJ5
ro.build.hidden_ver=I927RUXKJ5
ro.build.changelist=652095
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=CA
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=SGH-I927R
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=SGH-I927R-user 2.3.5 GINGERBREAD RUXKJ5 release-keys
ro.build.fingerprint=samsung/SGH-I927R/SGH-I927R:2.3.5/GINGERBREAD/RUXKJ5:user/release-keys
# Samsung Specific Properties
ro.build.PDA=I927RUXKJ5
ro.build.hidden_ver=I927RUXKJ5
ro.build.changelist=652095
ro.tether.denied=false
ro.flash.resolution=1080
# end build properties
ro.opengles.version = 131072
wifi.interface=eth0
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttys0
ro.sf.lcd_density=240
dalvik.vm.heapsize=64m
# Samsung USB default mode
persist.service.usb.setting=0
# Set Default Timezone as America/New_York
persist.sys.timezone=America/New_York
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.locationfeatures=1
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=2.3_r7
media.stagefright.enable-player=false
media.stagefright.enable-meta=false
media.stagefright.enable-scan=false
media.stagefright.enable-http=true
media.stagefright.enable-rtsp=false
dev.sfbootcomplete=0
ro.com.google.clientidbase=android-samsung
ro.com.google.clientidbase.ms=android-samsung
ro.com.google.clientidbase.am=android-samsung
ro.com.google.clientidbase.gmm=android-samsung
ro.com.google.clientidbase.yt=android-samsung
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.locationfeatures=1
keyguard.no_require_sim=true
ro.config.ringtone=S_Over_the_horizon.ogg
ro.config.notification_sound=01_Sherbet.ogg
ro.config.alarm_alert=Good_Morning.ogg
ro.config.media_sound=Media_preview_Touch_the_light.ogg
ro.monkey=0
ro.opengles.version=131072
ro.secdevenc=true
ro.wtldatapassword=true
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Here if the result of the cat proc/mounts
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=111 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/usb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /app-cache tmpfs rw,relatime,size=8192k 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p2 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p1 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,journal_checksum,data=ordered 0 0
/dev/block/mmcblk0p6 /data ext4 rw,nosuid,nodev,noatime,barrier=1,journal_checksum,data=ordered,noau
to_da_alloc,discard 0 0
/dev/block/mmcblk0p3 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0

Cheers for that
edit: I believe I have what I need now, thank you to those who provided the files for me. I will update when I have something tangible for you.

Well I have some bad news for you guys.
The stock kernel provided is bitwise EXACTLY the size of the partition that holds it, and I need to add about 500KB of space to make recovery work.
Thus, repacking the ramdisk with a hacked recovery isn't going to be possible unless the kernel image can get much smaller to accommodate.

utkanos said:
Well I have some bad news for you guys.
The stock kernel provided is bitwise EXACTLY the size of the partition that holds it, and I need to add about 500KB of space to make recovery work.
Thus, repacking the ramdisk with a hacked recovery isn't going to be possible unless the kernel image can get much smaller to accommodate.
Click to expand...
Click to collapse
Isn't it possible to resize the partitions ?
also this mean Samsung has no intention to release any other kernel/version of android or the kernel needs to remains always the same?

Has anyone tried the kernel from the KL1 build? CIQ should be removed from that (it came out a few days after the CIQ fiasco), which could provide the space we're missing...

Symmetric said:
Has anyone tried the kernel from the KL1 build? CIQ should be removed from that (it came out a few days after the CIQ fiasco), which could provide the space we're missing...
Click to expand...
Click to collapse
Thanks for the tip, I think I might have something worth testing if someone wants to hop into IRC
I am on freenode as utkanos in #koush

...and we have liftoff!
I got CWMR booting on the 927r and thus far it appears stable. Very early stages right now so I'm testing it deeply thanks to a helpful owner as we speak. More details as they come.

Symmetric said:
Has anyone tried the kernel from the KL1 build? CIQ should be removed from that (it came out a few days after the CIQ fiasco), which could provide the space we're missing...
Click to expand...
Click to collapse
Good call

Work beautifully achieved

Symmetric said:
Has anyone tried the kernel from the KL1 build? CIQ should be removed from that (it came out a few days after the CIQ fiasco), which could provide the space we're missing...
Click to expand...
Click to collapse
Hooray for me!
Let the games begin?

utkanos said:
...and we have liftoff!
I got CWMR booting on the 927r and thus far it appears stable. Very early stages right now so I'm testing it deeply thanks to a helpful owner as we speak. More details as they come.
Click to expand...
Click to collapse
Amazing work utkanos, now I can get my flash fix on my GF's phone! Thanks a million!

[Q] Dark Tremor?

Can someone explain what is the difference between DTa2sd and the built-in moving apps to SD?

DT A2SD opens up much more possibility. With a partitioned SD card and DT a2sd you can also run Dalvik Caches from SD, Control your swap settings (Given your kernel supports it), you can even symlink apps essential to system function. Regular apps2sd simply stores apps in a folder on your memory card.

I see ... thanks!
I've never used it ... what kind of partition scheme do I need on my SD card for it to work?

d0g said:
I see ... thanks!
I've never used it ... what kind of partition scheme do I need on my SD card for it to work?
Click to expand...
Click to collapse
here is an excelent post to formating your sdcard for use with dt a2sd. This is what i used and was very easy,
http://forum.xda-developers.com/showthread.php?t=1158993&highlight=partition+sd+card

I'm using Titanium Backup Pro ... which allows to move 'any' app to SD, and also Dalvik stuff ... is DT different?
And if I enable it, does it apply only to future installs, or is there a way to have it move current apps?

no.. it does however take a little work to move existing apps to the sd card. you must also download terminal emulator from the market. once you have dt a2sd flashed and terminal emulator installed open the terminal emulator and enter the following commands:
su{enter}
a2sd reinstall{enter}
cachesd{enter}
this will move all the apps you have already installed to your ext partition.
the downside to tibackup is that you must manually move your apps and a2sd moves them automatically when you download them.

dbenney said:
su{enter}
a2sd reinstall{enter}
cachesd{enter}
Click to expand...
Click to collapse
I tried this but got "[X] SD Card not mounted." (From adb on Mac.)
Do I need to mount the sd-ext first?
Also -- what will happen to all the apps which I moved to SD with Ti? Do I need to move those back to int for DT to move them to ext?
Thanks!

FWIW ... this is what a2sd info said:
Code:
sh-3.2# a2sd sysinfo
[ ] Apps2SD is launching...
__ _____
| \ |
| | |
|__/ | Darktremor Apps2SD 2.7.5.2 (2010-09-30)
[ ] GetProp Command = /system/bin/toolbox getprop
[ ] SetProp Command = /system/bin/toolbox setprop
[ ] Mount Point = /sd-ext
[ ] Starting Darktremor Apps2SD Version 2.7.5.2
[ ] Launching Apps2SD Start Program with sysinfo
[ ] Starting Darktremor Apps2SD in sysinfo mode
[ ] System Information:
[ ] Kernel Information:
Linux version 2.6.38.7-SavagedZen-2.2.1-CFS-HAVS+ ([email protected]) (gcc version 4.4.0 (GCC) ) #9 PREEMPT Thu Jun 23 09:16:14 CDT 2011
[ ] CPU Information:
Processor : ARMv7 Processor rev 2 (v7l)
BogoMIPS : 662.40
Features : swp half thumb fastmult vfp edsp thumbee neon vfpv3
CPU implementer : 0x51
CPU architecture: 7
CPU variant : 0x0
CPU part : 0x00f
CPU revision : 2
Hardware : supersonic
Revision : 0003
Serial : 0000000000000000
[ ] Memory:
/system/bin/starta2sd: line 366: i: command not found
MemTotal: 424236 kB
MemFree: 8260 kB
Buffers: 744 kB
Cached: 161140 kB
SwapCached: 0 kB
Active: 281628 kB
Inactive: 83584 kB
Active(anon): 203704 kB
Inactive(anon): 440 kB
Active(file): 77924 kB
Inactive(file): 83144 kB
Unevictable: 264 kB
Mlocked: 0 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Dirty: 0 kB
Writeback: 0 kB
AnonPages: 203600 kB
Mapped: 40444 kB
Shmem: 552 kB
Slab: 23868 kB
SReclaimable: 9408 kB
SUnreclaim: 14460 kB
KernelStack: 5632 kB
PageTables: 11576 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 212116 kB
Committed_AS: 1813656 kB
VmallocTotal: 450560 kB
VmallocUsed: 121740 kB
VmallocChunk: 296964 kB
[ ] Mounted Partition:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /app-cache tmpfs rw,relatime,size=49152k 0 0
/dev/block/mtdblock4 /system yaffs2 rw,relatime 0 0
/dev/block/mtdblock6 /data yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock5 /cache yaffs2 rw,nosuid,nodev,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0602,dmask=0602,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0602,dmask=0602,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/klye.plugin.iw-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/com.lastpass.lpdolphin-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-2 /mnt/asec/klye.plugin.en-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-3 /mnt/asec/com.onepassword.passwordmanager-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-4 /mnt/asec/com.jajah.mobile-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-5 /mnt/asec/com.ngc.fora-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-6 /mnt/asec/com.lexi.l.mm-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-7 /mnt/asec/com.evernote.skitch-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-8 /mnt/asec/com.ideomobile.hapoalim-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-9 /mnt/asec/com.appspot.swisscodemonkeys.apps-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-10 /mnt/asec/com.google.android.stardroid-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-11 /mnt/asec/com.americanexpress.android.acctsvcs.us-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-12 /mnt/asec/gbis.gbandroid-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-13 /mnt/asec/com.logmein.ignitionpro.android-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-14 /mnt/asec/com.noinnion.android.greader.reader-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-15 /mnt/asec/com.quoord.tapatalkxda.activity-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-16 /mnt/asec/com.google.android.apps.unveil-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-17 /mnt/asec/com.mint-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-18 /mnt/asec/com.lastpass.lpandroid-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-19 /mnt/asec/com.swype.android.installer-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-20 /mnt/asec/com.melodis.midomiMusicIdentifier-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-21 /mnt/asec/com.facebook.katana-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-22 /mnt/asec/com.imdb.mobile-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-23 /mnt/asec/com.google.android.apps.shopper-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-24 /mnt/asec/com.amazon.venezia-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-25 /mnt/asec/com.clov4r.android.nil-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-26 /mnt/asec/com.biggu.shopsavvy-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-27 /mnt/asec/com.jrummy.liberty.toolbox-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-28 /mnt/asec/com.google.android.apps.docs-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-29 /mnt/asec/com.evernote-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-30 /mnt/asec/com.yelp.android-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-31 /mnt/asec/com.intsig.camscanner-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-32 /mnt/asec/com.qo.android.am3-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-33 /mnt/asec/com.rainfrog.yoga-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-34 /mnt/asec/com.skype.raider-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-35 /mnt/asec/com.netflix.mediaclient-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
[ ] Valid Partitions:
nodev sysfs
nodev rootfs
nodev bdev
nodev proc
nodev cgroup
nodev tmpfs
nodev debugfs
nodev sockfs
nodev pipefs
nodev anon_inodefs
nodev devpts
ext2
ext3
ext4
nodev ramfs
vfat
nodev cifs
nodev fuse
fuseblk
nodev fusectl
yaffs
yaffs2
nodev mtd_inodefs
[ ] Swap Information:
: applet not found
cat: can't open '/proc/swaps': No such file or directory
cat: can't open '/proc/swaps': No such file or directory
[ ] Partition Information:
Filesystem Size Used Available Use% Mounted on
tmpfs 207.1M 44.0K 207.1M 0% /dev
tmpfs 207.1M 0 207.1M 0% /mnt/asec
tmpfs 207.1M 0 207.1M 0% /mnt/obb
tmpfs 48.0M 0 48.0M 0% /app-cache
/dev/block/mtdblock4 350.0M 176.2M 173.8M 50% /system
/dev/block/mtdblock6 427.6M 230.7M 196.9M 54% /data
/dev/block/mtdblock5 160.0M 1.5M 158.5M 1% /cache
/dev/block/vold/179:1
7.4G 5.7G 1.7G 77% /mnt/sdcard
/dev/block/vold/179:1
7.4G 5.7G 1.7G 77% /mnt/secure/asec
/dev/block/dm-0 2.0M 300.0K 1.7M 14% /mnt/asec/klye.plugin.iw-1
/dev/block/dm-1 4.1M 2.0M 2.0M 50% /mnt/asec/com.lastpass.lpdolphin-1
/dev/block/dm-2 2.0M 604.0K 1.4M 29% /mnt/asec/klye.plugin.en-1
/dev/block/dm-3 5.1M 3.1M 2.0M 61% /mnt/asec/com.onepassword.passwordmanager-1
/dev/block/dm-4 4.1M 2.3M 1.8M 56% /mnt/asec/com.jajah.mobile-1
/dev/block/dm-5 3.1M 1.2M 1.8M 40% /mnt/asec/com.ngc.fora-1
/dev/block/dm-6 2.0M 728.0K 1.3M 35% /mnt/asec/com.lexi.l.mm-1
/dev/block/dm-7 3.1M 1.5M 1.6M 49% /mnt/asec/com.evernote.skitch-1
/dev/block/dm-8 3.1M 1.9M 1.1M 63% /mnt/asec/com.ideomobile.hapoalim-1
/dev/block/dm-9 2.0M 904.0K 1.2M 43% /mnt/asec/com.appspot.swisscodemonkeys.apps-1
/dev/block/dm-10 4.1M 2.2M 1.9M 53% /mnt/asec/com.google.android.stardroid-1
/dev/block/dm-11 3.1M 1.7M 1.4M 55% /mnt/asec/com.americanexpress.android.acctsvcs.us-1
/dev/block/dm-12 3.1M 1.3M 1.8M 41% /mnt/asec/gbis.gbandroid-1
/dev/block/dm-13 4.1M 2.9M 1.2M 71% /mnt/asec/com.logmein.ignitionpro.android-1
/dev/block/dm-14 3.1M 1.5M 1.5M 50% /mnt/asec/com.noinnion.android.greader.reader-1
/dev/block/dm-15 5.1M 3.0M 2.0M 60% /mnt/asec/com.quoord.tapatalkxda.activity-1
/dev/block/dm-16 4.1M 2.5M 1.6M 61% /mnt/asec/com.google.android.apps.unveil-1
/dev/block/dm-17 3.1M 1.8M 1.2M 60% /mnt/asec/com.mint-1
/dev/block/dm-18 4.1M 2.1M 2.0M 52% /mnt/asec/com.lastpass.lpandroid-1
/dev/block/dm-19 2.0M 92.0K 1.9M 4% /mnt/asec/com.swype.android.installer-1
/dev/block/dm-20 5.1M 3.7M 1.3M 74% /mnt/asec/com.melodis.midomiMusicIdentifier-1
/dev/block/dm-21 5.1M 3.9M 1.1M 77% /mnt/asec/com.facebook.katana-1
/dev/block/dm-22 6.1M 4.2M 1.9M 69% /mnt/asec/com.imdb.mobile-1
/dev/block/dm-23 7.1M 5.5M 1.6M 78% /mnt/asec/com.google.android.apps.shopper-1
/dev/block/dm-24 5.1M 3.8M 1.3M 75% /mnt/asec/com.amazon.venezia-1
/dev/block/dm-25 9.1M 7.2M 2.0M 78% /mnt/asec/com.clov4r.android.nil-1
/dev/block/dm-26 7.1M 5.3M 1.8M 74% /mnt/asec/com.biggu.shopsavvy-1
/dev/block/dm-27 5.1M 3.6M 1.4M 71% /mnt/asec/com.jrummy.liberty.toolbox-1
/dev/block/dm-28 8.1M 6.2M 1.9M 76% /mnt/asec/com.google.android.apps.docs-1
/dev/block/dm-29 8.1M 6.9M 1.2M 85% /mnt/asec/com.evernote-1
/dev/block/dm-30 7.1M 5.7M 1.4M 80% /mnt/asec/com.yelp.android-1
/dev/block/dm-31 12.2M 10.6M 1.6M 87% /mnt/asec/com.intsig.camscanner-1
/dev/block/dm-32 11.2M 9.2M 2.0M 82% /mnt/asec/com.qo.android.am3-1
/dev/block/dm-33 20.3M 19.0M 1.3M 94% /mnt/asec/com.rainfrog.yoga-1
/dev/block/dm-34 16.2M 14.0M 2.2M 87% /mnt/asec/com.skype.raider-1
/dev/block/dm-35 23.3M 21.9M 1.4M 94% /mnt/asec/com.netflix.mediaclient-1
[ ] MTD Information:
dev: size erasesize name
mtd0: 00c00000 00020000 "wimax"
mtd1: 000a0000 00020000 "misc"
mtd2: 00500000 00020000 "recovery"
mtd3: 00280000 00020000 "boot"
mtd4: 15e00000 00020000 "system"
mtd5: 0a000000 00020000 "cache"
mtd6: 1aba0000 00020000 "userdata"
[ ] Phone Serial #: HT07CHLxxxxx
[ ] Bootloader Version: 0.79.0000
[ ] Radio Baseband: 2.15.00.04.08
[ ] Hardware ID: supersonic
[ ] Product Model: PC36100
[ ] Product Brand: htc_supersonic
[ ] Product Device: supersonic
[ ] Product Board: supersonic
[ ] Rom: 4.24.651.1 CL61076 release-keys
[ ] Base Rom Version:
[ ] Setting File System Ready property to 1.
sh-3.2#

d0g said:
I tried this but got "[X] SD Card not mounted." (From adb on Mac.)
Do I need to mount the sd-ext first?
Also -- what will happen to all the apps which I moved to SD with Ti? Do I need to move those back to int for DT to move them to ext?
Thanks!
Click to expand...
Click to collapse
that looks right.... did your phone restart after a2sd did its thing? also when you use terminal emulator... did you download it to your phone from the market? use terminal app on phone, not on computer, im sure you can do it that way but thats above me.
i would move the apps bsack to internal storage through ti.. you dont want multiple copies of stuff eating storage space.

I tried from Terminal on the phone (as su) and got this:
Code:
> a2sd reinstall (su)
[ ] Apps2SD is launching...
__ _____
| \ |
| | |
|__/ | Darktremor Apps2SD 2.7.5.2 (2010-09-30)
[ ] GetProp Command = /system/bin/toolbox getprop
[ ] SetProp Command = /system/bin/toolbox setprop
[ ] Mount Point = /sd-ext
[ ] Starting Darktremor Apps2SD Version 2.7.5.2
[ ] Launching Apps2SD Start Program with reinstall
[ ] Starting Darktremor Apps2SD in reinstall mode
[X] SD Card not mounted.
Cannot reinstall applications to SD card.
rm: cannot remove '/data/dta2sd.lg2': Permission denied
cp: cannot create '/data/dta2sd.lg2': File exists
rm: cannot remove '/data/dta2sd.lg1': Permission denied
cp: cannot create '/data/dta2sd.lg1': File exists
rm: cannot remove '/data/dta2sd.log': Permission denied
grep: /init.rc: Permission denied

OK, so I'm a bonehead.
Turns out I don't HAVE an ext partition!
(Didn't realize Ti moved stuff to a folder on FAT)
Sorry!

lol no problem. jsut follow the partition sdcard link i posted and you will be all good

One more question...
With dt installed, can I still have some apps internal? Or do they all go to SD?
CM7.2.1 / from xda app ]

[Q] how can I tell what type of EXT partition a ROM supports for a2sd?

I am trying to figure out what type of EXT partition I should be using. I created a 5GB EXT4 partition but when I goto my apps manager in settings it show that the apps are still on internal storage, and the ones that I can move to SD are showing that my storage is around 24GB.
The a2sd tool I am using is Darktremor Apps2SD 2.7.5.2. As per the installation instructions for the ROM I went into terminal emulator ran a2sd reinstall. But my apps still show that they are either installed on internal storage or on the 24GB partition.
I am using this ROM:
http://forum.xda-developers.com/showthread.php?t=2086163
Any help would be awesome. Thank you.

Okay first off everyone will tell you that 5 gig is a bit excessive and some say over 1 gig will cause issues. I run about 1.5 gig on mine with no issues. Second lookiing under settings will tell you nothing at all. Dt's script just tricks the os into thinking your sd-ext is part of the internal memory but does not show anything larger than stock under the app manager. A quick way to check is open up terminal and type "su" press enter and grant terminal superuser permissions. Then type a2sd sysinfo and it will tell you how much of each partion is used or if you titianum backup that will also show your sd-ext info.

Truth on size. I Upped mine to 2 GB and had nothing but issues. I just dropped back to 1.5 and it's a lot more stable

HipKat said:
Truth on size. I Upped mine to 2 GB and had nothing but issues. I just dropped back to 1.5 and it's a lot more stable
Click to expand...
Click to collapse
I have 3gb ext with no problems at all on 32gb class 10 card. It seems some people have problems and others don't.

Evilone69tmg said:
I have 3gb ext with no problems at all on 32gb class 10 card. It seems some people have problems and others don't.
Click to expand...
Click to collapse
I tried a new 16GB Class 10 today and it was a nightmare. Took it back for a Class 4 and no probs

HipKat said:
I tried a new 16GB Class 10 today and it was a nightmare. Took it back for a Class 4 and no probs
Click to expand...
Click to collapse
Interesting.
I use a 32GB Class 6 without problems.
Glad I didn't go for the Class 10.

9h0s7 said:
Interesting.
I use a 32GB Class 6 without problems.
Click to expand...
Click to collapse
I have a 16GB Class 10 and have used up to 2.5 GB sd-ext with no issues either. I currently have 512MB swap, 1.4GB sd-ext ext2, remainder fat32 and have no problems flashing any rom.

It could be because I use EXT4, that makes the Class 10 have problems, but I did some Googling and there are a lot of people with Class 10 Cards having Problems. One thing I forgot to do was add a Swap partition, but I'm still not sure if I really needed one or not

Cool, I will lower it down to around 1.4GB but how can I tell if the ROM I am using actually supports EXT4 I had already ran a2sd sysinfo and this is what it said is it supporting the EXT4 and swap partition?:
[ ] Apps2SD is launching...
__ _____
| \ |
| | |
|__/ | Darktremor Apps2SD 2.7.5.2 (2010-09-30)
[ ] GetProp Command = /system/bin/toolbox getprop
[ ] SetProp Command = /system/bin/toolbox setprop
[ ] Mount Point = /system/sd
[ ] Starting Darktremor Apps2SD Version 2.7.5.2
[ ] Launching Apps2SD Start Program with sysinfo
[ ] Starting Darktremor Apps2SD in sysinfo mode
[ ] System Information:
[ ] Kernel Information:
Linux version 2.6.38.8-BlackDome_TSP_v2.1 ([email protected]) (gcc version 4.4.3 (GCC) ) #3 PREEMPT Sat Feb 9 10:11:05 EST 2013
[ ] CPU Information:
Processor : ARMv7 Processor rev 2 (v7l)
BogoMIPS : 407.63
Features : swp half thumb fastmult vfp edsp thumbee neon vfpv3
CPU implementer : 0x51
CPU architecture: 7
CPU variant : 0x0
CPU part : 0x00f
CPU revision : 2
Hardware : supersonic
Revision : 0003
Serial : 0000000000000000
[ ] Memory:
/system/bin/starta2sd: line 366: i: command not found
MemTotal: 422800 kB
MemFree: 13240 kB
Buffers: 24944 kB
Cached: 53120 kB
SwapCached: 6804 kB
Active: 173752 kB
Inactive: 165252 kB
Active(anon): 128832 kB
Inactive(anon): 132740 kB
Active(file): 44920 kB
Inactive(file): 32512 kB
Unevictable: 328 kB
Mlocked: 0 kB
SwapTotal: 999976 kB
SwapFree: 979464 kB
Dirty: 0 kB
Writeback: 0 kB
AnonPages: 257332 kB
Mapped: 52664 kB
Shmem: 304 kB
Slab: 15832 kB
SReclaimable: 4976 kB
SUnreclaim: 10856 kB
KernelStack: 5664 kB
PageTables: 8872 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 1211376 kB
Committed_AS: 3991596 kB
VmallocTotal: 450560 kB
VmallocUsed: 120076 kB
VmallocChunk: 268292 kB
[ ] Mounted Partition:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
tmpfs /app-cache tmpfs rw,relatime,size=8192k 0 0
/dev/block/mtdblock4 /system yaffs2 ro,relatime 0 0
/dev/block/mtdblock6 /data yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock5 /cache yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mmcblk0p2 /system/sd ext4 rw,noatime,nodiratime,barrier=1,data=ordered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
[ ] Valid Partitions:
nodev sysfs
nodev rootfs
nodev bdev
nodev proc
nodev cgroup
nodev tmpfs
nodev debugfs
nodev sockfs
nodev pipefs
nodev anon_inodefs
nodev devpts
ext3
ext2
ext4
nodev ramfs
vfat
nodev cifs
nodev fuse
fuseblk
nodev fusectl
yaffs
yaffs2
nodev mtd_inodefs
[ ] Swap Information:
: applet not found
Filename Type Size Used Priority
/dev/block/mmcblk0p3 partition 999976 20512 -1
[ ] Partition Information:
Filesystem Size Used Available Use% Mounted on
tmpfs 206.4M 48.0K 206.4M 0% /dev
tmpfs 206.4M 0 206.4M 0% /mnt/asec
tmpfs 206.4M 0 206.4M 0% /mnt/obb
tmpfs 8.0M 0 8.0M 0% /app-cache
/dev/block/mtdblock4 350.0M 339.5M 10.5M 97% /system
/dev/block/mtdblock6 426.0M 144.3M 281.7M 34% /data
/dev/block/mtdblock5 160.0M 2.8M 157.2M 2% /cache
/dev/block/mmcblk0p2 4.7G 182.2M 4.3G 4% /system/sd
[ ] MTD Information:
dev: size erasesize name
mtd0: 00c00000 00040000 "wimax"
mtd1: 00100000 00040000 "misc"
mtd2: 00480000 00040000 "recovery"
mtd3: 00340000 00040000 "boot"
mtd4: 15e00000 00040000 "system"
mtd5: 0a000000 00040000 "cache"
mtd6: 1aa00000 00040000 "userdata"
[ ] Phone Serial #: HT114HL12974
[ ] Bootloader Version: 2.10.0001
[ ] Radio Baseband: 2.15.00.11.19
[ ] Hardware ID: supersonic
[ ] Product Model: X10
[ ] Product Brand: SonyEricsson_x10
[ ] Product Device: x10
[ ] Product Board: es209ra
[ ] Rom: 4.24.651.1 CL61076 release-keys
[ ] Base Rom Version:
[ ] Setting File System Ready property to 1.

Pretty much everything is good on EXT4. I use that with every ROM I Flash

Yes you are good with ext4 I cut and pasted the part you need to look for that way you know what is going on. Under valid partitions there is a whole list of things but there is only a couple of things that you need to worry about I have them in bold and underlined. Now support of ext2-4 is dependent on your kernel and all of the new kernels support ext4. You can see by what I have highlighted yours support all three. If it only supported ext2 then it would only show ext2 where I have it highlighted. If it supports ext3 then it will show ext2, ext3 but ext4 would not be in the list. Hope this helps you out.
[ ] Valid Partitions:
nodev sysfs
nodev rootfs
nodev bdev
nodev proc
nodev cgroup
nodev tmpfs
nodev debugfs
nodev sockfs
nodev pipefs
nodev anon_inodefs
nodev devpts
ext3
ext2
ext4
nodev ramfs
vfat
nodev cifs
nodev fuse
fuseblk
nodev fusectl
yaffs
yaffs2
nodev mtd_inodefs

So I should just resize it?

jlmancuso said:
Yes you are good with ext4 I cut and pasted the part you need to look for that way you know what is going on. Under valid partitions there is a whole list of things but there is only a couple of things that you need to worry about I have them in bold and underlined. Now support of ext2-4 is dependent on your kernel and all of the new kernels support ext4. You can see by what I have highlighted yours support all three. If it only supported ext2 then it would only show ext2 where I have it highlighted. If it supports ext3 then it will show ext2, ext3 but ext4 would not be in the list. Hope this helps you out.
[ ] Valid Partitions:
nodev sysfs
nodev rootfs
nodev bdev
nodev proc
nodev cgroup
nodev tmpfs
nodev debugfs
nodev sockfs
nodev pipefs
nodev anon_inodefs
nodev devpts
ext3
ext2
ext4
nodev ramfs
vfat
nodev cifs
nodev fuse
fuseblk
nodev fusectl
yaffs
yaffs2
nodev mtd_inodefs
Click to expand...
Click to collapse
Yes that is very helpful I wasn't sure how to interpret that information. I thought that maybe it was just telling me which partitions were valid as in not corrupted. Did not realize that it meant supported. Thank you. Would Swap be listed there if it was supported?

Yes but there are very few kernels that support swap. Also you see how it says nodev before some of the listed items those are supported but not present on your device.
Sent from my EVO 4G using xda app-developers app

jlmancuso said:
...Second lookiing under settings will tell you nothing at all. Dt's script just tricks the os into thinking your sd-ext is part of the internal memory but does not show anything larger than stock under the app manager...
Click to expand...
Click to collapse
So what you are saying here is that my apps are actually being moved to the ext4 partition by A2SD but when I look under settings that storage is't being represented? So the second tab there "On SD Card" has nothing to do with my ext4 that is the fat32 leftover bit after setting my partitions. So I don't need to ever select "Move to SD card" button in the App info because a2sd does it automagically?

Bingo! If you have a2sd installed you should never do the move to sd card option it can cause issues with your apps. Now if you have run the a2sd install or reinstall in the terminal window then you wont have to do anything else ever. When you install an app it goes to your sd-ext with no actions needed from you. As long as your internal memory stays over 100MB free everything will run great. There are options to move your DC and data to sd-ext but I only move the apps myself since the apps dont run anyways. They are transformed in the DC and run from there. If you move the DC to your sd-ext then it will slow down your phone because sd-ext is not as fast as your internal memory.

[4.4] CM 11.0 broken

Hello
I try to build cm 11, but Its broken.
My log is : http://pastebin.com/zakHeqW8
It stucks at samsung logo. I dont know what would fix it.
Anyone idea?

bubor said:
It stucks at samsung logo. I dont know what would fix it.
Anyone idea?
Click to expand...
Click to collapse
ther is something wrong with mount points
in linux is configurable in /etc/fstab but in android??
maybe is something with filesystem, do U add vfat module to image??

croolyc said:
ther is something wrong with mount points
in linux is configurable in /etc/fstab but in android??
maybe is something with filesystem, do U add vfat module to image??
Click to expand...
Click to collapse
you dont need sdcard0 or sdcard1 to boot, nor vfat.
All other fses are mounted.
Filesystem Size Used Free Blksize
/dev 361.2M 132.0K 361.1M 4096
/sys/fs/cgroup 361.2M 12.0K 361.2M 4096
/mnt/secure 361.2M 0.0K 361.2M 4096
/mnt/asec 361.2M 0.0K 361.2M 4096
/mnt/obb 361.2M 0.0K 361.2M 4096
/mnt/fuse 361.2M 0.0K 361.2M 4096
/system 590.6M 441.1M 149.4M 4096
/efs 11.8M 8.1M 3.7M 4096
/cache 307.1M 5.5M 301.6M 4096
/data 2.0G 115.9M 1.9G 4096
/preload 503.9M 104.6M 399.3M 4096
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,seclabel,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p2 /system ext4 ro,seclabel,noatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p1 /efs ext4 rw,seclabel,nosuid,nodev,noatime,user_xattr,acl,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p3 /cache ext4 rw,seclabel,nosuid,nodev,noatime,user_xattr,acl,barrier=1,journal_async_commit,nodelalloc,data=ordered 0 0
/dev/block/mmcblk0p6 /data ext4 rw,seclabel,nosuid,nodev,noatime,errors=panic,user_xattr,acl,barrier=1,journal_async_commit,nodelalloc,data=ordered 0 0
/dev/block/mmcblk0p11 /preload ext4 ro,seclabel,nosuid,nodev,noatime,user_xattr,acl,barrier=1,journal_async_commit,data=ordered 0 0

Probably this is the problem:
Code:
I/ ( 116): NV Interposer: k:Error creating socket.
I/ ( 116): NV Interposer: Communication layer init failed.
D/NvOsDebugPrintf( 116): Init second stage failed.

Adam77Root said:
Probably this is the problem:
Code:
I/ ( 116): NV Interposer: k:Error creating socket.
I/ ( 116): NV Interposer: Communication layer init failed.
D/NvOsDebugPrintf( 116): Init second stage failed.
Click to expand...
Click to collapse
and I have no idea how to fix it. (maybe no internet permission for SurfaceFlinger? )
I've found tegra3 base with same issue http://pastebin.com/GvrTX968
I dont like that either:
Code:
I/SurfaceFlinger( 116): Using composer version 0.0
It was
Code:
I/SurfaceFlinger( 112): Using composer version 0.1
edit: and omnirom 4.4 works. ( https://github.com/omnirom/android_...53b0969124a8817beed8fad03ceaad68546b22#diff-0 patch didnt help)
Missing BOARD_EGL_NEEDS_LEGACY_FB in:
https://github.com/CyanogenMod/andr....0/services/surfaceflinger/SurfaceFlinger.cpp

So what are the chances of a working KitKat 4.4 ROM? Also are you saying we can use your Omnirom safely? Thank you for developing for us!

stormdude124 said:
So what are the chances of a working KitKat 4.4 ROM? Also are you saying we can use your Omnirom safely? Thank you for developing for us!
Click to expand...
Click to collapse
going to release omni rom 4.4, but it has many problem ATM, and I dont feel I could fix it, problem is in old HALs.
Android droped tegra2 support in 4.2, CM in 10.2, so its miracle to hace stable cm-10.2.

[ROM] CM11(F2FS) [4.4.4] All Variants!!!(Maguro, Toro, and Toroplus)(7-9-14)

CyanogenMod 11 with F2FS and Bsmitty Kernel
Build 7-9-14 Dalvik
https://drive.google.com/file/d/0BzFtTE47m7SdNjhLekZGeDNnNm8/edit?usp=sharing
Changes
Script rewrote and applied to updater script via /Temp folder along with all GSM related files and build.prop changes
Build 7-19-14 ART
https://drive.google.com/file/d/0BzFtTE47m7SdSC16RTdSem5FQVU/edit?usp=sharing
This ROM Features:
F2FS Support
BSmitty 6-28 F2FS Kernel
GSM/CDMA Convergence Script
CyangoenMod 11(Android 4.4.4)
Bugs:
GSM not working as of previous builds[WIP]
If the Dalvik build doesn't flash properly unzip the zip file and navigate to "META-INF - com - google - android" and open the updater script and change
Code:
package_extract_file("/1Variant.sh", "/temp/1Variant.sh");
to
package_extract_file("/temp/1Variant.sh", "/temp/1Variant.sh");
ART will have the change but I just realized the typo. Sorry for the issues.

*Reserved For Updated Information*
File Systems after Install
Code:
rootfs / rootfs ro,seclabel,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,nosuid,nodev,noatime,nodiratime 0 0
sysfs /sys sysfs rw,seclabel,nosuid,nodev,noatime,nodiratime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
none /sys/fs/cgroup/memory cgroup rw,relatime,memory 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,seclabel,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,timer_slack,cpu 0 0
/dev/block/platform/omap/omap_hsmmc.0/by-name/system /system f2fs ro,seclabel,noatime,nodiratime,background_gc=off,discard,user_xattr,inline_xattr,flush_merge,active_logs=2 0 0
/dev/block/platform/omap/omap_hsmmc.0/by-name/efs /factory ext4 ro,seclabel,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.0/by-name/cache /cache f2fs rw,seclabel,noatime,nodiratime,background_gc=on,user_xattr,inline_xattr,flush_merge,active_logs=2 0 0
/dev/block/platform/omap/omap_hsmmc.0/by-name/userdata /data f2fs rw,seclabel,noatime,nodiratime,background_gc=on,user_xattr,inline_xattr,flush_merge,active_logs=2 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,nosuid,nodev,noatime,nodiratime 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,noatime,nodiratime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
As you can see System, Data, Cache are F2FS!
News 6-18
The last build I tried using getprop and sed to replace lteCdmaOnDevice for those who were on Maguro so I can create a One Rom for GSM and CDMA.
Today's build will be testing a script in init.d called 10variant
Code:
!#/bin/bash
PROP=$(getprop ro.product.device)
if [ "$PROP" = "maguro" ];
then
sed -i 's/telephony.lteOnCdmaDevice=1/telephony.lteOnCdmaDevice=0/g' /system/build.prop;
else
fi;
a little script I wrote up for this and the script is temporary because I don't want the script to have to run every boot and only on instllation.
I'll work with the edify languange for the updater-script and make a more permanent solution.

thank you very much! you do not know what I was trying to convert the CM11 in f2fs without getting results

pablomoreno said:
thank you very much! you do not know what I was trying to convert the CM11 in f2fs without getting results
Click to expand...
Click to collapse
Not a problem, If you're on Maguro(GSM) please read the second post. I forgot to add some lines to the code.

is this CM11 only with F2FS' modified updater-script or any other modification (ex. ROM f2fs commits)?

Did you merge the commits to give full support for f2fs in this ROM? Or just changed the update script?
Edit: nevermind, it was already asked in last post.
Sent from my Galaxy Nexus using XDA Free mobile app

I thought the commits had already been added? The CyanogenMod website has commits dating back to 2013.
I added the partition line to the updater-script and also bsmittys f2fs kernel.
Sent from my Galaxy Nexus using XDA Premium HD app

I will be working on a new build today.
I'll have three versions released. All Variant(fixed for testing), Maguro, and Toro/Toroplus.
My main goal is to have one ROM that works across GSM and CDMA by changing the build.prop during the installation process.
Sent from my Galaxy Nexus using XDA Premium HD app

dezful said:
is this CM11 only with F2FS' modified updater-script or any other modification (ex. ROM f2fs commits)?
Click to expand...
Click to collapse
From what I can find for CyanogenMod MKFS has been updated through to allow F2FS Partitions or otherwise it wouldn't mount them with the method I'm using.
I think the major thing right now is to iron out some of the bugs.

New Build in OP for Dalvik Run Time.

blmvxer said:
From what I can find for CyanogenMod MKFS has been updated through to allow F2FS Partitions or otherwise it wouldn't mount them with the method I'm using.
I think the major thing right now is to iron out some of the bugs.
Click to expand...
Click to collapse
Unfortunately, CM didn't commit the modifications to give full support to f2fs. Take a look at Vanir commits for that.
Sent from my Galaxy Nexus using XDA Free mobile app

I'm running the 6/17 nightly with f2fs and most recent DirtyV and it's running nicely so far
Sent from my Galaxy Nexus using XDA Premium 4 mobile app

Atento said:
Unfortunately, CM didn't commit the modifications to give full support to f2fs. Take a look at Vanir commits for that.
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
I'll take a look. That may fix the random reboots I get.
Sent from my Galaxy Nexus using XDA Premium HD app

The line I used to try to allow both variants to work on the same rom fails for toroplus(my phone) but seems to work for maguro. I will hopefully have a working updater-script by the end of the day.
for toro and toroplus users please remove this
Code:
getprop("ro.product.device") == "maguro" || sed -i 's/telephony.lteOnCdmaDevice=1/telephony.lteOnCdmaDevice=0/g' /system/build.prop + getprop("ro.product.device") + "\".");
from the updater script to flash without error.
I'm going to test this little script I wrote up for init.d since I can't find a way using the edify language for the updater-script.
Code:
!#/bin/bash
PROP=$(getprop ro.product.device)
if [ "$PROP" = "maguro" ];
then
sed -i 's/telephony.lteOnCdmaDevice=1/telephony.lteOnCdmaDevice=0/g' /system/build.prop;
else
fi;
Revised Code
Code:
#!/bin/bash
PROP=$(getprop ro.product.device)
if [ "$PROP" = "maguro" ];
then
sed -i 's/telephony.lteOnCdmaDevice=1/telephony.lteOnCdmaDevice=0/g' /system/build.prop;
fi;

6-18-14 Builds for Dalvik and ART are ready for testing.
I believe I've made a good temp-fix for allowing both GSM and CDMA on the same ROM.

Did you merge the 3 commits related to f2fs?
Sent from my Galaxy Nexus using XDA Free mobile app

I did, I've only suffered one reboot since this mornings install.
I'm still using the CM source for 6/16 to stay more stable instead of building with each days nightly.
Also for anyone else if you're using maguro please give me feedback since I wrote that script to mix GSM and CDMA in one install.
Sent from my Galaxy Nexus using XDA Premium HD app

@blmvxer Why you separately ART and Dalvik??

Error flashing dalvik 18-6, error executing updater binary...

imam.krismanto said:
Error flashing dalvik 18-6, error executing updater binary...
Click to expand...
Click to collapse
I'll check it out today.
And I figured it would just be faster. I usually restore my apps from Google and switching to art can be slow and annoying.
Sent from my Galaxy Nexus using XDA Premium HD app