yashsingh1/xdaforums huggingface dataset:
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] ziddey:
I almost want to say that there definitely seems to be improvements with using f2fs over ext4 beyond a placebo, but again, I've barely played with the device beforehand. In fact, I flashed straight to this rom upon booting it up for the first time.

I'll give nvcplsvc.apk a shot, but it looks like it helps tweak whatever kernel settings are already there (smartdimmer is enabled by default, and is why the backlight goes out with too low a "regular" brightness).

As well, I noticed some screenshots of Antutu on stock roms reporting 900 for storage IO, vs most results for this rom are at 600 (I did manage over 1100 with f2fs though!).

I haven't seen any errors being spit at me in dmesg for using the sepolicy I stole from twrp, so it seems to be a success. Glad to hear it's been committed upstream already. The only concern is that I'm not sure how to implement fsck.f2fs if needed, although I've read it only detects errors but can't actually fix them, so what's the point..

Looks like nvcplsvc.apk is for specific 3d tweaks and power savings.

I swapped in libstagefright_httplive.so from tiktak r13 4.4.2 and it seems to be working well.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] x000x:
ParanoidAndroid, I forget what version but I haven't updated it in a very long time. Been too lazy :P but I guess this gives me the incentive to finally try something new out :)
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] jerbear294:
A port of Android L developer preview? :p
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] ziddey:
Anybody interested in testing f2fs, here's a boot.img (OC enabled) and hacked TWRP:

boot: http://d-h.st/iao

twrp: http://d-h.st/iJl

Flash via fastboot, dd in recovery, or create an update zip.

You'll need to manually format your data partition to f2fs. In recovery, issue:

# mkfs.f2fs /dev/block/mmcblk0p12

Just like it sounds, this will wipe /data and /sdcard, so backup..

Do not format /data via TWRP menu or it will restore back to ext4 and you will not boot.

Ramdisk uses sepolicy from twrp, which has f2fs policy.

Credit goes to [MENTION=4239374]ss2man44[/MENTION]: http://xdaforums.com/showthread.php?t=2634271

Note this is a test and is at your own risk. Know how to revert if things go awry. That said, it's been working well for me.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] ziddey:
Am seeing this as well. Not a router issue.

dmesg gets spammed with thousands of "qtaguid: iface_stat: stat_update() lo not found"

Eventually, wifi crashes and tablet needs to be rebooted, or it'll hardlock or straight up reboot.

Update:

FIXED

: From http://forum.odroid.com/viewtopic.php?f=78&t=5375

This works well, but qtaguid is needed for tracking throughput (e.g. that fancy status bar bandwidth meter included with Gravity Box).

The better fix is mentioned here: http://boundarydevices.com/second-release-jellybean-4-3-beta-mx6/ "The issue was caused by an incomplete patch set pulling in code from the AOSP kernel, and was addressed by simply cherry-picking patches to the netfilter drivers."

[MENTION=5094650]dolorespark[/MENTION], specifically, this commit is necessary: https://github.com/boundarydevices/linux-imx6/commit/ec99b775eb78b58a23db9af6009b02b3ad4abf7b

I made a build and have been streaming with Google Play Music for the past hour without a hiccup, and dmesg is nice and calm now.

Aside: I did see these sepolicy issues with wifi coming on, but it doesn't seem to affect anything? (I am using sepolicy from twrp so that might be responsible)

[ 37.652578:2] =========== WLAN going back to live ========
[ 37.671075:3] type=1400 audit(1406602595.610:4): avc: denied { relabelto } for pid=655
comm="d.process.media" name="cache" dev=mmcblk0p12 ino=669 scontext=u:r:media_app:s0 tcontext=
u:object_r:app_data_file:s0 tclass=dir
[ 38.033159:2] type=1400 audit(1406602595.970:5): avc: denied { getattr } for pid=671 c
omm="zygote" path="socket:[8457]" dev=sockfs ino=8457 scontext=u:r:untrusted_app:s0 tcontext=u:
r:init:s0 tclass=unix_stream_socket
[ 38.058284:2] type=1400 audit(1406602596.000:6): avc: denied { getopt } for pid=671 co
mm="zygote" path="/dev/socket/zygote" scontext=u:r:untrusted_app:s0 tcontext=u:r:init:s0 tclass
=unix_stream_socket

