yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Q&A, Help & Troubleshooting] Oh.Y.Not:
Are there anyone that use project management apps? What is a good one? I use SG Project Pro on my iPad, and pretty much this is the only app still tying me to my iPad. I'd love to find something similar on the Android side so I can truly be Apple free.

Basically, SG Project Pro has an intuitive interface, multiple ongoin projects, linking with MS Project, Very good reporting features, Gantt timeline, action list, batch email to all contractors, and risk management. If there is one like that for Android, I'd be ecstatic.

It doesn't need to be free. SG costs 40 bucks and is worth every penny and more. I don't mind spending the money for a well made one, keyword being well made, at least on par with SG Project Pro.
[Eee Pad Transformer Q&A, Help & Troubleshooting] funnycreature:
There are only two apps for that and only one allows editing. Android tablets suck when it comes to productivity. Search the market for Ms project. Can't link from tapatalk easily.

Sent with transforming Android technology.
[Eee Pad Transformer Q&A, Help & Troubleshooting] Richa Shaily:
Project Management App

Hi, I have used Project Planning Pro, available on iPad, Android and Windows and found it to be the only app that offers quality features at a minimal price ($20). The availability of this app on multiple platforms make it useful for users utilizing different platforms.

I am particularly fond of its ability to open MPP files in XML format within the app. Once the file is opened, it can be read or edited as per needs. It also allows import of files via Dropbox and mail.
[Desire Android Development] zyonee:
First of all, this is not my work. I only compiled it.

This is the usual ClockworkMod recovery, compiled from the CM7 sources with additions/modifications by j_r0dd. What I've done is only to compile it for the HTC Desire. For details, check out the link to j_r0dd's original thread for the Nexus S.

The credits go to Koush for the recovery itself and to j_r0dd for the modifications.

Original Nexus S thread with changelog here.

Download:

recovery-clockwork-5.0.2.7.111102-j_r0dd_mod-bravo.zip

(old) recovery-clockwork-5.0.2.7.111027-j_r0dd_mod-bravo.zip

Change log:

02-Nov-2011 (v5.0.2.7):

Merged 5.0.2.7 sources from CM7 repo again (some bugfixes)

Added option to wipe cache partition and dalvik cache at the same time

27-Oct-2011 (v5.0.2.7):

Merged 5.0.2.7 sources from CM7 repo (support for internal/external sdcard in backup/restore)

07-Oct-2011 (v5.0.2.6):

Rearranged wipe menu to avoid accidental factory wipes

Added "Reboot Bootloader"

Moved SD Card partitioning into a function of its own for both int/ext SD card

Merged 5.0.2.6 sources from CM7 repo

Added a menu choice of ext2/ext3/ext4 when partitioning SD card

25-Sep-2011 (v5.0.2.3):

Updated to j_r0dd's 5.0.2.3 version. Currently no changes made by myself.

17-Jun-2011 (v4.0.0.5):

Moved the "Wipe data/factory reset" to the bottom of the wipe menu to reduce the risk of accidental factory wipes.

19-Jun-2011 (v4.0.0.5):

Added "Reboot bootloader" option in advanced menu.

Added the ext4 modifications kindly supplied by roalex. Needs testing. Please make a proper nandroid backup with a proven working recovery version before trying this.

20-Jun-2011 (v4.0.0.5):

Added "Show log" in the advanced menu. This can help when reporting errors here. Use it. :)

21-Jun-2011 (v4.0.0.5.z110621):

Reverted and correctly added roalex's ext4 additions.

Modified recovery.fstab for ext4 support on some devices.

23-Jun-2011 (v4.0.0.5.z110623):

Removed NULL ext3 in recovery.fstab to hopefully get ext4 working properly.

06-Jul-2011 (v4.0.0.5.z110706):

Added "Advanced backup". Now you can backup/restore individual partitions.

Some other commits from other devs in github

Changed file limit from 10000 to 50000 in unyaffs. Should help when restoring large data partitions fails.

17-Jul-2011 (v4.0.1.0.110717):

Rebased completely on j_r0dd's 4.0.1.0 source and removed roalex's ext4 additions, as it wasn't working for everyone. Now trying with the original ext4 support which is included in CWM.

20-Jul-2011 (v4.0.1.4.110720):

Bug fixes

Disclaimer

These recoveries are compiled using the latest commits from koush, j_r0dd and others. That means they haven't been thoroughly tested and might have minor/major issues. I take no responsibility for any damages this thing might cause, but most things should work as intended. If you want something guaranteed to work, I think you should stick with one of the older versions.

