I can't find out why my Verizon Samsung galaxy s3 randomly crashes. It started a few days ago on version 410. I have tried flashing the 414 version which is supposed to fix a memory leak bug. But that hasn't helped at all. So I tried clearing cache and dalvik cache which seems to have helped temporarily but soon enough it started freezing again. I have recently flashed 327 version of cm which is when I first got cm, (this version never had issues when I had it) if anyone can help me trouble shoot this problem it would be greatly appreciated.
opening the default cm messaging app sometimes causes: "Loading conversations" which then is followed by my phone freezing. Also if it is related, I have enabled developer options but I can not open them. When I try to open dev options, my phone doesn't crash but my settings app goes unresponsive and I have to close it.
Oh and last night I downloaded a root checker because I couldnt find superuser. Apparently my phone wasn't rooted? I reinstalled superuser and it seems to be rerooted now. But I don't know what's happening with my phone. It wasn't rooted but was running cm? Anyway, it still crashes even after rerooting
tl;dr: d2vzw constant crashes on all versions of cm. Can't fix it. Need help
Maybe you need to look at this before attempting to fix your phone: http://forum.xda-developers.com/showthread.php?p=28390383
Sent from my GT-I9300 using xda app-developers app
Oomahey said:
Maybe you need to look at this before attempting to fix your phone: http://forum.xda-developers.com/showthread.php?p=28390383
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Good call. Didn't notice that. How can I move my post? Or does a moderator have to do it?
spartanlb said:
Good call. Didn't notice that. How can I move my post? Or does a moderator have to do it?
Click to expand...
Click to collapse
Red triangle top right of post and report it .
jje
JJEgan said:
Red triangle top right of post and report it .
jje
Click to expand...
Click to collapse
Thanks. Done
Hello guys. I am facing some terrible problem here. After I flashed the ROM I got some problems with the gamma maybe. In settings I see some color changes and etc. General in grey color. I see the problem looking at the screen even when I am in the closing process menu.. Cause it's still grey I think. I really hope it's from the ROM not from the tablet. Absolutely every other color don't make problems. Is it possible to have problem because of the gama and do you think it's because of the CyanogenMod 10.1 4.2.2 android. And if there is someone else with this problem please help. It's not so bad problem it's annoying and it makes me worry if it's possible to start getting bigger.
Sent from my GT-P3110 using xda app-developers app
ivanbelejkov said:
Hello guys. I am facing some terrible problem here. After I flashed the ROM I got some problems with the gamma maybe. In settings I see some color changes and etc. General in grey color. I see the problem looking at the screen even when I am in the closing process menu.. Cause it's still grey I think. I really hope it's from the ROM not from the tablet. Absolutely every other color don't make problems. Is it possible to have problem because of the gama and do you think it's because of the CyanogenMod 10.1 4.2.2 android. And if there is someone else with this problem please help. It's not so bad problem it's annoying and it makes me worry if it's possible to start getting bigger.
Sent from my GT-P3110 using xda app-developers app
Click to expand...
Click to collapse
Best option is to go to stock Rom and check if problem exist!!!
And if you are getting that grey effect only in settings it might be software problem.
Sent from my C1505 using xda app-developers app
Droidlover123 said:
Best option is to go to stock Rom and check if problem exist!!!
And if you are getting that grey effect only in settings it might be software problem.
Sent from my C1505 using xda app-developers app
Click to expand...
Click to collapse
Okay. I will try then, but not now. Anyway I don't like CyanogenMod 10.1 .. For example there is allways after reboot system massage '' This system cannot be enhanced'' Don't even know what is that doing. And sometimes my Open Process bar don't work. I will try going to stock ROM then if there is no problem i will try some more ROMs but i am worrying the battery life will die flashing ROM after ROM.
Thank you !
ivanbelejkov said:
there is allways after reboot system massage '' This system cannot be enhanced'' Don't even know what is that doing.
Click to expand...
Click to collapse
Well, consider that message a compliment -- your phone is so good that no other enhancements are possible! Sorry for the OT...
Update: This issue has been resolved in CyanogenMod 11. As of now, there is no 'official' CM 11 for the Samsung Galaxy Tab 2 (GT-P3100, GT-P3110, or GT-P3113), but CodyF86 has a great build of it here. Anyway, here is the commit: (http://review.cyanogenmod.org/#/c/56562/3)
Hey Guys,
Let me first start off by saying this problem in no way effects overall performance and operation of my device. With that being said, this problem is just more of a cosmetic issue with CyanogenMod and the OCD I have towards it. Right after CyanogenMod upgraded from the 10 to 10.1 builds, the boot logo changed from landscape to portrait. What happened with my device (Galaxy Tab 2 7.0 GT-P3113) is slightly odd. The boot logo for CyanogenMod is now stuck in the upper right corner of the screen and appears squished. As I said before, this DOES NOT impact device operation, so if you have another thread to watch, I suggest you do that. But if you are inclined to help me fix this problem, please note that I have already done the following:
Flashed device to stock ROM using ODIN
Re-rooted the device using the auto root tool for this device
Flashed CWM Recovery latest version (Touch) using ODIN
Re-installed the latest version of CyanogenMod 10.1 Stable
There is an image of the issue attached to this post below if you are interested.
Thank you for your support!
-RespawnedEvil
RespawnedEvil said:
Hey Guys,
Let me first start off by saying this problem in no way effects overall performance and operation of my device. With that being said, this problem is just more of a cosmetic issue with CyanogenMod and the OCD I have towards it. Right after CyanogenMod upgraded from the 10 to 10.1 builds, the boot logo changed from landscape to portrait. What happened with my device (Galaxy Tab 2 7.0 GT-P3113) is slightly odd. The boot logo for CyanogenMod is now stuck in the upper right corner of the screen and appears squished. As I said before, this DOES NOT impact device operation, so if you have another thread to watch, I suggest you do that. But if you are inclined to help me fix this problem, please note that I have already done the following:
Flashed device to stock ROM using ODIN
Re-rooted the device using the auto root tool for this device
Flashed CWM Recovery latest version (Touch) using ODIN
Re-installed the latest version of CyanogenMod 10.1 Stable
There is an image of the issue attached to this post below if you are interested.
Thank you for your support!
-RespawnedEvil
Click to expand...
Click to collapse
Same problem here, only on my device it changes after about 5 seconds to normal. Already looked into this and, as far as I could find, there is no solution yet.
its common problem we all get that
Same here.
I rarely reboot the device and it doesn't seem to actually affect the device, so I just ignore it.
ddochi11 said:
Same here.
I rarely reboot the device and it doesn't seem to actually affect the device, so I just ignore it.
Click to expand...
Click to collapse
LET'S not ignore this bug, as this is not supposed to happen. If anybody else has this issue, please raise your hand and post it here. This has been going for a loong while and needs to be fixed.
Hey there is a way to get rid of it.
Please follow the instructions
1. Get the latest phillz recovery. Install it using ur present recovery.
2. Get the latest black hawk next kernel v1.8.3. Flash the zip file.
3. Get the vendor blobs (not necessary cuz the latest nightlies have them preinstalled)
4. Go to /system/buildprop file n change rf. so .hwrotation=270 to rf. so
.hwrotation=0
5. Reboot the device.
Press thanks if I helped.
Sent from my GT-P3100 using xda app-developers app
*EDIT: The screen is screwed up now. It's taking portrait touch responses instead of landscape ones, and the screen does not rotate.
I can confirm this works in landscape mode, but isn't portrait the intended orientation?
No I changed the settings wanting it to be in landscape mode cuz i use tablet ui n it makes my tab look better. Need to work around a way for portrait mode.
Sent from my GT-P3100 using xda app-developers app
Yes, but the touch screen reverses the input of my finger and rotates the screen opposite and to the left of the way I'm holding it. You have no idea how hard it was to restore the build.prop when you need to use a broken UI to enable USB debugging. Ugh..
OK but I have no such issues, been running it smoothly since a week.
Sent from my GT-P3100 using xda app-developers app
I have it aswell!
I have this same issue, not only with the rom, but ALL of them.
Report to CyanogenMod Developers?
Someone should forward this thread to the CM dev team. Maybe then, and only then will it be fixed.
i think all of the tab2 which use CM rom have the same problem, my tab2 p3110 too...
hope someone of the CM devteam can fix it
impliu said:
i think all of the tab2 which use CM rom have the same problem, my tab2 p3110 too...
hope someone of the CM devteam can fix it
Click to expand...
Click to collapse
I believe it is only a problem with the 7" models of the Samsung Galaxy Tab 2 tablets.
vehvariya said:
Hey there is a way to get rid of it.
Please follow the instructions
1. Get the latest phillz recovery. Install it using ur present recovery.
2. Get the latest black hawk next kernel v1.8.3. Flash the zip file.
3. Get the vendor blobs (not necessary cuz the latest nightlies have them preinstalled)
4. Go to /system/buildprop file n change rf. so .hwrotation=270 to rf. so
.hwrotation=0
5. Reboot the device.
Press thanks if I helped.
Sent from my GT-P3100 using xda app-developers app
Click to expand...
Click to collapse
I've tried to install black hawk next kernel,and my p3110 was stucked at the Boot Logo..
I must flash phillz recovery first? I'm using the CWM recovery.
The problem is there in almost every ROM except for AOSPA http://forum.xda-developers.com/showthread.php?t=2168670 . If we can just find whats the difference?
THpubs said:
The problem is there in almost every ROM except for AOSPA http://forum.xda-developers.com/showthread.php?t=2168670 . If we can just find whats the difference?
Click to expand...
Click to collapse
That seems odd indeed. I will compare the two tonight and hopefully get some results.
Also, thank you for introducing me to a lovely new ROM.
-RespawnedEvil
RespawnedEvil said:
That seems odd indeed. I will compare the two tonight and hopefully get some results.
Also, thank you for introducing me to a lovely new ROM.
-RespawnedEvil
Click to expand...
Click to collapse
You welcome. I used AOSPA but its a bit sluggish compared to CM. Might work for you but I want speed
Philz recovery is a must. Otherwise it won't boot. Use the latest version of it.
Sent from my GT-P3100 using xda app-developers app
I think this is the common bug for tablets
I can't click on the Install button when trying to install an APK. The screen acknowledges the touch, but the button doesn't do anything. But when I rotate the phone to Landscape, it works fine.
Youtube video link: https://www.youtube.com/watch?v=U9xHA3f7-_c
(For some reason the forum doesn't want to embed this video)
Anyone have any ideas? Let me know.
Stock CM11S and Root.
It's a bug. Happens to me using Mahdi rom as well. Most likely cm related. Just stick to the workaround for now, would probably help if you made a post on jira.cyanogenmod.org so cm can look into it.
Sent from my One A0001 using Tapatalk
I've been getting random reboots for a while now on this Oneplus One and I would like some help finding out the culprit. I run Temasek's CM12.1 ROM and have been getting this problem intermittently. It reboots when I do something sometimes or when my phone is just laying there.
The last_kmsg file is here:
https://drive.google.com/file/d/0ByoZACOjvb0DSjJSTEpJSmlES3M/view?usp=docslist_api
If you could help, that'd be amazing. Thank you.
nivekx9 said:
I've been getting random reboots for a while now on this Oneplus One and I would like some help finding out the culprit. I run Temasek's CM12.1 ROM and have been getting this problem intermittently. It reboots when I do something sometimes or when my phone is just laying there.
The last_kmsg file is here:
https://drive.google.com/file/d/0ByoZACOjvb0DSjJSTEpJSmlES3M/view?usp=docslist_api
If you could help, that'd be amazing. Thank you.
Click to expand...
Click to collapse
Yes there is a kernel panic/error pls post it inside the temasek development thread. There is nothing you can do. The dev must fix that.
Sent from my A0001 using XDA Free mobile app
Thanks!