Jump to content
  • Welcome Guest To Mopar1973Man.Com

    We are a Dodge Ram Cummins Turbo Diesel forum. We are very friendly and helpful group of Dodge Ram Cummins owners. We will try to keep your truck running the best we can and provide information for diagnostics, repairs and even guide you on the best replacement parts to use. 

     

    Registration is free. Registering on the site will provide access to many more things like...
     

    • Contribute to the Forum being able to ask questions and get support for your Dodge Ram Cummins.
    • Contribute to Article Database adding your ideas and suggestions.
    • Classified Ads posted by the members. Post up your used parts and vehicles.
    • Member Garage where you can proudly display your vehicles and modifications that you have done to them.
    • Download files, documents, and Quadzilla Adrenaline tunes for your truck.
    • 911 Support Network. We've got a group of members will to aid you if your truck breaks down on the road.
    • Reduced Advertisements displayed to you.

kzimmer

App permanently crashing after gallon trip calibration

Recommended Posts

@Me78569 I thought I'd make a new post instead of pm'ing or stuffing this into an old thread.

 

I decided to calibrate the new MPG feature. I started at a MPG offset of %150. I reset the gallon trip and drove 350.3kms. Gallon trip showed 13.9 Gallons, and I put in 14.719 gallons. So 150%{1+[(14.719-13.9)÷13.9]} = 158.838%.

 

Key on, truck not running, quad open and connected. Went to settings, changed MPG offset from %150 to %158.84. Instant crash. And now every time I open the app it instant crashes, even after device reboot and truck key off/on. 

 

I'm guessing that if I clear cache and data from the app, it'll come up again. And if I do that I'll lose my tune since I've made a couple changes and I don't have a backup because the exporting feature is still bugged for my device. So I guess when I have time I'll go through the directories and try to manually export the tune before I wipe the app.

 

One thing to note is I did not turn off mpg offset in settings before I changed 150 to 158.84.

 

All in good fun and f bombs, haha.

Share this post


Link to post
Share on other sites

The only thing I could think of is dumping the app and reinstall the app again... Yeah, the changes will be gone but at least you'll get back to working. I would for sure hook up with @Me78569 report this bug so it can be repaired. You might also just load up a fresh copy and just do the calibration again and see if the decimal is the problem.

Share this post


Link to post
Share on other sites

no clue.  I honestly dont know about decimal numbers for mpg....  It might get pissy about that.  Beyond that Quadzilla power will have to help I am not in on the dev of the app side.

Share this post


Link to post
Share on other sites
1 minute ago, Me78569 said:

no clue.  I honestly dont know about decimal numbers for mpg....  It might get pissy about that.  Beyond that Quadzilla power will have to help I am not in on the dev of the app side.

 

That's the only thing I can see that is going wrong. @kzimmer is changing from 150 to 158.84 that would be the only thing I could see that might create a hang. @kzimmer I would try the new copy with just 158 and see if it passes.

Share this post


Link to post
Share on other sites
5 minutes ago, Mopar1973Man said:

@kzimmer I would try the new copy with just 158 and see if it passes

 

I'll definitely try this next time I'm in the truck. Might not be until Friday.

 

@Me78569 do you know if this variable is a floating point or just an integer?

 

@Quadzilla Power might be able to help.

Share this post


Link to post
Share on other sites

Yea looking at the profile file I dont think the Iquad app knows how to handle the decimal. 

 

 

No idea i am not versed in the iquad app code.

Edited by Me78569

Share this post


Link to post
Share on other sites

All the variables (even ones with decimals) are passed as integers. There is just an offset multiplied into the number when passing that gets taken into consideration in the code. There aren't any floating point numbers passed from the app to the device. There are some inside the Adrenaline and probably some inside the app, but none in the interface. 

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×