Database Users

First Day with G1 (diary) - Hardware problems ?

This is my first topic so: hello all, my name is Filipe and im from Lisboa, i buy the G1 with sim unlock from T-Mobile (Uk version) two days ago. First Day im really impressed with Device, I try a lot of stuff, like bar code reader, Camera, GPS, i download a lot of stuff in the Market, and, with the help of the forum, i access the device as a root user, for wifi sharing with my computer.
Today (monday) i worked far from where i live, (im a network engineer and i need the device for planing my life, and for navigate across the country). I have a company phone so i only need G1 for internet access, and for that i buy dedicated sim card only for 3g connection). Like i said before, today was the first working day for the G1.
3g active all the time
(8:00 AM): Wake up, unplug it from charger.
(8:30 AM): See the traffic status over the internet
(9:00 AM): Arrive to my car, plug the phone to charger, start Imeem mobile for music (Start with nirvana ), start GPS with one navigation system that i find yesterday and i liked alot, called wisepilot, i have other navigation system like Nav4All and AndNav2! but i can only put wisepilot to work (??). First Problem. GPS Satellites take 10 minutes to apear (??)
(10:40 AM): Arrive to destination unplug the phone and damn, the back end of the G1 is HOT, very HOT, i never experienced nothing like it in my other HTC 3300, but it never slow down or lag the map, and the music continues playing without any kind of delay. So i Guess that is normal ???. Turn of the GPS with Useful Switchers and go to work. I don't know if im closing the programs correctly, if i press Home for 3 or 4 seconds i found last used programs, and i only have to touch them to open, so my guess is that they continued running in background and not really closing when i press back (??) for closing them. (when i go to terminal and make #top command i see alot of stuff, can this be the cause of high temperature??? a lot of things working in background?)
(11:00 AM): BIG PROBLEM: the battery is dead. completely dead, i dont know why, the 3g is always on but everything else is off (everything that i can put off in useful switchers). I dont have where to plug it for charging so i have to wait until 5 PM
(5:00 PM): Arrive again to car, start google maps, start tunewiki for music (start with Bob Marley other day of work ) and back to home again
(7:00 PM): when i arrive home, after two hours of driving i only have 57% charged (this is too low isnt it???) and the device is again to HOT.
(9:00 PM): when i start this topic G1 just show the message that battery is lower that 15% and is hot again, it is plugged to PC just like i show in next photo.
The device was very very nice, alot of stuff to explore but and alot of IU problems (Incompetent User), i dont know why the device is always to HOT and im loosing battery very very fast. But always stable and without lag.
{
"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"
}

Well first off, congrats on your G1. I got my ADP1 (developer G1) just after christmas and love it. It does get very hot. It has never really been a problem for me, just an annoyance. That is just the price for having background apps, more ram, and a pretty powerful processer. My iPhone doesn't have any of those features (well... it didn't before I jailbroke anyway ) and it STILL gets hot. It is just a common problem with many modern smartphones (my friends blackberry storm does the same occasionally). I wouldn't worry too much about it. And the G1 battery is pretty crappy. It is low compared to even some dumbphones. You can either buy one of the extended batteries available online, or just use a program like Advanced Task Manager (in the market) to shut off all other applications running in the background. Especially since those pesky radio apps like to run in the background
Hope this helps! Enjoy your G1!

Filipe.Nogueira said:
Click to expand...
Click to collapse
I love the design! My battery does the same thing you described, as i have to use it for planning, internet, and coding, etc. Seems to be a normal thing across all G1 owners thought

Turn off 3G -- you don't need it for navigation and it sucks the battery dry fast.

Also, takes a few charge/discharge cycled for battery capacity to get up to maximum.

Yeah I think the low capacity battery is a serious problem, I will consider buy a new one. And, if I navigate using google maps I need the 3g connection because the maps loading and the music streaming in background...
I erase all the settings and data of my phone yesterday (alt + w in startup menu) and it is more cool and fresh.
When I'm writing this in g1 battery goes from 36% to 28%...

