yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S7 Questions and Answers] biTToe:
Let's see if this works

I have been plagued by this problem for months now. It just seemed to pop up all of the sudden.

Either the screen would come on in my pocket, even though my screen is always off, or I'd go to pick up the phone to see what time it was and a proxemity warning , LARGE and ANNOYING, would cover the entire screen... sucks at 2am in the dark.

So...

SamPay has three options in Use favorite cards setting

O Lock Screen

O Home screen

O Screen off

All three were "on"

I will disable 'Screen off' first and see if that fixes my problem. If not I will work my way up the list.

I will (hopefully) report back in a day or two. IF it works for me, perhaps it will work for others.

Really what I want is an unlocked bootloader damnit.

Science is like sex,

Sometimes something good comes

but that's not the reason for doing it.

R. Feynman
[Samsung Galaxy S7 Questions and Answers] GreeTech:
Factory reset helped me when I had this issue. Good Luck!
[Samsung Galaxy S7 Questions and Answers] dbal:
Had the issue with a non working proximity sensor just out of the box and after the initial consequent updates all the way to Nougat. Found this thread and one day before sending it to the service center, tried the factory reset and works flawlessly ever after! Probably confirming the rule to reset once after every major update...!
[Samsung Galaxy S7 Questions and Answers] preslmayer:
Hello!

I have a problem with my proximity sensor and lights sensor too (see attached screenshot).

I have checked it with *#0*#.

It seems that the sensors will not be detected. The LED ist working.

A Factory reset didn't help.

What could be the problem?
[Samsung Galaxy S7 Questions and Answers] FeijaoSanto:
Hello, any idea of what happened with all this sensors and the solution??

My problem is worst, because NONE sensor is working :crying: :crying:

Image of what is happening when i open the sensors!
[Sprint LG G3] taso10:
Hey everyone, I recently flash Ressurection Remix 6.0.1 onto my LS990. Everything works great, I have service, 3G works and everything else software wise is awesome. The only thing, I am not getting LTE (i have a registered sim card with sprint inside) and I am not able to perform any service/dialer codes: (##UPDATE#), (##SCRTN#), (##DATA#), etc. Since I am receiving service and my 3G works, I don't think its the EFS that is the problem? If anyone can guide me through a way to fix this? thanks so much in advance.
[Sprint LG G3] jralabate:
I think the codes only work on stock roms
[Sprint LG G3] taso10:
Thanks for the reply, so the best way to do this, would be make a nandroid backup, flash a stock rom, perform the prl update and then restore the backup? when i restore the backup, does that overwrite the PRL again? or should i exclude the EFS restoration so it keeps the one from the stock rom?
[LG G5 Questions & Answers] Schrotty35:
Is there a dark theme with dark settings?
[LG G5 Questions & Answers] BySezerSimsek:
if I buy g5, I'm thinking of making a dark theme. as g4 genisys theme ;)

http://xdaforums.com/showpost.php?p=62641170&postcount=2
[LG G5 Questions & Answers] tweetyfiestuky:
Come on, don't think any more and get it!! Good

Enviado desde mi LG-H850 mediante Tapatalk
[LG G5 Questions & Answers] GottZ:
Android n will deliver dark theming too (reminder)
[LG G5 Questions & Answers] KillerofJoy:
Best phone I've had in my hands.. H830.. T-mobile with no root and I could live with it but one click root now has root available.. Costs 40 bucks.. Gonna wait it out until twrp encryption is worked out..
[8525, TyTN, MDA Vario II, JasJam General] philchan:
I just got my new cingular 8525 and when on the 3g or wifi connection I cannot access my works website. Sometimes it finds the url and says it is loading at the bottom of the screen but nothing comes up. Sometimes it tells me the page does not exist at all. Someone please advise me what to do. I am not that good with comp terms and all so I will need some help on this one. Here is the website.

HTTPS://wizmo.radiator.com
[8525, TyTN, MDA Vario II, JasJam General] philchan:
bump

need help
[8525, TyTN, MDA Vario II, JasJam General] mcorrie1121:
Are you only having problems with your work's site or all sites?
[8525, TyTN, MDA Vario II, JasJam General] philchan:
pie is only having problems with my work site it just shows a blank page.
[8525, TyTN, MDA Vario II, JasJam General] MikeChannon:
You could try Opera Mobile or Opera Mini. Probably a faster browser anyway.

Mike
[Galaxy Note 3 Q&A, Help & Troubleshooting] Elcs:
Hello guys,

About 22 months ago I grabbed a UK Note 3 (n9005 iirc) on the O2 network and loved it to bits. I requested my unlock code in early April, received it and proceeded to grab a new phone and passed my old Note 3 onto my Dad.

The Note 3 had it's bootloader unlocked, rooted, custom recovery flashed and running SlimLP and is till pretty great.

So my Dad pops his Three SIM into the Note 3, it asks for the unlock code, he puts the code in direct from the email I received from O2 and... code failed, unlock unsuccessful. My Dad being my Dad, asked me to input the code and nada, no go. O2 sent me a new code today after I spoke to them this morning and informed them... that new code is exactly the same as the old one that didn't work.

I checked the IMEI number against the one in the email and they match perfectly.

Could the fact that the the bootloader is unlocked, the phone is rooted, there's a custom rom on and/or a custom recovery installed be affecting the unlock code? My Dad has everything else working to his satisfaction on the phone all except this whole network issue.

At this moment in time I am quite frustrated that despite having the code it's not straight away simple and working as expected.

Any assistance would be most welcome.
[Galaxy Note 3 Q&A, Help & Troubleshooting] audit13:
The bootloader has never been locked on the phone afaik.

The unlock code needs to to be entered using a stock Samsung dialler.

I recommend flashing back to stock, sim unlock, flash back to a custom rom.
[Galaxy Note 3 Q&A, Help & Troubleshooting] Elcs:
I'm sure the bootloader was locked as it triggered the void warranty bit but it's been so long ago that anything could have happened.

SlimLP uses the stock dialler for Lollipop anyway but it's no pain to flash the phone with a stock rom (does it matter if it's an O2 stock ROM or can it be a stock Lollipop Rom?) and give that a go.

