Develop Bugs

[REQ] Galaxy tab gmail app

Ive been searching and searching and have not been able to find it. Hopefully it does exist already. Rom im using is supernova with CW3. EXT 4 so it would have to be compatible with that. Also if there is to many known issues with it let me know. TIA.

Just find the zip and unzip take the app out and copy and paste it to system>app directory with root explorrer
Sent from my SPH-D700 using XDA App

thats why i requested it because ive been searching with no luck. I recently seen that a rom has it so i know its available i just want to stick with the rom im using. So if anyone else knows where i can get it and that its resized for the epic let me know.

Which ROM is it in?

http://db.tt/KlBgVzR
Here i made a link jus 4 u
Sent from my SPH-D700 using XDA App

No push?
Is it just me, or does this app not support push/IMAP Idle? Even with Gmail set up using IMAP, the emails don't come until refreshed or it checks for new mail, and there is no option for "as items arrive."
What's the deal with that? Very disappointing, unless I'm missing something.

Chief85 said:
Is it just me, or does this app not support push/IMAP Idle? Even with Gmail set up using IMAP, the emails don't come until refreshed or it checks for new mail, and there is no option for "as items arrive."
What's the deal with that? Very disappointing, unless I'm missing something.
Click to expand...
Click to collapse
Anyone got answer to this? Would like it to work flawlessly before i install it. TIA

kelmar13 said:
Which ROM is it in?
Click to expand...
Click to collapse
Quantom rom

gtuansdiamm said:
Just find the zip and unzip take the app out and copy and paste it to system>app directory with root explorrer
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I copied and pasted to system/apps but won't install. Am I doing something wrong?
edit: fixed with reboot

Do you guys happen to know if this version still has the same issues as the version that's been floating around since the galaxy tab came out?
I've flashed it before, worked great, or so I thought, until without warning I stopped receiving e-mail pushes. Apparently its an issue specific to exchange (which I'm using) with specific e-mails that will lock it up and prevent any new e-mails from being pushed. If you delete said problematic e-mails, it will start syncing again, but I can't take that chance with work.
If any of you guys happen to use exchange with this new galaxy tab e-mail app and have reliable success with it I'd love to hear about it. Otherwise it's plain old regular email app for me

Click on Address no longer brings up MAPS

Used to be able to click on an address in text messages or in any browser and android would open it in MAPS or EARTH or NAVIGATION etc.
I recently installed AOKP milestone 6 for the first time, coming from Caulks 1.6. I'm not sure if it's an AOKP issue or if it's a 4.0.4 issue or what. I do know my buddy just lost this function on his G Nexus when he updated to Jelly Bean. That makes me think it's not a 4.0.4 issue because it worked normally for him on ICS. I definitely haven't taken any OTA updates so even if it was part of the Apple patent bullsh!t how would it be effecting me?
This is really important to me because I use this function multiple times a day.
Also, Maps takes forever to focus when I zoom in on a map. Any ideas on that?

A quick search shows issues with strings.xml not associating correctly, regardless of app.
Did you clear, uninstall and try fresh with one of the apps?
If you're into giving things, you could start here..
Sent from my SPH-D710 using xda app-developers app

MoHoGalore said:
A quick search shows issues with strings.xml not associating correctly, regardless of app.
Did you clear, uninstall and try fresh with one of the apps?
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
I searched but couldn't find anything. What did you search for. Appreciate the response. You thinking to fresh install maps? Or sms and browser?
Sent via phone that is not the one coming out next month that I want really bad even though not long ago this one was the phone I wanted really bad.

jirafabo said:
I searched but couldn't find anything. What did you search for. Appreciate the response. You thinking to fresh install maps? Or sms and browser?
Sent via phone that is not the one coming out next month that I want really bad even though not long ago this one was the phone I wanted really bad.
Click to expand...
Click to collapse
Strings is just a way of using localized data contained to point to more data that it may contain. Its a SQL function, well, to me.
But I do not know if its a root or an app function within Android itself. Someone smarter than me may have that answer.
I'd try clearing cache and data for the particular app, removing, then reinstall. But it may be more severe of an issue if no app will work.
Did you recently flash a ROM?
: edit: Please disregard that obvious dumb question I ask at the end. Its been a long day..
Sent from my SPH-D710 using xda app-developers app

