Database Info

Nexus S Freezing - How big a problem is this?

I'm on the verge of buying a Nexus S but I am now reading about many freezing issues where the phone loses all responsiveness after the backlight goes out on occasion - the only solution being to pull the battery and reboot, only to have it happen again.
This thread shows that some people are returning their phones to Samsung and are seeing a fault diagnosis of 'bad BGA' and a fix of 'PBA replaced'
Original Problem:
Technical Inquiry
Phone Freezing / Locked U
Freeze/Delay Between Menu
Problem found:
BAD BGA COMPONENT
WARRANTY, REPLACE PART
Solution:
Replaced PBA
Passed All Functional Testing
Just how wide a problem is this, is it something that will affect pretty much everyone at some point or are these cases failry isolated?
edit: I am buying from someone who has this phone on contract so I am wondering also if I will be able to get support from Samsung should I run into this problem. Are warranty issues dealt with by Samsung direct or are they passed through the carrier when originally obtained on contract?
Any thoughts?

never experienced any of these problems. you have a 30 day return policy (maybe less now)

zephiK said:
never experienced any of these problems. you have a 30 day return policy (maybe less now)
Click to expand...
Click to collapse
Unfortunately not, see my edit above.
Also, it seems users are running into this problem after owning the device for a while, taking them beyond their 28 day / 30 day return

i've had mine since it was first available and never had any problem like this.

I've also never seen this.

milkham said:
i've had mine since it was first available and never had any problem like this.
Click to expand...
Click to collapse
same. ive had it maybe like a 1.5 week after release date

It happens to me if i mess around with custom kernels and o/c speed but so far if i use netarchy's stable CFS, it'll be fine. No freezing and having to pull my batt.
It happens if i use hornity or some BFS kernels. Haven't tried Jame Bond yet to test it out.

i think the OP is confusing the SGS issues with SNS
the SNS doesn't have any of those problems listed.

AllGamer said:
i think the OP is confusing the SGS issues with SNS
the SNS doesn't have any of those problems listed.
Click to expand...
Click to collapse
the thread the OP linked is Nexus S

only time that has happened to me is when i overclock to 1.4 ghz and the phone can not handle it

Ok, it's encouraging that this isn't affecting everyone but still a bit worrying.
AllGamer said:
i think the OP is confusing the SGS issues with SNS
the SNS doesn't have any of those problems listed.
Click to expand...
Click to collapse
Wrong - as zephiK has pointed out, the link is to a whole load of people having issued with the Nexus S, NOT the Galaxy S.

I believe the most problems with smartphones are in software, not hardware. And software could/should be patched/updated.

and this is one of the reasons that preventing me from walking into cpw and buying it tomorrow.

I am Having this exact issue with my phone. it is unusable the phone freezes every 20 minutes. Hope Samsung finds a fix for this soon.

I just got my nexus s the other day but I haven't had any freezing either I hope those with the issue get it sorted out though

loading another ROM would help, or perhaps it might be a hardware issue, in which case, take it back for an exchange

AllGamer said:
loading another ROM would help, or perhaps it might be a hardware issue, in which case, take it back for an exchange
Click to expand...
Click to collapse
Happens in stock rom, and many other custom roms too. So I dun think its the rom problem

oh dear, this is exactly what I'm concerned about. Any pattern as to which are affected by this, ie just slcd or just samoled? Only a thought.
I shall soon receive my second nexus s and I really don't want to have this problem!

I'm using the i9023 if that info helps.

Yes thanks but it's not what I wanted to hear as the chances are that this is the one I will receive.
I've heard of people reporting successfully fixing this with a full reflash, others say it's a hardware issue.
Keep us posted.

How to install init to fix froyo freeze ?

hello xda members
i have install froyo fx06 bundle here
my problem is sometimes the phone freeze. i read the entire post to find the solution to fixed that. then i found the only solution is to install init at here . can someone make a tutorial how to install that. i mean the step by step tutorial.

Have you any idea as to how to use ADB or terminal? If you do, then you are pretty much done, with the exception of executing those commands in that post. If not, you'll have to wait till it gets committed like the rest of us Or just wait till someone that does know, comes across your thread! That thread is mainly there for people who know how to do this already.

