yashsingh1/xdaforums huggingface dataset:
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] mikembley:
Installed the kernel on sero7pro-aosp510-beta0-v1.2, initially seemed fine but then i started getting reboots without warning regularly, so i thought i'd go back to the previous kernel but that lead to a weird situation, my home screen would not initialize properly .

Screenshots showing missing homescreen, none of the other parts of the UI would work either: Screenshot1, Screenshot2

I should have gotten some logs, but it totally slipped my mind and I rushed on to recovery to reinstall.

I wiped, then flashed sero7pro-aosp510-beta0-v1.2 which lead to a hang on the bootanimation (even after a couple hard resets), but I managed to get a logcat with adb.

Currently trying another wipe and flash, see if i can get back to basics, will post update.

Update

Looks like my usb gamepad scares the crap out of running services, I caught this logcat:

Sideupdate

I've been trying to get my Retrolink SNES Controller to work, and apparently it shares the same vendor/product id as the NES version. Thankfully the buttons share similar mappings. Just the SNES controllers X/Y and shoulder buttons would not work. So i added the extra buttons and i'm assuming the NES version would still work since the mappings for the buttons still exist. Vendor_0079_Product_0011.kl
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] LNRrgB:
I tried the beta kernal, but could not reboot. A powering off pop-up shows itself at random points during boot. Seemed to almost make a full boot once, or twice, when I started doing different button pushes, and screen touches..... mostly hopeful thinking, I expect.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] jachol:
Problems.

Hi,

I've been using the experimental kernel ... all seemed OK for 2-3 days, until after a long session I found I'd run the battery level lower than normal (12% or so indicated) ... on connecting the charger there was a red USB plug animation on screen (not sure if this is normal, I've never seen it before).

After a few hours charge all seemed normal, although I wasn't seeing the charge animation, and sometimes connecting the charger caused the the tablet to boot, reported battery stats were haywire, and seemed meaningless. I was also seeing the message below (screenshot) on each bootup

I decided I'd better reflash the stock kernel, the battery indicator in the notification area looked good, so I tried to boot recovery only to get a red flashing message saying any update flash wasn't allowed as battery was too low, so as you'd expect I gave it another charge (3 hours +). Tried recovery again, same message as before (Oh shoot !).

I finally got into recovery by booting with charger connected, and disconnected charger once booted, in Philz battery showed 23 %, took a chance and flashed the stock kernel, followed by a recharge.

This AM, bootup OK apart from still seeing screenshot message, battery stat reports are normal and showing a full charge, and so far tab is behaving.

Dopa I don't know if the above is down to the experimental kernel or maybe an overdischarge on my part, certainly battery state reports seemed unreliable, and I'd say that battery charging was screwed up. ... Hope you can make some sense of the above.

I have the Sera7Pro UK model. ... J.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] dolorespark:
Experimental Kernel - dopa5 beta2

I've posted a new version of this experimental kernel for use with Lollipop (Android 5.x) ROMs. All battery-related issues should be resolved and everything should work as expected.

However... this is the first kernel I've built using gcc 4.8, so expect the unexpected (all previous kernels including beta1 were built using gcc 4.7). This is also the first dopa kernel to support overclocking a version of the Tegra3 chip that appears to have been used in later production runs of the US model (and possibly others as well). If you've never been able to o/c before, this kernel may enable it (I'll backport this support to the dopa1 kernel soon).

Thanks for the reports so far - and my apologies for any difficulties you've encountered. One thing worth noting: if you run into problems booting or running this kernel, force the tablet off, disconnect any USB attachments

and

remove any external SDcard, then try again.

sero7pro-aosp5xx-boot-dopa5-beta2.zip - experimental kernel beta2

sero7pro-aosp5xx-boot-dopa1.zip - "stock" kernel used by DoPa Lollipop ROMs
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] jachol:
New kernel installed OK ... initially I was seeing the message posted earlier, this resolved itself after a couple of reboots,

