Develop Bugs

[Q][DEV-ONLY] PORT SMS COUNTER from XPERIA J/Miro

Hello everyone!
I'm trying to port SMS Counter from Xperia J to Xperia S JB Settings.apk.
I know @niaboc79 inluded it in his eXistenZ v2, however wifi tethering doesn't work with 96 firmware.
Probably it'll be a silly thing but I haven't been able to find a solution yet to this problem. Here's the logcat:
Code:
I/ActivityManager( 574): START {act=android.intent.action.MAIN cmp=com.android.settings/.SubSettings (has extras) u=0} from pid 2145
E/AndroidRuntime( 2145): FATAL EXCEPTION: main
E/AndroidRuntime( 2145): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.settings/com.android.settings.SubSettings}: [B][B][B]android.view.InflateException: Binary XML file line #2: Error inflating class appwidget-provider[/B][/B][/B]
E/AndroidRuntime( 2145): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2071)
E/AndroidRuntime( 2145): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2096)
E/AndroidRuntime( 2145): at android.app.ActivityThread.access$600(ActivityThread.java:138)
E/AndroidRuntime( 2145): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1207)
E/AndroidRuntime( 2145): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 2145): at android.os.Looper.loop(Looper.java:213)
E/AndroidRuntime( 2145): at android.app.ActivityThread.main(ActivityThread.java:4787)
E/AndroidRuntime( 2145): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 2145): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 2145): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:789)
E/AndroidRuntime( 2145): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:556)
E/AndroidRuntime( 2145): at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:110)
E/AndroidRuntime( 2145): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 2145): Caused by: android.view.InflateException: Binary XML file line #2: Error inflating class appwidget-provider
E/AndroidRuntime( 2145): at android.preference.GenericInflater.createItemFromTag(GenericInflater.java:441)
E/AndroidRuntime( 2145): at android.preference.GenericInflater.inflate(GenericInflater.java:317)
E/AndroidRuntime( 2145): at android.preference.GenericInflater.inflate(GenericInflater.java:263)
E/AndroidRuntime( 2145): at android.preference.PreferenceManager.inflateFromResource(PreferenceManager.java:269)
E/AndroidRuntime( 2145): at android.preference.PreferenceFragment.addPreferencesFromResource(PreferenceFragment.java:285)
E/AndroidRuntime( 2145): at com.sonyericsson.settings.smscounter.SmsCounterSettings.onCreate(SmsCounterSettings.java:193)
E/AndroidRuntime( 2145): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:800)
E/AndroidRuntime( 2145): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1039)
E/AndroidRuntime( 2145): at android.app.BackStackRecord.run(BackStackRecord.java:635)
E/AndroidRuntime( 2145): at android.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:1405)
E/AndroidRuntime( 2145): at android.app.Activity.performStart(Activity.java:5017)
E/AndroidRuntime( 2145): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2044)
E/AndroidRuntime( 2145): ... 12 more
E/AndroidRuntime( 2145): Caused by: java.lang.ClassNotFoundException: android.preference.appwidget-provider
E/AndroidRuntime( 2145): at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:61)
E/AndroidRuntime( 2145): at java.lang.ClassLoader.loadClass(ClassLoader.java:501)
E/AndroidRuntime( 2145): at java.lang.ClassLoader.loadClass(ClassLoader.java:461)
E/AndroidRuntime( 2145): at android.preference.GenericInflater.createItem(GenericInflater.java:375)
E/AndroidRuntime( 2145): at android.preference.GenericInflater.onCreateItem(GenericInflater.java:417)
E/AndroidRuntime( 2145): at android.preference.GenericInflater.createItemFromTag(GenericInflater.java:428)
E/AndroidRuntime( 2145): ... 23 more
D/SomcTransmitPowerBroadcastReceiver( 895): Old PowerLevel: 3, current PowerLevel: 3
W/ActivityManager( 574): Force finishing activity com.android.settings/.SubSettings
So the error is Error inflating class appwidget-provider, but layouts and xml are the same as in the original file
Any idea would be much appreciated, this is driving me crazy.
Thanks in advance.

Any answer yet? Does anybody know something about this?

Tip.. Use Xperia Miro settings apk.. As A based like mine.
Sent from my LT26i using xda app-developers app

{
"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"
}
Sent from my LT26i using xda app-developers app

TrinityHaxxorX said:
View attachment 2310843
Sent from my LT26i using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply Trinity
That's what I was doing till know. However, I'd feel like to try implementing it in our settings.apk and all seems right except from the issue above. I've changed the layouts from Linear to Relative since it's said in StackOverflow that some layouts are not available with widgets, but no results yet.
PD: does wifi tethering work for you with those settings.apk? Mine not with .96

