Currently only icon files are supported, I am working on adding the splash / Launch images for iOS as well.

Upload a square icon of preferably  512×512 or bigger and you will receive a zip file with the required images as seen in the below screenshot.

Keep in mind that each time you visit this page, all uploaded and generated files are removed. So this might be problematic if many try to run this script at the same time (which I don’t expect).

Todo:
Generate all required files according to the default directory layout as generated by cordova’s create script.

The script: http://arenddeboer.com/cordova/.

Script source: cordova_icon_gen_source.zip (please share any updates or improvements you make)

Here is the update to config.xml courtesy of  Corey Maass

<icon src=”cordova/cordova_128.png”/>

<icon src=”cordova/cordova_android_36.png” gap:platform=”android” gap:density=”ldpi”/>

<icon src=”cordova/cordova_android_48.png” gap:platform=”android” gap:density=”mdpi”/>

<icon src=”cordova/cordova_android_72.png” gap:platform=”android” gap:density=”hdpi”/>

<icon src=”cordova/cordova_android_96.png” gap:platform=”android” gap:density=”xhdpi”/>

<icon src=”cordova/cordova_bb_80.png” gap:platform=”blackberry”/>

<icon src=”cordova/cordova_bb_80.png” gap:platform=”blackberry” gap:state=”hover”/>

<icon src=”cordova/cordova_ios_57.png” gap:platform=”ios” width=”57″ height=”57″/>

<icon src=”cordova/cordova_ios_72.png” gap:platform=”ios” width=”72″ height=”72″/>

<icon src=”cordova/cordova_ios_114.png” gap:platform=”ios” width=”114″ height=”114″/>

<icon src=”cordova/cordova_ios_144.png” gap:platform=”ios” width=”144″ height=”144″/>

<icon src=”cordova/cordova_64.png” gap:platform=”webos”/>

<icon src=”cordova/cordova_48.png” gap:platform=”winphone”/>

<icon src=”cordova/cordova_173.png” gap:platform=”winphone” gap:role=”background”/>

<gap:splash src=”cordova/res/screen/android_ldpi_portrait.png.png” gap:platform=”android” gap:density=”ldpi”/>

<gap:splash src=”cordova/res/screen/android_mdpi_portrait.png” gap:platform=”android” gap:density=”mdpi”/>

<gap:splash src=”cordova/res/screen/android_hdpi_portrait.png” gap:platform=”android” gap:density=”hdpi”/>

<gap:splash src=”cordova/res/screen/android_xhdpi_portrait.png” gap:platform=”android” gap:density=”xhdpi”/>

<gap:splash src=”cordova/res/screen/blackberry_transparent_300.png” gap:platform=”blackberry”/>

<gap:splash src=”cordova/res/screen/iphone_portrait.png” gap:platform=”ios” width=”320″ height=”480″/>

<gap:splash src=”cordova/res/screen/iphone_retina_portrait.png” gap:platform=”ios” width=”640″ height=”960″/>

<gap:splash src=”cordova/res/screen/ipad_portrait.png” gap:platform=”ios” width=”768″ height=”1024″/>

<gap:splash src=”cordova/res/screen/ipad_landscape.png” gap:platform=”ios” width=”1024″ height=”768″/>

<gap:splash src=”cordova/res/screen/windows_phone_portrait.jpg” gap:platform=”winphone”/>

or in plain ascii:

cordova_128.png
cordova_16.png
cordova_24.png
cordova_256.png
cordova_32.png
cordova_48.png
cordova_512.png
cordova_64.png
cordova_android_36.png
cordova_android_48.png
cordova_android_72.png
cordova_android_96.png
cordova_bb_80.png
cordova_ios_114.png
cordova_ios_144.png
cordova_ios_57.png
cordova_ios_72.png
splash_default_ipad_landscape_1024_768.png
splash_default_ipad_landscape_2048_1496.png
splash_default_ipad_portrait_1536_2008.png
splash_default_ipad_portrait_768_1024.png
splash_default_iphone_320_480.png
splash_default_iphone_640_960.png

After installing Ubuntu 12.04 and creating a simple RAID 1 mirror everything looked great, until after a reboot. I was unable to assemble the array with an error message like the above. It turned out I had to remove the package mdraid and it magically started working again. Hope it helps someone.

Thanks to Jonik for the info.

Source:

• http://superuser.com/questions/101630/creating-a-raid1-partition-with-mdadm-on-ubuntu/102111#102111
• http://superuser.com/questions/102086/how-to-build-initrd-without-dmraid-driver-on-ubuntu-9-10/102098#102098

Updated March 11, 2012

This application enables WiFi Ad Hoc mode on supported Android devices.

WARNING – In a worst case scenario you may have to restore your device with a backup rom. If you are not ready to do so please don’t use this app.

