Notices
GS - 4th Gen (2013-2020) Discussion about the 2013 and up GS models

GROM VL2 installed

Thread Tools
 
Search this Thread
 
Old May 29, 2019 | 06:20 AM
  #256  
maclem8223's Avatar
maclem8223
Pit Crew
 
Joined: Jun 2011
Posts: 225
Likes: 37
From: Tennessee
Default

Install went well. I'll post some pics once I can clean it up a bit more. My main issue right now is the back-up camera. It was working at first right after the system booted up. Went through the process of installing gapps and any updates needed to the vline. Running the current beta version now and the back-up camera isn't working. When I put it in reverse the screen will flash like it is going to the camera but will just pop back up with the same screen I was on if that makes any sense. Overall though I love it so far regarding capability.
Reply
Old May 29, 2019 | 07:05 AM
  #257  
jdpdata's Avatar
jdpdata
Thread Starter
Instructor
 
Joined: Mar 2017
Posts: 1,159
Likes: 452
From: CA
Default

@maclem8223 do you have a '13-14 GS? This is known to occurred on those models. Contact GROM support, they will give you patch to fix this issue. My 2015 GS backup camera work right out of the box and continue to work without any issues.
Reply
Old May 29, 2019 | 07:54 AM
  #258  
HUSKERnKS's Avatar
HUSKERnKS
Lead Lap
 
Joined: Jan 2011
Posts: 655
Likes: 108
From: South Carolina
Default

Can anyone confirm they are still supporting Carplay (not Airplay) in the most recent firmware? They said it is not a guaranteed feature long term.

Steve
Reply
Old May 29, 2019 | 08:15 AM
  #259  
maclem8223's Avatar
maclem8223
Pit Crew
 
Joined: Jun 2011
Posts: 225
Likes: 37
From: Tennessee
Default

Originally Posted by jdpdata
@maclem8223 do you have a '13-14 GS? This is known to occurred on those models. Contact GROM support, they will give you patch to fix this issue. My 2015 GS backup camera work right out of the box and continue to work without any issues.
Yeah, its a '14. I'll pull the firmware version # and all that good stuff then contact them. Thanks!
Reply
Old May 29, 2019 | 09:02 AM
  #260  
yelloiroc's Avatar
yelloiroc
Driver School Candidate
 
Joined: Feb 2019
Posts: 42
Likes: 14
From: MA
Default Problem after firmware update.

After the most recent software/firmware release I now have a black screen with some high pitched whining sounds. This happened the instant I selected update firmware. I tried doing the firmware update process described on groms page for issues with a black screen but no change.

Oddly enough and likely unrelated about five mins after that a dtc code came on for a wheel speed sensor. Trac. Control was disabled, steering wheel controls stopped working, cruise control stopped working, speed read outs through odbii connected devices stopped and car no longer shifts to 5th or 6th gear. A battery discount cleared up dtc code. Disconnecting vline brought normal operator back to steering when and Lexus command device, but still no 5th or 6th gear. Vline also stopped working.
Reply
Old May 29, 2019 | 09:21 AM
  #261  
maclem8223's Avatar
maclem8223
Pit Crew
 
Joined: Jun 2011
Posts: 225
Likes: 37
From: Tennessee
Default

Originally Posted by yelloiroc
After the most recent software/firmware release I now have a black screen with some high pitched whining sounds. This happened the instant I selected update firmware. I tried doing the firmware update process described on groms page for issues with a black screen but no change.

Oddly enough and likely unrelated about five mins after that a dtc code came on for a wheel speed sensor. Trac. Control was disabled, steering wheel controls stopped working, cruise control stopped working, speed read outs through odbii connected devices stopped and car no longer shifts to 5th or 6th gear. A battery discount cleared up dtc code. Disconnecting vline brought normal operator back to steering when and Lexus command device, but still no 5th or 6th gear. Vline also stopped working.
You to huh? My CEL has come on, TRAC OFF warning in gauge cluster along with a message, 'Check Access System with Elec. Key'. LOL, this isn't starting out well for me.

Edit: This started after updating to the Beta for me. Just installed everything last night but didn't have a chance to drive it. So I first noticed it this morning on my way to work. Car is running fine though. Maybe they don't want us installing the Beta. I like being a guinea pig though. I'll go back to the latest release version.

Last edited by maclem8223; May 29, 2019 at 09:25 AM. Reason: Update
Reply
Old May 29, 2019 | 09:28 AM
  #262  
jdpdata's Avatar
jdpdata
Thread Starter
Instructor
 
Joined: Mar 2017
Posts: 1,159
Likes: 452
From: CA
Default

Originally Posted by yelloiroc
After the most recent software/firmware release I now have a black screen with some high pitched whining sounds. This happened the instant I selected update firmware. I tried doing the firmware update process described on groms page for issues with a black screen but no change.

Oddly enough and likely unrelated about five mins after that a dtc code came on for a wheel speed sensor. Trac. Control was disabled, steering wheel controls stopped working, cruise control stopped working, speed read outs through odbii connected devices stopped and car no longer shifts to 5th or 6th gear. A battery discount cleared up dtc code. Disconnecting vline brought normal operator back to steering when and Lexus command device, but still no 5th or 6th gear. Vline also stopped working.
WTF!? Do you have some device connected to your ODB2 port? And you think a bad GROM firmware update caused all your issues? I'd remove whatever you have connected to ODB2 first. I don't see how VL2 could cause any of those DTC codes and malfunctions, but you never know I guess.
Reply
Old May 29, 2019 | 09:29 AM
  #263  
