• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM][5.1.1][OFFICIAL] CyanogenMod 12.1

Keep the lowram flags?

  • Yes

    Votes: 57 68.7%
  • No

    Votes: 26 31.3%

  • Total voters
    83
  • Poll closed .
Search This thread

smiskkissen

Senior Member
Sep 16, 2009
88
5
Came from cm11 and installed 03-07 cm12 fully wiped. Works flawless for now. Camera, netflix etc. no problems. Good performance too.

Going to be my daily driver for now. Afaik offline charging is the only remaining bug.
Thanks Ziyan for the great work!!
 
  • Like
Reactions: ramosroger

TheMan0790

Senior Member
May 22, 2011
844
430
I am pretty lazy to go about clean flashing to get the camera working again...does anyone possibly have a means of fixing the camera not showing up that does not involve a clean flash?
 

alboz83

Senior Member
Feb 2, 2011
535
82
Cagliari
Came from cm11 and installed 03-07 cm12 fully wiped. Works flawless for now. Camera, netflix etc. no problems. Good performance too.

Going to be my daily driver for now. Afaik offline charging is the only remaining bug.
Thanks Ziyan for the great work!!
There isn't the only remaining bug because occasionally Camera get FC, green line is still present, 1080p video record are not fluid, charging text remain on the lockscreen.
Then i found other bug, it's impossible to change from 3g to 2g, remain always in 3g
 

smiskkissen

Senior Member
Sep 16, 2009
88
5
There isn't the only remaining bug because occasionally Camera get FC, green line is still present, 1080p video record are not fluid, charging text remain on the lockscreen.
Then i found other bug, it's impossible to change from 3g to 2g, remain always in 3g
That may be true. I don't really record video with my phone so it doesn't concern me, but you're right. There are some more bugs left
 

varadparulekarofficial

Senior Member
Nov 25, 2014
89
25
Mumbai
There isn't the only remaining bug because occasionally Camera get FC, green line is still present, 1080p video record are not fluid, charging text remain on the lockscreen.
Then i found other bug, it's impossible to change from 3g to 2g, remain always in 3g
I didnt get you.. Its impossible to change from 3G to 2G, and always remain in 3G...?
Whenever you wish to change your network mode just dial *#*#4636#*#*
and select whichever you want-
GSM Only - Only 2G
WCDMA Only - Only 3G
WCDMA preffered - 3G/2G..

Sent from my Galaxy Nexus using Tapatalk 2 Pro
 

alboz83

Senior Member
Feb 2, 2011
535
82
Cagliari
I didnt get you.. Its impossible to change from 3G to 2G, and always remain in 3G...?
Whenever you wish to change your network mode just dial *#*#4636#*#*
and select whichever you want-
GSM Only - Only 2G
WCDMA Only - Only 3G
WCDMA preffered - 3G/2G..

Sent from my Galaxy Nexus using Tapatalk 2 Pro
Yes i change from *#*#4646#*#*, but from menu don't work.
 

TheMan0790

Senior Member
May 22, 2011
844
430
Went ahead and clean flashed 03/07 build - camera is all good. Also, anyone notice that 5.1 is pushing out to AOSP? Supposedly one of the fixes is that the notification LED blinks again while the phone is in silent mode...this is probably the one thing I am waiting for in this update.
 

garrymar

Senior Member
Mar 12, 2015
55
49
@Ziyan, thank you very much for maguro maintenance! Thank you for bringing CM 12 to maguro!

What is the best place to report problems related to the builds (the forum, CM JIRA)? I'm sure many problems may come from upstream. Thank you in advance!
 
Last edited:

eternal404

Member
Feb 16, 2011
19
15
I did a full wipe and flashed the latest build. LP asks for a password upon boot. Whatever I enter it will say it is correct and claim my data is corrupt ("Decryption unsuccessful") and offer to perform a factory reset.
I suspect it has something to do with f2fs support (looks like it cannot read /data) but I read here that f2fs works for /cache and /data. My partitions are as follows: System (ext4), cache (f2fs), data (f2fs).
I tried with a different kernel (DirtyV R11) and got the same result.

Any ideas? Should I turn /data into f2fs (and then how can I restore my /data nandroid) ?
 

alvarjo

Member
Jan 1, 2012
27
3
Hello,

