Related
I think I've found the cause of this, where you download something from the Market and it says downloaded but just sits there forever. Google has something called a "checkin" service that sends them anonymous usage data, bug reports, crash logs, etc, but it fails a lot. When you download something from the Market, it sends a message to Google about it, and if it fails it just freezes.
You can turn this off easily with a system property. I haven't seen any issues with doing this except that it will break the setup wizard if you have this set during boot after a wipe.
All you need to do is add this line to the end of /system/build.prop:
Code:
ro.config.nocheckin=1
So, something like this:
Code:
adb pull /system/build.prop .
(edit file with notepad, vim, emacs if you hate yourself)
adb remount
adb push build.prop /system
adb shell reboot
Hopefully this helps someone and Google doesn't shoot me down from space
build.prop reverts after reboot
hey
followed instructions
- pulled build.prop
- added ro.config.nocheckin=1 to end
- adb remount (RW filesystem)
- pushed new build.prop, says 2593 bytes written
- rebooted device
upon reboot: /system/build.prop reverts back to original
any idea for a Rogers Dream user here
Just wanted to clarify that the steps should actually be:
Code:
adb remount
adb pull /system/build.prop .
*(edit file with notepad, vim, emacs, whatever)*
adb push build.prop /system
adb shell reboot
Otherwise, people are going to reboot their computers willy-nilly, and not their androids.
cyanogen said:
Hopefully this helps someone and Google doesn't shoot me down from space
Click to expand...
Click to collapse
Google is going to have you wacked for figuring this out.
terminal commands plz?
G1-evolve said:
terminal commands plz?
Click to expand...
Click to collapse
Code:
su
mount -o remount,rw /system
echo "ro.config.nocheckin=1" >> /system/build.prop
reboot
cyanogen said:
Code:
su
mount -o remount,rw /system
echo "ro.config.nocheckin=1" >> /system/build.prop
reboot
Click to expand...
Click to collapse
Thanks alot! What would be the "Undo" to this incase one day I need to wipe/flash a rom?
edit: seems to still "hang" and not work. Only works if I log into "gtalk"
After having completed this procedure, I've still managed to "hang" the market once. Though in all fairness, once is fine, because it used to happed daily.
However, I've noticed something that some people might consider a "down side" - when you uninstall apps, they remain in your downloads. That's exactly the same behavior that people were complaining about before cupcake came out.
besides anonymous usage data, bug reports and crash logs, what else would i be disabling by doing this?
AlfaTrion said:
besides anonymous usage data, bug reports and crash logs, what else would i be disabling by doing this?
Click to expand...
Click to collapse
Well, as I've mentioned in my post above yours, all apps that you ever downloaded while having check-in disable, will stay in your My Downloads. Again, it doesn't bug me as I use aTrackDog primarily for update checks, but I know some people don't like this.
Have you tried clearing the market cache in Settings > Applications > Manage Applications > Market? I'm curious to know if that assist with that at all.
jordanjay29 said:
Have you tried clearing the market cache in Settings > Applications > Manage Applications > Market? I'm curious to know if that assist with that at all.
Click to expand...
Click to collapse
I haven't, but I'll try. Though I am quite sure it will not do anything because that list remains the same through flashes and upgrades, so I'm sure it's pulled from Google servers.
my solution......
Whenever the market hangs when I download [email protected] reboot and it works fine. I don't get the hang problem a lot so it doesn't bother me to reboot.
pistol4413 said:
Whenever the market hangs when I download [email protected] reboot and it works fine. I don't get the hang problem a lot so it doesn't bother me to reboot.
Click to expand...
Click to collapse
It's not only about Market hanging. After disabling check-in, Market actually works much faster because data does not get sent to Google every time you do something (download / remove / update / etc.)
Would there be a way to schedule this checkin? Or make it run only once every x times? That might bridge the difference between no hangs and retaining all past downloads, and many hangs but clearing the downloads list.
jordanjay29 said:
Would there be a way to schedule this checkin? Or make it run only once every x times? That might bridge the difference between no hangs and retaining all past downloads, and many hangs but clearing the downloads list.
Click to expand...
Click to collapse
The framework could be modded for that, but thats a lot of work. Right now, the checkin code is a listener, and just wakes up for certain events (like an app install).
I THINK this could happen if one changes or deletes the APN of the phone.. for me it started to freeze the download after I completely closed the 3g/2g connection. So maybe google uses that connection in order to gether the data instead of the wifi. Can that be changed so that both use the wifi?
script to disable checkin service:
Code:
#!/bin/sh
su
if ! grep -q "^ro.config.nocheckin=" /system/build.prop; then
echo "Mounting system as read/write"
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
echo "Disabling Checkinservice"
echo "ro.config.nocheckin=1" >> /system/build.prop
echo "rebooting.."
reboot
else
echo "CheckinService already disabled"
fi
jordanjay29 said:
Would there be a way to schedule this checkin? Or make it run only once every x times? That might bridge the difference between no hangs and retaining all past downloads, and many hangs but clearing the downloads list.
Click to expand...
Click to collapse
I disassembled the classes.dex from the checkin.apk with baksmali and in the CheckinService.smali these fields are defined:
Code:
.field private static final CHECKIN_INTERVAL:J = 0x6ddd00L
.field private static final CHECKIN_INTERVAL_MAX:J = 0xa4cb800L
.field private static final CHECKIN_INTERVAL_MIN:J = 0x927c0L
Values in decimal(dont take the last character for conversion!). I think they should represent milliseconds:
0x6ddd00L: 7200000
0xa4cb800L: 172800000
0x927c0L: 600000
Maybe you can "schedule" the checkin service by changing these values, assemble the dex again with smali, replace the original classes.dex in the apk and push it back to the Phone.
Code:
adb remount
adb pull /system/app/checkin.apk .
Make a backup copy of the apk ;)
extract the classes.dex
java -jar -Xmx512m baksmali-0.94.jar -o ./checkin classes.dex
Edit the File
java -jar -Xmx512m smali-0.94.jar -o classes.dex ./checkin
Replace the classes dex in the pulled checkin.apk
adb push checkin.apk /system/app/checkin.apk
adb shell reboot
You can get smali and baksmali from here:
http://code.google.com/p/smali/
I was talking about the explicit checkin that happens after apps are installed, etc..
Hi,
This is my first guide and my english is something that i call "horrible", so please, don't be rude.
Kies runs a service on our android phone to communicate with Kies software (Windows). Sometimes, kies process doesn't do proper cleanup of itself processes and leave some zombies around our memory.
This guide is to make a Tasker profile that switch the kies service, so you can activate it when needed, and disable when you want some more RAM.
Requisites:
Tasker
Rooted Phone
Busybox
So, go to Tasker and create a new Task (+) and put a name like "KiesSwitcher".
Add the following actions (Remember to tick Use Root when using Run Shell):
Script -> Run Shell -> Command: "mount -o rw,remount /system"
Task -> If -> %KIESEXE !~ (doesn't match) 1
Script -> Run Shell -> Command: "chmod 0644 /system/bin/kiesexe"
Script -> Run Shell -> Command: "kill -9 $(pidof kiesexe)"
Variable -> Variable Set -> %KIESEXE To 1
Task -> Else
Script -> Run Shell -> Command: "chmod 0755 /system/bin/kiesexe"
Script -> Run Shell -> Command: "/system/bin/kiesexe &"
Variable -> Variable Clear -> %KIESEXE
Task -> End If
Script -> Run Shell -> Command: "mount -o remount,ro /system"
Now, go to your home screen, Add Widget -> Tasker -> select your Kies Task.
Leave a comment if you have some suggestion or improvement and hit thanks if you want to just appreciate my work.
what's kies? ....................
Samsung Kies /ˈkiːs/ keess[1] is a freeware software application used to communicate between Windows or Macintosh computers, and more recently manufactured Samsung mobile phone and tablet computer devices, usually using a USB cable connection (though wireless LAN Kies connectivity is now possible using some devices).
This software may be used for:
Data backup
Data transfer (between the Windows or Mac PC & a Samsung mobile device)
Multimedia (audio, video, photos, etc.) management
To purchase/acquire additional or special device features
Device firmware and operating system (OS version) upgrades
Sent from my GT-I9300 using xda app-developers app
Lol...I know what kies is! ......a POS!
I personally doesnt use this, but some people like to sync música and photos by this. Anyway it resolver my problem of having zombie processes of Kies.
Sent from my GT-I9300 using xda app-developers app
NOTE: This script now works with both Android 4.2.2 and 4.3 (Aug 12th, 2013). Also as of Aug 11th SManager v2.8.3 has been updated to support Android 4.3
the_boo discover how to set/reset the Nexus 10 screen resolution from the command line. Attached is a script to toggle to a resolution setting of your choice. This worked well when connected to my Samsung PN58C8000 HDTV with screen set for 16:9. Playing videos with MX Player had no side bars at all on the HDTV. This setting is global and not app specific.
Although not required, use Script Manager-SManager(NoAds) and a SMWidgets desktop widget, as a shortcut to the script, set the widget to execute in the back ground. Running the script in the background is visually much nicer as a terminal console is not required or seen during execution.
Issues:
1) Sometimes the resolution can only be changed BEFORE the HDMI cable is attached.
2) Once the N10 froze with a blank screen at full brightness. Had to hard power cycle. Never had that happen before.
3) If for any reason the Nexus 10 is rebooted before the display is reset back to normal, the resolution will persist through the reboot. The script can still be used to toggle back or the reset command can be run in a terminal session "am display-size reset".
4) Root permissions are required so any terminal session must already be in root or you need to add a leading 'su root' before the rest of the command. Example:
> su root sh "/path to the script/hdmi_toggle.sh" "/sdcard/hdmi_toggle" 1920x1080 288
"hdmi_toggle.sh" script:
Code:
#!/system/bin/sh
#
# Script: hdmi_toggle.sh
#
# NOTE: This script requires root permissions!
#
# Purpose: Toggle the display resolution to reset or match a specific HDMI
# display target. Script dynamically detects the android version
# and adjusts the screen commands to match the ROM.
#
# This script requires two or three command line arguments:
# 1) The path on internal storage where the HDMI display toggle state
# is stored.
# 2) The display resolution. Additional resolutions are possible.
# HDTV: 1920x1080
# PC Monitor: 2560x1440
# 3) For Andorid 4.3+ only, add a density value to make the icons display properly
# HDTV: 1920x1080 with density 288 or smaller
# PC Monitor: 2560x1440 with density less than 288
# NOTE: 288 is the default value if no denisty argument is specified
#
#
# Example Android 4.2.x command usage:
# > sh "/path to the script/hdmi_toggle.sh" "/sdcard/hdmi_toggle" 1920x1080
#
# Example Android 4.3+ command usage:
# > sh "/path to the script/hdmi_toggle.sh" "/sdcard/hdmi_toggle" 1920x1080 288
#
# NOTE: The path to the HDMI toggle directory must already exist and have
# read/write permissions.
#
## The commands to be executed depend on which version of Android is
## installed.
version_43 () {
if [ "$CURRENT_STATE" == "ON" ]; then
# Reset display state
echo "Reset display"
wm size reset
wm density reset
echo "OFF" > "$TOGGLE_FILE"
else
# Set display state
echo "Set display resolution to $RESOLUTION and density $DENSITY"
wm size $RESOLUTION
wm density $DENSITY
echo "ON" > "$TOGGLE_FILE"
fi
}
#
version_42 () {
if [ "$CURRENT_STATE" == "ON" ]; then
# Reset display state
echo "Reset display"
am display-size reset
echo "OFF" > "$TOGGLE_FILE"
else
# Set display state
echo "Set display resolution to $RESOLUTION"
am display-size $RESOLUTION
echo "ON" > "$TOGGLE_FILE"
fi
}
#
TOGGLE_PATH=$1
TOGGLE_FILE="$1/hdmi_state.txt"
#
# NOTE: Resolution values are not validated.
RESOLUTION=$2
#
DENSITY=$3
# Set a default desnsity if there was none specified
if [ "$DENSITY" == "" ]; then
DENSITY="288"
fi
#
# Test that the toggle state path exists and has read/write permissions
if [ ! -d "$TOGGLE_PATH" ]; then
echo "The toggle directory '$TOGGLE_PATH' must exist."
exit 1
# Make sure the toggle path directory has read/write permissions
elif [ ! -r "$TOGGLE_PATH" ] || [ ! -w "$TOGGLE_PATH" ]; then
echo "The toggle directory '$TOGGLE_PATH' must have read/write permissions."
exit 1
fi
#
# Automatically set the toggle state to OFF if the toggle file does not exist
if [ ! -f "$TOGGLE_FILE" ]; then
echo "OFF" > "$TOGGLE_FILE"
fi
#
# Set the display to the specified resolution or reset
CURRENT_STATE=$(cat $TOGGLE_FILE)
#
echo "current_state ($CURRENT_STATE)"
#
# Detect the Android version
VERSION=$(getprop ro.build.version.release)
#
# Set or reset the screen resolution
if [ ${VERSION:0:3} = "4.3" ]; then
version_43
else
version_42
fi
#
exit 0
Here are the "before resolution change" and "after resolution change" Nexus 10 screen shots. The SManager widget is circled in red in the before picture. The widget toggle icon is really for the "Samsung Remote" app but using Desktop VisualizeR it can be set to any image file or icon.
Adding the script as a SManager desktop widget instructions
3DSammy said:
the_boo discover how to set/reset the Nexus 10 screen resolution from the command line. Attached is a script to toggle to a resolution setting of your choice. This worked well when connected to my Samsung PN58C8000 HDTV with screen set for 16:9. Playing videos with MX Player had no side bars at all on the HDTV. This setting is global and not app specific.
Although not required, use Script Manager-SManager(NoAds) and a SMWidgets desktop widget, as a shortcut to the script, set the widget to execute in the back ground. Running the script in the background is visually much nicer as a terminal console is not required or seen during execution.
Issues:
1) Sometimes the resolution can only be changed BEFORE the HDMI cable is attached.
2) Once the N10 froze with a blank screen at full brightness. Had to hard power cycle. Never had that happen before.
3) If for any reason the Nexus 10 is rebooted before the display is reset back to normal, the resolution will persist through the reboot. The script can still be used to toggle back or the reset command can be run in a terminal session "am display-size reset".
4) In a plain terminal session, if you execute the script WITHOUT a leading 'su root', the script still works but produces permission errors. I am running rooted Stock so am not sure if you need to be rooted.
"hdmi_toggle.sh" script:
Code:
#!/system/bin/sh
#
# Script: hdmi_toggle.sh
# Purpose: Toggle the display resolution to reset or match a specific HDMI
# display target.
#
# This script requires two command line arguments:
# 1) The path on internal storage where the HDMI display toggle state
# is stored.
# 2) The display resolution.
# HDTV: 1920x1080
# PC Monitor: 2560x1440
#
# Command usage:
# > sh "/path to the script/hdmi_toggle.sh" "/scdard/hdmi_toggle" "1920x1080"
#
# NOTE: The path to the HDMI toggle directory must already exist and have
# read/write permissions.
#
TOGGLE_PATH=$1
TOGGLE_FILE="$1/hdmi_state.txt"
#
# NOTE: Be aware that the resolution values are not validated.
RESOLUTION=$2
#
# Test that the toggle state path exists and has read/write permissions
if [ ! -d "$TOGGLE_PATH" ]; then
echo "The toggle directory '$TOGGLE_PATH' must exist."
exit 1
# Make sure the toggle path directory has read/write permissions
elif [ ! -r "$TOGGLE_PATH" ] || [ ! -w "$TOGGLE_PATH" ]; then
echo "The toggle directory '$TOGGLE_PATH' must have read/write permissions."
exit 1
fi
#
# Automatically set the toggle state to OFF if the toggle file does not exist
if [ ! -f "$TOGGLE_FILE" ]; then
echo "OFF" > "$TOGGLE_FILE"
fi
#
# Set the display to the specified resolution or reset
CURRENT_STATE=$(cat $TOGGLE_FILE)
#
echo "current_state ($CURRENT_STATE)"
#
if [ "$CURRENT_STATE" == "ON" ]; then
# Reset display state
echo "Reset display"
am display-size reset
echo "OFF" > "$TOGGLE_FILE"
else
# Set display state
echo "Set display resolution to $RESOLUTION"
am display-size $RESOLUTION
echo "ON" > "$TOGGLE_FILE"
fi
#
exit 0
Here are the "before resolution change" and "after resolution change" Nexus 10 screen shots. The SManager widget is circled in red in the before picture. The widget toggle icon is really for the "Samsung Remote" app but using Desktop VisualizeR it can be set to any image file or icon.
Click to expand...
Click to collapse
I can't download SManager, it says its not compatible in the play store
Sent from my Nexus 10 using xda app-developers app
As of May 25th the Playstore no longer shows SManager (v2.8.2) as being incompatible with the Nexus 10.
ThugosaurusRex said:
I can't download SManager, it says its not compatible in the play store
Click to expand...
Click to collapse
I bought SManager for my Nexus 10 before the "incompatibility" issue came up in the playstore. After writting the SManager developer he replied with this email from May 7th, 2013:
==================================
Thanks a lot for your interest in S Manager.
In the last version 2.7.0 of SManager a little bug was introduced when app was published. I forced to request bluetooth feature, instead suggest it, so this is the reason why versions vary per device. Devices with bluetooth should accept 2.7.0 whereas devices without bluetooth only accepts until 2.6.0.2 version.
I hoped to fix (restoring previous features) this issue in few days, but for various reasons I do not have published fixed version yet.
About incompatibility device android market it is very "intelligent" and decides itself if devices are compatible or not. I hate such feature because sometimes works and sometime does not work.
One of the most common issue of incompatibility is related to lcd density. And usually custom roms customizes the lcd densities.
Attached is 2.7.0 no ads version.
If still does not work for you, or the next version(Hope release it in less than 2 weeks) is incompatible please, let me know.
Best regards,
Devwom
=================
The playstore still shows incompatible for me even after installing v2.7.0 and I cannot get any updates unless the apk is emailed to me by the developer. Also be aware that the paid version is the only one that has the "Execute scripts from widgets without opening console" feature. I think the free version still supports desktop widgets.
I completely forgot about that until your post.
Hi,
I wonder why there are only 2 comments for such an important post...
This issue has been bugging me a lot, ever since I've tried to watch a movie on my 1080p tv through HDMI.
Is this solution safe to use? does it work well?
Animor said:
Hi,
I wonder why there are only 2 comments for such an important post...
This issue has been bugging me a lot, ever since I've tried to watch a movie on my 1080p tv through HDMI.
Is this solution safe to use? does it work well?
Click to expand...
Click to collapse
First you do need this script to change resolutions as it just wrappers the raw "adb display-size" commands. To get the most from the script, as a convient desktop toggle, you need SManager and I think that still shows as incompatible with the Nexus 10 in the playstore. I bought SManager before the playstore issues appeared.
As far as safe to use I have not noticed any issues at all. With that said I do not use the HDMI cable very often. The solution definitely works for at least two resolutions as listed in this post 1920x1080, 2560x1440 and I saw a third working resolution in this post "1280x800".
Thanks.
Did you try the app mentioned in the thread you linked? Is it working on the same principal as your script?
Sent from my Galaxy S3 using Tapatalk 2
Animor said:
Thanks.
Did you try the app mentioned in the thread you linked? Is it working on the same principal as your script?
Sent from my Galaxy S3 using Tapatalk 2
Click to expand...
Click to collapse
I have not tried the app mentioned in this thread so cannot comment on what it uses but the adb display-size would have api equivelants so I am sure at a system level they use the same approach.
One more thing on May 25th SManager v2.8.2 was released and that is compatible with the Nexus 10 as I received an automatic update. This means you could use this HDMI toggle script as described in the original post.
Hello,
I would really like to use this script but I don't have a lot of experience. And it gives be the error: The toggle directory ' ' must exist.
How can I get past that/ what am I doing wrong?
I could really use a more step by step guide. What I've done is I saved the script in a file ending with .sh, I installed the programs that OP said and ran it as root.
I am running a rooted unlocked buttered aokp rom with the kmanta kernel.
Thank you
bv90andy said:
... I would really like to use this script but I don't have a lot of experience. And it gives be the error: The toggle directory ' ' must exist.
How can I get past that/ what am I doing wrong?I
Click to expand...
Click to collapse
Here is a step by step guide I wrote in a different thread. It has details on the raw commands but also how to install and run the toggle script. What it does not have are the specific SManager steps for adding the script as a desktop SManager widget.
I will add those later but I am on the run at the moment. From what you wrote I think you are almost there anyway.
3DSammy said:
Here is a step by step guide I wrote in a different thread. It has details on the raw commands but also how to install and run the toggle script. What it does not have are the specific SManager steps for adding the script as a desktop SManager widget.
I will add those later but I am on the run at the moment. From what you wrote I think you are almost there anyway.
Click to expand...
Click to collapse
hi, thanks for your reply. I followed your instructions from your other thread and tried to run your script from the terminal and the error is almost the same, it now says The toggle directory '/sdcard/hdmi_toggle' must exist. I've created that folder once in the terminal then again with es explorer and checked for it to have read/ write permission with es explorer. I don't understand what I'm doing wrong. do I have to place something in that folder?
I'll appreciate any further input when you have the time. thanks.
Perhaps you should try the app based on the same code more or less, from the other thread. I haven't tried it myself though since I lost my hdmi cable.
It should do things automatically.
Sent from my GT-I9300 using Tapatalk 4 Beta
Adding the script as a SManager desktop widget
For those unfamiliar with SManager here is a how-to for using the toggle script as it was intended.
On a PC:
1) Copy the script directly from the original post.
2) Then paste it into a text editor and save with the name "hdmi_toggle.sh"
On your Nexus 10:
3) Copy the "hdmi_toggle.sh" script from the PC to some directory on your N10.
4) Create the toggle state directory "/scdard/hdmi_toggle" on the Nexus 10 using any File Browser
In SManager:
1) Open SManager (it will start in file browser mode).
2) Navigate to the location you saved "hdmi_toggle.sh"
3) Select it and a pop-up window will appear
4) Make sure that "hdmi_toggle.sh" is set up as:
> "ls script" is selected (the default)
> Enter in the "Arguments" fields values such as: "/scdard/hdmi_toggle" "1920x1080"
5) Select Save then Exit
Adding the SManager Widget to the desktop:
1) Make sure you have installed the SMWidgets from the playstore
2) Add a SManager Widget to the desktop and a pop-up panel will appear (same as adding any desktop widget)
3) Select "Add one script widget"
4) Select "hdmi_toggle.sh"
5) Select "Yes" for the "Run widget in background?" pop-up (This may only be a feature of the "No Ads" paid version of SManager)
Click on the widget to test it out and it should toggle ON/OFF the resolution you specified in the SManager "Arguments" field. You can have as many of these widgets as you want to toggle specific resolutions. Using an icon change app to change the SManager widget icon to be consistent with your desk top theme.
bv90andy said:
... The toggle directory '/sdcard/hdmi_toggle' must exist. I've created that folder once in the terminal then again with es explorer and checked for it to have read/ write permission with es explorer. I don't understand what I'm doing wrong. do I have to place something in that folder?.../QUOTE]
I suspect you have not added the command line arguments in SManager. See the newly posted instructions (post-12), specifically in the "In SManager" section #4. Please read that entire post.
Good Luck.
Click to expand...
Click to collapse
Animor said:
Perhaps you should try the app based on the same code more or less, from the other thread. I haven't tried it myself though since I lost my hdmi cable.
It should do things automatically.
Sent from my GT-I9300 using Tapatalk 4 Beta
Click to expand...
Click to collapse
That app is the boss. Works flawlessly. Thanks for pointing it out.
3DSammy, thank you for the detailed explanation!
Sent from my GT-I9300 using Tapatalk 4 Beta
So, not having a clue what I'm doing, I followed the directions, but get the following error:
"syntax error: 'elif' unexpected"
I feel like I did something (or probably didn't do something), but it's beyond my depth as to what it was. Any ideas?
3DSammy said:
...and a pop-up window will appear
4) Make sure that "hdmi_toggle.sh" is set up as:
> "ls script" is selected (the default)
> Enter in the "Arguments" fields values such as: "/scdard/hdmi_toggle" "1920x1080"
5) Selec....
Click to expand...
Click to collapse
I just wanted to say that at point 4 in smanager arguments you made a mistake and wrote /scdard/hdmi_toggle this gave me a headache because I just copied the arguments this time around and it wasn't working for this reason.
Another thing to note is that resolution 2560x1440 works as well, and it doesn't break some 3rd party launchers.
And a quick question as well: have you tried this in 4.3? because it doesn't seem to work. I also tried just the command in terminal and it doesn't take the command. They must have changed something
bv90andy said:
I just wanted to say that at point 4 in smanager arguments you made a mistake and wrote /scdard/hdmi_toggle this gave me a headache because I just copied the arguments this time around and it wasn't working for this reason.
Another thing to note is that resolution 2560x1440 works as well, and it doesn't break some 3rd party launchers.
And a quick question as well: have you tried this in 4.3? because it doesn't seem to work. I also tried just the command in terminal and it doesn't take the command. They must have changed something
Click to expand...
Click to collapse
You are correct about the "scdcard" mistype. I have installed 4.3 but have not tried that script or the command yet. I would suggest trying one of the apps in the themes and applications thread to see if the programmed solution still works. I don't use the HDMI output on the N10 so looking at this is low on my priority list.
They changed the code in 4.3, it is no longer am display-size, it is now "wm size" and it seems people are having trouble getting it to work in TE
the_boo said:
They changed the code in 4.3, it is no longer am display-size, it is now "wm size" and it seems people are having trouble getting it to work in TE
Click to expand...
Click to collapse
I have Nexus 7 2nd gen. Native resolution is 1200x1920 and default density is 320 (though technically the density is about 323).
To get it to work correctly in 1080p, I have to run the following commands as root:
wm size 1080x1920
wm density 288
To change it back:
wm size reset
wm density reset
If I don't change the density to 288 or smaller, the icons and everything get messed up, especially in landscape.
I wrote a script to do it, but I have to run them by calling "sh script.sh". I have "#!/system/bin/sh" as the first line, but I can't get permission to execute the scripts. No matter how many times I run "chmod 755 script.sh", the mode doesn't change. Yes I'm su, that's required for wm after all. I also got SManager and SMWidgets. SManager fails to execute the scripts as well even though it has root access and the scripts are configured to use root. And SMWidgets, though it is installed, doesn't appear anywhere. How do I run it?
Hello,
please anybody do know how permanently disable ipv6?
This is working:
Code:
sysctl -w net.ipv6.conf.all.disable_ipv6=1
sysctl -w net.ipv6.conf.default.disable_ipv6=1
but after off/on wifi is ipv6 again running.
I have Purity ROM 5.1.1_r13 - LVY48E
Thanks
Why do you want to stop IPv6?
(If you want it to be permanent, put the commands in a script in your /system/etc/init.d/ directory, assuming your ROM has one.)
I've seen a few Build.Prop tweaks floating around, but thought it would be a good idea to start a repository for quick reference. Can add tweaks as they become known and verified to work. To edit the build.prop you will need ROOT access. Also, it has been reported that certain build.prop tweaks can cease to function, after removing root.
My use case and reason for posting, is to try and be close to stock as possible and use the most minimal changes. This assists in streamlining my added tweaks after I apply OTA's and updates. As of now, the following tweaks are working with the 8.1.0 and 9.0 (Nov Patch)
Unlock/Flash/Root Guide provided by @nathanchance
https://forum.xda-developers.com/pixel-2/how-to/guide-unlock-flash-root-pixel-2-walleye-t3702417
WiFi Tether
net.tethering.noprovisioning=true
Disable USB Debugging Notification
persist.adb.notify=0
Disable Sending Usage Data
ro.config.nocheckin=1
There are too many build.prop editors out there to list, so I'm going to bypass recommendations. However, the following is a way to edit the build prop from the ADB Shell on your PC. Ensure USB Debugging is enabled on your phone, if it isn't already done, and run the following commands. Just replace the command between the "quotation marks" below. Ensure you have the latest ADB drivers for your PC and navigate to the "CMD" shell.
adb shell
su
**(grant permission if phone asks)**
mount -o rw,remount /system
echo "persist.adb.notify=0" >> /system/build.prop
reboot
EDIT#2 Disable Sending Usage Data
b00ster23 said:
I've seen a few Build.Prop tweaks floating around, but thought it would be a good idea to start a repository for quick reference. Can add tweaks as they become known and verified to work. To edit the build.prop you will need ROOT access. Also, it's been reported that certain build.prop tweaks cease to function after removing root.
Unlock/Flash/Root Guide provided by @nathanchance
https://forum.xda-developers.com/pixel-2/how-to/guide-unlock-flash-root-pixel-2-walleye-t3702417
WiFi Tether
net.tethering.noprovisioning=true
Disable USB Debugging Notification
persist.adb.notify=0
Disable Sending Usage Data
ro.config.nocheckin=1
There are too many build.prop editors out there to list, so I'm going to bypass recommendations. However, the following is a way to edit the build prop from the ADB Shell. Ensure USB Debugging is enabled, if it isn't already done, and run the following commands. Just replace the command between the "quotation marks" below.
adb shell
su
**(grant permission if phone asks)**
mount -o rw,remount /system
echo "persist.adb.notify=0" >> /system/build.prop
reboot
EDIT#2 Disable Sending Usage Data
Click to expand...
Click to collapse
Is those build.prop tweaks (except from disabling USB notification) even working?
xFirefly93 said:
Is those build.prop tweaks (except from disabling USB notification) even working?
Click to expand...
Click to collapse
Why yes they are. The purpose that I use them for is to stay at stock with the least invasive changes. Makes it easier to update OTA's and reapply my 'tweaks'