yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] Unitas:
All that boot image will do is mount your second partition on your sd card according to what the file system is, assuming the file system is supported by the phone.

The old boot image only mounted ext2 partitions, but did not properly dismount them before the phone shut down. This, Cyano believes, is the cause for the NFS handle errors, making the partitions unusable and forcing people to reformat them.

LucidRem then edited the boot image to include options to have the partition mounted as read-only before shutdown, thinking this might solve the problems. While it might have prolonged the errors, my phone eventually succumbed once more to the NFS errors and I had to reformat.

All I did to the boot image was replace "ext2" with "auto" in the file that mounts the sd partition, runme.sh.

This way, as Cyano was thinking, the system will mount an ext3 partition (or ext2 if you still have it) on bootup instead of ext2-only. Cyano thinks that the journaling feature in ext3 filesystems (a feature that ext2 does not have) will stop the NFS errors.

By merely changing the mounting option from ext2 to auto, it will detect whatever filesystem you have on the partition and mount it accordingly. Cyano suggested "auto" instead of just "ext3" to keep backwards compatibility for those who still have ext2 partitions, while still allowing us to use ext3. So having your app/data partition as ext3 is what Cyano thinks will solve the issue. The modded boot image merely allows the phone to use the ext3 partition.

Make sense?
[G1 Android Development] Henchman:
Do I do this BEFORE trying to install the Hero Rosie rom?
[G1 Android Development] DOHCtor:
It does makes sense but my phone was already able to use the ext3 partition without the modded boot.img. So it was pointless for me to flash that boot image?

So what I think you're saying is that I didn't have to do anything since my phone had a fresh rom install, fresh ext3 partitioned sd card, and everything was mounted already? (I'm using symlinks to run my apps and dalvik-cache on sd).
[G1 Android Development] Kinslayer81:
You need to do a 'busybox mount' instead of plain mount, because the built in mount command doesn't support the 'auto' type. Even if you're stuck at the boot you can run this command via adb shell and you'll see the phone will finish booting (once dalvik-cache becomes available again).
[G1 Android Development] jaygajay:
Do it after so that when you flash the Hero ROM it won't overwrite the boot.img if you had flashed it before the ROM

Wow. Okay I will repack another boot.img with 'busybox mount' and post results later after work.

The phone has ext3 built in but some ROMs explicitly mount with an '-t ext2' command. So even if you formatted your card to ext3 and android supports it, it is still using ext2. Unless the ROM you are using already had the '-t auto' command in the boot.img. Type 'mount' in treminal or 'adb shell mount' from your computer and see what filesystem your /system/sd partitioin is using.
[G1 Android Development] leomak:
thanks jagajay~

i followed your steps on Hero and it shows the following result

C:\Documents and Settings\Leo\Desktop\sdk\tools>adb shell mount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mtdblock3 /system yaffs2 rw 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev 0 0
[COLOR="Red"]/dev/block/mmcblk0p2 /system/sd ext3 rw,noatime,nodiratime,errors=continue,data=[/COLOR]
ordered 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=
1000,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,s
hortname=mixed,utf8 0 0

does it means i m done?:)
[G1 Android Development] jaygajay:
That should be it.
[G1 Android Development] LucidREM:
you can't mess with the partition while it is mounted .. so unless someone has the "unmount" for android you have to go into recovery mode to access the partition before the mount is done .. it's really not that hard
[G1 Android Development] pentace:
Interesting

I had my rosie build flying with ext2 now that im using ext3 its crawling like it is a fresh install... Any ideas why?
[G1 Android Development] Praeluceo:
Filesystem Thoughts

I know it's a phone and there's no real difference between users, but it's probably better to get in the habit of using chmod 711 or chmod og+x rather than just carte blanche 777. But even then, 755 should have worked as it's executable.

Also, I'd put a disclaimer on the ROM that it is the user's responsibility to determine whether they have hardware wear-leveling on their SD cards -before- updating to ext3 (or any journaled filesystem) as this feels to me to be a really quick way to toast the card. As it stands, the extra writes for ext3 will significantly decrease the lifespan of the card, but not so much to make it shorter than the average lifespan for a cell phone I don't believe, but there is a performance hit with writes on ext3 that might be perceptible on our phones. I think we need G1 ext2/ext3 benchmarks.

