yashsingh1/xdaforums huggingface dataset:
[Oppo R7 Plus] celoxocis:
This is interesting. I the R7SM a 15022 too?

I always thought the R7M is project code 15023.

Do you have an R7SM at hand?
[Oppo R7 Plus] t-mobile_mda:
yes i have..
[Oppo R7 Plus] celoxocis:
I will need some information output of:

ls -l /dev/block/bootdevice/by-name/

and

cat /proc/partitions

and

cat /sys/devices/soc0/revision

please post output using pastebin.com.

Maybe this ROM will work on the R7SM too.

Only difference could end up being the trust zone.

You will need minimal adb & fastboot and USB debugging enabled. If you need an how to. Let me know.
[Oppo R7 Plus] celoxocis:
Please post output of "adb shell dumpsys sensorservice".

I think the SoC revision hardware and sensors are the same.

Some relevant partitions differ in size (most important system and userdata)

the rom will not work "out of the box" nor will my TWRP recovery.

However i can build an TWRP for the R7SM. Unless you already have a working TWRP for the R7SM?

And i can build an CM Rom for the R7SM. Do you know if Bootloader is unlockable for the R7SM?

If not the Bootloader should be unlockable using the same method i used for the R7S.

What ROM version are you running of ColorOS?
[Oppo R7 Plus] celoxocis:
The sensors are exactly the same.

Whats the last available properly working ColorOS version for the R7sm?

If you have a download link please link here.

I will need to extract additional information from the stock ROM such as OTA assert.

Kernel boot cmd's and Ramdisk offset information.

The version trustzone usually can't be found in the stock rom but you can dump it using:

adb shell [Hit Enter]
su [Hit Enter]
dd if=/dev/block/bootdevice/by-name/tz of=/storage/emulated/0/tz.bin [Enter]

Then look into your internal SDCard for the "tz.bin".

Please attach that binary file to your reply or upload it somewhere. Should be only like 1MB zipped (or even less).

The binary file is generic and the same on all R7SM it does not contain any unique sensitive information. It is safe to share.

Also, i know there are like two "Full Netcom" Versions. One has 3GB and one 4GB. Which version is yours?
[Oppo R7 Plus] t-mobile_mda:
as far as i know color os 3.0 is the latest softeare.. let me check link for u..

tz file,

color os 3.0,

http://xdaforums.com/r7-plus/general/rom-r7plus-coloros-3-0-beta-t3304799

direct link,

https://mega.nz/#!tUEVhJAY!e9HX0Krpe6OdBS2fNDjZDhCsnrmCcn3u21fHCiFY88I
[Oppo R7 Plus] LordAlberto:
What's the best method to update CM? When installing your latest, I lost all settings, most apps etc. But I noticed on Oppo forum you said it can be done without losing anything.

Thanks mate.
[Oppo R7 Plus] celoxocis:
Just download the latest ROM. Boot into TWRP and install latest ROM + latest Gapps. You won't lose any settings and apps. Only if you factory reset. Which you only should do when coming from ColorOS.
[Oppo R7 Plus] LordAlberto:
Lol, wasn't sure so I followed install guide from page one. Doh!! :silly:

Will remember that in future...:D

:good:
[Oppo R7 Plus] celoxocis:
Thanks. Even the trust zone is the same. I think it will work flawless once i modify what's required and build the ROM.

But you will have to Unlock the Bootloader to boot the CM rom.

If the R7SM does not have proper fastboot binarys to unlock the bootloader you can follow my Unlock pdf guide in the R7S TWRP Recovery thread to use the Project Spectrum bootloader to unlock the device.

Just skip the part for rooting the ROM. As you obviously have a rooted device with a working TWRP.

And replace step 31 & 32 with a previously backup of your aboot.

Backup your original aboot like this:

dd if=/dev/block/bootdevice/by-name/aboot of=/storage/emulated/0/aboot_r7sm_backup.mbn [Enter]

Copy the file into the minimal adb & fastboot installation folder to revert after unlocking the bootloader.

