For some reason when I plug headphones into my nook color I can't hear any music/alerts etc. The only sound I hear is what sounds like an eight bit helicopter. Anyone have anybidea what this is?
Also when I first turn on my nook it makes a very high frequency sound, I think it may be related to the battery based on my experience racing electric r/c cars, any ideas?
And lastly for some reason I can't get any videos to play on it, even videos that used to work, any ideas/fixes?
Any help would be very appreciated, I love my nook so I wanna get these issues resolved as soon as I can. Thank you in advance.
Sent from my NookColor using XDA Premium App
It's hard to say anything without knowing:
what OS you're running
whether, how, and how much you've overclocked
what adjustments to sound output, if any, you've made in DSP Manager or Nook Tweaks
how long you were using the NC before the problem started
How to ask a question
Taosaur said:
It's hard to say anything without knowing:
what OS you're running
whether, how, and how much you've overclocked
what adjustments to sound output, if any, you've made in DSP Manager or Nook Tweaks
how long you were using the NC before the problem started
How to ask a question
Click to expand...
Click to collapse
Cm7 nightly 132 and up
Running at 800mhz
No adjustments at all
Using it for about two months before the problems started
Sent from my NookColor using XDA Premium App
First, I'd say those are odd symptoms and may be indicative of a hardware fault. However, the NC has been known to have a number of audio issues, and adjusting gains in dalingrin's Nook Tweaks app (it's on the market) can address many of them.
Nightly 132 is known to have graphics acceleration issues which may be the source of your video woes. They should be addressed in the next nightly, 135, or you can roll back to an earlier version (at this point, I'd see what Nook Tweaks does for you, and otherwise just deal until 135 comes out).
Also, it may sound dumb, but play with how your headphone jack is seated. Sometimes the slightest turn or movement in or out can do wonders.
Well, I never thought I'd hear about this again...
My friend bought a NC from eBay a few weeks ago, and it had some strange problems. First, it wouldn't play any media. It would load a file and look like it's starting to play, but there would never be any audio or video. If a video file was open, we could move the slider to different parts of videos, and it would show that frame, but it would not actually play. He left it with me to fix.
That night, I found the same "8-bit helicopter" pulsing coming from the headphone jack while the Nook was plugged in to a power source. I also noticed that the top right corner on the backside was becoming very warm, much hotter than my properly functioning NC.
The Nook continued to refuse to play any media, it would not even play the intro vid of the stock ROM. Teardown pics show that the area which was producing excess heat was the audio chip. I'm guessing it fried out, which would explain all the symptoms.
That particular Nook also appeared to have been opened up previously. We assumed someone tried to hardware mod it and failed, and tried to recoup some loss.
Edit: The Nook operated normally otherwise, except massive battery drain. It would hold a charge cold off, but the battery would discharge in just hours, even while sleeping, while on.
TheAmazingDave said:
Well, I never thought I'd hear about this again...
My friend bought a NC from eBay a few weeks ago, and it had some strange problems. First, it wouldn't play any media. It would load a file and look like it's starting to play, but there would never be any audio or video. If a video file was open, we could move the slider to different parts of videos, and it would show that frame, but it would not actually play. He left it with me to fix.
That night, I found the same "8-bit helicopter" pulsing coming from the headphone jack while the Nook was plugged in to a power source. I also noticed that the top right corner on the backside was becoming very warm, much hotter than my properly functioning NC.
The Nook continued to refuse to play any media, it would not even play the intro vid of the stock ROM. Teardown pics show that the area which was producing excess heat was the audio chip. I'm guessing it fried out, which would explain all the symptoms.
That particular Nook also appeared to have been opened up previously. We assumed someone tried to hardware mod it and failed, and tried to recoup some loss.
Edit: The Nook operated normally otherwise, except massive battery drain. It would hold a charge cold off, but the battery would discharge in just hours, even while sleeping, while on.
Click to expand...
Click to collapse
This sounds like mine... lol unfortunately. I'm gonna buy a new battery to fix the drain issues, other than that I'm going to attempt to wait out the media issues. Thanks for all the help everyone.
Sent from my NookColor using XDA Premium App
nerdcroid said:
This sounds like mine... lol unfortunately. I'm gonna buy a new battery to fix the drain issues, other than that I'm going to attempt to wait out the media issues. Thanks for all the help everyone.
Sent from my NookColor using XDA Premium App
Click to expand...
Click to collapse
I don't know where you got your NC, but assuming you haven't opened it up, you might try flashing back to stock and taking it into a store to see about a warranty replacement. They may just tell you to call customer service, but at least you can say you verified the problem with someone. If you've only had the thing two months, you don't want to just live with bad hardware.
Taosaur said:
I don't know where you got your NC, but assuming you haven't opened it up, you might try flashing back to stock and taking it into a store to see about a warranty replacement. They may just tell you to call customer service, but at least you can say you verified the problem with someone. If you've only had the thing two months, you don't want to just live with bad hardware.
Click to expand...
Click to collapse
I bought it from best buy. I did open it up like a Month and a half ago because one of my SD cards was put in wrong (oops) so it was floating around loose so I opened it up and pulled it out but that was the only time I opened it up.
Sent from my NookColor using XDA Premium App
Does anyone know what kind of fees I'd be looking at if I took it in to get repaired?
Sent from my NookColor using XDA Premium App
@theAmazingOne did your friend ever try a pair of Bluetooth headphones?
Sent from my NookColor using XDA Premium App
Related
Is this a defect? Do I need to return the phone? I'm working with all the latest OTA updates.
I've tried to force 720p and 480p through settings, and tried auto-detect.
If I have it on the gallery app in a slideshow and plug it in, I see the "HDMI" label in the status bar before it goes black.
Strange thing is that the buttons still light up and go off with the HDMI cable plugged in if I hit the power button. But I can't use the power button to turn it back off. I have to do a battery pull.
PITA! HDMI was one of the reasons I bought this dang phone?
Can anyone out there think of any reason why this might be happening?
Thanks for any help.
You're not the only one. My cable is collecting dust somewhere for the past month. Maybe cyan will fix it? This is my first htc and I'm starting to think I shouldn't hold my breath for the company to fix it. As time progresses, I'm liking this phone less. I don't know if all htc phones are like this that it seems like it was rushed to market too soon without fixing the glaring bugs with it.
Sent from my PC36100 using XDA App
I share some of your sentiment, but not all of it. I still love this phone. But HDMI was one of their big, giant marketing points that got me to buy it. A phone with an HDMI out! That's crazy! Also, when I think of what I can do with it it's pretty cool.
But for it not to work at all? Not one bit? That is just crazy.
My theory is that they didn't realize what kind of copyright hell they were unleashing upon themselves when they put it on there, and so they intentionally broke it. If they ever release some kind of source code maybe one of these chefs can make it work.
Can you try another cable that is known to work? I've been messing around the HDMI output the past week since I got my cable (Molex #687860003, from eBay), and I think the implementation is pretty fault-tolerant. I've been plugging and un-plugging it repeatedly and never had a lockup, with and without the Gallery/Video application active. Blu-Ray rips at 1280x720p look and sound amazing for such a small device. There was some discussion on another forum about a bad run of Amzer cables (that caused lockups), so maybe it's worth borrowing someone else's cable and giving it another go before turning in the phone for replacement. Good luck.
I use it everyday without a problem (Youtube).
rasterX said:
Can you try another cable that is known to work? I've been messing around the HDMI output the past week since I got my cable (Molex #687860003, from eBay), and I think the implementation is pretty fault-tolerant. I've been plugging and un-plugging it repeatedly and never had a lockup, with and without the Gallery/Video application active. Blu-Ray rips at 1280x720p look and sound amazing for such a small device. There was some discussion on another forum about a bad run of Amzer cables (that caused lockups), so maybe it's worth borrowing someone else's cable and giving it another go before turning in the phone for replacement. Good luck.
Click to expand...
Click to collapse
Thanks for the advice. Unfortunately, I don't have another accessible. But you are correct in that I should try it with another cable (and probably on another TV as well).
I went ahead and bought this one. It looks legit, plus it's long. I'll test it again when it arrives. http://cgi.ebay.com/ws/eBayISAPI.dl...40086&ssPageName=STRK:MEWNX:IT#ht_3062wt_1137
ive been using mine since day one without a problem. i bought the phone and cable from sprint on launch day.
The problem is with the old fps fix kernels. now they support hdmi out too. htc has the most lazy ass devs ever if they capped the fps cuz of hdmi... lmao
gmelchert said:
The problem is with the old fps fix kernels. now they support hdmi out too. htc has the most lazy ass devs ever if they capped the fps cuz of hdmi... lmao
Click to expand...
Click to collapse
Wait! Come back!
By "old" fps fix, which do you mean? I'm using the netarchy-toastmod 3.7.2.a kernel, which supposedly had hdmi fixed. (I'm going to update to the latest now, I hadn't noticed there was another.)
Should I be using a different kernel?
Use version c.
Sent from my PC36100 using XDA App
Ok Mr Momoman. I will try when I get home.
Sprockethead said:
Wait! Come back!
By "old" fps fix, which do you mean? I'm using the netarchy-toastmod 3.7.2.a kernel, which supposedly had hdmi fixed. (I'm going to update to the latest now, I hadn't noticed there was another.)
Should I be using a different kernel?
Click to expand...
Click to collapse
thats odd... It worked fine on the 3.7.2b that i was using... hmm yeah try the upgrade
Yeah the release notes say that HDMI is working on all 2.7.x releases. Who knows. I'll try at home and report.
Here's whats happening on my Xoom.
1) Audio - even if the volume is 1 click from silent, it plays full blast
2) Headphone - even with headphone jack plugged in, it plays full blast from speaker
I've adjusted audio w/ the rockers as well as in the system settings and they never play correctly. It's either FULL blast or too quiet to hear anything until it's raised to the max.
This applies to games playing, videos, music, anything that uses the audio.
Anyone else have this problem? It's quite frustrating...
Am I the only one with this problem?
Nope I have the same issue.
Sent from my Xoom using XDA App
acleansc4 said:
Am I the only one with this problem?
Click to expand...
Click to collapse
I've been having the same issue, but not universally. I can't recall specifically what app(s) didn't suffer from this, but I know there were 1 or 2. That said, as long as I haven't fabricated that memory, it would seem to indicate a software problem, not hardware.
My hope is that it will get fixed in one of the honeycomb updates.
I want to say that YouTube was one that didn't have the problem, but can't test (don't want to wake the misses)
Sent from my Xoom using XDA Premium App
The same thing happens on my Xoom too.it didn't happen when I first got it though.it just recently started doing it.hopefully a update will fix it.
Sent from my DROIDX using XDA App
acleansc4 said:
Here's whats happening on my Xoom.
1) Audio - even if the volume is 1 click from silent, it plays full blast
2) Headphone - even with headphone jack plugged in, it plays full blast from speaker
I've adjusted audio w/ the rockers as well as in the system settings and they never play correctly. It's either FULL blast or too quiet to hear anything until it's raised to the max.
This applies to games playing, videos, music, anything that uses the audio.
Anyone else have this problem? It's quite frustrating...
Click to expand...
Click to collapse
You should clarify if you are using a bone stock XOOM or an unlocked/rooted/overclocked XOOM.
I do not have this problem, though I can say that All but the top 3 or 4 volume settings are inaudible. I spend my time at one or two steps below max since the max volume setting is majorly overdriven.
OK.problem fixed simply by restarting my Xoom lol..try it & see if it works and let us know please.
Sent from my Xoom using XDA App
setite said:
You should clarify if you are using a bone stock XOOM or an unlocked/rooted/overclocked XOOM.
I do not have this problem, though I can say that All but the top 3 or 4 volume settings are inaudible. I spend my time at one or two steps below max since the max volume setting is majorly overdriven.
Click to expand...
Click to collapse
Sorry about not mentioning it in the first post.
I am running a BONE STOCK Xoom.
Arun01 said:
OK.problem fixed simply by restarting my Xoom lol..try it & see if it works and let us know please.
Sent from my Xoom using XDA App
Click to expand...
Click to collapse
I did a factory data reset and it has solved the issue. However, I haven't added any of my media files yet to retest. Update on that to follow later on...
So after reloading some media, the sounds all messed up again. Bone stock Xoom...WTF
Even the headphone jack doesn't disable the rear speaker when inserted...
I'm tempted to return but I'm sure they'll fix this soon...HOPEFULLY!
edit: After the 3.0.1 update, all issues with audio have been fixed!
I've been having this issue with my epic for the past month or so. If something (other than a phone call) is playing audio (game, music) through the speaker or the earbuds I hear a crackling noise when I touch the screen and only when I touch the screen. It's very easily reproduced too. For example, I'll have pandora playing through the speaker and it'll play fine until I touch the screen to change the song or do something else. If I keep my finger on the screen it'll continue making the crackling noise until I lift it off. Doesn't happen if I touch the screen while it's off. The same thing has happened on every rom I tried including odin to stock eb13 and ec05. Since I've had the phone for less than a year, can I take it to a sprint store and get a replacement? Or does anyone have any idea how to fix this?
Sent from my SPH-D700 using XDA App
This may not make the most sense, but it sounds like you've got some exposed wires or something on the inside, my guess would be that the capacitive touch screen is causing some feed back when the field is broken and you touch it. May be a bad capacitor, or just some crossed/exposed wire, but we have had a similar issue with a wall touchpad in one of our class rooms. they control a Audio visual box and once it was damaged would produce a crackling over the speaker system when you would use the touch pad to change source or adjust volume and the AV box was turned on. The unit had to be replaced, I'd be willing to bet the same would go for the phone as replacement parts wouldn't be the easiest to come by.
gearless said:
This may not make the most sense, but it sounds like you've got some exposed wires or something on the inside, my guess would be that the capacitive touch screen is causing some feed back when the field is broken and you touch it. May be a bad capacitor, or just some crossed/exposed wire, but we have had a similar issue with a wall touchpad in one of our class rooms. they control a Audio visual box and once it was damaged would produce a crackling over the speaker system when you would use the touch pad to change source or adjust volume and the AV box was turned on. The unit had to be replaced, I'd be willing to bet the same would go for the phone as replacement parts wouldn't be the easiest to come by.
Click to expand...
Click to collapse
Do you think I should call Sprint first or just go into a store?
dieselg5 said:
Do you think I should call Sprint first or just go into a store?
Click to expand...
Click to collapse
Go into the store so they can see the problem personally. They will most likely order you a refurb.
dieselg5 said:
Do you think I should call Sprint first or just go into a store?
Click to expand...
Click to collapse
Go to a store, Sprint will tell you that over the phone. haha
This is a well known issue around here. Hold up ill dig up a post about it. I am happy to say that as of Bonsai 4.1.1 this issue no longer exists.
http://forum.xda-developers.com/showthread.php?t=1026971
dieselg5 said:
I've been having this issue with my epic for the past month or so. If something (other than a phone call) is playing audio (game, music) through the speaker or the earbuds I hear a crackling noise when I touch the screen and only when I touch the screen. It's very easily reproduced too. For example, I'll have pandora playing through the speaker and it'll play fine until I touch the screen to change the song or do something else. If I keep my finger on the screen it'll continue making the crackling noise until I lift it off. Doesn't happen if I touch the screen while it's off. The same thing has happened on every rom I tried including odin to stock eb13 and ec05. Since I've had the phone for less than a year, can I take it to a sprint store and get a replacement? Or does anyone have any idea how to fix this?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
p3dr0maz said:
This is a well known issue around here. Hold up ill dig up a post about it. I am happy to say that as of Bonsai 4.1.1 this issue no longer exists.
Click to expand...
Click to collapse
Must be various on a per phone basis then, because I've flashed EVERY single ROM to date and I've never experienced that.
p3dr0maz said:
This is a well known issue around here. Hold up ill dig up a post about it. I am happy to say that as of Bonsai 4.1.1 this issue no longer exists.
http://forum.xda-developers.com/showthread.php?t=1026971
Click to expand...
Click to collapse
It doesn't sound like a software issue, therefor a rom won't fix the issue. If he goes back to stock, and the issue persists its hardware. Sounds like a loose wire, but I can't be sure...
Sent from my SPH-D700 using XDA Premium App
XtaC318 said:
It doesn't sound like a software issue, therefor a rom won't fix the issue. If he goes back to stock, and the issue persists its hardware. Sounds like a loose wire, but I can't be sure...
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
We were trying to track down the cause, but never did, we still think it might be vodoo sound related when its built into the kernel...
But if it happens on stock, it could be something else, only happens to me on modded kernels.
If you can see this link please take a few moments to click and read, its for a good cause, you can make a difference, help spread the word today...
http://www.picketfenceblogs.com/vote/3616
I've never expiernced this either
Not sure what to say if it happens on stock. Proud to say i've never ran stock except for the 2 minutes before I flashed a custom ROM. And yeah I mentioned the ROM because it does have a custom kernel and even though we've all heard arguments that it's this or that i still have to say it's gotta be something in how voodoo is compiled into the kernel like ecooce says.
So I odin back to DI18 and let it update before I took it to the store and of course it's not happening anymore
I remember going back to stock after ACS 1.1 destroyed my phone a few times (my phone would freeze a lot and since there's no journaling in 1.1 everything would get corrupt) and I still had the issue. Playing air attack hd with the crackling was horrendous. Anyway, thanks for the support everyone. Sorry for the scare
dieselg5 said:
I've been having this issue with my epic for the past month or so. If something (other than a phone call) is playing audio (game, music) through the speaker or the earbuds I hear a crackling noise when I touch the screen and only when I touch the screen. It's very easily reproduced too. For example, I'll have pandora playing through the speaker and it'll play fine until I touch the screen to change the song or do something else. If I keep my finger on the screen it'll continue making the crackling noise until I lift it off. Doesn't happen if I touch the screen while it's off. The same thing has happened on every rom I tried including odin to stock eb13 and ec05. Since I've had the phone for less than a year, can I take it to a sprint store and get a replacement? Or does anyone have any idea how to fix this?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I am glad you fixed it.
Kernel bug. Likely not a hardware issue.
I have the same exact behavior with Genocide 1.0. I'm unaware if this occurs in other Voodoo sound enabled Kernels but it sounds like it does.
On stock EC05 the problem goes away. For me anyways.
It does for most. TWZ 1.4 doesnt have the problem and neither does Bonsai 4.1.1 kernel AFAIK. There might be other known good combos.
TheDub said:
Kernel bug. Likely not a hardware issue.
I have the same exact behavior with Genocide 1.0. I'm unaware if this occurs in other Voodoo sound enabled Kernels but it sounds like it does.
On stock EC05 the problem goes away. For me anyways.
Click to expand...
Click to collapse
I have the same issue on certain kernels. I was just about to ask, too. VERY noticeable when I'm playing music in my car and need to do something onscreen, makes the audio sound terrible.
I had this issue on several roms, including acs and the previous bonsai. In fact, my experience with acs was identical to yours. My phone just didn't play well with it. I don't have this problem with stock plus rom, even with the genocide kernel. Give that one a shot.
Sent from my SPH-D700 using XDA App
greezestain said:
I had this issue on several roms, including acs and the previous bonsai. In fact, my experience with acs was identical to yours. My phone just didn't play well with it. I don't have this problem with stock plus rom, even with the genocide kernel. Give that one a shot.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
or its loose wire on your audio jack could be short to graounf when you tap the phone
TheDub said:
Kernel bug. Likely not a hardware issue.
I have the same exact behavior with Genocide 1.0. I'm unaware if this occurs in other Voodoo sound enabled Kernels but it sounds like it does.
On stock EC05 the problem goes away. For me anyways.
Click to expand...
Click to collapse
Mine also crackles when the brightness adjusts. This includes when the screen fades out when I turn it off.
I hadn't noticed it when simply touching the screen though, just with the brightness. Also, I never noticed it until I started running custom roms with voodoo built in.
Sent from a secret underground bunker
Download voodoo control and turn down headphone amplifier or turn down volume limit. Might do the trick.......
Has anyone lost like 60% of sound reproduction volume with the upgrade to 3.1? I'm about to do a wipe and reinstall if it's just me, but basically I can't hear **** now.
I used to be able to hear the tablet clearly from another room, not loudly but i could make out what song was playing. Now I can barely hear the tablet when it's in my hands. Is it 3.1 or did primordial do something. Is there a sound mod app? I have looked and my volume settings all APPEAR to be maxed out.
bump
tenchar
I don't know that it's a 60% reduction but I have noticed it as well.
Sent from my Transformer TF101 using XDA Premium App
No change for me. Internal speakers are still plenty loud. Headphone is too quiet, but that was the case with earlier firmware too, but that can to some extent be solved with a free app called Volume+. (It's a pay app in the market, but free if you go to the author's own site, and enable installing apps from outside the market.)
What's hopeless for me is the microphone. It barely picks up anything more than 2-3 inches away from the mic port. To Skype, I actually have to hold the tablet sideways so my mouth is right next to the mic, which seems ludicrous to me. Been meaning to start a thread and ask if others have the same issue.
I just tried to play some mp4s that I have, I noticed that the volume is lower too.
It was anemic before and possibly slightly more now. The overall volume (or lack of it) is the only thing I really find disappointing about the TF. Was playing a vid for a doc at a meeting the other day, and three of us huddle around it had a hard time hearing it cranked all the way up. The slightest noise of anyone else doing anything in the room just killed it.
Yeh I've had a major drop in left speaker and bad drop in volume on headphones ...... And mine was the official 3.1 update too...... Very dissatisfied
Sent from my Desire HD using XDA App
Same problem here. Video is very low when playing avi's or TV Shows Stream. But YouTube app is plenty loud.
Any fixes?
I bought volume + and now it is much louder. Left speaker is still lower volume though. But now atleast I can hear music from the tab.
Sent from my Samsung Epic
Bumping this. I'm hoping someone has an idea. It feels like its getting worse. Basically I used to be able to place the tablet on a rack in front of the ****ter and enjoy a show while I pooped, but now I simply can't hear it at all, even with no white noise or anything that could be an issue. So with what you guys have said, I know I'm not crazy.
SOMEONE PLEASE FIGURE THIS OUT. I HAVE NO IDEA HOW.
some peeps already figured out it's a messed up sound config file and you can fix it if you are rooted, was readig through a thread on it here I bleieve lst night. I'm sure it'll be fixed with a software update.
darkonex said:
some peeps already figured out it's a messed up sound config file and you can fix it if you are rooted, was readig through a thread on it here I bleieve lst night. I'm sure it'll be fixed with a software update.
Click to expand...
Click to collapse
I'm delivering pizzas right now. Do you have a link
I had this too before I sent it in for RMA service.
In fact, I knew about this issue before I even upgraded to 3.1 so I was aware and decided to see if these people were making this up or not. After upgrading I did notice a significant decrease in volume. This was disappointing, it almost made me feel like I was using the Nook Color again.
You're not imagining this. Before the sound was so loud that you could hear it from another room and the unit actually vibrates a bit. Now it's so low it's hard to hear the low tones in anything.
My guess is they messed with it to try to fix the imbalanced speaker issue but ended up messing it up for other people now. ETA for fix is fifteen years. See you then!
Noticed lower volume too after update. take the srs_proceeding.cfg file from my 3.0.1 and paste it to the 3.1 rom and it was louder.
Sent from my Transformer TF101 using Tapatalk
Mine is fine. I'm not rooted and I have the update.
Sent from my awesome Asus Transformer using XDA's premium app.
As the title states. Nexus 4 random power offs. Has anyone seen anything like this?
Here is the background info:
My parents have Nexus 4 phones as do I. All of our phones were ordered at the same time about 2 months or so ago when they became available again. All phones are the 16GB version. All phones bone stock with just OTA updates, not unlocked or rooted other than how they are shipped. All using T-Mobile prepaid plans.
My phone and my father's seem fine. My mom's however seems to shutdown on its own. It is random. Initially I thought that it may be an issue where she isn't used to a smart phone and isn't charging it enough. It happens though at times while it is connected to the charger. It also has happened while carrying it off the charger.
One odd thing is that when they got the phone they brought them to my house and dropped them off to have me set them up. One had the plastic screen protector with the printing on it from the factory the other didn't. I don't know which is which though now. It is a 50/50 shot if this is the one.
I have been around android since the G1 days and run the same phone. I can't think of a setting on the phone that would power it down at a certain time or period of time. She really doesn't have much for apps and is a very light user.
Not sure what to try but I was thinking about doing a wipe of the phone to see if it helps.
Anyone else have any ideas? If the wipe doesn't help the only other thing I can think of is that there is a physical issue with the phone.
I haven't seen this on my phone but there was a period of time where HD Widgets on my N7 would cause a reboot. That was fixed with an app update. This isn't a case where the device reboots. It is a complete shutdown which I find odd. So I have seen an app cause issues kind of like this. For the most part the apps that she has on her phone, I also have on mine. Well I have way more but there really isn't anything on her phone that I am not also running.
I should add that she has the phone in a TPU case. As we all do. My case design is a little different than theirs but they have cutouts for the buttons. So it isn't a case where the case is pressing on the power button. That could be an issue with my case as it covers the power button but I haven't had that issue.
Thanks
Sounds like it might be a defective battery...
Sent from my Nexus 4 using xda app-developers app
BigDig said:
Sounds like it might be a defective battery...
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
That is what I am kind of thinking. Either the battery or the smart battery chips. I think I will try a wipe first but like I said but it is odd.
sennister said:
One odd thing is that when they got the phone they brought them to my house and dropped them off to have me set them up. One had the plastic screen protector with the printing on it from the factory the other didn't. I don't know which is which though now. It is a 50/50 shot if this is the one.
Thanks
Click to expand...
Click to collapse
That sounds kind of questionable (fishy) to me... I also have the 16GB version, and I also did the OTA when I got it. But to be honest the stock OS lasted only about an hour before I rooted and started trying out custom ROMs I have not had the issue you're describing though. How are the results from your factory reset?
Also, would you consider putting on a stock-based custom ROM (such as rasbean vanilla) for your mother's phone? If the problem is software based then a reset or a new ROM might yield different results. But if the problem persists it might be hardware and I'd suggest you contact Google about servicing.
amartolos said:
That sounds kind of questionable (fishy) to me... I also have the 16GB version, and I also did the OTA when I got it. But to be honest the stock OS lasted only about an hour before I rooted and started trying out custom ROMs I have not had the issue you're describing though. How are the results from your factory reset?
Also, would you consider putting on a stock-based custom ROM (such as rasbean vanilla) for your mother's phone? If the problem is software based then a reset or a new ROM might yield different results. But if the problem persists it might be hardware and I'd suggest you contact Google about servicing.
Click to expand...
Click to collapse
I don't want to root and have my mom run a modified ROM. They live about a half hour from me so I haven't tried a wipe of the phone yet and because of the distance I don't want to deal with the issues that sometimes come up when you go with modified ROMs when I am not there. She is a very basic user and this is the first smartphone for my father and mother. Keep in mind they are in their early 70s and not really that strong on the tech side of things. I have to get some time to run over there and take a look at it. Maybe later next week.
I was just wondering if anyone else has had this issue. I think if a wipe doesn't help I will talk to Google. A search really didn't show much other than some people that were seeing a random reboot issue. I have seen apps doing that.
I have been through their warranty replacement process and it is a bit of a PITA. I am on my 3rd Nexus 7 due to hardware issues with the first 2. My N4 and my fathers have been rock solid.
While I have run custom ROMs in the past, I usually run stock until I find a need that requires me to root. Eventually I will probably root and go with a custom ROM on my N4 but
sennister said:
She is a very basic user and this is the first smartphone for my father and mother. Keep in mind they are in their early 70s and not really that strong on the tech side of things.
Click to expand...
Click to collapse
Yeah, I know what you mean. I'm giving my parents my old LG P990 phone and I just put an AOKP rom on it. I also installed Nova Launcher for them and configured it so there's just one texting app and one calling app the one and only one homescreen. No dock either, just in case they click something by accident or get lost in the app drawer
Since you have the same phone as your mom, a self-less workaround would just be to give her yours (pre-configured), and then you can fiddle around with the problematic one until you find a decent solution. :good:
amartolos said:
That sounds kind of questionable (fishy) to me... I also have the 16GB version, and I also did the OTA when I got it. But to be honest the stock OS lasted only about an hour before I rooted and started trying out custom ROMs I have not had the issue you're describing though. How are the results from your factory reset?
Also, would you consider putting on a stock-based custom ROM (such as rasbean vanilla) for your mother's phone? If the problem is software based then a reset or a new ROM might yield different results. But if the problem persists it might be hardware and I'd suggest you contact Google about servicing.
Click to expand...
Click to collapse
amartolos said:
Yeah, I know what you mean. I'm giving my parents my old LG P990 phone and I just put an AOKP rom on it. I also installed Nova Launcher for them and configured it so there's just one texting app and one calling app the one and only one homescreen. No dock either, just in case they click something by accident or get lost in the app drawer
Since you have the same phone as your mom, a self-less workaround would just be to give her yours (pre-configured), and then you can fiddle around with the problematic one until you find a decent solution. :good:
Click to expand...
Click to collapse
Hmm. That is a good idea. The PITA part would be to get everything loaded from my phone to hers. I really wish I could run Titanium backup without root as it would make it super easy to move the apps over. Though I don't have that much loaded on my phone. Things that are a pain to set up have configuration export methods like Tasker. It would rule out the end user being the source of the issue. I don't think that is it though. If we swap and it goes away, then I can consider the wipe as the solution. If the problem moves to me then it is a physical issue and call Google. If the problem persists with her, I load all her apps on the phone I carry as well to see if I start to have the issue or it becomes a training issue. The thing I like about this the most is that it is a clear process to rule out several things. I can go over there and sit with the phone but if it doesn't power off when I am there I don't gain much other than spending some time with my parents.
I don't think this is an issue but I did have to provide my IMEI# when doing the activations. In the past though on T-Mobile I have handed phones down to others and all we did was a SIM swap. I would imagine that is the case here.
Oh and one thing I did leave out. They were using their old cell phone chargers on the N4 phones. I told them to swap chargers and use the ones that came with the phone. The old ones may not put out enough power and the phone could in theory run down to the point where it shuts off and slowly charge from that point and I don't think it would turn back on. Keep in mind a retired user who just had a knee replacement so she is at home more often than not.
Did you find out the cause? I have the same issue happened twice today
The random shut off either charging or not happens to me but as mentioned before in a related thread, a lot of the times it also happens on Wi-Fi, and having WiFi optimization on.. purple were turning that off and some fixed the issues. This is my second nexus 4, so I right id give it a try and not use wifi and hasn't happen since I received mines on the 4th of may
Sent from my Nexus 4
noodles2224 said:
The random shut off either charging or not happens to me but as mentioned before in a related thread, a lot of the times it also happens on Wi-Fi, and having WiFi optimization on.. purple were turning that off and some fixed the issues. This is my second nexus 4, so I right id give it a try and not use wifi and hasn't happen since I received mines on the 4th of may
Sent from my Nexus 4
Click to expand...
Click to collapse
So you're saying it's a software issue?
Looks like it.. Turning off optimization or not even using WiFi at all worked..
Sent from my Nexus 4