Currently, MTK devices still allow mirroring of F2F with it's native Cast app.
Motorola Moto M (android 7.0, MediaTek Helio P15, 4-32GB ROW version) works like a champ, but overheats and drains dead fast whenever casting F2F to Chromecast/Android Smart TVs*.
Slightly cumbersome, though.
This cheap accessory has more or less eliminated the "suicide dash" and SPs going off.
Position the suction cup higher up with space left over for your LEFT thumb to activate specials.
*Technically just a phone holder, the "joystick" is a suction cup with a knob, and the right side is untouched, per the picture.
Effective phone size: 5.2-6.3"
@BlackRazak I'm getting a new phone , OnePlus 5T. Just wanted to know if this game will run smoothly on it , thanks
Yes.
The 1+ 5t is great for F2F.
But overheating during AM is a slight issue, especially if left between nodes.
Also, background processes plus f2f memory leak don't play nice, so a sporadic reboot is great.
Good choice, but have you considered a pocophone, or helio P60 device?
@BlackRazak I'm getting a new phone , OnePlus 5T. Just wanted to know if this game will run smoothly on it , thanks
Yes.
The 1+ 5t is great for F2F.
But overheating during AM is a slight issue, especially if left between nodes.
Also, background processes plus f2f memory leak don't play nice, so a sporadic reboot is great.
Good choice, but have you considered a pocophone, or helio P60 device?
What about them? I mean poco and p60 .. how are they better in all .. specs.. you know @BlackRazak
@BlackRazak I'm getting a new phone , OnePlus 5T. Just wanted to know if this game will run smoothly on it , thanks
Yes.
The 1+ 5t is great for F2F.
But overheating during AM is a slight issue, especially if left between nodes.
Also, background processes plus f2f memory leak don't play nice, so a sporadic reboot is great.
Good choice, but have you considered a pocophone, or helio P60 device?
What about them? I mean poco and p60 .. how are they better in all .. specs.. you know @BlackRazak
Read the thread.
It's not about specs, but BALANCE.
SD8xx series run well AT 1ST, but are struggling after a couple of years.
Thing is, most flagship users rarely change their phones often.
SD6xx is even worse, with errors creeping up within 1yr of release for F2F.
In my tests, MediaTek mid-range devices (and even entry level) handle F2F REALLY WELL.
Can't explain why, but optimization on both game and hardware ends are in sync.
Even 2016 spec MediaTek.
This cheap accessory has more or less eliminated the "suicide dash" and SPs going off.
Position the suction cup higher up with space left over for your LEFT thumb to activate specials.
*Technically just a phone holder, the "joystick" is a suction cup with a knob, and the right side is untouched, per the picture.
Effective phone size: 5.2-6.3"
This cheap accessory has more or less eliminated the "suicide dash" and SPs going off.
Position the suction cup higher up with space left over for your LEFT thumb to activate specials.
*Technically just a phone holder, the "joystick" is a suction cup with a knob, and the right side is untouched, per the picture.
Effective phone size: 5.2-6.3"
@lightningbaron sorry buddy, those iPega style BT pads no longer work, especially after kabam removed bluestacks/emulator support.
The pad i posted (JL01) is just a physical holder, making play more comfortable.
No buttons whatsoever.
Even the Dpad just floats above the screen, and is actually physically touching your device.
Previously, you'd get an Android TV Box/Console or even a JXD/GPD type tablet, ones with mapping and BT pad compatibility, to work with F2F.
Configured correctly, i managed to get a Snakebyte Vyper (Android 4.4.2, RK3188 1.6GHz quad, 1.5GB RAM, 8GB, BT 4.0) and it's WONDERFUL Bluetooth Gamepad
to run F2F PERFECTLY, that is Pre-6.0 update.
With MAPPED controls replicating ALL moves replicated by the HARDWARE BUTTONS of said gamepad.
Which is how i conquered Kaon.
(Plus lots and lots of Energon, my best bots at the time were below 2500Pi: 4* G1 Megatron, Galvatron, Rhinox, Barricade and Grimlock)
Imagine my horror when 6.0.1 update happened and the following devices WOULDN'T WORK:
- Nexus 6
- Moto Z Play
- Moto G3 Turbo
- Snakebyte Vyper
- Moto G5 Plus
- Nubia Z11
- Droid Turbo 2
- Droid Maxx 2
Really hoping your CRASH/FC was a one off, @lightningbaron !
SD425/430/450 has had a decent record handling F2F; unlike the 625, 626 and 660.
Especially with your vanilla 8.0 and 4GB RAM config!
NO LONGER WORK WITH F2F.
Even with the mapping features of some devices (including purpose-built gaming tablets like the JXD S192 or GPD XD), F2F WON'T accept hardware controls or changes to it's touch input code.
STRICTLY TOUCHSCREEN.
Best bet to prevent fatigue, phone overheating and user-error are variants of:
The fan-based models especially helpful for users experiencing battery drain and FC due to overheating.
Really hoping your CRASH/FC was a one off, @lightningbaron !
SD425/430/450 has had a decent record handling F2F; unlike the 625, 626 and 660.
Especially with your vanilla 8.0 and 4GB RAM config!
DOES KABAM HAVE SHARES IN MEDIATEK OR WHAT
Apologies for any confusion, the device that crashed was my tablet, not the Moto G6 with SD450; to the end, the SD450 has a decent record.
Moto G6 (4GB RAM, SD450), received November security update this morning. Played the game, when I lost network connection in spotlight mission, it crashed and I got the health penalty.
Sadly this was on first time launching TFTF after rebooting post installation of update.
At the airport lounge, i saw a guy playing MCOC on a Chuwi/Teclast WINDOWS tablet.
It looked like a Surface but it was some China tab.
The guy barely spoke English, so there.
Would it also handle F2F?
I might get one online! @Kabam Rimehaven please explain.
BlueStacks still working, albeit with limited functionality.
Thanks, @lightningbaron for your functional setup!
(Thinkpad Yoga S1, Intel Core i5 4th Gen 4200U (1.60 GHz) 8 GB Memory 128 GB SSD, 12.5" 1080p)
So TOUCHSCREEN functionality is a must as BT or USB joypads (or any mapping of touchscreen input) is now dead, at least since 7.0.
October 2018 security update has no effect on following devices:
Moto M (7.0, Helio P15)
Moto C Plus (7.0, MT6737M)
Moto E5 Plus (8.0, SD425)
But
These devices exhibiting FREEZING:
Moto E⁴ Plus (7.1.2, MT6737M)
Moto X4 (9.0, SD630)
Comments
Sadly, "no longer compatible with your device" now pops up after the 7.1.2 Update.
Anyone have a functioning NVidia SHIELD?
Does it run?
Motorola Moto M (android 7.0, MediaTek Helio P15, 4-32GB ROW version) works like a champ, but overheats and drains dead fast whenever casting F2F to Chromecast/Android Smart TVs*.
Slightly cumbersome, though.
*Model tested: Toshiba 40L5650 paired with Moto M
- moto c plus $89 ✔️
- moto e4 plus (MT6737 version) $100 ✔️
- moto m (Helio P15 version) $123 ✔️✔️
- Oppo A3 (Helio P60 version) $150 ✔️✔️
* TESTED 11.27.2018
✔️ Fully Functional
✔️✔️ Exceptional
Very playable; too early to say if it will crash.
Still feel more comfortable playing on an 8" tablet running MediaTek processor; just need to be more patient and deal with crashes.
For 7.2.0, SD425 and 450 devices are running a-ok, especially with 4gb RAM and vanilla Android 8.0.
Caution:
DO NOT UPDATE TO 9.0 PIE JUST YET.
1. Lag
2. Freeze
3. Terrible battery optimization
Android 7.1.2
Moto e⁴ Plus, 3-32GB
1. Oppo A3- Helio P60, 4-64GB, Android 8.0
2. Moto M- Helio P15, 4-32GB, Android 7.0
3. Moto Z2F- SD835, 6-64GB, 8.0
4. Moto X4- SD630, 6-64GB, 8.0
5. Moto E5 Plus- SD425, 3-32GB, 8.0
More pronounced LAG, OVERHEATING and FREEZES:
1. Moto e⁴ Plus- MT6737, 3-32GB, 7.1.2
2. moto c plus- MT6737, 2-16GB, 7.0
3. moto Z2P- SD626, 4-64GB, 8.0
SD835, >4GB RAM
SD845, >4GB RAM (except 9.0 devices)
iOS A11, A12 series phones (just casual overheating)
JL-01 Gamepad add-on
(iOS/Android compatible)*
$2-10
This cheap accessory has more or less eliminated the "suicide dash" and SPs going off.
Position the suction cup higher up with space left over for your LEFT thumb to activate specials.
*Technically just a phone holder, the "joystick" is a suction cup with a knob, and the right side is untouched, per the picture.
Effective phone size: 5.2-6.3"
Yes.
The 1+ 5t is great for F2F.
But overheating during AM is a slight issue, especially if left between nodes.
Also, background processes plus f2f memory leak don't play nice, so a sporadic reboot is great.
Good choice, but have you considered a pocophone, or helio P60 device?
What about them? I mean poco and p60 .. how are they better in all .. specs.. you know @BlackRazak
Read the thread.
It's not about specs, but BALANCE.
SD8xx series run well AT 1ST, but are struggling after a couple of years.
Thing is, most flagship users rarely change their phones often.
SD6xx is even worse, with errors creeping up within 1yr of release for F2F.
In my tests, MediaTek mid-range devices (and even entry level) handle F2F REALLY WELL.
Can't explain why, but optimization on both game and hardware ends are in sync.
Even 2016 spec MediaTek.
You have me thinking and wondering if this would work?
https://flash.newegg.com/Product/9SIA0U088S4751?icid=WP_0_12032018
@lightningbaron sorry buddy, those iPega style BT pads no longer work, especially after kabam removed bluestacks/emulator support.
The pad i posted (JL01) is just a physical holder, making play more comfortable.
No buttons whatsoever.
Even the Dpad just floats above the screen, and is actually physically touching your device.
Previously, you'd get an Android TV Box/Console or even a JXD/GPD type tablet, ones with mapping and BT pad compatibility, to work with F2F.
Configured correctly, i managed to get a Snakebyte Vyper (Android 4.4.2, RK3188 1.6GHz quad, 1.5GB RAM, 8GB, BT 4.0) and it's WONDERFUL Bluetooth Gamepad
to run F2F PERFECTLY, that is Pre-6.0 update.
With MAPPED controls replicating ALL moves replicated by the HARDWARE BUTTONS of said gamepad.
Which is how i conquered Kaon.
(Plus lots and lots of Energon, my best bots at the time were below 2500Pi: 4* G1 Megatron, Galvatron, Rhinox, Barricade and Grimlock)
Imagine my horror when 6.0.1 update happened and the following devices WOULDN'T WORK:
- Nexus 6
- Moto Z Play
- Moto G3 Turbo
- Snakebyte Vyper
- Moto G5 Plus
- Nubia Z11
- Droid Turbo 2
- Droid Maxx 2
I see OEMs have been playing F2F.
Here are some gamepad holders with
BUILT-IN FANS. $8-15.
SD425/430/450 has had a decent record handling F2F; unlike the 625, 626 and 660.
Especially with your vanilla 8.0 and 4GB RAM config!
DOES KABAM HAVE SHARES IN MEDIATEK OR WHAT
BLUETOOTH Gamepads, like these:
NO LONGER WORK WITH F2F.
Even with the mapping features of some devices (including purpose-built gaming tablets like the JXD S192 or GPD XD), F2F WON'T accept hardware controls or changes to it's touch input code.
STRICTLY TOUCHSCREEN.
Best bet to prevent fatigue, phone overheating and user-error are variants of:
The fan-based models especially helpful for users experiencing battery drain and FC due to overheating.
Apologies for any confusion, the device that crashed was my tablet, not the Moto G6 with SD450; to the end, the SD450 has a decent record.
iPhone 8 issues as reported by @iuJacob
- Input Latency
- Command Misfires
By other users
- Overheating
- Force Closes
- Graphical Glitches
- Lag/Freeze
iPhone XR seems to be the least problematic with v7 2.0 of F2F.
1792x828, 120Hz LCD exhibits no ghosting.
2932mAh battery gives 9% per 1 hr of F2F.
A12 SoC runs fine, with not much overheating thanks to low res LCD and 3GB RAM.
Pixelation, graphical glitches non-existant at time of writing (12.14.2018)
Sadly this was on first time launching TFTF after rebooting post installation of update.
It looked like a Surface but it was some China tab.
The guy barely spoke English, so there.
Would it also handle F2F?
I might get one online!
@Kabam Rimehaven please explain.
Thanks, @lightningbaron for your functional setup!
(Thinkpad Yoga S1, Intel Core i5 4th Gen 4200U (1.60 GHz) 8 GB Memory 128 GB SSD, 12.5" 1080p)
So TOUCHSCREEN functionality is a must as BT or USB joypads (or any mapping of touchscreen input) is now dead, at least since 7.0.
Replication CONFIRMED:
Xiaomi Mi 6
Samsung Galaxy Note 8
Fix:
Closing of background processes, soft reboot OR RAM optimization
(Memory leak likely cause)
MediaTek:
MT6737M
MT6750
P15
P23
P30
P60
P90
Qualcomm:
SD425
SD430
SD450
SD630
SD845
IOS:
A11X
A12
No issues with that device beforehand.
Crashes and slight lag plus longer loading times.
List of CERTIFIED Processors for F2F:
MediaTek
- MT6737M*
- P10
- P15
- P23
- P25
- P60
- P70
- P90
UniSOC
- SC9832E*
- SC9863
Qualcomm
- SD425*
- SD630
- SD835
- SD845
Rockchip
- RK3288*
- RK3399*
Apple
- A11X
- A12
* Minimal configuration 2GB RAM, Android 6.0-8.0
If and when I find out the cause of crash, I may let Kabam know. For now I blame Google.
If anyone is wondering, hoping the logs will tell me.
October 2018 security update has no effect on following devices:
Moto M (7.0, Helio P15)
Moto C Plus (7.0, MT6737M)
Moto E5 Plus (8.0, SD425)
But
These devices exhibiting FREEZING:
Moto E⁴ Plus (7.1.2, MT6737M)
Moto X4 (9.0, SD630)
@lightningbaron