heh cache snuck in there

As well, any reason you didn't include a bootanimation.zip? I threw the one from my Nexus 4 on 4.4 (768p).

Anyone else not have working network location? I'm not seeing any sort of nlp partial wakelocks at all, and location doesn't work for anything (even wifi based location)
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] someguyatx:
I flashed this rom last night along with the NvCPLSvc apk and it's running great so far. I am not seeing the typical lag this tablet produces. I will report back after a bit more use.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] dolorespark:
FYI... thanks to [MENTION=584916]ziddey[/MENTION]'s efforts (and a bit of my own), I'm putting together a package that should make it easy to transition to the F2FS filesystem (no terminal stuff needed :) ). It's a back-port of a later version of the code than CM is using, along with some zips to do the dirty work plus a modified copy of CWM Touch 6.0.5.0.

Initial results are encouraging: with the help of a nandroid backup, I was able install it without losing any data, and Antutu's numbers look somewhat improved. It should be along "later" (staying up 'til 6am working on this hasn't helped my productivity).
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] ziddey:
Trying to figure out why network location isn't working.

379:W/LocationManagerService( 513): no network location provider found
380:E/LocationManagerService( 513): no geocoder provider found
381:E/LocationManagerService( 513): No FusedProvider found.
382:E/LocationManagerService( 513): no geofence provider found
1537:W/GCoreFlp( 997): No location to return for getLastLocation()
1545:W/LocationOracleImpl( 1028): Best location was null
2205:W/GCoreFlp( 997): No location to return for getLastLocation()

According to http://xdaforums.com/showpost.php?p=47137588&postcount=2266 some people have had luck adding NetworkLocation.apk

edit: Scrolled past these the first time, but they are way more important:

W/LocationProviderProxy-network( 513): com.google.android.gms resolves service com.android.location.service.v3.NetworkLocationProvider, but has wrong signature, ignoring
W/LocationProviderProxy-fused( 513): com.google.android.gms resolves service com.android.location.service.FusedLocationProvider, but has wrong signature, ignoring
W/GeocoderProxy( 513): com.google.android.gms resolves service com.android.location.service.GeocodeProvider, but has wrong signature, ignoring
W/FusedProxy( 513): com.google.android.gms resolves service com.android.location.service.FusedProvider, but has wrong signature, ignoring
W/GeofenceProxy( 513): com.google.android.gms resolves service com.android.location.service.GeofenceProvider, but has wrong signature, ignoring
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] dolorespark:
F2FS Support Packages

I've posted some packages that should make it easy to try F2FS ("flash friendly file system") on your /data partition - without losing any of your apps or data. On my tablet, I've seen a 25-50% improvement in Antutu's 'Storage I/O' results. If you decide it's not for you (or you find an unexpected bug), there's a corresponding set of packages to restore ext4 support.

Even if you're not interested in 'f2fs', you may want to install the 'ext4' boot zip because both boot packages should fix the problems people were having with streaming in Google Music. Similarly, you may also want to give CWM Touch v6.0.5.0 a try (especially if you like stuff that uses a LARGE font).

Installation

The steps for installing

and

removing f2fs support are identical - just use the appropriate packages:

make a nandroid backup to your

external

SD card

install the CWM zip

reboot back into Recovery

install the format zip

install the boot zip

restore your data (only!) using "advanced restore from /storage/sdcard1"

wipe dalvik-cache