to revert simply do:

fastboot flash aboot aboot_r7sm_backup.mbn

Like said. Only required if the R7SM has no fastboot binarys to unlock the bootloader.
[Oppo R7 Plus] t-mobile_mda:
hey again..

i will chcek ur pdf now..
[Oppo R7 Plus] sirizak:
Wierd volume behaviour

G'day Celoxocis I've got a wierd issue with my volume. I put my phone in to Do no disturb mode and now I can't disable it again. Also during a phone call I have no control of the call volume. Not sure if the two are related.

Any ideas?
[Oppo R7 Plus] t-mobile_mda:
just wanna ask that,

if i installed the TWRP this mean bootloader is unlocked..?
[Oppo R7 Plus] stupidfellow1997:
not sure but did you use the soundmod? it may affect.

if not u can disable it via quick settings. Just add it from the system tiles.

or u can just click several times on your volume key.
[Oppo R7 Plus] sirizak:
yeah tried that also. Might be time for a factory reset.

Update: It just magically came good. Moving on.
[Oppo R7 Plus] celoxocis:
It depends. I don't know your TWRP source. If the TWRP is somehow signed then you won't need an unlocked bootloader as long as you run Official Oppo roms.

Best and easiest way would be to boot your phone into fastboot and check your bootloader status.

"adb reboot fastboot" once in fastboot issue "fastboot getvar all".

However all of this will only work if Oppo hasn't removed fastboot binarys from the R7SM.

They removed it on the R7SF. So it's possible they did it on the R7SM too.

You will know when you issue "adb reboot fastboot" and the phone just reboots. It means R7SM has no fastboot binarys.
[Oppo R7 Plus] celoxocis:
I have just tested it and I can use all settings as expected and enable/disable DND mode.

Could be an cache problem?
[Oppo R7 Plus] t-mobile_mda:
i can send the twrp..and device not enter to bootloader mode.. only restarts device when i enter the bootloader command,

adb reboot fastboot or adb reboot bootloader

i think this device has no fastboot binary..this mean will we try ur precedure in the Guide_v3.pdf..?

---------- Post added at 10:40 AM ---------- Previous post was at 10:31 AM ----------

Btw maybe can be usefull,

device has no google apps.. and i am installing over twpr and there is no pb installing succesfully but not exist any google apps..

open_gapps-arm64-5.1-pico-20161111.zip
[Oppo R7 Plus] celoxocis:
Yes you can follow the Guide. Just skip the parts I wrote before and backup and restore your original aboot with the commands I wrote.

Also I recommend to create a full backup using TWRP just select every partition possible but select "system image" instead of "system".

It's better for system restoration should you need to restore. (The other does Unconditional patching)

With such a backup you can simply just restore.

Copy that backup to your PC.

But I don't think anything will happen as I tested the steps in the Guide countless times when porting Cm to the R7Sf. The R7Sm is almost identical.

(Just differs in system and userdata partition size).
[Oppo R7 Plus] celoxocis:
I think they killed Google apps API in Chinese ColorOS. TWRP places all files into the system partition but there is no framework interface (API) to communicate with Google Services.

It will work in CM version for R7Sm.
[Oppo R7 Plus] t-mobile_mda:
oki i will take full backup but i think this procedure is abit risky.? and this aboot is compatible with my dvice..?

21. Then download the latest aboot from project spectrum from my GDrive here:

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

PS; i used this recovery for my device and worked; oppo_r7s_recovery.img

it is stock recovery

dd if=//storage/sdcard1/oppo_r7s_recovery.img of=/dev/block/mmcblk0p23
[Oppo R7 Plus] celoxocis:
I thought you have TWRP recovery for the R7Sm?

If not I can build you one.

Yes just downloaded the PS aboot and follow that part of the Guide.

The Project Spectrum aboot comes official from Oppo and is signed by Oppo. All it does is let's you enter fastboot and use fastboot binarys. Most importantly the bootloader unlock.

