Sudden increase in problems

Darnielle · 12-07-2011, 11:05 AM

My Vox had been relatively problem-free before today; it froze a handful of times and WiFi has been patchy, but other than that it worked smoothly.
This morning around 12PM I was given a prompt that an update was available for the Vox. "Great!", I thought, "This'll be Kobo fixing some problems."
I clicked to update and then the device locked up. I restarted it, and the touchscreen wouldn't accept input. I restarted it, and this time the screen worked fine. I checked the Firmware Update app and it says Firmware is up to date.

But now, problems with WiFi have skyrocketed, to the point that I have to toggle it five or six times to get it to work at all. The wake from sleep bug now happens two out of three times the device enters sleep, and typing seems less responsive. I'm not sure whether the lock-up during the update caused this or whether it's just bad timing, but I thought I'd better make a thread since the circumstances are unique.

Has anyone else experienced something like this? Can someone shed some light on the situation?

Jesslynne · 12-07-2011, 11:17 AM

I am definitely having the same type of issues. Wifi won't connect to a remembered network unless I do so manually, and if I put it to sleep it's guaranteed I have to hard boot it because it won't wake from sleep and when it DOES, the screen is frozen.

I've tried a factory reset but it hasn't helped at all.

KoboJW · 12-07-2011, 11:18 AM

Is this the first time you updated since you bought your Vox? We have not pushed a new update since early November...

Jesslynne · 12-07-2011, 11:26 AM

I myself hadn't updated recently. My problems have just grown phenomonally large.. and I haven't done anything all that differently. It's just started and now it's frustrating me to no end..

I demo my own Kobo normally, so I keep it in sleep mode during work (normally all day really...) and now it just either wakes itself from sleep freezes and drains my battery when I don't have it on me to notice.. or never wakes from sleep ever.

Darnielle · 12-07-2011, 11:50 AM

@JW: No, my Vox was up to date before the update notification appeared... I checked here and found it strange that a thread hadn't been made.

An icon, the android mascot with one arm raised, appeared on the notification bar while I was reading. I opened the tray to see what it was, and it said something along the lines of 'An update is available for your Kobo Vox'. I don't have any apps that would cause a notification like this to appear, and the fact that it gave the device name makes me think it's unlikely to be a virus or malware. I was thinking it might've been a techie at Kobo jumping the gun with an update.

oldyellr · 12-07-2011, 12:47 PM

From the Kobo Vox user guide:

Quote:

Updating your Kobo Vox software

Your Kobo Vox regularly checks for software updates by itself. Software updates offer new features and typically better stability. You can also manually check for updates.

To check for updates:
1. Tap the Home button on your Kobo Vox.
2. Tap the Menu button on your Kobo Vox.
3. Tap Settings.
4. Tap About Kobo eReader.
5. Tap System Update.
6. Follow the onscreen prompts to install software updates.

I also came across an item in the settings somewhere called "Update Firmware", or something like that, but I can't find it again. Where is it and what does it do different from the system update? How do I know if my firmware needs updating? If I find it again, should I click it to see what happens? Since my Vox has been running fine for the last couple of weeks since I've had it (updated to 2011/11/17 when I started it) except for one instance of having to wake it with a 10-second reset, I don't really want to try anything that might mess it up.

KoboJW · 12-07-2011, 12:49 PM

So you already applied the November update?

Can you tell me the build number you now have?

You can find it under:

Settings > About Kobo Reader > Build Number

Thanks!

KoboJW · 12-07-2011, 12:53 PM

Firmware update is found in the application page. It is there because very occasionally part of the first update does not successfully apply, so the app fixes it. If you aren't experiencing problems, you have no need to run it.

taming · 12-07-2011, 01:26 PM

By first update, are you referring to the setup that people did when the Vox was brand new and had never been set up at all? I seem to remember that a small % of devices purchased within a fairly narrow time period needed this, but most did not.

Darnielle · 12-07-2011, 03:02 PM