Solved!!!
It was only an identifier which was bad written. It supposed to be ..58 and I've written ..59
Soon I'll write a guide of how to
Please, mods close the thread.
Enviado desde mi LT26i usando Tapatalk

[APP][MOD] fb integrated messenger

facebook integrated messenger MOD (No separate messenger needed)
{
"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"
}
Optimized with Messenger enabled inside the app. No need for the separate app or any prompts to install it!
Need to uninstall any version of facebook & messenger before installing, and recommend deleting bloatware apps in /system/app or /system/priv-app:
facebook app installer
facebook app manager
85.0.0.0.18 patched
● Version modified to 999 so the app won't ask you to update
● Fixed crash when opening gallery from composer
● No duplicate emoji buttons in composer
● Bubble style delivery state icons like in Messenger
● Blue title bar to fit FB's design

Excellent! Just what's needed. My contacts have all changed to xxxx###@facebook.com.

When you fix the [email protected] in the Messenger, this App is more than great

Its asking to update.

ahvamaria said:
Its asking to update.
Click to expand...
Click to collapse
it's not....see above about removing fb system apps

Thanks
Working great with my mate 20 X
---------- Post added at 03:49 AM ---------- Previous post was at 03:46 AM ----------
Only problem
Facebook messenger cant reard my contacts name rt

Latest link?

mockneygeeza said:
Latest link?
Click to expand...
Click to collapse
link in OP still live so keep trying

Works great on a note 8, thank you

It doesn't work anymore, Facebook's new Reaction APIs Crashes the APP. any fix ?
AppStateLoggerExceptionHandler: java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.String com.facebook.feedback.reactions.api.FetchFeedbackReactionSettingsGraphQLModels$FetchFeedbackReactionSettingsQueryModel$FeedbackReactionSettingsModel$ReactionInfosModel$AnimationModel.a()' on a null object reference
05-04 18:36:20.812 16614 16649 E AppStateLoggerExceptionHandler: at com.facebook.feedback.reactions.ui.FeedbackReactionHelper.b(fb4a_ia_no_activity_rollout:100)
05-04 18:36:20.812 16614 16649 E AppStateLoggerExceptionHandler: at com.facebook.feedback.reactions.ui.FeedbackReactionHelper.c(fb4a_ia_no_activity_rollout:108)
05-04 18:36:20.812 16614 16649 E AppStateLoggerExceptionHandler: at com.facebook.feedback.reactions.ui.FeedbackReactionsDownloader$PersistanceRunnable.b(t_push:281)
05-04 18:36:20.812 16614 16649 E AppStateLoggerExceptionHandler: at com.facebook.feedback.reactions.ui.FeedbackReactionsDownloader$PersistanceRunnable.a(t_push:259)
05-04 18:36:20.812 16614 16649 E AppStateLoggerExceptionHandler: at com.facebook.feedback.reactions.ui.FeedbackReactionsDownloader$PersistanceRunnable.run(t_push:141)
05-04 18:36:20.820 16614 16649 E CatchMeIfYouCan: java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.String com.facebook.feedback.reactions.api.FetchFeedbackReactionSettingsGraphQLModels$FetchFeedbackReactionSettingsQueryModel$FeedbackReactionSettingsModel$ReactionInfosModel$AnimationModel.a()' on a null object reference
05-04 18:36:20.820 16614 16649 E CatchMeIfYouCan: at com.facebook.feedback.reactions.ui.FeedbackReactionHelper.b(fb4a_ia_no_activity_rollout:100)
05-04 18:36:20.820 16614 16649 E CatchMeIfYouCan: at com.facebook.feedback.reactions.ui.FeedbackReactionHelper.c(fb4a_ia_no_activity_rollout:108)
05-04 18:36:20.820 16614 16649 E CatchMeIfYouCan: at com.facebook.feedback.reactions.ui.FeedbackReactionsDownloader$PersistanceRunnable.b(t_push:281)
05-04 18:36:20.820 16614 16649 E CatchMeIfYouCan: at com.facebook.feedback.reactions.ui.FeedbackReactionsDownloader$PersistanceRunnable.a(t_push:259)
05-04 18:36:20.820 16614 16649 E CatchMeIfYouCan: at com.facebook.feedback.reactions.ui.FeedbackReactionsDownloader$PersistanceRunnable.run(t_push:141)
05-04 18:36:20.822 16614 16649 E AndroidRuntime: Process: com.facebook.katana, PID: 16614
05-04 18:36:20.822 16614 16649 E AndroidRuntime: java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.String com.facebook.feedback.reactions.api.FetchFeedbackReactionSettingsGraphQLModels$FetchFeedbackReactionSettingsQueryModel$FeedbackReactionSettingsModel$ReactionInfosModel$AnimationModel.a()' on a null object reference
05-04 18:36:20.822 16614 16649 E AndroidRuntime: at com.facebook.feedback.reactions.ui.FeedbackReactionHelper.b(fb4a_ia_no_activity_rollout:100)
05-04 18:36:20.822 16614 16649 E AndroidRuntime: at com.facebook.feedback.reactions.ui.FeedbackReactionHelper.c(fb4a_ia_no_activity_rollout:108)
05-04 18:36:20.822 16614 16649 E AndroidRuntime: at com.facebook.feedback.reactions.ui.FeedbackReactionsDownloader$PersistanceRunnable.b(t_push:281)
05-04 18:36:20.822 16614 16649 E AndroidRuntime: at com.facebook.feedback.reactions.ui.FeedbackReactionsDownloader$PersistanceRunnable.a(t_push:259)
05-04 18:36:20.822 16614 16649 E AndroidRuntime: at com.facebook.feedback.reactions.ui.FeedbackReactionsDownloader$PersistanceRunnable.run(t_push:141)

