Moto G bugs - does vf's custom firmware fix them?

[DarranAmes]

There are a number of very annoying bugs that exist in the retail (and tesco) android firmware for 4.4.2 - which are detailed extensively here  - https://forums.motorola.com/posts/48fb0b8150

Motorola seem to be investigating, but don't yet have a solution.

Now I understand that vodafone are (or have) released the Moto G.  I assume that they would have undertaken some testing.  I'd like to know whether the 4.4.2 firmware for vf experienced things like 'stealth aeroplane' mode, etc.

Link for vf 4.3 and 4.4.2 firmware - http://sbf.droid-developers.org/phone.php?device=14

If they do fix the problems, then I might flash my phone.

Thanks,

Darran

[jeffkinn]

I think you are over estimating what networks do to firmware. They'll test that the radio works with the network and they'll add some customisations such as a Vodafone splash screen and perhaps some Vodafone apps.

They will not do anything to the core OS be it stock Android or anything else laid on top of stock.

If there are bugs on the MotoG from Motorola, they'll still be there in the Vodafone version.

[DarranAmes]

If that's the case, then I'd fail to see how vodafone would offer up a branded 4.4.2 seeing as it performs so poorly on their network - and I would have thought that the right thing to do would be to hold back on 4.4.2 until the underlying issues had been fixed (4.3 works just fine on vf).

(I was kinda hoping that as a result of any testing, that they would have gotten new radio code before releasing).

[jeffkinn]

On what basis do you say that 4.4.2 performs poorly? I think the Moto G is probably the first KitKat device that Vodafone supplies, and that has only just been launched.

Certainly no Samsung phones have yet been upgraded to 4.4.2 - not 100% sure about the HTC One offhand.

[DarranAmes]

Take a read here - https://forums.motorola.com/posts/48fb0b8150

The vast majority either have retail or generic tesco firmware (and subsequently unlocked).  None had network problems with 4.3, just since 4.4.2 was rolled out.

I'm not knocking the hardware - the G is a great phone; it's just that 4.4.2 has some serious radio issues (particularly when using vodafone or one of its MVNO as a carrier).

[jeffkinn]

Tesco uses the O2 network - what relevance does it have to the performance of a device on the Vodafone network?

[DarranAmes]

Unlocked and used with a vodafone sim (therefore cutting o2 out of the mix) 

4.3 tesco unlocked + voda sim = fine

4.4.2 tesco unlocked + voda sim = cellular problems

4.3 retail + voda sim = fine

4.4.2 retail + voda sim = cellular problems

Not hard to see the pattern - 4.4.2 and vodafone as carrier does not make for a good phone.

There are some suspicions that it might be down to the frequencies on which the operators run their services.

Like I say, read the thread - all 17 pages of it, rather than me reproducing it all here!

This is why I raise the question here - so that someone with inside knowledge of vodafone (and what customisation, if any) they've done could give their input.  Or indeed whether they've actually tested 4.4.2.

[jeffkinn]

@Nabs Please read this thread. You're running 4.4.2 on your Nexus 5 I assume. Is it ok on the Vodafone network?

[Nabs]

Hi DarranAmes,

I haven't read all 17 pages on the motorola forum but had a quick skimthrough the first few so I have an idea of what the issues are.

I don't think this is something related to Android 4.4.2 core as, like @jeffkinn mentioned, i've been running it on my Nexus 5 with none of the issues mentioned. In fact the only issue I have had with my Nexus 5 since the 4.4.2 update is it's insistance on freezing up the keyboard when in the hangouts app though thats probably the app rather than Android itself.

I suspect the issues are going to be device specific, and as they all appear to in some way relate to the radio connection I'd hazard a guess that it's a bug in the Motorola drivers. It could be, and has been seen in the past (though can't remember which handset now) that certain frequencies cause the phone to behave in different ways which would explain why it only affects devices on some networks and not others.

With regards to the Vodafone specific version, they might have had a fix included in their build if it was picked up in testing. Either way Moto seem to have a pretty good handle on the issue and, at least from the first couple pages, seem quite keen to look into it so fingers crossed they get something out soon. 

Nabs

[DarranAmes]

Hi @Nabs and @jeffkinn

Thanks for taking a look - my curiosity is that I suffer this somewhat annoying feature and would dearly love to know what solutions (if any!) have been identified.

I agree that it seems to be a Motorola-specific problem with 4.4.2 (though I seem to recall coming across some similar reports for nexus 4 users whilst having a dig around) - hence was curious as to whether it has cropped up on vf's internally testing (and I would suspect that vf have more clout at getting things fixed as us as individuals!).

Appreciate both your rapid responses - I will sit back and see what happens.

Thanks,

Darran