(First off, I'm not 100% certain that this thread is in the right place. Devs, please move if necessary.)
I have a SM-T210 that I have recently flashed the NoleKat_v2.1 (KitKat 4.4.2) build on, and while I'm 90% happy with it, there is one small annoying thing that is bothering me and I wanted to see if there was a work-around available that I don't know about and/or whether I'm doing something wrong.
One of my favorite features of the Galaxy Tab, something that I had learned to lean on, was the autocomplete function. I know this new build has the autocomplete--I've found it works on SOME of the functions, but ONLY certain functions. It no longer works in email, Facebook, or several other apps where I found it useful. I have gone through my settings and can't seem to find a control to turn it on or off.
Any input would be appreciated.
I found the "Android Auto Complete Tutorial" on the tutorialspoint website. (I'd post the link, but XDA does not let me post outside links because I've posted less than 10 posts). I was wondering if their tutorial could be used to make autocomplete work on my Galaxy Tab.
Related
I'm sorry if this has already been debated elsewhere. I did search and try to locate threads on this already, but didn't come up with anything which (seemed) relevant to this problem.
If anyone has a link handy for another thread which already discusses this, I'll close the thread if that is wanted.
With that said... Here's my issue.
As stated elsewhere, one of the main things which excited me about Gingerbread was the ability to do native SIP dialing. About time, I say! Now I've flashed Gingerbread on my SGS and so far the results has been below underwhelming.
From what I can tell this is how you get SIP/VoIP/Internet calling on your phone using Gingerbread:
1. Sign up for Google Voice.
2. Install Google Voice and sign in.
3. Voila. Your Gingerbread Android-device now has a bunch of SIP settings and options.
This is ofcourse, unless your manufacturer has somehow crippled your phone's software.
That might be the case with Samsung's firmware, but I wouldn't know because the steps outlined above is absolutely impossible for anyone outside the US. You cannot sign up for Google Voice anywhere else. End of story.
So. Is this for real? Did Google release a smartphone OS for worldwide consumption, touting "native SIP", native internet calling as feature and then implement it in a way which means it will only work in one country, all else be damned?
I seriously find this very hard to believe. There has to be a way to get this functionality up and running otherwise. Seriously? The internet maestros at Google implements a core OS-level function tied to (one) geo-location? Is third-party solutions ala Sipdroid the solution for everyone else?
So... Please tell me I am completely mistaken and that there are steps for getting SIP running on my phone, despite me not have an adress of residency ending in "US".
Any hints or links in any direction so that I can actually get to try this out would be über appreciated.
Bump.
I realize posting this while Europa were getting ready for sleep and only US-people were around might have been bad timing.
Just bumping this again to see if there's any more response. I can't seriously be the only one wondering about this.
If bumping is severely against forum policies, let me know and I'll make a note of it and wont do it again.
http://forum.xda-developers.com/showthread.php?t=1043016
Use this zip as an update from CWM recovery, enables the menu "Internet call settings" under "Call settings".
Works on odex and deodex ROMS [I have the same JVB as the OP]
Problem solved
Thanks Vinnie.
Since I already have some framework-res.apk dependent mods, I just pushed the permissions-file as mentioned in that thread, and now I have "Internet calling options" available.
Yes, I realize this will only work while on wifi and SIP over 3G will be disabled, but at least it gives me something to experiment with so that later I will know if handing over my other mods for 3G VoIP/SIP will be worth it.
Thanks for the response and handy link. Now if XDA had better search, I might not have needed to pollute the forums with duplicates like this
Edit: Checked the entire thread and saw that there is an update.zip with eyecandy as well. Will try it out later.
Hello everybody,
just started a temporary sale for NFC ReTag PRO...
Use any NFC tag (write protected and re-writable) to trigger multiple functions on your device!
You can use this app to associate multiple functions (e.g. toggle Wlan, Bluetooth, Mobile Data, Airplane mode, start navigation,run Tasker task, launch any installed app, use media buttons, call a phone number, add a timestamp, calendar entry and many more) to a specific NFC Tag via an app internal database.
Get it NOW and save some money
Link to the Support thread:
forum.xda-developers.com/showthread.php?t=1477138http://
Free version also available !
Nice and first! Downloading now...
Text to speech bug
Hi all,
I've come across a weird bug that once i have run the "speak current time" actions under the labs section, my phone continues to speak the time for other various actions (eg opening/closing folders, setting the alarm etc).
So far there seems to be no way of stopping it, even killing the Google text to speech service does nothing.
Anyone else with this problem or any solutions?
Regards
G
GenePaton said:
Hi all,
I've come across a weird bug that once i have run the "speak current time" actions under the labs section, my phone continues to speak the time for other various actions (eg opening/closing folders, setting the alarm etc).
So far there seems to be no way of stopping it, even killing the Google text to speech service does nothing.
Anyone else with this problem or any solutions?
Regards
G
Click to expand...
Click to collapse
Hi G,
received your e-mail and replied this via e-mail a couple of minutes ago ...
Hi Gene,
No, you are the first reporting this. There is no Retag background service which could cause this and NFC Retag doesn´t change a TexttoSpeech setting, therefore I would say it´s not related, but stranger things had happen.
First thing I thought, it´s probably related to the CAR Mode ... a lot of devices speak a lot of things (Sms received, folder opened etc. ) while in car mode..annoying and mostly unexpected ... the first time it happen to me, I was completely clueless what was causing this and how to disable.. So please check if the car mode is enabled.
Second thought was the Standard Android Accessibility feature, please check under Settings--> Accessibility that the TalkBack option is disabled (provides spoken feedback for blind users ).
If this doesn´t help, reboot your device and please check again...If the issue still occurs, could you please give us some more details (device, firmware version, etc.) and if possible a log file, so we could analyze this in detail?
ascsa said:
Hi G,
received your e-mail and replied this via e-mail a couple of minutes ago ...
Hi Gene,
No, you are the first reporting this. There is no Retag background service which could cause this and NFC Retag doesn´t change a TexttoSpeech setting, therefore I would say it´s not related, but stranger things had happen.
First thing I thought, it´s probably related to the CAR Mode ... a lot of devices speak a lot of things (Sms received, folder opened etc. ) while in car mode..annoying and mostly unexpected ... the first time it happen to me, I was completely clueless what was causing this and how to disable.. So please check if the car mode is enabled.
Second thought was the Standard Android Accessibility feature, please check under Settings--> Accessibility that the TalkBack option is disabled (provides spoken feedback for blind users ).
If this doesn´t help, reboot your device and please check again...If the issue still occurs, could you please give us some more details (device, firmware version, etc.) and if possible a log file, so we could analyze this in detail?
Click to expand...
Click to collapse
Hi ascsa,
Thanks i got your email. Great to see such quick response from developers. I wasn't expecting it, hence the post here as well.
Just to clarify for any other readers, i'll repeat what i sent in my reply email to you.
Driving mode and talkback are disabled on my device.
I found a temporary fix by clearing the data from Application Management->All->Google text to speech service, but it then randomly starts again at a later time. I think the fault may lay more with Android than any app as there are a couple of other applications out there having the same issue. Something about Android calling the wrong service (text to speech) when various apps are started.
For your and others information, my device is a Samsung Galaxy S3 GT-I9300T Android 4.1.2 Stock Vodafone AU ROM, rooted. Baseband I9300TDUELL2.
Cheers
G
GenePaton said:
Hi ascsa,
Thanks i got your email. Great to see such quick response from developers. I wasn't expecting it, hence the post here as well.
Just to clarify for any other readers, i'll repeat what i sent in my reply email to you.
Driving mode and talkback are disabled on my device.
I found a temporary fix by clearing the data from Application Management->All->Google text to speech service, but it then randomly starts again at a later time. I think the fault may lay more with Android than any app as there are a couple of other applications out there having the same issue. Something about Android calling the wrong service (text to speech) when various apps are started.
For your and others information, my device is a Samsung Galaxy S3 GT-I9300T Android 4.1.2 Stock Vodafone AU ROM, rooted. Baseband I9300TDUELL2.
Cheers
G
Click to expand...
Click to collapse
No Problem ... ... but let´s move to the official support thread (http://forum.xda-developers.com/showthread.php?t=1477138&page=100) ...because this is an old thread ...NFC Retag PRO is currently NOT on sale ... and we shouldn´t confuse the users ...
Just to clarify for any other readers, my e-mail answer to your last post :
The Galaxy S3 GT-I9300 (international model) is one of our main testing devices. Not sure if, there is a problem with the Vodafone Rom or the Australian T model, but it´s working fine here on 4.1.2.
Had a short look at our code and the official api and everything seems fine ... but without a log file or better a device on which we could reproduce the error it´s nearly impossible to be sure ...However, you mentioned it happens with other apps, too , so I would bet on some Vodafone "enhancements" ...
Btw. have you tried the Samsung TTS engine (settings--> language& input -->text-to-speech output--> preferred engine) instead of the Google engine?
I notice there are several versions of tasker. Which do I need?
Muscipula
Sent from my SM-G903F using Tapatalk
Just recently pulled my old DS7 out of the corner and after seeing, nvflashed this really great Unofficial CM10.1 for Dell Streak 7 ROM on it. Works great, apart from the one tiny problem - it thinks it's a phone ... I already used Uninstall Master to remove some Phone features, such as: SIM Toolkit(it's called Mobile Data i think?), Messaging and Mobile Network Configurator. Was wondering how or where can I change or modify the settings related to how the Cyanogenmod acts as a Phone or a Tablet so that many apps from Play Store wouldn't default to the portrait mode.
On a sidenote - thanks to giveen and anyone involved in making this really awesome CM port to DS7 :good:
karlis1989 said:
Just recently pulled my old DS7 out of the corner and after seeing, nvflashed this really great Unofficial CM10.1 for Dell Streak 7 ROM on it. Works great, apart from the one tiny problem - it thinks it's a phone ... I already used Uninstall Master to remove some Phone features, such as: SIM Toolkit(it's called Mobile Data i think?), Messaging and Mobile Network Configurator. Was wondering how or where can I change or modify the settings related to how the Cyanogenmod acts as a Phone or a Tablet so that many apps from Play Store wouldn't default to the portrait mode.
On a sidenote - thanks to giveen and anyone involved in making this really awesome CM port to DS7 :good:
Click to expand...
Click to collapse
The reason why it is that way is because there are 4G models of the DS7
giveen said:
The reason why it is that way is because there are 4G models of the DS7
Click to expand...
Click to collapse
Understandable, but since I have a Wi-Fi only version I wanted to know if It's possible to change this in form of a setting or a few lines inside a configuration file without involving compiling. I even faintly remember stumbling upon something like this on a CM9 version I had on my old Xperia MT15i Neo ... if only I could remember or find where or how (currently strolling through the developer and CM10 related menus) - deleted my Xperia related bookmarks when I sold it.
p.s. - people mentioned some problems with the on-screen keyboard disappearing as described in one of the posts on the main CM10.1 thread, I've noticed them myself too and they tend to be application specific ... it feels like the keyboard crashes or force-closes due to not enough memory, like in lighter applications the keyboard works fine, but when trying to use the keyboard for writing for example a post in the comments section in a website will most likely result in keyboard disappearing after first input character.
So I am still trying to figure out why you started a new thread about this and what your question is.
To remove mobile data completely requires a new compile, something that cannot be done right now for a variety of reasons.
I guess I simply went too far off topic while trying to explain why I'm writing here... sorry.
So, to clear things up, the question still remains the same - what can I do to make it act more like a tablet and less like a phone on my Wi-Fi only DS7. So what I'm trying to find in the developer and CM menus is if I can more or less simply switch between some sort of "phone" and "tablet" mode so that some applications from Play store wouldn't default to portrait view mode.
And I noted that I've already uninstalled/disabled (call it how you want - I can restore them from the Unnstallers Recycle Bin if something weird starts to occur) some of the system .apks and as You already pointed out:
To remove mobile data completely requires a new compile, something that cannot be done right now for a variety of reasons.
Click to expand...
Click to collapse
... so thanks for clarifying that and no need to do any special versions - it's just fine how it is now. I didn't come here to request anything to be compiled or modified for me but just to ask for info, heck, I wasn't even expecting You to be answering on this thread.
karlis1989 said:
I guess I simply went too far off topic while trying to explain why I'm writing here... sorry.
So, to clear things up, the question still remains the same - what can I do to make it act more like a tablet and less like a phone on my Wi-Fi only DS7. So what I'm trying to find in the developer and CM menus is if I can more or less simply switch between some sort of "phone" and "tablet" mode so that some applications from Play store wouldn't default to portrait view mode.
And I noted that I've already uninstalled/disabled (call it how you want - I can restore them from the Unnstallers Recycle Bin if something weird starts to occur) some of the system .apks and as You already pointed out: ... so thanks for clarifying that and no need to do any special versions - it's just fine how it is now. I didn't come here to request anything to be compiled or modified for me but just to ask for info, heck, I wasn't even expecting You to be answering on this thread.
Click to expand...
Click to collapse
I make it my special concern to answer questions, even if it with sarcasm
I'm not sure what more you can do besides deleting the phone. Comment out in build.prop the rild stuff
I wonder if he is referring to TabUI? Which I as well am trying to relocate the flash able .zip which enabled this display difference. I have been running cm10.1 2/12 because of the sensors not working on the 2/14 build.
Sorry to piggyback the thread, but is there an answer for where the tab ui .zip is for the 2/12 build?
Sent from my Galaxy Nexus using xda premium
Reposting from where I previously put this, on the suggestion that folks here might have more idea what I am talking about.
Yes, this is a question but I couldn't see that it fit in better to one of the other forums. If I am wrong please accept my apologies and redirect me, thanks.
I'm trying to work with a custom build of Android based on KitKat to incorporate a stylus, copying some of the functionality (though not code) from Samsung which sells Android-with-stylus builds for e.g. the Note 3. I'm not including details of the specific device because right now I am working on a custom dev device and my aim is to write code which is generic enough to be usable from any Android (based on KitKat). The build (written by others) already incorporates drivers and sends stylus events correctly as motion events etc. Programming at the app level I can receive onHover, onTouch, onClick etc
The specific functionality I am trying to achieve is to pick up a stylus-button-click while hovering. It's perfectly possible to do this in any app, using an onGenericMotion Listener.
However, I want to make my "stylus-action" have system-wide effect - so that anywhere (in any other app, or in the launcher or whatever) I will pick up the event (prior to any other app) and bring up my custom menu. (just like AirCommand in Samsung Note 3) I guess in my custom Android this would then make that particular action somewhat protected or unusable for other users, but I'm ok with that.
In older Android (prior to ICS) you could try something by putting up a System Overlay (i.e in regular app code, without hacking the ROM at all), but this is no longer possible.
This is not an attempt to tapjack or whatever, I understand why this functionality has been removed from the domain of the regular programmer, and I don't want to regress my ROM back to pre-ICS behaviour by allowing the System Overlay hack. Now I am programming the system (if my change is good enough I'd like to submit it back to AOSP) so I would like to know the best method to address this. Since Samsung have already done this, it must be legal (using legal in the terms of "Android will allow it"), and I want to do it right.
Is it possible to write something similar to the System Overlay when you are running from a system service? Or is there a good choke-point to capture events before they are broadcast to the current running apps?
I was looking at (sorry, not allowed to post links) AndroidXRef /frameworks/base/core/java/android/view/View.java specifically in the function dispatchHoverEvent() which looks like a promising place. My naive idea is that I would place code here checking the MotionEvent to see if the button is pressed and if it is, don't call any listeners and instead call my little menu app (or broadcast a custom message, or something anyway). However, I've never written code on the ROM level before (LOTS of experience writing app code) so I don't know if this is a really bad point or a good point to add in code. Should I be putting things at a higher level or a lower one? Will this capture all events or not? Is it all just trial and error?
If this is the wrong place to ask questions like this, please tell me where on XDA I should be asking it. If it's the right place - please answer
Thanks
Kibi
I'm looking to remove the SMS limit. I'm currently on 6.0 (pure nexus rom), but I would also like to know how to do it on 5.1.1. Manually is preferred so I know exactly what is being changed on my device.
Why? Because it's my phone and I should be able to remove this ridiculous limit if I want to, and...
I wrote a python script that sends out multiple SMS to a large group of my friends. I keep getting that annoying pop up that the app is sending large amounts of text messages, and having to hit the allow button multiple times. This wouldn't be an issue if hitting the allow button actually sent all of the text, but it doesn't. Quite frustrating.
I've read a few thread on XDA about the issue, but can't seem to remove the limit. I tried following a guide in one of the s3 categories to no avail.
I am looking for this too!
After hours of searching today - it appears that the setting has been moved into the framework?
com.android.internal.telephony
https://android.googlesource.com/pl...droid/internal/telephony/SmsUsageMonitor.java
I hope I'm wrong as I'm no Android dev.... But, if I'm correct the only way I know of to "fix" it is to make the change in a custom Android build/ROM.
This SUCKS as I use mass texting for business purposes (communicating with many individuals who sign up for contract work). I really like Android N (along with AndroidPay) - but, looks like I'll be going back to M (on a custom ROM)...
If anyone locates/determines a way to alter that file using RootExplorer/Sqlite or some other way - please let me know.