Database Info

[ROM] CyanogenMod 7 for the ZTE Blade :: V7.1.0 (9 Oct 2011)

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 2.3 (Gingerbread), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
First time flashing CyanogenMod 7 to the ZTE Blade, or coming from another ROM?
Root the device and install ClockworkMod Recovery. Instructions are available here.
Perform a NANDroid backup of your current ROM.
Format the system, data & cache partitions of your device.
Perform a factory reset.
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Upgrading from earlier version of CyanogenMod 7?
Perform a NANDroid backup of your current ROM.
Flash CyanogenMod (your Google Apps will be backed up & restored automatically).
Issues?
Experience issues? Please provide the following info:
If the device was hard reboot, please provide the file "/proc/last_kmsg".
If the device was soft reboot or is "bootlooping", please run a logcat and provide the full output.
Please use Pastebin when possible.
Download Links:
Official post​
CyanogenMod:
Latest version: update-cm-7.1.0-Blade
Download: link
Mirror: link
MD5sum: 580c9db7463a1d737f9890e4ea488ccf​
Google Apps addon:
Version: gapps-gb-20110828
Mirror: link
Mirror: link
Version: Google Talk with video addon
Mirror: link
Mirror: link​
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!

I didn't see the market after i flash, any solution to get the market?

andy8274 said:
I didn't see the market after i flash, any solution to get the market?
Click to expand...
Click to collapse
Dear Andy8274,
Usually people say "hello", "please", "thanks", and at least start reading the entire post, even sometime use the research tool, before asking this kind of question.
Best regards,
Tuc

maybe You have to install gapps? I don't know :/
I can't bring A2SD into this rom, DarkTremor beta and stable- system stays in blank, black screen. My method (http://forum.xda-developers.com/showthread.php?t=1281887) works, but by unknown reason free space on /data still falls down like a rock (app, app-private and data moved to SD)

uosiumen said:
I can't bring A2SD into this rom, DarkTremor beta and stable- system stays in blank, black screen. My method (http://forum.xda-developers.com/showthread.php?t=1281887) works, but by unknown reason free space on /data still falls down like a rock (app, app-private and data moved to SD)
Click to expand...
Click to collapse
I had the same issue in the GSF b27 while trying your method. and finally managed to make A2SD working perfectly using the following commands in the terminal emulator:
Code:
su
a2sd reinstall
a2sd datasd
I don't know if it can help...
Tuc

Tugdu77 said:
I had the same issue in the GSF b27 while trying your method. and finally managed to make A2SD working perfectly using the following commands in the terminal emulator:
Code:
su
a2sd reinstall
a2sd datasd
I don't know if it can help...
Tuc
Click to expand...
Click to collapse
So, you've installed dark tremor A2sd? Out it was built-in your system?
Sent from my ZTE-BLADE using XDA App

Clean install, all was going well and now.
Then tried to make a call, died had to pull the battery out.
In addition i can't make calls or connect to the internet, setting are all ok

uosiumen said:
So, you've installed dark tremor A2sd? Out it was built-in your system?
Click to expand...
Click to collapse
I'm still using GSF b27: A2SD was already built-in, just needed to be activated. So once you installed A2SD, try to activate it with my previously described method.
It also found an app that could help: http://forum.xda-developers.com/showthread.php?t=917377
Tuc

uosiumen said:
maybe You have to install gapps? I don't know :/
I can't bring A2SD into this rom, DarkTremor beta and stable- system stays in blank, black screen. My method (http://forum.xda-developers.com/showthread.php?t=1281887) works, but by unknown reason free space on /data still falls down like a rock (app, app-private and data moved to SD)
Click to expand...
Click to collapse
Use S2E app from the market it working OK with CM7.

I can confirm:
CM7.1 + S2E (market) = victoria
--
simono_pl: dzięki

GAMES work great
Hiya,
Just wanted to say that this ROM is the best for 3D (for me anyway). Been using GSF for a few months now and I gave up on angry birds (sluggy) and others.... Just put CM 7.1.0 and Angry birds workds like a dream
General UI (scrolling and oppening apps) it is slower than GSF (dunno why, maybe the theme?) But performance wise (once the stuff has been opened) it seems to run faster and thats what I want. Any chance of having a less heavy theme available?
WIFI - Works
CALLS - WORK
LATITUDE - works (even checks in automatically, never managed that on GSF)
GAMES - WORKS LIKE A DREAM
BLUETOOTH A2D - Works perfectly. Playing music with (andless, I love that prog, so easy UI and folder view ...)
So, basically, All good work guys I just wish for a less heavy UI

Hello,
I am not a Blade owner but one of my friends is one and he asked me to upgrade his phone to CyanogenMod. As I am not the owner I would like to ask you how to install the rom if the device is a gen1 one model and what I should download. Thanks in advance and sorry for OT!
Sent from my Optimus 2X using Tapatalk

