Original shield tablet - Recent update has killed my right speaker? - Shield Tablet Q&A, Help & Troubleshooting

Hi
I have the original shield tablet running 6.0.1 build number MRA58K.40827_726.6502 software version 4.2(24.3.68.8). I recently updated the software and for some reason the right (or bottom) speaker no longer works (headphones work tho). This tablet is like new, pristine condition and was sent out as a replacement as the old one was a fire hazard, so a bit gutted. I noticed in the recent change list there was something about sound, so I am hoping its software related. Any ideas if its possible for me to roll back the software without having to wipe the tablet? Thanks

You can roll back, but you'll need to be familiar with TWRP, rooting, fastboot, the like.

Updates are vicious, in general. Why trying to fix something that works; for you?

Related

[Q] Iconia A100 Headphone Issue (3.2.1 made it worse)

Like everyone else I had the headphone issue, where sound would play through both the headphones and the speakers on the A100 unless plugged in at a certain time. I got sick of waiting for the 3.2.1 update to become available to me, so I manually updated to Acer_A100_1.014.08_COM_GEN1 (British region apparently) and did an OTA update to the next 2 available updates. Now my headphones aren't recognised at all.
Is this due to some sort of regional hardware difference (Australian A100)? Have I probably accidentally caused some sort of hardware issue in the last few days and this is coincidental?
I would find a way to go back flash your region model back to stock firmware and see if that fixes the problem. Then update like normal and see if the problem occurs with the new updates. Sounds like software issue. It didnt happen to me but then again I havent played around with mine in a couple weeks.

[Q] Screen flickering/shifting/cycling up

For 6 months, my Nexus 5 have been the best thing that happened to my life. But after the 4.4.3 update around Jun13, this display issue appears. Display keeps shifting upward in a continuous manner. For example, the keyboard is now in the middle, and the top part is below, it keeps flickering and moving. So I thought it may be a software bug since it coincided with the update (and no, I did not drop it). I tried all (factory reset, turn auto settings off, Developer options settings) to no avail. I contacted Google support and after a few emails, they told me to contact Japan support team. I don't know anyone from Japan. (Actually I do, but when he called them, the Google person couldn't speak English and my friend can't speak sufficient Japanese). (Note: A friend of another friend bought this phone from Google Store Japan)
So I thought, wth, let's open the back, maybe there're loose connections, like the battery or something. But now the adhesive is tampered with, a small dent in the case (due to the very strong adhesive) and the back does not pop completely back. One corner is a bit loose, so there's no fooling them that I have opened it.
I updated to 4.4.4 and new issue, the display is gone, just backlight. I managed to fix this eventually. Now I'm back to 4.4.2, and the display is still shifting. During bootup, Google logo is stable, but the next animation is shifting. Bootloader is stable, but sometimes it moves up a grid after I press a button. So I assume that the display moves when the system processes something.
So my conclusion now is that this is probably hardware/GPU issue. Or is it? My warranty is as good as void already since I can't communicate with Japanese, and since I opened the back, it really is void already. I have 2 immediate plans of attack: 1) flash a custom rom, if software issue; 2) buy a triwing screwdriver to check the back, if loose hardware.
Any thoughts?
You have answered your questions already m8.. If I were you, I would find someone who can speak Japanese and tell them to contact Google support and act as a interpreter.. I'm sure you will find someone in your workplace.
Since you've opened up the back and damaged the device to a point where it doesn't pop back, the warranty is gone most probably. But I would still contact Google first and then go-ahead with tampering the hardware.
- Sent from an IceCold Hammerhead!
tsuwariwarirap said:
For 6 months, my Nexus 5 have been the best thing that happened to my life. But after the 4.4.3 update around Jun13, this display issue appears. Display keeps shifting upward in a continuous manner. For example, the keyboard is now in the middle, and the top part is below, it keeps flickering and moving. So I thought it may be a software bug since it coincided with the update (and no, I did not drop it). I tried all (factory reset, turn auto settings off, Developer options settings) to no avail. I contacted Google support and after a few emails, they told me to contact Japan support team. I don't know anyone from Japan. (Actually I do, but when he called them, the Google person couldn't speak English and my friend can't speak sufficient Japanese). (Note: A friend of another friend bought this phone from Google Store Japan)
So I thought, wth, let's open the back, maybe there're loose connections, like the battery or something. But now the adhesive is tampered with, a small dent in the case (due to the very strong adhesive) and the back does not pop completely back. One corner is a bit loose, so there's no fooling them that I have opened it.
I updated to 4.4.4 and new issue, the display is gone, just backlight. I managed to fix this eventually. Now I'm back to 4.4.2, and the display is still shifting. During bootup, Google logo is stable, but the next animation is shifting. Bootloader is stable, but sometimes it moves up a grid after I press a button. So I assume that the display moves when the system processes something.
So my conclusion now is that this is probably hardware/GPU issue. Or is it? My warranty is as good as void already since I can't communicate with Japanese, and since I opened the back, it really is void already. I have 2 immediate plans of attack: 1) flash a custom rom, if software issue; 2) buy a triwing screwdriver to check the back, if loose hardware.
Any thoughts?
Click to expand...
Click to collapse
It is incredible, i have exactly the same problem and i did the same as tsuwariwarirap did. So if it is the same issue could be a kind of software problem? Or maybe all the nexus5 hardware will have issues with 4.4.3 or 4.4.4 ?
shevaperu said:
It is incredible, i have exactly the same problem and i did the same as tsuwariwarirap did. So if it is the same issue could be a kind of software problem? Or maybe all the nexus5 hardware will have issues with 4.4.3 or 4.4.4 ?
Click to expand...
Click to collapse
It's a hardware issue. A software update can't cause the flex cable or the display to go bad like that. If you have flashed back to fully stock and still have these issues, your only option is to replace the damaged parts.
Hi, do you mean this kind of issue
How did you solve this?!

