Related
Hello everybody,
I apologize for this post being so big but I had to cover all the details. I just got my new Galaxy Note N-7000(ceramic white) in India through Flipkart.com on 13th Feb. The phone worked fine the first day but since the next morning, I have been encountering a lot of problems. This is my first ever android phone so im pretty new to android and I am really scared if I might have gotten a defective piece. So please guys any help would be really great!
Here are some of my problems -
1. Phone restarted when moving apps from phone to SD card. Happened once.
2. Restart when changing the tabs in stock internet browser. Happened twice. Also the tabs move with a bit of lag. This is surprising with such high specs of the phone.
3. Restart when browsing the gallery. Happened Once.
4. Restart when connecting to usb mode through USB Utilities under settings>wireless and network>USB utilities. Happened Once.
5. Freeze when viewing gallery. Happened once and I had to remove the battery and reinsert and switch the phone back on because even the home button was not responding.
6. Freeze when trying to attend incoming call. Happened only once.
7. Advance task killer shows several apps open even if I never touched those apps. Mostly they are the default Samsung apps but sometimes a few apps I installed.
8. Apps like skype, viber, ect crash often and give a message 'application crashed and gives options to either force close or report'
9. Generally gets very hot even when browsing the internet or the market and burns like hell when gaming. The heating problem has reduced a little ever since I updated the firmware which Kies showed.
Guys, Im not sure if I am just panicking for nothing and if these things are normal but I feel such a costly phone with high specs shouldn't give these many problems. Plus I have installed only decent apps like skype, facebook, viber, astro, asphalt 6, blood and glory, angry birds, omnisketch, box, barcode scanner to name a few and they just fill only up to half the 4th app screen . I haven't installed any custom roms or have rooted my device yet as I am a complete noob. I havent even installed any apk's or apps outside of the android market or Samsung apps. Thanks in advance for any help!
First thing you should perform is Hard Reset.
backup your data then go to setting - privacy n Factory data reset (dont select to format USB storage. so data on SD card will remail as it is.
dr.ketan said:
First thing you should perform is Hard Reset.
backup your data then go to setting - privacy n Factory data reset (dont select to format USB storage. so data on SD card will remail as it is.
Click to expand...
Click to collapse
ok i will try this now and then install the apps back and let you know...but are you sure these problems are not a manufacturing defect or some hardware problem?..Hey btw what is the difference between hard resetting from the privacy settings and hard resetting by pressing the volume up+lock button+menu button?
Doesn't sound hardware related in my opinion. If hard reset doesn't work flashing a new rom will more than likely solve it. I've never had these issues though (other than apps auto starting on boot). Is there not an update available for the firmware?
Sent from my GT-N7000 using XDA App
dr.ketan said:
First thing you should perform is Hard Reset.
backup your data then go to setting - privacy n Factory data reset (dont select to format USB storage. so data on SD card will remail as it is.
Click to expand...
Click to collapse
Now that the topic has come up, Dr. Ketan.. Could you please explain the difference between a normal reset and a hard reset. I tried searching. Couldn't find an accurate answer.
adtyn_1991 said:
ok i will try this now and then install the apps back and let you know...but are you sure these problems are not a manufacturing defect or some hardware problem?..Hey btw what is the difference between hard resetting from the privacy settings and hard resetting by pressing the volume up+lock button+menu button?
Click to expand...
Click to collapse
You just check it first without installing extra application then after. If it occurs only after installing some stuff, it is just confliction with app.
Both methos are same, reset with recovery option is useful when you are unable to boot your device normally.
Technoholik said:
Now that the topic has come up, Dr. Ketan.. Could you please explain the difference between a normal reset and a hard reset. I tried searching. Couldn't find an accurate answer.
Click to expand...
Click to collapse
What i know is soft reset is just clear appl n memory from background, say simply rebooting device.
Hard reset will wipe all data except from System ROM, so making device as it was at time of purchase.
I also wanted to add that some apps will run in background. They are software update, samsung hub, samsung account, wifi sharing. etc. Apps like a keyboard or rdio will run in background.
Rooting the device allows you to have greater control and the ability to freeze apps so they can't run in background.
Sent from my GT-N7000 using xda premium
Reset device or full wipe do not help. Phones not see watch. Please help!!!
Go in parameter to enable ?
Where to look? I can not find.
With the screen on, hold the button in. That will bring up different settings
fr0st420 said:
With the screen on, hold the button in. That will bring up different settings
Click to expand...
Click to collapse
The first paragraph of brightness. The second device. Item no bluetooth. Paragraph device shows "Bluetooth is currently disabled"
Check if Airplane mode is not activated in parameter.
dersie said:
Check if Airplane mode is not activated in parameter.
Click to expand...
Click to collapse
I have the same problem. All started with the HTC One M7 problems with no audio during calls.
Did Full Wipe on the phone, reinstalled, finally got it working but couldn't connect the watch to Android Wear.
Restored Android Watch and data with Titanium but still nothing.
Finally read that you have to reset the watch. Did that and now I'm stuck on the "Install Android wear on your phone" screen.
I've tried connecting to the watch with different phones without any success..none of the phones sees the watch.
If I push the crown I get the settings page with only the following options:
Adjust Brightness
Bluetooth Devices - which shows: Bluetooth is currently disabled)
Always on Screen
Power off
Restart
Reset device
About
no place to check the airplane mode...nothing.. It's like there should be a "switch" to start the bluetooth somewhere..
any ideas greatly appreciated. For the moment I have a nice black thing on my watch which isn't doing anything..
[email protected] screen
If don't works with any phone maybe it is time to RMA ?
dersie said:
If don't works with any phone maybe it is time to RMA ?
Click to expand...
Click to collapse
RMA? What does that stand for?
[email protected]
depeche101 said:
RMA? What does that stand for?
[email protected]
Click to expand...
Click to collapse
I have exactly the same problem. If you frequently press device. Bluetooth is activated for 3-5 minutes. Watch are charged watchfase. That's all. Off. :crying:
RMA Return Merchandise Authorization
Not variant. Ebay shop.
Same Problem
I am having the same problem. Right now my LG G Watch R is useless. I wonder if it was on airplane mode before I factory restore it and that is what is causing the problem.
taastar said:
I have exactly the same problem. If you frequently press device. Bluetooth is activated for 3-5 minutes. Watch are charged watchfase. That's all. Off. :crying:
RMA Return Merchandise Authorization
Not variant. Ebay shop.
Click to expand...
Click to collapse
my case exctly... nice black piece...
The problem of overheating.
Harvesting hours in the refrigerator for 10 minutes.
Gat. Bluetooth works. Has not yet warmed up.
Then off again.
taastar said:
The problem of overheating.
Harvesting hours in the refrigerator for 10 minutes.
Gat. Bluetooth works. Has not yet warmed up.
Then off again.
Click to expand...
Click to collapse
BUMP
Anyone? No ideas whatsoever?
I did try the fridge thing...Worked once so I could pair the phone but didn't even sync.
Tried again with no success.
dep
Well I have an update. I honestly don't know what has changed...but my watch works again. Having the occasional connection lost problem as reported by many in the new 5.0 update in the watch but nothing too serious.
Anyway, reset your watch. Forget the watch in the Android wear app (or delete data and clear cache), but also delete the paired watch from the phones bluetooth menu.( BTW: I deleted all my paired devices in the phones bluetooth menu and then paired the watch first, don't know if this affected or not, if all else fails you can try this also).
Then turn off bluetooth from your phone. Start Android wear app and let it turn on bluetooth. THis way I can pair my phone. Whenever the watch loses connection to the phone and doesn't reconnect toggle bluetooth off and on from the phone and it works again.
Perhaps it's because the watch is already on Lollipop and the phone not yet...
dep
depeche101 said:
Perhaps it's because the watch is already on Lollipop and the phone not yet...
dep
Click to expand...
Click to collapse
I haven't had any issues and my T-Mo G3 is still on Kit-Kat.
Best practice if pairing gets wonky or whatever, is exactly what you did. Clear / Forget all pairings. Turns everything off. Turn phone on, enable BT, run Android Wear, turn on Watch - wait - follow regular steps and everything should be golden.
If it's still not working, try a reset on the Watch - if it's still won't work, RMA or take it back to the place you bought it from.
depeche101 said:
.
Perhaps it's because the watch is already on Lollipop and the phone not yet...
dep
Click to expand...
Click to collapse
I'm on lollipop on both watch and phone and getting constant disconnections
I will say that my rom is a leaked version of lollipop from Samsung on my note 3
But to date since Xmas it's been a joke
To the point that it might be going back if it doesn't get fixed in the next few days
I am going to go back to official kit kat later and see if that helps
I must say before the lollipop update on both watch and phone it worked brilliant not one disconnection when I trialled the watch when it was first delivered.
If it had been like it is now I would have sent it back there and then
I'm just hanging on because I know it did work prior to the updates
So I'm sure it will again
So I've had my R for a couple of months now, and it's been working fine, until after it was updated to 5.0.2. It stopped connecting to my Nexus 6, so I reset it. After that, the Android Wear app would never find it. I've wiped my phone, tried two other phones (Nexus 5 with Lollipop, Nexus 4 with KitKat) and nothing sees it. I haven't unlocked the bootloader or anything. It just sits at the "Install Android Wear on your phone" screen. Any ideas?
smgoller said:
So I've had my R for a couple of months now, and it's been working fine, until after it was updated to 5.0.2. It stopped connecting to my Nexus 6, so I reset it. After that, the Android Wear app would never find it. I've wiped my phone, tried two other phones (Nexus 5 with Lollipop, Nexus 4 with KitKat) and nothing sees it. I haven't unlocked the bootloader or anything. It just sits at the "Install Android Wear on your phone" screen. Any ideas?
Click to expand...
Click to collapse
I'm having the same issue as you right now.. in the past when my watch is still rooted... I just need to clear the dalvik cache in recovery and it be fine... but now i restored to stock so I can't perform this.
any help?
I am having the exact same issue. And lately google play services and contacts and other things began randomly crashing ALOT on my verizon note 4. Nothing rooted all stock on phone and watch. Did our bluetooth radios die or is this a widespread problem with an update noone has documented yet? I need my watch lol. Any one else?
RngrYogi said:
I am having the exact same issue. And lately google play services and contacts and other things began randomly crashing ALOT on my verizon note 4. Nothing rooted all stock on phone and watch. Did our bluetooth radios die or is this a widespread problem with an update noone has documented yet? I need my watch lol. Any one else?
Click to expand...
Click to collapse
smgoller said:
So I've had my R for a couple of months now, and it's been working fine, until after it was updated to 5.0.2. It stopped connecting to my Nexus 6, so I reset it. After that, the Android Wear app would never find it. I've wiped my phone, tried two other phones (Nexus 5 with Lollipop, Nexus 4 with KitKat) and nothing sees it. I haven't unlocked the bootloader or anything. It just sits at the "Install Android Wear on your phone" screen. Any ideas?
Click to expand...
Click to collapse
d3bugu said:
I'm having the same issue as you right now.. in the past when my watch is still rooted... I just need to clear the dalvik cache in recovery and it be fine... but now i restored to stock so I can't perform this.
any help?
Click to expand...
Click to collapse
Did anyone figure out a solution to this? Is it the watch or the phone (i'm using an s6 edge)?
All i get is "install android wear on your phone" on my moto 360, and on the android wear app it doesn't find my watch. I literally cannot do anything on my watch but stare at the "install android wear on your phone" message. I only tried to reset my watch because it was connecting and disconnecting rapidly every 5-10 seconds for hours and was my last resort.
Anyone please help?!
d3bugu said:
I'm having the same issue as you right now.. in the past when my watch is still rooted... I just need to clear the dalvik cache in recovery and it be fine... but now i restored to stock so I can't perform this.
any help?
Click to expand...
Click to collapse
I am having same problem as op, why would you not root again and wipe dalvik if that was working before, i have been trying to root so i can do this but i cant got stuck on twrp and would not boot to start up so i flashed everything back to normal and bluetooth will not show at all on any device...
I believe it has to do with the latest version of android wear. Ever since the last update a lot of people have been reporting the same and similar problems in the play store. A fix for me even though it is inconvenient is resitting the watch and re installing android wear. Every since the update I have to do that every couple of days.
Ginxeng said:
I believe it has to do with the latest version of android wear. Ever since the last update a lot of people have been reporting the same and similar problems in the play store. A fix for me even though it is inconvenient is resitting the watch and re installing android wear. Every since the update I have to do that every couple of days.
Click to expand...
Click to collapse
Can you provide steps on how u do that because I have followed all steps on this form can still don't work. Ever since I tried to root it with windroid I got stuck on installing super user and wouldn't install then it was stuck on just booting to twrp I have with windroud and adb the stock image files and it goes back to normal but ever since the watch won't show up at all on any device tried multiple any help would be appreciated
Sent from my SM-G925T using XDA Free mobile app
what I do is first I unpair the watch from the phones bluetooth settings, then I uninstall android wear from the phone. Then I take the watch and I go under settings and reset the watch, once the watch is finished resetting I re-install android wear on the phone and re-pair.
Ginxeng said:
what I do is first I unpair the watch from the phones bluetooth settings, then I uninstall android wear from the phone. Then I take the watch and I go under settings and reset the watch, once the watch is finished resetting I re-install android wear on the phone and re-pair.
Click to expand...
Click to collapse
Thanks but what about the root and all I have problem
Sent from my SM-G925T using XDA Free mobile app
ANSWER: after resetting your watch, you must unpair the watch from your phone, then go to settings/apps/android wear "clear data" . then start the whole pairing process again.
---------- Post added at 02:27 AM ---------- Previous post was at 02:27 AM ----------
Ginxeng said:
what I do is first I unpair the watch from the phones bluetooth settings, then I uninstall android wear from the phone. Then I take the watch and I go under settings and reset the watch, once the watch is finished resetting I re-install android wear on the phone and re-pair.
Click to expand...
Click to collapse
THIS^^^
i answered after scanning the thread too quickly
I've done every steps above: Factory reset my GWR, then on my phone I clear data in setting - apps - android wear then pair again. My GWR connect successfully but after sync app it disconnect, then my phone can not find the watch anymore.
I've done all these steps 5-6 times and the result still the same!
I dont know whats wrong with my GWR?
I have same problem
Especially when the "install android wear on your phone" text appear on watch, below it is G watch R but is there 4 digit " name" of the watch did not showed, and adroid wear not see the watch to pair.
The watch is on 5.0.2
Pls help me.
Tong Ngoc said:
Especially when the "install android wear on your phone" text appear on watch, below it is G watch R but is there 4 digit " name" of the watch did not showed, and adroid wear not see the watch to pair.
The watch is on 5.0.2
Pls help me.
Click to expand...
Click to collapse
This is what happened to mine. I tried all the things mentioned in this thread, but finally the only thing that worked was a hard factory reset (swipe from top left to bottom right over the LG logo when booting) and then leaving the watch on charger for like 3 hours and finally my phone could see and connect to it. I've heard this worked for others too.
Jevenji said:
This is what happened to mine. I tried all the things mentioned in this thread, but finally the only thing that worked was a hard factory reset (swipe from top left to bottom right over the LG logo when booting) and then leaving the watch on charger for like 3 hours and finally my phone could see and connect to it. I've heard this worked for others too.
Click to expand...
Click to collapse
Does anybody actuallly knows a method to fix this? im having the exact same issue on my g watch R, there is no code with the name and my G4 cant find it. i tried everything mention here, even the factory reset on recovery and then charger for more than 3 hours... but nothing everytime i try its the same thing, no code no pair. thanks
morrisx10 said:
Does anybody actuallly knows a method to fix this? im having the exact same issue on my g watch R, there is no code with the name and my G4 cant find it. i tried everything mention here, even the factory reset on recovery and then charger for more than 3 hours... but nothing everytime i try its the same thing, no code no pair. thanks
Click to expand...
Click to collapse
for me also
i dont know what to do i try everything but cant connect
i thinking about to reflash the stock rom but i dont know how to do it
Sent from my LG-D802 using XDA Free mobile app
update
i install the urban rom from xda
and after long night with bootloop in the cradle which is normal in this rom . you need to put your watch after the rom is load but i forget. the watch working again
thanks Leedroid for your work
Sent from my LG-D802 using XDA Free mobile app
Fixed
tried everything ... only the urban ROM can fix the problem (maybe is only the kernel what is need to update)
after 2 days it was ok now i have the problem again. the watch cant connect
Sent from my LG-D802 using XDA Free mobile app
yogibogi said:
after 2 days it was ok now i have the problem again. the watch cant connect
Sent from my LG-D802 using XDA Free mobile app
Click to expand...
Click to collapse
what version was it on b4 i was having the same problem on 5.0.2 but after manual update to 5.1.1 everything works good.
im on 5.1.1 .
i think my bluetooth is broken
useless watch
So my watch updated last night, and now I am trying to figure out all the changes.
I see that we have new gestures. I don't really use them, so Meh.
I also see that my battery projection jumped from 50 hours to 3 days, so that I freaking awesome if it pans out.
Anyone see anything else?
-Chris
cdaly1970 said:
So my watch updated last night, and now I am trying to figure out all the changes.
I see that we have new gestures. I don't really use them, so Meh.
I also see that my battery projection jumped from 50 hours to 3 days, so that I freaking awesome if it pans out.
Anyone see anything else?
-Chris
Click to expand...
Click to collapse
No more reboot watch.. Have to turn it off and on again.
matejilic said:
No more reboot watch.. Have to turn it off and on again.
Click to expand...
Click to collapse
Yeah I noticed that. Find this odd as to why they removed that
Hawke84 said:
Yeah I noticed that. Find this odd as to why they removed that
Click to expand...
Click to collapse
I think Google's reason was: "Why? Because F**k you, thats why!" It also baffles me that they still haven't incorporated custom canned responses to declined phone calls; you are stuck with the default ones even though you set up custom ones on the phone - the reason was probaby the same as the reboot omisson.
matejilic said:
I think Google's reason was: "Why? Because F**k you, thats why!" It also baffles me that they still haven't incorporated custom canned responses to declined phone calls; you are stuck with the default ones even though you set up custom ones on the phone - the reason was probaby the same as the reboot omisson.
Click to expand...
Click to collapse
but how to make a factory reset now? there is no item in menu.
Hawke84 said:
Yeah I noticed that. Find this odd as to why they removed that
Click to expand...
Click to collapse
Just hold down the button until it buzzes and reboots. Hardware reboot.
shobull.eu said:
but how to make a factory reset now? there is no item in menu.
Click to expand...
Click to collapse
Have you tried 'Unpair with phone'? To me that sounds like it would do a factory reset since an unpaired watch is basically useless.
Big change
Hi all,
Also got marshmallow, and biggest change for me is that it won't pair with phone. It comes up alright, and after accepting the Bluetooth code the phone wear app says "couldn't connect with ...". I tried factory resets (via unpair phone setting item), fresh install of wear phone app, and what not - still no luck.
Will try to downgrade and see if that helps.
Yours,
Christian
Hawkeye3 said:
Have you tried 'Unpair with phone'? To me that sounds like it would do a factory reset since an unpaired watch is basically useless.
Click to expand...
Click to collapse
From what I understand factory reset is "Unpair with phone" now, as when you select it asks: "are you sure you want to unpair and factory reset watch.
Interesting thing, is the new Reminders app, doesn't seem to work it asks to update android wear on phone when I open it, but nothing happens.
cholm said:
Hi all,
Also got marshmallow, and biggest change for me is that it won't pair with phone. It comes up alright, and after accepting the Bluetooth code the phone wear app says "couldn't connect with ...". I tried factory resets (via unpair phone setting item), fresh install of wear phone app, and what not - still no luck.
Will try to downgrade and see if that helps.
Yours,
Christian
Click to expand...
Click to collapse
I replied to you in the other thread but will post here as it may be useful to others..
I have the same issue. After OTA , i factory resetted and now it will not pair. I get "failed to pair...." I have tried multiple resets and cleared the data on the android wear app but no joy. I have gone back to 5.1.1 using the first post of the factory image thread. I was able to flash boot.img and system.img but recovery.img failed due to a partition error. Now everything is working again. Paired and synced on first attempt.
Downngrade wakes up watch
Hi there,
mhacin said:
I replied to you in the other thread but will post here as it may be useful to others..
...
I have gone back to 5.1.1 using the first post of the factory image thread. I was able to flash boot.img and system.img but recovery.img failed due to a partition error. Now everything is working again. Paired and synced on first attempt.
Click to expand...
Click to collapse
I also went back to 5.1.1 and things now work again - recovery flash also worked.
Seems the problem is really on the phone end. I have a Nexus 4 with "Fake stock" ROM (marshmellow). I could get the watch to pair with my Nexus 7 running stock 6.0..1 and that paired just fine. I also see other problems with the same Nexus 4 ROM with other bluetooth devices - e.g., my Jabra Tag II bluetooth audio RX/TX. I've posted on the ROM bug report forum.
My watch gives an error about a muted microfone although the mike is enabled everywhere in the settings where possible.
" Microfone disabled, waiting for injected audio."
Any suggestions?
Edit: Also the screen goes off after some time although I haven't enabled it anywhere?
Maybe I'll just reset it...
The biggest change for me - now we have native vibration when the watch disconnects (on connects) ... it was about f'in time ...
cholm said:
I have a Nexus 4 with "Fake stock" ROM (marshmellow).
Click to expand...
Click to collapse
I also have nexus 4 running Chroma MM. I will wait for OTA again and this time I wont factory reset to see how it goes
Manually updated mine to 6.0.1 using adb and now my iPhone (9.3 beta3 and latest android wear app) constantly looses connection. Have to pair as new device, restarting phone and/ or watch won't help.
Does anybody experience the same?
Might have to go back to 5.1.1 ...
Gesendet von iPhone mit Tapatalk
Hmm, well thats a disappointing. The removal of the reboot and reset is moronic and the new gestures are useless.
For the most part I cant get them to work, and even if I could why would I want to look like I was a nutter because I was randomly flapping my arm around trying (usually unsuccessfully) to control my damn watch?
delete me
mhacin said:
I replied to you in the other thread but will post here as it may be useful to others..
I have the same issue. After OTA , i factory resetted and now it will not pair. I get "failed to pair...." I have tried multiple resets and cleared the data on the android wear app but no joy. I have gone back to 5.1.1 using the first post of the factory image thread. I was able to flash boot.img and system.img but recovery.img failed due to a partition error. Now everything is working again. Paired and synced on first attempt.
Click to expand...
Click to collapse
Which 5.1.1 is better?
SharpSA said:
Which 5.1.1 is better?
Click to expand...
Click to collapse
I used the one at the top of the list. I don't know what the differences are between 5.1.1 versions
Suddenly the WiFi on my daughter's s8 won't turn on. I go to turn it on, wheel spins for a few seconds and then turns back off. Just started yesterday was working fine prior.
I've reset all network connections
Factory reset phone
Nothing seems to let me re-enable WiFi at all doesn't make a lick of sense. Anyone have any suggestions to try before I have to go buy a new replacement ugh.
Phone is TMobile s8 on the latest software G950U with Android 9 April Patch
When you did the factory reset, did you also reinstall any apps or settings? If so, reset again, but don't restore anything. If you still can't turn on WiFi, I'd say the radio has failed. Time to give her yours and get an S10. [emoji1]
rcobourn said:
When you did the factory reset, did you also reinstall any apps or settings? If so, reset again, but don't restore anything. If you still can't turn on WiFi, I'd say the radio has failed. Time to give her yours and get an S10. [emoji1]
Click to expand...
Click to collapse
Guessing radio is failed, because before it even hits restore point when first boot after factory reset and it asks if you want to configure WiFi it exhibits the same behavior Ugh this sucks
IrishTR said:
Guessing radio is failed, because before it even hits restore point when first boot after factory reset and it asks if you want to configure WiFi it exhibits the same behavior Ugh this sucks
Click to expand...
Click to collapse
No reason not to take it to a T-Mobile shop and see if they can do anything with it. I just wouldn't get my hopes up.