Personally I use PixelPro dialler which doesn't seem to take over the phone part like it used to, only the dialler side.... But that's by the by.
[Galaxy Note 3 Q&A, Help & Troubleshooting] audit13:
Knox and a locked bootloader and two different things.

Knox is present in almost every Samsung android phone running 4.3 or higher. It is Knox that triggers the change from 0x0 to 0x1.

Locked bootloaders are present on phones from att and Verizon. There could be others but these seem to be the most common. Att and Verizon note 3 bootloaders, once locked, have never been successfully unlocked as no one has been able to find a working exploit.

When I say stock dialler, I am referring to the stock Samsung dialler.
[Galaxy Note 3 Q&A, Help & Troubleshooting] Elcs:
Flashed back to a 5.1.1 stock O2UK network ROM, entered the code and voila.... network unlocked.

Thanks for the assist.
[MTCB Android Head Units Q&A] whitetigerlgt:
So i deiced to get the 10" Joying rx3188 unit with android 5.1.1 that recently came on the market. So far I rooted it and got it set mostly how i want, but I discovered an issue with bluetooth. Basic phone pairing and functionality works properly and ive also paired my OBD2link MX unit with it as well for the torque app, which works fine as well. the issue i'm having is that other apps that would use bluetooth, think that bluetooth is disabled on the unit. when i try to have them use bluetooth, they ask if they can turn bluetooth on. Selecting yes hangs the app and i have to force end the app to stop it. Even if i go in to torque, it reads bluetooth as disabled even tough the app itself works fine otherwise.

It seems as if the OS is not properly flagging to apps that bluetooth is turned on as far as i can tell. Is there a workaround for this, or something i can do to signal to apps installed that bluetooth is indeed enabled on the HU?
[MTCB Android Head Units Q&A] popeye70:
Sorry i don't understand, Torque is working for you or not?

But, what's the "bluetooth name" of your device? Because to work properly i think it must be "OBD" or "OBD2", otherwise you have to search an Xposed module that can help you.
[MTCB Android Head Units Q&A] sterod:
I'm having the exact same problem with the same unit also on Lollipop. I've notified the developer in the Forum post below and he is looking into it. This now makes a total of 3 people with the same problem.

http://forum.carjoying.com/thread-52.html
[MTCB Android Head Units Q&A] CadillacMike:
what apps are you having problems with?

