Database Info

Help! Cm6 rom is so close to perfection :'(

Once again I am here seeking the help from developers for my phone. Which is not the XT720 (XT701 instead), but I really don't know where else to turn.
I was restless again, so then I went and started looking for roms. I found this one:
Speed XT701 2.2.1版 beta7 搞掂wifi
This is really new and is running CM6 based moto blur extremely smoothly. Search on google and click the first few links to see the interface. Amazing as always, the CM roms. The touch sensitivity is ON PAR with the Iphone 4. I was so glad that everything was working - Camera, SDcard, SERVICE, SMS, CALLING, all working so perfectly. It was completely different from the CM 7 mod.
And honestly, It really seems even faster than the CM7 rom. I read from the translated description that it is using "smart200mhz to 600 mhz" processing for superb battery and so on. It really does have a lot of attractive features and usual and completely destroys the 2.1 rom.
Now comes the horrible, devastating part. No wifi. .
I did the 3 wipes, updated, and 3 wipes again, and it still had no wifi.
Right now I'm really leaning towards sticking to this rom. My solution is to keep my backup of the 2.1 stock, and nandroid over to it when I need to so that I can download new apps, back then up in SD, and then nandroid back.
Can anyone please help me figure out how to get wifi? I'll donate from paypal if someone can help me resolve this wifi issue. . Just terrible, this problem. So close.

firzen_net said:
Once again I am here seeking the help from developers for my phone. Which is not the XT720 (XT701 instead), but I really don't know where else to turn.
I was restless again, so then I went and started looking for roms. I found this one:
Speed XT701 2.2.1版 beta7 搞掂wifi
This is really new and is running CM6 based moto blur extremely smoothly. Search on google and click the first few links to see the interface. Amazing as always, the CM roms. The touch sensitivity is ON PAR with the Iphone 4. I was so glad that everything was working - Camera, SDcard, SERVICE, SMS, CALLING, all working so perfectly. It was completely different from the CM 7 mod.
And honestly, It really seems even faster than the CM7 rom. I read from the translated description that it is using "smart200mhz to 600 mhz" processing for superb battery and so on. It really does have a lot of attractive features and usual and completely destroys the 2.1 rom.
Now comes the horrible, devastating part. No wifi. .
I did the 3 wipes, updated, and 3 wipes again, and it still had no wifi.
Right now I'm really leaning towards sticking to this rom. My solution is to keep my backup of the 2.1 stock, and nandroid over to it when I need to so that I can download new apps, back then up in SD, and then nandroid back.
Can anyone please help me figure out how to get wifi? I'll donate from paypal if someone can help me resolve this wifi issue. . Just terrible, this problem. So close.
Click to expand...
Click to collapse
I'm sure our dev's would love to help as it might help with our phone as well. First can you post a link to this amazing ROM please? Thank you!

