ColorOS 2.0 (International) Beta - Oppo Find 7 and 7a

ColorOS 2.0 International Beta for OPPO Find 7/7a was released Monday (21 April 2014; link from post on OPPO Forums).
I installed the Beta Monday night on my Find7a. Overall I find it better than the stock ColorOS 1.0.x: smoother performance, lot fewer "glitches", more polished.
The International edition includes full Google App Services (which makes lot of Apps on the Play Store able to be installed; installing the prior Google App Services Packages on stock version was missing some base services which wouldn't allow some APKs to be installed, whether via Play Store or manually via SD card or ADB).
Some currently outstanding shortcomings:
Security is still lacking
"Password" is limited to four numeric digits
There is no passphrase option
Voice print did not work for me at all (could not set up)
There is no ability to encrypt entire device (only per app basis, which wouldn't encrypt SD card(s); encrypting all apps is cumbersome)
WiFi HotSpot SSID is still limited to ten characters
Partioning is still not optimal (would really prefer unified partitioning)
I have ~100 apps installed; had to remove quite a few after receiving space errors
I did not move any apps to the SD card - I may at some point (although before that I'll most likely work on re-partitioning)
3GB for /data, of which (removing the minimally used subdirs):
[email protected]:/data # df /data
Filesystem Size Used Free Blksize
/data 2.9G 2.6G 326.3M 4096
[email protected]:/data # du -ms /data/*
129 /data/data
243 /data/app-private
343 /data/app-asec
353 /data/app-lib
612 /data/dalvik-cache
959 /data/app​
rooted by default
I would prefer an easily rootable phone versus one that is rooted by default
Many corporate mobile management SW, BYOD or otherwise, often check for rooted / jailbroken phones, which, coupled with limited security mentioned above, limits the appeal of this device in its current state for any work purpose
Minor setup-time issue:
WiFi configuration at initial setup time is still set to 2.4GHz only, so does not see any 5GHz AP / SSID - this should be changed to "Auto" as the phone is capable of 5GHz (802.11n + 802.11ac) access
Unfortunately, for my personal use, the limited security prevents this phone from being my primary device (until CM / PA / Omni release their ROMs, hopefully at some point in the next few months).
[Otherwise so far the phone is still performing quite well.]
[EDIT]
Better link (thanks to AfterDeath from OPPO Forums for pointing out to me)

Regarding the password issue, I see this in the OPPO Forums ColorOS Discussions / Suggestions area; I've added a comment there as well.

Regarding device encryption, I see this in the OPPO Forums ColorOS Discussions / Suggestions area; I've added a comment there as well.

Thank you for your impressions! Is the new 2.0 ColorOS beta really rooted by default O__o ???

TheShortOfIt said:
Thank you for your impressions! Is the new 2.0 ColorOS beta really rooted by default O__o ???
Click to expand...
Click to collapse
The Beta has root enabled by default (although the su binary is not installed, so no way for apps installed via Google Play Store to, as such, get privilege escalation).
From a post I made on the OPPO Forums:
Code:
$ adb shell
[email protected]:/ # id
uid=0(root) gid=0(root) context=u:r:shell:s0
As compared to, for example:
Google (ASUS) Nexus 7 (2012 / grouper): Stock Android (KitKat 4.4.2 / KOT49H), not rooted:
Code:
$ adb -s <sernum> shell
[email protected]:/ $ id
uid=2000(shell) gid=2000(shell) groups=1003(graphics),1004(input),1007(log),1009(mount),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats) context=u:r:shell:s0
Google (Samsung) Nexus 10 (2012 / manta): Stock Android (KitKat 4.4.2 / KOT49H), rooted:
Code:
$ adb -s <sernum> shell
[email protected]:/ $ id
uid=2000(shell) gid=2000(shell) groups=1003(graphics),1004(input),1007(log),1009(mount),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats) context=u:r:shell:s0
[email protected]:/ $ su -
[email protected]:/ # id
uid=0(root) gid=0(root) context=u:r:init:s0
Another member on that same forum is fairly sure this is simply because of the Beta status and should not be the case for GA.
[EDIT] Added link to post

Works great here! I really like the blur effect, especially on folders.

Is this version matching KitKat? Could you run something like isGenuine and tell how it is reported? Unfortunately I need a real testing device for KitKat, so OPPO 7 looks very tempting, but if no KitKat then I have to buy some crap as SGS5.

It's reported as Android 4.3
Sent from my X9006 using XDA Premium 4 mobile app

Definitely 4.3 still. I gotta say though that I like it much better than the latest stable software. All the transitions through the UI and the blur effect, especially in folders, do it for me.

Just installed the beta and first impressions are much better than what the phone shipped with. I can take pictures and listen to music at the same time w/o the SD card disappearing/unmounting on me. Before if I did any 2 tasks at the same time that required the SD card it would be a no go and I'd have to restart the phone. Granted it's been less than an hour so we'll see how it goes.
Default auto brightness is still too bright but so is CM, or was on my old phone. I always edited the brightness levels and miss this option immensely.
Some spelling/grammar issues but not a huge deal probably were in the 1.2.x version as well
If this update does nothing except fix the SD card issues I'll be happy with it.
So just a fyi for those of you who like to trim things down as much as possible by uinstalling/freezing things don't do that with Files or Files v2.10._SVN10964 as it shows up in TB (unless it changed once I reinstalled the apk from the beta os zip). It'll mess up the process of selecting ringtones, notification sounds, and will end up FC alarm when you go to choose the alarm noise. Or at least for me it did. Things worked once I reinstalled it.

question, will this beta version of color os 2.0 get updated when we install it on find 7? will it get to final version or somehow we will have to re flash the phone?

Once you go beta you stay in the beta update server.
That means when a new beta is out you will get it via ota.
Sent from my X9006 using Tapatalk

smart cover + Color OS 2.0
Today i had my first day with the smart cover (Color OS 2.0)
The lid tends to lift while in the bag causing the screen to power up. Coupled with the quick discharge of the battery, this is anither issue that they must attend.
We need an option to not awake the screen when the lid opens. The double tap works much better.

MrColdbird said:
Once you go beta you stay in the beta update server.
That means when a new beta is out you will get it via ota.
Sent from my X9006 using Tapatalk
Click to expand...
Click to collapse
and if it goes to final version (no longer beta)?

Quote from Oppoforum:
From User Addel, Product Manager of Oppo
OTA
This is the first Beta version for Find 7 so OTA is not available for this version.
http://www.oppoforums.com/threads/find-7-coloros-2-0-0i-beta.11926/

clarckent said:
Today i had my first day with the smart cover (Color OS 2.0)
The lid tends to lift while in the bag causing the screen to power up. Coupled with the quick discharge of the battery, this is anither issue that they must attend.
We need an option to not awake the screen when the lid opens. The double tap works much better.
Click to expand...
Click to collapse
+1, or adjust the sensivity of that option.

Morak75 said:
+1, or adjust the sensivity of that option.
Click to expand...
Click to collapse
Where please? Haven't found that option yet. Thank you. :good:

clarckent said:
Where please? Haven't found that option yet. Thank you. :good:
Click to expand...
Click to collapse
I meant, it'll be nice that in future updates they put that kind of option

Ahhhh, ok, ok.

Xposed Framework has a module for that
Check the magnet off module in the xposed framework. it fixed my issue with the screen turning on when the cover opens up by mistake.
Morak75 said:
+1, or adjust the sensivity of that option.
Click to expand...
Click to collapse

Related

[APP] Multi-User App Share

I have created an app that will help share apps across users on google's new 4.2 multi user feature.
Thanks to mentose457 and unwired for giving me the idea.
see this thread (http://forum.xda-developers.com/showthread.php?t=1994169)
It works by removing package elements from user's package-restriction.xml file to add the app and adding the package element back to remove the app. (located at \data\system\users\10\package-restrictions.xml where 10 is the user's id)
This is quickly thrown together and will likely have a ton of bugs, but I wanted to go ahead and get it out there for testing.
- This is BETA
-You must have ROOT
- This changes system data on non documented files it could screw something up.
- I'm not responsible for any problems this causes or lost data or bricked or broken devices
- please use cation
- it is currently built to run on main user to enable or disable apps on secondary users (once root is fully working on secondary users I will see about making it run correctly on secondary user's account)
- not tested thoroughly with paid apps*
- does not currently support system apps**
- due to the way I pull the app list from the package manager some installed apps may not show as available to add/remove
- apps installed first on a secondary user's profile will probably not show in the list to add/remove
*paid apps seemed to work but I did not have internet access during testing. My theory is that any paid apps that use Google's license verification will not work or not work for long. So adding your Google Account to the secondary user's play store is probably still the best way to share paid apps.
**The entries in the xml for system apps is different. Therefore I will have to research them more before getting it to work or deciding not to mess with those apps. Currently some will show not installed on other users even though they are and removing/adding them will not work correctly.
------> DOWNLOAD HERE https://play.google.com/store/apps/...tm_medium=forum&utm_campaign=app_announcement
I'd love to get feedback to what is working and what is not. Also if anybody figures out anything more about the package-restriction.xml file I'd love to hear it. Especially when it comes to system apps.
Thanks mate added my sons Google account and it is all running perfectly. Seperate saves and account details for apps and allowing me to share my paid ones with him
First review on play store is up.
Will have a mess around with apps and report back but it appears to be running sweet at the moment
Cheers danny...
Sent from my Nexus 7 using Tapatalk 2
I wanted to chime in as well. It is working on AOKP. Thanks again jeepguy04.
Looks like it's working for me too :thumbup:
Strange, I'm rooted. Using root apps such as cache mate, titanium & sixaxis.
Multi user app enabler says not rooted.
So does root checker??
DeadlyDazza said:
Strange, I'm rooted. Using root apps such as cache mate, titanium & sixaxis.
Multi user app enabler says not rooted.
So does root checker??
Click to expand...
Click to collapse
On the first 'owner' account I'm rooted, but the second user account doesn't recognize root in apps shared through multi user app.
rkuijpers said:
On the first 'owner' account I'm rooted, but the second user account doesn't recognize root in apps shared through multi user app.
Click to expand...
Click to collapse
That is a known issue (if you want to call it that). For me it's not a problem as my second user is a guest just like on my computer.
Sent from my Galaxy Nexus using Tapatalk 2
mentose457 said:
That is a known issue (if you want to call it that). For me it's not a problem as my second user is a guest just like on my computer.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I know, that's why I quoted the user I meant to answer
It wasn't meant as a negative comment, as I think this app is very useful.
I tried this with ten games and all worked fine (free and paid) except Retro Racing. It works with primary user but crashes with secondary user.
https://play.google.com/store/apps/details?id=com.mrqwak.retroracing
Do you think it is possible to have a shared folder for fotos and musik for multiple users?
some one post the apk my devices are not compatible lol
Great idea! My solution involves just buying everyone their own tablets.
Sent from my Galaxy Nexus using XDA Premium HD app
player911 said:
My solution involves just buying everyone their own tablets.
Click to expand...
Click to collapse
... Fail
Does it works on nexus10 ?
agabe said:
Does it works on nexus10 ?
Click to expand...
Click to collapse
Should work on any tablet running 4.2 (or phone if your custom rom enables the multiple user profiles)
joeyman08 said:
some one post the apk my devices are not compatible lol
Click to expand...
Click to collapse
Currently I only have it available in the market to tablets to avoid confusion for people wondering why it doesn't work with their phone. Maybe I will change that since only nexus devices or phones with custom roms are running 4.2. Those users tend to be a little smarter and know if their phone has multiple user profiles or not.
Here is a link to the apk for anybody that can't see it in the market.
bergfex said:
Do you think it is possible to have a shared folder for fotos and musik for multiple users?
Click to expand...
Click to collapse
The shared folder idea is interesting but beyond the scope of this app. Probably could do it with symlinks or something (not very knowledgeable in linux). Maybe I will look into it and either make another app or find a way to make it fit in with this app.
Yes. Symlinking the photos/music folders outside /data/ should work. But I don't have a 4.2 device(nor willing to set up an emulator) so I'm unsure.
Looking forward to trying on my p5113 CM 10.1
jeepguy04 said:
I have created an app that will help share apps across users on google's new 4.2 multi user feature.
Thanks to mentose457 and unwired for giving me the idea.
see this thread (http://forum.xda-developers.com/showthread.php?t=1994169)
It works by removing package elements from user's package-restriction.xml file to add the app and adding the package element back to remove the app. (located at \data\system\users\10\package-restrictions.xml where 10 is the user's id)
This is quickly thrown together and will likely have a ton of bugs, but I wanted to go ahead and get it out there for testing.
- This is BETA
-You must have ROOT
- This changes system data on non documented files it could screw something up.
- I'm not responsible for any problems this causes or lost data or bricked or broken devices
- please use cation
- it is currently built to run on main user to enable or disable apps on secondary users (once root is fully working on secondary users I will see about making it run correctly on secondary user's account)
- not tested thoroughly with paid apps*
- does not currently support system apps**
- due to the way I pull the app list from the package manager some installed apps may not show as available to add/remove
- apps installed first on a secondary user's profile will probably not show in the list to add/remove
*paid apps seemed to work but I did not have internet access during testing. My theory is that any paid apps that use Google's license verification will not work or not work for long. So adding your Google Account to the secondary user's play store is probably still the best way to share paid apps.
**The entries in the xml for system apps is different. Therefore I will have to research them more before getting it to work or deciding not to mess with those apps. Currently some will show not installed on other users even though they are and removing/adding them will not work correctly.
------> DOWNLOAD HERE https://play.google.com/store/apps/...tm_medium=forum&utm_campaign=app_announcement
I'd love to get feedback to what is working and what is not. Also if anybody figures out anything more about the package-restriction.xml file I'd love to hear it. Especially when it comes to system apps.
Click to expand...
Click to collapse
Great to see this is available
Thanks:good:
Why the full network access and google play billing service permissions?
excarnate said:
Why the full network access and google play billing service permissions?
Click to expand...
Click to collapse
Google Play billing service is for accepting donations via in app purchase. Under settings anybody can donate if they feel the app has value to them... so far I've gotten two $1 donations...lol
network access is for connecting to internet for ads and also for ACRA (Application Crash Report for Android) it basically sends error reports to me to help fix errors. It can be disabled under settings if you do not want it reporting errors.
Does not populate menu on my Nexus 7.

Debloating Script for Lollipop N900TUVUFOB6

** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **​
Background
This script is written for the sole purpose of reducing the power consumption of Android 5.0 update for T-Mobile Note 3. A lot more can be removed from the system but that will not make a significant contribution to power.
The debloat script does not really remove anything; it only disables the apps. You can always run the enbloat script to revert it.
THIS SCRIPT IS FOR LOLLIPOP ONLY. WILL NOT WORK ON OTHER ANDROID FLAVORS.
What this script does
Please read below and understand what this script does before you use it. There may be an app on the list that you may actually want to keep.
Removes: FOTA, update, and security vehicles.
Because: these vehicles push "Security Updates" onto the device. If you make the mistake of accepting this security update, even after you root your tablet, it can patch the hole and you will never be able to use the same exploit to root again.
Removes: Google apps including Gmail and Google sync apps except for Maps, Youtube, Chrome, and Voice Search.
Because: Google apps do a lot of bookkeeping, locationing, and internet access in the background with very little benefit to the user, while consuming a lot of power. If you use Gmail my suggestion is to use the default Email program since it allows a better management of the sync schedule and consumes less battery (and a few other good things). Note that this can severely limit your access to Play Store so either install all store apps you need before debloating or use sideloading to install them after
Removes: Knox
Because: I am yet to meet a single person who likes this nightmare of an app.
Removes: Tmobile stuff except for Voice mail and hotspot
Because: Tmobile bloat does too much activity in the background. In particular, Lookout scans your device constantly to no obvious advantage.
Removes: Backup/cloud agents
Because: Most advanced users backup their data through other means
Removes: Remote control and tracking mechanisms
Because: If you are reading this you most likely don't want your device to be remotely tracked or controlled by Samsung
Removes: ANT services, health, INDI (v2), secgba (v2), Peel (v2)
Because: They run in the background and use the radio.
Removes: Weather (unified) daemon
Because: Major battery hog
Removes: Chat ON, Gear Manager Stub, Bloomberg
Because: Not particularly useful and can be installed from the market if needed
Removes: Enterprise and VPN tools
Because: Most users don't use them
And since someone will ask at some point, no, this script won't trip your Knox!
Requirements:
Rooted Samsung Note 3 SM-N900T (T-mobile model) on Lollipop N900TUVUFOB6. See this thread.
Android Terminal Emulator: https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
Download link:
Attached below
Instructions:
Make a backup of your files/system. Also have a flashable Odin ROM handy to recover from possible disasters. I am not responsible if you brick your device while using these scripts.
To debloat:
1- Unzip the attachment and copy debloat.sh to your phone at /sdcard
2- Run the terminal emulator and type the following:
su
cd /sdcard
sh debloat.sh​3- It will do its thing and reboot your phone in about 5 seconds.
To restore the bloatware:
1- Unzip the attachment and copy enbloat.sh to your phone at /sdcard
2- Run the terminal emulator and type the following:
su
cd /sdcard
sh enbloat.sh​3- It will do its thing and reboot your phone in about 5 seconds. You have all your bloat back now.
Note that while running the debloat script you may get force-closing popups. This is normal; after all you are disabling these applications.
Limitations:
If you have previously removed bloat using other means this script CANNOT recover it for you. enbloat.sh can only restore what debloat.sh has disabled.
Final Notes
With this script you should be able to get anywhere between 0.25 to 1 percent discharge per hour in standby mode. Your awake time should also be around 1-3%. You will still find that Google Services will wake up and use GPS every time you unlock your phone. To get even better battery performance turn your GPS off when you are not using it
This should be sufficient for 99% of people. After you apply this script, if you still want more try this: Disable Phonesky, google play services, Google framework, and stock YouTube by renaming their apks (not the directory they are in but the apks themselves) to .apk.bac, reboot, and install an older version of youtube that does not need Google Services, such as 5.1.10. Note that this drastic removal of Google services will make assisted GPS very slow in Google Maps. If you don't understand what that means it is best to stick with the debloat script and not mess with your system.
Regardless of whether you end up using this code or not, my suggestion to you is to go to Settings -> General -> Security -> Security Policy Updates -> untick Automatic Updates.
Update
Version 2 removes more background processes. If you have already used version 1 to debloat, I recommend that you use version 1 to restore the bloat and then use version 2 to debloat again.
Thanks for contributing your work!
Frank
411y0ur8453 said:
See above/
---------- Post added at 09:15 PM ---------- Previous post was at 09:05 PM ----------
Anyways, we don't need a big long debate about it. I am just saying there needs to be a little more objective evidence for this, especially when the logic and reason at the beginning of the OP doesn't match the logic and reasoning in the list of applications being removed.
And the knox app is embedded deep into the device's core framework, simply removing the app is doing very little to remove it in it's entirety.
Click to expand...
Click to collapse
This is true. Knox is embedded deep into the system even bootloader removing the app will do close to nothing. Not putting down the work put into the script as it is indeed a time saver if you have spend a little time with Android. If not they can be turned off manually. As for the security holes. There will always be a way to root and mod. Oems have that to themselves. Take a look at our brethren over with verizon and att. Their devices are locked down tight and came like that out of the manufacturer. Our devices are unlocked boot loader wise. If they wanted to they would have locked our models too.
From the Moderator
Please avoid wandering into the philosophical world ........
Remember this ••• If you root the phone or customize it ••• then forget about security or other updates that come from the carrier or the manufacturer ......... by default you have agreed to abandon those updates ...... if they are important to you then, do not root and stay stock....... EASY
Post on topic, be kind , be respectful ........ thanks ~~~ oka1
oka1 said:
Please avoid wandering into the philosophical world ........
Remember this ••• If you root the phone or customize it ••• then forget about security or other updates that come from the carrier or the manufacturer ......... by default you have agreed to abandon those updates ...... if they are important to you then, do not root and stay stock....... EASY
Post on topic, be kind , be respectful ........ thanks ~~~ oka1
Click to expand...
Click to collapse
Also a very good point...:good:
Meh... A lot of the time, removing and freezing apps can be counter productive.
For example,mpdecision, which controls when cores come online, has calls to it embedded into Samsung's camera apk, and removing or renaming this file can negatively impact battery life when using the camera application because a lot of the time, oems don't build checks into their software. They simply expect the file to be present, and when it's not, it can create a loop and drain battery.
Unless you've gone through the entire system to look for references to the apps you're removing, it's best to simply freeze or leave them alone.
freeza said:
Meh... A lot of the time, removing and freezing apps can be counter productive.
For example,mpdecision, which controls when cores come online, has calls to it embedded into Samsung's camera apk, and removing or renaming this file can negatively impact battery life when using the camera application because a lot of the time, oems don't build checks into their software. They simply expect the file to be present, and when it's not, it can create a loop and drain battery.
Unless you've gone through the entire system to look for references to the apps you're removing, it's best to simply freeze or leave them alone.
Click to expand...
Click to collapse
You are right about the mpdecision process and it makes common sense to not remove a process like that. The same can be said about different timers and alarm processes in the system and the list goes on.
Having said that, I would be more than happy to explain how each item on this list contributes to saving power or protects the system from being subjected to unwanted patches without compromising the integrity of it.
And finally, I have been already using this setup (even a more aggressive version of it) for a few days on my phone with excellent power results and not a single hiccup or force closed app. I have also constantly monitored the wake locks and background processes to make sure the situation you referred to does not occur. I would be glad to hear your feedback if you use it and find a different outcome.
Op, can you share me one with Gapps and debloating all stuffs which are not necessary (TMO Services),if you live away from US of A? It would be much helpful for people like me.
jhbalaji said:
Op, can you share me one with Gapps and debloating all stuffs which are not necessary (TMO Services),if you live away from US of A? It would be much helpful for people like me.
Click to expand...
Click to collapse
There is a lot that can be taken out but every piece removes a bit of functionality with it. If you live abroad it is understandable to remove all TMO stuff but, for example, if you remove more Google stuff than this script does YouTube will stop working and maps becomes slower. Also, there are services like printers or widgets like flipboard etc that you may still want to keep. So to what extent do you want to debloat your system?
I had already debloated several apps but thought this could help a bit more with the battery. So far I haven't had any issues, crashes, etc.
Thanks for sharing.
Update: It causes Milk Music to not work.
dirtybudha said:
I had already debloated several apps but thought this could help a bit more with the battery. So far I haven't had any issues, crashes, etc.
Thanks for sharing.
Update: It causes Milk Music to not work.
Click to expand...
Click to collapse
What is milk music? I don't have that app. Do you mean google music? Oh, you mean the one from the play store?
OK, Milk music is a samsung app. It needs the samsung account apps that are some of the things that this script disables. If you need your milk music back, run the enbloat script and you will have it back.
Yeah, I followed the instructions which were UBER easy. Thanks for that.
I figured it was related to that.
najoor said:
What is milk music? I don't have that app. Do you mean google music? Oh, you mean the one from the play store?
OK, Milk music is a samsung app. It needs the samsung account apps that are some of the things that this script disables. If you need your milk music back, run the enbloat script and you will have it back.
Click to expand...
Click to collapse
Here is an example of how debloating can be beneficial. On an unmodified phone I set the brightness to about 50 percent and let the phone play a 720p video in a loop. I could get 10 hours of screen time. However if you look closely, Lookout has been busy in the background burning 13% of the battery. So if I had disabled it I would have arguably got another hour of screen time.
I love this scipt! As a laymen, all I have to do is import it via Rom Toolbox (Pro) to the sciprter--then execute. My device runs at least twice as well as before.
Thanks, OP!
cant wait to try this out
deleted

Magisk or SuperSU for HTC ONE M9 7.0 NOUGAT? (VODAP100)

Hi,
I'm wondering what your experiences are with
Magisk or SuperSU for HTC ONE M9 7.0 NOUGAT?
(I'm on CID: VODAP100) :silly:
Which was better for you personally, and have you experienced any any issues with updates to their binaries or problems during installation, or perhaps problems with Google Pay and NFC beam for example?
Thanks for your input. :highfive:
I'm using Magisk 14.0 and NFC is working fine. I stopped using SuperSU when ViperOne M9 6.0 got released (1st February 2017).
I can't say anything about android pay since it's not supported in my country. Pokémon Go (which is relying on safety-net, too) is working fine, though.
Flippy498 said:
I'm using Magisk 14.0 and NFC is working fine. I stopped using SuperSU when ViperOne M9 6.0 got released (1st February 2017).
I can't say anything about android pay since it's not supported in my country. Pokémon Go (which is relying on safety-net, too) is working fine, though.
Click to expand...
Click to collapse
I see, so Magisk is pre-installed with ViperOne M9 6.0.
I've read that Google Pay won't work with Custom ROMs, which is a shame because it sounds like a good ROM from what I have heard.
Perhaps Google allows rooting in Germany as Germany doesn't use Google Pay. In the UK Google Pay is very popular, and so is using NFC on the transport system. Hmmm, so it could be country specific as to whether NFC gets turned off after rooting. Maybe there is a workaround. :good:
Having said that, I've read that Google Play lists devices with unlocked bootloaders as "Uncertified", yet, I have an unlocked bootloader (via HTCdev/not sure if that makes a difference) and Google Play says "Certified", and as you say, Pokémon is working for you (which uses SafetyNet) so perhaps there won't be an issue but it's rather hit and miss as to what will happen it seems.
Maybe it will say "Not Certified" after Google Pay is opened and granted permission to scan device though, who can say for sure, I don't know. One thing I do know is that my software version has been reported by many to have encryption problems pertaining to the reading of the IMEI after rooting. I've read that in a few places on the internet, that's why I'm trying to get as much info as possible beforehand.
Do you think Magisk 14 is okay for me to flash via TWRP with my current Android version?
I'd really like to get rid of the Vodafone bloatware on my HTC, and more importantly try some battery tweaks but I'd really like to use all phone feature if possible after rooting. (Such as NFC and Google Pay. I'm surprised Google hasn't made a public list of what will work and what will not). Google!
It's actually the first time that I ever hear of NFC not working on a rooted M9 and I highly doubt that that's true.
There are no country-specific differences in regard to root and the hardware of your phone. It might be that the app doesn't allow you to activate NFC (that's an assumption I don't know that for sure since I've never used the app) but the NFC chip itself doesn't get affected by rooting this phone.
Edit: And I haven't heard of phones that lose their IMEI due to root, either. You can create problems by flashing incompatible roms but not by rooting the device.
Edit2: You need to be aware that not all SuperSU versions are compatible with this phone, though. However, the incompatible ones only create a bootloop.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
It's actually the first time that I ever hear of NFC not working on a rooted M9 and I highly doubt that that's true
There are no country-specific differences in regard to root and the hardware of your phone. It might be that the app doesn't allow you to activate NFC (that's an assumption I don't know that for sure since I've never used the app) but the NFC chip itself doesn't get affected by rooting this phone..
Click to expand...
Click to collapse
Yes I agree, I don't think the NFC chip itself is affected either.
From what I've read, the NFC option ends up "Greyed Out" in some cases. What I meant when I said "Country Specific" was, that perhaps in cases where it does get "Greyed Out", that maybe it happens if a user roots their phone in a country where Google Pay is available to use. (Just a hypothesis).
Flippy498 said:
Edit: And I haven't heard of phones that lose their IMEI due to root, either. You can create problems by flashing incompatible roms but not by rooting the device.
Click to expand...
Click to collapse
I trust your knowledge. In my case though, it happened to me and I had not introduced any new ROM ever. I simply unlocked the bootloader on HTCdev. The phone reset to its own recovery factory image after bootloader unlock, but with missing radio and IMEI. It had never been unlocked before, no new image. Others on the internet said it's something to do with the capabilities encryption reading of some versions of SuperSU on this exact phone Software – Nougat 7.0 CID: VODAP100. A bit of a mystery. I'm not an expert but I know I didn't download or backup any image or ROM of any kind. It was already on it, I just unlocked it. Fixed now though thanks to the info here. Great forum. :good:
Flippy498 said:
Edit2: You need to be aware that not all SuperSU versions are compatible with this phone, though. However, the incompatible ones only create a bootloop.
Click to expand...
Click to collapse
Yes I've heard that too. I think this one in the screenshot is OK for my version, would you ever use Kingroot yourself? I'm having a slight issue with SuperSU though as you can see. :silly: LOL :laugh: hmmm I'm really tempted to use Magisk 14 now.
↓
I think it should be 5.67 MB, not "KB" and because of that it's saying 16000+ % downloaded and it wouldn't stop downloading. (screenshot).
Only use Kingroot or any other one-click-root method if you need some nasty malware on your PC and/or smartphone (depending on the version you use).
The latest SuperSU version I've flashed myself was 2.79 SR3.
Flippy498 said:
Only use Kingroot or any other one-click-root method if you need some nasty malware on your PC and/or smartphone (depending on the version you use).
The latest SuperSU version I've flashed myself was 2.79 SR3.
Click to expand...
Click to collapse
I've heard that too. Thanks for confirming.
May I ask, what in your experience is the best app to use to extend battery life on the HTC One M9?
I'm torn between not rooting and trying Naptime via "Dump" or trying Magisk 14 with a Magisk Module but then the other side of me says, ah to hell with it just root and Greenify then you can install Adaway too. :silly:
These are the Devs instructions to use DUMP in case anyone is wondering:
"To use Naptime's features without Root you need to grant it DUMP permission via ADB on your computer by executing this command:
adb -d shell pm grant com.franco.doze android.permission.DUMP
You also need to grant WRITE_SECURE_SETTINGS permission:
adb -d shell pm grant com.franco.doze android.permission.WRITE_SECURE_SETTINGS".
(Edit: The app should be force closed either manually or by running this command from adb after the others commands mentioned above. Originally just the two commands above were at the Google Play description, but the app notified (on opening it) that it needs the force close command :
adb -d shell am force-stop com.franco.doze )
What do you think? I'd also be interested to know what your favourite apps are in general. You seem like you probably know some great ones.
Titanium Backup.
I actually don't think that battery saver apps are worth installing. When an app gets started the battery usage is higher than during the normal usage of the app. Therefore, keeping an app active and re-opening it needs less battery capacity than always killing the app (e.g. with greenify) and restarting it at a later point. In general android is capable enough to handle its ram and the battery on its own.
The best advice I can give you is uninstalling all apps that you don't need and stay away from YouTube, Facebook and all those other bad developed social media apps that drain your battery. That's why I mentioned TiBa at the beginning of the post.
On the other hand this device's release date lies more than 2 years in the past. You mustn't expect any great usage times per battery cycle, anymore, due to the age of the hardware. Batteries don't last forever.
I don't use any fancy apps. Only adaway, TiBa, solid explorer and the venom tweaks of ViperOne M9 require root.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
Only use Kingroot or any other one-click-root method if you need some nasty malware on your PC and/or smartphone (depending on the version you use).
The latest SuperSU version I've flashed myself was 2.79 SR3.
Click to expand...
Click to collapse
Flippy498 said:
Titanium Backup.
I actually don't think that battery saver apps are worth installing. When an app gets started the battery usage is higher than during the normal usage of the app. Therefore, keeping an app active and re-opening it needs less battery capacity than always killing the app (e.g. with greenify) and restarting it at a later point. In general android is capable enough to handle its ram and the battery on its own.
The best advice I can give you is uninstalling all apps that you don't need and stay away from YouTube, Facebook and all those other bad developed social media apps that drain your battery. That's why I mentioned TiBa at the beginning of the post.
On the other hand this device's release date lies more than 2 years in the past. You mustn't expect any great usage times per battery cycle, anymore, due to the age of the hardware. Batteries don't last forever.
I don't use any fancy apps. Only adaway, TiBa, solid explorer and the venom tweaks of ViperOne M9 require root.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Those are excellent apps.
I wish I could install hosts via adb or Adaway itself via that command on NOUGAT but I can't I don't think.
I use Adaway on my Moto G and it is brilliant.
I prefer an old version of ES File explorer as I'm just familiar with it, but that one you have is great too. Titanium Backup I've always found a little complex.
I'm going to give Naptime a go, I agree force closing apps that are restarted often uses a lot of resources but I'd like an option to turn the phone to a high sleep mode, but still recieve some push notifications I've installed Naptime (before I seen your response) and I gave it permissions with adb.
I'll see how it goes and perhaps report back here if anyone is interested. Also, there's quite a nice article about uninstalling bloat via adb without root that I'm reading here on XDA at the moment. I've already manually force closed apps like ZOE, perhaps I can squeeze a bit more out of the system here and there with that.
Google Services is really killing it, and I don't even have an option for uninstalling Chrome. lol Hello Google!!

Instant messaging apps do not work on the 5.1

Hi everyone, the issue I am facing is that instant messaging apps (Viber, Facebook messenger, etc) do not work on my 5.1. Notifications settings are OK, unrestricted data access is allowed for these apps, so this is not a notification issue. The apps do not receive messages unless I launch them (when I launch the apps, there are no new messages, they start arriving a couple of seconds after launching). I contacted Nokia, but they did not have a clue... I did everything they asked for (factory reset, etc.), nothing helped.
Does anyone else have similar issues? Does anyone have any idea what the solution might be?
So it's been reported before that Nokia/HMD is the worst for how aggressively they limit background app usage. This can't be fixed in the current stock ROM but Nokia might help us out with Pie (if it ever materialises).
zondajag said:
So it's been reported before that Nokia/HMD is the worst for how aggressively they limit background app usage. This can't be fixed in the current stock ROM but Nokia might help us out with Pie (if it ever materialises).
Click to expand...
Click to collapse
Thanks. It seems that the 5.1 was my last Nokia.
The Android One project is a bit of a farce given the update cycle is so delayed. It's good to have the security of assured updates, but only providing them when the hardware is no longer relevant seems a waste. Also it's possibly the Mediatek chipset to blame, but this phone has not had a great deal of interest on XDA, which could also be in part due to the Android One project making custom ROMs a little less relevent.
You can fix it yourself by uninstalling com.evenwell.emm app from user space. That crappy service which HMD bundles into firmware "improves" battery life by killing all non-system background apps.
qwertysmerty said:
You can fix it yourself by uninstalling com.evenwell.emm app from user space. That crappy service which HMD bundles into firmware "improves" battery life by killing all non-system background apps.
Click to expand...
Click to collapse
how to unistall? with adb?
noki2 said:
how to unistall? with adb?
Click to expand...
Click to collapse
yes via adb:
adb shell
pm uninstall --user 0 com.evenwell.emm
qwertysmerty said:
yes via adb:
adb shell
pm uninstall --user 0 com.evenwell.emm
Click to expand...
Click to collapse
Not working. They are no apps like this..
Adb shell says, [not install for 0]
TANVIR TUSAR said:
Not working. They are no apps like this..
Adb shell says, [not install for 0]
Click to expand...
Click to collapse
Have you upgraded to Pie? In Pie it's named com.evenwell.powersaving.g3
qwertysmerty said:
Have you upgraded to Pie? In Pie it's named com.evenwell.powersaving.g3
Click to expand...
Click to collapse
Yes... I found it. I thing about this name but then i thought it might be important app. Thanx
qwertysmerty said:
Have you upgraded to Pie? In Pie it's named com.evenwell.powersaving.g3
Click to expand...
Click to collapse
Should i delete com.evenwell.powersaving.g3.overly.base
??
Yes, you can delete overlay as well.
Yuo may need to uninstall these packages as well
com.evenwell.PowerMonitor
com.evenwell.PowerMonitor.overlay.base
I noticed that my 1Password service was still being killed after uninstalling com.evenwell.powersaving.g3.* packages. After removing PowerMonitor stuff everything back to normal and Nokia 5.1 Pie became usable again
I have the 2gb variant and its no use. Its a crappy phone... No notification what so ever even after disable/uninstall the evenwell apps and battery saver etc apps. Its no use as doon you start browsing only Google apps remains active. All other are killed. Not a android one phone. Its a stupid phone!!!
I believe I have found the definitive answer for this, after much googling around.
I have a 5.1 Plus (TA-1108) and tried the ADB disabling of evenwell apps and others but it still would stop services after restarts. I eventually found a post on the "Don't kill my phone" Github which alluded to the hidden setting of the "Duraspeed" task killer that is bundled.
The dontkillmyphone website says you can ADB in and change this hidden setting to 0, but this doesn't persist after a restart. The value will still be a 0, but it seems this task killer only reads the value after it detects a change in the value (bizarre, I know). So to disable this Duraspeed thing, you need to change the hidden setting value from something else to a 0 on each boot.
Luckliy, this is very easily done by Tasker/Macrodroid/etc. Use this post:
https://github.com/urbandroid-team/dont-kill-my-app/issues/57#issuecomment-484000884
but the short of it is to enable WRITE_SECURE_SETTINGS to tasker (by running this:
adb shell pm grant net.dinglisch.android.taskerm android.permission.WRITE_SECURE_SETTINGS
for tasker, google for your app of choice)
and then set a task that runs on boot to change a "Custom Setting", Global type, setting name setting.duraspeed.enabled to a value (doesn't matter, I use 2) and then immediately after change the same setting to 0.
I have this set up on my phone and my wifes phone and ever since they have been perfect with background services (my Garmin watch, lastpass, etc) as well as any email/notification apps.
TANVIR TUSAR said:
Should i delete com.evenwell.powersaving.g3.overly.base
??
Click to expand...
Click to collapse
Lol, I uninstalled all evenwell apps, it didn't make any difference
qwertysmerty said:
Yuo may need to uninstall these packages as well
com.evenwell.PowerMonitor
com.evenwell.PowerMonitor.overlay.base
I noticed that my 1Password service was still being killed after uninstalling com.evenwell.powersaving.g3.* packages. After removing PowerMonitor stuff everything back to normal and Nokia 5.1 Pie became usable again
Click to expand...
Click to collapse
How to start adb usb debugging on this phone?
I have adb sdk installed, every other phone but Nokia 5.1 is visible when I type adb devices.
Should I use adb on Linux or Windows, install any special drivers from Nokia?

Themes / Apps / Mods [Anxious] OOS v502, Companion v346, True Silent v2, Verizon PU v16

These modules are made for personal use. If you have an issue it is likely on your end. It's like running OOS 10.5ish w/ OOS 11/Pixel 4 Pixel 5/9 Pro/server side features via a whole lot of sed. The "thoroughness" of this OP is to minimize the need for back and forth between us. All OOS 11-11.2.* should be supported. Remains to be seen what changes with Color OS based OOS.
Anxious OOS v502 features:
(Template - Magisk module installer)
Android 12.1 Emojis, Blurs, Immersive Navbar, Nova Launcher w/ Google Feed, Pixel 5 features (device personalization services, flags, google phone framework, overlays), Premier Tier, 9 Pro Camera
Anxious OOS Companion v346 features:
(Template - MMT-Ex 1.6)
Anxious Kernel Script - Infinite Pills, Infinite Alcohol | Gboard - Faster Voice Typing, Google Lens, M2 (telescoping gif, tenor autocomplete, trending search), No Spacebar Branding, Ogg Opus Encoder, Pill Shape, Pixel Props, SODA, Tenor V2 * Languages (autocomplete, trending term, suggested search term), Tflite (emoji predicition, main word predicition, triggering model), Translate Dictation | Google Duo - In Call Effects w/o FPS Cap, Message Captions, Opus FEC, Outgoing Call Camera Switch, Restrict Low Bandwidth Logging, Video Processing-Sink, VP9 Hardware, 720p (for most things) | Google Phone - Duo Handover, STIR/SHAKEN (carrier/os support required), VVM (all carriers) | Google Photos - Cache Aware Video, Jpeg Backup Quality 100%, New Video Editor Backend/Frontend w/ Export Frame
True Silent v2 features:
(Template - MMT-Ex 1.6)
Silent .ogg file for notifications. Useful for apps like Facebook Messenger that don't respect notification channels properly. Seperate module so less reselecting when debugging anxious module. Also doesn't need to be uninstalled with OTAs.
Verizon Plus Ultra v16 features:
(Template - MMT-Ex 1.6)
Fixes for using Verizon on the 7 Pro.​
All feature lists are constantly changing. Not everything is listed. Because sometimes the modules put you front in line for a/b server testing of literally anything Google.
The embedded links for some features are just links to what I consider to be a good enough explainaiton of the feature.
Google is your friend, I am not.​
Support:
Basically none. This is made for my personal use. If you don't follow the instructions, you'll probably end up in a non-boot/bootloop.
What I'm Using:
Kernel - Kirisakura 1.3.9 R
Magisk - Stable
Rom - 11.0.4.1.GM21AA (7 Pro)
Do not use Open Beta/AOSP/LOS/etc... with my modules.
There are no special instructions for updating, unless stated otherwise in a release post. The below install instructions are not meant to be followed for updating.
Prerequisites:
You need "Busybox for Android NDK" and I strongly recommend "Cross Compiled Binaries" with sed installed to /system/bin. They are on the magisk module repo.
How to install:
1. Read entire OP. Reread entire OP. Do it again.
2. Install "Overlay Mount Fix". Skip to next step, if it fails to install.
3. Uninstall Google Framework/Phone, and/or Nova Companion apk, if any/all are installed. Go to the Play Store listing for Device Personalization Services and click uninstall, if it's available. Reboot, if you uninstalled any modules. There are probably other modules you should uninstall. But that's your problem, not mine.
4. Install "AnxiousOOS_v*.zip". (Magisk Manager only)
5. Reboot.
6. Install Google Phone as user app, you can use apk from companion module, from apkmirror, or clear Play Store data and then it should be offered by the play store.
7. Clear Play Store data if you didn't in step 6. Then update apps that now have an update in the Play Store.
8. Set up Device Personalization Services, Google Phone, i.e. grant all permissions (including "Draw over other apps" and "Modify system settings"), set as default phone app, spam app (search "spam" in settings), open app and set up available features. Don't forget to check all Settings>Apps and notifications>Special app access and check all of them for the aforementioned apps + Google apps (hit overflow menu and show system).
9. Install "AnxiousOOSCompanion_v*.zip". (Magisk Manager only)
10. Reboot.
11. Clear Play Store data
12. You profit.
13. Donate.
14. I profit.
15. Install Verizon specific module. Reboot. Reset APN defaults (search "sim" in settings, 1st suggestion>sim 1>access point names>overflow menu), if using Verizon module.
16. Call Screen/Hold For Me.
17. 100% jpeg quality.
Download(s) faq:
Q: Can you provide a mirror?
A: No.
Q: Why?
A: Mega is very mobile friendly and collects no metrics, I can't even track the number of downloads!
Changelog:
Will be available on each release post. I will not compile a changelog in one post.
Magisk:
Don't use anything older than the latest stable magisk.
Tips/Troubleshooting:
You should check "Settings>
Security & lock screen>Google Play system update" for an update. My modules might enable being on the latest. Might not.
If any app is reported as unsupported in the Play Store then clear the Play Store's data. It should work after that but a reboot might be needed sometimes.
Google has the ability to break pretty much anything with server side updates.
Clean installs of roms will probably have better outcomes, if it didn't work.
The app that live caption exists in, is called "Device Personalization Services". If it's not available you need to manually enable the service. I recommend this app manager. While you're at it you should enable all activities, providers, receivers, services. I also suggest using App Ops and Shizuku (required for App Ops functionality). All the linked apps also make debugging/troubleshooting easier.
Random:
You should read the Magisk documentation and MMT-Ex wiki.
Thank you
A lot has changed compared to the old instructions, so I'll gradually update the OP to reflect helpful FAQ, improved instructions, etc...
I also may have figured out how to get the latest Google Play system update. But that's unconfirmed. Since I don't have (or want) testers.
Welcome back! I'm glad to see you back on here hope that whatever you had going on in your life was resolved.
ImjustSaiyan92 said:
Welcome back! I'm glad to see you back on here hope that whatever you had going on in your life was resolved.
Click to expand...
Click to collapse
At least 10 years off till a refutable research facility would even consider injecting my retina with stem cells. And I won't have a diagnosis on my lung nodules for months or longer. But it would be the slowest growing metastatic colon to lung cancer my oncologist has ever seen but I currently have my bets on a benign inflammatory condition or pulmonary fibrosis as a result of chemotherapy. Haven't found a bookie to take my bets, yet...
But now I can be hella rude to people who don't read with the two eyes they have because I essentially have one eye lol.
Thanks for this, finally.
What is soda, pills and alcohol about?
twoxa said:
Thanks for this, finally.
What is soda, pills and alcohol about?
Click to expand...
Click to collapse
Speech on device API and utter nonsense (it's also a song, that is absolutely appropriate to post on the family friendly environment of XDA)
I installed it the way it was explained .. but what was to change .. did not see change ..
douglasmietto said:
I installed it the way it was explained .. but what was to change .. did not see change ..
Click to expand...
Click to collapse
Then you did it wrong.
TotallyAnxious said:
Then you did it wrong.
Click to expand...
Click to collapse
I'm just not using the Kirisakura kernel ..
douglasmietto said:
I'm just not using the Kirisakura kernel ..
Click to expand...
Click to collapse
Or following the instructions.
You're not going to get any helpful support from me with one sentence posts that demonstrate you didn't follow instructions lol.
There are many "it"s you must install. And not everything is in the OP because I shouldn't have to tell users on a developer forum that something like a Terminal app is required when I say modules are needed as prerequisites that require a Terminal app for set up of those prerequisites.
The kernel has absolutely no effect on making this work or not. And you thinking so demonstrates the "learning curve" for my instructions are to difficult for you.
You're going to waste your time if you're gonna spend time trying to get the right kernel for something that doesn't need a right kernel.
yes it was installed .. what changed the alarm clock .. changed the calculator and install the google phone from the play store ... so you mean it is not a simple magisk module? have other necessary settings through a terminal to work correctly?
douglasmietto said:
yes it was installed .. what changed the alarm clock .. changed the calculator and install the google phone from the play store ... so you mean it is not a simple magisk module? have other necessary settings through a terminal to work correctly?
Click to expand...
Click to collapse
I'm saying you can't even read my OP with two eyes, and I have one eye...
I will not be responding to you anymore.
TotallyAnxious said:
I'm saying you can't even read my OP with two eyes, and I have one eye...
I will not be responding to you anymore.
Click to expand...
Click to collapse
I followed exactly all the steps of the op .. and I noticed that the rom got a little faster .. I'm sorry if I asked any stupid questions .. I didn't want to cause you any trouble
douglasmietto said:
I followed exactly all the steps of the op .. and I noticed that the rom got a little faster .. I'm sorry if I asked any stupid questions .. I didn't want to cause you any trouble
Click to expand...
Click to collapse
If you expected some drastic visual changes this isn't it haha
So far so good here, nice having working voicemail in Google phone app.
"& "Cross Compiled Binaries" with the bare minimum of sed installed to /system/bin. They are on the magisk module repo."
Can you elaborate here? What's sed? And why they should be installed?
Installed it, everything was working except one snag, my settings was FCing everytime I tried to go to the app section.
It's something on my end most likely as I am using Bliss (which is different than your rom,) and it probably isn't compatible.
Love the work regardless and again I'm glad to see you back!
ImjustSaiyan92 said:
Installed it, everything was working except one snag, my settings was FCing everytime I tried to go to the app section.
It's something on my end most likely as I am using Bliss (which is different than your rom,) and it probably isn't compatible.
Love the work regardless and again I'm glad to see you back!
Click to expand...
Click to collapse
This is the kind of user I like.
douglasmietto said:
calm friend .. i don't know why so much stress if you're nervous go fishing to relax .. if you don't want to answer questions about your work, just don't post to the XDA group.
Click to expand...
Click to collapse
Why are you on a developer forum asking to be spoon fed information?

Categories

Resources