Making G3 work with nfs and cifs - G3 Q&A, Help & Troubleshooting

Making G3 work with nfs and cifs - G3 Q&A, Help & Troubleshooting

Dear All,
I´ve been researching this subject, and found a couple of threads pointing me in the right direction. In particular this post about mounting cifs on LG G2 was useful:
http://forum.xda-developers.com/showpost.php?p=49291439&postcount=29
I did the following:
I found an Ubuntu 12.04 image and ran it in my vmware, got latest NDK and the Marshmallow Kernel from LG´s website. For the defconfig, there are plenty of configs for G3 so I chose a random and rather small one (1 kb instead of the others that are typically around 20 kb) and followed the steps. When I came to the .config screen I did not find any option to enable cifs or nfs support, so I did the whole thing over again for G2 - just to see if that´d give me the option although I wouldn´t be able to use it for the G3. I found a Jellybean kernel on Lgs website for G2, assuming that´s what was used back in 2013 when that thread was started, and NDK 8d which was the current version back then. I found a small config file there as well for the defconfig, and got into the menu again. Other options it seems, but still none for cifs and nfs. I then tried to add some config lines into the defconfig for nfs, which I found by googling but with the same result.
Should the kernel have some support for nfs in itself, and why would I at least not get it in the menu when trying to do it for G2, like the guy in the other thread managed to do it?
FYI, I love what you can do with ES Explorer and similar apps, but I´m after mounting nfs and cifs - not accessing them via another app.
Hoping for advise - thanks in advance!

Allright, this took me a while but I got it all sorted out!
A brief overview of what I´ve been through:
I found out that I needed a 64-bit Ubuntu, hence got the latest 16.04 and set it up in a VMWare. I tried my best to build my kernel using NDK, but constantly ran into issues with missing files and a whole lot more. I then decided to target cyanogenmod, who has a guide which in detail explains what to do.
The Cyanogen method uses SDK instead of NDK, and requires you to have a branch of Android on your phone already installed, similar to the one you´re building for.
Again I had various issues untill I tried with the 12.1 snapshot (Lollipop), and finally I could build my Rom. I enabled all cifs options under File Systems/Network File systems in the menuconfig, and all with regards to NFS client, except for NFS v4 which also created some problems. You´ll need to have insertion of modules enabled as well from menuconfig.
After that I was able to have mount manager (an old app that you need to google for, market does not have it anymore) do the job. You´ll need to look for dns_resolver.ko and cifs.ko in your android environment under Ubuntu, and put these files on for instance your sdcard on your phone, where you´ll tell Mount Manager that they´re located. They need to be loaded in the same order as they´re mentioned above.
Your mounts are going to show up as files and not folders, if you don´t do the following from a terminal under android:
$ setenforce permissive
NFS I´ve not yet been succesful with, not least because my firewall blocks NFS regardless of whether if I open the right ports, allow all traffic on the hanewin (NFS mounting system) exe files and so on. So at the moment I start looking into getting the job done with NFS, I also need to get another firewall.
Anyway, on this particular Android build, I got a terrible connection speed, but after googling this for a day or two, the fix for me was to change the channel of my 5ghz wifi to 48 on the router. Then it went from 10 mbit to 120 mbit speed!
Still samba(cifs) is slow, which is not what you want with UHD high kbps rate clips, so I´m researching what can be tweaked here.
Anyway, cifs is working, and I thought I´d share this with you so others can learn from it. There´s alot of trial and error I´ve been doing, and if I can save others from having the headaches I had, I´ll be happy
PS: My phone is rooted, but we´re not even at the stage where I´ll be trying it at my phone yet.
PS: Mounting via shell is possible, but I couldn´t get this to work till I installed busybox. Also, for password protected shares, you´ll need to add the unc path.
Example:
busybox mount -o unc=\\\\192.168.178.11\\Movies,user=username,pass=password -t cifs none /storage/sdcard1/cifs/Movies
Doing this in Mount Manager is easy. Do what you would do anyway with setting the remote and local dirs, and add an option with "custom" where for the option name you type "unc" and the value will be "\\\\192.168.178.11\\Movies"
PPS: I figured that you get alot of glitches for VR videos (2880x1440) when using cifs, and I´m on a wifi with 160 Mbps here. I finally made it into getting NFS to work, and that works!
Here´s how:
Make sure you´ve turned root permissions on for adb and apps on the phone and adb into your phone, then:
su
setenforce permissive
insmod sunrpc.ko
insmod lockd.ko
insmod nfs_acl.ko
insmod nfs.ko
For the insmods, you need to point to where they are stored on your phone, obviously.
Now you can (example)
busybox mount -t nfs 192.168.178.11:/VR /storage/sdcard1/mnt/VR -o nfsvers=3,noatime,hard,nolock,rsize=65536,wsize=65536,udp,intr,async,ro
You´ll now have access to VR through /storage/sdcard1/mnt/VR!!
I tried this on both the 5ghz 160 (-200, depending on how close I am to the router) and on a powerline wifi giving me around 35 Mbit speed.
The last one did not work well, so you really need alot of speed.
One thing I struggled with was that I had stuttering after 4-5 minutes getting worse and worse. I found out that in developer options you can switch on awesomeplayer instead of the default one, which solves that problem.
I also found out that D855 (LG G3) is not a 2560x1440 (as it says in the specs) but 3200 x 1600 phone - under the screen settings, you can set the DPI to 640 and it works fine. Yes, this is really true - find a dpi calculator and check it out! I may be mistaken of course, let me know in that case. This gives you almost 39 % more pixel density, so alot more realism!
Have fun, and remember that all the things that are easy to google, setting up ubuntu, finding cyanogenmod stuff, compiling etc is not mentioned here because this is not where you´ll hit your head against the wall. The things I´ve described are those where you really need to be spending time, as the information is rare and device specific since not that many people are dying to connect to an nfs server from android, and even less want to stream UHD clips to the phone
Btw, I´m using the app VRTV since it can be setup to be used with a cheap game pad that I got from aliexpress for EUR 8, so that you don´t need to take off your headset for anything - you can just fast forward, skip to next clip, adjust volume, recalibrate etc. from the game pad.
For headset I´m using one with the highest FOV outthere. It´s the Bobovr Z4, that´s very comfy to wear and even has builtin headphones. I got it for around 25 EUR, also on aliexpress.
If I did not already mention it, I use hanewin under win 10 for nfs server.
One very last thing: Your screen is going to dim after a few minutes, especially when inside a VR headset. This is due to LG´s very ungenerous threshold for when the phone is considered hot, and they´ve decided that the screen should be dimmed to keep it from going too hot. I tried various things.. an app called Lux, another one called Stay Awake, an app solely ment for getting rid of this behavour, and looked for ways to get inside of LG´s own hidden menu where you can get rid of the throttling.
None of it worked - the last two options related to that I´m not using a stockrom here.
Well, I´m happy to use cyanogenmod because the phone is much cooler with that, but since the phone´s so picky with what´s considered hot, it´s still a problem.
I found out that you can edit thermanager.xml in system/etc where you wanna set all values for backlight to 255. Make it look like this:
<control name="backlight">
<mitigation level="off"><value resource="backlight">255</value></mitigation>
<mitigation level="1"><value resource="backlight">255</value></mitigation>
<mitigation level="2"><value resource="backlight">255</value></mitigation>
<mitigation level="3"><value resource="backlight">255</value></mitigation>
<mitigation level="4"><value resource="backlight">255</value></mitigation>
<mitigation level="5"><value resource="backlight">255</value></mitigation>
<mitigation level="6"><value resource="backlight">255</value></mitigation>
<mitigation level="7"><value resource="backlight">255</value></mitigation>
<mitigation level="8"><value resource="backlight">255</value></mitigation>
<mitigation level="9"><value resource="backlight">255</value></mitigation>
And then reboot. I did a test for 20 mins playing a 180/SBS/2880x1440 video, and brightness is still where it should be - at the max!
In my temp monitor, the system temp is 47 C, so that´s fine. Back when I´d be using Marshmellow stock rom, the phone would shut down itself after 15 mins of doing the above at about 57 C.
Now, I cannot guarantee that this, or anything else suggested in this post will not damage your phone. If you want to be 100 % sure of no damages caused by any of this, simply don´t do any of it. IF you do it, it´s your own responsibility. None of this was tested for 3 months on 100000 phones, so I really can´t tell.
G3 is a great choice for a VR experience, since you can get it for EUR 270 - cheaper than any other phone with that resolution. I got mine for EUR 100 second hand, so as an alternative to GearVR, this is a very cheap way of achieving the same.

