SPEN is always disconnected. - Samsung Galaxy Note 10+ Questions & Answers

I got this problem after I factory reset my phone(I think?) I already tried everything I could, and I know that the SPen isn't the one causing it cause I tried another SPen from another Note 10+ and it isn't working, and I insert my SPen to another Note 10+ and it is working fine.
I'm also updated to the latest software, using Exynos Variant and not rooted.

Found this for you. Give it a shot.
Good luck

louforgiveno said:
Found this for you. Give it a shot.
Good luck
Click to expand...
Click to collapse
Sometimes you have to do a couple times over a couple days. For some reason the spen cap/battery isn't charging so nothing happens when you try to use it.
Mine did the same thing but after a couple resets over a couple days it finally started working normally. It's been fine ever since.
I tried clearing app data, clearing system cache, a hard reset and maybe a network reset. Don't think any of that fixed it. Think was just doing the spen resets and taking the spen out/in... cycling it. It needs wuv too I guess
Play with it.

Related

[Q] Issue after ICS update - Phone freezing

After the ICS update on my non-rooted phone, the phone seems to be freezing
up and becoming unresponsive. After a while it looks like the radio "resets", all
the icons disappear in the top bar (signal, wifi, data) and it shows no service.
Then slowly one by one they all come back and I can use the phone again.
Sometimes I receive the "System is not responding" dialog box, but not always.
There is not one particular program it is doing this in, it can be something as
simple as pulling down the notification bar that will cause the freeze.
Any suggestions are appreciated, I couldn't find anyone else with the same issue.
Thanks.
Try:
Turn off phone
Take out SIM
Put SIM back
Turn on
I've had my phone act weird with respect to signal, wifi and data when this was the issue. Worth a shot, at the very least.
Digital_Buddha said:
Try:
Turn off phone
Take out SIM
Put SIM back
Turn on
I've had my phone act weird with respect to signal, wifi and data when this was the issue. Worth a shot, at the very least.
Click to expand...
Click to collapse
Thank you for the response.
Tried this and had the system is unresponsive issue right on reboot. If I do a
factory reset, does it reset to the current firmware or what was originally on the
phone (probably a really stupid question). I wonder if some other program isn't
ICS compatible and is doing something in the background. Doesn't look like
anyone else is having this same issue.
jdscully said:
Thank you for the response.
Tried this and had the system is unresponsive issue right on reboot. If I do a
factory reset, does it reset to the current firmware or what was originally on the
phone (probably a really stupid question). I wonder if some other program isn't
ICS compatible and is doing something in the background. Doesn't look like
anyone else is having this same issue.
Click to expand...
Click to collapse
If you do a factory reset and it was the standard Kies legit update from Tmo, it won't downgrade your phone - will just re-install a fresh copy of your ICS. Did you do a restore of apps from your last version (gb?) with data? That could cause problems I would think..
VoiD_Dweller said:
If you do a factory reset and it was the standard Kies legit update from Tmo, it won't downgrade your phone - will just re-install a fresh copy of your ICS. Did you do a restore of apps from your last version (gb?) with data? That could cause problems I would think..
Click to expand...
Click to collapse
Yes I did the legit update on Kies, standard stock phone un-rooted.
Do I need to backup pictures before the reset, its been a while since
I had to do this.
At this point, I think its worth a try to wipe it clean and clear out all the
data.
jdscully said:
Yes I did the legit update on Kies, standard stock phone un-rooted.
Do I need to backup pictures before the reset, its been a while since
I had to do this.
At this point, I think its worth a try to wipe it clean and clear out all the
data.
Click to expand...
Click to collapse
wipe the dalvik cache and cache then reboot
I did a factory reset and that solved the issue.
Thanks for all the assistance.
I've done a factory reset and wiped the cache more than once already and i still get a force close or unresponsive, enough that its really irritating me now. Any advice? And also, when texting, the typing responds very slow.
Sent from my SGH-T989 using XDA
itsdamage said:
I've done a factory reset and wiped the cache more than once already and i still get a force close or unresponsive, enough that its really irritating me now. Any advice? And also, when texting, the typing responds very slow.
Sent from my SGH-T989 using XDA
Click to expand...
Click to collapse
Are you letting it sit for like 10 minutes during first boot after factory reset then reboot again before setting up. Its likely that some scripts are running from the initial installation and you need to let it rot until its done..
I did exactly that, thanks for the advice. Hoping that may fix the problem. I wiped the cache and factory reset, then let the phone sit for a good while before going through the play store and re-installing everything.
This issue just resurfaced again. The last 2 days I am getting the freezing, radio reboot and android process not responding.
No one else having this issue?
I think I'm in the same boat. I was stock GB, and just did the mini OTA update (which was great). A few days later ICS became available via Kies from T-Mobile, and I "upgraded".
Since the upgrade my phone is laggy, screen is significantly less responsive and also my battery life is less than before.
I have NOT done a factory reset of my phone yes (plan on doing that today), but even with that I have read that performance does not improve.
Ideally, I would love to return back to the stock tmobile gb firmware. However, even after literally 2 hours of reading I can't find the "how-to" and files I need.
I would appreciate any assistance.
t989 chip lags
ive notice this happen on my tmobile galaxy s2. i think it has to do with the Qualcomm chip on tmobiles stock roms.
When i had sprint i bought my girlfriend a galaxy s2 on the sprint network which runs the samsung exynos chip. She never complained about any lag or freezing whatsoever. I then left sprint because of their garbage network and joined tmobile.
bought 2 galaxy s2s and i noticed the lag almost immediately. The phone has random lag spikes as well as freezing and force closes. It had it on stock gingerbread and it has it on stock ICS too.
My girlfriend complains about freezing all the time so i decided to root her phone too. Right now im testing DarkSides v7 rom and if its pretty good in performance i will flash her phone with it too. So far it has been pretty snappy and everything works.
jdscully said:
This issue just resurfaced again. The last 2 days I am getting the freezing, radio reboot and android process not responding.
No one else having this issue?
Click to expand...
Click to collapse
Yes i have the exact same problem...and the clock goes off too...if i don't reboot then this will keep happening...if you go into settings then development settings and tick off only let 4 process run in the background it should stop...try it and let me know
Sent from my SGH-T989 using xda premium
tonydetroit said:
I think I'm in the same boat. I was stock GB, and just did the mini OTA update (which was great). A few days later ICS became available via Kies from T-Mobile, and I "upgraded".
Since the upgrade my phone is laggy, screen is significantly less responsive and also my battery life is less than before.
I have NOT done a factory reset of my phone yes (plan on doing that today), but even with that I have read that performance does not improve.
Ideally, I would love to return back to the stock tmobile gb firmware. However, even after literally 2 hours of reading I can't find the "how-to" and files I need.
I would appreciate any assistance.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1668502
follow that first post. i went through exactly the same problems and found this guide and am now happy again and running stock GB on my Galaxy S2.
Because you are on stock ics (im guessing you are..), you can just follow that guide and flash the UVLDE update.
Yes clock resets to standard standard time.. I already did a factory reset and worked done for a couple weeks. My wife has same phone and she is getting the freeze ups now.
jdscully said:
Yes clock resets to standard standard time.. I already did a factory reset and worked done for a couple weeks. My wife has same phone and she is getting the freeze ups now.
Click to expand...
Click to collapse
Yeah really sux...it's random..I'm using a custom kernel and still having that problem....
Sent from my SGH-T989 using xda premium
Yup here too. Almost reminds me of XP. Really ticking me off & it never happened on gingerbread. Rooted now & before I'm on rogers 4.0.4. wondering if there's going to be fix? Haven't seen if Google / rogers /at&t have commented?
Sent from, The Eclectic Chair.
I'm getting the freezes as well even after doing a factory reset.
It sucks, I'm waiting for cyanogen to release a stable release and then I'm switching.
djtheraven said:
Yes i have the exact same problem...and the clock goes off too...if i don't reboot then this will keep happening...if you go into settings then development settings and tick off only let 4 process run in the background it should stop...try it and let me know
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Thanks for the suggestion, I'll give it a try. But it really shouldn't be necessary on a phone that's got more going for it than the stock nexus that 1st came out with ics.
There's something else going on.
Sent from, The Eclectic Chair.

