Database Users

How to use Terminal emulator

hi
need some little help
in this tread http://forum.xda-developers.com/showthread.php?t=769026 it stands that you shall type in these lines "then upon first boot go to terminal and enter these (without the quotes) and press enter after every line.
su
rm /data/system/batterystats.bin"
but how do i use terminal emulator? and what is it? and were and when do i type the lines in?

Download "Terminal Emulator" from market. Then open the app which brings up a screen where you can type.
Type in what it says you should type and press enter when it says to.
Sent from my Nexus One using XDA App

dont bother is a goood answer....coz i got that build and have never done that terminal stuff, and not had one freeze or anything...awesome build.
matt

How to get Netflix working on kindle fire Kernal 3.0

I had a hell of a time finding this while digging through the forums. I thought I would wrap it up in one nice neat easily readable thing....
In order to get Netflix working on the 3.0 kernal you need to do 1 of 2 things.
Option 1
You can edit build.prop by using Root Explorer and going to /system/build.prop and selecting "Open in Text Editor" Via long-press. Than edit build.prop on the line ro.product.model and change it to Amazon Kindle Fire
Option 2
You can use ADB to do it as well by doing this
From the command line:
I) Remount /system in read/write mode using:
Code:
adb remount
II) Next, Copy build.prop to your PC, it will show up in the same directory as adb.exe
Code:
adb pull /system/build.prop
III) Next Edit build.prop using notepad or your preferred text editor on the line (notepad++ is mine) ro.product.model and change it to Amazon Kindle Fire
IV) And Push build.prop back to the device
Code:
adb push build.prop /system/build.prop
Finally, After Either Option Restart the Device and you should be watching Netflix bau55 style.
THANKS TO nathris AND twa_priv for providing the fix
s0m3f00l

I think his latest updated ROM fixes the issue with build.prop. There's nothing new but the did fix the name.

ya I flashed his 4/22 rom and Netflix works fine.
Sent from my Amazon Kindle Fire using xda premium

Hashcode updated hist 04-22 build with the fixed build.prop. The build can be found here: http://rombot.droidhive.com/ROMs/otter/cm9/

I installed from CM9 reloaded and I had to go through the fix.

s0m3f00l said:
I installed from CM9 reloaded and I had to go through the fix.
Click to expand...
Click to collapse
Yeah, all roms build before yesterday probably have this issue.

Dpi changer non root

Any dpi changer without root? I really don't wanna root this phone everything is perfect
Sent from my Nexus 6P using Tapatalk

digweed4me said:
Any dpi changer without root? I really don't wanna root this phone everything is perfect
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Don't have a 6P. but on my Nexus 5 I changed DPI by using an adb command:
adb shell wm density DPI && adb reboot (where DPI is a value of your choice)
see: http://www.androidbeat.com/2015/07/how-to-change-dpi-of-android-device-without-root/
cheers!

hr_kaleu said:
Don't have a 6P. but on my Nexus 5 I changed DPI by using an adb command:
adb shell wm density DPI && adb reboot (where DPI is a value of your choice)
Click to expand...
Click to collapse
That could cause some problems in apps. One of the common is Swiftkey being enormous. Best way to do it is to change ro.sf.lcd_desnity in the build.prop but that require root.
Still worth to give it a shot, just remember this if you see any problems with scaling after using the adb method.

See this thread for changing dpi without root: http://forum.xda-developers.com/nexus-6p/general/guide-modify-partition-root-t3240721
Note you still need to have an unlocked bootloader.

Change app icon grid

Is there a way to change the grid size of the homescreen without using another launcher? I would like to have 5 app in one line.
Thanks for the help!

yeah if you are rooted. simply go to /system/build.prop and look for ''ro.sf.lcd_density=480'' and change it to 440 or 430.

Actually you don't have to be rooted. All you need is adb and few commands:
Take a note on your current density
Code:
adb shell dumpsys display | grep mBaseDisplayInfo
there will be density: parameter (it is the current one)
In order to change screen's density:
Code:
adb shell wm density $density
Replace $density with desired value (e.g. 480).
To get back to default execute following command:
Code:
adb shell wm density reset
Make sure to reboot your phone after making changes for them to be reflected.
Not that these settings change density of the screen. Some applications may behave incorrectly with values other than default.

bablu048 said:
yeah if you are rooted. simply go to /system/build.prop and look for ''ro.sf.lcd_density=480'' and change it to 440 or 430.
Click to expand...
Click to collapse
460 dpi is a must try!

[GUIDE] Tasker - Your device doesn't appear to be rooted!

I've been working on tasker on my phone, and i run into a problem, when i wanted to execute shell commands, using root.
"Your device doesn't appear to be rooted!" I've been browsing the internet about this problem and i found a solution that actually works (at least it works for me)
1. You need a file explorer with root acces to / (Root Explorer, ES File Explorer etc)
2. Open "/system"
3. Open "build.prop"
4. Add this line (or a line containing modversion) at the beginning "# modversion for tasker"
6. Reboot your phone
7. Done :fingers-crossed:

Good info, thanks for sharing. Using Magisk? Some other solutions are to prepend "su" to your Run Shell commands:
su
input swipe xxx yyy
And another is to install supersu app (even though you don't use it art all with magisk).
Sent from my SM-G955F using Tapatalk

RuggedHunter said:
Good info, thanks for sharing. Using Magisk? Some other solutions are to prepend "su" to your Run Shell commands:
su
input swipe xxx yyy
And another is to install supersu app (even though you don't use it art all with magisk).
Sent from my SM-G955F using Tapatalk
Click to expand...
Click to collapse
Yes I am using Magisk!