yashsingh1/xdaforums huggingface dataset:
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] dolorespark:
Yes.

The Android 5.1 source code was just released and I've downloaded it. Some of my many patches failed to apply cleanly, so I'll have to adapt them to the new code before I can build it. The final product will be along "in due course".

As it happens, I've been spending a lot time on several projects but sadly, I don't have much to show for my efforts - with one exception. A user in Germany wrote me about his M470BSG, a model I'd never heard of. I added support for it to the kernel and built a version of PhilZ Recovery for him to test. It appears to work OK, so future ROMS will support that variant (I'm also going to reissue PhilZ and my last Kitkat ROM).

Any time after the DoPa boot logo appears, enter "adb logcat > logcat.log at a command (DOS) prompt. Let it run until the "not responding" popup appears and you've cleared it. Then, press Ctrl-C. Zip the resulting log (about 200k) and post it.

I identified and corrected the only

known

problem with the WiFi MAC address over a year ago. If you're running any of my ROMs released since January, 2014 (any Kitkat or Lollipop ROM, or my last modified-stock ROM), then you already have that fix. If you still have this problem, then it's a different issue.

The manufacturer-assigned WiFi MAC address is stored in a partition labelled "BCK", along with other machine-specific info, The bootloader is supposed to pass it (and the BT MAC address) to the kernel on its command-line. For some reason, this fails to happen on some devices. To fix this, I modified the kernel to read this info directly from the "BCK" partition if it wasn't available elsewhere.

If this fix doesn't work for you, it's possible that the address is simply missing from "BCK". If that's the case, the fix would be to put it there. It's easy enough to do but I wouldn't want to try it until I've done some investigating. Are you set up to use ADB? If so, we can proceed. Also, is this a refurb? (I can imagine that some refurbs might not have been restored fully/properly.)

A log would be very good. I'd be happy to investigate myself - but only if I can do it on the cheap :)
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] jhsnyder:
Re: ephemeral WiFi MAC address problem

I flashed directly from the stock ROM to your latest/current (lollipop) ROM, should that be relevant. And yes, this is a refurbished unit.

I'll have to check your earlier posts about this; I wasn't aware of your fix.

I'm running the adb-tools package on Arch Linux, so easy to provide a logcat transcript.

I don't recall seeing a BCK partition when I poked around with adb shell, but then I wasn't looking for it. Not sure I would have noticed had it been present.

So that I don't waste your time, let me first look at the posts documenting your fix, and root around the tablet filesystem (so to speak). If I can't make it go on my own, I'll follow up. Either way I'll document what I've found.

It'll be a few days.

Thanks for the quick response, Jim
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] TheLoonyRebel:
Tunnel Bear does have a free limited option that give you something like 500mb per month. Otherwise it's like $5 for unlimited VPN. I'll try to get the log within the next day or two I've been a bit flu ridden so I'm not quite all there right now. :crying:
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] tmoulder:
Thank you! I'm very happy to hear that! No pressure, not asking for an ETA or anything, just wanted to know if I should continue checking in. Thanks again for all your hard work.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] dolorespark:
You were looking in the wrong place. The BCK partition is just raw data with no filesystem, so it's never mounted.

root@m470:/ # ls -la /dev/block/platform/sdhci-tegra.3/by-name
lrwxrwxrwx root root 2015-03-17 11:02 APP -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-03-17 11:02 BCK -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-03-17 11:02 CAC -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-03-17 11:02 CDR -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-03-17 11:02 LNX -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-03-17 11:02 MDM -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-03-17 11:02 MSC -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-03-17 11:02 SOS -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-03-17 11:02 THD -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-03-17 11:02 TMP -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-03-17 11:02 UDA -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-03-17 11:02 USP -> /dev/block/mmcblk0p10

Hmmm... I identified the issue in my reply to you: the bootloader fails to pass the MAC address to the kernel on its commandline. The underlying cause is unknown because Nvidia has never released its bootloader code for the Tegra3. This is the case with your tablet - the addresses should be where I put "[**HERE**]" in the commandline you provided.

In fact, you're missing several arguments. Here's what I get at that point (slightly modified to obscure my MAC addresses):

ddr3=0x0 hpdet=0x0 wifiaddr=00:1A:98:B8:3C:E6 btaddr=00:1A:98:B8:3C:E5

