Related
Hi,
Since today I have a new problem - when trying to start the camera by pressing the camera button or via rograms I got the message "Unable to initialize camera. Failed to set up the camera device."
I have the original ROM, nothing modified. Some days ago I was making pictures with the phone, worked well. I have not installed any programs since then.
Any ideas for workaround?
Also sorry if I'm repeating another thread, tried to search but found nothing.
Thanks,
Boyan
Guys, am I the only one who has experienced this???
Yeah I haven't had this issue before. Have you tried a soft-reset? Maybe a backup of your ROM when the camera used to work? As a last resort, I hate to say it but you could always try a hard-reset?
http://forum.xda-developers.com/showthread.php?t=375474&highlight=CAMERA
I have the same problem
Exactly the same behaviour
when I try to start the camera I get an error box (rotated) with white square : " camera
impossible to initialize the camera.Failure of camera peripheral configuration"
it was working OK 10 days ago and I didn't change anything from this date except making a sprite backup.
Loading a 1 month backup didn't help neither a full hard reset (same behaviour just after the hard reset)
Looks like a harware failure, Ilook for a hardware test software for the camera ????
Trying to solve, I looked at the camera launching process, I've found a link like:
_camera.lnk
that contains:
21#"\Windows\Camera.exe" ?CameraRc_Grey.dll,-1106
any idea if that is normal content, looks curious for a link especially the interrogation point mark?
What about the -1106 figure ?
Is it possible that this link being corrupted ?
Otherwise, I phone to HTC technical support and the fact that the error stays just after a hard reset lead to think its a hardware failure; however loks teribly like a software pb....or a dry soldering point? They told me to bring the phone to a fixing office in Paris area delay announced to repair between 1 and 7 days
Any other help welcomed
problem disappear
hi rvgpoi,
the good news are that the problem disappear, the bad news are that I have no idea why...
I have not made hard reset (in fact, never), just couple of soft resets... but after that the camera was NOT working... couple of days later, i just wanted to show the problem to a friend of mine - and it was working...
I'm pretty pissed from HTC support - I have mailed them for this problem, and still no answer (1 week). This is not acceptable for a decent company.
In order to try to see where the problem is - can you tell me how to look at that:
_camera.lnk
that contains:
21#"\Windows\Camera.exe" ?CameraRc_Grey.dll,-1106
to see what is the value (while camera working)...
Good luck with your camera
Yes, same for me.
I am using Start->Program --> Camera.
I think that we should wait HTC support center for this problem.
Camera fails to initialize
Hello all,
I have the same problem exactly. I have the device for 6 weeks. Camera worked for two weeks. Stopped working for a week and then returned for a few days then failed again with the same message you guys got. I have done a number of hard resets- does not help. I am in a country with NO HTC service center and sending it to Europe will deprive me of my only phone for a long time. HTC Europe has NOT replied to my email from 3 weeks ago.
Any ideas? Rom update-if exists? Reinstall Rom? Any other ideas???
Jeremy
Solution, maybe
Guys,
my camera suddenly started to work again, I was extremly happy, activated GPS photo, took some pictures with coordinates, when i tried the camera later that day - it did not worked again. restarts, resets - nothing helped.
the next day I took out the battery for 10-15 minutes - and when I put it back, the camera worked!!!
Today the camera is not working again - and currently my battery is out. Let's see what will be the result.
Good hunting
Camera fails to initialize
I should have mentioned other problems that might be releavant- Bleutooth does not turn on from the momeent I purchased, touch pad is sometimes very slow for initial reaction. I have NO added programs beyond manafacturer originals.
Same problem...
Hi,
I'm a newbie, I didn't think that there was a so big and interesting forum about pdas and, especially, for my htc polaris...
I've got the same problem with the cam...
When I turn on the device, cam works fine...
After a while, it continue working...
After some hours, it stops working.
I have a full original firmware on it:
ROM: 1.25.408.1 12/12/2007
Radio: 1.58.21.23
Proto: 26.65.30.04H
I also tried to contact support, but with no responses, at the moment...
I also searched for a original upgrade (for the warranty), but nothing...
I think the problem is in apmd (or similar else) os daemon.
I think the os turn off cam device for power savings, and after it is not able to restart it before launch camera.exe program, that returns that strange message...
I searched in registry with ceregeditor if it is possible to disable power saving for a single device, to make a test, but I'm not a so good mobile engineer.
A newbie question:
The upgrade WM 6.1 bepe 0.67 can resolve this problem?
And again: if I upgrade anyway, I lose my warranty?
Camera fails to initialize
I called up the UK support center. After going over the problem with them I was told to return the device for servicing. Seems they will have to do a new Flash Rom. Two weeks without the device at least and I have to pay for international courier.
the problem still stays... this time removing the battery didn't help.So I'm again camera-less. Still no reply from HTC.
I'm also with original firmware:
ROM: 1.25.405.1 12/12/2007
Radio: 1.58.21.23
Proto: 26.65.30.04H
as you see the rom is different, same problem. In my case turning off the device does not help - the camera is not working even after switching it back on.
Are you able to deactivate power savings for cam?
Another think:
Your rom version is older than mine,
Perhaps a new rom version resolve the problem,
but is not original version, and we should ask to cooked new rom developer if they have found something wrong in cam device apmd functions...
I have the same problem, but for my TC it is simply resolved by doing a soft-reset and starting the camera after it's ready..
still annoying though..
same problem here,
sometimes cam will work but it to often will not. :/
sure ift the cam even dont in factory default config (hard reset) it is broken.
I got longest working duration in factory default, approx one to two weeks.
using third party binaries the failure appears randomly.
Im pretty sure this is a software issue, else a soft rest wont fix it, eh ?!
workaround:
one but very poor solution is, once the cam starts, _never_ quit it, just minimize.
yep, I know ... but the only way I found atm.
// update //
approx one day without any probs and I used nearly every feature of my device....
Im not familiar with the CCD chip technology, I dont know if there is any possibility for burn-in effects, therefore I switched to the front cam for "stand by" and got the good old failed to ini ... error immediately when I tried to switch back to the rear cam.
now I will test if the front cam is got the same error ...
and I'll get some info if 24/7 on can harm the ccd chip
// update //
I have my cam now approx one week always on and have no problems at all.
I have got no news about cam.
I called htc support, they told me to install a fix for camera that I found in htc e-club.
But that fix is not for our problems, is for camera quality.
I installed it but the problem still remain.
Sometimes it goes, sometimes no...
try that :
http://forum.xda-developers.com/showthread.php?t=391455
don't work
The sd memory isn't a solution,
because I have 1985MB free of 2GB.
If you soft-reset and don't work again,
Take the pda off without the battery for some minutes.
The cam will works again,
but after some time goes down again!!!
My Galaxy Tab 7.7 turns on every few minutes and displays a message for a moment in the lower right corner. The message is "USB Device Disconnected".
The device is not connected to any USB device.
This has been happening for many weeks now.
I've tried to turn the USB Debug option on but that didn't change anything.
I have not rooted the device.
I have not flashed the device.
I am running only stock applications from the market.
Does anyone else have this issue?
It's maddening because the device constantly turns itself on. At night I either remove it from my bedroom (the display lights up the room when it comes on) or turn the device upside down on the table so I can't see it when it comes on.
yes, i have the same issue
no idea what the reason is
Same issue.
One Added Note
One item to add...
It appears that if the unit is charging it does not have this problem. This makes logical sense as the USB is connected, albeit to the wall outlet.
I'm going to wait until ICS - which is due here in Thailand at the end of this month. If that doesn't fix it I will contact Samsung.
Living here in Asia makes taking things back for repair very difficult as the many small but authorized vendors aren't set up for this, the language barrier adds heavily to the issue, and finding an English speaking official Samsung office is quite difficult.
I will monitor the forum to see if a fix arrives before my software update.
Thanks everyone!
Same problem here. When this happen for me the mobile network disconnects, I am thinking that it may be some problem with the mobile network card...
When connected to wifi this is not visible although i might get the usb message.
But on 3g i loose all connection sometimes only for a second but sometimes for up to a couple of minutes...
Sent from my XT910 using Tapatalk
Update
I wanted to add some more information...
I happened to remove my carrier's SIM a week ago and the "USB device disconnect" error continues at the same rate.
I guess my next question is how do you contact Samsung support?
Do they have a Tablet support phone number?
I don't care which country the support line is located within, as long as it's English-speaker focused.
bump
very annoying to lose mobile network all the time
I changed Galaxy Tab 7.7 (3G Version) three times, all three tablets had same problem.... any idea to fix it?
I think the problem gets worse if the tablets not been rebooted for a while.
But after reboot I think mine is a bit more stable.
How is it for the rest of you?
---------- Post added at 10:50 PM ---------- Previous post was at 10:49 PM ----------
I also find it weird that you have the same problem with three tablets, but at the same time it seems that very few of us are affected???
I called Samsung and they said they never have complaints on this issue.... anyway, i got three devices from different stores have the same problem.. I think the issue is the rom. That problem hopefully can be solved after ICS upgrade...
Same problem; not so often but it happens once in a while.
I don't know if it is causing the instability that I have noticed with this device but it is kinda weird.
Do you have micro SD card plugged into the device? I read some other forums and some people removed the micro SD card, the issue resolved afterward.
I just removed the micro SD card, I will let you guys know if the issue can be fixed or not soon...
Sent from my GT-P6800 using XDA
Solved
I think all this happens because of Kies software. It's a monster, I will never use it any more. Even uninstlling may not help. Better use MobilEdit instead.
Anyway, I found solution in registry. So, try this:
Before starting, disconnect all usb devices from PC
1. Open Windows registry editor
2. Open key HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Enum\USB
3. Press CTRL+F and search in data value your device name (egz. Samsung)
4. Delete all key branches with name started: Vid_*** where your device will be found (You may have to enable permissions first).
Reconnect device. That's all
i have the same 'problem' but..., never used Kies software
Anyway, solution is in the registry. Evidently some usb drivers are conflicting.
Deleting those Vid_*** keys simply resets usb drivers on particular port.
You can check your phone on another computer without driver
Vytookas said:
I think all this happens because of Kies software. It's a monster, I will never use it any more. Even uninstlling may not help. Better use MobilEdit instead.
Anyway, I found solution in registry. So, try this:
Before starting, disconnect all usb devices from PC
1. Open Windows registry editor
2. Open key HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Enum\USB
3. Press CTRL+F and search in data value your device name (egz. Samsung)
4. Delete all key branches with name started: Vid_*** where your device will be found (You may have to enable permissions first).
Reconnect device. That's all
Click to expand...
Click to collapse
I don't see how this has anything to do with the problem.
The USB device issue is happening on the tablet, not on the PC. How does removing USB drivers from my PC fix the tablet issue?
omarrabbat said:
I don't see how this has anything to do with the problem.
The USB device issue is happening on the tablet, not on the PC. How does removing USB drivers from my PC fix the tablet issue?
Click to expand...
Click to collapse
Sorry, I didn't notice, that device is disconnected
Same problem with GSM version. Could someone try log at the logs when/after it have happend? Dmesg and logcat. Will also try to do it myself.
same issue here. Never used kies before. I'm not sure if it has something to do with interfering gadgets near the tab.
Strange thing some (or most) people dont notice that bug(?). I tried several 7.7's now and can confirm that this looks like rom issue as every 7.7 has that problem. It really annoys me, escpecially combined with the battery status screen-on bug. When battery is lower than 10% screen turns on like every 2 minutes or so... Good thing to save remaining battery
Oh and I never used Kies too. Didn't even install it yet.
People,
I hesitate to ask the question again, but I promise you that I've read everything on the subject that I can find (including many of the 171 pages of the "Nexus 5 Flashable Modems and EFS Backup" thread...) and also on a lot of other sites.
My son's N5 on 5.1.1 ran out of battery a month ago (it worked perfectly for the 15 months that I had used it) and when he recharged it he'd lost mobile data. He had the mobile service triangle in the notification bar, but empty. No service.
I have tried absolutely every suggestion that I've read. Airplane mode on/off. Flashed 3 older radios. Installed older Lollipop & Kitkat 4.4.4 from Google Nexus factory image site. Installed the latest nightly of Cyanogenmod. Installed MPZ79M. Rooted it. Nothing works.
I don't believe it's a hardware problem - when I remove and replace the SIM the notification goes from the square with a diagonal bar across it ("no SIM") to the empty triangle. But as soon as I reboot (not just screen off & waken, but full restart) the triangle is replaced with the "No SIM" square again. The same reaction happens on the initialisation after a factory reset - at the "Register SIM" screen it says "No SIM", but extracting and replacing the SIM starts the "Attempting to connect to service" sceen, though this just does nothing until my patience runs out and I skip it. The SIM itself has 3 scratches along it, so all in all I don't think it's a contact problem, but something in the software. The SIM works fine in the Nexus 4 that I've given him.
EFS - I don't know enough about it still, but the phone displays the correct IMEI, so I'm hoping that this means that the EFS is not corrupted?
I know that this is a well-known problem, but on the off-chance that somebody has read a solution that I haven't found...
Thanks for your patience and any help you can offer.
Oh well...
...I guess I have a £350 paperweight?
I suppose at least I can use it as an entertainment console, since wifi seems to be ok. But a terrible shame to waste such a beautiful device.
Maybe you already tried it... Just to be sure:
a) You have incorrect APN configuration, to solve this try resetting your APNs via Settings > Wireless & networks > More > Mobile networks > Access Point Names and then click in three dots above and select "Reset to default".
b) Your mobile phone antenna unit is not working properly, solving this is pretty easy, shutdown your phone, remove your phone's back panel very carefully (using a plastic material..i did it using guitar pick) and then you'll see two wires adjacent to edges of your phone, just remove and refix them gently and reboot your device.
c) Reboot in safe mode and try to play with the preferred network type.
d) I had this problem "No service and no signal network in nexus 5" after restarting phone.
I tried to restart phone few times again and reinsert sim card. No luck.
Then I took sim card out while phone was on ( I forgot to turn it off) and reinsert it and now it's working fine.
It must be a contact problem. Just not shure how long will it work.
Primokorn said:
Maybe you already tried it... Just to be sure:/QUOTE]
Thanks, Primokorn, I'll give your suggestions a go - appreciate the ideas.
I have tried the APN settings, but since there's no SIM (huh!) it's greyed out, though it's temporarily updateable if I extract/replace the SIM while the phone's on - but it's grey again on the next reboot.
Click to expand...
Click to collapse
Primokorn,
No luck. I tried all of these with no result at all. It looks as if this is a very serious flaw in the Nexus 5 - I had my doubts, to be honest, when my son said it started after the phone ran out of battery, but I see exactly the same explanation from other people in the huge number of threads reporting this no-radio problem. How can Google issue such a good phone with such a lousy bug in it...? No point in even asking them (though I've seen at least one person who tried with an impressivly helpful response from the Google support person) since not only is the phone out of warranty but it has been rooted.
Oh well, I enjoyed it while I had it...
There is getting to be quite a bit of information to look through when looking for tip/solutions related to the new Joying 2GB / Sofia units. Since this is not a MTCB or MTCD unit, the threads seem to be scattered all over and very difficult to find in searching. I have seen roll-up threads for other units, that contain information such as ROMS available, tips, tricks and useful information. Kind of a "one stop shop" for the newer Joying HUs. If you have useful software, mod, tips, customization's, get something to work, etc please post here and I can include.
CPU Information - Rockchip Sofia x64 C3230RK / mali 450 GPU / Up to 1.2Ghz / 4 core / FYT5009 SoM - rated to run at up to 85C. My particular is unit clocked at 1.04Ghz.
Advanced Settings Password: 3368
Homescreen menu: 8086
Backlight Current menu: 5768
Android 6 Thread
https://forum.xda-developers.com/an...ing-intel-head-unit-android-6-update-t3597121
Android 6 specific tips:
ADB Access: https://forum.xda-developers.com/showpost.php?p=71616884&postcount=273 -OR-
https://forum.xda-developers.com/showpost.php?p=72057022&postcount=12
Viper4Android: https://forum.xda-developers.com/showpost.php?p=72064749&postcount=41
Latest ROM - Current ROM can be downloaded from link on the Joying blog site.
https://www.carjoying.com/Joying-blog/59.html
Android 5.1 Discussion about the Feb 22, 2017/March 5, 2017/March 15, 2017 updates:
https://forum.xda-developers.com/an...d-units/joying-intel-update-feb-22nd-t3561285
People have experienced issues with the Joying Launcher (UI3) after the update. This seems related to having other packages (google voice search ) installed prior to installing the ROM. Install time 25-35 minutes.
Recovery from non-bootable system - Without being able to access recovery, about the only solution is to reload the ROM package. Unzip ROM to SD card or USB stick, put in unit (GPS Maps slot, if using SD card ) and press the 'recessed' reset button. The unit should find the update and reload the ROM. This will wipe your data, but does leave the apps. If you use titanium backup, and have a backup, you can restore your data fairly easily. See blog article above for step by step instructions.
Root - Unit comes with root accessible in adb. SuperSU can be installed easily. There are 2 methods for installing superSU. The first method is an overwrite of the boot partition with a pre-rooted image. Problem here is if future upgrade makes boot partition changes, this method will overwrite with an older version. I recommend method 2, which modifies the existing boot partition ( need source so I can provide credit ).
https://forum.xda-developers.com/showpost.php?p=69648860&postcount=84&nocache=1&z=8361786322568856 (over-writes boot partition / may not work on Joying Feb update )
https://drive.google.com/file/d/0B4qmTV7N4JliSjZMdGg3Z18wbkU/view?usp=sharing ( modifies existing boot partition )
OS & Google Apps - Android 5.1.1 ASOP based w/ pico installation of google applications. Voice actions are supported with installation of 'Google App' from play store. No support for google search talk back.
Recovery- A recovery partition is present but does not have any type of graphical UI. It does look like a complete stock android ( command line ) recovery, but no access using USB is available. It maybe be possible using PC-PC OTG cable.
SD Cards - I have not heard of any sdcard size limitations, up to 200GB have been reported to work. Must be formatted as FAT32. NTFS, exFAT, and ext3/4 do not work. You can format a USB stick with ext4 and it will work fine.
Google Voice Calling - Stock BT dialer crashes when being called from google applications ( such as google voice search ). Workaround is available.
https://forum.xda-developers.com/an...oogle-voice-to-initiate-calls-joying-t3528923
Enable OK Google from any screen - https://forum.xda-developers.com/showpost.php?p=72447390&postcount=968
Bluetooth Tethering & BT Settings - Bluetooth tethering, connects instantly, very reliable connection, works great for streaming music, gps etc. Saves phone battery vs WIFI hotspot. Limited to ~2Mbs ( slower than WIFI sharing )
https://forum.xda-developers.com/an...elopment/bluetooth-settings-launcher-t3504526
(also good discussion here on the effects of process killing when entering standby )
Difficult to pair BT devices - Forces device pairing into database - Device pairs normally once HU thinks it has connected previously. I was able to pair TPMS, keyboard, etc using this method(s).
https://play.google.com/store/apps/details?id=com.brachcon.btautopair&hl=en
Modified stock bluetooth app to allow connection to all devices
https://forum.xda-developers.com/showpost.php?p=71280945&postcount=88
Backup Cam guideline mods - Make your lines match your camera view
https://forum.xda-developers.com/showpost.php?p=70325711&postcount=403
Apps not working after resume - The joying code will kill most applications when going into standby. This is really bad for apps that are supposed to be run at boot and background process, as they are not restarted when exiting standby. Symptoms include, widgets not updating, apps not getting GPS lock, process show running but background services are no longer running. This can be fixed by installing an updated apk file in /system/app/Sofia-1-C9-Server-V1.0 which removes the task killer. Also the key/button mods V2+ (below) will remove the task killer.
https://forum.xda-developers.com/showpost.php?p=71047452&postcount=62
Key/Button Mods - Extend the usefulness of your steering wheel keys and on unit buttons- V2+ also removes app kill on standby.
https://forum.xda-developers.com/an...-units/joying-2gb-steering-wheel-key-t3543390
If you just want to change the SRC button to call up google voice search, go here. ( also removes task killer )
https://forum.xda-developers.com/showpost.php?p=70480258&postcount=549
Immersive Mode / removes top navigation bar - No app needed - Full Screen on apps you choose, can be set from adb w/ root. Argument is list of package names separated by "," or "*" for all apps. ( survives reboot )
Specific apps:
settings put global policy_control immersive.full="com.google.android.apps.maps,com.pandora.android,com.spotify.music"
All apps:
settings put global policy_control immersive.full="*"
Clear / back to default
settings put global policy_control immersive.full=
Change Overscan - problems touching the corners, changing overscan can help:
https://forum.xda-developers.com/showpost.php?p=71492575&postcount=169
Phone/Tablet view on apps - No app needed - Change from 160dpi -> 161dpi gives "phone" view of many apps instead of "tablet" with no noticeable size change to other things. Done via adb. Requires reboot to take effect.
> wm density 161 # ( phone mode apps )
> wm density 160 # ( original tablet mode apps )
Heatsink mod Unit can run hot at heavy cpu load (such as benchmark testing). Can slightly reduce performance by throttling. Some users opt to add additional heatsink/fan to reduce temperatures.
https://forum.xda-developers.com/an...inside-look-joying-android-head-unit-t3546872
Red Themed Radio - Re-theme of stock apps - Don't like the look, change it. Can be done easily by unzipping the apk file, change images, rezip and install.
https://forum.xda-developers.com/showpost.php?p=70367793&postcount=434
More Radio Mods ( Layout change, more colors )
https://forum.xda-developers.com/showpost.php?p=71625005&postcount=286
xposed / xposed framwork - At this time, I am not aware of any way to make this work with the new Joying units. I have tried several packages and all have resulted in a non-bootable system. Please let me know you go get it to work.
Viper4android - Installer script that works on these models
https://forum.xda-developers.com/showpost.php?p=71317345&postcount=101
Nova or other launcher - Need to freeze or remove stock Joying launcher(s) in some cases, for other launchers to work correctly.
Other very useful Joying 2gb/sofia threads:
Audio Discussion / DACs - https://forum.xda-developers.com/an...ts/joying-2gb-sofia-headunits-common-t3577217
https://forum.xda-developers.com/an...pment/joying-android-5-1-1-2gb-units-t3465561
https://forum.xda-developers.com/an...opment/2gb-ram-intel-cpu-heres-specs-t3468322
Yes this is really needed. A FAQ with overview links and tips in just one post
Some people mentioned it was possible to boot into a restore function from a memory card with the update zip. If true, do we know what the exact process is? Any keys need to be held down?
Update, verified this procedure works:
sonof said:
I did recover from endless Android logo (resulting from trying to root with Joying HU root.zip found in this thread).
I did the following:
Put latest Joying update files to microSD card and insert it to GPS slot. Press and hold both reset and power buttons. Once it boots continue holding reset button.
This lead to automatic install of Joying update files and my HU was back alive but I hate the Joying company for not providing means to enter recovery and a complete ROM.
Edit: For me it did not ask if I want to update or not. It just began updating automatically. In contradict to the post above. But I was unable to boot to Android when I tried this.
Click to expand...
Click to collapse
My VW has reverse parking sensors. Does it not support those?
Just installed this unit. Speedwise it's night and day compared to my old Erisin (1gb 3188). Display is nice and crisp. Bit of a fiddle getting it mounted because of all the crap that needs to be stuffed behind it, but after some swearing and elbow grease I got it secured.
From the instructions, I cut an orange wire because I don't have a backup camera. I do however have optical parking sensors. On my Erisin this was supported (it showed a car model and visual indicators on screen). This unit doesn't appear to have this function. Can anyone confirm? I still get the beep from the speakers, so it's not really a big issue, but would be nice to know.
---------- Post added at 10:49 PM ---------- Previous post was at 10:49 PM ----------
catu said:
My VW has reverse parking sensors. Does it not support those?
Click to expand...
Click to collapse
Didn't see your post before asking the same question
anotheruserx said:
I'd like to work on this one.
But I have two questions;
1) did you manage to get any logs of how it failed?
2) When you made it unbootable, what was the exact procedure you used to recover the unit?
Click to expand...
Click to collapse
I didn't get any logs, as I couldn't connect to it until I reloaded the ROM. If I was able to make a USB connection, at least I could have looked at the logcat.
Procedure to recover: Insert USB drive with ROM, push recessed reset button, wait 30m for ROM to install, set up apps again. I have this procedure down pretty good. - The joys of playing with the system partition without USB access or recovery tools.
catu said:
My VW has reverse parking sensors. Does it not support those?
Click to expand...
Click to collapse
Actually, it turns out it does, however only when there's an obstacle (hopefully we can change this). Yesterday I only tested while stationary. Today I used it while driving, and noticed that whenever the sensor picked something up, the unit does actually display the sensors. It feels next to useless for me when it only shows on beeps, but at least we know it's there.
Well, that is the way my discarded Newsmy worked. Takes getting used to, but you then again you don't really need confirmation that "nothing" is in your way
Will need to think about this then, thank you.. Cant make up if I want this or the Ownice C500.
catu said:
Well, that is the way my discarded Newsmy worked. Takes getting used to, but you then again you don't really need confirmation that "nothing" is in your way
Will need to think about this then, thank you.. Cant make up if I want this or the Ownice C500.
Click to expand...
Click to collapse
After updating to the January firmware parking sensors are gone completely.
edit: enabling "radar" is the solution
Installed supersu (like described in this thread) yesterday and updated it from the play store. Worked fine.
Then I installed Viper4android, also from the store. I didn't expect it to work, but it does! Driver installed, and after a reboot it does exactly what it's supposed to.
Also installed Nova Launcher and set as default home. No issues with that so far. I have not frozen or uninstalled any of the original launchers.
On my Joying unit 130N2 (8 inch unit for VW) the backlight on the display does not work when it is cold. We had minus 8 degrees centigrade here and it took more than 10 minutes before the backlight came on. The radio is playing music and it is actually possible to change channel as long as you know where to touch the monitor. Today it was 5 degrees and it took only about 3 seconds before the backlight came on. I wrote Joying about it and they confirmed to me that there was an issue with 8 inch models for VW. They told me that they were working on a completely new firmware that would fix the problem. I told them that to me it seemed to be a hardware problem and how they wanted to fix that with a software. Their answer of course "No worry my friend ......". I told them that I wanted to return the radio because a radio that doesn't work when it is cold is useless to me. They told me that I would have to send it to China so that their engineers could investigate the problem. I then told them that I had bought it from a German website and it was delivered to me from Germany so if their wanted it to be sent to China then they would have to pay me for it - in advance. They told me that their warehouse in Germany did not accept any returns so it was impossible for me to return it. Then I opened a case with Paypal for selling defective merchandise. Then suddenly their warehouse in Germany was accepting returns. I had put this text also on the Joying Forum, but of course they deleted it. So when dealing with Joying and in case you have problems my advice is to be very tough on them otherwise they will BS you.
Kurt Lund said:
On my Joying unit 130N2 (8 inch unit for VW) the backlight on the display does not work when it is cold.
Click to expand...
Click to collapse
I have the same problem on the same unit. With the car headlights off, backlight is dim when it's cold, but gets brighter when it has time to warm up. And when the headlights are on, the backlight isn't on at all until it warms up.
I thought about writing Joying about it but I expected the kind of response you got. Plus, I've had my unit for a few months already so a PayPal claim isn't an option. Please let us know if you hear anything else about it from Joying.
Hi Joshnat,
Yes we have the same problem. Sometimes I can get mine to light up by turning the headlights on and off a couple of times. Are you sure that you cant make a Paypal claim? As far as I know you have 180 days.
Anyway, you should write to them and let them know that you know that many others have this problem.
Regards
Kurt
Kurt Lund said:
On my Joying unit 130N2 (8 inch unit for VW) the backlight on the display does not work when it is cold. We had minus 8 degrees centigrade here and it took more than 10 minutes before the backlight came on. The radio is playing music and it is actually possible to change channel as long as you know where to touch the monitor. Today it was 5 degrees and it took only about 3 seconds before the backlight came on. I wrote Joying about it and they confirmed to me that there was an issue with 8 inch models for VW. They told me that they were working on a completely new firmware that would fix the problem. I told them that to me it seemed to be a hardware problem and how they wanted to fix that with a software. Their answer of course "No worry my friend ......". I told them that I wanted to return the radio because a radio that doesn't work when it is cold is useless to me. They told me that I would have to send it to China so that their engineers could investigate the problem. I then told them that I had bought it from a German website and it was delivered to me from Germany so if their wanted it to be sent to China then they would have to pay me for it - in advance. They told me that their warehouse in Germany did not accept any returns so it was impossible for me to return it. Then I opened a case with Paypal for selling defective merchandise. Then suddenly their warehouse in Germany was accepting returns. I had put this text also on the Joying Forum, but of course they deleted it. So when dealing with Joying and in case you have problems my advice is to be very tough on them otherwise they will BS you.
Click to expand...
Click to collapse
You may have a faulty screen, my first one did something similar and wasn't very responsive to touches. I returned and my second unit was like night and day with how much better it looked and worked.
Has anyone got a factory backup camera to work? I have a 2015 Camry and right now I have the older Pumpkin rk3066 and the place that installed it hooked up the factory backup camera. I got my new Joying hu yesterday and am going to install tomorrow myself. I'm really hoping I can use my factory camera with this head unit also.
Sent from my LG-H918 using Tapatalk
mad212 said:
Has anyone got a factory backup camera to work? I have a 2015 Camry and right now I have the older Pumpkin rk3066 and the place that installed it hooked up the factory backup camera. I got my new Joying hu yesterday and am going to install tomorrow myself. I'm really hoping I can use my factory camera with this head unit also.
Sent from my LG-H918 using Tapatalk
Click to expand...
Click to collapse
I have the same car and HU, my oem backup carmera works. I bought a harness on Amazon including backup camera, USB, and aux in.
https://www.amazon.com/gp/product/B01BM3QGCO/ref=oh_aui_detailpage_o01_s00?ie=UTF8&psc=1
Quick tip:
You can adjust backup camera brightness, saturation and contrast by touching the screen while backup camera is on.
Is there a trick to putting in the sd cards? Mine won't click in so it won't mount.
Edit: Forget it i just had to get the edge of a screwdriver and push it in. Had me worried for a minute.
Sent from my LG-H918 using Tapatalk
Does anyone have a link or info on the dummy proof DIY on how to Root the joying unit? I want to install some of these enhancements so need to root the device and have never done it so was looking to see if anyone has a link or good write up for the slow like me. Appreciate it. I have a Joying 2gb 7 inch unit.
Looking to install this option
https://drive.google.com/file/d/0B4q...ew?usp=sharing ( modifies existing boot partition )
thedru13 said:
Does anyone have a link or info on the dummy proof DIY on how to Root the joying unit? I want to install some of these enhancements so need to root the device and have never done it so was looking to see if anyone has a link or good write up for the slow like me. Appreciate it. I have a Joying 2gb 7 inch unit.
Click to expand...
Click to collapse
Within the zip there is a file with instructions - HOWTO.txt
How-To install:
1. You need a Windows PC that is connected to the same WiFi network as your HU.
2. Unzip the attached file somewhere to your disk.
3. Run CMD.exe as Administrator
4. Change directory to the folder that you unzipped.
5. Run the install.bat script with an IP address of your HU as a parameter:
C:\Users\<username>\Downloads\Joying_JY-UL135N2_SuperSU> install.bat 192.168.123.137
6. Wait until script finishes and reboot your Head Unit.
7. DONE!
You should now have the SuperSU application working.
I don't know when it has started, but now when everyone try to call me the phone ring but i have to wait about 3-5 seconds before i get the notification on screen and i can answer
I have got the MIUI global 12.5.1.0 (RJUEUXM) and i know it is quite buggy, but i have googled a bit and none seems to have my same problem.
I read that i could try to wipe the system cache (on a oneplus one forum) but the standard recovery mode doesn't have this option, and i really don't want to wipe the phone to get another one
Any suggestion? Is there a way to wipe the system cache without formatting? Do anyone had my same issue?
Thank you
MIUI is trash that's why. And it's related to agressive memory management. (killing apps in background, even system ones)
k3lcior said:
MIUI is trash that's why. And it's related to agressive memory management. (killing apps in background, even system ones)
Click to expand...
Click to collapse
I have tried in the built-in power manager to set the power saving option for the dialer app to none, but no luck
Try disabling "Turn on MIUI optimisation" in the Developer options (scroll to the bottom of the page). It may work, or it may not work. Xiaomi thinks that disabling it can cause issues ...
Updated at 12.5.2.0 (RJUEUXM) and the problem is still present.
Do anyone have the same problem?
surcof said:
I don't know when it has started, but now when everyone try to call me the phone ring but i have to wait about 3-5 seconds before i get the notification on screen and i can answer
I have got the MIUI global 12.5.1.0 (RJUEUXM) and i know it is quite buggy, but i have googled a bit and none seems to have my same problem.
I read that i could try to wipe the system cache (on a oneplus one forum) but the standard recovery mode doesn't have this option, and i really don't want to wipe the phone to get another one
Any suggestion? Is there a way to wipe the system cache without formatting? Do anyone had my same issue?
Thank you
Click to expand...
Click to collapse
Similar problem with notification delays, in my case it affect sms and clock, dunno if this the same as your, however i post anyway, just disable via ADB the DOZE feature for apps affected with delays (do not work if i disable battery optimization in the normal settings).
Enable developer options in the device, enable usbdebug, connect the phone to the pc, install the correct usb MI drivers (use the MiUsbDriver.exe command), surf to adb directory and whitelist the system apps you want to have instant notifications.
To retrieve the list:
adb shell dumpsys deviceidle whitelist
To whitelist apps affected:
adb shell dumpsys deviceidle whitelist +com.xxxxxxxx.xxxxxxxx
Of course replace the apps name xxxxxxx with the correct name of system apps installed in your device.
Use the first command and check again if the apps you whitelist are now in the list as "user". Setting is permanent until you do a clean flash or flash a new rom.
No idea if you need to unlock the bootloader to apply such change, try it if work.
kd276 said:
Similar problem with notification delays, in my case it affect sms and clock, dunno if this the same as your, however i post anyway, just disable via ADB the DOZE feature for apps affected with delays (do not work if i disable battery optimization in the normal settings).
Enable developer options in the device, enable usbdebug, connect the phone to the pc, install the correct usb MI drivers (use the MiUsbDriver.exe command), surf to adb directory and whitelist the system apps you want to have instant notifications.
To retrieve the list:
adb shell dumpsys deviceidle whitelist
To whitelist apps affected:
adb shell dumpsys deviceidle whitelist +com.xxxxxxxx.xxxxxxxx
Of course replace the apps name xxxxxxx with the correct name of system apps installed in your device.
Use the first command and check again if the apps you whitelist are now in the list as "user". Setting is permanent until you do a clean flash or flash a new rom.
No idea if you need to unlock the bootloader to apply such change, try it if work.
Click to expand...
Click to collapse
thanks for your replay, but no look for me.
surcof said:
thanks for your replay, but no look for me.
Click to expand...
Click to collapse
Sorry this isn't helping for your specific case.
Hi,
yes my brother has this problem when a friend calls his second sim card ... he uses two SIM cards at once, you also use two cards at once? (At once=two sim cards in mobile)
I only use one sim and I don't have this problem. the above advice did not help my brother, the problem is definitely in the dual sim function (implementation). Please report it to someone on xiaomi to fix it.
PS: can you try to use only one SIM card? if your problem goes away. let us know if this is the core of the problem. Thank you.
Ochrana said:
Hi,
yes my brother has this problem when a friend calls his second sim card ... he uses two SIM cards at once, you also use two cards at once? (At once=two sim cards in mobile)
I only use one sim and I don't have this problem. the above advice did not help my brother, the problem is definitely in the dual sim function (implementation). Please report it to someone on xiaomi to fix it.
PS: can you try to use only one SIM card? if your problem goes away. let us know if this is the core of the problem. Thank you.
Click to expand...
Click to collapse
i only use one sim card, never used two
I have the same problem but in my case I think it's about having Zepp app giving notifications to my watch. Do you have a similar app? You can try to disable phone access to all apps except dialer and see if works...
DrunphO said:
I have the same problem but in my case I think it's about having Zepp app giving notifications to my watch. Do you have a similar app? You can try to disable phone access to all apps except dialer and see if works...
Click to expand...
Click to collapse
Nop, the only app i use is the dealer
Have you found any solution?
Happen to me as well on mi9t pro. Further googling led me to believe this was issue with phone app by google. You can check theor review on playstore and most people having this issue.
i have factory reset my phone and problem is still there.
Little update: i have had this issue for all the time when i was in holiday with a poor interbet connection, now that i'm returned home, where i have quite alwais signal the issue seems gone.
May be that the dialer need internet access to work properly?
Hi,
I'm having the same issue with my poco x3 i keep having a delay before my screen turns on when i'm receiving call. Is someone still having this issue or it's just me ?
I don't think there's a link with Wifi, at least that's really strange to me.
Thanks
Answer is in second post, this doesn't happen on custom ROM's. (unless they are based off MIUI)
Same problem with Xiaomi mi 11
Try to remove all the email accounts from the gmail app, it should fix.
Same issue... POCO X3...
3/4 secs delay in notifications...
the phone rings and I can't see who is calling... After 3/4 sec it shows the notification...
It's very funny how everyone is ignoring @k3lcior 's posts, when he is just spitting truth in your face.
Sorry, guys, but you can't just ignore the real cause and look for a cheap workaround that might fix it in theory. In reality, ROMs like the official one from Xiaomi (MIUI) are extremely aggressive in terms of killing background apps, etc. They want to reduce battery strain, no matter how much stuff it breaks.
This is a problem across different apps. There are tons of issue reports from app users, that can't use some apps properly, because MIUI keeps killing it, even though it already has been whitelisted in the power saving list, as not allowed to be killed. It still gets killed, though.
So, if you guys want to keep your apps alive and not getting killed all the time, you have no choice but to switch to a different ROM. Even if you find a workaround on the official ROM, then it's still very unreliable.
To be clear, once again:
Even if you whitelist your app, it can still get killed, because MIUI does not give a crap, if you need the app. It still may get killed!