working fine for me on multiple devices on both nougat & oreo
ensure u removed the system apps mentioned in op

Unable to sign in after adding e-mail id & password rounding ..... rounding nothing happened .
Tested on Redmi Note 8 pro android 9 pie

Google Services on Fujitsu Arrows F-03L

Hi,
i'm trying to install few apps on Fujitsu Arrows F-03L (Android 8.1 Oreo). Most of them are requiring Google Services which is also not pre-installed on the phone. The most recent versions of Google Play Services are just crushing, so i've ended up with 14.5.82 (040400-222134188) build, and the older ones are saying that Play Services should be updated. Play Services require Services Framework, so i've installed 8.1.0-4487743 build.
The apps (Youtube) however are still failing to start. I can see the error in logs, but do not know how to fix it:
Code:
11-22 12:05:19.091 2391 2391 E AndroidRuntime: java.lang.RuntimeException: Unable to create application com.google.android.gms.common.app.GmsApplication: java.lang.SecurityException: addOnPermissionsChangeListener: Neither user 10103 nor current process has android.permission.OBSERVE_GRANT_REVOKE_PERMISSIONS.
11-22 12:05:19.091 2391 2391 E AndroidRuntime: at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5920)
11-22 12:05:19.091 2391 2391 E AndroidRuntime: at android.app.ActivityThread.-wrap1(Unknown Source:0)
11-22 12:05:19.091 2391 2391 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1699)
11-22 12:05:19.091 2391 2391 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
11-22 12:05:19.091 2391 2391 E AndroidRuntime: at android.os.Looper.loop(Looper.java:164)
11-22 12:05:19.091 2391 2391 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6680)
11-22 12:05:19.091 2391 2391 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
11-22 12:05:19.091 2391 2391 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:467)
11-22 12:05:19.091 2391 2391 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:821)
11-22 12:05:19.091 2391 2391 E AndroidRuntime: Caused by: java.lang.SecurityException: addOnPermissionsChangeListener: Neither user 10103 nor current process has android.permission.OBSERVE_GRANT_REVOKE_PERMISSIONS.
11-22 12:05:19.091 2391 2391 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:2013)
11-22 12:05:19.091 2391 2391 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:1959)
11-22 12:05:19.091 2391 2391 E AndroidRuntime: at android.content.pm.IPackageManager$Stub$Proxy.addOnPermissionsChangeListener(IPackageManager.java:6145)
11-22 12:05:19.091 2391 2391 E AndroidRuntime: at android.app.ApplicationPackageManager.addOnPermissionsChangeListener(ApplicationPackageManager.java:1442)
11-22 12:05:19.091 2391 2391 E AndroidRuntime: at qkz.a(:[email protected]@14.5.82 (040400-222134188):12)
11-22 12:05:19.091 2391 2391 E AndroidRuntime: at com.google.android.gms.common.app.GmsApplication.onCreate(:[email protected]@14.5.82 (040400-222134188):49)
11-22 12:05:19.091 2391 2391 E AndroidRuntime: at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1120)
11-22 12:05:19.091 2391 2391 E AndroidRuntime: at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5917)
I wonder if anyone has positive (or any) experience with these phones? E.g. rooting/custom builds/installing gapps... any help appreciated.

Hi,
I have the same phone as you. I feel like not a single soul is using it except me bruh. I only found this page about it, and even there is no answers... Do you still use it? The version of Play Services you installed is already kinda old and is asking for an update. Did you managed to find a new one that works? Maybe working Play Store? Or just anything that could help me with this phone, working gapps, root, way to have a cursor on the screen, bc the navigation it has doesn't allow me to even register in a lot of apps i need like Telegram or Whatsapp, maybe just working versions of that apps. Anything will help..

Hi mate, i've abandoned the idea of using this phone as an Android device - i couldn't make it work with Play Store/Gapps, and without them it's pretty useless - i can't even sync my contacts. It's a shame cause i love both the form-factor and build quality of this device.

