188 replies to this topic

[emotty]

Snap.IT, on 26 August 2012 - 10:41 PM, said:

1. it's not on black on this version, the wallpaper and the brightness of the text as well as the larger font size should make it readable.
2. you're going to have to confirm any action, if you confirm it, it's not made by mistake, it's made because you didn't read what you just confirmed.

It's a pain in the arse to change most things because it will break the touch, that includes text colour and fonts, i only managed to get away with enlarging fonts because i could do that via the kernel interface and have it accepted, i can't do that with colour.

Sorry but it's going to stay this way until koush decides to change it.

1) its the white text with the blue background that is hard to read when *selected*

2) after selecting the option i didn't read the next bit,yes my fault for not reading to confirm that i didn't select the right option in the first place cos i misread it because i couldn't read it cos it was blue and white when i selected it ..


was just an idea ... you spent all the time making a great tool but didn't correct the mistake (imo) of the original ..

[Snap.IT]

emotty, on 28 August 2012 - 02:59 AM, said:

1) its the white text with the blue background that is hard to read when *selected*

2) after selecting the option i didn't read the next bit,yes my fault for not reading to confirm that i didn't select the right option in the first place cos i misread it because i couldn't read it cos it was blue and white when i selected it ..


was just an idea ... you spent all the time making a great tool but didn't correct the mistake (imo) of the original ..

Maybe on the next version, at the very least i'll lower the brightness to a more reasonable level since that in itself makes it hard to read, it's too bright as it is.

[targetbsp]

Snap.IT, on 28 August 2012 - 03:36 AM, said:

at the very least i'll lower the brightness to a more reasonable level since that in itself makes it hard to read, it's too bright as it is.

I approve of this.

[vNa5h]

Snap.IT, on 28 August 2012 - 03:36 AM, said:

Maybe on the next version, at the very least i'll lower the brightness to a more reasonable level since that in itself makes it hard to read, it's too bright as it is.

waiting for it..
the 6.0.1.2 is just too damn bright

[Snap.IT]

New version of 6.0.1.2 testing.

Lowered brightness (set to 100 out of 255) and tweaked performance:

Fastboot flashable: recovery-clockwork-6.0.1.2-blade-testing-20120830.img
MD5: 343b410308bb80eeaccb2058dbf5e34c

Recovery flashable: recovery-clockwork-6.0.1.2-blade-testing-20120830.zip
MD5: 86f484657f79512afb7a6e63f073bb2c

Edited by Snap.IT, 30 August 2012 - 03:27 PM.

[bhush]

working very nicely.brightness is perfect now.

[emotty]

looks better thanks

[sej7278]

still can't really read the white text on light blue background, but i guess the newer 6012 testing is slightly better than the first one.

[mitchde]

I used the 6.0.11 a few (3) times to backup and restore after full wipes using CM9, different CM10 and back.
ALWAYS 100% errorfree restores - including my /ext . Thats so great!
Many thanks to the dev for that new+valide+easy to use CWM.

Q: If i use the newer test 6.0.12 , can i restore 6.0.11 backups with that or would it be better to backup first with 6.012 if thare are some major (not only speed tweaks) changes in the way of backup/restore to 6.0.11?

[targetbsp]

CWM can restore backups from older versions.

[sej7278]

targetbsp, on 31 August 2012 - 10:35 AM, said:

CWM can restore backups from older versions.

although CWM 5020 can't restore backups from CWM 6012 it seems, it had problems with .android_secure when I tried it, which is annoying as that's what the TPT's include.

So when TPT'ing make sure to have CWM6 on your sdcard to flash from CWM5, then you can restore your CWM6 backup.

[Snap.IT]

sej7278, on 31 August 2012 - 10:48 AM, said:

although CWM 5020 can't restore backups from CWM 6012 it seems, it had problems with .android_secure when I tried it, which is annoying as that's what the TPT's include.

So when TPT'ing make sure to have CWM6 on your sdcard to flash from CWM5, then you can restore your CWM6 backup.

Or just replace the recovery.img in the tpt with the .img for this version.

[vNa5h]

the delay between menu pages is still significant

[arpit22x]

I have TPTed my phone with gen3-v2a with recovery 5.0.2.0........ After that when I am flashing touch recovery 6.0.1.1 via CWM recovery (from zip).....its going into the old recovery instead of new touch recovery after rebooting system.... why? Whats wrong with me?
Please answer.

After flashing the rom, was able to install.

Edited by arpit22x, 01 September 2012 - 06:33 AM.

[..Abel..]

Thanks For the Update with lesser brightness !!

[Snap.IT]

vNa5h, on 01 September 2012 - 05:32 AM, said:

the delay between menu pages is still significant

Strange thing is, i don't experience this at all. It's instantaneous on my device.

Can you plug it in and adb pull /tmp/recovery.log and attatch it to your post?

[Guilherme Haschel]

No delay between menus here on Brazilian Gen2. 6.0.1.1 Thanks Snap.IT!

[Snap.IT]

arpit22x, on 01 September 2012 - 06:03 AM, said:

I have TPTed my phone with gen3-v2a with recovery 5.0.2.0........ After that when I am flashing touch recovery 6.0.1.1 via CWM recovery (from zip).....its going into the old recovery instead of new touch recovery after rebooting system.... why? Whats wrong with me?
Please answer.

After flashing the rom, was able to install.

The TPT you're using puts recovery in the boot partition so that when it boots up it's booting to recovery, when you install 6.0.1.1 it installs into the recovery partition, if you reboot and hold down vol- after the flash of 6.0.1.1 you'll arrive in the 6.0.1.1 recovery but if you just let it boot it will boot whatever is in the boot partition (which, before you flash a ROM, will be 5.0.2.0).

This is usually covered on the instructions on the page where you download the TPT.

[bladebuddy]

First of all let me thank-you for bringing us this Snap.IT
However I am running into the same problem each time I use it.
MD5 sum matches download link and it flashed o.k over an older version of you're cwm recovery.
Each time I try to do a nandroid backup it keeps freezing at the same place " please see photo's.
My phone is a Gen1 tpt to Gen2 amold San Francisco.
Running SSRLS7.
Do you have any idea what's wrong I have deleted my old nandroid backups and the cwm folder but still at a loss as to what's wrong.
Any help appreciated.

Attached Files

•  uploadfromtaptalk1346773825705.jpg   141.44K   23 downloads

[bladebuddy]

Just spotted my mistake I seem to have a different version on to the the one on page 1, checked the sum of the wrong file, noticed my error and flashed the version I should of done in the fireplace and I still have the same problem.
Do you think flashing an older version of cwm the reflashing this will work sorry for the messup.