yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] Br1cK'd:
I see waht you mean, the app is only taking pics around 3MP. I had not realized this, nor do I know where to begin fixing it. Not to say it won't be fixed, but it won't be soon. You may want to try the Modified Twiz camera in the (edited) second post, if you can live with the one FC it has.

Sweet!! TY mendozinas.

E1, this means you can now create your own accurate battery mod in the kitchen, without having to upload the 1.3.5 framework, its already there! Go thank mendozinas, cause thats freakin fantastic!

I had not planned on it. I wanted to keep the AOSP theme just that, AOSP like. It can be ported over to the other framework, but I won't have time to do that for at least a week. If anyone else wants to port that over, including the correct xml edits for the text and clock colors, go for it, and upon testing, I'll post it for everyone.
[Vibrant Android Development] misfitpierce:
Ill check it out. I may just stick with it and wait it out. 3MP is not that bad. Its a great rom none the less.

Galaxy S T959 (Zendroid 1.3.5 + Bali 1.8.6UV + KA6 Modem) Custom Undervolting. XDA Premium App
[Vibrant Android Development] Br1cK'd:
I'm a dummy, 2nd post has the modified Twiz camera, not the third, sorry. Its actually a nice modded camera with a ton of features, I removed it due to the FC when taking video at the highest resolution, other than that its tip top.
[Vibrant Android Development] misfitpierce:
Yeah ill prob use that for now. Appreciate the fast response tho. Rom is top notch too... you da man.

Galaxy S T959 (Zendroid 1.3.5 + Bali 1.8.6UV + KA6 Modem) Custom Undervolting. XDA Premium App
[Vibrant Android Development] fishman0919:
That awesome!!! Thank You Both
[Vibrant Android Development] OldeCrow:
@Br1cK'd

Best AOSP Theme I've seen to date! :D

BTW dono if green progress was intentional but here's a screeny with AOSP Orange
[Vibrant Android Development] Br1cK'd:
Actually, the progrss bar color on that theme slipped my mind completely. I think its stock twiz green right? What was the hex code you used there, Ill fix up those colors tonight, thats an easy one. Thanks for the heads up

Sent from my ZenDroid, meditating on the XDA App
[Vibrant Android Development] OldeCrow:
You would ask me that! :D

It's in my cheats folder of compiled xml's....

looks for xmlprinter thingy... there..

<gradient
android:startColor="#80FFD300"
android:endColor="#A0FFCB00"
android:angle="270.0"
android:centerY="0.75"
android:centerColor="#80FFB600"
>
</gradient>

them's be the yellow values for the progress bar!

btw you might think about changing out the AOSP radio's and check boxes for the orange vibrant ones from the 2.1 roms they look very similar but display better over dark backgrounds like in the settings and stuff... just my 2c though ;)
[Vibrant Android Development] Br1cK'd:
It would be fantastic if you could either upload the file or pm me the text from your progress_horizontal.xml. Also, if you have a framework available that has the check boxes and radials youre referring to, I'm in husy mode again, so research time is slim to none, but if you have them and dont mind sharing, all credit will be given where its due.

Sent from my ZenDroid, meditating on the XDA App
[Vibrant Android Development] OldeCrow:
PM incoming! :)
[Vibrant Android Development] Br1cK'd:
Ty sir, received and dl'd. I'll take a look at that source when time allows. Appreciate the input.

Edit - I took a peek, you're talking about the same check boxes and radials I used in ZenDroid. I do like the way they look, but not sure if they fit with the Froyo AOSP Theme. I know they look great (why I use them in ZD), but those are GB style.

Edit 2 - AOSP Theme updated with progress bar color change, ty OldeCrow for the suggestion.
[Vibrant Android Development] OldeCrow:
lol ya I know the AOSP purists will have small farm animals over that, I have an idea for the aosp images that might make them work better with the black backgrounds I will try out when I get a chance! :)
[Vibrant Android Development] blaxtar.inc:
This might be a no-brainer to most but how did you customize your launcher like that?
[Vibrant Android Development] OldeCrow:
It's LauncherPro from the market, I keep the android icons seperate on the phone for customizing the links too...
[Vibrant Android Development] Mdtolic:
@Br1cK'd - Dude, thank you for the AOSP theme! First flash was a strange combo of AOSP/Zen. Re-flashed and it's all vanilla now. Love it with Launcher Pro. :p