R^7Z said:
Have you any idea as to how to use ADB or terminal? If you do, then you are pretty much done, with the exception of executing those commands in that post. If not, you'll have to wait till it gets committed like the rest of us Or just wait till someone that does know, comes across your thread! That thread is mainly there for people who know how to do this already.
Click to expand...
Click to collapse
i don't know how to use ADB or terminal. actually this is my first time heard that. hehe

Some say it isn't that difficult while others have a difficult time trying to understand English, much less speak/type it(like myself ). If you feel up to it, you can start by reading HERE. Unless someone else has this simplified elsewhere. If that were the case and I knew of it, I woldn't be pointing you in this direction.

Thank you for trying to help me.

today i have install [RIL + ROOTFS] on my device after found this thread http://forum.xda-developers.com/showthread.php?t=950383
but the problem still same. i have read that [RIL + ROOTFS] is to fixed freeze because 3g problem i think. but i think my problem is not about 3g.
my problem i think is about my device sometimes not showing display, it happen if i put my phone in standby mode then when i want to on back it will not show the display. but i can tell that my phone is working and not freeze, only it have blank screen.
please help me..!!

hotsmusic said:
today i have install [RIL + ROOTFS] on my device after found this thread http://forum.xda-developers.com/showthread.php?t=950383
but the problem still same. i have read that [RIL + ROOTFS] is to fixed freeze because 3g problem i think. but i think my problem is not about 3g.
my problem i think is about my device sometimes not showing display, it happen if i put my phone in standby mode then when i want to on back it will not show the display. but i can tell that my phone is working and not freeze, only it have blank screen.
please help me..!!
Click to expand...
Click to collapse
and i think it's not because flax cable because this problem only happen when i use froyo fx06.

Honestly, I've never had any real problems with FroYo freezing on boot. Just the SoD issue due to partial panel collapse. Supposedly, that (modified rootfs) only fixes the freezing on boot issue. Unfortunately, there is no way I can reproduce the issue you are experiencing on my end to help troubleshoot. Some blame it on the operator/service provider and others think it's the build itself. As for me, well I'm not sure what to think because it doesn't seem to affect me much. Have you tried Gingerbread yet? Might be something to play around with till the issue gets fixed.

R^7Z said:
Honestly, I've never had any real problems with FroYo freezing on boot. Just the SoD issue due to partial panel collapse. Supposedly, that (modified rootfs) only fixes the freezing on boot issue. Unfortunately, there is no way I can reproduce the issue you are experiencing on my end to help troubleshoot. Some blame it on the operator/service provider and others think it's the build itself. As for me, well I'm not sure what to think because it doesn't seem to affect me much. Have you tried Gingerbread yet? Might be something to play around with till the issue gets fixed.
Click to expand...
Click to collapse
Thank you for trying to help me. actually i have try to set my phone in airplane mode to test if the problem because operator/service provider , but the problem still the same. it's not freeze because i still can fell it vibrate when i touch the screen only the display not show up.
about gingerbread. i have read that gingerbread is android 2.3 and froyo is 2.2 right? but why many people like to use froyo then gingerbread? if gingerbread have any problem. sorry if i asking to many question.

I'm not 100% on this but I think it has something to do with the fact that the porting is still in alpha phase for our devices. If anything, this can be looked at as good or bad. Good, that we have gotten this far and it seems our devices are pretty much stable. Bad, that this might be as good as it gets for a while. You have to weight the options of a faster port(in terms of stability) but less complete(in terms of functionality) or a more complete port but not quite as fast. I remember when we first got FroYo, it seemed like a complete mess. It took till the third release (FRX03) for stability to take place(noticable) because the devs were trying to figure out what caused the instability. When it's all said and done, the end user experience is all that most are looking for. When this is the case, it's difficult to say what should be done. Wait till it becomes more stable or try to come up with work arounds. Troubleshooting can get you so far until you require more understanding of what affects what. Hopefully, I have bored you out of your mind and that this makes things clearer as to what you can do to help!

thank you for your kind to help me. i have change to gingerbread but it have same problem like froyo. then i tried to hard reset then reinstall froyo and change the kernel. now it working great without problem except camera not working . maybe because i change the kernel htc-msm-linux-20110214_200559-package.tar . but it's ok for me. i will wait till new release.

You must have the similar issues some others have (on foreign carriers/other than USA based) Now, I'm not saying this is the problem just that others that have a similar issue, are on those carriers. There have been updated kernel packages that include the camera fix but I would suggest a little more reading into what you need to do, to ensure that you aren't causing the issue you are experiencing now.

