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
Related
OFFICIAL NEWS...SORRY GUYS
What devices will not get Android 4.0?
We work hard to ensure each of our products has the optimal user experience and therefore some products will remain at their current version of Android. In general, devices with 512MB ROM or less will not be upgraded to Android 4.0. These devices include the HTC ChaCha, HTC Salsa, HTC Wildfire S, HTC Explorer, and others.
Thank the devs for CM9
I think it's been pretty clear from the beginning that the WFS is not a candidate for HTC ICS. Therefore:
bobdarkside said:
Thank the devs for CM9
Click to expand...
Click to collapse
+1
This is the reason why devs exist,
Already knew it. No regrets here.
HTC=N00b
[email protected] works even smoother and faster than all stock ROMs (and I could be wrong, but feels like even faster than CM7 )
Everyone Already Knew. No regrets.
The devs rock. Period.
bobdarkside said:
Thank the devs for CM9
Click to expand...
Click to collapse
CafeKampuchia said:
I think it's been pretty clear from the beginning that the WFS is not a candidate for HTC ICS. Therefore:
+1
Click to expand...
Click to collapse
klacenas said:
This is the reason why devs exist,
Click to expand...
Click to collapse
Scyllax said:
Already knew it. No regrets here.
Click to expand...
Click to collapse
davidang said:
HTC=N00b
Click to expand...
Click to collapse
nforester said:
[email protected] works even smoother and faster than all stock ROMs (and I could be wrong, but feels like even faster than CM7 )
Click to expand...
Click to collapse
SomeDudeOnTheNet said:
Everyone Already Knew. No regrets.
The devs rock. Period.
Click to expand...
Click to collapse
I know,i know,i know,i know....
Agree,agree,agree,agree...
Just sharing the news for the ones that dont know
Y they r launching desire c which has got 512 mb ram with ics?
They r dumb people...just interested in launching new one....any way we have to thank them for desire c, for providing better chance for sense 4 porting
Sent from my HTC Wildfire S A510e using XDA
ok htc
i'll be a very rude person and stick to my cyanogenmod 9
which has much better battery life and lasts more than half of the day
smartboy0668 said:
Y they r launching desire c which has got 512 mb ram with ics?
Click to expand...
Click to collapse
Because ROM and RAM are not the same thing. 512MB RAM is fine, but 512MB of ROM (Stupid naming, as it isn't really read-only) is a problem when you toss in sense on top of base android. It would leave you practically no space for apps (which is already an issue on GB) or anything without link2SD or similar, which HTC isn't going to be doing as stock. For example, my incredible S (which is getting ICS) has a full 1.1GB of ROM, so they have loads of space to play with.
There's people in the dev section working to port the golf (aka desire c) ICS rom to the wildfire S. They're only able to get it to fit via extra optimizations (deodexing, pngcrush, stripping optional stuff, etc.)that HTC wouldn't be interested in using.
Yes, no offical ICS for us, but htc says that we will get more software updates
droid000 said:
Yes, no offical ICS for us, but htc says that we will get more software updates
Click to expand...
Click to collapse
2.3.5 was the last...AFAIK
Sent from my HTC Wildfire S A510e using XDA
smartboy0668 said:
2.3.5 was the last...AFAIK
Sent from my HTC Wildfire S A510e using XDA
Click to expand...
Click to collapse
Gingerbread went up to 2.3.7.
But the fixes in those aren't real relevant to the WFS. 2.3.6 fixed a voice search bug and 2.3.7 added wallet support to the nexus S.
compro01 said:
Gingerbread went up to 2.3.7.
But the fixes in those aren't real relevant to the WFS. 2.3.6 fixed a voice search bug and 2.3.7 added wallet support to the nexus S.
Click to expand...
Click to collapse
Thanks for explaining some stuff,and about the ROM/RAM,,,i just cant be bothered sometimes to type
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
I'm pretty sure this is the most ridiculous question our wildfire devs will ever hear.... but anyways here it goes!...
I was wondering if kernel 3.x is applicable/possible/needed for wildfire???.(the devs can laugh now!)...It's just that I'm currently following many device forums on xda and they seem to be pretty excited about the kernel 3.0 stuff.....I just wanted to know if our wildfire can have the luxury of kernel 3.x ...
And obviously from the question itself you will know that I'm a complete newbie ..:silly:
nrjwgh said:
I'm pretty sure this is the most ridiculous question our wildfire devs will ever hear.... but anyways here it goes!...
I was wondering if kernel 3.x is applicable/possible/needed for wildfire???.(the devs can laugh now!)...It's just that I'm currently following many device forums on xda and they seem to be pretty excited about the kernel 3.0 stuff.....I just wanted to know if our wildfire can have the luxury of kernel 3.x ...
And obviously from the question itself you will know that I'm a complete newbie ..:silly:
Click to expand...
Click to collapse
I think that it would be so difficully that its very unlikely. Sorry buddy
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
heavy_metal_man said:
I think that it would be so difficully that its very unlikely. Sorry buddy
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Click to expand...
Click to collapse
Yeah I thought so! Can you please explain why it's difficult to develop?
Sent from my Wildfire using xda app-developers app
nrjwgh said:
Yeah I thought so! Can you please explain why it's difficult to develop?
Sent from my Wildfire using xda app-developers app
Click to expand...
Click to collapse
Well I don't profess to know what needs to be done but I imagine that all the drivers will need to be ported, as well as that fact that we have no gpu. That could cause issues with the kernel hacks that are already in place just so we can run gingerbread, let alone jellybean. Which I think is needed for the 3.x kernel. But again I don't know, I'm just speculating.
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
heavy_metal_man said:
Well I don't profess to know what needs to be done but I imagine that all the drivers will need to be ported, as well as that fact that we have no gpu. That could cause issues with the kernel hacks that are already in place just so we can run gingerbread, let alone jellybean. Which I think is needed for the 3.x kernel. But again I don't know, I'm just speculating.
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Click to expand...
Click to collapse
U think 3.x kernels should work on ICS as well, since my phone came with ICS and a 3.x kernel.
Sent from my Galaxy Nexus using xda premium
I would like that if it was possible to happen but there's always a way of getting it
Sent from my HTC Wildfire using xda app-developers app
Not possible or is it?
I'm really curious to is there anyway this HTC Wildfire getting that kernal if there's a way hopefully people shall revealing their secrets and how they do it :]
But for now there "currently i sn't m8"
------------------------------------------
Btw i'm new to this all :]:good:
Since I can't post this in the CM10 thread itself, I'll ask here.
What's going to be of the CM10 for the One V? As I see Lloir has stopped all development for the One V. I'm just curious and it's one of my concerns, don't be asking me to do it myself etc.
Thanks.
Hope for the best mate.... Someone will be there....:fingers crossed:
Yeah I wonder too...
I hope its not the end of the v
Sent from my One V
rohov said:
Someone will be there....:fingers crossed:
Click to expand...
Click to collapse
soham_sss said:
I hope its not the end of the v
Sent from my One V
Click to expand...
Click to collapse
Till 1ce,ck,etc.etc....will be there,dev won't ever stop...its not a dead device and never will be.
I hope so too! I just got my device and is doing sufficient for me, especially with CM10, love it!
Just hope something happens with codefireX, that's an awesome ROM.....
Why the hell won't it boot is a question.:banghead:
Sent from my One V
soham_sss said:
Just hope something happens with codefireX, that's an awesome ROM.....
Why the hell won't it boot is a question.:banghead:
Sent from my One V
Click to expand...
Click to collapse
It's because 4.2.2 doesn't really work for PrimoU yet. The devs are working on it.
There are so many features of the CM10 I'm unwilling to give up, the status bar brightness control, the sweep2on feature is definitely my favourite.
MormegilND said:
It's because 4.2.2 doesn't really work for PrimoU yet. The devs are working on it.
Click to expand...
Click to collapse
I know the question is: why wont it boot
The answer cannot be because it does not work properly:banghead:
Sent from my One V
RedGoblinz said:
There are so many features of the CM10 I'm unwilling to give up, the status bar brightness control, the sweep2on feature is definitely my favourite.
Click to expand...
Click to collapse
dude the "sweep2on" feature is a feature a the kernel not cm10 roms
soham_sss said:
I know the question is: why wont it boot
The answer cannot be because it does not work properly:banghead:
Sent from my One V
Click to expand...
Click to collapse
It doesn't work properly because they're still working on the kernel drivers. Therefore, it won't boot.
Really? I never thought of that, lol. Just a question, it's alright if you dont answer I understand: What ROMs use Maxwen's HELLBOY?
RedGoblinz said:
Really? I never thought of that, lol. Just a question, it's alright if you dont answer I understand: What ROMs use Maxwen's HELLBOY?
Click to expand...
Click to collapse
All jb ROMs are compatible with hellboy
Sent from my One V
soham_sss said:
All jb ROMs are compatible with hellboy
Sent from my One V
Click to expand...
Click to collapse
But Hellboy is only for GSM devices. If you have a PrimoC, go with one of Simon's kernels.
Are the differences between the X/XL/S/V quite considerable? I don't mean in terms of RAM, screen size, etc. but actual chips, models, etc.? I noticed that CM10.1 has official M-releases for the XL and S.
I wonder if they just limit the devices that are accepted into main, regardless of the quality of their branch, or if there are just a few things missing from Lloid's work that would let it get integrated into mainline.
Sadly, the One V is by far the weakest and most entry-level device of the One line.
HOV = 1ghz/1core
HOS = 1.5ghz/2core
HOX (global edition) = 1.5ghz/4core
HOX+ = 1.7ghz/4core
bananabux said:
Sadly, the One V is by far the weakest and most entry-level device of the One line.
HOV = 1ghz/1core
HOS = 1.5ghz/2core
HOX (global edition) = 1.5ghz/4core
HOX+ = 1.7ghz/4core
Click to expand...
Click to collapse
your just realising that? :laugh:
tyraen said:
Are the differences between the X/XL/S/V quite considerable? I don't mean in terms of RAM, screen size, etc. but actual chips, models, etc.? I noticed that CM10.1 has official M-releases for the XL and S.
I wonder if they just limit the devices that are accepted into main, regardless of the quality of their branch, or if there are just a few things missing from Lloid's work that would let it get integrated into mainline.
Click to expand...
Click to collapse
easiest way to get officially supported by CM is - someone from CM to own a One V
bananabux said:
Sadly, the One V is by far the weakest and most entry-level device of the One line.
Click to expand...
Click to collapse
Sorry, like I said I didn't mean in terms of processor, etc. Unless you mean there differences between CPU architectures that make it hard to support CM10.1?
1ceb0x said:
easiest way to get officially supported by CM is - someone from CM to own a One V
Click to expand...
Click to collapse
Darn.
1ceb0x said:
easiest way to get officially supported by CM is - someone from CM to own a One V
Click to expand...
Click to collapse
Like he said... If someone can donate a one v to cm it'll be nice lol
Sent from my HTC One V using xda app-developers app
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