also, what car did you put it in? How does it look? 10 inch screen sounds awesome
[MTCB Android Head Units Q&A] sterod:
I'm having two problems right now. The first is that I am unable to pair my Logitech k810 keyboard, and I am unable to connect to a Bluetooth dongle that is used by my radar detector / laser Jammer with an application called Alp connect. I've found quite a few bugs with this head unit and I'm reporting them all to the developer. It works okay my main concern is that it is quite sluggish and I think that is due to the one gigabyte of RAM and lollipop. I installed it in a 2011 Subaru Impreza
[MTCB Android Head Units Q&A] CadillacMike:
I'm fully on board with the concept "your money your car, do what you want" but what do you use a keyboard for in the car?
[MTCB Android Head Units Q&A] sterod:
Quite often I'm too lazy to unpack my laptop when I have to compose a lengthy email on the go so I prefer to do it with a keyboard rather than try to use the touch screen to bash out a couple paragraphs.
[MTCB Android Head Units Q&A] whitetigerlgt:
Torque is working, but if you go to adapter status in torque i shows BT not enabled. And thats the issue, the BT status is off when apps check it. For torque, it does not try to turn on BT to function. other apps do, and when they do, they hang.

I need to somehow flag BT as on for other apps so they dont say they need to turn on BT to work.
[MTCB Android Head Units Q&A] whitetigerlgt:
apps like tablet talk, or obdlink or solostorm. all think BT is off, and try to turn it on when you want to use the BT obd2 adapter.

its in a Mazda MX-5. ;)
[MTCB Android Head Units Q&A] pounce:
If your objective is to solve the problem get a usb keyboard. They work. If your objective is to get bluetooth keyboards working you might have to wait a long time.
[MTCB Android Head Units Q&A] sterod:
Well, I hope you are wrong as my previous NewsMy NU3001 head unit worked perfectly with it. I'm aware I can use a USB keyboard. In any case I'm happy the developer is willing to try and fix it. What is your source for claiming it will be a long time for it to be fixed?
[MTCB Android Head Units Q&A] whitetigerlgt:
Also to add to this, im also unable to pair my qstarx 10hz BT gps unit.
[MTCB Android Head Units Q&A] sterod:
It may be helpful to post your Bluetooth concerns in the same thread as mine on the Joying Forum I linked to above so that the developer is aware it's not just me and may encourage him to work on this more quickly.
[MTCB Android Head Units Q&A] whitetigerlgt:
Just popped my head in over there. I was hoping that peeps here would know of a trick or flag for the OS to make all apps think BT is on. then they could get past the check and just access BT, kinda like what the torque app does.
[MTCB Android Head Units Q&A] sterod:
Yeah if someone finds a way to do that I'd be interested to know how as well. Slightly off-topic did you try installing a custom recovery or the Xposed framework on this unit? I have tried and failed many different types of attempts to do it on this unit.
[MTCB Android Head Units Q&A] pounce:
My source? Joying didn't write the software.
[MTCB Android Head Units Q&A] sterod:
And what relevance does that have to the speed at which the issue can be resolved? It seems that you are just being defeating for no purpose. The developer is willing to help and he has expressed that desire in many Communications I've had with him so far. I prefer to be optimistic and that he has the right people to contact to resolve the issue
[MTCB Android Head Units Q&A] whitetigerlgt:
no. i just have it rooted so far with supersu installed. what feature in xposed could be used to help here?
[MTCB Android Head Units Q&A] sterod:
None that I can think of I was just curious if you had been able to install Xposed. I am curious as to how you were able to install SuperSU, as I was only able to install King root.
[MTCB Android Head Units Q&A] pounce:
http://xdaforums.com/wiki/Generic_Android_Head_Unit/MCU_Explained
[MTCB Android Head Units Q&A] sterod:
That article is almost 2 years old and they are probably talking about MTCB based units. These new Joying 5.1.1 units are MTCD based, Its possible they have overcome those bluetooth limitations.
[MTCB Android Head Units Q&A] TT_Vert:
I also have the same problem. I use a radar detector app for my valentine one that interfaces w/ the radar detector via BT and the software sees BT being off even though the head unit sees the bluetooth device. So I need to trick the software into thinking the BT is enabled even though it "thinks" it is not. it clearly is enabled. My 7" 4.4.4 device works flawlessly but nothing on 5.1.1 devices.

Dave
[MTCB Android Head Units Q&A] sterod:
I am not entirely sure that is the problem. Some people have suggested that "Profiles" are missing from the Bluetooth "Stack" in the stripped ROM. I am not an expert so I cannot comment as to the validity.

http://forum.carjoying.com/thread-52-10-lollipop-bluetooth-problems.html
[MTCB Android Head Units Q&A] TT_Vert:
It is a problem as i cannot connect w/ 5.1.1 as the software stops since it doesn't see BT as on and it won't continue past that. Everything works fine on 4.4.4 I have the exact same units except android version. UQ-130 (4.4.4 and it works) UQ-135 (5.1.1 and it says enable bluetooth)

