yashsingh1/xdaforums huggingface dataset:
[HD2 General] elojo_8:
lock my "info 8" report with mtty i have the Sleep of death problem

in the lastest lines see this

i have another tilt 2 and it have a bad block but not says nothing about of partitions

BLOCK 1228 (0x4CC) is bad block

BLOCK 3202 (0xC82) is bad block

Partition[0], type=0x20, start=0x2, total=0x63E

Partition[1], type=0x23, start=0x640, total=0x980

Partition[2], type=0x25, start=0xFC0, total=0x1A880

Partition[3], type=0x4, start=0x1B840, total=0x1F780

Cmd>info 8

--- 2K bytes sector version ---

DEVICE NAME=samsung_kby00n00hm

DEVICE ID=0xBC

DEVICE MAKER ID=0xEC

PAGE SIZE=0x800

TOTAL PAGE SIZE=0x840

BLOCK COUNT=0x1000

BLOCK PAGE=0x40

Checking block information

BLOCK 0 (0x0) is reversed block

BLOCK 1 (0x1) is reversed block

BLOCK 2 (0x2) is reversed block

BLOCK 3 (0x3) is reversed block

BLOCK 4 (0x4) is reversed block

BLOCK 5 (0x5) is reversed block

BLOCK 7 (0x7) is reversed block

BLOCK 9 (0x9) is reversed block

BLOCK 10 (0xA) is reversed block

BLOCK 11 (0xB) is reversed block

BLOCK 12 (0xC) is reversed block

BLOCK 13 (0xD) is reversed block

BLOCK 14 (0xE) is reversed block

BLOCK 15 (0xF) is reversed block

BLOCK 16 (0x10) is reversed block

BLOCK 17 (0x11) is reversed block

BLOCK 18 (0x12) is reversed block

BLOCK 19 (0x13) is reversed block

BLOCK 20 (0x14) is reversed block

BLOCK 21 (0x15) is reversed block

BLOCK 22 (0x16) is reversed block

BLOCK 23 (0x17) is reversed block

BLOCK 24 (0x18) is reversed block

BLOCK 26 (0x1A) is reversed block

BLOCK 27 (0x1B) is reversed block

BLOCK 32 (0x20) is reversed block

BLOCK 1228 (0x4CC) is bad block

BLOCK 3202 (0xC82) is bad block

Partition[0], type=0x20, start=0x2, total=0x63E

Partition[1], type=0x23, start=0x640, total=0x980

Partition[2], type=0x25, start=0xFC0, total=0x1A880

Partition[3], type=0x4, start=0x1B840, total=0x1F780

CE Total Length(with sector info) = 0xDCFC200

CE CheckSum Length(without sector info) = 0xDC20000

Cmd>

i
[HD2 General] lukedunk:
Like AngelDeath, I also have problems with restarts when trying to install apps from market (or also via titanium). These problems happen with all NANDroid builds (Froyo and Gingerbread), and persist despite task 29, task 2a, and after restoring stock WM from SD card. Using MTTY shows a few bad blocks, but not sure if they are related to this problem. Anybody with clues as to what's going on or how to fix? I'm not sure if I'm still under warranty, but regardless I'm not sure if I can duplicate the problems in WM to get the device replaced.
[HD2 General] AngelDeath:
Lukedunk,

Just an update, I just reverted to the EU version of my 1.5 Android rom which uses sd-ext and app2sd (was using Tmous version) and I no longer have the problems, but if I go back to Tmous version they re-surface again, so I do believe the bad block and their location does matter.

My bad blocks are in the data portion which I always use a 445cwr partition. I can almost bet if you go to a eu version which uses a sd-ext, I would almost bet your problem will go away.
[HD2 General] jianC:
This thread might be of some use: http://xdaforums.com/showthread.php?t=405740
[HD2 General] sagarjawaress:
Hello, i do not know how to check bad blocks but i am facing serious problem!

