Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

7 Neutral

About gavin.19

  • Rank
  • Birthday 05/12/1978

Profile Information

  • Location
    Belfast, N.I
  • Your Current Device(s)
    ZTE Skate/Y300/Moto G
  1. Has the update dropped for o2 Moto G (2013) for anyone? I have heard Tesco phones got it. Thing is, I was running Lollipop with CyanogenMod for months but call waiting would never work. I went back to stock 4.3 on o2 and I got an update to 4.4.2, but that's the latest update it'll give me. Not even 4.4.4. I'm wondering if I flash the Tesco build instead so I can get Lollipop, will call waiting still work or is reliant on it being an o2 build? The phone was originally Tesco but it's currently unlocked/rooted and I'm using an o2 sim.
  2. On CM11 nightly builds (and other ROMs that use CM in part) the iPlayer, when starting to watch something, will cut to a green screen, lock up, then reboot the phone. If I use the last stable build (from May) then it works fine, but I get issues with dropped calls, callers not being able to hear (or vice versa), or calls ending when the proximity sensor is tripped. Calls are obviously more important than being able to use the iPlayer, but it'd be nice to try to find a workaround for this if possible. Can anyone using the CM11 nightlies test the iPlayer to see if they get the same issue?
  3. I wasn't aware of the extra space required. On that note, I regret getting the 8GB version now. Will have to get one of those little MicroSD dongles.
  4. One of the few things I'd like to do. Pity Xposed doesn't work with ART.
  5. Congrats. Seems we're one of the few unlucky ones that had to go the more expensive route, but still, it's still a lot less than the £20 Tesco would charge.
  6. One of many articles that have popped up today stating the same info, worded a little differently. I still haven't heard of a single person anywhere in the UK that has confirmed they've got the update yet. http://forum.xda-developers.com/showpost.php?p=49208630&postcount=164
  7. I downloaded the update zip that's linked in the xda thread and copied it to the root of the sdcard, ie where Music/Pictures etc folders are. I flashed the latest German Retail ROM from http://sbf.droid-developers.org/phone.php?device=14 When it rebooted, it detected the update and asked if I wanted to apply it, so I did. Prior to all this, my phone was rooted, network unlocked and had an unlocked bootloader. I don't know which of those are/aren't necessary, but that's what i had. I just switched the runtime to ART and rebooted. It took a few minutes for it to optimize all the apps again but it's back working and I haven't noticed any issues at all (yet).
  8. The more expensive unlock method worked for me - http://www.ebay.com/itm/160993247848 Got my code in a little over 24 hours.
  9. http://www.modaco.com/topic/367280-its-here/?p=2186409 The rollout has started in France, and then Germany, at least according to reports at http://forum.xda-developers.com/showthread.php?t=2594590
  10. Cheers. That smgreen guy suggested I use the £6.50/3-working-day unlock method. I'm just waiting for him to clear his current backlog and start taking orders on that listing again.
  11. Rollout has begun in France. http://forum.xda-developers.com/showthread.php?t=2594590&page=4
  12. Could you expand a bit on why you think nothing has changed or why we won't see any updates? From a thread on XDA it says that the KLB20.9-1.10-1.9 relates to Europe. The US page lists 172.44.4.falcon_umts.Retail.en.US as the build/version id. The update page seems to have only been added yesterday. There is no OTA update available on my phone yet, but it looks like they're at least prepping for it. Yes, if your phone is unlocked, and even then some people with handsets from Tesco have reported issues. Also, it needs a wipe, as opposed to just being able to update to 4.4.
  13. He has been on holiday for 2-3 days but says he'll be back today (2nd). I'll probably just wait a week or two to give the servers time to update and try again. I should mention that the other seller issued a prompt refund on both the listings that I tried, ie the base £2 one and the £5 'Tesco-specific' one. Neither worked, but you get a refund anyway so I'd just try the £2 first.
  14. Cheers. I gave in and transferred to Tesco, although it'll probably not be until the 2nd/3rd until it's completed. I will do as you suggested though and try again in a week or two, then I can switch back to O2.
  15. I'm sure they all use the same servers. As soon as I get the code (or don't), I'll leave a message. EDIT: I got a reply informing me of a refund for the first listing, then I got another one about half an hour later saying exactly the same thing for the Tesco-specific listing. IMEI rejected again. I'm sorely tempted to just go the PAC route so I can at least start using the phone properly. If it's an issue with waiting for the servers to be updated then it could be weeks, if ever. I'm not going to sit around trying different unlockers every so often on the chance it'll work. I'm going to check out the £20 Tesco route as a last resort.
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.