yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] mightycaz:
How do you do the regedit? what software do i need? any guides already written?

HAHA its like 20 questions up there!!! ^^^^^^

Thanks

Ok, i got task manager program with a regeditor and i changed that value to 160 but now it is a turquise/green colour! im not sure what is goin on now!

It was decimal that i needed to select. Sometimes im just dumb!!!!! no more pot for me before i decide to play with my phone :) :)
[Touch Diamond, MDA Compact IV Themes and Apps] ziao:
Try this:

http://www.ziao.nl/2009/02/release-zifi-vga/
[Touch Diamond, MDA Compact IV Themes and Apps] grahamkdt:
Another one...

You could also try this... it let's you choose any colour you like.

PS. I haven't tried this myself on the Diamond, but I had it on my older devices.
[Touch Diamond, MDA Compact IV Themes and Apps] blake_spector:
BaseHueExpress would do the trick _after_ selecting guava bubbles theme, to avoid reg editing.. it has no effect on the original htc black.tsk theme, cause the 'flatness' and 'blackness' is kinda hardcoded into this theme. Though its a good app for quickchanging the magical basehue value without manually touching the registry :)

@ziao

the skin looks very nice, very aesthetic. i dont have wisbar, so it is as beautiful as useless for me ^^ but nice work anyways!
[Touch Diamond, MDA Compact IV Themes and Apps] ziao:
Thank you :) I appreciate it
[Touch Diamond, MDA Compact IV Themes and Apps] blake_spector:
btw, here's the result.. very simple, nothing fancy - i like it.

if anyone cares for my carbon fibre background, ask.. i'll share it. its selfmade ;)
[Touch Diamond, MDA Compact IV Themes and Apps] dwizzy130:
I'd love that bg. Can you post it please?

dwizzy130
[Touch Diamond, MDA Compact IV Themes and Apps] blake_spector:
sure i can. here it is - it actually looks much better in realworld, than on the screenshot. fits really well to the tiny little pixels on our precious vga screen.
[Touch Diamond, MDA Compact IV Themes and Apps] Sergio PC:
Aaaaaaa this is cool, thanks ive been looking for this tweak 4 ever.

Greets.
[Touch Diamond, MDA Compact IV Themes and Apps] cokoblazed:
hey ziao, how can i get, my taskbar to look like this w/ the ovals in the bottom bars and the long oval in the top bar?
[Touch Diamond, MDA Compact IV Themes and Apps] ziao:
Download and install Wisbar, found here

http://www.lakeridgesoftware.com/products/pocketpc/WisBarAdvance/index.php?page=download

Download Zifi VGA, found here:

http://www.ziao.nl/2009/02/release-zifi-vga/

Copy one (or all) of the three folders to your device, Storage recommended.

Go to Wisbar settings, install a new theme and browse for it.

Tweak wisbar to your likings and Enjoy =]

If you need any help, don't hesitate to ask - however, do this in my thread, so we won't hijack this thread.

http://xdaforums.com/showthread.php?t=441531
[Touch Diamond, MDA Compact IV Themes and Apps] ilordvader:
How to change the Bottom Bar Fuctions ?

Original is - Phone (left) & Contacts (right)

I want Camera on my bottom bar on - Left

please
[G1 Android Development] vettejock99:
"RC33JF" vs. cupcake - does cupcake have multitouch built in?

I expect some are going to jump on me for asking a dumb question, but a search on this site, which I consider the finest knowledge base around on this topic, yielded mostly conversations around the fact that cupcake will support multitouch, but they don't mention if it is turned on out of the box. In other words, would we need Luke/JF's patch work as we did with RC30 for multitouch to work, or would it just work as it should.

With RC33 out and my confidence in JF that there will be a "RC33JF out within a week" and what appears to be a MUCH more usable cupcake image (as of 2/2, anyway), I am thinking hard about if I'd give up RC33 and Maps, Gmail, etc. and just use AndNav, K9, etc. and APK repositories to survive to get my A2DP bluetooth and full time virtual keyboard, and cupcake is looking more and more promising...
[G1 Android Development] Dharkaron:
first off, multitouch only works in the browser. Im not sure if the current browser would work with the cupcake firmware. If it does then you could just push it to the phone using adb.
[G1 Android Development] justanothercrowd:
JF or LucidREM can one of you please please please make this image without the multi-touch hack in it. You don't know how much i would appreciate it and probably others. Its too weird to have it throughout the OS and there aren't any apps that can utilize it.