My build number is:

Code:

imx51_bbg-eng 2.3.3 GRI40 eng. 
UK.20111115.151942.39970 test-keys

mr_nobody · 12-07-2011, 03:14 PM

Since the most recent patch was pushed out on Nov. 17 and yours is dated Nov. 15, that's a little bit suspicious looking...

afv011 · 12-07-2011, 03:47 PM

Quote:

Originally Posted by Darnielle

My build number is:

Code:

imx51_bbg-eng 2.3.3 GRI40 eng. 
UK.20111115.151942.39970 test-keys

"test-keys" looks wrong to me. The software should be signed with an official Kobo key, not a "test key", these tests keys are for development work only.

Also, note the "eng" at the end of the build number, this would indicate this is an Engineering build (for development only), as opposed to a Release build (for production).

KoboJW · 12-07-2011, 03:57 PM

OK, I didn't realize you were in the UK. By the build number, it looks as though your device failed to update. Can manually check for updates again and let me know if it still thinks you need to apply the update? Make sure your device is well charged first, please.

Thanks,
James

Darnielle · 12-07-2011, 04:15 PM

'Current firmware V15 is up to date. No update is needed.'

If the Vox failed to update, aren't the build descriptors afv011 pointed out somewhat strange?

Reader Paradice · 12-07-2011, 04:22 PM

Quote:

Originally Posted by afv011

"test-keys" looks wrong to me. The software should be signed with an official Kobo key, not a "test key", these tests keys are for development work only.

Also, note the "eng" at the end of the build number, this would indicate this is an Engineering build (for development only), as opposed to a Release build (for production).

--------------------------------------------------------------------------
My 'official' Kobo download (other than the initial one after bringing home) also has 'test key' at the end of the string. That is the one that was downloaded after james said that a download was available....

imx51_bbg-eng 2.3.3 GRI40 eng.
CAN.20111117.18253940022 test-keys

I have had no issues with this one that I can see....

12-07-2011, 11:05 AM	#1
Darnielle Enthusiast Posts: 37 Karma: 136122 Join Date: Dec 2011 Device: Kobo Vox	Sudden increase in problems My Vox had been relatively problem-free before today; it froze a handful of times and WiFi has been patchy, but other than that it worked smoothly. This morning around 12PM I was given a prompt that an update was available for the Vox. "Great!", I thought, "This'll be Kobo fixing some problems." I clicked to update and then the device locked up. I restarted it, and the touchscreen wouldn't accept input. I restarted it, and this time the screen worked fine. I checked the Firmware Update app and it says Firmware is up to date. But now, problems with WiFi have skyrocketed, to the point that I have to toggle it five or six times to get it to work at all. The wake from sleep bug now happens two out of three times the device enters sleep, and typing seems less responsive. I'm not sure whether the lock-up during the update caused this or whether it's just bad timing, but I thought I'd better make a thread since the circumstances are unique. Has anyone else experienced something like this? Can someone shed some light on the situation?

12-07-2011, 03:02 PM	#10
Darnielle Enthusiast Posts: 37 Karma: 136122 Join Date: Dec 2011 Device: Kobo Vox	My build number is: Code: imx51_bbg-eng 2.3.3 GRI40 eng. UK.20111115.151942.39970 test-keys

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Calibre won't open all of a sudden.	kindlecrack	Devices	4	09-13-2011 11:19 PM
Help with starting all of a sudden...	mharrop19	Calibre	9	01-19-2011 01:56 AM
Classic Power Issue all of a sudden	jhempel24	Barnes & Noble NOOK	8	11-21-2010 06:17 PM
Sudden Kobo failure	The Whether Man	Kobo Reader	7	08-30-2010 09:19 PM
DR800SG sudden reboot?!	Franky	iRex	0	05-13-2010 12:04 PM