Oh well, thanks for answering. Good to know you're still on that forum. I still do not leave hopes to switch to it as the main device, tho. Fortunately, I don’t need G-Services so much (besides, they may be banned from us so soon), and with the rest of the necessary applications, I got used to working and configuring them through emulation of clicks through adb. With all the cons and inconveniences, I like it, it has everything i need for now, like messengers, browser and some specific android apps. I bought it for a digital detox. But still, if i wasn't so stubborn in my desire to use it, i wouldn't even try after a couple of unsuccessful attempts. There must be a line between stripped down functionality and simple disrespect and limitation of important functions. It's very sad that they ruined such a great smartphone (and the form factor in general)

[EOL][11.0][OFFICIAL] LineageOS 18.1 for Oneplus 5 & 5T

{
"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"
}
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
HOW TO INSTALL LINEAGEOS:
- Official instructions
- In short: sideload in Lineage recovery (suggested) / flash in TWRP
HOW TO UPDATE LINEAGEOS:
- Download update from Updater app
- Install update
DOWNLOADS:
LineageOS 18.1: Official Oneplus 5, Official Oneplus 5T
Google Apps: MindTheGapps
Recovery: Suggested: Lineage recovery for Oneplus 5, Oneplus 5T | Alternative: TWRP
DEVELOPER RESOURCES
LineageOS source code:
- https://github.com/LineageOS
Device tree:
- android_device_oneplus_cheeseburger
- android_device_oneplus_dumpling
- android_device_oneplus_msm8998-common
Kernel:
- android_kernel_oneplus_msm8998
Android version: Android 11
Kernel version: Linux 4.4.y
Required firmware: OxygenOS 10.0.1 (shipped with ROM, no need to install manually)
Telegram group: https://t.me/los_op5

Issues:
- Safetynet does not pass. Magisk hide & MagiskHide Props Config help here.
- Wireless display does not work
Notes:
- Relocking bootloader https://forum.xda-developers.com/t/...s-18-1-for-oneplus-5-5t.4173997/post-84770085 (thanks for @Eric_Lev ) (not suggested though)

Really appreciate your efforts dude
Will try this out

Would you consider removing the lineage recovery from future builds?

Any idea about oneplus 5t

Added to the OnePlus 5 Index Thread here.

T1mb3 said:
ROM OS Version: 2.3.x Gingerbread
Click to expand...
Click to collapse
You most probably forgot to update this entry, just wanted to let you know. Thanks for this ROM Really appreciated!

JulianXhokaxhiu said:
You most probably forgot to update this entry, just wanted to let you know. Thanks for this ROM Really appreciated!
Click to expand...
Click to collapse
There actually is no option higher than Android 10 yet

JulianXhokaxhiu said:
You most probably forgot to update this entry, just wanted to let you know. Thanks for this ROM Really appreciated!
Click to expand...
Click to collapse
T1mb3 said:
There actually is no option higher than Android 10 yet
Click to expand...
Click to collapse
As you can read in Big Changes To XDA Forums are Coming Soon with the transition to Xenforo all DevDB threads will eventually be reverted to "normal" threads. For this reason, it was decided not to add the option "A 11" anymore.

T1mb3 said:
There actually is no option higher than Android 10 yet
Click to expand...
Click to collapse
Having said this...
Oswald Boelcke said:
As you can read in Big Changes To XDA Forums are Coming Soon with the transition to Xenforo all DevDB threads will eventually be reverted to "normal" threads. For this reason, it was decided not to add the option "A 11" anymore.
Click to expand...
Click to collapse
...you can always edit the first post using the edit button at the end of the post (instead of using the edit project option for DevDB threads) and manually change it to Android 11.

Is it rooted?
Does this pass SafetyNet?

sergio_sant said:
Is it rooted?
Does this pass SafetyNet?
Click to expand...
Click to collapse
This is not rooted by default. Latest Magisk works for that purpose.
This does not pass safetynet. I will have to look for a solution. Other ROMs use kernel-side patches for safetynet and those are not allowed in LineageOS.

UPDATE:
* Sync LineageOS sources
* SELinux is now enforcing
* TWRP does not get overwritten by Lineage recovery for now. This may change when LineageOS makes their decision on the topic.
* More detailed changelog
* Download

T1mb3 said:
UPDATE:
* Sync LineageOS sources
* SELinux is now enforcing
* TWRP does not get overwritten by Lineage recovery for now. This may change when LineageOS makes their decision on the topic.
* More detailed changelog
* Download
Click to expand...
Click to collapse
Hi，bro. I am trying to build los18 for oneplus5t, should I use pick this commit https://review.lineageos.org/c/LineageOS/android_packages_apps_Settings/+/287931 as you said to avoid that TRWP does get overwritten by Lineage recovery， is it right？

