yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] oquinones:
You should still have your update.zip on your internal storage that has Clockwork in it. You have to reinstall packages and that will bring up Clockwork.
[Vibrant Android Development] coldblooded79:
Tried JIT on the deodexed stock rom..hung forever at Vibrant boot screen. Thanks for the effort though.
[Vibrant Android Development] s0niqu3:
You only see the stock recovery because clockwork is loaded into the ramdisk by the stock recovery, and thus cleared on every reboot, that's why there's an update.zip in the root of your internal sdcard at all times.

Just select "reinstall packages" that will load clockwork

cheers,

=)
[Vibrant Android Development] antonio91282:
i just did my nandroid and i soooo want to flash this but the only positive feedback was from a guy who might not actually even have the JIT installed. did this work for anyone at all?
[Vibrant Android Development] s0niqu3:
I'm also wondering if this is a deodexed rom issue, I'm going to restore an earlier stock nandroid backup, and try again.

cheers,

=)
[Vibrant Android Development] bahnburner:
Well, after restoring backups of the modified files and checking that it would boot I cleared caches in stock recovery and reinstalled your JIT update. It hung at the Vibrant screen again. DDMS reports the same thing as before. It just loops the waiting on SurfaceFlinger message still. I'd advise pulling your update link since no one has been able to get a successful boot after flashing your package. Thank you for your hard work, but it's honestly not ready for prime time.
[Vibrant Android Development] oquinones:
Tried to flash for the 2nd time and did what you said but still hangs at the Vibrant screen. Gonna restore my backup again and keep an eye on the thread to see what comes of this.

Thanks for your efforts though. ;)
[Vibrant Android Development] rexrbgh:
It's still stuck at the Vibrant screen after I select that. Is there any hope?
[Vibrant Android Development] ELFungi:
Yes there is hope. When you selected it, did the install mention ClockworkMod Recovery, installed, and then reboot on its own? If it did, try going back into recovery and see if Clockwork Recovery is there.
[Vibrant Android Development] the3dman:
Pull your battery and try again.
[Vibrant Android Development] rexrbgh:
No, it says that it has installed packages but, it mentions nothing of Clockwork. I keep rebooting into recovery and nothing changes.
[Vibrant Android Development] bahnburner:
You're going to need to adb push the clockwork recovery update.zip back to your internal sd card.
[Vibrant Android Development] the3dman:
Well I am not going to pull the files because someone may want to play or edit it more but I have put a warning in the OP.
[Vibrant Android Development] rexrbgh:
Ahahaha, great I don't mean to be a bug but, could you point towards how instructions on how to do so?
[Vibrant Android Development] bahnburner:
I don't think "Many" is the correct word. Aside from you, and the one person that immediately overwrote your package with Vibrant4, no one has successfully gotten your mod to boot. Might I suggest the word "All" as a proper replacement.
[Vibrant Android Development] bahnburner:
Let me get this straight. You decided to guinea pig an extremely experimental mod with ABSOLUTELY no feedback as to whether or not it works, yet you don't know how to use adb. I'm honestly astonished as your ridiculous ignorance.

I'm going to (probably incorrectly) assume you actually have adb installed.

Boot into stock recovery (this may work will the phone is looping on the vibrant screen as well)

adb push C:/****/update.zip /sdcard/ (replace **** with the location of the clockworkmod update)

That's it.

I assuming you're a windows user based on your sheer ignorance and fact that you expect everyone to hold your hand.
[Vibrant Android Development] rhcp011235:
hehehe.

So it seems this only works with stock setup? No davilk cacheh hacks? so it seems.

nice work though.
[Vibrant Android Development] rexrbgh:
Sorry, I know that I shouldn't have and we all make mistakes...
[Vibrant Android Development] bahnburner:
Atleast you admit it. Let me know if you need anymore help.
[Vibrant Android Development] ELFungi:
Not to be disrespectful in any way, but shouldn't JIT improve your linpack score by a lot more than that? How can you be sure that it was working at all?
[Vibrant Android Development] the3dman:
You would think... but from other people who had this running on other phones reported the same thing not much difference in linpack.
[Vibrant Android Development] jeremiah_mn:
Seriously, was this comment needed? :rolleyes:
[Vibrant Android Development] bahnburner:
Yes.