Source code available here.
[Desire Android Development] suiller:
it works... thank you ;)
[Desire Android Development] zyonee:
Superb! I'll change the OP to confirmed then. :)
[Desire Android Development] sjknight413:
bit hesitant to flash this, had a few usb bricks from recent clockworks. reckon some people who have flashed it could nandroid backup then restore and check it all works?
[Desire Android Development] zyonee:
Well, like I said, I can't guarantee that it works, especially since I have no Desire to test it on. I've used j_r0dd's source which is based on Koush's source for the official CM7 3.2.0.0 ClockworkMod recovery. It might work, or it might not work. Testing it is up to each person.
[Desire Android Development] sjknight413:
dont get me wrong, i didnt mean any disrespect :) looks like you have done good work! but i have only had my desire 4 days and already had 2 usb bricks! will probably test in a couple of days
[Desire Android Development] zyonee:
Don't worry about it, I wasn't offended in any way. I'm wondering though if the USB bricks are caused by flashed (.img) recoveries. As I remember it, USB bricks were common with the earliest attempts to run recoveries by uploading the recovery binary to the phone's RAM while having to keep it plugged in to the computer.
[Desire Android Development] sjknight413:
well i know i got the usb bricks whilst restoring nandroids when my phone wasn't plugged in. that help in any way?
[Desire Android Development] zyonee:
Maybe your misc partition got overwritten with garbage. In my opinion, nandroid shouldn't touch this partition. The USB brick issue is usually caused by a corrupt misc partition.
[Desire Android Development] sjknight413:
yeah i dont really know why it does, its easily fixable by reflashing the mtd0.img file generated from your cid and rom version though, its just a massive nuisance!
[Desire Android Development] zyonee:
You should check your nandroid backup folder. If there's a misc.img or something like it, maybe you should move that file elsewhere. That way, nandroid shouldn't overwrite your misc (mtd0) partition. I'm only guessing that it does handle that partition.
[Desire Android Development] teorouge:
Is it wiping sd-ext correctly? "Official" 3.2.0.0 posted here some times ago restarted recovery upon sd-ext wipe.
[Desire Android Development] zyonee:
No idea, not using sd-ext in any of my phones.
[Desire Android Development] Jameswgm:
I'd like to know this too. Can anyone who's upgraded to this version of 3.2.0.0 let us know their findings?
[Desire Android Development] zyonee:
It'll probably behave the same way, seeing as this one only changes the menus, I think.
[Desire Android Development] zyonee:
Updated OP to version 4.0.0.0.
[Desire Android Development] teorouge:
Thanks, please see http://xdaforums.com/showpost.php?p=14598355&postcount=357 .

You should mod 3.1.0.1, no later CWM worked ok. ;)
[Desire Android Development] zyonee:
Yeah, I got that even on my Nexus S.. I'm just cloning & compiling. Got no idea how to downgrade to an earlier version. Limited programming skills. :o
[Desire Android Development] zyonee:
I fixed the SD card mounting bug. Please re-download 4.0.0.0.

Still buggy. Each time you leave a file list, you'll need to "adb shell umount /sdcard" from your computer. Looking into it.
[Desire Android Development] zyonee:
Added back the 3.2.0.0 version in the OP so you won't have the /sdcard mounting issue. Hopefully it can be resolved soon, so we can start using the 4.0.0.0 version. Sorry for the inconvenience. :)
[Desire Android Development] zeltron:
Desire_recovery-clockwork-4.0.0.5.z110706-j_r0dd_mod cannot restore his backup, I have also checksum md5 error on backup proced by itself.
[Desire Android Development] zeltron:
ClockworkMod Recovery v4.0.0.5.zyonee110621 is ok it can backup and restore without MD5 error.

Just the progress bar doesn't work
[Desire Android Development] horst0815:
i can confirm the md5 mismatch error on 110706 recovery. this doesn't work
[Desire Android Development] Towleeeie9613:
I rooted with AlphaRevX beta and it came with this recovery and it will boot into it, but I can't do anything with it at all. I'm currently trying 4EXT and hopefully that will work.
[Desire Android Development] Kanzar:
So looks like 110623 is the stable/almost 100% working version? Looking to update the CWM on my phone...
[Desire Android Development] ckhacks:
Doesn't restore sd-ext here....
[Desire Android Development] epivitor:
Which is the latest stable and 100% working version for both ext3 and ext4 ?
[Desire Android Development] zyonee:
Seems like none of my versions work 100%. I might go back to merely compiling j_r0dd's versions without any additions. It may break ext4, but it'll be the latest version and should work well with ext3. I haven't made up my mind yet.
[Desire Android Development] zyonee:
Ok, so here goes. I'm making a new attempt. Rebased everything on j_r0dd's current 4.0.1.0, but without roalex's ext4 additions. See original post.
[Desire Android Development] ptr_hamilton:
Just downloading it and gonna try with insertcoin on ext4 ;)