kpzhao said:
Hi，bro. I am trying to build los18 for oneplus5t, should I use pick this commit https://review.lineageos.org/c/LineageOS/android_packages_apps_Settings/+/287931 as you said to avoid that TRWP does get overwritten by Lineage recovery， is it right？
Click to expand...
Click to collapse
I did it this way: https://github.com/LineageOS-cheese...mmit/65b18d38368955a5a9cac58d09bf5c867624fb53

Great work, thanks for this rom. I LOVE IT
this is the 1st custom rom i install and the instructions were smooth. I did upgrade because oneplus stopped supporting OP5 and just sent a message in the community app giving fake excuses for the delays.
I noticed this bug
some apps that has the option to login with fingerprint doesn't work properly ( i.e. TD Canada Trust, Manulife)
as soon as the phone tries to communicate with the fingerprint reader, it freezes. 1st login in Manulife app, it asks if you want to allow or deny access to fingerprint reader, if you deny, it will let you login with the password if you remember it. if you accept, it hangs.
In TD Canada Trust app, first time you login with your password, it gives you a popup asking you if you want to enable fingerprint login, and you cant press anything other than closing the app.

T1mb3 said:
UPDATE:
* Sync LineageOS sources
* SELinux is now enforcing
* TWRP does not get overwritten by Lineage recovery for now. This may change when LineageOS makes their decision on the topic.
* More detailed changelog
* Download
Click to expand...
Click to collapse
Can't call through VoLte, Volte cannot call!
Cannot tap to wake(settings-Display-Advanced-Tap to wake)

Hello，I build los18 for 5t successfully as your building guild . However it is no sim card and I get this log
10-12 10:12:46.522 21233 21233 E PhoneInterfaceManager: [PhoneIntfMgr] getIccId: No UICC
10-12 10:12:46.621 21233 21233 E AndroidRuntime: FATAL EXCEPTION: main
10-12 10:12:46.621 21233 21233 E AndroidRuntime: Process: com.android.phone, PID: 21233
10-12 10:12:46.621 21233 21233 E AndroidRuntime: java.lang.IllegalArgumentException: value of system property 'gsm.version.baseband' is longer than 91 characters: MPSS.AT.2.0.c4.7-00070-8998_GEN_PACK-2.271073.1.277412.1,MPSS.AT.2.0.c4.7-00070-8998_GEN_PACK-2.271073.1.277412.1
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at android.os.SystemProperties.set(SystemProperties.java:236)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at android.sysprop.TelephonyProperties.baseband_version(TelephonyProperties.java:140)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at android.telephony.TelephonyManager.setBasebandVersionForPhone(TelephonyManager.java:10107)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at com.android.internal.telephony.GsmCdmaPhone.handleMessage(GsmCdmaPhone.java:2850)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at android.os.Looper.loop(Looper.java:223)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7656)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
10-12 10:12:46.656 764 3655 E IPCThreadState: attemptIncStrongHandle(77): Not supported
10-12 10:12:46.656 764 3545 E IPCThreadState: attemptIncStrongHandle(82): Not supported
10-12 10:12:46.656 764 3830 E IPCThreadState: attemptIncStrongHandle(79): Not supported
10-12 10:12:46.657 764 3545 E IPCThreadState: attemptIncStrongHandle(78): Not supported
10-12 10:12:46.784 21323 21323 E CarrierIdProvider: read carrier list from ota pb failure: java.io.FileNotFoundException: /data/misc/carrierid/carrier_list.pb: open failed: ENOENT (No such file or directory)
10-12 10:12:47.593 0 0 E [20201012_10:12:47.591117]@3 synaptics,s3320: all finger up
Could you give me some suggestion?