reboot (ignore the "fix root" prompt - it's incorrect)

Notes

the two versions of the 'boot' zip are

identical

except for a single file ('fstab.m470') that tells the system how to mount the '/data' partition. IOW, the 'ext4' version has full support for 'f2fs' - it just doesn't use it. I'm hoping we can find a way to determine the formatting at boot time so that a single boot image can handle both formats.

the 'f2fs' version of CWM can mount your '/data' partition but it can't truly format it. If you try, it will just erase all the files. If you want a genuine reformat, you will have to use the f2fs-format zip.

these versions of CWM were pieced together from prebuilt versions for other devices, so I had no control over things like font size or formatting capabilities. At some point I expect to either build or "repurpose" a version of PhilZ Touch with 'f2fs' support.

IMPORTANT: when you have CWM reboot, it will claim that you've lost root and offer to fix it. This is incorrect. You have

not

lost root and can ignore the prompt. The pre-installed SuperSU will continue to work as-is.

Downloads

Install F2FS

sero7pro-boot-f2fs-dopa1-v2.1.zip - boot image with f2fs support

sero7pro-boot-f2fs-dopa1oc-v2.1.zip - overclocked boot image with f2fs support

sero7pro-cwmtouch-f2fs.zip - CWM Touch v6.0.5.0 with f2fs support

sero7pro-format-data-f2fs.zip - format data partition using f2fs

Restore EXT4

sero7pro-boot-ext4-dopa1-v2.1.zip - boot image with ext4 support

sero7pro-boot-ext4-dopa1oc-v2.1.zip - overclocked boot image with ext4 support

sero7pro-cwmtouch-ext4.zip - CWM Touch v6.0.5.0 with ext4 support

sero7pro-format-data-ext4.zip - format data partition using ext4

Credits

[MENTION=584916]ziddey[/MENTION] for having identified these useful additions and fixes
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] nccruz:
How do we know when f2fs is working?

thanks....
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] ziddey:
# mount
...
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data [B]f2fs [/B]rw,seclabel,nosuid,nodev,noatime,nodiratime,background_gc=on,discard,user_xattr,inline_xattr,acl,errors=recover,active_logs=6 0 0
...

Or more easily, if you've flashed the f2fs boot.img and you're able to successfully boot at all.

As for having a universal ramdisk, the easiest way would be to add an additional line in init.m470.rc to mount /data with the different fs. This would work, but would obviously spit errors to dmesg in either scenario.

mount_all /fstab.m470
# mount ext4 /dev/block/platform/sdhci-tegra.3/by-name/THD /thirdparty wait ro

I believe I read that TWRP goes the extra mile and checks the file system type beforehand.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] ziddey:
Alright guys, I managed to get network location provider working

Following the suggestion from http://xdaforums.com/showpost.php?p=43903590&postcount=2

I added com.google.android.location. Note, from my understanding, this may have been deprecated in kitkat if not earlier? However, until the stock fused provider is fixed, this should work just as well.

Modified framework-res.apk: http://d-h.st/X0l

In my research, I also came across this: http://xdaforums.com/showthread.php?t=2017043 which I think is pretty nifty. Just putting it out there

Now you'll also need NetworkLocation.apk. I found a link to one from http://xdaforums.com/showpost.php?p=47098364&postcount=183

This is from 11-02 PA_Gapps full, which to my knowledge was a 4.4 GAPPS?

Either way, push it to /system/app and voila. NLP is now working.

Say goodbye to any chance at decent battery life :p

Protip: Download Wakelock Terminator and set Google Play services (com.google.android.gms) -> Filter: NlpCollectorWakeLock

It has begun. Hello you piece of **** wakelock:

As well, GPS locks almost instantaneously assuming you're outside

:victory::victory::victory:

Update: Just a warning. I haven't enabled wakelock terminator yet since I wanted to see how bad it is. So far, while nlpcollectorwakelock hasn't been bad, there seems to be a real harsh wlan kernel wakelock now. Battery drain is now as horrendous as any other Android device now (real bad).
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] Gster09:
It took me a little longer than I'd hoped, but I finally got back to playing around with the tablet and this ROM. You were right in that my previous experience was an anomaly.

I did not really try to recreate the issues I'd had, but simply went through the installation process and had no issues this time whatsoever. I started by flashing the new CWM image with f2fs support and wiping /system, then flashed the following in this order: v2.1 ROM, format-data.zip, boot-f2fs zip, gapps, nvcpl, nexus 7 spoof, and an updated SuperSU. I then wiped dalvik-cache and rebooted with nary a problem.

Playing around with it for a few hours, I have not noticed any problems with WiFi, both games that hung up for me before are running well, and Dolphin is playing videos off Amazon Prime without issues.

Two things I'm still seeing. Llama still locks the GPS ON, no matter what I try, but based on a previous comment by [MENTION=584916]ziddey[/MENTION] I'm wondering if the app is locking into the GPS because it cannot get a network location off the Android Polling service. ?? * I'll try the modified framework apk and see if that solves it. * Also, I'm experiencing a little lag when using the back button and I wonder if the overclocked kernel would help. Trouble is, I'm not sure how to enable the OC kernel and not mess with the f2fs boot image. So I'll leave that alone for now.