Battery stats are reading normal, and are compatible with pre-flash figures, tab has been running approx 6 hours since reflash with some on/standby use ---battery drain seems normal AFAICT.

looking good so far. ... J.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] dolorespark:
AOSP 5.1.1_r4 - DoPa5 v1.2 beta2

Yet another beta... This time, the latest release of Lollipop.

This version doesn't appear to have many changes from previous 5.1.1 releases, and installs the same dopa1 kernel used in v1.2 beta1. If you prefer to live dangerously (kinda), install the dopa5 kernel beta after the main ROM. Either way, don't forget to install Gapps. There's no need to wipe anything if you have another version of Lollipop installed. If you do a wipe, though, you may want to wait to install Gapps until after you've booted the new ROM once. Doing so will prevent the Setup Wizard from running and possibly hanging while it looks for a connection.

This beta also doesn't have any changes of mine - which is why it's still a beta. While a few users have reported getting "process System is not responding" popups at start up, I've only seen that once. However, every time I boot I can see that SystemUI gets killed then restarted: the status and navigation bars appear, disappear, then reappear before the lock screen shows up. While this shouldn't happen, I don't believe it has any effect on performance thereafter. I plan to investigate the cause, and hopefully fix it before the final release.

sero7pro-aosp511-beta2-v1.2.zip the full ROM

sero7pro-nexus7spoof-beta2-v1.2.zip identify tablet as a Nexus7 to (possibly) show more apps in PlayStore

sero7pro-philz6.58.0-dopa-v2.7.zip a customized version of Philz Touch CWM-based Recovery v6.58.0 usable on all versions of the Sero 7 Pro

pa_gapps-modular-nano-5.1-20150315-signed.zip a copy of the final Gapps Nano package for Lollipop v5.1

sero7pro-aosp5xx-boot-dopa5-beta2.zip - experimental dopa5 kernel beta2

sero7pro-aosp5xx-boot-dopa1.zip - dopa1 kernel used by DoPa Lollipop ROMs
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] sinnedone:
I'll definitely be playing with these in the next few days. Thank you

As far as system process being forced closed that's happened to me several times on lollipop but not on kitkat.

I tried going into recovery to fix permisions but thats

not an option.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] jachol:
New ROM + experimental kernel installed, all seems normal, but haven't had time to use the tab much.

Will see how things go. .. J
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] LNRrgB:
up 'n runnin'

Seems more stable so far...feels it.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] TheLoonyRebel:
This is weird. On the new beta I am getting low memory space issues despite having 5.5gb free internally and 50gb out of 64gb on my micro SD card. This is happening on both the stock and experimental kernel. Clean install. Even did an factory reset with no luck. :crying:

Edit: Okay did a fresh install of the ROM by itself then booted into the ROM. No memory space issues. Installed gapps (Aroma 5/25). No memory space issues. So it appears to be that there's more than just the one issue that's noted in the ROM notes for Beta 2 that's going on by installing the ROM and gapps at the same time.

Edit 2: ISSUE FOUND! Installed 5/14 Xposed Framework for 5.1.x zip in recovery and the memory space issue returned with this installed.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] ratyfu:
Same here. Also after flashing latest xposed.

Besides: I couldn't restore my backup in cwm. It failed on trying to restore /data.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] mobby_6kl:
USB DAC

So my USB DAC (MUSE X5 / PCM2704) arrived from China, and it sadly doesn't work with my Sero.

It's obviously recognized as sound stops playing from the speaker the moment it's connected, but I can't hear anything through the headphones. The volume buttons toggle between 0 and 100% volume but, again, nothing can be heard.

Otherwise it works perfectly fine with Windows and my OPO (still on CM11s), though there's also the same problem with volume being either "nothing" and "holy crap my ears!".

I'm probably not running the latest build, is this something that could've been fixed recently?
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] mikembley:
Seems stable so far, glad to see overclocks persist properly, good work!

I've been trying to search for a solution for getting USB Host API to work, nothing seems to be working.