I have connected my smartband BLE to the GN with no problem, but when it lost its sync becuase it is far away from my phne, it doesnt recover the conection. I have restart bluetooth to get it, but mnany time I don't realized that there were any lost of sync.

I don tknow if this is a bug related to Bluetooth or the program smart connect form Sony, but in CM11 worked
 

wbedard

Senior Member
Jul 22, 2010
478
411
Any SELinux enforcing kernels for this ROM?

@Ziyan , et al.

Is this ROM know to work when booted with SELinux in enforcing mode? If so, would someone please provide a pointer to the kernel used to test/confirm this? Ziyan, as you have time, could you provide a build of your kernel configured to boot in enforcing mode? I looked around and most all the LP kernels for this device (except freshgiammi's) seem to boot with SELinux in permissive mode. Thanks in advance for your consideration of this request!

R/
wbedard
 

Top Liked Posts

  • There are no posts matching your filters.
  • 311
    cyanogenmod-10-banner-600.jpg

    For instructions about installing or building for maguro, see the CyanogenMod wiki page.

    The latest builds are available at http://get.cm/?device=maguro.

    Known Issues page for the Galaxy Nexus (GSM) (not updated yet)

    Google Apps can be found at http://wiki.cyanogenmod.org/w/Google_Apps - beware that if you choose OpenGApps, only the pico version will fit, unless you change your partition sizes!

    Want to support development? You can consider donating, I spent countless of hours with this :)

    XDA:DevDB Information
    CyanogenMod 12.1, ROM for the Samsung Galaxy Nexus

    Contributors
    Ziyan, MWisBest, Everyone else who helped me: AOSP, Hashcode, ...
    Source Code: https://github.com/CyanogenMod/

    ROM OS Version: 5.1.x Lollipop
    ROM Kernel: Linux 3.0.x

    Version Information
    Status: Snapshot

    Created 2014-12-01
    Last Updated 2016-07-20
    92
    After countless unofficial builds and hours spent with this, I am happy to announce that maguro is now considered stable enough to get official CM12.1 nightlies :) moving on to CM13 after I find some time, which will hopefully become a nightly soon as well, since the hard part of the work is now done ;) updated the OP accordingly (the builds in the downloads section will stay up for a couple days, just in case there's a problem we need to compare with an older build).
    52
    Sorry for not being active lately guys, I was busy, as my new semester just started :( but don't worry, I didn't forget my plans for this, I'll release a new build soon :)
    48
    New build up. Changes:
    - reclaimed ~6 megabytes of userspace RAM
    - enabled video stabilization, exposure and whitebalance lock in the camera HAL (our ducati supports these, but it's not advertising it! what a *****...)
    - disabled dex2oat watchdog (this should make the optimizing apps dialog on every boot disappear, and hopefully fixes installing large apps)
    - synced with CM repos (01/01)

    I also switched back the default I/O scheduler to BFQ - I hope that the lockups some of you experienced were caused by an older CM bug (they made some BFQ-related platform changes).
    If anyone encounters another one, and wants to switch back, simply change sys.io.scheduler to cfq in /system/build.prop. Alternatively, use your favorite kernel settings app to change to CFQ on boot (but I'd recommend changing build.prop instead - I think Kernel Adiutor has a nice interface for editing it). And remember: if it locks up again, no need to remove the battery: just hold down the power button for at least 10 seconds, and the device will turn itself off.

    will 13 come :fingers-crossed:
    As soon as I'm satisfied with the results (currently, I'm not - looking at you, memory management).

    The folks over at the S3 camp are enjoying a nearly bugfree CM13 with 3.0 kernel. Funny if you look back at codewokx swearing while getting CM9 to work (camera was a pain).
    Facts:
    - they received official KitKat update with proper drivers and stuff, tuna only got 4.3 (Samsung updated their EGL blobs for KitKat, meaning they didn't have to port over to a new kernel like we did, and didn't have to switch to a newer camera and domx hal)
    - there's at least 10 people actively maintaining it over CM
    - their user and developer community is at least 10x bigger

    I can't express how hard and time-consuming it is to maintain tuna with only two active developers :(
    48
    Just a heads up, the flashlight toggle has been fixed, but CM's ffmpeg **** broke the domx, so video playback is now gone, I already have the fix composed in my mind (lol), just need to test it... my finals are here, so I'm pretty busy now, but I'll try to fix and upload a new build in the next few days :)