Thanks for the tips, suggestions, and late nights you've put into this. ;)
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] ziddey:
Yes, I imagine the patched framework-res.apk + NetworkLocation.apk will help with your llama issues.

As for the lag, try removing nvcplsvc.apk. It seems to have brought a whole hell of a lot of lag my direction.

The OC kernel really doesn't do much of an overclock at all. It brings the CPU to T30 speeds (1.4ghz with 1.5ghz single core turbo). The flag for gpu overclock is also enabled, although I haven't verified if it actually does boost anything. If anything, it'd again only be to T30 speeds (520mhz vs 416mhz). Completely mild compared to what some kernels allow for other tegra3 devices. Unfortunately, the only OC boot.img available currently is my old one that doesn't have the patch for Google Play Music (it has a greater impact, but GP Music seems to be one that is severely affected). As well, I haven't checked to see if a different sepolicy was used than mine. All in all, I doubt that 100mhz would make much of a difference.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] dolorespark:
I'm glad it worked out OK this time. If you want an overclocked version of the kernel with F2FS support, wait a day (or two). I have all the pieces to put it together but I was just too tired to package it.

I have never seen any lag on this tablet before (I don't do anything really taxing) but have been noticing it lately. NvCPLSvc may be less useful than believed.

I inherited the OC settings from randomblame and never touched them since I'm deeply suspicious of overclocking. They may be sub-optimal.

If you want to see exactly what I've done with this ROM, look at my github repos. I just updated them to include everything I've released so far.

When you posted that logcat excerpt (which I've seen before many times), I suspected the problem might be in overlay/frameworks/yadayada. I was aware of the extra settings but since no one had mentioned any problems (and I don't care to have Google watching my every move), it was low on list of priorities.

Now that's a MAJOR improvement - and very high on my list. However, does it require that you be within WiFi range to get that instant lock? I will add the appropriate lines (there are more entries to be added than those shown in the cited postings) and try to find out.

I've had that README sitting on my Desktop for at least 6 months now. I had planned to use the overlay directory for my Phab7 Xposed module to add back various resources that many vendors leave out of their ROMs. However, while Phab7 was a great add-on in pre-KitKat days, it isn't that useful since they removed the Tablet UI, so I haven't pursued it.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] ziddey:
I think it's great the way it is. If anything, it could even be considered a "stock" offering, removing the gimping of the T30L and bringing it back to what it was supposed to be. Any "real" overclocking may not be worth the hit on battery life. Besides, it's not like +30% freq is going to touch any of the current A15 arch cores. Maybe if these chips really were something and could be overclocked while maintaining low/reasonable voltages and not easily hit throttling.. Eh, maybe I'll look into it, but it's not really that big a deal to me either. Did see that some folks have pushed to 2ghz though :p

I'm not sure on the intricacies of A-GPS, but I imagine the data remains available if disconnected from wifi? Either way, location behaves the same as all other Android devices now. GPS reception is still rather weak, but that's really more an issue with the device than anything else. I'll do some more testing in the coming days, but I'll be out of town for a while.

I'm not aware of the other lines, but it sounds like they might fix support for the fused locations apk? If so, the seemingly deprecated network locations apk would not be needed. As it is though, it's not spewing any errors at all and is working exactly as it should.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] nccruz:
I booted after install with no problem....did not try mount command..
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] dolorespark:
The overclocked versions are now available. There are links in the same posting as the other packages
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] Gster09:
Indeed. With the patched framework and network location.apk, Llama finally released its hold on the GPS. However, as you suspected, battery life went down the tube. I left the tablet sitting on my desk this afternoon and look what happened!

P.S. I'll try it without nvcplsvc and report back if I see a clear difference.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] ziddey:
hehe that's pretty typical of google network location and is how it is for every other android device. Which is why I find it funny when people complain of battery life when losing 2% per hour in standby. Look for the xda thread for betterbatterystats for the apk. See if nlpcollectorwakelock is a big partial wakelock for you. Somehow, it isn't for me, but I am now seeing outrageous wlan rx kernel wakelocks. Typically this means there's lots of network activity keeping the phone awake, and I did just flash the firmware on my router, so while I can't unconditionally blame it on nlp, I'd suspect that more than anything else (although again, the rx wakelock points at incoming data so...)