Before you start. Make sure you enter developer options and click the checkmark "Allow OEM unlock". It writes a flag for the fastboot unlock to allow unlock.

There is actually no risk if you backup your aboot which is the only part that needs temporal replacement. For the BL unlock. Once done you write back your original aboot and have the exact same device as before just with unlocked bootloader.

The "fastboot OEM unlock" just writes a "flag" for the bootloader in a hidden place (I guess MBR).

To allow for unsigned ROMs to be booted.
[Oppo R7 Plus] t-mobile_mda:
yes yes i have twrp for this device.. i just tried the r7s stock recovery for testing..

and enabled the "enable OEM unlock"

now it is time to test.. ;)
[Oppo R7 Plus] t-mobile_mda:
hey..

i think it is done,

D:\Android\Root\SuperSu>fastboot oem unlock

...

OKAY [ -0.000s]

finished. total time: 0.010s

C:\R7sm_Backup>fastboot flash aboot aboot_r7sm_backup.mbn

target reported max download size of 268435456 bytes

sending 'aboot' (1024 KB)...

OKAY [ 0.040s]

writing 'aboot'...

OKAY [ 0.020s]

finished. total time: 0.060s
[Oppo R7 Plus] celoxocis:
Very good. Just as I thought the same method works for the R7SM. I will build an CM for the R7SM later today. I'm currently not home and have no access to my home-rig. I will message you with a download link when it's done.

Btw how much RAM does your R7SM have?

3GB or 4GB?
[Oppo R7 Plus] t-mobile_mda:
thanx alot for everything.. i will be wait for u..

device has 4gb ram..

Total Ram: 3644MB
[Oppo R7 Plus] acetcb:
hi, i the guide pointed to OPPO R7sf and snapdragon, what about for R7Plusf Qualcomm, which ColorOS need to be installed and the rest follow same procedure.?
[Oppo R7 Plus] celoxocis:
The R7 Plus was released earlier than the R7S and it's shipped with fastboot binarys. No need to follow the guide. Just reboot into fastboot and unlock the bootloader.
[Oppo R7 Plus] acetcb:
thanks for the reply. and after unlock the bootloader, proceed to flash the twrp from your drive?

or take form this guide" http://xdaforums.com/r7-plus/development/guide-root-oppo-r7-r7-plus-one-click-t3212055 ".

another thing, mind if i asked, both your ROM and TWRP are tagged with R7s & R7sf, is it also compatible with R7plusf as this thread posted in R7plus section...i'm confused.
[Oppo R7 Plus] celoxocis:
No you have to flash this one:

https://twrp.me/devices/oppor7plusf.html

No just compatible with R7Sf as the opening post describes.

R7Plus ROM is here:

https://download.cyanogenmod.org/?device=r7plus
[Oppo R7 Plus] acetcb:
noted. thanks for the help.

this are the untouched CM rite? any build from u for R7plusf?
[Oppo R7 Plus] teemo:
[MENTION=4096919]acetcb[/MENTION]

Do not flash 2016.11.13, it will not boot.

Flash 2016.10.31
[Oppo R7 Plus] celoxocis:
What's the commit that causes it to not boot?

I build for R7S on 11.11 it's fine. Don't want to repo sync unless I know what's the cause?
[Oppo R7 Plus] acetcb:
noted. just finished download and in the middle of copying to phone.....and saw your reply....

what about mokee and aicp? it's also based on cm rite?
[Oppo R7 Plus] celoxocis:
Almost all ROMs use CM as the base. They just include more features gimmicks that divert from CM. Which don't get included in CM for different reasons. Doesn't mean they are worse nor better. Some include fixes, some include bugs, some might be less battery efficient others better.

I don't build roms for R7Plus (can't test, don't own the device). Mine are strictly CM based with my custom optimizations from CM as the can't be included in CM builds because of commonization issues.
[Oppo R7 Plus] acetcb:
yes, thanks for the reply... i'll try teemo one first..

aicp_r7plus_mm-11.0-FINAL-20161030.zip
[Oppo R7 Plus] teemo:
Looks like it does boot, but BootAnimation is not running. Display does not seem to be initialized.