MetaMorph not seeing BB

I installed Busy Box a few days ago,and works great... then i installed MM about an hour ago,but whenever i launch MM it does it's "check" and says it doesn't see or detect BB... why would it be doing so?
[update] FIXED

What did you do to fix it?

I stressed out over this too, my solution was just restarting the darn metamorph app and everything worked just fine.

Thanks I just wanted some constructive advice or tips on how to fix this since the issue has been reported and the community has been asked for help; yet the answer was found and totally disregarded to make any note of it for anyone else who may have any other similar issues and come looking for a solution.

rubbachicken said:
Thanks I just wanted some constructive advice or tips on how to fix this since the issue has been reported and the community has been asked for help; yet the answer was found and totally disregarded to make any note of it for anyone else who may have any other similar issues and come looking for a solution.
Click to expand...
Click to collapse
sorry about that... i wasn't getting notifications to my thread like i was suppose to.
i just reinstalled it (BB) and it recognized it,must have had a bad instal or a wonky APK... but all is fine now.

Auto rotation problem in custom ics rom

Hi guys
Last night I installed the fallout rom on my desire s and it's all done.
I'm facing a problem, that is even when I disable auto-rotate from display settings, it still keeps rotating the phone. (In settings menu, and everywhere else unless I disable auto rotate in some app but most don't even have the auto rotate setting and follow the default settings, which is set to disable but is still on for some reason)
Basically I want to disable auto rotate permanently. I do not ever need it.
Any idea how to do this? There must be a way. This is really a deal breaker for me for this rom and it's the first custom rom i've installed on my phone.

This bug is known about Fallout. There is no fix.
You can try a newer Sense 4 ROM (like Nik Project X)

Googley35 said:
This bug is known about Fallout. There is no fix.
You can try a newer Sense 4 ROM (like Nik Project X)
Click to expand...
Click to collapse
I dont think there will be a fix because it it works!!!!!!!!!

flykthewiz said:
I dont think there will be a fix because it it works!!!!!!!!!
Click to expand...
Click to collapse
Not making a lot of sense there.
I understand ROM loyalty and am convinced that fallout is a great ROM and one which I want to stick with. However, your experience of never having had a certain problem does not mean that you can say it doesn't exist.

g-banjo said:
Not making a lot of sense there.
I understand ROM loyalty and am convinced that fallout is a great ROM and one which I want to stick with. However, your experience of never having had a certain problem does not mean that you can say it doesn't exist.
Click to expand...
Click to collapse
2 ppl are flashing the same rom, but only 1 is experiencing the problem, where do u think the problem lies.
Rom dev are not able to fix the problem if they are not experiencing it.

rain987 said:
2 ppl are flashing the same rom, but only 1 is experiencing the problem, where do u think the problem lies.
Rom dev are not able to fix the problem if they are not experiencing it.
Click to expand...
Click to collapse
You may have a point but it isn't valid in this case as the problem started two months after the installation.
Actually I lean to the feeling that this is not a problem with the ROM but I'm finding it interesting that I have now found several people mentioning this problem associated with this ROM - so I'm now seeking clarification, which is not really helped by apparently automatic denial that a problem exists by people who have no knowledge of it.

g-banjo said:
You may have a point but it isn't valid in this case as the problem started two months after the installation.
Actually I lean to the feeling that this is not a problem with the ROM but I'm finding it interesting that I have now found several people mentioning this problem associated with this ROM - so I'm now seeking clarification, which is not really helped by apparently automatic denial that a problem exists by people who have no knowledge of it.
Click to expand...
Click to collapse
My desire s with stock rom is experiencing some issue, i called htc up, tech told me to do a factory reset, hey that solve the problem, but wait, i dont think that should be the solution, ROLL OUT ANOTHER OTA!!!
Same case here, just do a fresh clean install, with backup apps and data. If after 2 months it happen again, then come back and report. Or you expecting fallout v6, which in my case i dont mind :victory: in xda new roms are always welcome.
The dev or someone with expertise needs to experience the issue for you to have clarification, if non are having u only get assumptions from people who are not knowledgeable enuf.