Things i've tried

Adding permission files (android.hardware.usb.accessory.xml, android.hardware.usb.host.xml, tablet_core_hardware.xml) to /system/etc/permissions/

Selinux in permissive mode

I've tried to compile the kernel myself, but it a bit out of my league. I believe its because of gcc 4.8, so i gave up for now.

The USB Host API example works when i revert back to my 4.2.1 backup, but not in the current betas. I've been wondering what could have changed or lost along the way. Drivers? Something overlooked in kernel config? Incompatibility with UK version? Changes to OTG charging? Sorry for all of this, i've just been playing detective for a couple of weeks and it really doesn't help that some of this stuff is completely alien to me.

I would love to get this working so I can use my Arduino with my Sero, been longing to make a custom gamepad for it :) and other apps like DSLR Controller rely on it.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] dolorespark:
I looked into this and found that the USB section of audio_policy.conf, the file that tells the system how to route sound to/from various devices had changed. I'll include an updated version in the next release.

Meanwhile, if you're feeling intrepid, you can install the attached file yourself using ADB or a file manager. Unzip it and put it in '/system/etc'. I'd advise renaming the original so you can restore it if needed. If using ADB, don't forget to use the 'adb remount' command to make the /system partition writable. Using either method, you'll have to ensure the file permissions are correct or Android will reject it. As seen from a directory listing, they're 'rw-r--r--' (owner: read/write; group: read-only; other: read-only - from a command prompt 'chmod 644 [filename]').

I ran chainfire's USB Host Diagnostics and am puzzled by the results. My first attempt failed due to SELinux permissions issues, so I repackaged the kernel as "permissive" and reran it. It tells me that the kernel recognized the device but Android didn't. It's not at all clear what Android (or the test app) is looking for.

The device I used was a Broadcom Bluetooth dongle (connected via an OTG cable) that presents itself as a USB keyboard, USB mouse, and USB BT interface. Android definitely recognized the keyboard and mouse, and added them as input devices. However, based on a logcat, it didn't do anything with the raw Bluetooth interface.

Perhaps if I read the article you cited, I'd understand better understand what's going on :o It's 2:45am now, so I'll defer that until tomorrow, then get back to you.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] mikembley:
Thank you for taking the time to look at it. I found some more reading material regarding the host api, again i'm not well versed in the android/linux ecosystem so i'm just prodding around looking at things and possible causes like an innocent bystander :)
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] dolorespark:
Thanks for that. If nothing else, it had a sample code for an app that shows what's attached via USB. Even better, it had a precompiled version so I didn't have to build it :) Here's the link: sample apps.

