Hi all,
i bought a new head unit abd have installed it last weekend on my car. First hours the new HU runned well, so i updated to HAL9k Rom 4.0.0. Approx 1h later the HU went down to a black screen. I checked power and fuse, everything seems to be allrigt, my old radio run without any issue when put it back into the car. The day after i have tested the new Pumpkin, again black screen - but after 10min the HU get booted and everything worked as there have never been something.
When i went to my car today after some minutes the HU shutdown again (has been signaled on the screen), since this there is again a black screen
details HU
PX6
MTCE_HT_V3.30_1
Kernel 4.4.167
rk399-userdebug 9 PQ2A.190305.002 20191104.1620055 test-keys
what i've done so far:
- pressed reset to reoot - no success
- pressed reset longer then 1min - no success
- pressed power button longer then 1min - no success
- put SD card with imcu.img ans hal9k update.zip in the HU, pressed/hold power button then presse reset and release both - button lights blink on time
no recovery mode, no reboot, only if i press reset one time blink on button lights
any ideas?
best regards
also tested: press/hold Power and reset, release reset after 5sec while keep power pressed: no success
got an update from my dealer: connect batterie pülus with acc direct an radio plug, HU start after this. It seems to be an issue with the external canbus box with to less power on ACC cable
Related
Hi Everyone,
I know its a few threads about how to unbrick Advent Vega and how many threads is that many ideas how to do it.
I was running ViewCOMB 3.2 built 5.1 and everything was ok, but ive installed Rom Manager from Market, and tried other rom (wrong one ).
After reboot nothing is happening, i mean when i press power button for ok 10 sec and then short press again, screen is on black with backlight for about 1 sec and keep coming off.
Ive tried to turn into boot mode (2sec. back + 2 sec. power) about 1000 times already with power cable on and off, but nothing happening.
I have drivers installed on my laptop (had installed custom rom already).
I want to specify a few facts:
Is battery must be charged to full? or should start another try from flat?
If so, how to drain battery if tablet wont power up?
Is better to try with power cable on or off?
Some people saying about holding buttons for a 2 sec, other for 1 sec, what is right?
Any ideas?
Many thanks!
Finally after hours of pressing and holding power + back buttons I've sorted it.
- hold power button for about 10 sec. (to make sure device is off)
- hold back button 2 sec. (don't release)
- press power button till notification sound will come on.
Then had notification sound from Windows about new device connected. On my device list was Nvidia usb boot-recovery device.
Before last try I've charged battery to full (blue light) then disconnected power cable. I couldn't do it with battery full and power cable in (strange).
I think the main hint is to make sure that device is off. Ive noticed that even if screen is off device might be running.
Hopefully this little explanation will help
okti said:
Finally after hours of pressing and holding power + back buttons I've sorted it.
- hold power button for about 10 sec. (to make sure device is off)
- hold back button 2 sec. (don't release)
- press power button till notification sound will come on.
Then had notification sound from Windows about new device connected. On my device list was Nvidia usb boot-recovery device.
Before last try I've charged battery to full (blue light) then disconnected power cable. I couldn't do it with battery full and power cable in (strange).
I think the main hint is to make sure that device is off. Ive noticed that even if screen is off device might be running.
Hopefully this little explanation will help
Click to expand...
Click to collapse
THAAAAAAAAAAAANNNNNKKKKK YYYYYYYYYOOOOOOOOOOUUUUUUU!!!!!!!!!!!!!!!!!!! I had the same problem and I thought it was bricked for like, 4ever, so THNX!!!
i had exactly the same problem last night when i asked CWM to do a backup and the screen went black and wouldnt switch on.
one way to tell if it hasnt powered off properly when its stale booting is to look under the black surround between the screen and the camera and you may see a faint blue light. Only viewable with about 5 deg viewing angle (so same as the screen LOL)
i found i could not get it into boot mode at all. No matter how many times i did it. Ending up taking the back off and pulling the battery and then trying again - guess what? Worked straight away first time!!!
I can only presume that when its in this stale boot state it isnt shutting down properly, even if the light is off etc. Although i did come across a post after sorting it that said sometimes it can take a 60 second press of the power button to properly shut it down when its in stale boot.
So now i'm back to standard modded stock rom 2.2 and its horrendous!!!!
Just finished downloading the beta ics rom exe - so gonna whack that on and have a play! Hope its as good as they say it is. If it isnt, then i'll put honeycomb back on.
I think that instead of pulling tha battery out you could also press and hold the power button for 9 seconds, right?
Gents,
I have just got a Xoom 2 16GB Wi-Fi only model and seem to be having a problem.
I have read the original Xoom tips & tricks thread and searched but want to clarify a few things...
On the Xoom2
1. The charging LED does not light. Apparently it only lights when the unit is powered off. Ok, I can accept that.
2. When plugged in, if I try to power my unit off it powers up again on its own.
I spoke to Motorola tech-support about this and they said that was "designed" behaviour. The unit will automatically power on when the charge level is above a certain threshold.
Is the above true? Does the unit have to be VERY low on battery before the LED will indicate that charging is taking place?
I'm rather confused as all of the above seems totally counter intuitive to me.
Any advice appreciated.
Yes you cannot charge the tablet while it is powered off, it will automatically turn on and charge.
Apparently they changed this in the latest software update but I have yet to test this out.
Sent from my Motorola Droid Xyboard 10.1 with Verizon 4G LTE
The behavior will change when you get the 3.2.2 update. There's a powered off charging mode for quick charging now.
Xoom 2 charging
Yes, my xoom 2 also turns on to charge! found this weird but it must be the case.
Hrm.
Ok so I've done more digging and it does say on the Moto website that the "on to charge" behaviour is normal.
I am keep to get mine updated to 3.2.2 however my "System Updates" option just tells me that my system is up to date despite being only 3.2
Furthermore, I had trouble powering my device up again. I had what seemed like problems straight out of the box but after speaking to tech support they told me to charge the unit for a while (like a few hours) and then give it a go.
I did this and still no joy. I called again and they asked me to try pushing and holding all three buttons (i.e. vol up, vol down and power) together for 15s.
After I did this the unit powered up, I managed to get through the setup procedures and have a little play.
Then I put the unit in my bag and left for home. I got home and the unit wouldn't power up. So I tried the reset and got presented with a funny menu (looked like a bootloader to me).
Not sure what I selected here but it booted albeit with some weird apps showing.
I rebooted again and now it seems fine but not sure it's actually charging!!!
I might have to send this unit back for a fresh one.
Ok,
I've narrowed down my problem. If the unit is plugged into the wall adapter it will charge and work as normal. If it enters standby mode the unit will power on when the power button is pressed
Great.
However, if the unit IS NOT plugged in and it enters standby the power button WILL NOT turn the screen back on. It will just sit there lifeless.
The only way to recover from this state is to "reboot" it by pressing and holding the 3b buttons (vol up, vol down and power) for something like 10-15 seconds until the bootloader menu is shown.
Here's the real kicker though, if the unit is on but SHUTDOWN using the power button pressing the power button subsequently WILL turn the unit back on (i.e. it will go through the boot process showing the Moto logo/circles animation).
But again, once powered on, if the unit enters standby the power button will not turn the screen back on.
What is going on here? Does it just sound like my unit is faulty and needs to be replaced?
Any help appreciated...
SF
Bump.
Anyone got ideas/suggestions regarding the power button/standby issue I am describing above???
have you fully charged it yet?
Yup.
I charged it for a good 8 hours + (overnight) and it still exhibited the same behaviour.
I think the power button is dodgy/intermittent and that is what is causing the issue.
Either way, I've RMAed the unit back to Expansys and am awaiting a replacement.
Hello, i own a Joying PX5 2Gb with Android 6.0.1 which I really enjoy and I have the fast-boot function.
I really like this, I start the car and within less than 2 seconds the head unit is ready.
But i don't get how this works, my car didn't start a whole day and the day after that it also powers on in 2 secs. how does it find its power to keep the head unit in stand-by ?
I can't power it on when my car isn't started so i guess there is no 12v without ignition, that I don't understand.
I also wonder - is this like the "Sleep" function on a computer? Will the units need a full cold restart every now and again to flush things out?
up
https://www.ubiquitous-ai.com/en/products/os/quickboot/
rigattoni said:
https://www.ubiquitous-ai.com/en/products/os/quickboot/
Click to expand...
Click to collapse
It is not the ubiquitous fast boot and it is not a cold boot hibernation method.
All head units have a hardware part (radio chip, AMP, bluetooth, MCU, USB, etc.) and an Android part. The FYT units (most Joying, some KLD, some FunRover, some Witson and a few more) bring the android part into deep-sleep, and switch off the hardware part completely.
If the non-android hardware parts would remain under power it would drain your car battery in 2-3 days, so that is completely switched off.
Keeping the android memory under power will last at least 30 days, but possibly 50-60 days.
That's why you have the constant power and "switch on/off contact" ACC+ wire (ACC= Accessory power. To power your accessories, whatever they are, which you only need with contact on).
If you switch off contact, the acc off is detected in the FYT units, generating a broadcast "com.fyt.boot.ACCOFF" (and "com.fyt.boot.ACCON" when contact is turned on). Some FYT apps stop "voluntarily". Other apps are killed by the system server (SofiaServer on Sofia, 000000_com.syu.ms on the PX5). And then the MCU only keeps memory under "power" using the constant power line.
Traditional hardware (AMP, radio chip) only take milliseconds to "be ready" when power is put back. Android 3-5 seconds (2 seconds is a very optimistic estimate from Joying).
maybe lineo warp, it creates a snapshot of the system that just booted and save it on SD, so for the next time, kernel has fully booted and inited, just the final part of the UI had to start.
https://www.lineo.co.jp/products/warp2.html
So my android head unit randomly stopped working. Basically it boots normally but then it says Optimizing apps 1 of 1 for like 5 minutes, then it turns off, boots again, optimizing apps 1 of 1. It just cycles indefinitely. I cannot seem to get it into recovery mode. I've tried holding reset, holding power, holding reset plus power.
My unit is a 7 inch Bondroad Android 5.1.1 2G. I didnt mess with it or anything.
If you need more info please inform me.
Thanks
Hi guys
I wanted to upgrade the user interface on my Android head unit. ( Carsara, Android 8,1,)
Started upgrading via USB, the update went thru and i thought it was finish. So I turned off the car to restart it. I started the car, but the screen was completely black. Nothing is working
Later I find out that i should have waited 15-20 minutes for the update to reboot, something i didn’t do. In other words, I turned off the power before it was finished with the reboot. And now it’s dead
Any suggestions so I can get it back to life? Or is it a lost case?