yashsingh1/xdaforums huggingface dataset:
[G Tablet Android Development] stanglx:
Add the -O ^huge_file file option to your mkfs.ext4 when formating the partition. (it won't work with this feature since it requires special kernel option that brakes compatibility with existing modules)

mkfs.ext4 -O ^huge_file ........

Report back...
[G Tablet Android Development] anlog:
Will do...
[G Tablet Android Development] gojimi:
I have had this result with every attempt of every rendition of data to a loopback device regardless of format and regardless of ROM and Regardless of Kernel.... hence why it is being left out of any VEGAn-TAB versions for now and the foreseeable future.

Just wanted you to know you are not alone.
[G Tablet Android Development] rcgabriel:
LOL, I think I finally got a basic ext4 setup working - JUST ext4 formatted data partition, nothing else. Do not bother doing this if you just want improved benchmarks, it really is a very marginal improvement right now.

Here's what I did (this is using Vegan beta 5.1):

**NOTE** this will wipe your data partition out and probably bootloop your G Tablet. Be careful. Have adb working first. And make sure you know how to nvflash just in case you really screw something up. :)

1) Boot into recovery mode

2) From my desktop, I ran:

adb push mkfs.ext4 /sbin
adb shell

3) At the shell I ran:

chmod +x /sbin/mkfs.ext4
mkfs.ext4 -b 4096 -m 0 -O ^huge_file -F -L userdata /dev/block/mmcblk3p2
mount /sdcard

4) DO NOT REBOOT YET.

5) Now I ran, again from my desktop:

adb push vegan-withext4-and-ext4ramdisk.zip /sdcard

5) Now you need to use the Recovery Menu to flash the working boot.img (i.e. ramdisk/init.rc + ext-4 supporting kernel) or else things will not boot happily for you. So go ahead and flash vegan-withext4-and-ext4ramdisk.zip.

For your information, my init.rc mounts /data as ext4 AND does not currently run inandop.sh at all because inandop.sh in its stock form will puke on an ext4 formatted /data partition and will cause a boot loop. Any kernel with ext4 support and any ramdisk that mounts /data as ext4 instead of ext3 should work fine here, as long as you also comment out the call to inandop.sh in init.rc.

6) If you have both made an ext4 filesystem on your /dev/block/mmcblk3p2 device AND flashed a boot.img with correct kernel and ramdisk, you *should* now be good to reboot.

IF you get the dreaded bootloop, don't panic, just boot to recovery. You can always go to the adb shell from recovery to manually reformat as ext3. Or just repartition your whole SD card using the Clockwork Mod GUI.

It's hard to really brick your G Tablet up doing this, but it's easy to boot loop it in a way that requires reformatting things. I am attaching the mkfs.ext4 binary and my test boot.img flasher with a 10.8.2-based kernel that supports ext4. Don't expect any brilliant results - as far as I can tell, my Quadrant scores are only very, very marginally better than with ext3 on my /data partition. 2450-2500ish.

I am going to work on getting the ext4 loop devices working on an ext4 partition, like ownhere's script does from the Desire forums (http://xdaforums.com/showthread.php?t=859419). I suspect the script just needs to be hacked up a bit to support all these things. Or you can use a third partition as Chenglu was suggesting a few posts back.

That should get great benchmarks, hopefully without sacrificing stability.

In any case, an ext4 file system on /data ought to be significantly more resilient than the ext3 file system that we have by default.
[G Tablet Android Development] rcgabriel:
LOL gojimi, the good news is I've at least got ext4 working well and it seems stable. I'm going to experiment more with ways to speed I/O up with and without loop devices. I agree that the loop devices in their current form are 1) too unstable and prone to corruption 2) too hard to undo/back out once done.

BTW, from ownhere's post in the Desire forums:

So as he says himself and as I sort of suspected the "writes" aren't real atomic O/S operations with the loopback solution, they are just writing to a kernel buffer that gets flushed here and there. :) Thus the incredible improvement in performance at the price of some stability.
[G Tablet Android Development] stanglx:
Doesnt make sense...

See here:

http://xdaforums.com/showpost.php?p=10239773&postcount=3

UNLESS... the internal storage is really that slow - becomes the bottleneck... Note the huge performance increase came from using external SDCard.

For the URL above follow exactly:

"How to roughly check your filesystem write speed"

For an apples to apples check.
[G Tablet Android Development] gojimi:
rcgabriel, yes I was working through the very same thing... it is partially how they did a bit of lagfix for the dell streak... by putting data2ext.... so if you want some more reading you can look here as well.

