yashsingh1/xdaforums huggingface dataset:
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] dolorespark:
Attn: International Users/Lurkers

I've developed a Kitkat ROM which is compatible with both the US and UK versions of the Sero 7 Pro ('m470' and 'm470bse', respectively). A beta version will be released soon.

I'd like to see if this compatibility can be extended to the two other versions of this tablet: 'm470bsd' and 'm470bss' (sold in Europe and Australia, I believe). To do so, I need the assistance of one or two owners of those models. If you have ADB installed on your PC and are comfortable using it, please run the following commands and post the results here (some of the output is fairly large and should be attached to your posting rather than included in-line).

Reboot, and as soon as the lock screen appears, run

adb shell dmesg > dm.txt

Do not delay or we will lose the beginning of this log which contains some vital information. Zip this file (about 100k) and attach it to your post.

adb shell cat /proc/partitions

adb shell ls -la /dev/block/platform/sdhci-tegra.3/by-name

adb pull /proc/config.gz

This is also fairly large but is already gzipped; attach it to your post.

Note: if you don't have enough posts on XDA to post a reply here or include attachments, send me a PM so we can make appropriate arrangements.

If the hardware in the BSD and BSS models proves to be substantially identical to the other versions, we'll move on to the next step in our quest for a "universal ROM" for the Sero 7 Pro :)
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] folliclekev:
M470BSS

Hi, I have tried to get the dm.txt but all it says is "klogctl: Operation not permitted". If have tried a number of times and get the same result. I have attached the dm.txt, the config.gz and the partitions and blocks in a txt file. I wish you success and hope we can update our Aussie Sero 7 Pros very soon.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] dolorespark:
Thanks for posting that.

Getting a dmesg log may require your tablet to be rooted - is it? See if this is any more successful:

adb shell cat /proc/kmsg > km.txt

Unlike dmesg, this doesn't terminate automatically, so after a few seconds, press Ctrl-C to kill it.

If that doesn't work - but you are rooted - then we may have to take another tack and pull the report from within Android. Reboot, then as soon as the lock screen appears, run these commands ASAP:

adb shell - this will start a shell session on the tablet

su - this will start a root shell; the prompt should have a '#' rather than a '$'

dmesg > /sdcard/dm.txt - send the report to your internal SD card

exit - leave the root shell

exit - leave the Android shell and return to your OS

adb pull /sdcard/dm.txt - pull the report from the sdcard and save it in the current directory

Thanks for your help!

BTW... I spammed a lot of threads seeking help. Which one did you see my request in?
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] rodos15:
m470bss

Hi dolorespark, I use your sources for the 470bss, just change the following lines in your cofig:

# CONFIG_MACH_TEGRA_DT is not set

# CONFIG_MACH_ARUBA is not set

# CONFIG_MACH_CARDHU is not set

# CONFIG_MACH_P1852 is not set

# CONFIG_MACH_E1853 is not set

CONFIG_MACH_TEGRA_ENTERPRISE=y

# CONFIG_MACH_M470 is not set

# CONFIG_MACH_M470BSD is not set

CONFIG_MACH_M470BSS=y

CONFIG_BOARD_M470BSS=y

# CONFIG_BOARD_M470BSS_V1 is not set

CONFIG_BOARD_M470BSS_V2=y

# CONFIG_MACH_TAI is not set

# CONFIG_MACH_KAI is not set

Then just rename all the file names in the ramdisk e.g. fstab.m470 to fstab.m470bss and edit the init.m470bss.rc with the new file names, also rename the sensors file names in the "/system/lib/hw/" e.g. lights.m470.so to lights.m470bss.so.

If you need anything else let me know.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] folliclekev:
This thread is where I found this. I got some info this time in dm.txt. The km.txt has permission denied.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] CanuckinPA:
I didn't reboot a second time. I used ES File Explorer, found two data files, but both were empty? Could that be because I'm using Link2SD?

