Related
Hi Guys
Samsung Captivate is my very first Smartphone and i always knew i was gonna get an android phone.
I bought this phone yesterday and i absolutely love it.
But i am facing some problems
1. the phone is a bit laggy.
2. the battery life doesnt seem very great.
3. The third one is very weird. I went to the android market to download apps. Once i select an app to download and install, there is no notification on the top area where it should show it. I mean it takes almost 10-15 minutes for that notification to show up and the phone is very unresponsive during these times. Also the music player crashed a couple of times.
Has anyone come across this problem. Please let me know!
Well , that was the first part..
I want to know the experiences of people who have already rooted the phone and installed Froyo on it. What are the noticeaable changes? Is there any improvement in battery life?
I am pretty sure i wanna root this phone and get rid of the ATT apps etc etc.
BTW i have attached a wallpaper which i hope u guys will like
Cheers
carporsche said:
Hi Guys
Samsung Captivate is my very first Smartphone and i always knew i was gonna get an android phone.
I bought this phone yesterday and i absolutely love it.
But i am facing some problems
1. the phone is a bit laggy.
2. the battery life doesnt seem very great.
3. The third one is very weird. I went to the android market to download apps. Once i select an app to download and install, there is no notification on the top area where it should show it. I mean it takes almost 10-15 minutes for that notification to show up and the phone is very unresponsive during these times. Also the music player crashed a couple of times.
Has anyone come across this problem. Please let me know!
Well , that was the first part..
I want to know the experiences of people who have already rooted the phone and installed Froyo on it. What are the noticeaable changes? Is there any improvement in battery life?
I am pretty sure i wanna root this phone and get rid of the ATT apps etc etc.
BTW i have attached a wallpaper which i hope u guys will like
Cheers
Click to expand...
Click to collapse
There is no Froyo for captivate , not yet anyway.
Root by itself doesn't fix anything , just lets you change system files and tinker around, more freedom so to speak.
Personally i am not having those problems, maybe you installed something that is eating up all resources, i have had similar problems on my Nexus one when i was downloading bunch of random programs and experimenting...
Try one of those app killers or restart phone maybe.
ghost77 said:
There is no Froyo for captivate , not yet anyway.
Root by itself doesn't fix anything , just lets you change system files and tinker around, more freedom so to speak.
Personally i am not having those problems, maybe you installed something that is eating up all resources, i have had similar problems on my Nexus one when i was downloading bunch of random programs and experimenting...
Try one of those app killers or restart phone maybe.
Click to expand...
Click to collapse
I factory reset my phone too , and i still have to install apps after resetting. Will keep you guys updated. BTW i thought rooting was to install froyo on the captivate.
I did not know tht it was just for the workarounds.
Hello guys
Please help me
I still am facing the same problem.
I have installed the AppBrain and fest web browser apps too, but somehow it still takes me a minimum of 10-15 mins before the download begins. And during that time the phone is very slow and unresponsive.
Is anyone else facing the same problem.
Please let me know!
------------------------
itzz(AN)dRoiD
I've noticed something similar to what you are talking about, but defiantly not to such extend. Marketplace seems to be slow on my phone, at least comparing to my brother's Evo. Sometimes just after I start download of a new app, the phone becomes unresponsive for a bit, but it doesn't freeze or anything, just I start noticing some lag, that's all. To your other concerns:
1. Remove Live Wallpaper and as many widgets from your screen as you can. After I did that, I don't have any lag at all. You can also use manual task killer application to shut down all of the AT&T crap that runs on background (and prevent them to start up again).
2. Coming from feature phone, battery live will always look bad on the Smartphone. For me, battery lasts the whole day, from 9AM till 12PM even with a heavy use. For a Smartphone, that's good results.
Only times I have had lag is when something is installing. Also when my network connection is bad and something is trying to pull data.
But then again i just switched from a Kaiser running WinMo to this phone, so I may just be use to lag by now
Sent from my SAMSUNG-SGH-I897 using XDA App
Can anyone shed some light on the issue I'm having? My nexus s after a while and I mean a while of sitting there not being used goes completely unresponsive to the point that I have to pull battery and reset! I've tried different Rom's and continue to experience same thing! It was working fine until a few days ago! I've wiped data and cache and davlik cache thru cwr and still have same problem. If anyone has had this issue and can point me in the right direction it would be greatly appreciated.
Sent from my Nexus S using XDA Premium App
Time to start looking at apps that might be running amok.
Maybe install a log collector and leave it running and autosaving, then review post-problems to see if anything stands out as crashing the system.
It's painful, but a Factory Reset might be your best recourse, then re-consider what apps, kernel and rom you're using and put back on a few at a time to isolate in groups what may or may not be causing issues.
distortedloop said:
time to start looking at apps that might be running amok.
Maybe install a log collector and leave it running and autosaving, then review post-problems to see if anything stands out as crashing the system.
It's painful, but a factory reset might be your best recourse, then re-consider what apps, kernel and rom you're using and put back on a few at a time to isolate in groups what may or may not be causing issues.
Click to expand...
Click to collapse
thank you for your quick response, i've tried factory rest to no avail, i quess i will start with the apps and slowly monitor them.
i'll go a little more drastic...
wipe the phone factory reset
then re-install apps that are known to be safe, and then monitor it
ALL GAMER in the process of doing that now, thanks for advice. Will report back findings! Fingers Crossed!
Extremely glad you posted this!
I have been having the exact same problem since the past 10 days, and it has gotten extremely frustrating. I use my phone as my main alarm, and I ended up going late to work a couple of days back because my phone had completely shut off. I performed a factory reset yesterday, and the same thing happened this morning. I leave my phone on and charging with the wall charger, so now I'm beginning to suspect if there's something wrong with the charger or the battery. I've registered a ticket with Samsung but i'm reluctant to send it in, because I've babied my phone and wouldn't like an misuse or scratches on it from being in the repair shop.
Please help! I love my Nexus S, and i'm running Stock 2.3.3 GRI40.
Hi, I have bad news for you guys.
there are already thread for this issue here:
http://forum.xda-developers.com/showthread.php?t=986181
And Google help forum here:
http://www.google.com/support/forum...ad?fid=44db6d8e31129d4c00049e3b2a6db4d1&hl=en
Please go to those and post comments as there are more and more of us with this problem. We've also got some sort of response from Samsung via Twitter - supposedly they are looking into this.
Also, flashing phone does not seems to help, but please go to those threads, its all there.
Just wanted to update on how my problem was going. I've tried everything you guys suggested but still experiencing the same thing. It's seems like it's a hardware issue from what I read from the previous posters post! I brought the best buy protection plan so they are sending me a new one! I think this is the only resort to anyone experiencing this issue. They gave me a loaner phone which is done lg piece of sh*t, man am I having withdrawals! I don't know if this issue was caused due to excessive flashing or not! I hope not cause that would definitely suck. I've only had the device for 3 months!
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.
Does anyone else have this problem? When I take video with my NS occasionally the recording ends up with out of sync audio and video, with the video pausing for a few seconds while the audio continues - the video then continues and finishes after the audio has finished. This happens when played but players both on my phone and on my pc. Any thoughts? The laggy video capture always seems to occur when I'm capturing moments with friends and family too and not when I try to reproduce the results haha...typical eh
Im facing the same problem too.
I m running on the stock rom, 2.3.4, rooted. I had this issue for twice & then i did a factory reset & hope it helps. But today when i record the video again, the same problem occurs again.
I don't know what to do. i googled abit & saw someone said clearing the camera app data would help, but seems.. it doesn't work for me.
anyone can help us? please?
Same issue since December. I have yet to find a good solution. It's a bummer as it does ruin what is otherwise acceptable video.
Sent from my Nexus S using XDA Premium App
Nice to know I'm not alone and that a developer is having the same issue as a relative noob like me! Any ideas what on earth could be causing it? It didn't do it when I was first using the phone, and now my phone storage is relatively full - perhaps lag in writing to the phones storage is causing it? Sorry for the late response, just it happened again last night to one of my videos and really irritates me!
...any solutions for this 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.