SuperZaxxon v.54 Final has been released!

[danielm]

Since the update to v1.54, my Pandora doesn't sleep any more when I close the lid. I changed the lid-close option to "screen off" and back to "sleep", but that didn't help. I also noticed that a sleeping Pandora wakes up when the charger is connected, and sometimes (battery full?) it even switches on the screen with the lid closed.

Also, what's the difference between the apps "Update Pandora OS" and "SuperZaxxon 1.54 offline updater? Would both do the same thing (when connected to WiFi)? Is one better than the other (better meaning not breaking anything)?

 

[PokeParadox]

Since the update to v1.54, my Pandora doesn't sleep any more when I close the lid. I changed the lid-close option to "screen off" and back to "sleep", but that didn't help. I also noticed that a sleeping Pandora wakes up when the charger is connected, and sometimes (battery full?) it even switches on the screen with the lid closed.

Also, what's the difference between the apps "Update Pandora OS" and "SuperZaxxon 1.54 offline updater? Would both do the same thing (when connected to WiFi)? Is one better than the other (better meaning not breaking anything)?

The "Update Pandora OS" is "rolling" so at the time the "SuperZaxxon 1.54 offline updater" was released it would be exactly the same - but from then on tweaks and improvement in preparation for the next update are constantly available which may/may not fix/break things.

You can see the offline updator pnd as a "stable snapshot" and the update OS as bleeding edge.

 

[Monkfish]

With LED customisation options i'm still having problems: i can set new values for each LED and save them so they apply - the new values for LED brightness stay until the unit leaves low power mode (i have my unit go into low power mode when the lid is closed) once the lid is opened the LEDs reset to their default factory settings. I know i posted about this before but i havent had much in way of responses. Perhaps i'm the only person with this problem, using SZ 1.54 and did a full reflash the list time i installed the firmware (i always update this way). any thoughts, wisdom or advice would be greatly appreciated

 

[danielm]

Is there any way I can see what's going on? Something like LogCat on Android? The screen seems to turn itself on _during_ charging with the lid closed, not just when the battery is full. And it takes a looooong time to charge the battery when the Pandora is not sleeping and the display is eating power ...

 

[notaz]

There is "dmesg" command that might show some clues.

 

[danielm]

OK, I'll try out dmesg later...

At least the WiFi-reconnection bug (running apps cannot connect to internet after WiFi got disconnected and reconnected again) is fixed with the latest update. Thanks for that!

 

[danielm]

