Welcome to the subreddit of the best wireless carrier in the industry! T-Mobile is the second largest wireless carrier in the U.S. offering affordable plans, the fastest network in America, no contract, and no overages. This is the place to discuss everything magenta!
Welcome to /Verizon! A community to discuss and ask questions about anything and everything Verizon, be it Wireless, FiOS, DSL, Landline, etc.
ROK Mobile 4G LTE is an MVNO running on the Verizon network, offering unlimited 256kbps data w/ 5GB @ 4G for $49.99 ($52.24) / month
I currently have Verizon, thinking of switching to t-mobile for $. I've never used them before- is coverage around here with Tmobile as good as it is for Verizon? Fwiw, I'm in the south side
Recently switched to Verizon almost 2 weeks ago from ATT. Have 6 lines on Unlimited+. I’m still familiarizing myself to the website/app. For the usage for each line it says that I’ve used the hotspot for the same amount of mobile data. So far I have used 22.41 GB of data and 22.41 of 4G hotspot data. Which I haven’t for the hotspot. Has this happened to anyone else? I’m not concerned about it, I just want to know if I need to address the issue with Verizon or if it’ll sort itself out.
Now, I’m not going to say that Mint Mobile doesn’t make the cut, because I’ve not tried them. I have seen network speed tests performed by reviewers and concluded with their results and my personal experience and understanding of what you pay for, that USM goes undefeated in the best bang for the buck.
I had an active line with them for around 2.5 years for my personal line. After porting a number I had with them to Visible, and having absolutely trash service (I was using Verizon’s network with USM), and being told by customer service through direct chat that “5Mbps download speed is our minimum acceptable speed, so there’s nothing more we can do to improve it for you”… I nearly had a brain aneurysm. You’re telling me that Verizon’s network is “good enough” in the fifth most populous city of the USA, where I got well over 25+Mbps down speeds on the SAME network with just a different front end/MVNO taking my money, and my home’s trashy DSL line getting 9Mbps down speed is BETTER than $35/month cell service?
I understand this was most likely a back end issue, and there’s more that could have been done to improve my experience if I tried hard enough, but the damage was done. I was being told a crappy speed was “sufficient” to put it lightly.
The phone line was being used by someone else in my household at this point, so I signed them up for their own account (with my details, as they wanted some privacy and aren’t very technical, and I handle all tech problems anyway), got them the 100 day trial activated, and service had been excellent. If I could speak for it holding up to my personal experience with the company, I would, but I can only go off of what the end user reports: zero complaints, zero issues, only some usage data bleed through from the original account that was used with the number (given it was all under the same name, all the same details, I can excuse the minor annoyance since there’s no real privacy breach or anything). The workaround for figuring out how much of the allotment of full speed data was done by taking the second billing cycle of the trial, deducting that total from the number provided by support chat, and making a note for how much to add to the running total for the second billing cycle (if there wasn’t the bleed through of usage data, which is a rare case anyway, it’d be easy enough to just go off the metric for that timeframe).
My “review” of sorts, with a TL;DR is as follows: if you want a quality service that goes above and beyond with customer relations, had solid connectivity where you already get quality service with the Verizon/T-Mobile network, and you don’t want to spend an arm and a leg, GET US MOBILE. They really do put the effort into helping their customers, new and old, and if my personal number wasn’t with another carrier because of a benefit that pays for the service, it’d be through US Mobile. The other user in my household that’s using it- flawless experience for the most part. Some minor hiccups and slow speeds at odd hours are to be expected with any network, and they are reportedly resolved on their own without a fuss.
I hope my experience gives a different perspective, and a slightly unique spin on how this company handles their customers and does business. Myself, I’ve had only data package billing cycles, and never had a problem with excessive data consumption or bad speeds. The other user, good enough speeds to be very happy and not once complained in the first few weeks of the free trial period. We both hope tunings continue to go this way for years to come, as I was a proud customer for around 2.5 years myself. I can say that since finding their service thanks to MVNO comparison sites and reviews, that there had never been a service this high quality for this price, nor that I bothered to test drive it myself (save my awful experience with Visible).
If you’re considering USM for a new line/port in, they’re FAST at getting you up and running (takes minutes at the most), and you’ll love the fact that the network experience truly is “premium” without making excuses. Just try them out, especially if you have an eSIM to spare in your phone, and see if they can save you money/offer a similar experience to what you get now. You’ll be pleasantly surprised, even if you don’t make the switch
So in about a month I’ll be traveling to the outback counties of Kentucky where T-Mobile coverage is almost non-existent even on postpaid.
My iPhone 13 Pro Max is unlocked and I’ve verified through my settings and T-Mobile.
I want an AT&T or MVNO that uses AT&T so I can stay connected as per FCC data, they cover the areas I’ll be traveling to the best. Verizon doesn’t seem to have a tower until a few towns over.
I only need coverage for about a week, is there any cheap option available? I don’t think there will be much Wi-Fi during my trip. I can do either eSIM or pSIM.
I played Diablo 2 when I was a kid, played Diablo 3 in middle school/early high school. Moved on to Path of Exile, briefly Lost Ark.
I now have a career, wife, a kid… I was so worried this game would let me down. $100 is a lot to ask, I actually had to work overtime to justify buying this game in our budget.
But damn, If I’m not having a good time. The skill tree doesn’t get enough attention. The open world gameplay is a grand slam. The massive map is amazing. The classes feel diverse, and subclasses (like… bone necro vs blood necro) feel totally unique.
I haven’t gotten to endgame yet, but this dad loves D4. Everyone knows Blizz can absolutely eat a bag of dicks. But it’s clear there is a lot of talent in the D4 team that just put a shit ton into this game.
It feels like this game was made for people like me, who miss the challenge but just don’t have the time to hardcore grind anymore.
Love it. That’s all.
So I moved across the country (and Canada) from Alaska to NC. I never imagined I'd find worse cell service, but the house in Durham is depraved with Verizon.
I have read other posts... Reset mobile, WiFi, bluetooth RCS on. RCS off. Reset APN. Force stop messages. Clear messages cache and data. Wifi calling on. Wifi calling off. Restart phone.
I feel like this should be simple... But it sure isn't!
Any help appreciated.
So I picked up a Z13 finally on a lucky restock but one performance question I haven’t seen answered yet is the performance on its own vs. a 3080 or a 6850 XG mobile gpu. Which would be best if I wasn’t able to snag a 4090 right away or is one necessary for gaming natively on the device? I usually only play Destiny 2 but don’t want massive frame drops during raids.
It boots, gets an IP but no data on the dashboard
I reset to factory, here is my log, if anyone can help it would be supremely appreciated:
--
On node 0 totalpages: 61440
free_area_init_node: node 0, pgdat c0b3c040, node_mem_map cde10000
Normal zone: 480 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 61440 pages, LIFO batch:15
percpu: Embedded 12 pages/cpu
u/cddf0000 s19916 r8192 d21044 u49152
pcpu-alloc: s19916 r8192 d21044 u49152 alloc=12*4096
pcpu-alloc: [0] 0 [0] 1
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 60960
Kernel command line: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 209340K/245760K available (6317K kernel code, 243K rwdata, 1932K rodata, 1024K init, 232K bss, 20036K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xcf800000 - 0xff800000 ( 768 MB)
lowmem : 0xc0000000 - 0xcf000000 ( 240 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.text : 0xc0008000 - 0xc090e410 (9242 kB)
.init : 0xc0a00000 - 0xc0b00000 (1024 kB)
.data : 0xc0b00000 - 0xc0b3cda0 ( 244 kB)
.bss : 0xc0b3cda0 - 0xc0b77024 ( 233 kB)
Preemptible hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 32. RCU restricting CPUs from NR\_CPUS=4 to nr\_cpu\_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <[
[email protected]](mailto:
[email protected])>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 6964K (cd42d000 - cdafa000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 159, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
cdns-i2c e0005000.ps7_i2c: 100 kHz mmio e0005000 irq 154
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: disable subpage write
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAEAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
nand: NAND_ECC_HW
nand: NAND_ECC_HW_SYNDROME
mtd->writesize = 2048
ecc->strength = 1
ecc->size = 2048
mtd->writesize = 2048
chip->ecc_strength_ds = 4
chip->ecc_step_ds = 512
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
nand_read_bbt: bad block at 0x000000140000
8 ofpart partitions found on MTD device pl35x-nand
Creating 8 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-dts-marker-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000005200000 : "sig"
0x000005200000-0x000006000000 : "reserve1"
0x000006000000-0x000007000000 : "upgrade-ramfs"
0x000007000000-0x00000a800000 : "upgrade-file"
0x00000a800000-0x000010000000 : "reserve2"
nf_conntrack version 0.5.0 (3635 buckets, 14540 max)
ip_tables: (C) 2000-2006 Netfilter Core Team
NET: Registered protocol family 10
ip6_tables: (C) 2000-2006 Netfilter Core Team
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs warning (device ram0): ext4_update_dynamic_rev:746: updating to rev 1 because of new feature flag, running e2fsck is recommended
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr,errors=remount-ro
devpts: called with bogus options
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 11/4, WL threshold: 4096, image sequence number: 262741923
ubi0: available PEBs: 36, total reserved PEBs: 28, PEBs reserved for bad PEB handling: 4
ubi0: background thread "ubi_bgt0d" started, PID 729
UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 733
UBIFS (ubi0:0): recovery needed
UBIFS (ubi0:0): recovery completed
UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "configs"
UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi0:0): FS size: 1396736 bytes (1 MiB, 11 LEBs), journal size 888833 bytes (0 MiB, 5 LEBs)
UBIFS (ubi0:0): reserved for root: 65970 bytes (64 KiB)
UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID A9E8BDA4-70DE-45D9-83BE-2DD9F129C0C6, small LPT model
ubi2: attaching mtd4
ubi2: scanning is finished
ubi2: empty MTD device detected
ubi2: attached mtd4 (name "reserve1", size 14 MiB)
ubi2: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi2: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi2: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi2: good PEBs: 112, bad PEBs: 0, corrupted PEBs: 0
ubi2: user volume: 0, internal volumes: 1, max. volumes count: 128
ubi2: max/mean erase counter: 0/0, WL threshold: 4096, image sequence number: 2067240595
ubi2: available PEBs: 104, total reserved PEBs: 8, PEBs reserved for bad PEB handling: 4
ubi2: background thread "ubi_bgt2d" started, PID 739
UBIFS (ubi2:0): default file-system created
UBIFS (ubi2:0): background thread "ubifs_bgt2_0" started, PID 745
UBIFS (ubi2:0): UBIFS: mounted UBI device 2, volume 0, name "misc"
UBIFS (ubi2:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi2:0): FS size: 11935744 bytes (11 MiB, 94 LEBs), journal size 1015809 bytes (0 MiB, 6 LEBs)
UBIFS (ubi2:0): reserved for root: 563754 bytes (550 KiB)
UBIFS (ubi2:0): media format: w4/r0 (latest is w4/r0), UUID EEB062CF-C448-4C2D-B662-A49819A4078C, small LPT model
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
random: id2mac urandom read with 1 bits of entropy available
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
In axi fpga driver!
request_mem_region OK!
AXI fpga dev virtual address is 0xcfbe4000
*base_vir_addr = 0xb051
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
===========================================Miner log===========================================
time="1970-01-01 00:00:10" level=error pid=886 msg="invalid URL -- ''"
time="1970-01-01 00:00:10" level=error pid=886 msg="invalid URL -- ''"
time="1970-01-01 00:00:10" level=error pid=886 msg="invalid URL -- ''"
time="1970-01-01 00:00:10" level=info pid=886 msg="release version"
time="1970-01-01 00:00:10" level=info pid=886 msg="asic mode"
time="1970-01-01 00:00:10" level=error pid=886 msg="No valid pools, please configure them first!"
time="1970-01-01 00:00:10" level=notice pid=886 msg="algo ltc fan_control_mode 2"
time="1970-01-01 00:00:10" level=notice pid=886 msg=platform_init
time="1970-01-01 00:00:10" level=info pid=886 msg="mmap fpga_mem_addr_hal = 0xb5cd9000
"
time="1970-01-01 00:00:10" level=info pid=886 msg="HARDWARE_VERSION = 0x2000b051
"
time="1970-01-01 00:00:10" level=notice pid=886 msg="chain_offset 0, chain 1"
time="1970-01-01 00:00:12" level=notice pid=886 msg="chain_offset 0, chain 1, pic firmware verion = 0x89"
time="1970-01-01 00:00:12" level=notice pid=886 msg="chain_offset 1, chain 2"
time="1970-01-01 00:00:15" level=notice pid=886 msg="chain_offset 1, chain 2, pic firmware verion = 0x89"
time="1970-01-01 00:00:15" level=notice pid=886 msg="chain_offset 2, chain 3"
time="1970-01-01 00:00:18" level=notice pid=886 msg="chain_offset 2, chain 3, pic firmware verion = 0x89"
time="1970-01-01 00:00:18" level=notice pid=886 msg="reset fpga"
time="1970-01-01 00:00:18" level=notice pid=886 msg="Begain check_fan_valiad"
time="2023-06-07 17:06:00" level=notice pid=886 msg="check_fan_valiad, check_fan_speed ok, fan_num = 4"
time="2023-06-07 17:06:00" level=notice pid=886 msg="Miner compile time: Mon Jan 24 16:01:20 CST 2022 type: Antminer L7"
time="2023-06-07 17:06:00" level=info pid=886 msg="godminer Version = 0xB051 1.0.0_release_dirty_master_4c4db04fc8fb8ce1a21da1db2301f261664943c2_Jan 24 2022 16:18:48"
time="2023-06-07 17:06:00" level=notice pid=886 msg="miner thread with 3 backend runtime created pid 886"
time="2023-06-07 17:06:00" level=notice pid=886 msg="opt_algo 6, ltc"
time="2023-06-07 17:06:02" level=error pid=886 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:06:02" level=error pid=886 msg="Data decode fail for chain 1.
"
time="2023-06-07 17:06:04" level=error pid=886 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:06:04" level=error pid=886 msg="Data decode fail for chain 1.
"
time="2023-06-07 17:06:07" level=error pid=886 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:06:07" level=error pid=886 msg="Data decode fail for chain 1.
"
time="2023-06-07 17:06:07" level=error pid=886 msg="Data load fail for chain 1.
"
time="2023-06-07 17:06:09" level=error pid=886 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:06:09" level=error pid=886 msg="Data decode fail for chain 2.
"
time="2023-06-07 17:06:11" level=error pid=886 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:06:11" level=error pid=886 msg="Data decode fail for chain 2.
"
time="2023-06-07 17:06:14" level=error pid=886 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:06:14" level=error pid=886 msg="Data decode fail for chain 2.
"
time="2023-06-07 17:06:14" level=error pid=886 msg="Data load fail for chain 2.
"
time="2023-06-07 17:06:16" level=error pid=886 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:06:16" level=error pid=886 msg="Data decode fail for chain 3.
"
time="2023-06-07 17:06:18" level=error pid=886 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:06:18" level=error pid=886 msg="Data decode fail for chain 3.
"
time="2023-06-07 17:06:21" level=error pid=886 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:06:21" level=error pid=886 msg="Data decode fail for chain 3.
"
time="2023-06-07 17:06:21" level=error pid=886 msg="Data load fail for chain 3.
"
time="2023-06-07 17:06:21" level=error pid=886 msg="Chain1 load EEPROM error."
time="2023-06-07 17:06:21" level=notice pid=886 msg="Error! Chain [1] EEPROM data corrupted"
time="2023-06-07 17:06:29" level=error pid=1167 msg="invalid URL -- ''"
time="2023-06-07 17:06:29" level=error pid=1167 msg="invalid URL -- ''"
time="2023-06-07 17:06:29" level=error pid=1167 msg="invalid URL -- ''"
time="2023-06-07 17:06:29" level=info pid=1167 msg="release version"
time="2023-06-07 17:06:29" level=info pid=1167 msg="asic mode"
time="2023-06-07 17:06:29" level=error pid=1167 msg="No valid pools, please configure them first!"
time="2023-06-07 17:06:29" level=notice pid=1167 msg="algo ltc fan_control_mode 2"
time="2023-06-07 17:06:29" level=notice pid=1167 msg=platform_init
time="2023-06-07 17:06:29" level=info pid=1167 msg="mmap fpga_mem_addr_hal = 0xb5cd6000
"
time="2023-06-07 17:06:29" level=info pid=1167 msg="HARDWARE_VERSION = 0x2000b051
"
time="2023-06-07 17:06:29" level=notice pid=1167 msg="chain_offset 0, chain 1"
time="2023-06-07 17:06:32" level=notice pid=1167 msg="chain_offset 0, chain 1, pic firmware verion = 0x89"
time="2023-06-07 17:06:32" level=notice pid=1167 msg="chain_offset 1, chain 2"
time="2023-06-07 17:06:35" level=notice pid=1167 msg="chain_offset 1, chain 2, pic firmware verion = 0x89"
time="2023-06-07 17:06:35" level=notice pid=1167 msg="chain_offset 2, chain 3"
time="2023-06-07 17:06:38" level=notice pid=1167 msg="chain_offset 2, chain 3, pic firmware verion = 0x89"
time="2023-06-07 17:06:38" level=notice pid=1167 msg="reset fpga"
time="2023-06-07 17:06:38" level=notice pid=1167 msg="Begain check_fan_valiad"
time="2023-06-07 17:06:38" level=notice pid=1167 msg="check_fan_valiad, check_fan_speed ok, fan_num = 4"
time="2023-06-07 17:06:38" level=notice pid=1167 msg="Miner compile time: Mon Jan 24 16:01:20 CST 2022 type: Antminer L7"
time="2023-06-07 17:06:38" level=info pid=1167 msg="godminer Version = 0xB051 1.0.0_release_dirty_master_4c4db04fc8fb8ce1a21da1db2301f261664943c2_Jan 24 2022 16:18:48"
time="2023-06-07 17:06:38" level=notice pid=1167 msg="miner thread with 3 backend runtime created pid 1167"
time="2023-06-07 17:06:38" level=notice pid=1167 msg="opt_algo 6, ltc"
time="2023-06-07 17:06:40" level=error pid=1167 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:06:40" level=error pid=1167 msg="Data decode fail for chain 1.
"
time="2023-06-07 17:06:42" level=error pid=1167 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:06:42" level=error pid=1167 msg="Data decode fail for chain 1.
"
time="2023-06-07 17:06:45" level=error pid=1167 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:06:45" level=error pid=1167 msg="Data decode fail for chain 1.
"
time="2023-06-07 17:06:45" level=error pid=1167 msg="Data load fail for chain 1.
"
time="2023-06-07 17:06:47" level=error pid=1167 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:06:47" level=error pid=1167 msg="Data decode fail for chain 2.
"
time="2023-06-07 17:06:49" level=error pid=1167 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:06:49" level=error pid=1167 msg="Data decode fail for chain 2.
"
time="2023-06-07 17:06:52" level=error pid=1167 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:06:52" level=error pid=1167 msg="Data decode fail for chain 2.
"
time="2023-06-07 17:06:52" level=error pid=1167 msg="Data load fail for chain 2.
"
time="2023-06-07 17:06:54" level=error pid=1167 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:06:54" level=error pid=1167 msg="Data decode fail for chain 3.
"
time="2023-06-07 17:06:56" level=error pid=1167 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:06:56" level=error pid=1167 msg="Data decode fail for chain 3.
"
time="2023-06-07 17:06:59" level=error pid=1167 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:06:59" level=error pid=1167 msg="Data decode fail for chain 3.
"
time="2023-06-07 17:06:59" level=error pid=1167 msg="Data load fail for chain 3.
"
time="2023-06-07 17:06:59" level=error pid=1167 msg="Chain1 load EEPROM error."
time="2023-06-07 17:06:59" level=notice pid=1167 msg="Error! Chain [1] EEPROM data corrupted"
time="2023-06-07 17:07:14" level=error pid=1485 msg="invalid URL -- ''"
time="2023-06-07 17:07:14" level=error pid=1485 msg="invalid URL -- ''"
time="2023-06-07 17:07:14" level=info pid=1485 msg="release version"
time="2023-06-07 17:07:14" level=info pid=1485 msg="asic mode"
time="2023-06-07 17:07:14" level=notice pid=1485 msg="algo ltc fan_control_mode 2"
time="2023-06-07 17:07:14" level=notice pid=1485 msg=platform_init
time="2023-06-07 17:07:14" level=info pid=1485 msg="mmap fpga_mem_addr_hal = 0xb5d0a000
"
time="2023-06-07 17:07:14" level=info pid=1485 msg="HARDWARE_VERSION = 0x2000b051
"
time="2023-06-07 17:07:14" level=notice pid=1485 msg="chain_offset 0, chain 1"
time="2023-06-07 17:07:17" level=notice pid=1485 msg="chain_offset 0, chain 1, pic firmware verion = 0x89"
time="2023-06-07 17:07:17" level=notice pid=1485 msg="chain_offset 1, chain 2"
time="2023-06-07 17:07:20" level=notice pid=1485 msg="chain_offset 1, chain 2, pic firmware verion = 0x89"
time="2023-06-07 17:07:20" level=notice pid=1485 msg="chain_offset 2, chain 3"
time="2023-06-07 17:07:23" level=notice pid=1485 msg="chain_offset 2, chain 3, pic firmware verion = 0x89"
time="2023-06-07 17:07:23" level=notice pid=1485 msg="reset fpga"
time="2023-06-07 17:07:23" level=notice pid=1485 msg="Begain check_fan_valiad"
time="2023-06-07 17:07:23" level=notice pid=1485 msg="check_fan_valiad, check_fan_speed ok, fan_num = 4"
time="2023-06-07 17:07:23" level=notice pid=1485 msg="Miner compile time: Mon Jan 24 16:01:20 CST 2022 type: Antminer L7"
time="2023-06-07 17:07:23" level=info pid=1485 msg="godminer Version = 0xB051 1.0.0_release_dirty_master_4c4db04fc8fb8ce1a21da1db2301f261664943c2_Jan 24 2022 16:18:48"
time="2023-06-07 17:07:23" level=notice pid=1485 msg="miner thread with 3 backend runtime created pid 1485"
time="2023-06-07 17:07:23" level=notice pid=1485 msg="opt_algo 6, ltc"
time="2023-06-07 17:07:25" level=error pid=1485 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:07:25" level=error pid=1485 msg="Data decode fail for chain 1.
"
time="2023-06-07 17:07:28" level=error pid=1485 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:07:28" level=error pid=1485 msg="Data decode fail for chain 1.
"
time="2023-06-07 17:07:30" level=error pid=1485 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:07:30" level=error pid=1485 msg="Data decode fail for chain 1.
"
time="2023-06-07 17:07:30" level=error pid=1485 msg="Data load fail for chain 1.
"
time="2023-06-07 17:07:32" level=error pid=1485 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:07:32" level=error pid=1485 msg="Data decode fail for chain 2.
"
time="2023-06-07 17:07:34" level=error pid=1485 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:07:34" level=error pid=1485 msg="Data decode fail for chain 2.
"
time="2023-06-07 17:07:37" level=error pid=1485 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:07:37" level=error pid=1485 msg="Data decode fail for chain 2.
"
time="2023-06-07 17:07:37" level=error pid=1485 msg="Data load fail for chain 2.
"
time="2023-06-07 17:07:39" level=error pid=1485 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:07:39" level=error pid=1485 msg="Data decode fail for chain 3.
"
time="2023-06-07 17:07:41" level=error pid=1485 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:07:41" level=error pid=1485 msg="Data decode fail for chain 3.
"
time="2023-06-07 17:07:44" level=error pid=1485 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:07:44" level=error pid=1485 msg="Data decode fail for chain 3.
"
time="2023-06-07 17:07:44" level=error pid=1485 msg="Data load fail for chain 3.
"
time="2023-06-07 17:07:44" level=error pid=1485 msg="Chain1 load EEPROM error."
time="2023-06-07 17:07:44" level=notice pid=1485 msg="Error! Chain [1] EEPROM data corrupted"
I have not seen many tech tree guides on the subreddit, so I decided to make one, starting with my favourite tech tree (and one that is very popular in general): the Grille 15. I'll skip the T6, because it should be a quick grind and that tank is kinda just food for KV-2s and Smashers...
The light German TD line is known for being squishy yet stealthy and having big and reliable guns that hit hard. This line is mostly about hanging back and supporting your team where it is most needed, because you lack armour and basic brawling ability. This does not mean you should sit in a bush until the heat death of the universe: big alpha guns give you a lot of power in the late game, where you can even start trading shots with other, even heavy tanks.
Sturer Emil: a weird one.
The St. Emil is an outlier in its own tech tree, boasting the best gun depression angles in the game, a huge punchy gun for its tier, a lack of prammo and somewhat HE-resistant armour. In my opinion, the Steyr WT would have fit this line perfectly, but I won't complain that we got such a special tank for free :D
Pros: - Amazing alpha for the tier, even in a full uptier
- Gun is accurate in comparison with the alpha
- AP pen is plenty enough
- -15 degrees of depression is the best in the game
- Gun mantlet can be trollish
Cons: - Speed is very underwhelming
- Frontal armour won't stop any HE shells bigger than 120mm (the sides won't stop anything)
- Camo isn't as good as other tanks of this line
- Engine tends to be damaged and set on fire
- Not game-changing, but sometimes annoying: only 10 degrees of elevation...
Others: For the equipment, this is a T7, so a gun rammer and camo net will be enough. I wouldn't run adrenaline but rather have double repair kit and medkit, because this tank's crew drop like flies. Ammo choice is simple: mostly AP, rest HE
Playstyle: This is an absolute odd unit... And the playstyle is not only incoherent with the rest of the line, but also with itself. On one hand high alpha and great gun depression point to a ridgeline warrior, but the weak engine (garbage reverse speed as well) and poor armour point towards a campier playstyle.
This tank sits in the middle and requires a hefty amount of map awareness: useless if too far back, will explode instantly if getting shot. This tank should be played second line, behind the heavies or meds, but in front of a pure-sniper TD such as a Skorpion. Early game, you should focus on finding a spot where you can safely hide, and quickly put a massive 500 damage in before disappearing: a ridge, such as the one on Winter Malinovka (just outside of spawn) or Rockfield (behind the second line bushes) are a perfect spot to lurk at.
Once the fighting has advanced, you can decide to reposition or push, knowing that you will probably outtrade anyone. Using this wisely, you can lock out the enemy from an area, secure a cap, or if shit hits the fan, trade shots. Don't forget to abuse those -15 degrees of gun depression, going over ridges and appearing in spots the enemy doesn't expect. Watch out for packs of mediums/lights, as one is already a lot of trouble, but several are a death sentence.
Rheinmetall-Borsig Waffenträger- the spirit of the line If you needed even more alpha and sneak, this is THE tank for you. The Borsig is a widely used tank, despite going completely against the heavy tank meta in this game: if that does not prove to you how good it is, nothing will. People simply love the idea of being undetected 70 meters away from an enemy, knowing they could hit them for 1k damage if they wanted to...
Pros: - Great alpha damage for the tier
- Fully rotatable turret
- Camo rating is among the best in the game
- Amazing HEAT pen: nearly 370mm
- Decent HE pen
- Access to a ridiculously strong set of superconsumables and provisions makes this tank exponentially better
- Good hull traverse
Cons: - No armour whatsoever: any tank can pen with HE
- The derp is inaccurate and unreliable at mid-to-long range
- Low AP pen
- Low shell velocity
- Tank is very light: takes a lot of ramming damage
- Gun depression is subpar
Equipment: Camo net, along with refined gun and calibrated shells are a must. EGLD and supercharger are both good (depends on your playstyle: supercharger for longer range engagements, EGLD if you find yourself closer to the enemy often), the rest is up to you.
Provisions: I run chocolate and improved fuel, but an absolute must (and an insanely broken provision that everyone should exploit) is the HE Spall liner, reducing HE damage to below AP-ish levels of damage.
Consumables: My go-to consumables are double repairs and reticle calibration, because this gun is quite inaccurate (the reason I don’t take adrenaline is that adrenaline is made for situations the Borsig shouldn’t be in in the first place, while reticle calibration serves the useful purpose of making your accuracy go from very bad to acceptable)
Playstyle: This tank is sniper-second line hybrid, although completely different from the Emil. Instead of hiding behind ridges and trying to stay within trash talking distance of the fight, this tank relies on its incredible camo values: if you find a bush, enemies will have to get nearly within proxy-spotting range to see you. Always find a good position for your flank, while always minimising the risk of being rushed with no support. Pushing alone is a death sentence.
At the start of a match, you should use this incredible camo to take a position that is hidden, preferably behind a bush (relatively far from the action, around >220m) so that you may stay undetected after shooting, or if you are unlucky and get city maps such as New Bay, Port Bay or the TD nightmare a.k.a Himmelsdorf, find a corner you can peek while minimising exposure. The priority is to get to a safe position with favourable view on your flank: the hills at spawn on Castilla, the tall ridges near the railways on Alpenstadt... Stay safe until the fighting has died down, but don't hesitate to find another sniper's nest or to reinforce the other flank if you are not being too productive for your own team. This is also the ideal moment to use reticle calibration to make every shot count.
Late-game the goal is to push with what is left of your allies: trading shots is less advisable than with the Emil, as your HP relative to the tier is worse, and high alpha guns become more common at T8. Instead, you can be a bit more daring with your positioning: take spots that are concealed without being concerned about remaining invisible after firing, any bush will do. Relocate often while keeping an eye out for enemies that are not within one-shot range, as they will be able to take the initiative against you. Basically: use the element of surprise.
Waffenträger auf Panzer IV- the true peak of the line We are at T9, yet we have reached the apex predator of the line, the reason of this line’s popularity, and the bane of all your enemies on open maps. Tell me: when was your last T9 ratings match without at least one, or even two Waffenträgers on either side? Yeah, I can’t remember either… And honestly, rightfully so, as this is probably my favourite tank in the entire game, even after the nerfs.
Pros: - Fully rotatable turret
- Very good camo values
- High accuracy and better shell velocity than Borsig
- Good pen for all shells
- Both guns are viable
- Access to HE spall liner
- Good hull traverse
- Rear placement of the turret is an advantage: more on this later...
Cons: - Turret is quite large and weak
- Engine is weak and easily set on fire
- 12.8cm: bad depression angles over the front, the gun is quite a bit heavier
- 15cm: the gun shield becomes MUCH bigger, elevation when looking backwards is 0 degrees
Equipment: Camo net and refined gun are a must, but on this one improved assembly is as well. Calibrated (for the HEAT and HE pen) and supercharger (for the subpar shell velocity) for the 15cm, rammer (for extra DPM) and EGLD (the aiming time isn’t amazing for a sniper) for the 12,8cm.
Provisions: Same as with the Borsig, I take improved fuel, HE Spall liner and chocolate
Consumables: You get more of a choice here for what you can take, depending on gun choice and your personal playstyle preferences. The only thing I would not let go of under any circumstance is my double repair kit, because the engine on this tank is made of explodium. I usually run this tank with double repairs and medkit (with the 15cm), but you could make the case for both RC and adrenaline on the 15cm, while RC is kinda pointless on the 12.8cm.
Playstyle: The Waffle does what the Borsig did save for camo but outshines the Borsig at everything else and feels more flexible. Thanks to the now good accuracy of the 15cm, it can stay back and safe for longer while hitting shots way more often, allowing you to focus on survival instead of constantly being pressed to get as close as you can without dying. And when the time is right, better mobility, turret traverse, accuracy and higher HP make you infinitely more capable of standing alone.
Early-game should be standard for a sniper tank: just find a bush with good vision over your flank and take shots whenever possible. You can’t be as daring in positioning as a Borsig (your camo is somewhat worse), but here comes the twist that has defined the Waffle’s playstyle: the rear-mounted turret. Use this to your advantage by sneaking around a corner or a rock undetected, taking a shot, then quickly going back. Same thing applies when in bushes: only your turret is sticking out when you take a shot, so that you minimise exposure to the enemies. The reason I call the rear-mounted turret an advantage when most oftentimes it’s regarded as a drawback is that this tank has a high camo rating and good manoeuvrability, while other rear-mounted tanks tend to lack both.
Once you have abused your newly learned trick and the battle has advanced, it’s time to think about repositioning. Just like this tank’s predecessor, a careful approach, methodically going with your allies and finding hiding spots such as bushes or corners where you can’t be surprised is better. The reason I said the Waffle is better when standing alone is because anything can stand better than a fish on dry land (a.k.a the Borsig). Tanks you should be especially wary of are anything with a gun as big as yours, because spall liner can negate SOME damage but not module damage, and people love to shoot at such a squishy target as you.
Grille 15- an underwhelming ending So, you kinda got carried away playing the amazing Waffle, huh? So, you buy this tank, and are met with a disappointing blend of characteristics… A decent damage per shot, good DPM for the alpha, good mobility and a dispersion on the move so bad you could miss a building from the inside. It does play slightly differently than its predecessors in that it has less than half of the Waffle’s camo rating and loses the fully rotatable turret: everything that made this whole line special…
Pros: - Decent DPM
- Best accuracy ingame when fully aimed
- Fast aiming time
- Great shell velocity
- Good mobility
- Access to HE spall liner
- Good AP pen
- Wide turret arcs
- Long gun barrel occasionally blocks shots
Cons: - Little armour
- One of the biggest aiming circles when not fully aimed (on par with the likes of KV-2)
- Terrible camo values
- Terrible HEAT pen
- Low HP
- Subpar traverse speed
- Barely any depression over the front (-4 degrees) and the sides (-5 degrees)
- Tank is very tall: on par with Jg.Pz. E100
Equipment: Camo net, refined gun and calibrated shells are most important. Supercharger isn’t necessary so go with EGLD, and I suggest taking engine accelerator as well as improved assembly. The rest is up to you, it won’t change that much.
Provisions: As per usual, chocolate, improved fuel and spall liner do wonders
Consumables: I’d say the choice boils down to two selections: either double repairs and medkit, or double repairs and adrenaline. I don’t understand people who take RC, as it brings little value to a gun that is already very accurate when aimed in…
Playstyle: The Grille definitely feels like it’s been made with camping all the way back in mind, having no fully rotatable turret, on the move dispersion factors worthy of a KV-2, little armour, little HP and not enough traverse speed. I play this tank as a dedicated sniper, taking advantage of its #1 accuracy when standing still, and sitting far enough from the engagement (>270m) to not be spotted after firing. Sometimes moving up is better, although you need to perfectly calculate your route to not end up in a sticky situation.
The early game consists of fighting the enemy team, but also your own tank: finding a position that has good view over your flank, doesn’t require good depression angles and is far enough to not immediately blow up after firing is hard. A few examples: the hill near both spawns on Castilla medium side, the classic camping ridges at spawn on Canal, the bridge at both spawns on Alpenstadt… And if you are very unlucky, you’ll end up on Himmelsdorf, which is completely flat (If you end up on the worst map in the game a.k.a Dynasty’s Pearl, Alt+f4). Fortunately for the player, the Grille excels at this, being insanely accurate and having a very easy time landing shots at this stage of the battle.
Now comes the hard part: moving up with the Grille. It is very easy to get carried away and ending up facing an enemy alone, which is an absolute no-no in this abomination. If you get caught off-guard, your enemy will always be able to either outtrade or outmanoeuvre you. When there is no choice, stick to tight corners on areas as open as possible: for example, the houses in the middle Oasis Palms are perfect cover if there are enemies on either side of the map. Try to quickly peek the enemy if they don’t know where you are, or if they do, try to bait a shot onto your tracks, or your extremely long barrel. DO NOT, under any circumstances, facehug the enemy because you are tall and have no depression while the enemy will have an easier time pushing you in a disadvantageous position.
This ended up being a gigantic wall of text, but hey, it's detailed alright, and I really tried giving my best tips from playing this line this much :)