Generic Android 5.1.1 MTCD Navigation Radio Install for BMW e46

Last month, I found this this Android 5.1.1 Headunit on Aliexpress for $227 shipped. I decided that the price was low enough to take the risk and purchased. The vendor's store is TONGTAI HONGKONG INDUSTRIAL CO.,LTD I am not endorsing the vendor, I didn't need them for any support yet, but I assume people will ask due to price.
Today was the first nice day since I got it, so I did the install this morning. I'm not going to recreate the install here, as there are already many for the Eonon, Dynavin, Avin, and others. This is just like those. I will note where I came across anything I wasn't expecting below.
A couple of points, I did not install a backup camera. My E46 is a Cabrio, and visibility is fine, I just don't think the benefits are there for me. Additionally, DVD is not important so I didn't check that out. I do want a working Radio, Bluetooth Calling and streaming and Navigation. This unit is doing all of that.
Opened Box
Retail box - I've seen other units that have the identical packaging
As Packed
Parts laid out
Parts laid out 2 - Note- connectors for the early and late radio's and early and late antennas. My car is one of the 2006 330's, and one of the last off the line.
Closer pic of unit - These look exactly like every other unit on the market.
Navigation SD card included - I read a lot of different solutions on where to put the GPS antenna. I was going to put it in the spot behind the instrument cluster, but BMW already had a factory installed antenna there. I guess by 2006, it was cheaper to put the antennas in all cars (like the factory Bluetooth). I used the metal cross bar above the radio. The antenna has a magnet on the base and i just sat it on top, it won't move. Reception, for me, is fine.
Back of unit. Cleaner than many - Note On many of these units the can-bus plugs into the back. I have been told that that makes fit difficult because of the amount of wires back there. The can-bus came off a pigtail on the mail unit and was easily tucked out of the way.
Another pic of the back of the unit - Note the white input plug under the antenna in. Those were for the RCA connectors for pre-amps. It wasn't needed it this install, the factory harness took care of everything, left those pigtails out.
Top with wiring diagram - All I did was remove the screws and plug it in, I didn't have to refer to any wiring. I will say I had trouble getting the adapter to line up with the factory plug. I almost broke the harness side. Not sure why it was so hard to align, but eventually it did.
Climate controls moved to the lower spot -Here are the climate controls moved into the lower section. I got a used navigation bracket off eBay for $20. The lighter clips were broken on one side, but not off. I had to use a cable tie to "lock" it in. If I had caught that before install, I would have swapped the lighter for a USB
Unit Installed
Radio Screen
Bluetooth Phone Screen
System Screen - Originally this was on a July MCU release, when I went into the about screen, it offered an update. An old ROM was on the Nav Card, and I overwrote the newer ROM with the older version. I sent the vendor a message to see if they can send me the link to the newer one. That said, I am not having an issue with this one.
Here is a walkthrough of it live. The video stops when I use bluetooth, not because of the headunit, but my phone stopped recording when making a call.
https://youtu.be/Vtv2tJte5oQ
All said and done I am very happy with this unit based after installation. I have been reading many people who have issues, so maybe I got a "good" one, or maybe issues are yet to come. If you have any questions, fire away.
Well it was great for 2 hours. Screen is unresponsive now. Any suggestions...
Sent from my iPad using Tapatalk
Sorry I cannot help with the unresponsive screen, but I have a question
For the few hours you enjoyed it, how was the display in direct sunlight?
-=Jeff=- said:
Sorry I cannot help with the unresponsive screen, but I have a question
For the few hours you enjoyed it, how was the display in direct sunlight?
Click to expand...
Click to collapse
It was ok, this morning driving to work their was a good bit of glare, but still very readable. I will try it with the top down and see what it can take would assume that would wash it out.
Pretty sure a matte screen protector would solve any issues with glare. Something like this should do for my screen
http://www.staples.com/Iessentials-...ctor-For-7-inch-8-inch-Tablets/product_210060
I have a car with a targa roof.. I tried a matte protector with my newsmy NU3001 and it did not help. I really like the idea of the Touch screen UI but I think I am out of luck for seeing it on the screen. I have a MTCD unit too but have not tried it yet.
Video of operation w/o working screen
https://www.youtube.com/watch?v=8lGyAQ0rZlg
Pattond said:
Video of operation w/o working screen
https://www.youtube.com/watch?v=8lGyAQ0rZlg
Click to expand...
Click to collapse
Have you tried to reflash the unit? Factory ROM for you unit should be available somewhere on the forum. It looks like it lost touch calibration.
f1x said:
Have you tried to reflash the unit? Factory ROM for you unit should be available somewhere on the forum. It looks like it lost touch calibration.
Click to expand...
Click to collapse
I thought that was exactly what happened. I reflashed both ROM and DMCU, but didn't help. The vendor sent my video over to his engineer and they are going to get back with me today. I am thinking its a physically problem with the screen like something worked its way loose or the heat of the day effected it.
System Re-Flash from recovery mode.
I just went into recovery mode and did a full reflash again hoping it gives some information about what is happening. I videoed it, and it will (in about an hour) be available here. https://youtu.be/9Q70WxcMzzg Warning beginning to end its 8:21. May be of use to someone trying to understand how to get into recovery mode and reflash
I went ahead and typed the messages on the screen after selecting "Update system/mcu image from sdcard and clear all" all the text that followed is below. I see an error came up in parsing the backup, not sure if that effects the loading or not, it seems to be running the same
__ Update rkimage...
Installation rkimage start.
Finding update package.
===UPDATE RKIMAGE===
Find and check firmware...
!!! Please KEEP your USB cable or DC-in connected !!!
Check parameter...
Update recovery.img...
Check recovery.img...
Update boot.img...
Check boot.img...
Update misc.img...
Check misc.img...
Update kernel.img...
Check kernel.img...
Update system...
Check system...
Update oem.img...
Check oem.img...
Update backup...
Check backup...
E:1 parse errors
Handle script error! ignore...
Copy Bootloader...
Installation complete.
Update rkimage complete.
Installation rkimage success.
Formatting /data...
Formatting /cache...
Formatting /mnt/internal_sd...
Installation mcuimg start
Installation mcuimg aborted
Installation mcuimg start
-----MCU Version :V1.66a
-----MCU customer : KD
Installation mcuimg success.
System will now power off/
Rebooting...
Click to expand...
Click to collapse
The vendor got with his engineer and is pretty sure it is the touch screen itself that is the issue, not the software (I was thinking the same thing). Their guess is the cable has somehow worked loose and want me to open the unit and check the cable connections. He sent me a photo of what to look for (below). Any recommendations/warnings before taking this thing apart tonight?
Thanks, this thread may be too much me, but if someone else is having the same issues, I want to make sure there is somewhere they can look for troubleshooting and hopefully an eventual solution.
BTW, so far vendor communication has been really good.
Hi, have you been able to fix it? I'm thinking of getting the exact same head unit (as opposed to universal one with all the extras I would need, like fascia, cage, harness)
schriss said:
Hi, have you been able to fix it? I'm thinking of getting the exact same head unit (as opposed to universal one with all the extras I would need, like fascia, cage, harness)
Click to expand...
Click to collapse
Mailed I back, they received today and are returning a new unit. Will update when it arrives
Sent from my iPad using Tapatalk
I got an update from the vendor, and the issue was a touchscreen cable worked loose. Absolutely a problem with the assembly in China, and probably something I could have fixed if I was skilled in electronic repair. My new unit is on the way here.
Sent from my SM-G920I using Tapatalk
I should be getting mine delivered tomorrow, hopefully no loose cables
Are there any benefits buying a eonon unit compared to this one? Are they from the same factory you think? The new eonon has Bluetooth 4 compared to others? How can that be if they are all from the same manufacturer?
I suspect they all come from same factory, Eonon, Joying or no brand - the only difference seems to be the software.
I'm quite happy with my "generic" unit, so far so good. But didn't test bluetooth more than just paired with my phone, no calls yet or any obd2 readers used.
My main use is navigation and that seems fine, but my phone seems to be getting a bit more accurate gps lock according to gps test apps.
PattonD, have you tried a Bluetooth call? How was it? Did you use the internal mic or an external?
One of the most important features for me...
The unit you bought is very interesting.
I got the unit. I tried the unit at home. Internal mic seems fine.
However, how is the reverse camera installed? Is reverse signal coming from the canbus system or must i cut the brown cable (cable 8, back car cable) and connect it to the reverse lights?
it is the plug
I'm not really sure what you mean mate