http://android.modaco.com/content/d...aco-com/325950/streakdroid-performance-mod-1/

Let me know how you get along.... I think ext4 for data would be nice in general.... though I believe our data currently is ext3. not sure like you said that there is any real life performance improvements with that.... the dell streak was not even ext3 so it did help them a bit i believe.
[G Tablet Android Development] stanglx:
Keep in mind it helped I suspect because they move that partition to the external SDCard..

Requirements BEFORE installing

1. A linux ext4 formatted partition on your microsd not bigger than 2gb in size- howto below for formatting

2. memory card reader - you cannot repartition over usb connection on streak
[G Tablet Android Development] rcgabriel:
OK, just ran from adb shell (bs=1M arg doesn't work on our dd, so I used the following command line which should be identical):

# sync; date; dd if=/dev/zero of=test.file bs=1048576 count=100 2>/dev/null; sync; date
Mon Jan 10 20:02:52 GMT 2011
Mon Jan 10 20:03:04 GMT 2011

That looks like 12 seconds to transfer 100M, or 8.33 MB/sec. That's on my /data ext4 partition.

On my /sdcard partition, which is fat32, I get:

# sync; date; dd if=/dev/zero of=test.file bs=1048576 count=100 2>/dev/null; sync; date
Mon Jan 10 20:07:37 GMT 2011
Mon Jan 10 20:07:50 GMT 2011

So that's 13 seconds, or about 7.69MB/sec.

I don't have an ext3 partition handy - do you care to try this on your /data partition and see how it compares?
[G Tablet Android Development] stanglx:
Dont have the device to check.. but see this Quadrant with ext4 (on MicroSD)

http://xdaforums.com/showpost.php?p=10336794&postcount=28

Your MB is in line from what I can see with the Archos but the Quadrant score is no where near...
[G Tablet Android Development] anlog:
When I run that command it completes instantly. Tried it from adb shell as well as term emulator directly from the tab.

I just dd'ed out a 100mb file to /data with ext3 and it took just over 27 seconds...
[G Tablet Android Development] anlog:
I was able to not only format /data as ext4, but also restored all of my data to it. In CW I mounted /data and /sdcard and tgz'ed my /data folder to /sdcard. Then after I formatted at ext4, flashed your kernel, and booted into gui, I just untarred the data.tgz back to /data and bounced. All of my data was back.

However, this basically breaks the ability of CW to do things like wipe cache or dalvik or even make backups, so I'm going back to ext3.
[G Tablet Android Development] pershoot:
CWM3 can handle ext4.

i am unsure if this has been ported over to the gtab for use yet, though.
[G Tablet Android Development] stanglx:
Then you are getting 3.7 MB/s which is very similar to what the Archos group got...

Ext4 is roughly double the performance..?
[G Tablet Android Development] anlog:
If I want to run another ext4 kernel with this modification, i just flash it and restore your init.rc and delete the inandop.sh file? Or are there other changes?

BTW, my wifi stopped working after I flashed your kernel. Is it compiled into the kernel or does it use the stock module?

:UPDATE:

Got wifi working. Had to blow away and restore stock files for /syste/lib/hw/wlan.
[G Tablet Android Development] anlog:
Well I can tell you that the Quadrant IO test runs SLOWER, but the scores are about the same (~2400). In real world usage, I'm finding that ext4 is no different than ext3 (at least on internal memory).

I'm still going to try to get some kind of functional dataloop going, because that does improve real world speed.
[G Tablet Android Development] stanglx:
It needs to be more reliable honestly.. I think the sync command would make the difference though with unfortunately high writes back to the storage.
[G Tablet Android Development] anlog:
Yea I mean it's just "delaying the inevitable". Eventually it's going to need to write...

BTW, anyone have a copy of mkfs.ext3?
[G Tablet Android Development] rcgabriel:
You can just mke2fs and then run tune2fs -j /dev/block/mmcblk3p2. Should be the identical result.
[G Tablet Android Development] anlog:
Cool that worked. Thanks!
[G Tablet Android Development] rcgabriel:
The thing is ext4 for /data is really rock-solid stable as far as I can tell. Even though Quadrant isn't much faster, it is faster for file I/O intensive operations, clearly.

Just about the *only* reason not to use ext4 on the data partition right now is that ClockworkMod can't mount it currently.

However, you can always store a known-good tarball on your SD card and untar it onto the data partition as anlog suggested if you want a backup handy.

Maybe I'll work on getting Clockwork Mod working with ext4 support?
[G Tablet Android Development] anlog:
Does it seem faster for you? After running the original data2loop I noticed that certain apps and functions were much faster. After going to ext4 (without data2loop), those apps and functions were running at the same speed as ext3 (without data2loop). Maybe I should have tested more???
[G Tablet Android Development] rcgabriel:
*Shrug* - some stuff, like restoring apps in Titanium Backup, seems marginally faster. I realize that it was much faster with data2loop, but I think data2loop willl be much more stable when we get it working with ext4 properly like the ownhere script does from the Desire forums.

But I'd also like to try running with an ext4 partition on a class 6 or class 10 SD card and see how that works in a few days when my card comes in.

BTW, I've already tried repackaging Clockwork Mod Recovery 0.8 with my ext4-supporting kernel. Clockwork runs fine, but the menu options still can't mount /data to do backups with it - the issue seems to be that the actual recovery binary only wants to mount /data as ext3. I'm going to see about re-compiling Clockwork to work with ext3 or ext4. If that's possible. :)
[G Tablet Android Development] Chenglu:
good work.

