yashsingh1/xdaforums huggingface dataset:
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] isaacj87:
I assuming the extra keyboards got tacked on during the build process. You can remove them quite easily with ADB:

adb remount

cd /system/app/

rm OpenWnn.apk PinyinIME.apk

That will remove both the Japenese and Chinese keyboards.

I also found that GPS did not initially work for me. I used a GPS/Sat app and let it sit for 10 minutes. After it locked on, I never had another issue with getting a GPS lock in any other app (e.g. Google Maps).
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] MrSimmonsSr:
Thanks for the tip! I've never played with Mounts2SD before but it sounds like just what I'm wanting. In reading through the manual today I noticed it requires init.d support in the ROM. Does this ROM support that already or will I need to execute the Init.d Injector to try to make it work?

Anyone already using Mounts2SD with this ROM?

Thanks!
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] ALooneyGuy:
This ROM...

...is working like a champ for me. Great work!
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] MrSimmonsSr:
Well, sadly I seems to have run into a few stability issues with this build. I got it installed with the minimal gapps package and without the OC kernel and was really enjoying it! I had gotten it all set up just the way I like it with lots of apps and such. I'd even taken the advice of some here and installed Link2SD and everything seemed to be going well.

The only small issue I'd seen was a few spontaneous soft reboots when turning on or off wifi and Bluetooth services. Additionally I had seen the issue where wifi would refuse to come back on without a hard reboot.

Then last night something less pleasant happened. Specifically it happened once when I was turning off Bluetooth. The device soft booted and never came out of the boot animation. It was just stuck there and I was tired an dozing off. I powered it off and then back on, thinking maybe the kernel for forcing a check of the file system behind the animation and was about to go to sleep anyway so decided to leave it alone, plugged in, and see if it would recover. Just woke to find it still showing the boot animation. I powered it off and haven't touched it yet.

So my questions are these:

1. Is there any way for me to extract any data from it that could be helpful in debugging the issue?

2. Is there any chance that flashing the ROM again without wiping it might get me up and running again without me having to reinstall everything from scratch again? What that be a bad idea?

Thanks for any and all feedback/input/suggestions!

MrSimmonsSr

Update: I decided to boot into recovery (philz) and wipe my cache and davliks cache and see if that helped at all. Now when I boot I get the boot animation for a few minutes, then a "Android is upgrading.." message that says "Starting apps." After a few minutes it seems to be stuck there. I'll leave it for a while and see if it does anything else..

Update 2: That didn't seem to help. With that in mind, I'd appreciate it if anyone would share their thoughts on whether or not any useful debugging info is likely to be gleaned from my device in its current state. I'd like to get it back in working order with a wipe and reflash, but providing debug info is one of the few ways I can actually contribute anything useful around here, so I don't want to miss a chance to do that when possible.

I have taken a full backup from Philz recovery. Is that of any use to anyone?

Is there anything else I could/should do before reflashing that could be helpful?

Do you guys think it is worth it to try a dirty flash just to get up and running or is it likely better to bite the bullet and wipe everything for a clean install.

If it makes more sense to do the full wipe, is there anything I should format besides what is included in Philz "Clean to install a new ROM" option? I did seem to notice some cruft left over after my install last time I used that choice. Should I go in and force some further partition formats manually to get a truly clean system this time around?

Thanks for all input and advice!
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] jerbear294:
I'd say a dirty flash, then a clean flash if the dirty flash fails. Of that doesn't work then hook up your tablet to the computer while powered off and turn it on. When the boot animation starts up, run

adb logcat -v long > logcat.txt

This will save a logcat named logcat.txt in your ADB directory. Hopefully it gives us some info.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] MrSimmonsSr:
Thanks for the input, JerBear! I have done a dirty flash and the tablet came back up nicely. Once I re-ran Link2SD, rebooted and it came back up as expected..

Then I noticed that some of the tweaks I'd made with Gravity Box were not getting applied. So I ran the Xposed Installer and rebooted again..