I am running NDT MIUI clk.(it works fine)

Also i am unsuccessful booting every other latest MIUI(bootloops).

Although i am successful booting latest NDT booting from clk, but when i try the same version from mag, it bootloops! I always flash ROMs so i know that i am using correct partition layouts & i do clean install. WP7 & WIN mo works fine! Some android ROMs which require ext also works fine!

Firstly i thought may be sd card is the problem but i formatted it and i am sure its fine!

Im worried that i will break my lovely HD2. I think all this is related to the bad blocks.

Please Help!

(I have EU HD2)
[HD2 General] Unconn:
Please do not cross post.

http://xdaforums.com/showthread.php?t=1189544&page=18
[HD2 General] naser6355:
hi friends

here is my info 8 log and it seems i have 5 BAD Block unfortunately.

when i install some of WP7 roms like xbmod after restart my touch screen stuck and the phone reboots by itself and this loop will go on...

in some android built after installation when its going to boot it reboots 3-4 times as well.

now i know the reason why :(

really isnt any way to correct them? :(

Cmd>info 8

--- 2K bytes sector version ---

DEVICE NAME=hynix_h8BES0UQ0MCP

DEVICE ID=0xBC

DEVICE MAKER ID=0xAD

PAGE SIZE=0x800

TOTAL PAGE SIZE=0x840

BLOCK COUNT=0x1000

BLOCK PAGE=0x40

Checking block information

BLOCK 0 (0x0) is reversed block

BLOCK 1 (0x1) is reversed block

BLOCK 2 (0x2) is reversed block

BLOCK 3 (0x3) is reversed block

BLOCK 8 (0x8) is reversed block

BLOCK 10 (0xA) is reversed block

BLOCK 11 (0xB) is reversed block

BLOCK 12 (0xC) is reversed block

BLOCK 13 (0xD) is reversed block

BLOCK 14 (0xE) is reversed block

BLOCK 15 (0xF) is reversed block

BLOCK 28 (0x1C) is reversed block

BLOCK 29 (0x1D) is reversed block

BLOCK 30 (0x1E) is reversed block

BLOCK 31 (0x1F) is reversed block

BLOCK 702 (0x2BE) is bad block

BLOCK 704 (0x2C0) is bad block

BLOCK 1121 (0x461) is bad block

BLOCK 1916 (0x77C) is bad block

BLOCK 3384 (0xD38) is bad block

Partition[0], type=0x20, start=0x2, total=0x63E

Partition[1], type=0x23, start=0x640, total=0xA00

Partition[2], type=0x25, start=0x1040, total=0x1DCC0

Partition[3], type=0x4, start=0x1ED00, total=0x18E80

CE Total Length(with sector info) = 0xF776800

CE CheckSum Length(without sector info) = 0xF680000

Cmd>
[HD2 General] Anden1986:
Bad blocks are unfortunatly not fixable 95% of the time. You can mark them as bad on a HDD so they dont interfere but on your phone I have no idea if you can :-( Only permanent solution is new mainboard with new NAND...

/Anders
[HD2 General] naser6355:
thanks for your answer but i know there is a solution by using JTAG boxes like OTR-Riff

but it is expensive and one like me cant do it by itself and it needs some hardwares

i'm just looking for a software based solution which i can do it my self using my usb cable and my pc :p
[HD2 General] Anden1986:
That is also correct :) But as you said yourself it isn't easy... As far as I have found out there is no solution og work-around based on software only :( I have had problems with reboots myself but solved the problem by filling up the memory with songs, videos and what not... Not pretty but it works for me :) Only alternative is a SD based Android build.

/Anders
[HD2 General] naser6355:
yes, i'm using winmo3.14 (i hate it :D ) and an ICS and a Froyo and at-last an Ubuntu on SD :D;)

afterall thats the good point of it :d u can have multiple builds plus most stable and bugless rom (default winmo) :p

( i'm kidding for sure , winmo 3.14 is most bugfull rom ever exists)
[HD2 General] deenseth:
How to check location of bad block?

Hi,

When I ran info 8 I got following bad blocks. How do I check if it is still have chance to install any ram.

I tried to install stock ram but got stuck at 8%.

Can someone to me how to partition nand and install EU version?

Cmd>info 8

--- 2K bytes sector version ---

DEVICE NAME=samsung_KBY00U00VM

DEVICE ID=0xB3

DEVICE MAKER ID=0xEC

PAGE SIZE=0x800

TOTAL PAGE SIZE=0x840

BLOCK COUNT=0x2000

BLOCK PAGE=0x40

Checking block information

BLOCK 132 (0x84) is bad block

BLOCK 304 (0x130) is bad block

BLOCK 2483 (0x9B3) is bad block

BLOCK 2541 (0x9ED) is bad block

BLOCK 2636 (0xA4C) is bad block

BLOCK 2689 (0xA81) is bad block

BLOCK 3488 (0xDA0) is bad block

BLOCK 4406 (0x1136) is bad block

BLOCK 4910 (0x132E) is bad block

BLOCK 5822 (0x16BE) is bad block

BLOCK 6268 (0x187C) is bad block

BLOCK 6903 (0x1AF7) is bad block

BLOCK 7366 (0x1CC6) is bad block

OS NOT FOUND !!!
[HD2 General] dazza9075:
NAND is relatively cheap because it contains bad blocks, there's not much you can do about that, as long as its flagged as bad which it will be before its sold then it wont use it. The problem is blocks that become bad afterwards. But don't try and fix labelled bad blocks, whilst it might work, it may also give you unexpected errors
[HD2 General] hengsheng120:
People have said that Samsung nand chips (tmous) tends to have more bad blocks then hynix (EU) dunno if that's just because of the storage size.
[HD2 General] iartty:
thankyou

thankyou for this information

after used my HD2 (EU ver.) with winmo6.5 for 2 years

just decided to flash into nand android

i've try many roms and flash and flash it from saturday till now:p

this is my info8

--- 2K bytes sector version ---

DEVICE NAME=hynix_h8BES0UQ0MCP

DEVICE ID=0xBC

DEVICE MAKER ID=0xAD

PAGE SIZE=0x800

TOTAL PAGE SIZE=0x840

BLOCK COUNT=0x1000

BLOCK PAGE=0x40

Checking block information

BLOCK 0 (0x0) is reversed block

BLOCK 1 (0x1) is reversed block

BLOCK 2 (0x2) is reversed block

BLOCK 3 (0x3) is reversed block

BLOCK 8 (0x8) is reversed block

BLOCK 2372 (0x944) is bad block

BLOCK 2707 (0xA93) is bad block

Partition[0], type=0x23, start=0x2, total=0xFE

Partition[1], type=0x0, start=0x0, total=0x0

Partition[2], type=0x0, start=0x0, total=0x0

Partition[3], type=0x0, start=0x0, total=0x0

CE Total Length(with sector info) = 0x80800

CE CheckSum Length(without sector info) = 0x80000

should worried with this 2 bad blocks or not ?

but in 24 hr. mine HD2 still work ok with Dorimanx-ROM-HIGH-END 3.1.9:)
[HD2 General] Gastozz:
How to fix this?

<5>[ 2.437072] Creating 6 MTD partitions on "msm_nand":

<5>[ 2.437103] 0x000004320000-0x000004420000 : "misc"

<5>[ 2.438720] 0x000004420000-0x000004860000 : "recovery"

<4>[ 2.442138] ###BAD BLOCK 571 04760000###

<5>[ 2.443481] 0x000004860000-0x000004d60000 : "boot"

<5>[ 2.449005] 0x000004d60000-0x000010160000 : "system"

<4>[ 2.453277] ###BAD BLOCK 652 05180000###

<4>[ 2.453948] ###BAD BLOCK 657 05220000###

<4>[ 2.471923] ###BAD BLOCK 801 06420000###

<4>[ 2.486511] ###BAD BLOCK 918 072C0000###

<4>[ 2.506347] ###BAD BLOCK 1077 086A0000###

<4>[ 2.520080] ###BAD BLOCK 1187 09460000###

<4>[ 2.559967] ###BAD BLOCK 1507 0BC60000###

<4>[ 2.564849] ###BAD BLOCK 1546 0C140000###

<4>[ 2.567138] ###BAD BLOCK 1564 0C380000###

<4>[ 2.576019] ###BAD BLOCK 1635 0CC60000###

<4>[ 2.590820] ###BAD BLOCK 1753 0DB20000###

<4>[ 2.616363] ###BAD BLOCK 1957 0F4A0000###

<4>[ 2.625000] ###BAD BLOCK 2026 0FD40000###

<4>[ 2.628631] ###BAD BLOCK 2055 100E0000###

<5>[ 2.629516] 0x000010160000-0x000010360000 : "cache"

<5>[ 2.632049] 0x000010360000-0x00001e800000 : "userdata"

<4>[ 2.640106] ###BAD BLOCK 2138 10B40000###

<4>[ 2.653442] ###BAD BLOCK 2245 118A0000###

<4>[ 2.672943] ###BAD BLOCK 2401 12C20000###

<4>[ 2.673217] ###BAD BLOCK 2403 12C60000###

<4>[ 2.673767] ###BAD BLOCK 2407 12CE0000###

<4>[ 2.700317] ###BAD BLOCK 2620 14780000###

<4>[ 2.712066] ###BAD BLOCK 2714 15340000###

<4>[ 2.716064] ###BAD BLOCK 2746 15740000###

<4>[ 2.745147] ###BAD BLOCK 2979 17460000###

<4>[ 2.766235] ###BAD BLOCK 3148 18980000###

<4>[ 2.779846] ###BAD BLOCK 3257 19720000###

<4>[ 2.780120] ###BAD BLOCK 3259 19760000###

<4>[ 2.837493] ###BAD BLOCK 3719 1D0E0000###

<4>[ 2.851959] ###BAD BLOCK 3835 1DF60000###

<6>[ 2.861083] PPP generic driver version 2.4.2

<6>[ 2.861328] PPP Deflate Compression module registered

<6>[ 2.861358] PPP BSD Compression module registered

<6>[ 2.862243] PPP MPPE Compression module registered

<6>[ 2.862274] NET: Registered protocol family 24

<6>[ 2.862365] PPPoL2TP kernel driver, V1.0

<6>[ 2.862365] SLIP: version 0.8.4-NET3.019-NEWTTY (dynamic channels, max=256).
[Galaxy S I9000 Q&A, Help & Troubleshooting] dadyal:
Why Samsung Don't Provide Android Updates Via Kies to Galaxy S Owner in Pakistan ? :mad:
[Galaxy S I9000 Q&A, Help & Troubleshooting] doomsdaycs:
i'm from india but we get updates.. but generally asian countries dont get updates as fast as the european ones, but hey u could always flash european ones via odin without any problems.. use the below link to download other stock firmwares..

www.samfirmware.com/WEBPROTECT-i9000.htm

Also in due time u will realise custom roms are much better than stock so i suggest u take a look at that too.. i have been using simply honey roms for months now, n i'm happy...:D

Dont forget to hit thanks!!:p
[Galaxy S I9000 Q&A, Help & Troubleshooting] dadyal:
Pakistani Galaxy S Comes with Arabic Rom with CSC : PAK

CSC : Pak Can't Be Upgraded with Kies
[General Questions and Answers] chadd74:
Ok hopefully since im a new member and this is my first post I am following protocol :)

I know their is a thread about this already but I cannot post on it.

My issue is with the new Android market that was released yesterday (7-12-11)

I cant see the movie tab. I know that rooted phones are not supposed to be able to watch movies but by changing the /system/xbin/su to mu it would work. However I still am unable to even see the movie tab after the file name was changed.

Thanks

HTC Aria CM 7.1 in USA
[Eee Pad Transformer General] Optimus-Prime:
I have had mine for about 9 days now, and it has dose the sleep of death thing twice already... i am running Prime 1.5 it seems that peoples screens dont work after some sleeps of death... just wondering on it.
[Eee Pad Transformer General] mikewong27:
I know that when I installed Prime 1.5, I get "Sleep of Death" every hour... I went back to stock and "Sleep of Death" went away... I'm not sure if this issue was fixed yet. I was told last week that it might be kernel related issue. But in the meantime, you can also try a different kernel and see if that fixes the problem... If not, try a different rom or even use Prime 1.4. Worst case is to go back to stock 3.1.

I'm still using stock rom right now and plan on using it for a while...
[Eee Pad Transformer General] Optimus-Prime:
ill have to give stock a test drive. i did see that when i changed roms i did get sleep of death.

we can just flash a CWM stock rom right?
[Eee Pad Transformer General] Drybonz:
I had this problem for the first time today. I'm on Prime 1.5.

I also had no sound when I got it back on. Had to reboot to get the sound back.

Any similar sound/sleep of death issues?

Any new information on a permanent fix for this?

Thanks.
[Eee Pad Transformer General] zephiK:
ASUS is working on a fix for this. It has something to do with 'power management.'

Just wait patiently while they release a OTA to fix this and then devs will also incorporate this fix within the ROM.
[Eee Pad Transformer General] worminater:
I had it nearly every time I left the tablet on for more than an hour without touching it. Upgraded to stock 3.1 and it hasn't happened since... (I manually flashed it; didn't wait for the OTA if that matters..)
[Eee Pad Transformer General] JoTeC:
My first TF suffered a SOD but I think it was a screen of death not sleep of death. I could never get it back so I replaced it at TigerDirect. My current solution? I pushed the TF off to the side of my desk and bought a Xoom... ;)
[Eee Pad Transformer General] darkonex:
I read Asus saying they were fixing hte dock draining issue, nothing about the sleep of death. I have never had this happen, though I'm on stock, and form the looks of it the peeps that are on custom roms have this issue so doubt they'd fix a non-stock problem.
[Eee Pad Transformer General] Drybonz:
I also only saw reference to the dock issue being fixed in an OTA. If you have a link to any information about the fix they are working on, it would be most appreciated.

