Develop Bugs

[BETA] AGPS fix for HTC One X - Andorid Revolution 18.1 ONLY

BE WARNED​
THIS PATCH WILL ONLY WORK ON​
MIKE'S ROM (Android_Revolution_HD-One_X_18.1)​
This patch will currently only work for the "Android_Revolution_HD-One_X_18.1" ROM because within this patch there is a modified build.prop. When you have done changes or custom settings on this ROM within the build.prop they will be lost and revert back to mike's defaults.
1. What damn changes?
I have add the value
ro.ril.def.agps.mode=2
Click to expand...
Click to collapse
to the build.prop
This should be required for enable AGPS by default. Not sure if this is true but on the one hand it seems to work and on the other hand this is a BETA patch.
2. Show the content of the gps.conf
This is the gps.conf within this patch:
NTP_SERVER=de.pool.ntp.org
AGPS=/data/xtra.bin
AGPS=http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_1=/data/xtra.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin
GPS1_CLEANUP_ENABLED=1
GPS1_SESSION_TIMEOUT=2
GPS1_XTRA_AUTO_DOWNLOAD_ENABLED=1
GPS1_XTRA_DOWNLOAD_INTERVAL=6
INTERMEDIATE_POS=1
ACCURACY_THRES=5000
ACCURACY_THRES=100
ENABLE_WIPER=1
CURRENT_CARRIER=common
PHONE_TYPE=UMTS
DEFAULT_AGPS_ENABLE=TRUE
DEFAULT_SSL_ENABLE=FALSE
DEFAULT_USER_PLANE=TRUE
REPORT_POSITION_USE_SUPL_REFLOC=1
QOS_ACCURACY=50
QOS_TIME_OUT_STANDALONE=60
QOS_TIME_OUT_agps=89
QosHorizontalThreshold=1000
QosVerticalThreshold=500
SUPL_HOST=supl.google.com
SUPL_PORT=7276
SUPL_SECURE_PORT=7275
SUPL_NO_SECURE_PORT=3425
SUPL_TLS_HOST=FQDN
SUPL_TLS_CERT=/etc/SuplRootCert
C2K_HOST=c2k.pde.com
C2K_PORT=7275
#UserParam
AssistMethodType=1
AgpsUse=1
AgpsMtConf=0
AgpsMtResponseType=1
AgpsServerType=1
AgpsServerIp=3232235555
AgpsServerPort=7276
AgpsServerFqdnType=1
AgpsServerFqdnStr=supl.google.com
AgpsSecureSocketOn=1
GpsPlusAutoDownloadOn=1
PdrEnable=1
WpsPdrEnable=1
LocationEnable=1
NetworkLocationEnable=1
use_logcat = 1
event_mask = 65535
nmea_sentence_mask = 31
# 1 = no lock (who the hell has coded this??)
engine_lock = 1
operation_mode = 4
fix_session_type = 0
time_between_fixes = 60
accuracy_threshold = 255
fix_timeout = 60
#XTRA related parameters
enable_auto_download = 1
auto_download_period = 1
#xtra1.gpsonextra.net
xtra_server_addr = 216.187.118.37
data_request_reply = 0
umts_profile_number = 0
apn_name = NULL
GpsMode=2
GpsOption=4
SessonType=2
QosTimeout=255
DataReceiveType=1
DeviceType=3
SensorMagneticOn=0
#TestParam
ULTSOn=0
#NetworkParam
IndexOfApn=3
#GpsPlusInfo
XtraDataSetTime=0
GpsPlusSetTime=-796640328
Click to expand...
Click to collapse
If you have additional parameters or other recommendations, please feel so free and submit this here.
3. How to test?
I have this configuration on my HTC running and it was a need to wait and also to travel arround to get an exact result. I was only Google Maps using and testing. If you have different Navigation Systems installed please also check and test this.
4. How fast?
GPS lock takes 1 to 3 seconds - than it's done. WiFi is also enabled so it doesn't matters if you are using UMTS/GPRS or WiFi.
5. Bugs?
Yes. At the moment it takes some time until you get the first exact result. At the moment it is only between 3 to 10 meteres exactly.
6. Goal?
I want to have a real 99,995% result and want to get a result with a different of max. 1 meter.
For this it would be great if you can give a Feedback please. Thanks!!

Help-me!
MrT69 said:
BE WARNED​
THIS PATCH WILL ONLY WORK ON​
MIKE'S ROM (Android_Revolution_HD-One_X_18.1)​
This patch will currently only work for the "Android_Revolution_HD-One_X_18.1" ROM because within this patch there is a modified build.prop. When you have done changes or custom settings on this ROM within the build.prop they will be lost and revert back to mike's defaults.
1. What damn changes?
I have add the value
to the build.prop
This should be required for enable AGPS by default. Not sure if this is true but on the one hand it seems to work and on the other hand this is a BETA patch.
2. Show the content of the gps.conf
This is the gps.conf within this patch:
If you have additional parameters or other recommendations, please feel so free and submit this here.
3. How to test?
I have this configuration on my HTC running and it was a need to wait and also to travel arround to get an exact result. I was only Google Maps using and testing. If you have different Navigation Systems installed please also check and test this.
4. How fast?
GPS lock takes 1 to 3 seconds - than it's done. WiFi is also enabled so it doesn't matters if you are using UMTS/GPRS or WiFi.
5. Bugs?
Yes. At the moment it takes some time until you get the first exact result. At the moment it is only between 3 to 10 meteres exactly.
6. Goal?
I want to have a real 99,995% result and want to get a result with a different of max. 1 meter.
For this it would be great if you can give a Feedback please. Thanks!!
Click to expand...
Click to collapse
Friend! I'm currently with Android Rom Revolutions 18.1. I did the tests off the wifi and data and then immediately turned the Sygic which took about 4 seconds to find my location. Do you think I should do some correction? : Confuso:

4 seconds to find your location? Is this bad or is this good?

I'm on 4.2 AOKP Rom and changed the files by hand to your Version. My GPS Works much better now.
My Lock Time on AOKP was 4 - 10 Minutes. With your Version i've got 1 - 2 Minutes on first Lock and 2 - 10 seconds on each relock!
:victory:

Great! Glad to read this
Sent from my EndeavorU using xda app-developers app

Just playing with Advanced Info on version 10.0.14291.1001

I was just playing on my 950 XL with advanced info
be sure you use version 10.0.14291.1001 or 10.0.14291.1000
what i did :
- put my phone in mtp mode
- browse on my pc to : this pc -> windows phone -> phone -> dpp -> mmo -> regscreen
--- > there a couple of files you can edit
- i replaced the file : imagelabel_dark.png with my own ( i put : my first test in it )
- and changed the content of the file : coo.txt with the text : test test test
- then HARD reset my phone ( or settings -> about -> reset your phone )
i know its not much but i just want to share this info.
have fun with it ..
Micheal
see here the result :

what it do for you ,advanced info meant for finetune your device ,it makes apps work better with the info on it ,you can change anything in that by just going
HKLM/SOFTWARE/OEM/NOKIA (or any OEM)/variant
all fields are change it make fun
also change Soc 8996(SD 820) below and PhoneManufacturer "HP"see any performance increase with Antutu Benchmark V6 and share your Results
SYSTEM/Platform/DeviceTargetingInfo/PhoneManufacturer == " HP "
SYSTEM/Platform/DeviceTargetingInfo/PhoneSOCVersion == " 8996 "

Coz antutu is fake.

augustinionut said:
Coz antutu is fake.
Click to expand...
Click to collapse
unfortunately that's the only benchmark tool For WM10. other apps need to upgrade WM 10

[DEV][Discontinued] WAS-Lxx [EU] Toolkit [0.0.0.5] All-in-One

