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

[dreamss]

i know this is unrelated to cm but any had their gamepad,analog,start fail? seema the whole gamepad board is fried


wondering if anyone know the point of failure and maybe have a fix since its a common issue with the roth

 

[Blash85]

Anyone having audio problems with 17/09 nightly? I made a clean install and got weird feedback sounds during first system start.

Inviato dal mio Nexus 5X utilizzando Tapatalk

 

[dreamss]

anyone ever look into CEC passtru for kodi on the shield portable? its supported on the shield console but it would be nice for the older shields

also would this rom support the madcats mojo? tegra4 based shield like device without a screen


my shield power issues are gone now, seems like it had to to charge the battery a few times and now it stays at 100% charge, its weird lol

 

[tincore]

Thanks for the effort!

Yesterday I was able to build this firmware but not without issues.

According to the wiki extract proprietary blobs needs to be executed.
https://wiki.cyanogenmod.org/w/Build_for_roth

My current firmware was an older nigthly build
After running
$ ./extract-files.sh

4 files were missing. Some are touchscreen related.
...
adb: error: remote object '/system/bin/rm_ts_server' does not exist
adb: error: remote object '/system/lib/hw/gps.tegra.so' does not exist
adb: error: remote object '/system/lib/hw/ts.default.so' does not exist
adb: error: remote object '/system/lib/librm_ts_service.so' does not exist
..

This made the build fail.

I tried to build with copies of those files found on the internet but, although the build succeeds, the touchscreen is not working.

Does anybody know where I could get those?

 

[RLShiftyDoggit]

Anyone have custom settings with kernel auditor I'm trying to increase batt life w/o killing performance too much also has anyone got HL2 or portal running on 6.0.1 and if so how

 

[Spleeno]

has anyone got HL2 or portal running on 6.0.1 and if so how

iirc you cant get it to run on marshmallow or cm13 because they removed the full blown opengl needed to run those games from the libs. so you'd have to try lollipop or cm12 to get them to run.

 

[Steel01]

That's not exactly correct. The shield portable drivers only support gles (basically mobile opengl). The tablet and console also support full blown opengl. The android 5.1 versions of portal and hl2 supported both gles and opengl. As far as I can tell, the android 6.0 versions removed gles support, leaving only opengl. Which the portable physically does not support (some floating point stuff, if I understood correctly). So, the only thing I can think to try is getting a copy of the 5.1 apk and side loading it to cm13, ignoring prompts to update. I've not heard of anyone trying this however, so no clue if it would work.

 

[Spleeno]

no idea how I twisted that in my head...
btw did you ever manage to get fedora running on the shield portable?

 

[Steel01]

btw did you ever manage to get fedora running on the shield portable?

Fedora boots just fine and has for a while. At some point, there was problems with gnurou's patches which caused the fbdev driver to stop working. Opentegra works for rendering; however, it doesn't support rotation atm. Looks like someone recently started working on the driver again, though. Also, no sound. Gnurou says everything is there, but for some reason, it just doesn't work. I've got some scripts on my dev box that'll build a working image, just haven't uploaded them anywhere since I didn't think there was much interest.

@ anyone interested in cm14:
It does boot, ish. However, when the launcher starts to display, the graphics stack crashes. I've looked into it a little bit, but haven't found exactly why yet. Maybe one of these days after the tablet support is finished.

 

[Spleeno]

well, with xrandr not working I might as well not even bother...

 

[Blash85]

@Steel01

Hello, first of all thanks again for your work.

I wanted to report a problem that maybe is well known.

I tried to solve it in the following ways:
- Wiping everything and flashing the 110 system image downloaded from Nvidia website;
- Trying using different nightlies, everytime doing a clean install;
- Using different kind of Open Gapps packages (micro, nano end even pico) released on different days;
- Not restoring app data when reinstalling apps during the system setup;
- Doing the various operations both with the microSD inserted and not inserted.

The problem is the following: after the CyanogenMod splash screen, the screen "Preparing to start... Starting apps..." appears, and then again the CyanogenMod splash screen. This cycle is repeated for 3-4 times, sometimes more, sometimes just once, before Android correctly boots.

Considering I tried any imaginable solution, I'm inclined to think this is a common problem, but I wanted to write about it anyway.

Are there any hopes this behaviour will go away with 14.1?

 

[Steel01]

Hmmm... So that's not just something weird happening to only my device then. I've been seeing that for a couple months now, but don't reboot terribly often, so I haven't looked to much at it. I'll see if I can once the tablet is clear for 14.1.

I haven't even tried to fix 14.1 here since the last time I mentioned it. I hope I can get it to work, but no guarantees.

 

[Blash85]

Kinda glad to read I'm not the only one, as I thought.
I strongly suspect this has something to do with the problem that official update 103 had: at every boot it ran the optimization of every app installed, making the boot procedure a real pain in the a**. With update 106 that was partially solved, while I never tried the 110 alone.

 

[Steel01]

Alright, think I tracked down the bootloop issue. Should be in the next nightly. Unfortunately, I'm not having much luck with cm-14.1 atm, though.

https://review.cyanogenmod.org/174159

 

[Blash85]

Alright, think I tracked down the bootloop issue. Should be in the next nightly. Unfortunately, I'm not having much luck with cm-14.1 atm, though.

https://review.cyanogenmod.org/174159

You da man!!
Great, looking forward to the release of the next nightly!

About 14.1.. what about the release of a stable/snapshot CM13 instead? Just to give a reference point to the modding community. Otherwise it seems like an "unfinished business", if you know what I mean.

 

[Steel01]

Well, appears I spoke too soon. Cm-13.0 got demoted to nighlties again. So no build until Sunday.

I've never had a stable build done before. I guess I can try when the next point release drops. AFAIK, there's no huge bugs on the portable like there is for the tablet, so I don't feel too bad about making a stable release. I know of some annoyances, but if there's any bad problems, let me know so I can try to fix it first.

 

[Blash85]

Well, appears I spoke too soon. Cm-13.0 got demoted to nighlties again. So no build until Sunday.

I've never had a stable build done before. I guess I can try when the next point release drops. AFAIK, there's no huge bugs on the portable like there is for the tablet, so I don't feel too bad about making a stable release. I know of some annoyances, but if there's any bad problems, let me know so I can try to fix it first.

As soon as the next nightly comes out I'll do a clean install and then report anything

 

[Steel01]

Well, update is out. And I meant to say weeklies, not nightlies in my last post...

Ran a couple reboots and seems good to me so far. I think I saw one bootloop on my test build, but compared to the hundreds before, that's doing a *lot* better. Still seeing the dexopt screen every boot, however. But at least it only lasts a couple seconds, so it's not bugging me outside of the dev side cringing that something isn't working exactly right...

 

[Blash85]

I tried with latest nightly, after a clean install.. Sad to say nothing changed.. At first boot it soft-rebooted four or five times.. App optimization, CM splash screen app optimization etc. and finally booted to home screen.
I tried stock firmware but it really feels old and I miss the ability to use the microSD as internal memory. And it is not bug free (had a soft reboot after closing Asphalt Extreme).
Anyway, with this CM mess and migration to Lineage, what will happen to this ROM?

 

[Steel01]

Oh? Meh. Mine went from like infinite boot loop to like one or two at the most. Got a suggestion from another Tegra 4 dev that I'm going to try eventually. Maybe it'll help.

I'm definitely continuing with Lineage for all my devices. The aforementioned dev got cm-14.1 booting on another Tegra 4 device, so I'm going to be coordinating with him to see if I can duplicate on here. We should be able to run N pretty solidly on the portable once I can get surfaceflinger to stop crashing on boot.