Axon 7 and Android Wear - Consistently Drops Connection and Forces Repairing

Hey all. So far I mostly love this phone, however I am noticing a few quirks. The main one is with Android Wear. I am connecting to a Huawei Watch. Works fine for a bit and then a pop up on the phone says it needs to be repaired and asks keep to confirm the 6 digit passcode on the watch and the phone. It happens at least twice a day. Very confusing why as I have a strong connection to Bluetooth and Wi-Fi. What I am confused about is why it acts like it is no longer paired. It even removes it from my trusted list of Bluetooth devices. Anyone else having this problem?
Another issue is with when I used SMS backup app to move my messages and call logs over. It keeps popping up with an alert saying I have 4000 unread messages even though I have none.
Any help here is appreciated guys!

I decided to just do a complete factory reset. Nobody else seems to be having the issues I'm having and I think it's because I restored from another device, etc. I am going to set it up completely from scratch and see how it goes. I'll install each app one by one, etc. I'll report back if improvements on the Android Wear/Messaging front. Also, the ambient light sensor decided to go all wonky and would be SUPER dark - I had to literally hold the phone to a light bulb to have it change. Def wasn't doing that for the first few days I had it. Seems to all be software related.

svenb352 said:
I decided to just do a complete factory reset. Nobody else seems to be having the issues I'm having and I think it's because I restored from another device, etc. I am going to set it up completely from scratch and see how it goes. I'll install each app one by one, etc. I'll report back if improvements on the Android Wear/Messaging front. Also, the ambient light sensor decided to go all wonky and would be SUPER dark - I had to literally hold the phone to a light bulb to have it change. Def wasn't doing that for the first few days I had it. Seems to all be software related.
Click to expand...
Click to collapse
Please tell me if that fixes it, because I want to get this phone and if it doesn't work correctly I'll keep looking.
-------------------------------------------------------------------------------------
Also, on my old phone, what I had to do was restart the phone and the watch at the same time.

So far so good! I did the Google restore, not the SMS Backup and Restore thing nor did I do the NFC backup from my Galaxy S7 edge like I did originally. The ambient light sensor is working perfectly now, all my apps are reinstalling, and it paired with Android Wear immediately, no drama. So far, things are looking good .

Same issue with Asus Zenwatch 3
I have the same issue with my Asus Zenwatch 3 and my european model of Axon 7. Will try the factory reset and get back. I also did the restore connecting with NFC from my previous Nexus 5.

I'm having 5 days now the new Zenwatch 3 and works flawlessly with Axon 7(A2017G version)
Notification works great.
No any kind disconnection.
Call quality through smartwatch in high level with loud and clear voice without interruption.
Music control through Zenwatch 3 to my Bluetooth hands free also works great.
Android Wear/Zenwatch Manager app installed at my Axon 7 working flawlessly with Zenwatch 3
Solid battery both at phone and smartwatch.
Until now everything rock solid.
Sent from my iPad using Tapatalk

I just got an update to my watch last night. I'll post if it fixed my issue or. not

This is mine version.
{
"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"
}
Can you post yours?
Sent from my iPad using Tapatalk

paatha13 said:
I'm having 5 days now the new Zenwatch 3 and works flawlessly with Axon 7(A2017G version)
Notification works great.
No any kind disconnection.
Call quality through smartwatch in high level with loud and clear voice without interruption.
Music control through Zenwatch 3 to my Bluetooth hands free also works great.
Android Wear/Zenwatch Manager app installed at my Axon 7 working flawlessly with Zenwatch 3
Solid battery both at phone and smartwatch.
Until now everything rock solid.
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Good to hear. I've been following threads here as I evaluate whether to get an Axon 7 or not.
I got a Zenwatch 3 recently. I'm using a NOte 4. I'm having problems with the phone being VERY laggy, even locking up for periods of time, when hooked to the watch. Battery runs down a lot faster too.
Maybe the Note 4 just isn't enough for Androidwear...

