Good Morning to you all!
Sorry if this has already been posted but I couldn't find much of anything on this topic. Does a "Google Edition" Rom exist for the EVO 4G LTE? I know we have the AOSP and AOKP roms but this is something I've wanted to ask for a while. I love the pure Google experience and I just have to wait about a year until i can upgrade to a new phone like a Nexus.
Thank you again for taking the the time to read this and for all the awesome work all you Developers put in for making this awesome phone even better.
Sent from my EVO using xda app-developers app
No. But the AOSP ROMs we have work fine. What's wrong with flashing one of them? They are essentially the same thing, except, well, better .
Captain_Throwback said:
No. But the AOSP ROMs we have work fine. What's wrong with flashing one of them? They are essentially the same thing, except, well, better .
Click to expand...
Click to collapse
I'm with you on that one. Not sure why anyone with knowledge of rooting (who doesn't mind a voided warranty) would want to buy a GE phone.
______________________________
HTC Evo 4G LTE
I don't have any problem with any AOSP Rom other than signal and connectivity issues. But its really just curiosity for me and I'm a big fan of Google so the idea of having a Google Editon EVO sounds cool to me.
Sent from my EVO using xda app-developers app
Well it won't happen.
And aosp is just as much Google as a GE would be.
Sent from my Nexus 7 using xda premium
Imagine having a GE ROM that had added functionality and customizations. Then, go download one of our CM/AOKP/DU ROMs. - imagination realized.
Or, put another way, take one of our AOSP ROMs, strip away functionality and customization, and you have a GE ROM.
Is that what you're looking for?
Not trying to sound smart ass, totally sincere.
Sent from my EVO using xda premium
scottspa74 said:
Imagine having a GE ROM that had added functionality and customizations. Then, go download one of our CM/AOKP/DU ROMs. - imagination realized.
Or, put another way, take one of our AOSP ROMs, strip away functionality and customization, and you have a GE ROM.
Is that what you're looking for?
Not trying to sound smart ass, totally sincere.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
What do you think would be a good solid AOSP Rom to either behave like a GE Rom or better I've only tried the CM Rom and the Xlyon Rom back and forth and couldn't get the feel I was looking for.
Sent from my EVO using xda app-developers app
ZamoraDC said:
What do you think would be a good solid AOSP Rom to either behave like a GE Rom or better I've only tried the CM Rom and the Xlyon Rom back and forth and couldn't get the feel I was looking for.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
You could always try Evervolv. That's probably the closest to AOSP, that is, with the least customization.
Captain_Throwback said:
No. But the AOSP ROMs we have work fine. What's wrong with flashing one of them? They are essentially the same thing, except, well, better .
Click to expand...
Click to collapse
Not true. Not trying to insult any devs in any way, but AOSP roms for anything other than a Nexus are hacked together using core binaries from other devices when necessary. There is never such a thing as a bug free AOSP Rom, except for a Google device and/or Google edition.
The Google edition roms on the other hand, were compiled by HTC for a device that they know in and out. Unfortunately, this is one of those times when "the vendor knows best", simply because of sheer resources and hardware documentation.
It would be possible to port the GE roms if you guys ported the GPE kernel and used that to port the rom, like Zarboz and newtoroot did for the DNA.
CNexus said:
Not true. Not trying to insult any devs in any way, but AOSP roms for anything other than a Nexus are hacked together using core binaries from other devices when necessary. There is never such a thing as a bug free AOSP Rom, except for a Google device and/or Google edition.
The Google edition roms on the other hand, were compiled by HTC for a device that they know in and out. Unfortunately, this is one of those times when "the vendor knows best", simply because of sheer resources and hardware documentation.
It would be possible to port the GE roms if you guys ported the GPE kernel and used that to port the rom, like Zarboz and newtoroot did for the DNA.
Click to expand...
Click to collapse
How difficult is this to do?
Sent from my EVO using xda app-developers app
ZamoraDC said:
How difficult is this to do?
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
I can't say.
For the DNA it was extremely simple (but zarboz is a boss so he would've gotten it anyway) since the two devices are almost identical (One and DNA).
But the fact that you guys have a 3.4.x official HTC kernel should help.
hacked together using core binaries from other devices when necessary.
Click to expand...
Click to collapse
You would be surprised at what shortcuts OEMs take too.
Just because they have the resources doesn't necessarily mean it's cost effective, or that their software engineers have the time, to redo everything from scratch for each device. It's usually much easier to make it for one and then adapt that copy for use on other devices. I actually found this site thanks to htc's sloppy implementation of hdmi on the original evo. According to them it was impossible to fix until Toastcfh and Netarchy did just that and rewrote their kernel from scratch (iirc).
If you think about it, this site probably wouldn't even exist if OEMs made good software. They often do have access to proprietary drivers and documentation, but most of that is slowly getting open sourced anyway.
That type of reasoning is a fallacy because more often then not OEMs are just too plain cheap to do things properly. They just need to hit their deadlines. So your only real options are to either buy a nexus device, or invest a little time in helping fix any issues that you may find.
Someone please correct me if I'm thinking of the wrong device, but I believe it was the htc TyTN2 where htc didn't even bother to include a fully functional display driver because they didn't want to pay the license for it.
http://forum.xda-developers.com/showthread.php?t=359534
CNexus said:
Not true. Not trying to insult any devs in any way, but AOSP roms for anything other than a Nexus are hacked together using core binaries from other devices when necessary. There is never such a thing as a bug free AOSP Rom, except for a Google device and/or Google edition.
The Google edition roms on the other hand, were compiled by HTC for a device that they know in and out. Unfortunately, this is one of those times when "the vendor knows best", simply because of sheer resources and hardware documentation.
It would be possible to port the GE roms if you guys ported the GPE kernel and used that to port the rom, like Zarboz and newtoroot did for the DNA.
Click to expand...
Click to collapse
Have you ever used one of the IRC builds of cm10 or cm10.1? They're more stable and are more feature rich than the stock ROM that shipped with this device or any of the updates that they were gracious enough to let sense users download over the air. The 3.0 kernel was seriously stable, but the 3.4 kernel is (nearly as) stable _and_ leaves more RAM for your silly animation effects and whatever. It's based on the reference kernel for the chip set, if I'm not making an arse of myself. So pick a build. I know 1/16 was an awesome cm10, and like I said in another topic I had 191 hours uptime on the 7/23 cm10.1 before I rebooted to rule out the ROM when I was having data issues(it was the network) </rant>
Sent from my EVO using xda app-developers app
xHausx said:
You would be surprised at what shortcuts OEMs take too.
Just because they have the resources doesn't necessarily mean it's cost effective, or that their software engineers have the time, to redo everything from scratch for each device. It's usually much easier to make it for one and then adapt that copy for use on other devices. I actually found this site thanks to htc's sloppy implementation of hdmi on the original evo. According to them it was impossible to fix until Toastcfh and Netarchy did just that and rewrote their kernel from scratch (iirc).
Click to expand...
Click to collapse
Not saying they are perfect and neither am I taking sides. But the fact of the matter is that AOSP is ported using binaries made for other devices and other hacks and so is nearly impossible to make it 100% compared to vanilla nexus roms. Issues are inevitable. And those same exact shortcuts you stated apply to and are no exception with AOSP ports like CM or evervolv. They also commonize (not a word, I know) as much as possible. They group devices like all the d2 and all the jflte, or even by processor like s4_common, etc under one common branch to make it easier for themselves to maintain.
I know I'm not gonna win here because of several things, namely being that I'm taking the "wrong" stance from the majority's point of view. But I just felt adding my 0.02 would help with the OP's original question.
xHausx said:
Someone please correct me if I'm thinking of the wrong device, but I believe it was the htc TyTN2 where htc didn't even bother to include a fully functional display driver because they didn't want to pay the license for it.
http://forum.xda-developers.com/showthread.php?t=359534
Click to expand...
Click to collapse
Ha! That was my first smartphone! I first signed up on xda (under a different name) when that phone launched (I got it as the att tilt) so that I could run manila and then android on it! That display driver issue was so frustrating. Sorry for ot, but I haven't thought about that in ages.
CNexus said:
Not saying they are perfect and neither am I taking sides. But the fact of the matter is that AOSP is ported using binaries made for other devices and other hacks and so is nearly impossible to make it 100% compared to vanilla nexus roms. Issues are inevitable. And those same exact shortcuts you stated apply to and are no exception with AOSP ports like CM or evervolv. They also commonize (not a word, I know) as much as possible. They group devices like all the d2 and all the jflte, or even by processor like s4_common, etc under one common branch to make it easier for themselves to maintain.
I know I'm not gonna win here because of several things, namely being that I'm taking the "wrong" stance from the majority's point of view. But I just felt adding my 0.02 would help with the OP's original question.
Click to expand...
Click to collapse
It's not accurate to say the binaries are made for other devices when the devices are all basically the same. The MSM8960, for example, has it's own binaries, but the same chip is used in a range of devices from the Evo LTE, Blackberry Z10, One X (LTE), One XL, Windows Phone 8X, LG Mach, Moto Droid Razr M, Droid Razr, Razr Max, Atrix HD, Incredible HD, Xperia GX TL SX & V, Galaxy S III... the list goes on
The binaries all of those devices use were developed for the Qualcomm devkit I've linked below.
When you're working with a sense ROM versus an AOSP ROM there are many differences in not only appearance but the framework as well, but once you start getting down to the kernel level the hardware is all basically the same. Where we have the advantage over OEMs is that most companies know it's counterproductive and a waste of money to go after enthusiasts who borrow their binaries from one device to use on something else. If an OEM did that they would be sued in a heartbeat.
https://developer.qualcomm.com/mobile-development/development-devices/snapdragon-s4-msm8960-mdps
edit: probably actually this instead, but same difference: http://shop.intrinsyc.com/products/dragonboard-members-only
To digress back to the OP's original question though, the google edition One is basically just the one with AOSP on it. If you can find a pure AOSP ROM it'll be the exact same thing.
Thanks for the info I'm really thinking of seeing if i can try and make my own ROM and plus I've always wanted to do so hopefully it all goes well. I just don't wanna brick my phone in the process hahaha. Do you guys think trying to build off of the HTC One GE rom and convert it over to the EVO or use an EVO based AOSP ROM? Thanks again for all the help.
Sent from my Evo 4G LTE using xda app-developers app
ZamoraDC said:
Thanks for the info I'm really thinking of seeing if i can try and make my own ROM and plus I've always wanted to do so hopefully it all goes well. I just don't wanna brick my phone in the process hahaha. Do you guys think trying to build off of the HTC One GE rom and convert it over to the EVO or use an EVO based AOSP ROM? Thanks again for all the help.
Sent from my Evo 4G LTE using xda app-developers app
Click to expand...
Click to collapse
Why don't you just build AOSP? You can use the CM kernel and pull the relevant vendor files from an existing AOSP ROM (or find an up-to-date github with them).
That way you don't have to worry about having the extra customizations, but you'll still have a kernel built from Qualcomm source along with the ROM.
asop aokp cm
I have tried a lot of ROMs and I find these devs do a much better job than stock ROMs yes you have some bugs in some but the always work them out cudos to the devs I'm just glad they still support my device and having gabe up on it
Related
I was doing a little bit of surfing and noticed that cyanogen has made a cyanogen 9 version for the galaxy 2 and the nexus s... And I was wondering if it was possible to get this on our phones...
This should be in the general section...
Anyways one day it will
Sent from my HTC_Amaze_4G using XDA App
Agree is should go in general. Cyanogen said that it wouldn't be until maybe January for an alpha of CM9.
As for asking for your specific phone, give it time... it hasn't even been a month since ICS source was released.
Sent from my HTC Inspire 4G using xda premium
Right. Moving to General.
jbizz said:
Agree is should go in general. Cyanogen said that it wouldn't be until maybe January for an alpha of CM9.
As for asking for your specific phone, give it time... it hasn't even been a month since ICS source was released.
Sent from my HTC Inspire 4G using xda premium
Click to expand...
Click to collapse
In the meantime, CM7.1 would be nice - but will they just skip over 7.1 for new devices and focus on 9?
Just as a heads up, Max Krivonos posted that he stopped working on CM7 for the amaze and is going straight to CM9,
Double edged sword. Great for CM9 but no CM at all for a few months.
Yea I really miss CM. Wish it would get here asap.
Sent from my HTC Amaze 4G using xda premium
I've thought alot about selling this phone due to the lack of having a huge community support (face it, it's no Sensation, Desire Z/HD, Evo, etc)... The hardware is good, the replacement? Obviously a Galaxy Nexus, if there is a solid CM9 port for this device, I would probably just save myself the trouble and keep using this, This has everything that the international GNex would have, except for the huge high res amoled screen. Please Koush/Max!!!! (I would think quite a bit could be borrowed from the Pyramid builds, with the obvious exception of the NFC/camera)
Uh... How long has the phone been out?? Let's face that first before complaining about the lack of development... It'd be nice if there was but its not going to happen over night...
jmhalder said:
I've thought alot about selling this phone due to the lack of having a huge community support (face it, it's no Sensation, Desire Z/HD, Evo, etc)... The hardware is good, the replacement? Obviously a Galaxy Nexus, if there is a solid CM9 port for this device, I would probably just save myself the trouble and keep using this, This has everything that the international GNex would have, except for the huge high res amoled screen. Please Koush/Max!!!! (I would think quite a bit could be borrowed from the Pyramid builds, with the obvious exception of the NFC/camera)
Click to expand...
Click to collapse
Be patient my friend! I think the reason behind (kinda) lacking developtment for this phone is because there will be an ICS came out soon for it in early 2012 and most Devs are waiting for the official Amaze ICS release rather than wasting their time to built rom that would only last for less than two months
On that perspective I am really thankful for Xboarder for his effort to brought us something to satisfied our addictiveness of flashing meanwhile
I am more thankful to Max Krivonos, and Keyan Mobli (Scepterr/kmobs), Max is probably gonna be the maintainer for the Amaze for CM9 and is currently the maintainer for the MT4GS, kmobs is the maintainer of the Sensation for CM9 and has it to a point where he's said "So I'm now using ICS as my daily driver"... There is hope, but if you're looking for CM7/9 or any REAL AOSP build, don't expect xboarder to deliver that, I don't think he compiles anything, he's a themer/kanger/(insert less offensive term here). There is hope, but I'm dying to see some actual AOSP builds, GB or ICS.
jmhalder said:
I am more thankful to Max Krivonos, and Keyan Mobli (Scepterr/kmobs), Max is probably gonna be the maintainer for the Amaze for CM9 and is currently the maintainer for the MT4GS, kmobs is the maintainer of the Sensation for CM9 and has it to a point where he's said "So I'm now using ICS as my daily driver"... There is hope, but if you're looking for CM7/9 or any REAL AOSP build, don't expect xboarder to deliver that, I don't think he compiles anything, he's a themer/kanger/(insert less offensive term here). There is hope, but I'm dying to see some actual AOSP builds, GB or ICS.
Click to expand...
Click to collapse
Well, I'm by no mean a tech guy or whatsoever in that manner. All I can do is follows instruction to flashing Rom and stuff so when it come to judging who done what I have no idea eventhough I'm very much understanding what kang is ...
Perhaps when Max and whoever on CyanogenMod team came over and gave us some ICS or CM9 goodness, 'til then, the very few peoples who get this Amaze forum go on as it is and gave us something to played with is Xboarder56, Mike1986 and NRGZ28 .... and for that I am appreciates their times and effort putting into it
Heck, I even thanksful those themer like Alexia Whitehurst, killathenoob, TheSneakerWhore for uploading their theme file even though I myself know how to extract files from rom and uploading onto UOT kitchen
Those guy are ways better than those who did nothing .
antiquezip said:
Heck, I even thanksful those themer like Alexia Whitehurst, killathenoob, TheSneakerWhore for uploading their theme file even though I myself know how to extract files from rom and uploading onto UOT kitchen
Those guy are ways better than those who did nothing .
Click to expand...
Click to collapse
Just trying to keep options out there during our "slow" (see:new) period. Development takes time--Hell, I'm stuck on a macbook until I can save up for a notebook. Once I get that, I'll be able to do real theming/modding. UOT framework feels like a cop-out right now, but it is all that is being offered and we need the activity to draw more people. I have a to-do list of mods I want to do, but until I get my hardware back, it isn't happening.
Ultimately, it is patience. This phone is very new--ICS is around the corner.
antiquezip said:
Well, I'm by no mean a tech guy or whatsoever in that manner. All I can do is follows instruction to flashing Rom and stuff so when it come to judging who done what I have no idea eventhough I'm very much understanding what kang is ...
Perhaps when Max and whoever on CyanogenMod team came over and gave us some ICS or CM9 goodness, 'til then, the very few peoples who get this Amaze forum go on as it is and gave us something to played with is Xboarder56, Mike1986 and NRGZ28 .... and for that I am appreciates their times and effort putting into it
Heck, I even thanksful those themer like Alexia Whitehurst, killathenoob, TheSneakerWhore for uploading their theme file even though I myself know how to extract files from rom and uploading onto UOT kitchen
Those guy are ways better than those who did nothing .
Click to expand...
Click to collapse
+1.
There is still very much a lot of effort being put in here.
I also am thankful to everyone helping out during our slow period. Although I can't wait for some true aosp action. I absolutely hate sense. It's pretty, but I just prefer aosp
wow man way to talk behind my back look at this:
https://github.com/Xboarder56/android_device_htc_ruby
wasnt gonna release yet but im working on cm7/cm9 compile so dont talk **** when you dont know.
PS: who fixed the recovery problem, me
PS: you compile just a basic recovery, hell port sense 3.5 with working data then talk
pss: just for prove recovery i compile 5.0.2.7 still working on fixing charging bug in this one but you make one of those without cm7 team and then you talk **** man i put hours into working on this **** for you just say that it makes me want to quite becuase you dont understand
http://www.multiupload.com/6ZLPJLUZ1S (5.0.2.7 recovery) happy now
Please refrain from argueing in thread's , take it to a PM . xBoarder doe's all of the work for us so don't even .
oh xboarder just schooled him. but back on topic i wish i could help xboarder but i know nothing about making roms and such.
ajbk4life1 said:
oh xboarder just schooled him. but back on topic i wish i could help xboarder but i know nothing about making roms and such.
Click to expand...
Click to collapse
its not easy building a device tree but i did build one i still got to find all the libs to get it to compile right but thats the device tree it will compile cm7 just doenst boot all the way right now but it does compile working recoverys
I am wondering given that this device just got honeycomb.. is there any chance of it getting ICS?
Part of the reason I'm wondering is because I am getting my flyer sometime between the 10th and the 17th coming up according to the "estimated delivery date" when I hit buy.
I have had ICS on my captivate before I ever even got to play with Honeycomb.. my mom got the transformer yesterday.. and there are a few minor quirks with honeycomb that I really don't like.. major example being if you pull up the task manager in ICS you can remove windows and close out the programs.. Honeycomb will pull up windows that aren't open.. and it gets cluttered fast if your done with something and seeing 5 or more windows you don't want open, but can't get rid of..
no sign of ICS anytime soon but maybe if kernel source is released and CM9 development someone will port it here. In regards to the task management, yes it can get cluttered but it is better than not having it at all like gingerbread
I'm hoping they'll have the decency to update us or at least release the source code required...
IANAL, but I believe HTC legally has to release the kernel source for anything it releases. If they never release ICS, we may never get a kernel for ICS.
Honeycomb kernel might work, but I'm not sure if HTC is legally required to release honeycomb kernel source.
As far as I am aware, they did/may have use some proprietary software which would screw up our porting efforts.
So it becomes an issue of "will they" and that is what I am wondering.
Personally I don't think we will ever see ICS on the Flyer. Here are my reasons:
1. Not a lot of Flyers were sold so there is not a large user base. Thus, there is not much developer interest.
2. Sense - From what I understand from what developers have said, the kernels that HTC makes are made to work with Sense and will not work with an AOSP build.
These two things combine to make bringing ICS to the Flyer difficult and there is no one around who appears willing to do it.
I really hope that I am wrong about this but I don't think that I am.
Someone want to educate a noob?
How is it that several other devices (including HTC ones, like the Sensation) are getting ICS ports, but the Flyer/View can't? I mean, it seems unlikely that HTC released AOSP kernel sources for other devices, and even if they did, they're certainly not ICS kernels. Why is it so important for us to have an AOSP kernel (and an ICS one, at that) from HTC in order to get CM on the Flyer/View?
Oh, and then there's devices that didn't even have Android like the TouchPad, and devices that don't have their source code released, like the Kindle Fire.
I'm definitely not a developer, so I'm sure there's something I'm missing...I'm just trying to figure out what it is.
I'm repeating what developers told me or wrote here. I don't know if it is right or wrong.
I think the bottom line is that it is easier to have an AOSP kernel.
I think you can build your own kernel but that is much more work and maybe a hard thing to do.
All of the custom ROMs that we have seen for the Flyer are just modified HTC ROMs that come with certain software preinstalled or other kinds of enhancements.
More popular devices have much more developer interest. I would imagine that some less popular device owners get lucky because some developer also owns the device and is willing to spend the time.
So far, one developer said he would try to bring ICS to Flyer. He tried but gave up because of kernel issues. I don't get the impression that he did too much but at least he gave it a go. No other developer has said anything one way or the other.
I'm not holding my breath..
but, I definitely won't give up hope just yet..
The most likely path would be a port of another HTC device that uses the same processor or very similar. SO when some of the other HTC devices are released with ICS around March or so, we might see some goodness, depends on how close the hardware is and if HTC releases some source code.
DigitalMD said:
The most likely path would be a port of another HTC device that uses the same processor or very similar. SO when some of the other HTC devices are released with ICS around March or so, we might see some goodness, depends on how close the hardware is and if HTC releases some source code.
Click to expand...
Click to collapse
Makes sense to me.
Shame this device hasn't received more attention.
DigitalMD said:
The most likely path would be a port of another HTC device that uses the same processor or very similar. SO when some of the other HTC devices are released with ICS around March or so, we might see some goodness, depends on how close the hardware is and if HTC releases some source code.
Click to expand...
Click to collapse
This is correct and likely the only way we see ICS in a timely manner.
Sent from my HTC_Flyer_P512_NA using Tapatalk
https://plus.google.com/105502178297258827378/posts/PxQ6cVjVdUd
dingnecros said:
https://plus.google.com/105502178297258827378/posts/PxQ6cVjVdUd
Click to expand...
Click to collapse
He's been debunked several times.
Sent from my HTC_Flyer_P512_NA using Tapatalk
So I guess the big question as far as an official update goes.. is how much effort would HTC have to put out in order to do the upgrade...
And will it be worth it for them to do so..
I guess the pen is the biggest issue prevent the ICS update
Since it only works in Sense ROM, so even we have a perfect CM9, the pen function is wasted
ytwytw said:
I guess the pen is the biggest issue prevent the ICS update
Since it only works in Sense ROM, so even we have a perfect CM9, the pen function is wasted
Click to expand...
Click to collapse
Would it be possible to take the pen code from honeycomb and implement it in CM9?
ytwytw said:
I guess the pen is the biggest issue prevent the ICS update
Since it only works in Sense ROM, so even we have a perfect CM9, the pen function is wasted
Click to expand...
Click to collapse
I'd be content with an AOSP rom now, with the pen worked in later.
Sent from my HTC Flyer P510e using Tapatalk
We will see... if any devs are willing, I am sure as heck willing to help and take a crack at it myself..
You can't do AOSP without HTC's help for the kernel and drivers and since HTC only does sense kernels I'm thinking that's not going to happen. I still think a port of an HTC ICS ROM from another device is the most likely path, unless HTC is feeling exceptionally benevolent toward the Flyer. Perhaps the Jetstream tablet will get ICS and that can be ported...
Just a curious question.
I'm far from experienced in how ROM development works, the process, etc.
So if it's an obvious question, I apologize.
What does it take to port some of the Sensation ROMs over to the Rezound?
Such as Android Revolution HD, Virtuous Inquisition, etc. some of which are AOSP.
Is it just the phone has been out longer, or just different phones, different developers, the fact we have LTE instead of GSM/HSPA/etc. or a combination of all?
Not trying to sound impatient at all, I'm quite content with current pickings, I'm just waiting for the day the Rezound is like the Incredible and the Thunderbolt where it's a ROM party basically.
I Am Marino said:
Just a curious question.
I'm far from experienced in how ROM development works, the process, etc.
So if it's an obvious question, I apologize.
What does it take to port some of the Sensation ROMs over to the Rezound?
Such as Android Revolution HD, Virtuous Inquisition, etc. some of which are AOSP.
Is it just the phone has been out longer, or just different phones, different developers, the fact we have LTE instead of GSM/HSPA/etc. or a combination of all?
Not trying to sound impatient at all, I'm quite content with current pickings, I'm just waiting for the day the Rezound is like the Incredible and the Thunderbolt where it's a ROM party basically.
Click to expand...
Click to collapse
Well I am far from experienced when it comes to ROM development as well, but I know that it is verrrryy difficult to port a ROM from one device to another, especially when one phone uses GSM radios and the other LTE. Plus, the images for the ROM would look rather bad because of the resolutions of the screens being different. As far as I know, I'm pretty sure it's near impossible to port a ROM.
Hope I helped!
Sent from my ADR6425LVW using XDA App
Well I know people port all the time and I'm thinking it wouldn't be such a farfetched idea to see Evo3D or Sensation ROMs over here, I was just wondering is all.
Aren't they essentially the same phone, only one is GSM and one is LTE?
Sent from my HTC Rezound
well most of those wouldnt be THAT bad to port but we need a working AOSP kernel for all of the AOSP ones. also there is really no sense in "porting" them it would make more sense to just apply their features to a custom rom and give the original dev credit
BBEgo said:
Aren't they essentially the same phone, only one is GSM and one is LTE?
Sent from my HTC Rezound
Click to expand...
Click to collapse
The Sensation is a bit different I believe but same general idea.
The 3D has the same specs inside as the Rezound, but beyond that, not sure.
I just bought this phone the other day, after having an HTC Inspire for over a year. I really enjoyed the benefits of it being a sister phone of the Desire HD, such as really phenomenal ROM development.
I know that there aren't any sources released for this phone, but after using LordClockan's Ice Cold Sandwich, I just can't get used to this TouchWiz.
If anyone has started a project, I can help out with anything that I can.
If not, would anyone here like to try & help out?
My ROM building knowledge is non existent, but I'm dedicated to get this going.
Sent from my SAMSUNG-SGH-I717 using xda premium
I sure hope so! I loved existz work on the Inspire!
one7dchevy said:
I sure hope so! I loved existz work on the Inspire!
Click to expand...
Click to collapse
Him, TwistedUmbrella, and LordClockan's teamwork is a testament to the wonderful community her at XDA!
Sent from my SAMSUNG-SGH-I717 using xda premium
I hope it's comming!
Have you tried the ICS roms that we DO have? They're not AOKP; but they run the AOSP stock apps and they've been themed well enough to be pretty damn close -- all while maintaining full s-pen capability, which is something even the CM9 folks can't claim yet (they don't have button functionality)...
Need kernel source first!!
Sent from my SAMSUNG-SGH-I717 using xda premium
paleh0rse said:
Have you tried the ICS roms that we DO have? They're not AOKP; but they run the AOSP stock apps and they've been themed well enough to be pretty damn close -- all while maintaining full s-pen capability, which is something even the CM9 folks can't claim yet (they don't have button functionality)...
Click to expand...
Click to collapse
I hate to disagree but they arent even close (no offense to current devs, this isnt their fault).
S-pen functionality needs either the source from Samsung or a new driver has to be written from scratch, which isnt worth the time or effort considering that Samsung likely will soon be releasing source for ICS (usually a few weeks after the OS is officially released).And, if he rumors are true, ICS should be official soon (however, to be clear, I dont believe ICS is coming any time soon).
The reason these other roms have S-Pen support is, surprise surprise, they COPIED large sections of code from the stock leaked release, where, conveniently, everything ALREADY WORKS!!
Stock apps will almost always work on ANY rom with little to no modification required, regardless of whether they are from an AOSP rom.
The current roms are heavily based on the leaked ICS rom with only small tweaks universal between nearly all roms, things like themes, lockscreens, sounds, animations, etc. are all pretty simple if you know what you are doing (something admittedly, I have not personally built a rom but Im very familiar with the process).
When Cyanogen (or possibly AOKP, Im not familiar with their roms and how they are developed) is released, we will begin to see true rom development begin to happen. Until there is source code from Samsung, we will continue to see roms with Touchwiz all over them.
To show you how easy this is, here is a link to have a bot build a rom for you for any of the Galaxy 1 or 2 phones.
http://romkitchen.org/
Click your phone choice (Galaxy 1 or 2 currently, the Note is NOT supported yet).
Click Generator in the upper right hand corner.
Use the six tabs across the top of the page to choose your Modem, Kernel, Theme, stock apps, etc.
Of course, this only gives you a base to work with, from there, its pretty easy to swap in or out what you want.
Think about it like this, I can give you a copy of Windows already pre-configured for your PC and them or customize it just by changing some registry entries and including the data files (wallpapers for example). The included drivers would be pre-built meaning that 'I' didnt actually write them, nor did I change much in Windows, all I did was provide the files containing the data and changed a few settings to link to the files.
Dsmforlife92 said:
Need kernel source first!!
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Not entirely true. I know some ICS roms that have been hacked to death to get at least partial functionality.
I'm thankful that some devs have taken their time to do what they have done, but what I am looking for hasn't been done.
AOKP is like AOSP, but more tweaks are added.
[edit] As for myself, I could care less about S Pen support. I haven't even used it, nor do I think I ever will. I got this phone for the monster sized screen.
Sent from my SAMSUNG-SGH-I717 using xda premium
littlewierdo said:
I hate to disagree but they arent even close (no offense to current devs, this isnt their fault).
S-pen functionality needs either the source from Samsung or a new driver has to be written from scratch, which isnt worth the time or effort considering that Samsung likely will soon be releasing source for ICS (usually a few weeks after the OS is officially released).And, if he rumors are true, ICS should be official soon (however, to be clear, I dont believe ICS is coming any time soon).
The reason these other roms have S-Pen support is, surprise surprise, they COPIED large sections of code from the stock leaked release, where, conveniently, everything ALREADY WORKS!!
Stock apps will almost always work on ANY rom with little to no modification required, regardless of whether they are from an AOSP rom.
The current roms are heavily based on the leaked ICS rom with only small tweaks universal between nearly all roms, things like themes, lockscreens, sounds, animations, etc. are all pretty simple if you know what you are doing (something admittedly, I have not personally built a rom but Im very familiar with the process).
When Cyanogen (or possibly AOKP, Im not familiar with their roms and how they are developed) is released, we will begin to see true rom development begin to happen. Until there is source code from Samsung, we will continue to see roms with Touchwiz all over them.
To show you how easy this is, here is a link to have a bot build a rom for you for any of the Galaxy 1 or 2 phones.
http://romkitchen.org/
Click your phone choice (Galaxy 1 or 2 currently, the Note is NOT supported yet).
Click Generator in the upper right hand corner.
Use the six tabs across the top of the page to choose your Modem, Kernel, Theme, stock apps, etc.
Of course, this only gives you a base to work with, from there, its pretty easy to swap in or out what you want.
Think about it like this, I can give you a copy of Windows already pre-configured for your PC and them or customize it just by changing some registry entries and including the data files (wallpapers for example). The included drivers would be pre-built meaning that 'I' didnt actually write them, nor did I change much in Windows, all I did was provide the files containing the data and changed a few settings to link to the files.
Click to expand...
Click to collapse
I appreciate the explanation, but you're not telling me anything I don't already know. I was just saying that our current roms have been themed/tweaked well enough to look like AOSP, so they're not that bad; and, you don't really have to deal with touchwiz annoyances anymore if you don't want to -- trebuchet, apex, and nova all work well.
CM9 or AOKP they're not, but they're exceptional given the single source-less leak we have right now... and they certainly blow away stock touchwiz GB! lol
littlewierdo said:
I hate to disagree but they arent even close (no offense to current devs, this isnt their fault).
S-pen functionality needs either the source from Samsung or a new driver has to be written from scratch, which isnt worth the time or effort considering that Samsung likely will soon be releasing source for ICS (usually a few weeks after the OS is officially released).And, if he rumors are true, ICS should be official soon (however, to be clear, I dont believe ICS is coming any time soon).
The reason these other roms have S-Pen support is, surprise surprise, they COPIED large sections of code from the stock leaked release, where, conveniently, everything ALREADY WORKS!!
.
Click to expand...
Click to collapse
Pen apparently works in the CM9 build for the international note. Haven't looked at the source myself yet, but it is probably just the standard wacom driver.
zonyl said:
Pen apparently works in the CM9 build for the international note. Haven't looked at the source myself yet, but it is probably just the standard wacom driver.
Click to expand...
Click to collapse
AFAIK, they haven't gotten the button to work yet, but it's promising.
Its going to take a lot kf time and effort and prob a group effort to get aosp or aokp roms for our phone. I believe the reason skyrocket and 989 have it is because they have had a lot of devs working together for long time on it. I can get a booted aosp rom hut no sound no camera no data. So theres a lot of work needed to be done
Sent from my SAMSUNG-SGH-I717 using xda premium
How hard is porting roms from the att HTC one x to the rezound? Please don't go to hard on me. Just was curious. Seems a lot of devs that are here also are on HTC one x. Awesome phone but sucks not having s-off and no expandable memory
Sent from my ADR6425LVW using Tapatalk 2
I would think it would take some effort and knowledge to port a rom and have it run up to standards. So probably not that easy.
Thank you Jon. Just was curious cause I have both phones. The one x is very snappy but the rezound us alot more fun to. Dev with.
Sent from my ADR6425LVW using Tapatalk 2
Actually i just looked and found a guide to porting a sense rom in between devices. It actually doesnt look that hard, it looks more like replacing just replacing files if anything. I think it just depends on what rom your trying too port. If your trying to port over a different sense version it might require more work. If your trying to port an AOSP rom it might not be too difficult. Porting an android version is probably the hardest.
I see. Would be nice to try figure out that stuff. I am too inexperienced to try I think. Done minor things. Was just seeing if the one xl jellybean update that dropped last night would help the devs over here.
Sent from my ADR6425LVW using Tapatalk 2
I was actually thinking of making a very basic rom to start with like a sense 3.6 rom that might have some tweaks and such. Maybe try making my own AOSP rom, though im not entirely sure how to go about making an AOSP rom. I suppose i could also try using the guide i found to port over a sense rom as well.
Wanna share where that guide is?
Sent from my HTC One XL using xda app-developers app
http://www.xda-developers.com/android/port-sense-roms-between-sense-devices-in-six-easy-steps/
I havent tried it yet, it might work.
This one may work out better
http://forum.xda-developers.com/showthread.php?t=1598713
Just keep in mind when porting, it will be better as well as easier if you can port from a device similar to what you are porting too. Similar cpus, gpus, lte, screen resolution and network type. It all needs to be taken into consideration.
Personally if I was you, I'd start looking at Sprint devices if you want to port to the Rezound. Sprint and Verizon have the closest devices and the closest bands of any other providers out there.
Of course there are always tricks to getting around porting a full rom. Once you get to going and learn your way around porting real good, you'll learn what they are and how to do it. If you need an example of this, look up my AOKP + TouchWiz hybrid for the Rezound.
Edit: This thread made me feel nastalgic. I remember back when I first started porting. I worked and worked hard learning new tricks here and there. Back then I wrote a guide. It wouldn't be useful now, but if you wanted to humor me and see how this old dog did it back in the day you should check it out http://forum.xda-developers.com/showthread.php?t=1169570
wildstang83 said:
Just keep in mind when porting, it will be better as well as easier if you can port from a device similar to what you are porting too. Similar cpus, gpus, lte, screen resolution and network type. It all needs to be taken into consideration.
Personally if I was you, I'd start looking at Sprint devices if you want to port to the Rezound. Sprint and Verizon have the closest devices and the closest bands of any other providers out there.
Of course there are always tricks to getting around porting a full rom. Once you get to going and learn your way around porting real good, you'll learn what they are and how to do it. If you need an example of this, look up my AOKP + TouchWiz hybrid for the Rezound.
Edit: This thread made me feel nastalgic. I remember back when I first started porting. I worked and worked hard learning new tricks here and there. Back then I wrote a guide. It wouldn't be useful now, but if you wanted to humor me and see how this old dog did it back in the day you should check it out http://forum.xda-developers.com/showthread.php?t=1169570
Click to expand...
Click to collapse
Thanks wildstang for the advice, Ill probably try just porting a rom that is really basic. Which phone do you recommend attempting to port a rom from for beginners?
jon7701 said:
Which phone do you recommend attempting to port a rom from for beginners?
Click to expand...
Click to collapse
One X or Evo 4G LTE.
jon7701 said:
Thanks wildstang for the advice, Ill probably try just porting a rom that is really basic. Which phone do you recommend attempting to port a rom from for beginners?
Click to expand...
Click to collapse
Snuzzo's on it
Snuzzo said:
One X or Evo 4G LTE.
Click to expand...
Click to collapse
Alright, I found a One X rom that looks interesting, I might give it an attempt. :good:
Edit: Just finished porting the rom, it doesnt boot or even show anything on my screen, but it installed. Trying something different.
jon7701 said:
Alright, I found a One X rom that looks interesting, I might give it an attempt. :good:
Edit: Just finished porting the rom, it doesnt boot or even show anything on my screen, but it installed. Trying something different.
Click to expand...
Click to collapse
Ok, so it did not error in recovery right?
wildstang83 said:
Ok, so it did not error in recovery right?
Click to expand...
Click to collapse
It did but i figured out the problem. I didnt expect the rom to work since i tried porting the 4.2 rom from the One X. :silly: Ill try a sense 4 or 4.1 rom later.