yashsingh1/xdaforums huggingface dataset:
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] dolorespark:
1) Nope. 2) Nope. The ext4 version is just a minor maintenance update - if you don't have any problems streaming stuff, don't bother doing anything.

It's supposed to provide a small speed-up when accessing your /data partition. That partition contains more than just "data". It holds: your downloaded apps & updates, the optimized versions of every app's Java code (i.e. 'dalvik-cache'), various system settings, your "internal SD card", and more.

My impression is that the real payoff comes later on. Many people report that their devices get slower and slower as their /data partition fills up and stuff repeatedly gets erased then rewritten - in other words, heavily used. Unlike ext4 which was designed for use on hard drives, f2fs was specifically designed for flash memory and avoids many of the issues that cause those slow-downs.

As to risks: it's nowhere near as tried-and-true as ext4, though it appears to have been tested extensively and has now been accepted as part of the Linux kernel. Another problem is that you're currently limited to this one version of CWM that supports it, though that's likely to change. From what I've read, at least some versions of TWRP support f2fs, though again from some of the bad stuff reported lately, I'm in no hurry to find out.

Overall, it's entirely optional. Your choice...
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] skinnydude:
I had this problem. I installed CWM Touch 6.0.5.0 and then it flashed fine after that.

I got the file from here

http://xdaforums.com/showpost.php?p=54496152&postcount=276
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] jamdev12:
I had the same problem too and I just rebooted the tablet back to recovery and it worked after the reboot. I don't know why this happens, but based on some comments it seems twrp has problems erasing as well as applying new Roms on this tablet.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] slicingtaco:
According to [MENTION=5094650]dolorespark[/MENTION] to fix the Google Play streaming we have two options 1) running his overclocked kernel @1.5ghz or, 2) convert the file system extension to F2FS?

Which one would be better
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] dolorespark:
None of the above. Any one of the four boot images listed in post 276 will fix the streaming issue.

FYI... I'm working on a solution that will eliminate the need for separate boot images for ext4 and f2fs. When done (and if successful), you should be able to format

any

of the main partitions (data/cache/system) with either filesystem and have the ROM handle it transparently. Whether we can get CWM to be as flexible remains to be seen...
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] slicingtaco:
Great Thanks bud. So what exactly was the issue in the kernel that made it have problems streaming through Google Play Music? I/O?
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] mkone5718:
Cast enabler (chromecast)

Has anyone got this to work on this rom?

http://xdaforums.com/hardware-hacking/chromecast/experimental-enable-mirroring-device-t2812193

I have installed this and the rom either crashes or connects with no sound. It also reboots the device. I would like to get this to work. Can someone else test and post their results?

Thanks!
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] mando41:
I tried but I always get a Google play services foreclose. I've tried downgrading Google play services, rebooting both phone and chromecast and clearing the chromecast cache. Nothing has worked so far. If anyone gets it to work please post how you did it.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] mkone5718:
Thanks for trying. I did all the steps you tried with no luck.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] mando41:
Do you know if this is implemented in the ROM?

Edit: reason I ask is because the OP in that thread said the app works for our device but this has to be added for it to work.

For those STILL having issues,

Check /system/lib/hw directory for the file "audio.r_submix.default.so".

If it doesn't exist, ask your device maintainer to add audio.r_submix.default to

the product_packages in the device.mk file. (You may not know what it means, but they will.)

EXAMPLE (Thanks, [MENTION=3900214]runandhide05[/MENTION]!):

http://review.teameos.org/#/c/389/
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] mkone5718:
I do see the "audio.r_submix.default.so" file in that directory. Still can't get it to work though...
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] mando41:
It would be nice is someone posted how they got theirs to work.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] ziddey:
Yes, screen casting does not work adequately. Audio is broken (perhaps the same reason it's broken for Miracast). It's generally laggy (compared to Nexus 4 and Moto G). And turning it off results in a soft reboot (which results in broken wifi among other issues). Regardless, screen casting is something that requires a deal more work anyway. Built-in casting from say Youtube/Google Play Music/Plex/WatchESPN all work fine, but that's obviously a completely different animal. Maybe I'll check the lolcat later, but either way, it's not something that's all too useful in my opinion (cropping / latency issues and whatnot).
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] dolorespark:
That's an understatement :) In AOSP 444_r1 (dopa v2.0), enabling audio for Miracast generated about 40 error messages a second, so I disabled it. Reading all these posts prompted me to look at it again. Edit: No change: a gazillion errors and it still doesn't work. If you want to play with it, see the note at the top of /system/etc/audio_policy.conf. I also tried swapping in various files from the Nexus 7 (2012), generally with unfortunate results. However, their com.android.media.remotedisplay.jar seems to produce less laggy results, so I'll use theirs in the next build.

