FAQs

If the joystick on Adventure is scrolling / panning the map even through you are not touching it, go to Settings in the Controller app and adjust sensitivity – reduce it in the direction you are getting the unwanted movement until it stops.

Is there going to be update to CI Pad operating system? Yes! Update to Android 11 in September 2023 and update to Android 13 later in 2023. (v4 and v4b units)

If your particular bootloop is caused by the power button, this is what do to:

1. Remove the metal plate covering the buttons.
2. Remove the silicone membrane covering the buttons.
3. Make sure there is no water, mud or debris under the membrane – wipe it dry/clean with a soft dry cloth / paper napkin.
4. Apply silicone oil generously. If there was dust or mud under the silicone membrane, wipe the applied silicone oil clean with dry cloth or paper towel/napkin and repeat the process until the buttons a completely clean.
5. If you are using silicone spray, let it sit until the propelling agent completely evaporates (at least 10 minutes) before you will put the silicone membrane back.
6. Put the silicone membrane and metal plate back.

You can use the above procedure also as a pre-caution to prevent problems with the buttons in the future.

Please watch this video how its done.

If the bootloop is caused by water getting inside the CI Pad, there is really not much you can do besides opening all the ports and letting the water evaporate. You can help it by using hair dryer set to low and blow air into one of the ports.

There are three possible causes:

1. Damaged operating system. That usually only happens when you are trying to perform the “Erase all data (factory reset) through the system Reset option (which you should NOT do – search the FAQs for CI Pad reset), while the battery is low on your CI Pad and it runs out of power before the reinstallation can complete. There is no other fix but sending it to us for a complete operating system re-flash
2. Water entered inside the CI Pad and is causing short circuit somewhere. If you suspect this could be the case, open all port seals and keep CI Pad in a dry, warm place to let the water evaporate. If you are lucky, the CI Pad will come to live. Do NOT try to charge CI Pad when you suspect water could have gotten inside (problems started during or shortly after heavy rain) or you will cause more damage.
3. Power button is being constantly pressed, which can happen by the button being damaged, the silicone membrane covering the button moved out of place and is pressing onto the button or water got inside (this is covered in a separate FAQ).

We have users showing us bootloop, while they actively hold down the power button with their finger. If you do that, the CI Pad will bootloop, because that is a function, not a problem. When you hold down the power button, you are telling CI Pad to start up. But when you keep the power button pressed, you are telling the CI Pad to shut down. So as soon as at least the very basic parts of the operating system load (you get our logo on the boot screen), CI Pad starts thinking you want to shut it down, because you keep the button pressed. So please, don’t do this!

If the bootloop is kept going long enough, it will completely drain the battery and possibly destroy it. When that happens, you will not be able to charge CI Pad again and it will appear to be dead. The only solution for this is to send it back to us for repair. So, please, try to avoid bootlooping CI Pad and when it happens, try to stop it as soon as you can (there is a specific FAQ on this).

NO.

CI Pad is not designed to be kept on your bike all the time. You should take it off even when just parking the bike over night.

There are several reasons:

1. There is something called reverse current – if you keep CI Pad connected to a power source that is not powered, it will slowly drain CI Pad battery. That applies to any power source, not just our power source for motorcycles – the same will happen if you keep the CI Pad connected to your USB wall charger, but unplug the charger from the wall socket. Or if you forget the CI Pad connected to your laptop and the laptop shuts down – the laptop starts draining power from the CI Pad and in this specific case the damage to CI Pad battery can actually happen very quickly. Even during one night with CI Pad fully charged.
   
   If you keep CI Pad being drained like that long enough, the CI Pad battery will get completely depleted and you will not be able to charge it again.
   
   So if you heard users say: “I just came to my bike one day and CI Pad did not start”, that’s exactly what happened to them. The only fix is to send the CI Pad to us for repair service.
   _
2. CI Pad is not designed to withstand the elements permanently. If you keep it exposed to hot summer sun or winter cold all the time, it will eventually quit on you. These limitations are clearly stated in the User manual.

To fix it you will need to externally download the updated version of the Manager app. Please follow these 3 simple steps:

• download the file here: https://drive.google.com/file/d/1IHtnpuzvkzrN0M9iK70z7fGd4eAIWw7X/view?usp=sharing
  • directly to the CI Pad or to your PC and load it to the CI Pad via USB.
• find the file in the File Manager, click on the file (apk) and it starts automatically, then click Done
• if the endless download still occurs: go to Settings – Apps & notifications – CARPE Manager – Storage and press both Clear Storage and Clear Cache

This is in fact an experimental function and might not work reliably. This (just like most other) features will be completely overhauled on new Android 11 update, so please hold on (and please do not ask for support for this feature until the Android 11 update is rolled-out).

Absolutely not.

DMD2 is just one of the pre-installed apps and you can use anything else. Here is a video guide, how to disable DMD2 as the default Home screen launcher on CI Pad.

Go to System Settings (swipe down twice to reveal notification area, click on the small cogwheel on the right), search for Home (if you set other than English as your system language, search for your language alternative). Among the search results there will be a sub-menu “Home app”. Click on that, click on “Home app” and change default to Lawnchair. If searching did not work for you, go to “Apps” in the System menu, open sub-menu “Default apps” and yet another sub-menu “Home app” and change to Lawnchair.

Following that DMD2 will show only when you open it (just like you would open any other app), while in all other cases you will get our standard Home screen.

If you are having GPS issues, first of all check that the Google Assisted Location is turned off in the system “Location” settings under the “Advanced” tab. Some apps are by default trying to turn this function on, especially the Google Maps. So if something asks “Do you want to use Google Assisted location to improve your position lock” or something along those lines, respectfully decline.

For v4 and v4b units we are implementing Google Assisted location support, so you will be able to use that Android function after the update.

If that did not help:

1. Check that the GPS antenna is not covered. The antenna will be covered, if you inserted CI Pad into the Holder up-side-down. The GPS antenna is next to the M8 connector, in the middle of the short CI Pad side.
   
2. on v3 and v4 units you can try to reset the GNSS chip through the GPSTune app, if you have it on your unit (not all CI Pad units have access to that app)
   
3. on v4 and v4b units please wait for the Android 11 update. The GPS is completely reworked and it will work a lot better.

GPS antenna location:

Before you start resetting and experimenting with GPS, please make sure the problem really is general. If you have an issue with GPS only sometimes and/or only in some locations, it is probably caused by weak GPS signal and you should just leave the GPS alone, because you might do more damage than good, especially if you try to experiment with some awkward third party apps promising to improve your GPS (they generally don’t do anything and if they do, it is usually to the worse).

GPS signal is generally weak (and your position lock might not be precise and/or it will take a long time to achieve the position lock) in the following situation:

1. there is only a limited view of the sky (tall buildings around narrow street, deep valleys surrounded by high hills/slopes)
2. heavy rain clouds, storm, heavy rain (water generally blocks GPS signal)
3. high solar activity (ruins precision even with good signal)
4. GNSS systems are intentionally disrupted. This can happen locally and in some cases even globally. You can search the web for GPS disruptions – there are communities actually keeping track of these events. It usually relates to wars and similar conflicts around the globe or protection of specific high value (usually military) facilities

CI Pad is completely sealed – the plastic parts are glued shut to prevent water ingress (which is one of the reasons for repairs being difficult, because we literary have to rip the CI Pad open and consequently replace the plastics).

As difficult as it is to repair, it makes the CI Pad also quite water resistant.

In normal case the only way water can seep inside the CI Pad is improperly closed port flap / seal. There is whole section about that in the User manual – you really need to push the port flaps completely in to make them flush the the CI Pad body. When they are new, it actually takes quite some force to push them into the correct position and e.g. the SD card and SIM flaps hold in place so well (when they are inserted properly), that it is not really easy to even make them out again.

So we are sorry to break it to you, but if water got inside your CI Pad, it is near certain that you are to blame for not closing the ports properly or not replacing them when they got damaged.

To give you a better idea, let us ask a question: Where do you think there are most water damage cases on the planet? Yes, we heard you! You just whispered Norway (or other country with frequent and heavy rains). Nope. The correct answer is Spain – one of the most arid counties in Europe and that for sure tells the story where most water issues come from (not the device, but the user;-).