I ran my note 4 edge and 360 sport for quite a while with no issues what so ever. I've been running my 360 off this Axon 7 for a few days now also without issue. Everything has been updated to the latest of what's available, not sure what could be happening on your end. There is a permission authorization required to keep Android Wear connected.
Sent from my ZTE A2017U using XDA-Developers mobile app

Just wanted to add that Yes the restore is the issue. I would always restore my bluetooth connections from previous phone and always had issue like this until I would wipe date on bluetooth and do each device new then they would stick. SO i just always do bluetooth connections fresh now

Don't know if it helps at all, but I just got an Axon 7 and was having this exact same problem. Found this thread and did a factory reset and restore through Google instead of the restore through Helium which is what I did when I first got the phone. It would not stay paired with my LG Watch Urbane even after the reset. After a bit of monkeying, I realized the ZTE has some battery/power management app that by default won't let Android Wear stay active. You have to go in and tell it to ignore it. I assumed that when the Wear app was asking me as I first set it up to exclude it from battery optimization, it was taking care of it all. Once I realized (which I probably shoulda thought about first) and excluded Wear from the power saver, I have had no problems at all and it works better than my Nexus 6P at keeping connection with my watch.

Oh boy! Should I upgrade to Oreo or wait?

Apperantly the update to Oreo has come around. How stable is it though, should I wait.
What's your experience?

From a few hours of work with the updated phone i do not see any problems. Performance is the same like on nougat and i am yet to see any bugs. If you like to work with new tch like me - go and get the update. If you are more cautious - wait for a few days and see the feedback before updating.

go ahead buddy, its good, no bugs, same as it was on nougat, 3-4 hours SOT..

Boy, we already waited too long, I just hit update

Are you on 2.21.401.1??
Same Sh1t... Different Day