Look forward to seeing this, but...
firzen_net said:
The touch sensitivity is ON PAR with the Iphone 4.
Click to expand...
Click to collapse
...what's that supposed to mean? I've never had a problem EVER with the phone registering my touches and my touches can be me barely touching the screen (i.e. I can't imagine how anything can actually be better than that).

Maybe he meant responsiveness of the UI? Just a guess. And yes I agree the touches on the phone is already very good in your sense.
syrenz said:
Look forward to seeing this, but...
...what's that supposed to mean? I've never had a problem EVER with the phone registering my touches and my touches can be me barely touching the screen (i.e. I can't imagine how anything can actually be better than that).
Click to expand...
Click to collapse
Sent from my Milestone XT720 using XDA App

For the touch sensitivity thing, I'm pretty sure its because I'm running 2.1, which is why the IPhone seemed faster with tracking my finger movement when I compared them side by side. The XT701 itself is already blazing fast, because I'ved used overclocking, setcpu, and memory manager, but then when I upgraded to this rom called the "speed beta 7" it was just overwhelming. I've never seen the phone so reactive.
The rom is a CM 6.1.2, android 2.2, so it would explain everything so much faster. I always thought I couldn't get the phone to be any faster, but this rom proved me wrong again.
Here is the link to the rom. I'm also going to be copying and pasting the post that the developers have along with the rom. It's going to be translated from Chinese into English, so it'll be rough. But you'll get the jist of what its saying.
http://u.115.com/file/dn6dnp8n
I nandroided back to my stock rom again =/. Apparently this Rom has close to daily updates so I'll wait a while. They started releasing it on the 7/18 and they're already on beta7.

Statement: As a consulting 2.2 version of the oil, therefore continue to provide useful new 2.2 ROM.
This ROM is not my production is transferred from the other forums, but I have used ever measured, easy to use just made up, hope you like
Version of the return to original author, has nothing to do with me ~
Mod Description:
This Mod is based on CM6.1.2 production, with Moto-style 2.2.1 version of the official 2.1 ROM, with a great memory, experience, ensuring smoothness and stability, and has a very strong memory recall mechanism.
And with improved functionality and greater ease of use, without adding redundant features.
This ROM native support APP2SD, support both computer and cell phone card reader (connected to a computer can not afford to card), NICAM excellent results.
CPU clocked Smart250Mhz to 600Mhz, power efficient correct, let your XT701 has a stronger fighting at the same time have sustained life.
ROM renamed Speed ​​XT701, translated as "rapid XT701", reflects the ROM features.
This Mod is currently only for a kernel customization, the future will be to consider other kernels, so there will be more than one branch.
Please note: Some functions can not achieve because the kernel is the reason, in the absence of perfect Neihe 前, Mod can not solve the problem.
701 began to decay ...
Speed ​​XT701 Beta7 stage is a more stable version, while faster than Beta1 has been greatly improved, A-GPS issues still need to look at, here adopted a compromise;
FM repair just around the corner, recommended update to this version.
Interface is slightly flawed, the next version of the repair.
2011.7.27 3:00 Updated Beta7
- New Atrix 4G interface; (blur Starter: Launcher.apk (2.39 MB) option, choose blur interface)
- Fixed dynamic Wi-Fi connection (thanks to S);
- Fixed Google Search FC;
- Streamlining the volume size;
- Increase stability;
- Add more beautiful Google Video;
- Support for 4-point touch; (thanks S)
- OC 800Mhz, standby frequency reduced to 125Mhz, more power, smoother!
- Strengthening the capacity of the hard decoding;
2011.7.26 update Beta6 Remastered 0:00
- Fixed browser FC;
- Update to the latest 3.0.27 version of the electronic marketplace;
- Update patch version of the power and temperature;
- Increase stability;
2011.7.25 0:30 Updated Beta6
- Solve the vibration problem to unlock;
- Because the library file repair Dlna caused errors;
- New dial-up interface and contact interface;
2011.7.24 10:30 update Beta5 Remastered (this can be ignored without the requirements of a friend)
- Replace defy the keyboard file, keyboard, power button and all other issues hang perfect solution
2011.7.23 10:30 update Beta5
- Replace the latest 113 version of the font, smaller, better display;
- Repair Beta4 problems (set English Bug, Android keyboard error, etc.);
- Extracted from the MOTO 4G distinctive ring;
- Add to unlock the other core vibration setting; (thanks to friends chj334499) (stability unknown)
- Replace the display of attribution in text; (thanks to friends fdwxd) (stability unknown)
- Replace the Chinese version of "MOTO mobile portal"
2011.7.22 10:30 update Beta4
- Optimize the network settings, better support for WCDMA networks, and enhance the connection speed and quality;
- The new configuration of GPS and speed;
- Force on A-GPS, to enhance positioning speed;
- Draw all the android machine configuration, integration into a machine with the XT701, collect all the network location server as a backup link;
- Configuration files using the latest CM6 0.11;
- Add cold patch, effectively reduce the temperature more than 20%; (please use this method with h ttp: / / bbs.gfan.com/android-2089915-1-1.html)
- Integrated Performance patch tested to enhance CPU performance to run sub-10%;
- Integrated the latest version of the DSI from CM6 0.11 patch, XT701 continue to increase endurance;
- Reduce the Wi-Fi scanning frequency, Wi-Fi throughout the day as more power;
- Replace CM6 0.11 the latest version of Wi-Fi and configuration files. (Not sure whether to fix dynamic)
- Completely remove the overclocking module, to save space;
- The kernel is locked, overclocking is invalid, it is deleted;
- Optimized version of the baseband added, the latest version from CM6 0.11;
- Add audio library, you can use third-party audio controller;
- Updated built-APP version;
- Add high-quality broadband talk configuration;
2011.7.21 10:30 Beta3 enhanced version update
- Added DLNA support;
- You can transfer data via WIFI and other equipment, or set up local area network to share streaming media, specifically refer to Baidu Baike.
- Repair software to download third-party market issues;
2011.7.20 10:30 update Beta3
- Re-optimize the configuration file of GPS and A-GPS files;
- In theory than in previous versions of the GPS version is better, basically reached the limit of Mod;
- Optimization of the hosts file, which greatly improve the google server connection speed; [thanks] to provide users 1179873587
- Improve the synchronization speed;
- Gmail and other google software to reduce latency;
- Replacement splash screen, more appropriate theme Moto, faster boot speed;
2011.7.19 10:30 Update Beta2
- Fixed error Android keyboard procedures;
- Streamlined some services for the Youtube upload and delete services;
- Add V @ P @ N service support;
- Streamlining the integration software, the production will follow after the official 2.1 version to make;
- Replaced with lower-resolution boot screen, improved boot speed;
- Replace the official 2.1 comes with wallpaper;
- Integrated the latest version of Moto input (from Motorola Atrix 4G);
- Change Root manager for the latest version, fix "is loaded as read-only" misplaced;
- Fixed several existing bug.
2011.7.18 18:30 update Beta1 Remastered
- Fixed multi-satellite GPS can locate the problem found;
Beta 1 update 2011.7.18 10:30
- Replace the landmark core library files, optimize media effectiveness.
- Replace the new version of CM software, a large amount of updated content, localization is not completely finished parts.
- Can be set not by third-party software to set maximum memory occupied by each program;
- Can change the screen mode and unlock the lock;
- By avoiding kernel crash DSI greatly reduces the chance of error;
- Has a more detailed set;
- Joined the GPS optimization patch, the original speed faster;
- Use of State Bank 2.1GPS configuration file, add add GPS module and the search speed so write the boot loader module list;
- Replace USB.apk the milestone comes the official Chinese version 2.2;
- Update to the latest versions of many programs;
- Add a contact interface numbers and call records to show ownership of the interface number to show ownership;
- Add to Google services pack version of the latest available version, download error correction;
- The electronic market is unable to update, talk can not update the map to the latest 5.7 version of China to speed up
- Increase Plus kit;
- You can replace the five versions of this toolbox baseband;
- Available through the Toolbox to streamline internal procedures;
- Can remove the camera sound camera;
- Can remove built-in multiple records;
- Easy to change the font;
- Minimum brightness breakthrough limit;
- Screening software function within the advertising;
...
- Streamlining the number of useless software;
- Replace the ADW as ADW.EX faster;
- Excluding services provided by voice prompts, and many other services;
- Use the native theme files, and add the mot-framework-res.apk (birth certificate);
- After extreme pressure test, the native theme with more stable characteristics, it is recommended that a friend like landscaping to restore native interface;
- With the birth certificate, you can install the software, the biological (moto software installation available)
Next Blur Beta 5 ready to try the latest version of its portable interface, please look forward to it!
Students do not envy MIUI, MIUI is based on the CM 0.1 development, and the current version has a lot of difference, and code optimization is not high.
Goal: present the mod of the already chaotic, mod rarely have their own style, hope this mod will enable students to experience the same as 2.2.1 to 2.1, and so restore the Moto mod style.
Known issues:
1. WIFI not dynamic;
(2) some special encoding video black;
3. FM is still not available;
4. Can not call recording;
(this part was in white text. I don't know if it means that its fixed or not. Because it does say that in the latest Beta7 wifi was fixed thanks to S or something)
(Note: points represent the normal running speed, running sub is the ultimate performance of a test, therefore, the common run from high up poor, but the machine is running;
For example: run the software needed to run sub-use lots of memory, ROM memory recovery efficiency is poor, will result in greatly reduced running speed after hours, but had no effect on the running sub-
So the actual speed will depend on the. )
Recommendation: To maintain the stability and speed, it is recommended to remove the JIT, of course, affect the reserves is small.
Recommended with the software: automated process killer from Kai Butler
Recommended with the script:
Swap 256M memory or more
beta 7 Download: http://u.115.com/file/dn6dnp8n
Please place this file to the root directory of cell phone coverage with the same name file (remove. Apk): init.choles.rc.apk (11.92 KB)
Downloads: 146
Yesterday, 03:47
Download the consumption of G coins 1
Brush Method: Download this package on the SD card OpenRecovery / Updates folder, the brush before you wipe 3 items.
Everything it says is true. It is fast as hell, no lag. The ONLY thing which is stopping me is the wifi, which bugs me even more, because it says here that Beta7 FIXED WIFI. I don't know why my wifi doesn't work!

interesting. I wonder what will happen if we apply this update to the running cm6 on xt720

Becarefull this could have a custom kernal that could bootloop or worst.
Sent from my Milestone using XDA Premium App

Really? I've been using this so far it's great. I've never seen my phone be so responsive ever. But there is still no Wifi. Everytime I try to connect it says, Connecting, and then Disconnected. Because of that I haven't even logged in with my account. No wifi causes the phone to run even smoother, cause a lot of background apps aren't runnning

mchlbenner said:
Becarefull this could have a custom kernal that could bootloop or worst.
Sent from my Milestone using XDA Premium App
Click to expand...
Click to collapse
firzen_net said:
Really? I've been using this so far it's great. I've never seen my phone be so responsive ever. But there is still no Wifi. Everytime I try to connect it says, Connecting, and then Disconnected. Because of that I haven't even logged in with my account. No wifi causes the phone to run even smoother, cause a lot of background apps aren't runnning
Click to expand...
Click to collapse
I think he's telling xt720 users to be careful.

Yes are kernal cant be messed
Thanks to moto locked bootloader.
Not for use it you have milestone xt720.
Sent from my Milestone using XDA Premium App

firzen_net said:
Can anyone please help me figure out how to get wifi? I'll donate from paypal if someone can help me resolve this wifi issue. . Just terrible, this problem. So close.
Click to expand...
Click to collapse
I just had a similar problem on the XT720 CM6. It turned out that wifi actually was working, but DNS lookup was not (I could use static IP in browser). I fixed it by replacing /system/xbin/busybox with a known-good version. You can test busyboxes with something like copying it to /tmp/busybox and then running (either via adb or terminal emulator):
/tmp/busybox nslookup android.com

Could you be a bit more specific Mioze7Ae. I have the busybox app; I don't think I have the terminal emulator. But I still don't understand what you mean.
I have Busybox app installed, and it says the "Status: Done!" after installing 1.18.4 :S.
As for the terminal emulator, I've heard of it but I don't have the app. So I install the app and then type that in the emulator?
EDIT: I just downloaded some Pro term emulator app. I turned on wifi, and then I typed in that code (cept I put xbin since I only installed it there) and it said:
Server: 8.8.8.8
Address 1: 8.8.8.8
nslookup: can't resolve 'android.com'
What does this mean? cause It just seems to me that my Wifi is still not working. Also, I've been seeing DNS around but I have no idea where to find it in my phone. Or DPN, something liek that but all I have in the Network settings is VPN and proxy, which is at default.
On a side note, could anyone help me find a working zip folder of Google apps for XT701/XT720/CM6? In the past I've installed them manually on android, and I've tried to use OR to flash the apps into my phone as well.

Look in the cm7 for the Motoroi thread & around post 50 there is a link to the cm website Google apps updates

With wifi connected try using the browser to go to a website via ip address instead of name. For example http://50.23.231.74/ worked, even though http://xda-developers.com/ did not. If ip addresses don't work then probably you have a different problem.

My problem right now is that I cannot even connect to the router at home (or anywhere else). It just keeps saying scanning connecting, and then looping back to scanning.
Sad thing is, just today I flashed another CM6 rom by the name of update-cm-6.1.2-XT701-Milestone-signed-by-s.zip today, and wifi worked. But then, a ton of other things stopped working so I nandroided back.
It just doesn't make sense that Wifi wouldn't work for some and not for others. I am still way too unexperienced for android.
I found it from this website, http://xt701.ghostry.cn which is sort of a jackpot for me. It has the latest releases of ROMS from China/world all uploaded onto that site. I don't know if it will be much help for XT720 developers, but that site is extremely updated.
Another slight problem which I am also overlooking for the sake of Speed is the LED being unusable. I always relied on it when my phone was on silent for texts, but now It is just gone. Any ideas how to get it back=/? Thanks for your input anyways!

So wifi is still not working. I've been reading around that it has to do with the Radio img??!? I don't get it.
I do know that this ROM doesn't have a FM radio yet, but I don't know if it has to do with my wifi.
I also tried replacing my tiwlan_drv.ko with other versions of it, but it ended up in an Error. Is it possible for me to flash a CM6 rom with a working wifi, copy the tiwlan_drv.ko file from there, and then use it on this current ROM that is not working? Like using root explorer to replace the .ko with the other roms one?
Sigh..

is this thread closed? nobody from august? i donwloaded some roms from http ://xt701.ghostry . cn and now i will install to my XT701 and see if any it's working so I can have android 2.2!!!

As long as you have xt701 your good to go.
Sent from my XT720 using XDA Premium App

i have now on my XT701 MIUI 1.12.30 Android 2.3.7 but i have some problems with network signal and when I try to call anybody the phone restarts! last night when I flased this ROM the calling was good. Strange!?!?

[APK] Seeder 2.0.0 entropy generator to provide significant lag reduction

Hey everyone,
Version 2.0.0 released!
This version introduces performance tuning, power management control, and an optional MMC I/O queue extension/timing change.
For those of you who have seen reboots / black screens that seem to be caused by Seeder, I suspect it may be due to the power management implemented in previous versions. Disabling power management (by unchecking "Suspend RNG service while screen off") may help. In my testing, battery impact was negligible (less than 2% per 24h).
The performance profiles are Light, Moderate, and Aggressive, and they control how frequently rngd wakes. The default configuration (Light) is unchanged from previous versions. Moderate and Aggressive may impact battery life (slightly), but may also help on devices where the entropy pool is drained quickly and often.
Last but not least, the "Extend I/O queue" option increases the nr_requests on MMC devices to 1024, and increases the dirty page expiry time, allowing more outstanding writes to accumulate. This may allow the I/O scheduler to make better decisions and combine more writes; some users have reported an improvement under heavy I/O.
Feedback appreciated!
---
On some (older) versions of Android, the JVM (and other components) often read random data from the blocking /dev/random device. On newer builds, this problem has been solved, yet depletion of the input entropy pool still seems to slow devices.
So, I cross-compiled rngd, and used it to feed /dev/urandom into /dev/random at 1 second intervals.
Result? Significant lag reduction (for some people)! :good:
Note - if you want to try it, you must be running a rooted device, and you only need to install one of the APKs (latest version is best). Then, just open it, and turn it on. The other files (patches / .zips) are intended for recompiling, packaging, and init.d integration. If you uninstall the app, either turn off rngd first (open, and click the on/off button), or reboot afterwards; the UI does not presently kill the daemon on uninstallation.
For more information on using the .zip flashing method, see Ryuinferno's post here:
http://forum.xda-developers.com/showpost.php?p=36479461&postcount=1924
FAQ
Q: Do I need the .apk or the .zip?
A: The easiest method is simply installing the latest .apk, attached below. You do not need to use the patch or the .zip file.
Q: What is the patch for?
A: The patch file contains the source differences needed to recompile the Seeder version of the rngd binary. You only need it if you want to recompile rngd yourself.
Q: What is the .zip file for?
A: The .zip file contains the latest rngd binary. It is intended for ROM builders or those who want to build their own CWMR packages.
Q: Seeder keeps shutting down! Does this mean I have to restart it?
A: The Seeder UI is only used to configure and start/stop the RNG service, which runs in the background. The RNG service is not visible from Android, since it is a native Linux process. You can terminate the UI at any time, and the service will continue running.
Q: Does seeder cause excessive battery drain?
A: Seeder 1.2.7 introduced an RNG service power-saving mode. The process automatically suspends whenever the screen is off. The code is actually in the rngd native binary, so suspend/resume events happen independently of the UI; you can see it in action by attaching to the running process with strace. This means that battery drain while the screen is off is highly unlikely.
While the screen is on, the RNG service simply polls a file descriptor every second, and, when needed, injects a small amount of random data into /dev/random (and calls an ioctl). It's unlikely that this would present enough load to trigger a CPU governor state change at 10mhz (let alone 200mhz), so it shouldn't impact battery life. Having said that, I have received sporadic reports that it does reduce battery life on some devices. They may be coincidental (other software installed at the same time), or due to extra device use while testing. Or, they may be real. If you think your battery drain has increased, shoot me a PM!
Q: How can I see the RNG service Linux process?
A: In a terminal, type: ps | grep rngd
Q: How do I uninstall the .apk?
A: Launch Seeder, and stop the RNG service. Then, uninstall the app as you normally would. Alternatively, uninstall the app, and reboot.
Q: Is seeding /dev/random with /dev/urandom safe?
A: Seeding /dev/random with PRNG-derived data does reduce the quality of its random data. However, it's worth noting that nearly all major OSes except Linux do this. Linux is one of the very few to offer a blocking RNG device. And, at least as of ICS, Dalvik doesn't even read /dev/random, so there is little difference anyway.
Updates
There has been a lot of controversy about Seeder/rngd. In newer versions of Dalvik, nothing touches /dev/random, and yet many users (including myself) still notice a lag reduction. There are theories ranging from kernel lock contention to UI polling load when crediting the entropy pool to simply kicking the governor. And many who believe it's all placebo. I'm trying my best to figure out what exactly is happening, and others are as well.
Someone asked how I arrived at the conclusion I did when I started the thread back in November, and I posted this; I think it might be better served here:
A while back one of the webapps I was hosting on Tomcat (server-side) was experiencing some inexplicable latency and while stracing java I saw it frequently hanging on read()'s from /dev/random. I checked the available entropy, and it was constantly under 250 or so. It was a VM, no HWRNG, so I decided to use rngd to push urandom->random.
Dropped session creation times under load from 5-10 seconds to less than a second.
It's worth noting that Linux is one of very few OSes that have a blocking RNG device. Free/OpenBSD, Windows, etc.. essentially only provide urandom. It's generally considered secure, even for long-term crypto keys, so long as the initial seed is big (and random) enough.
Checked on my device, and saw a few processes grabbing /dev/random. /proc/sys/kernel/random/entropy_avail reporting depleted input pool. Figured it was worth a shot, so I rebuilt rngd for arm (with a few patches, linked on first page), and tried it out. It made a significant difference. Posted it up on this thread, and had a lot of positive feedback. Wanted to get into Android development, so figured.. why not wrap a little UI around it. More positive feedback, so I threw it on the market as well.
I had no idea it would take off like this and was shocked when I saw it Thursday morning. I'm in the awkward position now of explaining why it seems to work for some people, and not for others, especially given the fact Dalvik doesn't have references to /dev/random as of ICS. Theories abound, but it looks like it might be an issue of polling the UI for input events when the entropy pool drops (which never happens so long as rngd is running).
I'm doing this as a hobby. I'm a *nix admin by trade, and can only spend time working on this stuff on evenings and weekends, and the last few weeks have been kinda nuts.
I want to stress to everyone that:
a) It doesn't work the way I thought it did on later Android builds, but it does reduce latency for me and many others even on these builds,
b) I'm offering (and always will offer) Seeder for free to everyone on XDA,
c) Like I say in the market description, if anyone has purchased it and it isn't working, PLEASE email me for a refund (and let me know what device you're on if you're willing).
I was one of the first to root the Captivate glide (my first Android phone), and submitted the A2DP bitpool patch; I was active in the n900 community. I hope everyone understands that I'm doing my best here!
I hope the technique proves useful to people, and if there is in fact contention at the kernel level, I hope it's solved so we all benefit.
Version 2.0.0 attached. No changes.
Version 2.0.0b1 attached. New performance profile selector, I/O queue extender, and power saving control. Improved root checking.
Version 1.4.0 attached. Major refactoring. Service control now fully asynchronous.
Version 1.3.1 attached. No changes from 1.3.1-beta.
Version 1.3.1-beta released. New root check method during ANR-sensitive code.
Version 1.3.0 attached. Proper IntentServices for process control, and notification on upgrade / loss of root / autostart failure.
Version 1.2.9 attached. Yet another update to the upgrade/autostart code.
Version 1.2.8 attached. Asynchronous startup of rngd during boot; this should solve the remaining autostart problems some users have reported.
Version 1.2.7 released. This version introduces a much more efficient suspend-on-sleep mode for rngd.
Version 1.2.6 released. This version reverts the suspend-on-sleep rngd change which may have been contributing to new latency. I'm sorting out a better way of implementing it.
Version 1.2.5 released. This version should fix the autostart failure some users have seen.
Version 1.2.4 released. This version implements a progress bar displaying your currently available entropy, as well as automatic rngd restart on upgrade.
Version 1.2 released. This version implements rngd suspend-on-sleep, and contains minor user interface updates, more robust process and superuser checks, and a new icon (thanks Nathanel!)
Version 1.1 released. This version uses the release signature, so you will need to uninstall the old XDA version first!
This version fixes the issue some users were seeing on later Jellybean ROMs, where the UI would misreport the RNG service status.
Caveats
There is a (theoretical) security risk, in that seeding /dev/random with /dev/urandom decreases the quality of the random data. In practice, the odds of this being cryptographically exploited are far lower than the odds of someone attacking the OS itself (a much simpler challenge). It's worth noting that as of ICS, Dalvik uses /dev/urandom exclusively, anyway, and that Linux is one of very few modern operating systems that even offer a blocking RNG device to begin with.
Support for rngd suspend-on-sleep was added to Seeder 1.2. It should no longer impact battery life while the device is asleep.
There has been a large amount of speculation on why/if this actually improves performance on ICS+ devices. I'm continuing to investigate and will post updates to this thread.
If you try it, let me know how it goes.
ROM builders - feel free to integrate this into your ROMs (either the .apk / application, or just the rngd binary called from init.d)!
If anyone's interested, I've launched a paid app on the Play store for non-xda users. As I add features I'll post the new versions here as a thanks to you guys (and xda community at large for being such a great resource). But if anyone's interested in the market's auto-update feature, just thought I'd mention it.
Cheers! :highfive:

This seems absolutely amazing!I think I'll try it out on the weekend, cheers!

Will this work for cwmr 6
Sent from my SGH-I927 using xda app-developers app

Hi,
I would try this, cause I experienced these lags, and they're really annoying, but I'd really need a simple instruction for what to do. You wrote how you managed to discover what to do and stuff, but I'm lost between the lines. Since I'm kind of a newbie, I'm kindly asking you to write some kind of instruction manual step by step, and forgive my ignorance

Laugher19 said:
Will this work for cwmr 6
Click to expand...
Click to collapse
Not yet. If a few people try it and report positive results, I'll make a flashable image. Stay tuned.
soadzoor said:
Hi,
I would try this, cause I experienced these lags, and they're really annoying, but I'd really need a simple instruction for what to do. You wrote how you managed to discover what to do and stuff, but I'm lost between the lines. Since I'm kind of a newbie, I'm kindly asking you to write some kind of instruction manual step by step, and forgive my ignorance
Click to expand...
Click to collapse
I updated the first post with instructions. Please be careful, though! Let me know if you need more detail.

lambgx02 said:
I updated the first post with instructions. Please be careful, though! Let me know if you need more detail.
Click to expand...
Click to collapse
I got troubles. Using Terminal Emulator I got an error message when I type the 3rd line ("cp /mnt/sdcard/rngd /system/xbin"), it says: "sh: cp: not found"

