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
Related
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
Hello
Will we see a Firefox OS port for the Desire Z?
+1 on this
Greets Vauvenal7
Sent from my myTouch 4G Slide
If you read up on Firefox os chances are that our phone isn't the best suited for it and being there are so few developers left here it is unlikely someone wants to pick up a project of this sort that will unlikely run well on the g2/dz
Sent from my Nexus 7 using xda premium
Firefox OS for Vision? Not so sure. It's not even commercial yet (I don't think, not in UK at least) so if we do see it on our device it won't be for a while. Unless you're willing to do it, of course, I'd definitely give it a go if that were the case. There are guides out there, and I'm certain the Vision is powerful enough to run it.
If you're anxious to try it, you can run it on your PC, either by emulating ARM or running the x86 OS.
If you're anxious to try it on your Desire Z, you're probably in for a long wait. You'll see it on Nexus before it comes to our device, and even that has yet to happen.
Patience, young padawan.
FYI, being a long time satisfied HTC Desire Z user and hacking on B2G for a while now (with Nexus S) I started working on running B2G on this device.
While it works not that bad, I limited myself to a quick hack thanks to the fosmaker tool. It needs a bit of help at Gecko and Gaia level :
- hwcomposer is not working, because it is an old version. This might result in some degraded graphic performances
- automatic brightness is gaia does not like the light sensor of this device, and sets the level too low when not facing light
- automatic network selection somehow is not enabled by default by the RIL, we need to force it on gecko side
- data call reply is incorrectly read by gecko, thus making him think the data call did not succeeded while it did
- physical keyboard events are correctly grabbed but do not make it to the destination, I have no ide why yet
- remapping the trackpad to the home button works, but you need to teach the keyboard input mapper layer of gecko/gonk about the Android keycodes for this (since the scancode it emulates is a mouse left click)
- placing calls/sms works, with the limitation that somehow main audio channel stays mute after a call is ended: no sound from keypad, videos, etc. But you can still call without any issue and it might be an issue I'm reproducing on other devices ...
- picture/video recording used to work last week, it got broke, but there's huge refactoring still happening on gfx layers, and gralloc is far from being correctly handled
- bluetooth works, I could pair with another Firefox OS phone (Nexus S) and exchange files
So to have something very perfect there is still some work to do, but nothing impossible if you want and have time. Anyone willing to hack and support this device is welcome to contribute !
This is more PoC patch than totally perfect (even if some part is waiting review to get into master), yet I added support (hackish) for forcing network automatic selection, support for the old ril so that SIM IO works and also data calls.
I don't have the time to ensure active support, but I can help someone who would like to.
Hello,
Those patches got a bit outdated, but current B2G master runs quite fine on Desire Z . Especially, thanks to Michael Wu's help, we have been able to test and acknowledge patches that makes the physical keyboard working, the bug being tracked at https://bugzilla.mozilla.org/show_bug.cgi?id=890186.
So if anyone is willing to jump in and help support B2G on this device, there is some nice and not too hard work to perform to enhance the support, please do not hesitate to ask me
FYI I've updated my branch with latest master and rebased some commits: BerTlvHelper just landed, and it processes FCP Template payload correctly, so I'm making use of it! So far I also fixed data call, the only thing I can't understand is why I have to force automatic mode by hand a couple of times to get RIL to register automatically on the correct network.
Some of the RIL related changes have finally been merged, thanks to a concurrent effort made by sku for supporting Fugu device. Having discussed with him, we are on good track to have the needed changes for Desire Z merged some day .
I still have a separate branch for: data call handling, home button hacking. Meanwhile, I'm stuck for building a complete image because of the lack of buildable sources for either 4.0.4 or 4.3 ROMs for this device. Hacking on prebuilt images has its limits when it comes to having nice and complete support ... If some of you can help me on this specific point any help is appreciated !
FTR, the master-HTC_Vision branch is available at https://github.com/lissyx/mozilla-central/tree/master-HTC_Vision
Just to summup since a couple of people asked me this by other channels: more or less most of the features are working. Major breakages are on Camera and Video decoding, which are broken.
My current setup to get B2G on this device is:
- follow the build steps that are documented on the Mozilla Wiki.
- configure (BRANCH=master) and build for an ICS-based device ; emulator should be fine, I'm re-using my Nexus S source tree.
- make sure to checkout my master-HTC_Vision branch for the gecko repository.
- flash an ICS ROM on the device, I'm using Andromads Audacity beta 5.
- extract boot.img, add a import init.b2g.rc line at the top, and add a init.b2g.rc file from the b2g gonk-misc repository, then flash back this new boot.img
- extract system.img, inject /system/bin/b2g.sh, /system/bin/rilproxy and /system/bin/fakeperm. Also inject /system/b2g/ and flash back this new system.img
- you can use the fosmaker (http://code.google.com/p/fosmaker/) project to perform those two steps: beware that fosmaker embeds an old version of b2g, so you'll have to search for its b2g/ subdirectory in the provided tarball and replace it with what you built.
On next reboot of the device, you should get B2G working.
Just a quick update to let you know that I rebased my master-HTC_Vision branch against uptodate master. Since there have been changes in the RIL worker, I hacked my code and finally fixed the automatic network selection by forcing automatic mode. So this is working not that bad, now
Another quick update with pics to show that I'm not bluffing . One pic of H264 playback on the device from within Browser app, and another of geolocation in HERE Maps.
View attachment 2548430
{
"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"
}
I'm still pushing to this master-HTC_Vision branch.
FYI, I get camera working if I build Gecko re-using my Keon's source tree
Hello,
I'm still hacking this, even though I have a hard time with the Camera: on Gecko master built from Keon's tree, it partly works. When camera preview runs, if you take a picture, you get a photo taken but it's all scrambled. This does not reproduces with the same exact code except if you turn off the preview in the Camera app (by hacking it). So you can takes pictures, but blindly.
Apart from this, I've pushed rebased code to the master-HTC_Vision on top of current master, and took some time to fix network. I now get my MVNO SIM card with a PIN code detected, I can unlock it, it correctly automatically select network, and I can place calls, send/receive SMS, place data calls (HSDPA).
No big news, I'm still pushing regular updates for the gecko branch for this device, still the same issues
Hello!
Is there any news about this project? Does it build and run?
Thanks!
asp2010 said:
Hello!
Is there any news about this project? Does it build and run?
Thanks!
Click to expand...
Click to collapse
Well I'm still pushing Gecko to the branch and building it, so yes, it does work, but it's not off the shelf .
FYI I've been recently relying on Desire Z for hacking and testing a LED API in Gecko.
Hi !
I've tried to follow your intruction, and the one on mozilla's website, but I get stuck on the HTC*logo.
Are you planning on adding a new configuration tree for the Desire Z ? So, it would be easier to build a version.
Thanks
Lippen said:
Hi !
I've tried to follow your intruction, and the one on mozilla's website, but I get stuck on the HTC*logo.
Are you planning on adding a new configuration tree for the Desire Z ? So, it would be easier to build a version.
Thanks
Click to expand...
Click to collapse
No. Thanks for trying though, but I don't have a configuration tree even to build, it's a total hack and I cannot afford spending much time than this kind of hacking. If you are willing to, I can help you though
{
"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
{
"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
{
"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"
}
SlimRoms is a custom android operating system. Our main goal is to offer users a slimmed down yet feature rich alternative to other android operating systems.
The entire SlimTeam work together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code.
All of the sources can be publicly viewed through GitHub and you can stop by our public Gerrit to submit patches of any type.
Slim6 is the project name for SlimRoms based on Android 6.0.1 Marshmallow and offers the following original features:
SlimLauncher
Slim Recents
Navbar customisations & Hardware key rebinding
Custom QuickSettings
Chamber of secrets and SlimActions shortcuts
Doze/Ambient display options
Proximity wake and speaker
Status bar customizations (Clock and Battery)
Advanced reboot menu
Important Links
slimroms.org - Our official website and your source for anything SlimRoms related.
Downloads - Slimify your device!
Installation instructions - Follow these steps if you want SlimRoms on your device.
FAQ - Have a question? Consider reading our FAQ first, you might find your answer there!.
Report-bugs - Found a bug? Send it our way!
Kernel Source - The source of your device's kernel.
Get in touch! - You can contact SlimRoms at these places if you have questions, requests or feedback.
Google+
Twitter
Facebook
Disclaimer: We are not responsible for any damages to your device.
XDA: DevDB Information
Slim6, ROM for the Motorola X Pure
Contributors
@thompatry, @gmillz, @javelinanddart
Source Code: https://github.com/SlimRoms
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Based On: AOSP, CAF, CyanogenMod
Version Information
Status: Beta
Current Issues:
Speaker phone mic is very quiet
Created 2016-010-16
Last Updated 2016-10-17
I have taken over for @gmillz on maintaining this device. He is still helping me but he does not have as much time to dedicate to it like he use to.
thompatry said:
I have taken over for @gmillz on maintaining this device. He is still helping me but he does not have as much time to dedicate to it like he use to.
Click to expand...
Click to collapse
Thank you, already installing...
this may sound stupid because the rom is still in alpha state, but is it already good for everyday use? thanks!
Sent from my XT1575 using XDA-Developers mobile app
You may experience some issues, but it's definetly a daily driver. I would call it beta
I would not give it Daily Driver status... it has potential but not there yet.
xxhunterxx11 said:
this may sound stupid because the rom is still in alpha state, but is it already good for everyday use? thanks!
Sent from my XT1575 using XDA-Developers mobile app
Click to expand...
Click to collapse
OCmylife said:
You may experience some issues, but it's definetly a daily driver. I would call it beta
Click to expand...
Click to collapse
Jimi Mack said:
I would not give it Daily Driver status... it has potential but not there yet.
Click to expand...
Click to collapse
It's really really stable actually, @thompatry did weeks worth of testing before releasing. The only bug that has been noticed is the bug where mic is quiet with speakerphone
Awesome!!
nice, long time since i have seen a new rom
javelinanddart said:
It's really really stable actually, @thompatry did weeks worth of testing before releasing. The only bug that has been noticed is the bug where mic is quiet with speakerphone
Click to expand...
Click to collapse
+1 I'm actually surprised how well its running.
Sent from my XT1575 using Tapatalk
There are a lot of changes incoming. (for the most part they are related to the kernel) The force reboot issue, which could happen is already fixed and only have to be merged. I'm really happy that we have devs like them :highfive:
https://review.slimroms.org/#/q/status:open
OCmylife said:
There are a lot of changes incoming. (for the most part they are related to the kernel) The force reboot issue, which could happen is already fixed and only have to be merged. I'm really happy that we have devs like them :highfive:
https://review.slimroms.org/#/q/status:open
Click to expand...
Click to collapse
The changes are just updating the kernel to what CM has and they're from motorola.
Also, @thompatry and I are cracking away at the speakerphone bug. We've accomplished breaking the mic, or fixing the volume but adding some extreme feedback, or causing the device to not boot at all
So, progress
We'll try to keep you guys updated on that
If any of you have ideas to throw at us to fix it (please think through them and test if you can) please do
Would it help, if I make a adb logcat during a call?
Edit: The extreme feedback also exists on CM if you call through both speakers instead oft just the top one. If I remember correctly our MXP has 3 mics, 2 for noice cancelling. Maybe disabling one or two would help
Am I missing it or is there no customization of the Power Menu?
Plus boot up and reboot times seem very long compared to other roms for this phone
Has anyone figure how to stop the notification light from flashing while on the charger but still be set up to receive notifications without turning off the notification light?
Ah the little things do make such a difference.
---------- Post added at 03:47 PM ---------- Previous post was at 03:45 PM ----------
javelinanddart said:
It's really really stable actually, @thompatry did weeks worth of testing before releasing. The only bug that has been noticed is the bug where mic is quiet with speakerphone
Click to expand...
Click to collapse
That bug has been common in CM roms for a while, have not really sen that bug too much in AOSP roms.
OCmylife said:
Would it help, if I make a adb logcat during a call?
Edit: The extreme feedback also exists on CM if you call through both speakers instead oft just the top one. If I remember correctly our MXP has 3 mics, 2 for noice cancelling. Maybe disabling one or two would help
Click to expand...
Click to collapse
Jimi Mack said:
Am I missing it or is there no customization of the Power Menu?
Plus boot up and reboot times seem very long compared to other roms for this phone.
---------- Post added at 03:47 PM ---------- Previous post was at 03:45 PM ----------
That bug has been common in CM roms for a while, have not really sen that bug too much in AOSP roms.
Click to expand...
Click to collapse
You'd have to dig around, I don't think so but I'm not sure
Pretty sure there isn't extreme feedback on Slim, or so I was told by @thompatry, I don't own a clark myself.
Dunno about reboot times tho
And yeah, we're aware its a common bug on a lot of roms, but we're not letting that stop us
We'll get there eventually
I had one reboot during a call and few ui freezes.... Btw the rom is awsome and it sleeps like a baby. Thanks! Waiting for the next =]
very stable rom fast and smooth and light no bloatware at all, is there anyway to add the color calibration from stock versions i just like the saturated colors hehe
This rom is amazing. Its is one the fastest I have seen on the X Pure. Thanks a lot
Can you please add clear all option in the recents panel and advanced reboot option?
I'm facing a bug: Whenever someone calls me I'm unable to hear their voice but they can hear me, but when I call them both of us are able to hear each other and there are no problems.
HPAR said:
I had one reboot during a call and few ui freezes.... Btw the rom is awsome and it sleeps like a baby. Thanks! Waiting for the next =]
Click to expand...
Click to collapse
Glad to hear you like it! Log from random reboot?
aakashverma0007 said:
This rom is amazing. Its is one the fastest I have seen on the X Pure. Thanks a lot
Can you please add clear all option in the recents panel and advanced reboot option?
Click to expand...
Click to collapse
We already have advanced reboot under the security options (I think, it's been a while since i turned it on)
aakashverma0007 said:
I'm facing a bug: Whenever someone calls me I'm unable to hear their voice but they can hear me, but when I call them both of us are able to hear each other and there are no problems.
Click to expand...
Click to collapse
Log? And can you reproduce this on another phone? If so, it might be on their end
SOU55 said:
very stable rom fast and smooth and light no bloatware at all, is there anyway to add the color calibration from stock versions i just like the saturated colors hehe
Click to expand...
Click to collapse
Glad to hear the ROM is good, but we didn't tweak color calibration from cm's kernel, and unless it's handled in-kernel, there's no way for us to add it, and I'm almost 100% positive that we're using a motorola based kernel.