Hello everyone,
As the title states, I'm running CM 10.1.3 rc2 on my P5113 using the p5110 build and every time I go to settings and tap on either lock screen/ screen security or the security tab itself the program force closes and says "unfortunately, settings has stopped."
Any idea what the cause is?
Same thing happened on 10.2 as well.
Adam
xx3rdwrightxx said:
Hello everyone,
As the title states, I'm running CM 10.1.3 rc2 on my P5113 using the p5110 build and every time I go to settings and tap on either lock screen/ screen security or the security tab itself the program force closes and says "unfortunately, settings has stopped."
Any idea what the cause is?
Same thing happened on 10.2 as well.
Adam
Click to expand...
Click to collapse
i have the same problem, im using p5100 and CM 10.1.2 stable version. everty time i tap on settings>security it will close
i think i have found what caused this, its because i have installed custom kernel, i've trying installing custom kernel and without it..
the kernel i've installed that caused this problem was DhollmenCM..
i have PMed the developer, he said the latest kernel have this issue (DhollmenCM-P51xx-Kernel_20130825), so he suggest me to install the july version
~HnR said:
i think i have found what caused this, its because i have installed custom kernel, i've trying installing custom kernel and without it..
the kernel i've installed that caused this problem was DhollmenCM..
i have PMed the developer, he said the latest kernel have this issue (DhollmenCM-P51xx-Kernel_20130825), so he suggest me to install the july version
Click to expand...
Click to collapse
Thanks for the reply!
I on the other hand was not running a custom kernel, I couldn't figure it out so I went with a stock Rom...
Related
hello all running into a issue with the current 29 december build of CM10 i got every thing booted up but there is no app button for accessing any apps. and the home screen is blank. i tryed the last 5113 nightly build but there is no onscreen qwerty keyboard... i am stuck can any one help me?
justin_48 said:
hello all running into a issue with the current 29 december build of CM10 i got every thing booted up but there is no app button for accessing any apps. and the home screen is blank. i tryed the last 5113 nightly build but there is no onscreen qwerty keyboard... i am stuck can any one help me?
Click to expand...
Click to collapse
Same problem here. I've been trying to go back to stock since its not fixed... You wouldn't have a 4.1.1 stock jelly bean for the p5113 would you?
Tyler.Boston1 said:
Same problem here. I've been trying to go back to stock since its not fixed... You wouldn't have a 4.1.1 stock jelly bean for the p5113 would you?
Click to expand...
Click to collapse
Sadly i dont have anything... hell i didnt even do a back up so im screwed my self...
Same issue here. no Apps button in latest nightly
Solution !!
justin_48 said:
hello all running into a issue with the current 29 december build of CM10 i got every thing booted up but there is no app button for accessing any apps. and the home screen is blank. i tryed the last 5113 nightly build but there is no onscreen qwerty keyboard... i am stuck can any one help me?
Click to expand...
Click to collapse
Hey, I have the same problem and i am running it on my galaxy S2- GT-I9100g. it seems that it's a launcher problem so i tried to install NOVA launcher and guess what it worked, so i am running NOVA launcher temporarily till a new version of CM10.1 comes out or find another solution .
Guys, am I the only one getting constant reboots on the latest nightlies? I load up a nightly (have tried 3/17, 3/19, 3/23 so far) and I clear data cache and dalvik prior and post load. I also load the newest 4.2.2 gapps for jb.
The phone reboots itself on everything from Temple Run to basic browsing to music playing through Bluetooth. There seems to be no rhyme, reason, or specific app causing it.
I am using the built in kernel... Is this kernel instability I am seeing?
Please tell me I'm not the only one experiencing this. I am a big fan of cyanogenmod, have used it on many phones over the years but this has been very unreliable for me.
Thanks, Brian
Did you try to fix permission using cwm or ROM manager? That might help. if not, try aokp 4.2.2 or liquid smooth.
Sent from a Shaftamle Galaxy S3
Shaftamle said:
Did you try to fix permission using cwm or ROM manager? That might help. if not, try aokp 4.2.2 or liquid smooth.
Sent from a Shaftamle Galaxy S3
Click to expand...
Click to collapse
Ok so I fixed permissions on 3/23 cyanogenmod nightly, still constant reboots. Then I flashed aokp (hilbert) newest nightly based on 3.0.68 kernel and I am getting the same problem.
Is there any other way to troubleshoot this? Can someone else speak up who is running the newest night lies without FCs or reboots so I know I'm not crazy.?
Thanks for your IMs as well... I will definitely try newer builds.
bguild said:
Guys, am I the only one getting constant reboots on the latest nightlies?
Click to expand...
Click to collapse
I didn't get constant reboots but I did get random reboots from time to time.
I also noticed the latest nightly I ran (3/23) seems very slow.
My fix was to restore my backup of CleanRom and I may just not return to CM 10.1.
Lockups and random reboots have been discussed for the last few pages in both the thread in this section and the dev section, commonly seems to have started 3/18 nightly when they switched over to the 3.4 kernel..newest nightlies were supposed to have some fixes merged but I haven't tried it yet
http://forum.xda-developers.com/showthread.php?t=2071252&page=124
personally had the issue on both 3/20, 3/21 , rolled back to the last nightly on the old kernel which is 3/17 and haven't had it happen since as for AOKP I don't use that so couldn't tell you what the issue is with that ROM
NeoMagus said:
Lockups and random reboots have been discussed for the last few pages in both the thread in this section and the dev section, commonly seems to have started 3/18 nightly when they switched over to the 3.4 kernel..newest nightlies were supposed to have some fixes merged but I haven't tried it yet
http://forum.xda-developers.com/showthread.php?t=2071252&page=124
personally had the issue on both 3/20, 3/21 , rolled back to the last nightly on the old kernel which is 3/17 and haven't had it happen since as for AOKP I don't use that so couldn't tell you what the issue is with that ROM
Click to expand...
Click to collapse
My thought is that in my case there may be something else going on. So far I have tried Cyanogenmod 3/17,3/20 and 3/23 nightly, a 3/23 nightly for AOKP, and now I just installed CleanROM 6.2 R2, which is Android 4.1.2 based. I think most of these kernels are 3.0.x based. I am definitely still getting occasional reboots and FCs but I will say it seems CleanROM is the most stable.
The common thread on all of these builds seems to be that the most instability occurs when attempting to connect to a bluetooth device. That is when I get the constant reboots. I'm talking like you start to play a song, and it gets through half way and just completely reboots itself.
I'm going to keep trying here, but I might have found the common thread in bluetooth instability.
Does the 3.4 kernel report as 3.4.x on the newer nightlies?
Yes it shows in the settings, I personally haven't had any issues with connecting or using my A2DP rocketfish Bluetooth headset even when I was on the newer nightlies with the 3.4 kernel, it was more of hadn't used the phone for a while went to turn the screen on and it wouldn't come back had to battery pull.
Haven't had a single problem since rolling back lockup or otherwise so I'm watching the main threads to hear when they get the issues with the kernel figured out before flashing anything newer
I just installed cyanogenmod 10.2 on my tab 2 7.0 and i turned on bluetooth however my bluetooth keyboard which worked in stock doesn't show up when scanning. I'm not sure if bluetooth is even working at all.
Jxt. said:
Hello,
does it scan other nearby devices?
Is your tablet visible to other devices?
Click to expand...
Click to collapse
Ok the keyboard connected after a while. It was actually the keyboard that was having issues since after a while I was able to see my neighbors in the dorm next to me s mac book showing up on bluetooth. The only issue I have still is that the delete key doesn't really function as backspace I have to highlight a chunk of text then hit it to delete. I downloaded an app called delete key as backspace but I can't figure out how to set that up. I looked in the screenshot instructions but cannot find a section for physical keyboard.
Jxt. said:
did you check the keyboard layouts?
Click to expand...
Click to collapse
where is that exactly I looked and all I can seem to fine are languages but I looked and theres nothing in there about delete as backspace
I have a P5113 running cm 10.2 nightly. It seems to be finicky with bluetooth. I use sixaxis to connect my PS3 controller, but sometimes it just won't connect. Have to manually turn on/off bluetooth a few times, wait a few seconds, try again. It eventually will work though.
Jxt. said:
Did you see this in your language input settings?
Click to expand...
Click to collapse
No when the keyboard is connected I still don't see physical keyboard options
Jxt. said:
Nightlys are always buggy, i also use the ps3 sixaxis but i never have trouble getting the bluetooth to stay on.
You should check out Pacman ROMs. :laugh:
Click to expand...
Click to collapse
I'm using a version called cm-10.2-20130919-UNOFFICIAL-p3110 It's not a nightly or even an official cyanogenmod supported version I think. I just ended up with it by following a youtube tutorial. This makes me think that when cyanogenmod for the tab 2 7.0 progresses I won't be able to update through cyanogenmod update.
If this is the case will I be able to just flash a rc version of 10.2 when it becomes available without having to wipe data factory reset? I really hate having to reinstall everything
please tell my you can put the home back and multitasking buttons back to normal in that rom. I really don't like what they have done with hiding them and having you drag your finger up from the bottom to get at them.
Really I just want the lightest rom possible using the least amount of resources on my tablet
Jxt. said:
I don't understand how yours look.. screenshot please
Click to expand...
Click to collapse
Uploaded with ImageShack.us
the home button and back and task switch buttons are normal in mine but they r in that annoying circle you have to swipe up to get in pac rom. I looked at a few roms before jumping on the cyanogenmod bandwagon
Jxt. said:
I don't see a circle...
Click to expand...
Click to collapse
no i am running cm 10.2 and pac rom has a half wheel thing. Look at the screenshots in this thread suggested earlier. I was just stating that I don't really like the way the buttons are in that rom as I looked into it earlier
http://forum.xda-developers.com/showthread.php?t=2202854
mikee286 said:
No when the keyboard is connected I still don't see physical keyboard options
I'm using a version called cm-10.2-20130919-UNOFFICIAL-p3110 It's not a nightly or even an official cyanogenmod supported version I think. I just ended up with it by following a youtube tutorial. This makes me think that when cyanogenmod for the tab 2 7.0 progresses I won't be able to update through cyanogenmod update.
If this is the case will I be able to just flash a rc version of 10.2 when it becomes available without having to wipe data factory reset? I really hate having to reinstall everything
Click to expand...
Click to collapse
I see you switched to PAC Rom already but back to your original question.
There was a Bluetooth keyboard problem with CM 10.2 early versions.
I think you were using Cody's version of CM 10.2 in the latest versions of CM 10.2 they fixed the "Bluetooth Keyboard Bug" so if you want to use CM 10.2 you just need the latest versions or you can install an app to fix the Keyboard problem and keep using the older versions.
https://play.google.com/store/apps/details?id=com.heightdev.ganhou&hl=en
hcfte said:
I see you switched to PAC Rom already but back to your original question.
There was a Bluetooth keyboard problem with CM 10.2 early versions.
I think you were using Cody's version of CM 10.2 in the latest versions of CM 10.2 they fixed the "Bluetooth Keyboard Bug" so if you want to use CM 10.2 you just need the latest versions or you can install an app to fix the Keyboard problem and keep using the older versions.
https://play.google.com/store/apps/details?id=com.heightdev.ganhou&hl=en
Click to expand...
Click to collapse
thank you I am downloading the app. I have not switched to pac rom I was debating it but I ended up going with cm because its not bloated.
As I mentioned in an earlier post I think I am using an unofficial build of cm 10.2 built sometime in september. Would I be able to flash an official nightly build without having to wipe data factory reset Again the file I have currently flashed is cm-10.2-20130919-UNOFFICIAL-p3110
mikee286 said:
thank you I am downloading the app. I have not switched to pac rom I was debating it but I ended up going with cm because its not bloated.
As I mentioned in an earlier post I think I am using an unofficial build of cm 10.2 built sometime in september. Would I be able to flash an official nightly build without having to wipe data factory reset Again the file I have currently flashed is cm-10.2-20130919-UNOFFICIAL-p3110
Click to expand...
Click to collapse
I think this http://forum.xda-developers.com/showthread.php?t=2391355 is the Rom you are using it's the same one I use on my P3113. When CM 10.2 first came out they had a BT problem and that app worked for me.
I believe CM fixed the problem before Cody's last release and my keyboard has been working again without needing the App to fix it.
I just checked my Backspace button and it works fine on my BT 3.0 keyboard.
I did switch the Kernel to Next 2.1.2 so I don't know if that makes any difference.
I would ask in Cody's thread about being able to flash the latest CM 10.2 over Cody's without doing a clean install.
hello, i love my galaxy s3 and even more because i took the leap and rotted and I am running on roms. My favorite rom is cyanogenmod but I have never gotten the camera to work on it with anything greater than cm10.0. I am currently running AOKP which allows the camera to work which is awesome too but i would love to go back to CM. I have searched for hours but never found a solution that worked. I tried flashing a file that some around this forum and other forums have said fixed the CM camera issue but that did not help. If anyone know of a fix so i could use CM10.1 or CM 10.2 I would be greatly appreciated. Thank you for your time.
Have you tried a clean install of CM 10.2? I haven't had any issues with my camera running any custom rom.
Does it work at all, or are you just missing some feature?
esjames said:
Have you tried a clean install of CM 10.2? I haven't had any issues with my camera running any custom rom.
Does it work at all, or are you just missing some feature?
Click to expand...
Click to collapse
I have not tried a clean install. I will try that when I get a chance. The camera sometime opens and I can zoom in and out a few seconds but then it freezes and the phone restarted. Also, other times the camera open to a black screen and freezes and the phone restarts. It really sucks This is the only issue I am having with CM and why I switched to another rom.
Doing a clean install fixed the problem. Thank you so much for your help. I would like to mark this thread as SOLVED but i do not know how. Hopefully an admin can do this.
godfather17 said:
Doing a clean install fixed the problem. Thank you so much for your help. I would like to mark this thread as SOLVED but i do not know how. Hopefully an admin can do this.
Click to expand...
Click to collapse
Just press your first post and modify it. Glad you fixed your issue.
I'm waiting for Android Milky Way
Hi guys,
I tried to flash the Franco kernel with the CM11 snapshot M9, for some reason i get pixel distortion top right. Where the cell bars show, sometimes over the complete right side of the screen.
Thereafter i re-flashed the rom directly following with the franco kernel, same result though.
Any ideas?
Thanks!
Its known issue. Graphics overlay on screen touch.
Workaround: Goto 'Developer Options' and disable Hardware Overlays.
U have to do this every time u reboot the phone.
Update your ROM, you're using a outdated ROM thats lacking the commits. Easier to update your ROM than to do a workaround on every reboot.
zephiK said:
Update your ROM, you're using a outdated ROM thats lacking the commits. Easier to update your ROM than to do a workaround on every reboot.
Click to expand...
Click to collapse
You're saying there is an update for stable version?
Or do you mean flashing the latest nightly?
Thanks for the answers guys!
Waanzin said:
You're saying there is an update for stable version?
Or do you mean flashing the latest nightly?
Thanks for the answers guys!
Click to expand...
Click to collapse
Latest nightly.
What samflorin said, M10 is out for some phones. OnePlus One is still being worked on so they didn't push M10 yet. When it does, it should be very close to the OTA.
M9 was a very old build that lacked the commits causing conflict on the kernel side of things. Once you update, all should be good