Bluetooth not working

Not sure if this is just my phone but bluetooth has not been working the last update of 7.1.2 and Android O the most recent version. When I toggle bluetooth it does not activate and i have tried clearing out the cache. Not sure if this is a software issue or possible related to hardware. I did have a good drop with my phone although nothing on the exterior appears damaged. Not sure if anyone else is experiencing the same thing.
Just RMAing the phone. It appears that it is only my phone doing it. Actually Google's customer service is really good. I'm glad I bought from them.
I had a Galaxy S4 from Samsung in 2013 and the battery ended up swelling and I called them for a replacement which they would not replace, but would thoughtfully sell me a new battery. Then they lost $5.3 billion from their Note 7 recall due to the battery and I was very happy and laughed.
Was this just the phone audio in your car by chance? I have a similar issue and have an open case with google about it.
marc.ientilucci said:
Was this just the phone audio in your car by chance? I have a similar issue and have an open case with google about it.
Click to expand...
Click to collapse
No it's definitely the phone. I have my Nexus 5x right now on 8.0 and it's working fine. Nothing wrong with the software.
I use Android auto as well and it's working fine. There's something wrong with the hardware component in the phone most likely. I have a 2017 Honda Civic
Did an RMA and sending it out.
mikeprius said:
No it's definitely the phone. I have my Nexus 5x right now on 8.0 and it's working fine. Nothing wrong with the software.
I use Android auto as well and it's working fine. There's something wrong with the hardware component in the phone most likely. I have a 2017 Honda Civic
Did an RMA and sending it out.
Click to expand...
Click to collapse
sorry - let me clarify my question. Was bluetooth media working and just not phone calls over bluetooth? I have a 2017 honda civic as well (LX version so a dumb head unit) and only having bluetooth phone call issues. I can play spotify and other stuff like youtube just fine.
marc.ientilucci said:
sorry - let me clarify my question. Was bluetooth media working and just not phone calls over bluetooth? I have a 2017 honda civic as well (LX version so a dumb head unit) and only having bluetooth phone call issues. I can play spotify and other stuff like youtube just fine.
Click to expand...
Click to collapse
No. Bluetooth would not activate at all so nothing worked. When i toggled the switch it would not turn on and scan for bluetooth. It appears that my situation was much significant as nothing worked. My replacement should be here tommorow. For your stock rooted set up did you just boot into TWRP then flash the latest SU ? Lately I've been running stock, so I don't know what the most recent form to root is for 8.0
Last time I rooted was like April or May of this year, but I just booted the TWRP image, flash TWRP, then flash SU
I've been stock rooted for some time but for the 8.0 update I rooted with SuperSU SRS3 via TWRP. Google had me actually grab a bug report and shoot it over to them along with information about the bluetooth radio manufacture of the car. I am cool with continuing to help them out. anyway, thanks for your feedback and i hope the new one works!
Got my new pixel replacement. It was the phone, I'm on the latest 7.1.2 update and it's working fine. The refurb looks brand new, you can tell it's a refurb by the charging port, but the rest of the phone is virtually new. No scratches on the glass or scuffs on the metal body. Compared to the current pixel I have with multiple long scratches along the front glass screen, even though it's a refurb its still in much better condition than my current Pixel.
I noticed my night light is super orange the screen is compared to my current Pixel. I think this is an issue related to earlier batches of the Pixel. It's just very orange with the night light but given the condition my current pixel is in, I'll still take it over my current one.