I'm having a problem with the FlexT9 keyboard though. It's totally freezing up. Requires a battery pull. Any ideas?
[Vibrant Android Development] Br1cK'd:
I was going to try to test the kb, but I see its a paid kb on the market. If you could capture a logcat of when it locks up and post it for me, I might be able to figure it out.

Sent from my ZenDroid, meditating on the XDA App
[Vibrant Android Development] Mdtolic:
Logcat sent by PM. Home that was OK?

First time doing that. Phone locked up in a TM, I pulled the battery and then captured the logcat after it rebooted. It was too long to send in a PM, so I cut it in half. Hope I sent the right half. Thanks man.

Edit: I just thought to add the whole thing as an attachment. Duh. Sorry.
[Vibrant Android Development] OldeCrow:
sd read ahead tweak...useless?

//Begin long winded post about merits of sd read ahead "fix"

been doing some experimenting today, had a conversation with a friend the other night who also has a Vibrant and he mentioned that his phone wasn't running with the 1024 sd read ahead buffer I had set in init.d (modded zen rom, running edt tweaks and darky's new zipalign script) anyway I responded that he was being silly since I put the edt scripts in myself and I adjusted the read ahead value to 1024 it should then be working, and the other init.d scripts were working because I have a zipalign log file generated by the zipalign script... so I did some experimenting with a free market app called "sd speed increase" which when not enabled at boot will just show your current sd read ahead buffer and of course it showed 1024 on my development phone which doesn't have an external sd card in it... my daily driver has a 16m sd card in it and interestingly enough sd speed increase shows the default value of 128k... :mad: When I unmount the sd card the value jumps up to 1024 as declared by the init.d script and the value is verified by looking at /sys/devices/virtual/bdi/179:0/read_ahead_kb which also reports 1024...

when I plug in the sd card the media scanner runs and the value displayed in sd speed increase drops down to the default value of 128k again.

I have no reason to doubt the app is reporting correct information which leaves me to conclude setting the sd read ahead buffer size in init.d is pointless as something else in the rom is resetting it to 128k. Setting the value with the app however does seem to "fix" the value that you set in the app for the phone so if there is any merit to adjusting the sd read ahead buffer it can be accomplished with the app at least.

I haven't tested this on another rom yet so I don't know if this is a kb5, zen or vibrant general issue but I thought I would share it here since this is the rom I'm currently running...

the original post on the read ahead fix is here if anyone is interested:

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

you can flash one of the files from that thread if you want to try to reproduce my results or experiment with it but it appears the app from the market is the better choice at the moment.
[Vibrant Android Development] Br1cK'd:
Thx, I'll have a look at it when I get the chance.

Have a big question based off of this. Why are you downgrading it to 1024?

If you follow the post you linked to check the red ahead size, before modding or adding any scripts, ZenDroid read ahead, out of the box, is 4096 (which is that Mods top setting). By setting it to 1024, you are bottlenecking it before it even gets a chance to get going.

Now that app, do you think that its reading the external speed at 128, then you eject your external and it reads what the read ahead "fix" (or downgrade :p) does to the internal memory. Does the app read both simultaneously, or may it possibly be configured for the majority of smart phones that only have one sd storage, as opposed to our dual sd storage?

To answer the title of your post bluntly, yes its useless on this rom. Its my understanding the mod is designed for older phones and possibly older firmwares who have a lower setting hard coded into it. Zen read ahead is already at that mods highest setting, 4096.
[Vibrant Android Development] Br1cK'd:
Mdtolic, i see an error there, but thats your phone booting correct?

Can you capture the logcat when you make it lock up?

Also, I was wondering if anyone else uses that particular kb, T9Flex, has the same problem?
[Vibrant Android Development] Mdtolic:
Nope. I'm using the aLogcat app. I don't know how to do it any other way. The screen is completely frozen. Nothing works; not even the power button. I have to pull the battery.
[Vibrant Android Development] OldeCrow:
hehe 1024 was an arbitrary number, I knew it was above the reference of 128k and below what any dev would be using on a rom so it makes it easy to spot as the result of the read ahead "fix" in init.d

the sd speed increase app does in fact report 4096 by default when no sd card is installed but when an sd card is installed it drops to 128k in the stock zen configuration

