I think that Jelly Bean feels faster and more lightweight.Do you guys believe that Jelly Bean development would be faster for our wildfire and Jelly Bean could run faster and smoother than the current efforts that are made such as AOKP ICS?
Well, let's see it come first... I'd love to see JB on Wildy but not getting me hopes high.
And well, if it would come... We are talking bout CM10 then as the Cyanogen team has confirmed (JB on CM10).
Let's first complete the task of bringing a bug free ics and then move on to jb ;-)
Sent from my HTC Wildfire using xda premium
Well i heard somewhere that some "project butter" or what ever was it should have improved 4.1 so its less laggy etc.. so it may be less laggy, but i think it was still only somekinda cpu max thing so not sure.
Here's a video showing the difference between ICS and JB.
http://www.youtube.com/watch?v=V5E5revikUU&feature=player_embedded
well jellybean is way faster and smoother than ics on phones with gpu...as butter project pumps up the sysc desktop flips to 60.....am not sure if that cases our little wildfire to get smoother or slow down....hopefully we will get a better experience on jellybean....but the notification bar will suffer...as its 2 small for handing all those expanded notification infos..
As djpry said, Jelly Bean uses CPU an GPU together to make it faster than ICS. If I remember right, Wildfire as no GPU (or quite at least it doesn't have 3D GPU), so I don't think the speed difference will be noticiable between ICS and JB. Also, ICS uses a lot of GPU acceleration, and Wildfire's SoC seems to run it with difficulty.
pantapanta1 said:
I think that Jelly Bean feels faster and more lightweight.Do you guys believe that Jelly Bean development would be faster for our wildfire and Jelly Bean could run faster and smoother than the current efforts that are made such as AOKP ICS?
Click to expand...
Click to collapse
Because of the way that Jelly Bean uses to be faster than Ice Cream Sandwich, it requires a pretty beefy CPU, which the wildfire doesn't have. It would be nice to see CM10 or even any kind of Jelly Bean port on the Wildfire but I doubt it will happen, and even if it does I don't think it'll be considerably faster than the current Ice Cream Sandwich roms floating around.
Now the other day gingerbread came out and its now jellybean lol
Sent from my HTC Wildfire using xda app-developers app
reply
Our wildfire could use cm9 now . but it have so manyy bugs . i had try . and ! now they release cm10.but i stuck in the boot screen . i think the most important is the GPU . Our wildfire is older now . the cpu could now offer to many works . if it can , propolly there are so many bugs and lagg:highfive:
Anyway . I want my wildfire could touch JB !
calvin951121 said:
Our wildfire could use cm9 now . but it have so manyy bugs . i had try . and ! now they release cm10.but i stuck in the boot screen . i think the most important is the GPU . Our wildfire is older now . the cpu could now offer to many works . if it can , propolly there are so many bugs and lagg:highfive:
Anyway . I want my wildfire could touch JB !
Click to expand...
Click to collapse
it will dont worry.....but in a little while....
Short answer: ICS.
The Wildfire will probably get Jelly Bean, but don't expect Project Butter to live up to its name. The Wildfire has no GPU at all. I guess this would mean rendering would take place in the CPU, therefore slowing down the operating system.
arco (developer for CyanogenMod on Wildfire) has confirmed CM10 won't be coming to the Wildfire officially, but there are already early ports out there...
epic118 said:
Short answer: ICS.
The Wildfire will probably get Jelly Bean, but don't expect Project Butter to live up to its name. The Wildfire has no GPU at all. I guess this would mean rendering would take place in the CPU, therefore slowing down the operating system.
arco (developer for CyanogenMod on Wildfire) has confirmed CM10 won't be coming to the Wildfire officially, but there are already early ports out there...
Click to expand...
Click to collapse
Not sure about this but I'm not a developer
The early ports barely boot with lots of problems - but reading the respective threads you'll find out that there's no difference to the early stages of ICS ports.
I had the feeling (not more though) that bottom line they found it already more responsive compared against ICS - but that might also change (i.e. get better - or worser) with all those workarounds to be found and done to get missing things working.
To make that long story short: until everything almost works there won't be any useful prognosis. But there's indeed hope that it might be a bit faster than today's ICS ports.
BTW: nothing above GB will ever come to the Wildfire/Buzz officially anymore - ICS has also been designed for phones with a GPU
Related
Android 4.1 Jelly Bean
Android 4.1 will get interactive notifications, overhauled search results, faster touch-screen response, and a tool to tell people information they may want to know about what's going on nearby and what they might need to know.
http://developer.android.com/about/versions/android-4.1.html
http://developer.android.com/sdk/index.html
I like it. Nice adjusments. Better than other i..OS-es in my opinion. Looking forward for the port.
Deonix said:
I like it. Nice adjusments. Better than other i..OS-es in my opinion. Looking forward for the port.
Click to expand...
Click to collapse
If we get one. Ics is enough of a pain in the backside to get working with the defy.
Sent from my MB525 using xda app-developers app
jelly bean on defy?
There may be a future development of android jelly bean for defy ? Or he does not have enough hardware?
froyo was best for defy
GB was compatible
ICS not so compatible
JB don't know if any possibilities
popcorn1122 said:
froyo was best for defy
GB was compatible
ICS not so compatible
JB don't know if any possibilities
Click to expand...
Click to collapse
i think a bit different
FROYO was the worst for defy
GB was very good
ICS is definitely the best ( some exceptions though )
JB - maybe it would be even better
Shubhamqweasd said:
i think a bit different
FROYO was the worst for defy
GB was very good
ICS is definitely the best ( some exceptions though )
JB - maybe it would be even better
Click to expand...
Click to collapse
I totally agree that Froyo was the worst, it's so slow and ugly :silly: Gingerbread was a huge improvement and Ice Cream Sandwich is an even bigger improvement, but at the moment not all the power of it can be harnessed by our DEFY, so I'd say that Gingerbread is the best. But Motorola is to blame for that, cause with those proper custom kernels, ICS would be flying So, if no way for custom kernels to run arises, I'm guessing that troubles with missing libraries will be even bigger with Jelly Bean, so we might just not even see a CM based on JB for DEFY
Found the Jellybean wallpapers and the new bootanimation over at Android authority!
>>>>>Android Jelly Bean Goodies<<<<<
Has anyone tried the new Jelly Bean VoiceSearch/GoogleQuickSearchBox on our ICS builds yet? I've been searching all over, no-one has yet to post it. You guys had any luck?
I've just tried Jelly Bean on Galaxy Nexus, it's way more faster than ICS because it has this Project Butter (newer hwa) which makes UI constant on 60FPS, so no more UI lags!
Jelly Bean is based on ICS so there won't be so much trouble about porting it because we already have ICS
I think the main question would be whether Project Butter will run with our Froyo/GB Kernel we have to stick with?!
This is one of Epsylon3's posts on Google+. He's just awesome!
Thats great !!
He can takes his time, we will apreciate it very much anyway.
defy developers are really making effort.
I didn't see that on any other device forums
The efforts have been fruitful since the long study made by our developers . They made it easy . since once you get to know how things work . and how the ideas are and what kernel functions and codes u shd be actually knowing . It becomes lots easy for implementation
The Best of The Best of the BEST Dev World
As said : Our defy Devs is the most talented and supportive in all thread with even an locked BL , Don,t know how to give them the deserved appreciation
swapnil360 said:
This is one of Epsylon3's posts on Google+. He's just awesome!
Click to expand...
Click to collapse
Awesome..
Sent from my MB526 using XDA
I want to know how ep3 it's going to manage the fact that chrome it's the default web explorer in jelly bean when it's not yet functional in ice cream sandwich...
Enviado desde mi MB526 usando Tapatalk 2
swapnil360 said:
This is one of Epsylon3's posts on Google+. He's just awesome!
Click to expand...
Click to collapse
it will awesome for all of us , if it happened some how , our developers are best of all others ,
we were just given eclair , we had froyo(modded roms) , GB roms ( best and great performance ) , and we had ICS all good , except some issues due to locked bootloaders, otherwise we at this time could had best ICS rom Available ....... developers are trying their best working day & night for us ,
I am sure that we all will have jelly bean ,( not fully functional though ), but our great developers will make it happen for us all .......
once this Bootloader thing gets solved some how , can't say how ,
we gonna have rocking roms with overall best performance than all the device present in this xda forum ...... and i can bet on this ......
atlast thanks to all the developers of DEFY & DEFY PLUS .......
LIVEPROOF
So basically i found this through the news on xda-dev main site :
http://forum.xda-developers.com/showpost.php?p=28020178&postcount=36
Its how to port Jelly bean to your device, if someone could just do that, we would have jelly bean..right?
could someone with experiences please try it out? Would be kick-ass if it worked!:victory:
We don't have JB because the source hasn't been released; sure, someone can port a JB build to our device but since no drivers have been released it would be buggy as hell. What would be the point of having JB if it rendered your device unusable?
Sent from my HTC Vision using xda app-developers app
Simply put, the best luck the Vision/DZ/G2 has of getting JB is if there is an official Rom released for it (or released to hardware that is very very very similar to the phone's own hardware).
Thus why it took a while for any 'decent' ICS roms to show up on the DZ, and even then some stuff still doesn't work as well as gingerbread (i.e.: the camera and other hardware that HTC has not released the source for yet, or may never do so).
So it's going to be a while before you actually see an 'alpha' quality functioning JB rom for Vision/G2/DZ. Especially since HTC has no plans to release ICS for this phone, everything after gingerbread will most likely have to be reverse engineered.
If it was just easy as all that it would have been done already.
kbeezie said:
Simply put, the best luck the Vision/DZ/G2 has of getting JB is if there is an official Rom released for it (or released to hardware that is very very very similar to the phone's own hardware).
Thus why it took a while for any 'decent' ICS roms to show up on the DZ, and even then some stuff still doesn't work as well as gingerbread (i.e.: the camera and other hardware that HTC has not released the source for yet, or may never do so).
So it's going to be a while before you actually see an 'alpha' quality functioning JB rom for Vision/G2/DZ. Especially since HTC has no plans to release ICS for this phone, everything after gingerbread will most likely have to be reverse engineered.
If it was just easy as all that it would have been done already.
Click to expand...
Click to collapse
Okai, thanks!
So there are rumours going around the the HTC desire HD Will be updated to J-b, so for example (because the devices are..a little bit similar) Someone could work on it.and it might work? Right ?
( HTC said when releasing ICS for some devices that they would not update the Desire Z any more / devices with less than 500 ROM RAM right? )
siemz said:
( HTC said when releasing ICS for some devices that they would not update the Desire Z any more / devices with less than 500 ROM RAM right? )
Click to expand...
Click to collapse
Turns out HTC's own staff are idiots, they're talking bout 512MB RAM or less will not get ICS. ROM wouldn't make much sense, since even the Desire-Z can have either 409MB /system or 549MB /system depending on which hboot used.
The DHD has 768 MB RAM, and the HTC blog already confirms that DHD will get it:
http://blog.htc.com/2012/03/ics/
detailed dates here : http://www.htc.com/www/help/android4faq/?cid=android4blog
July-August for the DHD, June-July for the Desire S
But I'm not sure how much of the hardware components in say the DHD is close to that of the Desire-Z so time will tell.
I guess the idea is the device would need enough ram to run smoothly with a stock ICS possibly Sense-Style and default launcher/etc without any sd-ext, ram tweaks, etc. Though I'm already running ICS on my G2 right now, just lacking a smoother camera functionality (in comparison to when on gingerbread), but can shoot pictures and record videos just fine (Can't think of anything else I'm missing exactly).
Jellybean, probably a long way off.
I disagree. By the time the JB source is out, the 3.0 kernel will be even better and a complete replacement for the 2.6 one we're using now. CM will update to 10 and so will the respective ICS roms we have right now.
The only obstacles would be ones related to project butter, but we need the source first in order to really tell.
I would expect beta quality JB roms by August, assuming the JB source is released in the next few weeks.
Sent from my HTC Vision using xda premium
Hey guys,
Just wondering, why do ALL 4.1 and 4.0 Evervolv-based ROMs have massive problems in 3D performance? Scrolling is often not an issue, but window animations and transition animations are horribly laggy. It's reminiscent of the Froyo/GB Sense window animations (the ones that zoom in/out but don't quite finish), except much worse.
Can someone tell me why this is happening? VJ's AOKP 4.2 also suffers, while his CM10.1 4.2 does not. Cyanogenmod007 (4.1.2) suffers but Cyanomod007 (4.2) does not.
What you've got to realise that on HTC Desire, the board carries an Adreno 200 GPU with a stupid 1GHz single core Scorpion CPU, that isn't even close to the Galaxy Nexus, Nexus 4 or any other devices released with ICS and JB. We are using a 3 year old phone, that was nearing its end, but thanks to VJ, Nikez, CM10 and Evervolv team that we are able to enjoy the ICS and JB flavors on Desire. Those guys are already working hard to make the best possible use of resources on our Desire. Those ROMs are not, I repeat: ARE NOT, for daily use. Its just when you want to have a change of flavor on your weekend. The best and stablest are CM7.2 builds. All the ICS and JB are awesome, but they won't satisfy you. I often suffer from the change of flavors in a week and that's what those guys are devloping for. If you have a good phone, with HTC Desire as a backup one, then you can use those flavors.
Launcher can be an issue. Try Nova or Apex. Did speed up for me considerably.
Sent from my HTC Desire using xda premium
Ok, generally speaking, AospX is WAY faster than any JB 4.1-4.2.2 AOSP/AOKP ROM I have ever tried.
Any reasonal explanation for this?
Because with every successive iteration of Android, it gets farther away from the software for which the hardware was optimized.
That's obvious, but JB is still supposed to be faster (or at least on pair) with it's project butter and gpu optimizations present..
btw Nexus S is officially running on 4.2 so it's not like jellybean wasn't intended to run on such HW.
-SmOgER said:
That's obvious, but JB is still supposed to be faster (or at least on pair) with it's project butter and gpu optimizations present..
btw Nexus S is officially running on 4.2 so it's not like jellybean wasn't intended to run on such HW.
Click to expand...
Click to collapse
My guess is, JB utilizes hardware resources more efficiently. If the hardware capability just isn't there, there is nothing to optimize. Also, with every iteration, reverse-engineering closed-source drivers and making them compatible gets tougher as Android moves farther away from stock.
And comparing a Nexus, which is designed to be upgraded with AOSP for its lifetime, to an HTC, which is designed to be upgraded with Sense once (maybe twice), isn't really fair.
Ultimately, who cares. The faster the better. I've just tried Nikills after using Sabsa Prime - all I can say is wow. It's like using a new phone with modern h/w.
As above, JB isn't exactly designed to run on our hardware. Heck ICS wasn't either.. Its all about the complexity of the OS. You won't run Windows 8 smoothly on a PC that can, just about, handle Windows 7)
Sent from my CodeFireX'd Desire HD
That thanks button doesn't bite
I have only run one custom ROM so far. I went from stock 2.3.5 sense 3 which I used for a week or so..... I was impressed enough with the stock performance that the first day I decided this would be my first android phone to leave stock for any amount of time. Battery issues caused me to root and install cm10.1 m3. Turns out the battery is shot anyways nothing to do with either ROM. Cm10.1 runs on average just as fast as stock GB did and it has been just as stable.
So in this case I think stock GB ROM has enough stuff that no performance drop is felt going to cm10.
If I went cm7 I'm sure it would be a lot faster but it's fast enough as it is so I won't give up this ROM for a bit more speed.
Scrolling seems to be 100% smooth 99% of the time, the only lag is like a couple seconds to open an app especially when I have several running.
My nexus one which I loved was not even close to this perfect on any jb ROMs I tried on it. I went back to cm7. The desire HD is way faster.
I haven't tried any other ROMs on this phone and in trying to get rid of my flashing obsession. I probably won't try any more for a while. I hope.
Sent from my Desire HD using xda app-developers app
Just my 16 year of expert opinion, generally ICS is faster in terms of performance, but JB is much smoother.. going from CodeFireX to Nik's Rebirth ROm, its still pretty smooth, but not as slick as project butter. Still, a great ROM..
Sent from my Reborn Desire HD in another dimension...
That thanks button doesn't bite
mustavalkosta's cm 10.1 nightlie builds are MUCH faster on my dhd than the stock GB rom.
Android jb faster. Fact is that it need some time for the developers to make it stable port to jb. They have make kernel according to it port each and every file according to desire hd. And no one can deny that still after more than a year no ics is complete stable as stock gb Rom.
Sent from my HTC Desire HD using xda app-developers app
GuyInTheCorner said:
Just my 16 year of expert opinion, generally ICS is faster in terms of performance, but JB is much smoother.. going from CodeFireX to Nik's Rebirth ROm, its still pretty smooth, but not as slick as project butter. Still, a great ROM..
Click to expand...
Click to collapse
Your statement is right, from my experience JB is smoother, but ICS is faster (faster opening apps).
But comparison to Nik's ROM is simply not fair as it's a Sense4 ROM which is obviously slower / more stuttering than any other ICS AOSP.
That makes sense to me. I think iv can deal with the extra tiny bit of time opening apps cause I like how smooth the scrolling is.
Sent from my Desire HD using xda app-developers app
Alright, as we all saw in the last couple of days we got a new CM10 jb rom with minor fixable bugs. It's a step forward for our willy , but there's been a question bothering me and i hope most of you aswell: what are the actual highs and lows between a CM10 rom and especialy a CM7 JB styled rom (jellybread in our case) and also between CM10 and CM9 roms.
The actual question is: is it worth keeping CM10 as a daily rom with most of it's lags/delays knowing that there is something else to it than the simple "yo samsung user, i got CM10 on my willy too" ? Or we can use the CM7 jb styled or CM9 wich looks as good as the CM10 does but without the lagfest, the minor bugs (wich are not such a pain in the behind because the way i see it they should be fixed in about 1 week or so tops), and the excruciating pain I experienced when i was going through my settings, not changing anything, and it took my willy a good 6-8 seconds to show me the caller id after the ringtone started when my buddy called me.
Debate please and feel free to criticize my knowledge because i preety much started to dig deeper into android and willy since 1-2 weeks ago.
A really good question!
See there isnt much difference in terms of look between CM10 and jelly bean styled cm7 Roms.
There are a few good things about actual jelly bean like expanded/expandable notifications,better support for proxy connections etc.(We can get those kind of notifications in CMX as well )
Since,we dont have a gpu on our device,special features of ICS/JB like full hardware acceleration,butter project are pretty much useless for us.
Android has evolved to a great extent and has become much richer from times.Compare the looks of stock cm7 and now cm10,there's a huge difference.But its a good idea to have those rich looks with old speed and stability,without sacrificing a lot.
So if you ask me,I'll say cm7 roms will always win in the context of wildfire.You aren't sacrificing much being on gingerbread.
Yeah that's very true
CM9/CM10 are stable but somehow can't be bug free
Sent from my HTC Wildfire using xda premium
I try many cm9 roms, all is good but our Willy lacks of Gpu support, and also some bugs can't be fixed. CM7 is the best for stability and performance, and also with all mods you can have any style you want (CM9-10 style, MUIU, etc).
My vote goes to CM7 based JB style roms!
(and sory for my bad English).
Yes that is true. Cm7 jb are best bet for our Willy. Can anybody remember that HTC never released any update for our wildfire based on 2.3 version. But it is due to cm based rom and the efforts of all the developers that we are still holding our Willy with us in the modernized android world where i think processing powers are touching new heights. As @Wasimk32 said we don't have a gpu so hardware acceleration lag is pretty much going to haunt us. So i personally thank all the people who work for wildfire to breathe life into it.
And to @klyon too for keeping 2.2 rempuzzle alive which still make me feel what had HTC forget to make froyo on wildfire a complete rom. But i am thankful to them all this lead to revolution for our wildfire.
Sent from my HTC Wildfire using xda app-developers app