I had already use 3rd ext4 partion in inand.

boot faster,everything ok,Use feel very comfortable.
[G Tablet Android Development] GTO777:
I don't know if you all know about this, but i've used this on my vibrant and it rocks (conversion of rfs to ext4). They also have it integrated into clockwork to change the partitions back and forth on boot.

Maybe some of this can be applied here?

http://xdaforums.com/showthread.php?t=870480

http://project-voodoo.org/porting
[G Tablet Android Development] pcmtse:
Hi Rcgabriel,

Chenglu and us tested this CM and here are what we found so far.

1) we tried it and it backup ok

2) Upon restore, it can't recover properly on each partition. Use e2fsck to check shown many errors.

3) It does not back up boot and recovery partition

The backup file is ok and we just need to restore it mannually.

Will report back if we found anything more.
[G Tablet Android Development] rcgabriel:
Thanks for the feedback, pcmtse. Definitely could be some subtle issues there - I had a major failure of my G Tablet yesterday, bootloader stopped working for no reason and I had to use nvflash. Then the bootloader kept failing and had to re-nvflash every other boot. I was using my build of Clockwork Recovery 3.0 to restore each time.

I ended up having to revert back to Clockwork Mod 2.5.1 v0.8 and re-partition sd card/reformat as ext3 to get things back to stable again. I don't believe it's an ext4 issue since ext4 has run fine for days, so it seems like there are still issues with CWM 3 despite it appearing to work fine. So yeah, I'd stay away from CWM 3 until we get these things worked out.
[G Tablet Android Development] bigideasmb:
chenglu Thanks for sharing
[G Tablet Android Development] Dexter_nlb:
thats not his fault.. i made it like this as i have busybox in /system/bin on Folio :-) so its all correct (on my custom-rom)
[Nexus S General] SugarMouth:
I am trying my best to like this new keyboard but can't get used to it. I used to be able to quickly type on the old one but this new one is giving me issues. Is there a learning curve or something?
[Nexus S General] c_licious:
Yeah, it's called Smart Keyboard Pro
[Nexus S General] ryan562:
what google did was copy the keyboard from the droid x and just made the keys much smaller, which was their single biggest mistake and which explains some inaccuracy problems that people have been having, especially those with bigger/fatter fingers.

i use keyboard pro instead because i can adjust the size of the keys through the height adjustment feature. (yeah i have big hands/fingers). you can also adjust the multitouch sensitivity on it as well.

you can also download swype as an alternative from swype's website.
[Nexus S General] meetagrawal:
They need to make the space bar longer, and remove the period key. Pressing the space bar twice takes care of the period anyway.
[Nexus S General] jaker.the.skater:
I actually love the new android keyboard. I find it much more accurate than the froyo one. idk maybe its just me.
[Nexus S General] KidCold:
I agree with the spacebar being too small so i switched to swiftkey pro. If the spacebar was bigger i would switch back
[Nexus S General] Menace II Society:
Really? I always thought they copied the iPhone keyboard.

