Database Develop

WARNING: Android 4.4 KitKat on Nexus 7 (2012) 3G disables sms.

[EDIT: Linked thread from Nexus 7 (2013) forum: http://forum.xda-developers.com/showthread.php?t=2531897]
Hi,
I'm the developer of 8sms.
It seems that sms no longer works on the Nexus 7 3G if you upgrade to Android 4.4.
In the past, some people have been able to use sms on their tablets by downloading and installing a third party sms app (such as 8sms). Even though there is no stock messaging app with the ROM (and AFAIK, this is not an official feature), this has generally worked.
However, Android 4.4 KitKat on the Nexus 7 3G takes away this feature.
In Android 4.4, a messaging app must be set as the "default sms app" so it can be allowed to save new messages to the phone's message database. In other words, a messaging app must be the default sms app in order to operate fully.
In the Nexus 5 (and Android emulators), there is a setting Settings » ... » Wireless » Default sms app which allows you to choose your default sms app.
In the Nexus 7 3G, this setting DOES NOT EXIST.
(This is according to what one user of 8sms has told me. )
It seems that the "default sms app" is not supported on the Nexus 7. In other words, you cannot set an app to be the default sms app. That means it is not possible to use an sms app.
Can some other readers confirm this?
If confirmed, this is a LOSS OF FUNCTIONALITY.

You are right. Sms does not work at all on kitkat on my N7 LTE
Even hangout does not have SMS feature
Sent from my Nexus 7 using XDA Premium 4 mobile app

Agreed, I was the one to originally alert this OP to the issue. Incoming SMS triggers a notification in the tray that leads only to a pop-up dialogue. After dismissing it, the OS does not save the incoming SMS anywhere and installed clients cannot see it.

Same with my nexus 7 LTE. I have tried different sms apps but the outcome is the same with android 4.4 (everything was fine with 4.3.1)
Anyone has a working solution for this ?

i have wifi nexus 7 2012 so cant any thing for sure but i think google changed sms in 4.4 sms are integrated with hangouts so download go sms (i think they have updated their app for 4.4) and report back.

xateeq said:
i have wifi nexus 7 2012 so cant any thing for sure but i think google changed sms in 4.4 sms are integrated with hangouts so download go sms (i think they have updated their app for 4.4) and report back.
Click to expand...
Click to collapse
I already tried with Go SMS but no luck...

then try hangout, ur sms might be there as google told us

xateeq said:
then try hangout, ur sms might be there as google told us
Click to expand...
Click to collapse
On Nexus 7 the Hangouts App doesn't have such feature...
Even some guy before me mentioned this :silly:

Right, the issue is that the OS builds for Nexus 7 are barring SMS apps from participating in Kitkat's usual way of doing SMS, and there's no default app to rely on.
Sent from my Nexus 5 using Tapatalk

It is such a shame... I have not upgraded yet. I use 8sms. I hope there is a way to enable it.
Envoyé de mon Nexus 7 en utilisant Tapatalk

What a mess. Google needs to take a step back and stop trying to force us to use hangouts.

cmstlist said:
Right, the issue is that the OS builds for Nexus 7 are barring SMS apps from participating in Kitkat's usual way of doing SMS, and there's no default app to rely on.
Click to expand...
Click to collapse
I haven't updated my N7 to 4.4 yet so this may just be a false hope, but has anybody tried something like the following yet? (root is required)
1. Use TitaniumBackup or other tool to freeze the Simple Message Reciever app, (if 4.4 still has it. It may be called something else now.) This is what shows the message dialog for incoming texts.
2. Install 8sms and set it to run in standalone mode.
If that doesn't work then I would try injecting the MMS.apk from one of the ROMs based on 4.4 AOSP and see if it will take on the role of default SMS/MMS handler.

RobinD42 said:
I haven't updated my N7 to 4.4 yet so this may just be a false hope, but has anybody tried something like the following yet? (root is required)
1. Use TitaniumBackup or other tool to freeze the Simple Message Reciever app, (if 4.4 still has it. It may be called something else now.) This is what shows the message dialog for incoming texts.
2. Install 8sms and set it to run in standalone mode.
If that doesn't work then I would try injecting the MMS.apk from one of the ROMs based on 4.4 AOSP and see if it will take on the role of default SMS/MMS handler.
Click to expand...
Click to collapse
...doesn´t work, either

I wonder if, like the missing tethering feature, it can be restored by unhiding the SMS select menu via a modification of the framework apk?

cmstlist said:
I wonder if, like the missing tethering feature, it can be restored by unhiding the SMS select menu via a modification of the framework apk?
Click to expand...
Click to collapse
I think this is an avenue worth pursuing.
I don't think Google intentionally disabled sms on the Nexus 7. To me, it seems more like their build scripts doesn't list sms as a feature, and this was just a side-effect.
Unfortunately, I don't have a cellular Nexus 7 so I'm very limited in what I can contribute to this discussion.

bengtan said:
I think this is an avenue worth pursuing.
I don't think Google intentionally disabled sms on the Nexus 7. To me, it seems more like their build scripts doesn't list sms as a feature, and this was just a side-effect.
Unfortunately, I don't have a cellular Nexus 7 so I'm very limited in what I can contribute to this discussion.
Click to expand...
Click to collapse
And I do have one but I have no developer type experience.
Have you posted a thread about this on the N7 2013 forum? That might attract more attention too.

So this might be a stupid question, but this has nothing to do with MightyText right? In other words, MightyText should still work since it's not the tablet receiving the sms but the phone right?

@OP, From where you got Kitkat update for Nexus 7 3G. As i haven't received OTA yet also [REF] Nexus 7 Stock OTA URLs doesn't list Kitkat build for 3G version.
Also does this update disables 3rd party SMS for N7 2012 version only or is applicable to current generation N7 as well?

PsychDrummer said:
So this might be a stupid question, but this has nothing to do with MightyText right? In other words, MightyText should still work since it's not the tablet receiving the sms but the phone right?
Click to expand...
Click to collapse
Right, MightyText for tablets is just an interface with a phone and does not use the tablet's phone number.
rutu3 said:
@OP, From where you got Kitkat update for Nexus 7 3G. As i haven't received OTA yet also [REF] Nexus 7 Stock OTA URLs doesn't list Kitkat build for 3G version.
Also does this update disables 3rd party SMS for N7 2012 version only or is applicable to current generation N7 as well?
Click to expand...
Click to collapse
Google has posted stock factory images for KitKat on Nexus 4, 7 (2012 and 2013) and 10. These can be flashed in fastboot, and there are also flashable zips on the forum based on these factory images. Others on this thread have reported loss of SMS on the 2013 version as well.

cmstlist said:
Google has posted stock factory images for KitKat on Nexus 4, 7 (2012 and 2013) and 10. These can be flashed in fastboot, and there are also flashable zips on the forum based on these factory images. Others on this thread have reported loss of SMS on the 2013 version as well.
Click to expand...
Click to collapse
So that means Google has intentionally added code to block us from using third party SMS apps.
So we can start petition to get messaging working on nexus 7 or wait for developers to find some workaround to send / receive sms.
I believe in 2nd option more

[Q] Unable to set voicemail number - 5.1.1

I've tried to set a voicemail number on my phone, but it will not save.
I've tried going to Voicemail > Setup > Voicemail Number, entered the number (1416) and then clicked ok.
The phone closes the dialog without displaying an error, but the voicemail number still reads as <Not Set> and the voicemail notification still says "Voicemail number unknown", though clicking on the option again shows 1416 already filled.
Any suggestions on how to fix this issue?

make a contact as voicemail, enter the number, save. done.
oh, and ignore that setting, its probably not for your provider.

I did that, and I can call from the contact of course.
Issue is I get the voicemail notification, and when I click on it it just takes me to the setup menu.

domesdkg said:
I did that, and I can call from the contact of course.
Issue is I get the voicemail notification, and when I click on it it just takes me to the setup menu.
Click to expand...
Click to collapse
That`s an issue with all Nexus`s. Don`t know of a solution

gee2012 said:
That`s an issue with all Nexus`s. Don`t know of a solution
Click to expand...
Click to collapse
Seriously? They've left that as an unresolved known issue for this long?
Since the "Phone" app isn't on the play store, am I correct in assuming that it's part of AOSP? or is it Google made?
If it's AOSP I'll go write up a bug report, I did some searching over there earlier, but didn't see anything. Wanted to make sure I wasn't just being dumb before I submitted a bug report.

I don't have this issue
Sent from my Nexus 6 using Tapatalk

domesdkg said:
Seriously? They've left that as an unresolved known issue for this long?
Since the "Phone" app isn't on the play store, am I correct in assuming that it's part of AOSP? or is it Google made?
If it's AOSP I'll go write up a bug report, I did some searching over there earlier, but didn't see anything. Wanted to make sure I wasn't just being dumb before I submitted a bug report.
Click to expand...
Click to collapse
Wasn`t able to change the voicemailnumber since the Nexus 4 till the N6. Never had an issue on Samsung or LG phones.

The firt time i had the notification i had to set it but now its stored permanently. Im on stock unrooted 5.1.1
Sent from my Nexus 6 using Tapatalk

Mr_S said:
The firt time i had the notification i had to set it but now its stored permanently. Im on stock unrooted 5.1.1
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
First i thought it was a problem of my ISP but it works on LG, Samsung and WP phones so its a specific Nexus issue i guess. Somehow i always get the message: Unable to change the voicemail number, contact your provider. Have that on the N4/5/6.

From what I'm seeing this seems to be a problem with the dialer on vanilla android, on non-US carriers. Maybe you guys can provide some extra info to validate this theory.
gee2012 said:
First i thought it was a problem of my ISP but it works on LG, Samsung and WP phones so its a specific Nexus issue i guess. Somehow i always get the message: Unable to change the voicemail number, contact your provider. Have that on the N4/5/6.
Click to expand...
Click to collapse
gee2012 said:
Wasn`t able to change the voicemailnumber since the Nexus 4 till the N6. Never had an issue on Samsung or LG phones.
Click to expand...
Click to collapse
LG/Samsung: That fits my theory - they have their own dialer apps.
Error on N4/5/6: Was this in Europe? I've seen several posts about European users having this error message. Please let me know the carrier/country.
Edit: Netherlands on T-Mobile?
So maybe this problem only occurs on stock phones on certain carriers in certain counties?
Mr_S said:
The firt time i had the notification i had to set it but now its stored permanently. Im on stock unrooted 5.1.1
Click to expand...
Click to collapse
I'd guess you're probably in the states on a major carrier - can you verify?
Edit: Looks like you're in the UK. Still curious about the carrier though.

Im in uk on o2
Sent from my Nexus 6 using Tapatalk

Google Now can't unlock??

Hi all,
I'm running into an odd issue on the N6, although other devices seem to have this as well. . .
I used to be able to use google now to set alarm, send message, etc while its locked.
Now, doing the same things, google now replies that it can't complete the task until device is unlocked.
Is anyone else running into this and is there any way around it?
Thanks!

Bump ... help please?

rom you are using? and android version?

it only happens when the device is locked with a password or something similar. If you disable that you're good to go.
Sent from my Nexus 6 using XDA Free mobile app

I have this issue. I can't set alarms or reminders unless I unlock the phone. The voice prompt tells me so. Quite annoying. Hopefully they remedy it with smart voice unlock soon
Sent from my Nexus 6 using Tapatalk

This updated feature now affects texts via voice now. I can no longer wake my phone from sleep and send a text unless the phone is unlocked. More of a reason to move to a moto x pure now. what a huge step back.

arts711 said:
Hi all,
I'm running into an odd issue on the N6, although other devices seem to have this as well. . .
I used to be able to use google now to set alarm, send message, etc while its locked.
Now, doing the same things, google now replies that it can't complete the task until device is unlocked.
Is anyone else running into this and is there any way around it?
Thanks!
Click to expand...
Click to collapse
Hi, I just saw your post and I was having the exact same issue. The only way I can get around it currently is by rolling back to an old version of the "Google App" which seems to encompass Google Now, Voice Search, Google Now Launcher, and most importantly the OK Google "always on" functionality.
I went back through previous versions testing the "OK Google call _____" (screen off & device locked) feature until I found where it stopped working correctly and the "4.9.22.16.arm" version is the last one that does work the way it is supposed to. You can find older versions of the Google App on Apkmirror. Hopefully they track down the root cause of the issue and fix it soon.

Help with axon Elite, app notifications are not coming through in real time?

Evening all I am after a little help please I am new to this phone after having Samsung's for a long time and one thing that is bugging me is that apps that are real time e.g. whatsapp and anything with messaging are not getting the messages until I open the app and I am then flooded with messages? I have seen the options in the power menu for background apps but regardless of how I select the apps either on or off I still don't get the messages till I open the app?
Anyone else had this issue and know lof a work around?
Cheers

Hi! yeah, I had the same problem and I know more people is suffering the same experience. What I made was the following. Firstly, you should set the background apps in setting/power manager/manage background. Then, you have to make the same in Mi-assistant app/list of authorized and finally, you can install "Push Notifications Fixer" app from Google Play Store but be aware, because there are two versions of this app (rooted and not rooted devices). At this moment, my notifications come on time so, it's working pretty well.

Thanks so much for this I will check your advise out now.

The above isn't working unfortunately does anyone else have any suggestions?

hoppi05 said:
The above isn't working unfortunately does anyone else have any suggestions?
Click to expand...
Click to collapse
Have you updated to the latest firmware?
Sent from my ZTE B2016 using Tapatalk

Yes I have updated it twice in the week since owning it and it's done this on all versions

Did you check the APN settings?
Sent from my A1P using Tapatalk

No did not think about those as it did it automatically and for phone fiction as in call and texts it is fine but I will give them a once over to check, thanks
Sent from my ZTE A2016 using Tapatalk

Still not managed to fix this Si if any one can suggests any other ways to help let me know.
Thanks all

Crazyhat said:
Hi! yeah, I had the same problem and I know more people is suffering the same experience. What I made was the following. Firstly, you should set the background apps in setting/power manager/manage background. Then, you have to make the same in Mi-assistant app/list of authorized and finally, you can install "Push Notifications Fixer" app from Google Play Store but be aware, because there are two versions of this app (rooted and not rooted devices). At this moment, my notifications come on time so, it's working pretty well.
Click to expand...
Click to collapse
Where is power manager? I don't see that in the settings.(on 5.1.1)

Do you have 5.1.1 version in Axon Elite? Congratulations! You must be the only one. Rest of us have 5.0.2 version and in settings, you have an option with an icon battery. This is power manager or energy manager.
Enviado desde mi ZTE A2016 mediante Tapatalk

Crazyhat said:
Do you have 5.1.1 version in Axon Elite? Congratulations! You must be the only one. Rest of us have 5.0.2 version and in settings, you have an option with an icon battery. This is power manager or energy manager.
Enviado desde mi ZTE A2016 mediante Tapatalk
Click to expand...
Click to collapse
Ah, I thought all Axon's were on 5.1.1.

My profile switcher is also not working correctly

Crazyhat said:
Hi! yeah, I had the same problem and I know more people is suffering the same experience. What I made was the following. Firstly, you should set the background apps in setting/power manager/manage background. Then, you have to make the same in Mi-assistant app/list of authorized and finally, you can install "Push Notifications Fixer" app from Google Play Store but be aware, because there are two versions of this app (rooted and not rooted devices). At this moment, my notifications come on time so, it's working pretty well.
Click to expand...
Click to collapse
Hello, I have found an easy solution Here is the link, post number 5 http://forum.xda-developers.com/zte...n-mini-root-custom-roms-t3289640#post64791398

hi all well after speaking with ZTE support i performed a factory reset but prior to that they advised to clear cache on the apps with issues (not sure why) but this did help and for the first few days all was great but whatsapp is slowly getting more and more delayed? i have set all the power and start up options as advised also disabled the MI assistant but to no avail? so the reset may help others but for me this did not work.

Dooosu said:
Where is power manager? I don't see that in the settings.(on 5.1.1)
Click to expand...
Click to collapse
We were speaking about axon elite. It takes 5.02 lollipop version
Enviado desde mi ZTE A2016 mediante Tapatalk

No more google Assistant..

It's 2 weeks, I can't have any response from Google assistant on AA. The assistant is working fine without Android auto.
If I ask something for example a destination, it works, but no voice answer anyway.
So I can't have any info about Weather or calendar etc...
Does anyone have the same issue?
Already tried to reinstall AA, Google and Google Play services (delete cache and data)...but it does not help...
Xperia x compact Oreo

What happen?

Same problem hier - when the assistant is replying, the headunit mutes..
https://support.google.com/androidauto/thread/2475001?hl=en

I think that MAYBE you are experiencing the same problem as I am.
If you manually trigger assistant in your phone by holding the middle icon/button and say a command like call someone it will display a screen asking you for activation. No matter how many times you activate it. It will deactivate again and you will have to do the same process again.
Or it can be the mute headunit bug. I think I have both.

The issue is on the AA app without car unit, too.
Just no answer after asking anything...no assistant voice at all..
But Google app works ok...

Same here. Oneplus 6t. Found other fora describing the problem too. We just have to wait for a fix I think...

same problem

Is Google working on it? This issue is known... what is it waiting for?

mains75 said:
Is Google working on it? This issue is known... what is it waiting for?
Click to expand...
Click to collapse
What did google reply when asked for an update on the issue?

At first the routines also worked, but then never again. Now the wizard has been limited to a few commands in android auto.

AA Updated to 4.8.5 still the same problem...

Really strange that they managed to mess it up so badly. And apparantly no fix in the latest release.

Still don't understand if all phones have the same issue, or some model only

Having same problem too. No response, only a "blink" sound. The order works but no voice reply
Galaxy S8 Plus + Kenwood Unit
I tried to send a whastapp msg and it works, but no reply when i ask about weather or travel to any place (directly opens navigation app after "blink")

The issue is on the AA app without car unit, too.

Latest app update solved the problem

r4yv3n said:
Latest app update solved the problem
Click to expand...
Click to collapse
What latest app? Android Auto? It's still not working for me AA 4.8.594324.
Regards.
Alderon666

alderon666 said:
What latest app? Android Auto? It's still not working for me AA 4.8.594324.
Regards.
Alderon666
Click to expand...
Click to collapse
I have same AA version.
Look into Google App - version 10.84.19.21-arm64

r4yv3n said:
I have same AA version.
Look into Google App - version 10.84.19.21-arm64
Click to expand...
Click to collapse
Same version here.
Google Play Services: 19.6.29 (040400-278422107)
EDIT: OK... Yesterday Google Assistant didn't work on Android Auto on the phone. Today I tried in my car and it worked. Later I checked on my phone and it worked too. Very strange, because I'm quite sure there was no update from google.
Regards.
Alderon666

I saw a report of a server-side change. Hopefully this is fixed for everybody.