kpzhao said:
Hello，I build los18 for 5t successfully as your building guild . However it is no sim card and I get this log
10-12 10:12:46.522 21233 21233 E PhoneInterfaceManager: [PhoneIntfMgr] getIccId: No UICC
10-12 10:12:46.621 21233 21233 E AndroidRuntime: FATAL EXCEPTION: main
10-12 10:12:46.621 21233 21233 E AndroidRuntime: Process: com.android.phone, PID: 21233
10-12 10:12:46.621 21233 21233 E AndroidRuntime: java.lang.IllegalArgumentException: value of system property 'gsm.version.baseband' is longer than 91 characters: MPSS.AT.2.0.c4.7-00070-8998_GEN_PACK-2.271073.1.277412.1,MPSS.AT.2.0.c4.7-00070-8998_GEN_PACK-2.271073.1.277412.1
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at android.os.SystemProperties.set(SystemProperties.java:236)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at android.sysprop.TelephonyProperties.baseband_version(TelephonyProperties.java:140)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at android.telephony.TelephonyManager.setBasebandVersionForPhone(TelephonyManager.java:10107)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at com.android.internal.telephony.GsmCdmaPhone.handleMessage(GsmCdmaPhone.java:2850)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at android.os.Looper.loop(Looper.java:223)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7656)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
10-12 10:12:46.656 764 3655 E IPCThreadState: attemptIncStrongHandle(77): Not supported
10-12 10:12:46.656 764 3545 E IPCThreadState: attemptIncStrongHandle(82): Not supported
10-12 10:12:46.656 764 3830 E IPCThreadState: attemptIncStrongHandle(79): Not supported
10-12 10:12:46.657 764 3545 E IPCThreadState: attemptIncStrongHandle(78): Not supported
10-12 10:12:46.784 21323 21323 E CarrierIdProvider: read carrier list from ota pb failure: java.io.FileNotFoundException: /data/misc/carrierid/carrier_list.pb: open failed: ENOENT (No such file or directory)
10-12 10:12:47.593 0 0 E [20201012_10:12:47.591117]@3 synaptics,s3320: all finger up
Could you give me some suggestion?
Click to expand...
Click to collapse
Hi,
Pick this commit: https://github.com/LineageOS-cheese...mmit/def355758a279ff756f2f6f580db161aa0fb805b

T1mb3 said:
Hi,
Pick this commit: https://github.com/LineageOS-cheese...mmit/def355758a279ff756f2f6f580db161aa0fb805b
Click to expand...
Click to collapse
You are a good man, sir. I am very appreciated for your help.

Question Screen lock setup crashing (Unlocked bootloader + rooted)

I've unlocked the bootloader and rooted my OP11 (CPH2449GDRP), and when I try to set up any screen lock mechanism, it doesn't save it, but rather stops at the repeated input step and does nothing.
In ADB logcat, I can see that there's a crash happening when trying to setup any screen lock mechanism.
Spoiler: ADB Logcat
Code:
--------- beginning of crash
02-15 18:06:00.408 5591 19164 E AndroidRuntime: FATAL EXCEPTION: SET2T7cached
02-15 18:06:00.408 5591 19164 E AndroidRuntime: Process: com.android.settings, PID: 5591
02-15 18:06:00.408 5591 19164 E AndroidRuntime: java.lang.RuntimeException: An error occurred while executing doInBackground()
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at android.os.AsyncTask$4.done(AsyncTask.java:415)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:381)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at java.util.concurrent.FutureTask.setException(FutureTask.java:250)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at java.util.concurrent.FutureTask.run(FutureTask.java:269)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1137)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:637)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at java.lang.Thread.run(Thread.java:1012)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: Caused by: java.lang.IllegalStateException: Fail to enroll user password when creating SP for user 0
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at android.os.Parcel.createExceptionOrNull(Parcel.java:3048)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at android.os.Parcel.createException(Parcel.java:3024)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:3007)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:2949)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at com.android.internal.widget.ILockSettings$Stub$Proxy.setLockCredential(ILockSettings.java:1225)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at com.android.internal.widget.LockPatternUtils.setLockCredential(LockPatternUtils.java:727)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at com.oplus.settings.feature.password.SaveLockPatternAndFinishWorker.F1(SaveLockPatternAndFinishWorker.java:9)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at com.android.settings.password.SaveChosenLockWorkerBase$c.a(SaveChosenLockWorkerBase.java:2)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at com.android.settings.password.SaveChosenLockWorkerBase$c.doInBackground(SaveChosenLockWorkerBase.java:1)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at android.os.AsyncTask$3.call(AsyncTask.java:394)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at java.util.concurrent.FutureTask.run(FutureTask.java:264)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: ... 3 more
02-15 18:06:00.408 5591 19164 E AndroidRuntime: Caused by: android.os.RemoteException: Remote stack trace:
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at com.android.server.locksettings.SyntheticPasswordManager.createPasswordBasedSyntheticPassword(SyntheticPasswordManager.java:841)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at com.android.server.locksettings.LockSettingsService.initializeSyntheticPasswordLocked(LockSettingsService.java:2961)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at com.android.server.locksettings.LockSettingsService.setLockCredentialInternal(LockSettingsService.java:1910)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at com.android.server.locksettings.LockSettingsService.setLockCredential(LockSettingsService.java:1821)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at com.android.internal.widget.ILockSettings$Stub.onTransact(ILockSettings.java:580)
02-15 18:06:00.408 5591 19164 E AndroidRuntime:
Any idea how to fix this issue? I've recently updated from A.06 to A.07 firmware (by patching init_boot.img into inactive slot) but issue still persists. Thanks!

I have the exact same issue, it does not matter if I pick pin or pattern.

