<drellisdee> I just rebuilt from source several libs for velocity turbo i used 2.2.2 source but works on 2.2.1 too
<SavoxUnity> well
<SavoxUnity> when I say patched
<SavoxUnity> I mean replaced
<drellisdee> which ones are you refering too
<drellisdee> link me velocity 1.2 plz been waiting on trident
<SavoxUnity> Nightlies can be found here: http://awesomazing.com/velocity/betas/ USERNAME: velocity PASSWORD: supersecret |
<drellisdee> http://www.mediafire.com/file/tl58bwzd1duiv2a/velocity_turbo_v3_unzipme.zip
<SavoxUnity> i saw
<drellisdee> latest had small ommission in  earlier one this is flashover no wipe
<drellisdee> left out vold.fstab
<drellisdee> that turns 1.1 or should be 1.2 into vel turbo
<SavoxUnity> oh you can flasover?
<drellisdee> v3 one yes
<drellisdee> no wipe needed
<SavoxUnity> my usb port in trashed on the ally
<SavoxUnity> have to hold the cable in to get adb to work
* SavoxUnity has a repacement comming tomorrow
<drellisdee> and new recovery included will sd part the required partiotns now
<drellisdee> ive gotten a lot better at scripts now with your help btw
<SavoxUnity> badass
<drellisdee> look at bigdata.sh in recovery ramdisk if you want to make some changes/addditons (cleanup) but works well as it is
<SavoxUnity> i think people are gunna love this
<drellisdee> me too can be ported to virtually any device also
<Sora1995> SavoxUnity... any reason why apps all of the sudden aren't updating?
<SavoxUnity> in the latest nightly?
<Sora1995> no, 1.1
<SavoxUnity> is cache full?
<Sora1995> i still don't have a battery
<SavoxUnity> busybox df -h
<Sora1995> let me see
<Sora1995> k
<SavoxUnity> sd is almost done backing up
<SavoxUnity> im getting tired of holding this cable in....
<Sora1995> the busybox can be done without a computer, right?
<SavoxUnity> in terminal
<SavoxUnity> yes
<SavoxUnity> adb shell busybox df -h | grep /cache | awk '{print $4}'
<SavoxUnity> would jusst tell you what you want
<SavoxUnity> drellisdee,
<drellisdee> yes
<SavoxUnity> does the new recovery support wiping these new ext parts?
<drellisdee> yes and nandroid backup of them
<SavoxUnity> nice
<SavoxUnity> I cant wait to get the new ally, wifi adb is annoyingly slow
<SavoxUnity> select "Create a new ext3 data.img" This may take up to 10 minutes so be patient
<SavoxUnity> does this what? dump your data into a yaffs img then convert to ext3?
<SavoxUnity> also
<drellisdee> doesnt backup data there its a blank fresh data on only needs to be generated once
<drellisdee> its reused/wiped after that
<SavoxUnity> why ext4? there a noticable difference? I still use 2 on my servers because the lack of fragmentation
<drellisdee> dd if=/dev/zero of=data.img bs=1M count=1024
<drellisdee> no its ext3 by default I added a ext4 option for those that want it
<drellisdee> needs a journal to be effective
* SavoxUnity nods
<SavoxUnity> for the faster i/o I take it
<drellisdee> ye
<SavoxUnity> Im still a little confused, by the need to make this data.img..... is it mounting this img on the ext3 partition created?
<SavoxUnity> and the ext2... is this for swap?
<drellisdee> no
<drellisdee> no
<drellisdee> thats only so things that call for a wipe of mmcblk0p2 dont kill data
<SavoxUnity> Sorry for my ignorance, I drew the line at automation, never learned all too much about the filesystems
* SavoxUnity nods
<drellisdee> place holder for app2sd mmcblk0p2
<drellisdee> mmcblk0p2 is unused
<drellisdee> the data.img is your actual data partiton btw
<SavoxUnity> here goes nothing
<drellisdee> and is mounted as such on /data
<SavoxUnity> how are you able to trick it?
<SavoxUnity> vvm
<SavoxUnity> fstab
<drellisdee> rebuilt from source :)
<drellisdee> you used v3 pkg right?
<SavoxUnity> Yes
<SavoxUnity> its booting
<SavoxUnity> suposedly
<SavoxUnity> cant get the cable to work to get a cat going
<SavoxUnity> booted
<SavoxUnity> looks like it wiped my dalvik
<drellisdee> was I called wipe cache in updater-script I have custom binarys that require rebuilding dalvik cache
<drellisdee> you old data is still intact on the data mtdblock5
<SavoxUnity> Yeah it didnt preserv my data partition
<drellisdee> its still there but you use the data.img as data in this one
<SavoxUnity> Yeah Im gunna mount it somewhere and pull my shit off
<drellisdee> to go back flash old boot.img and use  vold and vold,fstab in old rom to handle parted sdcard
<SavoxUnity> /dev/block/loop0       1007.9M     44.1M    912.6M   5% /data
<SavoxUnity> ^ badass
<drellisdee> could do a mkdir /dataold and mount it there and use a cp
<drellisdee> but would get useless junk if done not in recovery
<SavoxUnity> # mkdir /system/mnt
<SavoxUnity> # busybox mount /dev/block/mtdblock5 /system/mnt
<SavoxUnity> heh
<SavoxUnity> way ahead of you
<SavoxUnity> useless junk?
<drellisdee> yes there is a reason nandroid requires recovery
<drellisdee> copying old is not problem but writing to new is if fs is in use
<SavoxUnity> I have had alot of problems dumping and restoring from userland....
<SavoxUnity> makes sense
<drellisdee> thats why cant dump those if in use
<drellisdee> except for like misc boot or recovery dumps those are fine from userspace
<SavoxUnity> hrm
<SavoxUnity> recovery mounts the old data
<SavoxUnity> /dev/block/mtdblock5    152.4M     49.8M    102.5M  33% /data
<drellisdee> yep
<SavoxUnity> :) new is /dev/block/mmcblk0p.......3?
<drellisdee> no
<drellisdee> mount bigdata
<SavoxUnity> beautiful
<drellisdee> mount -o rw /bigdata.data.img
<drellisdee> mount -o rw /bigdata.data.img /data-ext
<drellisdee> mount -o rw /bigdata/data.img /data-ext
<drellisdee> mount bigdata 1st then use 3rd line
* SavoxUnity nods
<drellisdee> or bigdata.sh mount-img will mount bigdata ie mmcblk0p3 then mount data.img as /data
<SavoxUnity> copying now
<SavoxUnity> hopefully it can preserve permissions
<SavoxUnity> so I can keep my app data
<SavoxUnity> UIDs seem to be the bane of my existance
<drellisdee> will need to umount data-ext then losetup -d /dev/loop0 to be able to umount bigdata
<drellisdee> err dev/block/loop0
<SavoxUnity> I got it mounted
<drellisdee> will need that to unmount
<drellisdee> have to remove the loop node to unmount mmcblk0p3
<SavoxUnity> I just rebooted
<SavoxUnity> unclean style
<drellisdee> check out bigdata.sh script for use didnt add a help
<SavoxUnity> and........... YES!
<SavoxUnity> I was able to preserve my app data!
<SavoxUnity> this is the first time ever!
<drellisdee> pretty sanppy so far huh?
<drellisdee> snappy
<SavoxUnity> well
<SavoxUnity> it seems to be very slow right when you come into userland
<SavoxUnity> when the sdcard mounts the fat
<SavoxUnity> only one FC problem
<SavoxUnity> W/ActivityManager( 1404): Process android.process.media has crashed too many times: killing!
<drellisdee> as all do on velocity mmcblk0p3 is mounted in early init thats blk1 thats slow you should move apps to internal
<SavoxUnity> buit I can manually tear out the data for it, and reboot should fix
<drellisdee> i intended to be on a fresh /data btw
<SavoxUnity> I know, I am in the middle of an audiobook tho
<Sora1995> savoxunity, drellisdee
<Sora1995> busybox df -h
<Sora1995> whoops
<SavoxUnity> gotta keep that bookmark
<drellisdee> kk
<SavoxUnity> lol
<Sora1995> http://pastebin.com/Y38gCS82
<drellisdee> move your apks to internal and it will mount faster the regular  sdcard block
<SavoxUnity> makes sense
<drellisdee> with 1gb data it makes no sense to run them on slower android_secure
<drellisdee> with a 32gb card you could have a 25gb+ /data
<SavoxUnity> Yeah
<SavoxUnity> 1g is more than enough though
<SavoxUnity> way more than enough
<SavoxUnity> the poor phone would cry when you opened the app drawer.... if you had that many apps
<drellisdee> gonna sign out let me know what you think
<SavoxUnity> aight
<drellisdee> i think its pretty much ready to release. maybe a scrit cleanup but thats all
<SavoxUnity> ill lookit the script
<SavoxUnity> its in ramdisk?
<drellisdee> yes recovery sbin
<drellisdee> look in updater-script too as to how i call it. same script for multiple args
<drellisdee> and used in recovery menus too
<SavoxUnity> this is awesome, great work man
<SavoxUnity> just when these kids thought it couldnt get any better too
<drellisdee> cpu wise no I/O was a whole new playground and have a 5x larger data too
<SavoxUnity> YOu should see my poor phone right now, I have the usb cable wrapped around it and taped, all so it will stay in long enough to restore my sdcard
<SavoxUnity> yeah
<drellisdee> wow no card reader?
<SavoxUnity> ...
<SavoxUnity> now... you make me feel foolish
* SavoxUnity cancels the copy
<drellisdee> goes without saying like app2sd dont umount/eject sd with phone booted
<SavoxUnity> heh heh heh
<drellisdee> however a fat32 partition like i used is way more forgiving than a ext one
<drellisdee> if someone does worts case is wipe data.img if the e2fsck i call on mount in init.rc doesnt repair it
<SavoxUnity> my phone did just do something... interesting
<drellisdee> what did it do?
<SavoxUnity> it vibrated for a solid second on 2nd splash.  Then rebooted
<SavoxUnity> on second boot, it came up fine
<SavoxUnity> other than my ....
<SavoxUnity> ok
<SavoxUnity> wierd
<SavoxUnity> having to do setup wiz again
* Sora1995 has quit (Quit: Leaving)
<SavoxUnity> mayhap... com.android.media data I removed is related
<SavoxUnity> no...
<SavoxUnity> I lost all my app data
<SavoxUnity> and everything wants to fc
<SavoxUnity> guess Ill go wipe...
<drellisdee> yes havent had that happen may be due to unclean mount
<drellisdee> use wipe data.img item
<SavoxUnity> trying just a reboot
<SavoxUnity> first
<drellisdee> script in recovery ensure no unclean mount
<SavoxUnity> something is very wonkey
<SavoxUnity> rebooted
<SavoxUnity> and now it want me to do setup wiz again
<SavoxUnity> like its not retaining data
<SavoxUnity> Ill wipe and see if its still acting rude
<drellisdee> always allow cleanup script to run in recovery too dont abort it that umounts cleanly
* SavoxUnity grumbles something about having to find his place in that damn book again
<SavoxUnity> Alright its fresh
<SavoxUnity> I didnt touch system, but shouldnt need to
<drellisdee> did you do the ext4 one?
<SavoxUnity> I wiped ext data img, cache and dalvik
<drellisdee> thats there for power users but ext3 is safer for data
<SavoxUnity> yeah, Im not convinced of the benifits of ext4
<drellisdee> i meant upgrade data.img to ext4?
<SavoxUnity> so no
<SavoxUnity> I didnt
<drellisdee> on pc yes on phone not much benefit
<SavoxUnity> seems good so far let me reboot to  make sure it doesnt forget again.... it is acting a lil sluggish tho
<SavoxUnity> pausing a long time between processes
<SavoxUnity> might just be firstboot woes
<drellisdee> yes same as 1st boot on normal for me
<SavoxUnity> the check that runs in init seems to take awhile....
<SavoxUnity> about a 8 second delay between the 1st 2 splashes
<drellisdee> yes fixes any journal corruption from user abuse
<SavoxUnity> wow, but after that bootup is considerably quicker (im clocked at 600 too)
<drellisdee> has my latest kernel too
<SavoxUnity> yes
<SavoxUnity> quick
<drellisdee> that allows better more stable overclock same one i released a few weeks go
<SavoxUnity> Nice... Im liking this.
<SavoxUnity> Definatly have to say goodbye to old data though
<SavoxUnity> to avoid those wierd complications
<SavoxUnity> Ill bet I can wasilly recover my apks
<SavoxUnity> but Not anything else
<drellisdee> apparently the clock spped wasnt the slow down it was the yaffs2 fs that was bootleneck. you can use ext on nand memory so there was no alternative
<drellisdee> you cant
<SavoxUnity> really, you cant? thats wierd
<SavoxUnity> well
<SavoxUnity> NOW
<SavoxUnity> we have all this extra space we can use
<SavoxUnity> idk what for :)
<drellisdee> google figured it out on gingerbread with ext4 requiring manufactures to go emmc instead of nand
<ThePunisher> http://forum.xda-developers.com/archive/index.php/t-971197.html
<drellisdee> ext only works on block fs not pure flash like nand
* Sora1995 (~Sora1995@24-171-2-5.dhcp.stls.mo.charter.com) has joined #velocity-dev
* ChanServ gives voice to Sora1995
<drellisdee> hey how do i set afk in irc?
<SavoxUnity>  /away
<SavoxUnity> well
<SavoxUnity>  /away MESSAGE