Meanwhile, I continue to work on a one-size-fits-all bootimage for ext4, f2fs, etc. I've done 2 different implementations and they both work great for the OS itself. However, apps that try to use busybox to remount partitions all fail (e.g. Xposed Installer), so it's on to implementation number 3.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] Cellular-Decay:
Has anyone heard about this, and do we need a fix?

http://community.norton.com/t5/Nort...ke-ID-To-Access-User-Information/ba-p/1159356
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] paratwa53:
Just go to this website on XDA it has the fix.

http://xdaforums.com/xposed/modules...mcct=/sitesearch.php&__utmv=-&__utmk=30699452
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] rodos15:
Cast screen audio problem

Hi dolorespark, is this helpful?

http://xdaforums.com/showpost.php?p=54755323&postcount=1537
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] ziddey:
Just an update on this. I made the wrong assumption and the actual culprit was the mirror enabler app's fix fc function, which replaces the audio policy with a generic one known to work with mirroring.

In other news, for any Plex users, a new version has been released with a workaround (requires an updated media server as well) that no longer requires using an old version of libstagefright-httplive.so. It seems to work, although it does seem to stall out briefly once or twice before streaming smoothly. You'll notice the info now shows "Experimental" instead of "Native"

----

I saw this in logcat when initializing the mirror:

I/Converter( 987): using audio bitrate of 128000 bps
W/AudioPolicyManagerBase( 134): startInput() input 63 failed: other input already started
E/AudioRecord( 987): start() status -38
E/MyAudioRecord( 987): AudioRecord::read returned -3

With the last line being spammed quite severely.

I had Google Now's OK Google detection enabled, so I tried flipping it off. Now, the logchat shows:

I/Converter( 991): using audio bitrate of 128000 bps
E/r_submix( 131): no audio pipe yet we're trying to read!

With that last line being spammed, although at a slower rate (in audio_hw.cpp, it sleeps after this error). As expected, audio is still not working, and the device still crashes and soft-reboots on disabling mirroring.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] dolorespark:
This error confirms what I had already surmised was the problem with Miracast audio: the failure is in audio_policy.xxxx.so - in our case, audio_policy.tegra.so. Depending on where in there, it may be something that can't be fixed since we don't have the code. Still, there's one glimmer of hope: that "input 63". Is that number assigned on-demand and variable, or is it arbitrary and unvarying?

The reason I ask is that we used to get errors saying that "input 1999" could not be opened. While working on something else, I stumbled upon an explanation of what it is: an arbitrary handle used to identify times when the microphone input is being used for background speech recognition, i.e. "OK Google". Vendor implementations of audio_policy.xxxx.so are supposed to support it and route requests to the mic, but ours was too old. With that I knowledge, I located the point in the 'C' code where the request goes from logical (voice recognition) to physical (microphone), and replaced requests for handle 1999 to requests for whatever arbitrary handle is used for the mic. Voila! "OK Google" now worked.

Maybe, just maybe, some similar trickery will work with audio_remote_submix...
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] ziddey:
Unfortunately, it looks like it's variable (and only when ok google is enabled):

W/AudioPolicyManagerBase( 133): startInput() input 31 failed: other input already started

W/AudioPolicyManagerBase( 131): startInput() input 14 failed: other input already started
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] dolorespark:
Sero7Pro AOSP Beta v2.5

Yes, folks, there _is_ original development for the Sero7Pro :) Like many other ROMs, this beta offers F2FS support, but unlike any other ROM I know of, the choice of ext4 or f2fs is yours, not the developer's.

Format any of the main partitions (/data, /cache, and/or /system) either way using the companion PhilZ Touch (beta) and this ROM will handle it. Try f2fs on one or all partitions (or revert to ext4) at will - there's

no

need to flash a different ROM every time you change formats.

---- Edit ----

The final version of DoPa v2.5 has been released, so this beta has been withdrawn. See the original posting for details.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] Tool Belt:
Unfortunately won't be able to try it for a few days, but YOU ROCK!!

Thank you.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] DreadApex:
Thanks delores and ziddey for everything you've done for this great little tablet!

I am excited to try the f2fs partitions and have been waiting for this since you first got it working and announced you were working on a new rom package!

I don't encrypt my sero, so should I go full boar and format all partitions?

anyone do this and have anything to report?