12-07-2011, 11:17 AM	#2
Jesslynne Zealot Posts: 141 Karma: 126 Join Date: Nov 2011 Location: Manitoba, Canada Device: Kobo Vox, Kobo Mini	I am definitely having the same type of issues. Wifi won't connect to a remembered network unless I do so manually, and if I put it to sleep it's guaranteed I have to hard boot it because it won't wake from sleep and when it DOES, the screen is frozen. I've tried a factory reset but it hasn't helped at all.

12-07-2011, 11:18 AM	#3
KoboJW UX Lead, Kobo Vox Posts: 113 Karma: 199002 Join Date: Oct 2011 Device: Boxes of Voxes	Is this the first time you updated since you bought your Vox? We have not pushed a new update since early November...

12-07-2011, 11:26 AM	#4
Jesslynne Zealot Posts: 141 Karma: 126 Join Date: Nov 2011 Location: Manitoba, Canada Device: Kobo Vox, Kobo Mini	I myself hadn't updated recently. My problems have just grown phenomonally large.. and I haven't done anything all that differently. It's just started and now it's frustrating me to no end.. I demo my own Kobo normally, so I keep it in sleep mode during work (normally all day really...) and now it just either wakes itself from sleep freezes and drains my battery when I don't have it on me to notice.. or never wakes from sleep ever.

12-07-2011, 11:50 AM	#5
Darnielle Enthusiast Posts: 37 Karma: 136122 Join Date: Dec 2011 Device: Kobo Vox	@JW: No, my Vox was up to date before the update notification appeared... I checked here and found it strange that a thread hadn't been made. An icon, the android mascot with one arm raised, appeared on the notification bar while I was reading. I opened the tray to see what it was, and it said something along the lines of 'An update is available for your Kobo Vox'. I don't have any apps that would cause a notification like this to appear, and the fact that it gave the device name makes me think it's unlikely to be a virus or malware. I was thinking it might've been a techie at Kobo jumping the gun with an update.

12-07-2011, 12:49 PM	#7
KoboJW UX Lead, Kobo Vox Posts: 113 Karma: 199002 Join Date: Oct 2011 Device: Boxes of Voxes	So you already applied the November update? Can you tell me the build number you now have? You can find it under: Settings > About Kobo Reader > Build Number Thanks!

12-07-2011, 12:53 PM	#8
KoboJW UX Lead, Kobo Vox Posts: 113 Karma: 199002 Join Date: Oct 2011 Device: Boxes of Voxes	Firmware update is found in the application page. It is there because very occasionally part of the first update does not successfully apply, so the app fixes it. If you aren't experiencing problems, you have no need to run it.

12-07-2011, 01:26 PM	#9
taming Trying for calm & polite Posts: 4,012 Karma: 9455193 Join Date: May 2010 Location: Mostly in Canada Device: kobo original, WiFI, Touch, Glo, and Aura	By first update, are you referring to the setup that people did when the Vox was brand new and had never been set up at all? I seem to remember that a small % of devices purchased within a fairly narrow time period needed this, but most did not.

12-07-2011, 03:14 PM	#11
mr_nobody Evangelist Posts: 440 Karma: 26671 Join Date: Nov 2011 Device: kobo mini, nexus 7 (2012), kobo vox	Since the most recent patch was pushed out on Nov. 17 and yours is dated Nov. 15, that's a little bit suspicious looking...

12-07-2011, 03:57 PM	#13
KoboJW UX Lead, Kobo Vox Posts: 113 Karma: 199002 Join Date: Oct 2011 Device: Boxes of Voxes	OK, I didn't realize you were in the UK. By the build number, it looks as though your device failed to update. Can manually check for updates again and let me know if it still thinks you need to apply the update? Make sure your device is well charged first, please. Thanks, James

12-07-2011, 04:15 PM	#14
Darnielle Enthusiast Posts: 37 Karma: 136122 Join Date: Dec 2011 Device: Kobo Vox	'Current firmware V15 is up to date. No update is needed.' If the Vox failed to update, aren't the build descriptors afv011 pointed out somewhat strange?

Advert

Advert