Related
In order to increase your resolution on the arc you need the phone to be rooted and get root explorer from the market (You can use ADP too)
Here are the steps:
1. Open root explorer and navigate to /system/
2. Mount the folder as r/w
3. Long press the build.prop file and select edit in text editor
4. Scroll all the way to the bottom and look for r0.sf.lcd_density=240
5. Change it to r0.sf.lcd_density=194 (I find 194 works the best, d4rkwind prefers 180 see post#28)
6. Save and Exit
7. Reboot your phone and you should now have a higher resolution.
8. To ensure that all apps span full screen install spareparts from the market and uncheck "Compatibility Mode"
The stock launcher app will not work too well with the new resolution, Try ADW launncher as thats what I use.
Reserved for future use.
Or u could just get lcd density chsnger on market lol does same thing
Sent from my LT15i using XDA Premium App
rumy said:
In order to increase your resolution on the arc you need the phone to be rooted and get root explorer from the market (You can use ADP too)
Here are the steps:
1. Open root explorer and navigate to /system/
2. Mount the folder as r/w
3. Long press the build.prop file and select edit in text editor
4. Scroll all the way to the bottom and look for r0.sf.lcd_density=240
5. Change it to r0.sf.lcd_density=194 (I find 194 works the best)
6. Save and Exit
7. Reboot your phone and you should now have a higher resolution.
The stock launcher app will not work too well with the new resolution, Try ADW launncher as thats what I use.
Click to expand...
Click to collapse
@rumy - What Clock Widget is that?
pato_bato said:
@rumy - What Clock Widget is that?
Click to expand...
Click to collapse
Looks like Beautiful Widgets to me
How is it possible to increace the resolution ,since the hardware can't "afford it";Or am i missing something;
tasgr86 said:
How is it possible to increace the resolution ,since the hardware can't "afford it";Or am i missing something;
Click to expand...
Click to collapse
Dear Tasos you are wrong, with this magic trick your display turns into a retina display, the one that iphone4 use! And maybe capable of 3D.. lol
Does 194 work Facebook and Market? I tried 210 (my favorite) previously but Facebook and Market didn't fill the screen which made it look quite awful..
Thanks for this guide worked like a charm
Stor-Anders said:
Does 194 work Facebook and Market? I tried 210 (my favorite) previously but Facebook and Market didn't fill the screen which made it look quite awful..
Click to expand...
Click to collapse
It does, you need to download spareparts from the market and uncheck compatibility mode.
pato_bato said:
@rumy - What Clock Widget is that?
Click to expand...
Click to collapse
https://market.android.com/details?id=com.androidapps.widget.weather2&feature=search_result&pli=1
festa20 said:
Or u could just get lcd density chsnger on market lol does same thing
Sent from my LT15i using XDA Premium App
Click to expand...
Click to collapse
For some reason LCD density changer did not work and slowed my system down.
Have not tried it on .184 firmware, the issue was on .181
It works fine on mine the lcd density thing organist I having seen any lag or slowing down.god knows im on 181 also
Sent from my LT15i using XDA Premium App
im curious towards doing this as it looked good on my old HD2, however im curious to see how some of the stock apps, specifically the Music and Messaging app looks with this density..would you mind taking a screenshot of those perhaps?..
thanks.
reptile64 said:
Dear Tasos you are wrong, with this magic trick your display turns into a retina display, the one that iphone4 use! And maybe capable of 3D.. lol
Click to expand...
Click to collapse
I've tried!It's interesting!But it doesn't increase the resolution.It's actually something like zooming out.You can find this feature in windows also ,as a magnifier.
mhuaaaaa! ! i think fontchanger from miui in the market is very simple and if you want apli fully fonction in devtool check disable compatibilyt for full screen. and haaahaaa too funy
x10iachotjanblisshdluciddark.bb58
So can someone tell me what the best resolution is for this?
My screens at 194dpi:
tasgr86 said:
I've tried!It's interesting!But it doesn't increase the resolution.It's actually something like zooming out.You can find this feature in windows also ,as a magnifier.
Click to expand...
Click to collapse
Ακριβώς!
HELP!!!
ARRRRRRRRRRRRRRR! Just did this and it worked fine. But my touch screen is now going crazy! I can't tap widgets or swipe screen because even a single finger held still against the screen makes it freak out! HELP!!!
Update: it seems to have sorted itself out, it's not doing it any more anyway... :-S
Hi all,
I´m still trying to find a way to get my hands on a Nexus 7 here in europe ... (not UK ;-)) ...to test my app NFC ReTag FREE
However, according to my dev console, there should be already some Nexus 7 users with NFC ReTag out there, and till today no bugs were reported, but I would like to double check it and receive some early feedback from the first Nexus 7 users ;-)
It´s not tested on the Nexus 7 yet and the UI is not optimized for the screen size (major UI changes are under development anyway ) but in general it should work without any problems.
Has anyone tried the app and could give some feedback ???
Video how it should work : https://www.youtube.com/watch?v=n7TrkZ2hzn0
No one with a NFC tag + a Nexus 7 + 5min time?
Sent from my GT-I9300 using xda premium
ascsa said:
Hi all,
I´m still trying to find a way to get my hands on a Nexus 7 here in europe ... (not UK ;-)) ...to test my app NFC ReTag FREE
However, according to my dev console, there should be already some Nexus 7 users with NFC ReTag out there, and till today no bugs were reported, but I would like to double check it and receive some early feedback from the first Nexus 7 users ;-)
It´s not tested on the Nexus 7 yet and the UI is not optimized for the screen size (major UI changes are under development anyway ) but in general it should work without any problems.
Has anyone tried the app and could give some feedback ???
Video how it should work : https://www.youtube.com/watch?v=n7TrkZ2hzn0
Click to expand...
Click to collapse
Just gave it a try. Apart from your logo looking a bit stretched all the text and buttons where correctly placed and I have scanned a few NFC tags and had them launch some apps and turn WiFi and Bluetooth on and off. I did have to allow it to turn them on and off each time seemed to be no way of granting access forever.
Quick question can you have it launch a specific web page based on the Tag not just Chrome?
Many thanks for your feedback!
To get rid of the Bluetooth security pop up, try the "on silent" or "toggle silent " parameter... Wifi should not have such a security pop up..
To open a website, use the "browse" activity with a parameter like "forum.Xda-developers.Com"... Without the quotes...
Sent from my GT-I9300 using xda premium
Anyone with additional feedback ?
Just given it a go, using my UK Barclaycard which has an NFC chip in. Set it to bring up the Barclaycard website using teh Browse action type which worked ok for a normal website but if you add https:// at the start it doesn't work.
Also when adding a tag there is an option for templates, when clicked I assume it should list some preset types but none are coming up ?
Nice app though, cool idea
CharlesW123 said:
Just given it a go, using my UK Barclaycard which has an NFC chip in. Set it to bring up the Barclaycard website using teh Browse action type which worked ok for a normal website but if you add https:// at the start it doesn't work.
Also when adding a tag there is an option for templates, when clicked I assume it should list some preset types but none are coming up ?
Nice app though, cool idea
Click to expand...
Click to collapse
Yeaah, i probably should add a FAQ or some additional help textes
For the HTTPS issue, have a look at the settings and use the "disable http prefix" option ...
Templates: it´s an option to store your own tags as templates ... no preconfigured templates available (perhaps I should add a hint within the next update )
So it seems, to work as expected (at least for me ) on the nexus 7 ...
Again, many thanks for your feedback !!! :good:
i changed this line "ro.sf.lcd_density= 160" of the build.prop file in system folder and it changed my bar to the look of the xoom tablet. i changed the line ro.sf.lcd_density= 150 and it was too small and i took it back up to 160 and it looks a lil better. i didn't take it under 150 so i don't know how low and how high you can decrease and increase it to. i think i heard if you change the line i just told you about than it will tell you some apps in the market store are compatible. i know quick office pro hd works on the nexus seven but im tring to get it to show up in the Google play store so i can purchase it. is what i heard true, if so than what value should i change the line to?
Sent from my Nexus 7 using XDA Premium HD app
ok the value 200 works and i can purchase the quick office hd.
Sent from my Nexus 7 using XDA Premium HD app
ronlsjr said:
ok the value 200 works and i can purchase the quick office hd.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
But that doesn't give the tablet interface (Xoom style)
FYI - I've read (have *not* confirmed though) that if you un-install and re-install the Play store *after* resetting your DPI value, that it'll use your new dpi value accordingly, so that you can see all apps the Play store.. Again, I haven't tested - just reporting what I read...
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
ronlsjr said:
i changed this line "ro.sf.lcd_density= 160" of the build.prop file in system folder and it changed my bar to the look of the xoom tablet. i changed the line ro.sf.lcd_density= 150 and it was too small and i took it back up to 160 and it looks a lil better. i didn't take it under 150 so i don't know how low and how high you can decrease and increase it to. i think i heard if you change the line i just told you about than it will tell you some apps in the market store are compatible. i know quick office pro hd works on the nexus seven but im tring to get it to show up in the Google play store so i can purchase it. is what i heard true, if so than what value should i change the line to?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I tried the DPI hack... and it's just that. A hack. All the apps have really small text, and layout, on basically every app. Even if you up the text size, it just doesn't look right...the layout is still too small.
The only real solution is the Hybrid rom, ParanoidAndroid. It took a while before I finally decided to try it, but I'm glad I finally did. It's the best ROM I've tried so far, and I don't think I will be able to switch to a new ROM in the future, unless it lets me set DPI for individual apps. In addition to DPI it lets you change the layout of the app. [the devs usually have 3 modes for the apps, so that it can run on a phone, tablet, or whatever..] so you can even make the Tablet UI with the default text size. Or you can put the DPI down a little, like I did, because I like the status bar a little smaller than full-size.
mvmacd said:
I tried the DPI hack... and it's just that. A hack. All the apps have really small text, and layout, on basically every app. Even if you up the text size, it just doesn't look right...the layout is still too small.
The only real solution is the Hybrid rom, ParanoidAndroid. It took a while before I finally decided to try it, but I'm glad I finally did. It's the best ROM I've tried so far, and I don't think I will be able to switch to a new ROM in the future, unless it lets me set DPI for individual apps. In addition to DPI it lets you change the layout of the app. [the devs usually have 3 modes for the apps, so that it can run on a phone, tablet, or whatever..] so you can even make the Tablet UI with the default text size. Or you can put the DPI down a little, like I did, because I like the status bar a little smaller than full-size.
Click to expand...
Click to collapse
Hi, I'm using the PA ROM right now,and I'm just wondering what you did to get the PlayStore to allow the download. I know you can use the PA settings to change DPI and workspace so can I do it in there? Or do I have to edit the build.prop file? I bought it for the Asus Transformer TF101. I haven't been able to use it for m NExus 7 and I really do want to check it out .
A better option is to create a /data/local.prop file (rw-r--r--) with the following in it:
# /data/local.prop
# ref: http://forum.xda-developers.com/showthread.php?p=29413138
qemu.sf.lcd_density=160
Click to expand...
Click to collapse
This has the benefit of affecting only the display and not how Google Play sees the Nexus
Sent from my Nexus 7
BillGoss said:
A better option is to create a /data/local.prop file (rw-r--r--) with the following in it:
This has the benefit of affecting only the display and not how Google Play sees the Nexus
Sent from my Nexus 7
Click to expand...
Click to collapse
Is there a way to get Google Play to see the nexus at a 10" tablet temporarily, so I can install QuickOffice Pro HD?
Bonisaur said:
Is there a way to get Google Play to see the nexus at a 10" tablet temporarily, so I can install QuickOffice Pro HD?
Click to expand...
Click to collapse
Hmm.... They might be using the model number to decide whether the app is compatible, so I don't think this will work, but you can try:
Open Google Play, press Home, press Recents, long-press Google Play in the list, then select Hybrid settings.
Leave the DPI alone [it should be at 213], swype over to the "Layout." In the drop down menu, select the highest value [should be 1000px, or maybe 800px]. Then tap the Apply button [left of the top-right corner].
Bonisaur said:
Hi, I'm using the PA ROM right now,and I'm just wondering what you did to get the PlayStore to allow the download. I know you can use the PA settings to change DPI and workspace so can I do it in there? Or do I have to edit the build.prop file? I bought it for the Asus Transformer TF101. I haven't been able to use it for m NExus 7 and I really do want to check it out .
Click to expand...
Click to collapse
You don't have to do anything, Google Play runs by default at stock DPI [213], so on ParanoidAndroid (unless you change it), it works out of the box.
Thanks for the help. Well I ended up trying to edit the DPI and/or the layout settings in different combinations while rebooting my tablet each time. I even changed the build.prop to see if I could download it. Nothing worked so I set it back to default/stock. Yet, when I looked online to "install" to device from the Google Play Store website, it worked for some reason. I have no idea what I did...
Anyway, on the side , since I edited the build.prop, do I need to do anything else other than reverse the changes? I switch the line back from 160 to 213. From what I searched that seems to be it...
As the subject says. Got some problems with it, and I was wondering if anyone else was using it without any problems?
Sent from my Nexus 4 using XDA Premium HD app
i am using it on my Nexus 4, befor on my Samsung S2 and Sony Arc - i´ve got no problem.
Connect Bot ersion 1.7.1 with the latest VNC Release
I am using irssiconnectbot.
But I guess it would be helpful if you specify your problems.
I'm using irssiconnectbot without any problems whatsoever.
Sent from my Nexus 4 using xda premium
hey_malik said:
I am using irssiconnectbot.
But I guess it would be helpful if you specify your problems.
Click to expand...
Click to collapse
Sorry, just got home now. Basically the problem is with private keys. I generate a private key, copy the public key to my router, and the private key always fails! I can't understand it because I've done this process hundreds of times with other devices and it works fine. It's not just Connectbot, I also tried Juice-SSH to see if that would help, but it's the same problem, the key fails.
I'm honestly doing my nut over this, I can't figure out what the problem could be!
Any input would be massively appreciated!
Cheers
Ian
iang123 said:
Sorry, just got home now. Basically the problem is with private keys. I generate a private key, copy the public key to my router, and the private key always fails! I can't understand it because I've done this process hundreds of times with other devices and it works fine. It's not just Connectbot, I also tried Juice-SSH to see if that would help, but it's the same problem, the key fails.
I'm honestly doing my nut over this, I can't figure out what the problem could be!
Any input would be massively appreciated!
Cheers
Ian
Click to expand...
Click to collapse
I use ConnectBot v1.7.1.2010.10.08 with a 4096 bit RSA key to connect to ubuntu linux without issue.
I copied my public key (openssh format) and pasted it into a new Gmail draft message. I then added it to the file ~/.ssh/authorized_keys
Make sure the entire key is one line and some text editor did not add <CR>'s or <LF>'s to the pub key...
It's why I use vim and Notepad++ as editors.
SpookyTunes said:
I use ConnectBot v1.7.1.2010.10.08 with a 4096 bit RSA key to connect to ubuntu linux without issue.
I copied my public key (openssh format) and pasted it into a new Gmail draft message. I then added it to the file ~/.ssh/authorized_keys
Make sure the entire key is one line and some text editor did not add <CR>'s or <LF>'s to the pub key...
It's why I use vim and Notepad++ as editors.
Click to expand...
Click to collapse
That's the thing. I do the same thing, copy it into a gmail draft them paste it into DD-WRT authorised keys. I think the most frustrating thing, is that it works fine with my N7, HTC Desire S but not with the N4, and I am not doing anything different.
I have triple checked the public key, and nothing appears to be added.
Cheers
Ian
Or you could set it up on a terminal emulator if you can find the binaries, and the libraries. That's how I'm doing it.
Hi,
I'm Paul one of the two developers of JuiceSSH.
One thing to check that often catches people out is that SSH can be very fussy on permissions on the home directory, the .ssh directory and the authorized_keys file.
Try:
chmod 700 ~;
chmod 700 ~/.ssh;
chmod 600 ~/.ssh/authorized_keys
It doesn't matter about the permissions on the device/JuiceSSH side.
Does the key work if you try and SSH in from your PC - ie is it just from your phone you're having problems?
Edit to add: My girlfriend uses an N4 and i've tested SSH keys numerous times on it during our development/testing so I doubt it's a problem with the Nexus 4 itself.
JuiceSSH said:
Hi,
I'm Paul one of the two developers of JuiceSSH.
One thing to check that often catches people out is that SSH can be very fussy on permissions on the home directory, the .ssh directory and the authorized_keys file.
Try:
chmod 700 ~;
chmod 700 ~/.ssh;
chmod 600 ~/.ssh/authorized_keys
It doesn't matter about the permissions on the device/JuiceSSH side.
Does the key work if you try and SSH in from your PC - ie is it just from your phone you're having problems?
Edit to add: My girlfriend uses an N4 and i've tested SSH keys numerous times on it during our development/testing so I doubt it's a problem with the Nexus 4 itself.
Click to expand...
Click to collapse
Hi Paul,
Thanks for replying. I don't think it's the permission because all of my other devices work fine. I've tried the same key from my N7, and my PC and it works fine. But, as you say, it may not be the N4 as others have used it and it works fine.
It's very frustrating in the fact that it seems to be isolated to just my N4, making support pretty difficult!
Cheers
Ian
iang123 said:
Hi Paul,
Thanks for replying. I don't think it's the permission because all of my other devices work fine. I've tried the same key from my N7, and my PC and it works fine. But, as you say, it may not be the N4 as others have used it and it works fine.
It's very frustrating in the fact that it seems to be isolated to just my N4, making support pretty difficult!
Cheers
Ian
Click to expand...
Click to collapse
Another good option is to run sshd on the server in debug mode and take a look at the more verbose logs of what is going on behind the scenes.
The safest way to do it is not to mess with the currently running sshd process or configuration (especially if it's a remote machine) but to spawn a new sshd server in foreground+debug mode on a different port number by running:
sudo /usr/sbin/sshd -p 2222 -D -d -e
Then setting up JuiceSSH to connect to port 2222 instead.
This will need port 2222 opening on any firewalls you have though.
If that still doesn't give any better clues feel free to paste the log here and i'll take a look.
Also I could give you a JuiceSSH APK file that has very verbose ssh logging turned on however you would need to have adb setup and installed on your PC in order to view the logs.
Thanks.
Paul
Cheers again Paul. I'm not too sure about being able to open another ssh service on my router. If you could help me out with that apk that would be great. Would it still get the logs even if I am making the connection to my router?
Cheers
Ian
Sent from my Nexus 4 using XDA Premium HD app
iang123 said:
Cheers again Paul. I'm not too sure about being able to open another ssh service on my router. If you could help me out with that apk that would be great. Would it still get the logs even if I am making the connection to my router?
Cheers
Ian
Sent from my Nexus 4 using XDA Premium HD app
Click to expand...
Click to collapse
Hi Ian,
I have PM'd you a link to the debug version and some instructions.
Let me know how you get on.
Paul
It seems as though Google killed Miracast compatibility now that Chromecast does screen mirroring. If you are like me and have one of each devices, you still may want to mirror to a Miracast device.
Required: Root
Navigate with a root explorer to your build.prop file located at /system/build.prop
Add the following line to the file:
Code:
persist.debug.wfd.enable=1
Save your build.prop file and reboot.
You should now see Settings > Display > Cast Screen > Menu > Enable Wireless Display
You should be good to go :good:
As noted in another thread, this will not work for netflix. It does work with watchespn, youtube, and amazon instant video.
Try Toaster cast on the play store.....
will this edit make screen cast work with the roku3? will try that prop build edit
confirm this works! i can do cast screen to my ROKU 3
I did the buildprop edit. Phone connects to TV but the sound is from the phone. Anyone else have this? Thanks
Sent from my Nexus 6 using Xparent Blue Tapatalk 2
treIII said:
I did the buildprop edit. Phone connects to TV but the sound is from the phone. Anyone else have this? Thanks
Sent from my Nexus 6 using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
That's actually kind of cool. That would solve my late night movie watching where I want to watch on the big screen but have to turn the volume low. Is the audio synced at least?
biggiestuff said:
That's actually kind of cool. That would solve my late night movie watching where I want to watch on the big screen but have to turn the volume low. Is the audio synced at least?
Click to expand...
Click to collapse
Haha. Yeah ditto!
The problem I Post d about sound only coming from the phone was because of viper android sound mod. I deleted that as it also made my headphone jack inoperable unless I had a 3.5mm jack with a mic plug.
Sent from my Nexus 6 using Xparent Blue Tapatalk 2
Does this work on 5.1? Thanks
Sent from my Nexus 6 using Xparent Blue Tapatalk 2
Yes, It work with Moto g lollipop 5.1 Gpe and Ezcast dongle. But the video lags a lot with MX player... And there after the all mirroring lags...
Any settings need to be twisted...
treIII said:
Does this work on 5.1? Thanks
Sent from my Nexus 6 using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
I added this initially when I couldn't get my EzCast working however, I don't seem to need it now. I can full screen cast normally on 5.1, even though performance is poor
where do I put this code at and how do I save it
GPS3 said:
It seems as though Google killed Miracast compatibility now that Chromecast does screen mirroring. If you are like me and have one of each devices, you still may want to mirror to a Miracast device.
Required: Root
Navigate with a root explorer to your build.prop file located at /system/build.prop
Add the following line to the file:
Code:
persist.debug.wfd.enable=1
Save your build.prop file and reboot.
You should now see Settings > Display > Cast Screen > Menu > Enable Wireless Display
You should be good to go :good:
Click to expand...
Click to collapse
.......
.. Were do I put dis code at and how to save it
Loudpack said:
.......
.. Were do I put dis code at and how to save it
Click to expand...
Click to collapse
Be careful what you are doing, because it clearly says where to add it- in the build.prop file in /system/ folder, it also says add the "following line", so you know what to edit in the build.prop file. simply add the line in the bottom to keep it clear from everything else. be sure to make a back up copy of the build.prop file in case you accidentally delete something an forget what it was...very possible!
I am wondering if it is possible to enable this in the same way it was possible to enable wireless tethering using adb.
v--The way you fix wireless tethering is to do the following--v
Start an adb shell: adb shell
In the adb shell, run this command: settings put global tether_dun_required 0
So why can't we do the same for build.prop?
Can anyone verify that if I were to do the following it would do the same thing?
settings put build.prop persist.debug.wfd.enable 1
or something similar?
Android Marshmallow
I came across this thread when looking for a solution to the same issue with enabling wireless display. I am writing to let anyone who this helps know that this solution still works with Android Marshmallow.
Thank you GPS3 for supplying this solution.
marcjc said:
I came across this thread when looking for a solution to the same issue with enabling wireless display. I am writing to let anyone who this helps know that this solution still works with Android Marshmallow.
Thank you GPS3 for supplying this solution.
Click to expand...
Click to collapse
What about the sound output?
Sent from my Nexus 6 using Tapatalk
blinqipa said:
What about the sound output?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I have an first gen Amazon FireTV which is hooked up to my surround sound and when I cast to it using the wireless display the sound goes over my surround sound system without issue. For more info, my N6 is currently running 10/27 - Cataclysm ROM (which did not have the wireless display option, until I followed this OP)
-Marc
I tried doing this but it said I did not have enough space and couldn't be saved, what do I do?
G
GPS3 said:
It seems as though Google killed Miracast compatibility now that Chromecast does screen mirroring. If you are like me and have one of each devices, you still may want to mirror to a Miracast device.
Required: Root
Navigate with a root explorer to your build.prop file located at /system/build.prop
Add the following line to the file:
Code:
persist.debug.wfd.enable=1
Save your build.prop file and reboot.
You should now see Settings > Display > Cast Screen > Menu > Enable Wireless Display
You should be good to go :good:
Click to expand...
Click to collapse
Sound only work....video not comming....please help
Sent from my Moto E using XDA Free mobile app
nabajyoti_bera said:
G
Sound only work....video not comming....please help
Sent from my Moto E using XDA Free mobile app
Click to expand...
Click to collapse
Most likely you are trying to cast protected content. Google play movies does this and i believe netflix too...maybe others but I cant recall. Anyway there is no way around playing DRM protected content through miracast.