Database Info

New Faster HTC Sense UI out today!

http://www.engadget.com/2009/09/14/htc-hero-firmware-update-peps-up-the-sense-experience-to-somethi/
Good news for HTC Hero early adopters: HTC has a new firmware update out now for the device that considerably speeds up the interface, if the multitude of reports to be found on the internet can be believed. Seeing as this was the number one gripe with the overall excellent UI, we're incredibly glad HTC has gotten work on this, and we'll be spending some more time with the device to return our newly tinted impressions. There's a video after the break demonstrating changes, and most actions seems quite a bit quicker and smoother, all the way down to opening and closing the apps menu, and sliding between home screens.
Click to expand...
Click to collapse
I hope the devs are able to snatch up a copy of that and get it into our already awesome roms! I vote for MyHero 0.1.1 myself

Wow. WRONG SECTION.
Okay, you do realize that it's the KERNEL that provides an increase in speed for the Hero ported builds, right?
Well, if you didn't...now you do. The build number does not matter. As for that OTA update that HTC is delivering, that comes standard with the HTC kernel that XDA had ages ago...and is NO LONGER in use. Most developers are using 2.6.29.6 - not 2.6.27! You do the math and figure out which would be more recent. JAC and CC's latest is based on the 2.83 build. While Drizzy's latest is based on the 2.86 build.
That HTC update is only the 2.73 build packaged in-full.

Reignzone said:
Okay, you do realize that it's the KERNEL that provides an increase in speed for the Hero ported builds, right?
Well, if you didn't...now you do. The build number does not matter. As for that OTA update that HTC is delivering, that comes standard with the HTC kernel that XDA had ages ago...and is NO LONGER in use. Most developers are using 2.6.29.6 - not 2.6.27! You do the math and figure out which would be more recent. JAC and CC's latest is based on the 2.83 build. While Drizzy's latest is based on the 2.86 build.
That HTC update is only the 2.73 build packaged in-full.
Click to expand...
Click to collapse
Hmm... That's not quite correct. That's like saying MS Word is slow because of the Windows kernel. MS Word is most of the problem...
Yes, the devs here have done some great stuff squeezing more speed out of the kernels with swap partitions and BFS - but that is only half the equation. Sense UI is an APP that run on top of the kernel, so it stands to reason that HTC could have optimized the code in Sense UI (and other apps) to improve performance.
-V

Reignzone said:
Okay, you do realize that it's the KERNEL that provides an increase in speed for the Hero ported builds, right?
Well, if you didn't...now you do. The build number does not matter. As for that OTA update that HTC is delivering, that comes standard with the HTC kernel that XDA had ages ago...and is NO LONGER in use. Most developers are using 2.6.29.6 - not 2.6.27! You do the math and figure out which would be more recent. JAC and CC's latest is based on the 2.83 build. While Drizzy's latest is based on the 2.86 build.
That HTC update is only the 2.73 build packaged in-full.
Click to expand...
Click to collapse
Yea, this is really not accurate at all. The patched kernels help with things like compcache, bfs, etc but the app/ui itself is what has been optimized in this release and is SIGNIFICANTLY faster than the 1.73.xxx version, even using the same HTC kernel.
Also, WRONG FORUM!

what i am looking forward to is the sense ui they said will come native to htc magics. we wont need to port the hero one anymore when that comes. hopefully soon, october was the month rumored.

vro25 said:
Hmm... That's not quite correct. That's like saying MS Word is slow because of the Windows kernel. MS Word is most of the problem...
Yes, the devs here have done some great stuff squeezing more speed out of the kernels with swap partitions and BFS - but that is only half the equation. Sense UI is an APP that run on top of the kernel, so it stands to reason that HTC could have optimized the code in Sense UI (and other apps) to improve performance.
-V
Click to expand...
Click to collapse
Hate to correct you here when trying to prove me wrong but;
ROSIE is the APK that runs over SENSE, not the other way around. The userinterface integrates itself with the OS.
And yes, I am more correct than not. Microsoft has nothing to do with Android. That's an entirely different ballpark, regardless of whether or not they are both operating systems. That comparison is irrelevant...considering "BFS" is not packaged with Microsoft kernels. The End.

