Hi
I have a peculiar problem with my MTCB-KLD6 head unit, running Android 5.1.1, MCU V2.86
1) During boot, if I hit the reverse gear, the backup camera view appears.
2) Once Android completes the boot, if I hit the reverse gear, the backup camera no longer appears.
3) However, if I keep the gear in reverse from boot till completion of boot, then the proper backup app appears with the backup grid. However, no buttons on the HU works and I'm stuck with the view.
Questions:
Q1: Anybody knows what is the issue?
Q2: Anybody knows what is the Android activity name for the reverse camera view app?
(I might try writing a simple android app to launch that activity manually and see if that works)
Notes:
1) I've tried installing malaysk firmware 5.1.1, but the same problem persists.
2) I'm using the reverse signal cable. I've tested the voltage and it reads 12+ volts when I hit the reverse gear. So wiring seems OK.
3) It used to work perfectly, but went bad recently.
4) Since it works during boot, my only assumption is that this is a purely software problem.
Thanks!
kenfoo said:
Hi
I have a peculiar problem with my MTCB-KLD6 head unit, running Android 5.1.1, MCU V2.86
1) During boot, if I hit the reverse gear, the backup camera view appears.
2) Once Android completes the boot, if I hit the reverse gear, the backup camera no longer appears.
3) However, if I keep the gear in reverse from boot till completion of boot, then the proper backup app appears with the backup grid. However, no buttons on the HU works and I'm stuck with the view.
Questions:
Q1: Anybody knows what is the issue?
Q2: Anybody knows what is the Android activity name for the reverse camera view app?
(I might try writing a simple android app to launch that activity manually and see if that works)
Notes:
1) I've tried installing malaysk firmware 5.1.1, but the same problem persists.
2) I'm using the reverse signal cable. I've tested the voltage and it reads 12+ volts when I hit the reverse gear. So wiring seems OK.
3) It used to work perfectly, but went bad recently.
4) Since it works during boot, my only assumption is that this is a purely software problem.
Thanks!
Click to expand...
Click to collapse
This is a very old topic and I am having similar issues with a MTCD unit. Did not see any reply for the topic. Have you resolved the problem?
Hi...i have similar...
Mine sometimes works..sometimes not...
After 5mins..or not...
Its totally random
Hello, when installing my android 8 MTCD in my VW Caddy, I connected the camera power to reverse light. But only when ignition was on, motor off, i had an rearview image. The seller told me to install a "filter adapter for camera" between the powercable from reverse light to the camera and that solved the problem..
Related
Hi,
The last few days my dialer has been ridiculously slow in making a call. Typing in numbers is fine and accessing the call history is also fine but if I touch an entry to start a call it takes anywhere from 10-20 secs for the call to start. Oddly enough this issue is not present when using car dock mode.
Has anyone come across this before and found a solution?
BTW I am on stock 4.4.2
Thanks
I should probably mention what I have tried already
- Deleted call history
- Cleared data and cache from the phone app
- Turned off a tasker profile I had that involved dialing a number
- Uninstalled recently installed apps
- Turned off fast boot and restarted (this actually helped for a short while but it has reverted)
Any other ideas? I am reluctant to do a hard reset but if nothing else works then I might just do that or upgrade my phone since I am due an upgrade soon
Deanicus said:
I should probably mention what I have tried already
- Deleted call history
- Cleared data and cache from the phone app
- Turned off a tasker profile I had that involved dialing a number
- Uninstalled recently installed apps
- Turned off fast boot and restarted (this actually helped for a short while but it has reverted)
Any other ideas? I am reluctant to do a hard reset but if nothing else works then I might just do that or upgrade my phone since I am due an upgrade soon
Click to expand...
Click to collapse
did you try factory resset??
jujak82 said:
did you try factory resset??
Click to expand...
Click to collapse
No, not yet. I am hoping to avoid that if possible
Anyone else have any ideas? The issue is not with the dialer but quite literally with the phone app although as I mentioned in my OP, if I select a number to be dialled from the dialer in the car dock app, it works fine. Very perplexing!
For anyone who might be experiencing the same issue, whilst I have not fixed it I did find that if my phone is connected to a network (either via wifi or mobile data) the issue disappears. I don't know why that happens but it is a least a bit of a workaround
Hi, I looked for other threads in which someone else faced the same problem, but I have not found any answer nor good solution.
The problem is that the screen of my S3 MINI turns on automatically.
I changed the ROM twice (2 different ones, CM 10 and 11), so I don't think the reason is a single "defective" app: I believe in another explanation, according to which the reason would be a broken pin inside the microUSB port of the smartphone.
That pin let turn the screen on like if it was put /unput in charge.
The Question: is there a ROM / KERNEL / APP that prevent the screen from making this error?
How much is hard to edit a rom/kernel in order to avoid that the screen lightness wolud depend from that pins?
And if the reason is a defective app, has someone ever discovered which one is?
I'm afraid it's a way to screw the consumer: this automatic and uncontrollable activity of the display destroys the battery life. It's like if the smartphone is broken: you should change it.
I cannot accept that a 440€ smartphone acts in this way. I'll never buy a Samsung product.
I won't talk about the home button broken (could someone give me an advice on which app that simulates the virtual buttons is better?).
Thank to you all!
Pietro C.
UPDATE 28/12/2014 h14:34 ITA
I did a screenshot and I also photographed with a camera the display while it was showing the CPU activity. I noticed something (an app? a opened file? a function?) that appears only when the display turns on automatically. Some green words. I'm going to upload photos.
UPDATE 16:30
Cannot upload photos. Here are the scripts that appears on my phone:
com.android.system
surfaceflinger
system_server
com.teslacoilsw.launcher
kworker/u4
com.android.phone
com.facebook.katana
com.facebook.orca
kworker/2
kworker/6
kworker/1
irq/72...
irq/474
mmcqd
ueventd
rild
mediaserver
admsrv
org.cyanogenmod.voiceplus
dhd_dpc
com.google.processo.location
org.whispersystems.whisperpush
com.textra
com.google.android.googlequicksearchbox.search
AND the last 5 listed down here are the green scripts that appears only when the phone turns on automatically.
migration/I
kworker/I:0
ksoftirqd/I
watchdog/I
kworker/I:I
UPDATE 03.01.2015
I fixed the issue at the moment. I installed CM 11-20140823 after wiping and formatting data.
I installed the lowest number of Google Apps (here I chose Nano Modular Package: http://forum.xda-developers.com/showthread.php?p=44417509#post44417509 ).
I'm quite sure it's a issue caused by a unidentified google app, because when the phone was "clean", the screen kept turned off ALWAYS, unless I pressed the accension button.
Now that I installed ONLY Google Play and Google Services, the screen is ok.
So I will download only the most useful Google Apps, hoping that won't find the one infected (if I'm right about the cause of the automatic flash of the screen).
I also discussed about this issue here , and I discovered that many people are searching for a solution.
Maybe someone could confirm or contradict my theory.
Workaround that works 100% of the time for those having trouble connecting.
Unlock phone and turn on car or head unit. Note you should have android auto installed already before this will work. Plug in the cable to your phone and you will hear the link sound and the screen on your phone will flash off for just a second. As quickly as possible once the screen goes black on your phone uncable the phone and reconnect it. I know this sounds janky, but it really works. You can tell it is working by the screen on your head unit going black in the background and you will see the android auto icon sI have tried all suggested fixes and this is the only one that works 100% of the time. It also does not take over the telephone's display so you can navigate to other apps and still have android auto running. It is quick and gives you the best of both worlds. I almost returned my 2016 gti due to the frustration from this issue, but now it is no big deal.
Hope this helps guys and gals.
No. For what I read , the only API available for 3rd parties are to send messages and music, and that, using google interface. No other developer can do anything with AA.
My N6 is running Android 7.0, have not had problems until a couple of days ago.
The right half of my display started scrolling while, the left side of the display was normal. I powered it off and back on a couple of times and, the issue was still there; I panicked and did a factory reset from the "Settings" menu hoping that would solve the problem, it did not; I still had a jacked up display.
Is this a failure mode that anyone else has seen?
I powered the phone off and, turned it back on with the volume control button pressed and, it booted into safe mode(?) then, I toggled the mode to "Restart" and, upon restart, my display was normal. This was not the end as, it will occasionally be split screen when I unlock it. I have discovered that sometimes if I receive or make a call the display will return to normal, if not, I just power cycle it into the safe-recovery mode (but not do anything else) then toggle to restart and, it's all good until next time.
Is it possible that another device (blue-tooth) in close proximity could cause my phone display to act up?
queensgate555 said:
My N6 is running Android 7.0, have not had problems until a couple of days ago.
The right half of my display started scrolling while, the left side of the display was normal. I powered it off and back on a couple of times and, the issue was still there; I panicked and did a factory reset from the "Settings" menu hoping that would solve the problem, it did not; I still had a jacked up display.
Is this a failure mode that anyone else has seen?
I powered the phone off and, turned it back on with the volume control button pressed and, it booted into safe mode(?) then, I toggled the mode to "Restart" and, upon restart, my display was normal. This was not the end as, it will occasionally be split screen when I unlock it. I have discovered that sometimes if I receive or make a call the display will return to normal, if not, I just power cycle it into the safe-recovery mode (but not do anything else) then toggle to restart and, it's all good until next time.
Is it possible that another device (blue-tooth) in close proximity could cause my phone display to act up?
Click to expand...
Click to collapse
So weird, but same thing has been happening to me the past few days. But I have a justified cause. It started immediately after installing Franco Kernel.
Sent from my Nexus 6 using Tapatalk
queensgate555 said:
My N6 is running Android 7.0, have not had problems until a couple of days ago.
The right half of my display started scrolling while, the left side of the display was normal. I powered it off and back on a couple of times and, the issue was still there; I panicked and did a factory reset from the "Settings" menu hoping that would solve the problem, it did not; I still had a jacked up display.
Is this a failure mode that anyone else has seen?
I powered the phone off and, turned it back on with the volume control button pressed and, it booted into safe mode(?) then, I toggled the mode to "Restart" and, upon restart, my display was normal. This was not the end as, it will occasionally be split screen when I unlock it. I have discovered that sometimes if I receive or make a call the display will return to normal, if not, I just power cycle it into the safe-recovery mode (but not do anything else) then toggle to restart and, it's all good until next time.
Is it possible that another device (blue-tooth) in close proximity could cause my phone display to act up?
Click to expand...
Click to collapse
It is a known hardware issue in some N6 phones, some have it and it only shows up on certain rom / kernel combos, even stock. One thing that helps is to use the interactive kernel governor and/or the down sampling factor. Of course you will need a kernel manager app for that.
https://forum.xda-developers.com/showpost.php?p=63249802&postcount=4602
Pkt_Lnt said:
It is a known hardware issue in some N6 phones, some have it and it only shows up on certain rom / kernel combos, even stock. One thing that helps is to use the interactive kernel governor and/or the down sampling factor. Of course you will need a kernel manager app for that.
https://forum.xda-developers.com/showpost.php?p=63249802&postcount=4602
Click to expand...
Click to collapse
That's good to know.
I inserted the Bluetooth question because, coincidentally or not this issue presented when I acquired a wristwatch ($19.00 from China) that connected to my phone via Bluetooth, It had it's own fitness app which I installed (which did not work). To me, there seems to be more "connection" than expected as, the fault thing only seems to happen when the watch was powered on (but not even connected via Bluetooth). If there was a bug caused by the companion app, that should have been taken care of by the factory reset.
I'm going to do some "scientific testing" by, not powering on the watch for a week and see if the issue reoccurs. Meanwhile, I will read up on kernel manager apps.
I've since flashed stock pn, and now elementalx. It's not acted up yet. Seemes to be a better performance kernel. We'll see how battery is. Sorry to hijack your thread!
Sent from my Nexus 6 using Tapatalk
queensgate555 said:
That's good to know.
I inserted the Bluetooth question because, coincidentally or not this issue presented when I acquired a wristwatch ($19.00 from China) that connected to my phone via Bluetooth, It had it's own fitness app which I installed (which did not work). To me, there seems to be more "connection" than expected as, the fault thing only seems to happen when the watch was powered on (but not even connected via Bluetooth). If there was a bug caused by the companion app, that should have been taken care of by the factory reset.
I'm going to do some "scientific testing" by, not powering on the watch for a week and see if the issue reoccurs. Meanwhile, I will read up on kernel manager apps.
Click to expand...
Click to collapse
Well, so much for "scientific testing" and wishful thinking.....didn't take long to eliminate the wristwatch, now to fix the problem.
.
*SOLVED*
Hi all,
Have my Galaxy S10 SM-G9730 Dual Sim (unrooted) for about 18months now and has never skipped a beat.... until the new One UI 3.0 update that I got a few days ago.
After a restart everything works fine then after 15min-2hrs I will lose auto rotate, screen brightness is also less responsive (proximity sensor seems to be ok). Toggling auto rotate/adaptive brightness on/off does nothing.
Same issue across all apps (Youtube, Camera, Messaging etc.)
Going to the *#0*# - SENSOR menu shows me that:
Accelerometer Sensor is responsive (x, y, z axis all change to reflect movement) but the "IMAGE TEST" doesn't rotate the image of the dog. Should it?
Gyroscope Sensor doesn't move at all, is it supposed to? "GYRO SELFTEST" shows a PASS.
I downloaded the app "Sensor Test" and most of the sensors give me the error:
"This sensor doesn't report any readings, seems you have error with sensor service in device firmware"
I have tried the following:
- Toggle auto rotate on/off.
- Restart phone (using power button - restart & using power & Vol down combo)
- Cleared cache from Bootloader menu.
- Settings - Apps - Reset app preferences.
- Factory reset (using both settings - Factory reset & using bootloader factory reset)
I have a feeling it is an app that isn't updated to run on One UI 3.0 but I have no way of finding the guilty app.
Called Samsung who were no help (try restart, try factory reset, send it to us but we will charge you as Samsung don't have international warranty , even though yes we agree that it was our update that probably caused it)
Seemed to be good for about 10 hours after the factory reset but came came again,
Anyone come across this and found a way out?
*edit* just checked after restart and Gyroscope Sensor shows values after restart (while auto rotate is working), This leads me to believe it is 100% the gyroscope at first which in time leads to the accelerometer also not working.
*edit x2* well I've just restarted my phone then went through every single app 1 by 1 (downloaded and bloatware) and checking for rotation after each app launch, that is: launch app, test rotation, close app, test rotation and do that 172 times!! I task killed maybe 5 times during the process..
after opening every app I still have auto rotation which leads me to believe its some system background process and not a 3rd party app issue. Damn..
Is there any way for me to monitor these? or monitor sensors stopping functioning?
*SOLVED* See post #6 below
I have same problem. After updating to one ui 3, the rotate sensor stops working after a while and only a reboot helps. Galaxy Note 10+ N9750 (snapdragon). Can't find fix yet
Same problem, autorotate feature is not working after software update (Samsung Galaxy S10 SM-G9730, One UI 3.0, Android 11)
Same thing here! If you read this please send a bug report to samsung we we can get their attention.
Didn't see anything on Reddit about it may be fixed on 3.1
Let's find out
*SOLVED*
Ok then, finally seem to have this sorted.
What I ended up doing was:
Downloading the latest firmware (the firmware that caused the problem) using frija.
I took a complete backup onto my laptop using Smart Switch.
I then flashed the firmware using Odin but again after a few hours sensors started to drop off again.
I then flashed the firmware again using Odin but this time I performed a nand erase while flashing.
Pushed my backup back onto my phone from my laptop using Smart Switch.
And hey presto!
This seems to have sorted it, I'm now well into day 2 and still working 100% which is the best it has been since the OTA firmware update.
Hopefully that will help others
My phone is doing this as well, I've got a US unlocked phone overseas as well. I followed your instructions and did the nand erase but after 2 days the sensors started messing up again.
tkwesa said:
My phone is doing this as well, I've got a US unlocked phone overseas as well. I followed your instructions and did the nand erase but after 2 days the sensors started messing up again.
Click to expand...
Click to collapse
It's the firmware..samsung is releasing buggy firmware..received 3.1 update yesterday... seems to have solved proximity and autorotate issue..smartview and NFC still not working for me.
So they force us into an update that breaks the phone and don't let us go back to the previous version of the software? That doesn't sound right.
Another marketing scam to get us on to the S21.
Same problem with S21 Ultra after Android 13. Rotate sensor flips 90degrees after some day or two of use. Now it was messenger that was active when the flip came.....
Any solutions apart from reflashing via 3rd party? That's quite a job to reset the phone.
Thanks!