Related
Hello all,
I have a HTC One M8 that i want to connect with my volkswagen RNS 315 device with build-in bluetooth but for some reason he doesnt see the device when i scan for bluetooth carkit. I am running my M8 on the latest Viper Rom with the lastest firmware.
Is there someone with the same issue around here.
Thanks already
Steven
steviegolf said:
Hello all,
I have a HTC One M8 that i want to connect with my volkswagen RNS 315 device with build-in bluetooth but for some reason he doesnt see the device when i scan for bluetooth carkit. I am running my M8 on the latest Viper Rom with the lastest firmware.
Is there someone with the same issue around here.
Thanks already
Steven
Click to expand...
Click to collapse
Hi there.
In my previous car I had a RNS510. In the car under the seat was a bluetooth module that used a Nokia (yeah really) protocol to connect phones to it, called RSAP. Its only built in a specific range of VAG cars in a short periods. I was a lucky one (not!) to get one.....
To get Bluetooth connectivity I used an app from Play Store as described here: http://goo.gl/eJxOUF.
My advice: check if it is RSAP by using the trial version of the software. The actual software isn't free. I got functionality (not full tho) with the app.
Edit: it connected my DHD, OneX and my m8 with it.
MarckX said:
Hi there.
In my previous car I had a RNS510. In the car under the seat was a bluetooth module that used a Nokia (yeah really) protocol to connect phones to it, called RSAP. Its only built in a specific range of VAG cars in a short periods. I was a lucky one (not!) to get one.....
To get Bluetooth connectivity I used an app from Play Store as described here: http://goo.gl/eJxOUF.
My advice: check if it is RSAP by using the trial version of the software. The actual software isn't free. I got functionality (not full tho) with the app.
Edit: it connected my DHD, OneX and my m8 with it.
Click to expand...
Click to collapse
Thanks (dank je) MarckX,
I will try the trail version in a bit to see if it works.
greets
Steven
Tested with the trail version of RSAP but still nothing . even with a iphone 4s and nokia lumia. so i am stuck now.
greets
Steven
steviegolf said:
Tested with the trail version of RSAP but still nothing . even with a iphone 4s and nokia lumia. so i am stuck now.
greets
Steven
Click to expand...
Click to collapse
Hi Steven,
Just did some quick research and it seems to use a2dp. And this is supported by the m8 out of the box.
Not on Viper anymore, but can you confirm if the next lib is still there:
/system/lib/hw/audio.a2dp.default.so
If so, can you tell me if you are using sound mods like HK or Viper4android?
Edit: just trying to eliminate some possibilities. Strange thing is that your iPhone4 and the Lumia don't work either.
MarckX said:
Hi Steven,
Just did some quick research and it seems to use a2dp. And this is supported by the m8 out of the box.
Not on Viper anymore, but can you confirm if the next lib is still there:
/system/lib/hw/audio.a2dp.default.so
If so, can you tell me if you are using sound mods like HK or Viper4android?
Edit: just trying to eliminate some possibilities. Strange thing is that your iPhone4 and the Lumia don't work either.
Click to expand...
Click to collapse
This i cant find on my phone /system/lib/hw/audio.a2dp.default.so under device. i had HK installed but with the latest viper rom it didnt work for me. at the moment i use viper4android. i installed the RSAP app with installation tool for systemfiles. but still no connection with the rns315. Thanks for helping me out MarckX
steviegolf said:
This i cant find on my phone /system/lib/hw/audio.a2dp.default.so under device. i had HK installed but with the latest viper rom it didnt work for me. at the moment i use viper4android. i installed the RSAP app with installation tool for systemfiles. but still no connection with the rns315. Thanks for helping me out MarckX
Click to expand...
Click to collapse
Just downloaded Viper and it should be there. What I would do:
1. Dirty flash Viper
2. Remove all bt contacts
3. Rename your phone name to fi m8
4. Try again
If not: try to pair your phone with bt to another one. If that works, it has to be your RNS
Then I would check RNS firmware if it's the last version available.
Thanks MarckX,
Do you mean the rom or viper4android ?
steviegolf said:
Thanks MarckX,
Do you mean the rom or viper4android ?
Click to expand...
Click to collapse
Lolol, that's a valid question. The ROM I mean. Dirty flash, so you won't have to do a new setup.
Dirty flash means without a cleanup wipe ? Sorry i am a newbee with that ..
steviegolf said:
Dirty flash means without a cleanup wipe ? Sorry i am a newbee with that ..
Click to expand...
Click to collapse
Yup. Flash, no wipes. [emoji41]
ok gonna try it and let you know asap
thanks MarckX
steviegolf said:
ok gonna try it and let you know asap
thanks MarckX
Click to expand...
Click to collapse
Graag gedaan! Hope it helps [emoji41]
I have done the dirty flash and changed the name like you said MarckX but still nothing sadly. only good thing is that my phone screen of my RNS315 changed there is just standing Phone instead that there is no phone found or to connect text. Connecting with a iphone or lumia with bluetooth on the HTC took some time to work after 2 reboots.
Anyone that have installed 5.1.1 ( malaysk, boo, DSA or any other) has success with Bluetooth on KGL MTCB. Please been trying all available fix for it but can't get it to work it connects to MCU but does not show up in Bluetooth app. People with KDL have no problem with that its just KGL I'm thinking. Tried with DSA and typos a while back to solve it but all they said was change BT in setting and change apk to KGL BT apk, but did not worked. So please anyone has a solution help.
Thanks
Sent from my A0001 using XDA-Developers mobile app
No one has KGL with 5.1.1 installed ?
Sent from my A0001 using XDA-Developers mobile app
Luv-Kush said:
No one has KGL with 5.1.1 installed ?
Sent from my A0001 using XDA-Developers mobile app
Click to expand...
Click to collapse
I didn't dare to risk as I read lot of ppl complaining on all LP ROMs beside DSAs only on KLD. So I believe it is not only type (KGL or KLD) but also my version that wil/mayl make problems with KLD based MTCC ROMs.
So I will wait and see if devs will realise how complex this mixture of types, versions and tom bases is and will start to deal with it in manageable way which will incorporate adequate testing and true understanding what is going on under the surface. Mal is too amateurish and focused on cosmetics (and lacking even good will to support users in trouble), DSA is dealing with his KLD unit and his target is to fix his own problem (with great good will to enable everyone else to use his work but not ensuring that it will work 100% as he cannot test each and every combination) while booroondook is not even active here on XDA at all.
So, as for me is most important to have robust basic functions as I drive a car and not play with gadget, I decided to stick with KK which works 100%. Yes I would like to have LP (even I don't see any concrete benefits as all basic functions are same!) but I don't want to risk reliability.
Thanks for answer nobody seems to figure out what's causing this. Well I'm on 4.4.4 booroondook for now. Same I think malaysk is too much to deal with, I like small and simple close to OEM but with more app space. So what u think is good 4.4.4 ROM and what r u using. Thanks again I guess we have to wait for 5.1.1.
Sent from my A0001 using XDA-Developers mobile app
Luv-Kush said:
Thanks for answer nobody seems to figure out what's causing this. Well I'm on 4.4.4 booroondook for now. Same I think malaysk is too much to deal with, I like small and simple close to OEM but with more app space. So what u think is good 4.4.4 ROM and what r u using. Thanks again I guess we have to wait for 5.1.1.
Sent from my A0001 using XDA-Developers mobile app
Click to expand...
Click to collapse
I'm also on booroondook LP as it is FUSE with minimal bloatware. Then I installed few customised apps and closed modules and I'm very happy. Everything works 100% stable and performances are as good as possible on these units (you have to be realistic what you pay is what you get).
I'll wait and see how LP will progress and if it gets performance and stability same as KK then I will upgrade. No other reasons. Nothing new, nothing better currently.
---------- Post added at 06:02 AM ---------- Previous post was at 05:58 AM ----------
Luv-Kush said:
Anyone that have installed 5.1.1 ( malaysk, boo, DSA or any other) has success with Bluetooth on KGL MTCB. Please been trying all available fix for it but can't get it to work it connects to MCU but does not show up in Bluetooth app. People with KDL have no problem with that its just KGL I'm thinking. Tried with DSA and typos a while back to solve it but all they said was change BT in setting and change apk to KGL BT apk, but did not worked. So please anyone has a solution help.
Thanks
Sent from my A0001 using XDA-Developers mobile app
Click to expand...
Click to collapse
BTW which MCU version of KGL you have? Is it higher than 2.83? I would like to know if anybody has later KGL MCU.
Same MCU 2.83. So you said "I'm also on booroondook LP as it is FUSE with minimal bloatware. Then I installed few customised apps and closed modules and I'm very happy. Everything works 100% stable and performances are as good as possible on these units (you have to be realistic what you pay is what you get)." how is your Bluetooth works fine ?
Sent from my A0001 using XDA-Developers mobile app
pa.ko said:
I'm also on booroondook LP as it is FUSE with minimal bloatware. Then I installed few customised apps and closed modules and I'm very happy. Everything works 100% stable and performances are as good as possible on these units (you have to be realistic what you pay is what you get).
So the Bluetooth works fine for you on boo LP.
Sent from my A0001 using XDA-Developers mobile app
Click to expand...
Click to collapse
Luv-Kush said:
pa.ko said:
I'm also on booroondook LP as it is FUSE with minimal bloatware. Then I installed few customised apps and closed modules and I'm very happy. Everything works 100% stable and performances are as good as possible on these units (you have to be realistic what you pay is what you get).
So the Bluetooth works fine for you on boo LP.
Sent from my A0001 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes. Both phone and OBD2. Phone is with CM 13 custom ROM and my obd2 is chiepest Chinese elm 1.5
I'm stating my phone and obd2 as I believe that problems are not only caused by HU and it's ROM but also by the other side. Yes tgese HU have very rudimentary BT support and thus it is important to have other side which is compatible. If your phone works fine with some other device, it is possible that both phone and that other device support higher version of BT stack which is higher than supported by our HU.
Click to expand...
Click to collapse
Luv-Kush said:
Anyone that have installed 5.1.1 ( malaysk, boo, DSA or any other) has success with Bluetooth on KGL MTCB. Please been trying all available fix for it but can't get it to work it connects to MCU but does not show up in Bluetooth app. People with KDL have no problem with that its just KGL I'm thinking. Tried with DSA and typos a while back to solve it but all they said was change BT in setting and change apk to KGL BT apk, but did not worked. So please anyone has a solution help.
Thanks
Sent from my A0001 using XDA-Developers mobile app
Click to expand...
Click to collapse
Hi,
I have a KGL MTCB unit with MCU KGL-2.83 installed on Opel Astra J.
I upgraded my unit (original KK ) to DSA 5.1.1 and I dont have any problem related with Bluetooth. I have tested the DSA roms based on MTCB fw and the newest based on MTCC fw. The bluetooth works in both versions so.. i think it is not a KGL problem at least in my unit.
vch88 said:
Hi,
I have a KGL MTCB unit with MCU KGL-2.83 installed on Opel Astra J.
I upgraded my unit (original KK ) to DSA 5.1.1 and I dont have any problem related with Bluetooth. I have tested the DSA roms based on MTCB fw and the newest based on MTCC fw. The bluetooth works in both versions so.. i think it is not a KGL problem at least in my unit.
Click to expand...
Click to collapse
I don't know what I'm doing wrong but my phone is connected but cannot see in Bluetooth app nor in setting Bluetooth. My MCU kgl 2.83 Bluetooth in factory setting is on SD_BT. Can you please tell me what can be the problem. I put 4.4.4 and I see it in both app and setting. Also can you tell me what Bluetooth in setting you have.
Sent from my A0001 using XDA-Developers mobile app
Luv-Kush said:
I don't know what I'm doing wrong but my phone is connected but cannot see in Bluetooth app nor in setting Bluetooth. My MCU kgl 2.83 Bluetooth in factory setting is on SD_BT. Can you please tell me what can be the problem. I put 4.4.4 and I see it in both app and setting. Also can you tell me what Bluetooth in setting you have.
Sent from my A0001 using XDA-Developers mobile app
Click to expand...
Click to collapse
Its very rare ...
My BT is different in factory setting i have WQ_BC6. You could try changing the BT to the one that i have in factory settings.
Just a stupid question maybe...but... i never have synced my phone with the BT stock option, i dont know if you sync first the phone in the BT stock option later it is shown in the BT app.
I always setup my phone following these steps :
-> I open the BT app (not the BT stock option inside of settings ) and in the phone section (i dont remember the icon), press the button that search phones. Have you try this way?
Luv-Kush said:
I don't know what I'm doing wrong but my phone is connected but cannot see in Bluetooth app nor in setting Bluetooth. My MCU kgl 2.83 Bluetooth in factory setting is on SD_BT. Can you please tell me what can be the problem. I put 4.4.4 and I see it in both app and setting. Also can you tell me what Bluetooth in setting you have.
Sent from my A0001 using XDA-Developers mobile app
Click to expand...
Click to collapse
Try other BT options - Im not sure that each and every unit even it is KGL uses the same BT module!
Also be sure that you enable Address/Phone book sharing on your phone when you pair, as if you don't then BT will not work even it shows as paired (happened to me).
Link just in case the embedding doesn't work.
Youtube Link: https://youtu.be/SzP-soM7cqA
TOP: PX3
5.1.1
MTCD_GS_V1.49_1 Apr28 2016
RK 3188
Mali400
4x1.6ghz
1GB RAM
16GB ROM
1024x600
Bottom: PX5]
6.0.1
MTCD_GS_V2.11_1 Jan7 2017
RK 3368
PowerVR G6110
4x1.2-1.5ghz
2GB RAM
32GB ROM
1024x600
First time shooting a video like this, I can post an update but I'll throw all my findings here.
Some if my initial issues;
With the MTCD PX3 5.1.1 RK3188 You could change the ACC timeout so that the unit would stay on for a specified time, that is no longer in the menu. (Car was off for 3hours and it still fast started so drawing current constantly)
Radio constantly resets after turning the key off even though the Headunit only goes into sleep it's still resetting all radio stations.
Some applications in the Google play store report they are not compatible with this unit ie: iGO Navigation. I had to side load it but that's causing issues with the sys.txt file.
The launcher is damn ugly...
Always says failed to download license when coming out of sleep even with WIFI & 4G connectivity.
(Will update as I use it more)
Positives;
Unable to make it slowdown with Spotify & iGO Navigation running at the same time like it used to.
Audio quality is a LOT better and having subwoofer control on the EQ is great.
No longer have engine whine/hiss either.
(Will update as I use it more)
Antutu benchmark comparison:
PX3:
Overall: 27808
3d: 1220
UX: 13079
CPU: 10293
RAM: 3216
PX5:
Overall: 39047
3d: 9019
UX: 13397
CPU: 12768
RAM: 3863
Please feel free to ask any questions etc.
Cheers
Mat
You should measure the power draw when it has been off for an hour or more. The Intel head units basically goes to a deep hibernation, drawing next to nothing (no more than a normal head unit) while the system is sleeping, and then it comes instantly back on and is ready to use within a second or two from turning on the ignition. It may be that the new PX5 has a similar or the same feature, which is why you don't set the ACC timeout anymore. On the Joying Intel units you can change it between what they call "dormancy" or "shut off" in the special settings app they have, allowing you to turn it all the way off when ACC is removed if you wish to do so.
Hilari0 said:
You should measure the power draw when it has been off for an hour or more. The Intel head units basically goes to a deep hibernation, drawing next to nothing (no more than a normal head unit) while the system is sleeping, and then it comes instantly back on and is ready to use within a second or two from turning on the ignition. It may be that the new PX5 has a similar or the same feature, which is why you don't set the ACC timeout anymore. On the Joying Intel units you can change it between what they call "dormancy" or "shut off" in the special settings app they have, allowing you to turn it all the way off when ACC is removed if you wish to do so.
Click to expand...
Click to collapse
Thanks for the idea, I have a DC clamp meter I'll use tomorrow to double check.
Just tried the ignition again after getting home from being out with friends. So the car was off for 6 1/2hours this time, hit the key & it instantly started.
Still not happy about it resetting the radio stations every time however.
Cheers
Mat
Edit: also showing an issue I'm receiving, PX3 top, PX5 bottom.
The 6.0.1 Octacore has a lot of apps that it's not "compatible" with.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
On Intel MTCD devices, they removed the option to set ACC off timer.... due to the power consumption during deep sleep is negligible. I think some ROM update is neccessary to fix that small errors
It is strange that lots of apps were not compatible with the device as it is a RK3368 (two years old chip). Perhaps is sending a wrong device information to Google play ?
good review. Sound like a fellow kiwi? note that other resellers offer MCU and ROM upgrade on rk3188 to enable sub control. e.g. jy1.90
Hi,
About..
=> and having subwoofer control on the EQ is great. <=
Mine Xtrons pic..
(Never.. Buy an Xtrons hu again.. Bad support and to slow communication via email too.. excuses after excuses received!!)
Anyway: have fun with it
BrGd
Madyen
I like that new launcher!
ikerg said:
On Intel MTCD devices, they removed the option to set ACC off timer.... due to the power consumption during deep sleep is negligible. I think some ROM update is neccessary to fix that small errors
It is strange that lots of apps were not compatible with the device as it is a RK3368 (two years old chip). Perhaps is sending a wrong device information to Google play ?
Click to expand...
Click to collapse
Ok did some clamp DC current tests,
Headunit unplugged. vehicle left for an hour. 37-55mA current draw tested 3 times in 15minute period.
Headunit plugged in, sleeping 3hours then clamped. 97-130mA. That's a noticeable drain increase, that's enough to make a vehicle not start if it hasn't been driven in a week.
An ACC timeout adjustment would be great again. Lets say the unit locks up? My older unit would lockup every now and then and just be the wallpaper on screen (launcher crash) and I'd have to turn ignition off the ACC timeout time to reboot the headunit properly.
What happens now? Do I have to go pulling fuses.
And for the device information all it does is report as PX5, Where as the PX3 reports at RK3188. So I have a feeling that's an issue?
Hopefully updates get dropped soon through various vendors as at the end of the day they're all the same generic core board.
Cheers
Mat
hi.
have you managed to gain root access on the unit
Soo...
I think difference too small to upgrade PX3 to PX5.
On PX3 we can turn off all google services and enjoy fast HU
RazGame said:
Soo...
I think difference too small to upgrade PX3 to PX5.
On PX3 we can turn off all google services and enjoy fast HU
Click to expand...
Click to collapse
PX5 aside, the upgraded memory to 2gb is a major factor and provides an out of the box experience without feature limiting mods that may be difficult for some.
Note that I have upgraded my rk3188 to 2gb which improves the unit from boot to opening multiple apps and do not see the cpu as a bottleneck at all.
Seems to me the PX5 isn't ready for prime time as of yet, I'll stick to recommending the Intel for the time being. The power usage when sleeping is disconcerting, the Intel units draw something like 12-13 mA when in sleep mode, which is really great! That is actually a major feature for me, as I'd be annoyed waiting a minute or so for the thing to boot up in the morning.
Bit of an update, Had a few scenarios where radio has not reset now. I can't figure out what aspect causes it to reset but it does happen occasionally between a key cycle.
Apart from the launcher look which I hate I've warmed up to the unit. App switching, Spotify buttons are already linked to << >> > || etc. Haven't been able to lag the volume control, or GPS/Spotify/Pandora switching etc.
Appears With my usage It hovers around 900Mb Ram usage, so there is a chance the biggest change I'm noticing is the memory being 2GB now vs 1GB.
But does anyone have info about the DSP on these units? It sounds a lot clearer and less muddy now which is odd, I wasn't sure that was a change. But It's a welcomed one.
Any questions feel free to ask.
Cheers
Mat
Thanks for all the info
Is there any reference to the voltage on the RCA outputs on the unit? Is it too much to hope that with an improved DSP they can put out a bit more than the old 2V?
Sound quality wise does the unit seem more inline with more established aftermarket units now like Alpine etc (if you have any experience with them), Whats the main difference here?
Okay, I have some info on the MTCD 6.X.X MCU/Software Updates etc.
I also have the update.img & dmcu.img for 12th Jan 2017 for the PX5 unit. (According to Xtrons support, I haven't used yet.)
Link: https://dl.dropboxusercontent.com/u/876493/XDA/PB系列 Android 6.0 软件 (20170112 ).rar
If someone can host? I can temporarily dropbox them.
Cheers
Mat
The following is a Google translate of the .txt doc
2016-12-26
----------
**- Fixed "occlusion" of the weather application search box text
**- Repair Media DVD, up and down keys function
**- Adds interface hints for system high temperature testing
2016-12-27
----------
**- Update the text strong blue BC6, BC8 sdk, optimize the startup speed;
2016-12-29
----------
**- Update the text of strong Bluetooth BC6, BC8 sdk, handle Bluetooth music software reported information error is mistaken for A2DP service disconnected;
2016-12-30
----------
**- Update the exception of APP external device VOL
2017-1-3
----------
**- Repair the radio boot, fast access to non-frequency display problem
2017-1-4
----------
**- Fixes the problem of getting the third-party interface part to get the wrong state
**- Update the kernel CVBS system switch bug
2017-1-5
----------
**- Update the kernel OTG USB bug
**- Update the text strong Bluetooth BC6, to solve the problem of ringtones and dial-up crosstalk;
**- Update the drive recorder watermark display
**- Update the kernel touch screen GT911 bug
2017-1-6
----------
**- Synchronize RK code,
**- Repair USB recovery part of the upgrade can not, the version number changes to V6.0.7
**- Remove the RK's own watermark, making MJPEG and H264 USB display the same way
2017-1-7
----------
**- KERNEL update, repair the boot screen darkening and then restore the issue, G-SENSOR support (yet to be perfect)
2017-1-9
**Music to DVD crosstalk problem
**- Delete the recorder
**- Undo deleted google voice in previous version
**- KERNEL, G-sendor and 4g version of the conflict bug
**- KERNEL, Config for TPMS & BACKSCREEN
**- Release the Bluetooth phone, HOME, BACK, and other key restrictions
2017-1-10
**- Added ZTE MF833V 4G dangle support
**- modify the Bluetooth call state can operate the machine other applications (public version of the Bluetooth application)
In this case,
2017-1-11
**- Update Wenqiang MD725 Bluetooth OBD;
**- Update recovery V6.0.7, fix manually selected MCU upgrade unsuccessful BUG
**- Update Settings application to detect MCU upgrade file error
2017-1-12
**- Tire pressure built-in according to factory factory settings
**- Update billion even USB crash problem
**- Update the network video playback problem
**- Fixed "open the radio in the rear view, close the ACC, will re-open ACC, exit the rear view as the radio, the radio did not sound" problem
Click to expand...
Click to collapse
Hi,
(((excuse me)))
I have not previously responded to your "review" between these 2 hu because I felt it unfair to compare them both like the way you already did.. is not an honestly comparing -and maybe you knew it?- mate!!
Prove it.. you gonna or I hear you say.. right?
Ok here we go..
How it is possible in the Xtrons name that you compare both hu while you did not even have updated your old 5.1 hu at all?
Your 5.1 hu with an very old fw and mcu version while the newer 6.1 hu one is with the most newer fw and mcu come? now is that comparing you called fair
I don't know why you did it that? But maybe.. I may have my own thought of kind of conspiracy but I will keep it for myself and I don't tell it ofcourse
If you are really wanted to comparing both of them honestly then you should first of all update your old hu one first and then compare it with the newer one.. right?
TOP: PX3
5.1.1
MTCD_GS_V1.49_1 Apr28 2016
Bottom: PX5
6.0.1
MTCD_GS_V2.11_1 Jan7 2017
Long live the Xtrons king :laugh:
Have fun mate.
BrGd
Madyen
Madyen said:
Hi,
(((excuse me)))
I have not previously responded to your "review" between these 2 hu because I felt it unfair to compare them both like the way you already did.. is not an honestly comparing -and maybe you knew it?- mate!!
Prove it.. you gonna or I hear you say.. right?
Ok here we go..
How it is possible in the Xtrons name that you compare both hu while you did not even have updated your old 5.1 hu at all?
Your 5.1 hu with an very old fw and mcu version while the newer 6.1 hu one is with the most newer fw and mcu come? now is that comparing you called fair
I don't know why you did it that? But maybe.. I may have my own thought of kind of conspiracy but I will keep it for myself and I don't tell it ofcourse
If you are really wanted to comparing both of them honestly then you should first of all update your old hu one first and then compare it with the newer one.. right?
TOP: PX3
5.1.1
MTCD_GS_V1.49_1 Apr28 2016
Bottom: PX5
6.0.1
MTCD_GS_V2.11_1 Jan7 2017
Long live the Xtrons king :laugh:
Have fun mate.
BrGd
Madyen
Click to expand...
Click to collapse
I was comparing my 2 units, What I removed and what I was installing.
I think you care a little too much.
Cheers
Mat
Madyen said:
Indeed, if you say so, you knew about this and that but never know about an update of an new fw for your own hu and you keep it working and used with an very old fw?.. come on mate.. is that a joke?
As I said, Long live the Xtrons king
BrGd
Madyen
Click to expand...
Click to collapse
You're still making no sense. It's a vehicle specific fit unit, if another manufacturer did a PX5 version to suit I'd of purchased that.
I got my PX3 unit In September, Car didn't get driven between Early December-Mid January due to me breaking my wrist and having it pinned.
I still don't see what you're getting at, but okay. Take your salt elsewhere bud.
Cheers
Mat
FauxDreams said:
You're still making no sense. It's a vehicle specific fit unit, if another manufacturer did a PX5 version to suit I'd of purchased that.
I got my PX3 unit In September, Car didn't get driven between Early December-Mid January due to me breaking my wrist and having it pinned.
I still don't see what you're getting at, but okay. Take your salt elsewhere bud.
Cheers
Mat
Click to expand...
Click to collapse
It is better comparison by having both units completely updated to the last versions of mcu and firmware.
Lots of issues are related to mcu and the one for ypur px3 is very old
if I did help you, please hit "thanks" button
ikerg said:
It is better comparison by having both units completely updated to the last versions of mcu and firmware.
Lots of issues are related to mcu and the one for ypur px3 is very old
if I did help you, please hit "thanks" button
Click to expand...
Click to collapse
The PX3 is already sold, It's why I bought the PX5. I had about an hour with the PX3 after removing it before it got picked up.
Cheers
Mat
Hi,
on toengel.net I currently find no explicit reference. So here - where do I get the already circulating Android8 update for the 2018 series? I still have the last German official TPM171E_105.1.2.84 for 7303, 7363, 7373, 7383, 7393, 7503, 7803, 8303, 8503, OLED803, OLED903 installed. Google does not really help till the 5th page i give up if only announcements are to be found from Germany.
Philips itself has already updated the latest product sheets and officially reveals Oreo.
OK - found out that the 2018 TVs produced in 2019 have Android 8 right out of the box. Update will come in nearest future. Has anyone a leak of the 2018 Models Android 8 used in the 2019 produced TVs?
i also bought a 55pus7303 and i am waiting for the android 8.0.... but no news in sight. Lets hope it comes asap anyway the 7.0 is pretty stable. i m pretty impressed by how good is the tv for this price.
Hi,
really soon....
[email protected]
Where is this update? I have 803 and was promised beginning of january.. the software currently on this tv is rubbish
Hi,
you can deactivate the Philips Collection in the meantime... this will improve the HOME performance... https://toengel.net/philipsblog/201...m-android-tv-homescreen-ausblenden-entfernen/
[email protected]
Thanks for the tip, but it hasnt really made a difference.. for a tv that is this expensive the software should be much, much better
I agree the software so far is not good enough for the hardware
My wifi keeps turning off (have to power cycle for it to return) not good when power switch behind tv. Tried .75 and .84 firmware. Was hoping to find some adb commands to make it stay. no luck so far
Also this translated link of toengal works better for me https://translate.google.com/transl...-homescreen-ausblenden-entfernen/&prev=search
Hi all, Got an 7303 model 43" currently downloading update via tv update not android update
Yours Ever faithful Servant
Grassden32
Ps Rebooting tv!!
Hi,
correct: https://toengel.net/philipsblog/201...vs-mit-android-tv-8-oreo-tpm171e-107-0-222-1/
[email protected]
Installed 8.0 last night. Works better. The home interface is much better in my opinion
Where is this update? Does phillips even know?
Toengel said:
Hi,
correct: https://toengel.net/philipsblog/201...vs-mit-android-tv-8-oreo-tpm171e-107-0-222-1/
[email protected]
Click to expand...
Click to collapse
Is this oficial? Let's wait for OTA update then.
So everyone is happy with the wifi turning off automatically? and not being able to turn it on without a hard switch off from the power socket - seriously this is a major issue that has been ignored and all my network connected devices that i want to link are affected - this is not right
Gogolakis said:
i also bought a 55pus7303 and i am waiting for the android 8.0.... but no news in sight. Lets hope it comes asap anyway the 7.0 is pretty stable. i m pretty impressed by how good is the tv for this price.
Click to expand...
Click to collapse
I have had the opposite experience with my 43pus7303 on both Nougat and Oreo. There is lag and stutters of Android all around the system. Even the animation when switching cable channels lags. Scrolling channels menu stutters and even the volume up or down isn't in real time.
zanziok said:
I have had the opposite experience with my 43pus7303 on both Nougat and Oreo. There is lag and stutters of Android all around the system. Even the animation when switching cable channels lags. Scrolling channels menu stutters and even the volume up or down isn't in real time.
Click to expand...
Click to collapse
There is lag for sure. I also experience it...but I haven't yet seen a really fluid TV because you don't really need it. I use my TV for kodi netflix YouTube and being a PC monitor...and at this pricetag it's perfect
Toengel said:
Hi,
really soon....
[email protected]
Click to expand...
Click to collapse
Hi Toengel, I have the Philips 50PUT7303/56 model, which is basically the pus7303 but UAE model. Any idea when we might get the OREO update?
The latest update we have is the TPM171E_105.001.044.009 from December 2018.
Thanks.
After the android tv 8 oreo for tpm171e update, HBO GO is not working anymore!
"Playback error occurred, please try again. (5.1)" is displayed when I try to play any of the episodes or film ....
Options: Retry or Back. If I choose Retry, the appis blocking the TV and I have to switch of/on the tv...
Tried to reinstall, uninstall/reinstall the app.. no luck..
Cleared android and app cache.. no luck!
restarted android... no luck!
I CAN NOT VIEW GAME OF THRONES!!!
Any suggestions?
Hi rgabi88, Is there any solution regarding your problem?
Thanks, Laszlo
I have done a stupid mistake to upgrade my firmware to latest version.
My TV is 55PUS7303/12, now i have version TPM171E_R.107.001.038.000.
I just don't like the Home screen, and now headset volume is controled separatelly from settings menu, before the update the volume was sort of master volume, also for tv speakers, and for headset.
I downloaded previous firmware from toengel.net/philipsblog/firmware-archiv/, but it seems I can't downgrade, the tv says it's older than the installed one.
The file that I got is named autorun-TPM171E_R.107.000.239.004
Do you guys have any idea ?
Hello guys, I wanna know that you who have updated your Pixel 2 XL to ANDROID 11, how is the experience? How is the battery life? Is it performing better than the ANDROID 10? How's the camera? Is it worth to upgrade? Thanks in advance.
in my case, the battery is better than 10. Performance is better. But it is still some small bug.
Camera is an app, the quality is depent on app version, not the android version.
quro13 said:
in my case, the battery is better than 10. Performance is better. But it is still some small bug.
Camera is an app, the quality is depent on app version, not the android version.
Click to expand...
Click to collapse
I'm updated with the latest google camera app. So, you are saying that the camera will be as it is.. right?
and which kind of bug you are facing bro? If you can help me giving these information. I'll upgraded to Android 11. Thanks in advance.
Sometimes receiving call , it is automatic turn on Speaker. Other people play games, the small horizoltal line at the bottom does not hide.
I have problem with Blackberry keyboard too.
quro13 said:
Sometimes receiving call , it is automatic turn on Speaker. Other people play games, the small horizoltal line at the bottom does not hide.
I have problem with Blackberry keyboard too.
Click to expand...
Click to collapse
Thanks a lot brother! <3