soadzoor said:
I got troubles. Using Terminal Emulator I got an error message when I type the 3rd line ("cp /mnt/sdcard/rngd /system/xbin"), it says: "sh: cp: not found"
Click to expand...
Click to collapse
Where did you transfer rngd to on your phone? Have to make sure the source path matches.

lambgx02 said:
Where did you transfer rngd to on your phone? Have to make sure the source path matches.
Click to expand...
Click to collapse
It does match, that's why I'm confused.. :\ which terminal do you use?

Will test this later, for sure! If all goes well, may I request permissions to include this with the MIUI build I will be learning to make and attempting to produce?
edit: My phone wasnt particularly laggy before except when playing games, but there is a noticeable difference after executing this binary. Noticed a few small hangs but unsure if it is related to this binary.

I've tested it ... integrated it into my rom and installed ... there was no lag even right after it first boot ... its incredibly smooth ... though I too noticed small hangs ... though I attributed this to the device getting ahead of itself ....
Sent from my SGH-I927 using xda premium

Yeah it kind of seems like its fine after settling a bit. Can't wait to see it in 0.7 thegreatergood.
Sent from my SGH-I927 using xda premium

Ok, everyone. I built a very simple Android app that bundles the rngd binary and starts/stops it. Details in first post.

lambgx02 said:
Ok, everyone. I built a very simple Android app that bundles the rngd binary and starts/stops it. Details in first post.
Click to expand...
Click to collapse
wow ... that was quick ... maybe i should look into a custom tweaking app for my rom ...

Zero Computing said:
Will test this later, for sure! If all goes well, may I request permissions to include this with the MIUI build I will be learning to make and attempting to produce?
Click to expand...
Click to collapse
Of course you can!
edit: My phone wasnt particularly laggy before except when playing games, but there is a noticeable difference after executing this binary. Noticed a few small hangs but unsure if it is related to this binary.
Click to expand...
Click to collapse
Yeah, sometimes we really do hit filesystem I/O limits, but at least this should help once everything has been cached.

Ok, autostart on boot is working.

Seems to be a little faster...game still lagging though guess I will give it time
Sent from my SGH-I927 using xda app-developers app

Trying it out. Definitely noticing faster returns to the home screen. I'm using the ICS "only one" build for galaxy note sgh-i717
.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app

OMG! I downloaded via qr code. and OMG! My phone runs sooo much smoother than before!!

This is one of the best mod for glide ever. Things are much smoother and faster to access. ES file explorer, dialer and contact list comes up so fast.
Thanks for this, really appreciate the mod. I'm keeeping it .
Sent from my SGH-I927