Dave
[MTCB Android Head Units Q&A] sterod:
I think you may have misunderstood what I wrote. What I was trying to say was that I don't think the problem is that the Apps think Bluetooth is off, then crash when it tries to turn them on, I think the problem (why these apps aren't working) is because they are trying to communicate with the Bluetooth module in the Rockchip board in a way that ROM is not allowing, hence the incorrect error of the apps reporting Bluetooth as being off.
[MTCB Android Head Units Q&A] TT_Vert:
In my situation the app thinks BT is off (The HU sees the BT device) and it won't proceed past. If it would just get past that screen where the app "thinks" the BT is disabled then it would actually see and connect to the BT device. The BT connection is actually initiated by the software to the radar detector hardware not by pairing the radar detector to the head unit. If it was some MCU issue w/ the SW speaking to the HW they it probably wouldn't work in 4.4.4 which it does.

Dave
[MTCB Android Head Units Q&A] sterod:
I think you are missing what I am trying to explain. My apps also think BT is off when it is not, same as you, and it also talks directly to the dongle, and it isn't paired either.

Please re-read my post above. Also, don't assume just because it worked on 4.4.4 that is has to work on 5.1.1. These are entirely different MCU's. MCTD based (4.4.4) vs MCTD based (5.1.1).
[MTCB Android Head Units Q&A] TT_Vert:
Logic would (should?) dictate that they don't regress on their functionality. I've never seen another android OS upgrade actually reduce functionality. I ordered a USB BT dongle, i'm curious to see what it does. If that resolves it i'll be happy.
[MTCB Android Head Units Q&A] sterod:
Hah, in a perfect world I would agree with you.

Don't bother with a USB BT Dongle, I tried 4 different kinds, the HU does not even acknowledge them being plugged in, nor do they appear in the Bluetooth settings. It looks like you and I are on exactly the same path, unfortunately, it leads to a wall. We either wait for Joying to fix it, or (hopefully) a Malaysk ROM.
[MTCB Android Head Units Q&A] TT_Vert:
Do you think a ROM can fix this if it's an MCU issue? I doubt he's going to code to fix this.

Dave
[MTCB Android Head Units Q&A] sterod:
Honestly, I don't know. I'm definitely hoping so.
[MTCB Android Head Units Q&A] TT_Vert:
You and me both. This is a deal breaker for me as I have the android HU primarily to interface w/ my radar detector. It uses it's gps for lockout as well as display of signals/freqencies. Of course I also use waze/pandora but if any of those don't work there is no need for me to use an android HU.
[MTCB Android Head Units Q&A] sterod:
The app I use, ALPConnect, does the exact same thing. Fortunately, the hardware on mine includes a hardwired speaker and GPS setup that work standalone. The benefit of the app was to get a nice big visual notification of a trap, as it would come into focus, duck the audio and play an alarm. It would also report the frequency of the radar and the type of laser hitting me. While I can get by without all that, I can't have the music blaring like I usually do, as the little speaker is only so loud and the Joying head unit doesn't have Mute Input wire to duck the audio.

While this is going slightly off topic, you may want to look into the AL Priority, it can interface with your V1 too and you will also gain laser protection. This thing has saved my a** countless times and paid for itself already many times over.

http://www.alpriority.com/
[MTCB Android Head Units Q&A] TT_Vert:
There is a lot more functionality than just that that the YaV1 gives me. Lets just hope for the best for both of us I'll report back if i find any breakthroughs, please do the same.

Dave
[MTCB Android Head Units Q&A] calhdt:
I am also having the same issues. I am trying to use the Dashcommand app but it hangs when trying to turn BT on. it works perfectly fine in Torque but i want to use the fuel consumption features in Dashcommand.

Dale.
[MTCB Android Head Units Q&A] cruizin01:
Any update on this from anyone? My new Joying unit is having the same problem with a couple apps.
[MTCB Android Head Units Q&A] dugstor:
Having the exact same problem, this rk3188 HU is utter c*ap shoot.
[MTCB Android Head Units Q&A] ByteEnable:
Still broken. Joyring as abandoned support for the rk3188 head units per a post in the joyring forums.
[MTCB Android Head Units Q&A] marchnz:
I dont see end of support for the MTCD from Joying at all, the last update was 21/11/2016 and these models are still available.

Their support is minimal for all units, but in terms of updates release, still there. Have you considered the sofia units have received "more support" because have new/carry over bugs that were probably OK on MTCD.
[MTCB Android Head Units General] kaitzo:
Hi,