if I run a speed test with the sd tools app it reports 10.4MB/s write and 19.8MB/s Read in the stock configuration.

When I use the sd speed increase app to force 4096 so it's reported even with the sd installed sd tools reports 11.2 write and 27.5MB/s read. That is a big enough increase reported in read speeds to make me look twice...
[Vibrant Android Development] Br1cK'd:
Unfortunately the logcat when you're booting is of a successful boot, and that gives me nothing in the way of the error thats causing the stop. If you want to grab one, you will need to get the android sdk installed on your system, and run a logcat through your command line to get the info I need. If you can grab one that way, I will do my best to figure it out.

But, which sd is you speed test app testing. By default, I did not tweak these settings, but I am failing to see where this is a problem with my rom, when you haven't tested your results, or posted results, run against any other rom and compared to mine, running stock configs.

I do think your apps are testing the external by default, but I digress.....

I hope you don't take this the wrong way, and you know I appreciate your feedback friend, but if this is something you want to solve, perhaps a separate Thinktank thread is on order. You can get more heads on it, and not derail ZenDrioid with something that I never changed from the original firmware source.
[Vibrant Android Development] Mdtolic:
Yeah, I didn't think that was right. I'll have to read up and see if I can do it the right way. Thanks Br1cK'd
[Vibrant Android Development] OldeCrow:
lol if your not worried about it then I'm not worried about it :D

I don't disagree with your assessment of what the apps may or may not be testing and I trust your judgement over a couple of hack apps from the market any day of the week!
[Vibrant Android Development] Br1cK'd:
I'm not sure I trust my own judgement at every turn, and I am by no means a ruling authority on how these things work man.

I do understand exactly what your findings are telling you, and yeah I see how that can be an issue, especially for those who use a large external sd as their primary storage. There may be a way to improve the speed for both internal and external sd. With our phones having the dual storage, that creates an extra hurdle in how our phones handle data, and there may be an entirely different set of configurations for how the external is handled on our Vibrants. Unfortunately, we are only two guys discussing this, and I don't have the time I want to have right now to track this kind of stuff down.

Thats why I still think a thinktank thread may be the way to go. Get some other minds on it, get others opinions and findings, collaborate, and maybe a fix will come out of it. I for one wouldn't mind hearing birger's or jellette's take on the read speed of our externals given your findings, and a thinktank thread would put this in its own light. Consider posting your findings like that, doesn't hurt to put it out there.
[Vibrant Android Development] Br1cK'd:
DL the android sdk from here: http://developer.android.com/sdk/index.html

From there, hopefully you're familiar with working from a command line, you set your path to the sdk/tools folder that the installation linked above will create on your computer, and run this command:

adb logcat

You will then see a ton of text scrolling across the screen, make the phone error, and the logcat should stop. Copy that text to a text document, and post it like you did before.

Hope this helps, good luck.
[Vibrant Android Development] fishman0919:
Don't know if it's been mentioned yet but there's a bug'ish with the AOSP theme.

If you have the option checked for Puzzle Lock under display for texts and calls, it will not work when you get a text... but if you unlock the screen and then put the phone back to sleep... the puzzle lock shows up on wake.
[Vibrant Android Development] Br1cK'd:
Good catch, I'm getting the same results with the stock framework too. I did intend to kill the puzzle lock option initially, but decided not to, and there maybe an edit I did in there that I didn't undo, will have to comb through some edits and see if I forgot to fix a string or two. That won't happen for a few days yet, too busy with work this week, but I'll try to get that patched soon, or just remove the puzzle lock all together.

Thanks for bringing that to my attention.
[Vibrant Android Development] Mdtolic:
What's a command line? Just kidding. Not really. But I'm still going to try to figure it out. I'm pretty happy with this kb and would like to make it work. I'll get back to you in a bit. Thanks again
[Vibrant Android Development] Br1cK'd:
A dos window if you're on a pc is what I was referring to as command line.

Godspeed.