INFO
I sold my P10 Lite, based on Huawei's decision to no longer provide bootloader unlock codes.
For a generic version of this project (ADB-Overlay) have a look at this thread.
The latest build of this project is still available.
---
Hello together,
here is a toolkit for the P10 Lite, it's designed to work primary with root (THE MOST TIME) so be careful what u are doing, specially if u are using the "Explorer". (Deleting the wrong file/folder on root lvl, could bring u in bad trouble!)
-
To all who used already my P9 Lite toolkit, there is currently not all available which u know from the old version, but i'll extend this toolkit in the next days. So, no worries about missing functions, they'll appear in some of the next builds.
-
About the usage,
- For a basic UI-Help just press F1
- If ur device is not detected u can switch off the "Device check" on the "Disclaimer" view (If u own a P10 which is not detected pls share a screenshot of the "adb devices -l" (l = lowercase L) command)
- U can also switch the (su -c) usage off (in the explorer view), BUT! after u performed any action which requires root, the trigger will be automatically switched on. (There is no other option, because my dll know only, use root or don't do so... There is no use root part-wise)
But anyways, i'm NOT responsible for any damage to your device!
Little preview of what u get
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tested Devices
Huawei P10 Lite [WAS-LX1A] [SINGLE-SIM]
Requirements
Platform: x86/x64 (Windows)
Frameworks: min. .NET 4
(Installed ADB/Fastboot driver)
Download
Mirror: See attachments
Mirror #1: GoogleDrive
XDA:DevDB Information
WAS-Lxx [EU] Toolkit, Tool/Utility for the Huawei P10 Lite
Contributors
k1ll3r8e
Version Information
Status: Stable
Current Stable Version: 0.0.0.5
Stable Release Date: 2018-08-01
Created 2018-03-30
Last Updated 2018-08-15

How-To
[Q:01] My device is not recognized by the toolkit?
1. Make sure NO adb-server is running!
2. U need to start ur device in android with enabled USB-Debugging (see the screenshot)
(Only in adb mode my toolkit can detect ur device)
3. Make sure that u granted adb access on ur device
(A popup will appear on the device and asks u to grant access.)
Try also to restart the toolkit after u granted access on ur device.
U can also check the device state by opening a cmd/terminal prompt and typing:
Code:
cd path\to\the\toolkit\adb
adb devices -l
check if ur device is listed as follows:
XXXXXXXXXXXXXXX device product:WAS-Lxx model:WAS-Lxx device:XXXXXXX
If ur device can't boot into Android or still didn't get detected, well, just deactivate the "Device Check" on the "Disclaimer" tab. And follow the description.
[Q:02] What does the Lxx Cxxx Bxxx mean?
The Lxx is the device model, the Cxxx is the region/operator identifier and the Bxxx is the build number.
Here is a short list about the regions/operators
ID (Cxxx) = Region/Operator | custom.bin (content)
----------------------------------------------------------------------------------------------------------------------------------------------------
C02 = Vodafone
C10 = Russia
C21 = Telefonica / O2
C40 = Czech Republic Telefonica / O2
C55 = Italia TIM
C66 = VIPmobile | vip/rs
C86 = Spain Yoigo
C109 = Amena/Orange
C112 = Latin America
C113 = Wind/Italy | wind/it
C121 = Türkei
C123 = Switzerland
C150 = T-Com | dt/de
C151 = India
C185 = North-Africa/Middle-East | hw/meafnaf
C209 = Asia (Pacific)
C212 = Iusacell/Nextel
C249 = Serbia Telekom
C432 = Nordic-European | hw/eu
C470 = Asia (Pacific)
C605 = Colombia
C637 = Spain
C636 = Asia-Pacific | hw/spcseas
C675 = India
C706 = New Zealand
C900 = GLOBAL
More comming soon...
Big THX for some of those "identifier" goes to:
@lost3
@baduncle
[Q:03] I want share my custom.bin & oeminfo, what i need to do?
U can get the files via the "Dual-/Single-SIM -> Export" or u can do the following steps (root required).
Open an terminal/cmd prompt and navigate to ur adb installation or the toolkit directory (path/to/the/toolkit/adb) and type the following commands.
Code:
adb shell
su
cat /data/custom.bin > /storage/emulated/0/custom.bin.bak
dd if=/dev/block/platform/hi_mci.0/by-name/oeminfo of=/storage/emulated/0/oeminfo.img.bak
exit
exit
adb pull /storage/emulated/0/custom.bin.bak custom.bin.bak
adb pull /storage/emulated/0/oeminfo.img.bak oeminfo.img.bak
Now u have 2 files, the custom.bin.bak and the oeminfo.img.bak just zip them and upload them to GoogleDrive or DropBox, etc. and share the link in this thread.
[Q:04] How can i manually boot into a specific mode?
Bootloader:
[device] = Turn the device off - Connect it to the PC - Press and hold: [Vol-]
[adb] = adb reboot bootloader
[fastboot] = fastboot reboot bootloader
E-Recovery:
[device] = Turn the device off - Connect it to the PC - Press and hold: [Vol+]
[adb] = N/A
[fastboot] = N/A
Recovery:
[device] = Turn the device off - Disconnect it from the PC - Press and hold: [Vol+ Power]
[adb] = adb reboot recovery
[fastboot] = N/A
Normal Boot:
[device] = Power button / Power button menu
[adb] = adb reboot
[fastboot] = fastboot reboot
Update Mode:
[device] = Turn the device off - Disconnect it from the PC - Press and hold [Vol+ Vol- Power]
[adb] = N/A
[fastboot] = N/A
[Q:05] Does the Dual-Sim upgrade survive an OTA?
Yes, the Dual-Sim modification will stay until u flash another oeminfo.
[Q:06] I upgraded to Dual-SIM and there is only one IMEI shown?
That's absolute normal... Because, u had a single-sim device before, so the device hold only one IMEI and the 2cd sim will use the same IMEI as the 1st sim or as shown the "0000000000000000".

Changelog
2018-08-01 - 0.0.0.5
* Added a Remote-Desktop
* Added a "partition selector" (recovery [Nougat], recovery_ramdisk [Oreo])
* Added a rooting option for Oreo
* Fixed a few bugs
* Realigned a few container
2018-04-21 - 0.0.0.4
* Added on the Device-Info view the BusyBox check
* Added the Phone control
* Added the Root menu (just waiting for permissions to include a zip)
* Added some features to the Explorer "View" menu (e.g. Sync with Treeview, Layout, Sort)
* Added a Display-Trigger to the "Power-Button" menu
2018-04-10 - 0.0.0.3
* Fixed a crash which appeared during device connection on the Explorer view
* Switched the whole window stuff to my new GlassWindow
* Added a AlphaChannelSlider (left beside the [--] button) for those which don't like transparent windows
* Added a Device-Info view
2018-04-01 - 0.0.0.2
* Fixed the icon bug (Big Icons, List)
* Re-positioned the "View" menu and made 2 of them, one for each view
* Refactored the "Button" layout, that they match now with the rest of the dark theme
* Added a fallback color "#2C2C2C" for those who got maybe the error message that the Glass-Effect couldn't be applied
* Added the "Shell-Tools" menu
* Added the 1st tweak (Pro-Mode)

Bug-Tracker
*FIXED in 0.0.0.2
- Noticed already the missing icons in the "Explorer" (Big Icons + List)
(Bug is already solved and will be fixed in the next version)
Known-Issues
- The "Explorer" "Big Icons" looking a bit ugly, that's because the p/invokes won't give me the "Extra Large" icons... I still work on it, so maybe it's fixed in the next version.
--
Drag 'n' Drop on any Explorer view, from outside the Application won't work until u run everything as Admin... That's a Windows UAC restriction and based on the fact, that we need the right's to create/delete/modify files/folders under Win8++ on the system HDD. (Like ADB pull for export of the oeminfo and custom.bin)
Missing Tweaks from the P9 Lite Toolkit
- As the screenshot shows, i managed to activate the "Double-Tap" menu, but that's all... The Double-Tap it self doesn't work... So there will be no "tweak" for this. - (Additional Info: The Double-Tap works^^ But ONLY on the lock-screen... And ONLY to turn the screen off... What a joke...)
- USB-OTG, is not available because, so far i know, u need a special kernel for it. (Which i can't provide, atm)
- AppTwin, because it should be enabled on any P10 Lite by default
Little - Update (1+2+3+4)
- I added a screenshot of the upcoming release, with integrated "Phone" control. (Currently only Call/Dial works)
- Added another screeny, now (Call/Dial/Add) is possible. Add, needs still interaction on the device side, like which "provider" (Device, Google, etc.) u want to choose. Dial, will insert the number in the default dialer, or it gets captured by any USSD protection. Call, will immediately start a call to the provided number.
- Just tested to send USSD-Codes like "*#06#", but it seems that u really have to type them... Even sending "*#06" and manually type the "#" doesn't work... U have to delete and re-type the whole USSD-Code...
- Added the final look of the "Phone". (At least, Add, Call, Dial, Hang-Up) is now possible.
For those which also use XAML, here are the control-button-geometries i created:
Menu-Button
Code:
<Path Fill="{Binding Foreground, RelativeSource={RelativeSource AncestorType={x:Type Button}}}">
<Path.Data>
<GeometryGroup>
<EllipseGeometry Center="2,2" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="7,2" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="12,2" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="2,6" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="7,6" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="12,6" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="2,10" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="7,10" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="12,10" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="7,14" RadiusX="1.5" RadiusY="1.5"/>
</GeometryGroup>
</Path.Data>
</Path>
Call-Button
Code:
<Path Data="M 1.25,5.55 A 8.5,8.5 0 1 1 0.75,7 Z M 5,9 8,13 13,5" Stroke="{Binding Foreground, RelativeSource={RelativeSource AncestorType={x:Type Button}}}" StrokeThickness="1"/>
Hang-Up-Button
Code:
<Path Data="M 1.25,5.55 A 8.5,8.5 0 1 1 0.75,7 Z M 5,13 13,5 M 5,5 13,13" Stroke="{Binding Foreground, RelativeSource={RelativeSource AncestorType={x:Type Button}}}" StrokeThickness="1"/>
Dial-Button
Code:
<Path Stroke="{Binding Foreground, RelativeSource={RelativeSource AncestorType={x:Type Button}}}" StrokeThickness="1">
<Path.Data>
<GeometryGroup>
<EllipseGeometry Center="9,9" RadiusX="8.5" RadiusY="8.5"/>
<EllipseGeometry Center="6,5" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="9,5" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="12,5" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="6,8" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="9,8" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="12,8" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="6,11" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="9,11" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="12,11" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="9,14" RadiusX="0.5" RadiusY="0.5"/>
</GeometryGroup>
</Path.Data>
</Path>
Delete-Button
Code:
<Path Data="M 0,7.7 5,2 16,3 16,12 5,13 Z M 8,5 13,10 M 8,10 13,5" Stroke="{Binding Foreground, RelativeSource={RelativeSource AncestorType={x:Type Button}}}" StrokeThickness="1"/>

WAS-LX1AC432B204dual
oeminfo

WAS-LX1AC432B206dual
oeminfo

I tested it on my WAS-LX1 C10 DS/ It works.

Perfect
Thank you !

rom issue
Dear Developer!
I suffering with a strange problem, i also opened a question thread about:
https://forum.xda-developers.com/p10-lite/help/please-help-fix-issue-t3805333
I'm not tried your toolkit yet, but i guess it maybe could help me... First: I would like to ask you what do you think about my issue(?). Probably you are much more technical than me, if you were able to create a toolkit for p10 lite... Should i try to fix my phone with your toolkit or can you suggest me any method? Do you have any idea what I could do?
Thanks you in advance!
Greets, NSX

nsx82 said:
Dear Developer!
I suffering with a strange problem, i also opened a question thread about:
https://forum.xda-developers.com/p10-lite/help/please-help-fix-issue-t3805333
I'm not tried your toolkit yet, but i guess it maybe could help me... First: I would like to ask you what do you think about my issue(?). Probably you are much more technical than me, if you were able to create a toolkit for p10 lite... Should i try to fix my phone with your toolkit or can you suggest me any method? Do you have any idea what I could do?
Thanks you in advance!
Greets, NSX
Click to expand...
Click to collapse
Use only stock ROMs for now, cuz there's no daily driver Customs for P10 Lite yet. Stock Oreo is really good. You can use HwOTA to flash stock ROMs.

nsx82 said:
Dear Developer!
I suffering with a strange problem, i also opened a question thread about:
https://forum.xda-developers.com/p10-lite/help/please-help-fix-issue-t3805333
I'm not tried your toolkit yet, but i guess it maybe could help me... First: I would like to ask you what do you think about my issue(?). Probably you are much more technical than me, if you were able to create a toolkit for p10 lite... Should i try to fix my phone with your toolkit or can you suggest me any method? Do you have any idea what I could do?
Thanks you in advance!
Greets, NSX
Click to expand...
Click to collapse
Heyho,
the "NRD-testkeys" are normally an issue with the "cust" partition. That means that ur oeminfo doesn't match with ur "cust" version. Let me explain... If u switch from SS to DS u change the device model (ID - Lx1 -> L21) this causes some problems on the "cust", because there is only one folder existent. The folder matching to the device u had before the switch. So all settings like "phone/umts" etc. are now invalid and can't be found under this model (ID). Because the folder simply doesn't exists.
How to fix it?!
U have to install/flash a complete stock rom via dload. - Get u FOR EXAMPLE an oeminfo like "L21AC432B183" and the rom "L21AC432B183", now u have to flash the oeminfo and straight after it, via dload, the FW upgrade.
-
During the flash of the "L21AC432B183" the system will check that u have "now" a L21 and will align the "cust" to that device.
Hope i could help u to understand how things work
Regards,
Sebastian

k1ll3r8e said:
Heyho,
the "NRD-testkeys" are normally an issue with the "cust" partition. That means that ur oeminfo doesn't match with ur "cust" version. Let me explain... If u switch from SS to DS u change the device model (ID - Lx1 -> L21) this causes some problems on the "cust", because there is only one folder existent. The folder matching to the device u had before the switch. So all settings like "phone/umts" etc. are now invalid and can't be found under this model (ID). Because the folder simply doesn't exists.
How to fix it?!
U have to install/flash a complete stock rom via dload. - Get u FOR EXAMPLE an oeminfo like "L21AC432B183" and the rom "L21AC432B183", now u have to flash the oeminfo and straight after it, via dload, the FW upgrade.
-
During the flash of the "L21AC432B183" the system will check that u have "now" a L21 and will align the "cust" to that device.
Hope i could help u to understand how things work
Regards,
Sebastian
Click to expand...
Click to collapse
Thank you very much for your help. im going to try all of this on next weekend, because workdays i have to use my phone.
greets, NSX
---------- Post added at 12:18 PM ---------- Previous post was at 11:59 AM ----------
k1ll3r8e said:
If u switch from SS to DS u change the device model (ID - Lx1 -> L21) this causes some problems on the "cust", because there is only one folder existent.
Click to expand...
Click to collapse
just a quick question: lx1 is single sim and l21 for dual sim?
Because i had a dual sim model but my sw version was lx1
did i misunderstood something?
btw, i having a very strange problem with the phone, out of the box. seems like a sw render problem. for example in nova launcher i have strange animation distortion and diatorted masking. i was hoping it will be fixed too with changing the rom but this problem still exist.. do you thing it can be because of some wrong factory software inatallation?
thanks, NSX

nsx82 said:
Thank you very much for your help. im going to try all of this on next weekend, because workdays i have to use my phone.
greets, NSX
---
just a quick question: lx1 is single sim and l21 for dual sim?
Because i had a dual sim model but my sw version was lx1
did i misunderstood something?
btw, i having a very strange problem with the phone, out of the box. seems like a sw render problem. for example in nova launcher i have strange animation distortion and diatorted masking. i was hoping it will be fixed too with changing the rom but this problem still exist.. do you thing it can be because of some wrong factory software inatallation?
thanks, NSX
Click to expand...
Click to collapse
Heyho,
np
-
Yes, the "Lx1" are always the SS and the "L[1-9]1" are the DS variants. - Btw. u can't see the "real ID" under "Settings -> Info" to see the "real ID" u have to look in the "current" oeminfo.
-
I wrote a tool for this kind of tweaking/exploring, have a look at it, u can get it here
EDIT:
About the issue with the display/animations, it could also be a problem with the HW... I have seen a few forum posts about "factory delivered" broken chips etc.... Maybe there is something else wrong, if it was really from the 1st day u got it.
Regards,
Sebastian

Little Update
Heyho together
-
Here is a little preview of the upcoming update.
* Added a Remote-Desktop (touch, swipe and keyboard are working so far)
* Improved the speed
* Fixed a few minor bugs
Release should be in 2-3 days
Version 0.0.0.5 is online!
Regards,
Sebastian

k1ll3r8e said:
[Q:03] I want share my custom.bin & oeminfo, what i need to do?
U can get the files via the "Dual-/Single-SIM -> Export" or u can do the following steps (root required).
Open an terminal/cmd prompt and navigate to ur adb installation or the toolkit directory (path/to/the/toolkit/adb) and type the following commands.
Code:
adb shell
su
cat /data/custom.bin > /storage/emulated/0/custom.bin.bak
dd if=/dev/block/platform/hi_mci.0/by-name/oeminfo of=/storage/emulated/0/oeminfo.img.bak
exit
exit
adb pull /storage/emulated/0/custom.bin.bak custom.bin.bak
adb pull /storage/emulated/0/oeminfo.img.bak oeminfo.img.bak
Now u have 2 files, the custom.bin.bak and the oeminfo.img.bak just zip them and upload them to GoogleDrive or DropBox, etc. and share the link in this thread.
Click to expand...
Click to collapse
I guess your Q&A kind of answers my question, though I want to be absolutely sure:
Sharing your oeminfo (and/or custom.bin) file(s) with others, does not give away any personal/unique info. I checked my oeminfo with a HexEditor and it seems to include my Firmware upgrade history (at least the last two updates), IMSI (only SIM/Network Operator - unless I overlooked something), and those hmac/&token values. With these infos nobody should be able to "do bad stuff" - am I right?
Please correct me if I'm wrong. Thanks in advance for any input, cheers!

callmeWhiskers said:
I guess your Q&A kind of answers my question, though I want to be absolutely sure:
Sharing your oeminfo (and/or custom.bin) file(s) with others, does not give away any personal/unique info. I checked my oeminfo with a HexEditor and it seems to include my Firmware upgrade history (at least the last two updates), IMSI (only SIM/Network Operator - unless I overlooked something), and those hmac/&token values. With these infos nobody should be able to "do bad stuff" - am I right?
Please correct me if I'm wrong. Thanks in advance for any input, cheers!
Click to expand...
Click to collapse
Heyho,
if you would have used my OEMInfo Tools, you would have seen that those values are no secret.
-
For example, the FW builds are needed to determine the current OS and if needed, the fallback/restore versions. Also the HMAC is needed for the OTA (the HMAC is used in conjunction with your IMEI, so the HMAC alone, is worth nothing). There is also a "Tamper-State" when and how often you unlocked/rooted your device.
But so far i saw, there are no "personal" data, like the IMEI or the SIM-Card Number. Maybe they are stored as one of those checksums (md5/sha1).
Regards,
Sebastian

k1ll3r8e said:
if you would have used my OEMInfo Tools, you would have seen that those values are no secret.
-
For example, the FW builds are needed to determine the current OS and if needed, the fallback/restore versions. Also the HMAC is needed for the OTA (the HMAC is used in conjunction with your IMEI, so the HMAC alone, is worth nothing). There is also a "Tamper-State" when and how often you unlocked/rooted your device.
But so far i saw, there are no "personal" data, like the IMEI or the SIM-Card Number. Maybe they are stored as one of those checksums (md5/sha1).
Click to expand...
Click to collapse
Thank you very much for clarifying and shedding some light on this, Sebastian!
From what I've read, reconstructing (files) from checksums doesn't (really/easily) work - though in theory (if enough additional parameters are given, and IMEI/IMSI are kind of short strings) it could be reverse engineered - unless I interpreted my research findings wrong :victory:
I assume it's safe though
Liebe Grüße nach Delmenhorst!

Hi world(first post since android(previous windows mobile member of xda)),
I have P10 lite for almost a year(not rooted for warranty issues).
I wanted to perform a stock firmware backup before I endulge in rooting/custom ROM.
Is that possible with TWRP(with or without rooting), and are there any how-to's?
Sorry for being such a newbie, just like to upgrade to 8.0 and revert back to stock in case of a problem or warranty issues.
Thank you.

Recovery

[ROM][magisk-based]*** GoogleWiz *** {Pixelize your OnePlus 7T pro}

***
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Wiz *** Pixelize your OnePlus 7T pro
"Extreme debloat: Go where OnePlus has never gone before"
You thought that OnePlus phones were pretty stock Android? Hmmm .... think again ... there's still lots of stuff on these phones that you actually don't need (or want).
For example, did you know they have an engineering mode? Did you know that they can connect to your phone remotely? Did you know that when the phone starts up it connects to a OnePlus server in the back? Well, I don't want all that ...
In addition, there are even standard things in Android that only 0.01% of the people ever use ... for example ... tracing, android dumps, ... these things are disabled in this ROM.
Then there's bits and pieces of Qualcomm stuff that you actually do not need/want (I don't even know what they do).
This is a ROM in the form of a Magisk (thanks: @topjohnwu) module. That's great (I think). You can install it on top of the normal OnePlus software. If you don't like it or want to revert back to the "standard" OnePlus software, just remove the Magisk module and ... done!
Upfront "warning"
There are a few features which I personally do not use. When you install this module then:
- you will no longer have face unlock
- you will not have VoLTE (I have disabled this because it does not work on my carrier)
Basic requirement
(1) Your OnePlus 7T pro must be ROOTED! Without root, do not read any further as you will not be able to use this ROM. There are other threads in the OnePlus 7T Pro pro forums which explain how to root (so please don't start asking how to do this).
(2) You must also be on the latest OnePlus software: 10.0.7.HD01BA (since I own a EU model of the OnePlus 7T pro, I have ONLY tested this ROM in this device/software). It "may" work on other variants of the device ... but I don't know. I can't answer questions to that either.
(3) You must have access to ADB over USB. If you don't know what this means, stop reading, then this is not for you.
Kernel requirement
This ROM will work with the standard out-of-the-box OnePlus 7T pro kernel. However, I would strongly advice you to flash the "arter97" kernel (see https://forum.xda-developers.com/on...development/arter97-kernel-oneplus-7-t3952578). It's a fantastic kernel and this ROM has some optimizations which go very well with this kernel (don't worry, they will work on the standard kernel as well).
Download?
Interested? Start downloading the magisk module from the link below (but please read further for installation instructions !!!).
https://drive.google.com/file/d/1XpiDKFQiuFuuTBvbKMAsxMH-B9Obi-Gz/view?usp=sharing
(click on the donwload icon upper right of screen)
The link contains always the LATEST version; check the changelog in post #2 below. You can find the file size and md5sum there as well.
Changelog
See post #2 below.
History
I once owned a Galaxy S8. ***GoogleWiz*** was one one the most popular ROMs on that phone. See https://forum.xda-developers.com/ga...t/rom-googlewiz-oreo-extreme-debloat-t3750641. The difference is that I have now converted this to a Magisk module (reason: the "dynamic partitioning scheme" of Android Q makes it really hard to flash in the classical way; as you know even full TWRP functionality does currently not exist for the OnePlus 7T pro.
(Re)Using this work
Other devs, please feel free to (re)use this for your own work ... I am not asking anything from anybody, no donation, no thanks, no beer ... you don't even have to mention that you (re)use this. We are here on XDA to share and learn from eachother. If you unzip the Magisk module, you can see exactly what is inside. But ... there has been quite some work into this. It was not created in 5 minutes. But I do this as a "hobby" ... I have always rooted and customized my Android phones. So hopefully you will enjoy. Source code in post #3 (https://forum.xda-developers.com/showpost.php?p=81887167&postcount=3).
Telegram
No telegram group; I don't have time for that, so do not ask please.
Features
The ROM does NOT contain OnePlus applications! The only OnePlus applications are "Settings" and "Camera".
Nova launcher (https://play.google.com/store/apps/details?id=com.teslacoilsw.launcher)
SwiftKey keyboard (https://play.google.com/store/apps/details?id=com.touchtype.swiftkey)
Google
play services (which can be put into doze mode)
play store (https://play.google.com/store)
photos (used as gallery; but NOT integrated with camera) (https://play.google.com/store/apps/details?id=com.google.android.apps.photos)
dialer (https://play.google.com/store/apps/details?id=com.google.android.dialer) with spam detect and nearby places
contacts (https://play.google.com/store/apps/details?id=com.google.android.contacts)
messaging (https://play.google.com/store/apps/details?id=com.google.android.apps.messaging)
text-to-speech (https://play.google.com/store/apps/details?id=com.google.android.tts)
gmail (https://play.google.com/store/apps/details?id=com.google.android.gm)
keep (https://play.google.com/store/apps/details?id=com.google.android.keep)
drive (https://play.google.com/store/apps/details?id=com.google.android.apps.docs)
maps (https://play.google.com/store/apps/details?id=com.google.android.apps.maps)
chrome (https://play.google.com/store/apps/details?id=com.android.chrome)
clock (with Spotify integration) (https://play.google.com/store/apps/details?id=com.google.android.deskclock)
calendar (https://play.google.com/store/apps/details?id=com.google.android.calendar)
calculator (https://play.google.com/store/apps/details?id=com.google.android.calculator)
search app integrated with Nova search bar (https://www.google.com/search/about/)
assistant (https://www.apkmirror.com/apk/google-inc/google-assistant/)
tasks (https://play.google.com/store/apps/details?id=com.google.android.apps.tasks)
translate (https://play.google.com/store/apps/details?id=com.google.android.apps.translate)
earth (https://play.google.com/store/apps/details?id=com.google.earth)
fit (https://play.google.com/store/apps/details?id=com.google.android.apps.fitness)
now cards integrated with Nova launcher (see https://forum.xda-developers.com/showpost.php?p=75591011&postcount=4)
lens (https://play.google.com/store/apps/details?id=com.google.ar.lens)
news (https://play.google.com/store/apps/details?id=com.google.android.apps.magazines)
chromecast (aka Google home) (https://play.google.com/store/apps/details?id=com.google.android.apps.chromecast.app)
youtube (https://play.google.com/store/apps/details?id=com.google.android.youtube)
markup (https://9to5google.com/2018/03/07/android-p-dp1-markup-screenshot-editor/)
measure (https://play.google.com/store/apps/details?id=com.google.tango.measure)
weather (just type "weather" in the google search app; it will offer you to get an icon on the desktop)
android auto (Google's car mode) (https://www.android.com/auto/)
snapseed photo editor (https://play.google.com/store/apps/details?id=com.niksoftware.snapseed)
docs (https://play.google.com/store/apps/details?id=com.google.android.apps.docs.editors.docs)
slides (https://play.google.com/store/apps/details?id=com.google.android.apps.docs.editors.slides)
spreadsheets (https://play.google.com/store/apps/details?id=com.google.android.apps.docs.editors.sheets)
streetview (https://play.google.com/store/apps/details?id=com.google.android.street)
pixel icons in statusbar, quick settings tiles
pixel ringtones, notifications, UI sounds
camera2 API enabled (but I don't think this actuall does something useful)
- OnePlus bloatware removed (dialer, phone, messages, calculator, notes, gallery, zen, ...) + lots of background APKs
- OnePlus background processes (which send data to OnePlus) are disabled
- ad-free through large "hosts" file (works both for apps and web pages)
- lots of optimizations, really, *lots* of them (too many to list)
- support for init.d / services.d (see posts below if you want to use this)
- passes SafetyNet (I am using Google Pay and some Belgian NFC pay apps)
- "clean" and as close as possible to a Pixel phone
- optimized network/wifi config
- optimized touchboost (slightly faster application startup)
- optimized kernel scheduling settings
- disabled all kernel debugging/tracing
- frequency scaling throughout full CPU frequency ranges (saves battery and better performance when needed)
- disables swapping / zram (who needs this with 8GB of RAM)?
- bash shell in "su" mode (when using "adb shell")
- latest busybox (by @osm0sis)
- 1x7 icon row for quick settings, 5 icons per row when you swipe down the full quick settings
- added .xml permission files to enable Pixel exclusive features (e.g. Google dialer)
- optimized .proto, .conf, .json, .ini, .sql files in the system
- improved thumbnail quality
- dalvik VM optimized settings (for "speed")
- auto clean junk files at boot time
- optimized audio settings
- optimized camera settings (e.g. supernight mode; but personally I don't see a difference in the night pictures)
- disabled "factory" and "engineering" mode
- reduced wifi scan interval
- auto sqlite optimization at boot time (only runs every 3 days)
- support for both 2.4GHz and 5GHz wifi bonding
- speaker and headset volume boost
Installation (really IMPORTANT to read)
You must start from the 10.0.7 "standard" OnePlus 7T pro software. I suggest you do a clean install from factory reset. Strictly speaking a full reset is not needed (so you could just go and install the Magisk module on your phone) but there may be certain side effects in that case. Anyway, assuming you will do a full reset, follow the instructions below:
Go to Settings > System > Reset options > Erase all data (factory reset)
Proceed through the normal setup sequence: accept the terms and conditions of OnePlus, skip the User Experience Program, skip the System Stability Program, skip the Push Notifications, skip the Built-in App Updates, connect to your wifi network, do NOT copy apps and data, enter your google account email of phone number, enter your google password, do 2 factor authentication (if you have enabled this on your google account), if a dialog pops up with "Add your current account", do that, disable Backup to Google Drive, disable Use Location, disable Send Usage and Diagnostic Data, type NEXT to use fingerprint, enter PIN code (twice), set up 1 or more fingerprints, you see a message about Google Assistant, press NEXT, you see a message about Google Pay, press Got It, skip the Anything Else screen, choose your screen calibration, choose font (slight preference for Roboto, better compatibility with Google apps), choose Navigation bar or Gestures, press START on the Setup Complete screen, you are now in the OnePlus launcher, allow carrier location service, swipe down the notification which says: Android Setup, click on Finish Setup, copy your data if you want that, press START, system will now check for updates, let it complete, copy your data from cloud or iphone, continue until you are back in the OnePlus launcher, go to Settings > About phone, tap build number 7 times to activate developer options (if you don't know what this is, search XDA)., enter your PIN, press back arrow, go to Settings > System > Developer options, enable "Advanced reboot", disable "Automatic system updates", enable "USB debugging mode", connect your phone to a PC, a dialog will pop up to Allow USB debugging (tick "Always allow from this computer") and press ALLOW, install the LATEST Magisk Manager APK (see https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445), push the Magisk Manager APK to your phone, e.g.
Code:
> adb push MagiskManager-v7.5.1.apk /sdcard/
open the app drawer, open the app called "Files", on the upper right, click the 3 dots, then "Show internal storage", on the upper left, click the 3 lines, select "OnePlus 7T Pro", scroll down and click on MagiskManager-v7.5.1.apk; install the app, open Magisk Manager, it will say your phone requires Additional Setup, click OK ... your phone will reboot 5 seconds later, open Play Store, select My Apps and Games, it will say that a number of updates are pending, press "Update all", exit Play Store, reopen it ... it might still say that there are pending updates, do them, activate NETFLIX ... do it NOW ... (if you first install the Magisk module, you will no longer be able to activate Netflix), push the downloaded magisk module to your phone
Code:
> adb push mm-googlewiz.zip /sdcard/
open the Magisk Manager app, press the 3 lines (top left of screen), press Modules, press + button (and allow Magisk Manager to access media), press the 3 lines top left in the file manager, select OnePlus 7T pro, scroll down and click on the mm-googlewiz.zip file, Magisk Manager will now install the module ... you will see some text output on the screen ... wait until installation is done (it will take a minute or so), press the yellow Reboot button which appears (your phone will reboot), unlock the lock screen by entering your PIN, let the ROM settle 30 secs ... it will say "Restarting" and reboot once more your phone, unlock the lock screen by entering your PIN, open the drawer, open the Settings app (will be in black mode [my personal liking] ... you can change later back to white), press Apps & Notifications, select Default Apps, press home app and select Nova Launcher, open Settings, press Apps & Notifications, select Default Apps => select "Phone app" and then select "Phone" (this is the Google phone app)
Now you will have NOVA launcher as default ... which you can customize to your liking (much better than OnePlus launcher).
Open Drawer, use the app Nova-settings to customize.
Open Drawer, click on "Nova Google Companion" => this will enable left swipe Google Now behavior in Nova launcher
Done! .... now you can further customize your phone in any way you want ...
Bootloop?
If - after installation - you should get into a bootloop then check the following thread (https://forum.xda-developers.com/7t-pro/how-to/guide-remove-magisk-modules-twrp-t3995677) for how to remove the Magisk module.
Disclaimer
I will try to support questions / feedback. I will not answer questions such as "Can you please add OnePlus feature X,Y,Z" ... I have deliberately removed them. If you want OnePlus apps, use the standard OnePlus software.. The usual applies: no warranty, installing this void warranty, install at your own risk, ... I am not responsible for soft or hard bricks. Your phone must be rooted (again).
Help ... I really don't like it ... I want to remove it ...
Stay calm. Open Magisk Manager, press the 3 lines top left on screen, press Modules, then press the trash icon next to "googlewiz" module and reboot ... you will have the standard OnePlus software again.
Removing Google apps
You can remove Google apps from the ROM as follows. Go to the following URL: https://raw.githubusercontent.com/foobar66/googlewiz/master/googlewiz.config click right and then "Save as". Save the file using "googlewiz.config" as file name. Note that this file is a LINUX plan vanilla text file. The file will look as follows:
Code:
keep=1
lens=1
news=1
assistant=1
sheets=1
snapseed=1
street=1
home=1
measure=1
fit=1
tasks=1
earth=1
slides=1
clock=1
calculator=1
docs=1
Edit the file and put "xyz=0" for Google apps that you do NOT want to install. Above is respectively for Google {Keep, Lens, News, Assistant, Sheets, Snapseed, Streetview, Home, Measure, Fit, Tasks, Earth, Slides, Clock, Calculator, Docs}. Put the file onto your sdcard, e.g. via adb ("adb push googlewiz.config /sdcard/"). Download today's version ([version: 2020-03-30 18:28]) of the module (or later). Re-install the module via Magisk manager and reboot. You will see debug output on the screen during module installation which Google apps are getting removed.
Credits
@topjohnwu, @osm0sis, @Zackptg5, @DeadmanxXD, @arter97

Changelog
[version: 2020-02-28 17:28]
Initial version
File size: 877404687, MD5: 038c3285a68e2be5421dc1a3eb2d041e
[version: 2020-03-01 08:34]
- fix some permissions in system/xbin files
- updated com.google.android.apps.docs.editors.sheets
- updated com.google.android.apps.turbo
File size: 881052548, MD5: 7fed9105aaba0bb1def6ca145527ea4d
[version: 2020-03-01 10:54]
- use original APN files
- update com.google.android.apps.docs.editors.sheets
File size: 881149942, MD5: 93d54a90fef970d7250723895b7c6cec
[version: 2020-03-11 18:46]
- small bug fixes
- upgraded a number of Google apps to latest version
File size: 898125981, MD5: 4b82cff7e572da635f6ca252ec54f58f
[version: 2020-03-30 18:28]
- updates to Google apps
- supports configuration file /sdcard/googlewiz.config
File size: 898132639, MD5: 1bcfa989673f3e59a378243306dc3d94
[2020-04-30 07:09]
- updated to Google apps
- update to latest OnePlus camera
- added Android Auto phone screen
File size: 963547129, MD5: 67a5057d0e882ec38b7e5101c8d0bbe7

How was this Magisk module created?
Actually the Magisk module is generated by a bash script (I use linux) starting from the original OnePlus software zips.
The script is attached to this thread. Download the zip file attached and then rename the file by removing the ".zip" extention). You will have a plain Linux bash shell script file. No secrets. Sharing all in the open (which I believe should be the spirit of XDA).
Reuse as you like ...
Source code
Feel free to (re)use ... no secrets, no hidden stuff, no need to thanks, no need to donate ...
https://github.com/foobar66/googlewiz
My only request ... if you make an interesting improvement, please share with the community so we all can benefit from it!

Misc stuff
a) How do you debloat? Well ... there are different ways.
- some init.rc files are not needed, the Magisk module bind-mounts "empty" files over the original ones so they do not run
- OnePlus APKs are "debloated" by bind-mounting an "empty" APK over them; Android will no longer recognize them as valid applications
- some background processes are not needed, they are "debloated" by bind-mounting empty files over the executables in /system/bin
Unzip the Magisk module, look at the file called "service.sh" and you will understand how this is done (partly).
Check out the previous post where you can find the bash shell script which I use to "generate" the Magisk module.
b) Debug info
To see what the module has done during boot, there is a dedicated log file /data/googlewiz/googlewiz.log, do:
Code:
> adb shell
$ su
# cat /data/googlewiz/googlewiz.log
c) Logging of init.d and services.d scripts. Init.d scripts run immediately together with Android boot. services.d scripts run once /sdcard is mounted. To see the debug output do:
Code:
> adb shell
$ su
# cat /data/LS00*
# cat /data/LS99*
d) You talk about "bloatware" ... what is actually "removed"?
Code:
./system/vendor/app/com.qualcomm.qti.improvetouch.service/com.qualcomm.qti.improvetouch.service.apk
./system/vendor/app/PowerOffAlarm/PowerOffAlarm.apk
./system/vendor/app/CACertService/CACertService.apk
./system/vendor/app/CneApp/CneApp.apk
./system/vendor/app/IWlanService/IWlanService.apk
./system/vendor/app/pasrservice/pasrservice.apk
./system/product/app/remotesimlockservice/remotesimlockservice.apk
./system/product/app/SimSettings/SimSettings.apk
./system/product/app/Duo/Duo.apk
./system/product/app/QdcmFF/QdcmFF.apk
./system/product/app/OPCarrierLocation/OPCarrierLocation.apk
./system/product/app/datastatusnotification/datastatusnotification.apk
./system/product/app/embms/embms.apk
./system/product/app/GoogleLocationHistory/GoogleLocationHistory.apk
./system/product/app/uceShimService/uceShimService.apk
./system/product/app/Music2/Music2.apk
./system/product/app/imssettings/imssettings.apk
./system/product/app/PerformanceMode/PerformanceMode.apk
./system/product/app/uimgbaservice/uimgbaservice.apk
./system/product/app/TTS/TTS.apk
./system/product/app/talkback/talkback.apk
./system/product/app/Videos/Videos.apk
./system/product/app/uimlpaservice/uimlpaservice.apk
./system/product/app/DynamicDDSService/DynamicDDSService.apk
./system/product/app/uimremoteclient/uimremoteclient.apk
./system/product/app/com.qualcomm.qti.services.secureui/com.qualcomm.qti.services.secureui.apk
./system/product/app/LatinImeGoogle/LatinImeGoogle.apk
./system/product/app/DeviceInfo/DeviceInfo.apk
./system/product/app/CallFeaturesSetting/CallFeaturesSetting.apk
./system/product/app/TmoEngMode/TmoEngMode.apk
./system/product/app/ConfURIDialer/ConfURIDialer.apk
./system/product/app/uimremoteserver/uimremoteserver.apk
./system/product/app/colorservice/colorservice.apk
./system/product/app/remoteSimLockAuthentication/remoteSimLockAuthentication.apk
./system/product/priv-app/GoogleFeedback/GoogleFeedback.apk
./system/product/priv-app/StorageManager/StorageManager.apk
./system/product/priv-app/GoogleRestore/GoogleRestore.apk
./system/product/priv-app/CarrierConfig/CarrierConfig.apk
./system/product/priv-app/OPAppLocker/OPAppLocker.apk
./system/product/priv-app/GooglePartnerSetup/GooglePartnerSetup.apk
./system/product/priv-app/daxService/daxService.apk
./system/product/priv-app/dpmserviceapp/dpmserviceapp.apk
./system/product/priv-app/seccamservice/seccamservice.apk
./system/product/priv-app/QAS_DVC_MSP/QAS_DVC_MSP.apk
./system/product/priv-app/WallpaperCropper/WallpaperCropper.apk
./system/product/priv-app/AndroidAutoStub/AndroidAutoStub.apk
./system/product/priv-app/ims/ims.apk
./system/product/priv-app/ConfigUpdater/ConfigUpdater.apk
./system/app/OPAppUpgrader/OPAppUpgrader.apk
./system/app/OPLiveWallpaper/OPLiveWallpaper.apk
./system/app/OPBugReportLite/OPBugReportLite.apk
./system/app/OPFilemanager/OPFilemanager.apk
./system/app/DeskClock/DeskClock.apk
./system/app/BuiltInPrintService/BuiltInPrintService.apk
./system/app/NVBackupUI/NVBackupUI.apk
./system/app/GooglePrintRecommendationService/GooglePrintRecommendationService.apk
./system/app/OPBreathMode/OPBreathMode.apk
./system/app/OPSoundTuner/OPSoundTuner.apk
./system/app/SimAppDialog/SimAppDialog.apk
./system/app/WapiCertManage/WapiCertManage.apk
./system/app/EngSpecialTest/EngSpecialTest.apk
./system/app/Backup/Backup.apk
./system/app/Traceur/Traceur.apk
./system/app/PacProcessor/PacProcessor.apk
./system/app/CarrierDefaultApp/CarrierDefaultApp.apk
./system/app/OPScreenRecord/OPScreenRecord.apk
./system/app/CompanionDeviceManager/CompanionDeviceManager.apk
./system/app/OPMmsLocationFramework/OPMmsLocationFramework.apk
./system/app/SmscPlugger/SmscPlugger.apk
./system/app/OPGamingSpace/OPGamingSpace.apk
./system/app/OPBackup/OPBackup.apk
./system/app/BasicDreams/BasicDreams.apk
./system/app/OemAutoTestServer/OemAutoTestServer.apk
./system/app/ARCore_stub/ARCore_stub.apk
./system/app/EngineeringMode/EngineeringMode.apk
./system/app/SoterService/SoterService.apk
./system/app/OPIntelliService/OPIntelliService.apk
./system/app/PartnerBookmarksProvider/PartnerBookmarksProvider.apk
./system/app/OPGeoIpTime/OPGeoIpTime.apk
./system/app/WAPPushManager/WAPPushManager.apk
./system/app/oem_tcma/oem_tcma.apk
./system/app/SensorTestTool/SensorTestTool.apk
./system/app/WifiRfTestApk/WifiRfTestApk.apk
./system/app/BackupRestoreRemoteService/BackupRestoreRemoteService.apk
./system/app/SdCardService/SdCardService.apk
./system/app/BookmarkProvider/BookmarkProvider.apk
./system/app/PhotosOnline/PhotosOnline.apk
./system/app/OPPush/OPPush.apk
./system/app/QColor/QColor.apk
./system/app/Calculator/Calculator.apk
./system/app/AntHalService/AntHalService.apk
./system/app/WallpaperBackup/WallpaperBackup.apk
./system/app/CtsShimPrebuilt/CtsShimPrebuilt.apk
./system/app/OEMLogKit/OEMLogKit.apk
./system/app/OPCommonLogTool/OPCommonLogTool.apk
./system/app/PlayAutoInstallConfig/PlayAutoInstallConfig.apk
./system/app/LiveWallpapersPicker/LiveWallpapersPicker.apk
./system/app/BluetoothMidiService/BluetoothMidiService.apk
./system/app/Rftoolkit/Rftoolkit.apk
./system/app/EasterEgg_O2/EasterEgg_O2.apk
./system/app/HTMLViewer/HTMLViewer.apk
./system/app/OPWallpaperResources/OPWallpaperResources.apk
./system/app/Netflix_Stub/Netflix_Stub.apk
./system/app/BTtestmode/BTtestmode.apk
./system/app/OPTelephonyDiagnoseManager/OPTelephonyDiagnoseManager.apk
./system/app/OPSesAuthentication/OPSesAuthentication.apk
./system/app/LogKitSdService/LogKitSdService.apk
./system/app/Netflix_Activation/Netflix_Activation.apk
./system/app/NFCTestMode/NFCTestMode.apk
./system/priv-app/Houston/Houston.apk
./system/priv-app/OPMms/OPMms.apk
./system/priv-app/InputDevices/InputDevices.apk
./system/priv-app/ProxyHandler/ProxyHandler.apk
./system/priv-app/DynamicSystemInstallationService/DynamicSystemInstallationService.apk
./system/priv-app/OPAppCategoryProvider/OPAppCategoryProvider.apk
./system/priv-app/OPCellBroadcastReceiver/OPCellBroadcastReceiver.apk
./system/priv-app/OPFaceUnlock/OPFaceUnlock.apk
./system/priv-app/LocalTransport/LocalTransport.apk
./system/priv-app/Contacts/Contacts.apk
./system/priv-app/HotwordEnrollmentOKGoogleWCD9340/HotwordEnrollmentOKGoogleWCD9340.apk
./system/priv-app/ONS/ONS.apk
./system/priv-app/ManagedProvisioning/ManagedProvisioning.apk
./system/priv-app/TagGoogle/TagGoogle.apk
./system/priv-app/RcsSDK/RcsSDK.apk
./system/priv-app/CallLogBackup/CallLogBackup.apk
./system/priv-app/OnePlusGallery/OnePlusGallery.apk
./system/priv-app/OPDeviceManager/OPDeviceManager.apk
./system/priv-app/WfdService/WfdService.apk
./system/priv-app/OPDeviceManagerProvider/OPDeviceManagerProvider.apk
./system/priv-app/CtsShimPrivPrebuilt/CtsShimPrivPrebuilt.apk
./system/priv-app/IFAAService/IFAAService.apk
./system/priv-app/SharedStorageBackup/SharedStorageBackup.apk
./system/priv-app/HotwordEnrollmentXGoogleWCD9340/HotwordEnrollmentXGoogleWCD9340.apk
./system/priv-app/MmsService/MmsService.apk
./system/priv-app/EmergencyInfo/EmergencyInfo.apk
./system/priv-app/BackupRestoreConfirmation/BackupRestoreConfirmation.apk
./system/priv-app/Dialer/Dialer.apk
./system/priv-app/OPSimContacts/OPSimContacts.apk
d) Which /etc/init scripts are disabled?
Code:
system/etc/init/tombstoned.rc
system/etc/init/perfetto.rc
system/etc/init/atrace.rc
system/etc/init/bluetooth-events.rc
system/etc/init/[email protected]
system/etc/init/perfservice.rc
system/etc/init/heapprofd.rc
system/etc/init/dumpstate.rc
system/etc/init/sarahd.rc
system/etc/init/incidentd.rc
system/etc/init/traceur.rc
system/etc/init/iorapd.rc
system/etc/init/bootstat.rc
system/etc/init/mdnsd.rc
system/etc/init/uncrypt.rc
system/etc/init/engineermode.rc
system/etc/init/recovery-persist.rc
system/etc/init/caffed.rc
system/etc/init/update_verifier.rc
system/etc/init/rss_hwm_reset.rc
system/etc/init/wfdservice.rc
system/etc/init/update_engine.rc
system/etc/init/recovery-refresh.rc
system/etc/init/flags_health_check.rc
system/etc/init/statsd.rc
e) If you want to have full "black", use Substratum (https://play.google.com/store/apps/details?id=projekt.substratum) and the Swift Black theme (https://play.google.com/store/apps/details?id=com.brit.swiftblack.layers). That will allow you to mod all the Google apps (and others) into full black mode.
f) "adb logcat" does not seem to move ... correct, to re-enable it do:
Code:
> adb shell
$ su
# setprop log.tag I

i use face unlock...

yenkoPR said:
i use face unlock...
Click to expand...
Click to collapse
Good for you, stick with OnePlus standard software.

Nice one might give this a blast later thanks op?

Ok what have I done wrong lol ?

jaythenut said:
Ok what have I done wrong lol ?
Click to expand...
Click to collapse
You downloaded from: https://mega.nz/#!2BZSiCwR!A4VQ6ZhSr...Sd_8F5W8Njb5Sg
I downloaded and it installs fine for me (just to be sure I was not using a local copy) ... it installs fine for me.
Check the md5 sum if you know how to do that: 3fb9c987cbe94874471c7c699e65d8a1

foobar66 said:
You downloaded from: https://mega.nz/#!2BZSiCwR!A4VQ6ZhSr...Sd_8F5W8Njb5Sg
I downloaded and it installs fine for me (just to be sure I was not using a local copy) ... it installs fine for me.
Check the md5 sum if you know how to do that: 3fb9c987cbe94874471c7c699e65d8a1
Click to expand...
Click to collapse
Asking for decryption key ?

jaythenut said:
Asking for decryption key
Click to expand...
Click to collapse
Weird ... that is the first time I see mega doing this ...
I will upload to a different cloud storage ... please wait a few mins ...
Edit: uploading to my Google drive ... will take 30 mins ...
Edit: OK ... file is uploaded to Google drive, please use following link:
https://drive.google.com/file/d/1XpiDKFQiuFuuTBvbKMAsxMH-B9Obi-Gz/view?usp=sharing
(click on the donwload icon upper right of screen)
File size: 877404687, MD5: 038c3285a68e2be5421dc1a3eb2d041e
I will update OP as well.

Can I 'dirty install' over the latest global stock ROM (already rooted with Magisk)?
Is the stock call recorder activated on this ROM?
Also, any possibility of working V4A being bundled in with this ROM? (I had no luck via the adb method).
Many thanks.

elmor0 said:
Can I 'dirty install' over the latest global stock ROM (already rooted with Magisk)?
Click to expand...
Click to collapse
Is the stock call recorder activated on this ROM?
Also, any possibility of working V4A being bundled in with this ROM? (I had no luck via the adb method).
Many thanks.[/QUOTE]
Dirty install should be possible.
ROM uses the Google dialer, so no call recording for now.
V4A ... never tried it so far, I would need to investigate ... try to find a Magisk module for it (not sure if that exists).

Done a dirty flash all seems to be working fine so far ?

Hi, thx for your work. Sadly for me its not working. Going to endless boot. Followed every Step. Sadly I didnt realize that I have Netflix installed wich was not Active and now even after removing the Modules it Says not Compatible with my Device....My Vault... Is there a Workaround for this?
Iam on Hd 1.0.0.7 AB
Edit: got it fixed with Netflix but even after full reset Iam not able to boot this Module

iceraum said:
Hi, thx for your work. Sadly for me its not working. Going to endless boot. Followed every Step. Sadly I didnt realize that I have Netflix installed wich was not Active and now even after removing the Modules it Says not Compatible with my Device....My Vault... Is there a Workaround for this?
Iam on Hd 1.0.0.7 AB
Edit: got it fixed with Netflix but even after full reset Iam not able to boot this Module
Click to expand...
Click to collapse
Did you have any other Magiks modules active when you tried to install this one?

foobar66 said:
Did you have any other Magiks modules active when you tried to install this one?
Click to expand...
Click to collapse
No. Just Clean new Install after Factory reset.

can i use this rom for op7p ?
and one question. hows swipe to home animation doing here? i've tried nova launcher on stock rom but swipe to home doesnt work properly and i the app icon doesn't collapse nicely

Dark Fear said:
can i use this rom for op7p ?
and one question. hows swipe to home animation doing here? i've tried nova launcher on stock rom but swipe to home doesnt work properly and i the app icon doesn't collapse nicely
Click to expand...
Click to collapse
I don't know it if will work for op7p ... try ...
Swipe to home works fine for me on OnePlus 7T pro

iceraum said:
No. Just Clean new Install after Factory reset.
Click to expand...
Click to collapse
Which country are you in? Just realize that I might have copied the wrong APN file ... (but not sure this is why it does not work in your case).
I am uploading a new version with the original APN files ... please wait a bit.
Edit: new version available (use original download link).

Question Konabess config for OnePlus 11 global / Indian variant

Hello so I was wondering if anyone here -> global, Indian user have tried to flash konabess GPU profile ? Cuz everytime when I do all works fine except stock camera app which start to show random issues like - camera lagging, force close etc.
The konabess file I was using have these -
[email protected]~692 lv1
clock - wle score/w
150 - 884 2.32w
220 - 1271 2.65w // -0.26w
295 - 1643/3.11w // -0.25w
348 - 1875/3.46w // -0.33w
401 - 2070/3.74w // -0.54w
475 - 2457/4.11w // -0.67w
550 - 2926/5.27w // -0.25w
615 - 3345/5.72w // -1.11w
692 - 3711/6.3w // -1.15w
So if anyone can test this, edit and make it work fine for both global and Indian variant it will be a big help ^_^

It works on global, I tried it.
Didn't tried camera, seems I have same problems. A bit lag and crashed when I tap on the miniature of photo taken to open it.
I restored the img backed up by konabess (vendor_boot, stock one) with termux and camera works well now.