TBH this forum seems a bit lonely... and my EpicParts question was easily abandoned
Whatever, greetings and happy new year to every one out there!
Today I happen to dig out a Sense 4 ROM for our E4G which boots, doesn't reboot THAT often and is resized well (what, you want links? I think that's a private workspace and maybe I shouldn't tell). But what bugs me most is that SystemUI (statusbar) always FCs for no reason and I can't do anything with that.
So here I got a HTC Incredible S ("vivo", which is the port base for our Sense 2.1 ROM) with a fully-functional Sense 4.1 build. Everything's working and things are better sized for WVGA. And it's smooth. Considering it's a single core device, I think there is already no obstacle blocking the port (I know that Sense4All project paused because One X is a quad core device and gets all sorts of reboots. Correct me if I'm wrong).
Thus, I wanna ask, as a non-coding noob:
1) Is porting process the same as common tutorials (copying frameworks, libs, etc)?
2) If not, is this even possible (to have Sense 4.1 ported from vivo)?
3) If not, again, what can I do to improve my current build on hand (i.e. simply stopping the SystemUI FC and maybe adding more HWA)? I don't intend to use the ROM as a daily driver... Just a tool for showing off
So... Thanks again for reading the thread and hope you can offer some guidance
Sent from HTC Incredible S @ Sense 4.1
If there was a stable version of Sense 2.1 or 4.0, it would be my daily driver. I really hope this project isn't abandoned.
xDecapitator said:
If there was a stable version of Sense 2.1 or 4.0, it would be my daily driver. I really hope this project isn't abandoned.
Click to expand...
Click to collapse
2.1 is already very usable apart from BT (nah I don't use that), but many devs have already left or are silent. Must be with their new toys. That's why I'm trying to help. If I had time in winter vacation I'll try a bit, but hope not too high
And so I need some guidance and answers... Please. Even one answer will do.
Sent from HTC Incredible S @ Sense 4.1
AndyYan said:
2.1 is already very usable apart from BT (nah I don't use that), but many devs have already left or are silent. Must be with their new toys. That's why I'm trying to help. If I had time in winter vacation I'll try a bit, but hope not too high
And so I need some guidance and answers... Please. Even one answer will do.
Sent from HTC Incredible S @ Sense 4.1
Click to expand...
Click to collapse
You can try to pickup where our last dev left off,
http://forum.xda-developers.com/showthread.php?t=1717089&page=18
The issue last reported by xboxfanj was that he too, got many force-closes.
Shinydude100 said:
You can try to pickup where our last dev left off,
http://forum.xda-developers.com/showthread.php?t=1717089&page=18
The issue last reported by xboxfanj was that he too, got many force-closes.
Click to expand...
Click to collapse
I do want to, but I'm not a code dev and know almost nothing except that "brute-force" porting method, and I don't know whether that will work.
I mean, here I got a fully working Sense 4 build on a SINGLE-CORE device, so is this a proof that porting to us is also possible?
Sent from HTC Incredible S @ Sense 4.1
You ported sense 4 to an htc phpne which is much easier than porting it to something not even close to compatible with the hardware so it will be more difficult
Sent from my SPH-D700 using Tapatalk 2
phonehunter59 said:
You ported sense 4 to an htc phpne which is much easier than porting it to something not even close to compatible with the hardware so it will be more difficult
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
But... I said
1) We HAD a now paused project that has ported Sense 4 and made it boot
2) I have a better Sense 4 base ROM (for our device, not HTC's) at hand with fewer random FCs
3) xboxfanj said that the port reboots because One X is quad core, and the ROM will keep searching for the extra cores. But IncS is single core and runs that beautifully (its port is based on One V and Desire X)
And that's why I'm seeking answers.
Sent from HTC Incredible S @ Sense 4.1
AndyYan said:
But... I said
1) We HAD a now paused project that has ported Sense 4 and made it boot
2) I have a better Sense 4 base ROM (for our device, not HTC's) at hand with fewer random FCs
3) xboxfanj said that the port reboots because One X is quad core, and the ROM will keep searching for the extra cores. But IncS is single core and runs that beautifully (its port is based on One V and Desire X)
And that's why I'm seeking answers.
Sent from HTC Incredible S @ Sense 4.1
Click to expand...
Click to collapse
Part of the problem is that we couldn't port qualcomm roms which would be stable if they booted, but we never got it booting. Tegra is all intercoded into libs and looks for kernel files we don't have which causes it to reboot and be unstable.
Sent from my LG-LS970 using xda app-developers app
xboxfanj said:
Part of the problem is that we couldn't port qualcomm roms which would be stable if they booted, but we never got it booting.
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
...And why?
Sent from HTC Incredible S @ Sense 4.1
AndyYan said:
...And why?
Sent from HTC Incredible S @ Sense 4.1
Click to expand...
Click to collapse
To be honest, we never quite figured it out. We never got a proper logcat, since it only gave us unhelpful information, which means it doesn't even start to fully boot.
xboxfanj said:
To be honest, we never quite figured it out. We never got a proper logcat, since it only gave us unhelpful information, which means it doesn't even start to fully boot.
Click to expand...
Click to collapse
And this means all my expectes efforts should be in vain, huh?
But check this, I got a Sense 4 ROM from marcusant's site and it's a port from Desire Z, based on One V seemingly. So far apart from all the hardware issues (wifi, cam, sensor), only thing that prevented me from sticking to it is that SystemUI often FCs. And I think that is another base to start on, since IT'S QUALCOMM.
Sent from HTC Incredible S @ Sense 4.1
AndyYan said:
And this means all my expectes efforts should be in vain, huh?
But check this, I got a Sense 4 ROM from marcusant's site and it's a port from Desire Z, based on One V seemingly. So far apart from all the hardware issues (wifi, cam, sensor), only thing that prevented me from sticking to it is that SystemUI often FCs. And I think that is another base to start on, since IT'S QUALCOMM.
Sent from HTC Incredible S @ Sense 4.1
Click to expand...
Click to collapse
What it called? I must have made that but i don't remember
Sent from my LG-LS970 using xda app-developers app
xboxfanj said:
What it called? I must have made that but i don't remember
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
And I think that must be your ROM 'cuz I've never heard of Marcusant doing that...
It's SpiderSense.
Sent from HTC Incredible S @ Sense 4.1
AndyYan said:
And I think that must be your ROM 'cuz I've never heard of Marcusant doing that...
It's SpiderSense.
Sent from HTC Incredible S @ Sense 4.1
Click to expand...
Click to collapse
I think that is just the original ROM but with modified app and framework.
xboxfanj said:
I think that is just the original ROM but with modified app and framework.
Click to expand...
Click to collapse
Is that so? There are two items in About Phone indicating phone model. One of them says "HTC One V", which I think is the port source, while the other says "HTC Desire Z", which is the device ported to I assume. I know that these can be modded, but why the hell does anyone take the trouble to mod it to Desire Z when we are Epic 4G? Thus I think it's a Qualcomm port.
Have you looked into it yet? Or maybe it's really your work and you know about it?
Sent from HTC Incredible S @ Sense 4.1
AndyYan said:
Is that so? There are two items in About Phone indicating phone model. One of them says "HTC One V", which I think is the port source, while the other says "HTC Desire Z", which is the device ported to I assume. I know that these can be modded, but why the hell does anyone take the trouble to mod it to Desire Z when we are Epic 4G? Thus I think it's a Qualcomm port.
Have you looked into it yet? Or maybe it's really your work and you know about it?
Sent from HTC Incredible S @ Sense 4.1
Click to expand...
Click to collapse
I had probably used the desire z build prop as well so it used some lines for our resolution. It's definitely my work. I remember making it..
Sent from my LG-LS970 using xda app-developers app
xboxfanj said:
I had probably used the desire z build prop as well so it used some lines for our resolution. It's definitely my work. I remember making it..
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
...So this means I should give up on that huh? Sigh.
Sent from HTC Incredible S @ Sense 4.1
You're only limited to the limits you place upon yourself, research, persevere, and you may get it working.
Sent from my SPH-D700 using xda premium
Shinydude100 said:
You're only limited to the limits you place upon yourself, research, persevere, and you may get it working.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Thanks for the encouragement, dude, but Senior III is extremely stressful in China, so I don't have time to look into anything that serious for now.
Sent from HTC Incredible S @ CM10
Related
Hi there,
Is it even possible to port over the HTC Flyer ROM for the kindle fire? I just think it would be cool to have a Sense ROM out there for the Kindle
ps. sorry if this is in the wrong section. im new to the forums
Probably not. Sense isn't open source
sent from my newly unlocked Rezound
pwned3 said:
Probably not. Sense isn't open source
sent from my newly unlocked Rezound
Click to expand...
Click to collapse
well that sucks...alright thanks though
I bet we will see sense pop up for this by lets say washingtons birthday.
Sent from my Amazon Kindle Fire
androidcues said:
I bet we will see sense pop up for this by lets say washingtons birthday.
Sent from my Amazon Kindle Fire
Click to expand...
Click to collapse
Why's that
Sent from my ADR6350 using XDA App
bradsinram said:
Why's that
Sent from my ADR6350 using XDA App
Click to expand...
Click to collapse
Why? Cuz Im a gamblin man. I am just betting that a Sense Dev has a hardon for the KF right now and wants to get some heavy UI action going on it.
This probably won't happen for your Kindle Fire's. HTC Sense has it's own framework to work around and to get it to work on a non-htc device would require working from the ground up. Which most devs arent going to put in that much time. Currently I have only seen a sense build for one non htc device (Nexus S I think..) and that doesnt mean there aren't more though.
In all I am just saying don't get your hopes up for a build, or a mostly functioning one at that.
Sent from my HTC EVO Shift 4G
notsointeresting said:
This probably won't happen for your Kindle Fire's. HTC Sense has it's own framework to work around and to get it to work on a non-htc device would require working from the ground up. Which most devs arent going to put in that much time. Currently I have only seen a sense build for one non htc device (Nexus S I think..) and that doesnt mean there aren't more though.
In all I am just saying don't get your hopes up for a build, or a mostly functioning one at that.
Sent from my HTC EVO Shift 4G
Click to expand...
Click to collapse
Beat me to it. I'd owned a few other non HTC devices hoping that Sense would be ported. But after extensive research and having done a few simple mods myself to Sense for theming, it's quite an undertaking to get Sense running smoothly. It's pretty fickle like that, porting over Sense features between HTC devices with different Sense versions is hard enough.
tldr: Don't get your hopes up. Do what I did and install Launcher Pro and Fancy Widgets and do your best to make CM7 look like Sense.
notsointeresting said:
This probably won't happen for your Kindle Fire's. HTC Sense has it's own framework to work around and to get it to work on a non-htc device would require working from the ground up. Which most devs arent going to put in that much time. Currently I have only seen a sense build for one non htc device (Nexus S I think..) and that doesnt mean there aren't more though.
In all I am just saying don't get your hopes up for a build, or a mostly functioning one at that.
Sent from my HTC EVO Shift 4G
Click to expand...
Click to collapse
Are you kidding me, just need to find something with the specs close enough to the kindle then it could happen. Especially since we wont be neding the phone services at all.
LOL whats up notsointeresting!
PS this should have been posted in the General section
androidcues said:
Why? Cuz Im a gamblin man. I am just betting that a Sense Dev has a hardon for the KF right now and wants to get some heavy UI action going on it.
Click to expand...
Click to collapse
Well I having an incredible 2 I'm quite the sense lover my self but I'm not gonna get my hopes up for us to get this although I've even seen semi working builds of sense on the Samsung captivate
Sent from my ADR6350 using XDA App
Maybe we can start this project and ask devs to help i have ported sense 2.1 from nexus s 4G to 3G and i want to help this can become a amazing rom.
yesterday i already tried building the rom but when i flash it with TWRP it reboots while flashing
Yea its possible and maybe a lil easier then a phone port. Theres no radio or bluetooth to fix. Just working wifi. Oh and I was gonna say the HTC G2 got a port (its a pure aosp) but im sure they did the ground work using the Desire Z.
Yes we can do it with the great developers of XDA.
BTW we can use the Leaked Honeycomb RUU from the htc flyer i have made a rom but it keeps crashing while flashing. I am trying to get it booted
Sent from my Nexus S using XDA App
EDIT: I will create a new tread for this
MIUI official port TUTORIAL
PDF
Chinese
here is english tutorial http://forum.xda-developers.com/showthread.php?p=22228486
Hope someone could port it to WFS
download
http://dl.dbank.com/c0bl30govp
HTC Wildfire S has ARMv6 processor, and MIUI is made for phones with ARMv7 processors.. So no MIUI for us
droid000 said:
HTC Wildfire S has ARMv6 processor, and MIUI is made for phones with ARMv7 processors.. So no MIUI for us
Click to expand...
Click to collapse
That's nonsense.
its not about the processor......its about the HUGE resizing which is main pain in the butt..........you do know ICS is meant for ARMv7 and above processors but it is running quite smooth on my friend's Wildfire.....
MIUI is the most good looking rom for any android phone. It would be great if we manage to port it to hdpa screen.
*se-nsei. said:
That's nonsense.
Click to expand...
Click to collapse
My mistake, didn't know that MIUI is open source now.. but just like csoulr666 said.. there is huge resizing and it requires lot of knowelge about programming.. it would be great if somebody ports it to ours wilfire s
First Miui ROM coming soon
I did it, I worked about 20 hours to port miui onto our phones
Alpha test comes soon!
I wont port it to WFS, I hate resizing, I had it to do a lot already in HenseMod for the custom theming.
For MIUI there's also a special framework, like htcresources.apk, which makes it difficult to port to WFS.
However, I've got some things in my mind and on my mac, expect end next week a flashable zip for CM7 users to turn your phone into MIUI.
matt5eo said:
I did it, I worked about 20 hours to port miui onto our phones
Alpha test comes soon!
Click to expand...
Click to collapse
Nice!! Can't wait
matt5eo said:
I did it, I worked about 20 hours to port miui onto our phones
Alpha test comes soon!
Click to expand...
Click to collapse
very excited
matt5eo said:
I did it, I worked about 20 hours to port miui onto our phones
Alpha test comes soon!
Click to expand...
Click to collapse
Any chance of this working on the A510a? (CDMA, MetroPCS.)
Sent from my HTC-PG762 using XDA App
bobdamnit said:
Any chance of this working on the A510a? (CDMA, MetroPCS.)
Sent from my HTC-PG762 using XDA App
Click to expand...
Click to collapse
Its A510c for us cdma users
Sent from my HTC_A510c using Tapatalk
kagevazquez said:
Its A510c for us cdma users
Sent from my HTC_A510c using Tapatalk
Click to expand...
Click to collapse
No, in my manual it is listed as model A510a. Even says that behind the battery.
Sent from my HTC-PG762 using XDA App
bobdamnit said:
No, in my manual it is listed as model A510a. Even says that behind the battery.
Sent from my HTC-PG762 using XDA App
Click to expand...
Click to collapse
Mine's an A510a and it's GSM with SIM.
Could this be the reason why porting to metro pcs phones requires more work? Or is this just a little miss understanding?
Sent from my HTC_A510c using Tapatalk
kagevazquez said:
Could this be the reason why porting to metro pcs phones requires more work? Or is this just a little miss understanding?
Sent from my HTC_A510c using Tapatalk
Click to expand...
Click to collapse
I really don't know, as I don't do much developing. I leave that to the pros.
However, I am willing to test anything on this phone just to get rid of HTC Sense. I have an LG Optimus M I can always fall back on.
I will also say that MetroPCS is a CDMA only carrier, and the original WFS required a SIM card and ours does not. Maybe they got HTC to modify the phone for them?
But the phone manual says its an A510a. insink made a MetroPCS stock ROM with a2sd support and that's what I'm currently using, and it was even labeled for A510a only.
Ill be kinda upset if I just bought a phone that's impossible to develop ROMS on lol
Sent from my HTC-PG762 using XDA App
Apologies. I just left the MetroPCS store, paying my bill. I inquired about my phone being an A510a. They told me that my phone manual isn't correct, and that it is indeed an A510c.
Again, I was misinformed. And I apologise.
Sent from my HTC-PG762 using XDA App
What do you think will run better on our phone Sense 4 or Sense 3.6? I am assuming Sense 3.6 since its going to actually get officially released but not so sure since Sense 4 is lighter. And do you think any of these 2 will be faster then stock ICS such as cyanongeMOD 9 when that will be officially released.
jakob95 said:
What do you think will run better on our phone Sense 4 or Sense 3.6? I am assuming Sense 3.6 since its going to actually get officially released but not so sure since Sense 4 is lighter. And do you think any of these 2 will be faster then stock ICS such as cyanongeMOD 9 when that will be officially released.
Click to expand...
Click to collapse
It will never be faster then the slimmed down stock ics
Sent from my Incredible 2 using xda premium
Sense 4 will. Its so much lighter of a UI than sense 3.6. But neither will run as well as AOSP
Sent from my ADR6350 using xda premium
Well comparing stock Sense 2.1 we get with the ROM, I could say its much faster and stable then AOSP Gingerbread(CyanongenMod).
jakob95 said:
Well comparing stock Sense 2.1 we get with the ROM, I could say its much faster and stable then AOSP Gingerbread(CyanongenMod).
Click to expand...
Click to collapse
No way...
Sent from my Incredible 2 using xda premium
i honestly dont know which will run better, but sense 4 runs well (and smooth)
id have to think sense 3.6 will run best just cuz it will be official, but idk
We should get Sense 4.0 ported from the One V as its lighter, and has the good ICS multitasking interface.
jakob95 said:
We should get Sense 4.0 ported from the One V as its lighter, and has the good ICS multitasking interface.
Click to expand...
Click to collapse
umm, thats what we're doing now
nitsuj17 said:
umm, thats what we're doing now
Click to expand...
Click to collapse
I got a good lolz from that
Sent from my Incredible 2 using xda premium
nitsuj17 said:
umm, thats what we're doing now
Click to expand...
Click to collapse
No we aren't doing that, we are porting it from the one x and s
Sent from my ADR6350 using XDA
I'm running opensense4 and I gotta say it runs very smoothly for an alpha, as soon as sense 4.0 and cm9 get fixed up I'm never going back to any gb Rom.
Sent from my vivow using XDA
jakob95 said:
No we aren't doing that, we are porting it from the one x and s
Sent from my ADR6350 using XDA
Click to expand...
Click to collapse
are you serious? you are correcting the guy who is doing the actual porting...unbelievable
just to clear up any confusion YOU ARENT PORTING ANYTHING, OTHER DEVS AND I HAVE BEEN and its from the one v
the one x is a hd resolution device and the one s a qhd resolution device.....these roms would have to be resized to work on our wvga res phone, whereas the one v does not, thats why all the wvga msm7x30 devices are using RUU's from the one v
i dont mean to be an ass, but dont correct me if you dont know ****, thanks
jakob95 said:
No we aren't doing that, we are porting it from the one x and s
Sent from my ADR6350 using XDA
Click to expand...
Click to collapse
If you want to resample over a thousand images from the One X or One S to match the resolution of the Vivow, then more power to you. Oh, wait... that is just the beginning - I forgot to mention the thousands of lines of code in the xml files you'll have to search through to make the needed resolution changes there also. Oops, still not done: that was just for the theme, that's not even counting the code in the ROM itself that provides instruction for all the apps to set the proper screen resolution for their graphics. Or you could just port the same Sense 4.0 ROM from the One V, with the proper resolution already set in the code and the graphics.
Terminators run on Android
Read the OP for opensense.. It's One V... And Nitsuj is the one who started it so I'm pretty sure he knows what device he is trying to port. The man is pretty ****ing amazing with his ****... The Roms Dont stink...
EDIT: didn't realize nit already responded, but the statement I have made still stands. Great job Nit
Sent from my Incredible 2 using xda premium
nitsuj17 said:
are you serious? you are correcting the guy who is doing the actual porting...unbelievable
just to clear up any confusion YOU ARENT PORTING ANYTHING, OTHER DEVS AND I HAVE BEEN and its from the one v
the one x is a hd resolution device and the one s a qhd resolution device.....these roms would have to be resized to work on our wvga res phone, whereas the one v does not, thats why all the wvga msm7x30 devices are using RUU's from the one v
i dont mean to be an ass, but dont correct me if you dont know ****, thanks
Click to expand...
Click to collapse
This made me lol. I love you nit.
Sent From My Mikrunny'd Superphone Using Magic (TapaTalk 2 Beta 2)
nitsuj17 said:
are you serious? you are correcting the guy who is doing the actual porting...unbelievable
just to clear up any confusion YOU ARENT PORTING ANYTHING, OTHER DEVS AND I HAVE BEEN and its from the one v
the one x is a hd resolution device and the one s a qhd resolution device.....these roms would have to be resized to work on our wvga res phone, whereas the one v does not, thats why all the wvga msm7x30 devices are using RUU's from the one v
i dont mean to be an ass, but dont correct me if you dont know ****, thanks
Click to expand...
Click to collapse
BURN!
BOOOOOOOOM goes the dynamite!
nitsuj17 said:
are you serious? you are correcting the guy who is doing the actual porting...unbelievable
just to clear up any confusion YOU ARENT PORTING ANYTHING, OTHER DEVS AND I HAVE BEEN and its from the one v
the one x is a hd resolution device and the one s a qhd resolution device.....these roms would have to be resized to work on our wvga res phone, whereas the one v does not, thats why all the wvga msm7x30 devices are using RUU's from the one v
i dont mean to be an ass, but dont correct me if you dont know ****, thanks
Click to expand...
Click to collapse
I am sorry I didn't look at the username of the person who made that first quote. And I wasn't talking about your ROM in the first place(don't know much about yours), I was talking about the One S ROM over at Mikrunny.
http://themikmik.com/showthread.php?11845-ROM-HTC-ONE-S-beta-1-(-vivio-W)-sense-4-0-and-ICS-4-0-3
I am sorry I didn't know yours was One V thought it was One S as well.
jakob95 said:
I am sorry I didn't look at the username of the person who made that first quote. And I wasn't talking about your ROM in the first place(don't know much about yours), I was talking about the One S ROM over at Mikrunny.
http://themikmik.com/showthread.php?11845-ROM-HTC-ONE-S-beta-1-(-vivio-W)-sense-4-0-and-ICS-4-0-3
I am sorry I didn't know yours was One V thought it was One S as well.
Click to expand...
Click to collapse
the one on themikmik is also one v, it was mislabeled as one s, there IS NO ONE S OR ONE X port, nor will there be for this phone
newt is also not maintaining a separate rom gong forward afaik and will be assisting with fixes on opensense
nitsuj17 said:
the one on themikmik is also one v, it was mislabeled as one s, there IS NO ONE S OR ONE X port, nor will there be for this phone
newt is also not maintaining a separate rom gong forward afaik and will be assisting with fixes on opensense
Click to expand...
Click to collapse
Alright, I am sorry for my ignorance. Thank you for your hard work to bring this ROM to us.
Do you think Android KitKat would be compatible with Wildfire? It is designed for lower end devices so would it be possible for a port of that new OS?
KoolKid98189 said:
Do you think Android KitKat would be compatible with Wildfire? It is designed for lower end devices so would it be possible for a port of that new OS?
Click to expand...
Click to collapse
Probably not. while it may technically be possible to achieve it is highly unlikely that anyone will be able to do it successfully, or even partially.
Just my 2 pence.
heavy_metal_man said:
Probably not. while it may technically be possible to achieve it is highly unlikely that anyone will be able to do it successfully, or even partially.
Just my 2 pence.
Click to expand...
Click to collapse
Fair but this could be a chance to breathe new life into our Wildfire, just saying.
KoolKid98189 said:
Fair but this could be a chance to breathe new life into our Wildfire, just saying.
Click to expand...
Click to collapse
I agree that it could be a very good opportunity, im just saying dont get your hopes up i suppose :/ we just about got got 4.1.2 from this dev here . alot of the "main players" have moved on from this device and i dont think we would have the skill to manage this. to start off with we would need a 3.4 kernel i believe, and i dont think they re-introduced support for non gpu devices in 4.3 kitkat so we would need to implement all the hacks that were required to get ics running and port them over to kitkat.
its a nice idea, but to be honest i think the amount of hours it would need to make it function may not actually work towards a stable daily driver
i`m amazed the wildfire got this far to be honest, and im happy i was here for it
heavy_metal_man said:
I agree that it could be a very good opportunity, im just saying dont get your hopes up i suppose :/ we just about got got 4.1.2 from this dev here . alot of the "main players" have moved on from this device and i dont think we would have the skill to manage this. to start off with we would need a 3.4 kernel i believe, and i dont think they re-introduced support for non gpu devices in 4.3 kitkat so we would need to implement all the hacks that were required to get ics running and port them over to kitkat.
its a nice idea, but to be honest i think the amount of hours it would need to make it function may not actually work towards a stable daily driver
i`m amazed the wildfire got this far to be honest, and im happy i was here for it
Click to expand...
Click to collapse
Yeah I to agree, also I wish there was a way to
So when android kitkat is released, I myself will try to port this, even if its not possible! I must still try
Sent from my HTC Wildfire using xda app-developers app
port?
that's not a proper word, we'll have to build it from scratch.
Wasimk32 said:
port?
that's not a proper word, we'll have to build it from scratch.
Click to expand...
Click to collapse
What is scratch ? You may say sources.And i think it's possible if erwin p and all the old dev come back and tried to build an new rom.
Sent from my HTC Wildfire using xda premium
Pator57 said:
What is scratch ? You may say sources.And i think it's possible if erwin p and all the old dev come back and tried to build an new rom.
Sent from my HTC Wildfire using xda premium
Click to expand...
Click to collapse
Scratch is basically start from the beginning, and it's always better to try making a KitKat ROM for Wildfire, you never know what the outcome could be right?
Wasimk32 said:
port?
that's not a proper word, we'll have to build it from scratch.
Click to expand...
Click to collapse
Pator57 said:
What is scratch ? You may say sources.And i think it's possible if erwin p and all the old dev come back and tried to build an new rom.
Sent from my HTC Wildfire using xda premium
Click to expand...
Click to collapse
Both are real words, just used in different context :thumbup: but yeah it would be defiantly a build from scratch job (using our own source code we would have to make specific to the wildfire)
Sent from my HTC Sensation XE with Beatse Audio Z715e using Tapatalk 2
So what we are waiting ?
For bigin, who is able to build or port an 4.2/4.3 kernel for our wildfire.
Sent from my HTC Wildfire using xda premium
Pator57 said:
So what we are waiting ?
For bigin, who is able to build or port an 4.2/4.3 kernel for our wildfire.
Sent from my HTC Wildfire using xda premium
Click to expand...
Click to collapse
Ah, now that is the real question. If the kernel doesn't get made then this is dead before it starts like.
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
Pator57 said:
So what we are waiting ?
For bigin, who is able to build or port an 4.2/4.3 kernel for our wildfire.
Sent from my HTC Wildfire using xda premium
Click to expand...
Click to collapse
We are waiting for Android KitKat to be released, we need a device that has a QVGA screen with a resolution of 240 x 320 pixels
AFAIK it would run without a 3.4 or even a 3.8 kernel. But the current 2.6 kernel would slow it down. Only very experienced devs can make properly working kernels. And we have almost no 'real' "i build from source" dev left in this forum. (not offensive, i appreciate the work of any dev/porter/whatever here )
4.1 is also running fine with that old arco - kernel but its really slow maybe because of the hardware maybe because of the kernel. I think its a mix of both components.
I tried with @kylon to get a functioning overclock kernel for the htc wildfire bee, (cdma device) and we couldn't manage to get it stable, and that's the buzz's sister phone. It shares almost all the same hardware :/ so I don't think it will be an easy task.
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
miniAndroidian said:
AFAIK it would run without a 3.4 or even a 3.8 kernel. But the current 2.6 kernel would slow it down. Only very experienced devs can make properly working kernels. And we have almost no 'real' "i build from source" dev left in this forum. (not offensive, i appreciate the work of any dev/porter/whatever here )
4.1 is also running fine with that old arco - kernel but its really slow maybe because of the hardware maybe because of the kernel. I think its a mix of both components.
Click to expand...
Click to collapse
Yea i know that all the dev have left the wildfire, but we can always learn and tried to building one.
Sent from my HTC Wildfire using xda premium
Pator57 said:
Yea i know that all the dev have left the wildfire, but we can always learn and tried to building one.
Sent from my HTC Wildfire using xda premium
Click to expand...
Click to collapse
Yeah, hopefully this could be a success
KoolKid98189 said:
Yeah, hopefully this could be a success
Click to expand...
Click to collapse
Just my 2p worth but doesn't kitkat and the kernel associated with it look for integrated GPU's which the wildfire simply doesn't have, so if someone was to create a kernel for kitkat you would have to emulate a GPU on the CPU which would slow down the phone to a unusable piece of crap.
Good idea but i doubt it's viable.
DosKey123 said:
Just my 2p worth but doesn't kitkat and the kernel associated with it look for integrated GPU's which the wildfire simply doesn't have, so if someone was to create a kernel for kitkat you would have to emulate a GPU on the CPU which would slow down the phone to a unusable piece of crap.
Good idea but i doubt it's viable.
Click to expand...
Click to collapse
Agreed. Ics barely ran without the kernel hacks to make it run. Though it is said that kitkat should be less resource hungry.
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
heavy_metal_man said:
Agreed. Ics barely ran without the kernel hacks to make it run. Though it is said that kitkat should be less resource hungry.
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
Click to expand...
Click to collapse
Yeah but did ICS have no GPU support? If it did then try porting the ICS hacks to KitKat and see how it goes.
KoolKid98189 said:
Yeah but did ICS have no GPU support? If it did then try porting the ICS hacks to KitKat and see how it goes.
Click to expand...
Click to collapse
While it's possible I have no idea what hacks were done to make it work. We needed kernel hacks for gingerbread.... The only one that would definitely know would be Arco, as he was the kernel developer for the buzz branch of cyanogenmod. I think most of the work on cm7 and 9 were arcos work, with some help from the guys here of course
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
i need a ported ubuntu touch ((
Buzz does not support Ubuntu, if there was a way we'd all try
But no. Sorry
Sent from my HTC Wildfire using xda app-developers app
No way of getting Ubuntu port, I think we were Lucky enough to get Cyanogenmod9 let alone 10/.2
Will_Xda said:
No way of getting Ubuntu port, I think we were Lucky enough to get Cyanogenmod9 let alone 10/.2
Click to expand...
Click to collapse
It's almost impossible :/
Stone. Cold said:
It's almost impossible :/
Click to expand...
Click to collapse
Past Devs already confirmed it would be useless even trying for XYZ reasons. I don't see what benefits we could get from it.
Now what I would like to see for Wildfire is a working sense3 port.
But tbh I'm just happy to see people are still using the Phone and people such as you are still Deving & theming
Sent from my HTC Desire X using xda app-developers app
Will_Xda said:
Past Devs already confirmed it would be useless even trying for XYZ reasons. I don't see what benefits we could get from it.
Now what I would like to see for Wildfire is a working sense3 port.
But tbh I'm just happy to see people are still using the Phone and people such as you are still Deving & theming
Sent from my HTC Desire X using xda app-developers app
Click to expand...
Click to collapse
I'll try look into sense 3, i know people been waiting a while for the sense 3.5
So i'll try to make one, also we may need a new kernal for the sense 3.5, because the current is in ok condition, but not stabler enough :/
Going to see if i can fix all the issues myself :good:
hmmm, sense 3,5 won't work good. maybe try to play around sense 2.1 first (;
Sent from my HTC Wildfire using xda app-developers app
drewniany92 said:
hmmm, sense 3,5 won't work good. maybe try to play around sense 2.1 first (;
Sent from my HTC Wildfire using xda app-developers app
Click to expand...
Click to collapse
It won't work good, because almost all the apks in the ROM are not ldpi and not compatible with the device, although i'm looking into this further more in development.
I'll try to compile sources from different devices with sense 3.5 which have some ldpi compatible features