THX !!
[Desire Android Development] zyonee:
Make a backup using a working recovery first! No guarantees that mine will work as intended. Thanks for testing. :)
[Desire Android Development] ptr_hamilton:
For sure - already did. It's just backing up, new seems to be that every img gets it's own md5.. Will tell more later.

Thanks again!
[Desire Android Development] zyonee:
Maybe that came with "Advanced backup" and also affects the regular backup. I'm not sure how it will affect restore. Maybe you can try it later?

Anyway, there are ways to manually make a md5 file for the whole bunch of files if needed. It's not too complicated. ;)
[Desire Android Development] ptr_hamilton:
I'm sorry :( I could not restore the complete one. It says MD5 missmatch.

What happend - here the log:

1st it checks all the single md5 checksums and gives me a OK

2nd After that it trys to find the nandroid.md5 which was not in the backup folder.

So it creates md5 for single img files but none for the whole backup. But on restore it checks that one too.

I'll try to restore the single img to see it that would work...
[Desire Android Development] ptr_hamilton:
okay I had to create a nandroid.md5

even a single restore doesn't work without. Restoring the whole backup now..
[Desire Android Development] zyonee:
Looks like I'll have to revert that one then. :(
[Desire Android Development] ptr_hamilton:
right. it's not

but once I did all was fine. ext4 worked!

Even restoring a complete backup created with 2507 worked :)

Just a little more and if the nandroid.md5 comes automatically it should be all great!
[Desire Android Development] zyonee:
I'll see what I can do. Maybe I can fix it, but more likely, I'll need to revert the whole thing..

Edit 1: Too complicated for me. Reverting. Anyway, if we need to restore img files separately, we can still use full backups and hand-pick the partitions to be restored. Will recompile and reupload as soon as I can.

Edit 2: Whoever did download my 110717 build from few hours ago, please redownload. The "Advanced Backup" was screwing things up. It created individual md5 files for each partition and would mess up the restore process unless a single md5 file for all partitions was manually created. Because of this, I reverted that commit.
[Desire Android Development] theooo:
Thanx for your effort dude, i really appreciate it. Downloading 110717 build and will flash it soon :D
[Desire Android Development] ptr_hamilton:
Yeah! This one' s great

No problem restoring and backing up

Thank you very much! Finally a working recovery with ext4 support and nice Features without multiple yes no choices!

Awesome
[Desire Android Development] zyonee:
Really glad to hear it. That means the Nexus One and Wildfire versions should work as well, since they have the same setup of mtd partition tables. ;)
[Desire Android Development] theooo:
Hello zyonee, in 110717 build will it format my sd-ext to ext4 if i do full wipe? Because some ROM are not compatible with ext4 for now. :)
[Desire Android Development] zyonee:
I think it will, yes. If you have an SD card reader, you can try it. If it does format ext4 and you want to reformat it in ext3, you can use a GParted live cd on your computer to reformat the partition (without touching the FAT32 partition) back to ext3 if needed.
[Desire Android Development] theooo:
Okay, thanx dude, that's explain why i got stuck in splashscreen after full wipe (factory reset). My ext3 reformated to ext4 meanwhile there's no ext4 support in my current ROM :)
[Desire Android Development] zyonee:
New version in OP. Minor fixes.
[Desire Android Development] bubu.:
Is this the latest CLockwork Recovery? I'm using a desire with Gingerbread Redux Rom, is this the best recovery for me? (Currently I have 2.5.0.7 installed via unrevoke3) -> Can I simply install this as usual .zip-flash from the 2.5.0.7-recovery?

Are there any real new features or is it better to stick with the old (but always stable since having flashed it last year) 2.5.0.7 recovery?

I have S-ON (default)
[Desire Android Development] zyonee:
Almost newest. I'm in my vacation and can't make updates for another week. It should work just fine.
[Desire Android Development] bubu.:
Okay thanks, I bet the 'Desire_recovery-clockwork-4.0.0.5.z110706-j_r0dd_mod.zip' is the file to download? I'm just asking because the version number is the same for more of one of the files, but just the data in the filename differs