rain987 said:
My desire s with stock rom is experiencing some issue, i called htc up, tech told me to do a factory reset, hey that solve the problem, but wait, i dont think that should be the solution, ROLL OUT ANOTHER OTA!!!
Same case here, just do a fresh clean install, with backup apps and data. If after 2 months it happen again, then come back and report. Or you expecting fallout v6, which in my case i dont mind :victory: in xda new roms are always welcome.
The dev or someone with expertise needs to experience the issue for you to have clarification, if non are having u only get assumptions from people who are not knowledgeable enuf.
Click to expand...
Click to collapse
So following your advice I did a totally clean install and the problem was still with me - so I figured it was a problem with the phone. Just to be sure I installed a different ROM and the problem was gone. That suggests to me, regretably, that it is problem with this ROM. Why it should happen to some people and not others is a bit of a mystery.

I felt it was both arrogant and ignorant of me to give feedback with a diiferent Rom on my phone, so I decided to flash fallout before making a reply since I had the zip on my pc. Never like going back to older roms, always going for the newer ones.
And result is, rotation works. No issue here. On and it rotates, with the phone still tilted I off and it went back to vertical without me tilting it back.
Sad that this Rom is having issue with your phone.
SentDeDesiredS

rain987 said:
I felt it was both arrogant and ignorant of me to give feedback with a diiferent Rom on my phone, so I decided to flash fallout before making a reply since I had the zip on my pc. Never like going back to older roms, always going for the newer ones.
And result is, rotation works. No issue here. On and it rotates, with the phone still tilted I off and it went back to vertical without me tilting it back.
Sad that this Rom is having issue with your phone.
SentDeDesiredS
Click to expand...
Click to collapse
You're right, it is sad. I was perfectly happy with it otherwise.

[Q] mm qcamera issue

