![(@r8[]np4nd4](/tmc/data/avatars/l/153/153664.jpg?1711743159){kind=avatar}
(@r8[]np4nd4
Member
I still have the screen reboots / power cuts after wake up. Does the extreme firmware perform better with this?
-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
Longer term Ohmmu experiences?
- Thread starter Durzel
- Start date
Haven't had that issue. What I do see is battery will discharge (load shared by car and battery) to anywhere from 49-80% (12.99-13.2v) then recharge back to 100%. No warnings or messages. Seems to be working.
Ok I removed it. No messages in service or notifications. But each charge/discharge cycle was greater. First time to 89%. Then 49% lastly it was at 67 and dropping using 25 amps. Each discharge cycle would go deeper and at a higher amperage. Last time was draining at 25 amps. Volts hold at 13.1 or so until about 49% and stop at 12.99 which I have also seen on an AGM. V4+ reached 106f but not overheat shown. I wasn’t brave enough to continue but it was like trying to make a failure and not succeeding. No warnings ever generated.
mstatkus
Member
Wow 25A .. I didn’t see a load over 9A ever. I also did not ever see it go below 90%.
I actually wouldn’t mind knowing what it’s doing while my trunk latch is busted. Just stays on and seems to draw 0-2A. Then seems to cycle a charge to the battery for a total of 54 minutes 25A charging off my wall connector.
I actually wouldn’t mind knowing what it’s doing while my trunk latch is busted. Just stays on and seems to draw 0-2A. Then seems to cycle a charge to the battery for a total of 54 minutes 25A charging off my wall connector.
On previous versions it would start at 25amps for a moment then reverse and charge back to full then slowly bring the battery voltage back to 13.2 and stop. Now it is behaving as above keeping in mind I'm on a older software version that hasn't changed in a month of more.
mstatkus
Member
Mine was blank for configuration until I installed Model 3 firmware. Then is says Tesla Model 3.
(@r8[]np4nd4
Member
When I selected update, OHMMU2 was not on the list. The software is updated at the server so if select update configuration, the version selected for your model will be the most current.
The config naming convention is odd indeed.
Logically, if using the latest debug Android apk or iOS v2 app, and choosing the same car, on any given day, we should all be pulling the same config with the same naming convention showing in the app.
Unless there are multiple flavors of v4+s out there (likely)...
But even then each combo of v4+ revision, car model and latest config pulled on T0 should result in the same matching config being applied.
Logically, if using the latest debug Android apk or iOS v2 app, and choosing the same car, on any given day, we should all be pulling the same config with the same naming convention showing in the app.
Unless there are multiple flavors of v4+s out there (likely)...
But even then each combo of v4+ revision, car model and latest config pulled on T0 should result in the same matching config being applied.
mstatkus
Member
Follow up post service center.
- trunk latch broke. New one works better than new.
- louver alert is from firmware updates and less critical software updates in this area due to low priority. They said a lot of alerts pop up in service mode and aren’t actionable.
I may drop it back in soon to keep testing.
- trunk latch broke. New one works better than new.
- louver alert is from firmware updates and less critical software updates in this area due to low priority. They said a lot of alerts pop up in service mode and aren’t actionable.
I may drop it back in soon to keep testing.
Anyone have luck applying different configs and having them stick with the debug Android apk?
It took me forever to get EXTREME to take and now (and before) no other profile will actually reflect even if the app reports it pulled successfully.
App permissions adjusted as Ohmmu wants (unrestricted BT and phone battery, app blacklisted for shallow and deep sleep).
Also this fun little error pops up from time to time.
It took me forever to get EXTREME to take and now (and before) no other profile will actually reflect even if the app reports it pulled successfully.
App permissions adjusted as Ohmmu wants (unrestricted BT and phone battery, app blacklisted for shallow and deep sleep).
Also this fun little error pops up from time to time.
mstatkus
Member
120mi round trip. I see it dipped to 32%. No issues so far.
Good. What revision of the v4+ (there are a few, despite the same external label)?
and what config (were you finally able to apply the Model Y config?).
Give the car/battery combo at least one month and ideally one or two software updates' worth of time to see if any errors or notifications creep in.
and what config (were you finally able to apply the Model Y config?).
Give the car/battery combo at least one month and ideally one or two software updates' worth of time to see if any errors or notifications creep in.
mstatkus
Member
I got mine last Sept last year (11 mo / 6 cycles). Was before some got tweaks after with firmware.
I just downloaded the Model Y config last month. Sean said if I have issues to use the Extreme one to get more logging. Battery was back to 100% this AM.
I may reinstall later today. Perhaps I jumped too soon. Never got any warnings just wasn't used to the extreme charge discharge cycles.
mstatkus
Member
Yeah I have no idea how far down the lead acid goes. I thought the same thing. Seems like sometimes when its charging the car it doesn’t charge the battery or vice versa.
Similar threads
