Related
This was the kernel thread but it is so full of question that it was renamed to Question and answer!
before ask search in the forum.
Guide to install:
http://sourceforge.net/apps/trac/androidhtc/wiki/HowToInstallWithAtoolsNand (Flash the phone)
http://sourceforge.net/apps/trac/androidhtc/wiki/HowToInstallWithAtoolsHaret (Dual system windows/android)
If you have "install module error" please install the android update on sourceforge. Read more here:
http://forum.xda-developers.com/showthread.php?t=848921
Awesome job on this l1q1d, i finally got around to getting the git set up on my computer yesterday so in can modify and compile so i'll try and get coding when i have some free time Thanks for all your efforts.
I have some memory issues with both 3-10-2010 and 4-10-2010 kernels. The memory usage is really high and my launcher(launcher pro) keeps getting closed/restarted all the time even without opening any other apps.
Here for testing...
Glad to see this thread started!! Thought dev for Kaiser had seen its end. I'm no coder but can help with testing.
Hey L1q1d, this isn't by any means vital but i find it annoying and don't know if any other kaiser users have found this. If i turn the phone on and don't unlock it before pressing the power button again (i.e. just to check the time), there is a relatively long delay before the screen turns off. If i unlock the phone and then press the power button it turns off instantly. I have attached the logcat from when the phone is turned on and then turned off, i have also indicated where it locks before turning off the screen. I'm looking into it but if you have any pointers or don't experience this with your device let me know please
-Arturo- said:
I have some memory issues with both 3-10-2010 and 4-10-2010 kernels. The memory usage is really high and my launcher(launcher pro) keeps getting closed/restarted all the time even without opening any other apps.
Click to expand...
Click to collapse
Ok scratch that looks like the problem has been caused by having data on ext2 partition.
The kernel 2.6.32 runs way better than previous, but i have a persistent fail that knocks out the screen, at start i can see a message saying "msm_i2c.0: Bus still busy, status 2100m intf 100" and another more saying "msm_i2c.0: Error waiting for notbusy". ¿It is a common fail or it's only mine?
Hi
the problem is I do not belong here
I tried several variants android
the Caller ID does not work
basic configuration of network settings, but it is not good
if you want to set up an error message is incorrect sim, and it is no longer a network
something that is not a solution?
L1q1d, good work. Some of the changes you have made, such as nand, affect all of the related phone types. So, you might want to at least mention them on the vogue kernel thread. On the other hand, the keypad and battery code is not used by vogue. As you know, Polaris uses the same battery code as Kaiser.
I'm thinking two changes for battery code:
a) going back to max voltage and current instead of average, to work better with poor batteries. My old battery sometimes has deep dips in its reported voltage, causing a recalibration to 5% capacity when it really has more like 40%.
b) the recommended capacity calculations at high and low calibration points should be "recommended = battery_capacity - (new - old)" instead of "recommended -= (new - old)". As things are, the recommended value is pretty close on the first calibration, but any subsequent calibrations apply the same correction over and over again, making the recommended value go negative or insanely positive. Of course I cannot remember the names of the variables.
@L1q1d
This is a nice idea to make this thread for kaiser users.
Today I tried the latest kernel 4-10-2010 with fresh froyo 2.2.1 (nand installation). First the system works well. But after installing the ADW.Launcher from the market and after a reboot I got always chrashes from this launcher and I never had this before with any other kernel and the launcher version has not been changed. So maybe I have the same issues then Arturo. Then I tried the app task killer but it chrashes after starting it (same problem). I think these problems could be memory issues in the latest kernel version.
Keep going on your nice work for kaiser
l1q1d I have just got a framework exception and as usual 90% of apps don't work anymore. It occured using the latest kernel.
Also I still keep getting those launcher pro redraws It didn't happen while using the 2.6.25 kernel. Has the memory management been changed in the new kernel?
Do you use compcache? Like wlan, compcache uses kernel drivers that have to match the kernel version. I use compcache with backing store on 4th partition of sdcard.
Sent from my Full Android on Vogue using XDA App
n2rjt said:
Do you use compcache? Like wlan, compcache uses kernel drivers that have to match the kernel version. I use compcache with backing store on 4th partition of sdcard.
Sent from my Full Android on Vogue using XDA App
Click to expand...
Click to collapse
Yes I do. I ripped the compcache.sh file from latest dzo's fresh froyo build.(I remember reading Kalt Kaffe's post about getting compcache to work with the newest kernel a while ago so I assumed that it has been sorted out and we can enable compcache with new kernel) I'm on NAND at the moment with both system and data. I've tried system on nand and data on ext2 partition but the launcher redraws were killing me, every time I opened opera mini and then closed it the launcher was closed and I had to wait for it to load into memory again.
I'm back to system and data on nand at the moment with new kernel and it's much much better but still it happens from time to time. I've never experienced launcher redraws with the old kernel so I don't really now what;s wrong.
About the 4th partition....you mean swap, right?
When I was on nand +sd card I had 3 partitions 1) fat 32 then 2) ext2 about 30 mb(I don't know what for is the first ext2 partition but i remember that i couldn't install data to sd card with only one ext2 partition) and finally 3) second ext2 partition for data about 300mb. So by creating the third ext2 partition I would activate swap in compcache? I've never tried as I heard that it might used up the sd card faster. also I only have two sd cards 6gb(class 4) and 12 GB (class 2) so I think i would probably need class 6 for swap file?
The compcache-required modules are included in the 2.6.32 modules attached to my first post of this thread. Those files should work with any recent 2.6.32 kernel. I would suggest that we should be able to get modules the same place we get zImage and NBH files.
I wouldn't recommend backing store for everybody. It works for me, with my 8GB card, but I'm not sure it ever even writes anything to the swap partition. And, yes, my fourth partition is a swap partition. Kallt-kaffe's latest compcache.sh script should work fine.
An easy way to find out of your compcache is working: use the "free" command from the command prompt. If swap is shown as zero, compcache is not working. You can also see failures in the dmesg log.
n2rjt said:
The compcache-required modules are included in the 2.6.32 modules attached to my first post of this thread. Those files should work with any recent 2.6.32 kernel. I would suggest that we should be able to get modules the same place we get zImage and NBH files.
I wouldn't recommend backing store for everybody. It works for me, with my 8GB card, but I'm not sure it ever even writes anything to the swap partition. And, yes, my fourth partition is a swap partition. Kallt-kaffe's latest compcache.sh script should work fine.
An easy way to find out of your compcache is working: use the "free" command from the command prompt. If swap is shown as zero, compcache is not working. You can also see failures in the dmesg log.
Click to expand...
Click to collapse
Excellent N2rjt i think you just found the cause of my issues. I updated my system with the modules you have linked enabled compcache again and then i entered the "FREE" command and swap shows zero. So the compcache is not working this must be the reason for constant launcher redraws. Now what could be the cause of "broken" compcache?
Sent from my Full Android on Vogue using XDA App
lzo modules are now included in the kernel, you need only ramswap. probably compcache script have some problem with it.
Ok, guys I got a compcache.sh file from the latest dzo's froyo and compcache is finally enabled. I will be testing the device to see whether the issues are gone. Thanks for your help.
Bug: white screen, Android still alive
How I got a white screen:
AT&T Tilt-flavored Kaiser, latest kernel and dzo's Fresh Froyo, both built from current git code.
I was typing on the hardware keyboard, actually entering a message for xda-developers. I wanted to say "dmesg | grep ds2746", but couldn't find the "|" symbol. I remembered that the hardware keys for the soft keys (between R-T and between I-O) have some symbols mapped to them, so I was trying different Fn- and Symbol combinations of those keys.
Eventually I hit Fn-(Left soft key), and got a text screen with dmesg logs.
Okay, how to get back to a graphical screen? I tried a few keys that didn't take me back, then had a brilliant idea, hit the red hangup key.
That blanked the screen, but when I hit other keys to wake up, I had a white screen. Yet, adb logcat verifies that the phone is still running Android, and it is even responding to my touches, just I can't see anything except white.
Edit: can recover by using Fn- keypad right soft key.
Battery issues?
If anyone has battery issues, please open a terminal, and type this:
> dmesg | grep ds2746 > /sdcard/dmesg.log
and send the dmesg.log file.
Thanks!
Good Evening,
i want to optimize the RAM Managment of my Arc
but idont really now how Supercharger works.
How must i begin ?
Can anyone write a how to ?
dubist said:
Good Evening,
i want to optimize the RAM Managment of my Arc
but idont really now how Supercharger works.
How must i begin ?
Can anyone write a how to ?
Click to expand...
Click to collapse
zeppelinrox said:
Before you start reading, just know that this is not difficult to implement... it's easy.
1. Download a script. 2. Load it. 3.Select what you want. EASY.
It works on ALL Android devices - Custom Roms or Stock Roms, Phones or Tablets, it doesn't matter!
Also Note: Nothing else does what The V6 SuperCharger does!
................Not AutoKiller Memory Optimizer, Not Auto Memory Manager, Not Minfree Manager...
................And NOTHING BEATS IT. PERIOD.
So... if somebody says to you that V6 SuperCharger does the same thing as [pick any app], tell them to first read about what they're talking about so that they can actually have an informed opinion.
Get A Taste of The V8 SuperCharger - Grab the 3G TurboCharger & Kick Ass Kernel Tweaks Installation Scripts!
......................................................... - V8 SuperCharger Alpha for Milestone!
==================================================================================
Memorable User Comments: "Feels like I have a new phone!", "Supercharger rocks bro, I'm actually mad I waited so long to do it...","I wish I hadn't upgraded yet", "Now I can wait to upgrade", "I was about to throw this phone through the wall", "I was about to return it but now I don't have to", "This cured my phone of cancer!", "Oh man... just applied the V6 Supercharger Script by ZeppelinRox on my Android.. I think it fixed everything..", "I can't live without this!", "My phone is better than new!", "my phones has turned god mode on or somthing"
==================================================================================
99SuperCharger Tweaking: Of course, I don't own any rights in regards to the actual tweaks applied to system settings.
This means anybody is free to mess with OOM groupings, OOM prioriteis and minfrees.
So it's fine to modify and share your tweaked 99SuperCharger file as long as you leave the credits intact
Developers may include the attached V6 SuperCharger Installation Script in their roms. (This installs 99SuperCharger)
The attached V6 SuperCharger installation script may NOT be disassembled in any way, or be used as a part of any memory management app or package.
This is because it is no different than an app/apk found in the market. It's an installation program.
I don't own any right to tweak OOM Groupings, OOM Priorities, or minfree values. But I do own this program.
ATTN DEVS: If you want to use the V6 SuperCharger memory system in your ROM, give proper credit and a HTML link to this thread.
..................Of course, baking it into the rom is 100% fine.
..................You can include a copy of the attached installation script in the system/xbin folder so users can use it with terminal emulator
.................. - giving it a short name is fine as it's a pain to type long file names in terminal.
..................Do not modify it, do not rebrand it (ie. It's not called "V6script"). Thank you.
This is the only permissible distribution of the attached installation script - unmodified, in a custom rom and in the system/xbin folder.
Modification and redistribution of the attached installation script is not permitted at all.
This means that you cannot feel free to zip up the attached installation script with other tweaks and this means that it is not be edited and shared.
ATTN USERS: If you use or encounter a ROM with the V6 SuperCharger memory system, without proper credit given and no SuperCharger source links, please make the Developer aware of it, and if necessary, please let me know about it. Thank you.
Personal Use: You may tweak the V6 installation script (leaving credits intact) to your own personal liking as long as it is NOT redistributed in any way.
If you want to share this, just link to this thread.
If you want to make a thread in other forums telling people about it, that's great.
But I would prefer that you do not post a copy of the V6 SuperCharger installation script in those forums.
If you already have a thread with a copy attached, I won't bother you about it. But please don't attach further updates.
Your co-operation is very much appreciated.
I don't want diluted/broken V6 SuperCharger installations floating around and then have people say it doesn't work.
==================================================================================
What's it do?
It makes your phone FAST... super snappy with better multitasking!
It rearranges and fixes the OOM Groupings and Priorites and lowmemorykiller values.
So basically, it's a COMPLETE MEMORY MANAGEMENT FIX!
It's the ONLY one of it's kind
NO LAUNCHER REDRAWS, faster than ever, multitasking is better... why?
Because it works with the lowmemorykiller and letting it work the way it's meant to work.
Also, because of the rearrangement, it works the same on all roms!
The problem with using minfree tweakers like AMM or AKMO is that it doesn't work the same on all roms.
Secondary apps may be in slot 3 on some roms but in slot 5 in others!
That's why you hear people comment "I tried AKMO but it didn't do anything..."
Most likely it didn't do anything because the apps weren't sitting where they were expected to be.
So fasten your seat belts and enjoy the ride!
==================================================================================
Note: Do this at your own risk, regardless of how little risk there is - since I included UnSuperCharging
........ Well, do a nandroid anyway, if you like
Requirements:
1. Rooted Phone. Milestoners, you can use Universal Androot (not in market ?)
2. Script Manager or Terminal Emulator to run the script. Stock ROMs can also use SM to load up boot scripts!
3. Busybox 1.18.2 OR LOWER - 1.18.3 or newer are VERY much a hassle with errors that should NOT be errors!
4. AutoStart Script by me - Enables Stock ROMS (Milestone) to utilize etc/init.d for boot scripts.
Stock ROMS (Milestone) - Vulnerable recovery is not required!
Installing/Using:
1. Download the attached V6_SuperCharger_for_Android*.txt script and save to your sdcard.
... Do NOT run the V6 SuperCharger install script at boot!
2. Load the script (V6_SuperCharger_for_Android*.txt) into Script Manager and select "Run as Root."
3. Touch the screen for the soft keyboard or slide out the keyboard and get SuperCharged! Just pick an option!
4. READ the script's output!
5. Afterwards, READ the html HELP FILE in the root of your SD Card!
6. Disable "Lock Home in Memory" if your ROM has this option.
7. Optional: For a quick status check, you can put a Script Manager widget for V6 SuperCharger on you desktop
Cool! - Here is a Visual V6 SuperCharger Installation Tutorial (Screen Caps!) by MalarKeY007 (thanks dude)
If you are using compcache and have lag or slow down after SuperCharging,
DISABLE compache, wipe caches and re-enable it.
Also make sure to uncheck/disable lock home in memory! (and leave it unchecked)
Note: V6_SuperCharger-AOR.zip is for use with Milestone's Androidiani OpenRecovery. Even if you have a Milestone, don't run it within Android.
........ AOR Usage: Extract to the root of your sdcard (Directory structure is in the zip)
.......................... You will now have a SuperCharger Menu on the main screen. Simply select the menu and select 1 of the 12 options.
Main points:
- CUST-OOMIZER! Use your settings without Autokiller Memory Optimizer or Auto Memory Manager!
- For newer phones with lots of ram, use the 3rd slot to set how much free ram you want.
- If you have /system/etc/rootfs/init.mapphone_umts.rc, it makes a backup and edits that single file. This is nice and tidy.
... Thank to kabaldan for pointing out the importance of certain things.
- Most Custom ROMs - If you have a /system/etc/init.d folder, it creates 99SuperCharger in there and edits /data/local.prop (20 entries added for adjusting priorities and groupings). You shouldn't need to configure anything else.
- Stock ROMs - If you have neither, it creates /data/99SuperCharger.sh which you can load up on boot (run as root) with Script Manager. The OOM groupings work as well since it happens on boot in local.prop (20 entries added)
Note: For some reason, the minfree levels do not stick on some Custom ROMs. I don't know why this is. Maybe a bug in GingerBread?
........ You can check /res/user.log to see if it ran...
........ If this happens to you, use Script Manager to load /system/etc/init.d/99SuperCharger "on boot" and "run as root"
In case of any error, you will find a related help file in the root of your SD card.
So... I think this covers ANY Android ROM
It also determines if you're using Script Manager and gives appropriate information/tips/help files depending on what other factors are present.
The above is really ALL YOU NEED TO KNOW.
The V6 SuperCharger script does everything!
Anything below is extra info!
It's just a single file... 806 lines (807 if you count the blank line at the end LOL)
The Nitty Gritty... For Geeks!
If you read Post #3 (History Parts 1-3), you'll see that at first it was only about minfrees and launcher redraw.
But after installing GingerBread, I saw that it needed more work than Froyo LOL.
Groupings were ALL MESSED UP and made NO SENSE to me whatsoever...
So I figured out how to group them more like CM6 (Froyo) but that still wasn't good enough...
So I further rearranged the OOM Groupings and Priorites and lowmemorykiller values and created a SuperCharger for phone memory...
THE ONLY COMPLETE MEMORY MANAGEMENT FIX!
Upon installation, V6 SuperCharger will first clean up any previous supercharging so none of your files get cluttered.
But if you toggle between Hard To Kill and BulletProof launchers, the memory adjustments aren't affected.
So you can leave your minfrees at stock/default settings and apply the Hard To Kill Launcher and still get the OOM Grouping/Priority fixes.
So if you love your ROMs memory settings, just try the HTK Launcher/OOM Fix... you won't regret it
It's pretty awesome
Here are some snaps....
Before...
After...
During....
Bonus....
Say Buh Bye to AKMO or any app that has to load on start up to change minfrees...
So did you notice the difference in groupings?
By default, CM7 has nearly all the apps in slot 5 and the launcher in slot 3.
Slightly aggressive settings will kill any chance of multitasking in that situation.
After SuperCharging, the apps get moved to slot 3 while the launcher is in slot 2 but the most important item in slot 2.
I've read, "oh you don't need to run any scripts for memory management..."
Well that's not true.
Playing with minfree values is one thing... it's playing with minfree levels... it's not really memory management...
Look at the pics above... now THAT's memory management...
If you look below at Post #3... that's how it all started... good background info in case you're wondering what the hell I'm talking about.
Notes: Minfree changes take effect immediately! This means you can switch from Balanced settings to Gaming and back again without rebooting!
.......... Switching between Hard To Kill and BulletProof Launchers require a reboot to take effect.
.......... Disable your OS's "Lock Home in Memory" option, if it has it. This takes effect immediately.
.......... Or use "Lock Home in Memory" as a "Saftey Lock" - to toggle your launcher from "Bulletproof" (0) or HTK (1) to "Weak" (2)
.......... Note: "Lock Home in Memory" is not 1 with my OOM Grouping/Priority Fixes
Cool Tip: Sometimes it's difficult to keep a wanted background app alive, such as an SMS app.
............. If you're in this situation, check out how to Bulletproof Background Apps!
Remember: When using scripts, use the SuperUser app to DISABLE SuperUser permissions for AMM!
................. It can still monitor your OOM groupings but it can't change your custom settings on boot.
................. If you have AKMO installed, disable it's option to Apply Settings at Boot!
If you are using compcache and have lag or slow down after SuperCharging,
DISABLE compache, wipe caches and re-enable it.
Also make sure to uncheck/disable lock home in memory! (and leave it unchecked)
V6_SuperCharger-AOR.zip is for Androidiani OpenRecovery for Milestone!! - For Milestone ONLY!
Click to expand...
Click to collapse
This is my setup for V6 Supercharger:
Download the Supercharger script (V6_SuperCharger_for_Android-update9_beta_6.sh.txt) and put in into your SD card.
Load the script (V6_SuperCharger_for_Android-update9_beta_6.sh.txt) into Script Manager and select “Run as Root.” (Do NOT run the V6 Supercharger install script at boot!)
Touch the screen for the soft keyboard or slide out the keyboard and Select “MegaRAM 2″
Once it’s applied then choose “Nitro Lag Nullifier“
Then click setting menu, choose config mode, u will see a check box named “browse as root”, tick that box
From the main screen of Script Manager click back twice
Go to data/ and run 99SuperCharger.sh install script at boot and reboot your device
i dont have the option MegaRam
i use the Option 1000 HP Number 17
Than i run the Nitro Lag Nullifier
and than i go out to config and tick the browse as root
than i go to data and select that the supercharger99 must start at boot.
Now i have restart my phone how can i see if this tweaks are working ?
now i have only 71 Free Ram and without the Programm i had 190MB Free :S
dubist said:
i dont have the option MegaRam
i use the Option 1000 HP Number 17
Than i run the Nitro Lag Nullifier
and than i go out to config and tick the browse as root
than i go to data and select that the supercharger99 must start at boot.
Now i have restart my phone how can i see if this tweaks are working ?
now i have only 71 Free Ram and without the Programm i had 190MB Free :S
Click to expand...
Click to collapse
It's not physical memory it's virtual memory.
this means ?
Just to update this thread if anyone looking, here's the Supercharger thread that gets regularly updated.
http://forum.xda-developers.com/showthread.php?t=991276
Nitro Lag filter is in the newer beteas, isn't it?
I think I use update 8 (latest non beta update) and I can't remember that I had that option.
Btw if you update with FlashTool and don't wipe data SuperCharger doesn't get cleared, so no need for a fresh install
Sent from my iPad 2 using Tapatalk
Flo95 said:
Nitro Lag filter is in the newer beteas, isn't it?
I think I use update 8 (latest non beta update) and I can't remember that I had that option.
Btw if you update with FlashTool and don't wipe data SuperCharger doesn't get cleared, so no need for a fresh install
Sent from my iPad 2 using Tapatalk
Click to expand...
Click to collapse
Or just take a backup of 99SuperCharger.sh
ShyamSasi said:
This is my setup for V6 Supercharger:
Download the Supercharger script (V6_SuperCharger_for_Android-update9_beta_6.sh.txt) and put in into your SD card.
Load the script (V6_SuperCharger_for_Android-update9_beta_6.sh.txt) into Script Manager and select “Run as Root.” (Do NOT run the V6 Supercharger install script at boot!)
Touch the screen for the soft keyboard or slide out the keyboard and Select “MegaRAM 2″
Once it’s applied then choose “Nitro Lag Nullifier“
Then click setting menu, choose config mode, u will see a check box named “browse as root”, tick that box
From the main screen of Script Manager click back twice
Go to data/ and run 99SuperCharger.sh install script at boot and reboot your device
Click to expand...
Click to collapse
for point no.9 i opened the script and when the dialog pops up i press run as root then run...do i need to do anything else or have i done something wrong?
You have to select the tweak you want to apply before you quit.
And then you go data and make 99supercharger.sh run as root and run at boot.
Sent from my iPad 2 using Tapatalk
Flo95 said:
You have to select the tweak you want to apply before you quit.
And then you go data and make 99supercharger.sh run as root and run at boot.
Sent from my iPad 2 using Tapatalk
Click to expand...
Click to collapse
Ive ran the supercharger ive chosen multitasking option dont know if thats wise. But then I ran the 99supercharger script but never ticked run at boot. So do I repply the v6 supercharger tweak then the 99 script or shall I run it again.
Sent from my LT15i using Tapatalk
Just browse to 99supercharger.sh, thick run at boot and you're good to go.
Sent from my iPad 2 using Tapatalk
how to
Hi
Im having issues installing v6 supercharger on my arc. I followed the tutorial:
http://forum.xda-developers.com/showthread.php?t=1334834
I got:
- stock rom+root
- busybox 1.18.2
- script manager setup as described in tutorial
- script on the sdcard
I tick run as root, click run and... the result is in the attachment. I got some syntax error. Any idea what went wrong? pls help!
Use a newer version
I broke my phone somehow using this?
So, I followed the instructions & here's what happened.
After the phone rebooted asking to do a clean? the screen went blank & stuck there for 15 minutes. I'm pretty sure that the instructions said that it might get stuck in a boot loop. IF that happened, just take out the battery. So that's what I did.
Apparently, big mistake.
Now, My LT15A won't do anything. When I push the power button, I get a big fat nothing. Not vibration. no LED.
So I've tried to flash the phone with a Generic UK firmware, but the phone doesn't even connect to flashtool.
The phone was under warranty, so I'm wondering if what I've tried will have voided it (pretty sure, but I'm new to this)
Here's what I (used to ) have:
LT15A rooted with Titanium & bloatware removed
Rogers - bootloader locked
Android 3.4.3 *.42
Hi,
You have to remove the battery, put it again, and start your phone. Repeat two or three times.
Maybe I wasn't clear. The phone won't turn on. Period. No vibration, no LED. Nothing.
Tried with wotan? If you can connect it in fastboot?
Sent from my LT15i using XDA App
I've tried to use FlashTool & I can't connect. I haven't tried Wotan. What is that.
I've since sent my phone in for a repair under warranty. I haven't unlocked the bootloader (as far as I know) to see if they will repair/replace it. If they won't honour the warranty, I'll try that.
Thanks.
I just uploaded tiny noot, a very minimal root tool for the NST glowworm. I think it would probably also work for the simple touch, but I've lent mine out and cannot test it to confirm.
I am basically a cobbler here; many thanks to GabrialD, DeanG and the folks with the minimal touch root tools, which this is based on - and of course to mali100 and the CWR team for getting that on the Touch and Glowworm. Everything below is put together with parts from those projects using what I've learned at XDA and from Dean's nook color repartitioning scripts.
They make it possible for someone like me to knock out a package that's a little more convenient to work from than booting noogie and manually copying in files.
I am using the clockwork recovery zip installation mode for copying in the minimal set of files - I'm not trying to support the google apps or the many interesting screen refresh hacks.
I am not including a modified uRamdisk - the stock uRamdisk supports ADB, and you can get root via adb wireless simply by typing su, so I chose to leave well enough alone.
GabrialD has already released a modified uRamdisk for the glowworm (to support root by default as well as the light) but since stock works for my purposes, I'm not using the modified one.
What it does include:
su and busybox
nook color tools in /system, so that nonmarket apps can be installed
adb wireless
ADW launcher
Amazon appstore, so there's at least once source of "easy" apps
Button Savior
Nook Touch Tools
Supermanager and the Busybox updater interface
The install process is three steps. Four if you decide - and you should - to make a backup of your device before you start. (that process is: make the noogie disk. boot from noogie. connect to your computer. dump the NSTG or NST using dd or another disk imaging tool, and is described in more detail with tips for lots of different operating systems at http://forum.xda-developers.com/showthread.php?t=1142983 That backup will let you restore your entire device to a known working configuration.
Download mali100's nook touch CWR disk discussed in this thread:
http://forum.xda-developers.com/showthread.php?t=1360994
the file itself is here:
http://forum.xda-developers.com/attachment.php?attachmentid=806433&d=1323121269
unzip the file and then write the .img file to an sdcard with your disk imaging tool of choice (dd in linux or win32 disk imager are two I use)
Once you've imaged the SD card, copy in these two zipfiles - leave them zipped:
http://www.mediafire.com/?ig75l5b9c24e7q6
http://www.mediafire.com/?2tfitzt97qqfaw7
Apply 1 of 2, then reboot, then
Apply 2 of 2
then remove your SD card and reboot. Although I have not gotten all the commands to run out of a single zipfile, Zydraka noticed, I think correctly, that you can run first the one and then the second without needing to reboot in between. I have done it that way successfully.
I tried putting all commands (copying the files, then setting permissions) into one file and the rooting process aborted in an ugly way. I ultimately needed to reimage the device to restore the oddly hosed /rom partition. After reimaging I was able to root successfully by running the two clockwork scripts back to back without a reboot.
A (very brief) guide to the CWR interface, for those who don't know it:
You will know your card is made correctly when you put it in your device and power on, and you see a clockwork gear nibbling at a nook N. Be patient while CWR loads; you will get to a screen with selectable menu choices.
Navigate up and down with the righthand buttons; navigate back with the lefthand upper button; choose an item or run a command using the raised n button.
Navigate down to "install zip file from sdcard" and hit N
Hit N again to "Choose Zip File from SDcard"
Navigate down to the first zip (labeled 1 of 2) and hit the n button
navigate to "yes - install"
hit the N button
once the first script is done, use the N button to navigate to and apply zip 2 of 2.
navigate back to the reboot menu using the lefthand side buttons. Once you are at the reboot menu item, you can pull the card, then reboot.
I used a 256 meg sdcard I had in the house for making the CWR disk. I find that to be a very convenient size for these disks - big enough to put a few files onto, not so big I wish I hadn't set it up as a CWR disk.
Thanks roustabout! It works great and it was super easy to do! I just got done installing a bunch of apps from Amazon.
Update: I just posted a tutorial with a video for noobs on my blog.
One thing to note, I didn't do the reboot that you mention in between the 1 and 2 packages and everything worked fine. I just installed 2 right after 1 and haven't had any problems.
Thanks for this, rooted last night everything is as it should be, the only issue I've run into is that I can't seem to install the Kindle app. It's not in the amazon market place, I tried backing up the APK from another device via EStrong and transferring the apk to the microSD, and I get a parsing file error. Any tips?
I have not been able to get Tasker to install yet, either.
One thing which sometimes works where other approaches fail (if you have the .apk file) is to ssh into your device (I use quicksshd) and log in as root, then cd to the directory the APK was copied to and issue the command
pm install blah-blah.apk
I have not yet tried that with Tasker, but it may also help with the Kindle app? I did need to do it for one of the apps I use, although I can't recall which one.
Edit: the 3.1 kindle app Zydraka points out works for me as well.
By default, the Kindle app is pretty unusable, very slow page turns. But by using the gesture-enabled screen refresh hack, it's very useable. (I found that using the no gesture version led to lots of apps just ignoring the hack's presence. I think Renate has a way around that, but I haven't read up on it.)
http://forum.xda-developers.com/showthread.php?p=22800284#post22800284
I got Tasker to install, but needed first to copy in the Maps jar and xml (to framework and permissions respectively) reboot and install via ssh - it might have worked just to reboot.
Since others may want Tasker available, putting the maps.jar and maps.xml files into the tinynooter is trivial, and I'll probably get to it soon.
I found that the older version of the Kindle app works, version 3.1.0.30. There's a donwload for it at Android Freeware. http://www.freewarelovers.com/android/app/kindle
So, after this, will the glowlight work in all apps? I need to make sure that, moon+ reader and EZpdf will glow in the dark, before I purchase the new nook.
thanks.
The glowlight seems to work in all apps. I'm not clear on how exactly it's turned on and off; it might be possible to have an app that uses a long press on the N button for something else, and that might interfere, but so far it works fine in the launcher, in the Kindle reader, in fbreader, in Newsrob (that I know I've tested.) even if you had an app that was doing something funny with that long press, you ought to be able to turn it on from the settings menu that comes up on a short press.
Once the glowlight is on, it seems to stay on until your screen goes to sleep, regardless of what applications you may also be using.
This is part of why I didn't get into the boot environment at all in this approach - I knew from manual rooting that I didn't have to change out uRamdisk so I decided to leave it all alone.
Thanks for tinynoot! It's working well for me, and glowlight behaves normally.
roustabout said:
I just uploaded tiny noot, a very minimal root tool for the NST glowworm. I think it would probably also work for the simple touch, but I've lent mine out and cannot test it to confirm.
I am basically a cobbler here; many thanks to GabrialD, DeanG and the folks with the minimal touch root tools, which this is based on - and of course to mali100 and the CWR team for getting that on the Touch and Glowworm. Everything below is put together with parts from those projects using what I've learned at XDA and from Dean's nook color repartitioning scripts.
They make it possible for someone like me to knock out a package that's a little more convenient to work from than booting noogie and manually copying in files.
I am using the clockwork recovery zip installation mode for copying in the minimal set of files - I'm not trying to support the google apps or the many interesting screen refresh hacks.
I am not including a modified uRamdisk - the stock uRamdisk supports ADB, and you can get root via adb wireless simply by typing su, so I chose to leave well enough alone.
GabrialD has already released a modified uRamdisk for the glowworm (to support root by default as well as the light) but since stock works for my purposes, I'm not using the modified one.
What it does include:
su and busybox
nook color tools in /system, so that nonmarket apps can be installed
adb wireless
ADW launcher
Amazon appstore, so there's at least once source of "easy" apps
Button Savior
Nook Touch Tools
Supermanager and the Busybox updater interface
The install process is three steps. Four if you decide - and you should - to make a backup of your device before you start. (that process is: make the noogie disk. boot from noogie. connect to your computer. dump the NSTG or NST using dd or another disk imaging tool, and is described in more detail with tips for lots of different operating systems at http://forum.xda-developers.com/showthread.php?t=1142983 That backup will let you restore your entire device to a known working configuration.
Download mali100's nook touch CWR disk discussed in this thread:
http://forum.xda-developers.com/showthread.php?t=1360994
the file itself is here:
http://forum.xda-developers.com/attachment.php?attachmentid=806433&d=1323121269
unzip the file and then write the .img file to an sdcard with your disk imaging tool of choice (dd in linux or win32 disk imager are two I use)
Once you've imaged the SD card, copy in these two zipfiles - leave them zipped:
http://www.mediafire.com/?ig75l5b9c24e7q6
http://www.mediafire.com/?2tfitzt97qqfaw7
Apply 1 of 2, then reboot, then
Apply 2 of 2
then remove your SD card and reboot. Although I have not gotten all the commands to run out of a single zipfile, Zydraka noticed, I think correctly, that you can run first the one and then the second without needing to reboot in between. I have done it that way successfully.
I tried putting all commands (copying the files, then setting permissions) into one file and the rooting process aborted in an ugly way. I ultimately needed to reimage the device to restore the oddly hosed /rom partition. After reimaging I was able to root successfully by running the two clockwork scripts back to back without a reboot.
A (very brief) guide to the CWR interface, for those who don't know it:
You will know your card is made correctly when you put it in your device and power on, and you see a clockwork gear nibbling at a nook N. Be patient while CWR loads; you will get to a screen with selectable menu choices.
Navigate up and down with the righthand buttons; navigate back with the lefthand upper button; choose an item or run a command using the raised n button.
Navigate down to "install zip file from sdcard" and hit N
Hit N again to "Choose Zip File from SDcard"
Navigate down to the first zip (labeled 1 of 2) and hit the n button
navigate to "yes - install"
hit the N button
once the first script is done, use the N button to navigate to and apply zip 2 of 2.
navigate back to the reboot menu using the lefthand side buttons. Once you are at the reboot menu item, you can pull the card, then reboot.
I used a 256 meg sdcard I had in the house for making the CWR disk. I find that to be a very convenient size for these disks - big enough to put a few files onto, not so big I wish I hadn't set it up as a CWR disk.
Click to expand...
Click to collapse
You know, it should be nice if before using the packages other people create, for your own project, you asked them for permission to use them, if not, at least create your own scripts.....
Yes I'm refering to me.... thats not cool.
Anyway, the two step process is not necessary here, thats just for preventing some Gapps database corruption, you edited that code away allready and there are no Gapps installed, so add the code to correct the permissions on the first zip, and everything should work fine, no need to rm dalvik either if you arent modifying framework.jar, etc, it should also speed the first boot time.
I apologize - this was intended to be a quick hack and largely for my own use (as I was testing stuff on both my and my girlfriend's glowworms) but I realized there were a lot of folks trying to root their gw's manually. I thought it worked well enough to share.
I didn't intend to present it as original and if I appeared to I apologize.
Say the word and I will yank the thread outright, and I would have no objection to your asking the mods to do so, either.
roustabout said:
I apologize - this was intended to be a quick hack and largely for my own use (as I was testing stuff on both my and my girlfriend's glowworms) but I realized there were a lot of folks trying to root their gw's manually. I thought it worked well enough to share.
I didn't intend to present it as original and if I appeared to I apologize.
Say the word and I will yank the thread outright, and I would have no objection to your asking the mods to do so, either.
Click to expand...
Click to collapse
Don't worry, just stating that before creating a thread with others people work, you should ask them.
Everything is fine, It didn't even pass my mind the idea of reporting it, we are a small niche community, active members must be praised, so dont worry, and I encorage you to keep deving ^^, just that before using other peoples work and starting a thread with it, ask them for permission, no one is gonna deny it and it's the kind way of doing things .
I'm planning to get my hands on a Glow tonight, so over the weekend I should be able to get together a full Nooter for it.
tiny noot - also works for older NST
Just so folks know, I've confirmed that the tinynoot rooter also works on the NST running 1.1.2 firmware.
It will probably work on earlier firmware also, since it is not replacing uRamdisk or framework files.
Are Supermanager and the Busybox Updater supposed to work? Supermanager crashes back to home, and Busybox won't install.
Did you apply both files, and is there an sd card in your device? I just tested the busybox updater and was able to get it to update the installed busybox. It requires that you have an sdcard inserted to work - I remember being puzzled by that the first time I tried using it on a device.
supermanager is crashing. I hadn't tried running it on the device before, and hadn't noticed that.
Looking at logcat, yes, supermanager's crashing in the background quite a bit. It seems to be looking for things which are not available, for instance, a dialer, and erroring out when it can't find them.
roustabout said:
[...] supermanager is crashing. I hadn't tried running it on the device before, and hadn't noticed that.
Click to expand...
Click to collapse
Supermanager has always been a problem, at least for me, using TouchNooter. I believe it's intended to provide file manager capability, particularly for installing APKs on uSD. Once I get Market (Play Store) access, reinstalling supermanager fixes the problem. At that point, I don't need it anymore.
I've always had to work around this when rooting my Touch devices. I'd suggest a basic file manager be provided instead for Day 1.
I'm rooted with tinynoot. Recently I've been experiencing excessive battery drain. I'm eliminating apps I'd installed to if that helps. Wondering if anyone has experience with apps that are problematic in that regard? Dropbox? Amazon Appstore? Facebook? 1Mobile Market? I assume nothing that was provided by default with tinynoot. Thanks.
Hi Glowco,
I'd suggest installing task management apps to get a view of what is actually running (not all processes relate to an installed app icon that you can uninstall). I use Advanced Task Manager to view running apps, and Autorun Manager to control what processes start up at boot time.
Ian
Thanks, I'll keep that in mind. In the meantime, as an experiment I uninstalled several apps including Amazon Appstore, 1Mobile Market, FB, and Wireless ADB. Good result - my battery charge hasn't decreased in an hour and a half. If I decide I miss them I can try adding them back and use your method.
That's good news!
I'd suggest that Wireless ADB is not to blame, since it does not stay resident once it's closed and in any case does nothing until you click the big red button
Of the others, I have Amazon Marketplace installed and I don't experience any battery issues (I'm Glownooted not Tinynooted but don't think that's relevant in this discussion), but I can't speak for the other two apps. If I were paranoid (and I am! ) I would point at Facebook, since it's purpose is marketing and wants to follow your every move
Ian
Improve your One X multi-tasking using this simple and quick script!
User Feedback from this script:
"Nubzori: Thank you so much. After 10mins of testing, loaded bunch of apps, news, twitter, pulse, xda, chrome, clock, task manager, none of these refreshed"
Note: this script only works on roms that support init.d, it's been brought to my attention that init.d is not supported on some stock roms/kernels although it must be said; Why the hell would anyone want a stock rom??
UPDATE 15/06/12 - Thanks to Orical who has advised me this link here is a solution to those having problems with getting init.d scripts to work. This basically gives you the ability to enable init.d scripts in any rom!!!
Steps to installing script - EASIEST METHOD
1. Download this script of your choice and transfer to your phone (using USB cable or download direct to your phone or AIRDROID or whatever)
2. Rename from multitasking.txt to just multitasking (without any extensions) and place this in your /etc/init.d/ or system/etc/init.d (if you cannot see this, make sure your es file explorer is showing hidden files and folders which can be changed within the settings of es file explorer, also you need to make sure you go up to root directory which is again enabled within es file explorer)
3. You must be rooted to access this folder (make sure you set es file explorer to go up to root directory). These scripts alter the minfree values in your lowmemorykiller system module.
4. Once you have moved script file to init.d to mark as executable by clicking on script and setting permissions as executeable within es file explorer.
5. OR Just open the file and you can find several options, one you need is 'linux handler', choose that and next select execute option. It will now executed automatically.
Alternative method of installing script:
adb remount
adb push C:\Users\your name here\Desktop\multitaskingxtremextra system/etc/init.d
adb shell
chmod 644 system/etc/init.d/multitaskingxtremextra
adb reboot
From what I know of, the android system generally handles around about 5/6 apps in memory without any problems, any more apps and then you start getting refreshes, I've tested using LBE firewall (running as service), battery status, firefox with multible tabs open, gmail, messaging, gallery and the sense launcher (as this is an app as well). Any more and it starts recycling ram for some reason and you will get refresh on some apps (depends on which app)
Troubleshooting:
Can't find init.d, here is the answer:
Use the root explorer to copy it to system/etc/init.d
Just open the file and you can find several options, one you need is 'linux handler', choose that and next select execute option. It will now executed automatically.
The default values for the One X are:
STOCK ONE X TEGRA:
8192, 10240, 12288, 14336, 16384, 20480
My multitasking script alters this to:
2560,4096,6144,7680,8704,10240
My multitaskingxtreme script alters values to:
1536,2048,3584,5120,8704,10240
My multitaskingxtremeextra has the xtreme script as well as:
Dirtybackgroundratio 70
Dirty Ratio 90
VFScachepressure 10
And kill oom allocating task 1
my multitaskingultimate has the same as multitaskingextremeextra except the minfree values are more aggressive for the best multi tasking you can get on the one x
512,1024,1280,2048,3072,4096 - this is the best settings I have used for multitasking and have run 6/7 apps and some cases more without refreshing on a full SENSE 4 rom which is impressive if you ask me, the combination of apps where Firefox, Chrome, Gallery, Youtube, Dialer, etc.
You should notice that most apps will not reload when multitasking (except if you are intense gaming such as shadowgun or something intense like riptide), in some cases too many apps running will cause refresh if multi tasking, take note in the fact that htc senses software uses up alot of ram leaving little free as it is for other apps.
If you want to return to default values, simply delete the script from your init.d and reboot your android phone
If this has helped you please hit the Thanks button rather than post thanks!!
My test was using chrome beta, ebay, gallery, file explorer, ebookdroid, whatsapp, gmail, text message and all did not refresh whilst using,
I will also experiment with different scripts & methods and post any alternatives that may further improve multi tasking on the one x.
NOTE: I hold no responsibility should you damage your phone in anyway using this script. However damage is unlikely.
Information:
min free kbytes (vm.min_free_kbytes)
This is used to force the Linux VM to keep a minimum number of kilobytes free. The VM uses this number to compute a pages_min value for each lowmem zone in the system. Each lowmem zone gets a number of reserved free pages based proportionally on its size. Default is 2048kb.
dirty ratio (vm.dirty_ratio) and dirty background ratio (vm.dirty_background_ratio)
This controls how often the kernel writes data to "disk" (in our case the internal microSD system card, not the removable microSD card). When your apps write data to disk, Linux actually doesn't write the data out to the disk right away, it actually writes the stuff to system memory and the kernel handles when and how the data is actually going to be flushed to the disk. These values represent a percentage, the higher the percentage, the longer it waits to flush, the lower the percentage, the more often flushes will occur. Now remember, we are dealing with solid state storage, not the traditional disk platter and spindle. So we are actually able to delay flushes a little longer with solid state versus a traditional hard drive disk.
VFS Cache Pressure (vm.vfs_cache_pressure)
Now here is where it gets interesting! File system cache (dentry/inode) is really more important than the block cache above in dirty ratio and dirty background ratio, so we really want the kernel to use up much more of the RAM for file system cache, this will increas the performance of the system without sacrificing performance at the application level. The default value is 100, as a percentage, and what you want to do is lower the value to tell the kernel to favor the file system cache and not drop them aggressively.
oom allocating task (vm.oom_kill_allocating_task)(enable or disable, generally in Linux this value is either a "1" or a "0," representing as on or off.)
This enables or disables killing the OOM-triggering task in out-of-memory (oom) situations. If this is set to zero, or disabled, the OOM killer will scan through the entire task list and select a task based on heuristics to kill. This normally selects a rogue memory-hogging task that frees up a large amount of memory when killed. If this is set to non-zero, or enabled, the OOM killer simply kills the task that triggered the out-of-memory condition. This avoids the expensive task list scan, which can take mass amounts of time and "hang" or freeze the system.
This thread would like to thank the following:
rayford85 - for pointing out #!sysbin in script which i stupidly left out and alternative installation method
Nubzuri - for pointing out to those who could not find init.d
rycon33 - for pointing out that init.d not supported on some stock kernels/roms
My MODS
----------------------------------------------------
[MOD] Improve Multi-tasking on HTC One X
----------------------------------------------------
[Currently owned devices]
- HTC One X Tegra 3
- Motorola Xoom
- HTC Sensation
- HTC Desire HD
Thanks a lot, much better multitasking now
Sent from my HTC One X using XDA
i thought it's about time we got something like this and decided to bother modifying the values, it is a noticeable difference!
Would this be the same or similar script to the one in this thread?
http://forum.xda-developers.com/showpost.php?p=26437514&postcount=93
My phone is rooted but I can't find the init.d folder. I have \etc but no init.d. Should I create the folder or just place it in etc?
nope its my own script, for some reason the op hasn't replied back yet about his script so i couldnt test it and decided to make my own, so far it is better than the original minfree on the htc one x tegra 3,
also you need to be using es file explorer make sure you can view all files/folders (including hidden) in settings of es file explorer
Does the phone need to be rooted ?
I downloaded es file explorer and set the hidden file/folder option. I still can't find /etc/init.d
I can see other hidden files and folders in other directories but can't locate init.d
Any ideas?
thanks for this
Thanks for your contribution .
@silentkill @john9 please hit the thanks button and you are welcome,
creepinchi: make sure you have access to your root directory, follow my instructions above in the first post, you need to be able to go up to root directory then you will see etc folder then go into init.d folder then place script here
I don't want to root my machine yet, is it possible to modify the files the other way?
don't you need to make the script executable chmod +X ?
yes executable, sorry forgot to mention this, will update main post
quick question if you/i made this as a cwm zip would you need to Mark it as executable In es?
Sent from my HTC One X using xda premium
I'm not sure I've not really tried, why don't you give it a go
Thanks! Only a quick test but seems much better on my One X. Chrome Beta has gone from reloading every time I dared to leave it to only reloading if I open 5 or so apps. Great job, makes the shiny sense multitasking screenshots seem a bit less silly now
mox123 said:
I'm not sure I've not really tried, why don't you give it a go
Click to expand...
Click to collapse
Will do when I get back on my pc.
Sent from my HTC One X using xda premium
P.m' d you with values.
I am rooted and have show hidden files enabled but still can't find the file. Is this only for the tegra 3 version?
I have been solidly using Gnabo V8 versions along with modded Boeffla kernels for stock touchwiz. During my experiances with mixing the two to get the best performance and usability, I have found some tricks to make a solid and very usable custom ROM that most WIFI only tablet users may find overall the best out there.
He key is what packages to use and how to configure.
Step one is removing unconfigureable or hidden settings that you cannot wipe. This makes sure what ever customizations you have done are gone and will not mess with how the installs function.
My way was to perform a clean for new ROM in Philz, and install a stock 4.4.2 ROM. When rebooting, power off by holding down the power key, and when powered off remove the back cover and disconnect the battery connector for 2 minutes. Reconnect and allow the stock ROM to finish installation setup. Make sure Bluetooth, wifi, miracast and other functions operate as they should. Once verified everything is functional, reboot into recovery and perform a full wipe for new ROM install, clear both caches, and install the Gnabo V8 version you have picked. DO NOT... Repeat do not install any other patches or additions outside of applying SU from Philz recovery and loading a SUupdate.zip. Reboot and perform the installation setup and let the tablet set for 15 minutes once the setup has placed you at the home screen.
You now have a clean base to start with further updating to Boeffla 2.6 Kernel and other minor patches to the apps that have been placed into the system.
Reboot into recovery and apply the Boeffla 2.6 kernel, and TiBackup.zip.
Once booted, remove the old Civato kernel utility and what ever apps you find useless. To add to your list of app removal for replacement... Video, Video Player, Music Sharing, Voice Note, Multimedia Service Layer, S Voice, and S Finder.
I will post all the apps and priv-apps in zipped folders for manual installation. They will fix some issues that were left uncorrected. Plus add features lost in Video playback, like play next, and sharing.
As for applying patches and Civato odexing tool, they cannot be installed through the recovery installer as they apply improper permissions and framework gets broken. Boeffla kernel doesn't work well with the framework.jar patch. Plus the 2.6 kernel has the Bluetooth fix built in. I will also include zipped folders of the patches to manually apply.
Along with the patch apks, I will include a zipped lib file collection to add further inhancements. One is to allow cropping in Photo Studio and a nicer way to clip videos.
Optional zipped folders to allow odexing, and fixed power off charging images.
Sounds like a lot, but with the zips being easy to place in a manually created system folder, all you need to do is run a few shell commands to allow 644 permissions and root users and owners. Then cut and paste into their respective folders.
Only TwFramework, Bluetooth.apk and Settings Provider will need to be copied over. The TwFramework is to remove the black bar on top, and Bluetooth.apk and secsettings.apk which fixes wallpaper functionality. Studdering is fixed by the kernel, and may not need bluetooth.apk replacement.
Right now i am messing with a few different Video.apk files for their stability and function, in wanting as many enhanced options as possible without FC issues.
Will start posting my zip files and instructions for permissions and using the odexing tool.
See post #2
Zip files and their permissions
The zipped bin folder has a single file. It should have 755 and 0 root 2000 shell
The zipped OdexerTool folder files should have 755 and 0 root 0 root.
Create the folder OdexerTool with 755 and 0 root 0 root as well.
The remaining zipped folder's files should have 644 and 0 root 0 root.
You will need to change face extension to zip or allow overide of detection by open as.
Will add more zipped folders... app, priv-app and lib in separate posts due to limitations on posting a reply.
PRIV-APP & Native Language files for Keyboard
All of the RAR folder's files should have 644 and 0 root 0 root, and are to be cut and pasted into their respective system folders.
Voice files for native languages.
The RAR files cover most of Europe, and outside countries, along with America, Canada, and Brazil.
Just find your local folder and set the permissions to have 755 and 0 root 0 root, and cut and paste into VODB. Inside the folder all files should be set to have 644 and 0 root 0 root permissions.
APP files for added features and patching.
Ok, I selected the best option for video... it has two looks. At and below a dpi setting of 197 it is white, and above it is dark. So most may like not being stuck one way or another.
Just set the permissions to 644 and 0 root 0 root, and cut in paste into the system app folder after removing video and other apps. That my not be over written.
LIBS for added 5 features and imaging
These are not required but are needed for using Studio and some S5 apps and or changing to another UI that supports S5 enhancements. There is more Stagefrieght capabilities as well.
You will need some of the apps and priv-apps to find the libs useful.
TWEAKS
Please note my attached build.prop is modified to use a tab 8.4 build and has a mix of system tweaks.
I have found a sweet spot with the Boeffla kernel utility... it gives great speed improvements without being tempermental.
Though, since I have been messing around with various system apk swaps... some small issues during tests were attibuted with the apk not playing well with the Gnabo ROM, not the kernel.
Since I have stablized my tweaking, the combination of ROM and kernel are stable enough to keep my tweaks permanent.
I set my governor to PegasusPlus with both internal and external memory to row. I use x633 64GB SD card, so slower speed types my need Bfq. I am able to get 2x to 4x the throughput with row row configuration. Noop performed the best for me, but was unstable under heavy loads, so I kept row as my safe optimal setting, running 256k for intenal cache and 2048k for my 64GB external memory.
CPU has been adjusted to 100mhz min to 1920mhz max with a -.025mv undervolt. I can run -.050mv undervolt but I find at heavy cpu usage it becomes unstable.
I set my GPU in a linear adjustment with the last 3 settings to push 700mhz with no undervolting.
Sound settings were minimal... only adjusted speaker gains to 60, as anything above caused distortion. Kept equalizer off and set mic gains to 31, with privacy mode enabled and DAC direct.
Display and LED, I turned off status and kept it disabled.
Misc 1, I set my power to 1800ma and ignore unstable power.
Tcp settings to LP.
Kernel delay is set to 0
Permissive, busybox and frandom set as enabled.
You will need to start busybox installer and remove installed busybox to run busybox from the kernel.
Samsung updates...
I usually don't bother with Samsung's gapps on updates, but I found that allowing quickconnect.apk to update made it worth while. I was familiar with Quick Connect when I used my personally modded stock 4.4.2 ROM with S3 UI and a bunch of S5 apps and libs, with a S2 Diamond ROM secsettings.apk. It was great but just felt too overly stretched to fit S5 apps proper. At the time I was happy but I could not tweak for best performance, as Boeffla Kernel was not available and stuck with Civato's kernel. I got use to Quick Connect being fully optioned, and it seems nobody had bothered using Quick Connect v1.6, so they would not know any different.
I tried a few tricks to get the update, and the best one was to use a stock untouched QuickConnect.apk, QuickConnect.odex, QuickConnectInteraction.apk and QuickConnectInteraction.odex. You will need to delete the data and remove them both before manually populating the files. Though the catch to making QuickConnect work is to only do QuickConnect files first and reboot, then do the QuickConnectInteraction files and reboot. Else QuickConnect will not work.
Oh another thing one must do... edit the system.db file and add QuickConnect in the list for it to show in the quick settings list.
The nice thing about the newer version of QuickConnect, is that it allows grouping your favorites on top of scanned devices, and you can relabel and assign images for personalization. The main reason I use QuickConnect is that I can eliminate two settings... Miracast and Bluetooth, and have other settings available without need to expand my quick settings list. QuickConnect also does a better job at mirracast functionality, as it disconnects without the bloody delay.
SFinder v1.100
After some more testings with various Sfinders... I found one that combines the S5 look and feel with tablet interface, and its speedy to boot.
Not sure if Samsung Content Agent helps, as it is an app I loaded in recently. Some SFinder apps use it and others don't.
I think my battery consumption has decreased since updating my Samsung apps. I get just about the same battery time with 4.4.2 as I do with my 4.2.2, which is a first. 11% per hour with miracasting while streaming is pretty good IMO.
If anyone is up to replacing their SFinder, here is v1.100