ironman159 said:
Hello,
I am not a Blade owner but one of my friends is one and he asked me to upgrade his phone to CyanogenMod. As I am not the owner I would like to ask you how to install the rom if the device is a gen1 one model and what I should download. Thanks in advance and sorry for OT!
Sent from my Optimus 2X using Tapatalk
Click to expand...
Click to collapse
install ClockworkMod 3 and Bobs your uncle
Btw. Played a bit more with interface options (quite a few ...) and managed to get a performance quite similar to the GSF one so quite happy now
all seems to work for me

What settings have you guys changed for better performance?

obsydian said:
Clean install, all was going well and now.
Then tried to make a call, died had to pull the battery out...
Click to expand...
Click to collapse
+1
Solution?
Edit: going in the zte entry of the application menu and calibrating the proximity sensor fix this

ironman159 said:
Hello,
I am not a Blade owner but one of my friends is one and he asked me to upgrade his phone to CyanogenMod. As I am not the owner I would like to ask you how to install the rom if the device is a gen1 one model and what I should download. Thanks in advance and sorry for OT!
Sent from my Optimus 2X using Tapatalk
Click to expand...
Click to collapse
You want to use the Gen1 to Gen2 tpt upgrade - http://forum.xda-developers.com/showthread.php?t=1258855

hmmmm 7.1.0 is nice in performance as now more heap size .more overclocking level i can reach upto 787 stable
but it has a really slowww interface
games work well without glitches .
but many hd gameloft latest games are unplayable i know it is bcoz of hardware .but sometimes software can enhance hardware performance as do overclocking
in next mod if possible cyanogen can increase gaming performance

applicationz said:
hmmmm 7.1.0 is nice in performance as now more heap size .more overclocking level i can reach upto 787 stable
but it has a really slowww interface
games work well without glitches .
but many hd gameloft latest games are unplayable i know it is bcoz of hardware .but sometimes software can enhance hardware performance as do overclocking
in next mod if possible cyanogen can increase gaming performance
Click to expand...
Click to collapse
There is only so much that can be done with a 600mhz armv6 phone. Most of those gameloft hd games were designed for armv7 phones at around 1ghz, the blade is half that speed.
The interface can be sped up by turning on 16 bit transparency in cyanogenmod performance settings, that allows it to use more hardware acceleration for drawing the interface. It causes a few minor graphics glitches though. You can also replace the launcher, remove the theme chooser & do a few other things to speed it up.

wbaw said:
There is only so much that can be done with a 600mhz armv6 phone. Most of those gameloft hd games were designed for armv7 phones at around 1ghz, the blade is half that speed.
The interface can be sped up by turning on 16 bit transparency in cyanogenmod performance settings, that allows it to use more hardware acceleration for drawing the interface. It causes a few minor graphics glitches though. You can also replace the launcher, remove the theme chooser & do a few other things to speed it up.
Click to expand...
Click to collapse
see now gameloft games are designed for 1 ghz processor as you are saying
so basically without overclocking it should work on 1 ghz processor with switched off graphics or without any graphical setting
now in this mod we have got 810 mhz we can provide more vm maybe we could reach 900mhz in next kernel .we could enable graphics using blade buddy and we have 512mb ram which can handle heavier processes .we could reduce those 100mhz gap in running game using graphics ,,ram and other system properties

applicationz said:
see now gameloft games are designed for 1 ghz processor as you are saying
so basically without overclocking it should work on 1 ghz processor with switched off graphics or without any graphical setting
now in this mod we have got 810 mhz we can provide more vm maybe we could reach 900mhz in next kernel .we could enable graphics using blade buddy and we have 512mb ram which can handle heavier processes .we could reduce those 100mhz gap in running game using graphics ,,ram and other system properties
Click to expand...
Click to collapse
It's not just the mhz, armv7 processors are more efficient, faster at the same speed & provide more features. Some Gameloft games will run, but you shouldn't expect them all to run, or run well, they were designed for higher end phones.

Ubuntu For Android (Not Ubuntu Installer)

The guys over at Ubuntu are developing something REALLY nice for the Android that are able to support both HDMI and USB, which I think the PLAY is capable of. This is some legit stuff guys! Time to revolutionize!
http://www.ubuntu.com/devices/android
It says that it's for multi-core phones, but maybe this could be ported to work on the PLAY in the long run? Discuss here!
EDIT: Something already popped into my head, since other Ubuntu distros can already be merged with the original Ubuntu itself, do you think removing the Android Ubuntu elements and adding them to a desktop Ubuntu system, then connecting the phone via USB with Debugging enabled would do the trick?

