Related
My phone freezes at times when i open the image gallery.
Just to give more info on the freeze: The phone becomes unresponsive (but if i have music playing, it will continue), after some time, the phone seems to restart, but not in the traditional sense. Like the lock screen will comeback, it will say no service...until it finds service, it will scan the SD cards...but the touch screen will remain completely unresponsive. If i hold the power button, the power off, flight mode and silent mode context menu will appear but i can't do anything because the screen wont response to my touch. The only way i can get it working again is removing the battery, which is annoying.
Is anyone experiencing this issue with the image gallery?
Also, when i send an image to my friend (BB user) it takes like 20 hours before he receives it, this isnt an exaggeration. I sent an image at 3pm, he got it at 8am. This is an issue for me. The image size was less than 200kb.
Need more info, like what rom are you using?
Sent from my SAMSUNG-SGH-I897 using XDA App
cappysw10 said:
Need more info, like what rom are you using?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Im using the rogers stock rom. (Android 2.1), normally i would just use a different gallery, but honestly i really like the one the phone came with. The phone is rooted and i applied OCLF. Other than that, there are no major modifications.
I have the same problem, it used to just lag a little bit but just now it completely froze. I had to take out the battery to restart. Should we be worried?
Any help from experienced users would new wonderful! Thanks!
same problem, rogers stock 2.1
now that i know i am not the only one with this problem, i think there may be something wrong with the rogers rom itself, and not my phone.
About 10-20% of the time it will just fail to load the gallery and freeze on me forcing a hard restart
stavs said:
same problem, rogers stock 2.1
now that i know i am not the only one with this problem, i think there may be something wrong with the rogers rom itself, and not my phone.
About 10-20% of the time it will just fail to load the gallery and freeze on me forcing a hard restart
Click to expand...
Click to collapse
Yea this has been a huge problem for me and a real annoyance. Im just waiting until my exams are over so i can figure out how to get off stock rom and flash something we a working gallery. Its embarrassing when ur trying to show off ur phone and it freezes just by opening up the gallery
When I turn off my phone because the memory gets real low even when i auto kill my apps or my phone simply dies due to low battery, i turn it on but somehow it resends a bunch of txts to my friends that i was txting with. I was wondering if this happens to anyone else and if there is a way to fix it? Thanks in advance
Which rom are you using?
I get what I call ghost notifications of text messages kind of the same way. I'll look at the message which clears the notification bar. When I turn off my phone at night and then back on in the morning I sometimes get a notification of the message I have all ready looked at. I think this was a problem in the international 2.2 roms hence the update to 2.2.1.
Oh, I'm using Cognition 4.1.1 ..... for now.
I am using the stock one. I haven't messed with the phone at all.
Oh ok thanks, to me it only happens when i turn it off it resends txts that i previously sent. It's kind of annoying not a big deal but gets old after a while. Thanks
I never had this problem with all ROMs I flashed. Or possibly I never noticed that happening. But I have to say that sometimes I still get double notifications for messages I have received previously after rebooting. personally I don't know why. I've tried cognition, phoenix, serendipity and now on firefly.
Sent from my SAMSUNG-SGH-I897 using XDA App
droid_07 said:
When I turn off my phone because the memory gets real low even when i auto kill my apps or my phone simply dies due to low battery, i turn it on but somehow it resends a bunch of txts to my friends that i was txting with. I was wondering if this happens to anyone else and if there is a way to fix it? Thanks in advance
Click to expand...
Click to collapse
What do you mean by "I turn off my phone because the memory gets real low even when I auto kill my apps"? Are you checking how much ram is free and shutting your phone down because of that?
modest_mandroid said:
What do you mean by "I turn off my phone because the memory gets real low even when I auto kill my apps"? Are you checking how much ram is free and shutting your phone down because of that?
Click to expand...
Click to collapse
well when my phone gets to a certain point as far as RAM it will turn off on its own. kind of like it resets itself i guess or i will turn it off myself and turn it back on otherwise it will be really slow and that's when the resent text message thing happens.
droid_07 said:
well when my phone gets to a certain point as far as RAM it will turn off on its own. kind of like it resets itself i guess or i will turn it off myself and turn it back on otherwise it will be really slow and that's when the resent text message thing happens.
Click to expand...
Click to collapse
That doesn't sound right at all.. Android is supposed to try to fill up the ram with the most recently used apps for quick access, but still manages a pool of free ram to keep things running smoothly. It should never get to a point where it "runs out" or shuts itself down, or even causes the phone to 'run slow'.
If you're running the stock official KB1 rom, then it's probably some app you're running that launches a very poorly coded service in the background that is eating all of your resources. You can try using a program called "Watchtower" that will tell you how much memory and cpu cycles each program is using to debug your situation, or simply uninstalling suspect apps until the situation improves.
Also, what batch is your phone from? You can find the build number under the battery, it's a four digit number like 1007, 1008, etc. Some of the earlier batches have a random shutdown problem affecting them (hardware defect), and if yours falls into the range of affected phones, you can go to an ATT store and they'll replace it with a new one.
modest_mandroid said:
That doesn't sound right at all.. Android is supposed to try to fill up the ram with the most recently used apps for quick access, but still manages a pool of free ram to keep things running smoothly. It should never get to a point where it "runs out" or shuts itself down, or even causes the phone to 'run slow'.
If you're running the stock official KB1 rom, then it's probably some app you're running that launches a very poorly coded service in the background that is eating all of your resources. You can try using a program called "Watchtower" that will tell you how much memory and cpu cycles each program is using to debug your situation, or simply uninstalling suspect apps until the situation improves.
Also, what batch is your phone from? You can find the build number under the battery, it's a four digit number like 1007, 1008, etc. Some of the earlier batches have a random shutdown problem affecting them (hardware defect), and if yours falls into the range of affected phones, you can go to an ATT store and they'll replace it with a new one.
Click to expand...
Click to collapse
Let me try the watchtower app first and I'll see if that helps me find the issue.
My build number is 1012, do you know the range for the ones affected by it? Thanks for your help
droid_07 said:
Let me try the watchtower app first and I'll see if that helps me find the issue.
My build number is 1012, do you know the range for the ones affected by it? Thanks for your help
Click to expand...
Click to collapse
I don't know the specific range, but I remember hearing that if you bought your phone before Nov 2010, you were eligible for a replacement. I could be wrong though.. I think there's a thread about it in the general section.
I have an un-rooted Galaxy Note (1) GT-N7000B running the latest 4.0.4 ICS Android.
Going back at least to June when I got the first version of Ice Cream Sandwich (and maybe earlier) I began to notice that sometimes I find the GPS-tag feature of the camera has reverted to "off". I don't know why this is happening? It is not immediate; it is usually after a few weeks. Inevitably, it is discovered after I have taken some photos that I thought were being tagged, then come to find they were not because the GPS-tag feature has reverted to "off".
Any ideas as to what triggers this to happen?
Percy Dolarhyde said:
I have an un-rooted Galaxy Note (1) GT-N7000B running the latest 4.0.4 ICS Android.
Going back at least to June when I got the first version of Ice Cream Sandwich (and maybe earlier) I began to notice that sometimes I find the GPS-tag feature of the camera has reverted to "off". I don't know why this is happening? It is not immediate; it is usually after a few weeks. Inevitably, it is discovered after I have taken some photos that I thought were being tagged, then come to find they were not because the GPS-tag feature has reverted to "off".
Any ideas as to what triggers this to happen?
Click to expand...
Click to collapse
Turning GPS to off *may* turn off the geo-tag feature..just turn geo-tag on, then come back, turn off the gps & again go & check if the geo-tag is on or off..I may b wrong, but plz try it once..
Yes shyamub4u, you are correct. Toggling GPS off turns off the GPS-Tagging feature in the camera, while turning GPS back on does not return GPS-Tagging in the camera to it's previous ON state.
Thing is, I was never turning the GPS off in the first place. But I'm guessing on a few occasions when the battery got down pretty low it went into the Power Saving mode, which killed the GPS, which in turn killed the GPS-tagging feature in the camera.
I will play around with the settings a bit later when my battery is down lower than it is now, and confirm this is what's happening. If so, I can adjust custom power settings to avoid this from happening again in the future.
Thanks
Percy Dolarhyde said:
Yes shyamub4u, you are correct. Toggling GPS off turns off the GPS-Tagging feature in the camera, while turning GPS back on does not return GPS-Tagging in the camera to it's previous ON state.
Thing is, I was never turning the GPS off in the first place. But I'm guessing on a few occasions when the battery got down pretty low it went into the Power Saving mode, which killed the GPS, which in turn killed the GPS-tagging feature in the camera.
I will play around with the settings a bit later when my battery is down lower than it is now, and confirm this is what's happening. If so, I can adjust custom power settings to avoid this from happening again in the future.
Thanks
Click to expand...
Click to collapse
I think u r right..powersaving mode will turn of the gps once its <15%, if I am not wrong..once if u find this is the exact reason, plz let us knw
Last night I was at home and noticed my wifi wasn't on, so I used the quick settings in the shade to toggle it. After a few seconds, wifi connected, and some unknown app took focus and closed repeatedly. After a few moments, it stopped and all was well.
I thought it was strange, so I turned wifi back off and the same thing happened. I rebooted, tried again, and got the same result. I was trying to think of a way to see what was happening, so I tried using the Screen Record function in Gravity Box, which didn't help much, because it happens so fast, and no info is displayed, just a black window that goes away quickly.
I then turned on the CPU usage in Developer Options to see if anything consistently came to the top when toggling. I saw a few apps each time Plume (Twitter), and Maildroid (email) were two of them. Both of these apps behave differently on wifi and 3G/4G (push vs. pull), so thought -maybe- it could be something with that. I uninstalled both of those, rebooted and tried again, getting the same result.
I recorded the screen when this was happening with the CPU usage displayed, and was wondering if anyone has any ideas? I don't really want to uninstall and reinstall EVERY app on my phone, so I was hoping someone may have seen this before or see something I'm missing when watching it happen.
Video: https://copy.com/8L6VTsqcdbUjVTz
Thanks for any input anyone can offer!
Do you check virus from your phone ?
I am also having this, seems to be due to 4.4.2 OTA, which I continue to delay as I am rooted.
Mine doens't only happen with wifi change, but also just randomly when using hangouts, keyboard stays out but hangouts min -> maxes quickly. I have tried freezing the update apps but it apparently didn't do anything as I was still asked to update earlier.
Only hangouts? I have that app disabled.in the app settings.
I can't say for sure that being on 4.4.2 fixed it, but I am on 4.4.2 now and it is not happening anymore.
I unlocked my bootloader and did the 4.4.2 SBF, unlocked and rooted. I installed probably 99% of the same apps (only ditched 1-2 that I never used anymore) and I am not having the flashing issue anymore.
Hard to tell for certain if the pending OTA was the cause, but it may have been.
Hi all,
I'm running out of ideas and could use another opinion please:
N6 running 5.0.2 (this is the second one incidentally, I sent the first one back for this same problem) - the phone will shutdown under certain circumstances. When this happens it does not restart, you have to press the power button to restart it. Mostly this happens when I use the Google Camera stock application to take a photo but only ever when the phone is not connected to WiFi. I have had it happen when I open the camera app as well (without taking a picture), if you put your ear to the upper speaker as soon as the camera app is opened you can here a cell location signal (similar to the sound you hear when you put your phone near a speaker) and then the phone turns off. I can stop this happening by using a third party camera app. I can also stop this happening if I disable Google location.
Yesterday I wiped the phone, signed in with my Gmail, and took 25 pictures, all OK. I then turned on Google Now, took one photo and the phone turned off. This is definitely something to do with location data but I don't understand why nobody else is experiencing this ? Maybe the phone is faulty but I'm going to have a hard to explaining that as I sent the last one back for the same reason.
Any suggestions are greatly appreciated.
Thanks,
Simon.
Glad I'm not the only one having this issue. I've seen this happen on my N6 too, both on 5.0.x as well as on 5.1. I've seen this happen even while unlocking the phone (I have face unlock enabled), and yes this happens mostly when using the camera. Never knew it has to do something with location services.
I'm running completely stock and unrooted by the way. I guess I should try flashing the factory image
Yes same with me, stock phone unrooted and although using the camera is the best way to get this to happen you are right, it sometimes happens at other times as well. If I go to an area with no WiFi and poor phone signal I can get it to happen everytime the Google Camera app is opened, so I have to resort to taking pictures in Airplane mode.
This has happened to me since I have had this phone and its replacement and I am curious to know why, when you open the Google camera app, if you immediately put your ear to the upper speaker it becomes active for about 3 seconds ? After that three second burst of sound the phone will turn off. To me, it sounds like a location signal is being sent when the camera is opened.
Yet turning off geolocation?
Sent from my Nexus 6 using Xparent Skyblue Tapatalk 2
same thing happening here,i was out today and when i tried to open the camera app phone kept crashing,soon as i was home on wifi camera app worked fine,i've switched off the location thing to see if that helps