Regardless, I did a full wipe and flashed everything and all is good now.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] dolorespark:
Just what I needed! I compared it to the output from my tablet and found that the two were nearly identical. The manufacturers for the RAM and flash memory are different but the existing code handles that. The processor is ever-so-slightly different and requires slightly higher voltages when running at higher speeds. This is particularly useful info for me because the next version of this ROM will offer selective overclocking (i.e. a single kernel that lets you choose your max speed, rather than separate kernels for normal and overclocked speeds). Without knowing that I have to accommodate this variant, the o/c option wouldn't work for you.

It's good to know that the same code runs OK on your device without any alterations. My goal here is to avoid having to rename any of the files so that a single ROM can be installed on any version of the Sero 7 Pro. With the help of [MENTION=2248375]mikembley[/MENTION], I've already confirmed this works on the UK version. I'm sure it will work on any of the other versions - provided the kernels are compatible, Now, I know they are - thanks!

Could you do me a favor? Reboot, and as soon as the lock screen appears, run dmesg. On line 34 of the output, you'll see something like this:

cpu_speedo_id = 7, soc_speedo_id = 1, cpu_process_id = 4, core_process_id = 0

What value do you get for 'cpu_process_id'? This identifies the "slight difference" in processors that I mentioned above. While mine is a '4', [MENTION=2489125]folliclekev[/MENTION] had a '3'. I'm curious whether the difference is model-specific or not.

Generally speaking, if I had a problem on the first run after a new install, I'd shut down then reboot. There's a lot of stuff going on during that first boot-up and things can happen out of the normal sequence of events, leading to "transient wierdness" :) If the problem persisted, I'd attribute it to Link2SD since others have mentioned similar problems.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] rodos15:
Mine is 3 too
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] RVD26:
I'm having trouble downloading 'sero7pro-aosp444-dopa-v2.51.zip'.

I get an installation error each time.

It's the first file listed in the OP.

Here's a screenshot of what pops up when I try to install from Recovery.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] dolorespark:
The "real" error here can be identified from the background graphic on your screenshot; "compiled by xboxexpert". That version of CWM is incompatible with later versions of Android that implement SELinux. Install an up-to-date recovery program such as the version of Philz Touch Recovery in the first posting - or better, my most recent build which can be found in the posting directly before yours. Install that using your existing CWM, reboot back into recovery, and it should all go smoothly thereafter.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] RVD26:
This worked. Thanks!

Can you tell me how to get camera pictures to save to the external SD card rather than the internal card?
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] stevenc88:
So what can be done with the Wiimote and this tablet?
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] dolorespark:
Good question. My description of this feature was a bit too brief, so I've clarified it in the earlier posting: it enables you to pair your Wiimote with the tablet via Bluetooth. What you do with it after that is beyond me - I don't own a Wiimote nor any games that might benefit from it.

[MENTION=584916]ziddey[/MENTION] had mentioned that Wiimote support was available in our kernel but wasn't enabled. When he built a kernel with it enabled, he found that the code was old and didn't support many newer features - plus at least some of the buttons didn't work. So, I went to kernel.org and pulled the latest version, then incorporated it into this kernel. Whether it's better than the original remains to be seen.

Find another Camera app. Neither the stock app nor Google's proprietary version support saving to SD card (perhaps because Nexus tablets, at least, don't have SD card slots).
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] folliclekev:
M470bss works with this rom.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] RVD26:
Is there any way to move apps to the SD card?

Sent from my Samsung Galaxy S5
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] jerbear294:
There are a few apps that do so.

Link2SD will move the app and it's data, but makes a separate partition on your SD card. Mounts2SD does the same thing AFAIK.

Personally I use FolderMount. It doesn't move the app but it will move the data and doesn't need a seperate partition. It's very fairly priced, as well. Worth every penny.

