yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] purple1:
ok so i flashed this rom in this order

1.flashed to stock

2.Rooted phone

3.flashed Rom

4.when its done booting let it sit for 20 min.

5.try to add gmail and sync contacts and it was fine

but as soon as i go to try to import contacts from my sim it says theres no sim card WTF this **** better not have deleted all my contacts and i know it wasnt from flashing to stock because i never flash with my sim and when i rebooted again it deleted my gmail and said i had to sign in again
[Vibrant Android Development] purple1:
what up cuhh
[Vibrant Android Development] Br1cK'd:
There is absolutely nothing in the rom or scripting that touches your sim card, but I refer you to the forum rules (no swearing please) and my disclaimer - I am not responsible for what happens to your phone, yadda yadda.

If you want help, try asking, friend, and not being quite so harsh and accusational.

Nothing you have done should have removed anything from your sim card. I can import contacts from my sim without issue, and my phone sees my sim. Whats concerning is you said your phone no longer sees your sim card. Does it not see the card, or does it not see contacts on the card? How old is your sim card? They do go bad sometimes. Does it have any marks on it from repeated removal and installation? Is your sim damaged? Can you provide some more information. Maybe try your sim in a backup phone and see if it reads the contacts, if you have one available to you.

Attention

I have now really, seriously, stripped the Puzzle Notification stripped for good. I will be uploading the full rom in a few hours when I get home from work. If you want the fix now, flash the attached update. This is for users coming from 2.0 ONLY.

Again, if you would rather wait for the full build, it will be posted this evening.

EDIT - No Wipe Update Removed
[Vibrant Android Development] purple1:
I probably did something wrong in flashing the rom I flagged another rom cm7 and its working good. The rom didn't read my sim nor sd card I have no idea what went wrong and my sim I had it scince 2006 but theres no scratches on the back oer anything
[Vibrant Android Development] burgon:
I know this sounds stupid, but just to be sure - try putting the sim in again. Make sure that the cut corner is sticking out. The only time I had my phone not recognize a sim is when I inserted it with the cut corner in.
[Vibrant Android Development] purple1:
I know its in right I checked flashed again and same thing happened doesn't recognize my sd nor my sim contacts
[Vibrant Android Development] Br1cK'd:
That is definitely an odd issue man, wish I could replicate it so I could troubleshoot it.

Haven't had any other reports of either sim or sd giving read problems after haven't flashing, unless they just haven't been reported.

Maybe 2.0.1 will treat you better, it will be live in a couple of hours.
[Vibrant Android Development] Br1cK'd:
Its going to make me a sad panda the day I can't do 15 things at once anymore. ;)

OP and 2nd Post Updated

v-2.0.1 -2nd Update Today

(6/23)

-Good Riddance Puzzle Notification! (really this time I mean it :rolleyes:)

This did not go unnoticed earlier my brotha. If I could really dedicate regular time to the team, I would heavily consider re-upping. Had a job interview yesterday for a better position with regular hours, and have been notified of a 2nd interview for next week. Keep your fingers crossed for me, if it works out I'll be back to a more normal schedule, and would definitely have time to put towards something bigger.
[Vibrant Android Development] dgsmith90:
Two questions for you:

1. Did you try another rom? If so and same problem, then

2. Take out the SIM card and check for burn marks or dark areas. This may sounds stupid, but the mytouch I used to have burned 2 sim cards to the point of not being able to read them anymore and they had to be replaced.
[Vibrant Android Development] SeanFloyd:
Thanks Brick'd, **** is quality as always.
[Vibrant Android Development] Br1cK'd:
Giggitty

Sent from my ZenDroid, meditating on the XDA App
[Vibrant Android Development] purple1:
It was the rom
[Vibrant Android Development] Br1cK'd:
What other roms have you tried besides going back to cm7?

You can't honestly say its the rom when you're having an isolated incident. Nobody has come close to issues like you were reporting.

It may be your phone and the rom, but I think something else you flashed left an unresolved issue on your phone friend.

Sent from my ZenDroid, meditating on the XDA App
[Vibrant Android Development] purple1:
so far ive been flashing all sorts of roms cant really be specific because i dont know all the names but project v, cm7, toxic something, bi-winning v2 and i tried this one its not my phone because all the other roms i use/try all read the contacts on my sim this is the only time ive encounterd this problem with any rom im guessing its just a bad download ill try your updated version later when im home
[Vibrant Android Development] Br1cK'd:
Weird stuff, does sound like you have been flashing quite a bit lately. Maybe 2.0.1 will work for you. I recommend verifying the md5 of your download to whats posted in the OP to make sure you get a good dl. Best of luck.