Android 10 obliterated my phone.

As the title says.
My phone has no longer been the absolute powerhouse that it once was since Android 9.
I'm aware many of you will spout that "U shld downgrid bak 2 vershion nooin?!?!"
Believe me I have.
The issues are still present.
So my issues are as follows:
My camera app is completely broken on version 10.3.3 (downgrading fixes this stupid issue / rooting removing and replacing the app)
Light sensitivity / screen rotate module is broken / turned off as most apps are telling me that it's non existent / not plugged in. (Downgrading / rooting / custom ROM does NOT fix this issue) I've tried all the usual crap with this case.
The keyboard issue
The stupid bar at the bottom that we can't utilise as we AREN'T PIXEL DEVICES ONEPLUS. I've heard a few people say to me that it's there for additional features and that we should get used to it. Well contrary to that information is the fact that the OnePlus team "fixed the keyboard bar" on the latest Beta ( which is now redundant ((cheers onepiss))
Battery related issues (Which can be fixed with downgrade / ROM)
To me it just seems like the Dev team gave up trying to optimise every OnePlus 6 phone they have out there as I seem to be a very specific case. I wanted this phone to last me at least four years but it feels like the dodgy updates are ensuring my regrets with buying a OnePlus phone.
:silly:
By mistake i did try it....
Aplications crash.....freeze.......
In resume:
I nuke it, and return to 9.0.9 full rooted and unlocked.
My best mode at this time would be a new physical battery....
Glad I'm not the only one!

Categories

Resources