Is there a way to do this? I had a Nook Color and it there was an app to change the gamma. Anyone know of an app that can do this for our TouchPads?
You can change the LCD density in the build.prop. Adjust it in increments of 10 until you find what you like.
Sent from XDA Premium on Thunderbolt
Stock dpi is 160.
I'm running 140 (slightly smaller). Valid is 0 to 255, but numbers over 240 caused issues with other devices so not a bad idea to have a current recovery backup.
How to edit your dpi manually:
Get Root Explorer from Market and scroll down to system, and tap it to open it. Then at the top, tap the [ Mount R/W ] button. It'll change to [ Mount R/O ] so you have read/write privilege. (If you're using a different editor, you'll have to figure out how to get read/write privilege.) Then long-press on your build.prop file, choose "edit".
Scroll down until you find this line (bottom section in ADDITIONAL BUILD PROPERTIES):
ro.sf.lcd_density=160
Tap to position your cursor at the end of the line and carefully change 160 to 140:
ro.sf.lcd_density=140
When done, tap the menu button, choose "save and exit" and tap the top button in Root Explorer to change back to [ Mount R/W ] and reboot.
There are other programs that let you edit system files, but you need one that uses root since this is a system file that can't be edited with some file managers.
Colchiro said:
Stock dpi is 160.
I'm running 140 (slightly smaller). Valid is 0 to 255, but numbers over 240 caused issues with other devices so not a bad idea to have a current recovery backup.
How to edit your dpi manually:
Get Root Explorer from Market and scroll down to system, and tap it to open it. Then at the top, tap the [ Mount R/W ] button. It'll change to [ Mount R/O ] so you have read/write privilege. (If you're using a different editor, you'll have to figure out how to get read/write privilege.) Then long-press on your build.prop file, choose "edit".
Scroll down until you find this line (bottom section in ADDITIONAL BUILD PROPERTIES):
ro.sf.lcd_density=160
Tap to position your cursor at the end of the line and carefully change 160 to 140:
ro.sf.lcd_density=140
When done, tap the menu button, choose "save and exit" and tap the top button in Root Explorer to change back to [ Mount R/W ] and reboot.
There are other programs that let you edit system files, but you need one that uses root since this is a system file that can't be edited with some file managers.
Click to expand...
Click to collapse
Does 140 give you any market app compatibility issues with some apps (Maps) for example. I know on my Thunderbolt there are only a few DPI's to chose from or I have app compatibility errors and can't update apps.
I use Nitrality from the market to change the DPI. It's under the UI section of the application I believe. I set my DPI at 200 and now I can actually see my icons.
180 Seems good. 160 a little too smal and 200 a bit too big for my taste.
I'm on 150 right now and think I'll keep it there until something goofy, like missing market apps happens.
Had that problem on the Nook and didn't even know it until I flashed a version with 160 dpi and instantly had about 6 updates in Market.
How does one get back to 160 dpi? The bar in nitrality wont go below 182 in portrait or landscape
Sent from my HTC Eva 4G using Tapatalk
For reason I'm getting launcher force close with anything under 160. Any idea why?
Mine's set to 150 and I just opened LPP, backed it up and uninstalled it. (I use it on my phone, but not optimal for tables, IMO. No FC's here.
Please post non development Questions into General Forum of device when there is no direct Q & A Forum.
Related
i installed ae button, wanna get rid of it, but when i do i lose the voice command button. i only have 4 buttons in the settings button manager. any idea how to get the buttons back to the way they started? or add buttons to the phones default button manager?
gbenj said:
i installed ae button, wanna get rid of it, but when i do i lose the voice command button. i only have 4 buttons in the settings button manager. any idea how to get the buttons back to the way they started? or add buttons to the phones default button manager?
Click to expand...
Click to collapse
voice command or the voice dialer? for voice command you need to reg edit and add this
hklm/software/microsoft/shell/keys
add key 40C6
1. add binary data "default" value "\windows\appbuttons\record.lnk" -b (with quotes)
2. add dword flags value 0 (0000000)
3. binary data icon value "location of icon"
4. binary data name value button 5 (press and hold)
5. binary data ResetCmd "\windows\appbuttons\record.lnk" -b (with quotes)
then add key 40C7
1. add dword named BtnWnd value 0 (00000000)
2. add binary data "default" value "\program files\voice command\voicecmd.exe" - ptt
3. add dword flags value 0 (0000000)
4. binary data "icon" value "location of icon"
5. binary data "name" value "button 5"
that should do it...
if you have the OEM voice dialer then point #2 at the file for the voice dial program and then point #5 at that icons location
srtpusher said:
voice command or the voice dialer? for voice command you need to reg edit and add this
hklm/software/microsoft/shell/keys
add key 40C6
1. add binary data "default" value "\windows\appbuttons\record.lnk" -b (with quotes)
2. add dword flags value 0 (0000000)
3. binary data icon value "location of icon"
4. binary data name value button 5 (press and hold)
5. binary data ResetCmd "\windows\appbuttons\record.lnk" -b (with quotes)
then add key 40C7
1. add dword named BtnWnd value 0 (00000000)
2. add binary data "default" value "\program files\voice command\voicecmd.exe" - ptt
3. add dword flags value 0 (0000000)
4. binary data "icon" value "location of icon"
5. binary data "name" value "button 5"
that should do it...
if you have the OEM voice dialer then point #2 at the file for the voice dial program and then point #5 at that icons location
Click to expand...
Click to collapse
thanks alot, but could i just have a little more detail about waht i need to do. im using total commander for reg edits, and used the reg edits before to fix my mms with verizon, but im not sure what to do here. i keep getting "Error in line 1, not a valid hex string!" every time i add binary data default value"..." for either of them
to answer your question, i want to set up button 5 to use a program called voice speed dial. eventually ill want a bluetooth headset to access that program, but for now i just want to get that button working again.
similarly, if its possible to adjust the camera button to run a program(flashlight) when clicked, and open the camera when held.
thanks for the help
gbenj said:
thanks alot, but could i just have a little more detail about waht i need to do. im using total commander for reg edits, and used the reg edits before to fix my mms with verizon, but im not sure what to do here. i keep getting "Error in line 1, not a valid hex string!" every time i add binary data default value"..." for either of them
to answer your question, i want to set up button 5 to use a program called voice speed dial. eventually ill want a bluetooth headset to access that program, but for now i just want to get that button working again.
similarly, if its possible to adjust the camera button to run a program(flashlight) when clicked, and open the camera when held.
thanks for the help
Click to expand...
Click to collapse
OK! was able to get it done, was a little unclear based on the descriptions in your instructions, but once i looked at them, and looked at the existing buttons i had in the other folders it made some sense. you kept saying add binary data etc, but instead i just had to add a string with a vale of wtvr, maybe ur right and i just dont know the terminology, but thats what my registry had for the other buttons so i kinda just copied them.
thanks alot
one more question. any idea how i can add the flashlight program to the camera button(without holding it down)?
Hi X10 mates, I was facing a typical SMS notification problem when i used "Handcent SMS" or "GO SMS". I was repeatedly receiving an invalid SMS notification of an old message which i deleted long back. Though it goes off when i clear the notifications, the notification comes back whenever i get a new message or open the "Handcent SMS" or "GO SMS" software. It was annoying me until i sat for 4 hours to crack it. I did all the crap (spend few hundreds too ) to crack it. If you are ready to do all the crap, here it goes,,,
PREREQUISITES
1.Get access to your ROOT folder
- I used "SuperOneClick1.7(Free)" - It works with the latest firmware 2.1.A.0.435 - Pinch Zoom
2.Get a file explorer for your mobile
- I installed "Root Explorer(2.5 pounds)/(Free)"
3.Get a ".db" editor
- I installed "SQLLite Editor(1.8 pounds)"
SOLUTION
4.Open the Root Explorer and grant "SuperUser" Access when it pops up (This is the case with SuperOneclick)
5.Go to /data/data/com.android.providers.telephony/databases
6.Open the "mmssms.db" (This is where all the mms and sms are stored) and select to SQLLite Editor in the pop up
7.Open the "sms" table and view for a row which has empty value in "thread_id" column.
8. Just press the row and delete the record ! And we are done !!
Though this may not be the easiest way, but i did at last!
Interesting. Can this help on MMS unsendable & unreceivable?
You can download it here. I like it.
http://www.miui-dev.com/miui-weather/
Sebring5 said:
You can download it here. I like it.
http://www.miui-dev.com/miui-weather/
Click to expand...
Click to collapse
nopes, install just fails. it gives no reason. Donno whats wrong.
ksekhar said:
nopes, install just fails. it gives no reason. Donno whats wrong.
Click to expand...
Click to collapse
Same here.
link12245 said:
Same here.
Click to expand...
Click to collapse
that's three in a row, same here
when i go to install it - the android system ask me to allow this application to :
read my gps to get my location .. .ok
access to my personal information.. hmmm ok...
Network access.. ok
directly call phone numbers? ... umm - no...
and access to system tools to issue system level alerts.. ok.
Why would this program need to directly call my phone numbers?
I'm not even going to try it...
Or am I being too paranoid?..
Here are the installation instructions:
step by step using root explorer
move miuiweather.apk to sdcard
open root explorer and navigate to /sdcard
long press on miuiweather.apk and hit COPY
navigate to /system/app
hit menu - PASTE (if it says you can't because its read only, hit the top right button mount r/w, then paste)
longpress on the miuiweather.apk in /system/app
select permissions
make checkboxes look like following: (where x indicates check, 0 indicates unchecked)
Read Write Execute
X ---- X ---- 0
X ---- 0 -----0
X ---- 0 ----0
(all three checkmarks in first column, first checkmark in second column)
same thing with the db file, except instead of /system/app, navigate to /data/data/com.miui.weather/databases/ to paste it
and permissions should look like this
X ---- X ---- 0
X ---- X -----0
0 ---- 0 ----0
you SHOULDNT "install" anything, just move the files to the proper places with proper permissions, and reboot.
Here is the support thread:
http://miui-dev.com/forums/showthre...ATHER-Help-amp-Support&highlight=miui+weather
Greetings!
First, this message will be rather long, for which I apologize. I am providing headings that allow whomever is interested to skip to whatever is relevant to them.
About the device:
It is one of two Eken GC10X tablets, purchased from Micro Center a while back dirt cheap. The second one is 6000 miles away in Europe. . . .
It is currently running Android 4.2.2
Its firmware revision is v2.0patch1
Its kernel version is 3.4.39+, dated Friday, October 18th, 2013, at 18:11:40 CST
Its build number is wing_k70-eng 4.2.2 JDQ39 20131028 test-keys
It comes pre-rooted by default. All that needs to be done is to install a terminal program and pay attention to certain paths.
About me:
I have been messing with computers, programming, and operating systems since the time of "wood burning computers"
I know my hosts file from my fstab, I have run various flavors of both Linux and Windows in both client and server configurations, and I know that both man pages and a good search engine Are Your Friends. (which is how I came to be here!)
Issue:
Since this Eken tablet comes with a bare minimum of internal memory, I was researching ways to mitigate this. I found an article that mentioned a workaround:
Copy everything in root to a large external SD card
Transpose the settings for the internal and external memory in the /etc/vold.fstab file
Save and Reboot
The result of this is a tablet that - regardless of the presence or absence of any external SD card - always boots as if it had never been booted before, (returns to "first-boot / out-of-box" setup). Any installed apps are gone and the "internal" memory - which is about 1-2 gigs - shows absolutely full. In addition to all that, I cannot do anything with the ADB port since it requires setting the "USB Debugging" flag, which gets reset on reboot. (i.e. The ADB interface is not available.
Examining the vold.fstab shows that the original setup of that file has been returned after I did a nuke-and-reboot.
I can reboot and re-install a terminal program and advanced file manager. (X-plore is my favorite)
I see three possible solutions:
Find the reason why it's booting like this and fix it.
Find a compatible firmware release for this tablet and re-flash it - if possible - from an external SD card.[/INDENT]
Do some kind of "nandroid" backup from the other Eken GC10X tablet I have and copy it to this one. Unfortunately it's 6000 miles away and I won't be able to get to it until sometime after January 2019. In addition, I cannot access the device via the ADB port.
Research I have done:
gsmhosting's allwinner forums
This site claims to have a (ahem!), "modified" version of the firmware, which I have downloaded.
The androidmtk site
This site has the "PhoenixCard" software which alleges that it can be used to create external SD card images of firmware files that can:
Install firmware from the SD card to the device.
Allow you to run the firmware from the SD card to verify it. It should be noted that MalwareBytes flags the updater.exe file because it attempts to download from a known Trojan site. Renaming the extension, (exe.bad), solves that problem.
I have not tried re-flashing any firmware version, though I have tried running the firmware from SD, which doesn't work.
Can someone help me with suggestions on how to return this tablet to normal?
Thanks in advance for any help you can provide!
Solution:
I guess it's "umpteenth time's the charm!" :highfive:
Having done considerable research, (with everything pointing to an issue with the busybox file being in the wrong place), I decided to revisit this, did a little more digging and ultimately found a solution.
Since nothing irritates me more than someone posting "I fixed it!" without telling everyone else HOW they fixed it, here are the steps I used to solve this problem.
Please be careful. You will be mucking around with your tablet's/phone's root file system in ways that can be fatal if you're not paying attention. It's not that difficult but you DO have to PAY ATTENTION to what you're doing.
TO-DO:
Instead of copying the busybox file, it should really be a symlink to /sbin/busybox.
If anyone figures out a way to create a symlink in Android that actually works, I'd like to know.
Here it is:
Pre-requisites:
The device MUST be rooted for this to work. I cannot help you with advice on how to root individual devices. This Eken tablet comes rooted by default.
Download off-line from Android Archives, (using a different system), an early version of X-plore, which is an excellent file manager.
Load X-plore onto a thumb-drive or a micro-SD card, (I used a micro-SD), and then install the SD card / thumb drive into the tablet you're trying to fix.
Steps to solve the problem:
First, go to Settings => Security and enable "unknown sources"
Open your device's file manager
Find the copy of X-plore you downloaded, and tap it to begin the off-line installation process.
Once it installs, open it and go to the "configuration" menu. This is within the three-dot menu drop-down in the upper right-hand corner.
Select:
* (near the top) Show hidden files => select the check-box. (optional)
* Root Access => Superuser + mount writable (this allows you to change permissions to permit writing the root filesystem)
* (scroll down) Dark mode => select the check-box. (this is a personal preference; IMHO it makes it easier to read.)
* Exit configuration by using the "back" button or back arrow in the upper left corner.
* You should now see two columns representing two views of the device's file-system.
On the left side, open the "Root" filesystem, also labeled with a "/"
Scroll down and find the "/sbin" folder and open it by tapping on it.
* You may, or may not, see several folders and files. You are looking for the file "busybox"
* If you don't see it there, you may have to "find" it using the magnifying glass icon in the center row of icons.
* Open the "find" dialog and replace the "*.*" with "busybox" and then select "OK".
* (assuming you found it), tap at the right-hand edge of the row with the file-name to "select" it - a big check-mark will appear there.
Go to the right-hand side list now. Find and open:
* Root (/) like you did before.
* system
* bin
* At the top of that column, you should see a folder icon, followed by "/system/bin"
Look to see if there is a file named "busybox" there. (In my case, it was missing - which is the problem)
(assuming it's missing)
Collapse the "bin" folder by tapping on it - it might take a couple of taps.
Touch-and-hold the "bin" folder until a long list appears. Scroll down to the bottom of that list and select "permissions"
Within the permissions dialog, there are three columns: Read, Write, and Execute.
* There should be three selected boxes under "Read".
* There should be ONE selected box, the top one, under "Write"
* There should be three selected boxes under "Execute"
* Directly below the last box under "Read", the box labeled "Recursive" should NOT be selected.
* To the far right of "Recursive" should be a note that reads "Mode: 755"
Under the heading "Write", select the other two boxes so that all three are selected. The word "Mode" should now be followed by "777" Close the permissions dialog by selecting "OK".
Verify the following:
* The arrow at the top of the center column is pointing to the right. If it is not pointing to the right, tap it until it points toward the right-hand column.
* The file "busybox" on the left-hand pane has a check-mark next to it and no other files are selected.
* The "bin" folder on the right-hand side has been collapsed and is selected by being a darker black with NO check-mark.
* The top of that column shows the folder icon and "/system/bin" as the selected path.
Copy the "busybox" file into the /system/bin folder by doing the following:
* Tap the "copy" icon in the center column - it will look like two pieces of paper stacked together.
* Verify that the dialog that opens:
* Just below the top right it says "busybox" (the file you're copying)
* Under that, "Copy to"
* Under that, a folder icon and then "/system/bin".
* Under that, the selection "Move mode (delete source files) is NOT selected!
* Tap "OK" to copy the file to /system/bin. Once the copy is done, the dialog will close.
Tap "bin" on the right hand side to open it if it does not open by itself.
Verify that "busybox" appears in both the left and right hand panes.
Press and hold the "busybox" file until the list dialog re-appears.
* Select "permissions".
* Verify that all three "Read" permissions are set, only the top "Write" permission is set, and all three "Execute" permissions are set. (You may have to clear the bottom two "Write" check-boxes.)
* Verify the "Mode" is set to "755"
* Close the permissions dialog by tapping "OK"
Collapse the "bin" folder by tapping on it.
Long-press the "bin" folder, select "permissions", and set the permissions of the bin folder to "755" the way you did for the busybox file above.
Return to the "Configuration" menu by following the steps at the beginning and select "Superuser" or "Normal User" instead of "Superuser + mount writable" to prevent accidental changes in the future.
At this point, you should be able to close and re-open X-plore and verify that "busybox" actually exists within /system/bin. If it does, you can reboot and your should be good to go.
If it's not there, re-trace the steps I listed above, paying particular attention to the "Superuser" setting in "configuration" and the various file permissions.
If you're still having trouble, post a reply below and I will try to provide what help I can.
Thanks for your patience and I hope this helps others who were puzzling with this as long as I was.
I managed to get myself stuck in a boot loop by editing build.prop on my android 6.0 Nexus 7 tablet. I added the linero.sf.hwrotation=0 at the end of the file and saved it and then when I rebooted, it made no difference. I then changed the permissions on the build.prop file to 666 then now after the Google logo it gets stuck on a blank screen.
My device is rooted and I have twrp. So I'm thinking hopefully I can boot into recovery mode then could I somehow reset the permissions? Can someone kindly guide me through what I need to do? What should the permissions be? Why was that line not working in the first place? Should I remove that hwrotation line?
Thanks
The permission should be 0744
jwoegerbauer said:
The permission should be 0744
Click to expand...
Click to collapse
Thank you. I booted into TWRP recovery mode and used the file manager to chmod the build.prop file to 0744 and rebooted it. Now it seems to be working.
Any ideas why my hwrotation setting is being ignored? only thing I can think of is that maybe it isn't supported on android 6.0? because most of the guides that are about that seem to refer to android 4.
ahmed123 said:
Any ideas why my hwrotation setting is being ignored? only thing I can think of is that maybe it isn't supported on android 6.0? because most of the guides that are about that seem to refer to android 4.
Click to expand...
Click to collapse
Try to make it persistent.
Example
Code:
# possible values: 0 = Landscape, 90 = Portrait, 180 = Reverse Landscape, 270 = Reverse Portrait
persist.ro.sf.hwrotation=180
jwoegerbauer said:
Try to make it persistent.
Example
Code:
# possible values: 0 = Landscape, 90 = Portrait, 180 = Reverse Landscape, 270 = Reverse Portrait
persist.ro.sf.hwrotation=180
Click to expand...
Click to collapse
Just tried that, still no difference. The boot google logo and android animation is still in portrait for some reason. When android starts up then you can see it flip to landscape which is the user setting part that I applied.