If you want to try it, open the zip and extract 'tab.apk' which is in the '/Ch02/CH-2_Examples/usbview/bin/' directory. Install it from an SDcard or use 'adb install [path-to-apk]'. Every time you plug in a USB device, the os will show a pop up asking if you want to let 'USB View' open the device. Tap 'OK' to open the app, then tap on the vendor id/product id on the left to see the details (which probably won't be meaningful to you).

The app demonstrated to me that Android

does

recognize miscellaneous USB devices, though it doesn't necessarily know what to do with them. I tried a USB card reader, the Bluetooth dongle I mentioned previously, and a USB headphone/mic adapter I've had kicking around for years but never used before (sadly, Android didn't know how to use it though Ubuntu did). Further, entries in my logcat clearly attest to that, such as this one when I plugged in the audio adapter:

D/UsbHostManager( 475): Added device UsbDevice[mName=/dev/bus/usb/001/004,mVendorId=3468,mProductId=12,mClass=0,mSubclass=0,mProtocol=0,mManufacturerName=null,mProductName=C-Media USB Headphone Set ,mSerialNumber=null,mConfigurations=[

All this makes me wonder what chainfire's DSLR and hostmode test apps are doing that prevent them from finding and/or manipulating your camera. You may want to try replicating my experiments then forward the results to him so we can find out whose code is missing what. If you do, also find out if he bypasses Android and tries to access USB directly at the kernel level. As currently configured, SELinux doesn't permit an 'untrusted app' to access a USB device, so that route is certain to fail without some changes to my SE policy configuration.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] dolorespark:
Holy Jumpin' Catfish!! Of _course_ it doesn't work for you and hasn't since Day 1 - "by design"!

All of the basic configuration files for the S7P were taken from the Nexus 7 (2012) device tree, then modified as needed by RandomBlame, and later, by me. One of those files lets you override any of a huge number of system settings including one named "config_usbHostBlacklist". It's there to keep the UsbHostManager from messing with internal devices connected by USB - a modem, f'rinstance. I guess that's how the 4G data version of the N7 had its modem connected because their config file - and ours - blacklists '/dev/bus/usb/001/'.

Given that '/dev/bus/usb/001/' is precisely where devices show up on the S7P when connected by an OTG cable, there was never any hope of getting your DSLR to work because the o/s was explicitly told to ignore it. Based on your testing and mine, it appears that Android handles devices it knows about (gamepads, flash drives, etc.) and gives UsbHostManager the leftovers, e.g. your DLSR.

If the test app worked for me, it was because I had recently cleaned up the aforementioned file and deleted that entry. It wasn't until I read your reply that I made the connection :o I'd like to say that it will be fixed in the next release but I don't know when that will be. I've been obsessing over startup problems in 5.1.1 and have yet to find the cause. Until I do, I can't see any reason to inflict it on others.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] mikembley:
This is great! Thanks for the explanations, I wouldn't have had a clue. I just wish i knew more about android/linux.

I think ill celebrate this news with a new dopa boot anim!
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] mikembley:
I forgot to mention, in the latest beta I've caught the sero rebooting without warning.

I'm not sure how I could provide relevant details, as it doesn't seem to be reproducible.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] dolorespark:
Me too...

Here's one that is reproducible: attach any OTG device then let the tab go to sleep (i.e. "Daydream" not enabled) - it will reboot after about 30 seconds. I believe this is caused by the beta kernel
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] mikembley:
Now you mention it, it did seem like it would occur a lot more when i was trying to get OTG to work. Do you know if there's anything that might be logged before it reboots, my idea was to keep logcat up until it reboots and see what happened before it cuts off.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] boonesmi:
what version do you recommend? the one from the OP? or is one of the recent betas preferable?

i am about to retire my sero7 and give it to a niece. no one in that family is tech savvy at all.. and the tablet will probably spend the rest of its life with the rom i install.

anyone have suggestions or recommendations?

as a note: ive not used the tablet much lately, and when it was my daily driver i ran it mostly ran kitkat roms (mostly omnirom, and aosp)
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] dolorespark:
I'd recommend my last Kitkat ROM (v2.7).

Reformat /system and /cache using ext4 but format /data with f2fs (f2fs takes more space but provides better long-term performance). Install the ROM and a very minimal Gapps - get the rest of the Google apps (if any) from Playstore. Turn off the power-hungry stuff like NFC, GPS, and excessive WiFi scanning.

Finally, enable a few select GravityBox tweaks: battery charge percentage on the navbar, perhaps the reboot option on the power menu (not Recovery though), and my favorite, swap the Vol Up/Down buttons when you rotate the tablet.

Oh... one more thing: install "Koi Pond (free)" live wallpaper - most people are taken with seeing goldfish swimming around on their tablet. That was the sole reason I bought my first tablet :)
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] CanuckinPA:
I flashed 5.1 and it appears to be working just fine. Thanks for the great ROM.

Just one thing that I seem to be missing is the advanced power menu. Do I need to install Gravity Box to get it back?

Also, when I close a screen there's a message at the top of the home screen that says "can't install widget". ???
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] enfermo:
and a very minimal Gapps the post for the Gapps pack is close

Can any one pls tell me where to download the mini pack?