Alright, I finally tried out dmesg and I hope no one objects to me posting a dump. To me it looks like WiFi is waking up the Pandora sporadically. Also connecting the charger while the Pandora is sleeping is waking it up (don't know if that is intentional).

Here is the dmesg output with comments to events:

(I will try this with  WiFi deactivated during the weekend)

>>>> Start of the log (after normal use with WiFi on)

[119697.228607] wlan0: authenticate with 42:4a:03:aa:48:d4 (try 1)
[119697.230926] wlan0: authenticated
[119697.231018] wlan0: associate with 42:4a:03:aa:48:d4 (try 1)
[119697.233825] wlan0: RX AssocResp from 42:4a:03:aa:48:d4 (capab=0x431 status=0 aid=2)
[119697.233825] wlan0: associated
[119703.090850] wlan0: deauthenticated from 42:4a:03:aa:48:d4 (Reason: 6)
[119703.104187] cfg80211: Calling CRDA for country: NO
[119703.837860] wlan0: authenticate with 42:4a:03:aa:48:d4 (try 1)
[119703.839843] wlan0: authenticated
[119703.888061] wlan0: associate with 42:4a:03:aa:48:d4 (try 1)
[119703.893157] wlan0: RX AssocResp from 42:4a:03:aa:48:d4 (capab=0x431 status=0 aid=2)
[119703.893188] wlan0: associated
[119709.137756] wlan0: deauthenticated from 42:4a:03:aa:48:d4 (Reason: 6)
[119709.150848] cfg80211: Calling CRDA for country: NO
[119709.939331] wlan0: authenticate with 42:4a:03:aa:48:d4 (try 1)
[119709.941467] wlan0: authenticated
[119709.986297] wlan0: associate with 42:4a:03:aa:48:d4 (try 1)
[119709.990600] wlan0: RX AssocResp from 42:4a:03:aa:48:d4 (capab=0x431 status=0 aid=2)
[119709.990631] wlan0: associated
[119711.306793] wlan0: deauthenticating from 42:4a:03:aa:48:d4 by local choice (reason=3)
[119712.557403] wlan0: deauthenticating from 42:4a:03:aa:48:d4 by local choice (reason=3)
[119712.684967] wlan0: authenticate with 42:4a:03:aa:48:d4 (try 1)
[119712.688842] wlan0: authenticated
[119712.736236] wlan0: associate with 42:4a:03:aa:48:d4 (try 1)
[119712.745971] wlan0: RX AssocResp from 42:4a:03:aa:48:d4 (capab=0x431 status=0 aid=2)
[119712.746002] wlan0: associated

>>>> Here, I put the Pandora to sleep and connect the charger afterwards (which woke it up)

[119763.306823] wlan0: deauthenticating from 42:4a:03:aa:48:d4 by local choice (reason=3)
[119763.307891] cfg80211: Calling CRDA for country: NO
[119763.309295] wl1251: down
[119763.539276] wl1251: unloaded
[119763.604980] ehci-omap ehci-omap.0: remove, state 4
[119763.605010] usb usb1: USB disconnect, device number 1
[119763.625091] ehci-omap ehci-omap.0: USB bus 1 deregistered
[119764.856445] PM: Syncing filesystems ... done.
[119765.005584] Freezing user space processes ... (elapsed 0.01 seconds) done.
[119765.025512] Freezing remaining freezable tasks ... (elapsed 0.02 seconds) done.
[119765.049194] Suspending console(s) (use no_console_suspend to debug)
[119765.167022] PM: suspend of devices complete after 117.492 msecs
[119765.167419] PM: late suspend of devices complete after 0.366 msecs
[119778.185180] Successfully put all powerdomains to target state
[119778.185729] PM: early resume of devices complete after 0.427 msecs
[119779.483337] PM: resume of devices complete after 1297.515 msecs
[119779.483764] Restarting tasks ... done.
[119779.782501] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[119780.792755] ehci-omap ehci-omap.0: OMAP-EHCI Host Controller
[119780.793273] ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 1
[119780.797546] ehci-omap ehci-omap.0: irq 77, io mem 0x48064800
[119780.808593] ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00
[119780.808654] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[119780.808685] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[119780.808685] usb usb1: Product: OMAP-EHCI Host Controller
[119780.808685] usb usb1: Manufacturer: Linux 3.2.45 ehci_hcd
[119780.808685] usb usb1: SerialNumber: ehci-omap.0
[119780.809143] hub 1-0:1.0: USB hub found
[119780.809173] hub 1-0:1.0: 3 ports detected
[119781.137908] wl1251: using dedicated interrupt line
[119781.231964] ieee80211 phy6: Selected rate control algorithm 'pid'
[119781.241180] wl1251: loaded
[119781.241455] wl1251: initialized
[119782.254028] wl1251: 154 tx blocks at 0x3b788, 35 rx blocks at 0x3a780
[119782.254150] wl1251: firmware booted (Rev 6.0.4.235)
[119782.317443] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[119793.708587] wlan0: deauthenticating from 42:4a:03:aa:48:d4 by local choice (reason=3)
[119793.785156] wlan0: authenticate with 42:4a:03:aa:48:d4 (try 1)
[119793.787536] wlan0: authenticated
[119793.941558] wlan0: associate with 42:4a:03:aa:48:d4 (try 1)
[119793.945922] wlan0: RX AssocResp from 42:4a:03:aa:48:d4 (capab=0x431 status=0 aid=2)
[119793.945953] wlan0: associated
[119793.957763] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

>>>> Here, I sent the Pandora to sleep again without interacting with it afterwards (WiFi was on and the charger was connected, the Pandora woke up all by itself)

[119801.238647] wlan0: deauthenticating from 42:4a:03:aa:48:d4 by local choice (reason=3)
[119801.240386] cfg80211: Calling CRDA for country: NO
[119801.241912] wl1251: down
[119801.469665] wl1251: unloaded
[119801.636566] platform mpu.0: max OPP set to 1
[120702.574584] platform mpu.0: max OPP set to 3
[120703.035217] wl1251: using dedicated interrupt line
[120703.130401] ieee80211 phy7: Selected rate control algorithm 'pid'
[120703.144866] wl1251: loaded
[120703.145111] wl1251: initialized
[120704.144653] wl1251: 154 tx blocks at 0x3b788, 35 rx blocks at 0x3a780
[120704.144775] wl1251: firmware booted (Rev 6.0.4.235)
[120704.208099] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[120727.045227] wlan0: deauthenticating from 42:4a:03:aa:48:d4 by local choice (reason=3)
[120727.144775] wlan0: authenticate with 42:4a:03:aa:48:d4 (try 1)
[120727.161804] wlan0: authenticated
[120727.269622] wlan0: associate with 42:4a:03:aa:48:d4 (try 1)
[120727.272399] wlan0: RX AssocResp from 42:4a:03:aa:48:d4 (capab=0x431 status=0 aid=2)
[120727.272399] wlan0: associated
[120727.286102] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[120737.582061] wlan0: no IPv6 routers present

>>>> The lines above are the output after the Pandora woke up by itself (you can see from the time that it was sleeping for a while)

 

[danielm]

Now I tested with WiFi disabled, and my Pandora still wakes up and switches on the screen sometimes when the charger is connected :-(

 

[Franko]

Is there any way I can see what's going on? Something like LogCat on Android? The screen seems to turn itself on _during_ charging with the lid closed, not just when the battery is full. And it takes a looooong time to charge the battery when the Pandora is not sleeping and the display is eating power ...

I actually have noticed this "phenomenon" and I must say that it is a bit disconcerting when you see it.  It just doesn't surprise me anymore.  Sometimes I'll raise the lid and it's ON - and it's down to 12% of it's battery level and I swear that I shut the thing down properly.  It just wakes up sometimes or reboots when you've shut it down.  There can only be one explanation - our Pandoras are possessed.  The technical side of me suggests that there are more logical reasons..

 

[Franko]

Just tried it again - shutting down...and it constantly reboots.  It's NOT related to the mini usb, nor bluetooth or wifi.  It's strictly related to the battery being close to full or being full and being connected to the main power supply.  I've tried numerous deductive tests...and it's related to the power supply somehow.  Once I pull the plug out of the main power port in the back, and attempt a shut down of the device?  It actually shuts down.

I guess that the moral of the story is to NOT keep the device plugged into the main power supply all of the time, or when it's not in use for an extended period of time.  Just charge the battery for a while, but then unplug it if you actually want your Pandora to rest like a good Pandy should.

 

[danielm]

Just tried it again - shutting down...and it constantly reboots.  It's NOT related to the mini usb, nor bluetooth or wifi.  It's strictly related to the battery being close to full or being full and being connected to the main power supply.  I've tried numerous deductive tests...and it's related to the power supply somehow.  Once I pull the plug out of the main power port in the back, and attempt a shut down of the device?  It actually shuts down.


I guess that the moral of the story is to NOT keep the device plugged into the main power supply all of the time, or when it's not in use for an extended period of time.  Just charge the battery for a while, but then unplug it if you actually want your Pandora to rest like a good Pandy should.

I'm not entirely sure about this, but I think it reboots with the charger connected, because it can only charge when the Pandora is running. Would be nice to have something similar as Android, that can be charged while being off (by booting into a charge mode instead of the OS?).

Still, while in sleep mode, the Pandora should definitely not switch on and even have the screen on while the lid is closed ...

 

[Neelix]

There's nothing mysterious about it. If the charger is connected then the CPU has to be on to control the charging.  So if you are in suspend mode (where CPU is off) and you plug it in, it wakes up.  And if you power off while the charger is connected it automatically turns itself back on.

- Neelix

 

[danielm]

There's nothing mysterious about it. If the charger is connected then the CPU has to be on to control the charging.  So if you are in suspend mode (where CPU is off) and you plug it in, it wakes up.  And if you power off while the charger is connected it automatically turns itself back on.

- Neelix

According to the Wiki, charging also works in "low power mode" and it is even supposed to be the best and fastest way for charging (obviously). The Pandora waking up from the low power mode and switching on the screen is definitely not intended and it makes charging the battery a pain in the a** because most of the chargers juice will be sucked up by the Pandora instead of the battery.

 

[EvilDragon]

Low-Power mode is NOT suspend.

 

[danielm]

Great, now I am seriously confused. I am talking about "low power mode - power button pressed less than 3 seconds".

I have never seen "suspend" and I don't know what the difference between suspend and low power is (the Wiki mentions "On", "Display off", Low power" and "Off"!).

Fact is that my Pandora is acting weird since I accidentally upgraded the OS. And when I say "accidentally", I mean it! It is not clear that "Upgrade Pandora OS" will download and install experimental stuff. I had enough "experimental" with Android and I have a severe aversion against it. (Yes, that was a rant  )

 

[Neelix]

Huh? :huh:

From the confirmation dialogue box before you proceed with an upgrade using that tool:
 

This little tool helps you to keep your firmware OS up-to-date with the latest tweaks.

Please note that this is in TESTING state and
might break parts of your system with unstable packages!

Make sure your Pandora is connected to the internet and click the Upgrade-Button.

That looks pretty clear to me. You can cancel without proceeding at that point.


Originally there was no suspend mode, just the low power mode. Then with one of the OS upgrades the proper suspend mode was added. (I don't specifically remember which one, but it may have been when the new kernel and SuperZaxxon were introduced) Because of the limitations I mentioned in my last post however it was set up so that (by default) if the sleep mode it triggered it will suspend if possible to do so, and go into the original low power mode otherwise. (usually this means it goes into low power mode only if the charger is connected at the time when it is triggered)

I hope this clarifies things somewhat.

- Neelix

 

[Franko]

There's nothing mysterious about it. If the charger is connected then the CPU has to be on to control the charging.  So if you are in suspend mode (where CPU is off) and you plug it in, it wakes up.  And if you power off while the charger is connected it automatically turns itself back on.

- Neelix

Okay.  This makes sense....errr, well it at least explains what's happening in my case.  I have to say though, that it's a bit puzzling the first few times you see it happen...  It's late and you just need to go to sleep, so that you'll be functional at work in a couple of hours, and so does your Pandy, or so you think.  You attempt to shut down the unit and it constantly reboots...why won't you go to sleep, Pandy?  Okay, one more beer...then it's off to bed...


At least I know now that my Pandora isn't possesed (or drunk) - it's just still getting refreshment via it's main power plug as well.  B)

 

[laurent0977]

Hello


The 1,55 zaxon will be release next ?


Lolo

 

[Linux-SWAT]

Probably after a big change.

 

[laurent0977]

Ok


Thanks