Thanks.
[Eee Pad Transformer General] Optimus-Prime:
So i replaced everything with stock, and no sleep of death yet to happen. but i have been using it alot lately so ill let it chill for about the next 2 hours and see what happens.
[Eee Pad Transformer General] Drybonz:
Thanks... let me know if it works for you.
[Eee Pad Transformer General] bmszabo:
Bought my TF a week ago, with 3.01, NEVER has seen SOD; today -finally- OTA upgrade to 3.1 in the Netherlands; since upgrade SOD every time TF goes in sleep mode.. :(

Great upgrade, thanks ASUS! Any solution (except downgrading) around, plz?
[Eee Pad Transformer General] davidboyd:
Last nights OTA update fixed my deep sleep problems. This update apparently included a power management fix.
[Eee Pad Transformer General] mushypeas:
I've had my transformer for 2 months now. I had it stock, always updated OTA, until the NVflash/APX mode rooting method appeared and then I flashed PRIME! v1.4 and never had any SOD until recently when I upgraded to PRIME! v1.5. However, I did two other things around the time of the v1.5 upgrade that could equally have started the problem, namely; I started using a 16GB SDHC card in the keyboard dock and I also connected HDMI to my TV for the first time using a C-to-A adapter (this also does not work properly - uinstable image - intermittent digital interference flickers along the bottom of the screen).

I have since re-flashed PRIME! v1.5 using the APX/NVflash method and have stopped using the 16GB SDHC card in the dock and now the SOD has stopped happening..... HDMI is still an issue but that could be the cable and/or adapter.
[Eee Pad Transformer General] DArkwIng24:
Deep sleep , could it be tegra 2 issue?

the Folio 100, the toshiba thrive and Asus TF has this problem. all of them have Tegra 2. if i set the folio 100 to 30 minutes before sleep i can use it as long as i don't let it go over 30 min before i wake up the screen. if i close the screen (via the button) i don't get deep sleep problem before 30 min has gone. so there is some problem related to the CPU and memory going to deep sleep and can not get interupts from the button anymore
[Eee Pad Transformer General] ogg1e:
My SOD seems to only happen when it's attached to the keyboard dock. If I leave it undocked, it never get's the SOD. I'm on a replacement dock, and the original dock I had never gave me the SOD either.

I have the latest firmware installed and that didn't make a difference.
[Eee Pad Transformer General] deadman3000:
No dock. But had my first SOD with Prime 1.6 + Netformer and IO fix OC'd to 1.5
[Eee Pad Transformer General] stangoesagain:
My first post so I'm locked out of development forum with the relevant thread

http://xdaforums.com/showthread.php?t=1070343&highlight=waking+sleepsleep+of+death

Anyway, had my TF for only a couple of days, goes to SOD two-three times a day already. I didn't play around with 3.0 much before doing OTA to 3.1 but 3.1 and now 3.2 still put it to this unnatural sleep.

Actually, it didn't wake up after updating to 3.2 itself.

From reading that thread the best probable cause appears to be the voltage issue when CPU clock speed changes - when waking form sleep clock speed goes up but voltage doesn't or something like that, and if some processes are left running, like logging to a file, the system never really goes to sleep so no problem with waking but a problem with catching the culprit.

Someone also said that in 3.2, by design, there should be even more sudden clock speed increases so SOD problem might become even more frequent.

One more possible argument for the voltage theory - SOD doesn't happen when TF is charging, meaning that CPU management is not that strict. Someone reported that Juice Defender, the app to minimize power consumption/CPU load, actually caused SOD on his TF.

The actual cause of SOD is a failure to get the correct value for blacklight on waking so looking at the display closely with a flashlight one still can see it running, allegedly, and can even unlock it. If that happens and the system is otherwise responsive maybe there's a way to force the backlight on, maybe some widget that toggles autobrightness on something. I'm waiting for my next SOD to test this theory, sometimes the screen doesn't look black, simply not light enough.

Maybe all I've said is nonsense but I'm an unrooted noob, I'm allowed.
[Galaxy S I9000 Themes and Apps] francomile:
*

HI! THIS A NEXUS S AOSP THEME FOR DEODEXED XXJVP ROM SAMSUNG GALAXY S I9000!

WARNING:I ADVISE YOU ALL TO PERFORM A NANDROID BACKUP BEFORE FLASHING!

FLASH EVERYTHING AT YOUR OWN RISK, I TAKE NO RESPONSABILITIES FOR WHATEVER HAPPENS TO YOUR DEVICE!!

THIS THEME IS FOR AOSP VANILLA LOVERS, JUST AN ATTEMPT TO GET A CLOSER LOOK AND FEEL OF NEXUS S! iT WILL ONLY WORK ON DEODEXED XXJVP ROM

This theme is based on Ock's Gingerbread theme v.8, thank him too for his great work:)

This theme contains:

- Nexus S Stock Battery, with no %

- Tweaks to Expanded Status Bar

- Green/grey Nexus S network and wifi icons (depending on connectivity to Google services)

-SIP Activation

-3D FIX (no more blur icons on 3D launchers)

- New Pop-up toasts

-Stock Gingerbread Power Control widget.

- Screen-off animation

- Stock Nexus Yellow progress bars

- Extended Power Menu

- AOSP lockscreen

- Stock Yellow Overscroll glow

- GenieWidget, AOSP MMS, AOSP CLOCK.

-All stock apps themed to match Nexus S icons, wich include:

*Browser.apk

*Camera.apk

*ClockPackage.apk

*Contacts.apk

*DialerTabActivity.apk

*Email.apk

*Gallery3D.apk

*JobManager.apk

*Mms.apk

*MusicPlayer.apk

*MyFiles.apk

*SettingsProvider.apk

*Settings.apk

*TouchWizCalculator.apk

*TouchWizCalendar.apk

*VideoPlayer.apk

*VoiceRecorder.apk

*******************************************INSTALATION******************************************************

-put the Nexus_S_THEME_JVP_vx_CWM3.zip in your internal sdcard

-in CWM recovery, choose install zip from sdcard

-in next menu: choose zip from sdcard

- navigate in the menu with vol. buttons and choose the Nexus_S_THEME_JVP_vx_CWM3.zip

- when it asks you to confirm install , choose yes

...it will install package.

after finish, choose back, back, and reboot system now

And that´s it, simple!:D​

CHANGELOG:

V.3.0:

Added:

-SIP.VOIP activation

-3D fix (no more blur icons on 3D app launchers)

-GINGERBREAD LAUNCHER

-GenieWidget

- Stock AOSP CLOCK app (DeskClock.apk, in substituition of Samsung ClockPackage.apk)

-MMS AOSP app (substituting Mms from samsung)

V.2.0 :

-Corrected wrong Bluetooth icon in Power Control Widget, which was the sgs one instead of the Gingerbread Nexus s one.FULL GINGER NOW ;)