It could also be that if you keep opening and closing the port flaps frequently, they are worn out or damaged. If you suspect this, please get a replacement – they are available on our eshop as spare parts.

In case you are having persistent software issues that cannot be fixed (please search our FAQs for a specific problem you might be having), you might have to reinstall the operating system on CI Pad and start over.

Before you start resetting and reinstalling things, consider the gravity of your issues – reinstallation should always be the solution of last resort for issues you simple cannot live with. Not something you do every day / frequently, because it can bring issues on it’s own. If nothing else, you are starting clean, which means you loose your data and will need to install all apps again.

Also consider the upcoming Android 11 update for v4 and v4b units – we strongly recommend to wait with reinstallation until the update is released – all will be wiped during the update and it is very likely that whatever issues you are having now will go away after the update.

So now, if you are really convinced you absolutely have to reinstall the CI Pad right now, here is how to do it on v4 and v4b units:

1. Do NOT use “Erase all data (factory reset) option” in the system settings (Reset options).
2. Make sure the CI Pad is charged to at least 60%.
3. Go to the Carpe Manager app – Repair&Update tab and select Re-install&Reset option.
4. Once you confirm the reset a download will start, following which the process is fully automated.
5. It will take minimum 10 minutes, but possibly longer depending on how fast the download will be – a massive installation file is downloaded to CI Pad to make sure the installation comes from a correct and uncorrupted installation file.
6. Do NOT use CI Pad until the re-installation completes – once the download start, simply put it down on the table and leave it be until the process completes.
7. Do NOT power down CI Pad during the process and do NOT disconnect it from internet.
8. If the screen saver is enabled on your CI Pad, the screen might go dark during the process – do not worry about it, the installation continues on the background.
9. The CI Pad will reboot during the process.
10. The process is completed, when you see normal CI Pad Homescreen.

For the case you actually did use “Erase all data (factory reset)” option in the system settings (Reset options), you need to finalize the configuration as explained in this video. After you complete the configuration you also need to go through the re-installation through the Carpe Manager as explained above or bunch of things will not be working.

Hotfix for CI Pad v4 and v4b. Global fix will be implemented on Android 11 update

Applicable to Kurviger version 3.0. and up:

https://play.google.com/store/apps/details?id=com.kurviger.app

Video tutorial here: https://youtu.be/c73uvPCgXCY

Before you begin:

1. Make sure battery is charged to at least 50%, but we recommend connecting to USB wall charger to make sure you don’t run out of power in the middle of the process;
2. A lot of data will be downloaded. It is recommended you connect to a fast WiFi before you begin. Do NOT change data connection during the process.
3. The whole process will take about 15 minutes.

Step by step:

1. Download this file in CI Pad storage (just open this page in the web browser on CI Pad and click on the link).
2. The process will be easier, when you change your Home screen launcher from DMD to Lawnchair (it is pre-installed on CI Pad). Go to System settings, search for „home“, click on “Home app”, it takes to do default apps selection. Click on “Home app” again – change to Lawnchair. Through the same process you can change the home screen launcher back to DMD when you are done.
3. Open Magisk. If you do not see Magisk in the list of installed apps:
   1. Long-press on home screen (after you enabled Lawnchair as your home screen launcher)
   2. Select “Home settings”
   3. Scroll to “App drawer”
   4. First line is “Hidden apps” – click and unselect Magisk.
   5. Go back to Homescreen and find Magisk in the overview of installed apps (swipe up on Home screen) – click on it to open.
4. Navigate to the tab “Modules” (menu on the bottom on the right)
5. Select “Install from storage”, navigate to “Downloads” and select the zip file downloaded in step 1
6. Openwebview module will be installed and you will be prompted to select version of Webview you wish to install. Select Bromite (first default option – do not change it, just select it.
7. Download of the payload will begin. It is a massive file, so it will NOT be instant.
8. WARNING: you will not get download progress bar – just sit tight and let it do its magic. Depending on the quality of your data connection, it can take 15 minutes or more.
9. WARNING: do not use CI Pad until the installation is complete – leave the installation screen as it is and just don’t touch it until it finishes. If the screen goes black (screen saver in case you disabled “Screen always on” in the Manager), don’t worry about it. You can revive the screen like you normally would by short-pressing power button.
10. Once the download is done, you will get a prompt to reboot CI Pad – let it reboot.
11. Download new Kurviger app.
12. Enjoy😉

Controller support:

Make sure you use the latest Controller app version to be able to use our controllers with the new Kurviger app (Controller app v2.81 or newer).

For CI Pad users: you will need to update the Manager app first, before you will see this new Controller app update. Lowest possible Manager app version 5.2. If you do not see available update on the App Shelf in you current version of the Manager, check-back again later.

For Play Store version of the Controller app: if you do not see new version available for update at the time of publishing this guide (June 6, 2023), check again next day – it takes some time for an update to be published on Play Store.

If you see this prompt in the Carpe Manager app, it means your ROM is outdated and needs to be re-flashed. Unfortunately this cannot be done remotely and you will need to send it to us.

Because you must have had this issue for at least a year, we strongly recommend to wait until we have the release version of Android 11 update ready so that we can flash the new operating system. That should happen in summer 2023.

1. The basic rule is not to do anything with / to the CI Pad you wouldn’t do with your smart phone (except for putting CI Pad on your bike:-D). Although it is a rugged device, if you put it through enough abuse, it could eventually fail. After all, it is not carved out of solid block of steel – it is an electronic device.
2. Do NOT keep CI Pad connected to a power source without the power source being connected to its own power supply. There is something called reverse current – if you keep CI Pad connected to a power source that is not powered, it will slowly drain CI Pad battery.
   That applies to any power source, not just our power source for motorcycles – the same will happen if you keep the CI Pad connected to your USB wall charger, but unplug the charger from the wall socket.
   Or if you forget the CI Pad connected to your laptop and the laptop shuts down – the laptop starts draining power from the CI Pad and in this specific case the damage to CI Pad battery can actually happen very quickly. Even during one night with CI Pad fully charged.
   If you keep CI Pad being drained like that long enough, the CI Pad battery will get completely depleted and you will not be able to charge it again.
3. Do not use USB quick chargers. There is a risk you will burn the fuse on the USB port. If that happens, you will loose all USB functionality (no charging and no data through USB port). If your CI Pad is charging on the bike but not through USB, it is most likely caused by the burned fuse.
4. Do not keep CI Pad exposed to sun when your bike is not moving. When you park your bike for lunch or something, either take CI Pad with you or cover it e.g. with your gloves. When there is no airflow to cool CI Pad down, the sun can heat the CI Pad enough to destroy the battery or damage the electronics. Also, long term exposure to sun will shorten the LCD life and might lead to LCD bleaching (loosing colors or getting an unwanted tint).
5. Do not keep CI Pad exposed to sub-zero temperatures especially with depleted battery – your battery might fail. If you put CI Pad on your bike and connect it to charging, sub-zero temperatures while riding don’t matter, because things get warmed up especially by the LCD and charging – please see User manual for details and limitation.

There are two completely different apps – DMD2 and DMD2 beta (if you are wondering why two separate apps are called almost the same, please know that we wonder the same. You need to ask Thork/DMD why).

DMD2 (non-beta) is one of apps preinstalled on CI Pad v4 and v4b. It is not owned by Carpe Iter and Carpe Iter has no control over that app. It is pre-installed on CI Pad Android 9 ROM and it will stay there until the operating system update to Android 11 (ETA August 2023). If you will opt for the update, you will loose DMD2. Even if you will decide to stay on Android 9 just to keep DMD2, please note that DMD2 will never be replaced by DMD2 beta (or whatever it will be called after the beta phase is over), unless you additionally install it manually (Thork/DMD licensing conditions will apply for manual installation).

Because DMD2 beta is an app different from DMD2, the DMD2 pre-installed on CI Pad will not be updated to “beta” (or whatever the app will be called after full roll-out (when the “beta” phase is over).

Also, it appears Thork/DMD guys decided to block our new Terrain Command III and BMW Control on DMD2 and possibly also on DMD2 beta. The communication protocols for Terrain Command III and BMW Control are identical to those on Terrain Command II and Adventure Control. Thork/DMD designed those communication protocols, yet the new controller generations appear not to work with DMD2 (both non-beta and beta). Because all our controllers use exactly the same communication protocols for DMD2 /DMD2 beta and some of them work, while others do not, that should be a clear indication to you that the limitations and restrictions do not come from our side.

As much as we’d love to make everything work also on DMD2/DMD2 beta, we cannot make that happen. DMD2/DMD2 beta are the only apps that actively block controllers and since we have no control over DMD2/DMD2 beta, it is only Thork/DMD team that can help you (if they decide to do so, which so far seems they are not planning to do).

There is a distinct difference between battery level indicator glitch and a charging issue.

How to tell the difference?

Go to the Power&Charge tab in the Carpe Manager app and compare reported voltage to the “Corrected” value. Fully depleted battery that would in theory show 0% will be 3,4V. Fully charged battery that would in theory show 100% would be at 4.2V (give or take).

So if you for instance see 4.0V, but the Corrected is telling you 30%, the indicator is wrong.

The “Corrected” value is our own non-stock battery level indicator. It has auto-calibrating feature and the calibration routine might start at 100% regardless the actual battery level. Just give it a few minutes to its magic – it will for sure settle to the correct value after a short while.

If you charged your CI Pad while it was off, our battery level indicator will also be wrong, because the last known battery level changed since the last time CI Pad was turned on. In that case our battery level indicator might start calibrating lower than what corresponds to the real value and slowly (within a few minutes) make it up to the real value.

How can you tell that the indicator is calibrating? When you see battery level at 100% and going down rapidly, that’s that – it is just calibrating. And similarly, when you see the battery level low and going up rapidly, that’s also that 😀

To sum up, if the CI Pad is connected to a power source and voltage is going up, there is no charging issue regardless what the battery level indicator is saying and there is no need to file a support ticket.

If you excluded hardware issues (search FAQs for “charging”) and battery level indicator issues (search FAQs for “battery level”) and your CI Pad battery level still goes below 50% regularly, there might be a software glitch in the charging service.

Here is a video guide, how to fix it.

Alternatively, just turn off AI Charge on the Power&Charge tab in the Carpe Manager app and restart CI Pad. After connecting it to a power source and disconnecting it again, the charging will go back to stock settings and there will no longer be any cycles and advanced battery management. It will simply just charge when connected to power and discharge when not. The batteries on CI Pads rarely ever fail, so letting it charge to 100% is a good trade-off for not having sleepless nights about charging algorithms;-).

And what is more important – in a few weeks there will be Android 11 update that will change everything about charging anyway, so in the meantime just stop worrying about charging and ride;-).

How to tell if the charging issues are software or hardware:

1. Connect CI Pad to a power source (USB wall charger or powered Lightweight holder or M8 charging cable with your bike started)
2. go to Power&Charge tab in the Carpe Manager app;
3. is connection to power source indicated without interruptions? It is for sure not hardware related issue.
4. does the battery stay above 50% (CI Pad does not discharge completely while riding)? It is most likely intended behavior – our algorithms cycle between charging and discharging to ensure longer battery life and to prevent overheating. You will rarely see 100% battery level, while the AI charging algorithms are enabled on the Power&Charge tab in the Carpe Manager app.

Charging algorithms explained:

1. you can tell which cycle is currently enabled on the Power&Charge tab in the Carpe Manager app. There are the following possible states:
   A. Charging unconditioned
   B. Discharging unconditioned
   C. Charging cycle up
   D. Discharging Cycle Up (yes, it does also charge now and then even when the cycle is “discharging”)
   E. Discharging Cycle Down
   F. Charging Cycle down (yes, it does also discharge how and then even when the cycle is “charging”)
2. The various charging cycles mean that even though the cycle might be “charging”, you can see the Current Now drop to negatives. That is perfectly fine and it is intended behavior.

To sum it up, if your battery does not drop below 50% while being connected to a power source, stop worrying about it – everything is fine;-).

Before you start hunting down ghosts, it is important to identify if the problem generally falls within software or hardware side of things.

How to tell the difference? Connect CI Pad to a power source (USB wall charger or Carpe Lightweight holder with your bike started) and check the Power&Charge tab in the Carpe Manager app. If it indicates that CI pad is connected to a power source, the problem is most like just software.

Please check individual FAQs for debugging hardware and software charging issues (search FAQs for “charging”).

You may have noticed that sometimes the battery level starts at 100% and then goes down rapidly.

That means the indicator is just calibrating. Simply give it a few minutes and it will settle down.

Why we did that? Stock Android indicator is designed for other use scenario. When you look at how you use your smartphone, it is in typical situations quite different from how you use CI Pad. You charge your smartphone over night and run it on battery the rest of the time. This is for what the stock Android battery indicator is built for.

With CI Pad, however, you keep it powered most of the time you use it and that’s when the stock Android battery level indicator sometimes gets confused. Which is why we made our own indicator, but for it to work properly, it needs to calibrate somehow.

Either way, all this is going to be redesigned on Android 11 for v4 and v4b units. Until then, please just stop worrying about indicators and just keep riding;-)

If your CI Pad is not charging EVER from any of the ports (USB, pogo pin, M8 cable), the charging circuitry is burnt and there is nothing to be done about it remotely. Please file support ticket and indicate that you were invited to do so in our FAQs.

There are two typical causes for burnt charging circuitry: 

1. you cut and spliced cables and/or connectors between the CI Pad and Carpe Iter Power source and while doing that, you reversed polarity. Damage can happen instantly, so even though you may have corrected the polarity later, the damage was already done. 
2. you bypassed the Carpe Iter Power source for CI Pad completely and connected CI Pad directly to 12V on your motorcycle (motorcycle battery or auxiliary power outlet on your bike). 

Please note that doing either of the two things above voided your warranty. 

For other charging issues, please check other FAQs, which are covering other scenarios (no charging through pogo pins, no charging through USB, no charging through M8 cable, charging vs battery level indicator)

We are talking here about NO charging – if your CI Pad does not drop below 50% of battery, don’t worry about it and just keep riding.

In case CI Pad is charging through USB, but it is charging neither through the pogo pins nor M8 connector, the problem is between our power source and your bike.

Yes, problems on the bike side are much, much more frequent than our power source failure. There was one single case of power source failure among thousands (which we anyway think was somehow caused by the user :-D).

Things to know/check:

1. When our power source is powered, it shows green LED
2. BLACK power source switches on and shows green LED after you start your engine – it starts when the voltage goes above 13,5V.
3. RED power source is always on and should not be affected by the drop of voltage on your bike.
4. Some bikes are not able to keep voltage above 13,5V especially at idle – if the green LED does not show on BLACK power source, check what voltage your bike is outputting. If your bike can exceed 13,5V when you rev-up, don’t worry about it. Unless you spend most of your riding at idle speed (very unlikely :-D), you don’t need to charge CI Pad 100% of the time (when the revs drop to idle).
5. You need to check the voltage on your bike while the CI Pad is connected to the power source. Your bike might be providing enough voltage when there is no strain, but once our BLACK power source starts drawing power to feed the CI Pad it might drop and cause the BLACK power source to switch off
6. our RED power source needs at least 10V, which should not really happen on any 12V motorcycle (that would indicate serious electrical issues on your bike, so if you see 10V when your bike is at idle and CI Pad is charging, run to your mechanic;-).
7. There could be some other issue with your DC rectifier or alternator (yes, that actually does / did happen to more than handful of our users). If the power seems alright – gives you green LED, but you are still having issues with CI Pad not charging on your bike, have your bike checked for electrical issues in a repair shop (they will most like need an oscillator to reveal issues such as excessive ripple voltage and such like).

If none of the above solved your problem, please file support ticket and indicate that you were invited to do so in our FAQs.

If the CI Pad is charging through the USB and pogo pins and not through M8 connector that can only be caused by broken internal wiring in CI Pad. All cases we saw so far were cause by the user twisting the M8 cable around (that’s why you get the M8 cable brackets for the holder to prevent that;-)).