Would this work on other devices?

New CM10.1 Audio HAL for Steelhead Amplifier

I have been using my Nexus Q for about a year via the audio amplifier outputs. When the last Music update broke Q functionality, I decided to give CM10.1 a try on the Q. After fighting some installation issues, where all audio output except "Alarms" were silenced, I found that audio is only working on the HDMI output.
After digging through the code and doing a bit of analysis of the stock Audio HAL, I figured out how to make an audio HAL that supports the TAS5713 audio amplifier used in the Q. As of now, it only supports one audio output device (either HDMI, S/PDIF, or TAS5713) at a time, and the output can only be changed during compile time.
But with some work, this HAL could eventually support all three outputs (HDMI, S/PDIF, TAS5713.) The issue is that Android only appears to support one output device at a time. In order to overcome this, I believe the audio HAL would have to replicate the PCM data stream and send a separate copy to each device.
Through experimentation, I found that the TAS5713 requires a 48KHz audio stream, and S/PDIF also works well with this rate.
Another challenge is that the TAS5713 amplifier volume is controlled by the kernel driver, so you have to tell Android that the Audio HAL will do the volume control itself (ie, not rely on the mixer in Android.) For this reason, if all three output devices are eventually supported, volume control for S/PDIF and HDMI would have to be done in software. Perhaps it can be done while duplicating the PCM stream by taking each of the 16-bit values and multiplying it by the volume level.
Looking through the Steelhead kernel, you can see that Google put some work into being able to synchronize the three audio output devices. This would also have to be added to the HAL for proper operation.
Anyway, I'm putting the changes out there in GitHub in case someone wants to do some more improvement to this audio HAL.
The fork of CyanogenMod/android_device_google_steelhead is hharte/android_device_google_steelhead:
https://github.com/hharte/android_device_google_steelhead
For binaries that you can flash to your Q (TAS5713 audio amplifier and S/PDIF) please scroll down to post #9 and choose the correct binary. Each binary only supports one audio output.

Please make this a reality.. I'm dying to have the analogue outputs working at the same as HDMI. it was possible on the stock Nexus Q image.

Thank you for the work you've put into making this a reality. I would love to try out a build with the amplifier selected as the output device, but it sounds like you can't control the volume natively?
Sent from my Nexus 4 using Tapatalk 2

Thanks for doing this!
After cloning your repository, I wasn't sure what to modify to have audio output through S/PDIF or TAS5713. Would you mind giving some advice to someone new to building CM?
Thanks in advance.

mahler47 said:
Thanks for doing this!
After cloning your repository, I wasn't sure what to modify to have audio output through S/PDIF or TAS5713. Would you mind giving some advice to someone new to building CM?
Thanks in advance.
Click to expand...
Click to collapse
In device/google/steelhead/audio/audio_hw.c, change the following line in the function adev_open():
adev->card = CARD_STEELHEAD_TAS5713;
Change CARD_STEELHEAD_TAS5713 to one of:
CARD_STEELHEAD_HDMI,
CARD_STEELHEAD_SPDIF,
CARD_STEELHEAD_TAS5713
Volume control should work fine for each of these, based on my last commit:
https://github.com/hharte/android_d...mmit/a15f772b5651e0b14c65f6ff1a6d498d2951e081
Then "brunch steelhead" to re-build CM10.1 for Nexus Q. After it is done building, you can go into out/target/product/steelhead/ and do "fastboot -w flashall" to wipe and flash the new CM image. If you are making minor mods, no need to use "-w" to wipe.
Please let me know if you find any issues. One of the main things I've struggled with when using CM10.1 on Nexus Q is that sometimes after installing gapps, the audio is completely silent. I have not found a good way to fix this other than downloading and installing "Audio Manager" from the Play Store.
-Howard

Howard, YOU ROCK!
This is amazing. My Nexus Q is nearly back to the functionality that I once had with stock firmware, and it's once again a useful device.
Here's my setup:
1) 2013-06-12 nightly build with your changes merged, and as instructed above, audio sent to S/PDIF. My Q is connected to the stereo via optical cable.
2) VNC Server is installed on the Q, and it turns on upon boot. I am using this VNC Server, but I bet others would work.
https://play.google.com/store/apps/details?id=com.schumi.vncs
3) I also have FTP server and ADB Wireless turned on upon booting so I can push files and mess with the Q remotely.
4) VNC Viewer installed on my other devices.
With all of that, I can basically control the Q remotely from my phone, tablet, or computer. VNC is slow, even with a wired connection, but it works.
Prior to your good work, I had to have the TV on to hear anything out of my Nexus Q. However, with the changes you've implemented, I no longer have to do that. My Q lives again!! :victory:
Thanks so much--things can only get better and better from here. This is exactly why the Android community is so amazing.

mahler47 said:
Howard, YOU ROCK!
This is amazing. My Nexus Q is nearly back to the functionality that I once had with stock firmware, and it's once again a useful device.
Here's my setup:
1) 2013-06-12 nightly build with your changes merged, and as instructed above, audio sent to S/PDIF. My Q is connected to the stereo via optical cable.
2) VNC Server is installed on the Q, and it turns on upon boot. I am using this VNC Server, but I bet others would work.
https://play.google.com/store/apps/details?id=com.schumi.vncs
3) I also have FTP server and ADB Wireless turned on upon booting so I can push files and mess with the Q remotely.
4) VNC Viewer installed on my other devices.
With all of that, I can basically control the Q remotely from my phone, tablet, or computer. VNC is slow, even with a wired connection, but it works.
Prior to your good work, I had to have the TV on to hear anything out of my Nexus Q. However, with the changes you've implemented, I no longer have to do that. My Q lives again!! :victory:
Thanks so much--things can only get better and better from here. This is exactly why the Android community is so amazing.
Click to expand...
Click to collapse
Glad to hear that it is working for you. I'm using AirBubble and Bubble uPnP apps on my Q along with "Remote for iTunes" on my phones/tablet. This allows me to actually use my iTunes library on the Q remotely, and DLNA as well.
What needs to be done next (but not sure when I will have time to do it) is to make some changes to the Audio HAL to replicate the audio stream for each output (HDMI, Amplifier, S/PDIF) and implement software volume control for the HDMI and S/PDIF.
Another really cool thing would be to be able to make the Q into a Bluetooth A2DP sink. Then you could pair it to your phone and use it as a set of bluetooth speakers.
Google obviously put a lot more effort into the Q than I have done (making a remote management app that is simple to use, and put a lot of work into making sure that the three audio outputs are synchronized.) So there is a lot more work that needs to be done.
Maybe eventually Cyanogenmod can take my audio HAL. At least it seems to be working as well as the one included in the CM10.1 nightly, and adds the choice of using the other audio outputs, although only as a compile option unfortunately.

I'm embarrassingly uninformed about the inner workings of Android, but is ALSA in Android in any way like it is in Linux? Because I think in Linux when you use ALSA to configure your sound devices and let's say you use Pulse Audio, you have to define in the ALSA config which devices to output sound to and also expose them somehow to the PA mixer. It sounds like what you're doing is only compiling one alsa module whereas a HAL more like the one Google's would be 3 separate modules, right? And then I have no idea how the Android mixer works, but in Linux you'd have a master slider that would control the digital sound and then separate sliders for each output device. Is that sort of behavior replicable in Android?
On a different note, I'm really really sorry to beg because I'm so close to getting a CM build environment set up for the first time, but could either of you gentleman upload a working TAS5713 build? I feel pathetic because it's taken me 2 days just to get a VM image set up on my wife's laptop and most of the CM repo synced and I just *know* that this rom is going to take hours to compile (assuming I was competent enough to set it up right and create a proper manifest). Once/if I get everything set up, I think I'm going to go ahead and commit to merging your amazing work with CM10.1 final when it's out and uploading the zip so that all 5 of us Nexus Q owners out there don't each have compile it from source, but for now, I'd appreciate any help y'all can give me