Sent from my ZenDroid, meditating on the XDA App
[Vibrant Android Development] purple1:
yup updated version working good n smooth was probably a bad download but all is good now keep up the good work
[Vibrant Android Development] blaxtar.inc:
Okay Br1cK'd...I'll start by saying that I love your ROM. I'm a huge fan of AOSP Vanilla ROMs and this is the best so far. I just flashed this one numerous times (I'll get to that later) and keep having issues. 1.3.5 worked flawlessly for me. No issues what so ever. Now after flashing 2.0.1, I have major issues. I flashed this 4-5 times with the following steps: 1) Odin back to Eclair 2.1. 2) Install CWM and flash. 3) Wipe data, cache and dalvik before installing zip 4) After flash, allowed phone to sit and settle for 10, 20, & 30 minute intervals before rebooting. 5) After reboot, just played around, opening apps and such. This is the same method I usually use for all the ROMs I flash and I never had any problems that a simple reboot or battery pull didn't solve. This time around, I keep having issues, mainly FCs and data. When I boot, it takes a while to load the Galaxy S screen. Also it occasionally gives the 'one vibration followed by three vibrations thing' during or after boot. When it does boot, like 3-5 FCs come up. Dialer, maps, Android processes, etc. After a reboot, it just gives a system failure error but it acts sort of normal until I reboot but the data drops sometimes. It also has an error loading the widgets after a reboot. Just really crazy for me. Any suggestions Br1cK'd or anyone else. I'm lost.

P.S. - I also verified the MD5 on the zip.
[Vibrant Android Development] Br1cK'd:
Good to hear! :D

Where to begin. MD5 verified, but did you try to dl again, just in case? The major changes from 1.3.5 to 2.0.1 were all contained in the settings.apk, android-policy.jar, services.jar, and init.d the script updates. Otherwise its basically the same build as 1.3.5.

You didn't flash the update, but the full 2.0.1 rom correct?

Also, did you make any changes to the rom prior to flashing it?

Finally, have you flashed anything else since experiencing this, and with what results?
[Vibrant Android Development] bdubs4200:
Dropped in to say, best title EVER! I loved zendroid! But I've been on a Ginger binge cm7/miui... catch is no lappy ne more> no Odin :-( but zendroid was in my top 3 100% stable roms. This looks tasty titties as always.
[Vibrant Android Development] purple1:
any good kernals that work well with this rom? any recomendations?

one that is fast as well as good in battery life
[Vibrant Android Development] Br1cK'd:
I run Bali 1.8.6, my phone doesn't work well with OC Kernels. Its my understanding that both DragonMODz and Bali OC versions do run very well with Zen.
[Vibrant Android Development] blaxtar.inc:
I'll re dl in just a sec to see. I'm sure there were not any major changes to the update that would cause any real issues. The last time I had an issue similar to this was the kernel issue you helped me with when you were using the ssj kernel. But yes I dl'ed the full 2.0.1. I didn't make any changes to my phone ouside of formating the internal sd before I odin (to clean the files from old, unwanted apps) I'll flash a couple more ROMs to see what happens in a few.
[Vibrant Android Development] Br1cK'd:
LMK what you find out. I am going to be crashing soon, but I'll be up and at a pc in about 8 hours, and checkin in on your results. Good luck, hope a re-download cures it.
[Vibrant Android Development] blaxtar.inc:
Just flashed B-Winning and Proj-V. Both gave me no problems. Gonna try Zen 2.0.1 again in a few.
[Vibrant Android Development] fishman0919:
Bali-X 1.2GHz seems to give me slightly better batt life over Bali 1.8.6uv when I use Voltage Control and drop it -25uv across the board and leave the Max at 1000Mhz... it's only been about a week and only 1 day with Zen 2+... but for me it works out about 8-10% more batt life left over Bali 1.8.6uv... but like a said, I could only be me
[Vibrant Android Development] Big Dog KMc:
I'm currently running [Kernel] Immortality-Team Whiskey-BLN,Voodoo,OC/UV user configurable,333MB RAM

By Mr. Apocalypse

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

and I am having very good results.

with other Kernels I could never OC past 1.15, Now I'm at 1.2 with no freeze ups

yet.

I am also under volting every step to -75 except for 1.2 is set to -25 thus far.

I am still running ZenDroid v1.3.5 but should work well with any rom.