And now I'm hung at the boot video again.. Me thinks I've found the problem!

I think what has happened was that I had the "Automatically move new apps to the SD card" option turned on in the Link2SD app, and then I installed the Gravity Box modules (and some others) for the Xposed installer. My guess is that having xPosed modules loaded on that other SD partition is probably a bad idea and that is causing some kind of a hang on boot up. Anyone who knows enough about Link2SD and Xposed know enough to say definitively?

I don't think this was behind the soft reboots I was suffering, but I do think it would explain why I was stuck at the boot video on the last one..

I will go flash dirty again, enable Link2SD, and then unlink all Xposed modules before enabling Xposed again and I'll let you know if that helped anything..

Thanks!

UPDATE: Well, it doesn't seem quite as straight forward as I'd hoped.. I was able to dirty flash again and then boot up.. I then ran Link2SD and let it install the mounting script and it worked fine on reboot.. Then I went into Link2SD and unlinked both Greenify and another module that had ended up linked onto my SD card.. I was hopeful that would allow me to enable Xposed without problems. Sadly it did not. The last time I re-enabled Xposed it got me stuck at the boot video again.. Strange.. anyone have any idea what might be causing that? It seems the tablet will work fine after a dirty flash with Link2SD enabled, but if I try enabling Xposed Framework again I'm right back in the same spot again.. I thought at first it had something to do with running Xposed and Link2SD together and letting some Xposed modules get moved to SD by Link2SD, but that doesn't seem to be the case after all, from what I can tell..

Any ideas?

UPDATE 2: One more bit of info. The boot loop that leaves me stuck in the boot animation definately seems to be related to the Gravity Box module, or some other Xposed module. I can enable the Xposed Framework with no modules turned on with no issues, but as soon as I enabled Gravity Box and rebooted, I was stuck in the boot loop again.. I will leave it alone until I get home and see if I can grab a logcat while it's in the loop. Maybe that will tell us something about what is going on. I saw a few other posts that mentioned something about file permission issues causing boot loop problems with Xposed before, so maybe that is what is happening here..

Thanks!
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] jerbear294:
I have been getting SODs on PAC so I flashed this- oh God, it's so stable!

I've got a new daily driver.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] Gazoo119:
Yes it has been totally stable for me too. So how about building PAC off of this? Is it possible?

---------- Post added at 05:33 PM ---------- Previous post was at 05:16 PM ----------

The only time I had problems with this ROM is when I attempted to set the min/max auto brightness settings in gravity box. The tablet did not like that and it got stuck on the android screen and I had to reinstall the ROM.

When I installed v1 of this ROM I also wiped data/media as that was posted in the instructions in the op. Just be aware all data will be wiped if you do that. Other than those things I don't know why you are having so much trouble.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] jerbear294:
The closest I can get is using Dolorespark's kernel tree- PAC only works with CM trees, not AOSP ones.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] MrSimmonsSr:
Now we're getting somewhere! I had also tried to adjust the lowest screen level up a bit in Gravity Box because the auto-brightness was way too low. That certainly explains why I only got stuck in a boot loop when I would re-enable Gravity Box. I guess we know not to do that again! Should we ask DoPa to add a warning to the Op?

I ended up having so many issues I decided to format everything I could in Philz recovery and do a clean install. For some reason the auto-brightness isn't giving me the same issues this time around. No idea what controls that. Also, no issues turning Wifi or Bluetooth on and off. So far, no soft reboots at all. Will keep my fingers crossed!

And, of course, this time I have a good Nandroid with it all setup like I like it, in case I manage to screw it up again.. :)

Thanks!

UPDATE: A few more thoughts...

Over here is the thread for the KitKat version of Gravity Box:

http://xdaforums.com/xposed/modules/app-gravitybox-v2-9-1-tweak-box-android-t2554049