Keep in mind that a lot of these users are probably using the stock microSD card that their phones came with and don't have Class 6 (I think the stock card was a C2 wasn't it?) cards, and have no way of readily knowing if it supports wear leveling. It's a good disclaimer so that when people's cards fail, they don't blame you (whether or not that blame is warranted, which I doubt it would be). It appears that most of your microSDHC cards do support wear leveling, but not so many of the <2GB microSD cards.

And in response to using JFFS, JFFS2, YAFFS, or any other flash-filesystem that supports built-in wear leveling, this would be a fatal idea, especially for the higher-end SDHC cards that support their own wear leveling. You'd have so many blocks being written so many places that neither system would work to the benefit of the lifespan of the card and I believe you would see a higher failure rate than a journalled filesystem over a non wear-leveling NAND device.

An interesting thing to look at might be using Cramfs or SquashFS if there were ever something we'd want to have mounted but not moved or changed. Such as perhaps the HTC Rosie "addons" to the base firmware. If those are static, then rather than putting them directly into our apps2sd partition we could keep them on a 3rd partition burned with a Cramfs image of those files. Just a thought, I know it's probably more involved than anyone would really want to do as most people seem to be having difficulty partitioning and formatting their card for apps2sd in the first place.

Anyway, that's my 2¢ worth.

Here are a couple links I found that might be relevant while reading about which filesystem to use:

http://wiki.openmoko.org/wiki/FileSystem_microSD_cards

http://www.ibm.com/developerworks/linux/library/l-flash-filesystems/
[G1 Android Development] DOHCtor:
it says ext3, just like the guy below your post. thanks for clarifying!
[G1 Android Development] osho741:
your right lucid, it wasnt that hard lol, i just get nervous whenever i see script lol, but thanks again man it appears to have worked fine :)
[G1 Android Development] Unitas:
No, as the original mount options were set to ext2-only. An ext3 partiton is an ext2+journaling. I could have set it to ext3-only, except those with ext2 partitions wouldn't be able to use them, so Cyano suggested it be set to auto.

An ext3 partition would still have worked with the old options, except the journaling feature would have been disabled which is what Cyano thinks will solve the problems.

It would have worked anyway, yes, BUT your ext3 partition would have been mounted as an ext2 partition (journaling disabled). Your partition would not have been using the journaling feature, which Cyano thinks will solve the issues. In order for the partition to use journaling, the boot image would need to have been modified to allow ext3 partitions to be mounted, not just ext2-only.
[G1 Android Development] fawaad:
I have a problem in converting ext2 to ext3. This is what I get. Do I need to reformat the entire microsd card?

/ # tune2fs -j /dev/block/mmcblk0p2

tune2fs 1.40.8 (13-Mar-2008)

Creating journal inode:

tune2fs: Can't read an block bitmap

while trying to create journal file
[G1 Android Development] cyanogen:
Run e2fsck on it first.
[G1 Android Development] fawaad:
Yeah I did.. Looks like there were some issues with the card.

Anyways, I started from scratch and reformatted the card using SDSplit. I think the script partitions it using ext2.

So after I was done, I reflashed my phone and while being in recovery I ran e2fsck and tune2fs, which didn't throw the error this time.

now running mount shows me ext3..

Thanks all.
[G1 Android Development] LucidREM:
Very Strange

so i did the conversion on my phone .. the EXT2 is now EXT3 .. but here's the thing .. my FAT32 is gone .. not entirely .. just mostly .. and when i stick it in the PC .. no files show at all .. so being that i am currently on a computer at the office i cannot easily check partitions .. but something is most definitely weird .. anyhow

anyone else experience such weird things?
[G1 Android Development] Tafkatoo:
Yes. One of three phones I mess with I tried working with the new apps2sd partioning the card and the 3.3.x auto ext3 updating etc. Long story short, ran into tons of odd behavior from the build, builds after that and the SD card itself regardless of apps2sd method used or used at all... including the fat32 partition and led to eventual failure on the SD card. (Abreast I returned it instead of working on it more. I do not wholly discount it may have been defective out of the box.)
[G1 Android Development] short/y:
Comparing ext2, 3 and 4 with/without atime