Can some one Pls tell me how to Turn off the power-hungry stuff like NFC, GPS, and excessive WiFi scanning

Thx for your time and help
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] jachol:
Go back to post #219 , it's all there if you read through the thread. ... J.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] dolorespark:
In the Settings app, select 'Performance' - there's a checkbox to enable reboot options on the power menu.

Hmmm... I haven't seen or heard of this problem. Any idea of what it's trying to install?

TKruzze is back and repackaging Gapps - they're now known as "TKGapps". See this thread.

All of the following are in the Settings app:

* WiFi scanning: on the 'WiFi' screen, tap the menu icon in the upper right corner, then select 'Advanced'. Turn off the options to notify when an open network is available and to enable WiFi scanning even when WiFi is off. It's up to you whether you choose to leave WiFi on all the time or have it turned off when the tablet is asleep (I'm at work right now, so I can't give you the exact wordings for these options.)

* NFC: select 'Other' - the option to turn NFC on/off is on that screen

* GPS: select 'Location' - you either just switch it all off, or you can leave it on and select the "battery saving" option which uses your IP address rather than the built-in GPS receiver.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] CanuckinPA:
Thanks --- I knew there'd be a checkbox or setting. Just couldn't find it.

As for the can't load widget message -- I have no idea what is trying to install. :confused:
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] enfermo:
Thx I Find the mention settings and tun off the items

So is my hope the battery will last long

Thx for your Time
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] dolorespark:
AOSP 5.1.1_r4 - DoPa5 v1.2 beta3

This is a beta that really

does

need testing: it has some major improvements, and likely some significant flaws.

Miracast (a.k.a. "screen cast") now has sound! Sadly, it continues to lock up the tablet when you disconnect, requiring a reboot. More significant, Chromecast should also have sound now. Update: I find that if I tell the TV to disconnect from screen mirroring, the tablet continues to work OK - for me, the lock ups only happen if the tablet initiates the disconnect.

USB Sound appears to work. My USB headset dongle gives me louder and better quality sound that the built-in headset jack. This feature should also support USB input (e.g. a mic) but I have no way to test this.

USB Host mode should be fully functional. Apps that support USB devices Android doesn't recognize (e.g. [MENTION=2248375]mikembley[/MENTION]'s DSLR camera) should work as expected.

There are also some smaller tweaks: references to the Nexus 7 dock are gone as is the outdated power widget on the home screen. I've also made it easier to pull down the Quick Settings panel.

As to potential problems... I've restored the "low memory killer" settings to their lower, Kitkat-era, values. This could mean that recently used apps reopen faster, or it could mean that new apps lag badly when started. Also, SystemUI continues to crash for me on almost every reboot due to an ANR. I've spent literally hundreds of hours on this and still have no real idea why. Please let me know of any new or unusual problems you encounter (

after

you've rebooted at least once since the initial install).

Oops: when using an HDMI cable, the sound comes from the tablet, not the TV. Here's the fix:

sero7pro-hdmifix-beta3-v1.2.zip route sound to the TV when using an HDMI cable

One last thing: this beta uses the original dopa1 kernel. Until I figure out why the tablet reboots if it goes to sleep with a USB-OTG device attached, I can't recommend its use.

sero7pro-aosp511-beta3-v1.2.zip the full ROM

sero7pro-nexus7spoof-beta3-v1.2.zip identify tablet as a Nexus7 to (possibly) show more apps in PlayStore

sero7pro-philz6.58.0-dopa-v2.7.zip a customized version of Philz Touch CWM-based Recovery v6.58.0 usable on all versions of the Sero 7 Pro

TK Gapps a link to the new "TK Gapps" thread here on xda-developers
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] CanuckinPA:
I'm still getting the 'can't load widget setting' every time I close an app and go back to the home screen.

Something else that I'm noticing....it takes almost four minutes from power on to boot up to the lock screen. When I swipe the lock screen I get a toast that says Apex Launcher is not responding while the home screen loads in the background.

Is this an unusually long boot time?