January OTA feedback for Tesco

[Guest PaulOBrien]

I thought i'd start a post to collate feedback on the January OTA for me to pass to Tesco.

So far...

• Battery problem fixed for some but not all
• Dolby now missing
• Icons are disappearing on reboot from the stock launcher

Anything else?

P

[Guest emayljames]

I'd also add that touch sensitivity is still not ideal, missing numerous touches.

I'm on Paul's latest image.

[Guest r00tmydevices]

Dolby Audio still showing under audio settings for me after root with latest image. Can select following options: Default, Music, Chat. Presumably that's the same as it was for everyone prior to the January OTA update?

Regarding issues with the battery. Earlier from being 100% fully charged, it dropped to 83% within minutes of switching device on whilst it downloaded and installed app updates. And depleted all the way down to 34% in under a couple of hours! :O Plugged USB charging cable in and continued to use device for a short while but noticed that the battery level wasn't moving from 34%. Does it not charge when connected to the mains if the display is on? Put device to sleep, went and grabbed a coffee and bite to eat. When I got back it's showing as fully charged which seems too quick to me.

Very strange behaviour from a barely used product. It's probably been charged no more than five times in total.

[Guest targetbsp]

From what people have been saying, there was a full on equaliser before. Not just presets.  I never looked at it myself!

 

You said you charged it 'earlier'.  How much earlier?  In my experience, Android tends not to notice it's battery depletion so much during standby - and then really make up for it when you next use it by plummeting the battery level to what it should be.

[Guest r00tmydevices]

From when I left it on charge, displaying 34% remaining, then returned to it a couple of hours later. Red light at top of screen had changed to green and it was now showing as fully charged. Device was not being used during this time. It was fully charged yesterday then switched off overnight.

Edited January 25, 2015 by r00tmydevices

[Guest SavageCore]

Clock still goes out of sync :(

[Guest Normola]

My clock was 5 hours out so I've tried altering the standard ntp server from pool.ntp.org to my isp ntp server. Will see if that makes a difference. Seems to have fixed it in the short term.

If you're feeling brave, the ntp server is configured in /etc/gps.conf. You'll need to be rooted to change this.

Edited January 26, 2015 by Normola

[Guest stevehudl2]

The battery charging problem did not seem to affect me as often as it did others, it would be now and then.

but since the update I have had problems charging it more often, last night it did not charge so I restarted it and took it to work, it was left on charge all day and did not charge even 1% I have restarted again and now it is finally charging!

I can't comment on the clock, it used to go wrong all the time and since then I have stopped trusting it and pretty much ignore that it's even there anymore.

It currently shows the correct time but it used to go wrong then put itself right again randomly so being right now means nothing.

Seriously tesco, unlock the bootloader and let some very skilled devs give us recovery and custom ROMs that work!

I own this tablet, not you, I should be able to do with it what I want, android is not owned by you and is meant to be open source, so why have you locked it down?

[Guest djnw]

I had not experienced the charge bug until this update. Very significant hangs sometimes coming out of sleep, too.

 

ed: it has now happened twice in three days.

Edited January 27, 2015 by djnw

[Guest glossywhite]

I've got some feedback:

"Dear Tesco, 

 

Please test your product before selling it, and not ON your customers. Most grateful.

Kindest regards, 

Mr. E. Shopper"

[Guest stevehudl2]

I've got some feedback:"Dear Tesco,  Please test your product before selling it, and not ON your customers. Most grateful.Kindest regards, Mr. E. Shopper"

Lol, please send that to them, if nothing else but for a giggle ha ha

[Guest glossywhite]

Lol, please send that to them, if nothing else but for a giggle ha ha

 

We have a bloke here who can do that... Paul ;)

[Guest seanspotatobusiness]

I also am experiencing inaccurate time keeping on my Hudl as well as frequent problems with charging. Often it will stay at the same level of charge for a random amount of time before it suddenly starts taking charge.

Edited February 9, 2015 by seanspotatobusiness

[Guest mac9091]

Hi there, as i have not had any issues (touch wood) with charging my hudl 2 i have not yet updated to the latest version and so far it seems to have been a good choice.

However with Tesco's latest news release, the decline of thier ebook store "blinkbox books" (BB) and teh pootential deal with Kobo, it has left me wondering. For those of us who choose not to root (at the minute anyway) how do we now get rid of this bloatware (the BB app) once it stops being avaliable? I posed this question to the BB and they stated that it could be removed via the settings, which i knew was rubbish as that only allows the uninstall of any updates that have been carried out.

