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

[r3pwn]

Quick tip: to avoid many keyboard-related issues, use the leanback(android tv) keyboard. It adds controller support (removes touchscreen keyboard support) and doesn't mess up terminal emulator. Also, I started working on the open-source app to manage the LED.

 

[Steel01]

Quick tip: to avoid many keyboard-related issues, use the leanback(android tv) keyboard. It adds controller support (removes touchscreen keyboard support) and doesn't mess up terminal emulator. Also, I started working on the open-source app to manage the LED.

Oh, now that is useful. I installed hackers keyboard to get around the terminal problem on my Nexus 5. I was looking for a gamepad aware keyboard for this. It would be nice to not lose touch support, but I suppose it's easy enough to switch inputs.

I'm taking a semi-detour tonight and seeing about getting cm12 to boot on my Shield Tablet. I want to see how Grid and the controller stuff react on there. If it's different, it might give me an idea on how to fix it on the Portable. Once I get them working on one, it should be easy to make them work on the other.

 

[r3pwn]

Oh, now that is useful. I installed hackers keyboard to get around the terminal problem on my Nexus 5. I was looking for a gamepad aware keyboard for this. It would be nice to not lose touch support, but I suppose it's easy enough to switch inputs.

I'm taking a semi-detour tonight and seeing about getting cm12 to boot on my Shield Tablet. I want to see how Grid and the controller stuff react on there. If it's different, it might give me an idea on how to fix it on the Portable. Once I get them working on one, it should be easy to make them work on the other.

Okay. Regarding the LED stuff, I found quite a few more customization options than stock offers. Cool stuff, too, like making it flash when storage is being written to. I'll see if I can get the bulk of coding it done and uploaded by tonight. :good:

 

[zach jeremay]

please help

it keeps saying error this is for roth bla bla not for thor devices and i dont know what im doing wrong. im rooted, unlocked bootloader, ive tryed with cwm and twrp and they both wont flash it..

 

[r3pwn]

it keeps saying error this is for roth bla bla not for thor devices and i dont know what im doing wrong. im rooted, unlocked bootloader, ive tryed with cwm and twrp and they both wont flash it..

That's odd... My first zip flashed with cwm and my second/third zips flashed with twrp.

 

[Steel01]

it keeps saying error this is for roth bla bla not for thor devices and i dont know what im doing wrong. im rooted, unlocked bootloader, ive tryed with cwm and twrp and they both wont flash it..

Which TWRP did you try? It should work with my build here. I don't think it will work with Abagren's cwm, although I think someone modified it to assert as roth and released that later in the thread.

The naming of the device is somewhat of a pain. The internal name is thor, but the reported one is roth. I thought all the asserts were roth, though.

 

[zach jeremay]

Thanks so much man

Your recovery worked your the best man

 

[r3pwn]

Okay. Here we go. Feel free to contribute, anyone: https://github.com/r3pwn/roth-LEDControl

Settings don't stick across reboots,but that can be fixed relatively easily.

 

[Steel01]

Well, I am just not having any luck this weekend. All my attempts to get CM12 booting on the Shield Tablet are ending in bootloops. No adb, no nothing. I'm seeing if I can get CM11 to boot again and work forward from there. So, I don't have that as a comparison yet. There's a bunch of stuff in those init scripts that could make a difference, however. If and when I get that sorted out, I'll hopefully have a lead to bring back this way.

On the Grid front, it seems my stuck in queue problem was actually a server problem. I can't do the wifi check on stock, either. I finally got it to pick the proper region and I'm back to the problem I had before. Namely, a segfault in mediaserver that it blames on libstagefright_omx.so. It appears to be getting passed a null. For what reason, I don't know yet. Could be missing a lib or permission or setting.
@r3pwn: Cool. Can you run a build off and post it, perchance? I don't have t the app building stuff set up and Fedora doesn't have the tools in their repos (yet, F22 looks to be getting gradle at least). I'll eventually get it all set up, but I've been too focused on the rom stuff to care recently.

 

[r3pwn]

@r3pwn: Cool. Can you run a build off and post it, perchance? I don't have t the app building stuff set up and Fedora doesn't have the tools in their repos (yet, F22 looks to be getting gradle at least). I'll eventually get it all set up, but I've been too focused on the rom stuff to care recently.

Yeah, actually, I'm off to go watch a movie with my parents then help someone learn how to add customizations to kernels (at a source-code level. I only know a little bit, so it'll be a learning experience for the both of us.). I might be able to build it in between the two (I do all coding and compiling the device I intend to use the app on, in this case, my shield). There's a couple things not added yet, but I just wanted to get my idea of the implementation up there. It's more like a mostly-functioning skeleton app than anything else.

 

[r3pwn]

Here you guys go: https://www.androidfilehost.com/?fid=95916177934538823

 