Malnilion said:
On a different note, I'm really really sorry to beg because I'm so close to getting a CM build environment set up for the first time, but could either of you gentleman upload a working TAS5713 build? I feel pathetic because it's taken me 2 days just to get a VM image set up on my wife's laptop and most of the CM repo synced and I just *know* that this rom is going to take hours to compile (assuming I was competent enough to set it up right and create a proper manifest). Once/if I get everything set up, I think I'm going to go ahead and commit to merging your amazing work with CM10.1 final when it's out and uploading the zip so that all 5 of us Nexus Q owners out there don't each have compile it from source, but for now, I'd appreciate any help y'all can give me
Click to expand...
Click to collapse
Hello,
Here is a build of CM10.1 from repo sync on 6/17/2013 for each of TAS5713 and SPIDF outputs:
These files ar enow being hosted at AndroidFileHost
TAS5713 (Audio Amplifier):
Download: https://www.androidfilehost.com/?fid=95784891001602467 (148MB)
MD5SUM: adc98db7a9905b89c0d2fa9eab601f58 *cm-10.1-20130617-UNOFFICIAL-steelhead_TAS5713.zip
SPDIF:
Download: https://www.androidfilehost.com/?fid=95784891001602468 (148MB)
MD5SUM: ec26a86a5011cf480a9efb3cee63e000 *cm-10.1-20130617-UNOFFICIAL-steelhead_SPDIF.zip
HDMI: Use stock CM 10.1 nightly build.
Note: If, after installing, you don't have any sound, then install gapps and download "Audio Manager" from the Play Store. Run Audio Manager and select the "Mute" profile, and then select the "Loud" profile.
To install:
Boot into recovery mode:
Code:
fastboot boot recovery.img
When Q has reached recovery mode, push the cm-10.1-....zip to /sdcard using adb, ie:
Code:
adb push cm-10.1-20130617-UNOFFICIAL-steelhead_TAS5713.zip /sdcard/
push gapps (if desired) to /sdcard/
gapps-20130301.zip http://goo.im/gapps/gapps-jb-20130301-signed.zip md5: b7e53e96e1c8b1a1c4865bf29418c8e0
From within recovery, "install zip from sdcard" and browse to cm zip file. After this has installed, it is a good idea to wipe data and cache. Then install gapps (if desired) by again choosing "install zip from sdcard" and choosing the gapps .zip file.
If cm10.1 gets stuck in a boot loop, then you probably forgot to wipe. Reboot the Q back into fastboot as follows:
Unplug power for Nexus Q and wait about 10 seconds.
Plug Q back in.
When the LED lights up on the top of the Q, cover it with your hand until the LED ring turns red. This has to be done in less than one second. If you miss it, try again.
As soon as the ring is RED, remove your hand, and the Q should be in fastboot mode.
Now, you can "fastboot -w" to wipe, or "fastboot boot recovery.img" to boot into recovery and wipe using the menu.
Please let me know how these work for you. I'm using these TAS5713 and SPDIF builds now and they are working fine for me.

Thank you so much! My foray into rom building was initially a disaster. I got what I thought was a good virtual image built and configured, but then I found out a fundamental error on my part...I had built a 32bit image. So, I finally just installed Ubuntu on a system partition and finally yesterday built my first stock CM image. I'm going to keep going so I can build for myself, but at least now I can listen to my music on my nexus q speakers while I'm working
Your build is working just great for me. The only times I've had volume issues on stock, I just had to wiggle the nexus q top and tap mute/unmute a couple times. I don't know if your HAL is any different or not yet, but so far, so good! Thanks again!
Edit:
I've mirrored your files and intend for this to be the place I'll put my builds in the future. I'm fairly sure Google Drive doesn't have bandwidth limits, so anybody reading...have at it!
Sent from my Nexus 4 using Tapatalk 2

Make sure you have plenty of RAM in your VM. I'm building on a Mac Pro running Ubuntu (not in a VM) and it takes about 35 minutes to build.
Tried once in a VM running under Windows and killed it after about a day... but the VM only had 1GB of RAM allocated to it.

Thank you so much for the amplifier-build! Just installed it and my Q is better than before. For everybody who wants to re-use the Q as a music player, I can really recommend bubbleupnp. It directly accesses your Google Cloud Music and makes it available via DLNA to other devices
Just install it on the Q and on your tablet / or phone. On the device you want to use as a remote, you can select which media server (Nexus Q) and which media renderer to use (Nexus Q). And - bam - you have your Q back. Browse your media from the phone and play it directly from the Q. Bubbleupnp even has an option for autostart, so once everything is setup, you don't have to use keyboard / mouse / monitor.
The DLNA thingy also has another neat side-effect: The Q now is recognized in Windows 8 as a dlna-device and you can browse you entire Google Music Library with the Windows Explorer and play stuff to your Q...
Guess someone's happy his little gadget is back...
Again. THANK YOU for your awsome work on the Q.

New Life for the Q
[Solved]: was using an HDMI to digital converter cable. Hooked it up to my TV and everything worked great.
First, I would like to say.... this is great! I thought the Q was done.
I'm having some trouble with the install. I was able to push everything to the device, booted into recovery, followed your instructions in flashing CM10.1 and gapps.... and then all I got was the orb sitting there with its blue light and no video. I've messed up flashing roms on other android devices so I thought I would pop back into recovery and try another shot at flashing CM10.1 without gapps. I boot into recovery, the light on the Q keeps spinning (which is what I remember) but there is no video! I know I am in recovery because I can top the Q and it reboots (first option in recovery). What can I do?
thank you,
Tony

Awesome work, thank you !
This is exactly what I was looking for.
Thank you also for the idea of using bubbleupnp, it seems that the new functionality will be better than the original.
I can hardly wait to re-image my Q.

Thanks a million for sharing your work! Works like a charm for me with the SPDIF build.

Bullet91 said:
Thanks a million for sharing your work! Works like a charm for me with the SPDIF build.
Click to expand...
Click to collapse
Op we need ypour help if you would mind updating this to the newest nightly and giving a little support I will kick you some money I emailed you too since you are the only one who has gotten the amp to function.

Thanks for the work you have put in, but every time i try to download the TAS5713 version it is not the 148mb you post says and does not have a matching md5sum.
Can someone host their working TAS5713 build for me?

unknownkwita said:
Thanks for the work you have put in, but every time i try to download the TAS5713 version it is not the 148mb you post says and does not have a matching md5sum.
Can someone host their working TAS5713 build for me?
Click to expand...
Click to collapse
Yes the build I downloaded doesn't work either.

im hosting the rom Anthony uploaded in this g+ post. To the best of my knowledge it is the TAS5713 CM10.1 rom that was originally modified by hharte. Ill keep it up for the foreseeable future. I TAKE NO RESPONSIBILITY FOR ANYTHING.
https://docs.google.com/file/d/0B8a2mhiG243Ja1lqc0xVQzAwdjQ/edit?usp=sharing

ianandamy said:
Yes the build I downloaded doesn't work either.
Click to expand...
Click to collapse
Are you flashing the AMP build provided in this post? http://forum.xda-developers.com/showpost.php?p=42690346&postcount=9
For me it is the SPDIF build which is working, I did not test the AMP one.

My Daily Driver Hall of Fame

