I like the concept. It's a different direction for home replacements. Aside from their unique little options, all of them are really quite similar. Given that I haven't seen this in action except on the video, and can't be sure how much of that is edited to show what it COULD be like, I won't comment either way on what I think about it, other than I like the idea and have already signed up to try to test it out. If I don't get in on that, I'll definitely be looking for it in the market after that initial test!
DroidForums.net | Android Forum & News
This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
New 3D Home Replacement Coming Soon
- Thread starter unix.punkx
- Start date
M
Matth3w
Guest
Yeah I didn't see an ounce of lag...and someone said it was on the Hero which is slower if I'm not mistaken.
SinCitySRT4
Member
it looks pretty sweet lets see how it runs on daily use
M
Matth3w
Guest
+1 here. But I guess we wait and see
jacestone40
Member
That was a impressive display to be honest...I have tried GDE and others will try Sweeter Home next maybe DXtop so TAT Home is worht the try
One thing just has to be for sure, if you desire to use this and also desire to overclock, no way in hell. Even if it didn't conflict, your battery would be depleted so fast it would create a vacuum in your phone, and it would be spaghettied by the black hole it created.
That said...the graphic rendering is fantastic on that demo. Holy crap.
That said...the graphic rendering is fantastic on that demo. Holy crap.
M
Matth3w
Guest
You don't know that for sure yet.
Where'sMyCoffe?
Member
Hmmm... how can the coders do this?
Lets see... according to my coding calculations... if the coders of this beautiful home replacement... depletes, nulls, and relinquishes the native home process completely, while having an IF ELSE coding scheme to call upon the default home launcher IF the home replacement crashes and the IF is false in the sense of the home replacement cannot relaunch itself... ELSE would call up the native home launcher.
After all, the native home launcher is on the system of course... maybe these codes here have found how to call upon it, without it running in the background.
Unfortunately the home "replacement" applications you all use, isn't really a "replacement", more so they are "facades" all the while the kernel of the system is still running the native home launcher.
The paging of the system could have many page faults... with both home launchers running, thus every time you run a stand-off application, like for example Gallery, etc... the system pages its memory basically seeing what will run what... this stuff can get icky.
Like I said, hopefully these coders are brilliant in the sense that they killed the native launcher. But even if they haven't found a code to distinguish the native home launcher, hopefully they have found a more efficient... power and resource efficient compensative.
Coding is fun, trust me. Not! lol no, it really is...
Lets see... according to my coding calculations... if the coders of this beautiful home replacement... depletes, nulls, and relinquishes the native home process completely, while having an IF ELSE coding scheme to call upon the default home launcher IF the home replacement crashes and the IF is false in the sense of the home replacement cannot relaunch itself... ELSE would call up the native home launcher.
After all, the native home launcher is on the system of course... maybe these codes here have found how to call upon it, without it running in the background.
Unfortunately the home "replacement" applications you all use, isn't really a "replacement", more so they are "facades" all the while the kernel of the system is still running the native home launcher.
The paging of the system could have many page faults... with both home launchers running, thus every time you run a stand-off application, like for example Gallery, etc... the system pages its memory basically seeing what will run what... this stuff can get icky.
Like I said, hopefully these coders are brilliant in the sense that they killed the native launcher. But even if they haven't found a code to distinguish the native home launcher, hopefully they have found a more efficient... power and resource efficient compensative.
Coding is fun, trust me. Not! lol no, it really is...