10char
[Vibrant Android Development] the3dman:
I have added another version to the OP could someone possible test this on a deodexed rom for me?
[Vibrant Android Development] bahnburner:
I'm downloading it now.
[Vibrant Android Development] jeremiah_mn:
Your comment implies that only non-ignorant people use linux/unix OS's... which is a pretty ignorant in itself. ;)
[Vibrant Android Development] bahnburner:
Actually no. My comment implies that ignorant people don't use linux/unix. There are plenty of non-ignorant people on windows as well.

All burbons are whiskeys, but not all whiskeys are burbons, basically.
[Vibrant Android Development] the3dman:
Thank You for testing this.
[Vibrant Android Development] angryPirate12:
using Vibrant4 ROM, i was able to install the 2nd release and boot past the Vibrant screen, get through the Galaxy S loading screen, and then i get the BSON (black screen of nothing).
[Vibrant Android Development] bahnburner:
Not a problem. I'd rather test it myself than see people begging for help if they get stuck in bootloops.

Same thing here. BSON right after the first run of the animated boot screen.
[Vibrant Android Development] the3dman:
Well it looks like this turned out to be a complete failure lol. Wasn't expecting that lol it worked the first time for me. Now I am trying hard to retrace the steps that got it working for me.
[Vibrant Android Development] gordon.mott:
Failed with first version - restoring from nandroid and will apply second version to see what happens.
[Vibrant Android Development] angryPirate12:
Can you tell us your exact setup and layout that it worked on, like ROM, Kernel, any tweaks(lag, gps, etc), use clockwork or stock recovery, did you install it using adb, busybox version, superuser version, anything that can help us to recreate your exact process.
[Vibrant Android Development] the3dman:
My phone is completely stock except for root and now this.

First I followed the guide here and it did not work:

http://xdaforums.com/showthread.php?t=659387

So searched for the files for the galaxy s and found them in a rom for the I9000

I extracted the needed files from the rom and made the first update.zip with them.

I then booted to the stock recovery and cleared the cache then booted to clockwork recovery and applied the update. After applying the update it automatically took me back to the stock recovery (not clockwork) and from there I cleared the cache again and rebooted the phone and after about 3min on the galaxy s logo it all booted up fine. Now it boots up quick. As far as I remember those were the exact steps I took.
[Vibrant Android Development] gordon.mott:
Well, flashed version 2, and galaxy s is flashing on the screen now. Keeping fingers crossed...
[Vibrant Android Development] angryPirate12:
thats odd, typically when you "install zip form SD" in clockwork, it installs and leaves you in clockwork, it doesn't reboot and bring you back to stock recovery
[Vibrant Android Development] the3dman:
I thought so too
[Vibrant Android Development] gordon.mott:
reboot started at 12:33. Still stuck on Samsung Galaxy S animation at 12:51.
[Vibrant Android Development] the3dman:
time to pull the battery lol.

www.xxthe3dmanxx.com
[Vibrant Android Development] ttabbal:
I haven't tried this yet, but for those running lag fixes, the recovery doesn't know about your cache, so it can't clear it. You need to do that yourself. How you do that depends on which lag fix you have. I did a dalvik wipe zip for the external partition hack, I'm not aware of one for the loopback version though.

So if this does require a dalvik wipe, and you don't do it (because recovery doesn't know how), it won't work.
[Vibrant Android Development] gordon.mott:
Gave it a second shot at 12:54. re-wiped cache to make sure I got it, this time also wiped the dalvik cache.
[Vibrant Android Development] zimphishmonger:
Would it work if you manually ran the script from /system/etc/init.d in recovery prior to running the wipe data and dalvik update.zip (had that lying around). would a bind mount work for that?
[Vibrant Android Development] ritalin:
Dude calm the hell down. I understand what your saying and all, but your just being a jerk. Everyone starts somewhere. Some of us require a hand and some of us dive in head first. Just because you dive in head first does not make you better then those that need a hand. Hell once this kid gets the hang of things he may end up being a damn ace at it and do some dev work of his own on some level.

Plus it took you what, maybe 2 minutes to type that out for him? Whats the big deal? He took a chance and tried something complicated, got in over his head and asked for help. Its a forum for an open source OS, helping is almost mandatory. You only put your hand on a hot stove once. He will either remember how to ADB push or not try something like this again. Helping him out doesn't hurt us though.

