[AOSP KRT16M] [v3.2] [5. Nov] 4.4 STABLE / Android 4.3.1 STABLE [Kernel 3.4.67]

[shoey63]

Thanks for your efforts @pabx :thumbup:

Sent from my C6603 using xda app-developers app

 

[samuelhalff]

To me, this is the only interesting project after FXP for the Z.

Nothing beats Swiss engineering .

Thank you. Keep it up pabx.

Thanks for your efforts @pabx :thumbup:

Sent from my C6603 using xda app-developers app

 

[jervine]

exFAT support?

Just flashed this, and noticed there is no exFAT support compiled into the kernel. Is this something that can be added easily? The email app is quite useful for some people - for the Exchange ActiveSync support for corporate email accounts.

Other than the above - really nice job on the ROM though. Feels like a Nexus device.

 

[pabx]

Just flashed this, and noticed there is no exFAT support compiled into the kernel. Is this something that can be added easily? The email app is quite useful for some people - for the Exchange ActiveSync support for corporate email accounts.

Other than the above - really nice job on the ROM though. Feels like a Nexus device.

You can cross compile https://github.com/rxrz/exfat-nofuse with this patch:

diff --git a/exfat_super.c b/exfat_super.c
index 5175473..9eccc55 100644
--- a/exfat_super.c
+++ b/exfat_super.c
@@ -1543,7 +1543,7 @@ static void exfat_evict_inode(struct inode *inode)
                //mark_inode_dirty(inode);
        }
        invalidate_inode_buffers(inode);