To all, I have been trying to hunt down the offending bit of code that may be causing the puzzle lock to not display message notifications. I have been entirely unsuccessful at this task this morning. I think I am just going to try to rebuild the framework from scratch, but I won't get around to that until this weekend at the earliest. I don't even use the puzzle lock, but its bugging me enough, that I will do all I can to get it fixed in due time.
[Vibrant Android Development] fishman0919:
NP..... :D TY
[Vibrant Android Development] iynfynity:
I have a question, i know that other kernels would work with this rom, but am i fine flashing other kernels? I'm asking because maybe the kernel that comes with it is optimized for the rom. Unfortunately, i don't use kernels with UV.
[Vibrant Android Development] Br1cK'd:
You can flash any 2.2 compatible kernel. I was having great results and battery life with DragonModz Kernel, but went to Bali specifically because it mounts to pc in recovery mode, and has no permission errors when running ddms through sdk.

Those are things the average bear doesn't use or need, but playing around with the software as much as I do, I use those two things a lot. ZenDroid is not optimized for any specific kernel, rather, its compatible with any kernel you wish to use. :D

Edit - I do prefer the performance Bali provides now in the latest UV Versions, and will be sticking with that kernel in ZenDroid for the foreseeable future.
[Vibrant Android Development] OldeCrow:
@Brick'D

I put the AOSP theme in the rom along with darky's latest zipalign script and flashed it, I swear it boots faster on the first run than some other roms boot normally! :D

Also after continued punishment by me I am finding this to be the fastest rom out there in general right now too!

Just plain remarkable!
[Vibrant Android Development] iynfynity:
Never mind. Fixed it
[Vibrant Android Development] mac1133:
anyone use Eugene AOSP vanilla VC RC3, how does this compare with the aosp theme?
[Vibrant Android Development] Br1cK'd:
Did you pull that script out of darkyy's rom? I'm not seeing it posted on its own. Also how does it compare to the zipalign script I'm using?

EDIT - Question retracted. The proper question is, whats not different about it. Going to test this script out, and most likely include it going forward.

2nd EDIT - I will be updating Darkyy's Memory Tweak as well.
[Vibrant Android Development] iynfynity:
I have this rom all set. I love it! been looking for a vanilla rom and this one is perfect!
[Vibrant Android Development] OldeCrow:
They are pretty similar, Eugene used the classic notification toggle buttons and Brick'D used... um... hell I dono what they are from but they look good :D

Also if you are a novice, flashing one of Eugenes rom's is a great way to become an expert whether you want to or not, if you want to stay a novice stay with this! :D
[Vibrant Android Development] iynfynity:
can I flash the 9 lockscreen while using the vanilla theme?
[Vibrant Android Development] OldeCrow:
a quick glance at the zip file looks like it will work but you will have the stock zen theme back with the 9 lock screens when you do. You can't get 9 lock screens with the AOSP.
[Vibrant Android Development] jrafael:
Try juwes memory script, better than darkys imho
[Vibrant Android Development] Br1cK'd:
Ill check it out.

Sent from my ZenDroid, meditating on the XDA App
[Vibrant Android Development] iynfynity:
can someone post the original wallpaper? I don't know where to find it.
[Vibrant Android Development] Big Dog KMc:
The second post in the OP has All of the Original Wallpapers.
[Vibrant Android Development] iynfynity:
it doesn't have the wallpaper that came originally with the romn The android holding the globe is what I'm saying.
[Vibrant Android Development] Big Dog KMc:
Ok. That would be the vanilla theme wallpaper.

will look for it.
[Vibrant Android Development] Big Dog KMc:
Here it is
[Vibrant Android Development] Br1cK'd:
Thx BigDog, good lookin out.

Hole everybody. Been toiling away tonight. I rebuilt the stock and AOSP frameworks, in an attempt to resolve the puzzle lock MMS issue. No dice, but I did manage to now include the Clock Toggle alongside the AM/PM toggle in Settings. I'm not going to put out a full release for this, it will be included in the next one, however....

2nd Post Updated

The AOSP Theme and the ZenDroid Theme restore have been updated, and now contain the Clock Toggle as mentioned above. Figured I'd let you guys get your hands on that little tweak while I'm still hunting for a fix for the Puzzle Lock issue.

The framework files in the UOT kitchen are still applicable for the stock theme, animations are still good as well.

Enjoy.
[Vibrant Android Development] OldeCrow:
@BricK'D

would it help to actually put the puzzle lock back in so the check box in settings switched between the puzzle lock and the AOSP lock? It's not like anyone will forget it's a Samsung phone so if the puzzle lock was there with the AOSP one that would be an acceptable compromise to me!
[Vibrant Android Development] Br1cK'd:
It would work in theory, but not the direction I want to go.

