188 replies to this topic

[targetbsp]

Screen flickers off and on for me.
Using an OLED Blade gen 1 TPT'd to gen 2

[shmizan]

working very nicely on my TFT gen 2 TPTed. no flickering touch and scrolling works as expected.
making a test backup as we speak, taking some time because it shows progress
ok it works excellent for me. quick backup and restore ticked makes backup fast!

very nice work snap.it !

Edited by shmizan, 17 August 2012 - 12:15 PM.

[Snap.IT]

targetbsp, on 17 August 2012 - 08:53 AM, said:

Screen flickers off and on for me.
Using an OLED Blade gen 1 TPT'd to gen 2

Try the new version, it seems some phones still have the problem with the lightsensor but it's turned off in the new version.

This should also help with brightness being set too low.

[Snap.IT]

Oh and everyone is very welcome, as usual when i stumble across something useful it's by mistake trying to make things work for my GEN3.

[rabaip]

Latest version works perfectly on my gen2. Thanks a lot!!

[TehStalker]

The only thing GEN3 is missing now is a proper TPT. That huge cache partition that sits there completely empty is ludicrous. Nice work on the recovery though!

[Snap.IT]

rabaip, on 17 August 2012 - 02:41 PM, said:

Latest version works perfectly on my gen2. Thanks a lot!!

I just updated it with a bit more brightness, visibility should be even better with the latest incarnation

[targetbsp]

Still no luck here.  I flashed the zip file version and if the light level changes the screen goes black then it redraws the UI.

[edit]
Actually the md5 differs from the recovery in the zip to the .img file. Wrong file in the zip?  I shall check...

[edit]
Yes, the .img download is fine (and very obviously brighter!)  The one in the zip is not.

Edited by targetbsp, 17 August 2012 - 03:10 PM.

[leemo92]

Double post

Edited by leemo92, 17 August 2012 - 03:12 PM.

[leemo92]

@targetbsp it was happening to me, its downloading the previous version instead, you have to copy and paste the link into the address bar to download the latest version. Just to let u know I use your cm7 kang

[targetbsp]

leemo92, on 17 August 2012 - 03:11 PM, said:

@targetbsp it was happening to me, its downloading the previous version instead, you have to copy and paste the link into the address bar to download the latest version. Just to let u know I use your cm7 kang

The zip I downloaded though had nosensor in the filename?  Suggesting it should have been the correct file?

[leemo92]

I'm not sure but I noticed the md5 was the same as the previous build and not the one I was attempting to download until I copied and pasted the link instead of clicking on it

[Snap.IT]

targetbsp, on 17 August 2012 - 03:13 PM, said:

The zip I downloaded though had nosensor in the filename?  Suggesting it should have been the correct file?

I messed up the links and the filenames, try it again.

[targetbsp]

Snap.IT, on 17 August 2012 - 03:23 PM, said:

I messed up the links and the filenames, try it again.

The MD5 of the zip matches the md5 in the first post.
But the md5 of the recovery inside that zip does nto match the md5 of the standalone recovery.ing file.
And the standalone recovery image file (when copied into the zip and flashed) works.  Whereas the zip as supplied doesn't?

is it just a caching issue for me then?  I've tried refreshing the page and copying the link as leemo suggests.

[Snap.IT]

targetbsp, on 17 August 2012 - 03:29 PM, said:

The MD5 of the zip matches the md5 in the first post.
But the md5 of the recovery inside that zip does nto match the md5 of the standalone recovery.ing file.
And the standalone recovery image file (when copied into the zip and flashed) works.  Whereas the zip as supplied doesn't?

is it just a caching issue for me then?  I've tried refreshing the page and copying the link as leemo suggests.

No, it's me that's being an idiot and having more than 20 terminal windows open while doing this.

I fixed it now, with the correct md5 and the correct file.

My apologies for this, my excuse is lack of sleep.

[targetbsp]

No worries. Been there and done that!  I'm just waiting to spread this to another (non-phone oriented) forum who would prefer the zip method and wanted to send them your links rather than mine so credit ends up where it's due.

I know it's somewhat in testing but it's a UK forum so they all have the same phone as me.

Edited by targetbsp, 17 August 2012 - 03:37 PM.

[Snap.IT]

targetbsp, on 17 August 2012 - 03:34 PM, said:

No worries. Been there and done that!  I'm just waiting to spread this to another (non-phone oriented) forum who would prefer the zip method and wanted to send them your links rather than mine so credit ends up where it's due.

If you get a chance, could you stop by the dual boot thread and take a look at my init.rc, now that this project is done it's the last one of three and it's driving me nuts.

And thank you. Don't forget to mention that it's KonstaT's kernel.

He's a wizard you know.

[targetbsp]

I hate to be the bearer of bad news, but whilst the MD5 of the zip has changed, the MD5 of the recovery.img in it hasn't...
It still seems to be the old one that's different from the standalone image, just zipped differently.

[leemo92]

+1

[Snap.IT]

targetbsp, on 17 August 2012 - 03:46 PM, said:

I hate to be the bearer of bad news, but whilst the MD5 of the zip has changed, the MD5 of the recovery.img in it hasn't...
It still seems to be the old one that's different from the standalone image, just zipped differently.

This has to be a drop box error because if i run md5sum in my dropbox folder i get that md5.

I'll delete it and reupload it to hopefully fix it.