Best results I ever had to date.
[Vibrant Android Development] blaxtar.inc:
Okay Br1cK'd...I am now totally convinced that this ROM will not work with my phone. I tried everything (redl'ing the ROM, five different kernels, etc...). No avail. I guess I'll wait on the sideline for the next update. :( Thanx for your help though, if you come up with anything else, let me know.
[Vibrant Android Development] Br1cK'd:
If you can grab some logcat action when its acting up I'll gladly have a look at the logs. Very odd this wouldnt work for you. As much as I flash my phone, I should be the one with problems like that. Wish I had more to offer.

Sent from my ZenDroid, meditating on the XDA App
[Vibrant Android Development] gunked:
Okay so how can I change the color from the ugly blue?
[Vibrant Android Development] Br1cK'd:
By editing the xml in the thread you linked. No blue in ZenDroid (one place, voicemail carrier number text, but thats it), so I am assuming you are modding something else? Please reserve posting in this thread for ZenDroid specific issues as requested in the OP.

Sent from my ZenDroid, meditating on the XDA App
[Vibrant Android Development] blaxtar.inc:
I said the same thing. I've never had a problem out of your ROMs. I too am a certified flash addict. What's a good standalone logcat app? I used to use the one attached to the Mobile Manager app. I'll flash it again just to do that. I hope it helps.
[Vibrant Android Development] Br1cK'd:
I remember someone mentioning alogcat in the market before, I use command line logcat on my pc, have no personal experience with logcat apps.

Sent from my ZenDroid, meditating on the XDA App
[Vibrant Android Development] blaxtar.inc:
Okay, n00b question. What's the best way to do it on pc? Or is there a youtube vid for it?
[Vibrant Android Development] Br1cK'd:
You have to have the Android SDK installed on your pc, you type "adb logcat" without quotes, press enter and watch the magic happen.

Android SDK - http://developer.android.com/sdk/index.html
[Vibrant Android Development] blaxtar.inc:
Excellent, I already have sdk on my pc. I'll flash Zen in a few and post my results. Thanx a bunch for the support Br1cK'd.
[Vibrant Android Development] blaxtar.inc:
Okay...here's the logcat. **fingers crossed**
[Vibrant Android Development] blaxtar.inc:
Okay...here's a better one.
[Vibrant Android Development] Br1cK'd:
It seems you have a lot of files on your phone. Not a problem, but thats where it looks like any errors were lying, with your data itself. Try deleting all the temp files, as in the .thumbnails in your DCIM folder, and all of the voodoo logs that are generated every time we reboot with a Voodoo kernel.

As an additional step, you may want to backup the data off your internal and external sd's, then format both, restore your data, and reflash. I know that sounds like a PITA, but it might help.

Whats throwing me is that you can't reproduce your issue with other roms. :confused:

Can you grab another logcat when you're having a flurry of fc's? Start logcat, then make it fc everywhere you can, and post that log if you don't mind.

When all else has failed for me in the past when my phone's been overtly buggy, I fall back on what I call old faithful. ODIN Eugene's Froyo That Doesn't Brick (http://forum.androidspin.com/showth...oyo-That-does-not-Brick!-Downgrading-Is-Fine-) followed directly by a battery pull and ODIN flash of Eugene's JK2 (http://forum.androidspin.com/showth...-Froyo-ODIN-Ready-Image-*-Updated-amp-Final-*), selecting repartition on the JK2 flash only.
[Vibrant Android Development] blaxtar.inc:
I tried to get the best ones I could...
[Vibrant Android Development] tenbeau:
My bad I did not wipe the cache prior to flashing. I did a complete wipe and flashed the 1.1 and all is well. I apologize I guess I was in to much of a hurry to taste the goodies!! This is a wonderful rom. Great work!!!!!!!!!!!!!!!!!!:):)
[Vibrant Android Development] Abu-7abash:
Another ****head troll we've all seen over and over again..
[Vibrant Android Development] Br1cK'd:
If you don't like it, then bug off. You should read the forum rules, especially the part about keeping your trap shut unless you have something constructive to say.

I'd love to run your rom that you worked on, oh wait, you don't have anything out there, making your entire point null and void.

Haters gonna hate, but man, don't hate the player, hate the game (as you watch from the sidelines).

That is all.

Good deal, and well, it gave me a good excuse to pull the No Wipe, which I don't like anyways. Glad all is well.

I'm used to it by now, doesn't get to me like it used to, lol. Not that I won't voice my opinion, just not going to let myself get drawn into any crap by the trolls
[Vibrant Android Development] Shortbus-Driver:
Wow the trolls are already stroking from under the bridge

