Love these suggestions! I'm using an old Motorola X Pure as one of my CCTV cameras via the excellent free IP Webcam app for a couple years now, but with a twist:
I've done this before with an old LG phone, and it seems that leaving the battery in the phone for camera purposes is a bad idea. It turns in to a spicy pillow within a year. I believe it's the heat - from getting cooked in the sun through the window, from the CPU working hard to encode MJPEG stream, and from the wireless radio constantly transmitting that stream, all while being held near maximum SOC..
So what I did this time around was remove the battery completely! I found an old 5V USB phone charger, say 1000mA output, and used a diode to drop the voltage to ~4.2V or so. Nothing out of the usual for a phone to see soldered on it's battery terminals.
Now this worked, but I found that certain high-load situations would cause the phone to power off. Solution was to add say 5000uF of electrolytic capacitors to the output of my new power supply.
With that added, setting Android to sync automatically via my NTP server with a command through the ADB shell, setting it to always connect to my IoT VLAN WiFi, and setting IP Webcam to start after boot, this solution has been working perfectly for quite some time!
It was a fun project too, and I got to reuse an old phone, and old charger I never would have used again, and some random capacitors that have been rolling around in a parts box for years. :)
Bonus: I control the camera's "night vision" mode via Home Assistant automations (turn on/off around sunset/rise) through the JSON API the app provides. This also provides some sensors like temperature, etc. The video stream is fed to ZoneMinder, which HA streams from. Motion detection in ZM triggers object detection via HA, and I get reliable notifications while I'm away!
This is great. I've always wanted to do something similar for my phones' battery compartments, but don't have the tools or knowledge.
I'm curious, is it possible to create fake 'batteries' for devices that pass the current directly from the charger into the device? I'm imagining something that looks like a battery, but doesn't hold any charge so people can use their old phones exactly as you do and never have to worry about it pillowing.
I can see a market for something like that, albeit a very small one since it would be device specific. I'd buy one if it existed.
I would definitely be in the marker for such a fake battery as well, though I suspect the fact that modern phones don't have normal battery connectors (and instead rely on glue and ribbon cables to connect power) will make a standardized product quite difficult.
Still, though, a correctly set voltage regulator with a normal USB plug and a few easy solder joints to attach the device's battery connectors to would already make the process quite a lot easier.
For some products, such things are already available.
For example, want to mains-power your Panasonic digital camera? [1] provides mains power in a battery form-factor. Just what you need for long term time-lapse photography.
The first model I designed and 3D printed was a dummy battery pack for an Android PDA. (We use cheap ones at work and the stock batteries puffed up after a year.) The idea should scale down to a phone with a removable pack, but may not be useful on devices with soldered batteries.
That's exactly right - or at least it's my theory which has so far worked just fine. Seems that without the extra capacitance on the output of my power supply, the voltage can droop just enough to cause a reset in the CPU or somewhere in the phone's hardware during high-draw moments. The extra capacitance helps lessen the droop enough to keep things humming along. :)
I forgot to mention this, but the phone has also been loaded with LineageOS to get rid of a lot of the default crap that was on there. It boots way faster and IP Webcam seems to run more reliably this way!
Glad to see Unified Remote mentioned! I created it 12 years ago, back in 2010 when Android and smartphones were basically brand new. I still maintain it, although less frequent feature updates these days.
Shameless plug here:
I made an open source coding framework / prototyping tool that works very well we old Android devices.
I've used it for a lot of things. Made robots, radios, home controllers, cameras, etc out of old androids :)
1) I did post it sometime ago but did not get too much traction :)
2) I never heard of bun.sh, I'll have a look!
3) I did not notice about the Discord link. Probably it has been like that for ages :/
I will replace it in the site. Meanwhile here you have a new up-to-date one
https://discord.gg/Rt2mkWp
This is great! Would love to join the discord. A couple things that I'm curious about: can you make a script/app start by default, can you use a node library (murmur specifically), can you interface with peripherals (led and knobs). I'd like to turn my old androids into screen-less walkie talkies, and phonk feels like I might be able to avoid android studio, which would be a relief.
1) Yes, you can make a script that starts on device boot.
2) Sadly you cannot use node libs. The JS engine I use is pretty dated (Mozilla Rhino) and I dont have time these days to do big changes.
3) Yes, you can interface with Arduino compatible hardware via USB serial or Bluetooth / Bluetooth LE.
4) If you want to do something screen less, you can run a script as a service (background). A bunch of years ago, when the ESP modules were not common I used an Android device as a network interface for my Arduino :)
If the old Android device doesn't get security updates, then it isn't safe to keep it connected to the Internet. Someone can hack into it and turn on the mic and camera. Or use it for mining cryptocurrencies.
That only works for the userland, mitigating security issues by replacing the main stock OS with Lineage.
Aren't most LOS roms based on ancient kernels (albeit mostly patched-up with security updates), that use ancient modules, with opaque BLOBS/Firmwares, that only sometimes get updated, if ever?
You could run "HighSecurityOS WhatEv" on your phone, as long as e.g. the Wireless-Interface runs something entirely independent of you with DMA rights, and probably faulty firmware, can you really trust your device? Or have I missed recent advancements in this problem space?
PostMarketOS aims to mainline more devices/phones, so maybe, even if your final OS of choice is Lineage (or derivative), I would check their HWCDB before checking, if Lineage works on a phone.
This is my concern. I use my old pixel (3a) as an always-on Syncthing node but worry about the security implications.
But I haven't been able to find good info on what exactly the implications are. If I'm not worried about targeted attacks, does a device that is just a passive node pose a significant risk?
In other words, how much do security updates address targeted attacks (not my threat model) vs widespread attacks of non-updated phones?
This varies case by case, and widespread attacks definitely happen.
Perhaps the most famous one on Android was the Stagefright attack, which could take over your phone by sending you a malicious MMS (which you didn't even have to open), or by getting the system media player to play a malicious MP3/MP4.
That was a while ago and I haven't kept current on similar attacks. Running an unpatched system is a gamble that nothing like that is still waiting to be discovered.
> Perhaps the most famous one on Android was the Stagefright attack, which could take over your phone by sending you a malicious MMS (which you didn't even have to open), or my getting the system media player to play a malicious MP3/MP4.
Which I would assume is not an issue if I'm using an old Android phone without a SIM card, so there's no way to receive any type of sms/mms message
The 3a will run Lineage, so you can get the latest OS updates. However, the vendor updates will not advance.
Lineage will try to scavenge firmware updates from other devices to upgrade what they can, but there might be problems with the wifi, bluetooth, or other firmware that can compromise the device.
This is less of a concern if your wifi connectivity is behind a NAT router, and Google is gone.
> This is my concern. I use my old pixel (3a) as an always-on Syncthing node but worry about the security implications.
Interesting, I've never thought of using an Android phone as a Syncthing node.
Is there a way for an Android phone to connect to Wifi, but not the internet?
I use Syncthing with local discovery only, which only needs the devices to be on the same Wifi network. Not having internet access and also not having a SIM card to get calls/sms/mms message should greatly reduce the risk of attack to the point where I wouldn't feel worried about it.
> Is there a way for an Android phone to connect to Wifi, but not the internet?
If you can manually set the IP address on it instead of letting the WiFi AP give it one, then you can just leave out the default gateway entry - The device will then have no idea how to route network data outside of your local LAN.
Alternatively, set up a different WiFi SSID that gives out IP addresses, but again without a default gateway address, and have your device(s) connect to that instead.
Or finally, if your router supports it, set a rule to block your device(s) (via it's MAC address) from accessing the internet.
> If the old Android device doesn't get security updates, then it isn't safe to keep it connected to the Internet.
That can be mitigated somewhat by it being a local-only device with firewalls between it and the wider Internet (so it can call out as needed but nothing out can call in). There is still a risk of another device on your WAN, temporarily or otherwise being infected and passing on the problem - you could have an extra AP and keep such devices on their own leg of the network to reduce that risk. You'd still be prone to something that can attack an old unpatched device just by being in range of it, of course, so perhaps use some sort of exfiltration monitoring at your network edge (or the edge of that walled-off WAN) to hopefully detect an infection trying to propagate from the device.
It seems like every Android device that I've had becomes ridiculously slow after a few years. Not even a factory reset helps. I'd be happy turning a few tablets into one of these ideas or even nothing more than glorified terminals if there were actually ROMs available for them. Lighter weight software that could give them new life like I've done for so many old PCs with a Linux distro.
I never had problems with devices becoming slow where a factory reset does not help, this sounds odd since a factory reset clears all configuration data. I tend to install some AOSP-derived distribution on devices which are supported (or which I port it to myself), for those for which I can not find a working distribution I pare down the factory distribution as much as I can by removing bloat and replacing obnoxious apps with functional ones from F-Droid. This makes it possible to use e.g. a Samsung Galaxy SIII from 2014 with Android 11 as a daily device for 'dangerous' work.
Never had problems with those either, who made those Android devices with such short-lived eMMC chips? I'm using a number of old Android devices from both well-known manufacturers like Motorola, Samsung and Sony as well as lesser-known ones like Ainol, none of these suffer from memory-induced slowdowns. In my experience it is the battery and the touch screen which are most likely to give out first. The battery can be replaced, sometimes the touch screen can as well but I tend to just use those devices for purposes where I don't need a screen (which I often actually just disconnect to save power) such as MPD-based media players, a trailer camera and IP cameras.
I gave my Galaxy Nexus to my dad, so it saw longer use than usual. After five years it was virtually unusable. It was already slow when I stopped using it.
My Nexus 5, which is sitting in a drawer nowadays, also becomes ever slower. Even my HP Veer, keeping the Nexus 5 company, isn’t getting any faster either—even though it never saw real use.
So yeah, basically all manufacturers “do it”. It’s not even about heavy use or anything.
A guess: You don't (re)write data on your phone storage much? This experience is common for my girlfriend who takes 50 GB of photos every few months, transfers them all to the PC and does it again, but uncommon for me who practically never uses the internal storage except for apps.
Not really, these devices all have seen intensive use and are still being used in that way. Some only have a tiny amount of flash on board (e.g. Motorola Defy only has 2GB, I have 5 of these running as media player, MPD player, trailer camera and IP cameras) yet they persevere. Some (e.g. Defy) even have been used with swap-to-eMMC for a while, I ended up disabling this because it is just too slow but it made it possible to run some apps which otherwise would not run on 512MB devices. In short, I have not had problems with flash wear - yet.
I have an S8 and although I am a Dev, I am really a Luddite on my phone. I have some random apps, a Google account and things like WhatsApp and Telegram but otherwise not really anything of note.
However, I find things like the share photo button sometimes taking 5 seconds for the list of who to share with to come up. How? Sometimes I click an app and it sits there for as much as 10 seconds before something comes up, tbf, that might be the app but I fail to see how compiled apps can become slower and slower over time by this much.
I suspect the enemy at the gate is tracking/metrics type apps that are sending a constant stream of drissle to the internet to try and get "actionable data" for their Lords and Masters but just make everything appear crap. I also loathe the need to fiddle all the time. Google Authenticator, absolutely fine until they decide that we need to press something to reveal the code, now it's 2 clicks instead of 1 50% reduction in productivity! I think they have reverted it but honestly, leave things alone!
a prominent example of this was the first google nexus 7 tablet, née Asus Memo Pad. Therein somehow the NAND flash became used up in some strange fashion making write speed unbearable. This also could not be fixed with a factory reset.
Old android phones make great dashcams. Most of them have automatic gps address lookup, g-sensor shock detection, far better cameras and more storage than most dedicated devices. There's several dashcam apps on the play store.
I have an original Samsung edge with a cracked screen. I keep it because it has an ANT+ radio on it that actually works, and still use it for updating and tuning my old Quarq power meter on my bicycle. It also works seamlessly with the ODB II Bluetooth scanner for working on my car. I migrated to apple and overall I'm much less annoyed than I was with android, but their support for non typical hardware devices still lacks. Somewhat intentionally, I might add. The iPhone should 100% be able to communicate for example with that bluetooth device but it refuses to pair with it because that protocol is locked down.
Ideally https://news.ycombinator.com/item?id=27885176 but when $$$ are involved nothing happens... (Thanks to all the product managers and the coding supporters in hn that cripple OS)
I have an original HTC One that would be absolutely excellent as an universal remote (because it actually has an IR blaster), yet HTC almost went out of their way to kneecap that in the last firmware update it got years back and no third-party IR apps seem to work with it.
I suspect it will end up as a 3D printer display, but the browser on it is hilariously slow by today’s standards, and pretty much every 3D printer front-end brings along enough JavaScript to choke it…
You can either change it (not always that hard even with minimal soldering skills, it’s actually harder to find a decent battery), or use it plugged in. My wife’s old Kindle Fire is my permanently plugged-in, wall-mounted kitchen recipe book.
Someone in a different post mentioned the risk of fire/battery bulging if you leave your device plugged in like that. Is that a legitimate risk? I assumed that (while not great for battery life) there's some circuitry that's making sure it's not charging a whole lot.
modern devices often keep the battery at 80% level if charged for a long time, for this reason. (they say "to extend battery life" in notifications, and that might also be a side effect, but AFAIK the primary reason is to reduce the probability of bulging.
But many/most of these older devices discuss, do not - and my personal anecdote is that of the tens of phones+laptops I have owned myself and managed for family through the years - there were 4 cases of bulging: 3 were constantly-charging devices (as in, 3-5 years with hardly any time not charging), and one that was dropped from height and bulged immediately.
Never heard or seen anything like that at all. The fact that you are not even given an option despite decades of "this really is one of the most important things to billions of devices" makes me a bit hesitant to believe it.
Maybe use a dummy battery? I use one for my 4g wifi modem. The battery got swollen so I replaced it with a dummy that connect directly to a USB charger.
Chargie [1] allows this for USB-A. It could be controlled via an Android app.
My problem with repurposing an old Android device is the security issues. Firmware doesn't get updated anymore. An alternative OS like LineageOS or PostmarketOS takes care of most of the software issues, but not the firmware itself.
Another issue is that the battery is going to be years old, and on 'recent old' Android devices its much more difficult to remove the battery.
If you go camping/offroading/overlanding one popular use case is getting an old Android w/GPS to use with Gaia GPS. You can use the Android Auto app but it's much less feature filled and you'll be using your phone to do a lot of things. Also AA on old/slower devices can be.. rough in my experience.
This is probably really niche for hn. Personally I use an ipad mini w/a Garmin GLONASS GPS receiver.
I discovered the other day that you can use your old android phone as a server for OctoPrint, a 3D printer controller that runs off a web interface. I am going to give this a try using my old OnePlus 3T.
i have tried to find old versions of apps but they almost always require andrdoid 5+ at least.
no, i have not rolled out own browser because i don't know how...
maybe there is a need to build or maintain apps for old devices using old sdks and tools?
I have searched for a way to use my Xiaomi Mi A1 phone. I want to use it as a personal cloud storage, but I haven't found out how to do it. Using it as a dedicated ebook reader maybe the best idea I can do with it.
It isn't that well supported in PostmarketOS (charging and OTG), but that sounds fairly fixable. Ideally you'd want both, then connect to a charger/ethernet combo.
You might be able to use the downstream kernel for that, or Termux on Android.
"Incredibly" valuable. Not anymore, they're common goods now. I bought a USB GPS module on Aliexpress the other day for a couple of USD. GSM modules also exist for USB. Virtually all of them run proprietary firmware. An old SoC is not very valuable, if you consider say Raspberry Pico and what you can do with such. The best thing to do with an old smartphone is IMO to recycle (= mostly downcycle) it. It still contains some valuable metals like cobalt and gold.
In the age post-bluepwn and broadpwn, I'd assume otherwise. Especially considering that most OEM images come with admob, which even has ultrasonic RCEs that can be delivered by your TV's or radio's audio signal.
Opsec kinda mandates to destroy all broadcom chips :D
So you also don't use a smartphone in general? Because otherwise having an extra device just for the alarm clock functionality, doesn't really stop the general spying on you... unless you are particularly worried about keeping your waking up times private.
One problem is power draw. I figured out I can use an old phone with a removable battery without the battery but I still need a battery to power it up. However,if I do certain things that I presume need a burst of energy (wrong term?) that is enough to power cycle the phone. At least that's my guess because flash doesn't work.
Also do not use an old phone with a battery with screen turned on, capturing photos on repeat. The battery WILL swell up. It may take a few months but it will happen. Don't risk it.
I simply have a laptop (65W) USB C connected to the phone. I wasn't able to turn it on a month or so ago but tried it again after your reply and yes it still works. I use open camera to take a picture every so often (30s is one option). The phone is old and has a cracked display but the back is user removable so it is really nice. I attach the USB C cable, connect the (now very swollen) battery in, power on the phone, and remove the battery once the phone boots. As long as I don't do anything insane like try to use the flash, it works.
I appreciate the laugh at
> I tried acetone, because I had a bottle next to the alcohol, which went well.
Haha
can you please expand on this part though?
> Unfortunately, the micro-USB connector charges the battery, it doesn't power the device. This can be fixed by connecting a random 5V power supply to the battery connector instead.
Do I need a soldering iron for this? Thanks in advance.
Edit: do you know how we could get open camera or any camera app on Android to take pictures with the screen turned off? It really doesn't need the screen on all the time.
My idea was to simply have the phone screen off, one always running app tapping into the RTSP stream on WiFi then offload it every few minutes. Could have a smart power supply hooked up to drain the battery to low digits every now & then. Smart batteries with programmable functions & voltages would have been a boon for so many legacy electronics
old, scratched phone "requiring repair" is something you can inconspicuously keep on your table, with recording app, if you want to learn what people discuss in your absence.
I've done this before with an old LG phone, and it seems that leaving the battery in the phone for camera purposes is a bad idea. It turns in to a spicy pillow within a year. I believe it's the heat - from getting cooked in the sun through the window, from the CPU working hard to encode MJPEG stream, and from the wireless radio constantly transmitting that stream, all while being held near maximum SOC..
So what I did this time around was remove the battery completely! I found an old 5V USB phone charger, say 1000mA output, and used a diode to drop the voltage to ~4.2V or so. Nothing out of the usual for a phone to see soldered on it's battery terminals.
Now this worked, but I found that certain high-load situations would cause the phone to power off. Solution was to add say 5000uF of electrolytic capacitors to the output of my new power supply.
With that added, setting Android to sync automatically via my NTP server with a command through the ADB shell, setting it to always connect to my IoT VLAN WiFi, and setting IP Webcam to start after boot, this solution has been working perfectly for quite some time!
It was a fun project too, and I got to reuse an old phone, and old charger I never would have used again, and some random capacitors that have been rolling around in a parts box for years. :)
Bonus: I control the camera's "night vision" mode via Home Assistant automations (turn on/off around sunset/rise) through the JSON API the app provides. This also provides some sensors like temperature, etc. The video stream is fed to ZoneMinder, which HA streams from. Motion detection in ZM triggers object detection via HA, and I get reliable notifications while I'm away!