Can't connect Kobo Aura - Page 2

davidfor · 03-08-2014, 05:51 AM

Quote:

Originally Posted by arasyi

My glo by default doesn't have the sort menu on Collection,
but adding one of these lines in Kobo eReader.conf fixed it (Thanks!):

What firmware version do you have?

arasyi · 03-08-2014, 06:18 AM

Quote:

Originally Posted by davidfor

What firmware version do you have?

3.2.0 (updated from 2.6.0)

rxmom03 · 03-09-2014, 08:21 PM

Quote:

Originally Posted by arasyi

My glo by default doesn't have the sort menu on Collection,
but adding one of these lines in Kobo eReader.conf fixed it (Thanks!):

Code:

LastLibrarySorter_shelfList_=sortByShelfName()
LastLibrarySorter_shelfList_=sortByCreationDate()
LastLibrarySorter_shelfList_=sortByItemCount()

Thank you! I had to add all three lines, but now have my sort options back.

Mary

davidfor · 03-09-2014, 09:29 PM

Interesting. When I removed the line, the sort menu disappeared. But, I only needed to put one line in to get display it. I would expect that if you look again, there will only be one of these lines.

TechniSol · 03-09-2014, 10:36 PM

I had the same problem when I upgraded to 3.20 on my Glo. I had the issue with the two finger lighting control hack, did a factory reset with the light button on boot, went through downloading/upgrading firmware twice through WiFi on the Kobo and later saw there was no way to sort the collections list, but individual collections had sort options. I followed David's advice above to add the line to the conf file. I expect that the two step firmware upgrade had something to do with the line failing to be added to the file. Not sure what version the first downloaded firmware was, as on reboot it checked again for an update and downloaded it without an opportunity to see the settings page.

