Kindle 3.1 software for Kindle 2, 2i, & DX (under construction)

[pmul]

Originally Posted by twobob

Umm. well my standard 2.5.x DXG runs out in 1-2 days when 3g enabled. not sure how long you were getting before.

Good point. I installed the update after only owning the DXG (bought used) for a few days. If it's normal for a DXG, then that's fine. I only expected it to last longer because my K2 did (bit over a week).

Originally Posted by twobob

Assuming you have a decent amount of books on the device it could just be that for the wakeup time.

Only about 20 books on it, the strange bit is that it wakes up quickly if it's been asleep for a short time, and takes ages if it's been asleep for a few hours. The wake-up looks like this: flick the power button, screensaver screen stays for 10-15s, and then the screen comes to life, and the Kindle is then in whatever state I had left it in (in book/out of book/etc). The delay is independent of method used to get into sleep mode, power switch or screen saver timeout

Originally Posted by knc1

Does you device create a /var/log/dmesg file?
If so, compress and attach it to a post.

I don't seem to have usb network running, I will have to install it. Given that I have 3.3 from a US 3G Kindle installed, I should install the usb network hack for that, and not the one for the DXG?

[knc1]

Correct.
Software changes need to be for the software version that is being run now - not what it was shipped with way back whenever.

[pmul]

Hmmmm...
I copied update_usbnetwork_0.43.N_k3g_install.bin to the root of my DXG and the "Install Update" option in the settings menu is still grayed out?

[knc1]

Originally Posted by pmul

Hmmmm...
I copied update_usbnetwork_0.43.N_k3g_install.bin to the root of my DXG and the "Install Update" option in the settings menu is still grayed out?

No clue.
Perhaps my advice was wrong.
One of the JB authors is active at the moment, perhaps he will post here.

[NiLuJe]

@pmul: You need to use the one that matches the hardware device, not the software.