*end advertisement* :P
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] spinn:
newbie here and I downloaded the Windows files from the DoPa stock rom thread. I had updated the USB Driver and extracted the Philz image to a directory, along with the Fastboot file. I started my Sero up and got the Fastboot logo, plugged the USB cable in and device was not recognized on my Win 7 laptop. Tried typing in fastboot flash recovery philz.img and got the message [waiting for device]. USB debugging was activated, but the Sero didn't appear to be recognized while in Fastboot mode. Where'd I goof?
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] nccruz:
if you are trying to load DoPa on your Sero 7, just follow the instructions on the 1st post... like no need to extract any zip files...
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] dolorespark:
The problem is not one you'd expect. Windows uses a USB device's Vendor ID and Product ID to decide which driver to use. The tablet provides 3

different

sets of IDs, depending on the mode it's in: Fastboot, ADB running in Recovery, and ADB running in Android. That means you have to install the very same driver 3 different times. I'll update the instructions to mention this.

In this case, open Device Manager, boot into Fastboot, then connect the USB cable. Under "Other Devices", you should now see "Fastboot". Right click on it and select "Update Driver Software", then follow the usual steps to install it. When done, you can type "fastboot devices at the command prompt - it should show you a serial number and the word "fastboot". If that works, you should be able to install Philz using fastboot without any problems.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] spinn:
Sorry, I'm trying to follow instructions per Post #536 which has the latest beta versions. The install appears to be different than originally.

---------- Post added at 10:08 AM ---------- Previous post was at 09:25 AM ----------

Thx! I'm actually trying it out on my work desktop and was able to get philz onto the Sero. Backing up my original Rom now. Last nite, I was working from a Lenovo T61 laptop and it just wasn't recognizing the device when I connected in Fastboot mode. None of the drivers seemed to work; on my desktop it recognized it right away.

15 min later, it's WORKING!! After getting Philz recovery installed, the instructions made sense. Thx for the help!
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] jachol:
M470BSE Success + a bonus

Hi guys

Install of Philz + ROM, both went smoothly no hiccups, and the bonus ...

a previously unrecognised 64GB SD card now OK, and installed as SD1.

Many Thanks ... I'd all but given up hope of an update for the UK model.

I still need to reinstall my apps, but first impressions are VERY GOOD :good:
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] Pow_2k:
My guess is an exFAT formatted card? I haven't had issues with 64GB cards on any of my devices but I believe I set the format to FAT32 first.

I've got both the ROM and the recovery downloaded, just need to install them. Don't know why I'm taking so long to do so. :)
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] jachol:
I see where you're coming from, but I don't think so, I always use the program SDFormatter to prepare SD cards, and AFIK it doesn't do exFat

A least cards I've formatted that way have only shown as FAT. The 64 GB card has been tried in various tabs and phones with no success,

But this is a first in a KitKat OS, and it's working that's all I need. ... J
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] Pow_2k:
I should start using that utility, as it is from the SD Association themselves. From looking at the Windows manual (playing the odds here...) it does mention that for SDXC cards (capacities greater than 32GB) on Windows XP the MS KB update to support exFAT is required. While I haven't tried the utility to confirm, this would indicate to me that it is likely the format that would be used on SDXC cards. No update required for Vista (SP2) or later as I would assume MS already had exFAT support included. The manual doesn't seem to indicate that the end user has any control over what file system is used for the format so I suspect FAT32 is forced for up to 32GB (2GB and smaller may be straight FAT) and exFAT for greater than 32GB, in order to get SD Association's "optimum performance." The utility does complete with a window that lists what format was used, so if you have another card to format you'll get your answer there.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] jachol:
Hi,

Got to hold my hand up, You're right. I just checked the cards properties in windows and it shows as exFat. I have that manual downloaded somewhere, but to be honest I don't recall reading it in any great depth, I should. ( I don't have another 64 GB card I could try, so couldn't do a check that way)

BTW the card is nothing special SDHC 64GB bought cheaply on ebay for another project originally, I know it's at least class 6, but possibly class 10. Anyway bottom line is with the 32GB of the UK model + the 64GB I have a stack of storage space.