But I see the hint of Droid X in it. And some iPhone too. Only slight button changes along the bottom.
[Nexus S General] SugarMouth:
Ya I downloaded and that is a whole lot better!
[Nexus S General] brianbrain:
Ditto. Gingerbread keyboard is the best one yet, imo.
[Nexus S General] Menace II Society:
I agree. I don't have as much errors on this one and it's the closest one to the iPhone keyboard (which was my favorite). On that 3.5" screen I was able to type out long text messages in portrait mode.
[Nexus S General] onthecouchagain:
I think the oversensitivity of the Nexus S screen contributes to a lot of typoes and errors as well. Ever try holding your finger just above the screen, but not actually touching it? It'll register as a press. I'm sure when fast thumbs are glazing over the keyboard while typing, it causes mis-hits and repeated hits (like tthis or thiss - something that always happens to me). Oddly enough, sometimes the complete opposite will happen, when it doesn't register hits despite knowing I've hit the key (it'll have the popup preview). This happens especially with the keyboard (resulting in ths or tis, or things likethis). All annoying.

I've always been very critical of the Android typing experience. It's one of the few sore spots of the Android experience in general. Gingerbread stock is without question better than previous iterations, but it still pales in comparison to typing on an iPhone (or even an iPod touch). Anyone who has typed extensively on one would know the difference. I'm sure it's a combination of both hardware and software that makes it so successful; I can type with utter confidence on an iPhone/iPod Touch.

I wish I could say the same for Android. I'm hoping Blindtype will be implemented soon and change all this. I'm also hoping they'll grow a brain and depart from Apple by including features like Custom Auto-Correction. Until then, alternatives help. The new "optimized for Gingerbread" Better Keyboard 8 is quite good. Smart Keyboard Pro is good too (love the Custom Auto-Correction feature).
[Nexus S General] ryan562:
yeah moreso the droid x then the apple one, check the pic out. i always used the droid x apk on my older android devices and i thought this new one would be the same or an improvement. i guess i thought wrong but hey that's just my opinion.
[Nexus S General] SugarMouth:
The 2.3 keyboard is just too small. Measure it to smart keyboard or swift key and you will see what I mean.
[Nexus S General] n1ggyn1ce:
I'm using swype and love it.
[Nexus S General] Smokexz:
I use it, I have to admit... I am still learning how to hit the keys just right. However, it is an amazing keyboard, love it.

Sent from my Nexus S
[Nexus S General] j.bruha:
Adding a vote for the Gingerbread keyboard too. Everytime I have to go back to the Froyo keyboard on friends' devices or my work phone, I find it much harder to type on than my Nexus S. I used to always need the haptic feedback turned on with the Froyo keyboard too, but I haven't bothered turning it on with this keyboard.
[Nexus S General] jwr2d2:
I like the gingerbread keyboard. I type a wee bit faster than I did with the froyo KB.

Sent from my Nexus S
[Nexus S General] mmague:
I'm also in love with the new Android keyboard. It may be smaller but it is more accurate than froyo. I don't have the biggest hands in the world but my hands are not small either.
[Fascinate General] neh4pres:
If you're running voodoo 5 and decide to go back to stock and unroot.. Would my warranty be good? Or would verizon know?
[Fascinate General] Poloasis:
If you odin back to di01 and if you clean all the folders from your sd. I don't see how they would know.
[Fascinate General] Powell730:
+1

they wouldn't be able to tell as long as you odin back to *di01* and clean your sd card. if you odin to dj05 you will be SOL though seeing as that DJ05 isnt out.. just make sure you ODIN to whatever verision is out at the time you return your phone.
[myTouch 4G Android Development] option94:
I take no credit for this other than building it and uploading it. This is 100% based off of code from Team Douche. Special thanks to cyanogen, Zinx, and Kmobs for giving us such great code to work with. Special thanks to Gridlock32404 for all the help he's provided me with android in general.

This is basically the same as the CM7 Alpha roms, but with all of CMParts and CM Settings removed.

http://www.multiupload.com/DU6VR2OMH7 (GingerBaked)

http://dl.dropbox.com/u/16719351/gapps-newmarket.zip (gapps)

http://dl.dropbox.com/u/11228290/recovery.img (ClockworkMod 3 Recovery)

If you haven't already been running a CM7 Alpha, you'll need to manually flash a new recovery image since 2.3 based roms are not compatible with the current recovery found in ROM manager.

Download the recovery image posted above, and flash using fastboot.

$adb reboot bootloader

$fastboot flash recovery /path/to/recovery.img (replace path/to/ with the actual path to where you downloaded the recovery image)

If you'd rather flash the recovery from the emulator follow http://xdaforums.com/show...&postcount=361

once you have the new recovery, install the ROM through recovery as you normally would. You'll need a full wipe. After flashing the ROM, you'll need to flash the gapps posted above. Thanks to Grankin01 for putting those together.

Also, if you decide to go back to a froyo rom, you'll need to flash the old recovery. If you need help flashing the recovery,

check this thread: http://xdaforums.com/showthread.php?t=852905

Also, if you are having trouble with adb/usb drivers check out the below thread by b16a2smith

http://xdaforums.com/showthread.php?t=896206

Known Issues for this ROM are the same as all of the current CM7 alpha builds.
[myTouch 4G Android Development] sykopompos:
First post!
[myTouch 4G Android Development] option94:
lmao!!

10char.
[myTouch 4G Android Development] stlouie65:
Really... I'm gonna give this a try, I'll be back with what I find
[myTouch 4G Android Development] option94:
Awesome. Let me know how you like it.
[myTouch 4G Android Development] stlouie65:
Yes Sir, will do.
[myTouch 4G Android Development] aznpr1de808:
YAY more crack flashing :D
[myTouch 4G Android Development] stlouie65:
Flashed, booting up now
[myTouch 4G Android Development] aznpr1de808:
same here :D
[myTouch 4G Android Development] bobsbbq:
Wow thanks for this. And this is the real deal, proper credits and all. Unlike some previous ones. Will be flashing this one soon.
[myTouch 4G Android Development] stlouie65:
After initial boot, this ROM boots quickly. I did attempt to open the wifi calling, just opened and closed. Gonna load the rest of my apps and test the camera
[myTouch 4G Android Development] option94:
The lack of credit is why I put this together in the first place.
[myTouch 4G Android Development] Jaskwith:
So if the issues are the same and what not and its just cm parts removed, what are the benefits of this vs cm7 ...?

Sent from my MT4G running Gingerbread :)
[myTouch 4G Android Development] aznpr1de808:
well obviously its for people who want a more original themed GB rom instead of having all the CM stuff.
[myTouch 4G Android Development] pgarza:
what can we expect from this ROM that would differ from the other CM7 thread? i dont understand the necessity of fragmentation on a particular ROM unless each iteration has its own unique features that sets it apart from the next...
[myTouch 4G Android Development] stlouie65:
It's being checked out now
[myTouch 4G Android Development] HeavyComponent:
So basically this is just like the first CM Alpha that was released, but just with recent stuff? I remember the first Alpha had no CM stuff.