Here are a few possibly relevant comments from that thread..
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] Gazoo119:
Thanks for the info. I have played with many of the settings in gravity box and the tablet itself and like I said the only setting that messed up things (so far) was the auto brightness setting in gravity box. So that setting is working for you now?

I don't use auto brightness......I set the brightness where everything on the screen is easily visible and leave it there. It's about the same brightness as it was when I was running DoPa 2.0 with auto turned on. I am happy with that for now. Maybe when I have time I will try what you did and see if it works for me.

I hope the rom will stay stable for you. Thanks again :)
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] MrSimmonsSr:
No, that setting isn't working for me in Gravity Box. I haven't tried it. I just didn't feel like I needed it with my latest wipe and refresh because the out of the box auto-brightness was working fine and not making my screen so dark, for some reason.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] alejflores94:
Can you please explain how to repair the GPS? Everything works great with this ROM! Its super smooth, the best I have tried so far but GPS is dead!
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] MrSimmonsSr:
For the record, there is nothing wrong with the GPS on this ROM that I can tell. First lock takes a while, as usual, but after that it is all good!

All I did was grab the free "GPS Test" app in the Play Store, set it outside running that app for a few minutes and it had a lock in no time .. Give it a try. Ever since I did that once, it has found a lock within a minute or so every time I've tried it..
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] isaacj87:
Pretty much what MrSimmonsSr said. I got a GPS testing app from the Play Store, set my tablet near as close as I could outdoors, and let it sit until GPS locked on. My GPS has always worked from that point forward. I've even done a complete wipe and reinstallation of the ROM and my GPS still works.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] dolorespark:
Thanks for the confirmation of what my testing on this ROM, CM11, and the stock ROM suggested: there are no inherent problems with this ROM's GPS. All 3 use the same code to locate and lock onto the GPS satellites. Those who are having problems might do well to read the Wikipedia articles on GPS and AGPS to better understand some of the issues.

In a nutshell: without assistance, it will take at least 12.5 minutes to establish a lock if the GPS hasn't been used in several days. That's how long it takes to receive a full listing of where every satellite is and will be for the next few days (transmission rate is 50 bits per second). To speed up the process, the ROM gets some assistance by downloading the same info from the internet every 3 days if the GPS is on. So, to speed up your initial lock, start the GPS within WiFi range. For the next few days, locks will be quick even if you're away from a WiFi connection.

Another thing to consider is that the satellite signals are very weak and subject to interference from the ionosphere. If you don't have a clear view of a fair amount of the sky, signals may be too weak to establish and

maintain

a lock. Since ionospheric conditions can vary from day to day, it's very possible for performance to be good one day and poor the next. For a summary of current conditions, see NOAA's Current Space Weather page.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] alejflores94:
Sorry for my question, but how can I get the non over clocked version? Am I supposed just to flash the boot image at the first post through twrp?
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] isaacj87:
The standard kernel (i.e non over clocked kernel) is included in the ROM package, so you have it already
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] dolorespark:
Test Kernel - OTG Charging Support

I've posted an experimental kernel that supports charging the battery while an OTG device (keyboard, flash drive, etc.) is attached. Other than this new feature, this kernel is identical to the dopa1-v1.1 kernel listed in the OP.

Installation is simple: just flash like any other update. Usage is equally simple, provided you follow the instructions.

Prerequisites

* an OTG "Y" cable which you can find on Amazon or E-bay. I found a vendor in Virginia on Amazon who got it to me via US Mail in 4 days.

* the original power supply that came with the tablet or any other charger that is capable of delivering at least 1.8 amps (1800ma). When plugged in directly, Settings->Battery should show "Charging (AC)".

Usage

Charging starts automatically if power is detected

when you plug in the cable

. Put another way: the charger must be connected to your OTG Y cable before you plug it in to the tablet. The OTG device itself can be attached or detached at any time. It will draw its power exclusively from the charger - if you remove the power, the OTG device will die.