-       clear_inode(inode);
+       end_writeback(inode);
        exfat_detach(inode);
 /*
        struct exfat_sb_info *sbi = EXFAT_SB(inode->i_sb);

But IMO there is no real reason to use exFAT on any android device: If you are using a large sd-card just use ext4: Android will share the filesystem via MTP anyway. Also note that the legal status of reverse engineered exFAT implementations is 'unknown'.

 

[_EriK_]

Hi! Thanks for this ROM , it's just amazing!!! Btw, is there any chance to implement T-mobile theme engine?

 

[jervine]

You can cross compile https://github.com/rxrz/exfat-nofuse with this patch:

diff --git a/exfat_super.c b/exfat_super.c
index 5175473..9eccc55 100644
--- a/exfat_super.c
+++ b/exfat_super.c
@@ -1543,7 +1543,7 @@ static void exfat_evict_inode(struct inode *inode)
                //mark_inode_dirty(inode);
        }
        invalidate_inode_buffers(inode);
-       clear_inode(inode);
+       end_writeback(inode);
        exfat_detach(inode);
 /*
        struct exfat_sb_info *sbi = EXFAT_SB(inode->i_sb);

But IMO there is no real reason to use exFAT on any android device: If you are using a large sd-card just use ext4: Android will share the filesystem via MTP anyway. Also note that the legal status of reverse engineered exFAT implementations is 'unknown'.

Fair point - decided to go with your suggestion of formatting with ext4 (once I've backed up the data on the sdcard). The reason I'd chosen exfat was that the stock ROMs had a module available for exfat, and that 4.2.2 seems to support it natively, whereas ext4 has not been supported on the sdcard. (I'll admit I'm lazy)

Thanks for making the sources available too.

 

[pabx]

Fair point - decided to go with your suggestion of formatting with ext4 (once I've backed up the data on the sdcard). The reason I'd chosen exfat was that the stock ROMs had a module available for exfat, and that 4.2.2 seems to support it natively, whereas ext4 has not been supported on the sdcard. (I'll admit I'm lazy)

Thanks for making the sources available too.

Sony ships with the 'Tuxera exFat' kernel driver. Tuxera has a contract with Microsoft so they are allowed to ship their own exFat implementation.
The code linked in my previous post on github is in a grey-area as Microsoft *requires* you to pay them in order to distribute exFat implementations.

The vanilla linux kernel (and AOSP) never included exFat support and probably never will.

 

[elspanish88]

Any chance of sticking this in a zip to install?

Sent from my C6603 using xda app-developers app

 

[jervine]

Sony ships with the 'Tuxera exFat' kernel driver. Tuxera has a contract with Microsoft so they are allowed to ship their own exFat implementation.
The code linked in my previous post on github is in a grey-area as Microsoft *requires* you to pay them in order to distribute exFat implementations.

The vanilla linux kernel (and AOSP) never included exFat support and probably never will.

Yeah, I"m happier to use ext4 (or other native Linux filesystem) as my desktop and laptop are Linux systems anyway, but as most (all?) stock ROMs don't support ext4 and I wanted support for file sizes greater than 4GB, exFAT was my original (in retrospect unwise) choice.

With a 64GB ext4 formatted SD card, it's not automatically mounted - listed as blank or has unsupported filesystem. I can mount the filesystem manually when connected via adb - although it seems that 'correct' way to do this in Android is to mount it somewhere and then use sdcard to 'remount' it in the location that the OS will actually use (sdcard seems to be similar to a bind mount but mounts via fuse in a way to remove permissions and case sensitivity).

The source for sdcard suggests this should work, so I guess I'm missing something somewhere else...

 

[pabx]

With a 64GB ext4 formatted SD card, it's not automatically mounted - listed as blank or has unsupported filesystem. I can mount the filesystem manually when connected via adb - although it seems that 'correct' way to do this in Android is to mount it somewhere and then use sdcard to 'remount' it in the location that the OS will actually use (sdcard seems to be similar to a bind mount but mounts via fuse in a way to remove permissions and case sensitivity).

The source for sdcard suggests this should work, so I guess I'm missing something somewhere else...

It doesn't get mounted because vold only expects fat32 sdcards. I hacked up a small patch and this makes the automount work:

http://pastebin.com/yM2aHhcG

However: You'll run into permission issues - setting a default ACL doesn't work as android apps will just override it with their 'more secure' umask.
So i guess yeah: The only real solution would be to launch the sdcard-daemon for the external sdcard.
CM has a patch for this: http://review.cyanogenmod.org/#/c/31215/ - but i wonder if it wouldn't be simpler to solve this in the kernel. (the sdcard daemon is just a big hack of google to simulate the old there-are-no-permissions-on-/sdcard behaviour)

 

[jervine]

It doesn't get mounted because vold only expects fat32 sdcards. I hacked up a small patch and this makes the automount work:

http://pastebin.com/yM2aHhcG

However: You'll run into permission issues - setting a default ACL doesn't work as android apps will just override it with their 'more secure' umask.
So i guess yeah: The only real solution would be to launch the sdcard-daemon for the external sdcard.
CM has a patch for this: http://review.cyanogenmod.org/#/c/31215/ - but i wonder if it wouldn't be simpler to solve this in the kernel. (the sdcard daemon is just a big hack of google to simulate the old there-are-no-permissions-on-/sdcard behaviour)

Yeah, I've spent today going round in circles to discover this as well. Android expects the sdcard to have no permissions and no case sensitivity. As a result, it's really not happy with an ext4 filesystem on the sdcard. The filesystem can be mounted within adb (and init.d support can be added to ensure this mounts during system boot). However, your'e right, the various applications don't like seeing the ext4 filesystem attributes. I've not figured out the syntax to pass to the sdcard binary to 'correct' this.

I was mounting /dev/block/mmcblk1p1 to a 'temporary' location, and then trying to use sdcard to mount this to /storage/sdcard1 via:
sdcard <temporary location> /storage/sdcard1 1023 1023 (where 1023 1023 are the uid and gid expected). But the sdcard binary just 'hangs', and although Ctrl+C would show the /storage/sdcard1 directory as mounted when 'mount' was ran - you couldn't actually browse the filesystem. so that was a no-go.

As a last resort I tried the ezymount app on the Play Store - and this really didn't work ... It could see the ext4 partition, but every attempt to mount it would fail, and to add insult to injury, a factory reset seemed to occur when I next rebooted my phone. Not fun. This is all caused by the ubiquity of FAT

 

[freerunner]

Awesome work @pabx

And greatest respect for you for keeping your source open.

Going to marry your device repos with my Primerunner project.

Feel free to pick anything you want from my repos vice-versa.

 

[pabx]

I had a look at the ext4 support today:

The CyanogenMod patch is a big mess, would require a significant amount of work to merge it into AOSP (CM10.1 is missing many 4.2 features in vold) and i simply do not like the sdcard-daemon-fiddeling.

IMO, a much better solution would be to add a new mount-option to the kernel that tells the VFS layer to represent all files with hardcoded uid:gid. This would be easy to do, but we still would need to fork vold() and we still would have to add support for each non-fat filesystem manually (fsck / mount calls).

But this still results in a complicated setup where the only benefit is to have support for files >4GB on an sdcard - and i do not think that this justifies the patch-mess.

Btw: UDF woulb be a VERY nice option (supported by all major operating systems) but unfortunately the linux implementation doesn't allow you to force the uid:gid for newly created files (you can tell it to 'forget' the UIDs on remount, but that doesn't help)

 

[Stony-D]

Hey pabx
Is your Rom based on the latest official Sony AOSP Workshop Rom?

 

[pabx]

Hey pabx
Is your Rom based on the latest official Sony AOSP Workshop Rom?

Workshop ROM? You mean the one from FXP? No:

This is based on Sonys c6603 device config and uses the Sony AOSP blobs.

 

[DesertHawk]

Anyone running this ROM please give me Settings.apk and SystemUI like ASAP. Even if you aren't flash it and give it to me. In return I'll give you a 4.3 Google Play Edition ROM. But I need these for cross checking.

How do you do that? Flash the ROM. Get any root file explorer. Go to System/App. Copy the two APKS to your internal memory. Upload it to DropBox or equivalent and PM me the link

Sent from my Sony Xperia Z using XDA Premium HD

 

[pabx]

Anyone running this ROM please give me Settings.apk and SystemUI like ASAP.

And what are you planning to do with them? There is nothing special about Settings and SystemUI in this ROM:

System-UI is compiled from the unmodified 4.2.2 sources and my changes for Settings are here: https://github.com/adrian-bl-yuga/android_packages_apps_Settings (and 100% useless if you are not using qc-fqd)

 

[Stony-D]

Anyone running this ROM please give me Settings.apk and SystemUI like ASAP. Even if you aren't flash it and give it to me. In return I'll give you a 4.3 Google Play Edition ROM. But I need these for cross checking.

How do you do that? Flash the ROM. Get any root file explorer. Go to System/App. Copy the two APKS to your internal memory. Upload it to DropBox or equivalent and PM me the link

Sent from my Sony Xperia Z using XDA Premium HD

You will give us the google play edition Rom from the Xperia Z?
I am dreaming? :fingers-crossed:

 

[DesertHawk]

And what are you planning to do with them? There is nothing special about Settings and SystemUI in this ROM:

System-UI is compiled from the unmodified 4.2.2 sources and my changes for Settings are here: https://github.com/adrian-bl-yuga/android_packages_apps_Settings (and 100% useless if you are not using qc-fqd)

For now im just playing around... Where ever it leads me too i guess. I ported 4.3 and it booted with FXP's 4.2 kernel so im surprised so im just going with the flow. Thanks bro

 

[Hellscythe]

For now im just playing around... Where ever it leads me too i guess. I ported 4.3 and it booted with FXP's 4.2 kernel so im surprised so im just going with the flow. Thanks bro

could you perhaps upload a test build for us in a new thread?