Related
Hello everyone, I'm associated with custom roms for sgy. Recently I met a person, who had successfully installed an sgy custom rom in galaxy ace. These two phones are more similar than we ever thought. So, why not the other way around??? Interested devs could actually modify ace ics roms and install it on y, instead of fiddling with galaxy mini????
Fantastic idea, I know, bit not improbable ...Coz I still have the Guy's pm ....
Sent from my GT-S5360 using xda app-developers app
AvijitGhosh82 said:
Hello everyone, I'm associated with custom roms for sgy. Recently I met a person, who had successfully installed an sgy custom rom in galaxy ace. These two phones are more similar than we ever thought. So, why not the other way around??? Interested devs could actually modify ace ics roms and install it on y, instead of fiddling with galaxy mini????
Fantastic idea, I know, bit not improbable ...Coz I still have the Guy's pm ....
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
Galaxy y roms can be installed on the galaxy ace i s5380i only by changing dpi and kernel but not on the original ace that uses the qualcomm processor and there is no ics for ace i
Enviado desde mi GT-S5360 usando Tapatalk 2
I wanna ask something....
How about safariking's CM9 Project???
Canceled? Aborted? Or Still in progress ?
Sent from my Phone !!!
Rikxzdjz said:
I wanna ask something....
How about safariking's CM9 Project???
Canceled? Aborted? Or Still in progress ?
Sent from my Phone !!!
Click to expand...
Click to collapse
The thread was closed but for now we should try to have a working CM7 instead of trying to build CM9
Enviado desde mi GT-S5360 usando Tapatalk 2
Porobu said:
The thread was closed but for now we should try to have a working CM7 instead of trying to build CM9
Enviado desde mi GT-S5360 usando Tapatalk 2
Click to expand...
Click to collapse
Yeah ... i'm just curious about the CM9... stopped suddenly...
How about CM7 Bugs ?? Bugs fixed list and bug list.... i was confused to the thread....
Sent from my Phone !!!
AvijitGhosh82 said:
Hello everyone, I'm associated with custom roms for sgy. Recently I met a person, who had successfully installed an sgy custom rom in galaxy ace. These two phones are more similar than we ever thought. So, why not the other way around??? Interested devs could actually modify ace ics roms and install it on y, instead of fiddling with galaxy mini????
Fantastic idea, I know, bit not improbable ...Coz I still have the Guy's pm ....
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
no one ever try that but similar method has been done a long time ago for cm7. all running cm7 for sgy is ported from ace. wifi dead, bluetooth dead, graphic buggy, etc.
AvijitGhosh82 said:
Hello everyone, I'm associated with custom roms for sgy. Recently I met a person, who had successfully installed an sgy custom rom in galaxy ace. These two phones are more similar than we ever thought. So, why not the other way around??? Interested devs could actually modify ace ics roms and install it on y, instead of fiddling with galaxy mini????
Fantastic idea, I know, bit not improbable ...Coz I still have the Guy's pm ....
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
As he said there are lot of bugs!! and by the efforts of devs it seems like fixing that is more tough than building a new one!!!
CM9 project Stopped! Sorry everyone can't get it to work whatever i did
Bad news.... :thumbdown:
Sent from my Phone !!!
safariking said:
CM9 project Stopped! Sorry everyone can't get it to work whatever i did
Click to expand...
Click to collapse
No prob....u tried ur best....d main fact is that der can't be a CM9 for sgy....d best we can do is build a custom rom closest to it....btw, do u guys know if ace has CM9?
Sent from heaven!
anasdcool71 said:
No prob....u tried ur best....d main fact is that der can't be a CM9 for sgy....d best we can do is build a custom rom closest to it....btw, do u guys know if ace has CM9?
Sent from heaven!
Click to expand...
Click to collapse
Agree.... :thumbup:
At least we had a working CM7 is enough....
Sent from my Phone !!!
Rikxzdjz said:
Agree.... :thumbup:
At least we had a working CM7 is enough....
Sent from my Phone !!!
Click to expand...
Click to collapse
Ace have CM9
safariking said:
Ace have CM9
Click to expand...
Click to collapse
By galaxyics team ??
Sent from my Phone !!!
Rikxzdjz said:
By galaxyics team ??
Sent from my Phone !!!
Click to expand...
Click to collapse
Yes! why?
http://forum.xda-developers.com/showthread.php?t=1490867
Maybe he will try to port it beta 9 os the latest one from galaxyics
Sent from my GT-S5360 using xda app-developers app
Y don't those of you who are linked to the ace forum tell the devs about this???? I'm sure something IS possible ..
Sent from my GT-S5360 using xda app-developers app
Filip98 said:
Maybe he will try to port it beta 9 os the latest one from galaxyics
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
It should be possible I will ask to maclaw
If ace has cm9, can't we port it to Y...both are arm v6 devices and d hardware is almost same too....
Sent from heaven!
anasdcool71 said:
If ace has cm9, can't we port it to Y...both are arm v6 devices and d hardware is almost same too....
Click to expand...
Click to collapse
you might be not aware the problem. here is the analogy. i have two notebook. both have x86 cpu, both have same lcd size and same resolution. my acer one use nvidia gpu and my asus one use ati. i can install windows 7 on both, but i need different set of driver to make both running without issue. and the problem not only for gpu, but almost for everything. the only one component where both can share same driver is cpu.
in phone world the situation event much worse. in pc world we have ibm-pc compatible. none in phone world. different type using different component and different soc. armv6 only cover cpu side. the other side completely different.
irfanbagus said:
you might be not aware the problem. here is the analogy. i have two notebook. both have x86 cpu, both have same lcd size and same resolution. my acer one use nvidia gpu and my asus one use ati. i can install windows 7 on both, but i need different set of driver to make both running without issue. and the problem not only for gpu, but almost for everything. the only one component where both can share same driver is cpu.
in phone world the situation event much worse. in pc world we have ibm-pc compatible. none in phone world. different type using different component and different soc. armv6 only cover cpu side. the other side completely different.
Click to expand...
Click to collapse
yes but drivers are available for your ati gpu, your soundcard..
it will be something like a 'Frankalaxy' yes, but it would definitly be a start!
btw people must be aware of this but anyway here is an article on freeyourandroid/guide/porting-android .com [remove the space pls]
maybe this could help.
and yes the galaxy ace is closer to galaxy y due to generation of production
i.e mini/gio are old phones while ace and y are in the same generation.
Would request someone to try...
I'm from a pure symbian background and still learning android dev so....
would love if someone could lead to me some heads up article
[Google is my ally]
---------- Post added at 12:13 PM ---------- Previous post was at 12:08 PM ----------
AvijitGhosh82 said:
Y don't those of you who are linked to the ace forum tell the devs about this???? I'm sure something IS possible ..
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
I'm using your next2ics rom and loving it
waiting for your next update
(you do have an experience in rom transgening so, why dont you try it?
would love have cm9 as d almostnext2ics update )
Hi
I've created this thread here in general to try an effort to a collaborative port of (any) sense rom to galaxy nexus, lets to the point:
I was trying a different rom instead of the stock. Why? Because a custom rom with sense provide lots of things that stock doesn't have (init.d for example). In my case, I was using Insert Coin for One X, because in the past I had some success with other devices.. well. I didn't had the same success with galaxy nexus.
Of course any rom can be used, we need success in this port disregard the rom used.
Obs.: For people unable to help and able to troll, this isn't a thread for trolling/blaming/"giving the unrequired opinion about it" or "why not buying a HTC phone instead", please, you can create your own thread for that or just use your facebook.
Thanks
I think there was already a thread about a wip port of sense and touchwiz that booted but some major stuff wasn't working.
Sent from my Galaxy Nexus using Tapatalk 2
I have one question about porting sense, what ROM is the best to use as base, cm10 or aosp?
I did some porting on my Droid 3 so I want to try on gnex also.
Thanks
Sent from my Galaxy Nexus using Tapatalk 2
eqjunkie829 said:
I think there was already a thread about a wip port of sense and touchwiz that booted but some major stuff wasn't working.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yeah but as I can see, they're focus in specific versions, and I don't care about versions since it works. And I want a specific focus in join efforts to port sense.
nasty007 said:
I have one question about porting sense, what ROM is the best to use as base, cm10 or aosp?
I did some porting on my Droid 3 so I want to try on gnex also.
Thanks
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
It's relative. AOSP will be more easily imo, but in other hand, cm10 can be adapted, since there's cm10 for tegra (so we can adapt the source code, if someone wants to give a try). I was trying with cm10 4.1.1 btw (cause the InsertCoin is 4.1.1).
My Octo-oraculus says that there are few other threads like this and NONE of them will end up with something actually usable.
MS. said:
My Octo-oraculus says that there are few other threads like this and NONE of them will end up with something actually usable.
Click to expand...
Click to collapse
My eyes says that most of other threads are about many other subjects and NONE of them are about a collaborative project.
If you can track down swamp goblin he might give some insight he got a sense Tom working on the nexus s
Sent from my Nexus 7 using Tapatalk 2
nasty007 said:
I have one question about porting sense, what ROM is the best to use as base, cm10 or aosp?
I did some porting on my Droid 3 so I want to try on gnex also.
Thanks
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Btw, I was thinking about trying backport the sense for Nexus S (since there's one port that was almost successful), the only problem is... the best port for NS is Gingerbread-based and I dont know how much effort will be needed to adapt a 4.x kernel with a 2.3 rom.
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
Hi everyone,
As you probably have heard, the Ubuntu Touch (alpha) image has been released for the Galaxy Nexus, Nexus 4, 7 and 10.
I would like to request porting it to our N7100 devices!
If I could I would do it myself but I have never ported anything.. However, if I can help in any way I will gladly do what I can!
For reference:
https://wiki.ubuntu.com/Touch
https://wiki.ubuntu.com/Touch/Porting
Since Galaxy S3 was one of the best-selling smartphone, I hope will be a port for it and consequentially for note 2 that has the same hardware platform
its not the place to Request a port.
wgspoelstra said:
Hi everyone,
As you probably have heard, the Ubuntu Touch (alpha) image has been released for the Galaxy Nexus, Nexus 4, 7 and 10.
I would like to request porting it to our N7100 devices!
If I could I would do it myself but I have never ported anything.. However, if I can help in any way I will gladly do what I can!
For reference:
https://wiki.ubuntu.com/Touch
https://wiki.ubuntu.com/Touch/Porting
Click to expand...
Click to collapse
big boooi no need to request, the porting instructions just came online and seem as "easy" as building CM from source.
its only natural that ports will be available on most devices.
Anthropostar said:
big boooi no need to request, the porting instructions just came online and seem as "easy" as building CM from source.
its only natural that ports will be available on most devices.
Click to expand...
Click to collapse
Yay!!!
Device = Note 2
Rom = Omega 12
([email protected] black,[email protected] pack)
Kernel = Perseus 32
(Cpu [email protected],Gpu [email protected])
Audio = AC!D + Noozxoide
There is no point of porting it currently, as most things don't work very well..
This is for devs, to test their apps. Not for users.. (yet )
DubelBoom said:
There is no point of porting it currently, as most things don't work very well..
This is for devs, to test their apps. Not for users.. (yet )
Click to expand...
Click to collapse
I am aware of this.. But porting also has it's own malfunctions and problems. By porting an alpha release some of these problems can be solved before the stable release, was my thought
I am building a Ubuntu ROM now, as it was said before, don't expect much the ROM, as it is still being developed. But I am pretty sure you guys like me, just want a taste of it.
Sent from my GT-N7100 using xda premium
@thyhack I would really like to help you in any way I can
Sent from my GT-N7100 using xda app-developers app
Great I would appreciate it, send me your contact info and we can get the ball rolling this week.
Sent from my GT-N7100 using xda premium
Thyhack said:
I am building a Ubuntu ROM now, as it was said before, don't expect much the ROM, as it is still being developed. But I am pretty sure you guys like me, just want a taste of it.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
All the best will be waiting :good:
Thyhack said:
Great I would appreciate it, send me your contact info and we can get the ball rolling this week.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
I have sent the info already you don't seem to have contacted me.
I pmed ya
Sent from my GT-N7100 using xda app-developers app
Hi Dev,
Ubuntu Touch is fabulous and it looks great.
I see you were working hardly last month in porting Ubuntu touch in SGN2.
But this month no update, not a single post. Is this project ALIVE or being DISCONTINUED or DEAD???
Dev pl work on it, we have lots of hope on you.
Thanks
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