I have no use for the multi and don't like the quirky issues that come with it.

Again please please please and thank you! Your work IS appreciated greatly!
[G1 Android Development] justanothercrowd:
you are incorrect multi-touch effects apps other than the browser in 1.41
[G1 Android Development] Dharkaron:
It may cause problems but it doesnt work properly. The app would have to be coded to work with the hack. I dont know of any apps that have been coded to work with this hack.
[G1 Android Development] uberingram:
It's off by default. Just go into your browser settings and uncheck what you checked in the first place.
[G1 Android Development] rub1k:
I don't know much about it (multi-touch) but if it's built into the OS and (allegedly?) leads to some quirks here and there (does it?) I don't understand how you can turn it off from the browser...

I'm sure there are a lot of us who don't care about multi-touch at this point, so I would agree with the OP that it would be nice to have the option of a modified RC33 *without* multi-touch.
[G1 Android Development] dwang:
I would like to add my request as well.

Its off by default in the browser but the kernel is still hacked to sense multi-touch which causes issues with certain apps. This is because the hack uses an existing field to sense the 2nd finger. So apps that actually use that field for legitimate purposes don't work correctly.
[G1 Android Development] Linuxslate:
Pls add me to the requests for a no-multi-touch version.

It is my understanding that you can turn auto rotate on and off in the browser, but not multi-touch.
[G1 Android Development] twistkill:
there are the highest chances that multi-touch wont be included in cupcake..that is in the original unmodified update..
[G1 Android Development] aukicadeso:
Which apps are having issues? Somebody mentioned Steamy Windows in another thread... what other apps are having issues. I like the auto-rotate/multi-touch functionality in that order.
[G1 Android Development] TheDudeOfLife:
I was having issues where my home screen would skip back and forth. I also had issues clicking the proper menu options/icons.

So yeah count my vote in too.
[G1 Android Development] I7oobie:
OMG, how many threads are you going to post this in? I've counted about 4. If your steamy windows app doesn't work on JF v1.41, go back to non-rooted. I took a look at your past 15 posts, and it all relates to the multi-touch. Version 1.31 didn't have it, you could use that...

/rant
[G1 Android Development] acousticdank:
Honestly, beggars can't be choosers.

If JF chooses to not implement this, I think it'd be a step back. You are all welcome to go back to 1.31 or even use the nonrooted version... or better yet, come out with your own version of root.

But, ultimately it's up to JF, and I really hope he doesn't waste his time making two separate versions of 1.33. Ofc, if you really want him to listen to you, don't be a beggar, and be a supporter. :eek:

https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=1014600
[G1 Android Development] rub1k:
If JF doesn't do it, someone else probably will... which is perfectly fine. Nobody is knocking JF if he won't do this.

