Related
[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
Q&A for CyanogenMod 11.0 for Galaxy S4 LTE-A (GT-I9506)
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:
rtc clock not working properly
I cant change rtc clock time, I tried -w and -systohc, but nothing
I have 20141013 installed
---------- Post added at 05:58 PM ---------- Previous post was at 04:58 PM ----------
Dsp manager also not working. When I change sound compression it works, but at next song it sounds normal, like if it wasnt activated.
RTC can't be set directly on all newer Qualcomm devices.
DSP Manager most likely will be changed in CM. Anyway its DSP Manager bug and not ROMs itself. So if you want look through CM JIRA and if there no such bug report. You can report it.
solk2 said:
RTC can't be set directly on all newer Qualcomm devices.
DSP Manager most likely will be changed in CM. Anyway its DSP Manager bug and not ROMs itself. So if you want look through CM JIRA and if there no such bug report. You can report it.
Click to expand...
Click to collapse
Ok, I'll report that. I also noticed that recovery backups dont have rtc time. I did some research on the internet and I found something about newer qualcomm devices have recovery time kept in a file in /data/time. I could check this by reading the file time_log.1.
I did know this coz one day recovery bacckups were changed from 1970 to 2014, but with wrong date, so I think I would have to do a full wipe, format data and system and reinstall the rom, I think this could work. I also read someting in the changelog like rtc showing correct or something like this. Maybe same time is kept coz I dont do wipes while installing a new nightly. I really appreciate your work, I love your rom.
It is set to 2014 in kernel. That what Samsung made in KK opensourced kernel. And dont be surprised if it will be set to 2014 next year. Day, month isn't changed forcefully. So thats why you see such date in recovery. While in normal boot mode time_daemon starts and sets date and time. So wipe don't change anything. These RTC changes related to normal boot mode only. Particularly to time_daemon.
And yes, recoveries like Philz support setting correct date.
Ok, thanks
Is screenshot function working for you?
Sent from my A0001 using XDA Free mobile app
Dialer
First of all, thank you for a great ROM. The only problem I have, is when I am calling someone. The screen just goes black. Is there any trouble with the proximity sensor?
When I take the phone away from my ear the screen is supposed to light up right? Mine doesn't do that...
Thanks!
B
Hi, is screen mirroring working with CM11 nightlies?
Gesendet von meinem GT-I9506 mit Tapatalk
Hi!
I've been having an issue ever since I started using one of the first nightlies of this ROM: After a random time both my WIFI and phone signal icons turn orange and the proces Android OS starts draining my battery together with having no signal at all. Turning off WIFI at that point doesn't seem to work anymore but can be done by putting the phone in airplane modes. When I disable airplane modes and have my WIFI disabled I can browser through my phone network but Android OS still drains the battery. After I reboot everything is back to normal, as long as I leave my WIFI off.
- I've installed various nightlies and have had the same problem on all of them.
- I've done both a firmware update and a factory reset of my wireless router: Linksys E2000.
- I've both enabeld and disabled the Google Location reporting.
The problem still occurs and I can (with a random time) reproduce it. If anyone can help me debug or solve this problem that'd be great!
Assuming you have CWM in use as recovery, enter CWM. Do a format on /system from mounts menu. Then do a factory reset. Install latest nightly from SD and voila. That worked for me a while back.
TonskuDaigle said:
Assuming you have CWM in use as recovery, enter CWM. Do a format on /system from mounts menu. Then do a factory reset. Install latest nightly from SD and voila. That worked for me a while back.
Click to expand...
Click to collapse
I'll give this a try and let you know if it helped. Thanks!
TonskuDaigle said:
Assuming you have CWM in use as recovery, enter CWM. Do a format on /system from mounts menu. Then do a factory reset. Install latest nightly from SD and voila. That worked for me a while back.
Click to expand...
Click to collapse
That did not work. Just got the orange icons again.
I'm open to suggestions.
(It's not exactly a question, but since I have less than 10 posts)
Hi, I've installed the 20141106-NIGHTLY yesterday, everything was working great, I updated to the 20141107-NIGHTLY today and now I don't have notification sounds, vibration and light, most of the audio files I select under Notification Sound are detected as Unknown Ringtone, the battery notification light is not working too, I wiped and restored factor settings through recover and installed the 20141106-NIGHTLY but its still the same, changing the color of the light confirms that the notification light is still working but does not activate wen it should.
Nevermind, I cleaned all my setting and reconfigured, it solved the problem
Hi friends, how can we root this ROM?
Thanks
As other users in the thread about solks2 CM11, I am affected by thebrandom reboot thread. I thought it might help to let you know that those reboot often occur when using waze (while charging the phone in my car). Sorry to post here but I do not have the 10 required posts to reply in the right thread.
---------- Post added at 11:08 PM ---------- Previous post was at 11:02 PM ----------
Hello,
I also have a bug when trying to use google now via bluetooth (stuck on a screen with "initializing" written). I tried several workarounds from the internet but without success. Some suggest that a2dp should be disabled but I didn't find an option to disable it... Anyone managed to make google now work with bluetooth?
I am unable to record videos, anyone else having this issue?
EDIT: I just updated to the latest NIGHTLY, still unable to record videos, in a week or so I'll go on vacation for the holidays and I really need to record some videos, so if someone knows whats wrong please help me, thank you
Revolted5 said:
I am unable to record videos, anyone else having this issue?
EDIT: I just updated to the latest NIGHTLY, still unable to record videos, in a week or so I'll go on vacation for the holidays and I really need to record some videos, so if someone knows whats wrong please help me, thank you
Click to expand...
Click to collapse
I accidentally pushed some wrong commits. Will push fix today.
solk2 said:
I accidentally pushed some wrong commits. Will push fix today.
Click to expand...
Click to collapse
Thank you, you're a life saver
EDIT: Back from work and what do I get? An amazing update, I'm finally able to record videos, thank you very much solk2.
Q&A for [ROM][OFFICIAL] CyanogenMod Nightly Builds for jfltespr
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.
Before posting, please use the forum search and read through the discussion thread for [ROM][OFFICIAL] CyanogenMod Nightly Builds for jfltespr. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Struggling with CyanogenMod 11
I installed last night with Philz recovery (most recent version), factory reset, wiped cache and dalvic cache first. Things appeared to be running smoothly initially but I realize I don't have any sound (DSP manager crashes when I open it or when I open Apollo). I'm not able to answer or make phone calls. I'm pretty new at this - do I need to update my modem? I know Knox got installed (0x1) and the baseband version says mk2. Is there a ROM that would work better for my phone?Can I install rom that say NAE and NG2? I'm just looking for something that's stable and has great battery life. Or is there something I'm doing wrong with Cyanogenmod?
Here's info in the about phone page:
SPH-L720
11-20141008-SNAPSHOT-M11-jflte
4.4.4
L720VPUEMK2 (baseband)
Kernel 3.4.104-cyanogenmod-gc55a5d6 etc
CPU ARMv7
Memory 1809 MB
Please help.
A second thorough wipe may be worthwhile. Otherwise download a fresh cm copy as the other may have gotten corrupted. Reload and reflash.
garbage914 said:
I installed last night with Philz recovery (most recent version), factory reset, wiped cache and dalvic cache first. Things appeared to be running smoothly initially but I realize I don't have any sound (DSP manager crashes when I open it or when I open Apollo). I'm not able to answer or make phone calls. I'm pretty new at this - do I need to update my modem? I know Knox got installed (0x1) and the baseband version says mk2. Is there a ROM that would work better for my phone?Can I install rom that say NAE and NG2? I'm just looking for something that's stable and has great battery life. Or is there something I'm doing wrong with Cyanogenmod?
Here's info in the about phone page:
SPH-L720
11-20141008-SNAPSHOT-M11-jflte
4.4.4
L720VPUEMK2 (baseband)
Kernel 3.4.104-cyanogenmod-gc55a5d6 etc
CPU ARMv7
Memory 1809 MB
Please help.
Click to expand...
Click to collapse
Hey garbage914, granted it's been several days, just wondering if you got your ROM issues sorted? I don't know much but glad to help in any way possible.
Cant connect to camera
Sent from my SPH-L720 using XDA Premium 4 mobile app
passlogin said:
Cant connect to camera
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I got the same thing when I was using the front facing camera today. Took one picture then FC. Had to reboot to connect again.
Probably the fastest rom iv tried. But WiFi signal comes and go. Some applications close by then self. And the voice recording is terrible.
SIM problems
Is there any way to use CM12 without having a SIM card inserted because it won't allow the phone to connect to any network even though I've ben using my phone on Boost Mobile for almost a year now.
I'm running TWRP and the 2/8 nightly, I've been unable to access my developer options since the flash, even with factory reset before and after flash. Also having issues with the camera, seems to only want to take a few photos before it just stops capturing and force closing, leading to "unable to connect to camera". Any thoughts on the dev options issue?
babyshrimps said:
I'm running TWRP and the 2/8 nightly, I've been unable to access my developer options since the flash, even with factory reset before and after flash. Also having issues with the camera, seems to only want to take a few photos before it just stops capturing and force closing, leading to "unable to connect to camera". Any thoughts on the dev options issue?
Click to expand...
Click to collapse
same thing here I got the rom today and it was working perfectly but then I tried switching to record video and it froze and closed. Now when I try to open it, it say "can't connect to camera" any solution?
Camera Won't Work
Everything was running smooth but then I decided to record a video so after taking a few pictures I switched to video record. It frozee for a second and then closed the program. I clicled on camera again and a message popped up saying:
"Camera error
Can't connect to the camera."
I have CyanogenMod Version:
12-20150226-NIGHTLY-jfltespr
I tried closing disabling the camera app but no luck.
Move from CM12 nightly to Lollipop Stock Rooted
Greetings!
I've been running the Cyanogenmod 12 nightly build 12-20150224-NIGHTLY-jfltespr on my S4 (baseband L720PUFNG2) with ClockworkMod 6.0.4.7 installed. I've been experiencing some battery issues and miss features included in the stock Samsung ROMs, such as a working IR blaster and multiwindow support, and would like to move from CM12 to a stock AND ROOTED configuration. I have a few questions:
1) Where do I obtain the *correct* ROM to flash? I'd like Samsung's stock rooted Lollipop, *if possible*.
2) Do I run TriangleAway FIRST, and then flash, or flash, and THEN run TriangleAway?
3) After I flash the stock ROM, am I safe to recover user apps AND system data with Titanium Backup, or should I simply start fresh, being spring and all?
4) What about KNOX? Will it complain/cause issues/take off and nuke the entire site from orbit?
BTW, I *have* searched these forums, but there's almost an ocean of data to sift through even so, and most of my results date from 2013/2014. I don't want to get this wrong, as this is my only phone, and I've already softbricked for a day (no PIT found!), and want to avoid that happening again if possible.
I'll keep hunting for what I want on my own, but any help you geniuses here can provide would be.... well, helpful.
Thanks!
Did you make a nandroid backup of your stock ROM before you went down the custom ROM route?
meldryn said:
Did you make a nandroid backup of your stock ROM before you went down the custom ROM route?
Click to expand...
Click to collapse
No, and that answer probably means, apart from "do a nandroid backup next time, idiot", that I have to do a full wipe and can't restore my user data. I'm actually fine with that, as I don't really have any information on my phone that isn't already attached to my Google account or otherwise stored in the cloud.
What are the consequences beyond losing my data because I didn't do a Nandroid backup, if any?
And where do I get the stock ROM, etc.?
I see a bit of a green tint after latest updates (03/08 and 03/11).
I see a bit of a green tint after latest updates (03/08 and 03/11). This is not hardware issue. Is there anyone who noticed same problem?
occulus said:
No, and that answer probably means, apart from "do a nandroid backup next time, idiot", that I have to do a full wipe and can't restore my user data. I'm actually fine with that, as I don't really have any information on my phone that isn't already attached to my Google account or otherwise stored in the cloud.
What are the consequences beyond losing my data because I didn't do a Nandroid backup, if any?
And where do I get the stock ROM, etc.?
Click to expand...
Click to collapse
well not making a nandroid could be bad because you could have a bad flash and soft brick and all u have left is download and/or recovery mode and u can always go back to having a functioning phone with your backup. And plus running cm12 u could restore your back up and update your prl and profile then restore your cm12 or do the same for a gps lock. Always make a back up man. U can get the stock touch wiz by either searching the forum for it which I'm sure it's here or u can go to sammobile type in sph-l720 and download the current stock tar file then re root and make a back up of stock before u even delete any bloat that way u will always have a completely stock back up.
http://howto.highonandroid.com/samsung-tutorials/how-to-extract-stock-recovery-from-samsung-firmware
Sent from my SPH-L720 using XDA Free mobile app
Installed the 3/28 nightly last night and really digging it. I don't use it as a phone so I won't be able to test that aspect. About the only bug I've come across is that Falcon Pro 3 Twitter client can't play Youtube videos inside the app. Works on stock Lollipop. Not a biggie but thought you guys might want to know about it. NFC seemed to work great when I used it during initial setup. Camera pics and video looks great. Will try testing Bluetooth with file transfers to Nexus 7 (2013) tablet later. I'll try to report any other issues I encounter in this thread. Thanks for the really excellent work.
Edit: Well, I just played a YouTube video within Falcon Pro 3 (from The Verge Twitter account) and it played flawlessly. So that last attempt was either a borked link or who knows?
I am having the same issue with 13., moving back to 12 trying a new download.
junior92x said:
same thing here I got the rom today and it was working perfectly but then I tried switching to record video and it froze and closed. Now when I try to open it, it say "can't connect to camera" any solution?
Click to expand...
Click to collapse
Haven't found one other than buying a new phone haha! Still using the S4 but can't figure out the problems
I've seen this mentioned in other places before, other threads and in the r/motox subreddit, about how the open GAPPS package apparently flashes the Google Dialer over the stock one, and it doesn't work with the Pure? Which is what causes the reboots whenever I try to make a call or, presumably, get a call, which until now I chalked up to random reboots in CM13.
So I've seen a bunch of posts about it, but none that explain how to actually fix it? Am I doing something wrong from the start?
Bonus question, I've been having radio problems on almost every AOSP rom I flash, either Wifi doesn't work upon booting and it persists in other ROMS or cell service is out (even though LTE data works fine). Is the radio (which I assume is the same as the "modem") included in each ROM package and is replaced every time you flash a new one, or does it persist in some system directory cross-firmware?
There are so many posts on how to fix I'm not sure how you could miss them. Set as default or uninstall.
lafester said:
There are so many posts on how to fix I'm not sure how you could miss them. Set as default or uninstall.
Click to expand...
Click to collapse
Set what as default? Or uninstall what? When I look in the apps list all I see is "phone". Nothing under the name google dialer or anything. It's just confusing, I didn't have this problem on other phones.
Sorry for the double post but I figured instead of making another thread I'll continue asking here, I'm STILL having cell issues, no matter what ROM I flash, stock or AOSP, or any of the radios I can find around the forums, whether it be with the February security update or not, I'm still not getting a connection. In fact once I flashed a new modem, I went from not being able to send texts etc. but able to get LTE data, to getting no connection at all. I'm totally lost, this is the second time it's happened I have no idea what to do. Happens in every single rom.
Last time it was fixed once I flashed from stock (which I had in turn flashed to try to get rid of the problem) to CM13 I think. But it was totally random, I have a feeling it didn't even have anything to do with the ROM itself...
Google searching: "Google Dialer reboots when making a call" >
http://android.stackexchange.com/qu...s-when-making-or-receiving-a-call-nexus-6cm13
https://www.reddit.com/r/cyanogenmo...cm_13_nexus_5_soft_reboots_when_a_phone_call/
Even from Open GApps own FAQ page:
https://github.com/opengapps/openga...boots-when-i-receive-or-make-a-phone-call-why
Thanks, I honestly dunno why I couldn't find that before. At first I wasn't even aware it was actually called the "google dialer" so I was just googling "phone app reboots after flash/root/etc" and obviously it wasn't turning up many results. But the stock rom rooted debloated thread had the instructions at the bottom, now I know. Whoops. Like I said, just really confusing coming from other phones where everything mostly just worked....
The baseband is still perplexing me though, in the bootloader under baseband it says <not found>. I'm keeping on trying to flash different stock roms to see if I get lucky.
EDIT: so I think flashing the modem at the SAME TIME as a new ROM might be the key? I think I saw something about that on some random obscure post and tried it out and bam, it worked like a charm. Anyway hopefully that works again when I flash to something new
Hi everybody. Today I flashed ops beta6 coming from Resurrection remix. Since I've tried, I couldn't get past the screen on Google setup saying "just a sec.." . Seems like I'm the only one having this problem, cause I can't find any similar post/thread.
Please help me!
tompere96 said:
Hi everybody. Today I flashed ops beta6 coming from Resurrection remix. Since I've tried, I couldn't get past the screen on Google setup saying "just a sec.." . Seems like I'm the only one having this problem, cause I can't find any similar post/thread.
Please help me!
Click to expand...
Click to collapse
Hello, why not posting your question in the related thread https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-beta-1-android-oreo-t3710003 and search for answers?
You did not mention which steps you take, sounds for me you coming from ressurection remix and just flash the ob6 rom without wiping etc? But I'm sure you did not, so please give exact steps to reproduce the issue.
And read some pages back in the linked pages thread, it's been discussed partially
why not posting your question in the related thread https://forum.xda-developers.com/one...-oreo-t3710003 and search for answers?
Click to expand...
Click to collapse
Hi, I didn't post on the rom's thread because now it's a "every rom i try" problem. It happends every time i clean flash a new rom (I've tried xXx, OOS stock beta 6, OOS stock stable and crDroid), and I've never got past the langage selection screen.
My steps are:
- Boot to Recovery, currently twrp clockworkx 3.2.1
- Wipe: Data, Dalvik & ART cache, Cache and System
- Install Rom
- Install Gapps (if needed)
- Install magisk (I've tried not to, nothing changes)
- Reboot
I'm really confused, a problem behaveing like this, seems related to the phone it self rather than to the single roms.
What would you suggest?
OT. If you find that this post it's not getting anywhere, I might follow your advice and post on OOS beta thread.
tompere96 said:
Hi, I didn't post on the rom's thread because now it's a "every rom i try" problem. It happends every time i clean flash a new rom (I've tried xXx, OOS stock beta 6, OOS stock stable and crDroid), and I've never got past the langage selection screen.
My steps are:
- Boot to Recovery, currently twrp clockworkx 3.2.1
- Wipe: Data, Dalvik & ART cache, Cache and System
- Install Rom
- Install Gapps (if needed)
- Install magisk (I've tried not to, nothing changes)
- Reboot
I'm really confused, a problem behaveing like this, seems related to the phone it self rather than to the single roms.
What would you suggest?
OT. If you find that this post it's not getting anywhere, I might follow your advice and post on OOS beta thread.
Click to expand...
Click to collapse
I solved my problem formatting the whole phone from twrp. I'm still confused on what caused this problem. Thanks anyway.
tompere96 said:
I solved my problem formatting the whole phone from twrp. I'm still confused on what caused this problem. Thanks anyway.
Click to expand...
Click to collapse
You got it. It's mostly cause of the internal storage you did not format. That's a common problem.
Stuck with 'Just a sec' after Factory reset
Hi All,
I have an One Plus 5 phone. I am getting it exchanged for One plus 6T. The delivery is scheduled today. I did a factory reset and when I reboot - I got stuck with this 'Just a sec' screen after language. It doesn't get past this. I tried ' Recovery boot' and 'Fast boot' Nothing is working. I searched all over internet. I can get the calls but cannot do any other thing. I am stuck with this ' just a sec ' screen for a like one hour now. Please please please help me out.
Facing same problem
lakshmla said:
Hi All,
I have an One Plus 5 phone. I am getting it exchanged for One plus 6T. The delivery is scheduled today. I did a factory reset and when I reboot - I got stuck with this 'Just a sec' screen after language. It doesn't get past this. I tried ' Recovery boot' and 'Fast boot' Nothing is working. I searched all over internet. I can get the calls but cannot do any other thing. I am stuck with this ' just a sec ' screen for a like one hour now. Please please please help me out.
Click to expand...
Click to collapse
i had this same issue solved by flashing nano or pico gapps
try this
Facing same problem with my htc 10 (pme)