Again.
hakeem9 said:
Yea, this is really not accurate at all. The patched kernels help with things like compcache, bfs, etc but the app/ui itself is what has been optimized in this release and is SIGNIFICANTLY faster than the 1.73.xxx version, even using the same HTC kernel.
Click to expand...
Click to collapse
The official build is not optimized. It's an official release, therefore it's a feature-rich build. HTC does not cut-down the applications list, widgets, etc. because the company has standards based on increasing speed and reliability whilst not having to sacrifice any adds-on. The optimization you speak of is only relevant HERE...at XDA, because the Hero ported ROM developers OPTIMIZE them by removing applications, widgets, and various other things packaged BY HTC within their official build to increase responsiveness on OUR devices that do not necessarily have the abilities to operate at a caliber comparable to the HTC Hero. (Run-on sentence, I know, I know.)

Reignzone said:
The official build is not optimized. It's an official release, therefore it's a feature-rich build. HTC does not cut-down the applications list, widgets, etc. because the company has standards based on increasing speed and reliability whilst not having to sacrifice any adds-on. The optimization you speak of is only relevant HERE...at XDA, because the Hero ported ROM developers OPTIMIZE them by removing applications, widgets, and various other things packaged BY HTC within their official build to increase responsiveness on OUR devices that do not necessarily have the abilities to operate at a caliber comparable to the HTC Hero. (Run-on sentence, I know, I know.)
Click to expand...
Click to collapse
You obviously do not like being wrong and obviously have no programming experience either. If they have optimised sense ui ofcourse its not just the kernel. When programming there's plenty of different ways you can get the software to produce a result to end user. if they tidy up the code and compact it down ofcourse you can make it more speedy and efficient.
replies

Reignzone said:
Hate to correct you here when trying to prove me wrong but;
ROSIE is the APK that runs over SENSE, not the other way around. The userinterface integrates itself with the OS.
And yes, I am more correct than not. Microsoft has nothing to do with Android. That's an entirely different ballpark, regardless of whether or not they are both operating systems. That comparison is irrelevant...considering "BFS" is not packaged with Microsoft kernels. The End.
Click to expand...
Click to collapse
Ok, seriously, the biggest problem with the Hero rom performance is the shell called touchflo. If you take a hero rom and use the regular home instead of touchflo the performance is night and day better. This is obviously not because of any change in the kernel (since the only change was the home shell). Based on that, I would say that HTC could improve what they collectively call Sense UI very easily by improving the shell portion of the equation.

Since my question was pointed towards the new HTC release and merging it with the current roms, that to me would seem like a DEVELOPMENT question. I also got many great answers on here that all seem like DEVELOPMENT type answers.
Right Forum. Thanks for the replies so far everyone. Hopefully we can determine if HTC released changes to the Sense UI application that the devs already had or if these are new changes (not Kernel).

If Im not wrong most of the Hero builds around here are already based on 2.73, including myhero.
Also, the increase in speed is more than just the kernel. Although a scheduler like BFS can increase the performance, the 1.7x Hero builds are much slower than the 2.73. I remember one of the Hero devs saying that the 2.73 Rosie.apk is way smaller than the 1.7x one.
Anyway, just take any 1.7 Hero build and compare it to a 2.7 build, hopefully both without BFS. I'm sure you will find that Rosie is generally more responsive.

If Im not wrong most of the Hero builds around here are already based on 2.73, including myhero.
Also, the increase in speed is more than just the kernel. Although a scheduler like BFS can increase the performance, the 1.7x Hero builds are much slower than the 2.73. I remember one of the Hero devs saying that the 2.73 Rosie.apk is way smaller than the 1.7x one.
Anyway, just take any 1.7 Hero build and compare it to a 2.7 build, hopefully both without BFS. I'm sure you will find that Rosie is generally more responsive.

