Related
I bought my Hero a few weeks ago because I dug the SenseUI (it looked better than the standard Android UI) and because there was an update to 2.1 promised.
At the moment I'm a little bit afraid of two things:
1. There will not be an update. There really are great apps out there requiring 2.0+ and many features I could use like built in VPN support.
2. If there will be an update it might look ugly as hell. From what I've seen from the leaked Expresso ROM, I can only hope that they won't do that ugly **** for the Hero update... actually I just hope they will never really release that design. The current SenseUI looks original, slick, elegant, starting with the home screen, to the individual app icon designs. Sounds stupid, but that stuff really looks neat unlike the Expresso UI I've seen (oh, too much rambling here)
Now, if all goes bad... is it possible to extract the Nexus One ROM and use it on the HTC? After all the Hardware is not too different and should work with a little bit of adjustment.
In general, I'm really amazed by what is going on here... but most ROMs seem to be a modification/theming orgy rather than a decent port of a decent, more advanced OS version. I don't mean to offend anyone. After all, these ROMs are great for people interested into all that modding and theming and all. But for me, it's important to have a nice looking and working OS, not so much community modifications.
well you can't argue about taste, so i'll leave that part out. my bets would go on something looking at least similar to the espresso leak.
there will be an update, that's for sure. it is only a matter of time, i hope not too much time...
about porting the nexus rom, i wouldn't hold my breath for it. the hardware might be not so different, but from how i see it the hero is a ***** when it comes to hardware. this is also the reason why there is only about a dozen roms at all, and the only one without compromises is mcr. look at the g1 section, they literally drown in roms.
and for starters, the nexus has the snapdragon cpu, which seems to be at least one generation further evolved when it comes to mobile computing power, i don't see it coming...
don´t worry .
i read a rumor in the morning that htc is going to release on february 15th
Yes, we will get Nexus version.
Simply put, Nexus is pretty much standard 2.1 Android.
so far, people like Lox have been working on getting version 2.0 & 2.01 running on the Hero, but now that 2.1 SDK has been released they will start working on that. But it will help when HTC release the source code for their own 2.1 version as that will give them all the drivers etc they need.
The only thing I can see causing problems are the live wallpapers, but I believe that people are getting these to run on the G1 so you never know what is possible.
I've been running 2.0.1 software with all the latest gallery,navigation etc apps for a while now so expect 2.1 versions soon.
PS I installed the Expresso version on my phone and uninstalled straight away. Reminds me way too much of HTC's Windows Mobile software !
GXFX said:
don´t worry .
i read a rumor in the morning that htc is going to release on february 15th
Click to expand...
Click to collapse
and where did you read that?
furrypotato said:
people like Lox have been working on getting version 2.0 & 2.01 running on the Hero, but now that 2.1 SDK has been released they will start working on that. But it will help when HTC release the source code for their own 2.1 version as that will give them all the drivers etc they need.
Click to expand...
Click to collapse
Two points!
1. The 2.1 SDK is *not* the source code for Android 2.1. The the tools and libraries required to build Android 2.1 applications, not the OS itself. As far as I'm aware, the 2.1 OS code has not been dropped into the AOSP (Android Open Source Project).
2. HTC are only required to release the source code to the kernel as this is licensed under the GPL, though this will contain the hardware drivers. HTC's version of 2.1 itself does not ever need to be released as the Android source code is licensed under the ASL which is not a copyleft license.
Regards,
Dave
furrypotato said:
that will give them all the drivers etc they need.
Click to expand...
Click to collapse
yeah, i wouldn't be so sure about that. the kernel sources for the g1 kernel .29 are out, doesn't help a tiny bit for the hero so far...
kendong2 said:
well you can't argue about taste, so i'll leave that part out. my bets would go on something looking at least similar to the espresso leak.
Click to expand...
Click to collapse
You are right of course... if they release an upgrade to 2.1 it's logical that they develop and use that for the Espresso. So I guess it will be the same as the Espresso ROM. I just hope that the Espresso ROM won't look like the leaks.
While you can't argue about taste... you have to admit, that the UI looks (stylewise) quite different to the original Sense UI. Usually I wouldn't mind change. Just take Apple's UI, or Google's UI on the web as well as in Android releases. They usually stay the same, sometimes adding more colors, using gradients, etc. and you still recognize the original style. It usually takes very long until a system has changed so much that you can't recognize it's origins. Take the difference between XP and Vista. Was quite huge. Now the difference between XP and Win7 was minimal (stylewise).
Now, in the leaked Espresso rom I can't recognize the old SenseUI at all, except for the widgets, which can be removed / customized anyway and are not the main concern of HTC's developers right now.
Well, in case it looks to my disliking:
I know, that Sense UI as a whole is not just a plugin but the visually relevant parts (home screen, lock screen, mesages app, mail app, contacts app etc.) are mainly applications, right? (Well, the designs for menu lists, like in "settings" are not apps I guess, but they don't bother me as they look the same in the current UI version) How hard do you think would it be to extract the old apps and replace their counterparts in the new ROM?
This could maybe even be done without rooting, like it's possible for the lock screen and home screen. I dunno about replacing the Standard htc apps though.
felikz said:
and where did you read that?
Click to expand...
Click to collapse
Look here - http://www.androidcentral.com/rumors-say-european-htc-hero-get-android-21-february
Sir_Oliver said:
Look here - ...
Click to expand...
Click to collapse
Well the rumor that it's going to be released in February... come one... HTC said it will release in 1Q2010 which leaves January to March. February is right in the middle so they just say February.
That alone, ok, but what about the list of features. It seems to be put together from previous rumors and leaked ROMs noone even knows of whether they apply to the Hero update.
I'd take such a rumor, originally from some obscure Polish website (not to say anything against Poland, but it's a local website and the rumor hasn't surfaced from a more global site anywhere else), with a (huge) grain of salt.
I'm with Olafos here. I've now tried a 2.0 and 2.1 ROM, but come back to MCR3.1 within a few hours. It's not even all totally about visuals, as I think had been mentioned. The contacts widget, giving me my favourite contacts on my homescreen is used a lot by me. The group text is used quite a bit too.
The contacts, messages and other things just don't look very nice on standard 2.1. When the Bravo comes out (or before) with 2.1 have these cool Sense UI additions?
How much different will the Nexus One be to what 2.1 on my Hero looks like? Right now it's totally put me off upgrading. I really want a bigger screen and snapdragon CPU, but I would miss the amazing UI and funcitonality of my Hero on 1.5 with Sense UI :-/
olafos said:
You are right of course... if they release an upgrade to 2.1 it's logical that they develop and use that for the Espresso. So I guess it will be the same as the Espresso ROM. I just hope that the Espresso ROM won't look like the leaks.
While you can't argue about taste... you have to admit, that the UI looks (stylewise) quite different to the original Sense UI. Usually I wouldn't mind change. Just take Apple's UI, or Google's UI on the web as well as in Android releases. They usually stay the same, sometimes adding more colors, using gradients, etc. and you still recognize the original style. It usually takes very long until a system has changed so much that you can't recognize it's origins. Take the difference between XP and Vista. Was quite huge. Now the difference between XP and Win7 was minimal (stylewise).
Now, in the leaked Espresso rom I can't recognize the old SenseUI at all, except for the widgets, which can be removed / customized anyway and are not the main concern of HTC's developers right now.
Click to expand...
Click to collapse
ok, point taken
olafos said:
Well, in case it looks to my disliking:
I know, that Sense UI as a whole is not just a plugin but the visually relevant parts (home screen, lock screen, mesages app, mail app, contacts app etc.) are mainly applications, right? (Well, the designs for menu lists, like in "settings" are not apps I guess, but they don't bother me as they look the same in the current UI version) How hard do you think would it be to extract the old apps and replace their counterparts in the new ROM?
This could maybe even be done without rooting, like it's possible for the lock screen and home screen. I dunno about replacing the Standard htc apps though.
Click to expand...
Click to collapse
i have no idea about backward compatibility of the android system... just try it with one of the 2.0 roms? i'd bet on foobar if you mix 1.5 sense parts with 2.x, but don't let that stop you from romcooking
I just realized I said:
"Now the difference between XP and Win7 was minimal (stylewise). "
Of course I meant Vista and Win7
Ich will nicht wirklich eigene Roms machen...mir fehlt leider die Zeit. Hoechstes der Gefuehle waere evtl. zu rooten und zu schauen was läuft
I think Android apps are backwards compatible, not so sure about the HTC Sense UI integrated ones though.
For the people that wanted to know if you can disable HTC Sense on the Desire, or just wanted to know how to do it:
Here is a short demonstration of how to disable HTC Sense on a Desire.
It's nice to know this is possible. IMO the stock version (Nexus One look) also has some nice benefits.
Sorry if this was already posted
thanks....
this what i needed to make my decision....
defintally a desire
thanks that what i was looking for..
so excited about getting the Desire...
But, I dont think that will completely stop all Sense processes.
The Sense framework is still being used, CMIIW.
gogol said:
But, I dont think that will completely stop all Sense processes.
The Sense framework is still being used, CMIIW.
Click to expand...
Click to collapse
All Sense on Android is, is a few apps.
The main one being the Launcher which you can disable as seen in that video.
There's then the Messaging and Dialler apps which you can replace with stock apps (without being rooted).
That's about it apart from the fact you'd be left with a Black notification tray instead of a White one and a far superior lock screen.
gogol said:
But, I dont think that will completely stop all Sense processes.
The Sense framework is still being used, CMIIW.
Click to expand...
Click to collapse
IMO, i dont think someone would disable the Sense (maybe just to see how the plain Nexus One looks like ).
and we have 576 MB RAM; I dont think we should worry about "apps that run in the background"
gogol said:
But, I dont think that will completely stop all Sense processes.
The Sense framework is still being used, CMIIW.
Click to expand...
Click to collapse
Jup I found out that even if you disable Sense, tbere will still be some 'behind the scenes' Sense stuff going on. Like for example, Stock 2.1 only supports 5 homescreens instead of 7.
So if you REALLY want the fast Stock 2.1 experience, disable Sense is not enough. You will have to put a real stock 2.1 ROM on it, or how it is called.
Anyway, most people probably wont have any problems with this.
Speaking of stock 2.1 rom being faster than the one with Sense UI.
How much faster is it? Is it very noticeable?
XDA mark said:
Jup I found out that even if you disable Sense, tbere will still be some 'behind the scenes' Sense stuff going on. Like for example, Stock 2.1 only supports 5 homescreens instead of 7.
So if you REALLY want the fast Stock 2.1 experience, disable Sense is not enough. You will have to put a real stock 2.1 ROM on it, or how it is called.
Anyway, most people probably wont have any problems with this.
Click to expand...
Click to collapse
Keeping the HTC framework will be to the owner's advantage, some of the HTC apps that don't run on a stock Android rom will then work properly.
a stupid question....can i put manila on the desire?? and then....it's android similar to windows mobile?? there's a cab for everything?
exscuse me for stupid questions but i have a topaz and i'm thinking about take a desire!
mikawa said:
a stupid question....can i put manila on the desire?? and then....it's android similar to windows mobile?? there's a cab for everything?
exscuse me for stupid questions but i have a topaz and i'm thinking about take a desire!
Click to expand...
Click to collapse
The contents of each tab in Manila are available as widgets in Android and they're far more customizable. There's really no reason to have Manila on Android.
nm... it was shown in the video @ the OP.
XDA mark said:
Jup I found out that even if you disable Sense, tbere will still be some 'behind the scenes' Sense stuff going on. Like for example, Stock 2.1 only supports 5 homescreens instead of 7.
So if you REALLY want the fast Stock 2.1 experience, disable Sense is not enough. You will have to put a real stock 2.1 ROM on it, or how it is called.
Anyway, most people probably wont have any problems with this.
Click to expand...
Click to collapse
When / If it gets rooted and vanilla 2.1 gets ported to it, I am going to always have a Nandroid backup of a version with SenseUI and a Nandroid backup of Vanilla 2.1 Android so I can swap between them as and when I want.
gogol said:
Speaking of stock 2.1 rom being faster than the one with Sense UI.
How much faster is it? Is it very noticeable?
Click to expand...
Click to collapse
From what I have seen, the difference is almost not even noticeable. But then again all the Desire video's I have seen are after it has just been turned on. Maybe the Sense UI will cause some lag after a while of using.
Anyway, Stock 2.1 HAS to be faster, that is a fact. 2 homescreens less, no Sense stuff running in the background, etc.
If I would turn off Sense UI, I would not do it for the speed improvement btw. I like the look of 2.1, with that 5 homescreens and the way to switch between them.
Dude it's a ''snap the dragon'' 1ghz cpu inside! You will not need extra speed
vegetaleb said:
Dude it's a ''snap the dragon'' 1ghz cpu inside! You will not need extra speed
Click to expand...
Click to collapse
And the Desire has extra RAM to accommodate SenseUI.
vegetaleb said:
Dude it's a ''snap the dragon'' 1ghz cpu inside! You will not need extra speed
Click to expand...
Click to collapse
Well, when I finally got my long awaited HTC TyTn, I asked on a forum if anyone knew if there were any possibility to overclock the CPU....
The only answer I got back then was : "..There's no need to overclock the TyTn, the CPU is a 400 mhz!!"
But now, I'm sitting here, stuck with my sloooow TyTn (after selling my Hero to earn money for a new Desire)
So...I guess we can always need some more power, just wait some months and the apps and games are demanding more than enough for the Snapdragon CPU....and you need to swallow a camel or two
vegetaleb said:
Dude it's a ''snap the dragon'' 1ghz cpu inside! You will not need extra speed
Click to expand...
Click to collapse
Yeah, sure it's a 1Ghz processor. But my HD2 has it and it still lags.
So I will take all the extra speed I can get for perfect performance
XDA mark said:
Yeah, sure it's a 1Ghz processor. But my HD2 has it and it still lags.
So I will take all the extra speed I can get for perfect performance
Click to expand...
Click to collapse
You can argue that on the HD2 it's down to the OS/custom ROMs that it still 'lags'. My brother has the a stock T-mobile ROM on his device and I fail to see any lag.
brummiesteven said:
That's about it apart from the fact you'd be left with a Black notification tray instead of a White one and a far superior lock screen.
Click to expand...
Click to collapse
The better lock screen you're talking about, is that after disabling Sense? Which lock screen would that be, and what lock screen does the alternative have? And I always thought there were several lock screens to choose from - I've seen one where you make a pattern, one where you just flick the lock screen down, one where you "turn a wheel", and possibly some others, can't remember.
That's a lot of "lock screen" for one post
Hi All,
Been looking around, (ive tried android on my kaiser once), and just wondered what is the best (most stable) android for kaiser, as a lot of them seem to have a lot under "not working"?
Thanks,
Tom,
Kinda hard to answer, since no one Android build has anything working 100%.
Myn’s Warm Donut will get you most of your stuff working, but there's still a lot of bugs.
Incubus26Jc's Super Eclair is pretty good, but you lose out on Camera and Bluetooth. Less bugs then Donut, but more stable IMO.
Although Polyrhythmic hasn't updated his 2.1D for a while, I still think it's the best of the eclairs. For Donut, Myn's is really the only game in town.
Eclair is still struggling with non-working camera, but GPS , WiFi, and BT are working reasonably well, if you are prepared to invest some time into hunting out the best combination of nbh and build.
Donut is reasonably complete, I have had Myns working with WiFi, GPS and Camera, or GPS, BT and Camera, but never managed all working at once, it is the most feature-complete and arguably the most stable build of all.
Given that we have only had Android on our kaisers since the end of last year, I still think that all the devs have done a remarkable job, and development continues.
Compared to the start of the year, when all that was possible was running from SD, with battery life measured in minutes, no wifi, gps, bt or camera, I think what we have now is a complete OS, it's been my everyday phone OS now for months, and once you get into a few good habits, it's stable and smooth, with decent battery life.
Thanks for replies guys,
I have installed Myn’s Warm Donut, but it seems the graphics are a bit weird, they seem like they are the wrong bit depth or something, not quite sure how to describe it.
Any help on this please?
Thanks,
Tom
XCougar said:
Thanks for replies guys,
I have installed Myn’s Warm Donut, but it seems the graphics are a bit weird, they seem like they are the wrong bit depth or something, not quite sure how to describe it.
Any help on this please?
Thanks,
Tom
Click to expand...
Click to collapse
Q: I installed Android but now everything is blurry.
A: It's due to wrong resolution. Kaiser phones have panel for 230x320 but you're probably using 320x480 build. Here is a post by user tatnai where he explains this situation for Vogue devices (it goes same for Kaiser).
Android FAQ: http://forum.xda-developers.com/showthread.php?t=683644
Click to expand...
Click to collapse
Myn's Warm Donut is basically a scaled down version of 320x480 resolution to fit 230x320 panels, with 110 density, hence the blurriness.
One build with native 230x320 I like is vilord's Tattoo Sense, but there is a camera and BT audio not working problem in that build - hopefully incubus26jc's next release will fix this.
milanche said:
Myn's Warm Donut is basically a scaled down version of 320x480 resolution to fit 230x320 panels, with 110 density, hence the blurriness.
One build with native 230x320 I like is vilord's Tattoo Sense, but there is a camera and BT audio not working problem in that build - hopefully incubus26jc's next release will fix this.
Click to expand...
Click to collapse
vilord's Tattoo Sense sounds pretty good, and it has rosie which I'd love to see working stable. I think I'll try this on the weekend, but just wanted to know, has anyone tried this? is it stable and/or fast? Its for the touch, but as far as I've seen, vogue builds work for kaiser... would this work too?
milanche said:
Myn's Warm Donut is basically a scaled down version of 320x480 resolution to fit 230x320 panels, with 110 density, hence the blurriness.
One build with native 230x320 I like is vilord's Tattoo Sense, but there is a camera and BT audio not working problem in that build - hopefully incubus26jc's next release will fix this.
Click to expand...
Click to collapse
Hi, thanks for reply, not that I don't believe you, but its not so much blurryness, there are pink and green bits everywhere? Or is this what your describing?
Thanks again,
Oh thats because you´ve choosed a wrong paneltype. Kaiser was built with 3 different Panels so you have to choose the right one. Look at the second sticky thread.
xPreSiDenT said:
vilord's Tattoo Sense sounds pretty good, and it has rosie which I'd love to see working stable. I think I'll try this on the weekend, but just wanted to know, has anyone tried this? is it stable and/or fast? Its for the touch, but as far as I've seen, vogue builds work for kaiser... would this work too?
Click to expand...
Click to collapse
I've tried it and believe it's the best Android build so far, despite BT and Camera problem (which we should be able to fix as it is Donut 1.6 Android).
For Kaiser you should use kallt_kaffe's update to get Wifi working and it also fixes Rosie and Market.
Thanks for info.
Ok please dont flame me, ive looked around and I used to flash windows mobile all the time, but I really dont understand these nbh files.
What are they, what do they do, why are there different ones e.g voguimg.nbh and kaisimg.nbh and polimg.nbh
Thanks for your patience with me
XCougar said:
Thanks for info.
Ok please dont flame me, ive looked around and I used to flash windows mobile all the time, but I really dont understand these nbh files.
What are they, what do they do, why are there different ones e.g voguimg.nbh and kaisimg.nbh and polimg.nbh
Thanks for your patience with me
Click to expand...
Click to collapse
VOGUIMG is for Vogue devices, POLAIMG is for Polaris devices and KAISIMG is for Kaiser. Think of them as some sort of bootloaders for Android. You flash the NBH, boot to the install console, install Android from SD to NAND/SD/EXT2 and boot Android. Also you have to choose the correct panel to avoid screen problems you're having. The only way to see which panel are you using on Kaiser is to test all three of them and see which one doesn't cause you screen problems.
To test which panel you're using you should first make an SD install with Haret, there you have the option to specifiy panel type in the config file default.txt and can change this before every boot. With NAND this is hard-coded into NBH file. Later you can flash to NAND if you decide to stick with Android.
Please go thru this Q/A topic, it should help you get the answers to most of newbie-type questions.
I´m not a developer and especially on android i´m a noob but i think the NBH contains all what is going to be flashed into nand. In case of WiMo it´s the whole Operating system, somtimes with radio too. In case of android the NBH contains the Kernel only. The kernel is designed for your device with all the drivers you need (touchscreen, wifi, BT, GPS, etc.). so kernels from other devices may not work becaus of other hardware specs. in worst case it may brick your device. I read alot before i flashed my kaiser an kallt_kaffe´s kernel seems to be the best for now. Nearly all funktions are available. Only the Camera have a bug, but i think it only takes only a little time to fix this too.
I use kallt_kaffe´s kernel and Myn´s Warm Donut RLS5 and i´m totally happy with it. Fingerfriendly (you´ll never need your stylus again except for reset ^^), and much more responsive then the fastest WiMo ROMs.
You only have to modify the nbh for your panel type. But you only can do trial & error to find out which type you have.
So... happy flashing.
Thanks everyone for your help, I have the tattoo sense rom on my phone now, my phone uses panel2 type of kaiser nbh.
I now understand the nbh better.
As im more then likely going to upgrade to a newer android rom when more stable ones come out, can anyone recommend a android application that will allow me to backup my txts, emails, contacts, and settings, etc.
Thanks all
Hey guys is it possible to resize or convert desire roms to buzz roms?
Practically, No. Else we would have had a lot more ROMs, especially Sense 2.1 / 3.0 ones, apart from SFM.
3xeno said:
Practically, No. Else we would have had a lot more ROMs, especially Sense 2.1 / 3.0 ones, apart from SFM.
Click to expand...
Click to collapse
Ann Alright ... but cant we just Resize the graphics and use any other Rom 's Scripts?
They are optimized for that device's hardware, and I am sure you know that there's a difference as big as day and night when you compare the hardware of Desire and Wildfire. If you saw the recent AOSP ROMs being developed by xdbg and Devnull, even a simple task of swiping from one homescreen to another uses the GPU by default (Which is absent, causing lag), which has to be overcome by using special functions. But this doesn't work everywhere.
Besides, resizing is an extremely tough job, and involves editing of tons of image files and XML files. You can see that in SFM, where inspite of evilsto resizing many apps and worked a lot on it, the overall appearance of the ROM is not suited for the Wildfire.
3xeno said:
They are optimized for that device's hardware, and I am sure you know that there's a difference as big as day and night when you compare the hardware of Desire and Wildfire. If you saw the recent AOSP ROMs being developed by xdbg and Devnull, even a simple task of swiping from one homescreen to another uses the GPU by default (Which is absent, causing lag), which has to be overcome by using special functions. But this doesn't work everywhere.
Besides, resizing is an extremely tough job, and involves editing of tons of image files and XML files. You can see that in SFM, where inspite of evilsto resizing many apps and worked a lot on it, the overall appearance of the ROM is not suited for the Wildfire.
Click to expand...
Click to collapse
Yeah ofcourse i know difference between hardware stuff also .. nyways ... hoping to develop some exe to do resizing stuff -- Finger crossed
http://forum.xda-developers.com/showthread.php?t=1543328
Anyone eager to port?
This gonna be a tough one considereing all the resizing that needs to be done
csoulr666 said:
This gonna be a tough one considereing all the resizing that needs to be done
Click to expand...
Click to collapse
right , but i calculated the ratio of hdpi/mdpi for the same image and it was 2.25 , so that 2.25(mdpi)=hdpi , by this we can catch up some batch png file converter that respects alpha info in the pic (because most doesn't) , and then resize everything by the ratio given so that the batch would resize everything to mdpi and keeps the alpha info in the pic ! by that we could finish all the resizing in one single day , there comes the kernel and compatibilty issues including connectivity and other usual bugs ... so what do you say guys ?? for now I tried :
Imagemagick (has what we need but as the resizing is in pixels meaning we have to calculate every ratio )
Fotosizer ( it could have done it , but no respect for alpha , always replaces by white ...
Come on guys we need researchers here , this resizing project could be universal !!
EDIT !!!!!!!!!!!
Guys , i found what we needed , i will be finishing all the resizing maybe tomorrow due to school (which i will be in house at 1:30 pm [2+ GMT in my country ), and also the download here sucks so it'll take some time , for now i will be working on my project it is amazing , behold the release
@seaskyways: If you resize everything I will help you with the port. But I think it
would be easier to wait for a latest mdpi htc phone with sense 4.0
Indeed, wait a bit. They first going to port it to hdpi (desire s, sensation,...) then its our time. I dont think it will ever come to mdpi.
Devices get faster and better displays.
If sense 4 comes to mdpi, it would be a slimmed down version like the pico sense 3.5.
I will definitely try sense 4 if it will come.
Lets first wait a stable base aka cm9.
Sent from my WFS running MIUI
Actually i am offering my WFS for sale so as long as it is between my hands , as long as I will work on it , I am going to hdpi phone , most likely Neo V ...
@matt5eo : What do you use for resizing , cuz the plan in my head didn't work , and the other alternate plan which i am working on is a killer !
So guys ?? matt5eo ?? wait for an mdpi device with the sense 4.0 ?? well for now we can port basic things as the Rosie and 3D wigets ... not the whole sense , this would do the job for now ... So , anybody thumbs up for da idea ?
you can forget porting this as the apps etc wont work on are processor the htc one series are running on dual core and one model running a quad core processor
Hold on , i thought One V was single core !!
Features
OS
Android OS, v4.0 (Ice Cream Sandwich)
CPU
1 GHz
Sensors
Accelerometer, proximity, compass
Click to expand...
Click to collapse
From GSM arena ...
seaskyways said:
Hold on , i thought One V was single core !!
From GSM arena ...
Click to expand...
Click to collapse
could be i remembered it from leaked info on it awhile ago
ok.. porting
seaskyways said:
Hold on , i thought One V was single core !!
From GSM arena ...
Click to expand...
Click to collapse
Anything is possible. Mainly for ports you want to work backwards So your looking at some smali editing for the framework apks, mainly modules (you have to use what WFS has available [based on physical hardware])... This will take the most time and where most ppl quit. Challenges of note for WFS have been Graphics (3D acceleration etc needed for ics. [best to look for advanced codexes for armv6 vfp] and the aforementioned resizing issues) and touchscreen will be your first hurdle most likely, then kernel, then custom hboot. Good luck.. not something I can even assist with at present.
Rob
Well , I am not working on the port itself , but i need some components of it , could any of the downloaders please upload me the following :
HtcLockScreen.apk
HtcClockWidget.apk
SystemUI.apk
Rosie.apk
with their odex files ??
This might help keep my projects of the Sense 4.0 patches working , I guess I can find something in there if I dug in the apks , + i have the powers and patience to port from hdpi to mdpi with correct percentages and software ... So please , I tried dowloading this thing but couldn't open it , some sort of error was popping ...
By the way , if you don't know how to extract the ROM from this RUU i can tell you , but please whoever knows please please give me the files needed ! and thanks !
HEY YOU GUYS!!!! I dont know if this can help but this is what i found about a leaked ruu from the One V http://forum.xda-developers.com/showthread.php?t=1591059
The One V is definitely single core and closer in spec, but still pretty far.
But it's probably better to wait a month or two for release of the Golf / Wildfire C as it will also have a single core processor and ICS / Sense 4, but identical screen size to the Wildfire S.