I can recommend SDFormatter... used it for a while now with no issues, IMO a lot of install fails are possibly due to poor card preparation. ... J.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] RamblingBarba:
I bumped up to the V2.6 beta to try out the Wiimote. I guess I may be doing it wrong but I get nothing from the Wiimote. The SERO sees the Wiimote whenI click it it gives me a dialogue box to enter a code stating that it is usually 0000 or 1234. I have entered both and clicked ok. It shows the Wiimote under "Available Devices" but the Wiimote doesn't seemed to move anything. I have tried on several games and two different emulators. It's probably a user error but I wanted to give the feedback none the less.

Thanks for the ROM. It is outstanding.:D
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] Tool Belt:
Any suggestions on how to set gpu over clock frequency?
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] dolorespark:
I'll assume you want to make this semi-permanent. If so, you'll want to create a file named 01cpufreq that will end up in /system/etc/init.d. You can create it on your PC and push it to the tablet using ADB, or create it directly on the tablet using something like ES File Explorer's text editor. It should look something like this:

#!/system/bin/sh

# set the GPU's maximum speed by setting its voltage (in millivolts), then enable this setting
# 1200 = 448mhz / 1250 = 520mhz (higher voltages will NOT increase the speed)
echo 1250 > /sys/kernel/tegra_cap/core_cap_level
echo 1 > /sys/kernel/tegra_cap/core_cap_state

# set the CPU's maximum speed (in kilohertz); e.g. 1200000 = 1.2ghz
echo 1500000 > /sys/module/cpu_tegra/parameters/cpu_user_cap

If you use ADB, run adb remount before pushing the file in order to make the /system partition writeable. Once it's in place, change the file's attributes to make it executable. You can use ES File Explorer's Properties dialog or ADB. E.g. adb shell chmod 755 /system/etc/init.d/01cpufreq

On the Bluetooth screen, the Wiimote should show as "Connected". If it doesn't, the most likely reason is that this feature just doesn't work (you're the first to test it). However, before giving up, see if there's a button on the Wiimote that has to be pushed to make it pairable. Also look at whatever labels are on it to see if the code is printed there.

If nothing gets it connected, the next step is to get a log of what the system is doing when you try to pair. Do you have ADB installed? If so, connect the tablet to your PC via USB, open a command prompt ("DOS window"), then change the current directory to wherever you want the log to end up. Next, enter this: adb logcat > logcat.txt. Now, try to pair the devices. After you've tried (and presumably failed), press Ctrl-C in the command prompt window to kill logcat. Create a new post and attach the log to it (zipped if its really big).
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] Tool Belt:
Thanks dolorespark. I will try playing with this over the weekend, appreciate the help.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] mikembley:
Perhaps it's because you are entering a code, i don't think the Wiimote likes the pincodes.

In my brief tests i could get the Wiimote to act as a basic controller and would only work navigating the menus.

I've tried to use it with Wiimote applications on the Play Store, but none would be aware of the Wiimote already being paired. I would put it down to the way that these apps are supposed to work with the older bluetooth stack which used L2CAP, although i'm new to this and could be wrong, i wouldn't mind trying to investigate.

On top of i was wondering if this perhaps fixed Playstation DS3 controller support, but unfortunately the typical OTG pairing wasn't working for me, but i will try to see if i can set the controllers master address via USB on PC.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] RamblingBarba:
:good:

There is a sync button on the wiimote and I used it. I have two different wiis available. One with old, first run wiimotes and the other with the latest wiimote with built-in rumble. The controllers are interchangeable to the consoles. The old remote paired without asking for a pin code and showed as paired in the settings>bluetooth menu but I still couldn't get it to input movement. I will investigate it more and try to get a logcat for you.;)

On the new wiimotes when the SERO asks for a pin the OK button is dimmed until an entry is added. You can progress without entering something.

