in which cyclocross bikes are proposed

57cm, 58cm, 59cm, 60cm, 61cm

We're big bicycle fans here. Bikes are tough to beat in terms of urban transportation: they're reliable, emissions-free, take up very little parking space, and cost almost nothing to operate. Depending on your commute or the length of your errand, it's possible that a bicycle will get you where you're going faster than an automobile. And they're great for your health.

Vehicular cycling (also known as integrated cycling, integrated traffic cycling, cooperative cycling, the British method of cycling[1], and bicycle driving) is the practice of riding bicycles on roads in a manner that is in accordance with the principles for driving in traffic.

Alright with that out of the way let's get to the AOKP goodness for our precious Kindle Fire. I originally flashed build 32 that I found over at XDA. Although it was working quite well, I did notice a few things here and there that I felt needed some attention. I downloaded the AOKP source and got to work. I ended up squashing a few bugs and adding a few features in the process and I am now going to share that work with all of you.

Here is the AOKP changelog for build 34:
fixed mobile data toggle not updating for serious
fix navigation buttons for tablets
long press home options added to General Interface for phones that have hardware buttons
fix icon transparency being applied to right-side buttons (BT, etc)
updated NovaLauncher to 1.1.1
Add BT MAP Profile
fix font sizing in statusbar
fixed volume sliders not updating when volumes are linked
many fixes for ColorPicker in ROM Control
gradient showing properly
color picker should fit in all screens now
show color preview before opening dialog (in-line)
fixed sound playing when volume zoom is enabled in camera
last.fm AVRCP crash fixed
contact pictures now displaying properly in notifications when receiving new sms
many other things! check out all the commits at http://gerrit.sudose...atus:merged,n,z

Here's how I got Swype installed and working on my Kindle Fire: You will need to be rooted to do this.



1) Download the installer from your beta email or transfer it from one of your other devices (If you get an error saying "Sorry! This is not an Android Phone..." make sure your browser is set to mobile view and not desktop.)

https://beta.swype.com/android/get/

2) Log in

3) Select your Beta version

4) Install the Swype keyboard

5) Use Root Explorer and navigate to /data/apps and find the Swype apk

6) Move the Swype apk (not the installer) to /system/apps

7) Make sure permissions are rw- r-- r--

8) Reboot your device

9) Long press on a text field, select input? method, then Swype

10)When you use Swype it will constantly Force Close

11)Go back into system/app and press install on the swype apk file that you placed there

12)Then delete the same apk from system/app and reboot.


That's it, Swype should work after that without any FC issues. To minimize the keyboard swype from the Swype key to the backspace key.

amazon kindle fire 6.3 + root + some goodies - trying 2012-04-29

Emacs-based clojure environment on OSX (‘GNU Emacs 22.1.1’).

cyann 4 hours ago | link

This is what I set on my MBP (equipped with SSD):
sudo pmset -a hibernatemode 25 destroyfvkeyonstandby 1 sms 0
reply


droithomme 3 hours ago | link

Thanks, that is very useful, I was wondering why it didn't scrub it from memory when it sleeps.
Article discussing this setting and providing links to a free and open forensic library so people can actually test the FW memory search method themselves, yanking passwords straight off of their friends laptops as a fun party trick or what not: http://www.frameloss.org/2011/09/18/firewire-attacks-against...
reply


ryannielsen 3 hours ago | link

It's not scrubbed from memory on short term sleep so the OS can provide a more user friendly experience – rather than dropping you at the EFI login window when you wake from sleep, you'll be presented with the more capable and better looking OS sleep unlock window.
If the machine is asleep for "a while" then it will write out a sleep image file and power off RAM (and other hardware) to go into a deep sleep. Since the sleep image file is written to the FDE volume, you must first unlock the volume at EFI's login window to gain access to the sleep image and resume from sleep. That process takes far longer than waking from a warm OS, so it's not done by default. You can change sleep settings using pmset on the command line and force it to always destroy the FV keys on sleep, if security is more important that a quick wake from sleep.
reply


droithomme 2 hours ago | link

Yes, I switched the pmset settings after reading the article I linked to that discussed his settings and making the comment.
Benchmarking it shows that with all programs quit and hibernatemode at 25, it takes around 2 seconds to enter RAM-off-sleep and 8 seconds to awaken from it, rather than both happening instantly with RAM-on-sleep. It's not really all that slow, I wouldn't say it's all that noticeably longer. It's kind of an impressively fast memory dump and restore.
reply

from Quicklisp

setting up zsh to use mime logic for handling files

including clojure completions