Camera, Gallery and Talk doesn't work

So I got the Galaxy Nexus GSM today and it's one hell of a sexy device.
It obviously came with Ice Cream Sandwich out of the box. And errors out of the box. Right when I start the phone, Talk FCs. When I try to start the Camera, it FCs.
I though "What the heck, Jellybean probably fixes that", so I unlocked it and flashed Paranoid Android. Everything is a lot faster now, but I still have the same problems, except now Gallery just crashes, which renders the Camera unusable, because they're apparently linked together in Jellybean.
I tried 3rd party apps (Zoom Camera, Paper Camera and a few others) and none of them work.
So it seems that everything that has something to do with the Camera doesn't work.
I tried everything that I could think of;
Reflashing
returning to stock
force stop Camera
Disable and enable all network related functions in G+ and Gallery
Clearing cache - both for individual apps and the option from the recovery
Trying 3rd party apps
Googling everything I could think of
Installing G+ (that made me able to open Gallery, but Gallery still force closes when I open Camera)
Changing battery
Of course I can't see it being anything but a hardware issue, but some people who have compiled CM10 by themselves have the same errors. I don't know if that helps me.
So before I return it some time this week, does any one have any suggestions to what I could try?
I'll give this thread two days before I return it.
Thanks in advance.
You rooted? If not and you know how to root, root it, replace the app (gallery, camera, whatever is not working) with stock JB version. Hopefully it's just corrupted apps... That's easy to fix
Thanks for the reply. I've already tried the Jellybean version of Paranoid Android and it made no difference.
I though "What the heck, Jellybean probably fixes that", so I unlocked it and flashed Paranoid Android. Everything is a lot faster now, but I still have the same problems, except now Gallery just crashes, which renders the Camera unusable, because they're apparently linked together in Jellybean.
Click to expand...
Click to collapse
mrhaxx1 said:
Thanks for the reply. I've already tried the Jellybean version of Paranoid Android and it made no difference.
Click to expand...
Click to collapse
Might be a long shot, but have you tried fixing permissions in recovery?
Sent from my Galaxy Nexus using xda premium
I have, but I just tried again and it made no difference.
Also, I forgot to mention that it's not a storage issue, as I can save screenshots just fine.
mrhaxx1 said:
I have, but I just tried again and it made no difference.
Also, I forgot to mention that it's not a storage issue, as I can save screenshots just fine.
Click to expand...
Click to collapse
Any solutions for this yet? having the same problem.
Nope, nothing yet.
And to make the bad things worse, I've lost the receipt. So I can't even return it.
Bumpity bump!
mrhaxx1 said:
Bumpity bump!
Click to expand...
Click to collapse
I just went ahead and called verizon.. and they're shipping me a new phone today. I see a lot of posts about this, with no solution. It'll be quicker to do it this way. Except you call whatever your carrier is. Or samsung, if nothing else.
Well, you see, I bought the phone refurbished. There was a guarantee on it, but I lost the receipt, so I can't return it or get a new phone.
I ordered a rear- and front-facing replacement camera. It should arrive in 7-15 days because I'm ordering from the USA.
I looked into it, and disassambling and assembling it should be fairly simple. Nearly the same process as the Nexus S, which I've disassembled before.
If it doesn't work, I've only lost $22 and it's not like I have a valid guarantee on it anyway.
Oh well, replacing the cameras didn't work.
And I even managed to break the volume buttons.
Even if I got hold of the receipt, there would be no way they would repair it now.
I can as well just go buy a new phone. Next month. Maybe. At least everything else still works.
When you flash ROM, do you ensure you completely wipe previous ROM and data? Also, if you use something like Titanium Backup to restore your apps after flashing a new ROM, make sure you don't restore system apps or data. That will definitely screw things up in every ROM as incompatible files are mixed.
Try doing a full wipe of your device it could help
Sent from my Galaxy Nexus using xda app-developers app
It was like that on the stock rom.
And yes, I always ensure to wipe everything. As said in the OP, I even tried returning back to stock.
I got the same problem, I GOT IT FIXED NO HARDWARE FAILLURE!!
Hi,
this is what i did, got it fresh from the box, didn't even bother to set-up, I instantly updated to Jelly Bean..
everything worked perfectly, besides the camera, it crashed instantly.. (gallery did not respond)..
i rebooted it 2 times, then pressed the Power button + volume down.. it went to an system boot thingy.. the i connected it to my pc with an usb (usb debugging enabled).
my win7 pc said the drivers were installed, then i pressed the power button. after loading. the camera worked perfect.. thats REALY everything i DID.. i'll keep you posted if it fails again.
it also worked after unplugging the usb.. Hope I helped you a bit.
I can second this fix!
IvanGrozni87 said:
Hi,
this is what i did, got it fresh from the box, didn't even bother to set-up, I instantly updated to Jelly Bean..
everything worked perfectly, besides the camera, it crashed instantly.. (gallery did not respond)..
i rebooted it 2 times, then pressed the Power button + volume down.. it went to an system boot thingy.. the i connected it to my pc with an usb (usb debugging enabled).
my win7 pc said the drivers were installed, then i pressed the power button. after loading. the camera worked perfect.. thats REALY everything i DID.. i'll keep you posted if it fails again.
it also worked after unplugging the usb.. Hope I helped you a bit.
Click to expand...
Click to collapse
So, I was having this exact same issue and was ready to call Verizon for a replacement, when I tried this as a last resort and VOILA!! IT WORKED! I am still unsure of how this all came about, but for the purpose of hopefully helping someone with the same issue, I will second this quick fix as IT DID WORK FOR ME.
I had this same problem (camera/talk fc'ed on start, whenever opening either app), tried all the fixes I could and nothing worked. I eventually disassembled the phone and used a toothbrush and isopropyl alcohol to clean the main board and the connections for each of the camera modules. After a couple rounds of cleaning, everything started working again.
navjas73 said:
I had this same problem (camera/talk fc'ed on start, whenever opening either app), tried all the fixes I could and nothing worked. I eventually disassembled the phone and used a toothbrush and isopropyl alcohol to clean the main board and the connections for each of the camera modules. After a couple rounds of cleaning, everything started working again.
Click to expand...
Click to collapse
Thanks for this information, I'll try to do it with mine too. Any results I will post here.

[Q] Problem since root

I finally rooted it yesterday and it now is very unresponsive at times. It will get to the point where it's frozen for about 30 seconds before it does anything. I flushed the caches and did a reset, same thing. So I flashed Jedi ROM on it. It's a little better but still has moments where ti freezes for a time. Is there a fix for this?
Rooting does absolutely nothing to the performance of the device. Its comparable to giving yourself admin rights on a windows computer. No performance change just extra features. Might want to check any apps that you installed after rooting
I did not install anything after root.
It works smooth as silk with the stylus. Possible sensitivity adjustment?
Maybe the sdcard needs to be reformatted?
marksm said:
I did not install anything after root.
It works smooth as silk with the stylus. Possible sensitivity adjustment?
Maybe the sdcard needs to be reformatted?
Click to expand...
Click to collapse
ROOT will not brake the phone or cause lag. it changes nothing internally except rights to your phone. no tweaks or files deleted. I can see it being something with the screen since you say the pen works great and using your finger I assume it micro stutters. but even the freezing for 30 sec does not sound screen related. I would wipe and format data, and then try another Rom. I used jedi from the first build all they up to 15 and it ran like a champ. its something you are doing, or have not undone yet.
I would suggest clearing caches. Its got nothing to do with rooting, but neither does rooting have to do with lag.
It sounds like an app was restored with data.
rangercaptain said:
I would suggest clearing caches. Its got nothing to do with rooting, but neither does rooting have to do with lag.
It sounds like an app was restored with data.
Click to expand...
Click to collapse
Agreed....
Excellent point ranger.....TY.....g
Sent from my SAMSUNG-SGH-I317 using XDA Premium HD app
no apps were restored either. When I flashed the new ROM I cleared every cache I could see listed and wiped it clean. All I can think of is the old stuff on the sdcard is causing issues so tomorrow I will reformat it and reset again.
Well then, the only thing I can think of is you flashed an incorrect kernel. What exactly did you flash?
Used the root tool from http://galaxynote2root.com. Odin and cwm6-root-note2.tar.
It still had the bad lag and freezing after I un-rooted it and restored the original ROM.
I have since flashed Jedi, didn't like it and now am on NOTEorious Prime.
What I have noticed is that the lag and freezing go away when I am connected to a wireless network. Maybe it screwed up my modem?
And have you verified the APN settings as being correct ?
Or they may simply be mixed up by default..
It may be set on ATT LTE.....instead of ATT PHONE for example...
Both will work...but one will drop the network speed by about 70%...
Just a thought....g
Sent from my SAMSUNG-SGH-I317 using XDA Premium HD app
Perhaps a factory reset from within recovery --- to make all settings default. By now there's a lot of stuff floating around in there.
Why would the original root change the APN settings.
I have factory reset several times. Even with the factory image applied fresh, it still freezes. The weird thing is, it responds just fine to the stylus.
I am at the point where I restore the stock ROM again and take it to ATT to see if they will swap it out.
Thanks for the help, keep the ideas coming..
Flashing a custom rom or recovery or kernel voids your warranty. Please don't tell us about plans to return the phone to at&t. The phone worked as expected before you began flashing.
It's not the radio or wireless either. It works perfect with the stylus but seems like it doesn't detect my finger to operate normally. Does Samsung have a tool to reset the display sensitivity?
There is a dial code for the touch screen. I don't know it, but I've found those codes by googling 'android secret note 2 dialer codes' or something like that.
Looks like I have it fixed.. It's working right since I followed the instructions here http://android.stackexchange.com/questions/39423/galaxy-note-10-1-does-not-recognize-finger-touch
I had installed swiftkey so I removed that and tried swype beta and it's all good now.
I restored everything back to stock and it is still having problems. The screen is unusable with my finger, I have to use the S Pen for everything.
Would reloading the stock ROM with kies be different than using Odin? Does Samsung put some key piece of code in the areas that get changed with rooting?
I am at a loss..
marksm said:
I restored everything back to stock and it is still having problems. The screen is unusable with my finger, I have to use the S Pen for everything.
Would reloading the stock ROM with kies be different than using Odin? Does Samsung put some key piece of code in the areas that get changed with rooting?
I am at a loss..
Click to expand...
Click to collapse
Ok to test you touch screen etc. type this in code in your dialer *#0*#!!
And don't think Sammy would put something in there, to make there phones not work correctly!
Me 2¢®
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4
Bajanman said:
Ok to test you touch screen etc. type this in code in your dialer *#0*#!!
And don't think Sammy would put something in there, to make there phones not work correctly!
Me 2¢®
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4
Click to expand...
Click to collapse
On the test screen, I have to tap screen many times until it finally registers. Then I drag my finger around for about 30 seconds before it starts picking up and filling in the boxes. It will finally let me fill in all the boxes and say it passes but it takes a lot of effort.
marksm said:
On the test screen, I have to tap screen many times until it finally registers. Then I drag my finger around for about 30 seconds before it starts picking up and filling in the boxes. It will finally let me fill in all the boxes and say it passes but it takes a lot of effort.
Click to expand...
Click to collapse
Yeah it's not suppose to be that difficult honestly. Something is defiantly wrong!!
Me personally if you bought the phone from an AT&T store! I'd reborn it for a replacement! And if it's not used from someone off the street. Then I'll put it back to fully stock, reset flash counter. Then return and replace at one of there local service centers. Especially if it's giving that much problems as it sounds to be doing. Seems as if the screen has some hardware issues inside...
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4

Heartbeat Sensor after Lollipop

My heartbeat sensor will turn on whenever it's covered. Almost like a proximity sensor in a reversed fashion.
In the one call I've placed since the update I've also noticed the front proximity sensor having a major delay in turning the screen off after putting the phone to my face to talk.
Anyone having these issues? Any fixes?
I've used S health to measure my heart rate in an attempt to correct the issue like one guy mentioned but I think he spoke to soon as it is not a fix.
Sad to say, it was merely a temporary fix, I did speak too soon. I have since tried disabling S Health altogether and that still didn't fix it. Today, I'm going to attempt flashing all the way back to original firmware via odin and then taking the OTA's back to lollipop to see if anything changes.
phobia09 said:
Sad to say, it was merely a temporary fix, I did speak too soon. I have since tried disabling S Health altogether and that still didn't fix it. Today, I'm going to attempt flashing all the way back to original firmware via odin and then taking the OTA's back to lollipop to see if anything changes.
Click to expand...
Click to collapse
I did a factory reset, and have yet to launch S Health again since. So far, the sensor has not lit up again. I'm afraid to start S Health though. I will just use Runstastic for now
I don't have this issue. Before I updated to lollipop I did do a factory reset.
Sent from my SAMSUNG-SM-N910A using xda premium
To report back: I backed up, flashed back to 4.4.4 via Odin, took OTA to 5.0.1, factory reset, then restored data and signed into all my accounts again. It seems the solution lies in waiting for AT&T to clean up their mess. The problem has come back for me.
Sent from my SAMSUNG-SM-N910A using Tapatalk
phobia09 said:
To report back...The problem has come back for me.
Click to expand...
Click to collapse
Thanks for tanking one for the team!
At least we have gained the knowledge that going through a full wipe won't help :good:
i noticed this today when i was wearing gym shorts. restarted the phone and it disappeared, for now.
i use the sensor a couple times a day out of curiosity.
please report back if you find a fix
update: after reboot it went away, then i noticed as soon as i plugged it in to charge, it came back. i used s-health to check heart rate, then it went away again. unplugging/replugging into charger did not make it come back.
I was having the same problem and did a search online that I found fixes the issue. Just uninstall Google fit. If you need it, just re-install and the issue is resolved.
hamza786 said:
I was having the same problem and did a search online that I found fixes the issue. Just uninstall Google fit. If you need it, just re-install and the issue is resolved.
Click to expand...
Click to collapse
Uninstalled Google fit about 2 hours ago and have yet to see the issue return, thank you very much. I have yet to reinstall, though.
So are u guys with the sensor issue. Was Google fit installed with lollipop update?
Sent from my SAMSUNG-SM-N910A using xda premium
hamza786 said:
I was having the same problem and did a search online that I found fixes the issue. Just uninstall Google fit. If you need it, just re-install and the issue is resolved.
Click to expand...
Click to collapse
phobia09 said:
Uninstalled Google fit about 2 hours ago and have yet to see the issue return, thank you very much. I have yet to reinstall, though.
Click to expand...
Click to collapse
Uninstalled Fit, opened S Health, checked pulse, then had hr light stay on lol
But I like the idea of removing the app that causes it, I just think it's S Health, I tried disabling S Health and so far so good (but I'm pretty skeptical)

Phone keeps on freezing up.

Ok so here's the story. My wife had an S8 kept freezing took every single app off, factory reset, cleared caches everything that I could think of we have tried. So traded up and got her the Note 8 well the same exact thing is happening. Does anyone have any ideas. I just took the SD card out to see if it was that. So we'll see. Some one has to know what's going on. Verizon has no clue as usual. Next thing I will try is a new Google account.
Thank you in advance hope some one can help me.
Chabot1987 said:
Ok so here's the story. My wife had an S8 kept freezing took every single app off, factory reset, cleared caches everything that I could think of we have tried. So traded up and got her the Note 8 well the same exact thing is happening. Does anyone have any ideas. I just took the SD card out to see if it was that. So we'll see. Some one has to know what's going on. Verizon has no clue as usual. Next thing I will try is a new Google account.
Thank you in advance hope some one can help me.
Click to expand...
Click to collapse
What's freezing specifically? What are you doing before it does it? Are you using any app package disabler?
I found this video on YouTube. This is exactly what's happening. I'm not using any app disablers or anything like that. She just wakes up in the morning and it's frozen just like in the video.
I saw some comments on that video about the AOD so I changed hers to a different clock to see if that will also fix it. I also uninstalled Samsung pay as that was another comment on there.
BTW her phone is stock no root.

Categories

Resources