Edit: Tried to flash it like a usual rom or kernel from my old clockword 2.5.0.7 but after a recovery reboot, the recovery is still the same (2.5.0.7), nothing has changed
[Desire Android Development] AlxMAX:
That ZIP file is not an update. You must extract recovery-clockwork-4.0.1.4.110720-j_r0dd_mod-bravo.img and recovery-clockwork-4.0.1.4.110720-j_r0dd_mod-bravo.md5 from the archive, check if the IMG file is not corrupted with the help of the MD5 file and use fastboot to flash the recovery.
[Desire Android Development] bubu.:
And this is possible with S-ON also? Is there a good howto? Thanks!
[Desire Android Development] zyonee:
Search for unrevoked 3.14 on this forum. It'll do it for you. ;)
[Desire Android Development] bubu.:
I'll tried the latest unrevoke already but always got stuck at "running root...". I followed a howto: Installing HTC Sync and uninstalling it again, than modifying the driver for my phone etc... :( Is it perhaps because I didn't find the option to set the default usb cable connection to charge?
[Desire Android Development] TheBlueRaja:
Would it be possible to have some sort of pin lock in recovery?

Its a pretty big security hold having a recovery image, but if you had a pin lock on it this would be more secure.

Thanks
[Desire Android Development] Blissful Choreography:
Cool idea, but wouldn't someone who knows how to get into recovery usually be able to fastboot flash their own recovery, provided they the right cable...
[Desire Android Development] Blissful Choreography:
Actually, this guy's idea is the solution: http://xdaforums.com/showpost.php?p=16038457&postcount=5478

But it would probably mean bricking your phone if you lost the password.
[Desire Android Development] TheBlueRaja:
Yes, but the point is they would have to do a good bit of work to get to this stage, find the Android SDK, install it, work out what to do etc. Your average thief isn't going to have a clue.

At the moment with some custom ROM's you get an option to reboot right into recovery, even if you have a security screen on (Cyanogen is one), just by holding the power button and selecting reboot - recovery. Thats one of the first things you would do as a thief, then your right into recovery, wipe data / factory reset and bam - shiny new phone. Your almost guided through it and there's no security - at all - in your way.

I though you could store the pin on a file in the phone, if you forgot the pin you could adb it to get rid of it.

I'm not looking for fort knox here, im looking to make things difficult because at the moment its really easy.
[Desire Android Development] AlxMAX:
@TheBlueRaja: reading your messages on the CyanogenMod nightly thread and this one I wonder how difficult would it be to write a routine to ask for the PIN! You realise that one should write code to implement a virtual keyboard or a kind of pattern reader (read the data from the touch screen, compute the approximate location where the user has touched the screen, draw rectangles or images at specific locations on the screen etc). Would this recovery fit in 5 MB? Then, where would it store the PIN (remember, it might be changed periodically by the user)? :rolleyes:

Later edit: maybe a smarter boot loader to make fastboot ask for a PIN would do the trick? I mean, when you type fastboot flash ..., HBOOT tells fastboot to ask the user for a PIN, then fastboot provides the PIN to HBOOT and it decides if it flashes or not.
[Desire Android Development] jaavaa:
Bought a new SD card to my Desire. Well did a nandroidbackup with the old card, partitioned the new one, copied all the stuff to my new card and now trying to restore nandroid to get my sd-ext. Well, im using 4.0.0.5.zyonee110706 version and it says im having md5 mismatch. I have triplechecked the md5 with my pc while mounted in the phone and in the sdcardreader. All md5 are perfect match. Any way to solve this problem?

Edit: Cant even restore backups from my old sd card.. Flashing newer version..
[Desire Android Development] zyonee:
Why not try the 4.0.1.4 version instead? I think it'll work better. The older one had some bugs concerning the md5 sums.
[Desire Android Development] tanjinjack:
In fact, I am having issues with nandroid backup.

It won't finish backing up, stucking at backing up sd-ext. Have to pull out battery in the end.

Went back to check the files in the folder, all images are there but there is no md5 file.

Anyone having the same issue?
[Desire Android Development] zyonee:
Strange. Is anyone else having this issue?
[Desire Android Development] casca:
I have tested, and the only thing I can notice is that the progress bar won't move when doing big operations(like backing up an sd-ext with 700mb), but after a while it moves on to creating the md5.Try again and wait a litle bit longer
[Desire Android Development] zyonee:
That bug is in the official cm7 recovery source. ;)
[Desire Android Development] euqilobaid:
I have the same issue. Backup is stuck at "Backing up sd-ext..." doesn't go anywhere from there. Have to pull the battery :(