I'd love it if someone ported it to the Play, but I doubt it will happen... I guess they say it's for dual core phones for a reason (performance!)
Sent from my R800i using XDA

Selim873 said:
The guys over at Ubuntu are developing something REALLY nice for the Android that are able to support both HDMI and USB, which I think the PLAY is capable of. This is some legit stuff guys! Time to revolutionize!
http://www.ubuntu.com/devices/android
It says that it's for multi-core phones, but maybe this could be ported to work on the PLAY in the long run? Discuss here!
EDIT: Something already popped into my head, since other Ubuntu distros can already be merged with the original Ubuntu itself, do you think removing the Android Ubuntu elements and adding them to a desktop Ubuntu system, then connecting the phone via USB with Debugging enabled would do the trick?
Click to expand...
Click to collapse
From what info i have got about the system it really is much like my project but tailer made to the tes device (atrix 2) with extra goodness that a team working hard have come up with...and not just me lol.
But if they release source it should let us come up with a installer that does everything they show for a much larger range of devices...we are already working on some of the features just a big 'watch this space'
Sent from my GT-N7000 using xda premium

It's already possible to run a full linux distro under Android. Bit hacky though. It runs in the background and you have to VNC into it to use the GUI. Works pretty nicely however. There are a few apps which automate the process, including this free one which works pretty well now:
play.google.com/store/apps/details?id=com.galoula.LinuxInstall&feature=search_result#?t=W251bGwsMSwyLDEsImNvbS5nYWxvdWxhLkxpbnV4SW5zdGFsbCJd

Nextil said:
It's already possible to run a full linux distro under Android. Bit hacky though. It runs in the background and you have to VNC into it to use the GUI. Works pretty nicely however. There are a few apps which automate the process, including this free one which works pretty well now:
play.google.com/store/apps/details?id=com.galoula.LinuxInstall&feature=search_result#?t=W251bGwsMSwyLDEsImNvbS5nYWxvdWxhLkxpbnV4SW5zdGFsbCJd
Click to expand...
Click to collapse
He knows this hence the (Note Ubuntu Installer) referring to one of my apps

Still no news here looks like its not running inside android like a vmware. Needs a dual core so that each core runs a different os. Ubuntu is utilizing one of the cores so would be worth while overclocking where possible. The host core still runs android so that they run together on the oppisite clocks

AVD vs real device?

Hey guys, first of all, sorry if I post on the wrong section.
I have aquestion for devs. I'm a student developer and I'm learning to develop for Android. Do you guys think I'd necessarily need an Android device or the Android emulator would be enough(maybe for one year or more). I also like w10 mobile and I don't know what to do.
Thanks!!!!!!
Also another question, I'm a really beginner dev, but I'd like to get involved in community development, hacking etc, what do you guys recommend to me? Where should a beginner like me start from?

I am always running the apps on a real device if I can. This is definetly needed if the app uses for example something like networking because these functions will not be available on an emulator. The main reason however for using a real device is that it runs a lot smoother. The emulator can take a long time to boot up and it can be really laggy when running the app. Also when you are holding the phone on your hand you get to see how the app really looks and feels.
Emulator is ok though if there is nothing else available.

VilleI said:
I am always running the apps on a real device if I can. This is definetly needed if the app uses for example something like networking because these functions will not be available on an emulator. The main reason however for using a real device is that it runs a lot smoother. The emulator can take a long time to boot up and it can be really laggy when running the app. Also when you are holding the phone on your hand you get to see how the app really looks and feels.
Emulator is ok though if there is nothing else available.
Click to expand...
Click to collapse
Thanks for your reply. Well... the emulator is not really slow on latest versions of android studio... but it does start pretty slow. I'll finally use a real device.

On ADV, how can you test GPS, other sensors?

Do you guys think I'd necessarily need an Android device or the Android emulator would be enough(maybe for one year or more)
Click to expand...
Click to collapse
You can use Android Studio emulator and it will work in most cases. Couple recommendations:
1. Select Android version with Google APIs when creating device
2. Install Intel HAXM (you can find it in SDK manager also) - this will really speed up your emulator including loading time
3. Android Studio 2.0 will be released soon and looks like they will improve emulator performance and functionality there.
Of course you may face something wich is not currently works on emulator but you will face this on a real devices too - some features may work different on devices from different manufacturers. But the chance with facing this kind of troubles is very low when you work on common stuff. Also you can take a look to the 3rd party emulators, like Genymotion.
Anyway I prefer to use real device when developing because I can "feel" it
Where should a beginner like me start from?
Click to expand...
Click to collapse
Start with creating some app which will work with some Rest services, display some sort of lists, images, use database to store data. Just think about creating something useful and interesting for you.
---------- Post added at 04:54 PM ---------- Previous post was at 04:50 PM ----------
Cuong Phan said:
On ADV, how can you test GPS, other sensors?
Click to expand...
Click to collapse
You can test GPS using different apps which mocks your location (you can download apk from play store and install it on emulator) or using the terminal:
1. Connect to emulator with "telnet localhost 5554" command. Maybe you will need to change "5554" with another digits - just look at emulator's window title
2. Set location with "geo fix 12.345 67.89" command
What other sensors you need to test?

