Search results

@notaz: What do you say to my observation & my explanation attempt?

Upgrade summary: Slight improvement, but practically still unusable. In other words: Measure-able but not feel-able. Improvement: ping 8.8.8.8 avg: before 200-260ms, after 60-70ms. (powersaving ON, no other networking activities besides ping) But concerning download speed and interruptions...

^ Make sure you save the control configuration as global! Else its is per game, which is a feature rather than a bug.

@Stainy: If you search this very thread for "driver bug" you will find numerous reports and also one solution (removing .SUB file from rom set) which MAY help. UPDATE: Links should now work properly.

Real life: Almost unnoticeable, except if you consciously do the maths. Changing screen brightness just by one bit already has more noticeable effect.

Power consumption internal vs external WiFi:

FYI: If the dongle sits at the port with USB-hosting disabled it consumes about 2mA. (measured with sysinfo). Not much, but still something. Worth knowing.

Someone, who knows the bootup process, please investigate where the TZ loss happens in this process. Or how TZ are even supposed to work by design on the hw/sw-clock of the Pandora.

Thanks for that confirmation. So for now better use the USB OTG port for multiple input devices via a hub. Downsides: - Less stable cable connection: The cable connection gets 1 piece longer (heavier, more traction) on an anyhow smaller port (less friction). - Slightly more power consumption...

Sorry, if my terminology is not 100% correct. I nevertheless hope that the essence of my report is understood. I was referring to most input devices as USB1 devices, and most mass storage as USB2 devices.

But before upgrading anything into the firmware, the issue needs to be fully resolved first:  

Thanks for your answer! As your release is announced for the near future, I will not compile myself (thx for info nevertheless, maybe another time), but rather anticipate the release  :D

1) The -u argument kept the TZ properly between standby/wakeup. 2) Also tested long term periods of standby and low-power-mode without hwclock -s -u in op_power.sh, and no noteworthy timedrifts happened. (But maybe those only occur over long term, not proportionally over time, but in sudden...

USB consumption (measured by sysinfo, numbers were calculated from state differences)  mA title  46 USB host service   0 USB network service per se ("Start USB network on bootup")  40 USB OTG cable connected (Unplugging always put consumption to as before! Service seems to really run only on...

Works fine: USB OTG port <—1— OTGcable <—2— USB2hub <—3— USB1device With the bootup service "Start USB network on bootup" activated, I dis/re-connected numerous times (~10times) at each juncture (1, 2, 3), and the USB1device always worked fine.     Works hardly: USB host port <—1— USB2hub...

I guess this has to do with the recent update of Flyspray (file attachments haven't worked, then ED performed the update). 1) The attributes are missing (you cannot categorize/assign/… the bug) 2) Bug submission fails with this error message: Query {INSERT INTO `flyspray_tasks` ( task_id...

  UPDATE: This was the wrong quote, a study on the internal WiFi with/out powersaving. Will quote the correct one below.

Praise: New power breakdown plot — great! So satisfying to see if suggestions get implemented that well! Thanks _wb_! New as of which version? Must be quite new, noticed only recently.

1) Repeated that battery out/in test at medium charge, and again I had: 40% (1575 mAh) —> battery out, wait ~20 minutes, battery in —> 46% (1791 mAh). 2) Will do the treshhold-altering test on the weekend, when I get time for it.

I finished my RTC tests.   Learnings: The RTC is not ticking when the Pandora is without a battery. The RTC is ticking while the Pandora is in normal operation, low-power-mode, standby and while being off. The RTC accuracy seems to not differ significantly between these modes, it drifts about...