• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

Cyanogen 5.1 ROM confirmed!

Search This thread

lenrek

Senior Member
Jun 29, 2010
394
32
I got another bug, in landscape mode i can't see the navigation keys. They just disappear.

I have the same problem. Refer to the image I uploaded.

Only solution is to reboot the phone, it would be back to normal. But after a period of usage, it would appear like this again. I can't capture any logs, because I am not sure how and when exactly the phone would behave this way.

---------- Post added at 10:11 AM ---------- Previous post was at 10:09 AM ----------

where you download from?somebody can share me a link

I follow the instructions from this link:

[ROM][5.1.1][Official] CyanogenMod 12.1 for OPPO R7 Plus

This link is from Oppo Community Forum.
 

Attachments

  • landscape_buttons.png
    landscape_buttons.png
    68.1 KB · Views: 161
Last edited:

trabando

Senior Member
Oct 29, 2011
305
32
I have the same problem. Refer to the image I uploaded to Google Drive:

https://drive.google.com/open?id=0B90RR6aGxr9DSVRsMTlTWlFmQ2M

Only solution is to reboot the phone, it would be back to normal. But after a period of usage, it would appear like this again. I can't capture any logs, because I am not sure how and when exactly the phone would behave this way.

---------- Post added at 10:11 AM ---------- Previous post was at 10:09 AM ----------



I follow the instructions from this link:

[ROM][5.1.1][Official] CyanogenMod 12.1 for OPPO R7 Plus

This link is from Oppo Community Forum.
Yeah I'm experiencing this still on latest rom.
 

Nexus5-32GB

Senior Member
Nov 2, 2013
440
137
Has anyone tried to encrypt the phone yet? I am on 12/04 build and it doesnt work. After pressing ENCRYPT button, phone reboots and I can see "green android" logo for only a second and phone reboots back then. Would that be because TWRP installed maybe?
 

lenrek

Senior Member
Jun 29, 2010
394
32
Yeah I'm experiencing this still on latest rom.

I just received a latest update to my Cynogen theme. After the theme update, I no longer encounter this issue. Now I believe this issue is likely due to theme and not the ROM itself.

Are you using theme in your phone? Do try another theme. If you unsure which one to try, this is the one I am using:

https://play.google.com/store/apps/details?id=com.chummy.jezebel.material.dark

I have no more issue after its latest update.

** Update:
The problem suddenly appear after a full day of usage. Now I am not sure what was wrong. The last thing I remember was toying the phone "Expanded desktop" setting. But I have disabled it after a few minutes of usage.
 
Last edited:

thepinkowl84

Senior Member
Apr 24, 2010
117
3
i was trying to go back to stock recovery from cm12..i downloaded stock rom , stock recovery..installed stock recovery using android sdk lite and windows cmd using this command.. fastboot flash recovery recovery.img..phone returned to stock recovery and i selected wipe data and cache..but when wiping starts screen goes black and phone switches off..when i restart recovery it dirctly shows the wipe screen and again screen goes black and its off..please help me..
 

Top Liked Posts

  • There are no posts matching your filters.
  • 8
    It is great to hear that CM is coming to OPPO R7 Plus!

    Current state is:
    - RIL (telephony, SMS, mobile data) is working
    - BT, GPS is working - camera is working
    - sensors are working
    - Wifi is semi-working
    - audio is broken (no speaker, no headphones)
    4
    As a quick update:

    - Audio is working now, there's only minor crackling noise when playing notification sounds in deep sleep
    - Wifi is working, it's a bit unstable though (sporadically loses connection)
    - fingerprint sensor is working

    Only blocker for official nightlies that I can see is that we need to fix the SELinux policies.
    4
    As I can see, you committed fully working fingerprint sensor HAL into cm.
    Correct.

    I am not a dev, but just curios that how you managed this ?
    AFAIK, fingerprint and Laser autofocus things are closed source by OEMs., thats why lots of devices lacking this in CM like OnePlus 2.
    So, how ?

    The fortunate thing is that the code actually talking to the fingerprint sensor runs in the trust zone, thus I 'only' needed to trace and analyze the communication between the stock ROM and the fingerprint trustzone app. This turned out to be manageable, and after understanding that protocol, implementing the HAL was pretty straightforward. Doing something similar should entirely be possible for most devices that do fingerprint management in the trustzone; unfortunately there are a number of devices with fingerprint sensor (especially the early ones) which don't do it in the trustzone, thus are mostly out of luck. I had an Oppo N3 before the R7 Plus and decided not even to start working on a fingerprint HAL for it due to the sheer complexity of the task.
    3
    CM for MTK version? I dont think it will ever happen...

    I don't think any of us actually has MTK hardware, so that sounds about right.

    In other news: I just turned on r7plus nightlies, they should start with the next round of builds (tomorrow).
    3
    At least on my unit the bootloader came unlocked. If it doesn't, it should work like on a Nexus by running 'fastboot oem unlock'.

    BTW, we fixed SELinux today; I expect nightlies to start in the next few days.

    Gesendet von meinem R7plusf mit Tapatalk