Jump to content

lllRL

Members
  • Content count

    1,137
  • Joined

  • Last visited

  • Days Won

    13

lllRL last won the day on December 30 2018

lllRL had the most liked content!

About lllRL

  • Rank
    Forum Legend
  • Birthday November 14

Profile Information

  • Gender
    Male
  • Location
    UK
  • Interests
    Hi :) https://www.youtube.com/c/RL1411

Recent Profile Visitors

4,548 profile views
  1. lllRL

    R1 WiFi dying

    @Jack or whoever else might be handling emails... I replied to that email regarding the replacement R1 five days ago. Any chance someone could check it please?
  2. lllRL

    R1 WiFi dying

    Saying what alongside the link to this thread mate?
  3. lllRL

    R1 WiFi dying

    Mine just started messing up again... back on the old firmware. Had to swap over to my TP Link WiFi for the umpteenth time as I either drop out repeatedly or get stuck with <0.25Mb bandwidth and 100ms ping/1000ms jitter instead of the usual 75/20Mb and 6ms/0ms.
  4. lllRL

    PS4 SDD broken?

    I haven't really played BO4 because of connection issues but the game seems a laggy mess either way. The menus are even worse than BO3's... I tried to play on a fairly new PS4 Pro with a brand new Samsung 860 SSD and the menus are disgusting, it takes forever to pull up the share menu to save a clip and my PS4 sounds like a jet trying to take off. I don't see any of those issues in other games... Maybe your fan could use a clean though. I cleaned my PS4 Pro out (I think the method for accessing the fan is a little different) and because there was only a little dust inside, it didn't seem to make much difference. That could be your problem if the console hasn't been cleaned out after five years. Edit: sorry, I was sleep deprived and failed to notice you'd already done that LOL
  5. lllRL

    R1 WiFi dying

    I've only had mine 18 months, if that...
  6. lllRL

    R1 WiFi dying

    A fix for this absurdity would be marvellous ๐Ÿ˜‚
  7. lllRL

    R1 WiFi dying

    R1 is on one again, which is just typical after I decided to put my modem/router behind it back into bridge mode. Woke up and the WiFi symbol is visible but no Internet (cross symbol). Took 45 minutes to reconnect, and then I changed the WiFi channel. 5 minutes later it's out again for another 2 hours. Reconnected itself, changed the channel again, and then it started disconnecting and reconnecting every 30 seconds for about an hour. Changed back to the default channel (7) and it's stayed online for the last hour or so. I'm gonna sling it in a cupboard if it drops out again tbh. I had enough of this on old firmware and thought DumaOS fixed it, but suddenly it's randomly dropping out again ๐Ÿค”
  8. lllRL

    R1 WiFi dying

    Alright cheers. Please post here when you have any updates so I get the notification.
  9. lllRL

    R1 WiFi dying

    None of those apply to me already plugged directly into the wall, no other devices near it, out in the open (signal is fine when it's actually working, better than my TalkTalk hub) and nowhere near a microwave lol
  10. lllRL

    R1 WiFi dying

    Yup, it just started again. Only difference is there's now zero internet access instead of it coming and going with 0.1Mb
  11. lllRL

    R1 WiFi dying

    I haven't downloaded anything from a PC BTW ๐Ÿ™„ lol
  12. lllRL

    R1 WiFi dying

    Sorry for the late reply (trying to fix my broken sleep pattern lol)... No I didn't have anything like that set up at the time. The WiFi just randomly started working again yesterday afternoon ๐Ÿคจ
  13. lllRL

    R1 WiFi dying

    In the words of Limmy... I don't get it *sad confused face* ๐Ÿ˜‚
  14. lllRL

    R1 WiFi dying

    Mine did pretty often. I went back to the old firmware a few weeks ago before ping assist wasn't working on DumaOS, but then I remembered the WiFi dropouts and they pissed me off more so I upgraded again lol. I just wish they'd justified the time it took to release DumaOS by giving us a fully working product ๐Ÿ™„ Haha nah it's TalkTalk fibre to the cab. Should be 80/20, modem stats claim I can get anywhere from 70-74 down, and over WiFi it's normally 67 tops. Bit strange considering the cab is a stone's throw away, but I'm paying less than I did for BT 50/10 so I can't really complain about that. I'm not really gaming anymore because the connections I get are shite despite constantly low stable pings (6ms to London for example). The average game gives me a good 300ms of UDP latency and I can't even run custom games with bots without lagging so I'm not exactly getting any use out of the R1. However it would be nice if the rest of my devices could use the bandwidth at least...
  15. lllRL

    R1 WiFi dying

    My log mostly says this: Sun Mar 3 18:20:02 2019 kern.info dpiclass-daemon: Kill flow due to timeout Sun Mar 3 18:20:02 2019 kern.info dpiclass-daemon: Kill flow due to timeout Sun Mar 3 18:20:01 2019 user.warn com.netdumasoftware.settings: Error opening wireless-mirror with error wireless-mirror: No such file or directory. Sun Mar 3 18:19:48 2019 user.warn com.netdumasoftware.settings: Error opening wireless-mirror with error wireless-mirror: No such file or directory. Sun Mar 3 18:19:40 2019 user.warn com.netdumasoftware.settings: Error opening wireless-mirror with error wireless-mirror: No such file or directory. Sun Mar 3 18:19:02 2019 kern.info dpiclass-daemon: Kill flow due to timeout Sun Mar 3 18:18:32 2019 kern.info dpiclass-daemon: Kill flow due to timeout Sun Mar 3 18:18:32 2019 kern.info dpiclass-daemon: Kill flow due to timeout Sun Mar 3 18:18:32 2019 kern.info dpiclass-daemon: Kill flow due to timeout Sun Mar 3 18:18:32 2019 kern.info dpiclass-daemon: Kill flow due to timeout Sun Mar 3 18:18:32 2019 kern.info dpiclass-daemon: Kill flow due to timeout Sun Mar 3 18:18:32 2019 kern.info dpiclass-daemon: Kill flow due to timeout Sun Mar 3 18:18:32 2019 kern.info dpiclass-daemon: Kill flow due to timeout Sun Mar 3 18:18:32 2019 kern.info dpiclass-daemon: Kill flow due to timeout Sun Mar 3 18:18:32 2019 kern.info dpiclass-daemon: Kill flow due to timeout Sun Mar 3 18:18:32 2019 kern.info dpiclass-daemon: Kill flow due to timeout Sun Mar 3 18:18:32 2019 kern.info dpiclass-daemon: Kill flow due to timeout Sun Mar 3 18:17:45 2019 kern.info kernel: [198622.428000] send: nf_ct_get failed Sun Mar 3 18:17:45 2019 kern.info kernel: [198622.428000] recv: nf_ct_get failed Sun Mar 3 18:16:05 2019 user.warn com.netdumasoftware.settings: Error opening wireless-mirror with error wireless-mirror: No such file or directory. Sun Mar 3 18:16:02 2019 kern.info dpiclass-daemon: Kill flow due to timeout Sun Mar 3 18:16:02 2019 kern.info dpiclass-daemon: Kill flow due to timeout I managed to stay connected to WiFi long enough to do this lol: That's with QoS disabled ๐Ÿค”
×