I might just try it out and see if noone else has yet.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] ziddey:
Just a heads up: f2fs can end up costing quite a bit more in disk usage (I haven't looked into it much but figure it might have to do with the log based file system). This is generally not a problem, but if you choose to flash a complete gapps (pa gapps full), and format /system as f2fs, you will most likely run out of space. Further, it looks like the gapps install may appear to succeed, but of course, you'll end up running into all sorts of problems. I imagine most people opt for a slimmer gapps, so this isn't really a concern. Otherwise, Motorola's implementations so far only have /data formatted as f2fs. Since /system is read-only anyway, there most likely won't be any benefit to going f2fs there.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] cfp33pfc:
Sero 8?

I use 2.1 on my 7 Pro and love it! I picked up an 8 yesterday at Walmart. Any plans to work on that? So far it seems perky and the larger screen is nice, without the overall size being much bigger. Thanks!
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] unomar:
Awesome work yet again. I'm running the 2.5 beta with ext4 and it cleared up all the Google play music issues I had.

Thanks!
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] nccruz:
Just did 2.5 beta...

could not go back to recovery with volume down+ power with charger cable connected..... no prob with cable disconnected...could this be caused by Philz-Touch?
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] DreadApex:
This is normal for the sero 7 pro and has acted this way for as long as i've owned it.

I have been using 2.5 beta with everything formatted to f2fs for several days now.

I have swapped my external sd card with my internal sd card and have been testing the results...

It was a nightmare getting it to work correctly, the fuse links for the emulated sd card are a pain in the ass.

However, I have got it working and have ironed out all the kinks i have run into and so far am loving it!

I am able to install whatever i want in huge batches and don't even have foldermount or link2sd installed!

I am not noticing much difference in performance compared to the earlier build using ext formats, but i am also running a bunch of stuff straight of the micro sd now, as well as no longer running the overclock kernel.... either way, i'm loving the rom and loving all the extra space.

It has been able to run everything I have thrown at it, kitkat feels right at home on the sero.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] rodos15:
Can you post your changes here, e.g. your boot.img or just the fstab.m470 and the init.m470?

Thanks
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] ziddey:
Been playing with the kernel a little. Forced it to be treated as a T33 (1.7ghz single core, 520mhz gpu), and disabled EDP (allows all cores to run at max speed, although I believe this might kill thermal throttling..)

Now vs original oc

If anything, I'd love to get the ram up from 667 to 800, but for some reason, the emc clocks aren't taking.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] dolorespark:
So... has the plastic case melted yet? Do you have a fire extinguisher close at hand, just in case? Please don't destroy your Sero 7 Pro - we need your skills for more ..umm.. sober pursuits.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] paratwa53:
What Theme package works best with the Sero 7?

I am messing around with a few, but not really happy with the ones I have tried.

I am also wondering if I were to install something like Apex launcher, will that screw anything up with this ROM?
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] jerbear294:
Have you tried XThemeEngine?
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] paratwa53:
Not yet, going to try it next. Thanks!
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] jerbear294:
If you decide to stick with it, I highly recommend the Gem Flat XTheme :)
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] paratwa53:
I have not been able to install it, it keeps telling me I need to enable it in xposed, which I did, but every time I go to open it it keeps telling me to enable it in xposed then crashes.

"You need to click install/Update in Xposed installer and activate icon themer module in module tab"

I have uninstalled and reinstalled 4 times, each time enabling it in xposed modules (check mark) then trying to go into it and I get that message.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] DreadApex:
install the framework using the install button within the xposed installer, then enable the module, then reboot.

After that, it should work fine.

Also, apex works fine, along with every other launcher I have tried so far. go wild!
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] paratwa53:
I tried and tried, can't get past that error message.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] Gster09:
I think what [MENTION=5365855]DreadApex[/MENTION] is trying to ascertain, is if you installed/enabled the framework already.

Step 1: Select "Framework" on the Xposed Installer main screen

Step 2: Select the option to Install/Update.

You'll know when that's been done because there will be two green numbers listed under the "active" column. You'll need to reboot after that.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] paratwa53:
Yes it's installed and I have the green numbers.

I downloaded the APK for the xtheme from the website and clicked on it to install (sideloaded). It said it installed, but everytime I go into it it gives me that error message. It even shows up in Xposed modules and I clicked the check mark and rebooted. But still the error persists.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] paratwa53:
I found an answer over at the xposed faq posted by ANDR01DN00B

"Guys I have the fix: after you activate the module for the first time, reboot. After that open the app and when it gives you the dialog to open xposed ect,, just press your device's back button, select your theme, and apply it. "

Thanks for your help!
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] CarmelSack:
First thanks so much for this Rom, excellent.

Two minor problems. I have full rom, Standard Google Apps, and Nexus spoof installed.

My home button does not work, it lights up, recognized the press, just does nothing.

Similar to that, I can not pull down from the top right of the screen to get to settings.

Any ideas?
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] paratwa53:
Did this happen immediately after flashing the new ROM? Or were you messing around with some settings and then it started?

