yashsingh1/xdaforums huggingface dataset:
[Oppo Find 7 and 7a] jallenhayslett:
Well, evidently they merged all the model specific stuff into two branches for COS2.0, one Chinese and one International. But pre-2.0, they were doing model specific builds. But, since Omni isn't working properly with 2.0 yet, I had to go with the 1.2.x X9070 build.

Hell, the X9070 didn't even have LTE enabled when they first released it. Users had to wait for an OTA update that enabled use of the proper LTE frequencies on China Unicom.
[Oppo Find 7 and 7a] uppon2:
Still happening to me at 30% battery, though it's only annoying when I want a quick charge
[Oppo Find 7 and 7a] beton87:
OK, I may actually learn something :P But of cource it won't work.

I made an init of repo with branch android-5.0, breakfast find7 made me a neat local manifest that seems ok:

<?xml version="1.0" encoding="UTF-8"?>
<!--Please do not manually edit this file-->
<manifest>
<project name="android_device_oppo_find7" path="device/oppo/find7" remote="omnirom" revision="android-5.0" />
<project name="android_hardware_qcom_display-caf-bfam" path="hardware/qcom/display-caf-bfam" remote="omnirom" revision="android-5.0" />
<project name="android_hardware_qcom_media-caf-bfam" path="hardware/qcom/media-caf-bfam" remote="omnirom" revision="android-5.0" />
<project name="android_hardware_qcom_audio-caf-bfam" path="hardware/qcom/audio-caf-bfam" remote="omnirom" revision="android-5.0" />
<project name="android_device_oppo_msm8974-common" path="device/oppo/msm8974-common" remote="omnirom" revision="android-5.0" />
<project name="android_kernel_oppo_msm8974" path="kernel/oppo/msm8974" remote="omnirom" revision="android-5.0" />
</manifest>

but brunch find7 fails with error:

build/core/product_config.mk:227: *** _nic.PRODUCTS.[[device/oppo/find7/omni_find7.mk]]: "frameworks/native/build/phone-xxhdpi-2048-hwui-memory.mk" does not exist. Stop.
WARNING: Trying to fetch a device that's already there
build/core/product_config.mk:227: *** _nic.PRODUCTS.[[device/oppo/find7/omni_find7.mk]]: "frameworks/native/build/phone-xxhdpi-2048-hwui-memory.mk" does not exist. Stop.

** Don't have a product spec for: 'omni_find7'
** Do you have the right repo manifest?

No such item in brunch menu. Try 'breakfast'

Repo sync was successful. breakfast find7 gives exactly the same error. It seems some makfiles are missing or did I just had bad luck with sync in time when not everything is merged?
[Oppo Find 7 and 7a] tork987:
Same here.

https://plus.google.com/111636206976026955175/posts/FcceLhQsbNA
[Oppo Find 7 and 7a] beton87:
I just edited the default manifest uner omni/.repo/manifests.default.xml as maxwen suggesten on g+ to point at android-5.0-caf

Now I don't get errors, just:

============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=5.0.2
TARGET_PRODUCT=omni_find7
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=krait
TARGET_2ND_ARCH=
TARGET_2ND_ARCH_VARIANT=
TARGET_2ND_CPU_VARIANT=
HOST_ARCH=x86_64
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.13.0-40-generic-x86_64-with-Ubuntu-14.04-trusty
HOST_BUILD_TYPE=release
BUILD_ID=LRX22G
OUT_DIR=/home/bial/android/omni/out
============================================