CoinsClassic said:
I've unlocked the bootloader and rooted my OP11 (CPH2449GDRP), and when I try to set up any screen lock mechanism, it doesn't save it, but rather stops at the repeated input step and does nothing.
In ADB logcat, I can see that there's a crash happening when trying to setup any screen lock mechanism.
Spoiler: ADB Logcat
Code:
--------- beginning of crash
02-15 18:06:00.408 5591 19164 E AndroidRuntime: FATAL EXCEPTION: SET2T7cached
02-15 18:06:00.408 5591 19164 E AndroidRuntime: Process: com.android.settings, PID: 5591
02-15 18:06:00.408 5591 19164 E AndroidRuntime: java.lang.RuntimeException: An error occurred while executing doInBackground()
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at android.os.AsyncTask$4.done(AsyncTask.java:415)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:381)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at java.util.concurrent.FutureTask.setException(FutureTask.java:250)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at java.util.concurrent.FutureTask.run(FutureTask.java:269)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1137)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:637)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at java.lang.Thread.run(Thread.java:1012)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: Caused by: java.lang.IllegalStateException: Fail to enroll user password when creating SP for user 0
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at android.os.Parcel.createExceptionOrNull(Parcel.java:3048)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at android.os.Parcel.createException(Parcel.java:3024)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:3007)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:2949)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at com.android.internal.widget.ILockSettings$Stub$Proxy.setLockCredential(ILockSettings.java:1225)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at com.android.internal.widget.LockPatternUtils.setLockCredential(LockPatternUtils.java:727)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at com.oplus.settings.feature.password.SaveLockPatternAndFinishWorker.F1(SaveLockPatternAndFinishWorker.java:9)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at com.android.settings.password.SaveChosenLockWorkerBase$c.a(SaveChosenLockWorkerBase.java:2)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at com.android.settings.password.SaveChosenLockWorkerBase$c.doInBackground(SaveChosenLockWorkerBase.java:1)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at android.os.AsyncTask$3.call(AsyncTask.java:394)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at java.util.concurrent.FutureTask.run(FutureTask.java:264)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: ... 3 more
02-15 18:06:00.408 5591 19164 E AndroidRuntime: Caused by: android.os.RemoteException: Remote stack trace:
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at com.android.server.locksettings.SyntheticPasswordManager.createPasswordBasedSyntheticPassword(SyntheticPasswordManager.java:841)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at com.android.server.locksettings.LockSettingsService.initializeSyntheticPasswordLocked(LockSettingsService.java:2961)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at com.android.server.locksettings.LockSettingsService.setLockCredentialInternal(LockSettingsService.java:1910)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at com.android.server.locksettings.LockSettingsService.setLockCredential(LockSettingsService.java:1821)
02-15 18:06:00.408 5591 19164 E AndroidRuntime: at com.android.internal.widget.ILockSettings$Stub.onTransact(ILockSettings.java:580)
02-15 18:06:00.408 5591 19164 E AndroidRuntime:
Any idea how to fix this issue? I've recently updated from A.06 to A.07 firmware (by patching init_boot.img into inactive slot) but issue still persists. Thanks!
Click to expand...
Click to collapse
rootet with magisk or magisk delta ? (stock , beta or canary )

ChrisFeiveel84 said:
rootet with magisk or magisk delta ? (stock , beta or canary )
Click to expand...
Click to collapse
Latest Canary of official Magisk

CoinsClassic said:
Latest Canary of official Magisk
Click to expand...
Click to collapse
does the problem only occur with root or also without root?

ChrisFeiveel84 said:
does the problem only occur with root or also without root?
Click to expand...
Click to collapse
It could have also appeared without bl unlock and without root, but I instantly unlocked the bootloader, and then I noticed, that screen lock setup isnt working. So even before rooting.

CoinsClassic said:
It could have also appeared without bl unlock and without root, but I instantly unlocked the bootloader, and then I noticed, that screen lock setup isnt working. So even before rooting.
Click to expand...
Click to collapse
Since I don't have my op11 yet (I'm not toying with the idea of unlocking the bootloader either), the best option is to ask the telegram group about something like this, as there are more people there who deal with the op11 and co
OnePlus Chat [EN/ZH]
Discussion Group / 讨论群: https://t.me/OnePlusChat System Update / 系统更新: https://t.me/OnePlusOTA Resources Center / 资源中心: http://t.me/OnePlusRes
t.me

ChrisFeiveel84 said:
does the problem only occur with root or also without
Click to expand...
Click to collapse
CoinsClassic said:
It could have also appeared without bl unlock and without root, but I instantly unlocked the bootloader, and then I noticed, that screen lock setup isnt working. So even before rooting.
Click to expand...
Click to collapse
Mine worked before rooting. I set my fingerprint then unlocked the boot loader. Now it doesnt work.

