Related
Hi. If you are the sort of person that likes to peck away at the keyboard with your stylus then you might consider porting the Galaxy Note 8 keyboard
to your T mobile Galaxy Note 2. Actually it is fairlly finger friendly too and fun to play with as it has option for making split keyboard and floating keyboard. The zip file and instructions for it are in this thread. Please thank xperiacle as his hard work brings us this nice app.
http://forum.xda-developers.com/showthread.php?t=2228836
please check post #41 for full instructions on odex roms and thank that poster (andnote)!
The only differences for me is, when using xposed framework apps settings module, set dpi to 320 and set Screen(dp) to 800x1280 (I know it doesn't match GN2 but works ok. Perhaps someone can fix to give option of 720x1280)
EDIT: Don't forget to check out the writing recognition option! (added a screen shot)
Here are some screen shots from my T-Moble Note 2
I followed the instructions but get FC when trying to open Samsung Keyboard settings. Should I try to rename the old .apk and reflash?
EDIT: nope, that didn't get it working either. On Tweaked 2.0 (UVMB4).
Gwanatu said:
I followed the instructions but get FC when trying to open Samsung Keyboard settings. Should I try to rename the old .apk and reflash?
EDIT: nope, that didn't get it working either. On Tweaked 2.0 (UVMB4).
Click to expand...
Click to collapse
Did you follow the instructions in post #41 of the thread I referenced? I had added that reference as it had more complete instructions. Sorry if you tried this before reading that post as it is helpful.
Also make sure when you start out that your default keyboard is not samsung. Use an alternate keyboard to edit the samsung keyboard setting such that Key-tap sound is not checked (its in the advanced part of samsung keyboard settings). Apparently enabling Key-tap sound can cause FC. Anyways, once you disable Key-tap sound, make samsung keyboard default. One more thing. Did you wipe Dalvik cache?
mscion said:
Did you follow the instructions in post #41 of the thread I referenced? I had added that reference as it had more complete instructions. Sorry if you tried this before reading that post as it is helpful.
Also make sure when you start out that your default keyboard is not samsung. Use an alternate keyboard to edit the samsung keyboard setting such that Key-tap sound is not checked (its in the advanced part of samsung keyboard settings). Apparently enabling Key-tap sound can cause FC. Anyways, once you disable Key-tap sound, make samsung keyboard default. One more thing. Did you wipe Dalvik cache?
Click to expand...
Click to collapse
I tried everything but changing DPI. I assume then that this is only for Paranoid Android-type ROMs with per-app DPI then?
Gwanatu said:
I tried everything but changing DPI. I assume then that this is only for Paranoid Android-type ROMs with per-app DPI then?
Click to expand...
Click to collapse
I'm not using Paranoid Android ROM. I'm just using the basic BMB4, rooted, and philz recovery. I use Xposed framework to change dpi among other things.
Here is a link to Xposed installer and module for changing dpi
http://forum.xda-developers.com/showthread.php?t=2067303
mscion said:
I'm not using Paranoid Android ROM. I'm just using the basic BMB4, rooted, and philz recovery. I use Xposed framework to change dpi among other things.
Here is a link to Xposed installer and module for changing dpi
http://forum.xda-developers.com/showthread.php?t=2067303
Click to expand...
Click to collapse
Ah I see, sorry about that, I'll give that a shot.
Are you on DPI 320 and just flash the keyboard it will give good layout?
As im at DPI 240. And flashing this keyboard, the layout not align well. Plus, using app per settings giving bad alignment too.
jasonkhoo87 said:
Are you on DPI 320 and just flash the keyboard it will give good layout?
As im at DPI 240. And flashing this keyboard, the layout not align well. Plus, using app per settings giving bad alignment too.
Click to expand...
Click to collapse
Yes. I am using 320 dpi all the way. While I especially like the option of a floating keyboard, I find it's just tad too small but I still have it as my default (at least until the novelty wears out!) and switch keyboards as needed (I use hackers keyboard a lot because I need Ctrl, tab esc.. and thumb keyboard is nice in landscape) . Perhaps someone can come up with a more optimal configuration.
Should this work on a Sprint Note II also?
mscion said:
Hi. If you are the sort of person that likes to peck away at the keyboard with your stylus then you might consider porting the Galaxy Note 8 keyboard
to your T mobile Galaxy Note 2. Actually it is fairlly finger friendly too and fun to play with as it has option for making split keyboard and floating keyboard. The zip file and instructions for it are in this thread. Please thank xperiacle as his hard work brings us this nice app.
http://forum.xda-developers.com/showthread.php?t=2228836
please check post #41 for full instructions on odex roms and thank that poster (andnote)!
The only differences for me is, when using xposed framework apps settings module, set dpi to 320 and set Screen(dp) to 800x1280 (I know it doesn't match GN2 but works ok. Perhaps someone can fix to give option of 720x1280)
EDIT: Don't forget to check out the writing recognition option! (added a screen shot)
Here are some screen shots from my T-Moble Note 2
Click to expand...
Click to collapse
finally it work.. with 240dpi :good:
after more then 5 times rebooting to test the current dpi
My S Note will not open. It gives error "Unfortunately*S Note has stopped". FC. Other wise it works well with dpi to 320 and set Screen(dp) to 800x1280. I reflashed my rom. All is well. I would like the Note 8 keyboard though.
Babyexp said:
My S Note will not open. It gives error "Unfortunately*S Note has stopped". FC. Other wise it works well with dpi to 320 and set Screen(dp) to 800x1280. I reflashed my rom. All is well. I would like the Note 8 keyboard though.
Click to expand...
Click to collapse
One possibility is to try S Note for the Galaxy Note 8. I tried it and it does seem to work but I have not found the optimal dpi. Currently I use dpi 320 and Screen (dp) 800x1280 with no FC.
Here is a link to get the S Note for Galaxy 8 plus a treasure trove of other apps to test! Try and let others know your experience.
http://forum.xda-developers.com/showthread.php?t=2217662
EDIT:S BTW, S Note 8 seems to work nicely when setting apps dpi to 213 and screen (dp) to 800x1280 via xposed apps setting module. If you are finding that S Note FCs when starting up, a possible solution: If you have titanium backup, first delete the original S Note via TB. Then flash S Note 8 via recovery. Do a dalvik wipe cache, reboot and change settings as described. This has worked for others as well.
choco376 has pointed out that voice recording causes FC with S Note 8.
I noticed if you check permissions in the Xposed App Settings module you will see that there are quite a few missing
shared packages including app to record audio and others to integrate S Note 8 better with phone and other applications.
Perhaps if we could flash the S Voice app (among others) for Galaxy Note 8 that would go a long ways. Anyone know where to find this?
Thanks!
Is the function available on the Compact? I know it's possible due to it using the same processor as the Nexus 5, and it has the option for 'Hotword detection' in the voice settings so I'd guess it should be functioning, but I can't seem to get it to work, even after following this guide: http://www.cultofandroid.com/44949/enable-the-nexus-5s-ok-google-feature-outside-of-the-u-s-tip/
Could someone please shed some light on the situation?
Cheers
crimsonnight said:
Is the function available on the Compact? I know it's possible due to it using the same processor as the Nexus 5, and it has the option for 'Hotword detection' in the voice settings so I'd guess it should be functioning, but I can't seem to get it to work, even after following this guide: http://www.cultofandroid.com/44949/enable-the-nexus-5s-ok-google-feature-outside-of-the-u-s-tip/
Could someone please shed some light on the situation?
Cheers
Click to expand...
Click to collapse
You need the Google Now Launcher (default launcher on Nexus 5) to enable this functionality. It is only available on 4.4.
Sent from my Z1 Compact
hol17 said:
You need the Google Now Launcher (default launcher on Nexus 5) to enable this functionality. It is only available on 4.4.
Sent from my Z1 Compact
Click to expand...
Click to collapse
Ah ok, cheers, any idea what the hotword detection tickbox currently does then? Can we install the launcher on Jellybean with an .apk or something to get the functionality?
*EDIT* trying this: http://forum.xda-developers.com/showthread.php?t=2506488
*EDIT 2* won't even let me install 'PrebuiltGmsCore.apk'
crimsonnight said:
Ah ok, cheers, any idea what the hotword detection tickbox currently does then? Can we install the launcher on Jellybean with an .apk or something to get the functionality?
*EDIT* trying this: http://forum.xda-developers.com/showthread.php?t=2506488
*EDIT 2* won't even let me install 'PrebuiltGmsCore.apk'
Click to expand...
Click to collapse
I believe Google Search has the functionality built in but Google Now Launcher enables it to work. Unfortunately, I believe there is some key API code in Kit Kat that is required for this.
Sent from my Z1 Compact
Hi All,
Does anyone know of a good DPI for the Find 7a? the stock 480 is a bit big for me.
I now DPI is a subjective thing, but I don't want to pick one where apps don't run properly.
sniper-joe said:
Hi All,
Does anyone know of a good DPI for the Find 7a? the stock 480 is a bit big for me.
I now DPI is a subjective thing, but I don't want to pick one where apps don't run properly.
Click to expand...
Click to collapse
320 is probably way too low, and that's the next valid step down.
(In theory, 400 was added by Android 4.4, however while Android supports it, the Play Store does NOT so you'll encounter lots of app compatbility issues - see the various complaints stemming from the Z Ultra GPe running a 400 DPI configuration.)
Entropy512 said:
320 is probably way too low, and that's the next valid step down.
(In theory, 400 was added by Android 4.4, however while Android supports it, the Play Store does NOT so you'll encounter lots of app compatbility issues - see the various complaints stemming from the Z Ultra GPe running a 400 DPI configuration.)
Click to expand...
Click to collapse
I have just rebooted using 320 and it's perfect! Everything works fine!
By the way Entropy, do you have a find 7a? I have been following your work for a long time!
sniper-joe said:
I have just rebooted using 320 and it's perfect! Everything works fine!
By the way Entropy, do you have a find 7a? I have been following your work for a long time!
Click to expand...
Click to collapse
What app did you use to change DPI???
Stock rom or modded?
Mord0rr said:
What app did you use to change DPI???
Stock rom or modded?
Click to expand...
Click to collapse
The option to change the system DPI is built into Dirty Unicorns, however, I have used texdroider DPI app on stock roms, but sometimes stock ROMS throw a fit.
sniper-joe said:
The option to change the system DPI is built into Dirty Unicorns, however, I have used texdroider DPI app on stock roms, but sometimes stock ROMS throw a fit.
Click to expand...
Click to collapse
Ah!
That one i tried and it din`t work....
When I changed the DPI I ran somewhere around 400 and used a modified play store to get around the incompatible error. Then Google started updating the play store too much and the dev for the modified play store fell behind and I just went back to default DPI. When I find the thread I'll link it.
Find what? Who the heck is OPPO?
*edit*
http://forum.xda-developers.com/showthread.php?t=1839871
BriefingHello everyone! So, today I'm gonna present you Google Dialer and Contacts apps to our beloved Xperia Devices. I ported it today because I have nothing to do
P.S - WARNING!111!! ACHTUNG!!! IT'S JUST FOR 6.0+.
Guide how to install
Download it (the newest is ver. 2.0 zip) using this link
Place it somewhere and remember that location
Reboot to your recovey and flash it
Then enable it like default dialer in Default Apps menu
It's simple AF! Isn't it?
Credits which no one never reads
Google for Android and apps
Apple for innovations
Justin Bieber for motivating music
TWRP for stuff like recovery with which noobs can brick their devices by flashing this piece of **** presented here
Oh, and forgot - I really don't give any ****s about bricked stuff and penetrated, exploded anuses after flashing this. Also I don't care about stuff like "This thread is ugly, bla bla bla" - mate, just leave it ASAP if it hurts your eyes. Any trolls will be recognized like sonuvabitchez and will be kicked out ASAP. God bless you, but not me. Thx for your wasted time. XD
P.S. - it really works, just tried to make it funny a bit.
Thanks , Work perfectly on Z3 It has the call block feature which is missed by Sony
zaky1 said:
Thanks , Work perfectly on Z3 It has the call block feature which is missed by Sony
Click to expand...
Click to collapse
Great then, thx for feedback. Now I'm working on porting Google Camera with Nexus features like HDR+ etc, but it will be hard/nearly impossible. Need someone with Nexus 6P to give me needed camera libs and camera. Thx in advance.
Usually the Google dialler will have call connect vibrate, call waiting vibrate options, but these are missing in ur port.
alexdonwarez said:
Usually the Google dialler will have call connect vibrate, call waiting vibrate options, but these are missing in ur port.
Click to expand...
Click to collapse
Usually there is no any try to port that stuff to Stock Sony ROM, so I'm sorry about some missing stuff. Will look that. Thx for reporting
alexdonwarez said:
Usually the Google dialler will have call connect vibrate, call waiting vibrate options, but these are missing in ur port.
Click to expand...
Click to collapse
So it's ROM-based function, and if it's present in the ROM - you have ability to enable this function, otherwise it will not work in Google Dialer, not in other Dialer apps. Sorry for that.
I really appreciate your work. I love Google dialer app, however google InCallUI is missing. Is it possible to make Google InCallUI work?
deepu28792 said:
I really appreciate your work. I love Google dialer app, however google InCallUI is missing. Is it possible to make Google InCallUI work?
Click to expand...
Click to collapse
Strange, cause me I have Google's in-call instead of Sony's one. Did you set Google Dialer as main dialer app? If no, set it as default in settings > apps > default apps. Also give it all permission, if it asks for them. Waiting for feedback!
MotexT said:
Strange, cause me I have Google's in-call instead of Sony's one. Did you set Google Dialer as main dialer app? If no, set it as default in settings > apps > default apps. Also give it all permission, if it asks for them. Waiting for feedback!
Click to expand...
Click to collapse
Thanks Broda it works. I dint knew about this thing. Thanks a ton bro, Now its perfect.
deepu28792 said:
I really appreciate your work. I love Google dialer app, however google InCallUI is missing. Is it possible to make Google InCallUI work?
Click to expand...
Click to collapse
No its not posible in Xperia UI - its a part of Stock vanilla android.
dex87xda said:
No its not posible in Xperia UI - its a part of Stock vanilla android.
Click to expand...
Click to collapse
It's possible. Check previous post though.
If there will be any updates to either Dialer or Contact apps - let me know via PM, because I don't have enough time to check it by myself. In this way I will keep my port up to date. Thx in advance
New version Google Phone 9.0.154771926 is now avaliable on Google Play Store.
asior25 said:
New version Google Phone 9.0.154771926 is now avaliable on Google Play Store.
Click to expand...
Click to collapse
Okay, will update it in few minutes. Stay tuned.
asior25 said:
New version Google Phone 9.0.154771926 is now avaliable on Google Play Store.
Click to expand...
Click to collapse
Permissions/libs/apps are updated to latest versions. Check this zip and let me know if this works, cause due update it shouldn't work on 7.0- devices.
Currently used - works properly.
@MotexT is it possible yhu mod tha latest google dailer to have like tha incall in tha screenshots below (3rd picture in tha screenhot)?
thanks.....
New version Google Phone 9.0.155139499 ( only Dialer)
Will this work on Z5P Nougat
ytheekshana said:
Will this work on Z5P Nougat
Click to expand...
Click to collapse
What is your OS ?
Wysłane z mojego D6503 przy użyciu Tapatalka
I've been through the build.prop extremely thoroughly but can't find even a mention of the LCD density. Anybody have any luck with changing their DPI?
Had the same problem and also no luck with different apps. But "Le DPI changer" works for me.
noisyriver said:
Had the same problem and also no luck with different apps. But "Le DPI changer" works for me.
Click to expand...
Click to collapse
Just tried it, and no luck it won't work...
You have to be rooted, but I assume you are as you tried to change the build.prop. And you need to reboot after the change.
You can change dpi in adb without root. I'm kind of busy right now but it's easy to find on Google
Sent from my Moto Z Play using XDA Labs
noisyriver said:
You have to be rooted, but I assume you are as you tried to change the build.prop. And you need to reboot after the change.
Click to expand...
Click to collapse
Correct, phone is rooted. The problem is ro.sf.lcd_density isn't present anywhere in the build prop to edit. I've been setting my DPI this way on all my past phones and tablets, this time it's just not there for me to edit