[ROM] [OFFICIAL/UNOFFICIAL] Cyanogenmod 13.0 for Shield Portable

[deathblade200]

I did enable adaptive backlight in the device tree. All the options are there and work. I'm just not certain that the hardware is actually doing anything with it. My screen dimmed to roughly 60% and wouldn't budge regardless of ambient light. This will be on the next build when I get to it.
.

are you saying you tried to enable this on the shield portable? if so its a waste of time the portable doesn't have an ambient light sensor or even a camera so it has no way to detect the current room lighting

 

[Steel01]

are you saying you tried to enable this on the shield portable? if so its a waste of time the portable doesn't have an ambient light sensor or even a camera so it has no way to detect the current room lighting

Yeah, I was wondering. Someone asked about prism. I saw a reference to the smartdimmer stuff in the adaptive backlight part of the Shield Tablet tree and pulled it over. It's all exposed to the software, but I wonder if it actually does anything... After I pulled this in, the color calibration stuff suddenly started working, but that might be a complete coincidence and was caused by something else.

 

[deathblade200]

Yeah, I was wondering. Someone asked about prism. I saw a reference to the smartdimmer stuff in the adaptive backlight part of the Shield Tablet tree and pulled it over. It's all exposed to the software, but I wonder if it actually does anything... After I pulled this in, the color calibration stuff suddenly started working, but that might be a complete coincidence and was caused by something else.

smartdimmer is prism which a user discovered over at the nvidia forums and even a way found a way to disable it. I would link you the thread but the forum won't let me

---------- Post added at 10:49 PM ---------- Previous post was at 10:37 PM ----------

Yeah, I was wondering. Someone asked about prism. I saw a reference to the smartdimmer stuff in the adaptive backlight part of the Shield Tablet tree and pulled it over. It's all exposed to the software, but I wonder if it actually does anything... After I pulled this in, the color calibration stuff suddenly started working, but that might be a complete coincidence and was caused by something else.

since the site won't let me edit my post and I kind of rushed through the last post the smartdimmer you are looking for is at /sys/class/graphics/fb0/device/smartdimmer/enable

CriticalComposer and Xodustrance over at the nvidia forums discovered you can disable it by using the init.d script

#/system/bin/sh

echo "0" > /sys/class/graphics/fb0/device/smartdimmer/enable;

so I'm sure you could incorporate that into your rom

 

[Steel01]

I'm in the process of uploading builds from last night. This build will have everything I've mentioned previously plus upstream cm changes up to last night.

So, I'm not seeing much on what this prism thing is. Based on the name smartdimmer, it sounds like a form of adaptive backlight. Does anyone have a decent explanation or link to it? And why would people want it turned off?

 

[leolawliet]

I'm in the process of uploading builds from last night. This build will have everything I've mentioned previously plus upstream cm changes up to last night.

So, I'm not seeing much on what this prism thing is. Based on the name smartdimmer, it sounds like a form of adaptive backlight. Does anyone have a decent explanation or link to it? And why would people want it turned off?

I notice some annoying flicker of the backlight randomly which I guess is just auto adjusting but when I disable prism it's gone.

 

[Steel01]

Alright, new build is up.

Hmmm... I've never seen my display do anything like that. I'll have to double check, but I think the current build will only enable smartdimmer if adaptive backlight is enabled.

 

[deathblade200]

Alright, new build is up.

Hmmm... I've never seen my display do anything like that. I'll have to double check, but I think the current build will only enable smartdimmer if adaptive backlight is enabled.

it makes the screen look washed out and some people like myself like complete control of the brightness which prism does not allow

 

[leolawliet]

Alright, new build is up.

Hmmm... I've never seen my display do anything like that. I'll have to double check, but I think the current build will only enable smartdimmer if adaptive backlight is enabled.

Thank you for working on an aftermarket firmware for the Portable, this gives me much hope. I'll keep an eye out and check the progress every now and then.

Just one quick question, other than GRID not working and Gamepad Mapper not working would that interfere with full button functionality on emulators that currently support the Portable button scheme? I'm not too big a fan of GRID lately, or gamestreaming. I can deal with no on-screen gamepad mapper, there's alternatives.

 

[r3pwn]

Thank you for working on an aftermarket firmware for the Portable, this gives me much hope. I'll keep an eye out and check the progress every now and then.

Just one quick question, other than GRID not working and Gamepad Mapper not working would that interfere with full button functionality on emulators that currently support the Portable button scheme? I'm not too big a fan of GRID lately, or gamestreaming. I can deal with no on-screen gamepad mapper, there's alternatives.

Nope, you're good to go. All gamepad buttons are working.

 

[Steel01]

Well, I got Grid working on CM on the tablet. The unfortunate news is that I think we'll have to wait for Nvidia to release lollipop for the portable before I'll be able to make it work here. The tablets stock OMX libs don't work on CM, but the ones in Nvidias code drop do. The OMX libs pulled in from the adt-1 work on the portable for most hardware acceleration, but I'm beginning to think they're missing stuff that the Grid uses. Well, I'm going to continue poking at both. Still plenty of problems large and small that need fixed. And a whole new platform coming in May that I'd like to have all this done before so I can basically just drop in the proprietary apps and go.

 

[r3pwn]

Well, I got Grid working on CM on the tablet. The unfortunate news is that I think we'll have to wait for Nvidia to release lollipop for the portable before I'll be able to make it work here. The tablets stock OMX libs don't work on CM, but the ones in Nvidias code drop do. The OMX libs pulled in from the adt-1 work on the portable for most hardware acceleration, but I'm beginning to think they're missing stuff that the Grid uses. Well, I'm going to continue poking at both. Still plenty of problems large and small that need fixed. And a whole new platform coming in May that I'd like to have all this done before so I can basically just drop in the proprietary apps and go.