There are a few mdss updates to 13 that was abandoned for 14. Lots of warnings in the log. Did not study it closely.

Log here.
[Oppo R7 Plus] celoxocis:
Ah that could explain it. I haven't used the old CM13 kernel for my latest build but the new and rebased CM14.1 kernel.
[Oppo R7 Plus] teemo:
Does it run without device-updates? IE, you just drop in the new 14.1 kernel?
[Oppo R7 Plus] celoxocis:
Yes just drop it in the manifest and sync. No need for device changes.
[Oppo R7 Plus] teemo:
Good to know. I actually did run it with N7.1 on aicp, but want it to be more polished before moving to nougat. Still a few minor things to fix and would like to bring xposed with it as well.

The improved speed of installing and restoring apps is nice though.
[Oppo R7 Plus] celoxocis:
The CM14.1 kernel is as good as it gets.

CM14.1 itself still needs some fixing.

Simple things such as the advanced reboot options are still buggy. That's why I'm sticking with CM13 too. And of course Xposed is a nice feature to have.

The feature to build with Snapdragons Clang for some slight speed-up is really nice too.

But only works starting with CM14.1.
[Oppo R7 Plus] teemo:
CM should be okay. This it's from my r7plus.
[Oppo R7 Plus] 63holdenolden:
These are the missing toggles I mean

View attachment 3767610
[Oppo R7 Plus] celoxocis:
are you sure they are missing?

I'm using the same CM sources as teemo for his AICP the only difference is the device tree which is based on the R7 Plus. I forked the R7Plus=>R7S and integrated the R7S kernel. The RIL is the same.
[Oppo R7 Plus] 63holdenolden:
Hi teemo , so you are able to disable the sims individually?

I cannot see the individual on/off toggles on your screen shots

As I haven't been able to find the setting page to do it

The screenshots are both from my phone , the color os has the on/off toggles but they are not there on the cm 13 one

This is not my first dual sim android phone but I'm feeling a bit silly not being able to find the setting :silly:
[Oppo R7 Plus] teemo:
LOL, I read up on the problem at xda and cm forums. Seem to be a minefield. "Accept or go back to CM12".

Quoting a random dev:

You are right, the toggles are not in settings.

But... why do you want it?
[Oppo R7 Plus] 63holdenolden:
My second sim is for work so I disable it when I am not at work so I don't get work calls or txt's after hours
[Oppo R7 Plus] stupidfellow1997:
used for a day~

realised battery drain faster than stock ROM

any idea? maybe noze is not available in CM?
[Oppo R7 Plus] celoxocis:
There is no Doze for the Oppo device's as it's missing a sensor which is required for Doze to work. Even Projector Spectrum has no working Doze. Doze is more marketing than it actually useful. It starts like twice in 24 hours which is a joke.

The higher battery drain is due to disabled Qualcomm MP decision but I'm working on that. So far my yet unreleased latest version (still testing) has Intelliplug and cluster plug. But my custom Power Hal is not applying the settings I want properly.

In the meantime you can switch both cpu governors using Kernel Adiutor to Lionfish. It will increase the battery time significantly without any noticeable performance degradation.

BTW even on the R7 Plus roms the MP decision is not enabled. The kernel has to be compiled with specific features for it to work properly. R7 Plus however has a bigger battery. That's probably why no one is noticing it there.

Stay tuned for my next release it addresses alot of kernel specific features.
[Oppo R7 Plus] stupidfellow1997:
ok..thx celox for your information ?

i will give a try on kernel auditor...
[Oppo R7 Plus] stupidfellow1997:
after switching the cpu governor to lionfish the battery did not drop too much compared to before..thx celox~
[Oppo R7 Plus] celoxocis:
In my tests it did. Maybe one of your apps is causing wakelocks. Install Wakelock detector and enable advanced options in settings. Leave it running it the background and check whats keeping the cpu up.

