[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
Related
Hi all, i have been having a very bazaar problem lately...When my phone boots up i get a pop-up message indicating that the gapps process shutdown unexpectedly...and sometimes i may even get a acore crash too. Applications from the market do not download...when i select my download i will end up getting a gapps crash and then the supposed download just sits there saying "starting...". Google talk doesn't even open! It will just say that the process quit unexpectedly. Even after a fresh install with factory data reset all these problems will continue. The initial boot up screen/tutorial will even show a gapps crash. I have tried with 3 different versions of cyanogenmod all with the exact same problem..Each version i've tried with a2sd enabled and disabled, formatting the partition each time before a new install to ensure no data carry-over issues. I don't know what to do. To me it seems like it make be something on googles side...but i can't for the life of me figure out whats causing these wild problems. Help would be very much appreciated.
ANDROID Market problems
I've recently had the same problem with the market getting stuck on "starting download". I thought it was something I modified as I'm putting together a STARGATE theme of my own based on kron2's work with this site and the theme for "Open Home" for DWANG's newest ROM. What worked for me was going back 1 restore point at a time till I found one that didn't have the problem (NANDROID backup). I also had luck with flashing DWANG's original unmodified ROM 1.17.1. I had the same problem when I flashed 1.16 ..weird. Up till 2 days ago I didn't have any problems changing anything in it. Others have said that they tried opening G-Talk at the same time and some how going between the 2 the problem would right itself. If you find out anything definite about what the exact problem is let me know as I'm going to keep looking for the answer myself.
six6star said:
I've recently had the same problem with the market getting stuck on "starting download". I thought it was something I modified as I'm putting together a STARGATE theme of my own based on kron2's work with this site and the theme for "Open Home" for DWANG's newest ROM. What worked for me was going back 1 restore point at a time till I found one that didn't have the problem (NANDROID backup). I also had luck with flashing DWANG's original unmodified ROM 1.17.1. I had the same problem when I flashed 1.16 ..weird. Up till 2 days ago I didn't have any problems changing anything in it. Others have said that they tried opening G-Talk at the same time and some how going between the 2 the problem would right itself. If you find out anything definite about what the exact problem is let me know as I'm going to keep looking for the answer myself.
Click to expand...
Click to collapse
I have searched and it seems many people have the Market/Gtalk problem.
I have the same problem (with an Eclair 2.1 Cyanogenmod rom) and I've not been able to find a solution. Wiping the cache makes nothing.
Anyone knows how to solve it?
Huh. I had a problem with the market at first with cyan 5.0.8 . I went in the terminal and ran fix_permissions after su and haven't had any problems since. Might try that
Sent from my HTC Magic using XDA App
3rd thread, about 4th rom flashed
constant issues with builds. have gone from stock to:
cm 6.1.3 -apps crashing, random crash notices i.e "phone book has crashed force close" - "the process com.android.phone has stopped unexpectedly"
cm 7 - random reboots, opening browser caused power cycle, wifi issues, lag (thread posted, no solutions at the forefront)
currently on tripnraver pre release. now another issue. no signal what so ever.
original baseband on this xperia x10a is .55. it is suggested to use with bands 52 or 49.
loading either of these basebands. which ive done. doesn't seem to fix the no signal problem. the description states should be backwards compatible even if appropriate bb is not installed on device. yet no luck.
attempting to flash either baseband fails to resolve this problem. currently trying to flash back to stock and try another full reinstall and baseband flash in flashtool.
any ideas would be a great help. having to flash x number of times between roms is getting quite time consuming
thanks everyone.
if you want to stay on the miui rom, you can flash the baseband patch located here and stay on whatever baseband works best for you (I'm on .55 and find it fantastic), then when you load the rom, go to dev tools>bad behaviour>crash the system server.
http://forum.xda-developers.com/showthread.php?t=1011608
Otherwise, I would recommend wolfbreaks cm 6.1.3, as it is the most stable. You must have done something wrong during installation as I never had an issue with his roms.
The only issue I have ever had with any rom is MiUi and thats because I used the wrong baseband. You must be doing something wrong for you to be having problems
if you want, try this flash, it's trips miui pre-final with the baseband patch implemented.
http://www.multiupload.com/KCKE9K2WKN
worked with my .54 baseband
thanks so much for the links to the baseband patches. i remember coming across a thread that posted it but unfortunately forgot to book mark. so im definitely going to go ahead and try with the patch installed. hopefully all works well
each rom ive flashed has been done properly according to instructions. cache wiped, dalvik, and full reset as per menu options in xrecovery.
one way or another i experienced lag for the most part, and as mentioned some random crashes. never had reset on wolfs rom just error messages at times. trips rom worked excellent, smooth and quick. hopefully with the patch implemented everything will work flawlessly
thanks you guys
*Updated
Flashed over rom with baseband patch. signal working. everything running smooth.
except for when using camera zoom. zoom default displays 0x. as soon as the option is selected it spawns an immediate force close
any patches? or similar outcome for anyone else?
i will outline my steps below so everyones up to speed on how i performed this flash.
- flashed back stock in SEUS
- root with one click (success)
- installed busy box (market)
- installed xrecovery apk
- booted into xrec
1. full factory reset
2. wipe cache
3. wipe dalvik cache
4. wipe battery stats
5. install custom zip from sd card
6. selected trips rom with bb patch implemented
5. reboot
Camera zoom doesn't work in most ROMs yet and the lag you were experiencing was likely just the FW "settling" it can take a little bit and a couple reboots sometimes for the phone to calibrate itself properly.
Sent from my X10i using XDA Premium App
thanks cmoney. maybe ill try my luck with cm7. give it a few reboots and hope for the best. great rom. im really loving trips iphonesque style
clean smooth and quick. everythings working great. hoping the zoom may get fixed soon enough. only other inquiry i have with regards to this rom is the apps2sd.
this feature is essential to myself personally. and it is not working as ive noticed on this rom. ive read a thread with regards to a fix for the last release. i checked the settings for an enable option in case the feature requires being manually set as active but nothing listed. within sd settings state reads as unavailable. if anyone has an answer as to whether this fix will function with the current pre release. ill be going ahead with completeling the flash and reporting what i find back on this thread.
thanks again everyone
Try Wolfbreaks rom. It's very very stable for me. It has cam and everything upto date.
im going to flash back to wolfbreaks updated 6.1.3 unless anyone can point me in the direction of a fix for trips rom.
the smooth and fluid feel of trips rom was brilliant. i am hopeful someone has directions for an apps2sd fix as i have flashed the build twice and the same issue has occured.
thesoundofsilence said:
im going to flash back to wolfbreaks updated 6.1.3 unless anyone can point me in the direction of a fix for trips rom.
the smooth and fluid feel of trips rom was brilliant. i am hopeful someone has directions for an apps2sd fix as i have flashed the build twice and the same issue has occured.
Click to expand...
Click to collapse
works for me on trips newest....
i just downloaded the new version 1.0
this is ridiculous. without the baseband patch. crash system server. no signal
now apps to sd is saying "apps2sd is not supported on this device"
this is an xperia x10, so obviously there must be something wrong here.
can anyone elaborate on exactly what to do about this because im going to attempt to flash back the rom, flash the bb patch right after, reboot. i assume this will only solve my signal issue. but this apps to sd is getting extremely frustrating and i can not figure out why it is not showing an enabled status.
- Flashed 1.0 with baseband patch - network signal resolved.
- apps to sd is STILL not working. and i really dont know what to do about this. everything else on this rom is perfect. is there something im missing? i came across a patch for apps2sd fix but this was for a previous version. would it be needed here? is there a setting that must be enabled first in order to start apps to sd as a service.
- as mentioned previously within the main menu, under sd card settings. message states "apps2sd is not supported on device" and on previous build would display "apps2sd unavailable". its simply impossible that the phone doesn't support it. as with every other rom the feature has worked. froyo would support it. the question is how do i go about enabling said feature?
thesoundofsilence said:
i just downloaded the new version 1.0
this is ridiculous. without the baseband patch. crash system server. no signal
now apps to sd is saying "apps2sd is not supported on this device"
this is an xperia x10, so obviously there must be something wrong here.
can anyone elaborate on exactly what to do about this because im going to attempt to flash back the rom, flash the bb patch right after, reboot. i assume this will only solve my signal issue. but this apps to sd is getting extremely frustrating and i can not figure out why it is not showing an enabled status.
- Flashed 1.0 with baseband patch - network signal resolved.
- apps to sd is STILL not working. and i really dont know what to do about this. everything else on this rom is perfect. is there something im missing? i came across a patch for apps2sd fix but this was for a previous version. would it be needed here? is there a setting that must be enabled first in order to start apps to sd as a service.
- as mentioned previously within the main menu, under sd card settings. message states "apps2sd is not supported on device" and on previous build would display "apps2sd unavailable". its simply impossible that the phone doesn't support it. as with every other rom the feature has worked. froyo would support it. the question is how do i go about enabling said feature?
Click to expand...
Click to collapse
I dunno man, it works fine for me, but I copied data from my 0.3.2 xrecovery image, so that might be why. try flashing that apps2sd fix for 0.3.2, should work fine
damn it. i just found that thread. found the links to the fixes. so far ive tried miui32_a2sd_fix.zip. and flashed that over with xrec prior to reboot. which did nothing.
there are two more links so im going to try those two flashes as well and hope that one of them will do the trick. if its working when utilizing .32 patches then ideally the bloody thing would have to work here. thanks for the input though dtox. much appreciated
I don't know what else to suggest man
From the feedback I see in the miui thread, everyone else is reporting it working!
Did you factory wipe, wipe cache partition, and wipe dalvik cache before install? then flash the miui 1.0.zip, and flash immediately the baseband patch then reboot into the rom.
Remember not all apps allow apps2sd so use something like android system info, go into the applications tab click on one, click manage and then see if the option "move to sd" is highlighted. Like I said check a few though, not all apps can be moved
i just replied in the dev section lol but yes i have gone ahead and checked the applications menu. specifically downloaded a file i have moved to sd on a previous occasion from the market.
nothing
the "apps to sd" selection is completely greyed out. no matter what application i click on or download. i did a full wipe, full install, and selected the apps2sd fix immediately after rom and bbpatch flash, prior to rebooting. issue still remains.
we'll see i guess. thanks again dtox
thesoundofsilence said:
i just replied in the dev section lol but yes i have gone ahead and checked the applications menu. specifically downloaded a file i have moved to sd on a previous occasion from the market.
nothing
the "apps to sd" selection is completely greyed out. no matter what application i click on or download. i did a full wipe, full install, and selected the apps2sd fix immediately after rom and bbpatch flash, prior to rebooting. issue still remains.
we'll see i guess. thanks again dtox
Click to expand...
Click to collapse
Try it again but without the fix...
i did that to it doesnt work i get the same message displayed
i tried with fix and without. another thing to note is that the rom itself says it should work with a different baseband as it has elements of unified. (which it doesn't) i had to flash the bb patch to get signal.
im not sure whats up with this but until i figure it out for a certainty ive flashed back over to wolf breaks rom. hopefully something will surface and i can give trips rom another go.
thesoundofsilence said:
i did that to it doesnt work i get the same message displayed
i tried with fix and without. another thing to note is that the rom itself says it should work with a different baseband as it has elements of unified. (which it doesn't) i had to flash the bb patch to get signal.
im not sure whats up with this but until i figure it out for a certainty ive flashed back over to wolf breaks rom. hopefully something will surface and i can give trips rom another go.
Click to expand...
Click to collapse
No idea man, like I said it is fine for everyone else so I'm so no big development will arise that will make it function with your phone....
maybe it has something to do with 10a. i dont know. but the point is it shouldn't even be doing this regardless. hypothetically if its froyo and it has apps2sd built in. it should work. its not the way ive flashed. the phone supports it. so my only conclusion the rom must not be as compatible as stated. and from reading different posts about the prev builds sometimes the patches worked at other times they didnt. and also the fact that the rom is claimed to work without the need for a bbpatch. yet without the patch instaled phone caught no single. i guess certain unexplainable glitches can be bound to happen at times but any how ill give it one last go.
if nothing comes out of that then im giving up on that build because it seems relatively hopeless.
lol I'm using an x10a...
Still man you're the only person reporting this. Don't you find that strange? What baseband are you using anyhow?
Hello all and I hope you all had a fab Christmas!
Yesterday for the first time my Nexus4 told me that my ROM is no longer cool. It also told me there is a new ROM in town, better and slicker. I decided to try it out. Custom ROM downloaded the new ROM for me and then I wiped out my PA 3.99. Did a cache wipe and a factory reset. Installed the new ROM which was downloaded into the PARANOIDOTA folder. Now comes the funny part. I got two messages one that there is a problem with google play and another that there is a problem with services or something like that. All this messages preventing me to use the phone while I could clearly see the massive soft keys in the background. Clicking ok on these messages wouldn't do anything as they will switch from one to the other. I rebooted and cleared again and reinstalled again with the same result. Can anyone share some light why it didn't work?
I mention that I used CMR v6.0.4.3
Thanks!
I think you needed to flash KitKat gapps after flashing the new rom
Sent from my Nexus 4 using Tapatalk
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.
OK, so got a few questions.
1. This is my main concern actually. So I'm running 14.1 with the correct Gapps n what not. Have the correct vendor image flashed as well like told in a previous forum here..Now, when. I got to update cm through the cm updater as promoted and update, it reboots to recovery, installs...And boot loops. Every single time. I always end up reflashing the previous nightlie (cm-11232016) and rebooting the phone after reflashing the vendor image again ...I'm confused as to what to do here I'm kinda stuck.
Question 2.
OK, when I receive a message notification and pull down the drop menu and use the "reply via SMS" option. (Yes using default SMS app, messaging) once the message has sent, it closes all background apps to where I'm at my home screen. I can't find any setting anywhere for this...Is there a way to stop this from happening? It's kinda an issue because I'm ice and it's really starting to bother me.
jessyjoseph2044 said:
OK, so got a few questions.
1. This is my main concern actually. So I'm running 14.1 with the correct Gapps n what not. Have the correct vendor image flashed as well like told in a previous forum here..Now, when. I got to update cm through the cm updater as promoted and update, it reboots to recovery, installs...And boot loops. Every single time. I always end up reflashing the previous nightlie (cm-11232016) and rebooting the phone after reflashing the vendor image again ...I'm confused as to what to do here I'm kinda stuck.
Question 2.
OK, when I receive a message notification and pull down the drop menu and use the "reply via SMS" option. (Yes using default SMS app, messaging) once the message has sent, it closes all background apps to where I'm at my home screen. I can't find any setting anywhere for this...Is there a way to stop this from happening? It's kinda an issue because I'm ice and it's really starting to bother me.
Click to expand...
Click to collapse
Please use the CM 14.1 existing thread for your queries. Look around the forum for answers. This is not the Q and A Section.
superviked said:
Please use the CM 14.1 existing thread for your queries. Look around the forum for answers. This is not the Q and A Section.
Click to expand...
Click to collapse
Will you move this for me please...I've been after answers for these for several days...If not a week now...I'd appreciate it..Thank you
I think you should revert back to 7.1.1 stock CM14.1 it's problematic