Last I asked, Lollipop for the portable was "on it's way", but it's been absolute silence since then.

 

[YamazakiRobert]

Last I asked, Lollipop for the portable was "on it's way", but it's been absolute silence since then.

on geforce forum the say the update 101 is the last kk version, lets wait for lp (maybe we recive 5.1 version, at least thats is my wish )

---------- Post added at 10:57 AM ---------- Previous post was at 10:55 AM ----------

Alright, new build is up.

Hmmm... I've never seen my display do anything like that. I'll have to double check, but I think the current build will only enable smartdimmer if adaptive backlight is enabled.

thanks for the option to disable the active back-light, whit that option i have some problems with movies

 

[Steel01]

To mirror what I said in the tablet thread: I'm putting the proprietary app stuff on hold for the time being to work on getting the rom more stable. Some things still don't work right, plus I still want to get multirom working period.

@r3pwn:
Can you transfer your shield app ownership over to the cm-shield org? Or would you rather me just fork it? One of these here soon days I want to get the dev stuff set up and start adding stuff like smartdimmer on/off (yeah, the auto brightness stuff really doesn't affect it) and console mode switcher to it. And set it up to work on the portable and tablet, autodetecting what's valid for each.

Edit:
New build in the first post. I updated a hardware button setting that enables more options in the button menu.

 

[zach jeremay]

What is multirom??

 

[r3pwn]

@r3pwn:
Can you transfer your shield app ownership over to the cm-shield org? Or would you rather me just fork it? One of these here soon days I want to get the dev stuff set up and start adding stuff like smartdimmer on/off (yeah, the auto brightness stuff really doesn't affect it) and console mode switcher to it. And set it up to work on the portable and tablet, autodetecting what's valid for each.

Yeah, I'm actually at my PC right now. I'll see if I can transfer ownership.
EDIT: Done! I have added a couple commits since last build. If you have it installed, uninstall it because that first version was signed with my dev keys and I'm not giving out my dev keys.

What is multirom??

Allows you to have multiple ROMs installed simultaneously and gives you the choice of which one you want to use upon boot.

 

[leolawliet]

So having official Lollipop sources from NVIDIA should speed up development, right?

 

[r3pwn]

So having official Lollipop sources from NVIDIA should speed up development, right?

Yep, just a bit. Looks like @Steel01 has pretty much everything (except controller and grid) working.

 

[Steel01]

New build is up. Nothing changed except for upstream cm12. There was a report on the tablet thread that new gapps caused wakelocks and cm pushed fixes to counter that. This build should have those fixes.

Yeah, there isn't a whole lot more that can be done to the ROM before Nvidia drops code and vendor blobs for lollipop. I still need to import the selinux policies. The control app could have several things added to it, but I haven't got to setting that stuff up yet. Most of my android dev time is going to either multirom on the portable or trying to fix bugs on the tablet (fwiw: there's still major ones). Course, I've been majorly distracted from all of this by the new Descent kick starter...

 

[r3pwn]

New build is up. Nothing changed except for upstream cm12. There was a report on the tablet thread that new gapps caused wakelocks and cm pushed fixes to counter that. This build should have those fixes.

Occasionally, while playing a game that's GPU-intensive and somewhat related to goats (that should narrow it down, I don't want to name anything specifically), something crashes, the device freezes, then it (the device) reboots. I tried to grab a logcat of it happening, but I have yet to get it to happen again (well, it's happened again, but not while attached to logcat). I am getting a crap-load of logspam from some audio service though. I'll report back later to see if we can make it stfu.

 

[Steel01]

I haven't done much gaming on the portable since I started working on this, so I haven't had a chance to see a problem like that. It might have to do with using the vendor blobs from a different device. But... I wouldn't think so. If you get that log, I'll want to see it. If only logcat did like kmsg and kept a last_logcat.

I've been playing around with cloning console mode tonight. I can get it set up, but I haven't figured out a way to do it smoothly yet. The first code block of the two sections is a script that will turn console mode on or off (run as root). Reboot for the changes to take effect. The second part I think should be automatic, but the window manager isn't automatically adjusting it's resolution, so it has to be forced and all services (well, probably just a couple, I'm just too lazy atm to figure out which ones really matter) restarted. And if you have a higher resolution monitor or tv, you should be able to change the resolution in the enable script to anything feasible. I don't have anything higher to test with, though.

WARNING: If you run this with no HDMI monitor or tv, you will have no display and will have to reverse the change via adb or factory reset.

#!/system/bin/sh

# Enable console mode                        
                                             
setprop persist.sys.hdmi.resolution 1920x1080
setprop persist.tegra.hdmi.primary 1   
setprop persist.sys.hdmi.resolution Max
setprop persist.tegra.stb.mode 1      
setprop persist.tegra.panel.rotation 0

reboot

wm size 1920x1080
restart

#!/system/bin/sh

# Disable console mode

setprop persist.sys.hdmi.resolution ""
setprop persist.tegra.hdmi.primary 0
setprop persist.sys.hdmi.resolution Max_60
setprop persist.tegra.stb.mode 0
setprop persist.tegra.panel.rotation 90

reboot

wm size 1280x720
restart

I still haven't got the app build environment set up to look at putting this into the control app. From the looks of a similar app on the Nexus 10, we should be able to fairly easily detect an hdmi cable being (un)plugged and take appropriate action. Though, what to do on unplug is debatable. I don't know how Nvidia turns the main screen back on without a reboot atm.