Used android emulators a lot, but mostly to test different unusual screen resolutions/dpi combinations.
They're ok speedwise, but you'll never get real feel of your app on AVD. And please, don't release anything, that just been tested only on AVD.
Also AVDs are quite good for recording videos of your app UI using screengrabbers on desktop (SSR - Simple Screen recorder is the best for me so far)
As for beginner's project - try to implement little game. I've started with simple rotating cube example from "Hello Android" book , and this little project ended with game with 3M downloads on play store

Android emulator will work when you begin a project.
If you need more tests or make a formal public apk, you can use real devices.

Best way is use both if you have device - use device. Another android versions, resolutions, sizes etc. test on the emulator.
If standard emulator is too slow, you can use genymotion.

Wine 3.0 on Android

It is here,
https://dl.winehq.org/wine-builds/android/
But ain't working on pixel. I am pissed off. Any workarounds?

It is not compatible with Oreo yet.
Just let them know on their forums:
https://forum.winehq.org/viewforum.php?f=2

NoobInToto said:
It is here,
https://dl.winehq.org/wine-builds/android/
But ain't working on pixel. I am pissed off. Any workarounds?
Click to expand...
Click to collapse
Look into Crossover. It uses WINE. http://www.androidpolice.com/2017/11/07/crossover-android-chrome-os-enters-open-beta/

skawtnyc said:
Look into Crossover. It uses WINE. http://www.androidpolice.com/2017/11/07/crossover-android-chrome-os-enters-open-beta/
Click to expand...
Click to collapse
Unfortunately, it is not for ARM devices...

I hope they'll update it so it's compatible with Android Oreo devices.

Looks like the new WIne 3.0 is ARM-compatible, and has been compiled for ARM devices:
https://dl.winehq.org/wine-builds/android/

I have Oreo on my Nexus 7 2013, wine works, tried to install some apps but no luck, only errors. Internet Explorer works, but i see only blank white web pages

numbazZ said:
I have Oreo on my Nexus 7 2013, wine works, tried to install some apps but no luck, only errors. Internet Explorer works, but i see only blank white web pages
Click to expand...
Click to collapse
what kind if binaries / apps were u trying to run?

nine7nine said:
what kind if binaries / apps were u trying to run?
Click to expand...
Click to collapse
Tried Live For Speed installer, also exe from unpacked game, and some photoshop cs6 repack) as i know LFS works good on wine.
Will try something else tomorrow

numbazZ said:
Tried Live For Speed installer, also exe from unpacked game, and some photoshop cs6 repack) will try something else tomorrow
Click to expand...
Click to collapse
how about trying actual arm binaries?
ie; windows rt, win8 arm && win10 arm PEs
last I heard, while the wine devs are working on x86 on arm, it wasn't ready - when compared to say; win10 for arm's x86 emulation layer...
I also know that in the past to run x86 binaries in wine on arm, you have to have binfmt_misc enabled in the kernel + qemu (emulator) to make it all work...
not sure, where things are at, at the moment. but I'd try running actual Arm compiled windows app and see if they run.... idk, I can't imagine that Wine is super useful on android yet. that said, I am curious - as I used to maintain buillds and patchsets for wine...

Only binaries compiled for ARM will function under Wine. You can find an updated list in the second post of this thread: https://forum.xda-developers.com/showthread.php?t=2092348

skawtnyc said:
Only binaries compiled for ARM will function under Wine. You can find an updated list in the second post of this thread: https://forum.xda-developers.com/showthread.php?t=2092348
Click to expand...
Click to collapse
it should be noted, this is specifically windows rt / win8 arm apps... and hasn't been updated in 3yrs.
I suspect that if u were to investigate the windows app store / UWP apps - there are probably a much higher number of windows apps that potentially could run in wine / for arm - but then you would likely require the Microsoft store or some other way to get the apps running in wine (not sure if wine even supports them).

skawtnyc said:
Looks like the new WIne 3.0 is ARM-compatible, and has been compiled for ARM devices:
https://dl.winehq.org/wine-builds/android/
Click to expand...
Click to collapse
It is not pixel compatible, and that is all this thread is about.