I noticed that when using CyanogenMod's weather service app. It would keep the phone awake constantly. So make sure you are not using the weather service. Its pretty new and it will drain your battery.
[Oppo R7 Plus] maniac103:
Settings -> Gestures is not sufficient for you? :p If you don't have it, you'll need to look into your kernel/DTS, specifically whether your TS driver supports them/has the code for them ported (if you don't use the Oppo 3508 driver) and whether your DTS entry for the TS has the synaptics,black-gestures-enabled attribute.

The development setting is totally unrelated to this.

---------- Post added at 01:54 PM ---------- Previous post was at 01:50 PM ----------

??? Please elaborate. No 8939 device has mpdecision, not even on stock. 8939 has perfd.
[Oppo R7 Plus] celoxocis:
i have seen the "synaptics,black-gestures-enabled" in the latest 15011 changes. However i used R7 Plus as a base and i can't remember coming across it.

I will have a look tonight. Currently Im working on cleaning up my workspace for a clean git commit next weekend. To get the R7S official.

I can see that on ColorOS stock the CPU's get hotplugged and and power suspended. Hence the better battery life.

I did extract ikconfig from stock kernel to see which features were used for the hotplug but as MP-decision is userspace and not kernel related.

It shouldn't come up and neither did i find a hotplug feature in the defconfig.

When i look in "init.qcom.post_boot.sh" for 8939 i can see this: http://pastebin.com/RDKcxzfS

especially the part which says:

"# Apply governor settings for 8936
case "$soc_id" in
"233" | "240" | "242")"

233 = R7S SOC_ID (should be the same for R7 Plus)

if its not MP-decision which hotplug feature is used in stock? As i can clearly see the cpu's being plugged on/off? :confused:
[Oppo R7 Plus] maniac103:
I thought it's perfd that brings the CPUs online and offline. I have to admit that I didn't check in detail though, will have to look into it.

BTW, SoC ID for r7plus is 239.

Gesendet von meinem R7plusf mit Tapatalk
[Oppo R7 Plus] lapocompris:
You need to update Project Spectrum to V1.1 Beta, then flash the latest ColorOS and finally flash the rootable ColorOS
[Oppo R7 Plus] maniac103:
Checked it, and it looks like on stock it's a proprietary kernel module that does the onlining/offlining. I'm experimenting with cluster plug now.
[Oppo R7 Plus] celoxocis:
okay that explains alot!

i was testing one build where i used Squid's idea from his Lux kernel to incorporate cluster_plug and the required changes for the R7S kernel.

his changes can be found here: https://github.com/sultanqasim/andr.../commits/squid_marshmallow?author=sultanqasim

it was okay but kinda felt the device getting hot after about half an hour of usage. cluster_plug turns the device into a quad core to save power. preferring the big cluster over the little.

from what i could see the proprietary kernel module acts different in that it prefers the little cluster and hotplug's the big cluster cpu's when needed.

squid uses a custom PowerHal for lux. i did not test it using the custom PowerHal but the common one CM provides. both devices lux/R7S are 8939.

i have not checked CM specific kernel changes for lux. but if it works fine for lux it could be used on 8939 devices for oppo such as R7Plus, R7, R7Plus.
[Oppo R7 Plus] celoxocis:
if you have found faster/easier/other way to switch from Project Spectrum to CM/pre-rooted ColorOS.

please write up a short guide i will post it in the Opening Thread for everyone.

there are other Oppo phones where ColorOS's fastboot was build "defunct" on purpose by Oppo, to prevent the Open community to build custom roms. (they called it "security measurements" which we all know is BS!)

such as the Oppo F1f. so if you coud share your way. maybe it even will work on those phones.
[Oppo R7 Plus] maniac103:
You did notice the Gerrit topic I linked to contains precisely those changes, didn't you? ;)

From my understanding, this commit does precisely that (plug both big and little cores under full load), so no, it's not turning the device into a quad core.

Yes, when added it'll be activated via the msm8939-common repo.