I updated on my single SIM and there are no problems. Battery life is the same (around 3 hours of SOT). On nougat I had problems with fingerprint reader lately (when turning on the screen, sensor didn't work - when I turn off smartlock, it worked) but now on Oreo there is no problems. Also, automatic "do not disturb" didn't work (worked just first time after reboot) and on Oreo it works.

So I've upgraded and no problems so far.
I didn't reset or anything, just upgraded.
Notification badges however don't really work for any app except for some that came with the ROM.

cile1977 said:
I updated on my single SIM and there are no problems. Battery life is the same (around 3 hours of SOT). On nougat I had problems with fingerprint reader lately (when turning on the screen, sensor didn't work - when I turn off smartlock, it worked) but now on Oreo there is no problems. Also, automatic "do not disturb" didn't work (worked just first time after reboot) and on Oreo it works.
Click to expand...
Click to collapse
well, the phone didnt have any major bugs or alot of stuff that are not working i did notice a major hit in bench marks like geek bench the single core score droped to nearly half of what it was before oreo lol but i managed to solve this by unlocking the bootloader which did do a reset for may phone and made it as fast as brand new a normal factory reset from the settings didnt change a thing so ya you can try factory resseting but it didnt work for me. another thing is that when rotating the phone while watching a video on youtube or something there is a bug where the phone takes about 5 to 6 seconds to respond that can be fixed by just restarting your phone . it is a really stupid bug. oh yeah and one more thing if you open the camera app and then press the home button the second screen will still have the camera zoom slider on it until you close the app also there alot of instances where the phone goes from the app to home screen without an animation but again nothing too big all of them are small little bugs
here is a post where is explain how my phones performance got way better after unlocking the bootloader https://forum.xda-developers.com/u-ultra/help/htc-lagging-problem-t3777187
if this was helpful for you please press the thanks button it make me happy have a gd day

The Quantum Guy said:
well, the phone didnt have any major bugs or alot of stuff that are not working i did notice a major hit in bench marks like geek bench the single core score droped to nearly half of what it was before oreo lol but i managed to solve this by unlocking the bootloader which did do a reset for may phone and made it as fast as brand new a normal factory reset from the settings didnt change a thing so ya you can try factory resseting but it didnt work for me. another thing is that when rotating the phone while watching a video on youtube or something there is a bug where the phone takes about 5 to 6 seconds to respond that can be fixed by just restarting your phone . it is a really stupid bug. oh yeah and one more thing if you open the camera app and then press the home button the second screen will still have the camera zoom slider on it until you close the app also there alot of instances where the phone goes from the app to home screen without an animation but again nothing too big all of them are small little bugs
here is a post where is explain how my phones performance got way better after unlocking the bootloader https://forum.xda-developers.com/u-ultra/help/htc-lagging-problem-t3777187
if this was helpful for you please press the thanks button it make me happy have a gd day
Click to expand...
Click to collapse
Geekbench is OK on my Ultra - I didn't make factory reset, just upgraded from Nougat:
{
"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"
}

Same for me geekbench is like nougat

I think it's safe to say the update on single SIM is much better than the one for Dual SIM, right.
My Ultra performs now much better, almost never stutters, consistant speed, and normal battery life. I hoped the google camera worked better on oreo, but it is still slow and unstable. i think the camera 2 implementation is not perfect. tested the gcam ports also on the old lg g5 and there it is almost like on a nexus/pixel.
All in all i'm very satisfied with the update, especially the improved outdoor visability is a nice surprice. but it came way too late and a half year without security patches is a nogo. hope tehy will come now at least every third month again.

So what about the badge notifications for Oreo?
What apps don't get them right?

The Android Oreo 8.0 update is FINALLY here

Here's the info released today on T-Mobile's website: https://support.t-mobile.com/docs/DOC-34136
{
"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"
}
It looks like the update pushes are on a daily limit right now. But regardless, it's here!

Downloading it right now!

LG G6 ThinQ. Nice!

never thought we'd actually get it, updating now!

Updating now. Odd that it is still unavailable via Bridge.

So far nothing really noticeable besides major changes to the setting menu. They also added a square dot on the navigation bar so that you can hide the bar per app. Battery life still unknown. I do wish we have 8.1 instead, but I think this is the end of this phone. I will check if the Bluetooth stuttering issue is resolved for my car.

Is someone willing to grab the KDZ from LG Bridge?
-- Brian

Battery life doesn't seem good. It appears to be noticeably worse although I don't remember the old battery life. Today is weekend so I am mostly at home connected to a very good wifi signal. Phone has NOT been reset. It was upgraded last night so today was the first full day use.
Total time 10 hr since removal from charger at 100%.
Battery is down to 34%. SoT is 3 hr even as of now.
About 25 min of YouTube and everything else is web browsing and using Relay Pro (reddit app).
Feels disappointing. I wonder if we'll ever see 8.1, which has more battery life optimization. My bet is never.

My wife's T-Mobile G6 feels more laggy and chop on this new update.
Man I miss the old days of all carrier phones being able to root and ROM, I'd love install Lineage 15.1 on this phone.
Oh well, I'm happy as a clam on my Pixel 2 XL which is smooth as butter.

Updated my G6 yesterday. It became really smooth and lag-free, whereas on Nougat my G6 was constantly microstuttering. So far, I like the update.

THE BATTERY DRAIN HAS BEEN FIXED FOR ME. Go to settings >> storage >> internal storage >> Free up space. Then select everything, including the various cache memories and delete them!
It doesn't delete your data, just some temporary cached memory that's used for efficiency which really isn't all that important. My battery on-screen time used to be 3 hours after the Oreo update, but now it's been well over 6 since freeing up space.

Khotum7 said:
THE BATTERY DRAIN HAS BEEN FIXED FOR ME. Go to settings >> storage >> internal storage >> Free up space. Then select everything, including the various cache memories and delete them!
It doesn't delete your data, just some temporary cached memory that's used for efficiency which really isn't all that important. My battery on-screen time used to be 3 hours after the Oreo update, but now it's been well over 6 since freeing up space.
Click to expand...
Click to collapse
Thanks, gonna give this a try.

Welp, that didn't work for me this drain is crazy getting tops 2 hrs of SOT. I've read on the net that resetting it to factory helped for some any confirmation on this?

I found the culprit which was Fitbit. I deleted the app and I'm at 4hrs SOT with 65% left. Will reinstall the app tomorrow and see how it goes.

Bad news the Oreo update broke my BT with my car head unit. It was working well enough with 7.0 but 8.0 causes the audio to cut in and out about every 2-4 seconds. My other phones playing the same content perfectly without any issues. I haven't factory reset the G6 yet, but BT on this phone never worked well with my car head unit. It does work flawlessly with my Sony WH-1000XM2.

focus-pocus said:
Updated my G6 yesterday. It became really smooth and lag-free, whereas on Nougat my G6 was constantly microstuttering. So far, I like the update.
Click to expand...
Click to collapse
Mine is exactly the opposite. Slow, laggy, awful experience.
I HATE LG's ROMs. Just way, WAY too stuffed with bloatware.

Android Auto is broken. It won't connect to my car.
This phone is brand new to me, I just got it as a certified refurb from Amazon. This is very disappointing to me, since I used it daily with my last phone.

OnuPlus 7T pro 5g Mclaren T-Mobile issues need to be solved

Using an oneplus 7t pro 5g Mclaren since February this year..i am not a power user..when OS11 update came i was so excited to upgrade and after upgrading my peaceful life with the device has become a nightmare..i am trying to point out the problems i have been facing..
1.the google app simply doesn't wanna work 99% of the time..(since OS10) i have use chrome for normal google search..
2.'ok google' or 'hey google' never did respond to me doesnt matter how many times i retrain my voice.
3.smart lock features doesnt work.
4.the battery capacity has been shown 3300 mAh on many device checking apps including benchmarking ones where it's supposed to show 4085 mAh as written on the box..besides that my phone battery backup forced me to put my belief on the 3300 mAh capacity..since OS11 update it has become worse just.
5.Oneplus cameras dont have that great reputation but i was happy with the shutter performance and the pics..OS11 destroyed that feeling with laggy camera app and bad performances..protrait mood fights hard to locate the face/object and 70% time gets defeated..theres obviously focus issues as well..but the 1 sec lag after pressing shutter is just unbearable..last 2/3 months i have been avoiding taking pics on my phone
6.Ghost Lock has made my device so pathetic that the phone itself wanna die i think..it doesnt matter gaming or making a simple call ghost locks have been happening all the time..phone hangs 10% of the time after it happens...minimum 5 times a day.
7.some third party apps arent working properly also which are very useful one's..like vanced/quick video recorder etc..
8.in developer options the Bluetooth LDAC options have been disabled.i bought an oneplus bullets Z along with the phone but later was surprised to see that it only supports AAC and another common codec no aptX or anything.i dont understand when i connect this headphone with a Xiaomi MI 9T all the codecs are available to choose on that device but not on my phone! The codecs arent available on the phone itself or the Bluetooth device i am confused.
9.i dont know what to say about the battery backup.never felt an urge to buy a power bank but now i do.i am not also a heavy gamer dont play PUBG or Asphalt. Games like Rise of empire or clash royale drains the battery such fast that my 3 years old Nokia 6.1 sometimes laughs at it.
10.heating issue isnt absent either..i only use the cover given with the phone when not at home..phone gets heated up with simple gaming sometimes unbearably during charging..i have been noticing also the charging time isnt like it used to be..20/30 minutes more ots taking for a full charge.
11.bluetooth device gets disconnected on calls specially when talking over social apps.and on some social media apps it doesnt wanna even get connected
Again i am not a super user of android..never tried rooting any device..this one is my first OnePlus device. what are my options to get rid of these problems? Specially to solve the problem with the camera i am seriously thinking of downgrading it to OS10 stable but i dont know that will fix camera lag at least or not..any suggestions to get rid of all/most of the problems written above will be heavenly..thanks for having patience to read all through
My current build number..
{
"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"
}

Wow, you must have spent (wasted) a long, long time typing that...
As for 4) that's a bug in most apps. The battery capacity is 4085maH
As for everything else, have you tried a factory reset and not restoring data/backup of app data from Google?
I don't have a single one of those issues on OOS 11.
If factory reset doesn't work, you can revert back to OOS10 using the MSM tool, or sell the phone. Do you think a) OnePlus reads these forums or b) actually cares at all?

Thanks for ur reply..actually it took a little time to write but u must have noticed i managed to make it funny for myself
No i didnt try that..u r suggesting me to factory reset and then not restoring the backup data and start fresh?

Ebrahim93 said:
Thanks for ur reply..actually it took a little time to write but u must have noticed i managed to make it funny for myself
No i didnt try that..u r suggesting me to factory reset and then not restoring the backup data and start fresh?
Click to expand...
Click to collapse
Yes, exactly. Just try it and see if it works. Don't have much to lose by trying. Considering I don't have a single issue with OOS11 (and specifically none of the ones you mentioned), I think you have some apps or more specifically app data that didn't take the upgrade to OOS11 well and are causing havoc on your device. Just factory reset, don't let Google restore apps (sms, call log, pictures are fine to restore), and see if you still have issues.

starcms said:
Yes, exactly. Just try it and see if it works. Don't have much to lose by trying. Considering I don't have a single issue with OOS11 (and specifically none of the ones you mentioned), I think you have some apps or more specifically app data that didn't take the upgrade to OOS11 well and are causing havoc on your device. Just factory reset, don't let Google restore apps (sms, call log, pictures are fine to restore), and see if you still have issues.
Click to expand...
Click to collapse
I bought the McLaren when it first came out. I loved the device and it worked flawlessly. I saw no need to sweat rooting the device and wasn't an option back then anyway. Even now it doesn't seem as clean as the earlier android phones I've rooted and owned but the world changes.
Unfortunately, I cracked my screen and was sent a refurb. I started dealing with sound corruption issues shortly afterwards. I never gave up on the phone and I knew there was some kind of conflict with newer Google updates my device pretty early on. I did MANY factory resets(erase all) and cleared cache both individually and as well as through recovery and it would only temporarily fix my issue. Then it would come back on it's own without any changes made by me.
At first, I had a lot of success uninstalling updates for the main Google app, clearing cache and data (sometimes resetting system app preferences and then rebooting into recovery where I would clear cache again and reboot. That worked for a while but as Google and other Google services received updates it became more difficult to fix using this method. By the time 11 dropped and the issue got worse, I was convinced I must have gotten either A) a bad egg or B) it was my fault and I turned the phone off in the middle of an install causing some kind of corruption that persisted through the updates somehow. The truth though may be somewhere between a phone that someone returned for a good reason and the increasingly more insidious nature of Google Apps. I was eventually defeated, made too many changes that the phone didn't agree with, got the Qualcom Error and was faced with either getting a new phone or seeking aid through a Community I've always respected.
Since then I've tried clean installs of the more recent RoMs but the issue was persistant. If it wasn't for the fact that the phone's speaker and mic would work again after a clean install (offline no SiM) but then get corrupted again within 5 minutes, I think I would have assumed a hardware issue only (still might be a bad egg on some level).
I decided to go back further, this time installing 10.0.36, which I guessed might be far enough back to a time before any issues and is a bit lighter (around 10 preinstalled apps lighter not including system). To my dismay (again, still offline) the mic and speaker corruption/conflict was still present. I began making one change at a time (mostly targeting anything mic or Google related) and it became clearer over the last few days that it was definitely Google and Google's zombie-like behavior to change settings back on it's own. I think that company went way past the point of overreach and intrusion a long time ago.
What happens is that ALL of the Google apps have (modify system settings) checked by default and I believe all it takes is one of them to have that access to let it's Google buddies come back to the party.
I would love to know where the conflict actually lies on a deeper level but that's probably a bit out my bubble of current knowledge and I just really need to have a working phone more than answers atm.
Now I'm praying that dropping in my Sim and signing in to the real owner (I seriously overpaid for a phone that's mostly not mine) of my phone doesn't somehow give Google access to some backup plan to allow itself free reign all up in my settings again. If it does, someone in charge of the google might be getting a 5G McLaren shoved into places that see less sun...in my imagination of course.