I couldn't get that much action from the old wiimote that shows paired. This is not a must have for me. It just seemed cool. I will keep looking into it though.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] dolorespark:
Here's another idea: in /system/usr/keylayout you'll find two files: Vendor_057e_Product_0306.kl and Vendor_057e_Product_0330.kl. Each one equates the numeric code generated by a button to the generic name for that button. The first one is for the original Wiimote. The second is for the later version and is just a copy of the first. They could be wrong. Try renaming them to see if the defaults built into the kernel do a better job.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] RamblingBarba:
Ok, I paired the old style wiimote as mentioned above. I tried it with the following emulators: FPSE, SuperGNES, NESOID and NES Emu aas well as various games. I get no input from the wiimote. I downloaded the WiimoteController app and went through the setup. It found the wiimote but when connecting it returns: "An error occurred. Last error: No route to host":eek:

I renamed the files as instructed above. I got the same results. Old wiimote would be found, pair and connect but not input new wiimote would not be found or pair or connect. I got the same same error from wiimote controller if it found a wiimote when searching.

Changing the vendor file names made no difference.:(
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] jachol:
Video streaming ??

Hi guys,

I've been trying to stream video with the updated ROM, from both BBC iPlayer, and video files stored on the tablet via a miracast dongle into my television.

HD video streams OK, but so far I have no sound transfer, I've found nothing in the tablet settings that helps, ideas, advice anyone please, I'm not makinng any progress. ... J
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] jonalowe:
Read the first post. Audio not working for Miracast.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] tmoulder:
Version 2.51

Hello All!

Been using DoPa 2.51, very pleased overall. Two things I've noticed:

1. On power-up the tablet is smooth and responsive. The longer I use it, it gradually becomes laggy, to the point of needing a reboot. I've tried cleaning cache, no effect.

2. The tablet's internal memory shows only 5.56 gb. Is this normal?

Thanks,

TM
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] jonalowe:
I've noticed the same lagging behavior. It almost acts like a memory leak in old versions of Windows
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] jachol:
Oops !, I'd missed that one, thanks for the info, at least I know why now saves me chasing rainbows. ... J. :good:
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] tinybeetle:
Ditto. It appears to be RAM availability. When it slows down ES Task Manager shows that I have less than 200mb of RAM left. What I do is use ES Task Manager's Kill All. That seems to restore the memory and the Sero runs better for a while again.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] RamblingBarba:
I use Disable Service and/or Autorun Manager to disable any nonessential services. I haven't experienced any lasting slow down. Periodically when apps are updating or something is syncing it will be slow for a minute or so.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] tmoulder:
What about the 5.56 gig memory, is that normal?
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] tinybeetle:
I upgraded to Dopa v2.61 from v2.51 and found that the Google launcher wouldn't complete the setup. It wouldn't accept the "next" button. The home button on the Sero worked. When I got into the Sero I found that my desktop was completely rearranged. Google Play Services kept crashing every few seconds. I found that the GMail app was missing.

The bottom line was that I had to reinstall GApps. Once that was done things worked correctly again. However, I did need to set up my Google accounts and (Yellow app) Email accounts again.

I suspect that if I'd flashed the GApps immediately after flashing Dopa v2.61 (prior to restarting) the Sero would have restarted then normally.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] nexy33:
I installed the latest gmail 5 on it last night on the UK zero and it works a charm also supports multiple accounts
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] tmoulder:
Which services do you disable?
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] ObviousMan:
I installed the latest update of GAPPS on 2.51, and I get constant crashes of the latest GMail app (when trying to update), launcher (any attempt to change the wallpaper crashes it for example). The Maps seem to be OK, but I have not played with it much, so is YouTube. Have not tried the Camera app yet.

Is there a compatibility issue?

OM
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] xtil:
Did you flash the GApps immediately after flashing the ROM? On my first attempt, I booted the ROM first, and then added GApps, and I had problems. Next try, I flashed GApps immediately after the ROM and everything is perfect.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] bradmax57:
Many thanks for sorting the UK version, had one since they came available in the uk and its a decent tablet but obviously not a drop of support from hisense, flashed the beta and all seems running well, new lease of life in the thing

Cheers