If you attach your OTG device without the charger connected, it will draw power from the tablet. You can later attach the charger and it should provide extra power to the device but it will not supply power to the tablet. You would have to unplug the Y cable from the tablet, then replug it to start charging.

Note: Even though the tablet is connected to an AC-powered charger, the tablet will only receive as much power as it would get from a USB connection (500ma). Settings->Battery will show "Charging (USB)". This is done to ensure the OTG device gets sufficient power and to avoid overloading the charger. As with any USB-powered connection, charging is slow and the battery's charge level may drop if you're performing any power-intensive tasks.

Bugfix(?)

While developing this, I had a couple of instances where the tablet rebooted when I plugged in an OTG cable. It appears that the hardware misidentified the type of connection and set up a regular USB session, then re-identified the connection a few milliseconds later and tried to set up an OTG session, The existing code couldn't handle this unexpected transition and crashed. I've added some code that I hope will fix the problem but I haven't been able to reproduce the scenario to see if it works. If you suffer a reboot, please report it and be specific: were you plugging in the cable or unplugging it? (Other tablets have issues when unplugging the cable but I haven't experienced that problem).

File

sero7pro-boot-otgtest.zip
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] ratyfu:
Great to see that development isn't over yet for this device! BTW: I can power my DSLR with a SE Live with walkman, but not with our hisense. Is this a hardware or a software limitation?
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] jerbear294:
I was just wondering about this earlier last week :)

I'll pick up an OTG Y cable when I get the chance.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] dolorespark:
Still alive...

For those who fear development has ceased: I've just started my second build of AOSP 4.4.3.2.1.000.000 - the bleeding edge of Google's efforts as of Monday morning. My first build worked but had some glitches, and I'm sure I'll have do yet another before I have something worth releasing. It may be a while (a week or so) but it will be along "in the fullness of time"...
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] moopile:
Keep up the great work !!!!! Thanks !!!!!
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] nccruz:
Great news, thanks and will eagerly waiting...
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] Gazoo119:
I appreciate it but I wasn't too worried because I was almost sure you would keep working on it. And besides if you had not, I have been very happy with the way the current rom is working. Honestly I never thought I would see a stable Kitkat for this device but you and a couple of others came through.:good: Thanks.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] x000x:
looking forward to this :D
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] dolorespark:
AOSP 4.4.3.x-v0

I've released a very-vanilla build of Android 4.4.3.

Changes

ART Runtime - the Dalvik VM is gone, it's ART only. This also means the Xposed installer and apps won't work until Xposed is updated.

SE Linux - new security policies make root access nearly useless and apps like SuperSU ineffective. As a temporary workaround, this build runs in 'permissive' mode. It also uses the generic AOSP su which doesn't prompt before granting (or denying) root access.

Installation

wipe /data and /cache

install sero7pro-aosp443x-v0.zip

install GApps (optional, see this thread)

reboot

wait at least SEVEN MINUTES before you start to sweat. With GApps installed, the first boot should take roughly 6 minutes. If it goes on for 8 or more minutes, turn it off then restart.

Notes

This is the tip of the AOSP master branch as of 2014-05-30 19:12:00 UTC. All of the expected features (WiFi, Audio, Bluetooth, GPS, etc.) seem to work OK. Developing it for the Sero7Pro required fixing a large number of SELinux policy errors. The ROM itself shouldn't generate any errors and could be run in 'enforcing' mode. The kernel, device, and vendor trees for this ROM are available from github

File

sero7pro-aosp443x-v0.zip
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] jhienk:
Awesome work! downloading now will post with bugs if any. Thanks Dopa!

Installed! Started to sweat around the 7 minute mark then voila! Android 4.4.3 running on my Sero 7 Pro!!!! How frikin awesome is that! So far no problems, running really smooth! Thanks for all your work ! You are the best there is! Cheers!
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] ccristal:
SU

Hi!

I've tried to flash the .zip file for SuperSU v1.97 (the first one that supports AOSP 4.4.3), but it hangs every time I launch it - presumably while trying to obtain root for itself. Anything trying to obtain root hangs.