In order to force the aosp lock screen, which is already in the twiz framework, just written into the background, you only have to change one entry in the android-policy from GlassLock to TapLock, and voila, no more glass lock screen. I have tested different mms apps, including twiz (yuck), and they all behave the same in regards to the puzzle notification. I think its an after effect of setting the TapLock as default.

I am leaning towards stripping the puzzle lock out completely now, to alleviate the problem, and go with what I wanted to do in the first place.

Sent from my ZenDroid, meditating on the XDA App
[Vibrant Android Development] Br1cK'd:
2nd Post Updated

Removed the Battery Popup notification from both the stock framework restore and the AOSP theme in the second post.

This mod will be included in the heavily delayed next version, sorry, been busy, but figured I would give you guys this little mod as well, for those that want to flash it ahead of time. No ETA for the next update, I'm still busier than a one legged man in an ass kicking contest.
[Vibrant Android Development] Big Dog KMc:
No problem. Take your time.

And if you can jump high enough,,,,,,, keep on a kick'in

EDIT:

WOOHOO 100th Post Here!!

Now in can collect social security, I a senior.

only took me a year and 2 months to do it.
[Vibrant Android Development] dallen50:
No probs here as well Br1cK'd !! Was getting concerned about your absence tho! Glad you're alright. Your ROM is the best one out there. :D:cool:
[Vibrant Android Development] Br1cK'd:
With all I've seen you do, you're only at 100?

Man after my own heart right there. Read read read and understand before you jump out there. Thats a rare thing around here anymore.

I'm still around, doing what I can here and there. Another week or so my schedule should lighten up and I'll be back to a somewhat normal life again. :cool:
[Vibrant Android Development] lazyb421:
Hey Br1cK'd just letting you know that I just flashed the stock framework restore and am still getting the battery popups.
[Vibrant Android Development] Br1cK'd:
Thats weird, I just decompiled my services and made sure the edits stuck.

I went ahead and re-uploaded the zip as well, try to dl it again and lmk your results.

EDITED - Something went awry, the pop is still present as stated by lazyb, I'll patch this properly when I get the chance, sooner rather than later
[Vibrant Android Development] Br1cK'd:
Realized there was one string I messed editing, testing now will be uploading the updated themes shortly.

Sent from my ZenDroid, meditating on the XDA App
[Vibrant Android Development] Br1cK'd:
New versions uploaded of the ZenDroid Framework and AOSP Themes, battery full popup should finally be removed. Im still charging and have to run out the door, but this should be good now.

Sent from my ZenDroid, meditating on the XDA App
[Vibrant Android Development] dallen50:
Thanks! Will flash this revision as soon as I get home!
[Vibrant Android Development] Br1cK'd:
I am reminded in these latest edits, how great of a team EDT really is. When I was with them, and we were all working together, we all seemed to have a piece of the picture and together as a whole made it happen. What kicked off this walk down memory lane was getting some assistance from both Romann and Whitehawkx in removing the Puzzle Notification, and it was like old times, I had a piece of it, Romann had another piece, and Whitehawkx had the final piece that made it all work.

Thanks guys, as always your assistance and expertise is appreciated.

-Edit - good lord this notification will not go away, It will be fixed soon, I swear on it. The puzzle notification will pop up for missed mms and calls, but the options no longwer in settings. There's got to be a string I missed somewhere. I will find it.

Op and 2nd Posts Updated

-I thought I had removed the puzzle notification, I-R-Fail and will be fixing this over the weekend, no wipe update when that is fixed.

-Updated Zipalign script to Darkyy's Modded Script

-Updated to Juwe's Memory Script

-Fixed the Battery Full Popup Removal, scripted properly now.

-Fixed a bug with the Hide Clock Toggle

-Several other tweaks you might not even notice.

-AOSP Theme and other add-ons have been updated as well, enjoy!
[Vibrant Android Development] Dan_Brutal:
Come on back brother. The front door is always open for you.
[Vibrant Android Development] fishman0919:
Thank You for another Zen releasse :D
[Vibrant Android Development] suchavibrantthang:
O happy day! I love this rom and the stable slimness. will be flashing soon!