ZenDroid_RC1
[Vibrant Android Development] mike216:
I was able to flash prior themes but I've fell in love with the stock look.I threw some transparency in the drop down and that pretty much has me satisfied. I can't say enough how much I like this build.glad you decided to come back to 2.2 I really like only solid perfect functioning roms
[Vibrant Android Development] Dan_Brutal:
Then don't flash it? Brick'd, people haven't changed much since you left. Still a bunch of ungrateful punks. Keep up the good work, and the door is always open for you........
[Vibrant Android Development] oka1:
Agreed +1 Good to see you working out your rom skills, again.

It always amuses me that people have more opinion than skill and so often expose their opinion (usually cynical) to the public no matter how lame it is.........
[Vibrant Android Development] mike216:
this build works perfect.GPS locks quick never had any issues with either of the two builds that came out and love the look.this post is in regard to a couple issues that 2 people posted,just sharing my experience.i didnt do a wipe as suggested and still havent had any issues.LISTEN TO THE DEVELOPER AND FOLLOW DIRECTIONS.I can get myself out of a bad flash thats why i went ahead and skiped the wipe but thats me always in a hurry
[Vibrant Android Development] Br1cK'd:
Devfucious say: A tiger cannot change his stripes, nor a Troll change his herpes warts. :D

Werd brotha, I'm here too, if there's anything I can do for the you guys at EDT, just holler.
[Vibrant Android Development] Shortbus-Driver:
Hey Crackstar996 welcome aboard the shortbus kiddo,now buckle up and enjoy the ride...arriving at special ed shortly
[Vibrant Android Development] Br1cK'd:
We're not getting infalammatory in here please. I think we can let this guy go, he's been quiet this whole time.

Don't get me wrong, support of your Chef is greatly appreciated, but I think he gets our point.
[Vibrant Android Development] seedofchaos:
Hey brickd is this the rom that you had some testers for earlier in the week?

I use swype so expect bad grammar and errors :D
[Vibrant Android Development] Br1cK'd:
Yes it is, this is the product of the testing from yesterday morning.
[Vibrant Android Development] :
Great to see you back with another rom Br1cK'd. Loki was one of my favorites.

I'm actually getting this issue as well. Coming from a complete wipe even. Made sure to clear the cache and everything. I've even odin'd back twice to see if that helped. I'm trying a few things right now to see if I can fix it but if you can think of anything that would be awesome.

Edit: I also get this quite a lot when I flash Eugene's roms but none others until now.
[Vibrant Android Development] Br1cK'd:
I would urge you to verify the MD5 of your download against whats listed in the OP. You may have a bad download. I flashed this multiple times, and haven't had a single fc in what I've made public. LMK if you can't get it figured out.

Edit - if it continues, if you can grab a logcat, that might help me figure it out.

Everyone - true to form, I have been tinkering with the looks a bit. I wasn't satisfied with the notification drop down. Attaching a screenshot to get opinions, and give y'all and idea of whats around the corner. I also want to change kernels, to DramgonMODz, any thoughts?

EDIT - Ignore the font, thats my own
[Vibrant Android Development] Sincitybronze:
my vote is please don't change the font
[Vibrant Android Development] :
Yeah I had checked the MD5 and it matched. I downloaded again just to try and it still happened so I'm not sure what up. It does it just once on boot so I let it go and it seemed to stabilize. Look great now.

As for the font, I personally like the stock font. And for kernels I like to try them all anyway so that sounds good. I tend to go back to Bali since I seem to get the best battery/performance with it. I have a couple of the DragonMODz kernels ready to flash and try out but just haven't had a chance to do that yet. It's already looking really nice though. I've never seen the Galaxy S boot logo this smooth!
[Vibrant Android Development] Br1cK'd:
Sorry y'all, ignore the font, thats my own, and one I paid for, will not be included

The changes are the shadows around the notifications, and the dragons in the quick panel.

With DragonMODz kernel, the galazy s bootanim has to go. Have to use a bootanimation.zip, DragonMODz doesn't recognize the samsumg.qmg boot animation. Not a biggie, and will still have it on shut down.
[Vibrant Android Development] Br1cK'd:
OP Updated

I'm sorry? :D

I went ahead and dropped the new changes, I gotta start getting ready for my week ahead. Will be the last update for at least a few days, I promise.

New in V1.2

-DragonMODz SSJ (1GHz) Kernel

-Framework Mods, More theming

-Restored Dialer Keypress Sounds

-Disabled the Secondary Setup Wizard, I personally don't care for it

