{
"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"
}
Prologue
This topic is dedicated to my attempt crafting a properly working CM11s port for the Oppo Find 7a based on the recently released OnePlus One image dump on phandroid.
This project is in its early alpha stages and can be seen as uncharted (bug infested) territory, don't expect miracles, but compared to ColorOS it should still be an overall improvement.
Latest Version Download
CM11s Version 4 (if you need SDCard Support, combine with Version 3 Support Package)
SDCard Support Package Version 3
Older Version Download
CM11s Version 3
CM11s Version 2
SDCard Support Package Version 2
CM11s Version 1
SDCard Support Package Version 1
How to install (if you wish to use internal storage)
1. Install TWRP Recovery on your phone
2. Install the CM11s Basic Installation Package on your phone
3. Do Wipe -> Advanced Wipe -> Cache / Internal Storage (this will delete all your data inside your internal storage!) inside TWRP Recovery
4. Reboot your phone
How to install (if you wish to use SDCard storage)
1. Format your SDCard to the EXT4 filesystem (make sure to disable EXT4 Journaling while you do this) using a Linux Computer / Virtual Machine
2. Copy the CM11s Basic Installation Package and the SDCard Support Package onto your phones internal storage or the freshly formated EXT4 SDCard
3. Plug the EXT4 SDCard into your phone
4. Install TWRP Recovery on your phone
5. Install the CM11s Basic Installation Package on your phone
6. Install the SDCard Support Package on your phone
7. Do Wipe -> Advanced Wipe -> Cache inside TWRP Recovery
8. Reboot your phone
What works?
WiFi
Mobile Connectivity & Data
SDCard Support (via separate support package)
Camera (including 4k recording)
Sound
Bluetooth
GPS
What doesn't work? / Known Bugs
WiFi reception is glitchy (known OnePlusOne bug, we have to wait until we get a new OTA that fixes this)
Force Close in SIM Subscription Settings (known OnePlusOne bug, we have to wait until we get a new OTA that fixes this)
NFC
Flashlight / Camera LED
Voice Wakeup (training works, but actual wakeup doesn't)
SDCard Support is suboptimal (at the moment you can only use internal storage OR sdcard, but not both (I'm working on this already))
Some applications still show upside-down back-facing camera (Barcode Scanner for example, could be a legacy camera support issue as all applications that use the new kitkat API work fine)
Sound is extremely low in video recordings (nothing critical, can be upsampled on a computer post-production, but still annoying)
Rare random force-closes (seems to have something to do with I/O timeouts)
Changelog
Version 4
Fixed inverted Accelerometer X-Axis (this fixes the landscape rotation issues apps were having)
Version 3
Improved Proximity Sensor Configuration (thanks to m3dd0g)
Fixed Back-Camera Orientation
Version 2
Removed NFC (broken)
Improved Battery Life
Improved I/O Performance
Fixed VOOC Charging
Version 1
Initial Release (thanks to graffixnyc for his filesystem dump @ http://forum.xda-developers.com/showthread.php?t=2751401)
Donations
Should you like my work feel free to buy me a beer (or help me pay my bills) by donating to me via PayPal.
My PayPal Email Address is [email protected]!
First
Hey i know the camera is fixed but when u use any other app that utilized the cemera such as barcode scanner ots still upside down
Sent from my Oppo Find 7a
Hello,
I have been following the thread about CM 11s since the beginning.
MrColdbird & the others contributors :
Thanks for your help and the update.
So this is a proper topic. You work very clean Coldbird, thats nice.
Thank you for your work.
dkotoric said:
Hey i know the camera is fixed but when u use any other app that utilized the cemera such as barcode scanner ots still upside down
Sent from my Oppo Find 7a
Click to expand...
Click to collapse
Not much I can do other than set the drivers physical mount orientation...
Sorry.
Thats cool i know nothing about development I just thought id mention it
Sent from my Oppo Find 7a
@ MrColdbird...
Gift for 1st thread... i hope you like it...
cheers
That's awesome. Mind if I put that in the op post?
Gesendet von meinem One mit Tapatalk
yep !
Is that a "yep" meaning you mind him doing it, or a "yep" as in "use it!" ?
marthell said:
Is that a "yep" meaning you mind him doing it, or a "yep" as in "use it!" ?
Click to expand...
Click to collapse
Most likely yep since lesscro stated his intention to make a graphic in the other CM11s thread and then said it was a gift for the thread in the post here.
Side note nice graphic, I wish I had an ounce of artist creativity let alone the ambition to use it.
Nice work and big thanks for the threat header/banner. Looks great.
I know it´s early,but Francisco Franco stated on G+ that he will maybe break his nexus-only-rule and develope for other devices, such as the OPO ( he bought a M8 recently, and will develope for this). So, when the kernel for the OPO start popping out, is there a chance, that these may work on this device too?
Brembo109 said:
Nice work and big thanks for the threat header/banner. Looks great.
I know it´s early,but Francisco Franco stated on G+ that he will maybe break his nexus-only-rule and develope for other devices, such as the OPO ( he bought a M8 recently, and will develope for this). So, when the kernel for the OPO start popping out, is there a chance, that these may work on this device too?
Click to expand...
Click to collapse
Yes of course.
m3dd0g said:
Yes of course.
Click to expand...
Click to collapse
Okay, nice. Thanks for the answer. Im not a dev, but it´s exciting to see that these two devices are nearly twins.
I also want to take time thanking Coldbird and other contributors for the great work. It feels much better with CM11s. Also donated, as a thanks for the effort!
I wanted to ask about other users experience with the rapid charging; for me it is charging fairly quickly, but not as fast as on the ColorOS. Just timed it and it went from 34 % to about 60% in 30 mins. I don't really mind, CM11s is worth it, but I just wondered if this roughly is the experience of other users aswell?
From what the kernel reported its charging at around 4 amps at peak. So no idea, never measured in coloros.
Gesendet von meinem One mit Tapatalk
marthell said:
I also want to take time thanking Coldbird and other contributors for the great work. It feels much better with CM11s. Also donated, as a thanks for the effort!
I wanted to ask about other users experience with the rapid charging; for me it is charging fairly quickly, but not as fast as on the ColorOS. Just timed it and it went from 34 % to about 60% in 30 mins. I don't really mind, CM11s is worth it, but I just wondered if this roughly is the experience of other users aswell?
Click to expand...
Click to collapse
I will try to test the fast charging tonight. If I can flash the cm11s successful
===================================================================
[result]: start charging from 14%, took 1hr 51mins to get fully charged to 100%. (using battery doctor), i think it's more like a normal charging time to me, doesn't seem to have fast charging ability. but i will test it again when the battery run below 20%.
I had to have another play with this before my find 7 goes back with a dead pixel! Its sooo good! Camera is awesome now, I did notice that there's no audio in recorded videos though. Is that just me? Sorry if this is known and if it has been mentioned already.
Thanks again, this has made me even more happy that I decided on the find 7 rather than waiting for the Oneplus One! Bet of both worlds!
Just noticed sensors maybe a little off still... In Google camera app photosphere is a little odd! Moving left/right causes the image to move up/down and vice versa! Still gonna use this for now though!
I noticed some sensor issues myself in YouTube starting at v3.
But I know what it is... M3dd0g forgot to inverse two of the gyro axis.
I manually did that in v2 but it got overridden in v3...
I will revert those two axis to what I set them to in v2.
Gesendet von meinem One mit Tapatalk
Related
All,
{
"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"
}
First of all; apologies this has taken so long to release into the public domain. I wanted to get it right first prior to full release.
SuperHero started out as a very experimental ROM - the feedback from which has surprised me. I expected a few Vanilla fans to download it and like it, but a lot of people are using the ROM as a definite alternative to a Sense UI ROM. I'm really pleased about the feedback it's received.
DESCRIPTION
Essentially, it's a HIGHLY stripped down VillainROM, and is geared solely for absolute, 100% performance. It's quick, folks.
It's about 80% Vanilla, but there are some Sense apps & HTC frameworks in the build for now. This may change at a later date.
SO, THE ROM:
- The excellent ADW Launcher (Recommended settings are: [drawersettings] New Drawer - NO, Animated Drawer - NO, Fast Drawer - YES)
(Use SpareParts to further improve the visuals)
- OTA Updater software installed
- All streaming issues fixed
- Press Home on Home Screen for Sense style quick select view
- Completely customisable home screen
- SIM Contacts can be disabled (and groups are fixed)
- Incredible Live Wallpaper performance - They don't stick for long though. Nice to show off with, that's about it.
- Boot CONTROL Widget
- Vanilla Camera @ 5mp (green tint exists, although, we're working on this)
- Vanilla Keyboard
- Vanilla eMail (Multiple Exchange accounts) (includes corcal and corgal)
- Vanilla Music
- Vanilla & Sense Diallers (option)
- Apps2SD
- Friendstream App working - Widget obviously not as it's SENSE.
- Significantly improved performance over Villain (due to JIT + Removed SENSE limitations)
- Working Vanilla Alarm & Lockscreen
- Gallery 3D MULTITOUCH with rotate fix
- VERY Stable
- All Hardware working
- Perfect OpenGL performance for the build
REMOVE SIM PIN UNLOCK CODE BEFORE FLASHING (as it causes boot problems)
DOWNLOAD LINKS!
Thanks
http://forum.xda-developers.com/showpost.php?p=6541857&postcount=11
awesome. I like, love you man
Server Busy?
getting Timeouts...
Seems like there are lots of people downloading...
alternative link please !!!!!!!!!
The VillainROM site is currently down. They posted on tweeter they are doing their best to fix it and keep us posted.
But i agree, an alternative download link could be great, since i'll probably won't have the time to flash my phone this weekend.
( I don't know why, but female friends really don't understand why it's so much fun to flash a new ROM when your phone is already working fine. )
Tweedeldee said:
( I don't know why, but female friends really don't understand why it's so much fun to flash a new ROM when your phone is already working fine. )
Click to expand...
Click to collapse
Common problem man, lol
Tweedeldee said:
The VillainROM site is currently down. They posted on tweeter they are doing their best to fix it and keep us posted.
But i agree, an alternative download link could be great, since i'll probably won't have the time to flash my phone this weekend.
( I don't know why, but female friends really don't understand why it's so much fun to flash a new ROM when your phone is already working fine. )
Click to expand...
Click to collapse
Unfortunately, I can't do an alternative link
I don't have a copy of the file to even upload to the mirrors folks. Sorry. I will ask around though
Also, most of my FTP passwords are saved on that server, although I have some here on my PC.
Do the bluetooth work?
Alternative link plz
anon2122 said:
Unfortunately, I can't do an alternative link
I don't have a copy of the file to even upload to the mirrors folks. Sorry. I will ask around though
Also, most of my FTP passwords are saved on that server, although I have some here on my PC.
Click to expand...
Click to collapse
No worry, there is nothing to be done when the whole site is down. (except giving angry phone calls )
BTW, the nice clock-meteo and battery-space widgets we can see on the screens are already included in the ROM ?
If they are external applications, could you give us their names ? Finding something in the Market is already a nightmare
(I might be able to flash the ROM this weekend anyway: since the team is doing a great work, VillainROM are working out-of-the-box without issue, I take 1 hour max to flash / configure it... that's around the time she needs to take a shower. )
Tweedeldee said:
No worry, there is nothing to be done when the whole site is down. (except giving angry phone calls )
BTW, the nice clock-meteo and battery-space widgets we can see on the screens are already included in the ROM ?
If they are external applications, could you give us their names ? Finding something in the Market is already a nightmare
(I might be able to flash the ROM this weekend anyway: since the team is doing a great work, VillainROM are working out-of-the-box without issue, I take 1 hour max to flash / configure it... that's around the time she needs to take a shower. )
Click to expand...
Click to collapse
OK. We are in contact with the host. He got woken by the server alarms. So rebooting now...
hi folks, if it is ok for nathan I am uploading the Rom I downloaded 12 hours ago.
Just give me 30 minutes for uploading.
MIRROR - http://www.multiupload.com/DUB447BZR0
MD5 Checksum - 84e51671632f59bc756bb9a101ff40fa
i posted at the other thread too:
even if i deactived sim lock (so that i hadnt to type in the pin with legendroid) on first boot it says invalid sim card.
any idea?
xmaskx said:
i posted at the other thread too:
even if i deactived sim lock (so that i hadnt to type in the pin with legendroid) on first boot it says invalid sim card.
any idea?
Click to expand...
Click to collapse
I experience the same problem.
It says invalid SIM and get stuck by preparing SD Card.
Just a questions: SMS and Contact apps are still HTC ones, or you switched to vanillas?
ermacwins said:
Thanks
http://forum.xda-developers.com/showpost.php?p=6541857&postcount=11
Click to expand...
Click to collapse
There is also Vanillain (3.0 is Darchstar's CyanogenMod 5.0.7 popular CDMA rom ported to our GSM heroes).
That's a pure non-sense rom. But I doubt the wii-remote apps can't work with Sense bits in the rom though, they don't do (that much) to the bluetooth framework.
This ROM is multilanguange?
Original links up again
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
TEAM GUMMY NIGHLY's
{
"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"
}
*
Team Gummy is proud to introduce the Team Gummy Nightlys.. Here you will find an overview of new options offered in the latest release. While there is more features than we could ever go over in here, we thought you might like a walkthrough some of the most popular
*
*
FEATURES: See our Google Doc Feature overview
*
Dark Gummy
Theme Chooser
Advanced Options
Hardware key rebinding
Navigation bar mods
Pie
Power menu customization
Device specific advanced settings
Blacklist phone call/messaging options
Performance Settings
Wakelock blocker
App ops
Sound Settings
Quiet Hours
Ascending ringtones
Live volume steps
Camera shutter sound controls
Display Settings
LCD Density
Notification Light Controls
Volume Rocker Wake
Status Bar Mods
Clock and Date alignment/customization
Custom battery icon options
Battery bar
Signal style tweaks
Breathing notifications
Notification count
Notification Drawer Mods
Custom carrier label options
Show connected Wifi network name
Clock click actions
Notification drawer custom background and transparency
QuickSettings Mods
Toggles per row
Fast toggle
Favorite contact toggle
Custom toggle
Lockscreen Mods
Active display
Lockscreen notifications
Slider targets and shortcuts
Custom handle options and colors
Lockscreen background customization
Lockscreen widget options
Slider torch
Language and Input Settings
Force Auto Rotate when keyboard is shown
Disable full screen keyboard in landscape mode
Show IME selector in notification area
Enter key instead of emoticon
Volume key cursor controls
*
Issues:
* Known so far!
*
Instructions for installations:
*
1. Download ROM
2. Download Gapps
3. Push to sdcard
4. Reboot Recovery
5. Wipe Data and Cache
6. Install ROM
7. Install Gapps
8. Reboot System
* Source github.com/TEAM-Gummy
* Kernel Source https://github.com/TEAM-Gummy/android_kernel_oppo_find7a
Contributions:
*
* Thank you to Cyanogenmod for device and hardware repositories. Without this, porting Gummy to QCOM devices would have been nearly impossible.
* Thank you to Google for the best source code.
* A HUGE THANK YOU FOR DHACKER FOR TAKING THIS PROJECT ON! HE IS THE MAN!
Link in first post
Is gps issue already solved?
Thanks for the great effort!
What GPS issue
Sent from my One M8 using Tapatalk
I'm going to try this baking.
Which custom recovery to use for flashing?
Sent from my X9006 using xda premium
I use twrp
Sent from my One M8 using Tapatalk
It seems that the only issue so far is the double tap to wake not working.
Ya that's ROM wide and will be fixed
Sent from my One M8 using Tapatalk
Are the updates OTA due to your own recovery being required?
Sent from my X9006 using Tapatalk
Well I guess TWRP would back my system up if my SD card wasn't in NTFS..noob..after I format it back to fa32 and put everything back on it I'll flash this rom and try it out. Thanks guys!
Hard to believe the initial post of no known issues with the first build but if it's true then that's gorgeous.
Well it's gorgeous either way.
Will give this and omni a test run later today.
Can't wait actually... Given the mediocre setup we have been presented with coloros.
Gesendet von meinem One mit Tapatalk
It works pretty well so far! Just played around with it for half an hour.
Two things I noticed: The camera does not go into landscape mode. And the Storage is still divided into two partitions (like ColorOS) Is it possible to unite them into one?
Awesome work so far!
The only issue i noticed in short test time, double tap to wake doenst work as wrote here before, double tap to sleep work
And one important question for me: Does the modem use Band 20 for LTE? I cant test it at that moment.
And it seems to be that fast charging works too. But iam not sure, because i charge at 36%, after 20 min. it was at 42% and 30 min later it was at 96%. There was a big jump in charging in 30 min.
betold said:
It works pretty well so far! Just played around with it for half an hour.
Two things I noticed: The camera does not go into landscape mode. And the Storage is still divided into two partitions (like ColorOS) Is it possible to unite them into one?
Awesome work so far!
Click to expand...
Click to collapse
will reply to this how I did over at oppo forums..
This is the way it is in colorOS as well I believe. We could have asked everyone to re-partition their internal sdcard but that's retarded. for one.. you would lose your pictures etc etc that you have taken using COS..
kejar31 said:
will reply to this how I did over at oppo forums..
This is the way it is in colorOS as well I believe. We could have asked everyone to re-partition their internal sdcard but that's retarded. for one.. you would lose your pictures etc etc that you have taken using COS..
Click to expand...
Click to collapse
You have been on ColorOS haven't you...?
Then you probably know the issues it has...
And now we got source-baked roms...
FOR CHRISTS SAKE DO YOU REALLY THINK ANYONES GOING BACK TO THAT HELLHOLE?! :silly:
But no, seriously. ColorOS is in the past for me one way or another, I gave it a chance, it failed. Hell even the CM11s port does a way better job at handling this device than ColorOS does.
So if I leave the old system behind, why not get the most of the "new" system anyway?
Part of that would be unified partition layout if you ask me.
MrColdbird said:
You have been on ColorOS haven't you...?
Then you probably know the issues it has...
And now we got source-baked roms...
FOR CHRISTS SAKE DO YOU REALLY THINK ANYONES GOING BACK TO THAT HELLHOLE?! :silly:
But no, seriously. ColorOS is in the past for me one way or another, I gave it a chance, it failed. Hell even the CM11s port does a way better job at handling this device than ColorOS does.
So if I leave the old system behind, why not get the most of the "new" system anyway?
Part of that would be unified partition layout if you ask me.
Click to expand...
Click to collapse
This is the way it is and will be for compatibility... I guarantee that all respectable AOSP ROM's will do the same.. In the meantime I am sure someone will release an aftermarket hack for people who want this..
kejar31 said:
This is the way it is and will be for comparability... I guarantee that all respectable AOSP ROM's will do the same.. In the meantime I am sure someone will release an aftermarket hack for people who want this..
Click to expand...
Click to collapse
I see no reason why it can't be done as a optional x-plattform feature.
LVM2 works via loopfiles just as much as it does via physical devices, make your script format /data and /internal_sd if you want and place 2 LVM loopfiles into both folders, taking up the device space there.
Then on bootup simply check whether the loopfiles exist or not, if they do bring up the volumegroup and mount the unified storage, if not go with the convential setup.
MrColdbird said:
I see no reason why it can't be done as a optional x-plattform feature.
LVM2 works via loopfiles just as much as it does via physical devices, make your script format /data and /internal_sd if you want and place 2 LVM loopfiles into both folders, taking up the device space there.
Then on bootup simply check whether the loopfiles exist or not, if they do bring up the volumegroup and mount the unified storage, if not go with the convential setup.
Click to expand...
Click to collapse
https://github.com/TEAM-Gummy
there is the source.. start with that, make it yourself
kejar31 said:
https://github.com/TEAM-Gummy
there is the source.. start with that, make it yourself
Click to expand...
Click to collapse
I might just do that when I find the time to invest into it. :fingers-crossed:
{
"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
Q&A for [ROM][5.0.2][SM-T700, T800] BlissPop by Team Bliss
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][5.0.2][SM-T700, T800] BlissPop by Team Bliss. 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!
jewnersey said:
new build in OP and post 27
Click to expand...
Click to collapse
Does the vpn work in this build?
chbdetta said:
Does the vpn work in this build?
Click to expand...
Click to collapse
dont know, havent tried, probably not. But i see some commits from barracuda so i will grab them and use them on the next build
Will you also support The T805 at certain point, course 5here is almost nothing for The T805. Aren't there any devs with worlds best tablet?
No t805 for now unfortunately
problem with my camera !!!!!!!!
Hii,I have a problem with the camera application, it closes by itself and there is a superposition SETTINGS and three buttons (pan mode, take photo and video mode) what it is and how to solve it? I would like to know if I'm the only one that this happens ...?! and the touch keys even installing your ZIP file by mounting / system it still does not ... normal ?! What ?! tell me please ... put everything aside from that .. great job on this ROM !!
GPS and key back light issues
I read through the posts in the other thread, but don't see any mention of GPS issues. I tried GPS status on the stock ROM and it was fine. On this one, it doesn't see any satellites. I am on a T800. Is this a known issue or is there a fix I can try?
I see the latest build for the T700 has the back light setting restored. Will you be able to fix that for the T800 too?
Thanks for your efforts.
Loving the ROM. Only thing I noticed so far is that it only detects 5ghz network with channel 36. Weird. But overall great.
Sent from my LG-D851 using XDA Free mobile app
slayer97 said:
Hii,I have a problem with the camera application, it closes by itself and there is a superposition SETTINGS and three buttons (pan mode, take photo and video mode) what it is and how to solve it? I would like to know if I'm the only one that this happens ...?! and the touch keys even installing your ZIP file by mounting / system it still does not ... normal ?! What ?! tell me please ... put everything aside from that .. great job on this ROM !!
Click to expand...
Click to collapse
Camera is gonna have problems.. There are numerous posts about it in several different threads.
Not sure about the button zips. Both work perfectly for me. Will wait to hear how other people fare.
JohnnieD72 said:
I read through the posts in the other thread, but don't see any mention of GPS issues. I tried GPS status on the stock ROM and it was fine. On this one, it doesn't see any satellites. I am on a T800. Is this a known issue or is there a fix I can try?
I see the latest build for the T700 has the back light setting restored. Will you be able to fix that for the T800 too?
Thanks for your efforts.
Click to expand...
Click to collapse
I haven't tried GPS but I'll see if I can sort out the problem. T700 has some different vendor blobs that I snagged from a lollipop leak for the note3.
T800 build coming down the pipe in a few hours
When is the next update of this ROM?! I likeI like the work done on this ROM, so I am interested in and I look forward to see more...!!!
Overview Button
Overview button wasnt installed with the rom or do i need to turn this on somewhere?
LoganC990 said:
Overview button wasnt installed with the rom or do i need to turn this on somewhere?
Click to expand...
Click to collapse
see the second post in the main thread for zips to fix the keys (must mount /system before flashing)
- mixed results with this
OR, manually edit the Generic.kl file (EXTREMELY EASY), as instructed in the same post as the downloads
Tried both still no result of the overview button appearing the changing of the file did fix the recent apps button but didnt add the others.
This?
{
"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"
}
Otherwise I have no idea what you're taking about
Yea it was the On Screen Nav Buttons i was needing thanks
Anyway great post/rom, do you think this will be made for the Galaxy Alpha SM-G80F? Or has it
You could always do it. . I'd be happy to guide you through the process. I had 0 experience with this until about 3 months ago (and no coding background) and I'm doing okay. Tab S is particularly annoying because it's fairly under-supported compared to other devices. Essentially, if there is a working cm12 build for your device (or any other lollipop), you can build this with limited difficulty.
jewnersey said:
You could always do it. . I'd be happy to guide you through the process. I had 0 experience with this until about 3 months ago (and no coding background) and I'm doing okay. Tab S is particularly annoying because it's fairly under-supported compared to other devices. Essentially, if there is a working cm12 build for your device (or any other lollipop), you can build this with limited difficulty.
Click to expand...
Click to collapse
That would be good would be good to use a rom i made so basically will i be taking a already made rom thats running lollipop and then changing it to work for Alpha?
5ghz not working
Review this link - http://forum.xda-developers.com/galaxy-tab-pro-12-10-8/general/cm12-port-lollipop-5-0-1-t900-galaxy-t2973591/page3
LoganC990 said:
That would be good would be good to use a rom i made so basically will i be taking a already made rom thats running lollipop and then changing it to work for Alpha?
Click to expand...
Click to collapse
You'll be taking source code, making a few changes (manual) and building from scratch ("automatic").
Pm me and we can start chatting on hangouts.
Great rom! Just flashed it yesterday and been having fun ever since. I also tried the Remote Play App to play on PS4. Got it to connect, however it shows the controls overlay on screen, but not the stream of the PS4. I already disabled HW overlays. Does anybody here have a similar experience? Also looked in the Remote Play thread.
Other than that, the notifications on the lockscreen are dark grey. In other screens I have seen that they have a lighter color. Is this configurable somewhere? Haven't been able to find that yet.