I strongly suspect that Kobo is depending on users installing incremental updates to get all their ducks in a row when they should be making sure all dependencies are present in each firmware since there is no guarantee of what firmware users started at and apparently not a very good mechanism in place to force necessary intermediate upgrades.(Wow, that's a long sentence...)

This sort of thing could explain why some people have battery drain issues, or other weird bugs that seem to be dependent on what order of firmware upgrade path has been taken. In short, it could explain a lot.

rxmom03 · 03-10-2014, 12:56 AM

Quote:

Originally Posted by davidfor

Interesting. When I removed the line, the sort menu disappeared. But, I only needed to put one line in to get display it. I would expect that if you look again, there will only be one of these lines.

I'm scared to touch it and mess it up again

But at least I know where to look now.

Mary

davidfor · 03-10-2014, 01:03 AM

Quote:

Originally Posted by TechniSol

I strongly suspect that Kobo is depending on users installing incremental updates to get all their ducks in a row when they should be making sure all dependencies are present in each firmware since there is no guarantee of what firmware users started at and apparently not a very good mechanism in place to force necessary intermediate upgrades.(Wow, that's a long sentence...)

Kobo can't rely on that because one of their problem solving steps is "Do a factory reset". That will install the latest firmware over the original. Also, testing an install over a factory reset is a lot easier and more repeatable than testing over incremental updates. I would expect most of their development testing to be a factory reset, install latest release version and then install the test version over that. Or factory reset and install the test version.

davidfor · 03-10-2014, 01:06 AM

Quote:

Originally Posted by rxmom03

I'm scared to touch it and mess it up again

But at least I know where to look now.

Yes, a very important rule is to never mess with a working system. But, it's a rule that a lot of people ignore. And some of us take great joy in ignoring.

tshering · 03-10-2014, 05:22 AM

Quote:

Originally Posted by TechniSol

I strongly suspect that Kobo is depending on users installing incremental updates to get all their ducks in a row when they should be making sure all dependencies are present in each firmware since there is no guarantee of what firmware users started at and apparently not a very good mechanism in place to force necessary intermediate upgrades.(Wow, that's a long sentence...)

After playing around a little with the update request, I am rather inclined to think that this is not the case. For instance, when you upgrade a Glo (Kobo as affiliation) from 3.1.1, Kobo delivers directly the link to the 3.2.0 file. And the same happens, when you upgrade from 2.6.1. Having to go through the upgrade twice might maybe related to a broken download.

TechniSol · 03-11-2014, 12:21 AM

Well, I may be wrong, I have no proof, but after the first firmware download it installed fine, started up fine, and then displayed what appeared to be a different but similar downloading firmware screen... If you're so sure of your positions Gentlemen, why are several, at least, users having what appears to be the same issue with the line missing from the configuration file? The odds against multiple users having the exact same corruption while everything else works are astronomical. Perhaps not everyone's device updates the same as others? The segmented availability of updates points to the possibility of differing delivery paths and mechanisms...

We all do a lot of guessing around here, and I could be completely wrong, but sometimes when you're trying to proceed by fitting insufficient data to a conundrum that is a risk you might take... No offense intended, but considering some of the things we've seen from Kobo, it would not surprise me if they occasionally "assumed" certain things and that's why certain things get left out depending on the upgrade path. This unit is a refurbed unit, I have no idea where it was originally sold, but do recall there was an issue a number of versions back where you folks in Aus required a double upgrade to get a certain version to work correctly. There are regional differences.

taming · 03-11-2014, 08:17 AM

Just out of curiosity, have folks who experienced the missing sort function done any customization/hacking on your devices?

sharphamster · 03-11-2014, 12:51 PM

Myself, I had not done any tweaks. I had an additional issue with the upgrade, but that seems to be hardware (screen) related.

TechniSol · 03-11-2014, 01:52 PM

I had the two finger touch lighting control hack installed, and the night mode hack, both of which worked flawlessly prior to the 3.20 firmware upgrade. 3.20 broke touch input because of the modification made with the two finger touch lighting control hack and my not knowing it had to be uninstalled prior to 3.20 being installed.

If nothing else, this alone makes the point that Kobo firmware updates do not necessarily include all components required, or the touch input would have worked after 3.20 was installed as the required code would have replaced Giorgio's modification.

I think that effectively makes the point I was trying to make above.

PeterT · 03-11-2014, 02:12 PM

Actually no.... Remember if the mod installs additional files, for instance init scripts, these would only be removed if the Kobo installation totally wiped out the entire contents of that directory, rather than just replacing the files they knew they had crated in the first place.

TechniSol · 03-11-2014, 10:04 PM

Well, it still doesn't explain how the line was missing from the conf file unless Kobo only wrote the line or replaced the file in some firmware versions... not the ones it updated to after the factory reset, obviously.

03-09-2014, 10:36 PM	#20
TechniSol GranPohbah-Fezzes r cool! Posts: 1,056 Karma: 3151024 Join Date: Jul 2010 Device: Nook STRs, Kobo Touch, Kobo Glo	I had the same problem when I upgraded to 3.20 on my Glo. I had the issue with the two finger lighting control hack, did a factory reset with the light button on boot, went through downloading/upgrading firmware twice through WiFi on the Kobo and later saw there was no way to sort the collections list, but individual collections had sort options. I followed David's advice above to add the line to the conf file. I expect that the two step firmware upgrade had something to do with the line failing to be added to the file. Not sure what version the first downloaded firmware was, as on reboot it checked again for an update and downloaded it without an opportunity to see the settings page. I strongly suspect that Kobo is depending on users installing incremental updates to get all their ducks in a row when they should be making sure all dependencies are present in each firmware since there is no guarantee of what firmware users started at and apparently not a very good mechanism in place to force necessary intermediate upgrades.(Wow, that's a long sentence...) This sort of thing could explain why some people have battery drain issues, or other weird bugs that seem to be dependent on what order of firmware upgrade path has been taken. In short, it could explain a lot. Last edited by TechniSol; 03-09-2014 at 10:48 PM. Reason: damned auto-mistake got me again.

03-11-2014, 12:21 AM	#25
TechniSol GranPohbah-Fezzes r cool! Posts: 1,056 Karma: 3151024 Join Date: Jul 2010 Device: Nook STRs, Kobo Touch, Kobo Glo	Well, I may be wrong, I have no proof, but after the first firmware download it installed fine, started up fine, and then displayed what appeared to be a different but similar downloading firmware screen... If you're so sure of your positions Gentlemen, why are several, at least, users having what appears to be the same issue with the line missing from the configuration file? The odds against multiple users having the exact same corruption while everything else works are astronomical. Perhaps not everyone's device updates the same as others? The segmented availability of updates points to the possibility of differing delivery paths and mechanisms... We all do a lot of guessing around here, and I could be completely wrong, but sometimes when you're trying to proceed by fitting insufficient data to a conundrum that is a risk you might take... No offense intended, but considering some of the things we've seen from Kobo, it would not surprise me if they occasionally "assumed" certain things and that's why certain things get left out depending on the upgrade path. This unit is a refurbed unit, I have no idea where it was originally sold, but do recall there was an issue a number of versions back where you folks in Aus required a double upgrade to get a certain version to work correctly. There are regional differences. Last edited by TechniSol; 03-11-2014 at 12:30 AM.

03-11-2014, 01:52 PM	#28
TechniSol GranPohbah-Fezzes r cool! Posts: 1,056 Karma: 3151024 Join Date: Jul 2010 Device: Nook STRs, Kobo Touch, Kobo Glo	I had the two finger touch lighting control hack installed, and the night mode hack, both of which worked flawlessly prior to the 3.20 firmware upgrade. 3.20 broke touch input because of the modification made with the two finger touch lighting control hack and my not knowing it had to be uninstalled prior to 3.20 being installed. If nothing else, this alone makes the point that Kobo firmware updates do not necessarily include all components required, or the touch input would have worked after 3.20 was installed as the required code would have replaced Giorgio's modification. I think that effectively makes the point I was trying to make above. Last edited by TechniSol; 03-11-2014 at 01:54 PM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Aura HD Kobo Glo/Aura/Aura HD future firmware feature request thread	arspr	Kobo Reader	25	03-26-2015 05:19 AM
Dymo tape fix for eBay Kobo Aura and Aura HD covers	RobertJSawyer	Kobo Reader	2	02-10-2014 10:34 AM
Kobo Aura cannot connect to internet	rainmark	Kobo Reader	2	12-21-2013 11:15 AM
KOBO Aura can no longer connect to the internet	Josieb1	Kobo Reader	3	12-20-2013 01:16 PM
Calibre won't connect to Kobo Aura HD	ophelia	Devices	1	11-09-2013 05:00 PM

03-09-2014, 09:29 PM	#19
davidfor Grand Sorcerer Posts: 24,905 Karma: 47303824 Join Date: Jul 2011 Location: Sydney, Australia Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos	Interesting. When I removed the line, the sort menu disappeared. But, I only needed to put one line in to get display it. I would expect that if you look again, there will only be one of these lines.

03-11-2014, 08:17 AM	#26
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	Just out of curiosity, have folks who experienced the missing sort function done any customization/hacking on your devices?

03-11-2014, 12:51 PM	#27
sharphamster Anathema Device Posts: 283 Karma: 257456 Join Date: Oct 2011 Device: Sony T3/350, Kobo AuraH20/Mini, Axim X50v	Myself, I had not done any tweaks. I had an additional issue with the upgrade, but that seems to be hardware (screen) related.

03-11-2014, 02:12 PM	#29
PeterT Grand Sorcerer Posts: 13,535 Karma: 78910202 Join Date: Nov 2007 Location: Toronto Device: Libra H2O, Libra Colour	Actually no.... Remember if the mod installs additional files, for instance init scripts, these would only be removed if the Kobo installation totally wiped out the entire contents of that directory, rather than just replacing the files they knew they had crated in the first place.

03-11-2014, 10:04 PM	#30
TechniSol GranPohbah-Fezzes r cool! Posts: 1,056 Karma: 3151024 Join Date: Jul 2010 Device: Nook STRs, Kobo Touch, Kobo Glo	Well, it still doesn't explain how the line was missing from the conf file unless Kobo only wrote the line or replaced the file in some firmware versions... not the ones it updated to after the factory reset, obviously.

Advert

Advert