So, something weird has been happening of late with my phone. During normal use, it suddenly hangs for a few seconds and then crashes, BSoD! I thought that was only exclusive to Windows. It has happened over 4-5 times now(in time span of a week) and I'm getting concerned. It certainly isn't ROM/Kernel issue as I've changed from Omni to Slim to CM, with stock kernel or others. The only thing I haven't tried is reverting back to Sony's stock ROM (because installing drivers on Windows 8 is absolute pain in the ass).
Here are a couple of images. http://i.imgur.com/9VtrxHl.jpg; http://i.imgur.com/E24EC2f.jpg (Please ignore the smudge )
Does any of you have any suggestions or any idea what the problem could be about? H/w?
With which rom you is this happening? To me it happened to me while using carbon 4.4
Enviado desde mi C2105 usando XDA Premium HD app
It used to happen to me on CM11 every once in a while, but I've been on Omni for the past 3 weeks and I've never encountered any BSOD's here
Oh and I think you meant 'stock' rom not stoke lol
Stronger1101 said:
With which rom you is this happening? To me it happened to me while using carbon 4.4
Enviado desde mi C2105 usando XDA Premium HD app
Click to expand...
Click to collapse
Currently, CyanogenMod. Happened on Omni ROM too.
Joel16 said:
It used to happen to me on CM11 every once in a while, but I've been on Omni for the past 3 weeks and I've never encountered any BSOD's here
Oh and I think you meant 'stock' rom not stoke lol
Click to expand...
Click to collapse
I originally faced it on Omni, then switched to CM. Still facing it I'll do a full wipe and try. I haven't tried reverting back to Sony's stock ROM yet. And yeah, thanks for pointing out the typo.
Sent from a toaster using Tapatalk
AayushDhuria said:
Currently, CyanogenMod. Happened on Omni ROM too.
I originally faced it on Omni, then switched to CM. Still facing it I'll do a full wipe and try. I haven't tried reverting back to Sony's stock ROM yet. And yeah, thanks for pointing out the typo.
Sent from a toaster using Tapatalk
Click to expand...
Click to collapse
You can try flashing the stock firmware(I'd recommend the latest), then doing a clean install I believe that would fix it. Also you might wanna delete those bsod error dumps. They might eat up your storage, idk where they're located though :L
Sent from my Xperia L using XDA Free mobile app
Joel16 said:
You can try flashing the stock firmware(I'd recommend the latest), then doing a clean install I believe that would fix it. Also you might wanna delete those bsod error dumps. They might eat up your storage, idk where they're located though :L
Sent from my Xperia L using XDA Free mobile app
Click to expand...
Click to collapse
Tried finding them, they sure don't consume large memory or I'd have noticed. Yeah just downloading the stock ftf and figuring out xperia drivers on Windows 8.
Edit: Just saw that the crush dumb was indeed of considerable size. 1.05GB.
Its a common problem in kitkat based rom. can't avoid unless you move to stock
TakuyaZ said:
Its a common problem in kitkat based rom. can't avoid unless you move to stock
Click to expand...
Click to collapse
Thanks for telling me that! I actually hadn't faced it before and in last week I kept facing it again and again so thought it might be something to do with H/w, my friend who also has XL isn't facing it. I'll move to stock if it keeps happening.
AayushDhuria said:
Thanks for telling me that! I actually hadn't faced it before and in last week I kept facing it again and again so thought it might be something to do with H/w, my friend who also has XL isn't facing it. I'll move to stock if it keeps happening.
Click to expand...
Click to collapse
Its randomly appearing, according to my use, it seems that it bsod if its too laggy/ram too low/overload
TakuyaZ said:
Its randomly appearing, according to my use, it seems that it bsod if its too laggy/ram too low/overload
Click to expand...
Click to collapse
Yep, phone hangs or lags heavily before BSoD.
Sent from a toaster using Tapatalk
AayushDhuria said:
Currently, CyanogenMod. Happened on Omni ROM too.
I originally faced it on Omni, then switched to CM. Still facing it I'll do a full wipe and try. I haven't tried reverting back to Sony's stock ROM yet. And yeah, thanks for pointing out the typo.
Sent from a toaster using Tapatalk
Click to expand...
Click to collapse
Try liquidsmoth is a good rom
Joel16 said:
You can try flashing the stock firmware(I'd recommend the latest), then doing a clean install I believe that would fix it. Also you might wanna delete those bsod error dumps. They might eat up your storage, idk where they're located though :L
Sent from my Xperia L using XDA Free mobile app
Click to expand...
Click to collapse
In the External SD CARD, this BSoD problem happened to me as well at that time i was on CM11. I thought my phone got bricked but i was wrong, i pulled the battery out and then everything worked just fine and there were no issues Regarding BSoD after that, PS-I am still using CM11 Nightly Release!
I faced it when using CM Nightly, Never faced it again on Candy Kat give it a try.
Related
I flashed the latest official nightly for CM10 and sure it's pretty buggy, but the biggest thing to me that's really bothering me is the closing of the app or rebooting of my phone when I try to use the camera or video camera as well as apps related to them. Is there any current fix or should I just wait for an upcoming nightly?
Sent from my SCH-I535 using xda app-developers app
Fallen224 said:
I flashed the latest official nightly for CM10 and sure it's pretty buggy, but the biggest thing to me that's really bothering me is the closing of the app or rebooting of my phone when I try to use the camera or video camera as well as apps related to them. Is there any current fix or should I just wait for an upcoming nightly?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I have had no problems with the camera, or anything for that matter! did you do a clean install?
jfhanny said:
I have had no problems with the camera, or anything for that matter! did you do a clean install?
Click to expand...
Click to collapse
I came from stock! The only thing I didn't do is flash back to completely stock-right out of factory. But I had no other ROM's or anything!
Fallen224 said:
I came from stock! The only thing I didn't do is flash back to completely stock-right out of factory. But I had no other ROM's or anything!
Click to expand...
Click to collapse
Clean install means wiping data/cache/dalvik.
Well then I did that!
Sent from my SCH-I535 using xda app-developers app
I would try reflashing, or getting a slightly older nightly just to check. I haven't had any problem with the camera on CM10 for quite a few builds now.
Yeah, sorry dude, mine works fine too . Had it happen one time on the last build but its worked fine since then.
Rumor has it.....some people got a bad batch of gapps with gallery issues. Make sure you're on 7/26 gapps. Also some have said that wiping cache/data for gallery actually cleared the problem up too. Its pretty random the people with camera issues, but its definately a common thing still. See the cm10 official thread and there are a LOT of ideas about it floating around.
Did you restore anything strange with TiBackup or anything? It's a long shot, but I noticed after accidentally restoring a "system app" from GB to JB, it caused me some problems (wasn't a GSIII phone though). I wiped & reflashed ROM to fix my issues, but it sounds like you've done that well enough.
Does your camera not work immediately after flashing CM10?
Fallen224 said:
I flashed the latest official nightly for CM10 and sure it's pretty buggy, but the biggest thing to me that's really bothering me is the closing of the app or rebooting of my phone when I try to use the camera or video camera as well as apps related to them. Is there any current fix or should I just wait for an upcoming nightly?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
First thing I would do is a permissions repair. fixing permissions can iron out all kinds of little issues.
You can do it through rom manager but I've never trusted it to do much properly so I always do permissions repair through recovery.
So, I already had the latest version of Gapps, I fixed the permissions, cleared the data/cache of the gallery, and flashed the latest nightly "8/22" yet it still isn't working. It's a pity having such a great ROM with such a potentially large drawback. I'm very much still open to more suggestions! I have nowhere near the Linux literacy of a developer, but push me to try something out of the ordinary and I can figure it out with not too much help!
Sorry if this has been posted somewhere else, but after flashing AOKP Build 3 my camera keeps giving me the error "cannot connect to camera." I have tried clearing data on the gallery app, rebooting the phone, and nothing works.
I researched some and tried some fixes I found but none had any effect.
I then reflashed to stock to see if stock Touchwiz would work and it works with no issues. Wiped all data, reformatted my SD card, removed my SD card and cannot seem to find the culprit. I also flashed CM nightly to see if it was an AOKP issue with my phone, but had same issue
For whatever reason I cannot flash any AOSP rom without having FC on my camera. Any help would be appreciated. Again, sorry if it has been posted somewhere I haven't found, but I've looked for a few days and didn't locate anything that worked.
Did you try fixing permissions?
Zalithian said:
Did you try fixing permissions?
Click to expand...
Click to collapse
Do that and also format cache and dalvik.
shinjielric said:
Do that and also format cache and dalvik.
Click to expand...
Click to collapse
Did all of those and still no change in outcome.
MistarJones said:
Did all of those and still no change in outcome.
Click to expand...
Click to collapse
What version of CWM are you using? I've heard some versions don't play nice with AOSP.
EDIT: I'm assuming you're using CWM.
You happen to try a different camera from the play store? My quess is it wouldnt work either as its probaly a kernel issue?
Sent from my SCH-I535 using xda app-developers app
shinjielric said:
What version of CWM are you using? I've heard some versions don't play nice with AOSP.
EDIT: I'm assuming you're using CWM.
Click to expand...
Click to collapse
I am using las test, CWM touch. Could try with non touch after work.
x714x said:
You happen to try a different camera from the play store? My quess is it wouldnt work either as its probaly a kernel issue?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Yeah I tried with several camera alternatives and all said couldn't connect to camera as well. :/
this happened to me randomly yesterday on CM10 M1, I'm on leankernal and using twrp. I had just flashed the aosp camera mod earlier so I thought it was that. I just restored a backup I made the other day and it was all good since. I guess its a good reason to make routine backups on aosp
DertyDOH said:
this happened to me randomly yesterday on CM10 M1, I'm on leankernal and using twrp. I had just flashed the aosp camera mod earlier so I thought it was that. I just restored a backup I made the other day and it was all good since. I guess its a good reason to make routine backups on aosp
Click to expand...
Click to collapse
I tried that and any backup still having camera FC issues.
Originally Posted by shinjielric
What version of CWM are you using? I've heard some versions don't play nice with AOSP.
EDIT: I'm assuming you're using CWM.
Click to expand...
Click to collapse
I am using las test, CWM touch. Could try with non touch after work.
Click to expand...
Click to collapse
I'm using cwm touch v6.0.1.2 and its working good for me.
Sent from my SCH-I535 using xda premium
I've had the same issue and reflashed multiple times and tried all the above.
My Galaxy III SCH-I535 operates on Android 4.1.2 aokp_d2vzw_jb_milestone_1
Kernel is 3.0.48-cynagenmod-faux123-vzw...
I love this ROM. I'm not sure how it randomly a day or two into operation just quit the camera operation completely. This would be a real miracle solved
MistarJones said:
Sorry if this has been posted somewhere else, but after flashing AOKP Build 3 my camera keeps giving me the error "cannot connect to camera." I have tried clearing data on the gallery app, rebooting the phone, and nothing works.
I researched some and tried some fixes I found but none had any effect.
I then reflashed to stock to see if stock Touchwiz would work and it works with no issues. Wiped all data, reformatted my SD card, removed my SD card and cannot seem to find the culprit. I also flashed CM nightly to see if it was an AOKP issue with my phone, but had same issue
For whatever reason I cannot flash any AOSP rom without having FC on my camera. Any help would be appreciated. Again, sorry if it has been posted somewhere I haven't found, but I've looked for a few days and didn't locate anything that worked.
Click to expand...
Click to collapse
Did you ever get this resolved? I'm having the exact same issue and would love to get it fixed.
re fix
bandit2443 said:
Did you ever get this resolved? I'm having the exact same issue and would love to get it fixed.
Click to expand...
Click to collapse
I wasn't able to get it to fix. I came to the conclusion that it was a hardware issue. For whatever reason it works on touchwiz but wouldn't work on aosp ROMs. I got a warranty replacement and it solved the issue. Wasn't able to find a software fix.
MistarJones said:
I wasn't able to get it to fix. I came to the conclusion that it was a hardware issue. For whatever reason it works on touchwiz but wouldn't work on aosp ROMs. I got a warranty replacement and it solved the issue. Wasn't able to find a software fix.
Click to expand...
Click to collapse
Oh wow... that's an idea i hadn't thought of. Samsung replaced it under warranty? What did you tell them was wrong with it?
Camera Can't Connect & Firmware
shinjielric said:
I'm using cwm touch v6.0.1.2 and its working good for me.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I am having the "cannot connect" issue on CM10. I posted about it here: http://forum.xda-developers.com/showthread.php?t=2152348
The camera works fine in stock, but on CM10 no-go. According to this post its a firmware issue: http://forum.xda-developers.com/showthread.php?t=2006128
only problem is to fix I need to figure out what camera firmware I have so I can flash a new one - but I cannot determine what firmware i535 has? Anyone?
Based on another thread, seems like I might be able to copy the bins from the cameradata folder on stock where the camera works. No need to flash or anything.
http://forum.cyanogenmod.org/index.php?/topic/66022-Can't-Connect-To-Camera
Sent from my SCH-I535 using xda app-developers app
I was hoping anyone here could relate to the problem my brother and I are having with pretty much all AOSP ROMs. Every time we install an AOSP ROM after even completely wiping everything except ext SD, after about an hour of run time to smoothness of the ROM goes away. The pull down is all choppy as well as scrolling the home screens. A reboot fixes it temporarily for around a minute or so and it goes back. We did find one AOSP nightly from the 15th that remained smooth but that was it.
If anyone has any ideas what could be causing this I would be eternally thankful. We have searched up and down and can't believe no one else is complaining of this. This is happening on both of our devices where pretty much the only similarity is that we use TWRP and update it regularly.
Thanks again for any advice you can provide.
Sent from my SCH-I535 using xda premium
I've had this same exact problem. I believe you meant the AOKP build from the 15th as that was the one that has remained smooth (but had some other bugs) for me. Seems like nobody else is having this problem.
Sent from my SCH-I535 using xda premium
Gordon Ramsay said:
I was hoping anyone here could relate to the problem my brother and I are having with pretty much all AOSP ROMs. Every time we install an AOSP ROM after even completely wiping everything except ext SD, after about an hour of run time to smoothness of the ROM goes away. The pull down is all choppy as well as scrolling the home screens. A reboot fixes it temporarily for around a minute or so and it goes back. We did find one AOSP nightly from the 15th that remained smooth but that was it.
If anyone has any ideas what could be causing this I would be eternally thankful. We have searched up and down and can't believe no one else is complaining of this. This is happening on both of our devices where pretty much the only similarity is that we use TWRP and update it regularly.
Thanks again for any advice you can provide.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
The reason people aren't complaining is because they haven't had that problem yet. The only thing I can tell you is when flashing ROMs make sure you completely wipe 2-3 times as for some reason with TWRP you have to do that to get some ROMs to work.
jmxc23 said:
The reason people aren't complaining is because they haven't had that problem yet.
Click to expand...
Click to collapse
Thank you for the wonderful insight. But in all seriousness I wonder what is causing it for us.
Sent from my SCH-I535 using xda premium
voltage526 said:
Thank you for the wonderful insight. But in all seriousness I wonder what is causing it for us.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
please read my edited post. I will also add that when flashing ROMs the results are very random even with the most stable of ROMs.
jmxc23 said:
please read my edited post.
Click to expand...
Click to collapse
Thank you. I wipe everything 2-3 times by habit though.
Sent from my SCH-I535 using xda premium
voltage526 said:
Thank you. I wipe everything 2-3 times by habit though.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Yes I wipe 3x and then use zips that wipe again.
then you guys might have to switch CWM recovery as I flashed most of the AOSP ROMs with no problems.
jmxc23 said:
then you guys might have to switch CWM recovery as I flashed most of the AOSP ROMs with no problems.
Click to expand...
Click to collapse
You really don't have any stuttering whatsoever with AOSP roms? Hmm.
I would think though if it was TWRP wouldn't a lot more people be having this problem? I will try CWM though.
Just wanted to update the thread. We have tried switching recoveries to CWM, also tried running the rom with absolutely nothing but Gapps. Same result after a few hours. This is on two completely separate devices, we can't be the only ones. Any additional advice would be really appreciated. This is driving us crazy!
I get pretty bad lag on carbon rom, flashing with CWM. Any other aosp rom runs fine but carbon seems to not like my phone
Sent from my SCH-I535 using xda premium
Carbon was the worst so far for me as well.
That goes with the fact not everyone will have the same results when flashing ROMs.
Hi guys =)
After I unlocked bootloader and flashed a custom Kernel, my phone started freezing and sometimes it gets stuck on a bootloop. I've flashed two custom Kernels and the stock one, but nothing seems to help My phone freezing happens frequently. And I can notice some glitches when listening to music or using Chrome. Sometimes I'm doing nothing and it freezes. After a couple of minutes frozen I can use it again.
Do you have any idea on how to fix it? It's quite annoying if I must say.
Latest firmware btw. Rooted.
igohenrique said:
Hi guys =)
After I unlocked bootloader and flashed a custom Kernel, my phone started freezing and sometimes it gets stuck on a bootloop. I've flashed two custom Kernels and the stock one, but nothing seems to help My phone freezing happens frequently. And I can notice some glitches when listening to music or using Chrome. Sometimes I'm doing nothing and it freezes. After a couple of minutes frozen I can use it again.
Do you have any idea on how to fix it? It's quite annoying if I must say.
Latest firmware btw. Rooted.
Click to expand...
Click to collapse
If you're using Phantom Kernel, may I suggest you to try version 4.5 like @faizalotai said to me on this. When I was using latest version, my phone freezes every time, but the downgrade solved the problem. You can get the v4.5 from attachments
It's exactly the lastest version I have flashed on my phone. I'll give it a shot. Thanks =D
You can try to use thunder zap kernel too.
Sent from my C2105 using xda app-developers app
srcharged said:
You can try to use thunder zap kernel too.
Sent from my C2105 using xda app-developers app
Click to expand...
Click to collapse
I've never used TZ, 'cause I read in other posts that it mess up a bit the modules and kernel files, besides phone's heat up a lot and for some users they can only change kernel after a fresh FTF flash. Is this true?
NO!!
DsvCdsSoftware said:
I've never used TZ, 'cause I read in other posts that it mess up a bit the modules and kernel files, besides phone's heat up a lot and for some users they can only change kernel after a fresh FTF flash. Is this true?
Click to expand...
Click to collapse
Most certainly no! cos i have flashed phantom and back to TZ and then again to phantom and so on loads of times..
i never had any problems. And everything is working crisply for me. No heating issues, nothing..
Im on CM11. Using TZ 4.1 r-2
I'm using. 14 firmware yet, cause I need Bluetooth in my work, but this issues I told you are in 4.2.2, but I'm thinking in giving a chance to TZ
Sent from my C2104 using XDA Premium 4 mobile app
Sure!
DsvCdsSoftware said:
I'm using. 14 firmware yet, cause I need Bluetooth in my work, but this issues I told you are in 4.2.2, but I'm thinking in giving a chance to TZ
Sent from my C2104 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Just give it a try and let me know. Use the Voltage table given by him. And soon we will have bluetooth on our devices. Its all set already!
Thanks, @DsvCdsSoftware It worked! No more phone freezing! I also flashed PurePerformances™X, it's just perfect =)
I'm wondering if anyone can take a look at the logcat and see what could be the problem with bbm. Been crashing once a day I'm the the latest version of Optipop with PA gaaps (nano), code blue kernel, and data and cache is f2fs. pastebin.com/TRVqj72w please and thanks
If you know what the first B stands for then you already know why you have problems
Sent from my Nexus 5 using Tapatalk (the older 4.9.5 not that new 4.10 abomination they released for god knows why reason)
Does it do it on stock?
Sent from my Nexus 5 using XDA Free mobile app
Haha. The first B could be Ben [emoji14]
MrObvious said:
Does it do it on stock?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I haven't tried it on stock, but I'm under the impression Optipop is close enough to stock with a few extras included.
Basche said:
I haven't tried it on stock, but I'm under the impression Optipop is close enough to stock with a few extras included.
Click to expand...
Click to collapse
Well try it first. You could try multirom or nandroid your current ROM.
Sent from my Nexus 5 using XDA Free mobile app
MrObvious said:
Well try it first. You could try multirom or nandroid your current ROM.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Would I be able to run stock on secondary? And I have data and cache partions in f2fs, does that matter for Multirom?? And can i run stock with f2fs partions as mentioned?? Thanks
BBM sucks it drains battery like crazy, remains active all the time for no reason, and that notification is plain annoying, but, maybe check by greenify
Basche said:
Would I be able to run stock on secondary? And I have data and cache partions in f2fs, does that matter for Multirom?? And can i run stock with f2fs partions as mentioned?? Thanks
Click to expand...
Click to collapse
IDK, it was just a suggestion to quickly see. If you have F2FS it may not happen.
I used BBM everyday on my N5 since it was released and never had a single issue, it never crashed or froze on me. I am using it now on my Moto X and it is working the same way, only problem I have now is that Moto display will not show a BBM notification on my lock screen like it does for everything else.
Alxhn said:
BBM sucks it drains battery like crazy, remains active all the time for no reason, and that notification is plain annoying, but, maybe check by greenify
Click to expand...
Click to collapse
It seems fine by me. Doesn't notice the battery drain that much But then I would have to try without it to see how much it will improve.
It could be the memory leak issue affecting random apps. I haven't found anything yet to confirm this, but I have been restarting my phone about once and day and will keep trying to see if that helps. Otherwise, thanks for the suggestions and help