MoHoGalore said:
Strings is just a way of using localized data contained to point to more data that it may contain. Its a SQL function, well, to me.
But I do not know if its a root or an app function within Android itself. Someone smarter than me may have that answer.
I'd try clearing cache and data for the particular app, removing, then reinstall. But it may be more severe of an issue if no app will work.
Did you recently flash a ROM?
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Yes. Just flashed to aokp yesterday.
Sent via phone that is not the one coming out next month that I want really bad even though not long ago this one was the phone I wanted really bad.

jirafabo said:
Yes. Just flashed to aokp yesterday.
Sent via phone that is not the one coming out next month that I want really bad even though not long ago this one was the phone I wanted really bad.
Click to expand...
Click to collapse
I personally haven't used aokp, and I apologize for asking a question that you clearly answered in your op. Been a long day.
I'd check to see if anyone with your setup can recreate or maybe, possibly, you had a corrupted or failed partial file or a failed write during flash.
Sent from my SPH-D710 using xda app-developers app

Hey, real quick, looking at Google code, looks like it may be linked to dalvik. Did you wipe or use a wipe all?
http://code.google.com/p/android-cu...ass-loading-sample/res/values/strings.xml?r=3
Sent from my SPH-D710 using xda app-developers app

jirafabo said:
I searched but couldn't find anything. What did you search for. Appreciate the response. You thinking to fresh install maps? Or sms and browser?
Sent via phone that is not the one coming out next month that I want really bad even though not long ago this one was the phone I wanted really bad.
Click to expand...
Click to collapse
And to answer your question, I just searched "Android getlocality" which is geocoding. Which will point you to strings, which are generic.. We use it in my line of work. Environmental Engineering.. ( i'm not a tree hugger btw..)
Sent from my SPH-D710 using xda app-developers app

Lol that's ok if you were. I just wondered bc I searched "address" and didn't find a thing related.
Ok just tested and it works in dolphin but not chrome. I just started using Chrome so that must not be a feature. As for sms I guess the it just doesn't work. I'll look into if I have a jelly bean sms app. I bet that's it.
Sent via phone that is not the one coming out next month that I want really bad even though not long ago this one was the phone I wanted really bad.

jirafabo said:
Lol that's ok if you were. I just wondered bc I searched "address" and didn't find a thing related.
Ok just tested and it works in dolphin but not chrome. I just started using Chrome so that must not be a feature. As for sms I guess the it just doesn't work. I'll look into if I have a jelly bean sms app. I bet that's it.
Sent via phone that is not the one coming out next month that I want really bad even though not long ago this one was the phone I wanted really bad.
Click to expand...
Click to collapse
I think you're on to something. There are multiple goecoder issues, random, with jelly bean on the the 'ol search. Multiple fixes if you're looking for a workaround.. NOT promoting a site, but stack overflow shows a few..
Open issues shows a few too.. http://code.google.com/p/android/issues/list Granted they are listed for the Nex..
---------- Post added at 10:36 PM ---------- Previous post was at 10:13 PM ----------
jirafabo said:
Lol that's ok if you were. I just wondered bc I searched "address" and didn't find a thing related.
Ok just tested and it works in dolphin but not chrome. I just started using Chrome so that must not be a feature. As for sms I guess the it just doesn't work. I'll look into if I have a jelly bean sms app. I bet that's it.
Sent via phone that is not the one coming out next month that I want really bad even though not long ago this one was the phone I wanted really bad.
Click to expand...
Click to collapse
And, to beat a dead horse deader, cause you touched on something I actually use, Andriod Chrome is using geocoding.. Odd that it isn't working for you. My maps in ICS have that function but it may still be broken in JB. Reference here.

Jellybean Camera service unavailable

Hi everyone,
I have a pretty strange problem. I have done a ton of research and seen it is common, but no one seems to have a solution. Anyways, I am unable to open neither Talk nor the camera app.
After booting the phone up, gtalk attempts to connect to the camera service. It is unavailable, so it immediately force closes. The same happens when I attempt to launch Talk.
I'm sure everyone is thinking: why don't you post a logcat, that would help. well.. I would if I could. According to alogcat as well as ADB the directory where the logcat is stored cannot be found.
I can tell from looking at the 'event log' after pushing the 'report' button when talk FC's that it is failing to launch due to a runtime error: 'failed to get camera info". This is really bothering me as I need my camera on my phone for my job.
I have flashed a few Roms in the past, but I have recently decoded to stick with the leaked stock. I've wiped EVERYTHING 5+ times, with no change. Restoring nandroids does not fix the problem either. No matter what ROM I flash, the problem remains. If anyone has any suggestions, I would greatly appreciate it.
Sent from my Galaxy Nexus using Tapatalk 2

One thing that I know will work. Unroot relock. Then it should definitely be fixed.
Then reroot and unlock.
So camera can't open at all??? Like click the icon and then force close???
--------------------------------------------------
If I have helped you.... hit that sexy thanks button. ^_^

I had this issue before. Everytime I would try to open the camera, it would forcr close. What I did was flash back to the IMM76K factory stock image. No need to relock.
Sent from my Galaxy Nexus using xda premium

DirgeExtinction said:
I had this issue before. Everytime I would try to open the camera, it would forcr close. What I did was flash back to the IMM76K factory stock image. No need to relock.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Where did you get the image you flashed from? I have found several, but they are just the ones that patch TO IMM76K.
Sent from my Galaxy Nexus using Tapatalk 2

rm2011 said:
Where did you get the image you flashed from? I have found several, but they are just the ones that patch TO IMM76K.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Look for your Galaxy Nexus type and download:
https://developers.google.com/android/nexus/images
Sent from my Galaxy Nexus using xda premium

rm2011 said:
Hi everyone,
I have a pretty strange problem. I have done a ton of research and seen it is common, but no one seems to have a solution. Anyways, I am unable to open neither Talk nor the camera app.
After booting the phone up, gtalk attempts to connect to the camera service. It is unavailable, so it immediately force closes. The same happens when I attempt to launch Talk.
I'm sure everyone is thinking: why don't you post a logcat, that would help. well.. I would if I could. According to alogcat as well as ADB the directory where the logcat is stored cannot be found.
I can tell from looking at the 'event log' after pushing the 'report' button when talk FC's that it is failing to launch due to a runtime error: 'failed to get camera info". This is really bothering me as I need my camera on my phone for my job.
I have flashed a few Roms in the past, but I have recently decoded to stick with the leaked stock. I've wiped EVERYTHING 5+ times, with no change. Restoring nandroids does not fix the problem either. No matter what ROM I flash, the problem remains. If anyone has any suggestions, I would greatly appreciate it.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
seems to me that the roms you're using dont have the camera binary. adb logcat is unavailable? that's unheard of, since thats a part of android itself. even user variant builds have it. can't think of a good reason for logcat to be removed.

I wiped EVERYTHING via fastboot and reflashed the stock image as suggested. I managed to flash successfully, but camera was still unavailable.
Logcat is working now, and the problem is a runtime error; "unable to retrieve camera information"
Any idea how I can check to see if the binaries are the problem? This is very frustrating... and I don't see how its happening, to be honest. I'm fairly certain it is not a hardware issue because I am definitely not the only one having the issue.
Sent from my Galaxy Nexus using Tapatalk 2

The last guy who had this exact same problem also was unable to fix it. If you flashed all partitions to stock and it still doesn't work, a hw issue does come to mind.
Sent from my Galaxy Nexus using Tapatalk 2

I guess its a possibility. I think what I need is someone who is proficient with the android source code to look at the camera service and see what makes it throw that log error. It almost certainly an ""if/else 'whatever the problem is' doesn't exist or is not correct, log e 'the error I am seeing in the log cat'"
If I was proficient in navigating the source code, I would do it. But I wouldn't know where to look. I need assistance of someone that is capable of doing this.
Again, I appreciate any and all help or assistance. Thanks will be given where it is deserved!
Sent from my Galaxy Nexus using Tapatalk 2

Well, as far as my limited knowledge can tell, the camera binaries are included. I did some research and found out that the camera is called "ducati" and I navigated to /vendor/firmware and found the file attached in the screenshot. Any suggestions would be appreciated. :/
Sent from my Galaxy Nexus using Tapatalk 2

rm2011 said:
Well, as far as my limited knowledge can tell, the camera binaries are included. I did some research and found out that the camera is called "ducati" and I navigated to /vendor/firmware and found the file attached in the screenshot. Any suggestions would be appreciated. :/
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
yeah, thats the binary for the camera. try another camera app, if you have already i'd say return it, i guess.
Sent from my i9250

bk201doesntexist said:
yeah, thats the binary for the camera. try another camera app, if you have already i'd say return it, i guess.
Sent from my i9250
Click to expand...
Click to collapse
I wish I could... but since I bought it used, that's not possible. Hopefully I can find a dev that knows the source code well enough to know where to look to see what causes this error.
Sent from my Galaxy Nexus using Tapatalk 2

bk201doesntexist said:
yeah, thats the binary for the camera. try another camera app, if you have already i'd say return it, i guess.
Sent from my i9250
Click to expand...
Click to collapse
I wish I could... but since I bought it used, that's not possible. Hopefully I can find a dev that knows the source code well enough to know where to look to see what causes this error.
Sent from my Galaxy Nexus using Tapatalk 2

Update: it appears that the camera service is not starting for some reason....
Sent from my Galaxy Nexus using Tapatalk 2

CM, AOSP, AOKP, 4.1.2 Bluetooth A2DP Solved?

CM, AOSP, AOKP, 4.1.2 Bluetooth A2DP Solved?
This worked for me, so I figured I'd share.
Unpair, turn off bluetooth, reboot. Using root explorer, go to /system/etc/bluetooth.
With text edit, open "input.conf" file. Change "idle timeout" to "0" (no timeout). Fix permissions, reboot, then pair devices again.
It might take about a minute for media to connect, but media stays connected with no drops.
Don't know why, but my uneducated guess is for some reason maybe it's reading "in seconds" instead of "in minutes". Anyway,p worked for me, try it let me know and share this post.
Sent from my SAMSUNG-SGH-I747 using xda premium

I dont have that file in my system/etc/bluetooth folder...?
Sent from my SGH-I747 using xda app-developers app

I don't have the file either. But I'm trying on latest 4.2
Sent from my SGH-I747 using xda app-developers app

geoldr said:
I don't have the file either. But I'm trying on latest 4.2
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Oh, me too. Is that why? Maybe the devs just forgot the file for the 4.2 builds?
Sent from my SGH-I747 using xda app-developers app

File is only on 4.1.2 ROM's.
Sent from my SAMSUNG-SGH-I747 using xda premium

mfc719 said:
File is only on 4.1.2 ROM's.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
So can we find the equivalent file for 4.2? Im searching google at the moment. Ill drop a heads up if i find anything
Sent from my SGH-I747 using xda app-developers app

Last night I was on Slim 4.2. I copied the files from his 4.1.2 ROM into the folder. Seemed to work, but got a lot crackle. Maybe if I deleted the original first it would have been better.
Sent from my SAMSUNG-SGH-I747 using xda premium

mfc719 said:
Last night I was on Slim 4.2. I copied the files from his 4.1.2 ROM into the folder. Seemed to work, but got a lot crackle. Maybe if I deleted the original first it would have been better.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
If you got crackle, then it didn't really work at all. Right? Are you just referring to the absence of bass that was fixed?
Does anyone know of a 4.1 ROM that has working bluetooth? ill DL it and pull the file and test it out.

mfc719 said:
CM, AOSP, AOKP, 4.1.2 Bluetooth A2DP Solved?
This worked for me, so I figured I'd share.
Unpair, turn off bluetooth, reboot. Using root explorer, go to /system/etc/bluetooth.
With text edit, open "input.conf" file. Change "idle timeout" to "0" (no timeout). Fix permissions, reboot, then pair devices again.
It might take about a minute for media to connect, but media stays connected with no drops.
Don't know why, but my uneducated guess is for some reason maybe it's reading "in seconds" instead of "in minutes". Anyway,p worked for me, try it let me know and share this post.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
I went temporarily back to Tasks last 4.1 build and I see the file, but everything is commented out. And it says "Defaults to 0 for no timeout". So technically mine is set to 0, and I still have no bass. Just no luck for us bluetooth people.

geoldr said:
I went temporarily back to Tasks last 4.1 build and I see the file, but everything is commented out. And it says "Defaults to 0 for no timeout". So technically mine is set to 0, and I still have no bass. Just no luck for us bluetooth people.
Click to expand...
Click to collapse
Supposedly, if you set
lpa.decode = false
in /system/build.prop
the bass issue is fixed. Its in one of these Q&A threads. Havent tried it cause that is for 4.1.2 only.
I stole the input.conf, main.conf, and network.conf files from a stock ROM and palced them in my /system/etc/bluetooth folder, set permissions, rebooted and......
didnt work. same exact issue complete with a total screen lock.
Boo!

jpride said:
Supposedly, if you set
lpa.decode = false
in /system/build.prop
the bass issue is fixed. Its in one of these Q&A threads. Havent tried it cause that is for 4.1.2 only.
I stole the input.conf, main.conf, and network.conf files from a stock ROM and palced them in my /system/etc/bluetooth folder, set permissions, rebooted and......
didnt work. same exact issue complete with a total screen lock.
Boo!
Click to expand...
Click to collapse
I tried the lpa.decode thing and it did not work.

Just so you guys know. The way Bluetooth is handle is totally different in 4.2 than it is on 4.1.

task650 said:
Just so you guys know. The way Bluetooth is handle is totally different in 4.2 than it is on 4.1.
Click to expand...
Click to collapse
That has become painfully apparent for me in the last few hours... Could you suggest a resource to educate us on the new methods?
Sent from my SGH-I747 using xda app-developers app

jpride said:
That has become painfully apparent for me in the last few hours... Could you suggest a resource to educate us on the new methods?
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Looks like were not getting any proper A2DP from AOSP for now. Which sucks. And TW ROM's are also crap. It was broken in 4.1, then working fine in 4.2, now they broke it again, and it doesn't seem like anybody is working on it.

geoldr said:
Looks like were not getting any proper A2DP from AOSP for now. Which sucks. And TW ROM's are also crap. It was broken in 4.1, then working fine in 4.2, now they broke it again, and it doesn't seem like anybody is working on it.
Click to expand...
Click to collapse
I was just browsing the google android dev site and they are definitely aware of it they have assigned an engineer as of November. Popular opinion is that the problem resides in the core stack(don't ask me).
Sent from my SGH-I747 using xda app-developers app

jpride said:
That has become painfully apparent for me in the last few hours... Could you suggest a resource to educate us on the new methods?
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Download source, find a way to fix the code, hope to fix Bluetooth is just about the only way.

jpride said:
I was just browsing the google android dev site and they are definitely aware of it they have assigned an engineer as of November. Popular opinion is that the problem resides in the core stack(don't ask me).
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
From what you are saying it sounds like the problem might only be solved with the next android iteration. Maybe 4.2.2. All I know is that after I installed 4.2 on my Nexus 7 and paired it to my car, the bluetooth audio cuts out a lot. So I am guessing this is a problem across 4.2 in general.
I found this page about the Nexus 7. Many users complaining about Bluetooth stutter.
http://code.google.com/p/android/issues/detail?id=39633

FYI. I'm reposting this from the SlimBean 4.2.1 Rom forum. I switched over to SlimBean 4.2.1 from Tasks ROM as a test of the Bluetooth issue. Here is a report. Mind you, its very cursory at this point. I'll have way more reliable data/info after tomorrow.
Depending on the app, my Bluetooth Audio streaming seems to be working. I just tested with Subsonic Streamer, both streaming online and local music sitting on my phone. Neither of those worked, i.e. erratic pacing, static clips, etc. I also used Audible to play an audiobook and it worked fine for about 5 minutes. I even turned the screen off to trigger the effect. Nothing. Maybe its not the best quality ever, yet. But its something. *shrug*
Click to expand...
Click to collapse

jpride said:
FYI. I'm reposting this from the SlimBean 4.2.1 Rom forum. I switched over to SlimBean 4.2.1 from Tasks ROM as a test of the Bluetooth issue. Here is a report. Mind you, its very cursory at this point. I'll have way more reliable data/info after tomorrow.
Click to expand...
Click to collapse
Sounds great! Task released an update with some changes to BT. But when I tried it I used poweramp and it was the same, unfortunately. Do you think you could download the free trial of poweramp and see if it work with the SlimBean ROM?

Delete please, I spoke too soon

MightText SMS for tablets

Is anyone else using this free app. If not, WHY. Absolutely love it! Get your phone SMS to your tablet AND PC!!!! You can also respond via tablet and PC.
https://play.google.com/store/apps/details?id=com.mightytext.tablet
Pretty simple to set up. Not sure how or if this will piss me off in the long run, but I'll let you know.
Sent from my Nexus 7 using xda app-developers app

I use it from my tablet, phone and computer and so far it's working out great! Haven't noticed any delay or anything, but so far it's exactly what I was looking for.
Sent from my Samsung Galaxy S3 via Tapatalk

Cloud SMS user here.
Similar to Mighty Text, but higher rated and has a $.99 price tag.
Extremely responsive Dev who is always improving/tweaking it.
This type of app is a must-have for me as well.

Been using it for about a month now myself. No issues, works great.
Sent from my SGH-T999 using xda app-developers app

i like it, but i never get notifications on my tablet,, it only seems to sync when i open up the app. developers weren't able to resolve the problem.

Using this and its great ....its a must have.
Sent from my Nexus 7 using xda premium

alan77ss said:
i like it, but i never get notifications on my tablet,, it only seems to sync when i open up the app. developers weren't able to resolve the problem.
Click to expand...
Click to collapse
Same here. Devs were responsive for a few emails, and then they just sort of dropped off. Please let me know if you get this figured out. Are out using Handcent or Go SMS on you phone?

That happened to me as well. I unlinked my tablet in the settings and added it back again and it fixed it.
Sent from my HTC Vision using Tapatalk 2

tducote said:
Same here. Devs were responsive for a few emails, and then they just sort of dropped off. Please let me know if you get this figured out. Are out using Handcent or Go SMS on you phone?
Click to expand...
Click to collapse
Devs were the same with me, responsive at first, then gave up. No extra sms apps installed so that's not the problem. Also tried resetting everything, but no joy.

jimbobvfr400 said:
That happened to me as well. I unlinked my tablet in the settings and added it back again and it fixed it.
Sent from my HTC Vision using Tapatalk 2
Click to expand...
Click to collapse
alan77ss said:
Devs were the same with me, responsive at first, then gave up. No extra sms apps installed so that's not the problem. Also tried resetting everything, but no joy.
Click to expand...
Click to collapse
Yeah, I tried unlinking and relinking. Didn't work. I decided to just pay the $5 per year and go back to DeskSMS. It has been super reliable across any and every build on my phone, and its companion, TabletSMS, has worked with both my Nexus 7 and my TouchPad. Worth the money to me.

App store issues?
I just picked up a Nexus 7 the other day and went to download Mightytext from the app store and it is saying my device is not compatible? I feel like something is very wrong here. Any suggestions?
---------- Post added at 09:41 AM ---------- Previous post was at 09:36 AM ----------
ocman21 said:
I just picked up a Nexus 7 the other day and went to download Mightytext from the app store and it is saying my device is not compatible? I feel like something is very wrong here. Any suggestions?
Click to expand...
Click to collapse
Derp... wrong app. Finally figured it out

I use it but I'm a little concerned about privacy... Its obvious the actual texts and phone numbers are going through mighty texts servers to get from AT&Ts system to my nexus 7 which is only connected via WiFi, or is that incorrect? I text a lot of highly sensitive info due to my line of work. I hope I'm worried for nothing because its a great app and one more reason to put my phone down while I'm on my tablet.
Sent from my Nexus 7 using xda app-developers app

roppolo said:
I use it but I'm a little concerned about privacy... Its obvious the actual texts and phone numbers are going through mighty texts servers to get from AT&Ts system to my nexus 7 which is only connected via WiFi, or is that incorrect? I text a lot of highly sensitive info due to my line of work. I hope I'm worried for nothing because its a great app and one more reason to put my phone down while I'm on my tablet.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I think it's going through googles servers since you login with your Google credentials, but I guess that could be just for authentication. If you need more privacy tablet talk syncs via Bluetooth but I think you have to pair it a lot.
Sent from my XT912 using Tapatalk 2

am in UK, I use TU Go from O2 I can text and phone from nexus 7. Not tried it with bluetooth headset yet
Sent from my Nexus 7 using xda premium

sendbeer said:
I think it's going through googles servers since you login with your Google credentials, but I guess that could be just for authentication. If you need more privacy tablet talk syncs via Bluetooth but I think you have to pair it a lot.
Sent from my XT912 using Tapatalk 2
Click to expand...
Click to collapse
Yeah I had tablet talk for awhile, I just hate having to connect it every time. I'd love for someone to give us some clarification on my privacy question. Lemme see if I can search for the answer. I'll post it here if I find it. :good:

Love this app
I love this app so much I made an inverted version. Screenshots attached.
I will upload to test if anyone is interested. Then I will start a post for it once I know it's working for more people then myself. I only themed hdpi so Nexus 7 only for now.
Let me know please!!!!!

iMessage.... What a complete and total copy..... Granted, you can easily say the same for this app and Whatsapp. Idk, I think this is easier and much better than whatsapp (used both). I messages claims to use phone number only.....so does MightyText....
What do you guys think?
Sent from my Nexus 7 using xda app-developers app

ok I made a new thread for the themed version here: http://forum.xda-developers.com/showthread.php?t=2205779
Enjoy!
DJ