When I use a Short Code as my Recipient for messaging, the com.android.phone crashes. Does anyone know why this happens, and what I can do to fix it? It happens on all the KitKat ROMs I've tried for LG G2.
Scenario:
I open messaging. It also happens with Hangouts, or any other SMS app.
I use my credit card Short Code as the Recipient: 96411
I send a message asking for Balance Info: Bal 1234 (Any message sent to the short code does the same)
com.android.phone crashes and message does not get sent.
It also happens when sending to any other short code. ie: ATT Balance info, etc... *46# or similar...
It seems to me that it's the phone that is crashing, and not messaging. Messaging stays running, but does not send message.
{
"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"
}
Thanks in advance!
SuperSport
I am having this same issue on a completely different phone. I just installed CM11 on my SGS2 on Sprint, and outbound shortcode replies, using either Hangouts or the Messaging app crashes com.android.phone. I've been searching around the web and still haven't found a fix. I believe there is another post someone put up on the Cyanogenmod forum/support area about this happening, but it doesn't have any replies.
Perhaps the issue is too new to have an answer. Hopefully someone else can shed some light on why this is occurring and if we can do anything to fix it.
MustWarnothers said:
I am having this same issue on a completely different phone. I just installed CM11 on my SGS2 on Sprint, and outbound shortcode replies, using either Hangouts or the Messaging app crashes com.android.phone. I've been searching around the web and still haven't found a fix. I believe there is another post someone put up on the Cyanogenmod forum/support area about this happening, but it doesn't have any replies.
Perhaps the issue is too new to have an answer. Hopefully someone else can shed some light on why this is occurring and if we can do anything to fix it.
Click to expand...
Click to collapse
Thanks for your reply. It confirms it is likely KitKat related. I wonder if it happens on Stock KitKat ROMs too. If not, maybe there will be a fix soon. A file missing or something.
Having the same problem on kitkat 4.4.1 on my samsung galaxy s plus. Appears to be a kitkat related problem.
Edit--
This could be a problem only in cyanogenmod.(and cyanogenmod based rom. Do not know for sure)
E/AndroidRuntime( 2127): FATAL EXCEPTION: main
E/AndroidRuntime( 2127): Process: com.android.phone, PID: 2127
E/AndroidRuntime( 2127): java.lang.RuntimeException: Error receiving broadcast Intent { act=android.intent.action.NEW_OUTGOING_SMS flg=0x10 (has extras)
E/AndroidRuntime( 2127): Caused by: java.lang.SecurityException: Calling uid 1001 gave packagefamily.mobitel.mymobitel which is owned by uid 10106
E/AndroidRuntime( 2127): at com.android.internal.telephony.SmsUsageMonitor.checkCallerIsSystemOrSameApp(SmsUsageMonitor.java:596)
E/AndroidRuntime( 2127): at com.android.internal.telephony.SmsUsageMonitor.getPremiumSmsPermission(SmsUsageMonitor.java:549)
E/AndroidRuntime( 2127): at com.android.internal.telephony.SMSDispatcher.checkDestination(SMSDispatcher.java:824)
E/AndroidRuntime( 2127): at com.android.internal.telephony.SMSDispatcher.sendRawPdu(SMSDispatcher.java:765)
E/AndroidRuntime( 2127): at com.android.internal.telephony.gsm.GsmSMSDispatcher.sendText(GsmSMSDispatcher.java:177)
The Voicemail Notification, SMS, and com.android.phone
I have run into an issue involving com.android.phone on my Samsung Exhilarate. Based on what I've been able to determine, it looks like there is an issue with Cyanogen 11. I don't know if this affects all phones, but it DOES affect mine.
Here's the background:
1) Replaced CWM with TWRP Recovery
2) Installed Cyanogen 11 on my phone (because the one I'd been using forever (cm7) was starting to act up - figured it was time to reflash
3) Installed gApps for Cyanogen 11
4) Installed SuperUser
Started using the phone, and noticed my Voicemail Icon in the notification bar was up. Checked VM, nothing. WTF? Also, got a blank text from, well, myself, as I was checking my VM.
Noted the following: Every time I check VM, I get a blank text from my self, and the VM Icon refuses to go away unless I kill com.android.phone. Doesn't appear to really affect anything else.
So - who can help? I'm up for anything, including hacking open any of the com. files if need be (so long as I don't brick).
V/R
Black-Wolf
Same issue
Hi all
I'm also facing the same issue with my Cynogenmod11 (kitkat 4.4.1) on my Samsung i9082 phone.
message crashes while sending it to any short codes. it recovers only by rebooting.
Does anyone have some fix for this ? Any temporary workarounds ?
Regards
Jatin.
Same issue in CM 10.2 Jellybean
Hello there. I'm facing the same problem with my Galaxy Ace 2, using CM 10.2 ROM, but in my case, it doesn't matter how long the message is, even if it's a long one, I still get the error, sometimes the phone even freeze and I need to reboot the device, but this doesn't happens everytime. The first time I fixed it by reflashing the ROM again, and it seems to fix the issue for quite some time, but then it starts again so here I am. Anyone has an idea why this happens? I really like CM rom and I don't wanna go back to the stock one.
Related
I've been having a really tough time downloading apps today. I switched back from another phone I was using. the apps hang after downloading but wont install. These are all apps I already have but need to update.
I've searched and searched and so far have tried the following:
1) cancel and restart
2) reboot phone
3) go to apps and clear the download manager
4) log into Google talk & sign out sign in etc
5) force close market
It's driving me crazy. It'll show it's downloading in the notification bar and then abruptly stop..then it'll show in market that it's installing but it's not really doing anything.
I'd really like some help with this please. I'm running stock rooted ji6.
Sent from my SGH-T959 using XDA App
Sorry forgot to add screen shot
{
"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 SGH-T959 using XDA App
Anyone??
Sent from my SGH-T959 using XDA App
Go to Settings->Applications->Manage applications
Filter by All, locate Market app in the list, click on it and Clear data
I had a similar issue, buy instead of "downloading" it said "installing". I installed the new market that just came out and everything is all set now.
i can't anything to download...it started this morning but worked fine last night. i was on eugenes ginger clone rom and the market just stopped downloading things...it says starting download, then the bar disappears, but the notification bar still says its downloading...then once its done in the status bar..........nothing. the app isn't installed and it doesnt say download complete...just........nothing.
anyone else? i even tried going back to nero beta 3. i've literally tried everything to get it to download. name it and i've tried it...
Did you try to odin it back to stock, then flash a new rom?
bstromberg said:
i can't anything to download...it started this morning but worked fine last night. i was on eugenes ginger clone rom and the market just stopped downloading things...it says starting download, then the bar disappears, but the notification bar still says its downloading...then once its done in the status bar..........nothing. the app isn't installed and it doesnt say download complete...just........nothing.
anyone else? i even tried going back to nero beta 3. i've literally tried everything to get it to download. name it and i've tried it...
Click to expand...
Click to collapse
That's how mine was behaving. I went to apps and market and did "uninstall updates" and it lagged and force closed a couple times and it eventually worked. This phone always lags when installing an app. My Motorola defy never had issues with market.
Sent from my SGH-T959 using XDA App
i had the issue. I basically had to stop all apps from updating, and do them one by one and even then it was a pain. You may need to just try a few times. Everytime I hit update all, thats when I have the issue. I just do it the old school way one by one, and keep trying if it dont work. Lol
Odd, but I had this issue yesterday when trying another new rom.
What I did was immediately after accepting the permissions and being brought back to the My Apps/Download screen where it shows all the apps, was to IMMEDIATELY click right back on the app....
for some unknown reason this was the only way I was able to update about 5 apps yesterday... never had an issue before.
Clearing the market data is also a popular fix as previously mentioned.
If someone can try my method I would be curious to hear feedback... I was amazed this worked its so simple/odd.
I recently took a screenshot that revealed another background window behind a warning message window that says "Hello world, PM EasyView!"
Is this some kind of malware? I tried scanning my phone with Lookout Security and it did not detect anything suspicious.
It all began when all of a sudden my stock 2.2.2 Defy's Task Manager kept showing popup messages telling me that my Hotmail app is running for too long and is consuming memory. This never happened before, ie. Task Manager app showing warning messages about apps running for too long. I suspect a malware infestation. Please advise.
{
"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"
}
If you are scared that you are infected by malware the only "safe" thing to do is a full data wipe.
You dont have clockworkmod installed do you? Would be helpfull to have a full copy of the system to analyze it. I think clockworkmod would be a perfekt method to get a copy of the whole system.
sorry i don't know how to solve this. maybe it's time for you to change to some other ROMs...
iRegistry said:
If you are scared that you are infected by malware the only "safe" thing to do is a full data wipe.
You dont have clockworkmod installed do you? Would be helpfull to have a full copy of the system to analyze it. I think clockworkmod would be a perfekt method to get a copy of the whole system.
Click to expand...
Click to collapse
Well not exactly scared but I was just wondering about the origin of that "Hello world" message. "PMEasyView"? I wasn't able to find any app or developer by that name among the apps installed on my phone. Just was wondering if anyone here knew thats all. I rooted my phone using SuperOneClick, does it install Clockworkmod too? Or do I have to do it separately?
tomarsenal said:
sorry i don't know how to solve this. maybe it's time for you to change to some other ROMs...
Click to expand...
Click to collapse
I did install CM 7.1(2.3.7) but I didn't quite like it..I mean don't get me wrong..CM 7.1 is awesome but the ADW launcher kept crashing on me, something was eating up the battery way to fast and this is weird but I found that the sound quality(headphone and speaker) had actually deteriorated..maybe I didn't get some settings right but anyways I decided to roll back to the Motorola stock 2.2.2 froyo JRDNEM_U3_3.4.3-36-1.7 and wait until CM9 was out.
Thanks for the replies guys..really appreciate you taking the time.
Anachronizer said:
CM 7.1 is awesome but the ADW launcher kept crashing on me, something was eating up the battery way to fast and this is weird but I found that the sound quality(headphone and speaker) had actually deteriorated..
Click to expand...
Click to collapse
If adw doesn't work for you, you can download another one from the market. I use go launcher and it works without any problems and damn fast. You should give it a try.
Sent from my MB525 using Tapatalk
Well it's typical behavior of mallware - I dont have information, that stock task manager will inform you, that some process is running more than x minutes ... try wipe to factory settings and you'll be sure.
Rooting doesn't install Clockworkmod. You only get superuser after rooting. Install 2nd-init and you get Clockworkmod.
You should start using Droidwall and AVG antivirus pro. Try limit the data freedom running in the background.
Thanks for the replies guys. I think I'll wait for CM9. I do have Droidwall installed and I've scanned my phone thoroughly with Lookout Security but nothing was detected. Is it possible that the firmware posted here, the 2.2.2 India one is somehow infected?
http://forum.xda-developers.com/showthread.php?t=1093352
I took another screenshot of the supposed malware today, this time without the task manager message. I was able to dismiss the task manager message by pressing the search key somehow.
I have seen exactly that same message today. I thought I have been fairly careful about Malware. However, there was an update that was installed from marketplace today.
I wonder if it is possible to look at an update history.
sailfast said:
I have seen exactly that same message today. I thought I have been fairly careful about Malware. However, there was an update that was installed from marketplace today.
I wonder if it is possible to look at an update history.
Click to expand...
Click to collapse
Is the message window in your case appearing under the exact same circumstances as mine? Which ROM are you using? And also if its possible could you do an inventory of the all the apps installed on your phone, then perhaps we can pinpoint the source. Thanks for the reply.
Hi... I am using 4.4.2 stock ROM, rooted.
The 4G LTE symbol is always on.
None of the following attempts removes it -
1. Connecting to Wifi
2. Removing Caller Id
3. Stopping all Verizon background apps
4. Stopping mobile data
5. Switching Wanam Xposed "Persistent data type icon" under notifications either on or off
It always remains grayed out but up there when I am connected to Wifi, like the picture below.
Is it also like this for you if you are using 4.4.2? Any more ideas that I can try to remove it?
{
"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"
}
Edit: I found a solution. See post #5 in this thread.
hirak99 said:
Hi... I am using 4.4.2 stock ROM, rooted.
The 4G LTE symbol is always on.
None of the following attempts removes it -
1. Connecting to Wifi
2. Removing Caller Id
3. Stopping all Verizon background apps
4. Stopping mobile data
5. Switching Wanam Xposed "Persistent data type icon" under notifications either on or off
It always remains grayed out but up there when I am connected to Wifi, like the picture below.
Is it also like this for you if you are using 4.4.2? Any more ideas that I can try to remove it?
Click to expand...
Click to collapse
I don't think it ever goes away on stock 4.4.2, maybe not even on 4.3, I've heard others complain about it as well. I think the only way to get rid of it is to install a custom rom. I am running JellyBeans build 2, it's pretty close to stock, and it got rid of that, it's only on when mobile data is on, not when wifi is on. Hope this helps.
newuser134 said:
I don't think it ever goes away on stock 4.4.2, maybe not even on 4.3, I've heard others complain about it as well. I think the only way to get rid of it is to install a custom rom. I am running JellyBeans build 2, it's pretty close to stock, and it got rid of that, it's only on when mobile data is on, not when wifi is on. Hope this helps.
Click to expand...
Click to collapse
Yes, that helps! Thanks. Weird, I didn't find many threads on this topic - only a few where the issue was resolved apparently by removing Caller ID app. It's good to know I am not alone.
I might try the JellyBeans 2... I have never changed to non Stock ROM's before, can such a change preserve all my apps and settings?
hirak99 said:
Yes, that helps! Thanks. Weird, I didn't find many threads on this topic - only a few where the issue was resolved apparently by removing Caller ID app. It's good to know I am not alone.
I might try the JellyBeans 2... I have never changed to non Stock ROM's before, can such a change preserve all my apps and settings?
Click to expand...
Click to collapse
I think if you make a safe strap backup you can always come back to it and restore if something makes you not like it.
As for keeping your apps and data, I think whatever is on your internal/external storage stays untouched, but as for the apps, JellyBeans is different enough from stock, although it looks the same, that you may have to do a data partition/cache wipe to get it to run stable. What I always do is make a note (no pun intended ) of all my downloaded apps and changes, or maybe back them up with Titanium Backup to the external storage, then just re-download from Play Store or restore with Titanium once the new rom has been installed. Just takes a few minutes of getting used to in the new rom environment. Good luck!
Removed it! With Xposed Framework, I downloaded a gem of a module called - "Samsung Data Connection Icon Fix". That did the job. Link - http://repo.xposed.info/module/net.thinkindifferent.dataconnectioniconfix
Hi,
I have recently flashed my oneplus 5 NitrogenOs, but I am facing some issues. I figured maybe any of you guys could help me.
1. When I try to add a new google account, a new screen pops up saying 'Checking info...' ('Informatie controleren...') and appears to be loading. This screen however, never closes. This way I am not able to add any google account to my phone. It appeared out of nowhere after some time of using the rom, so i currently have my google account already setup.
{
"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"
}
2. Google search is not working either (the app and the shortcut in nova launcher), it stops loading just before the end.
I am guessing these two problems are somehow related to google play services, but I have no idea how to fix them (obviously).
3. E-mail isnt loading anymore. The mail preview is showing the first 3-4 lines, but when i open the mail itself it shows nothing but the details (sender, time etc.). This occured after the clean flash (will get to that later on). I can also not send any e-mails. I tried this in 3 different mail-apps (with 3 mail accounts) including gmail and they all show the same results. This is not happening on hotmail.com in chrome.
Current phone details:
- Twrp multirom 3.1.1-0
- Bootloader is unlocked
- Running NitrogenOs 8.0.0 (latest build from this thread https://forum.xda-developers.com/oneplus-5/development/rom-nitrogen-os-cheeseburger-t3684946)
- Magisk v15.2 installed
- Flashed Gapps 'mini'
- Busybox installed (don't think this has anything to do with the problems)
- No Xposed framework installed
I am aware of the fact that the 'Checking info...' glitch has a lot of threads/posts already, but i haven't found any solution yet.
Things i already tried:
- Clean reflashing (rom, gapps and root (magisk and supersu))
- Updating google play services via apk
- Clearing cache/data from all google apps/services
- Removing updates from all google apps/services (this was not possible for google play services)
- Messing around with the host file (root/system/etc/hosts)
Both before and afther the reflash the first two problems occured after a short amount of time.
If anyone has a solution for any of the problems I would love to hear it, and if there is already a solution in another thread i would love a link too.
(ps. This is my first post so if anyone has tips, feel free to comment)
Try different gapps like nano or pico.
hadiyalkishan said:
Try different gapps like nano or pico.
Click to expand...
Click to collapse
Thanks for the quick reply. I tried wiping everything except internal storage and reflashed rom and pico Gapps. For now it seems to be working; mail shows up, all apps open and no google related bugs. Hope it stays like this, but either way thanks for your help!
I finally found out what causes the problems; it's viper4android. After installing the stock version and the materialised version over it the problems occured. Any idea how this could happen or how to undo it? Because i am kinda settled down already with my setup.
I tried uninstalling the drivers and uninstalling the materialised v4a, but the stock version cant be deleted because i flashed it via recovery.
how to fix it
hoangsc said:
how to fix it
Click to expand...
Click to collapse
What problems are you facing? All of them or only the checking info-bug?
Just in case anyone sees this in the future, it turns out my motherboard was messing up. Try to get logs with OnePlusLogKit first and send it to them with your phone.
Hi, my OnePlus 6t started freezing and rebooting itself last night at work and it became more frequent throughout the night. By the time I got home in the morning, it wouldn't stay on for more than a minute before rebooting. I tried uninstalling recently installed/updated apps, when that didn't work, I reset it and installed the latest OOS Rom. I reinstalled all my usual apps and everything looked good for a few hours then it started doing it again.
So I gathered some logs with the OnePlusLogKit and gathered all these logs:
{
"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"
}
I found this towards the end of one of the logs ([email protected]*):
Code:
[20190902_20:50:12.515674]@3 Kernel Offset: 0x1e01800000 from 0xffffff8008000000
[20190902_20:50:12.515680]@3 Memory Limit: none
[20190902_20:50:12.551900]@3 Rebooting in 5 seconds..
[20190902_20:50:17.552136]@3 SMP: stopping secondary CPUs
[20190902_20:50:17.552165]@3 Going down for restart now
[20190902_20:50:17.552172]@3 set_dload_mode ON
[20190902_20:50:17.553029]@3 Causing a watchdog bite!
Boot info:
Last boot reason: kernel_panic,NULL
It doesn't really tell me anything though, so I'm trying to find out how I can gather more information on what's causing this kernel_panic.
I also ran a bugreport with adb and under the DROPBOX SYSTEM SERVER CRASHES section it found 767 crashes, most of which are various system apps like Google Photos, Play Store, and Google Play Services. Though I'm not entirely sure if these, specifically Play Services, can cause the entire phone to crash.
Code:
2019-09-02 09:16:03 system_app_crash (compressed text, 1124 bytes)
Process: com.google.android.gms.ui
Package: com.google.android.gms v19056037 (19.0.56 (100400-262933554))
Build: OnePlus/OnePlus6T/OnePlus6T:9/PKQ1.180716.001/1908012000:user/release-keys
DD-EDD: 1073741826
java.lang.RuntimeException: Unable to start activity ComponentInfo{com.google.android.gms/com.google.android.gms.backup.component.SetBackupAccountFlowActivity}: android.view.InflateException: Binary XML file line #10: Binary XML file line #10: Error inflating class <unknown>
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3047)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3182)
at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:78)
at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:108)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:68)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1916)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:193)
at android.app.ActivityThread.main(ActivityThread.java:6898)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:537)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
Caused by: android.view.InflateException: Binary XML file line #10: Binary XML file line #10: Error inflating class <unknown>
Caused by: android.view.InflateException: Binary XML file line #10: Error inflating class <unknown>
Caused by: java.lang.reflect.InvocationTargetException
at java.lang.reflect.Constructor.newInstance0(Native Method)
at java.lang.reflect.Constructor.newInstance(Constructor.java:343)
at android.view.LayoutInflater.createView(LayoutInflater.java:647)
at com.android.internal.policy.PhoneLayoutInflater.onCreateView(PhoneLayoutInflater.java:58)
at android.view.LayoutInflater.onCreateView(LayoutInflater.java:720)
at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:788)
at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:730)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:863)
at android.view.LayoutInflater.rInflateChildren(LayoutInflater.java:824)
at android.view.LayoutInflater.inflate(LayoutInflater.java:515)
at android.view.LayoutInflater.inflate(LayoutInflater.java:423)
at android.view.LayoutInflater.inflate(LayoutInflater.java:374)
at com.android.internal.policy.PhoneWindow.setContentView(PhoneWindow.java:440)
at android.app.Activity.setContentView(Activity.java:2784)
at dzd.superSetContentView(:[email protected]@19.0.56 (100400-262933554):1)
at com.google.android.chimera.Activity.setContentView(:[email protected]@19.0.56 (100400-262933554):1)
at com.google.android.gms.backup.settings.component.SetBackupAccountFlowChimeraActivity.onCreate(:[email protected]@19.0.56 (100400-262933554):6)
at com.google.android.chimera.Activity.publicOnCreate(Unknown Source:0)
at qcx.onCreate(:[email protected]@19.0.56 (100400-262933554):7)
at android.app.Activity.performCreate(Activity.java:7149)
at android.app.Activity.performCreate(Activity.java:7140)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1288)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3027)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3182)
at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:78)
at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:108)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:68)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1916)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:193)
at android.app.ActivityThread.main(ActivityThread.java:6898)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:537)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
Caused by: java.lang.UnsupportedOperationException: Failed to resolve attribute at index 15: TypedValue{t=0x2/d=0x7f0405a2 a=3}
at android.content.res.TypedArray.getDimensionPixelSize(TypedArray.java:750)
at android.view.View.<init>(View.java:5081)
at android.view.ViewGroup.<init>(ViewGroup.java:659)
at android.widget.LinearLayout.<init>(LinearLayout.java:244)
at android.widget.LinearLayout.<init>(LinearLayout.java:240)
at android.widget.LinearLayout.<init>(LinearLayout.java:236)
... 34 more
========================================
So now I'm running
trying to catch it crash in action, but I'm unable to recreate the problem right now, I guess it wants to cooperate right now.
Am I on the right track? Am I doing anything wrong? How can I go about figuring this out? I just can't find exactly what's causing the KP.
Are you running a Custom Kernel? And are you on Open Beta? Magisk?
Sent from my OnePlus6T using XDA Labs
Mannan Qamar said:
Are you running a Custom Kernel? And are you on Open Beta? Magisk?
Sent from my OnePlus6T using XDA Labs
Click to expand...
Click to collapse
Stock kernel and Rom OOS 9.0.16, not Open Beta, and yes, running Magisk 19.3.
Could be issue with a Magisk Module or maybe an App.
Sent from my OnePlus6T using XDA Labs
Mannan Qamar said:
Could be issue with a Magisk Module or maybe an App.
Click to expand...
Click to collapse
Yeah I thought so too, so I removed all modules, but the problem still persists.
FearMyAnus said:
Yeah I thought so too, so I removed all modules, but the problem still persists.
Click to expand...
Click to collapse
Try without root. Do a clean flash without rooting
Sent from my OnePlus6T using XDA Labs
or just wipe data when it reboots enable usb debug oem stuff and fastboot boot twrp probably set magisk before the gms setup
ecompton59 said:
or just wipe data when it reboots enable usb debug oem stuff and fastboot boot twrp probably set magisk before the gms setup
Click to expand...
Click to collapse
Yeah I did that when I reset it before.
then best fix would be flash fastboot rom or oos setup so you know its fixed
---------- Post added at 08:52 AM ---------- Previous post was at 08:47 AM ----------
then best fix would be flash fastboot rom or oos setup so you know its fixed
ecompton59 said:
then best fix would be flash fastboot rom or oos setup so you know its fixed
Click to expand...
Click to collapse
That's what I did when I reset it. I flashed 9.0.16 fastboot rom.
I'll give you link did you fastboot erase user data or -w or edl mode will definitely fit if edl mode dont nice paper weight lol
ecompton59 said:
I'll give you link did you fastboot erase user data or -w or edl mode will definitely fit if edl mode dont nice paper weight lol
Click to expand...
Click to collapse
Sorry, I'm not quite sure I understand what you're saying, but I tried different kernels and roms, and the issue persists. So I just did a warranty claim instead.
get stock fastboot rom with the one plus 7 drivers when you plug in look at device manager on pc see what it says but not now lol sorry that didn't help
ecompton59 said:
get stock fastboot rom with the one plus 7 drivers when you plug in look at device manager on pc see what it says but not now lol sorry that didn't help
Click to expand...
Click to collapse
It just has to be a hardware problem, it would sometimes crash while I was in the new phone setup screen after resetting it.
I've got the same issue. Gonna have to do a warranty claim too.
DougDuLa said:
I've got the same issue. Gonna have to do a warranty claim too.
Click to expand...
Click to collapse
They emailed me asking for the logs I took because they couldn't recreate the problem. So you should try to get logs before you ship it out to them. OnePlus has the OnePlusLogKit built in.
FearMyAnus said:
They emailed me asking for the logs I took because they couldn't recreate the problem. So you should try to get logs before you ship it out to them. OnePlus has the OnePlusLogKit built in.
Click to expand...
Click to collapse
Thanks for the info! I'll try and do that. Much appreciated.