Android/iPhone farms Myth or True

NomixGuy

NomixGuy

Regular Member
Jr. VIP
Joined
Nov 20, 2025
Messages
232
Reaction score
101
Few things that I want to clarify about Android/iPhone farms. Tell me if every thing is a myth or true. Only guys with experience, please (I can speculate myself).

1. Android has lower trust score compared to iPhones
2. When using iPhones, screen streaming can provoke account ban
3. When using iPhones, Assistive Touch can provoke account ban
4. On iPhones nobody uses re-signed apps anymore, containerisation is way better
 
Advertise on BHW
In general, iOS devices tend to hold stronger trust and last longer under heavy activity compared to most Android setups. That difference is why many farms prefer running key accounts on iPhones.
 
Android usually gets a bit lower trust since it’s easier to mess with, but stuff like screen streaming or Assistive Touch on iPhone don’t really cause bans on their own. Re-signed apps are kinda old now, most ppl just use container setups coz they work way cleaner.
 
1. Android isn’t lower trust by default only suspicious Android patterns get flagged.
2. iPhone screen streaming is fine unless it looks like remote control.
3. Assistive Touch is safe unless used in bot-like patterns.
4. Re-signed apps are outdated; containerization is now pre
ferred.
 
Honestly, a lot of things people say about phone farms get exaggerated some are true in certain setups, some are just myths. From what I’ve seen, trust score depends more on behavior and network quality than the device itself and most bans come from patterns, not small things like assistive touch or streaming.
 
If you cant pass Play Integrity API checks on android you'll have problems.
 
Based on what actually works in practice: Android does have lower trust scores on most platforms because it's easier to root and modify, plus iOS users generally have higher spending patterns that platforms prefer. Screen streaming absolutely can trigger bans because it creates detectable network patterns and often introduces input lag that looks robotic.

AssistiveTouch is risky because it generates different touch event signatures than natural finger presses, and platforms are getting better at detecting these artificial input methods. The containerisation vs re-signed apps thing is true - modern iOS farms use container solutions to avoid the certificate management nightmare and detection risks that come with modified IPAs.
 
If you reverse engineer some of the anti-fraud tools, you'll see that they definitely capture data on whether or not you're using screen streaming for iPhone. To my knowledge, it's not a strong signal right now, but as with all ML-based fraud signals once there's a critical mass of people using screen streaming for iPhone doing suspicious stuff, it may turn into a stronger fraud signal and all that data that was previously collected will be used.

@NomixGuy, does you Nomix clicker hardware bypass screen streaming in some way or does it use screen streaming?
 
analyst33 said:
If you reverse engineer some of the anti-fraud tools, you'll see that they definitely capture data on whether or not you're using screen streaming for iPhone. To my knowledge, it's not a strong signal right now, but as with all ML-based fraud signals once there's a critical mass of people using screen streaming for iPhone doing suspicious stuff, it may turn into a stronger fraud signal and all that data that was previously collected will be used.

@NomixGuy, does you Nomix clicker hardware bypass screen streaming in some way or does it use screen streaming?
Click to expand...
Yes it uses iOS app for screen streaming and clicker device to emulate screen touches.
 
Compared to iPhones, Android typically has lower baseline trust, although behavior patterns matter more than the device.
When used naturally, screen streaming and Assistive Touch are generally safe; containerization is now favored and re-signed apps are out of date.
 
I agree to @Cloud Agency ,Most of these aren’t hard rules but risk factors where android vs iphone trust is more about setup quality, IPs and behavior than the device itself and things like screen streaming or assistive touch usually only become a problem if your usage pattern looks unnatural or automated.
 
android vs iphone trust is cope. signal stack wins.
streaming bans come from sloppy tools, not iOS itself.
assistive touch is noise. automation rhythm is signal.
resigned apps burned. containers scale cleaner and last longer.
 
Android/iPhone farms are real, but they’re a short-term manipulation trick that usually gets detected and burned by platforms sooner or later.
 
The "Assistive Touch" ban isn't a myth, but it's misunderstood. It’s not the feature itself, it’s the precision. Most automation tools use fixed XY coordinates. Real human touch has a "radius" and varying pressure levels. If you're emulating touches via Assistive Touch or a USB clicker, you need to implement Bezier curves for swipes and a random pixel offset for taps.

For keyboards : apps can use https://developer.apple.com/documentation/gamecontroller/gckeyboard to guess if you're using one or not. Having reverse-engineered multiple social networks apps on Android, I can definitely confirm that it's nearly always send in the same payload as other bot-detection flags (such as user being in debug mode, sensor data...) . However, I'm guessing this is not "that" bad of a flag, as lot of professionnals (i.e people that have to type a lot on phone, or edit gdocs/excel in a nomad way) have their bluetooth keyboard plugged.
 
karlheinrichr said:
The "Assistive Touch" ban isn't a myth, but it's misunderstood. It’s not the feature itself, it’s the precision. Most automation tools use fixed XY coordinates. Real human touch has a "radius" and varying pressure levels. If you're emulating touches via Assistive Touch or a USB clicker, you need to implement Bezier curves for swipes and a random pixel offset for taps.