Reignzone said:
Hate to correct you here when trying to prove me wrong but;
ROSIE is the APK that runs over SENSE, not the other way around. The userinterface integrates itself with the OS.
And yes, I am more correct than not. Microsoft has nothing to do with Android. That's an entirely different ballpark, regardless of whether or not they are both operating systems. That comparison is irrelevant...considering "BFS" is not packaged with Microsoft kernels. The End.
Click to expand...
Click to collapse
Wow. Where to start...
Yes, you're right - Microsoft has nothing to do with Android - I was stating an example of an App vs. an OS Kernel. You clearly missed what was a fairly obvious comparison. That make me wonder the type of person we're debating with - as it seems it's everyone against, well, you. But go ahead and stick to your guns.
My point was, kernel enhancements being done here are - for the most part - to optimize the build so it runs on inferior hardware (Dream, Magic 32B). BFS is a different beast altogether and a welcome add-on.
HTC managed to speed up Hero without resorting to BFS, this is because most speed improvements in the UI come from improvements in the Rosie.apk - hence the devs here "slimming" it down to use less memory and run better on non-Hero hardware.
Of course, that's not to say that some of the latest Hero builds aren't already using parts of this official Hero build - they all come from official Hero builds (leaked or otherwise).
The point is you are absolutely wrong in your argument that performance gains only come from kernel version increments. So you can either get over it and learn something - or you can keep arguing with everybody. Frankly I've already spent enough time on you and if you don't get it by now you probably never will so there is no point in continuing any further... But I'm sure others will probably want to have some fun at your expense if you still refuse to see the light.
I have a feeling this isn't the first time you've been corrected and I'm positive it won't be your last. As such, you shouldn't be so quick to jump on others.
Do you know the saying, "a little bit of knowledge is dangerous..."
;-)

You know, for a really good example of how it's not the kernel that determines the speed of everything, just think of how your market apps get updated all the time and how some will say *speed improvements*. The app gets updated to utilize the hardware and performance available and in turn improves its own speed better. Now the kernel does determine a great deal, but the apps are just as important with how they're coded. I would say these leaked kernel's are probably better than the new Rosie update, however there may be optimizations in the rosie ui, or other apps, that I'm sure the devs will rip or have already ripped that will continue to make our lives interesting in the coming days!
This forum is freaking amazing and you all are what make the experience here so enjoyable! Thank you all, especially you devs for making this such a great community!
~*Apollo*~

[DEV] Running Hero ROM on 32A with new radio and SPL