Now, to fix the problem (maybe), run the following commands:

dolorespark@fong:~$ adb shell

root@m470:/ # cd /sys/devices/platform/bck

root@m470:/sys/devices/platform/bck # ls -la
-rw-r--r-- root root 4096 2015-03-17 21:40 bno
-r--r--r-- root root 4096 2015-03-17 21:40 board_ver
-rw-r--r-- bluetooth net_bt_stack 4096 2015-03-17 11:02 bt_addr
-r--r--r-- root root 4096 2015-03-17 21:40 ddr3_det
[...]
-rw-r--r-- root root 4096 2015-03-17 21:40 usb_switch
-rw-r--r-- root root 4096 2015-03-17 21:40 vkey
-rw-r--r-- root root 4096 2015-03-17 21:40 wifi_addr

root@m470:/sys/devices/platform/bck # cat bt_addr
00:1A:98:B8:3C:E5

root@m470:/sys/devices/platform/bck # cat wifi_addr
00:1A:98:B8:3C:E6

If either MAC address is null or invalid (e.g. all zeros), you can set it to a value of your choosing. Before doing so, you may want to dump the entire contents of BCK to a file so you can restore it if something goes awry - it's only 2MB (I assume you know how to do so).

IIRC, all the Sero 7 Pros I've seen have an address that starts with 00:1A:98:Bx or 00:1A:98:Cx, with the WiFi address == the BT address + 1. To set the value using the addresses above as an example, enter:

echo 001A98B83CE5 > bt_addr

echo 001A98B83CE6 > wifi_addr

Confirm that your values were accepted, then exit and reboot. The address(es) you entered should now be permanent. To check, turn on WiFi and BT, then go to Settings->About tablet->Status (you'll have to scroll the popup to see the BT address).

If this doesn't work as expected, let me know.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] dolorespark:
AOSP 5.10 - DoPa5 beta v1.1 (US/UK/AU/DE)

A beta version of the latest Android release, AOSP 5.1.0_r1, is now available. It appears to be stable but I'm calling it a beta "just in case".

The primary DoPa5-specific feature of this ROM is the addition of support for the German model of the Sero 7 Pro (m470bsg). To support users of this model, I've also released a new version of PhilZ Recovery.

Installation

In general, new and existing users of DoPa5 ROMs should follow the installation procedures in this thread's first posting. Here are some version-specific notes:

German users - you

must

install the newest version of PhilZ (v2.7) because it is the only one that supports your tablet. Users elsewhere needn't bother since there are no other changes since v2.61.

Gapps - the Gapps maintainer has not yet created versions of his packages for v5.1. To work around this, I've repackaged his "nano" package to make it compatible. Please use my version to get basic support, then download the apps you want directly from Playstore (see "Notes" below for an alternate workaround).

Notes

Bluetooth tethering - it

may

now be possible to tether your tablet to your mobile phone to use its data connection. Currently, this is untested.

Gapps - the only difference between the 5.0 and 5.1 versions of the Gapps packages that I'm aware of is the installer's version check. One way to "fix" this is to get the package you want, then unzip it, Open the file 'installer.data' and change "req_android_version" from "5.0" to "5.1". Zip up the package, then install. Recovery's signature check will fail because you've modified the zip, so tell it to continue anyway.

DRM support - the additional package needed to provide DRM for DoPa5 v1.0 has been incorporated into this build and is no longer needed

RRO Theming (a.k.a "Layers") - basic support for themes using resource overlays remains available. However, additional tweaks added by the developers of Layers (mainly changes that enable themers to change color schemes more easily) are missing from this ROM because their patches were incompatible with v5.1. Once updated patches are available, they will be incorporated into the ROM.

Files

sero7pro-aosp510-beta-v1.1.zip the ROM

sero7pro-nexus7spoof-beta-v1.1.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 updated to support all known versions of the Sero 7 Pro

pa_gapps-nano-dopa51-20150315.zip a basic Gapps package installable on v5.1
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] a178235:
Same Wi-Fi Issue

I also have the same Wi-Fi issue with a different MAC address after every reboot. I also purchased a refurbished tablet. When I cat wifi_addr, I get 00:1A:99:CE:FF:87, but in Settings, it shows 00:34:9A:F8:72:17.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] jhsnyder:
ephemeral MACs

uh, OK ... but why should I have known to go there?

