yashsingh1/xdaforums huggingface dataset:
[Oppo R7 Plus] Heroeagle:
No just stuck on oppo logo then reboot sequently no cm logo appears
[Oppo R7 Plus] mkrogh65:
Fresh install of cm-13.0-20160521-NIGHTLY-r7plus.zip ...

Ran OK the the rest of Saturday.

Activated google now to make a call sunday - R7 Plus started to reboot.

Since then its boot looping every 30-45 minutes.

Im now using one of my other phones ...

I must say CM13 is not ready for this phone yet :/
[Oppo R7 Plus] maniac103:
How is Google Now related to making calls?

I must say that generalizations from specific problems don't work.

Gesendet von meinem R7plusf mit Tapatalk
[Oppo R7 Plus] mkrogh65:
Voice call -
[Oppo R7 Plus] maniac103:
I have to ask again: How is Google Now related to voice calls? IOW, what exactly did you do?
[Oppo R7 Plus] mkrogh65:
http://www.greenbot.com/article/2359684/android/a-list-of-all-the-ok-google-voice-commands.html

OK Google ... call xxx
[Oppo R7 Plus] maniac103:
The link is dead for me.

But anyway, how did you trigger Now? I assume you have 'On every screen' enabled and are speaking when the screen is on?

How exactly does the reboot loop look? Do you need to trigger another call after a reboot to get it to reboot again? Also, does it reboot to the Oppo logo or only to the CM boot animation?

Gesendet von meinem R7plusf mit Tapatalk
[Oppo R7 Plus] mkrogh65:
Yes .. from every screen enabled

Yes .. speaking with the screen on

I think - its like a soft reboot.

**Tried full reboot 2 times, but didnt solve anything

After the phone "fu**** up", it never really worked again

Meaning ... I couldnt take any calls, or dial any - result = reboot.

**Reboot to CM

Phone kinda useless right now :/

Got kinda "tired" - and grap my Moto X style ;)
[Oppo R7 Plus] maniac103:
Would it be possible for you to

install adb on your PC

enable ADB access in developer options

run 'adb logcat' on the PC

reproduce the problem (including the soft reboot)

and sending me the logcat output?

That would certainly help in debugging this issue.
[Oppo R7 Plus] mkrogh65:
Sure no problemo :)

Ill look into that this evening.

More to come ;)
[Oppo R7 Plus] teemo:
It is not the theme. The problem is, that after removing the screen lock, the fingerprints are not erased. They were earlier, but obviously that was changed.

The fix is to manually delete the fingerprints and create them again.

I get the vibrate for "wrong finger", when checking. After creating new prints, all is ok.

Edit: Almost ok. Looks like the HAL run into problems after deleting/recreating the prints, reboot helps though.

[IMG="HAL down."]http://teemo.dk/R7/HALdown.png[/IMG]
[Oppo R7 Plus] lenrek:
The theme also caused problem. It would FC when I try go into Fingerprints Setting. Revert to original/default theme fix the issue. Looks like the theme I was using has some issue: DEEP DARKNESS // CM12 / CM13. Though, I should report this to the theme developer instead...
[Oppo R7 Plus] teemo:
Yes, themes are tricky. I removed the theme before testing.
[Oppo R7 Plus] maniac103:
It indeed is. When setting the screen lock to 'None', the HAL gets the command to erase the fingerprint(s), which it does:

06-02 09:30:55.803 346 346 V fingerprintd: remove(fid=0, gid=0)
06-02 09:30:55.803 346 346 V FingerprintHAL: fingerprint_remove, id 0x00000000 gid 0x00000000
06-02 09:30:55.803 346 346 V FingerprintHAL: removeId(0)
06-02 09:30:55.803 346 346 D FingerprintHAL: clearEnrolledFingerprints()
06-02 09:30:55.878 346 346 D FingerprintHAL-QSEECom: QSEECom app fingerprints loaded
06-02 09:30:55.924 346 346 D FingerprintHAL: Cleared 1 previously enrolled fingerprints
06-02 09:30:55.936 346 346 D FingerprintHAL-QSEECom: QSEECom app fingerprints unloaded
06-02 09:30:55.937 346 346 V FingerprintHAL: goToIdleState()
06-02 09:30:55.937 346 346 V FingerprintHAL: stopWatchdogThread()
06-02 09:30:55.937 346 346 D FingerprintHAL: State machine now in idle state
06-02 09:30:55.937 346 346 D fingerprintd: onRemove(fid=0, gid=0)
06-02 09:30:55.939 25632 25632 V ChooseLockGenericFragment: Fingerprint removed: 0

However, the fingerprint list stored by the framework still contains the previously enrolled print:

root@r7plus:/ # cat /data/system/users/0/settings_fingerprint.xml
<?xml version='1.0' encoding='utf-8' standalone='yes' ?>
<fingerprints>
<fingerprint fingerId="595061550" name="Finger 1" groupId="0" deviceId="0" />
</fingerprints>

which means there's a problem in framework. I'll dig deeper.

EDIT: Deeper digging showed a problem in the HAL ;) When remove() is called with fid=0 (which means: delete everything), we're still supposed to send notifications for each removed entry. I'll fix this.

Another EDIT: Fix is here: http://review.cyanogenmod.org/#/c/147508/
[Oppo R7 Plus] lenrek:
Does this means, if lock screen was disabled, I will need to do fingerprint setup again when I enable it back?
[Oppo R7 Plus] teemo:
Awesome, thanks.

Yes, that's how it's supposed to work. I would prefer to be asked if they should be deleted, there are situations, when you want to disable screen lock and enable it again.
[Oppo R7 Plus] shadow25:
Hi [MENTION=765758]maniac103[/MENTION]

is possible to add the double tap to sleep everywhere in lock screen (I know there is it for the statusbar)? Since the R7 Plus support it by default, and because the screen is too big to get to the statusbar with one hand, would be ideal to add it. If this is not possible, could you tell me how to enable it? Thanks
[Oppo R7 Plus] lenrek:
Double tap status bar to sleep.
[Oppo R7 Plus] shadow25:
Yes, I know but read careful my post
[Oppo R7 Plus] lenrek:
There is a new nightly has the changes for fingerprint, have you tried it? Maybe is for security reason, hence if lockscreen is disabled, the stored fingerprint has to be removed.

#Update: Had flashed nightly 20160607. Now the phone would prompt about the consequence of removing device protection.
[Oppo R7 Plus] Thalkave51:
bootl r7 plus oppo

hola buenos dioas auqi saludos desde peru espero una solucion a mi consulta tengo un opp r7 plusm y hice un root pero cuando me puso la opcion de actualizar binarios en ves de poner modo normal puse modo twrp y se reinicio mi oppo r7 plus y se queda trabado en el logo de oppo y de ahi no arranca quisieras saber si tengop alguna solucion ya q quise hacerlo el hard reset pero no puedo no sales con las teclas esperopronta rrespuestas gracias
[Oppo R7 Plus] lenrek:
Camera hang in HDR-continuous shoot mode

Anyone face issue of SNAP camera hang when shoot with HDR + Continuous shoot mode? I need to reboot the phone after the camera hang in order to use the camera again.
[Oppo R7 Plus] coled3:
thread still alive?
[Oppo R7 Plus] teemo:
Yes, you just woke it up. CM is on nightly auto build. A sleeping thread just mean there are no issues to report ;)
[Oppo R7 Plus] lenrek:
The latest snapshot just released a few days ago, so ya, very much alive.

Though, I still prefer to stay with nightly.
[Oppo R7 Plus] rch.aj34:
Can comfirm , i'm on the latest nightly , 0 issues to report. overall great experience !
[Oppo R7 Plus] maniac103:
Newest nightlies should also have the echo in speaker phone mode fixed, BTW :)

Gesendet von meinem R7plusf mit Tapatalk
[Oppo R7 Plus] shadow25:
Great news, thanks ;)
[Oppo R7 Plus] 64bitss:
Hi,

I recentlyflashed my r7 plusF singapore to cyanogenmod 13 today, had to downgrade colourOS as the latest version disabled fastboot. No problems flashing after that.

I'm on the latest snapshot build (20/8/16). Everything works fine except the GPS (tested on google maps & pokemon go), either its a grey dot (based on last wifi I was connected to) or it flat out does not work.

I've tried replacing the gps.conf to my country's, download gps fix and status apps, turned the various settings on and off (auto time & date, sync, gps scanning), reboots and cache clears.

With some success, I've managed to get it to work (gps status & toolbox app), but I observed that the fix was temporary as every time I wanted to use the GPS, I had to run gps status & toolbox app for it to start working. Also the location tracker (blue dot) on google maps doesn't move as fluidly as it did on stock ColorOS, it moves like old gpses with the 1 second interval updates teleports and is slightly delayed.

Back on ColorOS, the gps worked smoothly on its own. As I use my GPS at least once a week (Google Maps when driving), I'm looking for a more permanent solution.

I was thinking of either wiping and re-flashing the ROM again or switching to the nightly build but don't know which route to go.

Update: Couldn't wait any longer, decided to flash to 24/8/16 nightly build, gapps micro version, now gps works "fine" without needed to edit gps.conf or the use of any third party apps. The 1 second interval update teleports still exist.
[Oppo R7 Plus] oppoau:
I read on here few weeks ago that the Speaker phone echo issue has been addressed. I'm on the latest nightlies however the issue is still there. Anyone know what's going on? Do I need to do a fresh install rather than dirty flash?
[Oppo R7 Plus] murkeyone:
Just come back to CM13 from PS, on CM13 Nightly 20160910, clean flash.

It still echos on the speakerphone for the caller when i tested earlier.

:(
[Oppo R7 Plus] maniac103:
Yes, it'll still echo, but it will echo significantly less than before and won't echo more than on ColorOS.

Gesendet von meinem R7plusf mit Tapatalk
[Oppo R7 Plus] lenrek:
Just notice new entry into R7+ CM13 change log:

https://review.cyanogenmod.org/#/c/163814

Better battery performance? :D
[Oppo R7 Plus] uyab.com:
I try CM 13 hoping this will do great.. It does.. At first..

After that so many apps unfortunately has stopped..

Facebook, browser, camera.. Many apps many times..

Did I do wrong steps? I have wiped data, cache, dalvik.. Reinstall the ROM but the issue persist..

Pls advice..
[Oppo R7 Plus] lenrek:
Anyone had tried the latest (20161113) nightly? My phone can't boot up after flashed it.
[Oppo R7 Plus] maniac103:
Got a logcat by any chance?

Gesendet von meinem R7plusf mit Tapatalk
[Oppo R7 Plus] Jarno666:
Tried latest nighty (20161113), couldn't boot, back to previos version.
[Oppo R7 Plus] Texan1:
Exactly the same here :mad: Tried flashing back an older version but still stuck on the Oppo logo when trying to boot. Have a done a full wipe too.
[Oppo R7 Plus] lenrek:
I used it as my daily driver, so can't test it now. I try to flash and capture the logcat later.

---------- Post added at 11:22 AM ---------- Previous post was at 11:21 AM ----------

Yup... That was exactly happened to me also. The phone just show Oppo logo. CM logo not appear at all.

Nightly 20161031 works on me though. I didn't do full wipe.
[Oppo R7 Plus] maniac103:
Are you guys using Xposed by any chance?

Gesendet von meinem R7plusf mit Tapatalk
[Oppo R7 Plus] Texan1:
No, I'm not. Managed to load back 31/Oct version but very wary now as to what caused the issue and if it will happen again with the next update.
[Oppo R7 Plus] maniac103:
I'd recommend to stay off the current nightlies for the next days. I'm on vacation at the moment, but I'll look into the issue once I'm back.

Gesendet von meinem R7plusf mit Tapatalk
[Oppo R7 Plus] teemo:
2016.11.13 flashed over 2016.10.31

BOOTLOG
[Oppo R7 Plus] teemo:
Reverting the mdss changes fixes the kernel. I reset to 23b8945 and built the kernel. Replaced the kernel in 20161113 build and flashed over 20161031. Looks good. However, I don't get the way github, gerrit and the buildserver are linked. The mdss changes are not driven from gerrit ( at least I cannot see it ;) ).

Building cm13:

Starting the cm13 project from scratch does not fetch the correct vendor files. I had to bring in the files from TheMuppets, adding it to roomservice.

Rolling back the kernel as above leaves errors building Android, but that was somewhat expected. No errors compiling kernel alone though.

If someone absolutely need the November security updates, you can PM me for an update. Just be aware that it is not supported and something may break :P

[MENTION=765758]maniac103[/MENTION], enjoy your holiday, its fully deserved. CM runs perfect as is from 20161031.

EDIT: Reset to "Fix potential NULL pointer" is enough to fix it, reverting only the two latest commits.
[Oppo R7 Plus] maniac103:
Thanks for that analysis, that'll help in fixing the problem. You don't see those changes in Gerrit because I pushed them directly.

That's to be expected. You can fetch blobs from TheMuppets (as you did) or via extract-files.sh from a running CM device. The former is the only tested method though ;)

That was the reason for pulling in those commits. The display HAL was updated to a newer CAF base, which expects the MDSS bandwidth stuff in the kernel. I guess I missed a follow-up pick.

I wonder whether it's just those commits that are missing:

https://github.com/CyanogenMod/andr...mmit/d902a23f5ec34ae44bbbcf0940ebb2fdccf1629e

https://github.com/CyanogenMod/andr...mmit/de705be0738e073eacd94d76b575cedea6967b0b

Especially the former will be needed for the DT changes commit that I added.

Gesendet von meinem R7plusf mit Tapatalk
[Oppo R7 Plus] celoxocis:
Ah and i was wondering why i did not see them in gerrit.

Just to clarify were both kernel branches rebased?

What i thought was:

that the CM14.1 kernel had an complete rebase (including PS/ColorOS code)

and the CM13 was sticking to the "good old" with an fast forwarded kernel including those Display Hal updates?
[Oppo R7 Plus] maniac103:
That's entirely correct, except the cm-13.0 branch didn't have the display HAL updates yet and I failed at applying them :( But once that is fixed, well have the state you described.

Gesendet von meinem R7plusf mit Tapatalk
[Oppo R7 Plus] lenrek:
Just notice a new nightly. Is it good to use?
[Oppo R7 Plus] kishd:
No does not boot.

Edit: Display does not initialize.
[Oppo R7 Plus] maniac103:
The next one should be fine again. I've added the missing kernel commits that broke the last few nightlies today.

And BTW, the builds _do_ boot, you just don't see anything of that boot process ;)

Gesendet von meinem R7plusf mit Tapatalk
[Oppo R7 Plus] PassiTheApe:
Hi,

I haven´t had this issue in ColorOS, but I can´t use Whatsapps voice messages anymore. My recordings in the builds I used so far (31/10 and 20/10) sounded metally, dull and low quality although voice recordings with any other app work just fine.

Does anyone else have this issue as well?

Btw, after not having updated my 20/10 build for a while my battery life decreased drastically. 4 days ago, before I went to 31/10 I had 2-3 hours screen-on-time and had to charge almost daily. I hope this has been straightened out now or will soon be?
[Oppo R7 Plus] Texan1:
Thanks maniac, appreciate the updates :good:

Any word on when the next nightly might drop?

Also couple quick questions re. CM14.1 for R7Plus…

Is it currently being worked on?

If and when it is ready, will we be able to flash straight over CM13 without a full wipe or would it be better to factory reset?

Cheers, Tex.
[Oppo R7 Plus] rch.aj34:
I Second Texan1's post , CM14.1 can't come soon enough !
[Oppo R7 Plus] maniac103:
Yes, yes, no. :)

I'll probably enable CM14.1 nightlies next week or something. I was tracking down an annoying display flicker bug, but it seems I got it smashed. I'll test for a few days, and if nothing new pops up, nightlies are good to go.

Gesendet von meinem R7plusf mit Tapatalk
[Oppo R7 Plus] Texan1:
Brilliant, thanks maniac, look forward to it :victory:

Just wondering if there is a possibility to include a feature that is incorporated into ColorOS. There is a menu option that allows you to show your mobile carrier's name in the top notification bar, hide it entirely or show the carrier's logo. Possible to get this option back in the CM version please?

Cheers, Tex.
[Oppo R7 Plus] lenrek:
Just saw a new nightly: 20161122.

Anyone flashed it yet? I tried to download, but always failed to download.
[Oppo R7 Plus] Texan1:
I see a new 1122 build has dropped but looks like it needs to be uploaded again, only a 25mb file.
[Oppo R7 Plus] Jacob_DK:
That's awesome. I'll be happy to test it. :)
[Oppo R7 Plus] PassiTheApe:
I think I have no luck using the OTA updates for the nigthlies using the respective cm recoveries :-/ the updates fail to install with an error as soon as they start. Does anyone have the same issue and might there be a way to fix it?
[Oppo R7 Plus] kishd:
The last nightly 22/11 nightly is not a complete file. Better to wait a little.
[Oppo R7 Plus] lenrek:
Ya... Better wait a bit more.

I am more anxious for CM14.1 !!! :fingers-crossed: :victory: :D
[Oppo R7 Plus] Texan1:
Any news on a new CM13 update that works?
[Oppo R7 Plus] rch.aj34:
About your carrier name option , you can use xposed and flat style status bar to accomplish it !;)

---------- Post added at 11:05 PM ---------- Previous post was at 10:51 PM ----------

Bravo! can't wait.:good:
[Oppo R7 Plus] kishd:
It's on the weekends that you miss having something new to flash. Now I know that I am a flashaholic.
[Oppo R7 Plus] EximusCode:
Cannot wait for CM14.1. I just want to have a taste of that sweet, sweet Nougat :)
[Oppo R7 Plus] PassiTheApe:
Yeah but that happened to me with the other nightlies too...
[Oppo R7 Plus] kishd:
The last working nightly is 31/10/16

This one

https://download.cyanogenmod.org/get/jenkins/185326/cm-13.0-20161031-NIGHTLY-r7plus.zip
[Oppo R7 Plus] maniac103:
The nightly brokenness is the reason why I haven't switched to 14.1 nightlies yet. I want to wait for the next round of weekly 13.0 builds before switching over.

Gesendet von meinem R7plusf mit Tapatalk
[Oppo R7 Plus] EximusCode:
When do the new Weekly 13.0 builds come through?
[Oppo R7 Plus] kishd:
In anticipation of CM 14 I removed xposed and installed suhide. Does systemless superuser and suhide work on CM 14.1 for the r7plusf?
[Oppo R7 Plus] maniac103:
Normally they're supposed to fire Sunday night, I think. Currently the build server looks stalled though, so not sure when it will happen.

I have no idea; never used SuperSU on CM.

Gesendet von meinem R7plusf mit Tapatalk
[Oppo R7 Plus] kishd:
I had to remove cm root and install supersu with suhide to get my banking app working with CM 13
[Oppo R7 Plus] EximusCode:
When you say "nightly brokenness", what appears to be broken?
[Oppo R7 Plus] Texan1:
Both the 161113 and 161122 builds had a display driver bug where you could only see the Oppo boot logo on the screen after flashing them, even though the rom had loaded underneath. Both unusable so the last working version is 161031.

Eagerly awaiting a new, working version!! :confused:
[Oppo R7 Plus] EximusCode:
So the display driver bug accompanied by the servers halting is making the job tedious.

With the display driver bug, did you use a different boot.img? Or maybe the boot.img needs to be updated. Besides that the only thing I can think of is a bug in the themes. Or the bootanimation.zip not being properly installed.

With the servers, would it be difficult to stop and restart it or just delete the current one and make a new one?
[Oppo R7 Plus] maniac103:
The bug was in the kernel, which is part of the boot image.

It's probably not difficult, just need to find somebody with the required permissions who has time to look into it. I'm lacking the former.

Gesendet von meinem R7plusf mit Tapatalk
[Oppo R7 Plus] EximusCode:
Deleted
[Oppo R7 Plus] teemo:
Or ask someone else that has the setup to build ;)

I compiled the CM13 kernel a few days ago and it is currently running fine in another cm13-based ROM (as 14.1 also does) :D
[Oppo R7 Plus] Texan1:
This lack of a new CM13 rom is eating away at me... it's ticked over a month now without a new, working rom! :crying:

Anyone with the skills/authority/know-how able to kick this back into gear?!? :highfive:
[Oppo R7 Plus] EximusCode:
How about we just wait a little but longer, we might eventually have a CM14.1 ROM soon.

But it isnt a horrible idea.
[Oppo R7 Plus] kishd:
From earlier posts it looks like if the build server for r7plus could be restarted by someone with the right permissions CM 14.1 nightlies can be enabled. Hope the right people see this. Unfortunately it looks quite difficult to find the right people in charge of the automatic build server.
[Oppo R7 Plus] shadow25:
Seems like the CM14.1 nightly for the R7 Plus is released but I don't see it in the CM site :confused:

P.S. The Nightly is online for the download :)
[Oppo R7 Plus] kishd:
Its here

https://download.cyanogenmod.org/get/jenkins/187851/cm-14.1-20161201-NIGHTLY-r7plus.zip

Downloading now. Thank you for the heads up.
[Oppo R7 Plus] shadow25:
Nothing bro ;)

P.S. It's boot and it is fantastic. There are some force closes and lack many of the classic customizations of CM but all in all it is a very promising work, good job guys! Finally the double tap/long press home button to sleep :cyclops:
[Oppo R7 Plus] f22217:
Just a little question before installing it.

Do I have to reset my phone or can I just flash it like an update?

Thank you by advance for your response
[Oppo R7 Plus] shadow25:
Backup your data and do a clean flash (all wipe)
[Oppo R7 Plus] rch.aj34:
Glorious ! R7 Plus looks slick and classy with CM14.1.
[Oppo R7 Plus] Texan1:
And there I was wishing CM13 would be updated when BOOM... CM14.1 comes along! :victory:

Did a dirty flash over the top of CM13, noticed Play Store has disappeared for some reason as well as one or two of my other apps. Will try a wipe/clean flash a bit later.

What version of Gapps do we use, assume ARM64, 7.1?

http://opengapps.org/
[Oppo R7 Plus] teemo:
Works for me. Mostly.

Tried a few weeks back on aicp - worked well, but the "update wizard" did not work, so had to do a manual install of everything. No big deal though.
[Oppo R7 Plus] maniac103:
If you see app crashes again, I'd appreciate if you could upload a logcat. I would like to at least check what's off there.

Gesendet von meinem R7plusf mit Tapatalk
[Oppo R7 Plus] kishd:
Did a dirty install, but flashed the ROM and immediately after flashed the 7.1 open Gapps stock package and everything worked fine. "CM bug report" or something similar crashes.
[Oppo R7 Plus] coled3:
I am in DIGITAL BLISS right now!!!!!! :) Thank YOU!!!!!!!!!!!!
[Oppo R7 Plus] manjake:
I'd recommend the micro version of gapps (7.1 ARM64). All the bigger gapps packages will replace the cm clock and cause it to break and all the smaller packages don't contain Google now. Really stable for a first nightly!
[Oppo R7 Plus] manjake:
Just a warning...

When attempting to install an OTA update through cyanogenmod updater it rebooted into recovery and got into a TWRP bootloop. Reflashing twrp and doing a full wipe (all partitions) didn't fix. In the end I had to reflash the stock oppo recovery via fastboot and then flash trwp again. I'd recommend downloading updates and flashing in twrp manually to avoid this
[Oppo R7 Plus] shadow25:
Oh, sure. I notice another strange thing in my R7 Plus. When I turn off the phone and try to turn on, it go into bootloop (don't exceed the oppo logo) but if I boot into TWRP and turn off the phone from here, the phone boot normally. Why? The same thing happened with the latest CM13, I don't understand :confused:
[Oppo R7 Plus] Jacob_DK:
I did the same, and I also see this error. Clearing the cache for the app doesn't help. Everything else seems to work okay, except for missing translations.
[Oppo R7 Plus] shadow25:
Confirm and add that during the flash of the ROM, after "Patching system image unconditionally..." it's show two time this error message "E: unknow command [log]"
[Oppo R7 Plus] EximusCode:
When you say OTA. From what Android version are you coming from? Android 6.0 or Android 7.1?
[Oppo R7 Plus] shadow25:
From Android 7.1, the last day Nightly of CM 14.1
[Oppo R7 Plus] EximusCode:
Okay, as Manjake stated. Download the update via the CMUpdater and then boot into TWRP manually, after locate the latest CM update file at (/sdcard/cmupdater/)

-or-

(/storage/emulated/0/cmupdater)
[Oppo R7 Plus] manjake:
from cm-14.1-20161201-NIGHTLY-r7plus.zip to cm-14.1-20161202-NIGHTLY-r7plus.zip

I dirty flashed the first cm14.1 nightly over cm13 manually in twrp initially - This works fine

The problem occurs when you let the Cyanogenmod updater boot into recovery to install a nightly OTA. This causes a TWRP bootloop. You can get into fastboot but android never boots.