For keyboards : apps can use GCKeyboard to guess if you're using one or not. Having reverse-engineered multiple social networks apps on Android, I can definitely confirm that it's nearly always send in the same payload as other bot-detection flags (such as user being in debug mode, sensor data...) . However, I'm guessing this is not "that" bad of a flag, as lot of professionnals (i.e people that have to type a lot on phone, or edit gdocs/excel in a nomad way) have their bluetooth keyboard plugged.
Click to expand...
That’s very insightful, thanks. Regarding human-like touch curves, do you think pre-recorded real finger swipes can do the same thing? E.g. via clicker API
 
NomixGuy said:
That’s very insightful, thanks. Regarding human-like touch curves, do you think pre-recorded real finger swipes can do the same thing? E.g. via clicker API
Click to expand...
Honestly, no idea. I would (and that's a big "would") say that it's undetectable for now since you're the first (or at least one of the first, never heard of anyone doing it) to implement it and the server-side automation detection is not ready for it. Again, I'm totally in the guess here, no way to know aside from running large-scale testing.

Other problem you'll run into (since I'm guessing you're going through a HID emulating a mouse to implement it) is that on iPhone <= X, you can't use absolute mouse coordinates (and god knows how hard it is to program relative mouse HID scripting on retina), and that's precisely the last generation where you can jailbreak easily and scale account creation/warmup for multiple accounts on one phone with crane. So get ready for headaches if you're going for implementing pre-recorded swipes with relative mouse.
 
NomixGuy said:
Few things that I want to clarify about Android/iPhone farms. Tell me if every thing is a myth or true. Only guys with experience, please (I can speculate myself).

1. Android has lower trust score compared to iPhones
2. When using iPhones, screen streaming can provoke account ban
3. When using iPhones, Assistive Touch can provoke account ban
4. On iPhones nobody uses re-signed apps anymore, containerisation is way better
Click to expand...
A lot of what gets said about phone farms is half myth, half outdated info.


  1. Android vs iPhone trust score, It’s not really about the OS anymore. It’s more about device integrity signals, app behavior, IP quality, and usage patterns. A clean Android can outperform a messy iPhone setup.
  2. Screen streaming causing bans, Not directly. It’s usually the automation behavior or abnormal interaction patterns that trigger flags, not the streaming itself.
  3. Assistive Touch bans, Very unlikely by itself. Platforms care about unnatural behavior, not accessibility features.
  4. Re-signed apps vs containerization, Most serious setups moved away from sloppy re-signing because integrity checks improved. Stability and consistency matter more than the method itself.

In 2026, behavior + network quality > device brand. The more your setup looks like a real, stable user, the safer it tends to be.
 
karlheinrichr said:
Honestly, no idea. I would (and that's a big "would") say that it's undetectable for now since you're the first (or at least one of the first, never heard of anyone doing it) to implement it and the server-side automation detection is not ready for it. Again, I'm totally in the guess here, no way to know aside from running large-scale testing.

Other problem you'll run into (since I'm guessing you're going through a HID emulating a mouse to implement it) is that on iPhone <= X, you can't use absolute mouse coordinates (and god knows how hard it is to program relative mouse HID scripting on retina), and that's precisely the last generation where you can jailbreak easily and scale account creation/warmup for multiple accounts on one phone with crane. So get ready for headaches if you're going for implementing pre-recorded swipes with relative mouse.
Click to expand...
You're right and it's a pleasure to see someone tech-savvy. Yes indeed absolute mouse doesn't work on iPhone X and below. So for old iPhones there's "legacy mode" in nomix. It's keyboard-based, like arrows to move pointer and tab to click, also hotkeys for swipes. It's even kinda faster than normal mouse control.
 
Last edited:
TechSavvyTess said:
A lot of what gets said about phone farms is half myth, half outdated info.


  1. Android vs iPhone trust score, It’s not really about the OS anymore. It’s more about device integrity signals, app behavior, IP quality, and usage patterns. A clean Android can outperform a messy iPhone setup.
  2. Screen streaming causing bans, Not directly. It’s usually the automation behavior or abnormal interaction patterns that trigger flags, not the streaming itself.
  3. Assistive Touch bans, Very unlikely by itself. Platforms care about unnatural behavior, not accessibility features.
  4. Re-signed apps vs containerization, Most serious setups moved away from sloppy re-signing because integrity checks improved. Stability and consistency matter more than the method itself.

In 2026, behavior + network quality > device brand. The more your setup looks like a real, stable user, the safer it tends to be.
Click to expand...
You confirm my own feeling about this... About re-signing – what is it then? Just one app per phone? Or containerization?
 
Advertise on BHW
You must log in or register to reply here.
Sign up now!

Main Menu

Home Main Forum List Black Hat SEO White Hat SEO BHW Newbie Guide Blogging Black Hat Tools Social Media Downloads

Marketplace

Account Selling Content / Copywriting EBooks / Methods Hosting Misc Proxies For Sale SEO - Link building SEO - Packages Social Media Social Media - Panels Web Design More

Making Money

Affiliate Programs Hire a Freelancer IM Journeys Making Money Pay Per Click Site Flipping Want to Buy

BlackHat World

Dispute Resolution Forum Suggestions & Feedback Introductions Lounge
Back
Top