-CORRECTED A MISTAKE ON SETTINGS.APK IN MENU .

**********************************************DOWNLOADS************************************************

NEXUS_S_THEME_JVP_v3.0_CWM3

NEXUS_S_THEME_JVP_v2.0_CWM3.zip

RESTORE_TO_ORIGINAL_CLOCKPACKAGE_AND_MMS_CWM3

Want to have all this mods and lo's of other usefull stuff in a app?

Download from the market PERKA'S FILE STASH APP

CREDITS:

OCK for base theme

$OMATOR for extended power menu

DHIRO1602 for overscroll glow

RAKSAN (For 3D Fix)

PERKA (for all the support and some files that i´ve stolen from file stash :D )

SCREENSHOTS:​

IF YOU LIKE THIS THEME HIT MY THANKS BUTTON:)

##################################################################################################################################################################
[Galaxy S I9000 Themes and Apps] hackeron:
NICE! thank you for this..

A jvq version would be great though.
[Galaxy S I9000 Themes and Apps] francomile:
I think I shall not make a jvq version, because of the lag problems with deodexed stock browser.Think it's not worthed;)
[Galaxy S I9000 Themes and Apps] francomile:
I would apreciate some feedback guys, just to see if everytings ok, and if in custom rom it´s working ok :)
[Galaxy S I9000 Themes and Apps] whatmonster:
Just flashed this over simply galaxy 3.9 on my vibrant everything looks good so far.

Vibrant to you! using XDA Premium App
[Galaxy S I9000 Themes and Apps] francomile:
Glad to hear that ;)

Enviado desde mi GT-I9000 usando Tapatalk
[Galaxy S I9000 Themes and Apps] ZacAttack:
Does the lockscreen have any music controls by any chance?
[Galaxy S I9000 Themes and Apps] francomile:
No, but in most of music apps like winamp you can choose the option to have the controls screen after unlock.

Enviado desde mi GT-I9000 usando Tapatalk
[Galaxy S I9000 Themes and Apps] SimeonAS89:
This is awesome and something I've been looking for since I changed to Gingerbread!

Just out of pure curiosity, is it possible to add in the lockscreen mods and possibly an accurate battery as an alternate option?
[Galaxy S I9000 Themes and Apps] sirtorax:
NICE! thank you
[Galaxy S I9000 Themes and Apps] gaurav2009:
nice thnxx