This cannot be resolved remotely. Please file support ticket and indicate that you were invited to do so in our FAQs.

If you cannot check charging through pogo pins (you do not have them), please check that there is no issue with power supply on your motorcycle side (please check “No charging on motorcycle” FAQ before filing a support ticket).

If your CI Pad charges through USB and M8 connector, but not through pogo pins, the problems most likely come from one of the following areas:

1. Pogo pins are worn out: the pogo pins require maintenance – cleaning and greasing. They are moving parts and work pretty much like a piston in an engine. We all know what happens, when you run your engine without oil…
   We will post a more detailed guide soon. In the meantime read our User manual😉
   The only fix is to replace the pogo pins – they are available as spare spare part on our eshop. But you can of course just go with M8 connector and forget the pogo pins.
   
2. Wire is is broken or connector undone – check all wires and connectors. Consider applying grease for contacts on the connectors before you mate them again. If you do not have anything better, quality white lithium grease will also work.
   
3. Holder is bent and the pogo pins are not properly mating with CI Pad: To check, look from the side of the holder – there is a small gap which should let you see if the pins are mated or not. If everything is right, you don’t see any pogo pins;-). If the holder is bent, try to straighten it or get a new one.
   
4. If you do not have M8 connector to check, if the problem comes from pogo pins only or is generally related to charging, check search FAQs for “No charging on motorcycle”.

If your CI Pad can charge through pogo pins or M8 connector, but not through USB port, the fuse was burned on the USB port. In that case it connection to a PC through the USB port will not work either (please test before submitting a support ticket).

This cannot be resolved remotely. Please file support ticket and indicate that you were invited to do so in our FAQs.

It depends what you mean by that.

There are 2 distinctly different types of questions we regularly receive:

1. the indicator changes value for a split second: our battery level indicator is overwriting the stock Android indictor, which sometimes manifests as “glitch” in the indicated value. Don’t worry about that – it is normal. And also it will be done in a completely different way after Android 11 update.
2. the indicated battery level goes rapidly down, while the voltage indicated on the Power&Charge tab in the Carpe Manager app stays practically the same: that is the battery level calibration procedure, which is explained in this post.

If you erased all data (AKA Factory Reset) of CI Pad v3, you will need to manually re-certify with Google. Please follow the manual and you can also watch video on our YouTube channel.

There are two completely different apps – DMD2 and DMD2 beta (if you are wondering why two separate apps are called almost the same, please know that we wonder the same. You need to ask Thork/DMD why).

DMD2 (non-beta) is one of apps preinstalled on CI Pad v4 and v4b. It is not owned by Carpe Iter and Carpe Iter has no control over that app. It is pre-installed on CI Pad Android 9 ROM and it will stay there until the operating system update to Android 11 (ETA August 2023). If you will opt for the update, you will loose DMD2. Even if you will decide to stay on Android 9 just to keep DMD2, please note that DMD2 will never be replaced by DMD2 beta (or whatever it will be called after the beta phase is over), unless you additionally install it manually (Thork/DMD licensing conditions will apply for manual installation).

Because DMD2 beta is an app different from DMD2, the DMD2 pre-installed on CI Pad will not be updated to “beta” (or whatever the app will be called after full roll-out (when the “beta” phase is over).

Also, it appears Thork/DMD guys decided to block our new Terrain Command III and BMW Control on DMD2 and possibly also on DMD2 beta. The communication protocols for Terrain Command III and BMW Control are identical to those on Terrain Command II and Adventure Control. Thork/DMD designed those communication protocols, yet the new controller generations appear not to work with DMD2 (both non-beta and beta). Because all our controllers use exactly the same communication protocols for DMD2 /DMD2 beta and some of them work, while others do not, that should be a clear indication to you that the limitations and restrictions do not come from our side.

As much as we’d love to make everything work also on DMD2/DMD2 beta, we cannot make that happen. DMD2/DMD2 beta are the only apps that actively block controllers and since we have no control over DMD2/DMD2 beta, it is only Thork/DMD team that can help you (if they decide to do so, which so far seems they are not planning to do).