NoobInToto said:
It is not pixel compatible, and that is all this thread is about.
Click to expand...
Click to collapse
To be honest I only installed it on my Pixel C, not my Pixel phone. Doing so would have been pointless since the resolution makes it very difficult to use. Also there's no way to access the software keyboard, making it even more difficult to use.
Even if you could install it, and those other issues were resolved, it doesn't have a x86 emulation layer so you're pretty much stuck with those old Windows RT apps and not much else. You're looking at something that really doesnt have much more value than proof of concept. I'm probably going to end up migrating my tablet to something like the Pixelbook so I can run Crossover on it and have both android and x86 Windows apps run natively.

skawtnyc said:
To be honest I only installed it on my Pixel C, not my Pixel phone. Doing so would have been pointless since the resolution makes it very difficult to use. Also there's no way to access the software keyboard, making it even more difficult to use.
Even if you could install it, and those other issues were resolved, it doesn't have a x86 emulation layer so you're pretty much stuck with those old Windows RT apps and not much else. You're looking at something that really doesnt have much more value than proof of concept. I'm probably going to end up migrating my tablet to something like the Pixelbook so I can run Crossover on it and have both android and x86 Windows apps run natively.
Click to expand...
Click to collapse
Well, I would still like to try it out. If they manage to make it work with windows 10, say, windows 10S , it would be cool, since windows 10 is more touch friendly than 7 . It is in the works I believe, to be made possible via qemu (full arm compatibility). Time will tell.

NoobInToto said:
It is not pixel compatible, and that is all this thread is about.
Click to expand...
Click to collapse
NoobInToto said:
Well, I would still like to try it out. If they manage to make it work with windows 10, say, windows 10S , it would be cool, since windows 10 is more touch friendly than 7 . It is in the works I believe, to be made possible via qemu (full arm compatibility). Time will tell.
Click to expand...
Click to collapse
My biggest regret about this is that I don't have an emulator to run Diablo II on my tablet. Sure, there are other games, but they don't really capture the experience the same way.

skawtnyc said:
My biggest regret about this is that I don't have an emulator to run Diablo II on my tablet. Sure, there are other games, but they don't really capture the experience the same way.
Click to expand...
Click to collapse
I managed to make doom 3 to work on my phone ( I don't recollect which one, pixel or nexus 6p, I switched to pixel about 2 months ago). I am not sure about diablo.

NoobInToto said:
It is not pixel compatible, and that is all this thread is about.
Click to expand...
Click to collapse
beyond installing, it doesn't seem to work for me... also, i'm unclear on whether this build is arm64 compatible.? (I know wine has an arm64 preloader though).
skawtnyc said:
Even if you could install it, and those other issues were resolved, it doesn't have a x86 emulation layer so you're pretty much stuck with those old Windows RT apps and not much else. You're looking at something that really doesnt have much more value than proof of concept. I'm probably going to end up migrating my tablet to something like the Pixelbook so I can run Crossover on it and have both android and x86 Windows apps run natively.
Click to expand...
Click to collapse
I suspect that running qemu + wine-x86 would be the better route to go (vs wine-arm or running qemu + windows)... i'm not too sure what the overhead would look like, but people are doing it on the rasberry pi 2/3...
it's probably also possible that using some of wine's env variables would improve performance (realtime priviledges for wineserver, critical threads, etc) and patching wine to support other enhancements (which is what I would do anyway, on my linux box).
NoobInToto said:
Well, I would still like to try it out. If they manage to make it work with windows 10, say, windows 10S , it would be cool, since windows 10 is more touch friendly than 7 . It is in the works I believe, to be made possible via qemu (full arm compatibility). Time will tell.
Click to expand...
Click to collapse
i'd like to, as well...
technically, you can run qemu + x86 wine on arm, right now. I just don't believe that anyone has packaged it up nicely for android...
and it would require additional manual configuration, init script, possibly a script/wrapper for launching apps too, depending... Another issue would be the vast majority of stock kernels don't have the support or enable stuff that is going to be required... mine suports binfmt_misc (which qemu will require), but i think other stuff may be needed. not positive.
it can't be that hard though, but I don't have much experience with qemu (and none on android), wine on the other hand - lots of experience with on linux. same goes for winelib...

does anyone know how to get access to the internal storage?
I cant even try to install anything, because I dont know where the Wine-Files are located.
Btw I'm using a Lenovo YogaBook
Thanks

trfr3ak said:
does anyone know how to get access to the internal storage?
I cant even try to install anything, because I dont know where the Wine-Files are located.
Btw I'm using a Lenovo YogaBook
Thanks
Click to expand...
Click to collapse
you'll have to figure out how to get into your internal storage yourself, but having a a proper file manager helps. you may need root to view the files (I did on my pixel)... also, not sure why you are asking for help for your yogabook in the google pixel forum...? (you probably shouldn't be).
as for where the files are. it's android, so app data is usually stored in /data/data/your.app.name... and this would be where wine installs it's binaries and prefix too. (org.winehq.wine)
---------- Post added at 10:22 PM ---------- Previous post was at 10:18 PM ----------
so yeah. looking at the binaries. they are compiled as arm-v7a. ... they should run (although, by default after install, they aren't in the PATH / can't be executed from a terminal)....
I guess maybe the arm64 version just isn't ready at this point && wine-3.0 for arm requires some manual setup on the pixel... might tinker with it later, or look into qemu + wine x86... we'll see