One more thing. This, "I assuming you're a windows user based on your sheer ignorance and fact that you expect everyone to hold your hand." makes you look like an ignorant ass. Its childish and has no place in this forum.:mad:
[Vibrant Android Development] ritalin:
Sorry but I know a good deal of people that use Linux and couldnt tech there way out of a paper bag if you put another OS in front of them. Being good at one OS DOES NOT make you special, it makes you normal. Its level of complication makes no difference.
[Vibrant Android Development] eugene373:
Windows 7 baby myself.. Linux for Android only :o
[Vibrant Android Development] angryPirate12:
the 1st generation loopback fix only moves data/dalvik-cache/system, thats what i use, i manually wiped the dalvik cache with root explorer installed both, and with both cache's wiped i'm still getting BSON on v2 and Vibrant screen on v1
[Vibrant Android Development] gordon.mott:
Fear not, my friends... I come bearing logcat.

http://pastebin.com/VSTjd9rp
[Vibrant Android Development] speedysilwady:
has anyone tried the jit files from the froyo galaxy tab system dump?
[Vibrant Android Development] the3dman:
Yep same issues.
[Vibrant Android Development] SamsungVibrant:
Can someone please detail the reason why the Hummingbird is not utilizing the huge CPU performance boost promised by the Dalvik JIT compiler, while Scorpion CPU's are?

Exactly what is holding Hummingbird back? I don't understand why Galaxy S phones with official Froyo 2.2, such as the international version, or the SGS Tablet that already have the official 2.2 are not gaining that huge CPU performance boost promised from the JIT compiler, while Scorpion CPU's are.

Thanks in advance for the detailed explanation!
[Vibrant Android Development] Trev420:
These custom roms and kernals and lagfixes (voodoo) make these phones quick as hell. Theres not one thing that lags or stutters on this phone. What do I need jit for?
[Vibrant Android Development] boimarc89:


srry for the flaming bruh but jus sayin....use the search bar 1st tho

yea lagfix is good enough for me too. Everything else is jus being envious of the nexus 1's froyo. I have a phone w/ a 4 in screen w/ a beautiful screen and 512mb of ram. Thats y i got it bcuz my mytouch always ran outa ram even using cm6 back in july.
[Vibrant Android Development] Trev420:
Remember we are all here because we love our phones and we love to talk about them with each other. I could easily find repair guides for my civic on google but id much rather ask my brother and dad for advice because they are knowledgeable and I enjoy the conversation and the feeling of getting help from then instead of some random google search.
[Vibrant Android Development] boimarc89:
true..i love talkin about android w/ my android nerd brothers in here. i was like that too but back in the Mt3G forum, no1 answered questions for me since i was new at root so i had to google everything and figure it out on my own...even while damn near bricking my fone foreal..not a soft brick. they should implement a irc chat on here. that would b cool. real time answers and convo like the cm site. most of that site revolves around the N1
[Vibrant Android Development] Trev420:
Chat would be cool.
[Vibrant Android Development] SamsungVibrant:
I must say, I did search this forum and Google after the flame, I still didn't find a detailed technical answer as to why Dalvik JIT doesn't give the Hummingbird the huge CPU performance gain, while the Scorpions do.
[Vibrant Android Development] anomalous3:
My assumption is that a LOT of the Codeaurora and ARM NEON optimizations haven't made their way into dalvik vm for our phones yet, and I don't think the kernel is even that far optimized for our devices (So far my kernel building attempts have only been successful when I compile for generic Arm v7, not for the specific chip that comes with our phones, the the S5PC110); Remember, when JIT first came out for the original Droid it boosted scores, but not all that much. When people were running prereleased JIT for the Nexus ones, it also boosted scores, but not anywhere near the ridiculous extent it does now. Now even the original Droid is seeing HUGE performance gains. The Nexus, being as open a platform as you can get, has had optimizations added early and often. I suspect that once our phones go through a few revisions of CM6, we'll see similar performance gains, though there's no telling if they'll be quite as large.
[Vibrant Android Development] Relikk356:
I was under the impression that the Humming bird didn't have the NEON instruction set, as that's an optional set for ARM7 cpu's. We really need a new benchmark program that takes in account the GPU. Our phones GPU is almost 5 times faster then 90 percent of what's available.

Here's some discussions.

http://www.greenecomputing.com/2010/09/

