{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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
Build instructions
Update: as of 2016/01/03, everything needed is merged, so simply follow the official build guide.
If you don't want to or can't (ex. remote servers) use extract-files.sh, simply clone proprietary_vendor_samsung into vendor/samsung.
wow this is great @Ziyan truly appreciate your awesome work!
Testing it now.
It's actually running really really well! Posting this from the 1130 build now! One thing that did work on FML and just refuses to on cm12 is getting the APN to stick, it says "APN settings aren't available for this user" (which I think it also said in FML but still stuck after it was saved), otherwise everything else has been mentioned in the op as far as quirks are concerned
I'm getting much worse battery life than with the last CM11 nightly. Overnight battery drain was 3.7%/hour, compared to around 1%/hour with CM11. According to GSAM, the main issue was system(mediaserver) at about 94% of battery usage. No media was being served, so far as I can tell. EDIT: battery life often improves for me a day or two after installing a new generation, so I'll see if it gets better today.
I notice that the google bar at the top of the page always has: Say "OK Google." My Nexus 5 running stock doesn't have this.
It's also much laggier than CM11.
Video works with NuPlayer unchecked in Developer Options. Specifically, I could play video with MX player.
Possibly related to camera not working, the flashlight doesn't work. I only tried turning it on with quick settings.
No crashed so far and no app problems other than camera.
Tap and Go setup (against my N5), worked properly. It didn't work on FML.
I'm testing without a SIM at the moment, just wifi.
Thank you Ziyan
I had my SIM fried somehow after i flashed the rom yesterday, I had to replace the sim card today with a new one, the old one is toast.
It happened during "cellular network setup", it wanted my pin number, as soon as i entered it it was asking for my puk number.
Typed it in, things finished but without network connectivity, had the no sim card sign on the statusbar.
Could it be something connected to the rom or it was just my sim card time to go?
Cheers
Just want to say thanks!
Don't have enough posts to be allowed to post on the CM11 thread, so doing it here.
Ziyan,
Thank you so much for your work on this and I am looking forward to the first monthly CM12!
foosion said:
I'm getting much worse battery life than with the last CM11 nightly. Overnight battery drain was 3.7%/hour, compared to around 1%/hour with CM11. According to GSAM, the main issue was system(mediaserver) at about 94% of battery usage. No media was being served, so far as I can tell. EDIT: battery life often improves for me a day or two after installing a new generation, so I'll see if it gets better today.
I notice that the google bar at the top of the page always has: Say "OK Google." My Nexus 5 running stock doesn't have this.
It's also much laggier than CM11.
Click to expand...
Click to collapse
Try turning off ok google detection from the launcher settings - also, if you use the default launcher, set the app drawer animation to "none", because CM forgot to update that part of launcher to lollipop - they left in the animation from 4.4, so it's laggy and ugly. I just submitted the patch set to fix that, they merged it already so the next build will have this set by default.
Also, if you manage to break camera or video playback, I noticed it tends to leave the video processing part of the CPU active all the time until you reboot, so try that out too
As for the lag, it should improve over time.
flip360 said:
I had my SIM fried somehow after i flashed the rom yesterday, I had to replace the sim card today with a new one, the old one is toast.
It happened during "cellular network setup", it wanted my pin number, as soon as i entered it it was asking for my puk number.
Typed it in, things finished but without network connectivity, had the no sim card sign on the statusbar.
Could it be something connected to the rom or it was just my sim card time to go?
Cheers
Click to expand...
Click to collapse
There's no way a ROM could to that
is the camera wb (white balance) fixed?
Same problem here with PUK.
you could collaborate with @MWisBest to solve the basic problems
blacktomcat said:
you could collaborate with @MWisBest to solve the basic problems
Click to expand...
Click to collapse
They already collaborate I think
Ziyan said:
Try turning off ok google detection from the launcher settings - also, if you use the default launcher, set the app drawer animation to "none", because CM forgot to update that part of launcher to lollipop - they left in the animation from 4.4, so it's laggy and ugly. I just submitted the patch set to fix that, they merged it already so the next build will have this set by default.
Also, if you manage to break camera or video playback, I noticed it tends to leave the video processing part of the CPU active all the time until you reboot, so try that out too
As for the lag, it should improve over time.
Click to expand...
Click to collapse
I rebooted and recharged about two hours ago and battery is draining at 1.7%/hour (including listening to music, not just on idle). While it's usually a mistake to rely on short time periods, the prior drain could well have been due to breaking camera and video playback. I'll continue to monitor.
I'm using the google now launcher and like ok google detection. If I get down to similar idle battery drain as on CM11, I'll leave detection on, otherwise I'll test with it off.
I'd hope lag would improve as we go beyond early testing
Thanks
EDIT: battery drain on idle is going down a bit, suggesting your diagnosis of broken video leaving the CPU active was correct.
blacktomcat said:
you could collaborate with @MWisBest to solve the basic problems
Click to expand...
Click to collapse
For those who don't know, we are getting Lollipop on GN because of these 3 people: @Ziyan , @freshgiammi , and @MWisBest. Lollipop FML was only possible because of those 3 people. Same thing applies for CM 12. It's not like they were working separately. So all 3 are due equal credits for making it work for us.
of course thread subscribed and waiting for the amazing work I'm sure ziyan will do :fingers-crossed:
changelog
It would be possible to have a small changelog as they come out new beta?
@Ziyan thank you for your work!
xaifer said:
It would be possible to have a small changelog as they come out new beta?
@Ziyan thank you for your work!
Click to expand...
Click to collapse
look at his git and on review.cyanogenmod.org
Same bug with PUK
Ok, I don't know which information matters but:
I'm in Germany.
Steps before flashing new ROM from the 30th:
-> wipe cache
-> wipe system
-> wipe dalvic
-> flash rom (everything from cwm)
While trying to flash gapps i got error code 6 (Which i found out later was a buggy version of CWM (6.0.4.7)) but I didn't care and rebooted.
Everything seemed to work, but a few seconds later he asked for the PIN (like always).
Typed PIN correctly, after the FIRST try, the phone asked for the PUK.
Now, after flashing a newer CWM and the most recent cm-11 nightly + gapps ... at least everything works again, except for the SIM cause i can't find my PUK ... well, gonna buy a new prepaid tomorrow. Still an interesting bug ... does anybody know how this could happen? Would be nice to use Lollipop, even if it's bugged as hell ^^
edit: Without SIM, the ROM looked awesome. I had no lag and any app worked. BUT the home button did not. ^^
Is this running the newer GPU drivers?
Has anyone tried lollipop minimum gapps yet with these builds?
http://forum.xda-developers.com/showthread.php?t=2943330
Related
Hello XDA,
I just tested the new Cyanogenmod 7.2 RC1 (if you don't know: It could be found at the cm website for quite a while now Cyanogenmod, device page, look out for GSM /CDMA . I am pretty thrilled (as always) by it. I really like the ICS features like the lockscreen and the animations or, besides, integrated network debugging. I mean this is not new at all (adb wireless for example) but it's an intelligent feature to integrate into the rom (especially as a developer). Its pretty good.
What do you all think about this rom? Have you already tried it?
The rom is good. I'm waiting for the next nightly release.
I had some problems with this nightly ... it forces many closes and reboots. Before installation i did a full wipe, cleared cache.
Now i switched to DK ICS Rom again.
But there i got problems too. Formatting /system in CWM manually solved my problems for the ICS-ROM. Perhaps someone could test, if it helps for problems on 7.2-nightlies too.
I'm very satisfied with it I'm using it since the release day and it's working flawless. Very stable no FC or anything like it. The animations and the ICS lock screen is what I really like also the performance is slightly better (I didn't benchmark it but I just have this feeling )
rschle said:
I had some problems with this nightly ... it forces many closes and reboots. Before installation i did a full wipe, cleared cache.
Click to expand...
Click to collapse
Have you wiped the Dalvik cache as well? As usual there are problems if you forgot to wipe it. This sound like I'm questioning a noob but don't be mad, it's just better to check something twice, then to have an unresolved issue.
For me, CM7.2 RC1 is the best room, the stability is good and the customization is excellent.
I'm also running 7.2 RC1 but after reading this topic I'm a bit confused, what ICS lock screen are you guys talking about? for me the lockscreen option haven't changed compared to 7.1:
(not allowed to post pics yet, so: ) dl.dropbox.com/u/6210453/screenshot-1332696183226.png
the catfishman said:
I'm also running 7.2 RC1 but after reading this topic I'm a bit confused, what ICS lock screen are you guys talking about? for me the lockscreen option haven't changed compared to 7.1:
Click to expand...
Click to collapse
When I was talking about the ICS lock screen I had in mind the option under the Settings>CyanogenMod Setting>Lockscreen>Style Options>Lockscreen Style>Ring option and then in the same menu under the "Ring-Lock Style" choose "Holo Style" which has the look of ICS lockscreen
Here is an image of it
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ah thank you, i didn't notice the extra options once you choose the ring style ...cool.
The only issue I have with CM7.2 RC1 is Wi-Fi connection. When I started my wifi it connects to the hot spot it obtain the IP address but the is no internet connection. Sometimes I just turn of and on the WiFi and it's working but sometimes I have to reboot my phone. I'm not sure where lies the problem, whether is the phone or my home hotspot (usually there are no problems with my PC to connect so I'm more sure to be the phones fault)
the catfishman said:
Ah thank you, i didn't notice the extra options once you choose the ring style ...cool.
Click to expand...
Click to collapse
No problem ^_^
PS: you can click the thanks button
Hi,
The CM7.2RC1 seems to be quite good.
However, I have lost brightness control completely. Notification power button is not working and when trying go to Display in Settings I am getting FC.
I upgraded from CM7.1.0 (stable) without wipe out.
Anyone have similar issue?
Nevermind. Just updated to ICS and things looks so much nicer, despite the camra and theter are not working yet.
Wifi Issues
CM 7.2 RC1 is almost flawless. The only issue I've had is connecting to Wifi. The connection is SLOW and times-out often. It doesn't matter where I'm at, or who's wifi I'm on, and I have checked the D/U speeds with other devices to confirm it's working... so I'm pretty sure it's a ROM issue. I haven't been able to find any fixes, yet.
punkcik5 said:
Hi,
The CM7.2RC1 seems to be quite good.
However, I have lost brightness control completely. Notification power button is not working and when trying go to Display in Settings I am getting FC.
I upgraded from CM7.1.0 (stable) without wipe out.
Anyone have similar issue?
Click to expand...
Click to collapse
That is unfortunate. I do not seem to suffer from this issue. ROM is indeed flawless. But I stopped beating around the bush and updated to Beta CM9
All is perfect but wifi isnt as good as 7.1 but the difference isnt great.
Now ill try gingervillain.
Sent from my HTC Desire using Tapatalk
SD Card Problem
Hallo guys. Hope you can help. So I flashed this rom and everything seems to be working fine. I set it up just the way I want it so I decided to do a nandroid backup. Now after I reboot it seems to be stuck in the "preparing sd card" stage. I'm sure this has been addressed before but I can't seem to find the right thread here. Can anyone point me to the right direction? Thanks!
I'm using CM72RC1 on BravoC. With stock kernel, gps locking is little longer. I change the kernel with CronModKernel, gps locking is faster.
Right now, I didn't have CM72RC1 stock kernel. Could someone tell me where to download it?
agismaniax said:
I'm using CM72RC1 on BravoC. With stock kernel, gps locking is little longer. I change the kernel with CronModKernel, gps locking is faster.
Right now, I didn't have CM72RC1 stock kernel. Could someone tell me where to download it?
Click to expand...
Click to collapse
The next nightly build should have a fix to speed up the GPS lock.
http://review.cyanogenmod.com/14644
Flashed 7.2 over my previous nightly.. it's stuck on the boot screen for like 6 minutes now..
Gonna reset it and see what happens.
EDIT:
Works after pulling out the battery and restarting.. probably just some weird glitch.
Android 4.3 Jellybean for Motorola Bravo
Quarx Builds: http://quarx2k.ru/
Gapps: http://goo.im/gapps/
Minimal Gapps (Gmail,Market,Gtalk,Synchronisation): http://quarx2k.ru/gapps-jb-20120726-minimal.zip
Status:
30.07.13: First Build. Works almost all.
01.08.13: Fix "Unknown" bug. Fix 1% battery. Dialer included, VideoEditor removed.. Backup gapps disabled(to prevent reboots during install rom).
17.09.13: Focal Restored, Ability to OC GPU(without gui yet), added patch for Data, DefyParts, 720p rec(bugged), Support HWUI app, Minimum brightness 2, Wide poho added.
20.10.13: 720p rec, Fix HWUI app, use thoemy wpa_supplicant, Call Recording, LTO support, many fixes and improvements in kernel, gpu 266mhz by default, Fix arrows that indicate upload/download activitiy at Wifi and mobile connections.
30.10.13: Fixes in kernel, Added two new options for ril "emptycallchanges" and"skipdatareg" (disabled by default), journal on ext enabled by default, fix reboots in recovery(not tested), updated twrp.
Thanks a lot Quarx.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks, this is great to see!
Hopefully quarx or another crafty Defy dev pulls a rabbit out of a hat soon with a moto audio library.
Awesome. :highfive: Did you build from Quarx's Defy sources and added in the Defy Common changes? Just curious, I've thought about doing that but I'm busy with Salad Bar and soon Paranoid.
Oh, and long time no see -- good to see you're still around
Thanks a lot aleeyt! Are you going to be taking over the JB Bravo port from Quarx for good?
skeevy420 said:
Awesome. :highfive: Did you build from Quarx's Defy sources and added in the Defy Common changes? Just curious, I've thought about doing that but I'm busy with Salad Bar and soon Paranoid.
Oh, and long time no see -- good to see you're still around
Click to expand...
Click to collapse
This is a separate version for Bravo. While there are no changes in the repositories, but I think soon they update. The Quarx now little time, so I will be engaged in development under Bravo, of course not without his help so far, but all the same separately. I think the ports for Bravo will no longer be the personal own builds.
Sound now works
All thanks for help to maniac103 and Quarx.
aleeyt said:
This is a separate version for Bravo. While there are no changes in the repositories, but I think soon they update. The Quarx now little time, so I will be engaged in development under Bravo, of course not without his help so far, but all the same separately. I think the ports for Bravo will no longer be the personal own builds.
Click to expand...
Click to collapse
I've been doing the same with ICS and haven't had any problems. So far, my biggest issue is having to revert the camera libs after pulls and merges with Epsylon's repo.
Thank god our platforms are so similar, for the most part, all I've had to do was change Jordan to Kobe and mb525 to mb520; well there's a bit more than that, but you've messed with the source so ya know what I mean.
You're quick! I'll flash 7/18 and give some feedback over the next couple hours
wow quarx server is overloaded giving internal service error
and downloading from aleeyt's server, i'm sitting pretty at 1 hour till flash
inverted gapps for jellybean: http://forum.xda-developers.com/showpost.php?p=28947948&postcount=1
Flashing over CM9 got me stuck at the (new) boot animation.
Also, when I go into recovery there's a new error at the bottom: Error: cp not found!
sdrawkcab3 said:
Flashing over CM9 got me stuck at the (new) boot animation.
Also, when I go into recovery there's a new error at the bottom: Error: cp not found!
Click to expand...
Click to collapse
I didn't have that problem. I never wipe data, but do wipe cache+dalvik both before and after flashing any new rom...but you probably already wiped.
Quarx is currently fixing mp3 issues and apps2sd.
quick changelog:
camera, video, pano, chrome work (side note: can't make swipe to delete picture work, but the camera to gallery feature works great)
FC accesing settings->system
it's pretty fast, I would say maybe the same or a tad bit faster than the last ICS build
new 'safe headset volume' option in sound settings, oh and sound works
developer options has to be turned on (switch on top right corner of screen) in settings
CM performance options, and defy parts now included
no CM power widgets yet obviously or custom statusbar options
no CRT screen-off animation, even though option available in display settings
no boosted, smartass governors or sio scheduler obviously
weather, calendar on lockscreen work
google now works (with voice!) but kind of laggy
new HWA settings app so you can choose apps to blacklist
@Aleeyt
Do you have a github repo? I checked your old one and it didn't have a trace of JB on it. Only asking cause I can't get the compile to start when using Quarx's repos as a base, nothing changed; the Defy(+) compiles just fine.
I'd post my terminal output, but I closed that window a few hours ago and didn't plan on asking for help in the matter. It tells me that it can't find cm.mk at device/*/kobe and that file is clearly there...Perhaps I'll go over Quarx's commit history and find what he changed and add that in to my local JB repo (haven't pushed anything to github yet and won't until I get somewhere either).
skeevy420 said:
@Aleeyt
Do you have a github repo? I checked your old one and it didn't have a trace of JB on it. Only asking cause I can't get the compile to start when using Quarx's repos as a base, nothing changed; the Defy(+) compiles just fine.
I'd post my terminal output, but I closed that window a few hours ago and didn't plan on asking for help in the matter. It tells me that it can't find cm.mk at device/*/kobe and that file is clearly there...Perhaps I'll go over Quarx's commit history and find what he changed and add that in to my local JB repo (haven't pushed anything to github yet and won't until I get somewhere either).
Click to expand...
Click to collapse
I do everything locally. I have not updated the repo, as yet not understood how to do it) Once the sorting out, update the necessary.
aleeyt said:
I do everything locally. I have not updated the repo, as yet not understood how to do it) Once the sorting out, update the necessary.
Click to expand...
Click to collapse
I hear that....I'm still trying to get all that figured out. My hardest part is remembering to initialize my local repo before doing changes.
New build available.
a lot of people, including myself, have been giving credit to Quarx and the other defy devs for the breakneck speed of development for the defy and our device...and rightly so.
but aleeyt, you really have been the one that got everything started for the bravo in the first place, by taking the initiative to get our device to Quarx. Otherwise, we would've probably been stuck with miui and cm7 defy ports like before.
Thanks a lot man.
July 19 changelog:
no more FC on Settings--> system, however none of the options really work (i.e. battery percentage, power widgets on notification bar, etc.)
mp3 codec, youtube and endomondo issues, apps2sd fixed
notification LED and sound present, no charging LED yet
the build is definitely worthy of being a daily driver
if you're using the inverted gapps link I posted earlier, the inverted google now is pretty glitchy, here's the same zip with the non-inverted velvet that works fine: http://www.sendspace.com/file/qf6f5e
Thanks for keeping Bravo right up there with the bleeding edge, aleeyt We're enjoying these daily ports!
So is crt working and hwa? I want to experience the smoothness, lol
Having trouble with email exchange force closing. Other than that...we have 4.1.1 on our phones.
Sent from my MB520 using xda premium
BravoMotorola said:
So is crt working and hwa? I want to experience the smoothness, lol
Click to expand...
Click to collapse
CRT still does not work, but hwa does.
I also get the exchange FC. I wonder if it's system app related. There's two different exchange apk's in the directory.
Sent from my MB520
DO NOT post in this thread until you have read the first three posts and last two pages of this thread in their entirety!
"Me Too" posts for known issues with no useful debugging information WILL BE REPORTED.
This is the thread for Omni nightlies for the Oppo Find 7a and 7s
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://dl.omnirom.org/find7/
Also, the nightlies support LVM for partition remapping, which allows the two internal data partitions (/sdcard and /data) to be merged into one that uses emulated storage for /sdcard (Android's standard method for ICS and later). Details can be found at http://forum.xda-developers.com/showpost.php?p=55081626&postcount=546 . LVM is significantly safer than other partition remapping solutions as it does not actually alter the underlying partition table. As a result, switching layouts is MUCH faster than methods which remap the partition table, and switching layouts is more reliable and doesn't fail in strange and difficult-to-repair ways (such as the frequent failures of another solution that can be seen in the ColorOS 2.0.2i beta thread). There's a good chance Oppo will be switching over to this method with a future ColorOS release, especially after their experiences with 2.0.2
For historical reference, I will leave the pre-nightly test builds in the Downloads section of this thread. However, these are now obsolete.
Gapps:
http://forum.xda-developers.com/showthread.php?t=2397942
(this isn't a nexus, use the modular releases, not full)
Omni only supports TWRP recovery, use any alternate recovery at your own risk. Official TWRP for this device is:
http://forum.xda-developers.com/showthread.php?t=2717916
Anyone flashing this should know the usual installation drill... Flash in recovery, flash gapps, wipe data/factory reset. If you don't know how to do these things, this package is not yet ready for users like you.
Thanks go to the following people for their help during bringup:
Jake Whatley and Kristof Petho (Omni)
Max Weninger for polishing the device up and getting it up to nightly readiness after I kind of burned out
Andre Saddler and Hieu Nguyen of the Paranoid Android team
XDA:DevDB Information
Omni for Find 7a/7s, ROM for the Oppo Find 7
Contributors
Entropy512, maxwen, xplodwild, jerdog, jakew02
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Nightly
Created 2014-05-21
Last Updated 2014-09-02
Reserved
Kernel source:
https://github.com/omnirom/android_kernel_oppo_msm8974/ plus the following Gerrit items:
https://gerrit.omnirom.org/#/c/7373/
https://gerrit.omnirom.org/#/c/7374/
https://gerrit.omnirom.org/#/c/7423/
https://gerrit.omnirom.org/#/c/7651/
https://gerrit.omnirom.org/#/c/7649/
https://gerrit.omnirom.org/#/c/7650/
https://gerrit.omnirom.org/#/c/7648/
Device tree:
https://github.com/omnirom/android_device_oppo_find7a/ plus:
https://gerrit.omnirom.org/#/c/7336/
https://gerrit.omnirom.org/#/c/7645/
https://gerrit.omnirom.org/#/c/7434/
Other Gerrit items:
https://gerrit.omnirom.org/#/c/7652/
https://gerrit.omnirom.org/#/c/7460/
https://gerrit.omnirom.org/#/c/7465/
https://gerrit.omnirom.org/#/c/7103/
Also there are misc patches to increase debug logging in a number of places (the basic setting NDEBUG to 0)
Blobs: donkeycoyote
Reserved
Current status as of 05/20/2014:
GPS works
Wifi works
Cellular radio works (data and voice calls)
Basic camera/camcorder functions work
Bluetooth works (tested with Google Glass and an OBDKey)
Sensors work (except for Google Camera Photosphere - see below)
Audio is flaky - Mic does not work in speakerphone calls (earpiece only) and headsets with microphones cause the audio HAL to barf. There are probably a number of other use cases where audio doesn't work well. Confirmed working are Google Play Music, Google Maps, earpiece calls, Bluetooth calls via Google Glass (Mic in speakerphone/headphones may be fixed in the 5/30 build - won't test until tomorrow.)
Not yet implemented (need to get the basics done first, these shouldn't be too hard since maxwen did them all on N1)
Screen-off gestures for music
"Hey, Snapdragon" voice wakeup - gotta talk to xplodwild about this
Superzoom mode (I'm about halfway there, it's in the 5/30 build but crashes when you take a shot, so effectively isn't really there...)
Known issues:
Rare spontaneous reboots due to the WCNSS firmware crashing (1-2 times/week for me)
Magnetometer (compass) gets "Stuck" if you use Google Camera
LPM (charging when device is off) is broken - device may charge but screen gets stuck on at the Oppo logo. (may sometimes happen when rebooting on charger)
Woot!
Here we go!
Sent from my OnePlus 7a
Finally a good vanilla build
My camera lenses produce a clicking noise everytime a camera app is closed. It didn't happen with color OS before. ¿is there any issue with it?
If you want to have a OP more attractive, i know content is attractive but picture too, here it is a simply prez from me...
You can use it freely... or trash it quickly !
Does VOCC Charging works now?
Also, 3-ring headsets do not work (ie like the headset that came in the box).
Great work guys... Running super for an alpha.
There's a typo, it's build in may, not april :good:
lesscro said:
If you want to have a OP more attractive, i know content is attractive but picture too, here it is a simply prez from me...
You can use it freely... or trash it quickly !
Click to expand...
Click to collapse
I'm not a big fan of flashy posts with lots of graphics. Means more data for my browser to load.
hulicow said:
Does VOCC Charging works now?
Click to expand...
Click to collapse
It's in-kernel, it's pretty much impossible to get a device with working charging without VOOC.
kristofpetho said:
Also, 3-ring headsets do not work (ie like the headset that came in the box).
Click to expand...
Click to collapse
That's what I meant by headsets with mics barf. (although headsets with media controls might be in the same boat...)
xabierd said:
There's a typo, it's build in may, not april :good:
Click to expand...
Click to collapse
WHAT? It's not 4/20???
No problem... then trash it as i say...
cheers
It's begun. Glad to see you got it through entropy.
Once the initial hiccups are ironed out this phone can finally take it's place as the stylish and capable smartphone it should have had from the very start.
Gesendet von meinem One mit Tapatalk
Fix for 3-ring jack not working incoming.
Entropy512 said:
Not yet implemented (need to get the basics done first, these shouldn't be too hard since maxwen did them all on N1)
Doubletap to wake
Screen-off gestures
Click to expand...
Click to collapse
Since 7a also use F3 for double tap it should be as easy as adding
<bool name="config_offscreenGestureSupport">true</bool>
to framework overlay
whats also the same is circle -> F4
the rest (F5 - F9) is different to the other oppos - actually we might need to filter them
out at the moment until we add support in the framework for them
maxwen said:
Since 7a also use F3 for double tap it should be as easy as adding
<bool name="config_offscreenGestureSupport">true</bool>
to framework overlay
whats also the same is circle -> F4
the rest (F5 - F9) is different to the other oppos - actually we might need to filter them
out at the moment until we add support in the framework for them
Click to expand...
Click to collapse
Thanks!
BTW, what was the story behind https://github.com/omnirom/android_...mmit/0f6126a18e85e254d15421751abe78939beab1fd - were you getting a bunch of input event spam waking up the device during suspend? That's a problem I'm periodically seeing on this device.
Entropy512 said:
Thanks!
BTW, what was the story behind https://github.com/omnirom/android_...mmit/0f6126a18e85e254d15421751abe78939beab1fd - were you getting a bunch of input event spam waking up the device during suspend? That's a problem I'm periodically seeing on this device.
Click to expand...
Click to collapse
Thats a little help to the "ear opening notification bar on call problem"
on the F5 it can take up to 500ms from screen off because of proxy
sensor until TS suspend is done - this filters out events during that time.
Its kinda hacky and doesnt solve the issue all the time but
better then before and little effort and risk.
We dont have the issue on the N1
maxwen said:
Thats a little help to the "ear opening notification bar on call problem"
on the F5 it can take up to 500ms from screen off because of proxy
sensor until TS suspend is done - this filters out events during that time.
Its kinda hacky and doesnt solve the issue all the time but
better then before and little effort and risk.
We dont have the issue on the N1
Click to expand...
Click to collapse
Wasn't that a different patch?
I'm seeing a problem where the device gets stuck wakelocked processing lots of input event spam from somewhere, or it's not properly flushing the key event queue. It's intermittent - sometimes it's absolutely fine, other times it just goes nuts.
maxwen said:
Thats a little help to the "ear opening notification bar on call problem"
on the F5 it can take up to 500ms from screen off because of proxy
sensor until TS suspend is done - this filters out events during that time.
Its kinda hacky and doesnt solve the issue all the time but
better then before and little effort and risk.
We dont have the issue on the N1
Click to expand...
Click to collapse
ah - no
LOL I was to much ahead and imagined another change you might
also find at some point
This one is actually obsolete AFAIKS since there is a check
for is_tp_suspended on top of the function. Think this is a "leftover"
for our properitary S2W impl that has been obsoleted
Smoother than Butter
Friendly Battery
Tons of Features
DirtyUnicorns Features
100% Build from Source
This is what
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
is!
CyanogenMod 13 based
Quicker system animations
Trimmed down fat and excess bloat
Option to enable all widgets
Numerous extra lockscreen options
LCD Density
Custom original BeanStalk Wallpapers by skyliner33v
Custom BeanStalk bootanimation by skyliner33v
3-minit battery support
Clock and date options
Contextual Header - Original and Polygraphic
Battery styles - Includes specific colors and styles. Also includes battery bar
Do not disturb option
Show notification count
Recent screen options
Customizable navigation bar
Use Omniswitch as default recents
Built-in screen record
Toast animations
App Circle bar
Gesture Anywhere
Disable FC warnings
Disable Immersive message
Force expanded Notifications
Configure scrolling cache
Build.prop MOD options to enable/disable tweaks as preferred
Less frequent Notification sounds options
CRT screen off/on options to specify how the animation shows
Enable/disable wake up on charge option
Superuser fully embedded into the build and accessed from settings menu
CM Performance options and features
Hide superuser icon
Developer options and advanced reboot enabled by default
Numerous cherry-picks and improvements throughout the build, baked into the
awesomeness of existing CM layout.
Numerous other options hiding throughout the build. For a full list of changes and features, please
Same as CM13
For Volte to work :
- Reinsert SIm2 after every reboot.
GAPPS
ROM
Thankz to @Travisholt92 for the mirror
Download ROM and latest GAPPs
Copy ROM and GAPPs from above to internal storage
Reboot into recovery
Full wipe and format
Flash ROM and then flash GAPPs
Reboot and enjoy the BeanStalk goodness
XDA:DevDB Information
BeanStalk, ROM for the Moto G4 Plus
Contributors
rahulsnair
Source Code: https://github.com/rahulsnair
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: TWRP 3.0.20 build
Based On: Cyanogenmod
Version Information
Status: Stable
Stable Release Date: 2016-10-18
Created 2016-09-24
Last Updated 2016-11-06
Here
One more ROM! Going to have a look at it later!
Send with my Moto G4 Plus (XT1642) with CM13 using Tapatalk!
Tested on XT1644 or u want me to test?
Great dev happy to see new rom, keep it bro
Best of luck for further development eg android nougat 7.0 and many more.
Looking forward to test this build. Could you provide us with some screenshots?
I'll try! But incoming call bug is present??? I have Moto G4 Plus double Sim xt1643
Nice to see another player in the game for this phone.
This is good to see, means progress to a fully working daily for this phone soon.
Only thing that stops me using any atm is incoming calls bug. Once that's fixed I'll be using it as a daily then with other bugs.
My model xt1622 single sim.
I've asked but got no answer, but I don't see why can't they just take the sim 2 code (wich completely works, incoming calls included) and apply that to sim one, and it work. Sim one fix would be a double fix as it would fix dual sim cards and single sim cards
Edit:
Ok figured I'd pass this on with other threads. Acording to the info I read, for those single sim xt1622 users, removing the sim card and putting it back on, incoming calls then with fine.
This is from the post:
ATTN - 1622 variant users. I received a pm from one of the 1622 single sim users informing me that the sim works if you remove and put it back. Here is the verbatim of the pm.
Quote:
Originally Posted by faissaloo
Hey,
I've been using the CyanogenMod build you guys made here on my single sim moto G4 XT1622:
http://forum.xda-developers.com/moto...3439348/page29
I've discovered that the SIM does in fact work if you remove it, put it back in and wait for about 10 minutes.
I would have posted in the thread but since I'm a new user, I can't, so feel free to quote this PM verbatim. Hope this helps!
So anyone with a xt1622 single sim phones, perhaps you can try this and report back.
Any xt1644 support yet?
mason2smart said:
Any xt1644 support yet?
Click to expand...
Click to collapse
Doubt it.
My xt 1625 runs flawless on this ROM long battery an massively customized an still no lag an great battery
Working good on xt1643 but The ROM has double chop and swipe ? I cant find these options
hazmatkid said:
My xt 1625 runs flawless on this ROM long battery an massively customized an still no lag an great battery
Click to expand...
Click to collapse
Are you able to receive phone calls??
GaBuzz said:
Are you able to receive phone calls??
Click to expand...
Click to collapse
Yup everything works greats I got xposed with countless other things modified but I'm not exactly a noob to this I've been a member for over 6 years
hazmatkid said:
My xt 1625 runs flawless on this ROM long battery an massively customized an still no lag an great battery
Click to expand...
Click to collapse
hazmatkid said:
Yup everything works greats I got xposed with countless other things modified but I'm not exactly a noob to this
Click to expand...
Click to collapse
Is it OK to ask what service provider you use? It's seems to work for some people but not other's, not sure if it's certain cell services that work while others don't.
GaBuzz said:
Is it OK to ask what service provider you use? It's seems to work for some people but not other's, not sure if it's certain cell services that work while others don't.
Click to expand...
Click to collapse
I switch between straight talk att no issues T-Mobile sucks sprint sucks Verizon is to much of a hassle
Very nice and smooth, 2 weeks ago I got my phone with my xt1621 and yesterday I unlocked the boot loader, twrp and root and install this rom, after using it all day long, I sitll have some battery left, almost like the stock, ther is something odd happening when i play, some times the screen just turns off all the sudden. Is this the blackout issue that other users are reporting on Moto G4 ?
Thanks a lot for this awesome rom!
Regards!:good:
tested and approved in XT1640, it worked very well in this variant.
hdemary said:
Very nice and smooth, 2 weeks ago I got my phone with my xt1621 and yesterday I unlocked the boot loader, twrp and root and install this rom, after using it all day long, I sitll have some battery left, almost like the stock, ther is something odd happening when i play, some times the screen just turns off all the sudden. Is this the blackout issue that other users are reporting on Moto G4 ?
Thanks a lot for this awesome rom!
Regards!:good:
Click to expand...
Click to collapse
No the blackout issue that was reported was a complete blackout when setting up the rom
New build is Up. Check Opng thread for the link. Enjoy
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WELCOME TO Cyanide
ROM INFORMATION
Basic intro for now, based on AOSP this ROM will be stuffed full of features while being stable and battery friendly. If you like options then you'll have a tough time finding more I would GUESS.
DOWNLOADS
ROM
Gapps
ROM INSTALLATION
If coming from a different ROM
1) WIPE DATA/FACTORY RESET
2) WIPE SYSTEM
3) Wipe Cache/Dalvik Cache
4) Flash the ROM and Gapps.
5) Reboot and PROFIT!!!!
6) Enjoy
If updating from older version of Cyanide
1) Wipe Dalvik, Cache, and System
2) Flash ROM and Gapps
3) Reboot and PROFIT!!!!
Thank You and Enjoy!
Google+ Community
XDA:DevDB Information
Cyanide, ROM for the Google Nexus 5
Contributors
vikrant699, rogersb11
Source Code: https://github.com/CyanideL
Kernel Source: https://github.com/DirtyUnicorns/android_kernel_lge_hammerhead
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Stable
Stable Release Date: 2017-01-23
Created 2016-12-27
Last Updated 2017-01-23
Wow! a new nougat rom for n5, Thank you.
Never seen this before. I'm downloading now.
Will report back
Thanks guys
John
Sent from my Nexus 5 using XDA Labs
let's flash again!
OMS?
Hi there,
Good to see more Nougat ROMs popping.
Does this build already contain the fix for the green artifacts whilst recording via Google Camera?
IWell guys I must say that on first impressions in very impressed.
The ROM downloaded very quickly
I flashed exactly as you said, wipe and clean install.
First time I tried it with open GAPPs 7.1Stock and it went through the installation process went through to installing super su then bounced back to TWRP when it came to installing GAPPs
I tried again with GAPPS 7.1 nano that I had used in a pervious ROM and it all installed no bother.
It did boot loop a couple of times before it got to the ANDROID boot animation.
I like the way the the ANDROID just sort of glimmers its simple and different.
It only took a few mins to boot and run through the set up and with use of titanium backup I had the whole thing set up in 10 mins.
The black and blue theme looks really good on my black Nexus.!
I ran through all the settings and couldn't find anything that isn't working for what I use.
I dont use this phone as a daily so I can't comment on the sim / signal / 4g etc.
All in all this looks like a great ROM that looks different from the others.
I prefer the Nova Launcher that you included over the pixel just coz I can do more with it.
This ROM is fast, smooth really well put together and looks different from the others.
It's the inbuilt theme engine that makes this a real winner although I'm not sure if you can add more theme than what are provided. There is enough there for me
Nice one guys
Thank you for you work.
Yes I have been poisoned by Cyanide
John
Cyanide has inbuilt themeing options, so OMS isn't merged. Substratum legacy may work if you don't apply framework. In built themeing includes changing of colours and fonts which is applicable almost everywhere.
I'm not asking for ETA's just asking if updates will be OTA or manual ?
Can someone make a screenshot of the features included?
What do you want a screen shot of ? There at lots in the O.P
No bettery percentage in systems user Interface
Sent from my Nexus 5 using XDA-Developers mobile app
I'm noticing that my battery seems to be draining very quickly.
It goes onto doze mode no bother when the phone isn't being moved.
I used TB to back up 2 apps and the battery was empty.
I did calibration with the battery when first installed.
I will do a screen shot on the next battery cycle.
John
Last battery cycle
I just had a quick go of the video recorder and it films and records & plays all good.
Just need to look at the battery
Second battery cycle.
This is without a SIM card
The ROM dose mode is working as the battery life doesn't move until you start to move the phone.
I'm not playing any games.
No extreme use only on Google + and on here XDA
Battery saver is on
Hope this is of some use.
I really like the ROM but the battery is running out very quickly but then it only takes half hour or so to fully recharge
John
johnhux7 said:
Second battery cycle.
This is without a SIM card
The ROM dose mode is working as the battery life doesn't move until you start to move the phone.
I'm not playing any games.
No extreme use only on Google + and on here XDA
Battery saver is on
Hope this is of some use.
I really like the ROM but the battery is running out very quickly but then it only takes half hour or so to fully recharge
John
Click to expand...
Click to collapse
So to have a look at the issue. I clean flashed my build. Again. Initially got the heavy battery drain from Android System and Miscellaneous, did a few reboots, no effect. So what I did was, enabled Battery Saver and then disabled it. Don't know why though but the heavy battery drain was gone for me. At 39% stats showed around 1 hour and 20 minutes left. Used it till the phone was off and yep, I got more than an hour of usage from those 39%. So I think it must be an app misbehaving in the background. And this battery drain issue is present in a lot of ROMs, like AOSiP and Fake Nexus. So its just an app draining the battery.
vikrant699 said:
So to have a look at the issue. I clean flashed my build. Again. Initially got the heavy battery drain from Android System and Miscellaneous, did a few reboots, no effect. So what I did was, enabled Battery Saver and then disabled it. Don't know why though but the heavy battery drain was gone for me. At 39% stats showed around 1 hour and 20 minutes left. Used it till the phone was off and yep, I got more than an hour of usage from those 39%. So I think it must be an app misbehaving in the background. And this battery drain issue is present in a lot of ROMs, like AOSiP and Fake Nexus. So its just an app draining the battery.
Click to expand...
Click to collapse
OK mate I will try that and see how it goes.
Anyway of finding out what app it is ?
John
Sent from my Honor 8 using XDA Labs
johnhux7 said:
What do you want a screen shot of ? There at lots in the O.P
Click to expand...
Click to collapse
I dont see whats in the features menu.
Rezei said:
I dont see whats in the features menu.
Click to expand...
Click to collapse
I can't get online with my Nexus at the MO due to hotspot issues.
I will get some screenshots up for you although I'm nothing to do with this ROM I'm just a tester.
You could always just flash the ROM yourself and have a look.
Failing that I'm sure that the developer will put up what you need.
It's a smart ROM. Looks good
John
Sent from my Honor 8 using XDA Labs
johnhux7 said:
I can't get online with my Nexus at the MO due to hotspot issues.
I will get some screenshots up for you although I'm nothing to do with this ROM I'm just a tester.
You could always just flash the ROM yourself and have a look.
Failing that I'm sure that the developer will put up what you need.
It's a smart ROM. Looks good
John
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
Ill wait patiently. Im on RR right now. But i want to test other roms. But search for a rom with similar amount of customization. Thanks.