.

It seems that contributing to LOS building ROM is not anymore tolerated, this post is deleted.

Maybe @Scavenger87 wants to take a look here ;-)
I guess it's better to have an own dedicated thread.

Thanks for setting up a distinct thread. Things were getting confusing!

john_matrix said:
Maybe @Scavenger87 wants to take a look here ;-)
I guess it's better to have an own dedicated thread.
Click to expand...
Click to collapse
Hey John great idea with opening a new Thread because i also think its really confusing already
john_matrix said:
@Scavenger87: Steel01 advised to let 15.1 (I think he is right because it's too old and because lot of changes have been done between 15.1-16.0)
Also have found this during LOS 16.0 debugging and when application is crashing:
Starting from Android 9, LMK can be implemented in userspace and needs new optimization settings:
Low Memory Killer Daemon | Android Open Source Project
source.android.com
Will see if this new userspace LMKD can be tuned.
@Trevor_g: can't say... I don't have an Nvidia controller to test.
Click to expand...
Click to collapse
Ok yeah i think he's right for multiple reasons
- 15.1 had still unsolved issues aside of broken omx like the crashing nv games app and not working screen mirroring which is working so far on 16.0
- 16.0 is Android 9.0 based which is the same as the actual Software for the Shield TV. That means there is maybe a chance they can use some Codes or even Apps like the Shield Accessories to makes things like the First Controller working again over WIFI.
I even found a lot Nvidia OEM Apps here on APK Mirror : https://www.apkmirror.com/apk/nvidia/
I think i start testing around with those apks as soon i installed the lasted 16.0 build
@Trevor_g
For your question i have to check that again on 16.0 with the old Controller but i think its still only working over a OTG Adapter.
Like i mentioned above maybe the Shield TV Accessories App is working.
mirhl said:
https://gist.github.com/webgeek1234/8ef1bd105d2add3aa9c29028c2befbb0
https://github.com/vartom/drivers-kernel-nvidia-49/tree/smaug49/drivers/hid
https://github.com/devmapal/nvidia-shield-controller-driver
Click to expand...
Click to collapse
Someone even mentioned this Linux Driver for the Controller
But to be honest dont suspect too much on lets say all this bonus functions because first the LOS Team have to work on the base build to make it stable and running right

Ok i installed the latest build (4/1/21) yesterday on my LTE Tablet over sideload because i had no extra SD Card to format it to FAT32 and with the new TWRP 3.5-9.0.
I installed also the Pico Gapps and then TWRP said when i was about to Restart that there's now OS installed.
But thats seems to be a bug with TWRP itself because after the restart there was the LineageOS screen waiting for me and after a freeze for about a minute or two i was able to complete my installation.
After this i now can say its the most stable LOS 9.0 Rom so far !
It has very less apps crashing so far i only had to start them twice sometimes and also the hw acceleration working now most of its time at Chrome and on the Youtube App.
I can really see there has going again a lot of work into this Rom and its really a pleasure now to see how it get more stable everytime.
Big thanks to @Steel01, @npjohnson, the whole LineageOS Team and of course to @john_matrix
Btw @john_matrix did you change anything on the partitions you mentioned earlier on this build ?
@Trevor_g
I did a short test yesterday with the controller and as suspected it doesnt recognize by the tablet. I soon test out those Android 9.0 based Accessories App from the Shield TV

Thank you for the rom
Can I just flash this over Lineage 14.1 or do I need a factory wipe?
Did anybody test gamepass streaming yet?

danielandross said:
Thank you for the rom
Can I just flash this over Lineage 14.1 or do I need a factory wipe?
Did anybody test gamepass streaming yet?
Click to expand...
Click to collapse
Yes you have to wipe the device first in TWRP to install this rom.
Maybe a little general guide for everyone here who want to try this build in this early state and help tracking bugs
For an clean Installation its important to wipe the device first with TWRP like shown on the first Screenshot.
After this go to Advanced and choose everything choosen on the second Screenshot.
Now you shutdown the Tablet and insert the SD Card or plug in the cable for sideloading.
After turning on the Tablet and choose Recovery Mode again, first install the Rom of course then choose Wipe cache/dalvik.
Now you have to install Gapps if you want to use it. Its recommend to use only the Pico Package.
Wipe cache/dalvik again and restart the device.
If you use Sideload it might says in the Shutdown Menu :
No OS installed !
Which is a bug in my opinion of the new TWRP 3.5-9.0 Package but please use this Version of TWRP in any case that the basement of the installation is everywhere the same !
This is IMHO the way to install a Rom in a clean way and helps tracking down bugs better when everyone used the same methodes.
@john_matrix
I installed the Rom today on a K1 16GB with the methode i described above and did it with my regular SDCard i use in all my Tablets. In comparsion to installing over sideload it didnt get the No OS installed! message at TWRP and i didnt had that 1 minute freeze at begin of the install-wizzard after the LOS Logo.
Also the Rom seems to be same stable as the one on the 32GB model.
But i have to test it a bit more side by side to make valid statements
Also Nvidia Games working nice as you can see on the Screenshots

Hi guys, so, long story short i got scammed on a dutch advertising portal and ended up with one of them shield tablets which were recalled a few years ago. Yep, those with the defective battery that may burst in flame one day
Anyways, i figured that since it hasnt happened until now, i might just be lucky and give it a shot.
Its great to see that there is still some active development of this device! flashed this rom and i gotta say im positively surprised. Its running nice and smooth and even though it crashed on me a few times after the first boot, but a few reboots later and its running like a charm! i didnt bother with gapps, root or anything yet though. really great job devs!

Scavenger87 said:
I installed the Rom today on a K1 16GB with the methode i described above and did it with my regular SDCard i use in all my Tablets. In comparsion to installing over sideload it didnt get the No OS installed! message at TWRP and i didnt had that 1 minute freeze at begin of the install-wizzard after the LOS Logo.
Also the Rom seems to be same stable as the one on the 32GB model.
Click to expand...
Click to collapse
My tablet was completely wiped with no OS so I just pushed the ROM, pico gapps, and magisk over USB onto internal storage with MTP/TWRP. Flashed it all from there and it worked fine. No issues or errors. I don't think it's at all necessary to sideload to use an external SD.

Jackill said:
Hi guys, so, long story short i got scammed on a dutch advertising portal and ended up with one of them shield tablets which were recalled a few years ago. Yep, those with the defective battery that may burst in flame one day
Anyways, i figured that since it hasnt happened until now, i might just be lucky and give it a shot.
Its great to see that there is still some active development of this device! flashed this rom and i gotta say im positively surprised. Its running nice and smooth and even though it crashed on me a few times after the first boot, but a few reboots later and its running like a charm! i didnt bother with gapps, root or anything yet though. really great job devs!
Click to expand...
Click to collapse
In this Thread beginning from here i share my informations so far about the two type of batteries and changing them out if you interested:
Finding Replacement Battery in 2017?
Anybody know where to find a battery that will fit in the Shield Tablet? I know there are several threads online (here on xda, on GeForce forums, and other places) that discuss replacing the shield tablet battery and a few different part numbers...
forum.xda-developers.com
airtower said:
My tablet was completely wiped with no OS so I just pushed the ROM, pico gapps, and magisk over USB onto internal storage with MTP/TWRP. Flashed it all from there and it worked fine. No issues or errors. I don't think it's at all necessary to sideload to use an external SD.
Click to expand...
Click to collapse
I did these two type installation because @john_matrix mentioned to use a SD Card which is formated with FAT32 instead of exFAT. I didnt had one lying around so i used sideload this time.

Thank you everyone and Scavenger87 for your feedback! ;-)
About stability, I guess the culprit is the fact I have played with the new userspace LMK but for me it's not stable enough to be used as daily.
For example, Youtube often continue to play videos greeny and blocky and this is annoying
I will try to fine tune the best settings for LMK.
About battery, I have changed mine too with this one:
https://fr.aliexpress.com/item/32807531204.html
It works good but require to use the board of the original battery.

