[Note: I posted this a few minutes ago as a reply to another post in the "4.3 ROM" thread in this forum, then realized it would likely be overlooked there. Please forgive the duplicate post. n00b]
Great news that albinoman887 got 4.3 off the ground. Unfortunately, I have a problem, and since I'm the junior...est of members, I can't yet post in the development thread where I could ask him this directly.
I did a factory reset on my MyTouch 4G, installed Albinoman's 4.3 (cm-10.2-20130813-Albinoman887-glacier.zip) ROM and the new GApps (gapps-jb-20130726) zip linked to in his thread, rebooted, and everything appeared to be working until it was time to enter and sync to my GMail account, at which point I received an error message indicating that the AOSP Android keyboard had closed. Sure enough, every time I attempted to input anything, the message reappeared and I had no way of logging into my Google account. Touch screen input works, but without a keyboard, that's as far as I could go.
Thinking maybe I had a corrupted GApps zip, I did another full wipe, re-flashed the ROM, and this time tried the 07/13 GApps zip; unfortunately, when I rebooted, I got identical behavior. Since I needed to use my phone as a, you know, phone (they still do that!) tonight, I did yet another wipe, flashed the latest 4.2 ROM (also from Albinoman) and, to make sure it worked, the newest 07/26 GApps. No problems, seems to work perfectly.
I've checked albinoman's 4.3 thread, and, while there are a few bug reports, no one else seems to be having this keyboard problem.
Any suggestions? As a n00b, is there any way for me to message albinoman directly without coming off as a whiny d-bag?
Thanks in advance...
Re: Flashed albinoman887's new 4.3 ROM - keyboard not working
jdburns said:
[Note: I posted this a few minutes ago as a reply to another post in the "4.3 ROM" thread in this forum, then realized it would likely be overlooked there. Please forgive the duplicate post. n00b]
Great news that albinoman887 got 4.3 off the ground. Unfortunately, I have a problem, and since I'm the junior...est of members, I can't yet post in the development thread where I could ask him this directly.
I did a factory reset on my MyTouch 4G, installed Albinoman's 4.3 (cm-10.2-20130813-Albinoman887-glacier.zip) ROM and the new GApps (gapps-jb-20130726) zip linked to in his thread, rebooted, and everything appeared to be working until it was time to enter and sync to my GMail account, at which point I received an error message indicating that the AOSP Android keyboard had closed. Sure enough, every time I attempted to input anything, the message reappeared and I had no way of logging into my Google account. Touch screen input works, but without a keyboard, that's as far as I could go.
Thinking maybe I had a corrupted GApps zip, I did another full wipe, re-flashed the ROM, and this time tried the 07/13 GApps zip; unfortunately, when I rebooted, I got identical behavior. Since I needed to use my phone as a, you know, phone (they still do that!) tonight, I did yet another wipe, flashed the latest 4.2 ROM (also from Albinoman) and, to make sure it worked, the newest 07/26 GApps. No problems, seems to work perfectly.
I've checked albinoman's 4.3 thread, and, while there are a few bug reports, no one else seems to be having this keyboard problem.
Any suggestions? As a n00b, is there any way for me to message albinoman directly without coming off as a whiny d-bag?
Thanks in advance...
Click to expand...
Click to collapse
The same issue did occur for me as well a couple of times, however I already had SwiftKey as the default keyboard prior to installing the update. So I could at least get in to the system. Once the phone booted up, I navigated to Settings -> Language and Input, and tapped on Android keyboard. The error doesn't show up for me anymore.
You can try setting another keyboard as the default before updating to 4.3. It may work for you too.
Hope this helps.
Same thing happened to me. I just went back to 4.2.2 for now since I need a stable DD. I'm sure albino will get it going!
Sent from my myTouch 4G using xda app-developers app
Solution for Keyboard issue 10.2
Hi everyone.
The problem is gapps package. The package that Goo Manager suggests is only for 4.2 not for 4.3
You have to download this and install it from recovery.
Look here, the second link on the post
http://forum.xda-developers.com/showthread.php?p=44607338
Unless in my HTC Sensation worked like a charm
Regards
Jorge
Hello there.
I recently tried to install the most recent version of PAC ROM for my Galaxy S4 (Sprint, SPH-L720, running PAC ROM 23.0 and Android 4.2.2) from their nightly basket builds (I tried to install the November 19th build.) The installation itself goes off without a hitch, as does the GApps installation. However, after installing it (cleaned out the cache and Davlik cache prior to installation, installed GApps after installation), I get multiple error messages. The keyboard process has stopped working, and android.process.acore have stopped working (tells me to blame Tyler.) The device also seems to be laggy in general, and when I try to launch the Phone app, it says it is not installed.
I just want to be able to use 4.3 and PAC ROM's newest features.
If someone can help me resolve this issue or link me to a stable but updated build of PAC ROM, that would be great.
Thank you!
D3xus said:
Hello there.
I recently tried to install the most recent version of PAC ROM for my Galaxy S4 (Sprint, SPH-L720, running PAC ROM 23.0 and Android 4.2.2) from their nightly basket builds (I tried to install the November 19th build.) The installation itself goes off without a hitch, as does the GApps installation. However, after installing it (cleaned out the cache and Davlik cache prior to installation, installed GApps after installation), I get multiple error messages. The keyboard process has stopped working, and android.process.acore have stopped working (tells me to blame Tyler.) The device also seems to be laggy in general, and when I try to launch the Phone app, it says it is not installed.
I just want to be able to use 4.3 and PAC ROM's newest features.
If someone can help me resolve this issue or link me to a stable but updated build of PAC ROM, that would be great.
Thank you!
Click to expand...
Click to collapse
You need to do a full wipe from PAC23 to 4.3 (factory reset in recovery)
Figures. :/
What app should I use to backup the contents of my phone to use after the update (messages, apps)
Q&A for [ROM][Official] CyanogenMod 11
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
i have lag on multitasking for this rom anyone have lag same as me ? can i fix that ?
sorry for my bad english
Unable to flash CM11 onto Moto XT905 (moto_msm8960_jbbl)
Hi all
Frustration... I've spent all day trying to get my Moto XT905 to run the CM11 builds which I'm told will work on it.. Followed the instructions on the "Install_CM_for_moto_msm8960" wiki using the ADB sideload method and had also tried flashing direct from recovery. Tried with CWM and TWRP but no success. Wiped system and data before each attempt.
The final error message from CWM read as follows:
"Can't install this package on top of incompatible data. Please try another package or run a factory reset. E:Error in /tmp/update.zip
(Status 7)
Installation aborted"
Can anybody point me in the direction of where I'm going wrong? Desperate to get off stock as my battery performance is miserable
Thanks in advance, very grateful of any advice
timhowes said:
Hi all
Frustration... I've spent all day trying to get my Moto XT905 to run the CM11 builds which I'm told will work on it.. Followed the instructions on the "Install_CM_for_moto_msm8960" wiki using the ADB sideload method and had also tried flashing direct from recovery. Tried with CWM and TWRP but no success. Wiped system and data before each attempt.
The final error message from CWM read as follows:
"Can't install this package on top of incompatible data. Please try another package or run a factory reset. E:Error in /tmp/update.zip
(Status 7)
Installation aborted"
Can anybody point me in the direction of where I'm going wrong? Desperate to get off stock as my battery performance is miserable
Thanks in advance, very grateful of any advice
Click to expand...
Click to collapse
Does your XT905 have official KitKat? If not, please fall back to moto_msm8960_jbbl and use a different recovery (made for JB BL).
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
timhowes said:
Hi all
Frustration... I've spent all day trying to get my Moto XT905 to run the CM11 builds which I'm told will work on it.. Followed the instructions on the "Install_CM_for_moto_msm8960" wiki using the ADB sideload method and had also tried flashing direct from recovery. Tried with CWM and TWRP but no success. Wiped system and data before each attempt.
The final error message from CWM read as follows:
"Can't install this package on top of incompatible data. Please try another package or run a factory reset. E:Error in /tmp/update.zip
(Status 7)
Installation aborted"
Can anybody point me in the direction of where I'm going wrong? Desperate to get off stock as my battery performance is miserable
Thanks in advance, very grateful of any advice
Click to expand...
Click to collapse
The error message is quite clear. When installing ROM (e.g. CM11) signed with keys different from what is currently running on your device (stock Motorola firmware), you have to wipe data / factory reset.
I have installed the 11-20141008-SNAPSHOT-M11-moto_msm8960_jbbl after doing a rsd lite flash of VRZ_XT907_9.8.1Q-94-1_CFC.xml with the downgrade script provided in another topic. I have noticed that the WiFi has had severe bandwidth issues regardless of whether bluetooth is enabled etc. Optimization is off and i also tried setting the frequency to 2.4GHz only.
I have done multiple clean reflashes incase it was an underlying bootloader bug but I haven't had any luck. Any help would be greatly appreciated.
kabaldan said:
The error message is quite clear. When installing ROM (e.g. CM11) signed with keys different from what is currently running on your device (stock Motorola firmware), you have to wipe data / factory reset.
Click to expand...
Click to collapse
Thanks for this kabaldan. However on every attempt I wiped system, data, cache and did factory reset (data & cache I believe) before flashing CM11 and got the same error message. Do you know why this would be? In each case, recovery said the wipe had been successful.
timhowes said:
Thanks for this kabaldan. However on every attempt I wiped system, data, cache and did factory reset (data & cache I believe) before flashing CM11 and got the same error message. Do you know why this would be? In each case, recovery said the wipe had been successful.
Click to expand...
Click to collapse
See what I said and check if that's the reason. I'm not so sure because I don't own a XT905.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
AndyYan said:
See what I said and check if that's the reason. I'm not so sure because I don't own a XT905.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
Click to expand...
Click to collapse
Thanks. Apologies but I am still a little confused... I don't have official KitKat. My system version is 98.21.7.XT905.Retail.en.AU.
I'm not sure what you mean by "fall back" to moto_msm8960_jbbl - I thought these were the CM11 ROM images I can't install. And how do I know if my recovery is for JB bootloader? I have a JB bootloader and have successfully flashed versions of TWRP (currently v2.3.2.3) and CWM. Would these even flash if they weren't compatible with my bootloader?
timhowes said:
Thanks. Apologies but I am still a little confused... I don't have official KitKat. My system version is 98.21.7.XT905.Retail.en.AU.
I'm not sure what you mean by "fall back" to moto_msm8960_jbbl - I thought these were the CM11 ROM images I can't install. And how do I know if my recovery is for JB bootloader? I have a JB bootloader and have successfully flashed versions of TWRP (currently v2.3.2.3) and CWM. Would these even flash if they weren't compatible with my bootloader?
Click to expand...
Click to collapse
You're now on JB BL and *should* flash moto_msm8960_jbbl instead of moto_msm8960, as the latter is KK BL-only.
Dhacker29's site used to have a copy of TWRP 2.7.0.0 for JB BL, but seems like the site is down, so I uploaded a copy: http://d-h.st/MSe , grab this and use it to flash CM11 JB BL mentioned above.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
Hi, so my wife's Razr M is on the official Kit Kat Bootloader, and I even did a factory reset and fresh install of the M11 build. Everything seems okay, and stable, but WiFi and Bluetooth refuse to turn on. I'll tap the "on" switch, and it'll say the radio is turning on, and then after a few seconds, returns to the off position. Is this known or common on this ROM, because I swear Bluetooth used to work.
I can try to see if I can pull a logcat or something if this is not common or understood yet, this this the right forum for this now?
bofis said:
Hi, so my wife's Razr M is on the official Jelly Bean Bootloader, and I even did a factory reset and fresh install of the M11 build. Everything seems okay, and stable, but WiFi and Bluetooth refuse to turn on. I'll tap the "on" switch, and it'll say the radio is turning on, and then after a few seconds, returns to the off position. Is this known or common on this ROM, because I swear Bluetooth used to work.
I can try to see if I can pull a logcat or something if this is not common or understood yet, this this the right forum for this now?
Click to expand...
Click to collapse
Did you turn on your Wifi, bluetooth, etc... before installing CM? I didn't have any issue on the test phone at work with the JB BL after installing the latest CM build. Kit Kat on the other hand... well that's why my main phone is on the stock rom until they can fix that issue.
Okay, I take it back, she's on the Kit Kat bootloader, and running CM11 now. I did a full wipe and installed the M11 build, which I believe only works under the Kit Kat Bootloader now. As I wiped, it should not matter how I had set WiFi or Bluetooth before. So my question is, under the KK Bootloader, does WiFi or Bluetooth work for anyone? Because they do not turn on for me.
I've been running CM11 for a long time.
took the 10/25 update Whisper Push, Hangouts and Goggle Play services, I'm getting "Unfortunately, Hangouts has stopped" error msgs
same with the 10/26 update, what's up?
TwoBuells said:
I've been running CM11 for a long time.
took the 10/25 update Whisper Push, Hangouts and Goggle Play services, I'm getting "Unfortunately, Hangouts has stopped" error msgs
same with the 10/26 update, what's up?
Click to expand...
Click to collapse
I too have been having issues with the latest nightlies. I set an alarm from the Clock app and it will skip the first couple alarms I set, then notify me an hour later that I missed my alarms. Also I am constantly getting errors that systemui.process has stopped whenever I try to turn off an alarm and during normal operation. Other things such as random reboots, and web pages not loading, which makes me refresh the page for it to actually load.
I think I'll revert back to around 10/16 because that was when I was having problems at all.
I restored a good running backup from 9/26 and everything is running great.
the 10/27 update was posted, I updated to the 10/27 nightly and seems to be ok so far.
Wifi, Bluetooth, Microphone
Hi,
I have had the following issues with multiple versions of CyanogenMod on the KK bootloader (unlocked).
Wifi only works on 5 GHz
Bluetooth does not connect to any device
Microphone only works when I am on speaker phone
Ear speaker is not very loud
Have to press the power button 2 or 3 times before my phone turns on
Is there something missing from my phone? I know some people have had issues with wifi and bluetooth. I could not find a fix that worked; unless I missed something. I'm going to try installing a stock rom now to see if it works. I don't know what else to do.
If anyone has any fixes or ideas, I would really appreciate it. Thank you.
*EDIT*
No luck with stock. Same issues with wifi and bluetooth
Microphone works
Razr M Telstra xt905 dimmed screen CM11 Snapshot M11
Quote:
Originally Posted by Rufus
... and add this to my build.prob and it seems to fix the 'sleep of death' - JBBL:
ro.mot.ds.fastdormancy.disable=true
Works for me for months on end like that, have to edit after each flash tho.
Although it has only been a few minutes since I rebooted. Not only has the above setting appeared to have stopped the 'sleep of death' (which I took as where the phone takes a number of attempts to wake it up), but it also appears to have fixed the issue with the screen coming back on, overly dimmed!
Of course, now that I have written this, it will all start to behave as it did before, but here's hopping it continues like this."
I have just flashed CM11 snapshot M11 JBBL on my Australian Telstra XT905 Razr M. It's all working well so far except for two issues. The first is listed above where the phone screen will sometimes come on dimmed. How do I enter the above into build.prob to fix this issue. (I'm an amateur)? Is it through the terminal window? Detailed instructions would be great please.
The other thing I've noticed is the battery seems to be draining faster then the Telstra stock 4.1.2 rom. Any feedback would be appreciated especially from Australian Telstra users.
Cheers
inter111 said:
I have just flashed CM11 snapshot M11 JBBL on my Australian Telstra XT905 Razr M. It's all working well so far except for two issues. The first is listed above where the phone screen will sometimes come on dimmed. How do I enter the above into build.prob to fix this issue. (I'm an amateur)? Is it through the terminal window? Detailed instructions would be great please.
The other thing I've noticed is the battery seems to be draining faster then the Telstra stock 4.1.2 rom. Any feedback would be appreciated especially from Australian Telstra users.
Cheers
Click to expand...
Click to collapse
I've tried adding that line to my CM11 Nightly build already, no effect, screen still dimmed after a quick wake in dark places. You can try anyway, but BACK UP BEFORE YOU PROCEED!
Since you don't look like you're familiar with doing this, I think using Root Explorer's inbuilt editor should be a bit easier. Go to /system and find build.prop. Long press and open it in a new window. At the bottom of the file, press enter for a new line and enter the above. Save and reboot.
Stock usually have better battery life than custom ROMs, that's normal.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
AndyYan said:
I've tried adding that line to my CM11 Nightly build already, no effect, screen still dimmed after a quick wake in dark places. You can try anyway, but BACK UP BEFORE YOU PROCEED!
Since you don't look like you're familiar with doing this, I think using Root Explorer's inbuilt editor should be a bit easier. Go to /system and find build.prop. Long press and open it in a new window. At the bottom of the file, press enter for a new line and enter the above. Save and reboot.
Stock usually have better battery life than custom ROMs, that's normal.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
Click to expand...
Click to collapse
Thanks for the reply. I had the same result as you. The screen is still dimmed after waking sometimes. I guess I'll just have to put up with it.
First of all I know there's another thread about this, but the guy seemed to be able to fix this problem by rebooting his phone so I'm making a new thread.
Today I flashed CM13 on my Nexus6P and it all worked fine until I tried starting the camera, which gave me the error mentioned in the title. Restarting the phone and erasng the app's data didn't work either.
Also everytime I boot my phone it shows me an "your device is corrupted" screen (not the bootloader unlocked screen) and when the phone starts it shows me something like "there's a problem with your phone, it might not work properly".
Is this my fault or is it a CM13 issue and how do I fix it? (I'm using today's official CM13 build with Open Gapps Mini arm64 for android 6.0)
Ju43 said:
First of all I know there's another thread about this, but the guy seemed to be able to fix this problem by rebooting his phone so I'm making a new thread.
Today I flashed CM13 on my Nexus6P and it all worked fine until I tried starting the camera, which gave me the error mentioned in the title. Restarting the phone and erasng the app's data didn't work either.
Also everytime I boot my phone it shows me an "your device is corrupted" screen (not the bootloader unlocked screen) and when the phone starts it shows me something like "there's a problem with your phone, it might not work properly".
Is this my fault or is it a CM13 issue and how do I fix it? (I'm using today's official CM13 build with Open Gapps Mini arm64 for android 6.0)
Click to expand...
Click to collapse
the error when booted can be resoled by flashing the latest vendor img, or at least the one relevant to your roms version.
took me about 2 weeks to figure this out because no one would give me the slightest hint when i asked.
the error screen when it first tries to start i havent been able to resolve, and am thinking there may be none.
not sure what your camera issue could be, but i have seen cam issues from the kernel, when the switch to 6.0,1 first began to merge.
maybe test another kernel, other than that i dont know.
Samehere
Ju43 said:
First of all I know there's another thread about this, but the guy seemed to be able to fix this problem by rebooting his phone so I'm making a new thread.
Today I flashed CM13 on my Nexus6P and it all worked fine until I tried starting the camera, which gave me the error mentioned in the title. Restarting the phone and erasng the app's data didn't work either.
Also everytime I boot my phone it shows me an "your device is corrupted" screen (not the bootloader unlocked screen) and when the phone starts it shows me something like "there's a problem with your phone, it might not work properly".
Is this my fault or is it a CM13 issue and how do I fix it? (I'm using today's official CM13 build with Open Gapps Mini arm64 for android 6.0)
Click to expand...
Click to collapse
I'm facing exactly the same issue. The camera works fine when I flash a stock based ROM like pure nexus or digitalhigh but as soon as I flash an aosp based ROM or cyanogenmod like chroma,screw'd,benzo. The camera says couldn't connect to camera and nothing seems to work. I've wiped cache, data but still no progress.
I even tried the flashable camera.zip but didn't work.
Problem Solved !!!
Ju43 said:
First of all I know there's another thread about this, but the guy seemed to be able to fix this problem by rebooting his phone so I'm making a new thread.
Today I flashed CM13 on my Nexus6P and it all worked fine until I tried starting the camera, which gave me the error mentioned in the title. Restarting the phone and erasng the app's data didn't work either.
Also everytime I boot my phone it shows me an "your device is corrupted" screen (not the bootloader unlocked screen) and when the phone starts it shows me something like "there's a problem with your phone, it might not work properly".
Is this my fault or is it a CM13 issue and how do I fix it? (I'm using today's official CM13 build with Open Gapps Mini arm64 for android 6.0)
Click to expand...
Click to collapse
Just flash the MBD08M.img via fastboot, then flash CM13 on top of it, restart the phone. The Camera won't work yet, now go to Benzo Rom and use his flashable vendor image for MMB29M via Recovery and Reboot. And it works like charm ! =D
You can also flash him flashable camera.zip, to get the stock camera
wrahul31 said:
Just flash the MBD08M.img via fastboot, then flash CM13 on top of it, restart the phone. The Camera won't work yet, now go to Benzo Rom and use his flashable vendor image for MMB29M via Recovery and Reboot. And it works like charm ! =D
You can also flash him flashable camera.zip, to get the stock camera
Click to expand...
Click to collapse
Thanks, I have reverted to stock ROM but I might try it soon