Greetings,
I recently bought a used Note II and that the seller had already informed me of this problem but I can't seem to figure it out;
Input on the mic and output on the earpiece doesn't seem to work during phone calls. Though any other app isn't affected by this. Apps that had been tested are: Messenger (Facebook), Camera, and Snapchat all are working flawlessly except for the Phone app. And here's a more "bizarre" scenario, any other ROM that I install or Factory Reset that I do retains this problem, even Stock ROMs are affected by this.
And sort or form of help is greatly appreciated .
-FeitXX
-Model: N7100
-ROM: CM13.0
Related
Hello,
I am facing a problem with my DHD not recognizing the numbers saved with an international format:
I am currently in Lebanon; and since I tend to travel, I save my numbers using the international format:
+9613xxxxxx
When back in the country and someone tries calling me the number shows as:
03xxxxxx
This is where the phone fails to recognize the caller...
The problem only seems to happen with the zero prefix. We have other numbers that do not use a leading zero:
+96171xxxxxx
These show up locally as
71xxxxxx
The phone recognizes them without a problem.
I've tried contacting HTC and their reply was to add the numbers twice... not a very smart solution.
So I've tried using a different ROM (Core Droid 2.3) and the problem persists.
Someone suggested the problem has to do with the stored procedures in /system/lib/libsqlite.so and provided a replacement, however it was for android 1.6...
1) So does anyone know how to get rid of this issue?
2) Otherwise, is there a ROM that solves the problem (just need on that keeps the stock camera application and that is not too bloated).
3) If not, is there a way to obtain the source of one of the ROMs on this forum to try to fix the issue myself and recompile?
Thanks!
For anyone else facing the same issue:
Cyanogenmod 6.1 solves the problem.
Coredroid 2.3 does not.
I am now trying to download VillainROM to whether the problem persists there.
No luck with VillainROM...
The ROM includes HTC sense, the graphics are very crisp compared to CoreDroid and Cyanogenmod but the prefix issue is present... making the phone no better than a $20 device off the market... at least as far as recognizing incoming calls is involved...
For anyone checking this..
I've settled for Cyanogenmod 7
With googleapps and arabic addons
The vanilla keyboard's arabic is not working... I can't write much arabic anyway but did download one from the market.... worked with a few glitches.... but otherwise arabic works great when visiting news sites etc...
Gmail app is not working so I am using K9mail.. which, besides a couple bugs, looks very promising.
Youtube app is not working so I am simply using the browser.
I think I am happy with my phone again...
if you use root explorer to remove gmail and youtube from /system/app/ reboot and install them from the market, they should work again
Thanks for the hint!
I found several apk files in the /system/app... no youtube or gmail though...
Am I doing something stupid?
Thanks,
Ah... was being stupid allright...
I just reinstalled and everything is now working!
Thanks again!
Dear All,
This is the first time I am participating on such a technical forum. Please forgive me if I am a little lengthy in details. I own a Galaxy Note 2 N7100 in India. Mine is not a carrier locked unit as there is no such practice in India. I recently installed CM 10.1.3. RC1 on my phone. The installation was perfect and after installation the phone seemed to be working perfectly. I installed a large number of apps that I regularly use and there was no problem. However, later on when I tried to connect my phone with my Fiat Linea Blue & Me system via Bluetooth then it got connected with great difficulty but the phone and contacts app crashed. Thereafter if I dialled a number from my phone I could neither hear the ring going through to the other number nor the voice of the person on the other side even after the phone was connected. However, the person on the other side was able to hear my voice perfectly. I disconnected the bluetooth but the problem was not solved. I did a factory reset and without installing any apps again connected my phone to Jabra BT & Fiat Blue & Me. this time everything worked flawlessly. However, after having installed all my apps, the problem resurfaced. Finally i was compelled to unroot my stock rom and everything is back to normal. All the apps are still installed and everything works fine.
Someone please guide as to what might be the problem. I have nearly 70 apps on my phone. Can anyone please help me?
I've got the same problem. I use the final version 10.1.3. When I want to turn on Bluetooth, it instantly turns off. I've got no idea what this is. Maybe the next release helps.
Sorry for bad English.
KitCrafty
Hello,
I know that this would be better posted to one of the development forums but (new member) can't post there...
anyway, I have the captivate glide and I recently installed literom from the greater good. Anyway, I'm running into some bluetooth issues and I was wondering if anyone has had any similiar issues? The forum for that rom does not mention the issues that I'm having (at least not that I found).
Basically, my bluetooth works fine. As long as I don't reboot my phone. Any time I reboot, my pairing information is lost for any devices I had. I can scan for devices, but when I try and connect, it says invalid pin or connection refused. If I run through the pairing procedure again, it works until the next reboot.
Anyone have any ideas for me? I like this rom and don't want to re-image it with something else... my bluetooth worked fine on the last rom I had installed (but nothing else did pretty much, which is why I reimaged it)...
sorry for throwing this out in the general forum, but to be honest I'm not 100% sure that my issues are related to this ROM just mostly sure... anyway, any help would be greatly appreciated.
Hey guys!
I installed Cyanogenmod just a few days ago for the first time.
I was (and still am) very happy with the replacement, but I ran into one issue related to sound. Before I installed cyanogen (on the default ROM) I had an issue with the Skype app: my voice sounded like a chipmunk. I thought it was a Skype problem. After installing this problem was FIXED! I was really happy. But then somebody called me on the ordinary phone and THEIR voice was distorted terribly and I was unable to hold conversation. I googled feverishly and found an "audio policy.zip" in a forum post related to a similar problem. It said I was to flash that file. And I did. Voila, the issue was indeed fixed! BUT, now Skype doesn't get audio input from me at all, and Viber also has a similar problem. So essentially I fixed one problem but got another instead. My guess is that the audio policy file wasn't perfectly configured for my specific phone, and...
that's what I need help with. Either to get a pre-configured file for my specific phone, or for somebody to help me configure it manually. This is what my current file looks like: pastebin.com*ZaTXd1UZ (replace * with / ). Please help.
Asking this for a friend who has an S9. I have an S10, so I have some familiarity, but we're still fighting with the problem. Here's the story:
He was on TMobile. I suggested he try changing to Total Wireless (Verizon MVNO) as I have had good luck with them. He switched and things were working fine for a few weeks.
Nothing on the phone was changed, but then about 2 weeks ago, his text messages weren't going through, particularly to iPhone users. Normally, we'd think this is a problem on the iPhone side, but nothing changed there either (his wife's iPhone)... in addition, this happened with multiple iPhone users, so it's not just one person...
We've done a ton of digging, contacted the carrier, they contacted VZ for help, tried different apps (stock, Google Messages, etc)... no one has been able to figure out the solution. The most recent finding was that the stock Samsung messaging app works fine for all users, but GMessages continues to have problems. With regard to GMessages, we have checked and confirm that iPhone users are getting detected at "SMS/MMS" and not RCS, so that doesn't appear to be the issue either.
APN settings match what I have (I have no problems with my S10 with any users - iPhone or otherwise).
Only remaining thing I can see is that his phone is seeing a CSC of TMB/XAA/SPR (mine is TFN/TFN/SPR). I think it could be due to the TMB/XAA he's seeing, but the carrier thinks this is not the issue. His ROM is showing up as SM-G960U_OYN_TMB.... I wonder if it's because it's U (instead of U1) so it's unable to switch to TFN?
Anyone else have any ideas on what could be going on here? Since the stock app works, it seems it's not a carrier issue... but I still don't get why that would fail to work on GMessages when it works fine on the stock messaging app?
Any ideas appreciated. We're quite technical and able to do all sorts of things (ODIN flashing, etc)... so nothing is off the table. Just trying to figure out how to fix this.
Bump - no one has any ideas or theories? I'm in brainstorming mode, so no idea is not worth trying!