Related

mssmison did it!: CyanogenMod 5.07 test 3. for kaiser!

wifi working with patch.
http://forum.xda-developers.com/attachment.php?attachmentid=325161&d=1273647492
http://forum.xda-developers.com/showthread.php?t=679680

could someone resize it to 240x320 please? cant wait to try this

Heads up! New Kaiser Wifi update: http://forum.xda-developers.com/showpost.php?p=6456191&postcount=33
Old one replaced build.prop with wrong version. Reinstall and use the new Wifi update.
Also to get rid of android-rebooting-problems with GPS Test application do the following:
1. Start terminal emulator
2. su
3. cd system/lib/hw
4. rwsystem
5. rm sensors.msm7k.so
6. rosystem
7. exit
8. exit
9. restart phone

So how is it? I'm too lazy to install it.

Dukenukemx said:
So how is it? I'm too lazy to install it.
Click to expand...
Click to collapse
Seems like a really nice build. I'm using 320x428 with 144 dpi. A bit slow because I'm currently not running in NAND but I would expect it to perform quite well once I go back to running NAND again.
I haven't tested it very much yet as I'm doing some experiments in WinMO at the moment.

just tried
hey
i just downloaded this and i have to say im impressed about this.
as i love the eclair design and everything and the donut speed i have to say this is impressing because it is FAST! not as fast as donut but pretty much the same. that could be due to the 500 mHz OC but i just like that build.
just needs to be optimized a bit, maybe a few apps like astro and others
and as the developer has a new phone we need a new one.
But i have to say its awesome!
i love it already and just tried it for 9 min.
just the OC needs to be removed i noticed right now and is there any way to set another value for the screen sensebility because quiet often it does not react on a touch.
so keep updating this!
nick

nice rom but it chews through battery like crazy. With a full charge battery will drop from 99 to 75(battery fix removed OC and set 1400 value) with just a 10min phone call and a couple txts. I think what we need is a new kernel highly optimized for battery life using the latest patches. Judging from the name alone of the kernel its running right now 2.6.25-01051-gc362ac-dirty and the fact that 2.6.25 was released in jul 2008 i think theres room for tons for improvement.
Does anyone know how to adjust the microphone gain? my friends complain they cant hear me..

