Changing DPI on the Smartwatch 3 - Sony Smartwatch 3

I decided to try changing the watch's DPI a little to see if I could make sideloaded apps more usable, and it worked! Settled on 220 for now, but will probably raise it. It was a bit of a crapshoot, since I've no idea what the stock DPI is.
Anybody else tried this? What values did you decide on? Thoughts?

[NUMINIT] said:
I decided to try changing the watch's DPI a little to see if I could make sideloaded apps more usable, and it worked! Settled on 220 for now, but will probably raise it. It was a bit of a crapshoot, since I've no idea what the stock DPI is.
Anybody else tried this? What values did you decide on? Thoughts?
Click to expand...
Click to collapse
Can you tell me Which sideloaded apps are working with 220 dpi?

donalberto17 said:
Can you tell me Which sideloaded apps are working with 220 dpi?
Click to expand...
Click to collapse
Well, I've only tried a few so far, but here's what I got:
- Browsers are now actually almost usable. UC Mini gives me the best experience so far. Chrome is ssssllllooooow, Firefox is okay-ish, CM Browser crashes on start.
- Stock Google keyboard is finicky, but manageable. Microsoft's handwriting keyboard got screwed up by the dpi change (it works, but the letters are off from where you actually touch the screen)
- Greenify is great
- ES File Explorer works okay
Curiously, only sideloaded apps seem to have been affected. Wear apps, watchfaces, etc. are the same. Notification cards are noticeably smaller, and so are Wear's system icons (charging and disconnected). So there's very little to mess up, and the change is really easy to reset even if you don't know the watch's stock dpi (I don't).

[NUMINIT] said:
Well, I've only tried a few so far, but here's what I got:
- Browsers are now actually almost usable. UC Mini gives me the best experience so far. Chrome is ssssllllooooow, Firefox is okay-ish, CM Browser crashes on start.
- Stock Google keyboard is finicky, but manageable. Microsoft's handwriting keyboard got screwed up by the dpi change (it works, but the letters are off from where you actually touch the screen)
- Greenify is great
- ES File Explorer works okay
Curiously, only sideloaded apps seem to have been affected. Wear apps, watchfaces, etc. are the same. Notification cards are noticeably smaller, and so are Wear's system icons (charging and disconnected). So there's very little to mess up, and the change is really easy to reset even if you don't know the watch's stock dpi (I don't).
Click to expand...
Click to collapse
Stock DPI is 280, btw did you made those apps system apps? or you just sideloaded those apps normally?

donalberto17 said:
Stock DPI is 280, btw did you made those apps system apps? or you just sideloaded those apps normally?
Click to expand...
Click to collapse
Nope, just installed normally with adb install. I can actually access /system partitions with ES anyway.

[NUMINIT] said:
Nope, just installed normally with adb install. I can actually access /system partitions with ES anyway.
Click to expand...
Click to collapse
Ok uc browser it's opening but not loading pages, can you explain me what I need to do? It needs to be a system app? and another question latest version of google keyboard will work?

donalberto17 said:
Ok uc browser it's opening but not loading pages, can you explain me what I need to do? It needs to be a system app? and another question latest version of google keyboard will work?
Click to expand...
Click to collapse
Oh yeah, the browser needs to be system. Sorry for being unclear!
As for the keyboard, yes, it will work. You need to install it and then enable it manually, like this:
Code:
adb shell ime enable com.google.android.inputmethod.latin/com.android.inputmethod.latin.LatinIME
then
Code:
adb shell ime set com.google.android.inputmethod.latin/com.android.inputmethod.latin.LatinIME

Okay, so UC loads pages just fine if you're on Wifi but not connected to your phone via Bluetooth. Weird.

Related

Change pixel density

Just now I applied a trick to have more info on my screen by changing the dpi setting. To to so in /system/build.prop modify the following line:
Code:
ro.sf.lcd_density=240
I changed it to 200. After modifying the settings in Launcher Pro I now have 6 rows and 5 columns in my homescreens which still have enough space in between.
You need root access to change system files. The file manager also needs to have root access. I used Super Manager for this.
I got this hack from doid-life. They also give an alternative way using adb.
You can also alter the build.prop by installing the PropEditor-0.3.apk from the following link;
http://code.google.com/p/net-widgetron-propeditor/downloads/detail?name=PropEditor-0.3.apk
Thanks, that made it a lot easier!
Now I also changed these lines:
Code:
ro.wifi.channels=14
wifi.supplicant_scan_interval=90
This way all 14 wifi channels are available (also in 3G mobile hotspot) and the phone scans every 90 seconds for new wifi networks instead of the default 45 seconds. As I always have wifi on that saves some battery.
Ok this is weird. I just discovered that anything else than 240 dpi renders the dialer unusable. Sometimes it opens to only close again a split second later. Pitty because I really like the lower dpi setting. Back at 240 dpi it feels like a phone for the vision impaired.
Can i ask how exactly are the changes brought to dpi adjust?
Sent from my MB525 using XDA App
Can someone please post a screenshot? Because I think this will make everything smaller so it's very hard to read anything.
LCDDensity for Root makes the same, you can find it on the market, free of charge.
Foxhound.kl said:
You can also alter the build.prop by installing the PropEditor-0.3.apk from the following link;
http://code.google.com/p/net-widgetron-propeditor/downloads/detail?name=PropEditor-0.3.apk
Click to expand...
Click to collapse
Cool thanks for this.
I started changing screen density with my HD2 when they only had android from sd card. Basically lower number means "higher definition" and you can fit more things on the screen.
so waht does having 14 channels for WIFI do?
When I change the pixel density, I get FC when opening „phone„. I am using Pay's ROM.
Jt612 said:
so waht does having 14 channels for WIFI do?
Click to expand...
Click to collapse
It allows people to connect to broadcasts on all possible WiFi channels around the world.
So North Americans who might be originally limited to 1-11 (is the NA device locked to this though?) won't miss out on the odd coffee shop hotspot overseas that broadcasts on 13.
m11kkaa said:
When I change the pixel density, I get FC when opening „phone„. I am using Pay's ROM.
Click to expand...
Click to collapse
Try to download spare parts from the market (if its not in that rom already) and uncheck compatibility mode and restart your phone. might work.

Four simple steps to use alternative keyboards

This approach works with non-smart keyboards.
1. Install your preferred keyboards from Market
2. Use ES file explore (with Root feature and RW mount enabled in the advanced setting) or use Root Explorer to copy the keyboard .apk file from /data/app to /system/app
3. Reboot and select the keyboard by pressing and holding at any text input box.
4. (optional) Sideload and install "Nookcolor Tools" from http://forum.xda-developers.com/showthread.php?t=868366. You will have an option to set keyboards.
So far this method does not work with
- SlideIt
- Thumb keyboard (thanks fr4nk1yn)
Confirmed! Thanks aruangra, it's quite easy. No need to tweak DB file!
not sure why nooktools is needed. I saw no option to change the keyboard in it.
copying to /system/app armed to allow the option change but add thumb keyboard to the list of non-working ones.
anyone know if this works for Swype?
This is great! Didnt even think to look in the nook section
Sent from my Kindle Fire using Tapatalk
fr4nk1yn said:
not sure why nooktools is needed. I saw no option to change the keyboard in it.
copying to /system/app armed to allow the option change but add thumb keyboard to the list of non-working ones.
Click to expand...
Click to collapse
Thumb Keyboard only FC's for me as well.
fr4nk1yn said:
not sure why nooktools is needed. I saw no option to change the keyboard in it.
copying to /system/app armed to allow the option change but add thumb keyboard to the list of non-working ones.
Click to expand...
Click to collapse
Thanks. NookcolorTools has a button to change keyboards. As you said, Nookcolor Tools is optional. I updated the guide above.
I tried using Simply Gingerbread keyboard, just FCs as well.
If any of these keyboards create a lib in /data/data/name_of_app/lib, you may need to copy it to /system/lib
Sent from my PG86100 using Tapatalk
anyone who installed thumb keyboard on their KF have issues uninstalling the app?
Swiftkey Phone and Tablet version work great, along with Hacker's keyboard (all functions of the apps work.) After you do the above steps, make sure to copy the lib files from /data/data to /system/lib as mentioned in a previous post. Once you do this, the program see's that it is installed and will continue with the setup.
I used the NOOK controls with root/superuser enabled to auto-select the keyboards it may or may not be a requirement. For swift, I was able to get both versions registered and fully working minus the Google search recognition because I can't find where to get the .apk without it going to the amazon app store. I also tried Swype and while the interface loads properly on the kindle, it does not function right and constantly closes whenever you hit a button.
jmalto said:
Swiftkey Phone and Tablet version work great, along with Hacker's keyboard (all functions of the apps work.) After you do the above steps, make sure to copy the lib files from /data/data to /system/lib as mentioned in a previous post. Once you do this, the program see's that it is installed and will continue with the setup.
I used the NOOK controls with root/superuser enabled to auto-select the keyboards it may or may not be a requirement. For swift, I was able to get both versions registered and fully working minus the Google search recognition because I can't find where to get the .apk without it going to the amazon app store. I also tried Swype and while the interface loads properly on the kindle, it does not function right and constantly closes whenever you hit a button.
Click to expand...
Click to collapse
Swiftkey works for me but seems to be missing the swipe down gesture to minimize. I currently have no way to minimize the keyboard. Are you experiencing this?
ckong1 said:
Swiftkey works for me but seems to be missing the swipe down gesture to minimize. I currently have no way to minimize the keyboard. Are you experiencing this?
Click to expand...
Click to collapse
This is the exact problem I'm having preventing me from using it.
I used the nook app as well, but when you are in a typable area, just long pressing brings up the keyboard changing option.
I hadn't tried it prior to installing the nook app, but I know that's always been available on my phone.
ckong1 said:
Swiftkey works for me but seems to be missing the swipe down gesture to minimize. I currently have no way to minimize the keyboard. Are you experiencing this?
Click to expand...
Click to collapse
I have the same problem. I had never used Swiftkey tablet before, so didn't know for sure about swiping down to mvoe the keyboard, but I tried it, and it didn't work.
It's extremely important to also move the lib files as described earlier in the thread. Without this, you will only get FC.
Felnarion said:
I have the same problem. I had never used Swiftkey tablet before, so didn't know for sure about swiping down to mvoe the keyboard, but I tried it, and it didn't work.
It's extremely important to also move the lib files as described earlier in the thread. Without this, you will only get FC.
Click to expand...
Click to collapse
I didn't touch any lib files and I didn't have any FCs. And if the minimize doesnt work for you, we can probably assume not a lib file issue then.
Thelgow said:
I didn't touch any lib files and I didn't have any FCs. And if the minimize doesnt work for you, we can probably assume not a lib file issue then.
Click to expand...
Click to collapse
Don't know. I was having FC, constantly, every few seconds. Moved the lib files and restarted, perfectly functional.
hybridowner said:
anyone know if this works for Swype?
Click to expand...
Click to collapse
Yes, it works for me...
will test with lastpass keyboard and report back. thanks for the find!
Houndog101 said:
Yes, it works for me...
Click to expand...
Click to collapse
How in the world did you get Swype to work? I've tried everything
Typing this with LastPass keyboard. It works!

What's up with Play?!

Riddle me this: I'm sitting here looking at a working Google Maps. Yet, Play says it's incompatible with my Nexus 7. And, that's not the only one! Apps like Boat Browser and, of all things, GMail! Anyone else running into this?
gjtoth said:
Riddle me this: I'm sitting here looking at a working Google Maps. Yet, Play says it's incompatible with my Nexus 7. And, that's not the only one! Apps like Boat Browser and, of all things, GMail! Anyone else running into this?
Click to expand...
Click to collapse
Screenshots? (power+volume down)
Off the top of my head, if you flashed a custom ROM, it could be that.
I ran a WW firmware ROM on my US Transformer Prime and certain apps became incompatible.
jaycustom said:
Screenshots? (power+volume down)
Off the top of my head, if you flashed a custom ROM, it could be that.
I ran a WW firmware ROM on my US Transformer Prime and certain apps became incompatible.
Click to expand...
Click to collapse
Screenshots forthcoming. Stock but rooted ROM.
<><~~~~~~~~~~~~~
Gary
Sent from my Nexus 7 using xda pro.
Changing your DPI can cause compatibility issues. If you haven't changed that, you may wanna try wiping data for play store app in settings.
Caliyork said:
Changing your DPI can cause compatibility issues. If you haven't changed that, you may wanna try wiping data for play store app in settings.
Click to expand...
Click to collapse
What is the default DPI? I changed some settings with Rom Toolbox Pro and that may have been one of them. Not sure, though.
gjtoth said:
What is the default DPI? I changed some settings with Rom Toolbox Pro and that may have been one of them. Not sure, though.
Click to expand...
Click to collapse
LCD Density = DPI
Did you change your screen size to make things either smaller or larger? that will break compaitiblity in the play store.
jbrawley1 said:
LCD Density = DPI
Did you change your screen size to make things either smaller or larger? that will break compaitiblity in the play store.
Click to expand...
Click to collapse
Found it, thanks! I reset it to 213. Still no joy.
gjtoth said:
Found it, thanks! I reset it to 213. Still no joy.
Click to expand...
Click to collapse
OK, I cleared caches, and that seems to have done the trick for MOST of the apps that showed incompatible. Strangely, GMail still shows incompatible, but I can deal with that. I was having autorotation problems and that's fixed now, too.
Thanks to all for your assistance.

Sideload and Remove apps...

I there is a lot of information about all the cool things we can do with our knew watches, but I thought I would link to a solution to a problem which has vexed me since purchasing my watch.
Android installs all wear capable apps to your watch without your control.
Well, now you have control.
Take a look at this doc.
Take a look at this doc.
Now, the document is a bit old, as you do not even need your phone, but it will give you the commands you need. You can plug your watch directly into your computer and manage your apps through adb (and possibly total commander, but I am not certain about that one). I tested this to remove apps I want on my phone but not my watch (Goodbye Lowe's and Amazon). You do not even need root to do this with regular apps, and as the author points out, using this method you can even sideload full Android Apps.
To interact with the device specifically, you change the code a little. For instance, instead of removing an app by...
Code:
adb -e shell pm uninstall -k com.glTron
You use
Code:
adb shell pm uninstall com.glTron
Be warned, if you uninstall a system app, or a dependency, things will be bad. However, if you stick to apps you know are user apps, this is relatively safe (the big system apps do need root permission to disable or uninstall).
Credit goes to Copyright:*corbin - Hacking Android Wear*and*EpicLPer. Great work!
I found the thread over in the wear development forum. There, they are compiling a list of full Android apps which work on wear.
Find that here.
Good luck.
Just got the watch and I've been playing with it the past few days. Did actually ruin some things trying to sideload system all's but restored it all just fine. Setting the DPI to 200 works really well with a lot of regular Android apps (adb shell wm density 200) without any negative effects to the UI or stock Android Wear apps (in fact they don't seem to be affected by the DPI change at all). Stock DPI is 280.
A lot of apps that don't depend on needing a status bar work really well. There's a thread on here on how to sideload and set the stock Google Keyboard as your default keyboard (which works really really well, honestly no issues typing with it). Can use things like terminal, Chrome and ES File Explorer from the watch itself with no issues at all. I'm going to try more apps later and possibly play with the DPI some more.
Apparently there's a way to get xposed working too, haven't tried it yet though. There's also a wayr to apprently get basic gapps and the Play Store working but I can't figure it out. Also can't figure out how to install apks directly from the watch itself. ES File Explorer and terminal aren't letting me install apps. WiFi works fine in all apps if you put the watch in Airplane mode or if you disconnect your phone from the watch. Hopefully we get data and networking over Bluetooth at some point, it'd be awesome.
Anybody try any emulators? I'm interested in trying something like epsxe to maybe play RPGs or something simple that doesn't require too many buttons to play.
DarkRazorZ said:
Just got the watch and I've been playing with it the past few days. Did actually ruin some things trying to sideload system all's but restored it all just fine. Setting the DPI to 200 works really well with a lot of regular Android apps (adb shell wm density 200) without any negative effects to the UI or stock Android Wear apps (in fact they don't seem to be affected by the DPI change at all). Stock DPI is 280.
A lot of apps that don't depend on needing a status bar work really well. There's a thread on here on how to sideload and set the stock Google Keyboard as your default keyboard (which works really really well, honestly no issues typing with it). Can use things like terminal, Chrome and ES File Explorer from the watch itself with no issues at all. I'm going to try more apps later and possibly play with the DPI some more.
Apparently there's a way to get xposed working too, haven't tried it yet though. There's also a wayr to apprently get basic gapps and the Play Store working but I can't figure it out. Also can't figure out how to install apks directly from the watch itself. ES File Explorer and terminal aren't letting me install apps. WiFi works fine in all apps if you put the watch in Airplane mode or if you disconnect your phone from the watch. Hopefully we get data and networking over Bluetooth at some point, it'd be awesome.
Anybody try any emulators? I'm interested in trying something like epsxe to maybe play RPGs or something simple that doesn't require too many buttons to play.
Click to expand...
Click to collapse
How did you sideload and retain wifi? I know that I need to put it in /system/priv-app/ but I have no idea how to push an apk there, and I have no idea where the apk is installed to for me to be able to find and then push over
Unless you are rooted, you do not have permission to write to /system. If you are trying to put regular apps in /system/priv-app/ then I would recommend against rooting. An exception may be (and DarkRazorZ) can confirm, but the keyboard may need to be in system.
Anyway, you cannot merely drop an app in the right place (usually/data/app/) you have to install it. To do so, use this code.
Code:
Adb shell pm install ***.apk
To install the play store, you do need root access and to put it in system/priv-app, but that is one of many hoops. I suggest you check that thread if that is what you intend to do.
I'm not sure how the whole networking with priv-app works, I tried playing around with it but didn't get very far. For Chrome, if I want to use it over WiFi, I have to put the watch in to Airplane mode and reconnect to WiFi. It's pretty quick and easy to do and forced WiFi on for every app. I don't know of any other way.
DarkRazorZ said:
Just got the watch and I've been playing with it the past few days. Did actually ruin some things trying to sideload system all's but restored it all just fine. Setting the DPI to 200 works really well with a lot of regular Android apps (adb shell wm density 200) without any negative effects to the UI or stock Android Wear apps (in fact they don't seem to be affected by the DPI change at all). Stock DPI is 280.
A lot of apps that don't depend on needing a status bar work really well. There's a thread on here on how to sideload and set the stock Google Keyboard as your default keyboard (which works really really well, honestly no issues typing with it). Can use things like terminal, Chrome and ES File Explorer from the watch itself with no issues at all. I'm going to try more apps later and possibly play with the DPI some more.
Apparently there's a way to get xposed working too, haven't tried it yet though. There's also a wayr to apprently get basic gapps and the Play Store working but I can't figure it out. Also can't figure out how to install apks directly from the watch itself. ES File Explorer and terminal aren't letting me install apps. WiFi works fine in all apps if you put the watch in Airplane mode or if you disconnect your phone from the watch. Hopefully we get data and networking over Bluetooth at some point, it'd be awesome.
Anybody try any emulators? I'm interested in trying something like epsxe to maybe play RPGs or something simple that doesn't require too many buttons to play.
Click to expand...
Click to collapse
Thanks for the hint on DPI - your are right, it helps side loaded apps, but i noticed that it also makes better use of the google now cards. The text is slightly smaller, and you can get more info (like a text) visible at one time, but still not to small. Regardless of sideloading, i am really enjoying the change to 200DPi (though, it really helps for apps like alpine quest and such which now show the whole thing)

[Q] Change screen density in build.prop

I am trying to change the screen density, as the default 480 density is just ridiculous.
But editing the build.prop changes nothing, as I saw in another thread, I should be modifying the file that references my phone model which should be build.ze551.dual.2p3GHz.prop (Zenfone 2 4GB, 32GB, 2.3ghz, dual sim).
But even including the line: "ro.sf.lcd_density=360" (this line does not exist there, I have to add it). Nothing happens after reboot.
I believe that I am editing the correct file as I tried to add the line "qemu.hw.mainkeys=0" and after reboot I got screen software buttons.
but the density does not change. I know I could use the method of execute in adb: "adb shell wm density 360" but with this method the swiftkey keyboard software does not work correctly and I heard that changing the density with build.prop it would work.
Can someone help me ? I really want to change the density.
check this thread: http://forum.xda-developers.com/zenfone2/general/tip-adjusting-dpi-root-t3098690
aktentasche said:
check this thread: http://forum.xda-developers.com/zenfone2/general/tip-adjusting-dpi-root-t3098690
Click to expand...
Click to collapse
Thanks. but as I said this method is what I am trying to avoid because a lot of apps stops working correctly like Whatsapp, Instagram, Photo editing software, Swiftkey, power save app, etc.
I've done the build.prop method on a lot of other devices and it always work like a charm, everything works nice. But for some reason it is not working with Zenfone and I am trying to figure out why.
JuniorBR790 said:
Thanks. but as I said this method is what I am trying to avoid because a lot of apps stops working correctly like Whatsapp, Instagram, Photo editing software, Swiftkey, power save app, etc.
I've done the build.prop method on a lot of other devices and it always work like a charm, everything works nice. But for some reason it is not working with Zenfone and I am trying to figure out why.
Click to expand...
Click to collapse
I'm also having the same issue. I haven't been able to find any sort of solution for this either. I might try a custom ROM just do I can do the build.prop change for density.
Sent from my ASUS_Z00AD using Tapatalk

Categories

Resources