[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Oswald Boelcke:
RR-N-v5.8.3-20170605-i9305-Official-HWC

BLUF:

Great ROM, the RR-N-v5.8.3-20170605-i9305-Official-HWC. Thanks very much in deed to @rodman01 for the superb job well done!:good:

No issues at all (so far)! Substratum working. The device is GApps-free. More details below.

Booted into TWRP (3.0.2-1) and restore my Nandroid backup with RR-N-v5.8.3-20170510-i9305-Official. Back into system, uninstalled PitchBlack Origins, Substratum, and NanoMod to initiate a clear start with the new ROM.

Back into TWRP. Dirty (i.e. only wiped dalvik and cache) flashed RR-N-v5.8.3-20170605-i9305-Official-HWC on top of RR-N-v5.8.3-20170510-i9305-Official. Flash occured without any issues including the flash of Magisk v12. Booted into system.

Initial boot took only about 3 - 4 minutes - no bootloop, no problems at all.

This time, SELinux status was on "permissive" after flashing the ROM.

Baseband/modem was available.

Magisk v12 was successfully installed. Magisk Manager apk working.

The Grenify Magisk module was still available without the requirement to go back into TWRP and to flash it.

(Remark for those how haven't noticed yet: Magisk Manager is no longer available in Google Play Store. Details are available here).

The ROM inherent kernel is not compatible with Boeffla-Config apk.

I enjoy that the revised kernel now also contains my favourite governer, zzmove. Going to play with its settings through Kernel Adiutor.

GPS is working.

Booted back into TWRP and flashed NanoMod, back into system.

The system is GApps-free!

Good localisation in energy saving mode (WiFi and mobile network only). See second last screenshot.

Play Store is working. Downloaded Substratum and PitchBlack Origins. Installed Substratum without any issues and in turn the overlays from PitchBlack.

Bluetooth is working (with wireless Stereo-earplugs).

Music is working in stereo.

Network and messenger are working.

Excellent charging time!

I personally like that the battery LED seems to be more dimmed than before.

On Locked Screen, not only voltage and battery temperature are indicated as before but also (loading?) amperage; however, latter always shows 0 mA.

[EDIT (20170607)]: Tethering is working, at least with IP4. Please refer to post #6766 for details.

[EDIT (20170607)]: Please refer to post #6776 for my first BBS (nearly) idle dumps.

I've to admit that I'm slightly unhappy with a drainage of about 4% per hour and nearly 25% Awake (Screen off) time.

Kernel wakelocks are pretty high. UPDATE: My initial glance into the first two dumps makes me to assume that WiFi is keeping it awake. The device has already a fixed IP assigned but it was probably the location where I parked it over night. It's actually the place in our home with the worst WiFi reception, and I simply believe it lost WiFi quite often and had to search for the network again. Didn't think of that before. I now took at first a 6-hours idle dump (attached) with the device in airplane mode - and this one is very satisfying:

Battery drainage - 0.8% per hour

Deep Sleep (): 6 h 6 s 99,5%

Awake (Screen Off) (): 1 m 28 s 0,4%

"battery-monitor" (): 42 s Cnt(c/wc/ec)38/0/39 0,2%

"PowerManagerService.WakeLocks" (): 26 s Cnt(c/wc/ec)52/0/0 0,1%

"mdm_hsic_pm0" (): 20 s Cnt(c/wc/ec)45/0/0 0,1%

Just charging the device, and I'm going to take a new idle dump overnight with WiFi on but at a location with excellent reception.

UPDATE (20170608): To the mentioned post #6776, I attached a new BBS idle dump taken for 13.5 hours with WiFi enabled and in a suitable WiFi environment.

This dump looks really decent to me and proves that the above mentioned first dump showned poor battery life simply due to my own fault. It's now very clear to me that sound dumps require a suitable environment. I apologise if it looks that I initially blamed the ROM or the kernel.

Level lost [%]: Bat.: -18%(100% to 82%) [1,3%/h]

Deep Sleep (): 12 h 16 m 25 s 91,5%

Awake (Screen Off) (): 1 h 7 m 55 s 8,4%

Screen On (): 18 s 0,0%

Wifi On (): 13 h 24 m 39 s 100,0%

"wlan_rx_wake" (): 33 m 49 s Cnt(c/wc/ec)3438/0/3438 4,2%

"battery-monitor" (): 29 m 39 s Cnt(c/wc/ec)1778/0/1779 3,7%

"mdm_hsic_pm0" (): 14 m 39 s Cnt(c/wc/ec)1903/2/0 1,8%

"suspend_backoff" (): 10 m 19 s Cnt(c/wc/ec)62/0/62 1,3%

"alarm_rtc" (): 9 m 23 s Cnt(c/wc/ec)1345/59/42 1,2%

"wlan_wd_wake" (): 8 m 35 s Cnt(c/wc/ec)4875/0/0 1,1%

Despite the from my point of view very acceptable battery drainage and kernel wakelocks, the Awake (Screen Off) time is still much too high, and I need to work on that.

Going now to explore further including stability, reboots, battery drainage etc. Certainly checking if any other of strantonz's kernel is working with this ROM.

OT: Congratulation to @rodman01 for 9,000 thanks. WELL DESERVED!