Index (use Ctrl + F)
Introduction
Panache DD HoF Requirements
Physical upgrades
After Root Report
2014 Stepp_aospX Editorial Correction
Stepp_aospX Troubleshooting Final Corrections
Beauty Shots -- Phone Screenshots
Click to expand...
Click to collapse
Introduction
It's 2014, and stock GingerBread is so boring, so you googled and found the best surviving Glacier rooting guide, upon the newest ROM list, but you saw the entries covered with dust, links as old as Fred Flintstone rolling towards extinction in a dinosaur powered car. You said to yourself, It's too late, the phone's dead.
Your lead is cold, and you don't feel like playing thread detective, so allow me to present, your best answer since the last phone retirement case...
Panache DD HoF Requirements
Well I do say old chap, we ought to have standards coming from a Titanic class phone, and thus...​
Stability - The least crashes, freezes, and bugs.
Function - Every hardware function works with software. Buttons! GPS! BlueTooth! WIFI! Data! Camera! Speakers! Light! Sound! Action! all working as intended.
Battery - Efficient Kernel, combined with ROM must match or exceed stock battery uptime.
Compatibility - Common apps on the market works on the phone. (Youtube, MX player, Browser, etc)
Physical upgrades
We can rebuild him, with a bigger battery!.​
SD Card: SanDisk ultra 64GB microSD from stock Samsung 8GB (iirc)
This was just an adhoc cheap fill one day on amazon.
Battery: Mugen 1700mAh Thunderbolt slim (similar size for MT4G/Panache) from stock 1400mAh OEM
Why? Stock died on 2013, charge held for literally 1 hour max, then battery started bulging.
Improvements: 48 hours uptime on light use, stock gingerbread 2.3
Also: Slightly bigger than stock 1400mAh, in length, fits very tight, no extra backcover required.
Alternatives: Anker batteries, use the search, I've heard they're the best upgrade and bang for your buck.
After Root Report
How I ate the breadcrumb trail, ROM after ROM; optional read..​So the first thing I did was find the newest version of android and the most recent candidate.
aospSX, which was the Synthetic.Nightmare's aospX's work carried over to android 4.2.2 (Jellybean) by SteppNasty.
Looked and felt amazing, however impassable amounts of issues lead me to switch, including malfunctioning stock camera, firefox, dolphin, and stock browser stops responding, and 1-bar signal which plagued Android 4.2 (term: "signal drop" if you want to search).
So I searched for the word "stable"...
CM 7.2, the most stable version of Gingerbread, the stability and battery was amazing, but it didn't feel as good as the JB ROM before.
So I searched again, and I found a like-minded user from the past with similar objectives, Darkgiant revealed through a conversation to another user about the most stable ROMs.
The clue is CM10.0 by either 0.0 or coderz, but one is a dead link, the other have outlined issues after it got discontinued.
So I went back, double guessed myself on the older versions of Steppnasty's ROM.
2014 Stepp_aospX Editorial Correction
For installation of aforementioned ROM, some non-obvious things he didn't mention..​To summon the proper Steppnasty's ROM for your android... you must:
Install the Stepp_aospSX Final
Fix Permissions
Reboot and setup phone settings (Language, google sync etc.,)
Reboot into recovery
Wipe Cache, Dalvik Cache
Install ICS GAPPs
Reboot and use the phone!
Trouble with ICS GAPPs ? (Based off of my anecdotal evidence).​After ROM installation from downgraded Froyo, ICS GAPPs wasn't applicable (md5 double checked)
I just used the phone as is, later on, somehow I was able to install the ICS GAPPs.
Incase you can't use GAPPs, know this may be temporary and you're missing these features (afaik):
Facial recognition via lockscreen
Software EQ for stock Music player
TLDR:
aospSX 1.0.0 -- Android 4.2.2 (JellyBean) -- newer version -- Unstable
Stepp_aospX Final -- Android 4.0.4 (IceCreamSandwich) works only without GAPPs.
Although the ICS version (Stepp_aospX) is old, it's better and not much different, a halfway mark between GB and JB.
Stepp_aospX Troubleshooting Final Corrections
Radio, bugs/glitches, GPS locking, Perma-Voicemail-Notification, My battery omg my battery :crying:!.​
Only swap radio files if absolutely necessary, and when you do, check the md5 sum every hair of the way.
The Radio Version, most important function to your phone, receiving calls from the network towers, has been changed! Haha I should've posted this before the link to rooting. It's when you were downgrading to Froyo (iirc), because no other ROMs I've installed changes radio, this ROM didn't change it either. But no worries, there are vast lists of these radios, available to download either here (CM Wiki) or here (dropbox by acefsw). Just use adb to push the PD15IMG.zip file as usual to sd for a recovery install. The difference between your signal, if it's even different, should be almost immediate after a reboot.
Bugs/Glitches:
Matrix/Zalgo Text // looks like y͏̴̡͢o͜͞҉̴͢u̢̨̕͝'̸ĺ̛͞͝l̕͜ ̸̵k̢͟͟͢ǹ̢̡̕͟ơ̸̡w̨͏҉̡̧ // Fix via rebooting
GPS Never-lock // Fix via dorqus
For GPS, you can also try FasterGPS the app.​
Perma-voicemail-Notification on every reboot // Temp fix: Settings => Manage Apps => Phone => Clear Cache.
Trying permanent fixes now, I've heard if you get voicemail, delete it from voicemail center, it'll work.​
Battery Drain from wakelock // GOOGLE PLAY SERVICES! // To Fix, either task it or filter it (require xposed framework) (For more information on battery, I'll make a separate section later on for wakelocks to filter by, to reduce drain, it allows battery drain only from user permitted activity apart from being idle)
Screen turns off automatically on camera mode and youtube videos // Fix: use screenOn app
Notification cannot be manually toggled off like app settings of JB. // No Fix, hope your app isn't as bad as my Lux D:
Headphone Heat: No bug noticeable, with ATH-M50 headphones, Skullcandy earbuds, Speaker phone over long hours, no over heating.
Extra tips while Unix Editing:
Code:
adb remount
to change permissions of /system/ folder files
[in shell]
Code:
mv renameMe.file renamed.bak
renames .file to renamed.bak, useful for creating backups before pushing gps.conf.
Code:
rm renameMe.file
deletes renameMe.file
Code:
cd ..
cd space
Moves up a directory outside of current folder
Moves into space folder
Code:
ls
lists items in folder
Final Result
Subject to change from threats, bribes and future tweaks/experiences.​
:good: Stability - 9/10, only zalgo text so far...
:good: Function - 8/10 Every hardware button works from stock apps, two of the cameras, LED, Flash, light sensor, microphone, voice search, gps, bluetooth, speakers, mobile data, backup-sync, auto-rotate all work well, I only wish some functions could work without tweaking, ie GPS and notifications bug.
Battery - 5/10 Efficient options provided with smartassv2 and selectable others, however the phone is awake more than necessary, see batstats Currently I'm trying to figure out what wake trigger is doing this (apart from google play) to see if it can beat <20 hour battery time from stock >48 hours with light usage.
Problem solved, new section write-up incoming soon...
:good: Compatibility - 10/10 Stepp_Nasty advised some amazon apps doesn't work, I don't dwell on those fields, being a canadian. However it's awesome that this works just as well as the stock gingerbread, and your camera resolution increased. See comparison (2592px × 1456px vs 2592px x 1936px).
This is the best ROM I can find, if you have another favourite, please list it and give it a rating, because in a few years this phone is going to the grave yard, and whoever is looking here now, still have a glimmer of hope!
Shoutout to XDA Glacier, past and future posters, for giving us the resources to build on this awesome phone.
Future Edits: Format; txt y u no wrd wrap, More Links, Updated Root Guide, Experience/Final Result, more Bugs/tweaks.

NO MORE SLOW.