jdpdata's Avatar
jdpdata
Thread Starter
Instructor
 
Joined: Mar 2017
Posts: 1,159
Likes: 452
From: CA
Default

Originally Posted by maclem8223
You to huh? My CEL has come on, TRAC OFF warning in gauge cluster along with a message, 'Check Access System with Elec. Key'. LOL, this isn't starting out well for me.

Edit: This started after updating to the Beta for me. Just installed everything last night but didn't have a chance to drive it. So I first noticed it this morning on my way to work. Car is running fine though. Maybe they don't want us installing the Beta. I like being a guinea pig though. I'll go back to the latest release version.
Where did you get the beta firmware? Are you sure you installed the correct version for your car?
Reply
Old May 29, 2019 | 09:32 AM
  #264  
maclem8223's Avatar
maclem8223
Pit Crew
 
Joined: Jun 2011
Posts: 225
Likes: 37
From: Tennessee
Default

Originally Posted by jdpdata
WTF!? Do you have some device connected to your ODB2 port? And you think a bad GROM firmware update caused all your issues? I'd remove whatever you have connected to ODB2 first. I don't see how VL2 could cause any of those DTC codes and malfunctions, but you never know I guess.
More than likely it is my fault for installing the Beta; however, I do have a T-Mobile SyncUP hotspot in my OBD2 port. Didn't even think about that being the cause.
Reply
Old May 29, 2019 | 09:34 AM
  #265  
maclem8223's Avatar
maclem8223
Pit Crew
 
Joined: Jun 2011
Posts: 225
Likes: 37
From: Tennessee
Default

Originally Posted by jdpdata
Where did you get the beta firmware? Are you sure you installed the correct version for your car?
You can enable Beta for the device and then it pops up.
Reply
Old May 29, 2019 | 09:37 AM
  #266  
jdpdata's Avatar
jdpdata
Thread Starter
Instructor
 
Joined: Mar 2017
Posts: 1,159
Likes: 452
From: CA
Default

Originally Posted by maclem8223
More than likely it is my fault for installing the Beta; however, I do have a T-Mobile SyncUP hotspot in my OBD2 port. Didn't even think about that being the cause.
Originally Posted by maclem8223
You can enable Beta for the device and then it pops up.
Ah, I see now. yeah, don't install anything not released by GROM officially. I know they're working on enabling ODB2 read-outs but that's not even close to being ready yet. Hope your issues is not permanent.
Reply
Old May 29, 2019 | 09:57 AM
  #267  
maclem8223's Avatar
maclem8223
Pit Crew
 
Joined: Jun 2011
Posts: 225
Likes: 37
From: Tennessee
Default

Originally Posted by jdpdata
Ah, I see now. yeah, don't install anything not released by GROM officially. I know they're working on enabling ODB2 read-outs but that's not even close to being ready yet. Hope your issues is not permanent.
Nah, I can revert back to regular user and the released updates pop-up. Re-installed the firmware update and it fixed the back-up camera. The issue with the warning lights is not the hotspot as there is no change when I clear the code and have it unplugged. So I'm thinking it is related to the beta software version of VLine that I installed. I will undo it just don't have to re-download the recent released version right now. Hopefully that fixes the codes.
Reply
Old May 29, 2019 | 10:40 AM
  #268  
yelloiroc's Avatar
yelloiroc
Driver School Candidate
 
Joined: Feb 2019
Posts: 42
Likes: 14
From: MA
Default

Originally Posted by maclem8223
Nah, I can revert back to regular user and the released updates pop-up. Re-installed the firmware update and it fixed the back-up camera. The issue with the warning lights is not the hotspot as there is no change when I clear the code and have it unplugged. So I'm thinking it is related to the beta software version of VLine that I installed. I will undo it just don't have to re-download the recent released version right now. Hopefully that fixes the codes.
It would be illogical to think it was the hotspot plugged into the of port. I reached out to groms about the issue but did not mention the dtc codes as I didn't want them to jump to the conclusion that is was an outside force that may have caused similar to how another user did. My only reply from them this far is "what did I install software or firmware".
Reply
Old May 29, 2019 | 11:05 AM
  #269  
jdpdata's Avatar
jdpdata
Thread Starter
Instructor
 
Joined: Mar 2017
Posts: 1,159
Likes: 452
From: CA
Default

Originally Posted by yelloiroc
It would be illogical to think it was the hotspot plugged into the of port. I reached out to groms about the issue but did not mention the dtc codes as I didn't want them to jump to the conclusion that is was an outside force that may have caused similar to how another user did. My only reply from them this far is "what did I install software or firmware".
Well that's logical that they would ask what software or firmware you were running. Software is the interface of VL2, firmware correspond to the underline OS of the device. They need to know exactly what version you were running to diagnose your issues. Withholding those info will only delaying their response to help you. I hope they will continue to support you. Most companies would void your warranty if you installed unsupported experimental BETA software/firmware.
Reply
Old May 29, 2019 | 11:11 AM
  #270  
maclem8223's Avatar
maclem8223
Pit Crew
 
Joined: Jun 2011
Posts: 225
Likes: 37
From: Tennessee
Default

Re-installed 'Release' versions and backup camera is working as intended along with everything else. Still have 'TRAC OFF' and a CEL with a DTC for Speed Position Sensor. I'll clear it tonight and see if it comes back.
Reply



All times are GMT -7. The time now is 03:00 PM.