If you are seeing nlpcollectorwakelock as the culprit, it's an easy "fix" with wakelock terminator.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] Shahhere:
Guys,

I am not sure what I did wrong but am getting the following error:

Creating Symlinks

symlink: some symlinks failed

E: error in /external_sd?Download?sero7pro-aosp444-dopa-v2.1.zip

(Status 7)

Installation aborted

I installed the 2.0 rom sucessfully and then tried to put the 2.1 rom by wiping the data and then dalvik cache....

Please help.....If someone is on Gchat in the morning please help me "Shahhere" is my screenname.

Shahhere
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] Shahhere:
Okay, I can bring the tablet back to the Stock Rom state but as soon as I try to install the Dopa rom or any other for that matter I get he SymLinks error or the Meta error :(.

Shahhere
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] CyberManiaK:
Do a Google seach for "android status 7" you will get a lot of results that may lead you to solve it. The usual cause is when trying to flash something that is not made for your device.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] nccruz:
maybe download 2.1 again and try installing...
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] Shahhere:
That cant be, iwas able to put version 2.0 and now I cannot even install that. I have wipped and downloaded several times to eliminate bad flash and download issues. Kinda stuck right now, do have stock running and even ran the packeged recovery batch files......

Shahhere
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] Shahhere:
Okay got things up and running by reflashing Philz touch recovery so it looks like my CWM was messed up....

Shahhere
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] dolorespark:
GPS fix

Following [MENTION=584916]ziddey[/MENTION]'s lead, I've posted a package that should speed up getting a GPS lock.

sero7pro-gpsfix-dopa-v2.1.zip

This replaces a single file (framework-res.apk) and enables the tablet to use Google's proprietary network location feature rather than AOSP's. To get any benefit, you do have to have some Gapp package installed - as long as you have PlayStore installed, you're set. In addition to the GPS fix, this update also increases the minimum brightness level when Brightness is set to 'automatic', and changes the default for the Daydreams screen saver to 'enabled' when charging.

FYI...

Based on my testing (assuming I did things right), you

do

need to have Location set to 'high accuracy' and have a WiFi connection available - at least initially. Last night, after I confirmed that the fix appeared to work, I turned off the tablet, my router, etc. This morning, I tried the GPS before I turned on the router - as always, it took forever to get a lock. I then got my connection going and retried - I had a lock on 8 satellites within 15 seconds. Even after I switched to 'device only', I still got a fast lock. So, depending on your usage pattern, this fix may cure what ails you or it may do nothing useful.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] vettejock99:
FWIW I got this error a couple of times trying to flash Dopa with a zip I knew to be good because I'd flashed it 20 minutes prior as well. Trying a 2nd time fixed it. odd but true.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] nccruz:
do you just flash this on top of f2fs-dopa1oc-v2.1? thanks...
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] Gazoo119:
Initial impression is very good. On high accuracy I had a lock in 28 seconds inside. I went outside and had an accuracy of 13 feet. Turned GPS off came back inside and had a lock in 18 seconds. Rebooted and applied device only and had apx. the same results. We all know the GPS receiver isn't very sensitive but after applying your fix its working much better. There were times before this fix it would not pick up a single satellite inside. Thanks a bunch for this :)
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] Gazoo119:
You flash it like you flash anything else. Of course you don't need to wipe anything because its just a patch like the oc kernal.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] nccruz:
thanks... just what I did since I was not waiting too long... Backed up and flashed the update and it seems to be working as noted...
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] ObviousMan:
I apologize for being too dense.

If I do not go to f2fs and stay with ext4 (currently using 2.1 dopa rom), then beyond installing sero7pro-boot-ext4-dopa1-v2.1.zip do I have to:

1. switch from philz touch v6.0.5 CWM to the sero7pro-cwmtouch-ext4.zip?

2. format data partition using ext4?

What exactly does f2fs speed up, and what is at risk if one to install it? I understand it improves Antutu score, etc. In real use what gets faster - games, browsing, etc?

Thanks.

OM