Or are Tesco happy to ignore this problem (for non rooted users) and expect us to be happy that it takes up some storage space???

[Guest munklefish]

Prior to the update I'd occassionally have the device show a fairly well charged battery that rapidly discharged but nothing regular.

Since the update I've been seeing my battery indicator show full or nearly full. Shortly after using it the device would then shutdown. The only way to get it to reboot would be to put it on charge. However this leads to 1 of 2 similar scenarios.

1) if the battery was showing full when it shutdown, the device will show as fully charged when I connect it to the charger. If I unplug it, it either won't boot up or shuts down before fully booting in to android.

2) if the battery status was showing as not full (eg 80%) when it shutdown it can be rebooted but shuts down before fully loading android or shortly thereafter. If I put it on charge it only takes a few minutes before it thinks the battery is fully charged.

In either case the only way to get out of this loop is to go through the process of charging until the thing has enough juice to power up. Then wait for it to shut itself down. Recharge, reboot, auto shutdown. And so on for typically 3 or 4 cycles.

To me this suggests that the devices battery status is only being update for a short period of time once (fully ?) Charged. After which it gets stuck at anywhere between 83 - 100%. Then when the battery actually goes flat the device shuts down. However when the charger is reconnected the device begins the charge under the impression that it only needs x% to fully charge itself before showing as being fully charged.

The charge status doesn't become unstuck by a manual or automated shutdown. However several on/off/charge cycles seems to eventually reset the battery status. Its odd however that whatever process detects a low battery and triggers the automated 'low battery status' shutdown does seem to know that the battery has reached a critical level.

It seems odd that their would be two separate process monitors for the battery that are working independently.

P.s. I'm also sporadicly experiencing the slowing of the clock when in use.

Edited January 28, 2015 by munklefish

[Guest r00tmydevices]

So far I've experienced extremely poor performance from my battery. It seems to charge to 100% okay but in use, with nothing but Chrome browser running, it depletes almost as fast as Usain Bolt! :O

I've downloaded a few battery monitor apps and need to start looking closer at the problem, making notes which I can then post to see what others suggest could be the issue. Poorest battery I've ever had the misfortune of using on any mobile device!

[Guest pudpoh]

For those of you having battery problems, this is something that can quite often happen after a firmware update. The general android advice is keep using the device until it powers itself off. Plug it in to charge but do not start it back up. Leave it a good 6 hours or so to fully charge even if the indicator is saying it has finished charging. You can then turn it on and use it and the battery should be ok after this.

[Guest r00tmydevices]

For those of you having battery problems, this is something that can quite often happen after a firmware update. The general android advice is keep using the device until it powers itself off. Plug it in to charge but do not start it back up. Leave it a good 6 hours or so to fully charge even if the indicator is saying it has finished charging. You can then turn it on and use it and the battery should be ok after this.

Will give that a try. Thank you.

[Guest jimwin]

I've just joined the HUDL 2 community, getting mine last weekend.

It's auto updated to a release date 06/01/2015, (not sure yet if this is the latest update mentioned here) and I'm definitely getting the charging issue.

 

I didn't use the device before the update, so I can't say if it was happening before.

[Guest r00tmydevices]

I've just joined the HUDL 2 community, getting mine last weekend.

It's auto updated to a release date 06/01/2015, (not sure yet if this is the latest update mentioned here) and I'm definitely getting the charging issue.

I didn't use the device before the update, so I can't say if it was happening before.

Yes, you have the latest update that most hudl 2 owners have installed. Try the above suggestion and let us know if it sorts out your battery issue.

[Guest welshblob]

So what what an occasional charging issue before the update now appears to be permanent and always requires a reboot to charge. Another point to note is that it only reaches 99% charged which wasn't an issue before the update. Also have experienced the clock being out of sync again but this is the first time since update. I have not done a factory reset since the update.

One odd thing that happened last night is when trying to power it down last night to charge then whenever connecting the charger then it kept turning itself on. I don't believe it did that before the update but not sure.

[Guest PaulOBrien]

I've raised the issues with Tesco, let's see what they say!

P

[Guest glossywhite]

I've raised the issues with Tesco, let's see what they say!

P

 

 

They'll say: "Thank you; every little helps" :P

[Guest r00tmydevices]

They'll say: "Thank you; every little helps" :P

You are too funny with your Tesco jokes. PMSL!

[Guest pudpoh]

I can also concur with others here, charging bug is not fixed, although I did install the Dolby equaliser apk the other day but have charged successfully a couple of times since then, but not today when plugged in at 12%. I may try a factory reset later today as don't have much on my Hudl and see what happens.