I just flashed latest TWRP (3.1.0) and touchscreen doesn't work, wtf.. do I have to go with the old version?
[ROM] [OFFICIAL] LineageOS for the Shield Portable
- Thread starter Steel01
- Start date
I had the same problem, I had to use 3.0.0.0 from the multirom. I think 3.0.2.0 worked too.
Also, I just installed the latest nightly (4/9) yesterday (boy was that an exercise), I'm having a few issues:
1. So I set up a pin on my Shield... the lockscreen doesn't show 0 or the icon to accept your input. I had to hook up an external keyboard to get back into my Shield.
2. Installing SuperSU kept my device from booting. Certain root programs require SuperSU specifically. Is there a version of SuperSU that works?
Thanks!
I haven't really tested encryption on this device. Shouldn't be any reason for it not to work, though. If there's a aspect ratio problem on the pin entry screen, I'll try to look into it. But honestly? Why would you want encryption and pin entry on a clamshell gaming device?
SuperSU is not supported by LineageOS. We cannot control external projects and will not attempt to support them. Raise the issue on the SuperSU side. However, we do have a su add-on zip that works in all cases I've ever needed. If that doesn't work, then an issue can be reported.
TWRP issues should be talked about in the appropriate thread.
SuperSU is not supported by LineageOS. We cannot control external projects and will not attempt to support them. Raise the issue on the SuperSU side. However, we do have a su add-on zip that works in all cases I've ever needed. If that doesn't work, then an issue can be reported.
TWRP issues should be talked about in the appropriate thread.
I didn't use encryption, just a pin lock. I do have my google account on there - gmail, hangouts, etc. If it ever gets lost, I'd rather that information not be easily accessible.
Regarding SuperSU - OK thanks! I worked around the issues I had anyway.
I posted about TWRP in the TWRP thread, thanks!
Regarding SuperSU - OK thanks! I worked around the issues I had anyway.
I posted about TWRP in the TWRP thread, thanks!
Another thing I've noticed is that there doesn't seem to be any support for the GPS in this LineageOS build? I tried a few GPS apps and they said there is no GPS present in the device (with location set to device only and location access granted). Thanks!
I personally used it as navigator once (Google Maps navigation), when my phone was broken. It took some minutes (yes, minutes) to lock, but worked beautifully.
Hmm everything else working fine apart from geforce. Strangely on my nvidia shield tablet, running a build by Bitobsession on a 6.0.1 rom geforce works fine. Any future chances at all of trying to get geforce working please?
From what I recall, the problem is that the Shield Portable support was removed from the Marshmallow version of the Geforce app.
Steel01, I ran into another issue. The HDHomeRun TV app has no sound when used on the Shield Portable with this LineageOS build. It does have sound with the stock rom. Video works fine. Do you think this is an issue on your end or HDHomeRun's end (I don't see reports of this anywhere else)?
Also, I cannot seem to wake up the Shield with an external keyboard hooked up via the OTG adapter. I always have to walk up to it and hit the button (I'm using it in console mode).
Thanks!
Just chiming in, I'm enjoying the build quite nicely, it generally works fine for what I mainly used my SHIELD for (emulation 99% of the time), but it DOES seem to have one small issue for me where, when I wake the system up from being suspended, the framerate for the entire system seems to drop significantly, to where every game I play on it just looks flitchy. It's not emulator-specific, as I'm still experiencing it even when browsing system setting or using the internet, and it's not that the device is processing slowly, because all games still run at full speed, it's just the screen is having trouble displaying enough frames per second to show them off. Restarting seems to fix it, but it only lasts until the next time I close the lid and suspend it again - after that I have to restart her again to get her running at full speed again.
Not a deal breaker, I can work with it, I just wanted the issue reported.
Not a deal breaker, I can work with it, I just wanted the issue reported.
Addendum: after some tinkering, I managed to find a solution, though for the life of me I don't know why it would work this way. Apparently the latest version of TWRP (3.1.0-0) was causing it, because flashing to 3.0.2-0 seems to have fixed it. No idea why it would be like that, but I'm happy to have my emulation machine back at full performance.
Thanks for all your hard work, guys, there's lots of little guys like me that really appreciate it.
Thanks for all your hard work, guys, there's lots of little guys like me that really appreciate it.
Further addendum: apparently "fixed" is the less accurate term, it's more like "diminished." I still have it pop up every now and then, but it's infrequent now, and when it does occur it's not as severe. Sorry for the excess posting, I didn't mean to use up so much page space when I started out to report this issue, I've just been discovering it as I go along.
Hey, wassup? And what's good with the 14.1 version? Let us know. About that nougat support thank you for your rom and work 
The controller can be used wired no problem. There's a post on the tablet forums that I believe I referenced here already that explains a command line method to pair a wireless controller. Just haven't made an app to handle that in a user friendly manner yet. So the answer is technically yes, but not usably.
14.1 is dead in the water as it stands right now. egl_bad_alloc on home screen display. I had something work once, but I haven't been able to reproduce since. I honestly have no clue what it's doing. So, I wouldn't hold much hope for the Portable getting any support past M. I'll probably take a shot at O, but if N wasn't happy, I seriously doubt O will be any better.
14.1 is dead in the water as it stands right now. egl_bad_alloc on home screen display. I had something work once, but I haven't been able to reproduce since. I honestly have no clue what it's doing. So, I wouldn't hold much hope for the Portable getting any support past M. I'll probably take a shot at O, but if N wasn't happy, I seriously doubt O will be any better.
how would I do a complete wipe? at the moment, CM is just booting and just Optimizing apps on and on and I can get into TWRP and thats about it
never mind, I got it back to stock using this site. Back to square one lol
http://nvidiashieldzone.com/the-nvidia-shield-portable/tutorial-restore-to-stock-image-port/
Hey man! So, I work on Molly (the ADT-1), which is one of the only other Tegra 4 devices. We may be able to help each other.
We had to hack up EGL to make it work with MM, and I've heard the hack we used applies to N as well. I may be able to help you with that. We use dmitrygr's gl hex edit to get our GL blobs to work on MM.
Feel free to take a look at Molly's device tree if you think that'd be applicable to you. Its in the git organization below (we called it libmhax).
But, I also pose a separate question, if you would, would you take a look at our kernel repo? Our kernel source (https://github.com/adt1-dev/android_kernel_google_molly on branch cm-13.0) builds/boots with 6.0.y ROM's, but as for 7.0+ it refuses to boot (Continual services being killed, which I have a hunch is SE Linux related). I am at an utter loss why our services refuse to start correctly.
New posts
-
[GUIDE] All about unlocking bootloader, TWRP and rooting Redmi Note 8/8T- Latest: the_weird_aquarian
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone