(or maybe be able to use recovery zip that requires effort after every reboot)
Though they might still have an edge on toasters.
If you can think about how deep into technicalities the most average person you know gets, then you can also understand that ~half of everyone is even less technical than that.
There's nothing wrong with this. That's just the way that it is. (We can accept this or be frustrated. Acceptance is more useful.)
As a workaround, I find that searching by part number provides a good filter.
Maybe I want a very particular Moto G Power to use for whatever. I don't search for any permutation of "Motorola G Power" at all, because that description doesn't help me.
Instead, I just find the part number (maybe something like "XT2041-7") and search for that instead.
This excludes a lot of listings straight away, and that's fine: I don't want to stumble through listings from people who don't know what they have. I only want to buy what I want to buy, and what I want is an XT2041-7.
Just thermal paste to the battery hah
In order to prevent issues this time around I've preemptively removed the back of the phone, and the camera modules so I can have a nice flat phone. Then I bought a heatsink nearly the same size as the phone itself. I've got thermal pads on the SoC which sits lower than the battery and the heatsink itself had thermal adhesive on it pre-applied which is sticking to the battery/phone frame holding it to the phone. No more phone overheating worries and if the battery goes pillowy it should just pop the heatsink up instead of warping the whole phone.
I've always wanted to get into wardriving but I've never had an opportunity.
is this something you have to do for work or is there a network of wardrivers out there?
I live in NYC so it'd probably be closer to warwalking, but still could be fun.
There has definitely been a community of folks doing it even longer. See the Wigle[1] website for more, including leaderboards and stats. Some people use the data for various reasons, I do it to help track law enforcement via bluetooth & wifi mac addresses.
Warwalking is also a thing! (or riding for bikes) You can often get much better results when walking because you have a longer time to catch all the access points.
You don't really need to modify your phone either, my dedicated phone lives on the dash of my van when I'm using it so the extra cooling helps. But if you don't want to warm up your phone or drain the battery by disabling Wifi scan throttling there are also dedicated devices people are building just for war driving using esp32, etc.
Generally, as long as you keep the phone plugged in, the battery should be safe virtually indefinitely - the battery management on board will keep it in a state where its a constant charge which means the chemistry will be stable.
Would you say this is a chemistry/QA problem? Have there been advances in battery / controller technology that achieves the above?
(My current machine is a Thinkpad P52 if it matters, but I also use older Macbooks and newer Thinkpads and older Dell machines this way, although they're plugged in less often these days.)
2. Open up the laptop and check if battery is swollen. After about 10 years, it's also a good idea to replace the CMOS battery before leaking.
3. Without opening, sometimes keys/trackpads don't work anymore as expected. This might be due to swollen battery packs (we had several Dells where this happened).
I think if you're considering re-harvesting old devices to use for hosting and get far enough down your list to get to phones then you've likely got enough constant maintenance costs in overseeing things that the additional worry of fire risk just isn't worth it.
Batteries, however, are absolute hellfire when they go wrong (because of chemistry - not just the temperature).
What is your source on this?
I've replaced the battery in always-plugged-in iPhone 3 times over 10 years because it was expanding into a spicy pillow.
I too want a way to run phones directly off of USB power, without a battery present.
Never again. I was genuinely shocked the thing turned on once I closed it up. It's one thing to have a conceptual understanding of how tiny the components inside a phone are. It's another thing to actually be trying to seat a plug into a socket with tweezers and just have no idea how you're supposed to tell if it's fully inserted or not.
Could have been worse -- the sentence could have ended right there...
(This is for a removable battery, but should be close for built-in ones too, I suppose)
[1] https://www.youtube.com/watch?v=7f8SliNGeDM&pp=ygUYZ3JlYXRzY...
Simple root, with a custom degoogled rom, and termux is all you need.
You don't need root if you webserver is listening on a port over 1024.
Termux plus some webserver like nginx is all you need.
Now to make it reboot resistant is another story.
The battery will swell and explode if you run 24x7 on a phone.
That's the big hurdle though - mainstream kernel support.
For most devices, even if they can be rooted and jailbroken, you're stuck with the kernel they come with. Doesn't have a new feature you need? A horrible security flaw in the network stack? You're out of luck. Most "repurpose your old phone" approaches have this problem. You can make it a server but you wouldn't want to expose it to the public Internet.
I think it's basically for the same reason as why they dropped 32-bit x86 support about 8 years ago. Not enough users. (That resulted in the unofficial Arch Linux 32 to maintain support.)
Once that’s done, then the ports can be submitted.
Look at the maintainers and contributors on the unofficial arm port. Orce this RFC gets accepted, the arm port can propose and figure out how to merge things together.
I write this from arch on arm (orange pi) thingy, btw
But yes, this is definitely an issue. I've been playing with a 2013-era Samsung device that came with a 3.0 kernel. It can run pmos with said kernel but there are multiple root LPE vulns. I've been looking into getting it to run a mainline kernel just for fun, but it's not going to be easy.
$ grep -rhoE 'Samsung Galaxy[^"]+' ./arch/arm*/boot/dts/ | sort -uThis blog is now hosted on a GPS/LTE modem (2021) - https://news.ycombinator.com/item?id=46049981
But I suspect it's just the "always on" nature and the battery. The usage pattern is just entirely different than having a phone in your pocket and using when you need it.
You're welcome to try though, maybe phones got more reliable.
Any ideas what I can do with it to give it some purpose?
It sounds like Qualcomm has to do everything from scratch on their hidden Linux software for every new chip.
Right now you have to find a skopeo binary for your arch, but that's WIP.
Exposing a port isn't exactly a safe thing to do nowadays, and I'd be wary of the security posture of an "old phone". Proceed with caution.
Assuming you are using an old phone with termux to serve de webpage. What could be an attack vector?
The phone will be running Android 7.1
agentifysh•2mo ago
ive been looking to build and serve my own servers and i have been considering to use old android phones to outright racks but the part I am still struggling to figure out is how to serve it publicly without ISP catching on as they require business plans for that and its not cheap
1bpp•2mo ago
agentifysh•2mo ago
srean•2mo ago
From your comments it is clear that they don't. Super infuriating. Why should they care what I do with ingress and outgress that I paid for, as long as I am not hurting them.
Nextgrid•2mo ago
ISPs who enforce data caps already priced it in and technically have an incentive for you to exceed your cap as fast as possible so you pay to increase said cap (they can however still slow down your traffic as they wish, to ensure sufficient capacity for everyone).
ISPs who don't enforce a cap actually still internally enforce a reasonable cap of several terabytes at their discretion. And of course, they can and will use traffic shaping to ensure the integrity of their network so your usage doesn't affect others. If you exceed that soft cap consistently several months in a row they may get in touch, but other than that you're fine.
TLDR: host your server and enjoy. When you get to the scale of the next YouTube, then you have to worry.
lelandbatey•2mo ago
Nextgrid•2mo ago
Otherwise, no worries.
Marsymars•2mo ago
rlupi•2mo ago
https://developers.cloudflare.com/cloudflare-one/networks/co...
Although, you may also go with a 5$ virtual host (e.g. Linode Nanode 1 GB) and wireguard to build your own tunnel (or just the 5$ virtual host to run your server)
agentifysh•2mo ago
eptcyka•2mo ago
flockonus•2mo ago
lelandbatey•2mo ago
As for the volume of traffic you're sending, you need to read the terms of your ISP contract, at least a little. Your ISP could have volume limits (e.g. only 5TB of traffic per month), and if you reach those limits, they could temporarily suspend service. But if they can't see what you're doing, and you're within the technical and contractual limits of your service agreement, and you're not causing problems for them, then an ISP is not going to care what you do.
Gabrys1•2mo ago
shevy-java•2mo ago
Not sure what changed, but things got more complex - and more expensive, too.
teo_zero•2mo ago
IP4 address exhaustion.
Nextgrid•2mo ago
No. No ISP who desperately tries to grow marketshare at all costs and lock their customers into a year-long contract will intentionally ban users. I'm not even sure where this misconception comes from, it's not like ISPs led a massive PR campaign warning people of the dangers of running a server.
The only way you will get banned is if you cause disproportionate strain on their network, which means you'd need to exceed the usage of the typical gamer (downloading games worth hundreds of gigs regularly), streamer (streaming 4k video for hours at a time), cloud backup customer (uploading gigabytes regularly), Windows user (in its default configuration Windows can use P2P to share updates), torrenter (sustained full-duplex bandwidth usage), and unlucky idiot with a compromised device spewing DoS traffic at line-rate.
Saturate the pipe consistently for several days by hosting video? Yeah sure you could get a warning and eventually disconnected, assuming they don't already have traffic shaping solutions in place to just silently throttle you to an acceptable level and leave it up to you to move your homebrew YouTube clone elsewhere when you realize it's too slow.
Hosting a website which will have a few mbps worth of traffic with the occasional spike? That's a rounding error compared to your normal legitimate usage, so totally fine.
The reason most consumer ISPs have a clause against running servers (not even defining what counts as a server) is to preempt a potential business starting a data center off a collection of consumer connections and then bitching about it or demanding compensation when it goes down or they get cut off. Nobody cares about a technical user playing around and hosting a blog at home.
lelandbatey•2mo ago
ISPs will have rules (maximum data volume per month) and restrictions (ISP equipment auto-drops all sending/receiving packets on port 25, 80, 443, or 456), but within those limits the ISPs do not care as long as you cause no problems for them.
Also, one of the easiest ways to expose e.g. port 80 of your in-house server is to just have your local server do an SSH port-forward to a remote server like a cheap VPS. Note that by default it'll bind to a localhost port on the remote, so on the remote you'd need to have an HTTP server reverse proxying to the remote localhost:8080, or you need to enable `GatewayPorts: yes` in sshd on the remote. Assuming you turn on GatewayPorts on remote.example.com, here's how you could expose port 80 of localhost:
You can make the above connection permanent by setting up `autossh` on in-your-house-computer.euroderf•2mo ago
lelandbatey•2mo ago
hn_acc1•2mo ago
lelandbatey•2mo ago
edbaskerville•2mo ago
(I'm lucky to have Sonic, in the SF Bay Area. A local ISP that actively campaigned for net neutrality and has 1Gps symmetric as the standard basic fiber plan. Pretty sure they're not shutting down anybody's servers.)
prmoustache•2mo ago
whynotmaybe•2mo ago
Some may block port 80 and 443 "For Security", but you can sometimes contact the support and they'll open it, even if you're not a business.
I have a webserver running at home and use the free dynamic dns from noip.com.
jeroenhd•2mo ago
No? I mean, I'm sure there are ISPs out there that do it, but that's a ridiculous thing to do.
louismerlin•2mo ago
Friends from other countries, India for example, have had different experiences though, where IPs were on a much more frequent rotation and required scripted solutions.