Related
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
My boss rooted his LG G2-D02 and installing CM 12.1 in the process. Now, after knowing that CM 13 was already released, he downloaded a copy of it and immediately flashed it onto his phone. He got a problem with Gapps and DL-ed a problematic version which caused the notification,"Unfortunately, Setup Wizard has stopped" to pop up repeatedly. We had tried following a few advices from this website but to no avail.
1.) We already tried using Force Stop and Disable under Apps->(Show system apps)->Setup Wizard (CM). I had also tried giving it app permissions, but all app permissions were already available.
2.) The only option is to flash CM 12.1 back again but it can't be done. My boss set the default recovery app to Cyanogenmod's own recovery program, which had limited functions, so I can't
also use TWRP ATM.
3.) My boss also tried something on ADB but to no avail
4.) Factory reset didn't also solve the problems.
I'm almost running out of solutions... Perhaps, I can use a helping hand from brighter minds in this community.
TIA
I'm using cloudyg2 v3.3 because cm13 has got a lot of bug for example
-I can't proceeded to music
-systtem has stopped once a hour
-I can't close touching vibration
I can't remember now but cm13 has got really much bug (yeah my english is very bad,I know this)
Now system is stable and battery is very very good but still İ can't scretch to music
So i just woke up, opened my Snapchat, to realize my camera is really dark, and i mean really dark. Unless i point the camera at a light source i can't see anything, just black. The weird this is that it's the same story inside the camera app, and even the front facing camera. Both of the cameras are really dark, i've tried delting the cache, rebooting, wiping my phone, and installing Cyanogenmod again, only to see the same **** over and over again. Any tips on how i can fix this?
Facing the same issue. When in capture mode it's dark and video mode it's completely bright. I am using the 11/18 NitrogenOS with CameraNX4.1 Fix.
Same. On npf10c, started immediately after flashing the pixel navbar fix through FlashFire. Wiping cache didn't do anything.
I have the exact same problem. I'm on 11/18 nitrogen OS as well. It was perfectly fine when I first flashed the ROM but after a day it went dark. If anyone has a fix please let us know
So recording video is broken, it gets super BRIGHT, but for some reason taking a picture with flash on fixes the problem temporarily. Otherwise though this is persistent.
Just got this Nexus and the camera was working fine. I'm on preview with French fk.. last night it just went dark after working fine. Funny it started at the same time
I flashed the NDB91K vendor and it fixed my black camera issue. You get the security message on boot, but the camera is working fine for me
Having the same problem here. Already tried wiping cache, reflashing vendor and dirty flashing Nitrogen. I am on 11.18 Nitrogen release. So far nothing seems to fix it.
Identical problem. I JUST flashed the stock boot.img and it fixed the problem. Going to re-root and flash elementalx and will report back.
yeah flashing the previous vendor fixes the issue. Not sure why that caused the problem
God ****ing dammit I just realized why this may have been happening to me. Franco is not currently supported for 7.1.1. And a user on reddit I spoke to said he was using flash while on 7.1.1.
That's probably what's causing this issue.
Kill me.
Even with fk installed I was able to use the camera just fine.... I ran on it for a couple of weeks even on dp
Running the 11/18 build of Nitrogen OS with banks GApps and having the same issue. Clean flashed. Flashing the latest image fixed it.
ThatInsaneHobo said:
God ****ing dammit I just realized why this may have been happening to me. Franco is not currently supported for 7.1.1. And a user on reddit I spoke to said he was using flash while on 7.1.1.
That's probably what's causing this issue.
Kill me.
Click to expand...
Click to collapse
Using Franco R37 with 7.1.1. No issues here :fingers-crossed:
Same here
Damn it. I just installed the pixel XL ROM and I'm getting dark camera and bright video. This is like way after the original poster too. How come no fix?
The problem still persists , i got the same issue and that too after opening snapchat , i really don't know what to do, any help , how can i get back to old kernel again?
Do you try flash other rom?
Does anyone have a link for the vendor image?
Sent from my Pixel XL using XDA-Developers Legacy app
Hi,
in my spare free time I compiled a new unofficial LineageOS 14.1 ROM on my beloved Phenom II system with ECC RAM and made it available to you for 90 days from
https://www.filefactory.com/file/5fqmz223n9gx/lineage-14.1-20170403-UNOFFICIAL-SonyLOS-kugo.zip
https://www.filefactory.com/file/121p40o8v8gb/lineage-14.1-20170403-UNOFFICIAL-SonyLOS-kugo.zip.md5sum
The ROM can be installed through a recovery like TWRP. I also applied some modifications, in particular:
- the SonyLOS kernel has been replaced with the Sony AOSP version which seemed to be more up to date
- using some 7.1 binaries of Sony AOSP instead of the 7.0 binaries used earlier enabling some more features (?)
- replaced the LineageOS camera with the Simple Camera app
- integrated Total Commander, Apollo music player v2, SELinux permission changer and Viper4Android apps since I need them
Consequently,
- patchlevel now is March 5th, 2017
- the fingerprint sensor now seems to be usable to unlock your device
- the FM radio works (however, you have to manually scan through the stations once because automatically finding the stations initially still does not seem to work completely)
- the selfie camera image no longer will be upside down (seemed to be an issue with the LineageOS camera app, also will work correctly with i.e. Focal if you prefer a sophisticated app instead of Simple Camera)
- I can now use Apollo again as I did on the Z1 compact with CM 12
- the bass boost and equalizer are back with Viper, you just need to invoke the SELinux changer on the rooted device and install the drivers initially through Viper itself
Thanks fly out to Sony AOSP, SonyLOS and the app providers. Feedback is also very welcome.
Regards,
jtk_de
@admin: Could we please move this thread and my previous one to the ROM section ? I'm still not allowed to post something there
Great to see you're still updating your ROM. Don't understand why you upload at filefactory (sloooow download) instead of androidfilehost for example. Will flash your ROM tomorrow.
- should I flash a stock ROM first or does it not matter which version I'm coming from
- what do I need the .md5sum file for?
- gapps are not included, right?
I tried to use androidfilehost but my uploads got interrupted so I had to stick with filefactory for now. You don't need to flash the stock ROM first, just wipe the system, cache etc. partitions in your recovery and flash the .zip.
The md5sum checksum file is there to ensure the ROM integrity and is not needed for the flash, however, TWRP optionally can read it and veryify that the ROM has been correctly downloaded and copied to your phone's storage. Gapps is not included since I use alternative apps, hence it must be installed separately.
Root access is integrated already and can be controlled via the developer settings. The only issue I experienced so far is that the volume cannot be altered yet during phone calls
I don't get viper4android to work. I install the drivers, reboot my device and then viper4android prompts me to install the drivers again. Am I doing something wrong?
Micka84 said:
I don't get viper4android to work. I install the drivers, reboot my device and then viper4android prompts me to install the drivers again. Am I doing something wrong?
Click to expand...
Click to collapse
You need to enable root first and start the SELinuxModeChanger installed with the ROM and set SELinux to "Permissive". Then the Viper drivers can be installed which can take quite long (a minute or so). If an Android dialog pops up because of this confirm that you would like to wait longer. Then reboot as indicated and enjoy the bass
That worked for me thank you
Hey,
many thanks for that ROM. Unfortunately i end up in a never ending boot animation. If i get in recovery (TWRP) and tell him to reboot, it tells me that no OS is installed. Any hints how this can be solved?
Thanks for any advice!
dreadavi said:
Hey,
many thanks for that ROM. Unfortunately i end up in a never ending boot animation. If i get in recovery (TWRP) and tell him to reboot, it tells me that no OS is installed. Any hints how this can be solved?
Thanks for any advice!
Click to expand...
Click to collapse
Hi!
I think there aren't any os on your device, thats wha twrp sad that... because, your systems encrypted. You could remove it. Try to flash again twrp from fastboot, than clear cache ( fastboot format cache ) and userdata ( fastboot format userdata ) from flashtools too. After that boot to twrp, than you could mount system, than flash the whole cm rom again. After that, i think it will boot correctly.
lba810701 said:
Hi!
I think there aren't any os on your device, thats wha twrp sad that... because, your systems encrypted. You could remove it. Try to flash again twrp from fastboot, than clear cache ( fastboot format cache ) and userdata ( fastboot format userdata ) from flashtools too. After that boot to twrp, than you could mount system, than flash the whole cm rom again. After that, i think it will boot correctly.
Click to expand...
Click to collapse
Thanks for the hint. Did what you said, but i cant mount system in recovery. It cant be selected in the list. Any other suggestions? Ok solved it. had to flash stock rom and boot.img before the steps you asked me to try. Thank you!
Thank you for putting this ROM together! There are the following problems on the OmniROM:
1. Incall speaker volume is not controllable
2. Slight incall echo on receiving side
3. Double tap to wake doesn't work
Is this still the case for your Lineage ROM?
avion540 said:
Thank you for putting this ROM together! There are the following problems on the OmniROM:
1. Incall speaker volume is not controllable
2. Slight incall echo on receiving side
3. Double tap to wake doesn't work
Is this still the case for your Lineage ROM?
Click to expand...
Click to collapse
1. Yes, the volume can't be changed during phonecalls
2. Didn't notice any echos so far
3. True
Could you try uploading to mega.nz? FileFactory is so slow
minimum Brightness
Hey!
i was just wondering if its possible to lower the minimal brightness a bit more. because minimal brightness is quite bright still. Im using this ROM for a few days now. Everything works pretty fine, but the battery life is a bit short for what i was expecting. If i dont use extreme battery saving mode its always around 24 hours. i barely do phone calls and i use it not very intensively... Highest Consumer is standby with 5%, which i think is wierd, isn´t it?
:good: Kudos. Everything seems to work well aside from the Bluetooth Audio cutting out after a few minutes. Overall I am really happy with it - happy enough that it's my daily driver.
Hi!
ROM will be better and better. Thanks.
Battery charging speed a bit slow, and if I'm using a mobil net, it's draining a little fast, plus in the evening, with wifi on, it goes down nearly 5%>. Camera is good. But, im using open cam software from google play. Fingerprint sensor working good, just a little hard to configure it. I'm using substratum theme engine, and i can theme most of the base and google apps. ( Except fingerprint sensor, with themed settings, the fingerprint setup screen cracked... but inthinknits theme problem ) And about bluethooth.. yes, it's dropping the connection after a few secs. But, if you left it, then reconnect automatically and just after that, it goes good. Until you turn it off. I used a sony sbh70 wireless headset with power amp.
And echo sound in calling. I can't hear echo, but other peoples in line, they sad it. They hear onselfs twice.. :/
If you would like it, maybe i can upload a logfile ( with matlog ) about the bluethooth problem.
Anyway, thanks foe thiese rom for our x compact.
It's good to see some other people are using the ROM and testing things that I can't test
According to my own experience battery lifetime is around 2-3 days when surfing via wi-fi, listening to music and calling from time to time. Battery charging with the Sony AC adapter coming with the phone is quite quick compared to the Z1C although the battery capacity is higher.
If I make another build I'll upload it to some faster provider though.
hello all,
give it some news there? Last entry April 2017.....
Hi all, are there some updates? I love Lineage OS
I'm wondering why there isn't an official build for the Xperia X Compact yet ? If I google "kugo lineageos" I get a hit for a stats page:
https://stats.lineageos.org/model/kugo
Which just says the page isn't rendered yet, but obviously someone has been devoting his/her time to the kugo. What could be the hold up? Same goes for the lack of other roms btw. It seems Sony is quite open towards the community but somehow this hasn't resulted in the overwhelming amount of roms I was hoping for ... It's quite underwhelming in fact. Could it be not enough (knowledgable) people own an Xperia X Compact ?
harryharryharry said:
It seems Sony is quite open towards the community but somehow this hasn't resulted in the overwhelming amount of roms I was hoping for ... It's quite underwhelming in fact. Could it be not enough (knowledgable) people own an Xperia X Compact ?
Click to expand...
Click to collapse
Sony gives us a sliver of what is needed for AOSP to run, camera, bluetooth, wifi, and radio band stuff all has to be manually made to work. The z3 line was the ONLY xperia line to ever get mainstream AOSP support from devs. If you bought your xperia thinking Sony's AOSP program was good you were sadly mistaken.
Hello. This is the only place where I think I can find ann answer to this bug.
The issue: all OnePlus 8 Pro cameras work normally with every single app, except the stock camera app. I can take photos and make videocalls, use instagram, whatsapp, etc. All cameras are working fine. Even face unlock, But the stock camera app opens in a black screen, then 3 seconds later, closes (and you can find it on the recent apps drawer.
What I did so far to debug this:
- Wiped the cache
- Wiped the cache and data for the camera app and the camera service
- Did a clean install (factory reset) on OOS 11
- Did a clean install (factory reset) rolling back to OOS 10
- Upgraded to a beta version on OOS 11.
- Did a clean install of OOS 11 using MSM Tools
- Updated the camera app to a beta version
- Updated the camera service to a beta version
All this with stock software.
Absolutely nothing that I do makes the stock camera app to work. I can assume that this is not a hardware issue, since all the cameras work on any app except the stock camera app. But if it's a software issue, why even wiping with msm tools didn't fix it? I really can't find an answer to this.
Has anyone ever faced this bug? I'm almost selling my oneplus 8 pro as defective since we don't have official oneplus support in brazil.
Thanks in advance for any tips!
If you've used msm to go back to stock then it must be a low level driver that's not working..
Haven't got a clue how that could be fixed though, i would reach out to OnePlus.
If you don't fancy that, the only other thing you could maybe try is one of the custom ROMs that now has the OOS camera baked into their ROM.
It's a long shot but perhaps that may work and may invoke a change that's inherited by the OOS system..
Sorry it's an odd one.