Seems to be going well so far for me, battery life seems good and for the general use I have had time to do it's worked well.
One crash that caused a reboot, after testing the hdmi output the tablet rebooted when I unplugged the hdmi cable from the tablet.

john_matrix said:
Thank you everyone and Scavenger87 for your feedback! ;-)
About stability, I guess the culprit is the fact I have played with the new userspace LMK but for me it's not stable enough to be used as daily.
For example, Youtube often continue to play videos greeny and blocky and this is annoying
I will try to fine tune the best settings for LMK.
About battery, I have changed mine too with this one:
https://fr.aliexpress.com/item/32807531204.html
It works good but require to use the board of the original battery.
Click to expand...
Click to collapse
Ok that means there is still some kind of memory leak problem with our tablets or is the memory managment on android 9 and higher not really suited for our low ram devices ?
I also read something about drawbacks with the in-kernel LMK as you can see here :
Drawbacks of in-kernel LMK driver
Android deprecates the LMK driver due to a number of issues, including:
Low-RAM devices had to be tuned aggressively, and even then would perform poorly on workloads with large file-backed active pagecache. The poor performance resulted in thrashing and no kills.
The LMK kernel driver relied on free-memory limits, with no scaling based on the memory pressure.
Because of the rigidity of the design, partners often customized the driver so that it would work on their devices.
The LMK driver hooked into the slab shrinker API, which wasn't designed for heavy operations such as searching for targets and killing them, which slowed down the vmscan process.
Is the zRam function now activated by standart on Android 9 and higher to compress amount memory is needed ?
I try to stresstest it today with a website that have a lot pictures sadly i cant use instagram anymore because you need a account now