-Updated Maps

-Added Scribble Bootanimation
[Vibrant Android Development] :
Secondary setup has always annoyed me. I like it better like this.
[Vibrant Android Development] Br1cK'd:
Interesting, did you change the kernel from Bali?
[Vibrant Android Development] blaxtar.inc:
It moves so fast lol...these should help too.
[Vibrant Android Development] blaxtar.inc:
Not at all. All original from the zip file. No apps, mods, or anything. Just a few restarts and battery pulls. A couple of sms came through. Other than that, it's a fresh flash.
[Vibrant Android Development] Br1cK'd:
The reason I asked about the kernel, it looks like you have some permission issues going on with more than a handful of apps. If you use a kernel that does not support init.d scripts, then the setperms script does nothing. Not the case, just wanted to explain my reasoning.

I've reflashed, and before even rebooting because I was impatient, tested out a few things you were having problems with or I noticed were fc'ing in the logcats, and so far I can't replicate any of it. :confused: I haven't even cleared my phone with Odin in two weeks and I can't get a bad flash. I am going to flash ProjectV (edit) and BiWinning* here in a few, then flash back as a last ditch effort to replicate your issues. Don't really think anything will come of it, but its worth a shot.

There is a logcat command that will capture the entire logcat to a text file, but I can't remember it, if someone knows it and doesn't mind posting it, that would be super.
[Vibrant Android Development] Br1cK'd:
Blaxtar, Ive been trying over the last few hours, flashing different roms then back, to reproduce even a single fc, and it sjust not happening. Sorry man, not sure what else I can do. I recommend trying to format your sd's, and/or the eugenes froyo that doesnt brick method as possible solutions for you.

Sent from my ZenDroid, meditating on the XDA App
[Vibrant Android Development] wachalookinat:
Anyone know why Eugene pulled the link to the above mentioned. It doesn't brick because you can't dl it. Lol
[Vibrant Android Development] Br1cK'd:
I think one reason he left and took his links is because people dont seem to read so much anymore, and are then smartasses about it.

I linked it a few posts back, just in case Google is broken.

Sent from my ZenDroid, meditating on the XDA App
[Vibrant Android Development] wachalookinat:
I know, I HATE smart ass's. He was the biggest cockiest smart ass of the bunch. Although there are other devs who give him a run for his money "rolls eyes"
[Vibrant Android Development] blaxtar.inc:
Yeah, I don’t understand it. Like I said, I'm a big fan of your ROMs and they usually work so great for. I guess I can't win them all. I always let my ROMs settle for at least 10-15 mins before I reboot. It doesn't fc as much as the first time I flashed. But it is very buggy still (data issues, system errors, laggy boots and such). I really can't explain what my be wrong. Maybe it doesn't agree with some of the new tweaks in the ROM. I'll try your suggestions with Eugene's No Brick odin files. If it doesn't work I may just roll back to 1.3.5 with the Immortal kernel until you get around to out-doing yourself again with a new update. Thanx again for all the help and support. Hopefully the next release will do better. :)
[Vibrant Android Development] Br1cK'd:
He wasnt a smartass, rather, he didnt have patience for blatant dumb-assery and people who act like jackasses. In that regard I completely identify with the man.

Sorry we couldn't get her runnin man, wasnt for a lack of trying.

Sent from my ZenDroid, meditating on the XDA App
[Vibrant Android Development] reyese24:
So do i just flash the vanilla theme through recovery???
[Vibrant Android Development] Br1cK'd:
Correct. Wipe cache, then flash.

Sent from my ZenDroid, meditating on the XDA App
[Vibrant Android Development] reyese24:
alright cool imma flash right now
[Vibrant Android Development] wachalookinat:
Lol
[Vibrant Android Development] angryattheworld:
Do I have to use the modified twiz camera in the 2nd post, or can I rip one of the twiz cameras from another rom that works?

I want to give the rom a spin, but I want 720p and 5mp more... I actually use it alot for work.

Any insight appreciated, thiking about ripping camera from Project V or Bionix 1.3.1 (what I'm currently running)
[Vibrant Android Development] fishman0919:
I pulled the one from Project V... I just like that style cam better and the touch focus is great
[Vibrant Android Development] Big Dog KMc:
I switched mine to the stock camera.

works great

this is my flashable file
[Vibrant Android Development] Br1cK'd:
Yep, any camera will work. I keep forgettng to research other options for that and the mms, I get into coding and get tunnel vision.

Sent from my ZenDroid, meditating on the XDA App