Related
Hi there,
maybe not a XDA specific Question but maybe s.o. could still help me.
I've got a SIEMENS emem ES75 GSM Modem wich I wanted to use as a SMS receiver for my Party next month (receive sms and project them onto a wall )
But I have some trouble controlling it using the AT-Commandset.
For example: the AT+GMM Command which should give me the name of the Manufacturer) Sometimes AT+ Commands are working, sometimes not.
As it works, I printed out the current settings using AT&V:
Code:
ACTIVE PROFILE:
E0 Q0 V1 X4 &C1 &D2 &S0 \Q0 \V1
S0:000 S3:013 S4:010 S5:008 S6:000 S7:060 S8:000 S10:002 S18:000
+CR: 0
+CRC: 0
+CMGF: 1
+CSDH: 0
+CNMI: 0,0,0,0,1
+ICF: 3
+IFC: 0,0
+ILRR: 0
+IPR: 115200
+CMEE: 0
^SMGO: 0,0
+CSMS: 0,1,1,1
^SACM: 0,"000000","FFFFFF"
^SLCC: 0
^SCKS: 0,1
^SSET: 0
+CREG: 0,1
+CLIP: 0,2
+CAOC: 0
+COPS: "T-MOBILE D"
+CGSMS: 3
Remember: it says "CURRENT PROFILE"
Then I used the AT&V Command when it did not work:
Code:
Current Settings............
E0 H0 Q0 V1
&C0 &D0 &P1 &R0 &S0
S00=000 S01=000 S02=043 S03=013 S04=010 S05=008 S06=000 S07=030
S08=000 S09=000 S10=000 S11=000 S12=050 S13=000 S14=000 S15=000
S16=000 S17=000 S18=000 S19=000 S20=000 S21=000 S22=000 S23=000
S24=000 S25=005 S26=001 S27=000 S28=000 S29=000 S30=000 S31=000
S32=000 S33=001 S34=000 S35=000 S36=000
#0 :
#1 :
#2 :
#3 :
#4 :
#5 :
#6 :
#7 :
#8 :
#9 :
Why does it output the "CURRENT SETTING" instead of the "CURRENT PROFILE"? And why can't I read the SMS? With this Setting it does not accept most of the AT+(..) commands. (AT+GMM, ...)
I sniffed the serial port communication from working applications and used the same commands and init-strings, but nothing
Any advice?
Nothing?
SOLVED: I restored the "WiFi Access Points" backup from Titanium and I'm back online. Is there any way to get details on what files that entails?
Original query:
I'm trying to connect to a corporate IEEE8021x network, and I hand-edited my /data/misc/wifi/wpa_supplicant.conf to add my corporate network.
This didn't work, the WiFi wouldn't even enable; the top item in the Wi-Fi Settings screen Says "Error". I deleted the entry I added, but the results are the same. I then deleted everything except the first two lines
ctrl_interface=tiwlan0
update_config=1
and it appears to try harder to enable it, and it shows on for about 15 seconds, but no access points show up, the GUI asks if I want to forceclose Settings, and then it turns off.
wpa_supplicant.conf had those two lines in it, and the usual list of access points I've seen, nothing else.
Is there some other WiFi config file I need to clear out, or GUI access to this stuff? I just want to get open-access APs working again for now.
dmesg reports:
TIWLAN: driver init
TI WiLink 1271 SDIO: Driver loaded
evt_wifi_power: 0
evt_wifi_set_carddetect: 0
mmc2: card_present 0
kxtf9 1-000f: IRQ TAP2 [2]
kxtf9 1-000f: IRQ TAP2 [4]
wlanDrvIf_Stop
kxtf9 1-000f: IRQ TAP2 [1]
kxtf9 1-000f: IRQ TAP2 [8]
tiwlan: 20 sec os_SignalObjectWait timeout
evt_wifi_set_carddetect: 0
evt_wifi_reset: 1
evt_wifi_power: 0
and the driver unloads
Thanks!
Apologies if this is in the wrong forum, I've been away from xda for close to a year...
I managed to get wallet to install and open, but it bails, and logcat indicates an error that there is no secure element.
Does anyone have the special sim with the secure element for ISIS and feel like giving this a try?
Steps:
1. Add com.android.nfc_extras.jar (attached) to /system/framework, chmod to 644
2. Add the signature from the attached nfcee_access.xml.txt to the /system/etc/nfcee_access.xml on your phone
3. Add com.android.nfc_extras.xml (attached as com.android.nfc_extras.xml.txt) to /system/etc/permissions, chmod to 644
4. Reboot the phone
5. Push the region/device free wallet apk to /system/app (can be found here: http://www.modaco.com/topic/354635-region-device-root-patched-google-wallet-apk-15-r87-v15/ )
the bits in step 1 and 2 came from http://forum.xda-developers.com/showthread.php?p=32338688 post #9
My phone was able to run wallet, but it got an error:
java.io.IOException: NFC EE failed to open
some digging led me to find that this can happen if you don't have any secure elements.
Well, scrolling back in the logcat, I found this:
01-12 15:51:04.642 1045 1069 D NFC_LIST: Allocated node: 0x5160a080 (0x51ca5a70)
01-12 15:51:04.642 1045 1069 D NFC_LIST: Allocated node: 0x5160a1c0 (0x51ca5a7c)
01-12 15:51:04.642 1045 1069 D NFCJNI : Open Secure Element
01-12 15:51:04.642 1045 1069 D NFCJNI : phLibNfc_Mgt_IoCtl()
01-12 15:51:04.642 1045 1336 D NFCJNI : Callback: > IOCTL successful() - status=0x0000[NFCSTATUS_SUCCESS]
01-12 15:51:04.642 1045 1069 D NFCJNI : phLibNfc_SE_GetSecureElementList()
01-12 15:51:04.642 1045 1069 D NFCJNI :
01-12 15:51:04.642 1045 1069 D NFCJNI : > Number of Secure Element(s) : 0
01-12 15:51:04.642 1045 1069 E NFCJNI : phLibNfc_SE_GetSecureElementList(): No SMX detected
01-12 15:51:04.642 1045 1069 D NFC_LIST: Deallocating node: 0x5160a080 (0x51ca5a70)
01-12 15:51:04.642 1045 1069 D NFC_LIST: Deallocating node: 0x5160a1c0 (0x51ca5a7c)
So there appears to be no secure element, or the libs have it disabled (haven't found any libs that don't make nfc_service explode).
Does anyone have the isis app working and have the special sim card with a secure element? If so, can you do a logcat and see if Number of Secure Element(s) shows greater than zero?
Would love to get this working
Trying it now I have both sim cards. I may need to replace phone soon though ISIS corrupted my element I think
vilord said:
Apologies if this is in the wrong forum, I've been away from xda for close to a year...
I managed to get wallet to install and open, but it bails, and logcat indicates an error that there is no secure element.
Does anyone have the special sim with the secure element for ISIS and feel like giving this a try?
Steps:
1. Grab the region/device free version of wallet from modaco here: http://www.modaco.com/topic/354635-region-device-root-patched-google-wallet-apk-15-r87-v15/
2. Grab the galaxy s3 wallet rollback package from here: http://forum.xda-developers.com/showthread.php?p=32338688 post #9
3. From the S3 package, push com.android.nfc_extras.jar to /system/framework, chmod to 644
4. From the S3 package, add the signature in system/etc/nfcee_access.xml to the nfcee_access.xml on your phone
5. Push the wallet apk to /system/app
My phone was able to run wallet, but it got an error:
java.io.IOException: NFC EE failed to open
some digging led me to find that this can happen if you don't have any secure elements.
Well, scrolling back in the logcat, I found this:
01-12 15:51:04.642 1045 1069 D NFC_LIST: Allocated node: 0x5160a080 (0x51ca5a70)
01-12 15:51:04.642 1045 1069 D NFC_LIST: Allocated node: 0x5160a1c0 (0x51ca5a7c)
01-12 15:51:04.642 1045 1069 D NFCJNI : Open Secure Element
01-12 15:51:04.642 1045 1069 D NFCJNI : phLibNfc_Mgt_IoCtl()
01-12 15:51:04.642 1045 1336 D NFCJNI : Callback: > IOCTL successful() - status=0x0000[NFCSTATUS_SUCCESS]
01-12 15:51:04.642 1045 1069 D NFCJNI : phLibNfc_SE_GetSecureElementList()
01-12 15:51:04.642 1045 1069 D NFCJNI :
01-12 15:51:04.642 1045 1069 D NFCJNI : > Number of Secure Element(s) : 0
01-12 15:51:04.642 1045 1069 E NFCJNI : phLibNfc_SE_GetSecureElementList(): No SMX detected
01-12 15:51:04.642 1045 1069 D NFC_LIST: Deallocating node: 0x5160a080 (0x51ca5a70)
01-12 15:51:04.642 1045 1069 D NFC_LIST: Deallocating node: 0x5160a1c0 (0x51ca5a7c)
So there appears to be no secure element. Does anyone have the isis app working and have the special sim card with a secure element? If so, can you do a logcat and see if Number of Secure Element(s) shows greater than zero?
Would love to get this working
Click to expand...
Click to collapse
---------- Post added at 09:44 PM ---------- Previous post was at 09:08 PM ----------
JTidler said:
Trying it now I have both sim cards. I may need to replace phone soon though ISIS corrupted my element I think
Click to expand...
Click to collapse
No Luck, I did all as stated no Google Wallet on the phone
Do you have time to look at the logcat?
On our phones, the internal secure element is disabled (and i haven't found any libraries that have it enabled that don't cause the nfc service to blow up)
Google wallet doesn't support sim-based secure elements yet (they're working to fix that now).
What I'm hoping is that it shows "Number of Secure Element(s) : 1" when the sim is in there...
then hopefully with an updated wallet that reads the sim, it will work.
I'd missed a couple of steps, please see the OP for updated steps and the missing preferences file
vilord said:
I'd missed a couple of steps, please see the OP for updated steps and the missing preferences file
Click to expand...
Click to collapse
No luck I tried. Used off market after changing build.prop crashes after "Adding your account"
No luck
How can I get logs?
when connected with usb, with drivers installed (or on a mac/linux box no drivers are needed), with usb debugging enabled, you can run "adb logcat" from your computer. You'll get hundreds of lines of stuff (connecting to network, changing status bar display, screen pressed, etc, etc, but if you page around enough, or if you output it to a file and search it, you should be able to find the section near where google wallet was trying to connect...
-jesse
how did/is this going
Let us rekindle this thread and see how we are doing with this. I also have a rooted ota 4.1.1 Razr M and would love wallet. I have been reading about it and how to get it done for the last few weeks. any progress?
vilord said:
when connected with usb, with drivers installed (or on a mac/linux box no drivers are needed), with usb debugging enabled, you can run "adb logcat" from your computer. You'll get hundreds of lines of stuff (connecting to network, changing status bar display, screen pressed, etc, etc, but if you page around enough, or if you output it to a file and search it, you should be able to find the section near where google wallet was trying to connect...
-jesse
Click to expand...
Click to collapse
If there's anything I can do to help, I'd need some guidance on how logcats and all that work, but I'm a fast learner and I'd be happy to offer my time and effort!
Heads up: once we get working 4.4, we should be able to use wallet assuming NFC doesn't get broken
Sent from my XT907 using Tapatalk
Hello,
i got a D802 phone which apparently has some sensors disabled in some way. When apps try to use them (so the system see them as existent) they fail or crash.
here some example log:
-Orientation:
Code:
W/OrientationEventListener( 957): Cannot detect sensors. Invalid disable
-Calibration:
Code:
E/AndroidRuntime( 7456): java.lang.NullPointerException: Attempt to invoke virtual method 'int android.hardware.Sensor.getType()' on a null object reference
E/AndroidRuntime( 7456): at com.qualcomm.sensors.sensortest.SensorID$SensorTyp e.getSensorType(SensorID.java:61)
E/AndroidRuntime( 7456): at com.android.settings.lge.MotionSensorCalibration$C alThreadRunnable.run(MotionSensorCalibration.java: 228)
E/AndroidRuntime( 7456): at java.lang.Thread.run(Thread.java:818)
-Gravity:
Code:
I/SensorManager(14094): registerListenerImpl() [Sensor: LGE Gravity Sensor, Rate: 200000, SensorEventListener: [email protected]] by com.kfodor.MySensors.SensorView.registerSensorListener():735
D/sensors_hal_SAM( 949): batch:sensor(android.sensor.gravity) handle:29 freq:1 report_rate:1 max:1.000000 min:0.000000
D/sensors_hal_Gravity( 949): enable: handle=29
D/sensors_hal_Gravity( 949): enable: handle=29, freq=1 report_rate=1 batch_rate=0 batched=0 wakeup 0
D/sensors_hal_Gravity( 949): enable: handle=29 synchronous req
I/sensors_hal_SAM( 949): sendEnableReq:sensor(android.sensor.gravity) Sending enable to svc no:20
E/Sensors ( 474): sns_acm_mr.c(776):Request made to disabled service
E/Sensors ( 474): sns_main.c(1331):Error writing request. sns_err 3 error 0 qmi_err 0
E/sensors_hal_Gravity( 949): processResp: Msg 2; Result: 1, Error: 3
D/sensors_hal_Gravity( 949): enable: Received Response: 1
-Acceleration:
Code:
I/sensors_hal_SAM( 949): sendEnableReq:sensor(android.sensor.linear_acceleration) Sending enable to svc no:20
E/Sensors ( 474): sns_acm_mr.c(776):Request made to disabled service
E/Sensors ( 474): sns_main.c(1331):Error writing request. sns_err 3 error 0 qmi_err 0
E/sensors_hal_LinearAccel( 949): processResp: Msg 2; Result: 1, Error: 3
-Rotation:
Code:
I/sensors_hal_SAM( 949): sendEnableReq:sensor(android.sensor.rotation_vector) Sending enable to svc no:18
E/Sensors ( 474): sns_acm_mr.c(776):Request made to disabled service
E/Sensors ( 474): sns_main.c(1331):Error writing request. sns_err 3 error 0 qmi_err 0
E/sensors_hal_RV( 949): processResp: Msg 2; Result: 1, Error: 3
I/SensorManager(14094): removeAllSensors() [Sensor: LGE Rotation Vector Sensor] by com.kfodor.MySensors.SensorView.registerSensorListener():732
I followed a lot of paths to find a solution, different distributions and full revert to all available stock versions. no way.
As my last trial I want to try to compare my NV data with a working one to search for some misconfigured parameter.
I found a great guide on how to access and extract all NV parameters and save to a text file, here:
http://www.droidviews.com/how-to-bac...imei-on-lg-g2/
As you can see, the guide is for changing IMEI, but the application permit to dump all parameters to a file.
I ask some good man to send me his dump. or i can send mine and get the differences. Because this file contains sensitive data, they should be removed (IMEI, S/N, MAC) even if i am not interested in stealing ids!
I have a D802 32GB.
thank you to everyone, hope to receive some useful feedback!.
Fabio T
My PH-1 reboots randomly, sometimes frequently, and it is accompanied with sudden surge of heat on the in almost the direct center of the phone, on both the front and back sides. This has happened on stock Oreo (from .010 to current stock builds), RR, Lineage OS, AOSiP, and Carbon ROM. I've had it occur while rooted/unrooted, with or without xposed, and have thoroughly wiped device in between new ROMs. And though the device does suddenly get quite hot it can happen when im in a dark cold place or outside in the sun. The only correlation is that it seems to only occur while talking on the phone but length of call is not a factor in that scenario. It could happen 5 times in an hour or in a week.
I'm new to modification, and although green I've made my way through it pretty well thanks to the great forums and tips offered here. Rooting/modding is now much simpler now but this problem has been persisting for almost two months. I've got a logcat from boot to crash taken via ADB (about 2-3 minutes real time) but don't know how to interpret it enough to discover the cause of the problem . Thanks in advance for any help provided. I will post the logcat but I'm not sure of how much to post or how for that matter haha.
Thanks again
That really sounds like a hardware problem if its persisting across ROMs.
Warranty for sure. Most definitely a hardware fault.
jhs39 said:
That really sounds like a hardware problem if its persisting across ROMs.
Click to expand...
Click to collapse
I've taken quite a few logs and there are two consistent segments that I can't get figured out. Any help would be great. The second one has way more variations on the theme and they're grouped. Also, my phone was brand new but NOT purchased from a retailer. I'm assuming I'm outta luck for warranty?
A) 05-17 20:58:36.979 1518 1877 E Diag_Lib: [IMS_FATAL]| 1877 |ims_qmi_register_client : Failed
B) 05-17 20:59:11.372 3949 6262 W Finsky : [102] com.google.android.finsky.billing.a.j.a(48): Got an exception trying to get proto method: java.lang.NoSuchMethodException: getAuthFrequency []
05-17 20:59:11.373 3949 6262 W Finsky : [102] com.google.android.finsky.billing.a.j.a(48): Got an exception trying to get proto method: java.lang.NoSuchMethodException: getUserHasFop []
05-17 20:59:11.374 3949 6262 W Finsky : [102] com.google.android.finsky.billing.a.j.a(48): Got an exception trying to get proto method: java.lang.NoSuchMethodException: getFingerprintValid []
05-17 20:59:11.374 3949 6262 W Finsky : [102] com.google.android.finsky.billing.a.j.a(48): Got an exception trying to get proto method: java.lang.NoSuchMethodException: getDesiredAuthMethod []
05-17 20:59:11.374 3949 6262 W Finsky : [102] com.google.android.finsky.billing.a.j.a(48): Got an exception trying to get proto method: java.lang.NoSuchMethodException: getAuthFrequency []
05-17 20:59:11.375 3949 6262 W Finsky : [102] com.google.android.finsky.billing.a.j.a(48): Got
crixley said:
Warranty for sure. Most definitely a hardware fault.
Click to expand...
Click to collapse
Thank you for the response. Please look at my reply to user below your post. Is any information gathered just from those logs?
It looks like it's constantly polling to register you on the network and failing. What company are you with? Try two things just to satisfy my curiosity:
1) go into mobile network> advanced and change automatically select network to off. Click below and choose your provider yourself from the list.
2) double check the access point name (APN settings)
crixley said:
It looks like it's constantly polling to register you on the network and failing. What company are you with? Try two things just to satisfy my curiosity:
1) go into mobile network> advanced and change automatically select network to off. Click below and choose your provider yourself from the list.
2) double check the access point name (APN settings)
Click to expand...
Click to collapse
I'm on Verizon and step 1, done. It was active so I switched off. Step 2 it lists 2 APN... Verizon (VZWINTERNET) **checked** and Straight Talk Verizon (TRACKFONE.VZWENTP)**not checked**
Now im curious so I'll run logcat and see if similar codes persist. It seems like I'm on the phone nearly every time it happens, don't know if there is a correlation.
Thanks!
KingBeefy said:
I'm on Verizon and step 1, done. It was active so I switched off. Step 2 it lists 2 APN... Verizon (VZWINTERNET) **checked** and Straight Talk Verizon (TRACKFONE.VZWENTP)**not checked**
Now im curious so I'll run logcat and see if similar codes persist. It seems like I'm on the phone nearly every time it happens, don't know if there is a correlation.
Thanks!
Click to expand...
Click to collapse
Would be registering on the network when you make a call, it registers with the nearest tower to you. Let me know if that helps!
crixley said:
Would be registering on the network when you make a call, it registers with the nearest tower to you. Let me know if that helps!
Click to expand...
Click to collapse
So went a few hours with the changes you recommended and it was doing ok so far. The reboots are randomized. Might be 1 time in 36 hours and others its 6 times in an hour. Phone activity, battery life, etc seem to have a wide deviation too. BUT, so far so good. Much of the logcat did look like nothing was throwing a fail code, but this one still popped up enough to notice .
05-21 06:53:19.972 1553 1897 E Diag_Lib: [IMS_FATAL]| 1897 |ims_qmi_register_client : Failed
05-21 06:53:20.335 1050 2263 I WifiHAL : event received NL80211_CMD_VENDOR, vendor_id = 0x1374, subcmd = 0xd
05-21 06:53:21.982 1553 1897 E Diag_Lib: [IMS_FATAL]| 1897 |ims_qmi_register_client : Failed
05-21 06:53:21.984 1553 1897 E Diag_Lib: [IMS_FATAL]| 1897 |ims_qmi_register_client : Failed
05-21 06:53:22.330 1050 2263 I WifiHAL : event received NL80211_CMD_VENDOR, vendor_id = 0x1374, subcmd = 0xd
05-21 06:53:23.991 1553 1897 E Diag_Lib: [IMS_FATAL]| 1897 |ims_qmi_register_client : Failed
05-21 06:53:23.993 1553 1897 E Diag_Lib: [IMS_FATAL]| 1897 |ims_qmi_register_client : Failed
05-21 06:53:24.348 1050 2263 I WifiHAL : event received NL80211_CMD_VENDOR, vendor_id = 0x1374, subcmd = 0xd
05-21 06:53:26.000 1553 1897 E Diag_Lib: [IMS_FATAL]| 1897 |ims_qmi_register_client : Failed
05-21 06:53:26.002 1553 1897 E Diag_Lib: [IMS_FATAL]| 1897 |ims_qmi_register_client : Failed
KingBeefy said:
So went a few hours with the changes you recommended and it was doing ok so far. The reboots are randomized. Might be 1 time in 36 hours and others its 6 times in an hour. Phone activity, battery life, etc seem to have a wide deviation too. BUT, so far so good. Much of the logcat did look like nothing was throwing a fail code, but this one still popped up enough to notice .
05-21 06:53:19.972 1553 1897 E Diag_Lib: [IMS_FATAL]| 1897 |ims_qmi_register_client : Failed
05-21 06:53:20.335 1050 2263 I WifiHAL : event received NL80211_CMD_VENDOR, vendor_id = 0x1374, subcmd = 0xd
05-21 06:53:21.982 1553 1897 E Diag_Lib: [IMS_FATAL]| 1897 |ims_qmi_register_client : Failed
05-21 06:53:21.984 1553 1897 E Diag_Lib: [IMS_FATAL]| 1897 |ims_qmi_register_client : Failed
05-21 06:53:22.330 1050 2263 I WifiHAL : event received NL80211_CMD_VENDOR, vendor_id = 0x1374, subcmd = 0xd
05-21 06:53:23.991 1553 1897 E Diag_Lib: [IMS_FATAL]| 1897 |ims_qmi_register_client : Failed
05-21 06:53:23.993 1553 1897 E Diag_Lib: [IMS_FATAL]| 1897 |ims_qmi_register_client : Failed
05-21 06:53:24.348 1050 2263 I WifiHAL : event received NL80211_CMD_VENDOR, vendor_id = 0x1374, subcmd = 0xd
05-21 06:53:26.000 1553 1897 E Diag_Lib: [IMS_FATAL]| 1897 |ims_qmi_register_client : Failed
05-21 06:53:26.002 1553 1897 E Diag_Lib: [IMS_FATAL]| 1897 |ims_qmi_register_client : Failed
Click to expand...
Click to collapse
Hmmm. Have you flashed any other modems? Might be worth a shot.
crixley said:
Hmmm. Have you flashed any other modems? Might be worth a shot.
Click to expand...
Click to collapse
Teach me master!!!! What resource will you point me to?
KingBeefy said:
Teach me master!!!! What resource will you point me to?
Click to expand...
Click to collapse
Lol
What I would do is full wipe and fastboot flash the latest full file. Seems like OTAs haven't been updating the modem and ROMs wouldn't either I doubt.
You could probably just fastboot flash the modem.img from from the latest fastboot release if you really didn't want to full wipe.
The full wipe doesnt scare me off. I took my lumps teaching myself from scratch and the nuances of the way dual partition devices function has been an interesting learn. I prefer using ADB/fastboot/twrp instead of doing and OTA because of the learning opportunity so I have the latest modem.img from the current Firmware from essentials site. I also use @invisiblek builds. I sent Essential the log and they offered a suggestion as well, saying
I am sending you two troubleshooting steps that.... One of the reasons we need to do this is that when you factory reset your phone you restored backed up information and you signed back into you google account....
Click to expand...
Click to collapse
One of the first things I learned in forums like this one was that until you are ready to go, don't sign in to anything. So I will try and do that. Thanks again for suggestions @crixley
I was having this issue a while back. Every custom rom/kernel caused the processor to lock up at Max frequency randomly thus causing quick overheating no matter how small the load. Performance is amazing through this, but overheating is very annoying. I fixed mine by sticking to stock rooted and not touching the governors or thermal throttling. Maybe I would suggest monitoring your processor with a kernel manager and/or trying to play around with governors and thermal options for now, if you in fact have the same issue, to see if you get something thats stable and sticks. Good luck
I had an issue with mine where it was constantly locking up and rebooting, mostly during multimedia activities like watching YouTube, gaming and even browsing chrome. I never monitored the temperature and it never felt hot to the touch but it just kept happening constantly. I bought it as a refurbished on eBay and was crashing out of the box. It was completely stock Android 8.1.1. Most of the time it would just constantly non stop crash after 30seconds-10minutes of being turned on,. Would just freeze, sit for 30 seconds and then reboot itself. A couple times it lasted sitting idle for 14 hours before crashing and then constantly do it again.
Anyways even though it was a refurbished unit and the seller was not the original owner, it was still under warranty period and was able to be replaced. Just open warranty rma with essential is what I would do. If the serial/imei you provide them is still under warranty they will probably honor it.
Also they gave me that troubleshooting steps too,. Factory reset, start fresh and don't login to your, it's bogus. Still had the same issue on my phone and I actually had to send my phone back twice before they replaced it. The first time I sent it in they said they ran diagnostics that didn't detect any issue, but when I got the phone back it crashed within 10minutes and I never logged into Google. Just a bad hardware issue.
KingBeefy said:
The full wipe doesnt scare me off. I took my lumps teaching myself from scratch and the nuances of the way dual partition devices function has been an interesting learn. I prefer using ADB/fastboot/twrp instead of doing and OTA because of the learning opportunity so I have the latest modem.img from the current Firmware from essentials site. I also use @invisiblek builds. I sent Essential the log and they offered a suggestion as well, saying One of the first things I learned in forums like this one was that until you are ready to go, don't sign in to anything. So I will try and do that. Thanks again for suggestions @crixley
Click to expand...
Click to collapse
I am seeing the same errors. What did Essential say? Did it resolve the errors?