I went on the hunt for some statistics comparing ext2 and ext3 and atime-related mount options and found this article: http://thunk.org/tytso/blog/2009/03/01/ssds-journaling-and-noatimerelatime/ It's for SSDs, is mainly concerned with ext4 and is not an Android environment but it's a data point.

In a create/destroy intensive environment where files are removed and recreated (i.e. "make clean") journaling caused the number of bytes written to go from 6.54 to 14.56, roughly 122% increase. A less intensive environment (make) drove it from 204.4MB to 230.9MB, only about 12% higher. So, my own conclusion, without knowing how the files on /system/sd are managed, I still wouldn't think I would see a noticeable effect on my microSD card's life expectancy. Besides, if you add "noatime" to the mount options it looks like you can offset a good bit of the effects of journaling and return performance to roughly ext2.

But don't take my word for it, go read it for yourself ... I've got too many instances of missing the point of statistical analyses :)

Also, the page on the OpenMoko wiki cited by Praeluceo about this (http://wiki.openmoko.org/wiki/FileSystem_microSD_cards) is good, too. It's much shorter but is still interesting reading. And everything he cited I confirmed in my own reading -- stay away from YAFFS and the other flash file systems because modern devices have wear-leveling built in. SquashFS and CramFS are worthwhile alternatives in the right situations.
[G1 Android Development] Unitas:
Did you do the tunefs in the terminal or use a different program? The last time my ext2 decided to screw itself up i just up and repartitioned it to ext3 in gparted. I lost everything on it but it was worthless anyway.

Although, after I was using the ext3 partition with apps and stuff to sd, eventually the ext3 partition went wacky too. If journaling really does fix the errors then perhaps it is my sd that is the problem. It's like the partition just gets locked down; I can cd into the data and app folders but aside from repartitioning (and therefore wiping) the partition I can't delete or write anything. It works for a while, but eventually it happens.

Edit: I think it is my sd card, I just took a close look and it's only class 2.
[G1 Android Development] LucidREM:
problem is .. i have no problem with the EXT .. it's the FAT .. the one i didn't even touch .. something in the processing of the EXT did something to the FAT and messed with the files
[G1 Android Development] fawaad:
Ok now I have a new issue. Although previously sorted out that I have an ext3 partition working on my phone, I can't seem to install anything. Neither from my SD card nor from the Market.

When I install it from the Market, it says don't have sufficient space left and when installed from the SD card, it says "This app can't be installed on this phone" or something.

Is it due to the partition itself or the ROM I am using? Btw, I am using RogerROM by VirtuDude. He did mention it supported App2SD Ext3. I am not sure if I have to do anything extra.

I have also checked whether the partition is writeable or not. I can see the installed apps working fine.

UPDATE: I have fixed my issue. I seem to not have writeable access. When I entered ls -l, I got drwxrwxr-x on the /system/sd/app folder. I fixed it by using chmod 777 /system/sd/app with su. All is good now :p
[G1 Android Development] Unitas:
sounds like the similar errors I was running into, only when I would try to chmod it, it would give me the finger.
[G1 Android Development] namsir:
gave me sbin:sh Permission Denied when i do e2fsk and tune2fs

can you help please?
[G1 Android Development] jaygajay:
Before step 10 you need to type

chmod 755 /system/bin/e2fsck
chmod 755 /system/bin/tune2fs
[G1 Android Development] namsir:
The wireless stop working after this.....anyone else got this problem? it says unable to turn on wifi.
[G1 Android Development] BolecDST:
How can I check if I have the ext3 partition? I upgraded ext2 and I want to be sure everything went fine.
[G1 Android Development] jaygajay:
adb shell mount
[G1 Android Development] namsir:
just to check....do i have to format my sdcard to ext3 instead of ext2?
[G1 Android Development] DOHCtor:
Can someone please modify JF's 1.51 ADP boot image to support ext3 and for it to call userinit.sh in /system/sd/ if it's there? I'll buy you a beer!
[G1 Android Development] alritewhadeva:
You'd have to unpack the boot.img and then complie a different kernel. WHy not just switch to cyanogen. It's JF based
[G1 Android Development] DOHCtor:
I appreciate what cyan does and I was on his rom for a week, but its too bloated for me with many features that I don't need. I only went to his rom because of the ext3 support and booting of linux swap (calling the userinit.sh in system/sd). But I don't have the time to keep up with the updates and deal with some lingering FC bugs.

Someone made a modified boot.img for the jf's 1.51 us version and it works, but the us cupcake seems to run really slow.

I'm sure someone can do this quick and easily. I would really appreciate it and I'll buy them a beer for their time.
[G1 Android Development] alritewhadeva:
Try contacting a dev lol. I've never tried unpacking the img and compiling a kernel before.
[G1 Android Development] DOHCtor:
Anyone? It can get tedius running e2fsck everytime I reboot my phone :(
[G1 Android Development] LucidREM:
Boot Image

did you try my boot.img? it's based off the US build .. not sure if the boot.img matters
[G1 Android Development] cyanogen:
I think you're the first person to call it "bloated" :confused:
[G1 Android Development] njuncos:
no FC's on his latest 3.6.7.2, unless you did something wrong or need to run fix_permissions

lol, and definitely NOT bloated...runs faster than ever. i guess since it is a "complete" rom you are calling it bloated?
[G1 Android Development] DOHCtor:
Is your modified u.s. boot.img compatible with the adp rom?

I'm just bad at wording it. It's definitely not bloated. It just doesn't fit my needs. I just want a basic rom that is rooted, can do a2sd, and with no extra apps. If I wanted the extra apps, I would push them into the rom myself. But now I need a boot.img to support ext3 and safely unmounts it when shutting down.

This doesn't mean I don't appreciate your hard work.

edit: I just flashed Unitas boot.img that was based off the US rom and it works on the ADP as well. #mount shows that it's mounted as ext3 with noatime.
[G1 Android Development] athost:
not to the point, deleted
[G1 Android Development] cripgballerkundikusu11:
right no i'm running ext4 with no problems
[Touch Pro2, Tilt 2 Windows Mobile General] trickyhenry:
alrights peeps .. enjoying my new tp2 but why oh why am i getting google mobile formatted pages when i use the opera google search box. i don't want mobile formatted pages and i'm guessing you don't either.

quick fix to turn this feature off?
[Touch Pro2, Tilt 2 Windows Mobile General] LordLugard:
From what i remember from the Touch Pro 1, there is a setting in Opera's config that you have to change (i think it is the user agent) otherwise Opera reports itself to some sites as a mobile browser.

Do a search for "opera user agent"..you'll find something.
[Touch Pro2, Tilt 2 Windows Mobile General] DaveTheTytnIIGuy:
On every version I've ever used (a lot), searching from the search box that's part of Opera ALWAYS loads mobile google. Even if you have Opera set to identify as a desktop browser.

Dave
[myTouch 3G, Magic General] trickshot:
Hi all,

I have noticed a strange issue with my UK Vodafone HTC Magic (default factory build). I downloaded the slightly better HTC keyboard Touch Input and installed it to my phone. If I go to "Settings" > "Locale & text" I can see the option to turn on the Touch Input, but have no option to turn off the Android Keyboard. Hence, as it stands I cannot use any alternative keyboard (e.g. the HTC one or even Better Keyboard), as I've no means to turn off the default keyboard.

Can any other UK owners confirm that this is the case? Only I have searched all over the place and cannot see any reference to this issue. I am assuming it is a restriction of build to ensure people don't switch off the keyboard in error, rendering the phone useless as it has no hardware one to fall back on. Nonetheless though, it does seem rather odd.

If I am correct and it simply isn't an option, is there anything I can do to enable it short of rooting the phone?

Thanks in advance for your help!
[myTouch 3G, Magic General] pdazealot:
same issue here after installing key

I had the compact keyboard working on the jf 1.51 build on my G1, but not on my Magic.
[myTouch 3G, Magic General] trickshot:
Yeah this is 100% factory spec - ie as its received out the box from Vodafone. Hence I'm guessing the option has been hidden,which seems pretty daft. I'm assuming I could still do a Force Close on the Android Keyboard to force the issue, but obviously that isn't a long-term fix.
[myTouch 3G, Magic General] Swifty:
Took me a little while to figure this one out but it doesn't set it as the active keyboard by just enabling it in 'settings'.

You have to go to an input box (eg. compose a text message) and select the text input box using the trackball (hold it down) after a few secs a menu appears allowing you to choose your keyboard.
[myTouch 3G, Magic General] trickshot:
Funny enough I was just coming in here to say that I'd found the solution, but you beat me to it! The one I found was pressing and holding the "123?" button, which then brought up the option to select the input method. Worked a treat.

Thanks for replying though; had I not stumbled on the answer myself you would have been a lifesaver!
[myTouch 3G, Magic General] andyathome:
Where we I find the HTC KB, i had a look on another post which suggested a file name .. HTC Chime i think - But googling that yielded nothing - Any clues anyone?
[myTouch 3G, Magic General] pdazealot:
Found out one that works and installs w/o issue.

I downloaded the file called HTC_IME.apk, and this installed, without any issues. Works great, and has Full Size Qwerty, xT9, and Compact Qwerty(like Blackberry Pearl). Do a search on google for HTC IME.apk+android, and install it. Issue resolved!
[myTouch 3G, Magic General] kevstv:
Big big big thank you to swifty and trickshot!!! I had this working on my G1 and could not get it working on my magic, I was getting so frustrated. You ARE lifesavers!! :)
[myTouch 3G, Magic General] xenotimes:
great discovery, thank you very much for this discovery, i'm going to install htc_cime again
[myTouch 3G, Magic General] parrot5:
Thanks, it works for me too
[myTouch 3G, Magic General] durrty_r3dd:
thankz gentlemen. i had searched every forum except this one(the only one im registered to) the keyboard was the only reason i could find to switch back to my samsung epix. that and a call recorder that workz. thankz
[myTouch 3G, Magic General] can7:
worked a treat thnx:)
[myTouch 3G, Magic General] zenderady:
Thankyou!thankyou!thankyou!
[Touch Dual, MDA Touch Plus General] deluxestyle:
My O2 XDA Star is switching off himself every time i transport it in my trouser pocket.

