Related
I had a strange reset of my phone last night, through what I think was no real action on my part, but I wanted to defer to the experts and see if anyone can help me make sense of this...
Also, as you'll see at the end of my post—if you make it through my rambling—I could find some of the info I seek elsewhere on this, and other forums, but the combination of data would be a difficult scavenger hunt and I thought this thread may help other lite (or lazy) power users with similar issues or info searches in the future...
So I was changing my battery out last night and when I was pulling the dead one out I had accidentally turned the phone on, but was talking to someone at the time and, being distracted, continued pulling the battery.
I got the new one in and turned the phone on to be greeted by what I think is called, and excuse my ignorance on terms as I have had no real interest in rooting to date, the debug screen—white background, cute little android rascals on the bottom, several restart options, etc. I believe I selected 'fast boot', as I think I have done when some random serious of events have greeted me with the 'debug' screen in the past.
All seemed fine and the device started up but it lagged on a black screen with an icon I interpreted as an 'update' icon and a progress bar. When I got to the OS, my settings, screens, apps, etc were reverted to stock conditions. My SD card retained all its contents and I used AppBrain so I was able to get things back to some semblance of normalcy rather quickly, but I am left with so many questions...
I've come up with 3 possible explanations...I made an error on the 'debug' screen, my device had a huge and random hiccup, or there was some strange update last night that, despite my best efforts, I cannot find mention of here or on any other forums.
Some additional info...
-on App Brain site, after linking the reset device back up to my E-mail/account, I have a totally new list named, not by the former 'ADR6300', but by 'HTC Droid Incredible'. This leads me to believe either AppBrain has changed its naming convention for this device since I originally set the app/account up, or there was some strange mystery update.
-I have always updated when prompted so I believe I was running the newest OS and am still on 2.2 now.
I'm not really looking for a solution to the reset, more looking for answers/theories and some preventative measures for reducing possible distress should something similar occur in the future.
-back-up methods...I use Launcher Pro Plus - paid, and just realized I can back-up home screens and settings through the launcher but is there anything else I should be doing?
-break down on that 'debug' screen, best option to choose for various issues, etc.
-has anyone heard of a similar story, update last night, or know the reason for AppBrain's new naming convention for my device?
Any other info, tips, or relevant advice would be much appreciated. As a Web/graphic designer and modern woman I am inquisitive and technical by nature but tend to subscribe to the 'if it aint broke, don't fix it' school of thought unless there is some new feature I hear about or want when it comes to my device. So I am not dense but I definitely don't know everything and I am looking to you, the 'experts' for answers
You held vol - and the pwr button when you turned on the phone. That is what made you go to the bootloader (debug). From there i'm guessing you had the phone do a factory reset, that is why everything went back to how it was when you first bought the phone.
2.2 is the "newest" build available without rooting your device.
Rooting and making a backup through Recovery is the best way (imo) to create a backup.
For what it's worth, I think g00s3y is spot-on
When you get to the hboot screen (the white screen with the Android dudes at the bottom), there should be 5 options:
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
FACTORY RESET
Seems most likely that you mistakenly hit the last one rather than the first.
Ive sort of tried to search this one (How do I search JUST the Epic 4g section of XDA??) and found no one describing this problem the way I do...
This is my second time having this issue, and the fix for it last time was a pain in the ass, so id like a new fix-
Every app, every aspect of my phone, continuously resets/reloads. This is most noticeable with Hancent SMS, as it saves a message as a draft when you close out of the app... Well, right now, ill be typing and "message saved as draft" will constantly pop up at the bottom of the screen (about once every 2 seconds), and the phone will lag and it will erase 1 or two characters(making me look like I cant type :silly: ).
If this was the only problem, maybe I could live with it, but it affects everything. Launcher Pro randomly/continuously resets. The notification bar often resets while trying to pull it down. The phone app will close or freeze as soon as I start receiving a call. Sometimes it'll play my ringtone without a way for me to answer, other times I never knew I missed a call unless they leave a voice mail... And sometimes its worse than others, sometimes its fine for an hour, then something goes stupid and even a reboot doesn't help. For instance, right now, it was happy. I launched aLogcat to check it out and now the screen orientation REFUSES to stay one way. Even setting the phone down, it switches directions every few seconds, which makes aLogcat reload and therefor its unusable.
I haven't mentioned what im running because Ive had this exact same issue on a totally different rom, almost a year ago, but im running-
build - SleeperROM_3.0.0_FC09
kernal - 2.6.35.7-Shadow-FC09_v1.0
baseband - S700.0.5s.FC09
firmware - 2.3.6
Ive had this happen on EB13 on the EpicExperience ROM too.
SOO, if anyone has advice on how to fix this, id be extremely interested.
On the other hand, last time I had this issue I was convinced it was a corrupt piece of memory somewhere early in the OS, something I corrupt during install, and I went ahead and reflashed and wiped and reflashed and wiped and returned to stock and etc. etc. etc... and that seemed to work... actually, I dont know exactly what part of the process fixed it, thats why I do not want to repeat it unless I have to... BUT, if someone would like to explain/point me in the right direction. I'd like to know how to DELETE AS MUCH AS POSSIBLE and FLASH as CLEAN as possible. (that is, if no one else knows of a fix for my problem)
thanks all!
Err, well only thing I can think of is a truly clean install using Odin. This means do not restore any data from backups. Then slowly begin installing applications 1-by-1 through the play store website (for speed sake) to see if your issue creeps up again.
It also couldn't hurt to format your SD card too. Corrupt data on the SD card can cause some wonky things at times.
get another device...i hope u have the equipment protection plan
Thanks for the advice guys OFF TO THE ODIN MACHINE! haha.
So the other day the app Widgetsoid releases a "Completely rewritten" update for their sweet app. I was obviously excited to play with this and set about recreating all of my toggles. One toggle I have is to toggle the camera flash on/off which is very handy to have a widget for on the homescreen. Another one I use toggles the screen always on/off which is handy when reading long articles. So I was using the screen always on toggle as a reading light (as the camera LED can be overly bright) when, after some time, my phone locked up. Following my natural instinct I pulled the battery and powered it back on. When it came back on I noticed that the screen always on toggle was still in the "on" position though I believe (honestly can't remember for sure) that the screen was timing out as if it were off. Anyways I put this out of my mind and decided to use the flashlight toggle as the screen hadn't been quite as bright as I wanted. However, upon toggling the flashlight to "on" The toggle froze in mid activation. I could see that I had clicked it but the animation never finished and the flashlight never turned on. I gave it several minutes to sort itself out and when it didn't I did another battery pull thinking that would clear it up. Well it didn't. Upon the phone restarting I was greeted by "Tango has stopped responding". Then when I tried the flashlight toggle again I got "Gallery has stopped responding" which flashed up and disappeared too quickly for me to click on it. I tried opening the camera to no avail. "Gallery has stopped responding". So one bug led to another to another to another as bugs so often do. No biggie, I was planning on doing a factory reset soon anyways so I backed up my data and went ahead with that. Unfortunately, when I finished the setup and went back to the camera app it gave me the same error. (please note that I did not restore anything after the reset.) So I did another just for sanity's sake but no change. I went into the bootloader and into recovery, cleared the cache and then did another factory reset. Nada. I downloaded a flashlight app to see if it could tell me anything new, which it sort of did. "Cannot connect to camera", it said when I turned it on. In my search on this forum for a similar issue I came across a post to a different issue talking about how when an app uses the camera it might not have let go when it was finished which causes problems for other apps. This makes enough sense except that I figured the reset would have resolved that issue. Unless, of course, the problem lies in the hardware which I am desperately hoping someone will tell me is foolish.
I'm not really sure what to try next in my troubleshooting short of unlocking the bootloader and flashing either the stock back over it or another ROM. I would prefer to try other possible solutions before this. Correct me if I'm wrong but shouldn't the factory reset restore the system and stock apps to their default state? Almost literally bit for bit? If that is the case then that means the issue isn't with the system or the camera app and must fall to the camera hardware itself? I feel it is worth noting that on about the third factory reset, during the initial setup (quite literally on the first screen) a popup popped saying "Talk has stopped responding". Why the Talk app would stop responding due to some issue with the camera seems out of place. Though as I said and we all know, bugs have a way of spreading to the places you least expect.
Anyways any help, suggestions or questions would be greatly appreciated. This really has me stumped.
I guess the question it boils down to (besides the three I've already asked) is how can I do a full wipe/reset that will actually reset everything? Or is it that the camera is really hung and if so any possible fixes for that? Anyone see any bright red flags waving violently in the storm?
Thanks in advance for any help you can provide
patrioticparadox
I am running 4.1.1 on a Verizon Galaxy Nexus build JRO03O
patrioticparadox said:
So the other day the app Widgetsoid releases a "Completely rewritten" update for their sweet app. I was obviously excited to play with this and set about recreating all of my toggles. One toggle I have is to toggle the camera flash on/off which is very handy to have a widget for on the homescreen. Another one I use toggles the screen always on/off which is handy when reading long articles. So I was using the screen always on toggle as a reading light (as the camera LED can be overly bright) when, after some time, my phone locked up. Following my natural instinct I pulled the battery and powered it back on. When it came back on I noticed that the screen always on toggle was still in the "on" position though I believe (honestly can't remember for sure) that the screen was timing out as if it were off. Anyways I put this out of my mind and decided to use the flashlight toggle as the screen hadn't been quite as bright as I wanted. However, upon toggling the flashlight to "on" The toggle froze in mid activation. I could see that I had clicked it but the animation never finished and the flashlight never turned on. I gave it several minutes to sort itself out and when it didn't I did another battery pull thinking that would clear it up. Well it didn't. Upon the phone restarting I was greeted by "Tango has stopped responding". Then when I tried the flashlight toggle again I got "Gallery has stopped responding" which flashed up and disappeared too quickly for me to click on it. I tried opening the camera to no avail. "Gallery has stopped responding". So one bug led to another to another to another as bugs so often do. No biggie, I was planning on doing a factory reset soon anyways so I backed up my data and went ahead with that. Unfortunately, when I finished the setup and went back to the camera app it gave me the same error. (please note that I did not restore anything after the reset.) So I did another just for sanity's sake but no change. I went into the bootloader and into recovery, cleared the cache and then did another factory reset. Nada. I downloaded a flashlight app to see if it could tell me anything new, which it sort of did. "Cannot connect to camera", it said when I turned it on. In my search on this forum for a similar issue I came across a post to a different issue talking about how when an app uses the camera it might not have let go when it was finished which causes problems for other apps. This makes enough sense except that I figured the reset would have resolved that issue. Unless, of course, the problem lies in the hardware which I am desperately hoping someone will tell me is foolish.
I'm not really sure what to try next in my troubleshooting short of unlocking the bootloader and flashing either the stock back over it or another ROM. I would prefer to try other possible solutions before this. Correct me if I'm wrong but shouldn't the factory reset restore the system and stock apps to their default state? Almost literally bit for bit? If that is the case then that means the issue isn't with the system or the camera app and must fall to the camera hardware itself? I feel it is worth noting that on about the third factory reset, during the initial setup (quite literally on the first screen) a popup popped saying "Talk has stopped responding". Why the Talk app would stop responding due to some issue with the camera seems out of place. Though as I said and we all know, bugs have a way of spreading to the places you least expect.
Anyways any help, suggestions or questions would be greatly appreciated. This really has me stumped.
I guess the question it boils down to (besides the three I've already asked) is how can I do a full wipe/reset that will actually reset everything? Or is it that the camera is really hung and if so any possible fixes for that? Anyone see any bright red flags waving violently in the storm?
Thanks in advance for any help you can provide
patrioticparadox
I am running 4.1.1 on a Verizon Galaxy Nexus build JRO03O
Click to expand...
Click to collapse
I would honestly try to flash another ROM. its hard to tell what is exactly causing this prob but I highly highly highly doubt its hardware. Make sure you wipe data and dalvik a couple times and go to mounts and storage and wipe system too. Do those a couple times, I always do just to be sure it works. Then after that try to flash another ROM stock or custom doesnt matter. This will help a lot.
Just a recommendation, I use and LOVE Codename Android Rom. Very very fast and stable with a lot of features.
Anyways, post back when you wipe everything out and flash a new ROM on there and let me know the outcome.
nothing yet...
myboyblake said:
I would honestly try to flash another ROM. its hard to tell what is exactly causing this prob but I highly highly highly doubt its hardware.
Click to expand...
Click to collapse
Just finished flashing the 4.1.1 back and still the same issue (did all of the data wiping). I'll try a custom ROM now though I doubt its going to make any difference.
What in the world has got a hold of my camera?
No dice
"Unfortunately Talk has stopped responding" on the first screen. "Gallery has stopped responding" when trying to open Camera app.
So despite several wipes and two distinct ROM flashes (used PARANOIDANDROID the second time) my device is still acting up.
Please help me out people. What is causing this error that is lasting across ROM flashes? What can I try to resolve this issue?
Rewiped everything and reflashed PARANOIDANDROID (2.23) just to be sure and still the camera doesn't work
seems like perhaps the registers ended up in an odd state.. know this is for a different phone, but you might give it a shot..
http://www.droidforums.net/forum/dr...amera-app-stoped-working-wont-initialize.html
---------- Post added at 05:03 PM ---------- Previous post was at 04:46 PM ----------
Looks like OMAPFlash can do a full reset on all the camera registers from looking at:
./Targets/Definitions/definitions_omap4.txt
in the OMAPFlash zipfile..
It might be worth a shot..
Slide opultl
No dice... I assume you were referring to clearing the cache and data. I had tried this before but gave it another shot anyways. In case you meant the screenshot part, I did that too and the screenshot captures fine but still the camera does not function. Also holding down the volume down and power keys never shuts the phone off I assume that is device specific (though several seconds after the screenshot captured the screen did flash off then on very quickly). I have tried disabling Gallery and rebooting in the hopes that would free up the hardware. Failed.
I am uber stuck on this.
Why is this persisting across flashes and what can I try to resolve it?
edit: just noticed that the bottom of your post was more info and not a signature. I'll look into that. Ran out of "thanks" for today but I'll get you yours
Since it won't delete....
As an update: I have tried contacting both Verizon and Samsung about the issue. Both recommend returning the device under warranty (as was expected). This would be fine except that I LEARN NOTHING! If the Samsung techies have a protocol/enumeration/anything to discover and resolve the issue then so can I (potentially), which means the general public should have this knowledge too, right? WHAT IS MY NEXT STEP?
(still have not yet OMAP_Flash'ed as I haven't found SOLID documentation on this yet.) (Google searching led me somewhere but left me confused. Please post documentation or the correct link if you have it and thank you) I am open to trying anything. Understand that my bottom line is giving Asurion $50 USD. "I LOST my phone, send me a [new] one". Phone gets replaced and I get to trash the old one. Sweet for everyone right? Wrong.
I don't give two runny, stinky butt creams about the phone itself. Which is not entirely, or honestly, even close to true. I'd hate to see a Nexus that can be saved be completely obliterated. If its totally bricked (which its very hard to do to a Nexus) then go for it. Smash that ***** up! But if, like mine, its recoverable then you owe it to the developer to try to save it. This Galaxy Nexus SCH-I515 reminds me of my SCH-a950. I loved that phone and literally (because of a now EX girlfriend) BEAT THE LIVING SNOT OUT OF IT. I literally threw it at my front porch as hard as I could from a good 30 yards away and yet it survived. Not only did it survive, it thrived. Never failing me (even until I finally upgraded) despite the "wear and F'ing tear" I had inflicted upon it.
I have actually dropped my Nexus several times. I have a massively cracked screen that I would love to show you all, yet the screen still functions as if there were no crack. I can click on the "options" toggle that is in the bottom right corner of many apps as if there were not a MASSIVE chunk of screen missing there. The phone is quite amazing. And before anyone says "oh you dropped it, that could have to do with the errors in the camera", NO. The camera worked just fine until what I described above. Samsung has done quite a magnificent job with this device (and all of their hardware, {I own a 26" computer monitor that kicks ass too}) making it resilient to adversity.
Now please, help me out....
I am hesitant to try the OMAP_flash as I haven't found decent documentation. PLEASE PLEASE post a link.
As I said I can always "lose" the phone and get a new one through insurance. So I'm not worried about screwing the phone, I just want to LEARN about the issue at hand.
What do YOU think is causing this issue?
If someone could post a link to the relevant info about the OMAP_flash then I will be happy to go forward with it.
Aside from all this I am shocked at the relative dismissal of this thread. I am seeking information from experienced members who have expertise on this device and while many are available I have gotten no replies as of yet. (this is not to discount those who have replied as I am very grateful for those suggestions as well) Please take two minutes and give me your thoughts. I don't believe this issue is similar to any other posts here and if you do believe it, kindly point me in that direction.
http://forum.gsmhosting.com/vbb/f63...-i9100g-via-usb-cable-freeeeeeeeeeee-1465412/
Here's a link, sorry I didn't post soon - I don't check back here often..
patrioticparadox said:
(still have not yet OMAP_Flash'ed as I haven't found SOLID documentation on this yet.) (Google searching led me somewhere but left me confused. Please post documentation or the correct link if you have it and thank you) I am open to trying anything. Understand that my bottom line is giving Asurion $50 USD. "I LOST my phone, send me a [new] one". Phone gets replaced and I get to trash the old one. Sweet for everyone right? Wrong.
I don't give two runny, stinky butt creams about the phone itself. Which is not entirely, or honestly, even close to true. I'd hate to see a Nexus that can be saved be completely obliterated. If its totally bricked (which its very hard to do to a Nexus) then go for it. Smash that ***** up! But if, like mine, its recoverable then you owe it to the developer to try to save it. This Galaxy Nexus SCH-I515 reminds me of my SCH-a950. I loved that phone and literally (because of a now EX girlfriend) BEAT THE LIVING SNOT OUT OF IT. I literally threw it at my front porch as hard as I could from a good 30 yards away and yet it survived. Not only did it survive, it thrived. Never failing me (even until I finally upgraded) despite the "wear and F'ing tear" I had inflicted upon it.
I have actually dropped my Nexus several times. I have a massively cracked screen that I would love to show you all, yet the screen still functions as if there were no crack. I can click on the "options" toggle that is in the bottom right corner of many apps as if there were not a MASSIVE chunk of screen missing there. The phone is quite amazing. And before anyone says "oh you dropped it, that could have to do with the errors in the camera", NO. The camera worked just fine until what I described above. Samsung has done quite a magnificent job with this device (and all of their hardware, {I own a 26" computer monitor that kicks ass too}) making it resilient to adversity.
Now please, help me out....
I am hesitant to try the OMAP_flash as I haven't found decent documentation. PLEASE PLEASE post a link.
As I said I can always "lose" the phone and get a new one through insurance. So I'm not worried about screwing the phone, I just want to LEARN about the issue at hand.
What do YOU think is causing this issue?
If someone could post a link to the relevant info about the OMAP_flash then I will be happy to go forward with it.
Aside from all this I am shocked at the relative dismissal of this thread. I am seeking information from experienced members who have expertise on this device and while many are available I have gotten no replies as of yet. (this is not to discount those who have replied as I am very grateful for those suggestions as well) Please take two minutes and give me your thoughts. I don't believe this issue is similar to any other posts here and if you do believe it, kindly point me in that direction.
Click to expand...
Click to collapse
Jesus, will people stop talking about insurance fraud........
It's these kind of people that people in your country have to suffer higher insurance premiums, and the very same group of fraudsters are complaining about high insurance premiums..
Regarding OMAP flash:
1) Remove battery
2) Open device manager
3) Plug your phone to your PC/laptop
4) Right click on OMAP4460, go to properties
5) Drivers tab
6) Update drivers, direct to the OMAP flash folder
7) Run the .bat
8) Reflash a ROM just in case.
I don't think it going to do a reg reset for the camera by default..
This is from: Targets/Definitions/definitions_omap4.txt
CONTROL_CORE_PAD_CAM_GLOBALRESET 0x4A1000C0
It is pulled in and used by:
Targets/Configurations/configuration_omap4460_tuna_8g.txt
CONTROL_CORE_PAD_CAM_GLOBALRESET needs to set for the correct location -- I have not done any digging, so I don't know what the location is..
Just Found this -- https://github.com/omapconf/omapconf/wiki
omapconf can be used to read/write/modify any register from within Android..
Mach3.2 said:
Jesus, will people stop talking about insurance fraud........
It's these kind of people that people in your country have to suffer higher insurance premiums, and the very same group of fraudsters are complaining about high insurance premiums..
Regarding OMAP flash:
1) Remove battery
2) Open device manager
3) Plug your phone to your PC/laptop
4) Right click on OMAP4460, go to properties
5) Drivers tab
6) Update drivers, direct to the OMAP flash folder
7) Run the .bat
8) Reflash a ROM just in case.
Click to expand...
Click to collapse
Insurance fraud? Um get a life! That's not why their premiums are high you ass! They do it to make more money you jack knob. My company charges $65/yr with a $25 deductible with up to 5 claims a year! That's so much better than asurion. And they give you a piece of **** replacement. Is all about money not the customer...now please me nice. Great ideas come from working together not from being an asshat!
*Originally I posted this in the Help section of the G3 forums but got no help, so I am posting this here*
Hey all,
So I'm posting this thread regarding a couple pretty weird glitches and bugs occurring on my G3, 3 specific ones.
The first: (Probably the least serious but still REALLY annoying) At EXACTLY 12:00AM every night no matter what timezone I set the phone to (I'm in AU on the AEST GMT+10 timezone but it does this at the same time on any timezone) the phone will switch it's WiFi off automatically without warning, reason or explanation. It just goes off and then I have to manually turn it back on. Sure I could use an app such as Tasker or AutomateIt to turn it back on but I don't see why this is occurring in the first place?
The second issue (Most recent): Lately after updating to the V20E firmware for my D855 I've noticed that a graphical glitch (Specifically related to the colour Blue) occurs when there are fast moving elements on my phone's screen (Such as when I move a chat head around on my phone from Messenger, or when I'm scrolling Facebook or my App Drawer fast, there's just a blue box around whatever object/s appear to be moving on my phone's screen. I've not dropped the phone at all, and it has only been present since updating from the V20D ROM. Not sure what could be causing it.
The third and by far the MOST ANNOYING of the issues I'm having, is that for no apparent reason, whenever I am listening to Music with the stock Music player, and I lock the screen (The screen goes off) about 5 seconds later weird stuff starts to happen..
The song will pause, play or even stop completely, seemingly on its own. The "phone" will change songs, artists and sometimes complete albums and playlists completely by itself, with me doing nothing but staring at the lock screen (It keeps doing it until I re-enter the Music app, then when I lock the phone the whole cycle just repeats itself.)
I've done some looking around and careful observations on the phone itself, and it seems that before the weird stuff starts happening to my music, the phone opens Voice Mate by itself, and then if I'm not present, it apparently closes it and then that's when the stuff happens. I've tried everything I can on a non-rooted phone to stop this. I've tried re-installing the Music app, Uninstalling all updates to the Voice Mate and it's packages to the factory version, force-stopping Voice Mate, everything and no matter what I do the phone still opens Voice Mate and the weird stuff starts happening (It's like it's taking commands from Voice Mate to do something but I'm not even doing anything ) It's been doing this since I got my phone when it came with Android KitKat 4.4 (I was on the D10M ROM until I moved to the D20D Android L ROM) and I moved ROMs doing a completely fresh start ( I factory wiped the phone and then upgraded via a CSE flash and put all my stuff back on it manually) and I would've thought a completely fresh start would have fixed it but apparently not... Either it's a bug that's been present for a while, or it's something deeper than the ROM.
So yeah some pretty weird issues, if someone knows what could be causing them, please let me know, especially if you know a way to solve them.
Cheers guys.
I'd do a factory reset for bugs 1 and 2. If that doesn't fix it, then do a clean flash from LG's Flash Tool. Regarding the first one, I think that it may be due to Quiet Mode on your phone? Or possibly even Battery Saver automagically kicking in at 12.
But yeah, backup your data and do a reset. It fixes around 80% of bugs after an update (As a rule of thumb I reset just before and right after an update to avoid any issues.
GuyInTheCorner said:
I'd do a factory reset for bugs 1 and 2. If that doesn't fix it, then do a clean flash from LG's Flash Tool. Regarding the first one, I think that it may be due to Quiet Mode on your phone? Or possibly even Battery Saver automagically kicking in at 12.
But yeah, backup your data and do a reset. It fixes around 80% of bugs after an update (As a rule of thumb I reset just before and right after an update to avoid any issues.
Click to expand...
Click to collapse
As I said before I've done a factory reset and complete re-flash via CSE, and nothing has fixed it it's been the same since I updated :/
iDefalt said:
As I said before I've done a factory reset and complete re-flash via CSE, and nothing has fixed it it's been the same since I updated :/
Click to expand...
Click to collapse
whoops, sorry didn't read the full post (newb mistake, had a teacher looking over my shoulder). Contact LG support?
Sounds like your phone is superstitious
Sent from my LG-D855 using XDA Free mobile app
GuyInTheCorner said:
whoops, sorry didn't read the full post (newb mistake, had a teacher looking over my shoulder). Contact LG support?
Click to expand...
Click to collapse
Yeah I thought that but I wanted to know if anyone here has had the same issues.
iDefalt said:
Yeah I thought that but I wanted to know if anyone here has had the same issues.
Click to expand...
Click to collapse
the WiFi issue seems like its something to do with battery saver/quiet mode (to me anyway). Unless your router is kicking the phone off at that time?
EDIT:
oh and regarding the Voice Mate issue it could be either the jack or your headphones?
Please do not double post. It is a violation of Forum Rules.
5. Create a thread or post a message only once.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer
Click to expand...
Click to collapse
This thread is closed. Your original will remain open here: http://forum.xda-developers.com/lg-g3/help/couple-weird-glitches-occuring-help-t2974077
Can you tell me if bluetooth is ON or OFF by default at startup after a factory reset? I swear that it was off the first time I booted up but now it is on. Makes me wonder if it was infected or changed. Anyone know if the default was changed? Thanks
Eutility said:
Can you tell me if bluetooth is ON or OFF by default at startup after a factory reset? I swear that it was off the first time I booted up but now it is on. Makes me wonder if it was infected or changed. Anyone know if the default was changed? Thanks
Click to expand...
Click to collapse
Bluetooth may or may not be "on" but it should not be "connected" or "remember" any devices if you did a factory reset.
However, without wiping internal SD and data, you are subject to "potential weird things" that can happen.
It's why I never report a bug unless I made absolutely sure to wipe data and internal SD before trying to reproduce an issue.
Bluetooth has been turned on by default for all the software versions I've used.
Upon a factory flash or reset, Bluetooth will be enabled but no devices will connect/be remembered.
On a side note, No application can "infect" an android. Most of these antivirus applications are complete bullcrap. Dont get me wrong, there are some dangerous apps out there, but you would still have to give the app permissions and accessibility access For it to do any damage. even then, simply uninstalling them Will remove everything.
Thanks for your responses. I do appreciate it. Well, unfortunately I have had multiple phones infected by ex-neighbors. I literally would lose control over the phone and during calls they would make beeping sounds like I had hit a key. Once I flashed my phone outside of town and they kept messing with it. I had always thought they had a tool which enables persistence even through flashing, but it may be that they are using Signaling System 7 (SS7) and are just reinfecting them remotely. (you can watch a 60 minute special on SS7 if u like, available online) They were using an IMSI catcher when I lived next door to them. With the Pixel XL I was having ALOT of data use and reset the phone after some weird stuff happened that I had come to recognize as likely signs of being compromised, and I think put in a new SIM with a new phone #. It was much better after that. It was a nightmare with them and one of them even followed me home after work a month after I moved away. Not to mention steal things like laundry soap and put them on their side of the street in front of my house. Creeps. At this point it is just pathetic and weird. Just trying to take reasonable precautions now and live my life. If they want to waste their time that is sad.
Really glad to hear the bluetooth being there is not a deviance from default. Thanks