Sent from my HTC Glacier
[myTouch 4G Android Development] bobsbbq:
It is very simple. This is a close to AOSP ROM with CM base and Framework, just all the CM stuff removed. So you get a more pure Gingerbread feeling ROM like the Nexus S shipped with. Obviously it is not compiled on the original source yet but you get the same kind of experience.

Everybody has different taste. This is more of a very light ROM
[myTouch 4G Android Development] stlouie65:
Appreciate this very much Bob, it's running smooth, still configuring my apps so I can run a fix_permissions to get all right
[myTouch 4G Android Development] RavenWulf:
from what I've read it appears it would be like Running eVil D's MT4G-G2 ROM as opposed to CM 6.1.2 RC2.

GingerBaked and MT4G-G2 = Pure Vanilla Android

CM 7 and CM 6.1.2 RC2 = Tweaked / Modded Vanilla Android
[EVO 4G Themes and Apps] jager87:
is there anyone that has made or can make some sort of MMA or ufc type theme

would be greatly appreciated

thanksoh and if its needed im running mikfroyo's custom rom

just not sure how themes work and such so i figured i would ask
[Android Apps and Games] metalmoot:
Hi evryone, I'm crazy about xda and I wanted to install xda app but when I want to launch this app, it load and says "this forum appears have deactivate tapatalk, please contact an administrator

I don't understand 'cause I see people using Xda app all days,

Have you got an Idea

thanks
[Android Apps and Games] missparker76:
Maybe you should report your bug here http://xdaforums.com/showthread.php?t=841646 ;)
[Android Apps and Games] PMGRANDS:
HERE TRY THIS "XDA" APP!!

Credit Goes To Someone From XDA,

Wish I Could Remember Who!

Anyone Knows Post Him/Her Name!
[Windows Phone 7 Development and Hacking] lyriquidperfection:
I have looked on the Connection Settings Info page which can be found by dialing *#9920# into the Diagnosis App on my Omnia 7.

Here you will find all your MMS settings and some Registry settings are also listed but none can be changed unfortunately.

One particular Registry entry that caught my attention is the following:

HKLM\System\AutoDataConfig

RunADC 0

Now this tells me that the setting is disabled as the phone is branded but it would be interesting to see if anyone can successfully write to this registry key or not or whether it requires elevated permissions.

This could be the breakthrough alot of people have been looking for to enable MMS for people using other carriers sim cards without having to flash their device.