(The updater checks the device id. [@knc1: it also checks the software version, but that's not something that we use in most packages, we usually allow stuff to be installed on every software revision ever]).

[pmul]

Yes,that's it, the DXG version of USB network installs fine. After SSHing, I checked /var/log:

[root@kindle root]# cd /var
[root@kindle /var]# cd log
[root@kindle log]# ls
messages wpa_supplicant.wlan0.log wtmp
[root@kindle log]#

no dmesg file? Should I have one?

[knc1]

Originally Posted by pmul

Yes,that's it, the DXG version of USB network installs fine. After SSHing, I checked /var/log:

[root@kindle root]# cd /var
[root@kindle /var]# cd log
[root@kindle log]# ls
messages wpa_supplicant.wlan0.log wtmp
[root@kindle log]#

no dmesg file? Should I have one?

A person could hope, but I guess not in this case.

Anything that seems unusual in 'messages'?
Like things failing or being re-tried?

'messages' is about things **after** the system initialization completes, not as much help as a dmesg file would have been.

'dmesg' file is the kernel message file as it initializes, it is the most likely place to find the cause of a slow start-up.

[NiLuJe]

You can call dmesg to print the latest part of the kernel log, but it might not be complete enough. That leaves you with playing with amazon's showlog.

[pmul]

Hi, no retry types messages, the only fails relate to volume:
121007:201249 audioServer[5550]: I volume:set:vol = 7:Setting the volume
121007:201249 audioServer[5550]: E def:mo::Failed to set volume (No master output)
Just to be clear, the start up time from off->main menu is normal, the time from sleep->wake is long, but only of the Kindle has been asleep for a few hours.

[twobob]

does simply typing dmesg give you nothing too? I should go check this on mine.

I would say that the DX does not have a great start up speed overally, in fact if you were to simply file all of this under "slow processor" fairly certain you would be correct.

Just so you know.

[pmul]

Originally Posted by twobob

does simply typing dmesg give you nothing too? I should go check this on mine.

I would say that the DX does not have a great start up speed overally, in fact if you were to simply file all of this under "slow processor" fairly certain you would be correct.

Just so you know.

Hmmm..
Possible, but on your DX with original firmware do you experience such a variability in the wake-up times? Mine has two speeds, instant (flick-brief pause-main menu), and long (flick-wait 10-15s-main menu). Long is only when it's been asleep for several hours. I have seen others in this thread reporting similar wait times, that they did not have with the original firmware. And all this (in my case) without having added books, so it probably isn't indexing.
If the slowness is just a DX being a DX, then OK. However it looks a bit strange that the startup times are so variable, and even though I had the DX for only a few days before updating to 3.3, I don't remember this long wake-up ever happening, and I used my new toy quite a bit during those days, luxuriating in the huge screen.

[twobob]

hmm will ask an expert.

Okay so started in the way you suggest - with a power flick - been suspended all night.

6 seconds startup.

Allegedly 2 -3 is more normal. but we timed it. 6. there you go.

[pmul]

Originally Posted by twobob

does simply typing dmesg give you nothing too? I should go check this on mine.

Typing dmesg does indeed give me a log, which I have attached here, nothing suspicious looking though (at least at first glance).

[pmul]

Ok, 6 seconds is about half of my wake-up time. I'm sshd into the DX at the moment, I will let it sleep for a few hours, do a wake and see if I get something in messages, a fast wake-up looks like this:

121007:210225 mxc_keyb: I def:unlocked2:status=unlocked:
121007:210225 fiveway: I def:unlock2:status=unlocked:
121007:210225 powerd[2113]: I def:pbpress:time=1349636545.308:Power button pressed
121007:210225 powerd[2113]: I lipc:evts:name=outOfScreenSaver, origin=com.lab126.powerd, fparam=1:Event sent
121007:210225 powerd[2113]: I def:statech:prev=SCREEN SAVER, next=ACTIVE:State change: SCREEN SAVER -> ACTIVE
121007:210225 powerd[2113]: I def:acc::Turn acc port on
121007:210225 powerd[2113]: E def:usbfs::Failed to open sys entry for USB FS ONLINE
121007:210225 accelerometer: I def:unlock::status=unlocked
121007:210225 cvm[3214]: I LipcService:EventArrived:source=com.lab126.powerd,name=outOfScreenSaver,arg0=1,arg1=<None>:
121007:210225 cvm[3214]: I PowerImpl:Information::handlePowerStateChangeEvent 3 1
121007:210225 cvm[3214]: I PrefixFreeVolume:ForceRescan:path=/mnt/us/documents:
121007:210225 cvm[3214]: I PrefixFreeVolume:ForceRescan:path=/opt/amazon/dict:
121007:210225 cvm[3214]: I PrefixFreeVolume:ForceRescan:path=/mnt/us/audible:
121007:210225 cvm[3214]: I PrefixFreeVolume:ForceRescan:path=/mnt/us/pictures:
121007:210225 cvm[3214]: I lipc:sip:prop=Volume, source=com.lab126.audio, value=7:Set int property
121007:210225 audioServer[2691]: I volume:set:vol = 7:Setting the volume
121007:210225 audioServer[2691]: E def:mo::Failed to set volume (No master output) 
121007:210225 cvm[3214]: I ScreenSaverBooklet:SSB_TRACE_USB_EXPORT:delayUSBExport=false:Password disabled
121007:210225 cvm[3214]: I ScreenSaverBooklet:IncrementSSImage::Incrementing the screen saver image index
121007:210225 cvm[3214]: I ScreenSaverBooklet:SwitchingToLastBooklet:lastBooklet=Home:Switching to last booklet
121007:210225 cvm[3214]: I BookletManager:SwitchingBooklets:from=ScreenSaverBooklet,to=Home:
121007:210226 cvm[3214]: W SystemBarImpl:SPIN:spinCount=0:count <=0 when stopSpinner() called
121007:210226 cvm[3214]: I MainView:Information::The device has WAN module so skip popping up the WiFi dialog.
121007:210228 cvm[3214]: I ContentCatalogImpl:ItemIterator:index=0,items=32,volumes=6,time=601:Catalog Iteration done
121007:210228 cvm[3214]: I RepositoryController:FETCHED CONTENT FROM CATALOG:numPeriodicals=2,numBooks=21,numArchivedItems=0:

[knc1]

Ah so. Is that your problem? That thing which is telling you that was 6 seconds:
210228 - 210225 = 0 hours, 0 minutes, 3 seconds.