Try powering down the device (not a reboot) then power up, if that does not work maybe you will have to re-flash the ROM
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] CarmelSack:
Immediately after. I did a power down.

I'll have to try a reflash.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] paratwa53:
Try going to recovery and clearing the cache then reboot.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] CarmelSack:
No luck, just reloaded Rom, seems to be fixed.

Thanks
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] Gazoo119:
Just wanted to say thanks for this. Installed without a hitch. I have not re-formatted anything...don't feel the need to but I am sure others will appreciate the flexibility. Thanks again for the wonderful work you do!
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] Cellular-Decay:
So how is everyone feeling about Kitkat on the Sero?

I was using Delorespark's modded stock ROM (sero7pro-bld60220-dopa-v2.0) with tablet UI and I was very happy with it. But with all the hype about Kitkat I decided to give it a try, and so far I'm having very mixed feelings about it.

First, the lack of a tablet UI is a big dissappointment. How could Kitkat not have a tablet UI? This very well may be a deal breaker for me.

Second, the default system UI sounds, particularly the keyboard sounds, are terrible. Copied the JB sounds over to fix that.

The default browser in KK seems worse than the one in JB (crashes a lot). Nothing Dolphin, Chrome or Firefox can't fix, but still...

And finally, I had heard that Kitkat was a lot faster, but after using it for the past few days I'm not seeing any difference. This morning I flashed Davepmer's F2FS compatible TWRP and Delorespark's Sero7Pro AOSP444-beta-v2.5 with cache and data formatted F2FS to see if that helps.

Anyway... I'm wondering if I'm missing something. What do you all like about KK over JB?

Thanks for any and all input.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] dolorespark:
And a hearty "You're Welcome!" to you and everyone else who's offered their thanks (but don't forget to keep pressing that button ;) ).

The final version should be out real-soon-now. Since I released the beta, I've spent a ridiculous amount of time on this. Some of it was productive (e.g. more f2fs support in more places) and some of it was pointless. In particular: getting encryption to work.

I get the impression that people who flash custom ROMs don't worry about such things. However, you should be aware that the first time you reformatted your /data partition, you lost the ability to encrypt your Sero 7 Pro. The new version of Philz Recovery I'll be releasing will fix that: use it to reformat /data (either ext4 or f2fs) and you'll be good to go should your paranoia ever get the better of you.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] paratwa53:
With L coming out soon, are you going to be looking at that for a port? I am very happy with the offerings you have given us for this great tablet and I am not even curious about what L has to offer, so if you don't I am still one very satisfied user!
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] Cellular-Decay:
[MENTION=5094650]dolorespark[/MENTION],

Any particular reason you use Philzs Touch? I prefer TWRP over CWM. Its UI is much more polished and touch friendly. I'm using Davepmer's F2FS compatible TWRP along with your AOSP444 2.5 beta and seems to be working fine (with cache and data formatted F2FS).

Also, Xboxexpert had a cool circle battery mod for his ROM that I really miss. Any way to get that working with your AOSP444 build?

Thank you for all your efforts. You are amazing!

Aloha, Tim
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] ziddey:
Haha, I actually took the case off to take a look at everything. There's a cute almost-heatsink on the case, but it doesn't come close to actually touching the chip. A thick thermal pad would fill the gap, but I doubt there'd be any improvement in cooling.

I'm sure the interactive governor settings could be tweaked a little, but as is, I found it to be a bit too happy to online cores and ramp up frequencies. Ondemand seems a bit tamer.

Either way, I've re-enabled EDP for now (although it's far too aggressive, with the first threshold at 45'c). With less than 4 cores online, it can still ramp up to 1.6ghz. Of course, benchmarks aren't as dreamy, but it should perform comparably in real-world usage.

This commit allows user voltage control: https://github.com/faux123/Nexus-grouper/commit/bf3abaee513b05bc386f4386c76e7f28f5e943bf

I'm currently forcing a cpu process id 4 T33 and undervolting by 50mv across the board (1.162v max vs. 1.075v for worst-binned stock T30L). It's been rock solid so far, and in my opinion, much more reasonable of an actual "overclock"

As well, arch/arm/mach-tegra/common.c needs to have this variable bumped up:

static int pmu_core_edp = 1300;	/* default 1.2V EDP limit */

The non-neutered tegras use 1300 I believe (for 520mhz gpu et al)

That said, given the undervoltability (original gpu overclock implementation provides 520mhz while maintaining 1.2v for soc), the tables could most likely be adjusted and edp brought back down to 1200 for battery life.

Activate xposed and gravitybox. You'll find your circle battery there. Personally, I prefer the text only option