Database Develop

[Q] Nexus One can't send SMS

Hi guys!. I just bought a second hand nexus one from the internet. It has CyanogenMod 7.2.0-passion, everything is working good, but it has two problems. 1. I can't send text messages. 2. I can barely hear something when I'm on phone, even with the incall volume on max.
The phone is rooted. I've tried apps from store for messaging. The same 330 error. What could I do?

First thing is probably check you have the correct APN, just Google search for your carrier and add or call directly and they should help. Off this won't work next best bet would be either a sim card that's bad or you need to change the radio.
Sent from my Nexus 7 using xda premium

(deleted)

did you check sms center number in messages setting? it must be correct depending your carrier

CM10.1 phone app blacklist - any alternatives?

This is not a Nexus 4 specific issue, but rather a general CM10.1 issue.
The stock CM10.1 phone app normally does a good job of blacklisting numbers - but when you have the phone connected to a Bluetooth handsfree, and the blacklisted number attempts to call you, then the Bluetooth handsfree will start ringing and it's impossible to stop the ringing unless the caller gives up or you disconnect the Bluetooth.
The handsfree device in question is the Ford Sync system built into my car. Earlier today, I blacklisted the number 6474964196 (for others who live in Toronto, blacklist it too!) after realizing it was a scam to impersonate the bank TD. Later, when I was driving out of the office with the phone connected via Bluetooth, my car started ringing and displayed that very number on my GPS screen as an incoming call. I kept rejecting the call using my steering wheel button, but the caller didn't relent.
The whole time, my phone screen itself did not show any signs on an incoming call. Normally when I drive I keep my phone in the cupholder, and if it gets an incoming call from a non-blacklisted number, the screen turns on and shows me the number along with a big red button to reject the call. But with the incoming call being from a blacklisted number, the screen remained off.
After failing repeatedly to silence that call, I had to wait till I got to a red light so I could manually turn off the Bluetooth. At the same time, I noticed the phone app showed nothing from the blacklisted number in my missed-calls log.
I'll report this on Jira later. In the meantime, does anyone know of an alternative call blacklist app that doesn't allow a Bluetooth handsfree to ring when a blacklisted number calls me?

I previously used root call blocker pro to block calls. I don't use Bluetooth so I can't say if it'll help you out.
You can also add the number to your contacts, then go into the contracts app and have all calls go to voicemail. CM's method is better because it doesn't let them go to voicemail.

Yes, there is a bug in there. I now use root call blocker.
Sent from my Nexus 4 using Tapatalk 4 Beta

I use true caller to block calls. It even has option to block numbers marked as spam by other users
Sent from my Nexus 4 using Tapatalk 4 Beta

Thanks for the suggestions guys. I'll use root call blocker and see.

I just create a contact names no answer and add the number there, with the option to send calls to voicemail. Now my phone won't ring when they call, and when I wipe and flash a new ROM, the blacklist numbers all carry over with my Google contacts. I have about 15 blacklisted numbers there.
Sent from my Nexus 4 using Tapatalk 4 Beta

Nexus: SMS exploit discovered

Attackers could force phones from Google's Nexus line to reboot or fail to connect to the mobile Internet service by sending a large number of special SMS messages to them.
The issue was discovered by Bogdan Alecu, a system administrator at Dutch IT services company Levi9, and affects all Android 4.x firmware versions on Google Galaxy Nexus, Nexus 4 and Nexus 5. Alecu is presenting the vulnerability Friday at the DefCamp security conference in Bucharest, Romania.
Class 0 SMS, or Flash SMS, is a type of message defined in the GSM specification that gets displayed directly on the phone's screen and doesn't automatically get stored on the device. After reading such a message, users have the option to save it or dismiss it.
On Google Nexus phones, when such a message is received, it gets displayed on top of all active windows and is surrounded by a semi-transparent black overlay that has a dimming effect on the rest of the screen. If that first message is not saved or dismissed, and a second message is then received, the latter is placed on top of the first one and the dimming effect increases.
When such messages are received, there is no audio notification, even if one is configured for regular incoming SMS messages. This means that users receiving Flash messages won't know about them until they look at the phone.
Alecu found that when a large number of Flash messages—around 30—are received and are not dismissed, the Nexus devices act in unusual ways.
The most common behavior is that the phone reboots, he said. In this case, if a PIN is required to unlock the SIM card, the phone will not connect to the network after the reboot and the user might not notice the problem for hours, until they look at the phone. During this time the phone won't be able to receive calls, messages or other types of notifications that require a mobile network connection.
According to Alecu, a different behavior that happens on rare occasions is that the phone doesn't reboot, but temporarily loses connection to the mobile network. The connection is automatically restored and the phone can receive and make calls, but can no longer access the Internet over the mobile network. The only method to restore the data connection is to restart the phone, Alecu said.
On other rare occasions, only the messaging app crashes, but the system automatically restarts it, so there is no long term impact.
A live test at the conference performed on a Nexus 4 phone with the screen unlocked and running Android 4.3 did not immediately result in a reboot. However, after receiving around 30 class 0 messages the phone became unresponsive: Screen taps or attempts to lock the screen had no effect. While in this state, the phone could not receive calls and had to be rebooted manually.
A second attempt with the screen locked also failed to reboot the phone because only two of over 20 messages were immediately received. This may have been caused by a network issue or operator-imposed rate limiting. The messages did arrive later and the phone rebooted when unlocking the screen.
Alecu said that he discovered this denial-of-service issue over a year ago and has since tested and confirmed it on Google Galaxy Nexus, Nexus 4 and Nexus 5 phones running various Android 4.x versions, including the newly released Android 4.4, or KitKat.
Around 20 different devices from various vendors have also been tested and are not vulnerable to this problem, he said.
This doesn't exclude the possibility that some devices from other vendors are vulnerable, but so far it has only been confirmed on the previously mentioned Google Nexus phones.
Alecu claims he contacted Google several times since he found the flaw, but mostly got automated responses. Someone from the Android Security Team responded in July and said the issue would be fixed in Android 4.3, but it wasn't, Alecu said, adding that this contributed to his decision to disclose the problem publicly.
"We thank him for bringing the possible issue to our attention and we are investigating," a Google representative said via email.
via PCWorld
Click to expand...
Click to collapse
What is your intake on this?