Askin' to be edicated ... I did a bit of googlin' (keywords BCK flash partition) and most of the hits were typos of "back"; none of the rest on the first page were relevant to this usage of "partition".

By "explanation" I meant "root cause". The answer to "root cause" is "we don't/can't know":

OK, then ...

Roger that.

$ adb shell cat /sys/devices/platform/bck/bt_addr
00:1A:99:C7:97:3F
$ adb shell cat /sys/devices/platform/bck/wifi_addr
00:1A:99:C7:97:40
$

in re "I assume you know ...": one might hope, eh? [dryly]

See above.

Also see:

http colon slash slash www dot coffer dot com slash mac_find slash​

or any of the other gazillion sites which offer translations. Wireshark offers a plaintext listing of MACs -> Vendors.

(I apologize for the obfuscation: the forum autobot tells me that I can't post links because *of* *course* n00bs caint post links, duh)

uh,

wait

. You are assuming that my /BCK values are invalid.

What if they're plausible? (ahem, see above ....)

Then

how do I change cmdline?

Believe me, you will be among the first to know. [amused]

All snarkin' aside, my sincere thanks that you have taken the time to respond. I am well aware that you could just blow off whines like mine. The open source ethos depends on people like you.

And I apologize in advance if I have missed a point here.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] dolorespark:
I'll revise my workaround for the problem and post a new boot image with the fix in a few days.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] jachol:
Just for info ... the wifi MAC address remains constant on my UK model Sero 7 both when running Dopa 2.6.1, and the latest Dopa 5.1 beta.

Checked over several reboots, unit was bought brand new, not a refurb. ... Jack.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] tinybeetle:
I'm pretty certain you've done so, but just checking to see if you've incorporated your DRM fix (or if it was fixed by Google) in the new 5.1 version.

Thanks for all you do for our Seros!
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] tmoulder:
Hello! Let me preface this with saying I've done a dirty install from Dopa 2.6, so this report may be related to that.

Installed 5.1, awesome, took about 4 reboots to get itself sorted out and running well. Noticed two things -

1. At power up, sometimes get a message about "system has stopped". Does not seem to be affecting anything, hit OK and move on. Have only seen it on reboot and power-up.

2. I had my external SD Card formatted as F2FS, made 2.6 lightning fast, but 5.1 did not recognize it. Had to reformat to exfat from Philz recovery to get the card visible to the OS.

Overall, awesome job! Hope this feedback helps.

Thanks!

TM
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] natenkiki2004:
I've been running 5.1 since you released it and have had no problems. Maybe it's because I dreadfully used 5.02 for 2 months or so but I am really liking the speed and performance of 5.1. Keep up the great work!
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] faheyd:
I'm using the latest 'AOSP 5.10 - DoPa5 beta v1.1 (US/UK/AU/DE)', and as others stated, after a couple of reboots, all is well (I didn't 'really' read the installation instructions on page 1 so had to do install twice). I installed on 19 Mar 15. I do NOT have the evil FaceBook app installed which I think is a power hungry pig of an app. My Sero is still on its first recharge after installation of v1.1, and still going strong. Power consumption is great, I'm very happy. Sure some features I like to customize are not there yet, but the day is young for this release. Wifi mac seems to be fine. Thank you dolorespark for all your hard work.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] jhsnyder:
ephemeral MAC address problem

Further to your latest response to my questions:

1) At line 18 of the logcat (that I still can't post) I see this:

W/kworker/u:0( 6): type=1400 audit(0.0:4): avc: denied { read } for name="mmcblk0p1" dev=tmpfs ino=5690 scontext=u:r:kernel:s0 tcontext=u:object_r:block_device:s0 tclass=blk_file

Possibly interesting because (from your ls -l) mmcblk0p1 is /BLK.

OTOH, since I can cat /sys/devices/platform/bck/wifi_addr as a user, it isn't obvious why selinux would prevent the kernel from reading BCK, but selinux behavior isn't always intuitive.

Here's another avc from dmesg followed by a reference to the wifi MAC:

<4>[ 13.569571:2] type=1400 audit(1426369196.700:4): avc: denied { read } for pid=6 comm="kworker/u:0" name="mmcblk0p1" dev=tmpfs ino=7686 scontext=u:r:kernel:s0 tcontext=u:object_r:block_device:s0 tclass=blk_file
<4>[ 13.572838:0] Broadcom Dongle Host Driver: register interface [wlan0] MAC: 00:90:4c:11:22:33

I don't know whether /system/etc/nvram.txt is used for anything - I'm guessing not - but it's interesting that nvram.txt contains the lines:

root@m470:/ # grep addr /etc/nvram.txt
macaddr=00:90:4c:c5:12:38
il0macaddr=00:90:4c:c5:12:38
root@m470:/ #

And dmesg contains this line:

<4>[ 13.497923:0] bcmdhd: fw_path: /system/vendor/firmware/bcm4330/fw_bcmdhd.bin nvram_path: /system/etc/nvram_4330.txt

nvram.txt & nvram_4330.txt have the same contents.

This line in logcat might be relevant:

E/WifiConfigStore( 473): Error parsing configuration: java.io.FileNotFoundException: /data/misc/wifi/ipconfig.txt: open failed: ENOENT (No such file or directory)

2) I see that one can override kernel cmdline parameters with fastboot, but how does one make changes to cmdline parameters stick?
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] Hoozer:
SD-Card mounting problem with F2FS

Hello DoloresPark,

as I told you I would, I have tried your 5.1-ROM on my device (german-version with "M470BSG"-naming).

All went fine so far. But I saw / recognized some things that seem to be a bit strange. You might know what could be the reason:

1. I have a SanDisk Ultra 64GB micro-SDcard and formated it in the "Recovery"-boot-menu for F2FS. And the farmating went without any errors. But back in the Android-OS in the settings for the storage I only get the option to "mount" or "format" the SDcard. If I click "mount", I see a short message telling me something like "USB-device removed" and nothing changed. I also tried to format it via the "format"-option, but after that there's also no change. The card seems not use-/accessable when formated in F2FS. I took it out of my Sero and formated it in Windows (7 Ultimate 64Bit) for exFAT. Now it is useable in my Sero. That's good, but not perfect, cause I thought the F2FS had better performance and "wear-leveling"-features, that I wanted to take advantage of.

Is there any way to get it working with F2FS? Did I miss something to enable somewhere?

2. As I wrote you before, I had no NFC options before in my stock-ROM (4.2.2). Now I have these options in the settings and the "TAG-Info"-app recognizes, if NFC is enabled in the settings or not.

Do you have an advice, how I could test, if there is NFC available or not? Were is the sensor-region at the back of the device?

3. Would it be possible to add some "auto-adjust-function" for the performance-settings? So the device could switch depending on the work-load? Or would it be possible to prepare performace-profiles that you can switch to by pressing a hot-key (like the options you have to en-/disable WLAN, Bluetooth, etc.)?

4. Sometimes the Play-Store seems to fail when i want to install an app. (I get a message with something like "... had to be closed"). (I used your linked gapps-package.)

Thanks a lot for your great ROM! I hope you also keep us Sero'ers happy in the future! ;)

Hoozer
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] origitat:
So where do we go to download GApps now since the thread that you linked to in the original post the OP has retired and the GApps links are no longer there :(
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] dolorespark:
Both the random WiFi MAC address AND the inability to mount F2FS-formatted SDcards are SELinux issues. I've fixed the MAC address problem and I can now mount an SDcard formatted with F2FS. However, a big problem remains: the card is read-only. This too is an SELinux issue and affects SDcards formatted using any filesystem that supports extended attributes ('xattr'), such as ext2/3/4. Once I've resolved this, I'll release an update that fixes both problems.

I don't have any other NFC-enabled devices, so I've never been able to test this. The sensor is in the bottom-left corner (as viewed from the back), above and to the right of the left speaker opening. On the US model, there's a big sticker on the back that shows, among other things, the location of the sensor.

Automatically adjusting performance depending on workload is the job of the CPU governor. Nvidia's implementation of the default "interactive" governor tends to be an all-or-nothing approach where it's either running full-speed or it's idling. I've considered a change that would produce a more balanced result, but in some cases it would just seem slower.

As to performance profiles... I had thought about adding a timed setting so that you could, say, boost performance for the next hour while you played a game, or reduce performance for the next 8 hours while you were travelling and away from a charger. However, I don't want to get too "fancy" since the design goal for this ROM is to provide functionality that has to be built-in, not features that can be added on using 3rd-party apps.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] Hoozer:
Hello DP,