I made a Hardreset but the same problem.

My O2 XDA Star is key locked every time. But it will be switching off if i transport it in my pocket.

Does anybody know this problem?
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] nicelad_uk:
Afternoon,

Is anyone working on a light Windows Mobile 6.5 Rom as yet? There were loads for the Blackstone when I had that and all quite stable and good. Just wondered...
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] DaveShaw:
They might turn up in time, you'll need to wait for the Hard SPL before cooked ROMs appear. There's mention of the Elite ROM project making a 6.5 ROM, and there's normally a lite version.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] nicelad_uk:
Sounds good, I'll get a donation there way. Anyone else noticing such high memory usage from stock version? 62% Im using!!! :)
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] Prille:
Yeah, same for me, around 60% and about 53% when using it without TF3D, but kinda starting to like the touchflo interface...
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] mallman:
agreewith you. not sure what click in my head but i am liking it myself
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] beast0898:
Hi memory useage is down to heavy cache settings and opera always running in background. It could be brought down but then TF interface and opera would not be as responsive. There is still plenty of mem free so suits me fine. Prefer responsiveness over free mem any day.

Cheers,

Beasty
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] Zafrumi:
what good is RAM if the device doesnt use it? its not a bad thing if more than 50% memory is being used imo, after all thats what its there for: to be used :) if the device starts slowing down because it needs more memory than it has, thats when its getting problematic.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] rvt1000:
Well,..... how about killing batterY? that's one major issue most of us have issues with... :D
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] Zafrumi:
dunno, my battery lasts like 5 days, even with 60% ram usage
[Windows Mobile Development and Hacking General] hoolahoous:
Is there a wm6+ proxy which has capability to modify the urls on the fly ?

For e.g. if user types http://www.cnn.com it could modify it to http://www.cnn.com?browser=winmo ?

I know for most of the sites the extra parameter will be useless but I need the extra parameter to be sent to few of the websites which my friend owns..

since I need that parameter to be appended to each request (image,css,js file, form post url etc) Just manually typing the url in browser will not work for me.
[Windows Mobile Development and Hacking General] hoolahoous:
any ideas ?
[Touch Diamond, MDA Compact IV General] Neo Cortex:
Just did a backup using Sprite and it reported errors. Said it could not backup the folders in "Documents and settings\Default" folder. When I looked in it there were 62 folders simply called "." . I cannot delete them. Anyone know how to get rid of them or what might be causing them