Hi all!
OK, so I had some spare time on my hands this afternoon and I came up with something pretty neat.
Ever notice how the HTC Hero and the HTC Magic 32A are nearly identical in specs? Same processor, same ROM, same RAM... Then why do all these devs port the HTC Hero ROMs over to 32B/Dream and then we get to try to port them to 32A? It always ends up being a mess of custom work and the problem of 'too many chefs in the kitchen'. I'm not slamming anyone's hard work here, but I wanted to find some other way.
The HTC Hero uses nearly identical radio and SPL as the new radio and SPL for the Magic 32A.
http://android.modaco.com/content/h...-24-11-hero-roms-radios-in-update-zip-format/
My device:
HTC Magic 32A
Radio: 6.35.07.29
SPL: 1.76.2007
Hero ROM used - HTC Generic 2.73 (rooted)
Changes Made that affect functionality:
- replaced boot.img and wlan.ko from CursorSense32A-0.3
- Umm, that's it...
What works:
- Wifi
- Camera
- LEDs
Untested (because I'm at work!)
- Bluetooth (pairs with my laptop, but can't test audio or a2dp)
Cosmetics
- Bluetooth name is HTC Hero
As you can see, it already works better than the initial HTC Hero stuff we got from the Dream devs before.
Am I stupid? Why did I do this when there is already a proper HTC Sense ROM for the Magic 32A? Because right now the Dream/32B devs have in their possession the HTC Hero 2.1 image and it's being ported to 32B/Dream. And now we're left trying to port these ROMs to the 32A platform. It's kinda like driving from New York to Toronto via Mexico City.
I'm excited to try some of these tactics on the Hero 2.1 ROM. I'm sure it'll work very much the same.

Why so many threads?

awesome work cursor!
This will probably kick start the Magic 32A development and the Rogers Dream.

maxisma said:
Why so many threads?
Click to expand...
Click to collapse
I prefer to keep a thread on topic and not always change the subject. This is a new topic.
Mods merge if necessary.

If you get it working I would be more than happy to update my SPL.

will the flash cause the it to become perfect SPL?

radonsg said:
will the flash cause the it to become perfect SPL?
Click to expand...
Click to collapse
Anything you see from me will only use an eng SPL.

Awesome
Keep up the great ideas. Now this really something I'd like to see developed. Sounds like this could really clean up some code for us who own the Rogers Magic
Thanks

cursordroid said:
Changes Made that affect functionality:
- replaced boot.img and wlan.ko from CursorSense32A-0.3
- Umm, that's it...
Click to expand...
Click to collapse
I can confirm this method works since I just did the same thing.
unfortunately, it did not work on new Hero 2.1 ROM. The screen stay black after HTC magic logo.

I am in
Keep it up. I can also Make Testing and even Making ROMS

Just tried Hero-ASOP 1.6 and its running. No wifi, camera, etc. but everthing else seems good.
And by everthing else I mean google synch, maps, browser, market.

Android Source 2.1 released! Now we just need the kernel

Looks like 2.1 was just released! Woot!
Looks like the changes are just being put into the git as well.
Now we are just left waiting for the kernel source drop so we can take advantage of the nifty 3d acceleration stuff.

dchadwick said:
Looks like 2.1 was just released! Woot!
Looks like the changes are just being put into the git as well.
Now we are just left waiting for the kernel source drop so we can take advantage of the nifty 3d acceleration stuff.
Click to expand...
Click to collapse
hmmm I didn't think about this only sounding exciting to me.

dchadwick said:
hmmm I didn't think about this only sounding exciting to me.
Click to expand...
Click to collapse
You are certainly not the only one. Once we get the kernel source will we finally begin to see a healthy amount of ROMs?
I really miss my G1 simply because of the sheer amount of options I had.

illogic6 said:
You are certainly not the only one. Once we get the kernel source will we finally begin to see a healthy amount of ROMs?
I really miss my G1 simply because of the sheer amount of options I had.
Click to expand...
Click to collapse
I miss my G1 too and if the Nexus Wasn't only compatable with T-Mobiles 3g network it would be tempting with the kernel in the Android Source tree and Cynanogen building roms for it.

illogic6 said:
You are certainly not the only one. Once we get the kernel source will we finally begin to see a healthy amount of ROMs?
I really miss my G1 simply because of the sheer amount of options I had.
Click to expand...
Click to collapse
We won't get kernel source compatible with 2.1 until after HTC releases a 2.1 ROM for the Hero, if even then (since HTC thinks they are immune to the GPL). Some bits from the 1.5 kernel source will be useful for uprev'd Android releases, but it will not bring the full feature set.

cmccracken said:
We won't get kernel source compatible with 2.1 until after HTC releases a 2.1 ROM for the Hero, if even then (since HTC thinks they are immune to the GPL). Some bits from the 1.5 kernel source will be useful for uprev'd Android releases, but it will not bring the full feature set.
Click to expand...
Click to collapse
Nah, I think your exactly right. Any kernel release at this point would be helpful.

cmccracken said:
We won't get kernel source compatible with 2.1 until after HTC releases a 2.1 ROM for the Hero, if even then (since HTC thinks they are immune to the GPL). Some bits from the 1.5 kernel source will be useful for uprev'd Android releases, but it will not bring the full feature set.
Click to expand...
Click to collapse
Given the kernel source I am fairly sure we could reverse the rest in a few days, the only thing keeping us back now is the lack of a frame of reference on exactly what they did to make CDMA work on GSM code.

Nanan00 said:
Given the kernel source I am fairly sure we could reverse the rest in a few days, the only thing keeping us back now is the lack of a frame of reference on exactly what they did to make CDMA work on GSM code.
Click to expand...
Click to collapse
There isn't much difference between the gsm kernel and cdma kernel with regards to radio functions. The kernel's job here is to present devices after boot, so that libhtc_ril.so can communicate to the hardware (/dev/qmi# and /dev/smd#). If you look at the code in gsm kernel, there is very little there, all the hard stuff is in the black box libhtc_ril.so. The shared library is called through the system_server process, which ends up being called by the framework, which is called by the phone app (or some other app) to make calls, send sms, etc. Notice that all it really took to get the leaked 2.1 working for basic phone functions was a config change in build.prop, telling the RIL to expect/use CDMA instead of gsm/umts.
The above can be said for other areas where we have difficulties, camera, sensors, lights, etc. All the kernel does is present devices or memory areas that user space things can manipulate. This allows HTC (and other phone makers, like Motorola or Ericsson) to keep their "important" code away from the GPL'ed kernel. A side effect is that when changes are made in Android where it expects stuff in /dev that are not present in the .27 CDMA kernel. This is why sensors and other stuff doesn't "just work", the 2.x code expects things that are not present in the only kernel we have.
Finally, Android framework is for the most part Apache licensed, hence why HTC and other phone makers are not required to release their changes to the Android system. This is why I had to reverse engineer the changes HTC made to send MMS on Sprint, for example. They had no obligation to publish those changes.

[THINK TANK] FROYO W/ 10...5...2Mb ram hack?

What do you think. 10mb is too much because you can't play 3D games, but maybe 5mb or 2.5mb ram hack? Thanx
sent from my G1 using CM7 IN-STEREO (( WHERE AVAILABLE ))

jp2dj1 said:
G1 using CM7
Click to expand...
Click to collapse
Where your timemachine parked?

not gonna happen, try swapper activator from the market this allows u to hold a swap on fat32 else format your memory card and use one of the scripts to enable swap on the swap partition. Only way to increase memory...

Killadude said:
not gonna happen, try swapper activator from the market this allows u to hold a swap on fat32 else format your memory card and use one of the scripts to enable swap on the swap partition. Only way to increase memory...
Click to expand...
Click to collapse
True, but everyone is saying that swap makes froyo roms a bit unstable. That's why I thought a 5mb ram hack.
P.s 100% you'll see an improvement in a ram hack rather than the swap. That's what people are looking for.
sent from my G1 using CM7 IN-STEREO (( WHERE AVAILABLE ))

jp2dj1 said:
True, but everyone is saying that swap makes froyo roms a bit unstable. That's why I thought a 5mb ram hack.
P.s 100% you'll see an improvement in a ram hack rather than the swap. That's what people are looking for.
sent from my G1 using CM7 IN-STEREO (( WHERE AVAILABLE ))
Click to expand...
Click to collapse
I would have to disagree, swap was giving no issues on several roms for me and 5+ other G1 users on the same roms. Compcache was giving us all issues, but only a few random reboots on occasion, or a FC or two.
However I am hearing that CC works fine as of the latest cyanogen release. I think the issues some people are actually having is ending up with both swap and CC on since the "default" settings changed over to cc.
As for the ram hack? I've not been having memory issues in froyo as far as a shortage on ram. I use swap, and have used it since I first rooted and etc. but I think I'll give CC another try now that cyanogen is recommending it. I'd rather have a good "3D fix" like what firerat did with his script on 2.1 roms, I don't think it works with 2.2 roms from what I read, but I would like to have LWP running like they did on 2.1
Just my two cents

Ramhack is not even possible on the newer kernel branches, plus 2.1+ is very dependent on 3D that it wouldn't make sense to add a "ramhack". it cripples 2.2 if you would do so..Go ask dumfuq or pershoot and they'll tell you that no ramhack will work for 2.2 .

Ace42 said:
Ramhack is not even possible .
Click to expand...
Click to collapse
Dude.... don't say that. We're talking about android here. Really, a 2mb ram hack will completely cripple any 2.2 roms?!
Sent from my HTC Dream using CM7 IN-STEREO (( WHERE AVAILABLE ))

Before anyone of you attempt this, adding swap file to your devices grants you the ability to run more processes, sure, but what you fail to realize is the devices almost constantly writes to the swap file.which uses up CPU cycles, causing your device to be a bit slower, also, flash memory, regardless the.format, has limited number of writes, adding a swap file makes the device write almost constantly,.reducing the overall lifetime of your flash memory. Adding a swap file isnt the best idea if you're looking for speed increase.
Sent from my SGH-T959 using XDA App

I thought Android 2.1 starting utilizing the GPU more, making the ramhack infeasible because it will severely degrade screen rendering performance from Android 2.1 and up.
Compcache is okay. Don't swap if you can help it.

xaueious said:
I thought Android 2.1 starting utilizing the GPU more, making the ramhack infeasible because it will severely degrade screen rendering performance from Android 2.1 and up.
Click to expand...
Click to collapse
Okay? People remember when 2.1 was way unstable then openeclair 2.1 w/ 10mb ram hack made it at least toyible (I know that it's not a word). I didn't in anyway make it severely degradable...
Sent from my HTC Dream using CM7 IN-STEREO (( WHERE AVAILABLE ))

I can see your not going to be convinced easily....If it was possible dumfuq o pershoot would have made a kernel with the ram hack...But froyo is more dependent on the GPU. Why do you think phones with 2.1+ have such powerful gpus? One app that would suffer is gallery 3D,videos,youtube,games,maybe animations. Just use compache, if swap isnt something you want...I dont like froyo on the G1, so i stick to 1.6, which is where it really shines..But i hate giving up things like unlock via trackball, text color,etc. And there's no way im putting vanilla on my MTS cause that wont do it justice.

Ace42 said:
I can see your not going to be convinced easily....If it was possible dumfuq o pershoot would have made a kernel with the ram hack...But froyo is more dependent on the GPU. Why do you think phones with 2.1+ have such powerful gpus? One app that would suffer is gallery 3D,videos,youtube,games,maybe animations. Just use compache, if swap isnt something you want...I dont like froyo on the G1, so i stick to 1.6, which is where it really shines..But i hate giving up things like unlock via trackball, text color,etc. And there's no way im putting vanilla on my MTS cause that wont do it justice.
Click to expand...
Click to collapse
Agreed. I don't know why you're so fond of the idea of having +5mb of ram anyways, that's not even enough to run a lot of apps or processes. The speed up would not be noticeable and since the froyo roms use more of the gpu(as stated before) you would probably even see some slow downs. You have to understand this, even if we HAD the ramhack no one would use it. You're better off with a new phone.

protomanez said:
You have to understand this, even if we HAD the ramhack no one would use it. You're better off with a new phone.
Click to expand...
Click to collapse
OMG!!!! WTF!!! BUY A NEW PHONE?? SURE STEVE... plus great analogy!!!
Sent from my HTC Dream using CM7 IN-STEREO (( WHERE AVAILABLE ))

So again, how was it possible to put a 10mb ram hack on openeclair 2.1 rom? :thinking:
sent from my HTC G1 using CM7 IN-STEREO (( WHERE AVAILABLE ))

the only reason the ramhack was used then was because the gpu drivers were broken until cm5 came out
the only reason eclair became usable is because of how CM set it up - the ram hack is not possible anymore and not even useful (never was IMO)

jp2dj1 said:
So again, how was it possible to put a 10mb ram hack on openeclair 2.1 rom? :thinking:
sent from my HTC G1 using CM7 IN-STEREO (( WHERE AVAILABLE ))
Click to expand...
Click to collapse
Does every rom developer and/or Kernel builder have to come in and smack sense into you?
2 days of you arguing.. if it was possible, common sense might tell you that someone would have jumped in and said "oh, here you go"
Froyo is majorly dependent on the gpus in the new higher end android phones. Using a ram hack, takes away ram from the GPU... froyo was NEVER made for the G1.
Rather then sit here and argue with people who know 100x more about it then you, why dont you go off and try and do it yourself and learn something in the process rather then clutter the boards with your mindless blabber?

crypysmoker said:
Does every rom developer and/or Kernel builder have to come in and smack sense into you?
2 days of you arguing.. if it was possible, common sense might tell you that someone would have jumped in and said "oh, here you go"
Froyo is majorly dependent on the gpus in the new higher end android phones. Using a ram hack, takes away ram from the GPU... froyo was NEVER made for the G1.
Rather then sit here and argue with people who know 100x more about it then you, why dont you go off and try and do it yourself and learn something in the process rather then clutter the boards with your mindless blabber?
Click to expand...
Click to collapse
I wish someone could smack some sense into me, so I can smack some sense back. Saying " froyo was never made for the G1" PROOFS THAT ANYTHINGS POSSIBLE. I'm just saying, a lot people like speed and would sacrifice 3D. I PITTY THE FOOL.
P.s all developers and kernel builders have more hospitality than you.
sent from my HTC G1 using CM7 IN-STEREO (( WHERE AVAILABLE ))

Rogers G1 2.1 Update for the T-Mobile G1?

Can the 2.1 version for Rogers can put onto the T-Mobile version of the HTC Magic or will it be problematic?

Looks like it works on 32a
http://twitter.com/Amon_RA/status/24101277025
http://twitter.com/Amon_RA/status/24113346424
http://twitter.com/Amon_RA/status/24116479740

Yeah i'm curious if it can be ported to us on 32b. Would probably work smoother than those legend ports
Sent from my U20i using XDA App

Anyone know if this has "Smart Dialer"?
Sent from my HTC Dream SparksMod using XDA App

is it sense ui?

asb123 said:
is it sense ui?
Click to expand...
Click to collapse
Yes it is sense

http://www.youtube.com/watch?v=1lNeYGQWymM

Come On Dudes! Do It! A Magic Sense Rom must run good on the G1!

Maybe somebody could replace the Sense UI for the Android original. The hardware is not so different, just a little bit more memory.
I want this ROM ported to HTC Magic 32B because since Android 2.x we always have memory leaks in the camera driver.

I definitely want this ported!

I definitely want this ported too! Especially if it finally bring Sense to the G1 without draining our battery in less than day. Or in another cases requires so many changes that it becomes too unstable.

hmmm what did rogers do that cyanogen didn't?

qipengart said:
Can the 2.1 version for Rogers can put onto the T-Mobile version of the HTC Magic or will it be problematic?
Click to expand...
Click to collapse
Some1 ported to 32b please please please

R3N0V4D0 said:
hmmm what did rogers do that cyanogen didn't?
Click to expand...
Click to collapse
Dude its Sense I love sense = o )

solaresdonis said:
Dude its Sense I love sense = o )
Click to expand...
Click to collapse
this is definitely possible. Most people Dont know that the cause for battery drain is a combination of:
1. swap
2. "optimized kernels"
These both exist to make sense roms usable on our phones, and they do make them usable but they drain battery.
the only advantage that this 32a build with sense may have is optimizations of the apk's and frameworks that could account for a speedier experience, and therefore introduce the possibility of cutting down on the two factors listed above.
It is very possible to do, and in fact easy. If the demand is high enough, i'll do it myself... add ideas/input here.

I definitely am up for a port
Sent from my Htcclay's SuperBad 3G using XDA App

jcarrz1 said:
this is definitely possible. Most people Dont know that the cause for battery drain is a combination of:
1. swap
2. "optimized kernels"
These both exist to make sense roms usable on our phones, and they do make them usable but they drain battery.
the only advantage that this 32a build with sense may have is optimizations of the apk's and frameworks that could account for a speedier experience, and therefore introduce the possibility of cutting down on the two factors listed above.
It is very possible to do, and in fact easy. If the demand is high enough, i'll do it myself... add ideas/input here.
Click to expand...
Click to collapse
Another thing to remember is that 32A's have about 100 mb more ram, so 32B's actually need some of those things to make them more usable. Anybody know anything about the radio that released with it? I mean, is it still a locked down 3.X rogers radio, or is it something 2.X, or even 6.X? Another thing of interest would be bluetooth, but I'm not sure if 32A's and B's share the same bluetooth chip. +1 for the port jcarzz, I would try it myself but I'm still learning. We should also try to extract the camara drivers, the way I understand it in CM5/6 we're using a hacky method with backported donut drivers and a few other things. We could really pull a lot from this.
Okay, so I looked a few things up and answered some of my own questions. It does include a new radio 6.35.16.19, but it's not something we can use. Maybe some of the guys who have JTAG equipment can experiment with flashing it. Since it's not a G1 radio we shouldn't get bluetooth working so cross that off the list too. Still a promising release though.

jcarrz1 said:
this is definitely possible. Most people Dont know that the cause for battery drain is a combination of:
1. swap
2. "optimized kernels"
These both exist to make sense roms usable on our phones, and they do make them usable but they drain battery.
the only advantage that this 32a build with sense may have is optimizations of the apk's and frameworks that could account for a speedier experience, and therefore introduce the possibility of cutting down on the two factors listed above.
It is very possible to do, and in fact easy. If the demand is high enough, i'll do it myself... add ideas/input here.
Click to expand...
Click to collapse
Please my liege. Do it.
Request: Make it awesome .

mejorguille said:
Another thing of interest would be bluetooth, but I'm not sure if 32A's and B's share the same bluetooth chip.
Click to expand...
Click to collapse
No, just like all the early 1.5 Hero roms that were from 32a phone... no Bluetooth.
I did a quick dirty port... got to boot but runs like crap... nonstop FC's and crashes. Really no time to play with it.

fishman0919 said:
No, just like all the early 1.5 Hero roms that were from 32a phone... no Bluetooth.
I did a quick dirty port... got to boot but runs like crap... nonstop FC's and crashes. Really no time to play with it.
Click to expand...
Click to collapse
Hehe I figured so, but I wasn't rooted yet when all the hero rom's started coming out so I didn't know that til now. And I looked through cyanogen's twitter and he mentioned that the camera drivers were tied to the radio so we can't pull that from it either. GL on porting it.