I recently bought a Joying Radio for a VW, it is a 8" touch screen and so far seems to work, I only have a really annoying problem with the noise. When I am not playing any music, the speakers emit a static noise, the volume of the noise never changes even if I turn up the radio. Since I am not always listening to music, I would still like to fix the problem. I read and the Sticky thread something about ground loop noise, but could never find an explanation to it. Maybe someone of you can help me :)

Also my weather app doesn't seem to work, if someone has any ideas ;)

Thanks in advance, if you need any other information for solving this problem, let me know ;)
[MTCB Android Head Units General] pounce:
How loud is it?

A very low static sound is common on these units. I have it both of mine. As you noted, thankfully the volume of the static does not increase with the volume so I really don't notice it when music is playing.
[MTCB Android Head Units General] popeye70:
You can try:

- linking the metal case of the unit to ground wire;

- shielding harness wires, as better you can
[MTCB Android Head Units General] kaitzo:
The noise is not that loud, you only hear it if you are not driving and have nothing playing.

Is the ground wire already included in the VW cabling so that I have to pull it out of the harness or do I have to run a cable myself?

As for shielding I assume I can just take some electrical tape or is there anything else recommended?

Thanks in advance!
[MTCB Android Head Units General] popeye70:
Hi kaitzo,

take a look at this thread of carjoying forum http://forum.carjoying.com/thread-24.html there is a link "solutions for radio bad reception" that can help for your problem too...

- radio1 subfolder has pictures about shielding wires

- radio2 subfolder has pictures about linking the iron case to GND
[MTCB Android Head Units General] kaitzo:
Hey, thanks for the reply, I already noticed that when I pull out the radio cable the noise is gone, so I am gonne give shielding it a try :) If that doesn't work, I will try connecting the ground wire.

I'll let you know if it helped solving the problem :)
[MTCB Android Head Units General] CadillacMike:
so I dont care about AM/FM radio. are you saying if you just left the AM/FM radio unplugged you would have no noise at all?
[MTCB Android Head Units General] kaitzo:
Yes, leaving the antenna unplugged solved the problem for me, since I will be listening to Spotify most of the time anyway it might be a solution. Nevertheless, I will try to fix it even with the Antenna plugged in. Trying the ground method next, as shielding didn't help. I also found that the VW connector and the antenna connector which was included with the car not join each other all the way, so it is always a bit loose, but even with force I can't completely join them. I will let you know if I succeed.
[MTCB Android Head Units General] xnonim:
And??

And after all you find a solution??? I’m with same issue
[MTCB Android Head Units General] TiberiusGavier:
Having Same Issue

Hello there,

Sorry to revive this thread a few months late, but I am having the same issue and wanted to see if anyone had any ideas to fix it. I installed a Ownice C500+ radio head unit into a 2015 Nissan Murano. Everything functions perfectly and works great - expect for one thing. Whenever the volume is on, there is a very faint staticky sound in the background. It never changes tones or volume. It just always stays at the same pitch and doesn't go away. Aside from turning the sound all the way off, the only time it doesn't do this is when I switch to the radio - then the hissing disappears and all is perfect again. But if I am playing music via USB/AUX/Bluetooth, etc, (or if I just have the volume on with nothing playing) the hissing noise is always there. It is faint and hardly audible, so during driving it is no problem. But if, for example, I am listening to a soft song while stopped at a red light - then I can hear it and it is annoying.

I have tried to change the amplifier gain in the head unit because I figured that is what is causing the noise. However, it does not seem possible in the Ownice unit. The sound equalizer does not have "gain" as an option to change, I checked into Advanced Settings as well, also tried engineer mode on Android unit, plus downloaded some equalizer apps but nothing has fixed it.

Any idea on what is causing this and what I can do to fix it? Any help or suggestions would be greatly appreciated :) Thank you
[MTCB Android Head Units General] lorrys:
Same here

Same issue here with a new Asottu Infidini Allwinner T8, with extra DSP chip included. Except that my hissing sound goes up with the volume. I will contact seller.
[MTCB Android Head Units General] TiberiusGavier:
Sounds good, I will keep working on it as well - let me know if they happen to find out what is causing it
[MTCB Android Head Units General] traxformania:
Same issue here : (
[MTCB Android Head Units General] lorrys:
Solved!

Asottu provided an android 7.1.2 update weeks ago. The issue is gone now. It was not an MCU update. Just Android.