The wifi scan interval is set to 15 seconds by default in this release. That will have a negative effect on battery life if you are out of range of a known network and have wifi enabled. I'll put together an update to change this when time allows. I use 120 seconds myself.

kallt_kaffe said:
The wifi scan interval is set to 15 seconds by default in this release. That will have a negative effect on battery life if you are out of range of a known network and have wifi enabled. I'll put together an update to change this when time allows. I use 120 seconds myself.
Click to expand...
Click to collapse
Thanks to update.
It working good on Polaris.
Also i change interval to 180 and density to 120 in .prop

Here's an update that changes the wifi scan delay to 120 seconds and also (not tested yet) changes the model name from Vogue to Kaiser.

i'm still trying to figure out if it's possible, somehow, to flash an update.zip file (to be able to use the cyanogenmod skins) with the nomorootfs we're using, instead of converting the skins to metamorph format
does anyone know if it's possible or how to do it?

Can't get wifi to work with updates, which one should I need?

kallt_kaffe's works for me. If something isn't working like it should, power off the phone and remove the battery. Then hold down the power button to remove any remaining power left. Place batter back in and try again.
Also, make sure to always fix permissions when you apply updates, even for wifi.

Dukenukemx said:
kallt_kaffe's works for me. If something isn't working like it should, power off the phone and remove the battery. Then hold down the power button to remove any remaining power left. Place batter back in and try again.
Also, make sure to always fix permissions when you apply updates, even for wifi.
Click to expand...
Click to collapse
edit: how stupid can I be? I've bought another phone and forgot to add the mac adress.

Certainly think mod needs work. So far the battery meter is off, and all this time I thought it drained less power. A lot of pop ups to force close apps. A lot of apps are running that I don't use.
mssmison didn't say he was going to put any more effort into it either. Hopefully, someone will pick it up.

Dukenukemx said:
Certainly think mod needs work. So far the battery meter is off, and all this time I thought it drained less power.
Click to expand...
Click to collapse
Try deleting /data/system/batterystats.bin. That usually helps when the batterymeter has gone bad.
A lot of pop ups to force close apps. A lot of apps are running that I don't use.
Click to expand...
Click to collapse
Have you removed or renamed /lib/modules/hw/sensors.msm7k.so? After I removed that it runs very stable for me.

kallt_kaffe how do you do it?
I'm new to the androidinstall.tar method. I'm tyring to run from haret but it seems impossible.
You said you where experimenting with something in winmo, so that implies you're using haret? Are you running from haret?
When I try, Polymod, and Mssmission they don't show an install option, when I try myn and incubus I get it installed but I get no sound. It was actually your gps kernel that let me get things installed all other kernels i tried had non-functional dpads within the installer environment. Also, trying another kernel once installed didn't fix the sound issue.
Anyhow just let me know if you're using Haret. I wonder whats up with the sound and missing install option. I tried the install two different ways one with a 2gb fat32 partition, and then another attempt using three primary partitions 1.3gb fat32, 300mb ext, 300mb ext. All installers then would give me options beside's fat, but not all intallers would have an install option.. I'm using radio 1.71.09.01.eMo, model: kais100, os: wm6.5 (shifu v.3)

kallt_kaffe said:
Have you removed or renamed /lib/modules/hw/sensors.msm7k.so? After I removed that it runs very stable for me.
Click to expand...
Click to collapse
I try start Skyforce game, but it forceclose.
It can work after i added "sensors.sapphire.so" into /lib/modules/hw/

I've installed the cyanogenMod updater from the marketplace, but it can only find older versions, no experimental versions, whatever option I set in the program.Anyone?

Dukenukemx said:
Certainly think mod needs work. So far the battery meter is off, and all this time I thought it drained less power. A lot of pop ups to force close apps. A lot of apps are running that I don't use.
Click to expand...
Click to collapse
battery life has been fantastic for me on this build...
although I reverted back to 400mhz and got rid of compcache.
I am sure that OCing to 500 by default is draining the battery faster.
I would rather a usable phone than a fast one...(although it still seems very fast to me)

[[Speed Improvements]] Brainstorming & Testing Thread!!