I think people are just asking (kindly, I don't see anyone being a jerk about it honestly) for a "vanilla" RC33... As in, exactly as it came from Google except WITH root access added back in. No extra stuff, no recompiled kernel, no extra modules, nothing but root access added back in.
[G1 Android Development] justanothercrowd:
All of my posts are about it because it is the biggest issue with people in the 1.41 build.

The stock RAW image viewer does not work properly either...or cracked screen app....just becasue the apps that take advantage of the second field arent great right now doesnt mean that this isn't an issue. It could end up being a big issue since most dev's don't develop for hacked ROMS.

And for your info I have been running 1.31 for the past few days. I just don't want to see this hack pigeon hole users into not being able to use certain apps. I would like to be able to take advantage of future releases without having multi-touch.

Currently it is only a benefit in the browser and the stock zoom works much smoother, and in the rest of the OS it is a bother.

I will continue to voice my concern and it appears that quite a few others have the same concern.
[G1 Android Development] I7oobie:
Feel free to ask all you want. I think it might fall on deaf ears. The point I was trying to make, is that it's not necessary to post in 4-5 different threads. I think one thread would be sufficient enough...
[G1 Android Development] dwang:
I agree with justanothercrowd. I'm all for the multi-touch hack, but the fact that its using an existing documented field is an issue.
[G1 Android Development] afoulke:
I believe if you search the threads JF has already answered this question or it has been at least brought up. The only problem that was really brought to light was the steamy app. Really I think this would be a huge hassle for JF who works for free to have to update two versions every time an update is to come out maybe a simple setting to turn it off would be easier and more likely.
[G1 Android Development] justanothercrowd:
a setting would be great. and im more than willing to contribute $$$ for the extra time spent. i would recompile my own but im not that savvy with the android platform yet.

any feedback jf?
[G1 Android Development] vettejock99:
Thanks - that is what I thought. Guess I'll be requesting CupcakeJF soon.
[G1 Android Development] AustinKnight45:
O no my multi touch wont let me play with my cracked screen app:(......really, come on now JF makes a bad ass mod with multi touch and people complain about a app that has no real use. Downgrade to RC29 then to RC30 and then to the RC33 HERE:http://xdaforums.com/showthread.php?t=479571 and you'll have your cracked screen app working perfect again lol
[G1 Android Development] dwang:
how do you know in the future somebody won't come out with a bad ass application that uses the field the multi-touch hack overrides and then everybody will be screaming for jf to remove the hack.
[G1 Android Development] metallicant:
I say leave everything be or if anything, have an option to turn multi-touch off or on. JF is a genius and whichever he feels the need to do so let him decide for himself.

Keep Auto Rotate, Multi-Touch, and Wifi Tethering going, just give us RC33 with a simple download to pc, install to phone, updated, and all three features (2 of the three actually) from 1.41RC30 still intact.

I want this update to be as simple as possible like it was with 1.41 without having to go back and get wifi tethering to work again and such..

By the way thank you so much JF
[G1 Android Development] AustinKnight45:
Then downgrade to JF 1.31 already.
[G1 Android Development] dwang:
Why? I don't see what the big deal is in leaving out multi-touch. Its just the stock kernel. Its not like JF has to do anything extra.

Its more work to compile in the multi-touch.
[G1 Android Development] Obsidiandesire:
No offence, but by now I hope developers will have realised that most people have a multitouch enabled G1, and anybody who cares about their app will update it so it doesn't conflict (Which sounds like an easy thing to fix), that way people won't whine. If multitouch was disabled by default, yet enabled in the kernel in an official release, would we have these problems? And would people be asking for versions "Without" Multitouch? I doubt it... but I could be wrong. Present me with valid evidence, I like to be corrected, it makes me learn more (Just don't correct my opinions for the love of God)
[G1 Android Development] dwang:
MT is compiled in the kernel, that means u can't enable/disable it based on the application. Its global..
[G1 Android Development] savethechicken:
Just my 2 Cents but for those that dont want the releases as they come from JF. If I remember correctly the source is available in the same post as the release so that you can do what you want with it. I can't do it, but he can't be the only person that knows enough to code this. You can't ask someone to take on more work for a few when the majority of us do like this hack. JMO
[G1 Android Development] AustinKnight45:
I think he might like the multi-touch feature ya know, he does all the work on these modes so keep telling him that your cracked screen app doesn't work and that's why you want him to take it out for now I don't know, think of something really good though.
[G1 Android Development] dwang:
I'm not saying he has to exclude it. Just provide 2 versions. The non-multi-touch version should barely take any additional work to provide.
[G1 Android Development] justanothercrowd:
Okay...again with the disinfo. Rooted G1's will never be the majority. Just like jailbroken iphones never will be just like overclocked computers never will be.

There aren't any developers I know of that are developing for the hacked multi ROM...only root access, which would make the application that takes advantage of multi not work for everyone else...which again IS the majority.

My point is we need root and extra features but not to the point that we limit what we can do as far as compatiblity with "official" apps.

Multi-touch will be implemented down the road as an API update according to the rumbling going around the google forums.

And I'm just curious, exactly what benefit are you guys seeing from the multi-touch? the only thing I've ran into is problems and no benefits. The broswer can benefit from it but as of right now it's more of a "hey my phone has multi-touch like the iphone" thing but that's about it.

It is great that we have proof of the concept with apple's patent's and all but I really don't see the benefit besides messing up other applications now and potentially in the future.
[G1 Android Development] rub1k:
Wow... I can't believe this thread is still going.

Nobody is demanding anything here.

Someone made a request (for valid reasons, whether some disagree or not).

If someone out there (JF *or* someone else; it doesn't matter who) is able to provide what's being requested, great. If not, oh well, it's not the end of the world.

I cannot comprehend why some of you are essentially saying "umm... no, you are stupid for requesting such a thing.. go away!"
[G1 Android Development] justanothercrowd:
I don't get it either...people are acting like I am disregarding JF's work (which I really appreciate) and asking for something unreasonable. No need for people to get upset.
[G1 Android Development] topdnbass:
Is it wrong to request?

No!

Anyone will agree that multitouch is more of a gimmick & proof of concept than functional.

The fact that its not too functional and ALSO hinders the functionality of other apps is what's getting to some people.

I personally don't use multitouch too often at all, other than when I want to show someone that it's possible.

As always, kudos to JF and Koush for their great work.

Respect is given where deserved.

However, many of us request just root, without the added gimmicks.
[G1 Android Development] rub1k:
Exactly... some (quite a few people, I assume) only want the root access added back in and NOTHING else.

There are instructions out there on how to manually add that into an image and (re-)sign it (using test keys), aren't there? I swear I saw some on here a long time ago...

So, at the very least, we know it's easily doable so someone will do it eventually (hell, I'll take a crack at it if nobody else beats me to it).
[G1 Android Development] nolageek:
I don't think the issue is you (and others) requesting it, but that you've whined about this on like five threads. At least you have your own now.

If an app other than Steamy Window breaks because of this, I'll be all for it being fixed, but I see no other app that's affected.
[G1 Android Development] rub1k:
My bad on that part; I didn't see other threads or bothered to look for any, really... but yes, this subject doesn't need more than one thread, you're absolutely right.

As to your second point, I don't think it has to do as much with a (crappy and useless, let's be honest) app. breaking because of multi-touch.. rather than with not wanting/needing the other stuff (new kernel, modules that 99% of people don't use, new/more binaries, etc.)... And it's no offense to the author of the modded release... It's just that some people just prefer to have root access only... and if they want other neat things to play with, they'd rather add those manually themselves since they would have the ability to do that.
[G1 Android Development] danguyf:
I'd like a version without multitouch. I love having multitouch, but not at the expense of over-riding an existing field that, it turns out, actually *is* used.
[G1 Android Development] topdnbass:
Ok so JFs new ROM is out and multitouch is included.

Who wants to team up and make a version without multitouch :)

I always thought it was just the browser.apk that was altered.
[G1 Android Development] dskyers:
how do i get keyboard

i see that you said something about full time keyboard where can i get it and how do i install
[G1 Android Development] justanothercrowd:
I am going to be compiling a new RC33 ROM including root access etc with the official kernal from RC33 that doesnt have the multi-touch code.

I spoke with JF and he helped me out with some unanswered questions. Give me 24 hours or so to get this complete. I am hoping to be able to finish it early tonight once I get off work. It will be made available to the community.
[G1 Android Development] JesusFreke:
Not recommended ;). A lot of the included modules most likely won't work.

Grab the kernel from JFv1.31 instead.
[G1 Android Development] justanothercrowd:
Will do.

Any word on undocumented changes in the RC33 kernal?
[G1 Android Development] bmfc187:
hi, im joining the request for NO multi-touch...i wouldnt use it a bit, i hardly ever use the browser anyways...only when im out and about, cuz i have my laptop at work and PC at home, so i never really need to use the phone's browser...im sure this will cause some to stay on an older version and miss out on the features brought to us thru updates, for fear that their phone will be screwed up by a feature that they didnt even want to begin with.
[G1 Android Development] acousticdank:
How is your phone gonna be screwed up? You can go back to the factory stock version anytime you want (as of now). JF has taken time to get us this far, I'm pretty sure it's gonna be ok for him to revert to non-multi touch if and when Google actually implements it (which I doubt they will).

So far you do not lose any functionality except with some apps like Steamy.

If people are such a worrywarts then why are they even rooting their phones in the first place? o.O Do they not realize that technically even rooting could be potentially "fatal?" :confused:
[G1 Android Development] quietlurker:
Here's a build using everything from RC33 except for the multi-touch kernel, the kernel is the old JF1.3 one. Just do what you always do with the update.zip (Power off, Power on + Home, etc.) If you're going from any other build except JF 1.4, I'd recommend a wipe to be on the safe side.

http://drop.io/jf141nomt

I haven't tested it extensively, but everything I did test seemed to work fine.

And for reference, JF, through his build environments, has pretty much provided everything anyone needs to build their own forks, add/remove applications/binaries, etc. In the future I'd encourage anyone who wants a specific feature added or removed to look into it.
[G1 Android Development] The_Kills:
You havent have had enough time to do extensive testing? . Multi-touch was something we didnt want present, because we saw it how it affect some apps, and the brower's performance. The only problem with your update, is while multitouch is gone. So is the whole browswer itself in a nutshell.

Not truely gone, but when you try to use it, you get the browser window come up for just about a second and then it just disappears terminating itself most likely.

There is no error message or "wait or force close" option...it just goes away right when you fire it up.

How did you manage to get this to happen? If you can get the broswer to work, that would be awsome, as everything else works without flaw, even the market app like everyone else complains it doesnt. (oh and I think my Wifi isnt working, it wont obtain my IP address for some reason)

My FW history if it helps: FW rc30>rc29>rc30JF1.3>rc30JF1.4>rc30JF1.3>your firmware.
[G1 Android Development] quietlurker:
That's strange because on mine, the browser is working fine. Did you try wiping before applying the update? I did test the browser, the dialer, and maps+latitude.... however, if you feel you can do a better job, please do. I built this for myself and thought I'd share the .zip for the hell of it. Just goes to show no good deed goes unpunished around here.
[G1 Android Development] The_Kills:
Oh cmon I was not offending youin the slightest, in fact awfully greatful and was waiting for it. Oh and I did no sort of wipe at all, I think I should just reflash once more and see if I get any other result. Hope you excuse my poor choice of words. Ill let you know how it goes.
[G1 Android Development] The_Kills:
Oh and I noticed your using the 1.41 recovery build, nice touch ;)
[G1 Android Development] The_Kills:
Oh you didnt need to post pics lol I believe you, lol heck if the creator of something is lying, that would just be stupid. But yah, I just performed wipe + reflash. And just waiting on the completion
[G1 Android Development] The_Kills:
Ok still the same problem. Just to be sure, are you on the same exact update.zip that you uploaded ?
[G1 Android Development] The_Kills:
Alright, still the same issue, the brower opens and closes right after, after trying the following:

Wiping and rebooting.

Wiped and went to ADP1 (browser worked)

Wiped and went to JF 1.4 rc33 (browser worked with multitouch)

Wiped and went to your firmware (same issue)

Wiped and went to JF 1.3 RC30 (browser worked)

Wiped and went to your firmware (same issue)

Wiped and went to ADP1 (browser worked)

Wiped and went to your FW (same issue)

Wiped and went to JF 1.4 RC30 (browser worked)

Wiped and went to your FW (same issue)

It'd definately the update.zip your providing, also i notced that it takes a longer time to copy the file than the other FW's, when the bar fills up, it stays there for quite a while, as if its failing at somethingand finnaly giving up and moving on to formatting and writing the BOOT.

I basically tried going from 1.3 RC30, ADP1, and 1.4 RC33, and 1.4 RC30, all to your firmware,so it's definately not a "going from this firmware issue" because not only did I try every firmware, I also wiped everytime.

Try out the build you uploaded I think you might have missed something.
[G1 Android Development] acousticdank:
lol, man, talk about being an ingrate. it sure is a poor choice of words.
[G1 Android Development] The_Kills:
: sorry

*sigh*

I guess ill stick with rc30 1.31 it should suffice.
[G1 Android Development] jamesd86:
yeah, the build he offered was a no go.

though i will say this, thank you for your effort! I was actually trying to do the same thing myself but am stuck in what to do with JF's build environment. keep at it and i'm sure you'll get it!
[G1 Android Development] The_Kills:
So it wasn't just me right?