[Steel01]

Been a busy couple days, so I haven't gotten much further. Still can't get my tablet booting cm to reference. But there's talk on the tablet forums that someone has all the Nvidia stuff working on PAC except for some stylus stuff. By implication, that includes grid and the controller. I have yet to get a response to see the code, though.

I did pull the adaptive backlight stuff over from the tablet tree. However, I haven't got to test it yet. Once I have that working, I'll drop another build.

 

[zach jeremay]

can you please add gamepad mapper back, its the one thing thats making me want to go back to stock

 

[MrPokination]

Hey, this sounds awesome but does the controller work %100 with all the games it used to work with (emulators, ect) also if the game mapper isn't there (see above post) then would snatching the apk from the original file system and putting it here work?

 

[r3pwn]

can you please add gamepad mapper back, its the one thing thats making me want to go back to stock

Hey, this sounds awesome but does the controller work %100 with all the games it used to work with (emulators, ect) also if the game mapper isn't there (see above post) then would snatching the apk from the original file system and putting it here work?

The controller does work 100%, but I'm not sure about the gamepad mapper. I would test, but I don't have access to my shield until Thursday.

 

[zach jeremay]

Yes, all I want is that if you guys make that happen you would be the best

 

[Rafostar]

So I started a proper post with quotes and all, but the android keyboard or textbox edit thing in Firefox did something weird and ate my post. And there's no undo... So this is my shorter and more miffed second attempt.

@Spleeno: My bad, I see that on my Nexus 5 now. I'll compare my dev tree with the N5's and see what the difference in that area is.

@r3pwn: On the Grid issue: I confirmed that this morning, but didn't have much time to look at the logs. I saw something about missing codecs, but that was at the top and maybe not related. I'll look more into it tonight. It could well be a worse underlying problem.

What are all required files for Grid? I have been trying to run Grid on my LG P880 (Tegra 3 phone) and after selecting game from Grid library in Shield Hub I have a green loading bar saying that it's starting my game and when it reaches 100% the app crashes :crying:

 

[MrPokination]

What are all required files for Grid? I have been trying to run Grid on my LG P880 (Tegra 3 phone) and after selecting game from Grid library in Shield Hub I have a green loading bar saying that it's starting my game and when it reaches 100% the app crashes :crying:

Hmm, its just a theory (a game theo...... wait) but maybe snatching all the nvidia brand apks from the /system/apps folder, put them in the cyanogenmod /system/apps folder and then take them out 1 by 1 to test which ones are needed and which ones do nothing, might work. it may sound tedious but I don't know any other way to do this without going into codecs and changing them. my guess is that it would be one of the apks that require online connectivity (obviously) I haven't tried it myself but it couldn't it would be anything other than the nvidia brand apks.
Hope it works

 

[Steel01]

Somehow missed or didn't get notifications for several posts. And it's been a busy week, so I haven't had much time to work on this. Hopefully tomorrow night or Saturday.

I'll try to pull in the gamepad mapper next time I have time. It's just a single apk, but I don't know what other dependencies it has. It does some low level mapping, so I wouldn't be surprised if it needs framework changes like the wireless controller pairing does.

I don't know what all grid needs. I do know that it uses hardware decoding, so the Tegra 3 may or may not have the physical capability to run it. If and when I get it running on here, might be able to give a better answer. If you copy the Nvidia apks around, make sure you pull from the android version you want to run on (eg, don't run anything from the Portable on Lollipop, instead pull from the tablet).

 

[Steel01]

Well, I still haven't done a whole lot here in the last few days. Been fighting back and forth with the Tablet. Finally got CM booting on it (posted a build over there if any are interested). And can the results of the proprietary apps be any more different...? Controller pairs and remains connected. Doesn't seem to ever get disconnected. It's still similar in that the pairing doesn't get saved correctly, however. But the Grid is what gets me. It's not even listed in the Hub... The logs say it's connecting to the gridserver and doing stuff, but I can't get to the list to start a game. *sigh* Well, at least I have some positive results with the controller that I can compare and hopefully stabilize here. Oh, and I also got audio working on the controller. Unfortunately, it's a bit... forced atm. Like can't get audio through the main speakers while the controller is connected.

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.

The buttons menu is on my latest internal build, but it only has the power menu options in it. I have no idea what changed except perhaps it really was an upstream issue. So, this should be fixed in the next build.

On the Controller Mapper: I tried to pull it in, but didn't get too far. Pretty much all of the triggers to this are in the framework. And I don't see anything in the Nvidia code drop implementing it. There are references, but they seem to be to missing code. I don't use this feature, so I'm not terribly inclined to put a lot of time into when there are other problems still existing. Plus, I believe there are third party apps on the store that implement similar functionality (eg. tincore).