Hey guys,
Seems there's a lot of ways you can improve the speed of Android in general. Some seem to be snakeoil... others, work quite well and there's proof to back it up.
I'm only interested in discussing the latter .
A lot of people have helped me gather a better understanding of Android (hyc, stinebd to name a few) in addition to a lot of Google searching. I am going to compile a list of what I have done, I would like to hear what you guys have done! Most app killer apps / app control will already be addressed, so those tools need not apply... I'm looking for real, permanent fixes here without adding more apps!
I am also trying to have topics that are easy working up to advanced. Obviously the more advanced topics are going to be harder to do. You've been warned.
So here's the disclaimer.
****DISCLAIMER****
Speed is as always relative. That basically means I don't want arguments about which build is faster. I want to argue about how to make every build faster .
Also, these tips should apply to any build, any device... they are pretty generic tips, but are obviously specific to Android, with some idiosyncrasies that apply to our port that wouldn't apply to native Android devices. Some is common sense, others are real ways to tear into the system. Hope you enjoy it!
Topic 1
Difficulty Easy - Apps/Widgets
I've noticed the number of widgets i have on my screens, or the number of apps that I have installed/are running in the background to greatly effect performance, in an obviously negative way.
Once I removed all the widgets (I only have the basic analog clock widget & the Google search widget on one desktop...) this seemed to improve general speed. One minor thing to check is if apps are set to auto/background sync. Only enable the ones you really want syncing, others just check manually.
On this same topic, replacing the launcher (the stock launcher in Android, Launcher2 is quite slow) can help immensely. I like ADW, but I've used LauncherPro in the past and it is good. Zeam also seems like a good launcher. I haven't used Go Launcher EX, I've heard good and bad things about it. Use what works best for you, try 'em all!
The last thing on this topic I would like to mention is animations. Settings -> Display -> Animation -> No animations can make the phone feel quite a bit snappier, obviously at the expense of the look/feel of the OS.
Topic 2
Difficulty Easy - Controlling app 'net Access
This leads me into the next topic, DroidWall. I've noticed that blocking apps from accessing the internet has been a very good thing - it's not so much a performance booster (although it probably does provide a little bump) it's mostly about battery life. Just be warned, if you block an app that is set to background sync, it will probably have very negative effects. Only disable an app's access to the internet with DroidWall after you've checked that app's background sync feature is disabled. I have a few apps allowed in DroidWall, and the rest are blocked. You can "whitelist" everything and check apps you want to block, or "blacklist" everything and check the apps you want to allow. It's a little annoying to remember to enable/disable DroidWall (I use the DroidWall widget to enable/disable it globally) but if you do, it is much better - you have complete control over how apps access the 'net on your device. It is available on the Market.
Topic 3
Difficulty Moderate - SD cache/readahead tweaking
The only reason I'm calling this one 'moderate' is the number of choices you have for settings for this... It's basically telling the SD card how much to hold on to or... read "ahead" if you will . This was turned way up in FRX07, (from 256kb to 2048kb or 2mb...) and I think this might be the source of a lot of the complaints of 'mini-resets' if you will where the boot animation is suddenly seen after a long system hang...
So some cards will work better with a larger setting - I've heard some with spankin new C6 cards that said 3072kb or 3mb was a good setting. Others have found a sweet spot at 256kb or 1024kb (1mb).
There are two ways of doing this - you can hack the init in the rootfs and adjust the setting manually, or be lazy like me and use SD Booster (from the Market). Adjusts the same settings, and they are applied immediately!
I would like to find a "sweet spot" - a good default if you will. Can folks test out 512kb and 1024kb, see if you have any more mini-resets within Android or any other slowness, etc... Obviously this isn't a cure-all for the slowness or the mini-resets, what we're looking to do is mitigate the effects. So let's focus on that, thanks!
Topic 4
Difficulty Moderate - Overclocking
Overclocking is obviously one relatively easy way to improve the speed of Android. In your startup.txt, add a line
Code:
acpuclock.oc_freq_khz=710400
for example to overclock to 710.4mhz. How did I find this value? I actually put in 714000, but if you look at dmesg near the beginning you'll see "ACPU running at ..." - that's what clock is the actual maximum. It goes in 19.2khz increments.
Feel free to experiment with how high your phone can go, just be warned that the higher you go the potential for failure goes up as well . Phone shouldn't blow up, but it might not work correctly or at all. Rebooting and scaling it back will fix it.
Here's the full *example* startup.txt:
Code:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmvkeyb_toggle=off gsensor_axis=2,1,3 pm.sleep_mode=1 physkeyboard=rhod400 acpuclock.oc_freq_khz=710400"
boot
You can put the command anywhere in the cmdline section, just make sure it's between the quotes and at least one space between each command.
Topic 5
Difficulty Advanced - How Android Manages Memory/apps
Ok, I'm going to take two approaches to this. The first, is the full explanation on how Android manages memory.
Please feel free to read the post I originally read that inspired me to start looking at this stuff - How to configure Android's *internal* taskkiller. It was very helpful for me to grasp how Android manages applications. This is the reason why application killers are not a good thing...
If you want to do it manually, Starfox suggests:
Code:
echo "1536,3072,8192,10240,12288,20480" > /sys/module/lowmemorykiller/parameters/minfree
To try to do these commands, adb is very useful. Once you get adb shell working, then you just need to "su" (provides 'super user' privileges (root)) and put in the echo command above ^^.
I had another user (thanks icevapor) suggest this script -
[Script] V6 SuperCharger! HTK & BulletProof Launchers! The ONLY Android MEMORY FIXER!
I tried it myself, and it works very well. This thread is a little overwhelming, but the jist of it is this:
Install Script Manager (on the Market)
Run the V6 SuperCharger script. I use "Aggressive 1 Settings" (#2) and then I use the OOM Grouping Fixes & "Hard to Kill" launcher (#17)
Point Script Manager to run /data/99SuperCharger.sh to run as root & on boot. This will ensure the tweaks are reapplied after a reboot.
Topic 6
Difficulty Advanced - Managing Apps that auto-start on boot
This is one of the most annoying things in Android. When you have no apps installed, it seems very fast. Then you install apps, and you never seem to get that original speed back... Now you can!
This is kind of difficult to do, I am still getting the hang of it... but here goes. All credit goes to hyc, his original post.
The basic idea here is you run a logcat (adb logcat is easiest here, or you can use GetLogs to pull logcat...) Look in this log for "for broadcast" and find apps that start on boot. For example,
Code:
Line 41: I/ActivityManager( 1394): Start proc nextapp.systempanel for broadcast nextapp.systempanel/.monitorservice.BootReceiver: pid=1752 uid=10060 gids={3003, 1015}
Notice there are two sides of the "for broadcast". The name of the package (nextapp.systempanel) and the name of the service, "nextapp.systempanel/.monitorservice.BootReceive". I made the mistake of disabling the app (the left side). Do not do this, you want to disable the right side!
So in the shell,
Code:
pm disable nextapp.systempanel/.monitorservice.BootReceive
This will be persistent across boots, it will go with your data.img.
Obviously this was just one example of an app to disable. So long as you disable the right side (after the 'for broadcast') you shouldn't disable anything that will cause a serious problem. The apps should still work, but for example if you disable Google Voice you won't get messages until you open the app. So think about that... You disable Titanium Backup schedules.BootReceiver, the schedules for Titanium Backup (if you have any) won't run. Stuff like that. Disable calendar, you won't get calendar events... Disable clock no alarms. Get it? Good. I have been rebooting several times, and I keep checking what is set to start on boot. I'm not quite happy with it yet, but there's some things I'm leery of disabling. Just be wary, if you do disable something and don't like it - just pm enable <whatever you disabled>.
Now experiment away! The one caveat is if you do break something with pm disable (and it's serious) you might get a failure to boot. It really depends on how bad you mess up. If you make a copy of your data.img before you start making these changes, you can revert to that data.img and start back there.

Alright guys. Going to use this thread as a way to brainstorm about ways to improve the speed. Read up what I've posted, let me know if I did anything wrong... Also let me know what you guys do to improve speed!
Don't care about what build you're running, this thread isn't about what build is fastest - this is a how do I make every build faster thread.
I also realize I posted this in the Rhodium section - I want to see if there's any RAPH-specific tweaks that others should be made aware of!

Slightly off topic post
I do realize all of us are looking for ways to improve over all performance but what about a means to restore these settings or even possibly a means to run a script to apply the setting(s)? Perhaps something like XDA_UC for winomo but for Android. Or should there be something like this available already and I'm just the last person getting to the party (or not)?

R^7Z said:
I do realize all of us are looking for ways to improve over all performance but what about a means to restore these settings or even possibly a means to run a script to apply the setting(s)? Perhaps something like XDA_UC for winomo but for Android. Or should there be something like this available already and I'm just the last person getting to the party (or not)?
Click to expand...
Click to collapse
I guess you didn't read the first post... I wanted to do all this without apps.
You can find an app to tweak almost all of these things. If you read the article, there's an app to adjust the values for minfree. As for the pm disable stuff, there's an app out there but hyc said the one he found was a paid-for only app. One of those task killer apps that with the paid version has a startup manager - he didn't mention which one, but I agree with him... I'd rather just do it myself.
So the two 'advanced' topics can easily be handled with an app. I don't want to do it with apps, if you do more power to you.

Not really looking for an app but I guess my post mentioned XDA_UC. Either case, I am just looking for a way to add commands without having to redo the command for each re-run start over of XDAndroid; like the froyo.user.conf file?
I usually remove the androidapps and media folders for the initial start. Seems to really boot much faster for both of my RAPHs (100 and 110)

R^7Z said:
Not really looking for an app but I guess my post mentioned XDA_UC. Either case, I am just looking for a way to add commands without having to redo the command for each re-run start over of XDAndroid; like the froyo.user.conf file?
I usually remove the androidapps and media folders for the initial start. Seems to really boot much faster for both of my RAPHs (100 and 110)
Click to expand...
Click to collapse
...Do you put the folders back in afterwards?
The pm disable stuff is persistent, as I said. The minfree stuff, in lieu of an app I would think either putting the echo command in froyo.user.conf, or I think you would be able to make the change directly to the init.rc (or init.cfg/init.froyo.rc for our port/FRX builds). Definitely easier to just put the echo command in the user.conf file.

Correct! Either that or I compress/zip the folders (again only for the initial start/boot) and uncompress after the boot. Quite obviously, the latter would require more space but you wouldn't require a reboot, less you wanted use of the androidapps folder(drag-n-drop app/XDAndroid supported method).
That PM stuff makes my head swirl; bad enough I stare at numbers each day for about 8 hours

R^7Z said:
That PM stuff makes my head swirl; bad enough I stare at numbers each day for about 8 hours
Click to expand...
Click to collapse
Yea, it took me a while to sort it out. I'm definitely doing it correctly now, but it took a few 'oh crap' issues before I got it right. I also think I can trim it more, but I want to dedicate more time to testing it. The first batch I romped thru, I knew I didn't want things like Pandora starting at boot. You might want to take a look at it, and just look for the stuff that sticks out at first. Don't mess with it if you don't know what it does, and you'll be safe.
The issue that the pm stuff solves is having a lot of apps - a lot of these apps are designed to start on boot, whether you want them to or not. This gives power users true control over the startup of apps... It definitely helped my phone out. All of the 'tweaks' combined have helped tremendously in fact. I have been on a mission the last few days, and I've definitely narrowed down some things that really seem to make a difference on my device. There is a lot of fluff & BS around how to make a phone faster/run better, I wanted to have a thread where all the facts were laid out, without any fluff (hopefully).

cpu freq of 710400 is working well on my raph800 so far, havent noticed too much change in setting minfree but i usually keep as much programs killed as possible.
About to issue the following pm disable commands
Code:
pm disable com.android.voicedialer/.VoiceDialerReceiver
pm disable com.pandora.android/.api.bluetooth.AutoStartReceiver
pm disable com.paxmodept.palringo.android.main/com.palringo.android.integration.AndroidTaskScheduler$Receiver
pm disable com.rechild.advancedtaskkiller/.AutoStartReceiver
pm disable com.google.android.apps.maps/com.google.googlenav.friend.android.ServiceReceiver

runs fine as hell yo.

We should test out: http://forum.xda-developers.com/showthread.php?t=991276
I use it on my epic4g... I'll have to stick it on my wifes tp2.

icevapor said:
We should test out: http://forum.xda-developers.com/showthread.php?t=991276
I use it on my epic4g... I'll have to stick it on my wifes tp2.
Click to expand...
Click to collapse
Hrm. There's some interesting topics there that I haven't addressed.
Not sure that script as-is should be applied to our phones, but most of it sounds pretty good.
Wow. I am impressed with that script. Kinda wish I had found that earlier to be honest... I can pretty much remove all the minfree discussion from my post in lieu of this script .
I ran it, and everything seems fine. I already had values that were pretty similar to what he had, so I haven't really noticed a huge difference in the other things the script did, but time will tell. I'm also curious if it gets reapplied correctly on boot.
Thanks for the link tho, assuming I can get it to work well (which so far it seems to work just fine) I will integrate it into the first post and probably remove all the blather on minfree. I'll keep the links up in case people want to read it, but having this script definitely circumvents any need to understand it yourself .
Well, it seemed to work... but I need to sort out how to get it persistent across reboots.
Alrighty, got it all sorted using Script Manager.
I've updated the first post with the details on how to use this script. Thanks again icevapor!

not sure if its placebo effect (haven't been testing it long yet) but i set the following settings and it felt even faster on RAPH800 (note: only deviations from defaults are listed)
froyo.user.conf -> compcache -> cc_disksize=86
froyo.user.conf -> compcache -> cc_memlimit=58
froyo.user.conf -> custom_shells -> echo "1536,3072,8192,12288,16384,24576" > /sys/module/lowmemorykiller/parameters/minfree
startup.txt -> acpuclock.oc_freq_khz=710400

Hi,
sorry for the noob question but...how can I check if an application is set to auto/background sync? And how I can enable/disable it for a single application?
Thanks

automatic_jack said:
Hi,
sorry for the noob question but...how can I check if an application is set to auto/background sync? And how I can enable/disable it for a single application?
Thanks
Click to expand...
Click to collapse
It's all app-specific. In Google Voice for example, you hit menu, more, settings, sync & notifications - this app has two options, "background data" and "synchronize inbox". To properly sync the inbox, bg data must be enabled.
Every app is different, and not all apps have these options - or even similar options. Just poke around the apps you have in question and see what settings are available.

arrrghhh said:
It's all app-specific. In Google Voice for example, you hit menu, more, settings, sync & notifications - this app has two options, "background data" and "synchronize inbox". To properly sync the inbox, bg data must be enabled.
Every app is different, and not all apps have these options - or even similar options. Just poke around the apps you have in question and see what settings are available.
Click to expand...
Click to collapse
ah, ok...thanks for the reply

Squirrels said:
froyo.user.conf -> custom_shells -> echo "1536,3072,8192,12288,16384,24576" > /sys/module/lowmemorykiller/parameters/minfree
Click to expand...
Click to collapse
Do you have compcache enabled or disabled?

This may seem slightly askew from the current conversation but hear me out.
So far, with what builds I've made for myself, I have been able to "strip" the entire build down to just bare essentials just by removing apps from the /system/app or /data folder BEFORE installing a build.
Non-essentials for me would be:
Car Home
Google Search (same as built in search anyway)
Music (I tend to use a different player for this)
Talk
Voice Dialer
and any pre-installed apps that may come with the build.
LauncherPro plus is my launcher of choice, with eye candy enabled.
Of course this is a slightly different platform (HTC Kaiser), but should work the same way for HaReT or XAndroid builds as well. Also, some of the commands entered could be done with Terminal Emulator, giving you a POSIX terminal with "su" already enabled.
Just my $.02

Hi all,
Launcher2 and ADW are both open source so I can use them...but, who is faster?
Thanks

automatic_jack said:
Hi all,
Launcher2 and ADW are both open source so I can use them...but, who is faster?
Thanks
Click to expand...
Click to collapse
I like ADW myself. Launcher2 doesn't seem so great...
I especially like a launcher that can rotate with the phone. Plus the other options ADW provides are very nice IMHO.
Try both, use what works best for you .

[[Speed Improvements]] Brainstorming & Testing Thread!!

Alright guys. Going to use this thread as a way to brainstorm about ways to improve the speed. Read up what I've posted, let me know if I did anything wrong... Also let me know what you guys do to improve speed!
Don't care about what build you're running, this thread isn't about what build is fastest - this is a how do I make every build faster thread.
I also realize I posted this in the Rhodium section - I want to see if there's any BLAC-specific tweaks that others should be made aware of!

Thanks. Great posting. Will try some of the topics I never used (because I didn't know about them).

ThaiDai said:
Thanks. Great posting. Will try some of the topics I never used (because I didn't know about them).
Click to expand...
Click to collapse
I'm sure there are more as well... These are just the ones that I found made the most difference on my device.
I'm also curious about the minfree setting. I've only tried a few settings, they seem good. I haven't done any drastic number changing, it seems like changing these values should be done with a lot of caution and testing. There are definitely some values that should not be touched and others that can take some more fudging with numbers .

Added Topic 3 and Topic 4 to startup.txt and rootfs.img.
Just booting. Let's see if this is stable.
Software options I do not test now because I only test the new versions now. So specific app optimization only necessary when ThaiDai Android Loader and installation procedure reaches v2
Ok, boot ok, started Android (NeoFROYO build(, will tell tomorrow if stable.
If so I will use this options as standard for Blacky and I will add software like Droid firewall.
Thanks and good night

Update - I redid topic 4, feel free to re-read it.

Thanks
Enviado desde mi FROYO BLUE CWM1.9 usando Tapatalk

Hi Arrrghhh!
Can a squashfsed and odexed apk boost speed inside Android OS?

john_matrix said:
Hi Arrrghhh!
Can a squashfsed and odexed apk boost speed inside Android OS?
Click to expand...
Click to collapse
No clue. What does that have to do with the Speed Improvements thread?
I'm guessing you tried and it didn't work? What APK!?!
I guess I don't really follow your train of thought. Does sqshfs'ing and odexing an APK make it run faster...? I'm pretty new to Android in general. Never even used a native Android device .

http://www.addictivetips.com/mobile/what-is-odex-and-deodex-in-android-complete-guide/
http://forum.xda-developers.com/showthread.php?t=709630

farukb said:
http://www.addictivetips.com/mobile/what-is-odex-and-deodex-in-android-complete-guide/
http://forum.xda-developers.com/showthread.php?t=709630
Click to expand...
Click to collapse
I still don't get what that has to do with our builds. ODEX and DEODEX have nothing to do with our builds... That stuff only applies to native devices, or builds that are ported from native devices (I would think).
Perhaps I'm missing something here... please tell me if I am .

Maybe they mean something else like: oxidized or deoxidized (reduced) apps. With these modified apps you can speed up the transfer of electrons, resulting in more performance without overclocking your cpu. And more: it will not reduce your battery capacity measurable. I used it in some of the builds I tried. You will get a nice small benefit also: because of the electron transfers you will get a small induced massage in your fingers for free.

ThaiDai said:
Maybe they mean something else like: oxidized or deoxidized (reduced) apps. With these modified apps you can speed up the transfer of electrons, resulting in more performance without overclocking your cpu. And more: it will not reduce your battery capacity measurable. I used it in some of the builds I tried. You will get a nice small benefit also: because of the electron transfers you will get a small induced massage in your fingers for free.
Click to expand...
Click to collapse
LOL!
Epic.

OK. I cant get V6 SuperCharger script to work! I downloaded the script and run it but I cant find /data/99SuperCharger.sh after I run it

x12CHRIS18x said:
OK. I cant get V6 SuperCharger script to work! I downloaded the script and run it but I cant find /data/99SuperCharger.sh after I run it
Click to expand...
Click to collapse
Did you make the choices in the script, or did you just exit the script?
You have to make sure ScriptManager is running as root too. There's a setting for it. "Browse as root" - make sure that is enabled. You won't be able to see /data without browsing as root.
...You have a TouchHD? I always thought you had a RHOD, lol.

Governor issue (??)

Hi!
I noticed that in my Tab Pro 8.4 right after turning it on, when I'm not doing anything and just staring at the monitor it let only one core on clocked at 300MHz (using dashclock CPU information extension). So far so good.
The problem is that after some time, in the same context (doing nothing staring at the homescreen) it let two or four cores on clocked at 1497, so I have to reboot in order to save battery.
Any ideas why this is happenening? Does that happen to you?
P.S.: Battery saving settings turned on

It's mpdecision bug - needs root to fix
This issue should be affecting all stock ROM users of TAB Pro 8.4.
I noticed it a while ago and recently had some free time. The issue was narrowed down to Samsung's buggy mpdecision binary in /system/bin and you need root access to fix it. There are two ways to do it (you'll need terminal and file manager with root access rights):
1. Open terminal, type "su" and then "stop mpdecision". Open Root Explorer, navigate to /system/bin and rename "mpdecision" file to something like "00mpdecision". Reboot. All cores will be running at 300 mhz when idle and tablet will feel noticeably smoother and faster. I did not see any serious impact on battery while running this way for 2 weeks already.
2. Download attached mpdecision file from CM11 modrianwifi ROM, unrar it and transfer it to your tablet. Open terminal, type "su" and then "stop mpdecision". Open Root Explorer, navigate to /system/bin and rename "mpdecision" file to something like "00mpdecision". Copy new mpdecision file into /system/bin, change ownership to root:root and access rights to rwxr-xr-x.
Reboot. The issue will be resolved for good and unused cores will be shutdown properly. Tablet will feel the same way it was before file replacement.
Hope it helped.
favero_ said:
Hi!
I noticed that in my Tab Pro 8.4 right after turning it on, when I'm not doing anything and just staring at the monitor it let only one core on clocked at 300MHz (using dashclock CPU information extension). So far so good.
The problem is that after some time, in the same context (doing nothing staring at the homescreen) it let two or four cores on clocked at 1497, so I have to reboot in order to save battery.
Any ideas why this is happenening? Does that happen to you?
P.S.: Battery saving settings turned on
Click to expand...
Click to collapse

Hm I'm not seeing this issue on my tablet running the NK1 firmware, though I think I do remember it happening on the AND3 Firmware (saw it under Android Tuner) , I wonder if it was fixed under NK1, I'm curious too - do you know a easy way to reproduce it?
Here is a screenshot of CPU-Z, my tablet has been running for at least 1 day without a reboot, and had some 3D games run on it etc, CPU cores always seem to fallback to offline and 300mhz under my test
On a side note:
I don't run the Samsung Touch Wiz Launcher I am using "TSF Shell" as my Launcher, and have disabled some Samsung apps like "My Magazine" and a few Knox things that run in the background. also I don't use too many widgets since I found out they can hog CPU esp on poorly written apps. ,

mpdecision
I saw this issue on NA1, ND3, NG1 and NK1 firmware. Initially I thought it was fixed in NK1, but it came back in 3 days after last reboot. I'm running heavily de-bloated rooted stock f/w (Knox is at 0x0).
As for reproduction - I was suspecting Flipboard, but the issue came back after its uninstall as well. Seems to be uptime-related. 1 day uptime is not enough for NK1 - please check after 2 more days.
I'm running TouchWiz, but used "MyAndroidTools" to disable several services and startups for few remaining stock widgets and apps. Now I'm totally happy with my Tab Pro - best tablet I've ever had.
otyg said:
Hm I'm not seeing this issue on my tablet running the NK1 firmware, though I think I do remember it happening on the AND3 Firmware (saw it under Android Tuner) , I wonder if it was fixed under NK1, I'm curious too - do you know a easy way to reproduce it?
Here is a screenshot of CPU-Z, my tablet has been running for at least 1 day without a reboot, and had some 3D games run on it etc, CPU cores always seem to fallback to offline and 300mhz under my test
On a side note:
I don't run the Samsung Touch Wiz Launcher I am using "TSF Shell" as my Launcher, and have disabled some Samsung apps like "My Magazine" and a few Knox things that run in the background. also I don't use too many widgets since I found out they can hog CPU esp on poorly written apps. ,
Click to expand...
Click to collapse

NetFluke said:
This issue should be affecting all stock ROM users of TAB Pro 8.4.
Click to expand...
Click to collapse
Thank you! I've replaced my /system/bin/mpdecision file with yours and so far the tablet is working properly.
I'll know in a few days if it sticks. But, I definitely had this problem with the governor with T320XAR1ANK1. FYI, for what ever it's worth, I've noticed this governor is slightly slower to ramp up. I don't really care, as the tablet is still super responsive, but some may also notice that Antutu and CF-Bench scores are slightly lower with this governor.

Yeah I can confirm its still present in K1, I tried to limit it down to a few things that could be causing it but have been unsuccessful sine it occurs at random it seems
but my thinking its either something to do with
1. video decoding (I watched a few videos) .
2. charging the tablet (I noticed on my ampere cable it was drawing 0~70 - 120 mA idle )- but this could be because cpu was already drawing more power then needed, usually it's 0 ~ with an occasional 30 mA when plugged in with screen off.
3. possibly game / 3d
...anyways I switched the mpdecision file and it seems to work fine now, except for a slower rampup speed like the others said - not really a big deal i'm sure this will help battery life too.

favero_ said:
Hi!
I noticed that in my Tab Pro 8.4 right after turning it on, when I'm not doing anything and just staring at the monitor it let only one core on clocked at 300MHz (using dashclock CPU information extension). So far so good.
The problem is that after some time, in the same context (doing nothing staring at the homescreen) it let two or four cores on clocked at 1497, so I have to reboot in order to save battery.
Any ideas why this is happenening? Does that happen to you?
P.S.: Battery saving settings turned on
Click to expand...
Click to collapse
WOW! Finally someone on this forum other than me noticed this issue
I think I posted about this issue in September or so, and nobody else here said they noticed anything. Then I stopped checking this forum regularly... I'm glad to see others have now noticed this problem and have even figured out the root cause too!

Thermal Daemon Mitigation OFF with CM?

Dear All,
I´ve managed to build a CM 12.1 with nfs support. Why 12.1? Well, for my D855, that was the only branch I could get working when building a kernel in Ubuntu, using the downloadable snapshot at CM´s site. The nighty´s would give me errors of different kinds during the building process, so the files on the phone needed when building are probably not the exact required version that match with the repo you can download in terminal mode.
Anyway, my experience with marshmellow is that the phone gets so hot that it turns itself off - another good reason to stay with 12.1.
My phone however still gets hot, which happens when using it with my VR headset to watch UHD clips. After 5 mins of watching, it dims down a bit. Then a few mins later a bit more, and so on until it looks like I´m staring at the screen through old cheap shades.
I´ve already disabled automatic brightness control, tried apps which claim to keep the brightness at the desired strength (Lux, the app is called), an app that´s ment to keep the screen always on (Always Awake), an app claiming to patch this exact bug, flashed a hack that´ll throttle only above 70 C. None of this helped. What I do know is that in the secret menu of stock firmware, there´s an option called Thermal Daemon Mitigation OFF, but I can´t access the secret menu through CM - only CM´s secret menu, that doesn´t have this option. Enabling this is said to cope with the problem.
There´s also a file named thermanager.xml in system/etc, which looks like something which can be modified to meet my requirements, but I´m not sure.
Finally, my least prefered option is to install a thermal pad on the SoC, but although I´m experienced with hardware, it´s on desktop level - not with such tiny things as a mobile.
So please, could someone help out here? Is there a way to rebuild the kernel with the stock secret menu or amendments to the throttling? Is there a way for me to get into the stock secret menu in CM?
Other ideas?
PS: I´m posting here because if there´s a way to get Thermal Daemon Mitigation OFF option related parameters set when building kernel in menuconfig, then it´s related to this sub forum.
PPS: Edited thermanager so all brightness values are 255, this seems to fix the problem!

Develop Bugs

welcome