For the few who remain using these tablets (and the even fewer who bought a 2015 shield controller like me) I have the final nail in the coffin for performance. Without custom OS. Allowing you to use your very specific (criminally underused) 2015 Shield controller wirelessly. Welcome to the end of your woes (performance not guaranteed, this crap worked for me though). I still haven't checked if battery usage has improved, but it has certainly let me depend on this and use my controller again as opposed to using a CustomOS (previously used AEX 6.7, good performance, but bad video playback and lack of wifi controller support).
Required thingys:
TWRP
This awesome script (JournalingDisabler.zip) (thnx very much skynet28): https://forum.xda-developers.com/t/...urnaling-in-internal-ext4-partitions.1252028/
Developer Options
Snacks? Drinks? This is gonna take some time, don't pass out halfway through lol
Boost 1: DISABLE JOURNALING.
Y'all. This is the good stuff. the nitro. This will make your tablet feel new (again, if everything goes right and I'm not some insane fluke). I only got the idea from an offhand comment from m0nt3s. I thought they were talking about one of the writing apps at first, but once I learned what it was, my brain imploded. Did a quick google search, and found skynet28's solution right away. It's a script designed to disable an ext4 logging service that eats up memory and processing power. I didn't think it would be compatible (but my chaotic neutral mind said why not), but it works:
1. Install TWRP using adb and prayer (that's what it feels like the first time around lol)
2. Download the zip (JournalingDisabler.zip) to your tablet.
3. Use the install button in TWRP, navigate to the zip, and install away.
It should show text saying journaling is disabled if all went well. The gains should be immediately noticeable on your next boot. I didn't notice any issues or side effects, but I also have the benefit of not having important/sensitive data on it, so just to play it safe, back up your data in case issues crop up later.
Boost 2: BACKGROUND PROCESSES
This one will be a touch more noticeable, especially if you multitask on this tablet, but it can definitely stop a lot of the hitching. This one will be in the bottom of the developer options. If you don't have dev options, go into the about tablet section and tap the build number until you become a dev. Setting it to 1 or 2 is decent, but setting it to none will have the biggest impact.
Boost 3: DON'T USE APP OPTIMIZATION
Seriously. Don't know who dropped the ball. But just turn it all off. It's not even a boost, it's just a negative having it on.
Boost 4: SYNCING
If anything is syncing, be it Gmail, your YouTube notifications, or a news feed, turn it off. Any time apps struggle and fight for WIFI, your experience sucks. If you aren't using it as a main (i'm using it in my car as a head unit)
Boost 5: Color Correction
Must have been the same peeps who dropped the ball on app optimization. With the gains you get above, you might not need to, but if you're trying to max it out this will do it.
That's it for me! This is what I've done to get my tablet feeling smooth again. Let me know how it goes?

I can attest that a lot of the above is what needs to be done to save the last days of this tablet. I did not now about the journal part- will have to try this. Related, I just flashed the original OTA's for the Wifi edition on my Shield LTE. By doing this I got a insane boost in battery life. The LTE (H+) does not work but I don't need it and there are other devices that have much better connectivity .

BLKMN said:
For the few who remain using these tablets (and the even fewer who bought a 2015 shield controller like me) I have the final nail in the coffin for performance. Without custom OS. Allowing you to use your very specific (criminally underused) 2015 Shield controller wirelessly. Welcome to the end of your woes (performance not guaranteed, this crap worked for me though). I still haven't checked if battery usage has improved, but it has certainly let me depend on this and use my controller again as opposed to using a CustomOS (previously used AEX 6.7, good performance, but bad video playback and lack of wifi controller support).
Required thingys:
TWRP
This awesome script (JournalingDisabler.zip) (thnx very much skynet28): https://forum.xda-developers.com/t/...urnaling-in-internal-ext4-partitions.1252028/
Developer Options
Snacks? Drinks? This is gonna take some time, don't pass out halfway through lol
Boost 1: DISABLE JOURNALING.
Y'all. This is the good stuff. the nitro. This will make your tablet feel new (again, if everything goes right and I'm not some insane fluke). I only got the idea from an offhand comment from m0nt3s. I thought they were talking about one of the writing apps at first, but once I learned what it was, my brain imploded. Did a quick google search, and found skynet28's solution right away. It's a script designed to disable an ext4 logging service that eats up memory and processing power. I didn't think it would be compatible (but my chaotic neutral mind said why not), but it works:
1. Install TWRP using adb and prayer (that's what it feels like the first time around lol)
2. Download the zip (JournalingDisabler.zip) to your tablet.
3. Use the install button in TWRP, navigate to the zip, and install away.
It should show text saying journaling is disabled if all went well. The gains should be immediately noticeable on your next boot. I didn't notice any issues or side effects, but I also have the benefit of not having important/sensitive data on it, so just to play it safe, back up your data in case issues crop up later.
Boost 2: BACKGROUND PROCESSES
This one will be a touch more noticeable, especially if you multitask on this tablet, but it can definitely stop a lot of the hitching. This one will be in the bottom of the developer options. If you don't have dev options, go into the about tablet section and tap the build number until you become a dev. Setting it to 1 or 2 is decent, but setting it to none will have the biggest impact.
Boost 3: DON'T USE APP OPTIMIZATION
Seriously. Don't know who dropped the ball. But just turn it all off. It's not even a boost, it's just a negative having it on.
Boost 4: SYNCING
If anything is syncing, be it Gmail, your YouTube notifications, or a news feed, turn it off. Any time apps struggle and fight for WIFI, your experience sucks. If you aren't using it as a main (i'm using it in my car as a head unit)
Boost 5: Color Correction
Must have been the same peeps who dropped the ball on app optimization. With the gains you get above, you might not need to, but if you're trying to max it out this will do it.
That's it for me! This is what I've done to get my tablet feeling smooth again. Let me know how it goes?
Click to expand...
Click to collapse
This works! Every bit of OP is legit.
I used current TWRP as of today, twrp-3.6.1_9-0-shieldtablet.img, from https://twrp.me/nvidia/nvidiahshieldtablet.html using fastboot install method on a fully updated Android 7 Nvidia Shield Tablet model p1761w.
Thanks, much respect!

It is important that those who still do not install TWRP should know that to enter fastboot, they must use the official nvidia drivers "SHIELD_Family_WHQL_USB_driver_201801"
This method helped me to lighten but it becomes impossible to install applications, the google services together with those of nvidia cause the ram to collapse and the system cannot manage correctly.
I strongly recommend you to change to a custom rom, you will finally feel the fluidity of the system
At this moment I use lineage 15.1 (android 8.1) + google services minimum (pico)
No chrome app - no Gmail app + facebook and instagram full app. and the system remains light.

nunitofiman said:
It is important that those who still do not install TWRP should know that to enter fastboot, they must use the official nvidia drivers "SHIELD_Family_WHQL_USB_driver_201801"
This method helped me to lighten but it becomes impossible to install applications, the google services together with those of nvidia cause the ram to collapse and the system cannot manage correctly.
I strongly recommend you to change to a custom rom, you will finally feel the fluidity of the system
At this moment I use lineage 15.1 (android 8.1) + google services minimum (pico)
No chrome app - no Gmail app + facebook and instagram full app. and the system remains light.
Click to expand...
Click to collapse
I really wish a developer(s) would take one more look at this device. If there was way to bump up the android version but retain the NVIDIA features it would breath a few more years into these . These tablets are still pretty good for mid range emulation and now that everything has changed with cloud gaming, they are not as irrelevant as it would seem . I've been having pretty good performance on my LTE 32GB that I flashed the original "WiFi edition " stock ROM on. I get great battery life now and use the tablet almost daily for gaming and light use. The sound is also still pretty impressive and I like the stylus functionality as I can't really afford a Samsung device.

What is "journaling"? Is it the same as the logging by logcat? You can set the buffer size to 0K or 64K (setting it to 0 still logs at 64K).