Good morning all,
I'm sure most of you are familiar with the "mm qcamera" bug. In a nutshell it is a service used by the camera that *sometimes* stays open on some nexus devices (and possibly any Android device) consuming large amounts of battery in the background. By large I mean 20% an hour sometimes more!
The bug was supposedly reported in android 4.4.2 and fixed in a later version of Android. (4.4.4? I'm not sure). I can confirm this still happens to my nexus 5 once in awhile.
Upon researching, it seems most threads are about the 4.4.2 software, however my Nexus is running 4.4.4 and is still experiencing the bug. It is hard to find anything to read on 4.4.4, most search results talk about older software.
My question is this: Is anyone experiencing this bug on their nexus 5 (or really any android device) running 4.4.4? Has anyone found a solution other than rebooting the device?
Here is some more information on the topic
https://code.google.com/p/android/issues/detail?id=70755

koszor said:
Good morning all,
I'm sure most of you are familiar with the "mm qcamera" bug. In a nutshell it is a service used by the camera that *sometimes* stays open on some nexus devices (and possibly any Android device) consuming large amounts of battery in the background. By large I mean 20% an hour sometimes more!
The bug was supposedly reported in android 4.4.2 and fixed in a later version of Android. (4.4.4? I'm not sure). I can confirm this still happens to my nexus 5 once in awhile.
Upon researching, it seems most threads are about the 4.4.2 software, however my Nexus is running 4.4.4 and is still experiencing the bug. It is hard to find anything to read on 4.4.4, most search results talk about older software.
My question is this: Is anyone experiencing this bug on their nexus 5 (or really any android device) running 4.4.4? Has anyone found a solution other than rebooting the device?
Here is some more information on the topic
https://code.google.com/p/android/issues/detail?id=70755
Click to expand...
Click to collapse
It only happens for some people and the reason behind it is unknown. For some it is a major issue, and for others it's never existed. Only way to get it to (maybe only temporarily) go away is to reboot. Not much you can do about it, but some have said it's better if camera apps are changed to user apps rather than leaving them as system apps.

Lethargy said:
It only happens for some people and the reason behind it is unknown. For some it is a major issue, and for others it's never existed. Only way to get it to (maybe only temporarily) go away is to reboot. Not much you can do about it, but some have said it's better if camera apps are changed to user apps rather than leaving them as system apps.
Click to expand...
Click to collapse
Interesting, do you think running a custom ROM or a different kernel will help... or hope and pray Android L fixes it?

koszor said:
Interesting, do you think running a custom ROM or a different kernel will help... or hope and pray Android L fixes it?
Click to expand...
Click to collapse
I doubt it, it might be a hardware driver issue, nobody knows what the real cause is. Personally I don't have this issue, I don't think another ROM or kernel will change anything much, although it's worth a shot if the drain applies to you.

It gives me a good reason to change ROMs.. haha. Ill give it some time and see what happens thanks for the quick reply so early in the morning!

koszor said:
It gives me a good reason to change ROMs.. haha. Ill give it some time and see what happens thanks for the quick reply so early in the morning!
Click to expand...
Click to collapse
Depends where you are in the world.. 10:46pm here in Australia. :angel:
But yeah, I have no idea if another ROM would fix the issue in any way. If it helps a little it's more likely because it's a clean flash, not because of the ROM itself, but who knows. Kernel won't affect this at all.

well, the camera daemon is normal to show up, especially when you use the camera or apps that use the camera. and its normal for it to take a larger % of battery than the camera app itself. what you havent really done is actually describe your problem. as far as i know, you dont have an issue, at least until you describe it. again, its normal for the camera daemon to appeae. now please, describe your actual problem. screenies?
---------- Post added at 11:25 AM ---------- Previous post was at 11:10 AM ----------
what's not normal is if it continues to drain battery, which i havent seen personally in a while, nor read any real complaints on it in a long time.

koszor said:
Good morning all,
I'm sure most of you are familiar with the "mm qcamera" bug. In a nutshell it is a service used by the camera that *sometimes* stays open on some nexus devices (and possibly any Android device) consuming large amounts of battery in the background. By large I mean 20% an hour sometimes more!
The bug was supposedly reported in android 4.4.2 and fixed in a later version of Android. (4.4.4? I'm not sure). I can confirm this still happens to my nexus 5 once in awhile.
Upon researching, it seems most threads are about the 4.4.2 software, however my Nexus is running 4.4.4 and is still experiencing the bug. It is hard to find anything to read on 4.4.4, most search results talk about older software.
My question is this: Is anyone experiencing this bug on their nexus 5 (or really any android device) running 4.4.4? Has anyone found a solution other than rebooting the device?
Here is some more information on the topic
https://code.google.com/p/android/issues/detail?id=70755
Click to expand...
Click to collapse
I've heard it only happens now when you leave the offending app that uses the camera (snapchat, skype, etc) running in the background. I can't confirm though as I've never had the issue even before the update.

simms22 said:
well, the camera daemon is normal to show up, especially when you use the camera or apps that use the camera. and its normal for it to take a larger % of battery than the camera app itself. what you havent really done is actually describe your problem. as far as i know, you dont have an issue, at least until you describe it. again, its normal for the camera daemon to appeae. now please, describe your actual problem. screenies?
---------- Post added at 11:25 AM ---------- Previous post was at 11:10 AM ----------
what's not normal is if it continues to drain battery, which i havent seen personally in a while, nor read any real complaints on it in a long time.
Click to expand...
Click to collapse
I can confirm I have the continual drain, unfortunately this was the other day and since then I have rebooted and charged my phone. I'm glad its only once in a while but from what I researched it should have been fixed in 4.4.4.
More info is available in the link I posted in the 1st post including screenshots and even links to XDA. The problem I have experienced a few times so far on 4.4.4 is identical to the link in OP.
bblzd said:
I've heard it only happens now when you leave the offending app that uses the camera (snapchat, skype, etc) running in the background. I can't confirm though as I've never had the issue even before the update.
Click to expand...
Click to collapse
Its gotta be snapchat, it used to lock up and soft boot my nexus 4 from a 'bug' or something like that ><
oh well, ill just have to keep an eye out for it.. I will try CM for a month or so and post my results back tho!

koszor said:
I can confirm I have the continual drain, unfortunately this was the other day and since then I have rebooted and charged my phone. I'm glad its only once in a while but from what I researched it should have been fixed in 4.4.4.
More info is available in the link I posted in the 1st post including screenshots and even links to XDA. The problem I have experienced a few times so far on 4.4.4 is identical to the link in OP.
Click to expand...
Click to collapse
do you have any apps that use the camera? and i mean any, there are many. if you used that app, and iy continued running in the background, the the camera daemon would also run in tbe background. if it is the old camera daemon issue that youre experiencing, then it would happen every time the camera is used, not occasionally. if its only once in a while, something else is causing your issue. i had the issue before, every single time i used the camera, not occasionally.