Shield Tablet can't be considered as a "low ram device" as Google defined them with up to 512MB (Android Go?)
Android Performance Optimization | Android Open Source Project
source.android.com
I also have devices with 2GB that are currently performing Lineage 17.1 very well (Sony Z3C and Nexus 4)
I don't know if zRAM is activated by default in Android but you still have the choice to activate it or no (in the kernel or in the fstab.
Additionnally, I don't know what is the policy to activate zRAM (my Mi9 have 6GB RAM and have zRAM activated by Xiaomi so...)
Another thing about zRAM is there are lot and lot of options you can activate such as compression, lz4, clear caching, etc... depending of your needs and I am not skilled enough to say exactly what will be the consequences of these options (but it cost nothing to try).
You also have to keep in mind that zRAM will consume more CPU times (as KSM).
Similarly, you can fine tune the CPU governor and IO scheduling (often I see CFQ by default but on the other way I have saw that Noop and Deadline gives best results).
Feel free to share your experience and if you have other ideas on what you would like to integrate in this ROM (as the best possible).
You are right to stress test the OS, you can also debug the memory and the weight attributed on the processes.

Ok but 2GB is really not much these day also this article from android source is really old i think i read there something about kitkat or so
But your right i also was suprised to see that my xperia z3 compact i have lying around is able to run lineageos 17.1 and even is supported by the LOS Team
Which leads me to the question is the memory managment on the Qualcomm SOC so much better ? Ok the Ram there is on the SOC itself instead of external like on our Tegra based devices.
I think i install tonight Triodexes 15.1 with zram to compare the effect it has.
I also noticed the hw acceleration crashes the most on the firefox browser like i told in the 15.1 Thread you can start one video and it runs if you leave everything untouched but your not able to start a second one even with autoplay.
Btw about the LMK i know its maybe a dumb question but did you try the original settings from the Oem Rom ?
Edit : The original values in minfree are: 18432,23040,27648,32256,36864,46080
And zRam is already activated on the LOS 16.0 Build with 511MB same like the oem rom

Scavenger87 said:
I did a short test yesterday with the controller and as suspected it doesnt recognize by the tablet. I soon test out those Android 9.0 based Accessories App from the Shield TV
Click to expand...
Click to collapse
Thanks SO much for looking into this for me! You mentioned later that the controller wasn't recognized by the tablet, however I'm also curious if the Accessories app from the ShieldTV might help. Thanks again, in advance!

Fwiw, there's a bunch of framework patches needed for the wifi direct controller to work. I've yet to get them all straight. Haven't had that working since cm-12.1. See the incomplete set for 16.0 here:
https://review.lineageos.org/q/topic:shield-blake-p
That's on top of:
https://review.lineageos.org/q/topic:nvidia-shieldtech-p
And there's no nvidia pairing app that works with a touch interface. It's a mess atm. I did get blake to pair to foster on 15.1, but only while the pairing wizard was open. As soon as I hit back to close it, the autonomous group goes down and the connection is lost. And now, it's close to impossible since nvidia didn't release the nvwifi prebuilt jar to link against. And the one from O doesn't work on P.

Hi @Steel01
Thank you for keeping us updated on your work with the controller and also for your work for this device in general
I already tought its not easy to bring wifi support back for the old controller but i think also there is no high priority since the second gen is working fine over bluetooth and they already cheap to buy used.
Other than this the rom is suprisingly good running for this early stage and most of the stuff is working
Is there something that needs special attention for testing at the moment to help you developing ?
Like i mentioned in a other Thread i have every generation of the Shield Tablet and Controller. Only on my LTE Modell the SIM Card Reader is unfixable broken
But i still hunting for a fully working device.

Before I flash this Rom: Why do I habe to wipe internal storage?

danielandross said:
Before I flash this Rom: Why do I habe to wipe internal storage?
Click to expand...
Click to collapse
Well i dont know if its really needed to wipe the internal storage but i think by the reason we testing here a new Rom in a really early stage we should give it the cleanest basement as possible to exclude problems that might caused by left over data that interference with the Rom