EDIT:

Also i installed 4.0.1.0.110717, than tried with 4.0.0.2, 3.2.0.0 and 4.0.0.5 - had the same problem. 4.0.0.2 was stuck at "Backing up sd-ext... app-private"

Reverted back to 2.5.0.7 which did the job without any errors.
[Desire Android Development] zyonee:
So we can assume that this issue is in the official cwm source then, I guess.
[Desire Android Development] Rageypeep:
it also seems to crash often if I wipe the sd-ext, it will just hang on "formatting /sd-ext", i have to pull the batt and try again, and keep trying until it works :(
[Desire Android Development] 2000impreza:
I just tested out the latest version of the recovery posted. I was able to backup the sd-ext without any issues. It looks like it's stuck but after waiting awhile it completed.
[Desire Android Development] nqk:
I'd like to know if these 3.x and 4.x CMW Recovery are supported by Rom Manager?
[Desire Android Development] casca:
same here, it looks stuck but we have to wait a bit longer and it finishes
[Desire Android Development] zyonee:
Once installed, I think so. Just let ROM Manager install its latest official version of cwm and then manually overwrite it with this custom version. I guess the commands passed from ROM Manager to the recovery should be compatible.
[Desire Android Development] flakz0r:
So anyone wants to compile the latest v5.x version? :)
[Desire Android Development] zyonee:
I'll see if I can somehow add j-r0dd's mods into the 5.0 source, but it's going to take a while, I guess. Don't have much time, but since j-r0dd's pretty much given up on this project, I guess I will. No idea when it can be ready, though.
[Desire Android Development] snapilica2003:
No need. The v5 is official you can find it here: http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.0.0-bravo.img

or

http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.0.0-bravo.zip
[Desire Android Development] zyonee:
But they don't have j_rodd's menu mods included, which this thread is all about. ;)
[Desire Android Development] johno168:
What are the mods exactly?
[Desire Android Development] zyonee:
You can use the link in the first post to j_r0dd's thread, where you can read his changelog. I merely ported it to other devices.
[Desire Android Development] sjknight413:
anybody have a changelog for v5? cant find one anywhere!
[Desire Android Development] zyonee:
I think it'll be avaliable on github once koush pushes the update to his repo. Until then, look for @koush and @clockworkmod on Twitter for some news.
[Desire Android Development] zyonee:
Updated original post. j_r0dd's 5.0.2.3 version is up. Please test.
[Desire Android Development] AlxMAX:
I have compared the j_r0dd's version with the CWM version and except for the menu rearrangements and the elimination of those multiple No-s in the confirmations, I haven't noticed any difference. Maybe the binaries? For the moment, I have tested only the installation of several zip files. There's something which caught my attention. In the show_advanced_menu function in extendedcommands.c, in the 2 cases of partitioning an internal or an external SD card, most of the code is the same. I have copied that code into a function and called that function with an index in a mount path table as parameter. If you think you can integrate the function into your recovery, just let me know.
[Desire Android Development] zyonee:
Well, I could take a look at it, but I can't promise anything. I'm more of a porter in this project, maybe making minor changes.
[Desire Android Development] jhannbernas:
can i just flash the zip file attached to this thread in my recovery directly to update my clockworkmod?
[Desire Android Development] zyonee:
No, you'll need to extract the .img file and flash with either fastboot, flash_image or unrevoked.
[Desire Android Development] AlxMAX:
The function in the attachment was added to extendedcommands.c, right before show_advanced_menu. Then, in show_advanced_menu, at case 4, you may replace the code up to the break instruction with partition_sd_card( 0 ); and at case 6 replace with partition_sd_card( 1 ); You may also consider adding a new case, Reboot to bootloader and use reboot_wrapper("bootloader"); to perform the task.
[Desire Android Development] zyonee:
Yep, bootloader was already added by me in the source when you posted, so the case numbers had changed as well. No matter, however, I incorporated your code and will let you test the compiled recovery once it's compiled. If it works, I'll put it in my github source. :)

Edit: Here it is:

Desire_recovery-clockwork-5.0.2.3.111001-j_r0dd_mod.zip

To anyone else who hasn't read the last couple of posts: What needs to be tested in this version is partitioning internal and external sdcard. Obviously, Desire doesn't have an internal one, but if the external partitioning works, one could guess that internal is ready for testing on LG Optimus 2X, and others.