" They've done studies, you know. 60% of the time it works, every time. "
[Vibrant Android Development] android53:
Iirc neon is what runs our hardware video support
[Vibrant Android Development] Relikk356:
Sorry, you're right. There's a newer blog, the links found on my previous post. I read this back in September before the rebuttal.
[Vibrant Android Development] iTylerA:
We all have gmail accounts... Maybe a google talk network would be good.

Sent from my Samsung Vibrant running Froyo. Please excuse my Swype.
[Vibrant Android Development] SamsungVibrant:
JIT discussion was good, why was thread closed?
[Vibrant Android Development] the3dman:
Mainly because I kept getting PM's about someones phone being messed up after flashing the files in the OP, even though it clearly stated that the flash did not work and was just a alpha test. So I ended up deleting the files and removing the info on it. I could have renamed the thread for JIT discussion but then it would not really be "development" so I ended up putting it up for removal. Sorry for the inconvience.
[Desire General] 4ftermath:
Say I'm using T-Mod R5b (LeeDroid 1.8) at the moment with a 512MB EXT3 partition. Now that I want to use the regular A2SD, how do I format my 2GB mSD so that I get back the original 1.83GB space? In other words, how do I remove the EXT3 partition?

Thanks
[EVO 4G Q&A, Help & Troubleshooting] genius764:
Which have you guys found to be the most stable? By this I mean, which has wifi tether working and themed without too many issues? Just as a note I had been using Ava-v5 but there was no wifi and some of the widgets were going crazy. Any input would be greatly appreciated. Thanks in advance.
[EVO 4G Q&A, Help & Troubleshooting] genius764:
awesome

thanks for the input.
[EVO 4G Q&A, Help & Troubleshooting] stillryan:
You gave people here a whole 3 hours and 15 minutes to respond to your question on a Sunday night. Your question has been asked quite a bit.

The usual answer is that there really is no best rom. The only way to find the really stable roms is to try a few out and see how they work out for you and then make up your own mind. Some people swear by CM6 and say all sense roms are ****. Others are the exact opposite and prefer having sense on their phone. It usually comes down to personal preference.
[EVO 4G Q&A, Help & Troubleshooting] Originalkingpin:
Stock rooted w/ King's Kernel, fricken sweet benchmarks!!
[EVO 4G Q&A, Help & Troubleshooting] DXL007:
DC 3.5 with stock kernel rocks
[EVO 4G Q&A, Help & Troubleshooting] genius764:
Hmmm

I was hoping to get some of you guys say the same roms but that didnt happen. sense or senseless doesnt matter to me. i like the senseless but i have no beef with sense. so far i have tested a few and settled on omj 2.2 v3.0. so far nothing crazy with the widgets. thanks for the input.
[EVO 4G Q&A, Help & Troubleshooting] genius764:
??

what is the difference between king's kernel and toast's/netarchy's?
[EVO 4G Q&A, Help & Troubleshooting] fachadick:
I've found BakedSnack to be incredibally stable, has everything working (i don't use tethering, but folks in the thread have confirmed it working) and his undervolted kernels rock.
[EVO 4G Q&A, Help & Troubleshooting] boredmug:
What the hell is this? It's not dead pixels.. I noticed this a few weeks ago and it looks like it may be getting worse. It's mainly noticeable on white backgrounds. I baby this phone. It's protected with a case and screen protector from day one. Never dropped. I would take it in now and see if I could get it replaced, but I hear replacements are coming with 2.2 and I don't want to be stuck without root. Anyone else have this lighter spot in their screen?
[EVO 4G Q&A, Help & Troubleshooting] scriptx:
I have this exact same anomaly. The pictures below don't quite do it justice, but I'm sure the passers-by can get the idea here. It's more evident when the screen is bright, and the background is white. Very annoying. Screen has never been dropped, etc. My HW revision is 0002.. novatek panel.
[EVO 4G Q&A, Help & Troubleshooting] The Local Moron:
Aww crap, I'm in the same boat as you guys...

And to think I was going to get a phone that WASN'T defective first time around :P
[EVO 4G Q&A, Help & Troubleshooting] boredmug:
Weird. That's almost the exact location of my spot.
[EVO 4G Q&A, Help & Troubleshooting] udjat:
I think it a heat spot from the CPU.