Reported to give problems on:

• HP Touchpad running Cyanogen Mod 9 ICS
• HTC Tattoo, Android 2.3.7 CyanogenMod-Arco-Kalim 
• HTC Incredible S with 2.3.3 RU (Bootloop)
• Huawei U8500 (msm7225)
• NOOK Tablet – BNTV250 (Android 2.3.4)
• Droid Incredible 2 running TSM GingerBangSense “M” Version 4.5  (results in a  bootloop, requires rom restore)
• HP TouchPad  Running CM7 Alpha 3.5 (no more wifi at all, requires rom restore)
• LG Optimus One (new update hopefully changes this)
• GPAD M7206
• Samsung I9003 Galaxy SL

Report statistics:

Please keep in mind that these numbers are a rough estimate. I will try to filter out duplicate reports (users who send in reports multiple times from the same device)

Features:

• Enable WiFi Ad Hoc mode (and keep infrastructure)
• Restore original settings

Issues:

• No WiFi signal strength visible in taskbar
• There are reports where WiFi completely stopped working (until a factory/hard reset).

Requires:

• Root Access (Superuser)
• BusyBox (don’t forget to actually use the BusyBox wrapper App to download the BusyBox binary!)

Use at your own risk! Please create a rom backup before using this tool.

If you successfully enabled WiFi on your device, please press the “It Works” button to report it to me. I will add your device to the list of supported devices.

Market link: WiFi Ad Hoc enabler (app removed until I have time to update it properly)

Scan to open application link in the Android Market

If you don’t have access to Android Market please use the direct download link:
WifiAdHocEnabler.apk   (app removed until I have time to update it properly)

Credits

Szymon for creating the wpa_supplicant file that allows you to see Ad Hoc networks ( http://szym.net/2010/12/adhoc-wifi-in-android/)

RootTools, a library that allows easy root related tasks: http://code.google.com/p/roottools/

The future

It was fun working on this app, but it has proven to be difficult to make something that enables Ad Hoc on a wide spectrum of Android devices. Therefor I will no longer be updating the application and will remove the “report to developer” option. My next project:  running Linux native on my Galaxy Tab P7510.
Starting point will be this thread by poitee -> http://forum.xda-developers.com/showthread.php?t=1189251

Thanks for all the feedback.

Update: March 4, 2012

Version 1.8.3 is out.

Hopefully added the Asus Transformer Prime TF201 with ICS / Android 4 to the list of supported devices.
Commands are now executed prefixed with busybox, hope this helps some of the “grep not found”  errors.

This is after hiding all items:

Just go over to http://wordpress.org/extend/plugins/clean-admin-ui/ or search for it in your WordPress plugin section using the terms admin, menu, ui.

• Requires WordPress 2.8 or higher
• Added option to hide Media menu item.
• I am thinking of creating a localized version

Let me know if there are more options you would like to see.

view source link

Requirements:

Tools:

• Soldering iron + tin
• (optional) Multimeter
• (optional) Soldering clamp
• (optional) wire stripper

Parts:

• Parallel Strip Veroboard (€ 8,22) )
• USB-A Receptacle (optional, a direct usb cable with micro or mini usb is also possible)
• 5Volt Regulator LDO (Low Dropout) LM2940 (CT) ( € 1,31)
• Heatsink for LDO (optional) (€ 0,5)
• C1             2200uF   16v (€ 0,65)
• C4             .47uF      Tantalum bead (€ 0,22)
• C5             22uF       Tantalum bead (€ 0.43)
• Bridge Rectifier, 1.5A, 100V (€ 0,5)
• Heat-shrink tubing (optional)
• ABS Case / housing (optional) (€ 1.17)
• Cable Gland Locknut (optional) or: a Grommet:
• hub dynamo connector (€ 2,- ?)

Note that these prices are ex FAT and I ordered them in larger volumes, ymmv.

Poor man’s (ms-paint) diagram

Step 1: saw a piece out of the veroboard, approximately 17 x 40 mm (the board below is too long, approx 65 in length)

Step 2: Solder the two tantalum bead capacitors on the voltage regulator. Be careful to not overheat the components, polarity is essential. Long leg is positive.
Place the 22uF Capacitor on the right,  the .47 uF on the left. Negative polarity combined in the middle.

Step 3: prepare capacitor C1 with the heat-shrink tubing, bend the pins (long leg = positive) as seen in the photo. Keep the legs as long as possible for flexible placement of this component inside the ABS case.

Step 4: place the components on the veroboard:
Looking at the first picture below; the middle three parallel stripes on the board serve as the main electrical paths for the components. The stripe on the left corresponds with the positive side on the diagram.
- C1: the long leg (+) should be placed on the left of the three middle stripes. The short leg should go in the middle. (in reference to picture 1)
Picture 1:

The bridge rectifier output legs should be placed as follows: The + (as indicated on the component) should go on the left of the three middle strips.
The – (negative) output should go in the middle. The AC input legs can be placed on the outer stripes of the board. (left and right in reference to picture 1)

And finally solder the voltage regulator as well.

Before going any further, check to see if it’s working properly.
Prepare the cable that runs to the dynamo, and connect it on the input legs of the bridge rectifier. Polarity is of course of no concern as we are dealing with an alternating current. Connect the dynamo to this kit, swing the wheel and measure the output voltage on the + (Vout) and – leg of the output regulator.

We should measure around 5 Volts

If it doesn’t work, carefully check the polarity of the capacitors and other components.

We can now safely cut the remaining component legs form the veroboard, and bend C1 to fit inside the ABS case.

I connected the heat-sink using a blind rivet this is ideal as it does not need any additional space (especially height).

Before connecting the cables, drill a small hole for the Cable Gland Locknut, connect the Cable Gland Locknut and route the wires through it.

Next, connect the USB A receptacle or if you like a mini or micro USB cable directly to the voltage regulator output legs. Connect the dynamo cable to the bridge rectifier.

In order for this whole package to fit inside the box, I had to saw one of the corners from the veroboard.

When using the same ABS case as listed in the requirements section, be sure to cut the two screw holes at the bottom of the case for more room.

That’s pretty much it. I will seal the case of with a polymer resin, to make it water proof. Be sure to only do this after you are absolutely sure everything works.

Revision 2 with grommets

That’s it! Let me know if you take on the challenge to build one yourself, or if I need to explain anything in more detail.

The latest incarnation is a stripped down version of the original. I left out the input tuning C2, C3, R1 (see original post for the diagram) and replaced the 4 Schottky diodes with an integrated bridge rectifier. The Schottky diodes  are more efficient due to the lower forward voltage drop, but require more soldering and space.  This version now fits into a small ABS case. I hope to replace the fixed USB cable with a USB A receptacle (if it fits).

Have a look at http://www.arenddeboer.com/flashnap/ ViewSource is enabled for a peak inside.

You can use any username / password combo as long as it doesn’t exist yet.

update:
Due to a take-down notice from the BPI connecting with this client is currently not possible.

Update:
Server back online with filesharing disabled.

Visiting verisign.com you will see a one year Code Signing Certificate will set you back  US $ 499,-

According to Adobe’s Flash Builder documentation only Certificates from the big four CA’s are trusted:

“A developer can use any class-3, high-assurance certificate provided by any CA to sign an Adobe AIR application. However, only ChosenSecurity, GlobalSign, Thwarte, and VeriSign come pre-installed on most end user’s machines (Mac OS X or Windows) and are trusted by the operating systems.”

These companies ask an amazing amount of money for a certificate, luckily there are better alternatives. The one I got was available for $75,- a year. This of course raises the question whether this certificate will be accepted, but I did found a couple of blog posts that reassured me this shouldn’t be a problem.

Hop over to author.tucows.com, register for an account and you will be able to purchase a Comodo Certificate through tucows.
The process will take some time. You will have to email documents to proof  your business/person identity and they probably call you as well. After receiving the certificate and signing the AIR package I was able to install my signed software successfully on:

• Windows 7
• Windows Vista
• Windows XP
• Mac OS X (10.6).

Unfortunately Ubuntu Linux 10.04 fails to recognize/trust the certificate out of the box (thanks to Jaap for testing this)

Before:

After:

The problem

I have a 4 drive spanned RAID (raid0) volume where one of the drives mysteriously dropped from the volume, becoming a so called non-RAID member.  I was pretty sure I had not messed around with this now non-raid drive. Neither had I performed any write operations to this disk. This led me to the conclusion that somehow the software raid manager (Intel Storage Matrix) had decided the drive was no longer part of the volume, but the data must still be intact. Apparently the meta-data for each member used by the (software) RAID BIOS is located on each member drive. So if this meta-data could be restored, the entire volume could be restored. Armed with this knowledge I booted into the RAID BIOS, and removed the other 3 drives from the volume. This will give you an intimidating warning about losing all data, but at least with Intel RAID this only wipes the RAID meta-data from the drive. After  removing all drives, I recreated the exact same volume, in the exact same order (order is critical!)  Now after booting into Windows I was able to recover the partition with the excellent tool TestDisk which you can find here: http://www.cgsecurity.org.

Be sure to follow the manual. In my case the partition didn’t show up using the quick-search, but after the more thorough  “Deeper Search”.

Many thanks go to Christophe GRENIER, the developer of TestDrive and the post from  “adamsap” on forums.extremeoverclocking.com