Deeco7 said:
What is your intake on this?
Click to expand...
Click to collapse
TLDR
joke, Well since I can't achieve the effect (reboot and unusual behaviour) I am saying this doesn't affect my life & the way my nexus works.. so..

Deeco7 said:
What is your intake on this?
Click to expand...
Click to collapse
My ... ummm, intake ... on this is that I never cease to be amazed at the lengths that a corporate security weenie will go to in order to justify his salary.
I recently retired from a large IT services firm in the US, and this is exactly the kind of far-fetched crap our corporate security people cited to justify taking away my Android connectivity to our Exchange servers. Grrrr...
JM2¢

Last I checked, only the provider can send class 0 messages.

This. No one can send them, and almost no carriers... at least in the U.S. use them. I have never seen a single one. The chances of getting 30 at one time is zero. It's a non-issue IMO.
If you want a crash bug, look to the iOS bug that caused any iOS phone or app to crash when a certain string of characters is displayed by it.

Unfortunately there is software out there that allows a user to send an anonymous class 0 sms messages, so I guess this bug needs looking at by the Google techies
Sent from my Nexus 5 using Tapatalk

I don't have a take on this
Sent from my Nexus 5 using Tapatalk

I award you no points & may God have mercy on your soul.
Lol but seriously, is this REALLY an issue?
Sent from my Nexus 5 using Tapatalk

cbutt said:
I award you no points & may God have mercy on your soul.
Lol but seriously, is this REALLY an issue?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I'm not really concerned about this, just thought I'd create a discussion about it. Don't worry about my soul, my friend.
Sent from my Nexus 5 using Tapatalk

If anyone is that worried, ... https://play.google.com/store/apps/details?id=com.silentservices.class0firewall

Deeco7 said:
What is your intake on this?
Click to expand...
Click to collapse
Meh... It's just a bug. Can be inconvenient if you reboot and don't connect to your network until you insert your PIN, but there are no security issues mentioned.
I'd be more worried about the bug in many american cell subscriptions that share SMS cost between sender and receiver. But fortunately I live in a sane country where only the sender pays for the messages

Dialer not sending full pause code

Do a lot of conference calls and have all numbers set dial access codes and pins using the (p) Pause. With LP they do not fully send when automated system repeats what was sent was never the full number. Example 8778741777,,,,1234567890#
The systems might just get 1234567 of the access code and this is for all company numbers I call.
Anyone have same experience?
Anyone have a fix?

parcou said:
Do a lot of conference calls and have all numbers set dial access codes and pins using the (p) Pause. With LP they do not fully send when automated system repeats what was sent was never the full number. Example 8778741777,,,,1234567890#
The systems might just get 1234567 of the access code and this is for all company numbers I call.
Anyone have same experience?
Anyone have a fix?
Click to expand...
Click to collapse
What rom are you using? It works for me on stock and on slimlp, our systems use webex which i dial into and have to use codes and they work fine.

Was using LS and now on Chroma but happened to me on stock... What I did to slow it down was put a (p) after 3 numbers seems it was sending it too fast for that system to handle...so think its now a phone issue more so how the other end was getting to numbers.
Thx for the reply

Same issue for me, using Chroma ROM and the latest radio (MDM9625_104446.01.02.95R). Not only are pauses not recognized, generally dialing digits after connection does not work. Huge issue, might try reverting the radio.

swamp2 said:
Same issue for me, using Chroma ROM and the latest radio (MDM9625_104446.01.02.95R). Not only are pauses not recognized, generally dialing digits after connection does not work. Huge issue, might try reverting the radio.
Click to expand...
Click to collapse
I seem to have found a reliable way to correct this. Was playing around with VoLTE and found this to be a contributor. If you have VoLTE enabled in 5.1 ROM, that is under Settings>Wireless&networks>More>Cellular networks>Enhanced 4G LTE Mode. When I turn off this option, post connected call digit dialing seems pefect. Switching it back on goes right back to not able to recognize.

Verizon note 8 on AT&T Calling error!

Hey everyone,
I have a bit of a weird issue here. I have a note 8 from Verizon which everyone knows comes unlocked. I am using it on AT&T and everything works well except for one thing. For some reason when I receive phone calls from people, it shows on the screen with a + sign in front of the phone number. So if someone calls me that is in my contact book, it will not show their name since there is no + sign in my contact book. So also now in my call history if I try to call that number back it sounds like it is trying to make an international call. I have no idea what is happening. Data, texts and calls work but instead of getting a call from 9999999999 I get +9999999999.
Please help me out here, I love the phone!!
Zachary

I've read about this issue before. Googling 'incoming calls show +' gives you some leads.
In short it seems to be related to Dialling Assistance settings (note spell error, is as in settings...). I couldn't find those via the regular settings (used to be accessible via settings in Phone app), but I could via the app 'Shortcut Master (Light)' ...
Search for 'dialing' and then launch:
'com.android.phone.operator.usa.AssistedDialingActivity'. My settings (N950U1) are as per SS...
Try playing with these settings.