Hello!
Yesterday I flashed my N4 with the stable CM10.1 Version. After flashing the gapps everything went fine. As keyboard I am using Swype. What happens now is that after my Device turns the screenlock on the keyboard switch automatically to standard android keyboard. That sucks, because I have to reswitch it everytime to swype.
Any Ideas?
No one an ideale?
Nexus 4
CM 10.1
Franco Kernel
Related
I just bought the student bundle got home and rooted my phone. I flashed and AOKP rom and a jellybean and the keyboard docking station would not work with either one. I went back to stock recovery and found the keyboard drivers and the keyboard worked. Is there anyway to fix it to where the keyboard would work on a custom rom ? I love my gadgets and like the various roms that are built.
I think the problem is proprietary drivers that not yet implemented to cm or aokp as source code for them not avaliable yet either wait till we get them or workaround appear as alternative drivers or multiboot with stock and cm or aokp
Sent from my GT-P5100 using xda app-developers app
rictrician said:
I just bought the student bundle got home and rooted my phone. I flashed and AOKP rom and a jellybean and the keyboard docking station would not work with either one. I went back to stock recovery and found the keyboard drivers and the keyboard worked. Is there anyway to fix it to where the keyboard would work on a custom rom ? I love my gadgets and like the various roms that are built.
Click to expand...
Click to collapse
You can use custom, just not AOKP, AOSP, CM9/10, I'm on romswell for the very same reason
Sent from my GT-P3113 using XDA
I was seriously searching for this! I just got it today and was trying to figure out why it wasn't working as I didn't try it on stock before i switched to cm10. So basically it doesn't work if you have cm10 installed?
It won't work on aosp/ aokp/cm9/10. Only stock based roms.
Sent from my MB870 using xda premium
Try stock debloated rom or debloat it yourself via app as titanium backup but make a nandroid backup first
Sent from my GT-P5100 using xda app-developers app
I also bought the Student Bundle (a great deal) and did the same thing you did. Metallice's ROM mostly works with the keyboard (I think everything except the App Drawer key works) and you can get that here:
http://forum.xda-developers.com/showthread.php?t=1681317
I ultimately rooted it and used ROM Toolbox to uninstall the bloatware. Unfortunately there is no overclocking kernel - there's a thread for a kernel for 4.0.3 but the developer sold the device and the kernel hasn't been updated yet. If anyone figures out how to get the dock working with custom ROMs, post it here! :laugh:
Same ish happened to me today. I was all ready to type some lengthy email and was like "Wtf!" I thought maybe the KB had to be charged. After realizing that wasn't the case, is why I'm here. Just like everyone else, little peved because stock sucks! Lol
Sent from my SCH-I535 using xda premium
Tab2lite however kicks ass, and and is stock based.
Sent from my GT-P3113 using Tapatalk 2
pogu said:
Tab2lite however kicks ass, and and is stock based.
Sent from my GT-P3113 using Tapatalk 2
Click to expand...
Click to collapse
Which one do you use? Screenies look cool, but I think I flashed rc1 and didn't like it. No Google now or JB launcher look so I switched back. Plus the themes link is dead :/
Lmk all you got. Thx mate!
Sent from my GT-P3113 using xda premium
Questions should be asked in Q&A forums, not Development forums.
Thread moved.
AOKP JB ROM now supports Student Edition Keytboards!
Get it here: http://forum.xda-developers.com/showthread.php?t=1841177
I have been using this now for a day or so, and it is an awesome ROM. Jelly Bean based.
The keyboard works for the most part, but for right now here is what works and what doesn't:
Internet - Works
Mail - Works
Lock Screen - Works
Volume keys - Works
Menu Key - Works
All numerical and letter keys - Works
Search key - Works
Home - Not Working
App key - Not Working
Brightness keys - Not Working
The devolper adds:
"I also sent this to codeworkx as well, so the CM10 folks should see the keyboard working soon."
Alright, so for a while flashlight or torch was not working on any cm based rom.
I thought it was just because it was a nightly, but now on cm 10 stable it still isn't working.
It worked fine on aokp.
tl;dr
torch(flashlight) doesn't work on any cm based rom.
Though torch works on aokp
tl;dr
Any ideas?
Thanks
EDIT: nevermind. flashmode set to normal and it works now.
Hello,
I recently installed the CM 10.1 version and I loved the multi window feature that comes with 4.2. But the ROM was just too buggy for me to use as a daily driver so I went back to CM 10.0. Is there any way I could download and use the multi window app with CM 10.0?
Also quick side question. What is the keyboard used with CM 10.1? its very similar to the android one.
Thank you all.
abehbeh said:
Hello,
I recently installed the CM 10.1 version and I loved the multi window feature that comes with 4.2. But the ROM was just too buggy for me to use as a daily driver so I went back to CM 10.0. Is there any way I could download and use the multi window app with CM 10.0?
Also quick side question. What is the keyboard used with CM 10.1? its very similar to the android one.
Thank you all.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1964814
This is the keyboard.
Sent from my mom's basement.
abehbeh said:
Hello,
I recently installed the CM 10.1 version and I loved the multi window feature that comes with 4.2. But the ROM was just too buggy for me to use as a daily driver so I went back to CM 10.0. Is there any way I could download and use the multi window app with CM 10.0?
Also quick side question. What is the keyboard used with CM 10.1? its very similar to the android one.
Thank you all.
Click to expand...
Click to collapse
no multiwindow feature in 10.1, what exactly are you talking about
skyrocketeer said:
no multiwindow feature in 10.1, what exactly are you talking about
Click to expand...
Click to collapse
he's talking about the multiwindow feature that's part of the stock TW JB 4.2.2 rom, like the note (i think)
There is no multi window feature on stock tw ROM for the skyrocket. Only flashbar. You are on the wrong thread
Sent via Samsung Skyrocket
After flashing latest CM 10.1 nightly (20130311) my tablet booted up but I got the message " Unfortunately System UI has stopped working". Rebooted into twrp recovery and flashed CM 10.1 20130310 nightly. Everything worked fine as usual. Tried flashing CyanDelta 20130311 update file and got the same message. Flashed back to CM 10.1 20130310 nightly again and everything was fine. Has anyone experienced this problem with the CM 10.1 20130311 nightly on Xoom wifi? I have flashed CM 10.1 20130311 nightly on both my GNex and my Nex 7 and have had no problems. Has anyone heard of any bugs with the Xoom CM 10.1 nightly (wingray)? Thanks.
Sent from my Xoom using Tapatalk HD
I had the exact same issue last night. I chalked it up to user error since I had not upgraded CM from within the settings before. I am new to CM and didn't have this option on the competing ROM I used.
kevk60 said:
After flashing latest CM 10.1 nightly (20130311) my tablet booted up but I got the message " Unfortunately System UI has stopped working". Rebooted into twrp recovery and flashed CM 10.1 20130310 nightly. Everything worked fine as usual. Tried flashing CyanDelta 20130311 update file and got the same message. Flashed back to CM 10.1 20130310 nightly again and everything was fine. Has anyone experienced this problem with the CM 10.1 20130311 nightly on Xoom wifi? I have flashed CM 10.1 20130311 nightly on both my GNex and my Nex 7 and have had no problems. Has anyone heard of any bugs with the Xoom CM 10.1 nightly (wingray)? Thanks.
Sent from my Xoom using Tapatalk HD
Click to expand...
Click to collapse
Just wanted to report the same. Yesterday build did not work so I had installed 20130310 build and it is ok although I did not check all the apps.
RoryPG said:
I had the exact same issue last night. I chalked it up to user error since I had not upgraded CM from within the settings before. I am new to CM and didn't have this option on the competing ROM I used.
Click to expand...
Click to collapse
sashykanth said:
Just wanted to report the same. Yesterday build did not work so I had installed 20130310 build and it is ok although I did not check all the apps.
Click to expand...
Click to collapse
So far all my apps seem to be working with cm10.1 20130310 nightly.
Sent from my Xoom using Tapatalk HD
gapps won't flash after reflashing older nightly
kevk60 said:
After flashing latest CM 10.1 nightly (20130311) my tablet booted up but I got the message " Unfortunately System UI has stopped working". Rebooted into twrp recovery and flashed CM 10.1 20130310 nightly. Everything worked fine as usual. Tried flashing CyanDelta 20130311 update file and got the same message. Flashed back to CM 10.1 20130310 nightly again and everything was fine. Has anyone experienced this problem with the CM 10.1 20130311 nightly on Xoom wifi? I have flashed CM 10.1 20130311 nightly on both my GNex and my Nex 7 and have had no problems. Has anyone heard of any bugs with the Xoom CM 10.1 nightly (wingray)? Thanks.
Sent from my Xoom using Tapatalk HD
Click to expand...
Click to collapse
I had the same exact issue with my Xoom. I reflashed an older nightly and it's working again but now I can't get Gapps to flash properly. Every time it loads no gapps....????
I have tried reflashing the latest gapps 3 times now.
Anyone else have this issue or have Any suggestions? Running twrp if it matters but thinking of switching to CWM to try flashing gapps to see if it will take.
I use the team eos gapp pack for Xoom only. When I tried using other gapp packs my system ROM would be full and I could not update supersu. When I use the team eos for Xoom only gapps I found that I have about 30 mb left on my system ROM. My supersu was able to update then. I am using twrp 2.4.3.0 on my Xoom. Am running cm 10.1 20130310 and will stay there until a fix has been made. Do not know if this will help you, just wanted to let you know what has helped me. Are you wiping cache and dalvik before flashing gapps? I'm taking it you are flashing a previous build over the newest nightly.
Sent from my Nexus 7 using Tapatalk HD
kevk60 said:
I use the team eos gapp pack for Xoom only. When I tried using other gapp packs my system ROM would be full and I could not update supersu. When I use the team eos for Xoom only gapps I found that I have about 30 mb left on my system ROM. My supersu was able to update then. I am using twrp 2.4.3.0 on my Xoom. Am running cm 10.1 20130310 and will stay there until a fix has been made. Do not know if this will help you, just wanted to let you know what has helped me. Are you wiping cache and dalvik before flashing gapps? I'm taking it you are flashing a previous build over the newest nightly.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I did wipe both dalvik and cache before flashing gapps. I was using the gapps 20130301 so it could be that or maybe it's an older version of twrp that's causing the issue because I think I'm on 2.4.1.0.
I saw in another thread that I just read someone else was using a different gapps the gapps unified 20130220. I was thinking of giving that a try but I will try the one you recommended first as we both had the same issue above. I will also try flashing the new twrp to see if that's it as well.
Thanks I'll post back up later whether it worked or not.
If you have goo manager you could just update twrp from there.
Sent from my Xoom using Tapatalk HD
Looks like system ui bug issue has been fixed in the newest cm 10.1 nightly (20130314). Thanks to the devs.
Sent from my Xoom using Tapatalk HD
There is a new app out https://play.google.com/store/apps/details?id=com.heightdev.ganhou&hl=en that worked great for fixing my Bluetooth Keyboard.
I am using CM 10.2 (4.3) on my P3113 and my Bluetooth 3.0 quit working all together` after I upgraded to CM10.2 (4.3), now as best as I can tell everything is back working again.