make: *** Brak reguł do wykonania obiektu `bacon'. Stop.
/* translation: No rules defined for creating object 'bacon'. Stop */
real	0m0.018s
user	0m0.005s
sys	0m0.018s

Still something is missing. Build instant finish with make error, something that rules for 'bacon' are not defined.

EDIT: After laptop reboot it started. Maybe something about system updates before. Now it's not instant build in 0s but it's getting warm.
[Oppo Find 7 and 7a] tork987:
i have now other issue :D

============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=5.0.2
TARGET_PRODUCT=omni_find7
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=krait
TARGET_2ND_ARCH=
TARGET_2ND_ARCH_VARIANT=
TARGET_2ND_CPU_VARIANT=
HOST_ARCH=x86_64
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.13.0-37-generic-x86_64-with-LinuxMint-17.1-rebecca
HOST_BUILD_TYPE=release
BUILD_ID=LRX22G
OUT_DIR=/home/sergej/android/omni/out
============================================
Checking build tools versions...
************************************************************
You are attempting to build with the incorrect version
of javac.

Your version is: javac 1.6.0_33.
The required version is: "1.7/1.8"

Please follow the machine setup instructions at
https://source.android.com/source/download.html
************************************************************
build/core/main.mk:219: *** stop. Schluss.

real0m4.105s
user0m2.744s
sys0m1.312s

EDIT: after update openJDK. it works

Edit 2.: I'm run out of storage :(
[Oppo Find 7 and 7a] beton87:
That's easy. You were referring to old guide. You try to build with javac with java 1.6. You need to swich to newer one. Find a guide for linux mint like this one: http://community.linuxmint.com/tutorial/view/1372 You may have java 1.7 already installed, then you just have to update alternatives to use it. If not, install java 1.7 or 1.8, openjdk or oracle jdk

EDIT: And my homemade build boots to black screen :( [MENTION=4683552]maxwen[/MENTION], any hints?

Local manifest made with breakfast, added DonkeyCoyote repo for properitary files like in wiki, changed frameworks/native and frameworks/av to android-5.0-caf

My build is stuck at omni logo and device is getting warm.
[Oppo Find 7 and 7a] maxwen:
You need to create a logcat so you need to create a "eng" build which enables unsecure adb to get access at this stage

Just config for omni_find7-eng and to a clean rebuild (lunch omni_find7-eng)

Must show TARGET_BUILD_VARIANT=eng then

With that you can use adb logcat to capture a log from booting - share that log here
[Oppo Find 7 and 7a] beton87:
That would be too easy ;) Build fails at:

target StaticExecutable: twrpTar_static (/home/bial/android/omni/out/target/product/find7/obj/UTILITY_EXECUTABLES/twrpTar_static_intermediates/LINKED/twrpTar_static)
bootable/recovery/twrpTarMain/../twrpTar.cpp:1246: error: undefined reference to 'tw_set_default_metadata'
collect2: error: ld returned 1 exit status
make: *** [/home/bial/android/omni/out/target/product/find7/obj/UTILITY_EXECUTABLES/twrpTar_static_intermediates/LINKED/twrpTar_static] Błąd 1 //Error 1
make: *** Oczekiwanie na niezakończone zadania.... //Waiting for unfinished tasks

Should I ask [MENTION=702506]dees[/MENTION] Troy about it?
[Oppo Find 7 and 7a] maxwen:
open file bootable/recovery/Android,mk

change line

LOCAL_MODULE_TAGS := eng optional

to

LOCAL_MODULE_TAGS := optional

I already told Dees_Troy the problem
[Oppo Find 7 and 7a] beton87:
Thanks for help, but now I have to figure out why repo sync is always stuck at fetching project device/generic/mini-emulator-x86-64

It just freezes at

: load refs ~/android/omni/.repo/projects/external/clang.git

EDIT:

Ok, repo is crap. Some of scripts is adding project android_device_oppo_find7a to roomservice local manifest, which does not exist on github because from what I remember the device tree is unified to android_device_oppo_find7

After removing that from roomservice, sync is fixed.
[Oppo Find 7 and 7a] maxwen:
should be fixed now with this

https://gerrit.omnirom.org/#/c/11011/
[Oppo Find 7 and 7a] beton87:
That was fast :)

Another issue with eng build: Bluetooth

Output attached
[Oppo Find 7 and 7a] maxwen:
run make update-api once
[Oppo Find 7 and 7a] Entropy512:
Actually, whoever broke the API should, as the error says, use [MENTION=6259787]hide t[/MENTION]o unbreak it...

Surprised it broke in Bluetooth as those audiofx definitions are somewhere else...

We should never be using "make update-api"...

I really hope I get some time over the holidays to do some cleanup stuff... Like finishing the CAF ifdefing!
[Oppo Find 7 and 7a] maxwen:
It's already on gerrit - plodey broke it a long time ago :)

Just to continue run update-api for now
[Oppo Find 7 and 7a] beton87:
Now I got a bootloop with logcat :) I also flashed TWRP 2.8.3.0. Now I can actualy see popup with updating application for a fraction of a second before reboot.

Find7a LVM (and I have a 64 GB sd card with exfat that [MENTION=4683552]maxwen[/MENTION] has fixed, and I want a build to make it running )

logcat here: http://ge.tt/2kmoCJ72/v/0?c

Aaand it seems lika a LVM issue:

12-22 20:42:28.026 3188-4006/? E/AndroidRuntime﹕ *** FATAL EXCEPTION IN SYSTEM PROCESS: MountService#onDaemonConnected
java.lang.IllegalArgumentException: Failed to find storage device at /storage/emulated/0
at android.os.Environment.isExternalStorageEmulated(Environment.java:791)
at android.os.Environment.isExternalStorageEmulated(Environment.java:775)
at com.android.server.pm.PackageManagerService.isExternalMediaAvailable(PackageManagerService.java:7917)
at com.android.server.pm.PackageManagerService.startCleaningPackages(PackageManagerService.java:7957)
at com.android.server.pm.PackageManagerService.updateExternalMediaStatusInner(PackageManagerService.java:12895)
at com.android.server.pm.PackageManagerService.scanAvailableAsecs(PackageManagerService.java:12808)
at com.android.server.MountService$3.run(MountService.java:864)
[Oppo Find 7 and 7a] maxwen:
Guess you have you deleted the image you are currently running from your device right?

And : logcat or it didn't happen
[Oppo Find 7 and 7a] cdysthe:
Hi,

I did a "Clean update files" and tried again. Is that what you mean? I also have the image I flashed initially from my SD card also. Got a nes SD card yesterday. I guess that should make a difference?

Update: Sorted this one out. My cache was full. Formatted it and updates works.
[Oppo Find 7 and 7a] beton87:
[MENTION=4683552]maxwen[/MENTION] does the Oppo AOSP help any way with Omni? They promise 5.1.1 ROM, does it come with blobs/source that will help in development?

http://community.oppo.com/en/forum.php?mod=oppo_viewthread&tid=42645

I wonder which one will work better - Omni or Spectrum ;)
[Oppo Find 7 and 7a] anwedr:
I was thinking the same thing given Entropy helped Oppo shift over to LVM and such.

Unless there's Omni staff assisting the Oppo AOSP, I can only assume Omni be the more stable Rom than Spectrum.
[Oppo Find 7 and 7a] maxwen:
The time there is something to see we have left 5.1 behind for sure :)

But getting newer blobs is always helpful
[Oppo Find 7 and 7a] cdysthe:
BackupManager fills my cache.

Every morning /cache is completely full preventing updates. I have to clear the cache before I can update. The cache is filled with files in the /cache/backup/1/_full directory. The files seems to be linked to my installed apps with names like org.fdroid.fdroid and com.pandora.adroid. The whole cache is filled with those files. There's also a _delta directory which doesn't take up much space. Why and when is my cache being filled and can I do something to prevent it?

UPDATE: I logged my phone over night and at the time my cache get filled this starts:

Starting com.android.server.backup.BackupManagerService$Lifecycle

So it's the BackupManager that fills the cache for some reason. I have not had problems with the in the past. Could I just turn it off, or is it some way for me to have the backup end up on Google servers instead of my cache?
[Oppo Find 7 and 7a] memooffon:
Flash charge not work for me just 1,200 mA

Could anyone confirm if it same.
[Oppo Find 7 and 7a] cdysthe:
Works here on my X9076
[Oppo Find 7 and 7a] maxwen:
what ever "flash charge" means

why you don't you use the correct term VOOC?
[Oppo Find 7 and 7a] cdysthe:
I assumed it meant the fast charge you get with the Oppo charger. On COS it shows in the lock screen when you are getting that kind of charge.
[Oppo Find 7 and 7a] supermooshman:
Anyone have a mirror for gapps?

The link provided seems to be down

http://downforeveryoneorjustme.com/http://fitsnugly.euroskank.com/
[Oppo Find 7 and 7a] cdysthe:
Stock TK-Gapps here:

https://www.androidfilehost.com/?w=files&flid=31523

This is the one I've been using without problems.
[Oppo Find 7 and 7a] kishd:
Just thought I would upload a link to the firmware and modem from the new aosp spectrum ROM from OPPO.

https://www.dropbox.com/s/kovil8j6h06oyj1/modem_spectrum.zip?dl=0

Download and flash with twrp
[Oppo Find 7 and 7a] cdysthe:
I'm on a Find 7 X9076. Sorry about my ignorance, but why would I want to flash this?
[Oppo Find 7 and 7a] kishd:
No reason to flash. Just that this firmware is designed by OPPO for their 5.1.1 ROM and OmniROM is 5.1.1
[Oppo Find 7 and 7a] memooffon:
Sorry , it is ok now by remove battery a minute.

3,760 mA for VOOC and 1,800 mA for Samsung charger.
[Oppo Find 7 and 7a] maxwen:
*deleted*
[Oppo Find 7 and 7a] supermooshman:
Anyone else having this issue?

From the lock screen, a touch is recorded in the top left corner (I marked it on the screenshot in attachment)

It's been doing this every couple of days, although I haven't figured how to recreate the issue.

So far only shutting down the phone helps
[Oppo Find 7 and 7a] maxwen:
thats odd but what's the real problem?
[Oppo Find 7 and 7a] supermooshman:
My bad, I'm writing this on my phone, which somewhat messes with my proofreading...

So a more detailed description of the issue:

It only occurs when I try to unlock my phone.

At the moment I have the "show touches" setting activated, so everything I report is what I visually see (no catlog yet seeing how I always had it while being out n about).

Anyway when it happens,everything touchscreen related gives a ghost touch in the upper left corner (power and volume buttons do what they should do).

The only thing which works to unlock is to change the volume and while the volume setting is visible swipe up. If I try to unlock the phone without the volume trick, the unlock motion isn't completed as there is the extra touch (meaning the screen isn't unlocked). So far I only was able to get rid of the issue by holding the power button until the phone turns off.

Again it only happened 4 times so far
[Oppo Find 7 and 7a] znarf2369:
[MENTION=4683552]maxwen[/MENTION]

for quite a while (nightlies since early oktober) my headset button isnt working properly anymore. i used to use it to skip music tracs with a double click or play/pause it by clicking it once. i thought that the button itself broke but one the OPO of a friend it is still working flawlessly. And even the stock Oppo headset isnt working that way at all. But same on the OPO, working there.

I tried to log it, but there is not really much showing in the log.

attached it anyway

maybe you know what the problem might be?
[Oppo Find 7 and 7a] maxwen:
you have cleaned your "headset hole"?
[Oppo Find 7 and 7a] cdysthe:
Let me just confirm that I am having the same problem. I thought it was my headset button, but when seeing this post I tried with another pair and I had the same problems. I also tried my buds on a Moto X and the button works fine there. I installed an app which is supposed to fix this kind of thing and it's a little bit better and it now gives me a beep when it works. But without it it's a hit and miss. Besides I do not like yet another service running for a little (but for me important) piece of functionality.
[Oppo Find 7 and 7a] maxwen:
any other headsets other then stock are not supported - especially when it comes to mic and buttons. wired headsets are a PITA because there is no standard how buttons are handled. so yes its a miss and hit if they work or not.

e. g working for me: xiaomi piston (full with all buttons)

not working: polk (no mic and no buttons)

But that has prolly not much to do with the post above from [MENTION=4148930]znarf2369[/MENTION] which would be typical for some dust in the headset jacket
[Oppo Find 7 and 7a] cdysthe:
These buds have worked perfectly on this phone with many different ROMs. I'll dig up my Oppo buds and test with those also.
[Oppo Find 7 and 7a] znarf2369:
yes i did, was my first assumption.

but you say every headset apart from stock isnt supported. but even the stock headset button doesnt work on the find7, but as soon as i try it with another device like the OPO it works. just tried it right now. neither stock nor my usual headset works on my find7s on latest nightly, but both work on the opo of my friend. so thats why i conclude that it probably cant be anything hardware related on the headsets itself
[Oppo Find 7 and 7a] maxwen:
all the ones that ever worked still work for me :)

therefore I am pretty sure its not a regression in 5.1

but you can try by flashing a different ROM on your find7 to make sure

cause the only remaining reason is prolly not something you want to hear and that

is that the contact responsible for the button handling (the third ring) is defect in the socket

or its something that you messed up in the setup - installed any weired apps lately? :)

factorry reset just to test would allow ruling that out
[Oppo Find 7 and 7a] maxwen:
all that use CM kernel might work
[Oppo Find 7 and 7a] cdysthe:
The Oppo buds didn't work either. Maybe there's some setting or running app OP and I have in common causing this? I've had situations like that in the past. I've also used a certain lockscreen that breaks the headset button functionality so it may not be Omni itself. I just know that it doesn't work. A workaround is using an app for this. I found one that worked.
[Oppo Find 7 and 7a] maxwen:
WAIT :p
[Oppo Find 7 and 7a] maxwen:
Any chance you can define that more precisely?
[Oppo Find 7 and 7a] znarf2369:
i have a very bad memory about that but i think it was early semptember (not ocotber) when i realised it didnt work anymore. what did just came to your mind?

are there any roms you know of out there currently supporting lvm so i can try

if the headset is working or not and make sure that it is (or better hopefully not^^) my devices hardware?
[Oppo Find 7 and 7a] maxwen:
No need to try anything just for this - I have some rough ideas

Just need to verify
[Oppo Find 7 and 7a] maxwen:
fixed tomorrow
[Oppo Find 7 and 7a] cdysthe:
Now that is good news although I was beginning like the little beeping button detection app. Not ?
[Oppo Find 7 and 7a] maxwen:
Remember: ONLY thing that is for sure fixed is detection of the button on stock oppo headset - nothing more
[Oppo Find 7 and 7a] cdysthe:
I think that'll do since stock oppo buds and my Meelec ones seem to behave exactly the same way as far as the button goes. The sound on the other hand... ?
[Oppo Find 7 and 7a] cdysthe:
And now it is tomorrow and it is indeed fixed for my Meelectronics M-Duo ear-buds. Play and pause works instantly which is all I need. Thanks!
[Oppo Find 7 and 7a] Cookie Ninja:
It says that the firmware are for Find 7A..... Can I use them for my Find 7S (X9076)? Thanks....
[Oppo Find 7 and 7a] beton87:
I guess it is best to install ColorOS, let it boot, and even install latest updates. If everything is working correctly then flash twrp and Omni.

But the firmware packages work for both 7a/7s
[Oppo Find 7 and 7a] maxwen:
Please confirm if VOOC charging works with the latest version

So the "real VOOC" - if you have one of the newer chargers you will see it on the green LED on the charger

EDIT: ok forget it - seems there has been some dirt or dust in my USB jack disabling correct contact :P
[Oppo Find 7 and 7a] cdysthe:
I'm running Omni on a X9076 without problem. In fact I had much more problems with COS
[Oppo Find 7 and 7a] cdysthe:
Is there no way, through logs or otherwise, to see if VOOC works? What I have noticed is that the time to full charge on the lock screen is much shorter when I have the VOOC charger connection. With other chargers the time to full charge is often not indicated at all, it just says "charging".
[Oppo Find 7 and 7a] Cookie Ninja:
Running latest nightly on my X9076. Beautiful and better than COS 1.2.9 and Spectrum. One request.....can anyone help me with a walk around to Unify / LVM my internal SD card? Always seem to be running into some or other problems (no SD card) after flashing unify/wipe script. Currently on classic partition.
[Oppo Find 7 and 7a] cdysthe:
Is it possible that the changes that made the the headset buttons work better have been reversed? Over the last couple of day play/pause is back to being slow or non responsive.
[Oppo Find 7 and 7a] maxwen:
LOL no ☺

https://github.com/omnirom/android_kernel_oppo_msm8974/commits/android-5.1
[Oppo Find 7 and 7a] cdysthe:
I guess that settles that. That change is still on top! :)
[Oppo Find 7 and 7a] cdysthe:
The last few days I've have had to wait for full Dalvik creation after nightly updates. Any idea why that may be and if I can avoid it? Normal reboots are uneventful. I'm on a Find 7 X9076

Update: I'm back to having to do Dalvik after the nightly updates. It takes a loooong time so I would like to figure out what's going on. Any way I can find out why the Dalvik cache has to be re-created every time?
[Oppo Find 7 and 7a] maxwen:
Hm - that's odd
[Oppo Find 7 and 7a] cdysthe:
Turned out it had to do with the Play Store and a somewhat borked update.
[Oppo Find 7 and 7a] jallenhayslett:
Has anyone else noticed the haptic feedback on the capative buttons being a lot stronger in recent builds?
[Oppo Find 7 and 7a] Cookie Ninja:
Bump!!!

Any answers??? Anyone?

Dead Cookies leave no trails...
[Oppo Find 7 and 7a] javier.pc:
Ok, I'll try to help you later. I've written a little guide in some other place; I'll copy the steps...
[Oppo Find 7 and 7a] maxwen:
I still prefer to do the manual steps as described here

http://xdaforums.com/showpost.php?p=55081626&postcount=546
[Oppo Find 7 and 7a] javier.pc:
Regarding LVM, perhaps I can give some advices based in my experience. Although it is really easy to set up, it can sometimes arise a problem that can complicate things.

1. Starting from a no LVM situation, first step is to download both setuplvm_find7_FULL_WIPE_10282014.zip and removelvm_find7_FULL_WIPE.zip. Refer to these posts to find them:

http://xdaforums.com/showpost.php?p=55187001&postcount=558

http://xdaforums.com/showpost.php?p=55081626&postcount=546

Copy both files to the external SD.

Warning

! to the

EXTERNAL SD

; the setup process completely wipes internal memory AND internal sdcard, so these files need to be located in the external card.

2. Make sure you had backed up of your data to a safe place (not internal SD, of course), then reboot into recovery; a note about this: I always have used official TWRP (actually 2.8.7.2), and never had problems. No need to wipe data because LVM setup reformats data and sdcard partitions, or it should ... I've setup and removed LVM several times and once, after setting up LVM, when installing the ROM, got lots of error messages. After investigating a bit, I realized that the /data partition had no format, so I formatted it from the TWRP menu and then everything worked as expected.

Select INSTALL and locate setuplvm_find7_FULL_WIPE_10282014.zip file, confirm and let TWRP work. After flashing, reboot to recovery again.

3. As an extra precaution, you can wipe partitions, to be completely sure that everything is installed as expected. Be careful! Don't touch raw_ partitions!! This could result in loss of the LVM configuration.

4. Finally, you can install ROM as usual: flash ROM, SU, GAPPS ...

5. Reboot, configure and you're done.

Hope this helps.

Tapatalkeado desde mi ME173X
[Oppo Find 7 and 7a] maxwen:
Thanks - going to link that in other places :)
[Oppo Find 7 and 7a] Cookie Ninja:
Thanks [MENTION=2449375]javier.pc[/MENTION] and [MENTION=4683552]maxwen[/MENTION]. Much appreciated.
[Oppo Find 7 and 7a] cdysthe:
This Dalvik creation after every nightly that started a couple of weeks ago is something I would like to figure out. Should I simply factory reset or even reflash, or is there another way for me to figure out what is causing it?
[Oppo Find 7 and 7a] maxwen:
lets start with providing a full logcat from a boot. But DONT do it on the device or after booting is complete. Use adb logcat sarted right after rebooting to get ALL.
[Oppo Find 7 and 7a] cdysthe:
Here's a log from boot after the latest nightly. Had to wait for Dalvik yet again:

https://docs.google.com/uc?id=0B9gvH0bPww8-ZHhiYWxvek01eUU&export=download