siani_8 said:
I bought the McLaren when it first came out. I loved the device and it worked flawlessly. I saw no need to sweat rooting the device and wasn't an option back then anyway. Even now it doesn't seem as clean as the earlier android phones I've rooted and owned but the world changes.
Unfortunately, I cracked my screen and was sent a refurb. I started dealing with sound corruption issues shortly afterwards. I never gave up on the phone and I knew there was some kind of conflict with newer Google updates my device pretty early on. I did MANY factory resets(erase all) and cleared cache both individually and as well as through recovery and it would only temporarily fix my issue. Then it would come back on it's own without any changes made by me.
At first, I had a lot of success uninstalling updates for the main Google app, clearing cache and data (sometimes resetting system app preferences and then rebooting into recovery where I would clear cache again and reboot. That worked for a while but as Google and other Google services received updates it became more difficult to fix using this method. By the time 11 dropped and the issue got worse, I was convinced I must have gotten either A) a bad egg or B) it was my fault and I turned the phone off in the middle of an install causing some kind of corruption that persisted through the updates somehow. The truth though may be somewhere between a phone that someone returned for a good reason and the increasingly more insidious nature of Google Apps. I was eventually defeated, made too many changes that the phone didn't agree with, got the Qualcom Error and was faced with either getting a new phone or seeking aid through a Community I've always respected.
Since then I've tried clean installs of the more recent RoMs but the issue was persistant. If it wasn't for the fact that the phone's speaker and mic would work again after a clean install (offline no SiM) but then get corrupted again within 5 minutes, I think I would have assumed a hardware issue only (still might be a bad egg on some level).
I decided to go back further, this time installing 10.0.36, which I guessed might be far enough back to a time before any issues and is a bit lighter (around 10 preinstalled apps lighter not including system). To my dismay (again, still offline) the mic and speaker corruption/conflict was still present. I began making one change at a time (mostly targeting anything mic or Google related) and it became clearer over the last few days that it was definitely Google and Google's zombie-like behavior to change settings back on it's own. I think that company went way past the point of overreach and intrusion a long time ago.
What happens is that ALL of the Google apps have (modify system settings) checked by default and I believe all it takes is one of them to have that access to let it's Google buddies come back to the party.
I would love to know where the conflict actually lies on a deeper level but that's probably a bit out my bubble of current knowledge and I just really need to have a working phone more than answers atm.
Now I'm praying that dropping in my Sim and signing in to the real owner (I seriously overpaid for a phone that's mostly not mine) of my phone doesn't somehow give Google access to some backup plan to allow itself free reign all up in my settings again. If it does, someone in charge of the google might be getting a 5G McLaren shoved into places that see less sun...in my imagination of course.
Click to expand...
Click to collapse
The problem isn't Google, it's OnePlus not following Google's mandated instructions on how to properly initialize and configure a new device that will be running A10, because they (OnePlus) rushed it to market. They didn't set up the partition tables properly to work with the new dynamic partitioning in A10 for a start.
A10 and A11 are part of Project Mainline which allows Google to update important parts of the phone transparently without having to wait for an OTA from the manufacturer and/or carrier. But because OnePlus didn't properly set up the device for A10, the transparent updates don't go over very well...and there is no way to fully undo them even with the MSM tool.
The blame solely lies with OnePlus as no other devices launched with A10 have this issue. OnePlus didn't follow the "basic" instructions available for the entire planet to see on Google's Android dev website. Google's only mistake was certifying this piece of crap.