Related
I've been experiencing this problem ever since I've had the phone. More often than not, accessing the Gallery will cause the system to freeze and I have to take out the battery to reboot. I applied the OCLF and it seemed to help for a little while, now this phone is back to it's old tricks. Has anyone else experienced this? Is there something I can do to fix it? I'm running stock btw.
I personally have not seen anyone else post that issue. I had an issue before when pics would not show because Media Scanner was not running... the roms I am on lately seem to resolve that though (back then when I had the issue I used an app in the market to scan my media and then the pics would show).
You say stock, do you mean stock JI6... as in you have done nothing to the phone?
Maybe not an option, but why not try a custom rom and see if that fixes the issue... if it does not, unroot and tell Samsung what's wrong and get a replacement.
I usually hate when people mention getting replacements, but you sound like you have a legit problem and not trying to work the system.
digitaltoddy said:
I've been experiencing this problem ever since I've had the phone. More often than not, accessing the Gallery will cause the system to freeze and I have to take out the battery to reboot. I applied the OCLF and it seemed to help for a little while, now this phone is back to it's old tricks. Has anyone else experienced this? Is there something I can do to fix it? I'm running stock btw.
Click to expand...
Click to collapse
yes, this is a common issue on stock 2.1.1 firmware right now, happened to me constantly, when it does this someone told me that when you open gallery, theres a memory leak bug which opens and then phone can't handle so it freezes.
Flash a custom ROM, i use axura 2.1, so far its been the fastest, most stable for me.
idk if this will work but ask for a gallery.apk from different roms where the leak has been fixed, and then try that, or just flash a new rOM.
digitaltoddy said:
I've been experiencing this problem ever since I've had the phone. More often than not, accessing the Gallery will cause the system to freeze and I have to take out the battery to reboot. I applied the OCLF and it seemed to help for a little while, now this phone is back to it's old tricks. Has anyone else experienced this? Is there something I can do to fix it? I'm running stock btw.
Click to expand...
Click to collapse
i had this problem when i just wantes to use stock with root. this is actually common problem with ji6 roms that still use the stock gallery apk.for some reason the stock gallery in ji6 always tends to lock up.there's a fixed version of the apk floating around somewhere.
I had this same problem with JI6, but it went away when I updated to the leaked JK6. This or any recent custom rom should fix the problem for you.
Sent from my SGH-T959 using XDA App
As i said its a memory leak bug, which has been fixed, you should either get a different gallery.apk from newer roms, or get a new rom.
I suggest a newer rom, but its up to you.
If you are running JI6, then this is a common problem for many people.
i had the same problem with my first and second vibrant, i updated to jk6 on number 2 and it went away.
can anyone post the apk to fix this????
Also interested in a the new Gallery .apk.... probably would have to push it using adb? I'm probably just gonna jump right on JL5 tonight.
Oh my goodness, a new thread, I hate doing this but I haven't had any luck...
So here's the deal, my Streak's camera only shows greyscale on the screen while I am taking pictures or shooting video....
Once taken, the color is there in the photo or pic in the gallery or whatever app I open to view the photo or watch the video.
Honestly I have no idea when this could've started because since the Streak's camera is not the best in the world, I don't use it much, but I do occasionally use it to recognize a business or scan a document to send it to someone or something else to that effect.
What I have done lately to the phone is flashed the 354 baseband and dsp1 files to the phone. So logically I tried to flash to where I was before that, the 351 files, and had no luck with that, so I went back to the 354 files.
I have tried to look for some setting that I may have left in black and white or greyscale but haven't found anything that I may have done to cause this, doesn't mean it's not my fault, but I could definitely do with some ideas.
Thanks guys for any suggestions.
Worst case scenario I'd do a fresh flash of StreakDroid....oops, forgot to mention I was running StreakDroid 1.9
I would try to get the camera.apk file from 1.9.0 (unzip the zip, then system, then app, then camera.apk (I think)) and try installing that after uninstalling your camera app. If that doesn't work then it's a little far out to fix. You can always try a factory reset and reflash if that doesn't work.
Sent from my Dell Streak using XDA Premium App
Well I tried got rid of the camera apk with Root Explorer but then it wouldn't let me reinstall it.
Well then I try to adb push the app but then got uid errors so I said the heck with it and did a fresh flash of StreakDroid
cdzo72 said:
... so I said the heck with it and did a fresh flash of StreakDroid
Click to expand...
Click to collapse
Did this fix the problem?
I just noticed this for the first time, myself. I did a factory reset/re-flash of 1.9.0 a few days ago, and I suspect that's when this started.
netonyx said:
Did this fix the problem?
I just noticed this for the first time, myself. I did a factory reset/re-flash of 1.9.0 a few days ago, and I suspect that's when this started.
Click to expand...
Click to collapse
Yeah, I dunno what I may have done to prompt the behavior, I'm sure I made some adjustment or installed something that affected it.
So I just started from scratch and flashed StreakDroid anew....
Each time I flash I do somethin in the order of things different and each time it gets smoother and smoother
cdzo72 said:
Yeah, I dunno what I may have done to prompt the behavior, I'm sure I made some adjustment or installed something that affected it.
So I just started from scratch and flashed StreakDroid anew....
Each time I flash I do somethin in the order of things different and each time it gets smoother and smoother
Click to expand...
Click to collapse
I ran into this problem as well as another person. They discovered that it was LBE. Once I uninstalled LBE, the color issues were fine.
Did you have LBE installed?
sgood1971 said:
I ran into this problem as well as another person. They discovered that it was LBE. Once I uninstalled LBE, the color issues were fine.
Did you have LBE installed?
Click to expand...
Click to collapse
Well I don't have the problem now that I flashed StreakDroid again but I sure wanna know what LBE is... forgive me for being dense but for the life of me I can't make out what that stands for sgood
Not sure what it stands for but its an app I found on xda and does permissions based blocking of apps. Kind of like iptables
Some people were having the same issue at streak.modaco.com and some found LBE Privacy Guard to be the issue and one person said Chainfire3D may be an issue.
In the SimpleStreak rom thread some users were attributing this to having stagefright installed. I do not use stagefright and have no idea what it is, just passing on the observation.
Colonel Panic said:
Some people were having the same issue at streak.modaco.com and some found LBE Privacy Guard to be the issue and one person said Chainfire3D may be an issue.
Click to expand...
Click to collapse
Yep that's the one and removing it fixed my issues.
vThanks
Thankyou,
I found that a reboot fixed the problem but i also have chainfire 3D installed so I was wondering if that caused the problem as I dont use the camera very often
Hey, i have a similar issue and dont have either of those apps installed. I can across the thread below first and posted my question here:
[Q] camera and video playback in black and white.
I am a noob. Both threads appear to discuss the same issue. Should i post to this thread?
First off, I'm sorry if it seems like this has been answered before, but I did a good deal of searching and couldn't find anyone who had quite the same problem I do.
I've been using Agrabren's CM10 - Disarmed Toaster for CDMA since Friday. But I ran into a "storage running low" problem this morning (after I let my phone go dead last night and then put it on the charger overnight) which caused me to do a full wipe and re-flash with his latest version (0.2.2). Since then, I haven't been able to receive texts at all. I have Google Voice, and I was getting the texts there, but not in the actual messaging app. I have since tried disabling and re-enabling Google Voice to no avail, and it is currently disabled to remove extra variables. I haven't been very scientific about my troubleshooting process, which has mostly involved a lot of flailing around, wiping, and re-flashing. But I've re-installed the ROM countless times and twice now have flashed a Sense ROM (MeanROM 2.6) to update my PRL and Profile and then flashed back to CM10. I suddenly got a flood of all my texts when I flashed to Sense, but still don't get any texts after flashing back to CM10.
I tried Paranoid Android and AOKP variants and have the same problem. I even tried Team DIRT's CM10 Codename Android and texts still didn't come in. I should also mention that I had the same problem a while back with Disarmed Toaster 0.1.6, and it probably started the same way with running out of battery and then having the storage low issue and re-flashing. I never figured out exactly what the issue was, but I think at the time I was able to fix it by flashing a Sense ROM and updating profile and PRL.
Sorry for the long explanation. Let me know if there is any other info I can provide to help. I really didn't want to go back to MIUI, but that might be only option at this point.
Also, for reference:
HBOOT - 1.40, S-Off
Recovery - 4ext 1.0.0.5 RC5
THANKS
you might wanna try looking here.
http://forum.xda-developers.com/showthread.php?t=1818387
efan3719 said:
you might wanna try looking here.
http://forum.xda-developers.com/showthread.php?t=1818387
Click to expand...
Click to collapse
Thanks. I already asked there and I've been following the thread. I don't think anyone else has mentioned this problem.
Sent from my PG86100 using xda app-developers app
I think it's the 4g logs growing exponentially and filling the space. You need to periodically clear the logs.
coal686 said:
I think it's the 4g logs growing exponentially and filling the space. You need to periodically clear the logs.
Click to expand...
Click to collapse
Yeah, I think that's what caused the "Storage space running low" that started the whole thing. But the real issue is why I was no longer able to receive texts in any CM10 ROM since I re-flashed to "fix" the storage problem....
Thanks for the tip.
Anyway, it seems as though the problem has been resolved. So far I'm receiving texts okay - here's what I did:
1. Called Sprint while on CM10 Disarmed Toaster, they said provisioning looks okay, and the did a "refresh" on their end - didn't help anything
2. Flashed MIUI - received texts fine
3. Flashed CM10 again - still not working
4. Restored backup of MIUI - received texts fine, used for a little while
5. Flashed CM10 again - now able to receive texts
I think there's something going on behind the scenes that I am not aware of. Somehow it looks like restoring my backup and using it for a while fixed whatever the issue was.
It could be the apn xml file in the cm10 rom. The settings are probably not set correctly. Have you looked through the thread where you got the rom to see if anybody else was having the same problem? If not you could always address this issue to the dev. Ask him if you can provide a logcat to him on the thread or pm him the logcat.
Jsparta26 said:
It could be the apn xml file in the cm10 rom. The settings are probably not set correctly. Have you looked through the thread where you got the rom to see if anybody else was having the same problem? If not you could always address this issue to the dev. Ask him if you can provide a logcat to him on the thread or pm him the logcat.
Click to expand...
Click to collapse
That's an interesting thought, but it doesn't seem to explain why no one else is having the same problem, or why it worked at one time, and then didn't work after I re-flashed.I guess there could be something wrong with the flash process that was corrupting that file on my phone. But I was able to *send* sms without a problem, so I'm not sure.
As I mentioned before, I've been following the threads for the ROM and no one else has mentioned the same problem. I asked the question in the thread, but I didn't get an answer.
Anyway, as I mentioned above it's working now, so I wouldn't be able to provide a logcat unfortunately. For anyone else with the problem, I guess the only suggestion I can give it to make sure you keep a backup of a working ROM handy if you're going to re-flash a lot.
I have had the same problem its agrabating get it
But it seems as the issue is inconsistent at best. I found out how to clear the 4g logs why are those logs even kept anymore?
The messaging this is the worst part I too use google voice
We need to find a better solution to this
mastadave99999 said:
I have had the same problem its agrabating get it
But it seems as the issue is inconsistent at best. I found out how to clear the 4g logs why are those logs even kept anymore?
The messaging this is the worst part I too use google voice
We need to find a better solution to this
Click to expand...
Click to collapse
Haha...
Just so you know, once you've cleared out the 4G logs, you can make that directory "immutable" so that the logs don't get created anymore. Just run this command in terminal emulator:
chattr +i /data/wimax/log
I'm obviously not an android developer, and I have no idea why the logs are still created. I also have no idea what caused the text message issue, but if you are currently not getting texts, I would suggest you restore a working backup and then re-flash Agrabren's ROM like I did.
SMS Help!!
soldierforchrist2 said:
Yeah, I think that's what caused the "Storage space running low" that started the whole thing. But the real issue is why I was no longer able to receive texts in any CM10 ROM since I re-flashed to "fix" the storage problem....
Thanks for the tip.
Anyway, it seems as though the problem has been resolved. So far I'm receiving texts okay - here's what I did:
1. Called Sprint while on CM10 Disarmed Toaster, they said provisioning looks okay, and the did a "refresh" on their end - didn't help anything
2. Flashed MIUI - received texts fine
3. Flashed CM10 again - still not working
4. Restored backup of MIUI - received texts fine, used for a little while
5. Flashed CM10 again - now able to receive texts
I think there's something going on behind the scenes that I am not aware of. Somehow it looks like restoring my backup and using it for a while fixed whatever the issue was.
Click to expand...
Click to collapse
Has anyone figured out why SMS stopped working? I am running AOKP JB ROM and I can send text messages but I am not receiving them. Thanks for your help.
Still not working
I've been having the same problem with the sms, it works if you re-flash something else a couple times then flash CM10 back on but sms will only work for so long. I would like to pick apart the problem and see if we cant find the source of the problem, it could be a temp file that CM10 has been saving that interferes with the sms, but that's just a guess. any help on this is greatly appreciated
Just wanted to say I too have encountered this. I have tried flashing unofficial aokp 3.5 and unofficial slimbean 1.1. Getting ready to flash an MIUI rom like mentioned above.
Some Experimenting....
I did a small experiment just now (to try and get incoming SMS working) because I had essentially experienced the EXACT same problem, except that it was with P.A.C.MAN v.23 instead. What I did was installed a stock-based rom (I used unSENSABLE), which obviously allowed all my SMS to come flooding in, and stayed on that rom for about a day. After that I made a nandroid backup (of unSENSABLE) in 4ext, wiped everything except sd (not using the superwipe, and including caches) and then restored the backup. After that I booted up, let it sit for a while, then restarted into recovery. Again I wiped everything without using the superwipe, and flashed P.A.C.MAN v.23.0.0 and then GAPPS and booted. After all that, SMS was working again. We'll see how long it lasts...
ok, for some reason, thought build.prop q's were relevant to the kernel...
anyway, I edited build.prop in /system with RootExplorer's text editor. changed the value for wifi.supplicant_scan_interval from 30 to 120. no extra lines or spaces, etc- just changed the number, saved, then rebooted. it took an obscene amount of time to boot up and the device stopped going into deep sleep after a short while. I installed better battery stats to see what was wrong and the app indicated mmc_delayed_work under kernel or partial wakelocks (i forget which). I restored the original build.prop and the device worked like normal.
Is this a bug or is ICS/JB different enough from GB that you have to go through alternate means to change build.prop (eg flashing an update script from CWM, or something similar)?
I've tried this twice already and gotten similar results and the method by which I edited the build.prop was exactly the same as I used to edit it on GB without issue.
another thread I checked out in the S II dev thread indicated that this is possible- editing build.prop (wifi scan at least, on top of a few others parameters)- w/o issue, so....yeah.
alljokingaside said:
ok, for some reason, thought build.prop q's were relevant to the kernel...
anyway, I edited build.prop in /system with RootExplorer's text editor. changed the value for wifi.supplicant_scan_interval from 30 to 120. no extra lines or spaces, etc- just changed the number, saved, then rebooted. it took an obscene amount of time to boot up and the device stopped going into deep sleep after a short while. I installed better battery stats to see what was wrong and the app indicated mmc_delayed_work under kernel or partial wakelocks (i forget which). I restored the original build.prop and the device worked like normal.
Is this a bug or is ICS/JB different enough from GB that you have to go through alternate means to change build.prop (eg flashing an update script from CWM, or something similar)?
I've tried this twice already and gotten similar results and the method by which I edited the build.prop was exactly the same as I used to edit it on GB without issue.
another thread I checked out in the S II dev thread indicated that this is possible- editing build.prop (wifi scan at least, on top of a few others parameters)- w/o issue, so....yeah.
Click to expand...
Click to collapse
I have no idea why that would happen, but I guarantee you the interval is fine where it is. I've left my player on with wi-fi over a week.
Mevordel said:
I have no idea why that would happen, but I guarantee you the interval is fine where it is. I've left my player on with wi-fi over a week.
Click to expand...
Click to collapse
I'm recording atm but problem isn't replicating. go figure; well, if it does, I'll post a logcat. if not, good for me since I forget to turn the wifi off most of the time and especially in places with no open wifi. anyway, I was posting this in case someone else did come across a similar problem and had a solution since my searches led nowhere (searching for anything mmc_delayed_work related comes up with little useful info/apparently a lot of once-valid GB tweaks are "busted"/not in ICS code base)
whether or not the scan interval isn't exactly the point, why I'm pursuing it; it's the specific point atm, but the general point is device ownership- tailoring your device to your heart's desire; complete ownership. that's the premise behind this whole site as I'm sure everyone here is aware. if I did something to mess it up along the way, great. but if it is a bug or something with ICS code base, it's be nice to know. a lot of folk like messing with build.prop so it'd be nice to know what can or cannot be messed with.
atm, it does look like I messed something up when editing and saving- perhaps I added a space or line where it shouldn't've been- since the device is sleeping as it should, again, if I find something, I'll post the logcat.
thanks for the re:
alljokingaside said:
I'm recording atm but problem isn't replicating. go figure; well, if it does, I'll post a logcat. if not, good for me since I forget to turn the wifi off most of the time and especially in places with no open wifi. anyway, I was posting this in case someone else did come across a similar problem and had a solution since my searches led nowhere (searching for anything mmc_delayed_work related comes up with little useful info/apparently a lot of once-valid GB tweaks are "busted"/not in ICS code base)
whether or not the scan interval isn't exactly the point, why I'm pursuing it; it's the specific point atm, but the general point is device ownership- tailoring your device to your heart's desire; complete ownership. that's the premise behind this whole site as I'm sure everyone here is aware. if I did something to mess it up along the way, great. but if it is a bug or something with ICS code base, it's be nice to know. a lot of folk like messing with build.prop so it'd be nice to know what can or cannot be messed with.
atm, it does look like I messed something up when editing and saving- perhaps I added a space or line where it shouldn't've been- since the device is sleeping as it should, again, if I find something, I'll post the logcat.
thanks for the re:
Click to expand...
Click to collapse
I understand.
Thinking about it, mmc_delayed_work seems like it's tryng to catch up the SDcard or something. Did you reboot cleanly? That may be the issue.
Mevordel said:
I understand.
Thinking about it, mmc_delayed_work seems like it's tryng to catch up the SDcard or something. Did you reboot cleanly? That may be the issue.
Click to expand...
Click to collapse
No clue. what do you mean by "reboot cleanly"? if by that you mean, did I reboot using the reboot option in the power menu, then yes. always.
After restoring a backup and re-editing build.prop, sleep worked like gamebusters. Except, bluetooth auto-toggled on ("bluetooth is turning on"). After rebooting, it was stuck on the boot animation screen for a few minutes. A reboot after that pretty much boot looped it. I restored my backup afterwards...
Looking in the logcat (after editing), I noticed a ton of errors and permission denials.... Since I don't have much expertise here, I can't say for sure that they're normal but they seem to be abnormal. Wayyy more than I remember seeing when I browsed through before on a "clean" boot. But again, with the lack of expertise (or any functional knowledge for that matter)
==
Now, after having restored the backup before making the edits and rebooting, it seems to be stuck in a bootloop....huh. ok, after rebooting it 2x, it finally seems to have booted up "normally." Both before restoring (w/ edits and BT error) and after restoring (w/o build.prop edits), it's taking a lot longer to boot up than it used to....guesstimating 3-4 minutes. When it boots up, I get/got: "process system isn't responding" (both before and after restores now) and something about alarm error.
I've attached logcats of both pre- and post-event, if you're curious. As to "solving" this,I'm just gonna re-flash the PA ROM and wipe caches to get rid of these problems. ergh. device meets my foot against the wall is next on the checklist.
thanks again. I'd like to say, Stay classy, San Diego, but we all know San Diego and its class
Hi everyone, Im a bit desperate right now, since Ive searched all the internet (or I tried) and all of xda, but couldnt find a solution to my problem. Also Im unsure what causes it (ROM, device, some app,...?), which is why Im posting in the general section. So on to my problem:
I have a Oneplus 6, with the most current official LOS release. Sometimes when I unlock my phone, some random app will start. I said semi-random, because its mostly Instagram or Authy, probably depending on which of the two I had opened most recently (actually sometimes both will open; I see Authy for a split-second and then instagram will appear and stay), but never (as far as I remember) other apps, even if I had antoher one open before it happens.
Now, I recently discovered that I can reproduce the behavior if I go to developer settings and change the display cutout setting to something different. It will reliably happen. So the screen goes black for a second, (probably re-drawing the UI) come back and Instagram will open. This led me to the idea that the UI crashes in a way. When it happens after unlocking the device, its always black for a second as well, while usually the screen is just there.
I only found evidence of the problem online regarding Samsung phones, mostly using Nova. Im using Nova as well, so that may be the cause. But I dont know for sure.
Does anyone know this problem? Why is it always one of those two apps, that appear? Can a log help me find the issue?
Things I already tried: factory resetting and setting up Nova from the ground.
Help very much appreciated
EDIT: I dug through the log file a bit and found something interesting (as far as I can say, Im far from an expert). I attached the relevant part, may be someone can tell me what happens?
diemadedrei said:
Hi everyone, Im a bit desperate right now, since Ive searched all the internet (or I tried) and all of xda, but couldnt find a solution to my problem. Also Im unsure what causes it (ROM, device, some app,...?), which is why Im posting in the general section. So on to my problem:
I have a Oneplus 6, with the most current official LOS release. Sometimes when I unlock my phone, some random app will start. I said semi-random, because its mostly Instagram or Authy, probably depending on which of the two I had opened most recently (actually sometimes both will open; I see Authy for a split-second and then instagram will appear and stay), but never (as far as I remember) other apps, even if I had antoher one open before it happens.
Now, I recently discovered that I can reproduce the behavior if I go to developer settings and change the display cutout setting to something different. It will reliably happen. So the screen goes black for a second, (probably re-drawing the UI) come back and Instagram will open. This led me to the idea that the UI crashes in a way. When it happens after unlocking the device, its always black for a second as well, while usually the screen is just there.
I only found evidence of the problem online regarding Samsung phones, mostly using Nova. Im using Nova as well, so that may be the cause. But I dont know for sure.
Does anyone know this problem? Why is it always one of those two apps, that appear? Can a log help me find the issue?
Things I already tried: factory resetting and setting up Nova from the ground.
Help very much appreciated
EDIT: I dug through the log file a bit and found something interesting (as far as I can say, Im far from an expert). I attached the relevant part, may be someone can tell me what happens?
Click to expand...
Click to collapse
Dude reflash your rom..
I'm also using nova no such problem
([emoji813]9/[emoji725]/9[emoji813])
PoochyX said:
Dude reflash your rom..
I'm also using nova no such problem
([emoji813]9/[emoji725]/9[emoji813])
Click to expand...
Click to collapse
did you even bother reading my post? I did that already. Multiple times
diemadedrei said:
did you even bother reading my post? I did that already. Multiple times
Click to expand...
Click to collapse
You said factory restore not reflash buddy use the appporiate wording you have a expensive phone you want to modify it and when issues happen you come here if you stood on stock with no modifications or custom rom you wouldn't have this issue I would suggest simply using an alternative launcher
([emoji813]9/[emoji725]/9[emoji813])
PoochyX said:
You said factory restore not reflash buddy use the appporiate wording you have a expensive phone you want to modify it and when issues happen you come here if you stood on stock with no modifications or custom rom you wouldn't have this issue I would suggest simply using an alternative launcher
([emoji813]9/[emoji725]/9[emoji813])
Click to expand...
Click to collapse
look, if you do not want to help me, thats perfectly fine, then please just dont post. I reflashed the ROM when factory resetting and flashed OOS in between.
If I wanted advice on which ROM or launcher to use, I would have asked for it.
diemadedrei said:
look, if you do not want to help me, thats perfectly fine, then please just dont post. I reflashed the ROM when factory resetting and flashed OOS in between.
If I wanted advice on which ROM or launcher to use, I would have asked for it.
Click to expand...
Click to collapse
Try reporting it as a bug