Hi
Just got a new S Cover with wireless charging for my Note 3. The charging and NFC work quite well.
Phone unlocking by flipping the cover works perfectly. I can also accept or reject calls using S View.
The problem is with the idle S View mode. On the bottom where the camera, missed calls (if there are any) and (I presume) settings buttons are there is some sort of overlay stating "Open the Cover" which doesn't let me use the buttons.
The phone is N9005 Note 3 running official 5.0 OTA update.
Couldn't find anything resembling this so I hope you guys can help.
I have previously used non-wireless S Cover whilst still on Android 4.4 and it worked fine.
I haven't tried to use that with Lollipop because it wasn't compatible wireless charging and it seemed more important to me.
Not sure if that is important, might try to find it and try if that works.
Related
I started a thread before, but found out it could be a software problem as a lot of demo units' compasses don't work all the time.
S4 has this problem too.
I have the N900W8 device, if that makes a difference.
Fill the poll out above to answer ^, or just comment down below.
Same problem here
nicholaschum said:
I started a thread before, but found out it could be a software problem as a lot of demo units' compasses don't work all the time.
S4 has this problem too.
I have the N900W8 device, if that makes a difference.
Fill the poll out above to answer ^, or just comment down below.
Click to expand...
Click to collapse
Hi, nicholaschum.
I've the same problem. Mi phone is a N9005 (europe free note 3).
I agree that is a software problem, as if you calibrate the compass sensor (*#0*#) it runs without problem until I restart the phone.
I've also tested several demo units at a samsung store and all of them (galaxy s4, note 3, s4 mini) presented the same problem.
The technical service guy told me that they can change the motherboard of the phone, but I doubt that itgonna fix the problem.
There is a lot of threads, here on XDA, but also in other forums reportinf the same problem on several samsung devices...but unfortunately without solutions.
I'm very pessimistic about this problem, due to that we're more concerned about getting new versions of android instead of get this kind of issues fixed.
Sorry for my english!
Mine's accurate in Smart Tools. DBT N9005 4.4.2 NB7
The calibration does seem to get lost upon a reboot, but you do not have to go into the service menu to recalibrate it.
When you are in google maps, simply rotate your wrist (not your arm). Rotate your wrist around and around about 3-4 times (no need for anything more than this so only takes 5 seconds). And then I find everything works just fine.
You shouldn't have to do that after every reboot, but its not too bad if you realise you don't need to go into the service menu and the right movement to recalibrate it quickly.
I've read quite a few comments that the Nexus 4 does have HD Voice, but could anyone confirm whether or not this is the case on 4.4.2 (stock)?
Me and the other half are both on 3 (UK), which supports the feature. I'm using a Nexus 5, and her a Moto G at the minute whilst I'm replacing the USB socket on the Nexus 4. At the minute, we both get the HD voice feature when calling each other, but the minute either I or her use the Nexus 4 it's just a standard call. I've seen a few reports and posts from around the time the phone came out confirming it did, but nothing more recently. I did see a very slight mention that it's been removed from the latest software but nothing to back it up and no follow up on it. So when I've replaced the socket I'm going to have a go putting 4.2 on there and seeing if it works then. I guess if it does it confirms it's been removed from the latest firmware and I'll have a look at custom roms, and if not I've either got a hardware issue or something else is amiss.
I have a 910C updated to NK5 and am only able to use the IR blaster sporadically, i.e. it works once then stops a few minutes later. I've read that this only affects certain Note 4 models, I've tried several IR apps and all have the same issue so it's definitely not app related.. According to Anymote comments, they mentioned that the workaround involved modifying the way the Note 4 sends out the IR codes or something.
Please mention:
- Your model version
- Build number
- Success percentage of IR signals (ex. mine is less than 20%)
SM-N910C
KTU84P.N910CXXU1ANK5
Less than 20%
gabster21 said:
I have a 910C updated to NK5 and am only able to use the IR blaster sporadically, i.e. it works once then stops a few minutes later. I've read that this only affects certain Note 4 models, I've tried several IR apps and all have the same issue so it's definitely not app related.. According to Anymote comments, they mentioned that the workaround involved modifying the way the Note 4 sends out the IR codes or something.
Please mention:
- Your model version
- Build number
- Success percentage of IR signals (ex. mine is less than 20%)
Click to expand...
Click to collapse
SM-N910C
KTU84P.N910CXXU1ANK5
Less than 20%
as well
this sucks!
IR Blaster
Att Note 4
N910a
KTU84P.N910AUCU1ANIE
Functions about 100% of the time when I use it with "Smart remote". Loads my vizio, apex, samsung, lg, tv, receivers, etc. All of which when I find the code that works best, work great. Only thing is that it has a slight delay, so when I mash on the button it will keep firing long after if I click it like 30 times in 2 seconds, it will do it 2-3 times a second, untill it caught up with it.
I wrote to Samsung support about the issue, their solution involved blaming 3rd party apps for the issue and suggesting using their soon to be decommissioned What's On application that obviously didn't work. Absolutely useless.
Solution found.
1. Clear the settings of smart remote app, Remove the updates of smart remote app using application manager, and force close it and reboot the mobile.
Its the latest version of it that breaks the IR. The guys paying someone for the fix are being scammed most likely.
The older version send IR signals in a slow fashion and it works perfectly fine. The latest version overdrives the IR module hardware capacity i guess and it breaks it....
Thanks
SM-N910U
KTU84P.N910UXXU1ANK7
Less than 20%
---------- Post added at 01:19 AM ---------- Previous post was at 01:08 AM ----------
ravian720 said:
1. Clear the settings of smart remote app, Remove the updates of smart remote app using application manager, and force close it and reboot the mobile.
Its the latest version of it that breaks the IR. The guys paying someone for the fix are being scammed most likely.
The older version send IR signals in a slow fashion and it works perfectly fine. The latest version overdrives the IR module hardware capacity i guess and it breaks it....
Thanks
Click to expand...
Click to collapse
It doesn't work for me, the latest is built-in in the firmware. And it seems the problem is from the IR driver not the software itself. Otherwise you can just install a 3rd party software to fix it.
Darnit...same here! At first after starting up the Smart Remote app it works fine, and after a while it stops working. rather anoying as I like this feature on my phone. Comes in very handy when watching TV and the phone at same time and needing to adjust volume or switch channels.
No option to remove any updates for the Smart Remote app in my case unfortunately.
N910C
Stock, latest software version
For me worked after a reboot using a 3rd Party App. It seems to die after sometime that the device is on. I really like this feature, in special because it save space to avoid to carry several remote controls with me.
I have the same problem, my IR blaster was working fine and it stopped working suddenly after the lollipop update.
I tried all solutions proposed by members in this forum and other forums (clearing cache, force stop the app, uninstall updates, restart) nothing seems to work!
SM 910c with lollipop 5.0.1
any suggestion guys?
same to me now it never work.
N910H
same to me after upgrading to lolipop 5.1.1
the infra red is not operating at all anymore..
I tried to uninstall the app and install it again, and tried different apps but no luck..
I also checked the infra red with another mobile camera but no indication that the infrared diode is operating though the upper blue led is functioning ok and is behaving always in the correct matter,
So i think its an issue regarding software....Are samsung aware of this frustrating problem?
should I return it to the agent since it is still under guarantee its onley 8 months..
any help will be greatly appriciated
I have a N910G and my IR blaster only works if I remove the plastic frame from the back of my phone.
Hey all. I just got my Note 3 two weeks ago and I love it. The battery life is great, great specs, unlocked bootloader, and I find it easier to use in terms of size compared to the Galaxy S5. There is only ONE problem with this device.
The mic stops working during skype calls after random periods and the only solution is to hang up the call and call again. This lingers even after restarts of the app and phone.
Being a Nexus user since the Galaxy Nexus, the first thing I did was install TWRP and the latest CM nightly. I personally can't stand Touchwiz, which is why I sold my bootloader-locked GS5 to get this bad boy.
Has anyone else encountered this issue? Is it a Skype problem? Is it CM? Lollipop? My mic is fine, it works perfectly in every other application.
Also, I've noticed that USB 3.0 mode doesn't show up in the Connection type selection menu. Is USB 3.0 file transfer only supported in the stock kernel?
I gather many people are having connection issues with their Android Wear devices.
Is this just a Note 3 issue?
Has anyone managed to get a stable connection using Lollipop?
Yes, my Note 3 with Lollipop (tested many ROMs, even the Note 4 ports) has this issue, and it's not only with Android Wear, but with several other Bluetooth LE devices. I've heard mixed explanations: some say it's something with Lollipop itself, affecting many phones (unless the manufacturer added patches to solve the issue), and Google solved it with Lollipop 5.1; others say it's something only with Samsung's Lollipop ROMs. The latter may be true, as @civato apparently solved the issue tweaking the kernel.
Some people say their phones don't have this issue, but I suspect it's because they haven't put their BTLE devices under the failing scenarios. I have a very easy test case:
1) Pair your Android Wear watch with your phone, using the Android Wear app. Make sure the watch is communicating with the phone.
2) Create a situation where your watch loses connection with your phone (e.g. walk away with the watch, put it in a Faraday cage etc.). But make sure it stays that way for some time, say 10-30 minutes (sometimes it happens as soon as it's out of range).
3) Notice that even though the watch is disconnected (the "no cloud" icon is shown), the Android Wear app on the phone will show it as "connected". Now even if you bring the watch close to the phone again, it will not reconnect automatically.
The same thing happens with other BTLE devices. Other symptoms include frequently disconnects / reconnects, even when the device is in range.
Mine has paired but refuses to connect now. I'll try Civ kernel.
Is there a Lollipop Civ kernel lol
Some problem here with my Sony Smartwatch. The new XEO Update don't fix the Bluetooth problems complete. Is any fix released to fix the Bluetooth Connection problems?
I had all sorts of problems on both the leaked Lollipop and the official Lollipop. It was driving me insane with its constant disconnections/reconnections and then just disconnecting until Bluetooth was cycled. It made the watch useless!!!
I then tried Dark Lords N4 port (v1.5). Boom! All working perfectly. No more issues at all and reconnects if i move out of range seamlessly.
Same problem, Note 3 XEO with Sony SW3. So maybe for now there is only way - root with knox 0x1 and N4 port ROM...
Had a few issues after getting Lollipop but nothing compared to the issues I got when Android Wear updated (on Friday I think it was).
My Moto 360 just wasn't wanting to connect, tried rebooting phone, then the watch, but didn't help. In the end I factory rest my watch and its been fine since.
Vince
Yep, bluetooth all over the shop...Headset and Moto 360.
I also have a lot of problems with Sony SW3 and Note 3. Not only I have inconstant BT connection, but also weird management of incoming phone calls: watch notifies phone calls that appear on the teleohone only 3 or 4 seconds later (that's a huge time).
Anaother issue: I have also tried to decline a phone call with the Smartwatch but the telephone went on ringing.
Inviato dal mio SM-N9005 utilizzando Tapatalk