I have the same thing. ;)
[EVO 4G Q&A, Help & Troubleshooting] mistersquirrle:
I also have one, in almost the exact same spot. I don't know what's causing it, but I also have that issue with my monitors on my laptops. I usually end up getting like 3-4 big spots on the screen. I don't notice it to much because I've gotten used to it, but my screens have preformed just fine even with the bright spots.

Just think of it this way, you can see those spots better in the sun now, since it's brighter :)
[EVO 4G Q&A, Help & Troubleshooting] jkcpsal:
I had that on my first phone. I also had light leakage so I figured they were related.
[EVO 4G Q&A, Help & Troubleshooting] scriptx:
It's really not a big deal to me, so long as it does not get worse. It's hardly noticeable. It's just one of those things you notice because it's wrong, but no one else would ever see. My Evo is great otherwise.. I'm not interested in risking a return for a refurb or unrootable 2.2 device.
[EVO 4G Q&A, Help & Troubleshooting] firemedic1343:
I have the same problem. Novatec 0002. It started out barely noticeable and it has grown to be significantly worse. A big white spot that is really really bright white on white screens.

I was showing off my EVO and everyone was just fixated on that spot. Can't show off the EVO anymore. I'm very upset, I would rather have an unrooted 2.2 than a big eyesore on the screen. I'm sure someone will root 2.2 soon enough.
[EVO 4G Q&A, Help & Troubleshooting] scriptx:
Might be worth making a stink about after a new hw revision (or with recent) and after 2.2 is rooted. Cry a river about light leakage and get a replacement. I can deal with it the way it is now, but would rather be proactive before it gets worse.
[EVO 4G Q&A, Help & Troubleshooting] tomh1979:
I have it as well didn't think much of it cause i had never heard anyone else say anything, now i atleast know im not alone, and it should be noted as a issue.
[EVO 4G Q&A, Help & Troubleshooting] scriptx:
For those of you with similar issues, list your hardware builds and screen manufacturers, etc.
[EVO 4G Q&A, Help & Troubleshooting] boredmug:
Revision 003 novatech panel. Seems like everyone with this problem has a nova panel so far.
[EVO 4G Q&A, Help & Troubleshooting] bomix:
Same here.

I have the same issue.. similar spot, I don't mind as long as it doesn't get worse.
[EVO 4G Q&A, Help & Troubleshooting] boredmug:
It doesn't bother me horribly, but I do find my eye being drawn to it. Also, for as much money as I've spent on this thing i expect the screen to not have defects like this. As soon as root for 2.2 is achieved I will probably be trying for a replacement.
[EVO 4G Q&A, Help & Troubleshooting] ktulu909:
I have been waiting on a replacement from radio shack for 8 weeks because of the same issue.REV 2 nova panel.Mine has gotten bigger and is now 2 separate spots.
[EVO 4G Q&A, Help & Troubleshooting] datajosh:
I have the same issue on a Rev 3 Nova, also ended up with some kind of weird screen "burn in" - you can see numbers from the vanilla lockscreen clock when the screen is black. I'm supposed to be getting a replacement (my third now) from the local repair center sometime in the next few days.
[EVO 4G Q&A, Help & Troubleshooting] boredmug:
So apparently these novatech panels are junk.
[EVO 4G Q&A, Help & Troubleshooting] roshambo:
Add me to the list as well. 002 w/Nova. Same exact spot about an inch above the back button at the bottom. Has anyone successfully got Sprint to replace theirs for this issue?
[EVO 4G Q&A, Help & Troubleshooting] scriptx:
Waiting for a new HW build (and verification that it doesn't have similar problems) before calling Sprint about it.
[EVO 4G Q&A, Help & Troubleshooting] firemedic1343:
I was going to do that also, I just don't want the phone to get a scratch or bump on it that will give them an excuse not to replace my phone.
[EVO 4G Q&A, Help & Troubleshooting] Joey SR:
How do i know which screen i have? I have slight light leakage above the home button but thats about the only problem.
[EVO 4G Q&A, Help & Troubleshooting] scriptx:
Worst case is insurance replacement.. but still, they should warrant the device being defective, considering the manufacturing problems they have had. It might be a good idea to call now to claim the issue so that it's on record.
[EVO 4G Q&A, Help & Troubleshooting] davenukem:
So, what should we all do? Replace and hope for a phone with an epson.
[EVO 4G Q&A, Help & Troubleshooting] xcodesterox:
worst thing is...

"Its a cosmetic defect, and Sprint does not see that as a reason to replace the handset"