It's not BS per se. Locking the bootloader from fastboot access by default is an important security measure. It's just unneeded to prevent any means of unlocking, but is Oppo actively doing that? They at least sent us an unlockable version of the R5 bootloader.
[Oppo R7 Plus] celoxocis:
Yes i did. I was just wanted to point you to the original author of cluster_plug which might have changes which are not on gerrit :)

The wording "Quad Core" was just used to explain what it does on idle :)

That would be amazing. Alot of effort went into his work. It would be great to have it in other msm8939 devices.

Yes Oppo is (or was) actively disabling the fastboot commands in LK. Their aboot is useless in every ColorOS release, especially for the R7S and F1f.

It could have hit other phones too.

Looks like they were "to lazy" to implement a proper way using hashcode checks. Like all other manufacturers do to unlock the bootloader. So they just made fastboot defunct.

Uberlaggydarwin and me were working on ways to unlock the bootloader in two totally different ways, without knowing of each others work.

In the end his way was the better and less intrusive one. We used his way. This was months before Project Spectrum hit the day of light in closed private betas.

So we were able to start build TWRP and CM for the R7S(me) and the F1f(he).

A lot of pressure was put on by the community via complains in forum/emails.

The last straw that broke the camel's back was Uberlaggydarwin contacting Oppo and putting pressure on them. "in his way" ;)

The first Project Spectrum betas had a defunct a fastboot like ColorOS. The betas after those included working fastboots.

I tested a Project Spectrum aboot while still in closed beta on any ColorOS version and i was able to unlock the bootloader but you couldn't boot using the aboot as the check fails.

Hence the PDF guide I wrote.

If the R5 is unlockable you could try if Project Spectrum R5 aboot can be used to unlock the bootloader.

Oh btw. Did they send you an R7S too?
[Oppo R7 Plus] maniac103:
That's not entirely true. You'll also need https://github.com/CyanogenMod/andr...mmit/f1747bef2e90be1d8d9d0245400c2472d59e0a2d

There is one totally annoying bug in it, which is why I didn't push it to CM13 (which I considered): sometimes on activity changes (be in in an app or switching between apps), there's a short black flash in the lower right corner of the screen. Sometimes (at least on 14.1) there's also glitches on the navigation bar when scrolling the notification shade up and down, which I assume has the same root cause. Not sure where to look for a fix though, as I'm not sure what the actual root cause is :(

Gesendet von meinem R7plusf mit Tapatalk
[Oppo R7 Plus] celoxocis:
Ah yeah I forgot about those common commits. I merged them in my fork of the msm8939-common and kept remote merging it.

I have yet to encounter those short black flashes and the navigation bar one. Could this be related to CM14.1 only? I have not experienced them on CM13. Like the tapping sound issue. It was CM14.1 related.
[Oppo R7 Plus] maniac103:
I haven't seen the nav bar glitch on 13 while I was using the rebased kernel, but I most definitely saw the black rectangle one.

Gesendet von meinem R7plusf mit Tapatalk
[Oppo R7 Plus] celoxocis:
Is there a way to reproduce the black rectangle one? I haven't encountered it and kept close attention to the lower corner and have tried everything last nite but nothing. Even stress tested the phone while switching tasks but nothing.
[Oppo R7 Plus] t-mobile_mda:
hey..

just wanna wonder that r u building it..?
[Oppo R7 Plus] celoxocis:
Read your PM. I sent you a message last nite.

Will send you the download link around noon.

Just make sure to create a backup as before.

Then factory reset in TWRP.

Flash the ROM.

Install Gapps (arm64 6.0.1) I recommend Pico.

Boot the rom and test drive everything.

Like said in PM. I haven't included CDMA system.prop's yet But those are added easy.
[Oppo R7 Plus] t-mobile_mda:
OK i will and i have no CDMA system in my area..so it is not pb..

thanx alot.. i m waiting for ur link...
[Oppo R7 Plus] celoxocis:
Just wondering. What area/country are you in?

I always thought R7SM was for China mainland only. But apparently some were sold in Argentina as well. (Had one request coming from Argentina)