Is there anything specific I need to do?

Thanks!

ccristal
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] TheLoonyRebel:
If you read the notes it says SuperSU as of right now is ineffective.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] ccristal:
Yes, I read that, but then how can Chainfire claim support for 4.4.3 starting from v1.97? Is there anything different between the security policies in the "standard" AOSP 4.4.3 and the one built for the Sero 7? :confused:

See https://plus.google.com/+Chainfire/posts/ZtXAhw164QD

ccristal
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] TheLoonyRebel:
Chainfire then followed up a few days ago with this: https://plus.google.com/+Chainfire/posts/TkGWeaiCYA9
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] ccristal:
As I said, I have tried with the flashable version of SuperSU. That should be able to write to /system, as mentioned by the post you linked.

ccristal
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] Gazoo119:
I gave this a quick try and found the stock browser kept freezing but chrome worked ok. Speedtest.net would work but freeze after showing the results. File ManagerHD would open then immediately freeze. I didn't test V4A however the built in sound effects worked perfectly. The GPS receiver in these tablets is weak. However when I took the tablet outside it only took around 20 seconds to lock on and I was testing using "GPS Test". Google maps worked good.

Trying to play a movie using XBMC over HDMI would freeze. MX Player would stutter playing .mkv files. I could not get the HW+ feature of MX Player to work.

The very basics of this rom are working and on the bright side, for me, XBMC Gotham RC1 worked flawlessly, even with my bluetooth headphones connected. But I had to go back to 4.4.2 for now. I wish I would have more time to run further tests but I don't see that happening for another two weeks.

Thanks Dopa for everything. You are amazing. I know its a very vanilla rom and I know if it's possible you will have this rom working as well as 4.4.2. :good:
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] taba4real:
Took me a restart to have it running after the 10th minute of waiting for the first time. Upon opening it, no playstore. =(

Downloaded playstore apk and it seems like it does not open the file at all....
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] dgjenkins:
Did you load gapps after installing the Rom? No aosp roms include gapps so you'll always need to install them yourself. I'd get the latest from paranoid android. Flash in recovery directly after flashing the Rom.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] taba4real:
Yes I got it from here....http://www.androidfilehost.com/?w=files&flid=15270 but looking at it need to dl standard GAPPS and not just the first link which was the browser...... tried now and everything seems to be workign now... reinstalling all apps through playstore....
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] TheLoonyRebel:
Have you tried this beta build for SuperSU perhaps?

http://xdaforums.com/showpost.php?p=53015925&postcount=5522

I'll try this in a bit on my Sero 7 with that 4.4.3 ROM. :D
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] ccristal:
Yep, I've tried 1.97 and 1.99r3. None of them works.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] TheLoonyRebel:
Yeah same here. No sweat at this point as stuff like Xposed doesn't work on 4.4.3 so I'm not in a hurry to jump forward. :D
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] dolorespark:
I tried an earlier iteration of 1.99 plus whatever version I put in 442-dopa-v1. Both kept crashing due to problems with ART, not SELinux (it's effectively disabled). I'll update my repo to the bleeding edge again, then try a new build to see if anything has improved
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] taba4real:
unfortunately, games i am playing like clash of clans and forces of war does not work with 4.4.3 thus the reason for going back to 4.4.2
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] jerbear294:
They're not compatible with ART yet. Once ART becomes more mainstream the apps should update.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] taba4real:
micro USB hub

Connected a USB hub with a micro USB plug... Worked well on key and mouse.... Will try to check on the third USB, I can make it charge....
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] taba4real:
Couldn't make this work with charging....
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] taba4real:
It works!!!! I am able to use a regular USB keyboard and USB optical mouse plugged into a USB HUB with a micro usb plug, added into the mix is the usb cable plugged into the charger. The tablet is charging while both devices are working very well... Good job DOLORESPARK!!!!!!