# What if your Droidkeep phone is not responding?

> Droidkeep phone offline or frozen? Reconnect ADB, restart the app, then open a ticket. Lost days are credited if it is not fixed within 24 hours.

- URL: https://droidkeep.com/help/phone-not-responding/
- Last updated: 2026-11-16
- Publisher: Droidkeep (https://droidkeep.com)

**Quick answer — What if your Droidkeep phone is not responding?**

First check your side: run `adb disconnect host:port`, then `adb connect host:port`, and reload the browser screen. If the phone stays offline, reply in its Support ticket with the time (UTC) and what you see. If **Droidkeep** support cannot fix it within 24 hours, the lost days are credited back to your balance.

**In brief**

- **Check three things first**: your ADB link, the rental end date, and whether only one app is frozen.
- **No restart button** in the client area: phone-level problems go through a ticket.
- **Rule**: If Droidkeep cannot deliver a phone within 24 hours of the order, its full price goes back to your balance. If a phone stops working and support cannot fix it within 24 hours, the lost days are credited back to your balance. Top-ups are not paid back, except where the law requires it.
- **Support**: A person answers support emails within 12 hours, seven days a week, including help with SSH keys, reinstalls and firewall rules.

## What do the symptoms mean and what should you do?

**Most problems are on the connection or in one app, not in the phone.** Work down the table before opening a ticket.

*Common Droidkeep phone problems, their usual cause and the next step*

| What you see | Usual cause | What to do |
| --- | --- | --- |
| `adb devices` shows `offline` | The ADB link dropped | `adb disconnect host:port`, then `adb connect host:port` |
| `failed to connect` | Wrong host or port, or the rental ended | Copy both again from the ticket; check the end date |
| Still offline after `adb kill-server` | A problem on the phone side | Reply in the phone's ticket |
| Browser screen black or frozen | Stream lost, or phone stuck | Reload the tab; if it persists, reply in the ticket |
| One app frozen, the rest works | The app hung | `adb shell am force-stop PACKAGE`, then open it again |
| App closes by itself after hours | Android's background limits or low memory | See the background apps guide |
| Phone gone after the end date | The rental ended and was wiped | Order a new phone; data cannot be restored |

## How do you report a problem to support?

**Reply in the phone's delivery ticket, or open a new one: Support, New ticket, topic Technical help.** Write a Subject of at least 3 characters and a Message of at least 10, then click Send. The ticket shows the status “Waiting for us” until the team answers, then “Answered”.

A good report has:

- the order ID (ORD-…) of the phone,
- the time it stopped, in UTC,
- what you see: the ADB state, the error, or a description of the screen,
- what you already tried.

Never send your account number, password or two-factor codes; the form warns about it.

## What do you get if the phone stays down?

**The days it was down, back on your balance, if support cannot fix it within 24 hours.** The credit goes to the balance, not to your wallet, and pays a renewal or a new phone. Top-ups are not paid back, except where the law requires it.

According to Droidkeep's own price grid, one day of a 30-day Keep 4 rental is worth about $0.10; a 16 GB day, about $0.66. The full rules are in [refunds and credits](https://droidkeep.com/help/refunds-and-credits/ "What does Droidkeep refund or credit?").

## How do you avoid the common causes?

**Keep your ADB client current, renew early, and give heavy apps enough RAM.** Old ADB versions bundled with other tools fail to connect more often; use Platform-Tools from developer.android.com, as the [ADB guide](https://droidkeep.com/guides/how-to-connect-adb-to-a-cloud-phone/ "How do you connect ADB to a cloud phone?") explains.

Apps that close after hours are usually held back by Android itself. The [background apps guide](https://droidkeep.com/guides/how-to-keep-an-android-app-running-in-the-background/ "How do you keep an Android app running in the background?") shows the exemption and the `adb` checks. To find your access details again, see [connect to your phone](https://droidkeep.com/help/connect-to-your-phone/ "How do you connect to your Droidkeep phone?").

## Phone problem questions

### Can I reboot the phone myself?

There is no reboot button in the client area. Ask in the phone's ticket.

### Does my rental keep running while the phone is down?

Yes, but if support cannot fix it within 24 hours, the lost days are credited back to your balance.

### Will a fix erase my data?

Not on purpose, but Storage is inside the phone; Droidkeep keeps no backup of it. Copy anything important with `adb pull`.

### How fast does support answer?

A person answers support emails within 12 hours, seven days a week, including help with SSH keys, reinstalls and firewall rules. A badge next to Support shows a new reply.

### The phone works but is slow. Is that a fault?

It can be an app using all the RAM. Check with the browser screen or close apps; if it stays slow, open a ticket with the times.

**Verdict**

- **Reconnect, restart the app, then write**: most issues end at the first two steps.
- **If the phone stays down for more than 24 hours** after your report, Droidkeep credits the lost days to your balance.

## Sources

1. [Android Debug Bridge (adb)](https://developer.android.com/tools/adb) — Android Developers (read 2026-11-16)
2. [Droidkeep refund policy](https://droidkeep.com/refunds/) — Droidkeep (2026-11-16)

**Need another phone?** Keep 4 for 30 days: $2.97, delivered through a Support ticket. [Rent Keep 4 for 30 days](https://droidkeep.com/app/checkout/?plan=p4-30d&product=keep-4&from=help-phone-not-responding&lang=en) · [All help pages](https://droidkeep.com/help/ "Where is the Droidkeep help center?")

---

Droidkeep: Droidkeep rents Android phones in the cloud that stay on 24/7: apps, idle games and automation keep running when your own screen is off, with the screen in the browser and ADB over the network. 4, 8 or 16 GB of RAM, from 1 day to 365 days. Paid in crypto, no KYC.