I had no problems with my WiFi-connection so far. (My WiFi-router has MAC-address-filtering enabled, so I think, if there was a "new" (faulty) MAC-address, I should have had problems to get a valid connection.)

Good to hear you have a guess what might be the origin of the F2FS-problem.

Thanks for the technical NFC-information. (My device has no sticker showing anything about NFC on the backside, so I assume my version is without NFC. If I ever find NFC working, I will report it here.)

The performance thingy was just an idea, cause I felt a bit uncomfartable always getting into the settings to check, what performance-settings I had put my deivece into the last time. Is there a tool you know of, that can en-/disable settings with on click (like in the pulldown-menu I described before)?

I was playing around with my own "bootanimation.zip". It seems that the used zip-format was faulty, cause it just didn't play. (I used WinRAR to ZIP with no compression; also tried 7-Zip with no compression,) The file was a reverse playing boot-animation of your default-DOPA-logo (chanegd just the numbering in the filenames), so all other data-requirements should have been met.. I used a filemanager-app that enables you to show and change the root-files, like "/system/media", where your animation-file was sitting. I replaced your file with mine, but then I got a "standard-android"-animation playing at bootup. I used this method, cause no flashing was needed and I saw the fiddling with the original file showed an effect (although it wasn't the final result I wanted to see!).

What program did you use to make the ZIP-file?

I also read something about a "shutanimation.zip", but this seems not to be executed. (I renamed your original bootanimation into "shutanimation.zip", but it was not played.)

Is this outdated info or does it require something to be changed in the ZIP-file or something else to take care of to work properly?

Thanks a lot for your fast response! (Some companies could learn from you! ;))

Hoozer
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] ratyfu:
Sorry to interrupt, just wanted to say that 5.1 is running buttery smooth, so far.

It's a more than huge step up from 5.0 and probably the best daily driver there is for our device.

I had to uninstall Facebook and its resource hungry sibling Messenger, though. They alone occupied more than 160MB of RAM, which on a 1GB device is just impossible to justify.

Also, I am using Greenify, which IMO is a must.

Great work [MENTION=5094650]dolorespark[/MENTION] !
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] faheyd:
Just had to put it on the charger after 7 days of light use, mostly book reading, google+, etc. No FaceBook. I'm calling this one a success!

Again, Thank you [MENTION=5094650]dolorespark[/MENTION] !
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] dolorespark:
WiFi MAC Address / F2FS SDcard Fix

I've posted an update zip for AOSP v5.1.0_r1 / DoPa beta v1.1. It fixes both the random WiFi MAC address problem and the inability to mount SDcards formatted with f2fs or ext4.

You can get it here: sero7pro-aosp510-beta-fix-v1.1.zip

Install it through Recovery and let me know if any issues remain.

FYI... Google has released AOSP v5.1.0_r3, so I'll be building a new beta that includes the above fixes "real soon".
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] ratyfu:
I've just lowered brightness and now my screen won't turn on anymore.

I also get a "Process System not responding" message at every boot, then immediately after clicking "wait" the screen goes dark again.

Apparently I fixed it by first increasing brightness again and then force closing Process System.
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] TheLoonyRebel:
Yeah I've been getting the same processing error on my end with the update. Also I've been trying to get a logcat of the VPN issue that I noted earlier but sadly it seems like Catlog doesn't want to freaking work at all on Lollipop 5.1 at all for me. Not to sound like a noob here but can someone remind me exactly how I can get a logcat again via ADB or at least a better app that might work so I can get a live logcat of what's going on when I try to use an VPN app like Tunnel Bear?
[Hisense Sero 7 Pro ROMs, Kernels, Recoveries, & Ot] ratyfu:
Here's a logcat from me regarding the VPN issue.

Hope it helps, as it's my first logcat :o

[MENTION=2440946]AngryManMLS[/MENTION]:

http://xdaforums.com/showthread.php?t=1726238

;tldr:

> Go to the ADB folder on your PC (if you don't have it, get it here: http://xdaforums.com/showthread.php?t=2317790 )

> Shift and right click anywhere in the folder then choose "Open command prompt here"

> Then type:

adb logcat > name of problem.txt

> whereas name of problem.txt obviously needs to be the name of the problem or just logcat.txt

> Make the problem occur on the Sero 7 Pro

> Back in command line press Ctrl+C to save the logfile.