I just reset my phone and it still does not work with the bootloader unlocked. I am actually sending the phone back and buying a oneplus 10 pro. After using the phone for the day I cannot stand the usb 2.0 tranfer speeds. I tried using wifi transfers but it is still not as fast as I would like. I make a lot of youtube videos so most times I am transfering 16gb - 30gb files and over usb it was taking forever. So, hopefully by friday I will have a new phone. Its sad, I figured going from a oneplus 9 pro it would have been a huge upgrade. I do not know why they send a type c to usb A 3.0 adapter with the phone if it is only capable of 2.0 speeds.

This happened to me right after unlocking bootloader. GOOD NEWS: I fixed it by locking and re-unlocking the bootloader. I then immediately set my password during setup and it worked fine. Face unlock and fingerprint also work perfect.
Edit: someone also said that it may not be a set thing, so maybe if that doesnt work try re-locking and unlocking again.
I know that this is a pain, but it should be a one time thing. I have not rooted yet but will do so soon.

JPower123 said:
This happened to me right after unlocking bootloader. GOOD NEWS: I fixed it by locking and re-unlocking the bootloader. I then immediately set my password during setup and it worked fine. Face unlock and fingerprint also work perfect.
Edit: someone also said that it may not be a set thing, so maybe if that doesnt work try re-locking and unlocking again.
I know that this is a pain, but it should be a one time thing. I have not rooted yet but will do so soon.
Click to expand...
Click to collapse
So I tried to relock the bootloader and the phone is stuck in a bootloop. It says it's locked but adp cannot detect it. I tried this after I made my last comment.

cavalier3400z said:
So I tried to relock the bootloader and the phone is stuck in a bootloop. It says it's locked but adp cannot detect it. I tried this after I made my last comment.
Click to expand...
Click to collapse
Are you using fastboot commands? I don't think adb Is supposed to detect it in bootloader. Also have you flashed any roms?

I have same issue on EU OP11 with firmware CPH2449_11_A.07.
Unlocked bootloader - fine.
Booted into OOS but cant set a lock password/code, just sits there with no error. I can skip that and get into the OS OK.
I tried a factory reset in OOS, no change.
I then tried a format in recovery, no change.
Relocked the bootloader and now I can set a lock password/code.
At no point had I flashed anything for root access. Very unusual.

Yep. Same issue here. Europe OP11 firmware CPH2449_11_A.07. Cannot set the lock screen password/pin/pattern I did skip it. Cannot set fingerprint or anything because of that.

cavalier3400z said:
So I tried to relock the bootloader and the phone is stuck in a bootloop. It says it's locked but adp cannot detect it. I tried this after I made my last comment.
Click to expand...
Click to collapse
Are you on full unrooted stock before locking? Do not know how oppo works, but if you were not on stock, I think you ahve to somehow recover thru edl, or maybe ur device is paper weight (If you were not on 100% stock)

gahffi said:
Yep. Same issue here. Europe OP11 firmware CPH2449_11_A.07. Cannot set the lock screen password/pin/pattern I did skip it. Cannot set fingerprint or anything because of that.
Click to expand...
Click to collapse
grim00 said:
I have same issue on EU OP11 with firmware CPH2449_11_A.07.
Unlocked bootloader - fine.
Booted into OOS but cant set a lock password/code, just sits there with no error. I can skip that and get into the OS OK.
I tried a factory reset in OOS, no change.
I then tried a format in recovery, no change.
Relocked the bootloader and now I can set a lock password/code.
At no point had I flashed anything for root access. Very unusual.
Click to expand...
Click to collapse
But the massacre with this model:/
Did you do something else or just unlocked a bootloader?

Arealhooman said:
Are you on full unrooted stock before locking? Do not know how oppo works, but if you were not on stock, I think you ahve to somehow recover thru edl, or maybe ur device is paper weight (If you were not on 100% stock)
Click to expand...
Click to collapse
How can they do anything at EDL, since there is no msmdownload for OP11?
regards
f.

qriozum said:
But the massacre with this model:/
Did you do something else or just unlocked a bootloader?
Click to expand...
Click to collapse
Problem started with just the unlocked bootloader. Not even rooted yet.

gahffi said:
Problem started with just the unlocked bootloader. Not even rooted yet.
Click to expand...
Click to collapse
Here in several threads there were so many attempts to restore OP11 that I already mix it all.
I am not sure if the accident @ChrisFeiveel84 has not shared the video as he removes the "cow" partitions and performs something else.
Maybe it will help?
In the thread with the conversion of the Chinese version OP11 at 2447/2449 there was also a problem with the pin/screen lock - but they probably solved it.

I can confirm:
Relock and Unlock bootloader a few times (3 cycles in my case) eventually allows lock screen security to be set with an unlocked bootloader.