Related
http://www.androidcentral.com/ice-c...on-leaks-out?utm_source=ac&utm_medium=twitter
Looks extremely underwhelming...
Better than I expected.
Via My HTC Evo 3D On The Now Network From Sprint.
Still looks horrible. =[
I think it looks terrible...nothing like ICS.
I'm Batman..
How is it "extremely underwhelming" ? Did you really expect a Sense-free release?! What were you expecting to get?
We are getting a major API revision and the long awaited HW acceleration.
This is far from underwhelming.
Its time for HTC to make sense OPTIONAL. Half of us switch to AOSP roms anyways. Looks like junk compared to stock ICS though.
Meh, boring, much rather prefer vanilla. On the plus side I guess it will help EVO 3D development.
It doesn't look much different from ginger bread with sense.
Guess whats getting ported today
I don't see the issue. It's updated, It's how HTC makes it, if It's not pretty, we theme it. If you don't like sense, then why comment? Obviously you're going to run cm9 or some other form of aosp.
Via My HTC Evo 3D On The Now Network From Sprint.
JoelZ9614 said:
Guess whats getting ported today
Click to expand...
Click to collapse
youre the best!
for everyone complaining notice that its only sense 3.5, not 4.0 like they said would be part of their ics releases. probably because this is only a TEST BUILD
JoelZ9614 said:
Guess whats getting ported today
Click to expand...
Click to collapse
You're the man JoelZ. I'll be lurking...
kellybrf said:
youre the best!
for everyone complaining notice that its only sense 3.5, not 4.0 like they said would be part of their ics releases. probably because this is only a TEST BUILD
Click to expand...
Click to collapse
You're prolly right. It definitely looks unfinished
I'm Batman..
JoelZ9614 said:
Guess whats getting ported today
Click to expand...
Click to collapse
I think I may have just creamed a bit. JoelZ, you are the maaaannnn!!!
I am going to take a stab on the port as well. The download is painfully slow however
"Sense based ICS ROM." It wont be the real deal until HTC releases it themselves in my opinion. Also, just leave it alone Joelz.
knowledge561 said:
"Sense based ICS ROM." It wont be the real deal until HTC releases it themselves in my opinion. Also, just leave it alone Joelz.
Click to expand...
Click to collapse
It is not too hard to build an ASOP if we have a working rom
So how did they get this? j/w b/c this is the first pure leak ive seen for us since Sinper's site was shut down long long ago. EDIT: I guess Capy has a source inside HTC to an extent!! Wish we could get an EVO3D leaker to come out lol.
Also to the Sense 3.5 on it is a little confusing b/c it looks nothing like either of the other sense 3.5 phone builds out, the high power one nor the low end device one.
I agree it likely/HOPEFULLY is saying sense3.5 on it b/c they are not fully done with it yet.
Keep the Thread Clean Guy's or you will force me to lock it
So with the port I'm gonna say that 4g won't work?
XOOM got ICS port right now, with everything working well (except face unlock, but hey...)
does that mean anything for us Flyer/View-owners? is it possible to port it to our tablet?
would love ics on the flyer
EDIT: Link: http://www.xda-developers.com/android/highly-functioning-cm9-kang-released-for-the-xoom/
what does it mean to us? That the xoom got an ics port, nothing more or less.
Different hardware types and kernels mean xoom with ics is meaningless to us.
My guess is he was asking if there was a way to port it and mod it to work. What we really need to hope for of CM9.x to arrive that will support the Flyer/Evo View.
Snow_fox said:
what does it mean to us? That the xoom got an ics port, nothing more or less.
Different hardware types and kernels mean xoom with ics is meaningless to us.
Click to expand...
Click to collapse
hahha somebody woke up on the wrong side of the bed, or are you always this negative? haha relax
im not stupid, i know that its a diffrent tablet, but this kinds of ports are being done almost daily.
as this fella mentioned, i was thinking of a mod, to get it to work.
He's not being grouchy, just straight forward. You cannot port a ROM complied for a completely different family of hardware and get it to function in any conceivable fashion. You'd be better off with a SDK build of ICS which would possibly boot if you hacked in a boot image, but none of the HTC specific hardware like camera, BT or video would function. There are already efforts underway to build ICS ROMs. Since ICS is built on top of HC, we have most of the pieces to build a vanilla ROM (no HTC Sense). Once HTC comes out with a working HTC device ICS ROM on hardware that is similar to the Flyer (yes some of their phones use similar hardware) that will be the port we want for ICS /Sense Roms.
I would love to have ICS on this device. Considering how much dev interest the blowout sales have generated I think its possible. But I am not going to how my breathe. I have a galaxy nexus but my evo view is still my primary device due to its pen and large screen. My wishlist for the next iteration of this device is: lighter, ICS, sprint 4g LTE in that exact order
Hopefully the fire sales have pushed HTC to keep going.
psijac said:
I would love to have ICS on this device. Considering how much dev interest the blowout sales have generated I think its possible. But I am not going to how my breathe. I have a galaxy nexus but my evo view is still my primary device due to its pen and large screen. My wishlist for the next iteration of this device is: lighter, ICS, sprint 4g LTE in that exact order
Click to expand...
Click to collapse
Reading about ICS on Prime on engadget has made me interested in ICS as well.
http://www.engadget.com/2012/01/10/hands-on-with-ice-cream-sandwich-on-asus-transformer-prime/
DigitalMD said:
He's not being grouchy, just straight forward. You cannot port a ROM complied for a completely different family of hardware and get it to function in any conceivable fashion. You'd be better off with a SDK build of ICS which would possibly boot if you hacked in a boot image, but none of the HTC specific hardware like camera, BT or video would function. There are already efforts underway to build ICS ROMs. Since ICS is built on top of HC, we have most of the pieces to build a vanilla ROM (no HTC Sense). Once HTC comes out with a working HTC device ICS ROM on hardware that is similar to the Flyer (yes some of their phones use similar hardware) that will be the port we want for ICS /Sense Roms.
Click to expand...
Click to collapse
yeah i know, but since ive seen others with ics, that made me a bit inpaitient
htc sensation got the ics leaked, and maybe someone can start by playing with that one.
and i dont really care if its manilla or sense, both will do good dont think flyer/view will be getting any ICS official soon, since HC just was released.
if i seemed grouchy, it may be because I am a comp sci major with aspirations of being a software engineer. I view the question as either yes or no and then explain the logic why not. No intentions of rudeness, but I tend to assume I'm talking to ppl with similar backgrounds... At least on the net anyway.
Wooow...okey then...my bad! I should know better..
Sent from my PG41200 using XDA App
We are keeping an eye on the HTC Sensation leak. Right now there are 2 or 3 pages of things that don't work and of course its a different radio and HBOOT. So its a ways out from being useful as a port other than a novelty. By that I mean you might get something to boot, but none of the hardware functions like camera and touch screen would work.
May want to wait for something more stable to port..sounds more like a way to brick a flyer than a novelty.
How much difference is there between sensation and flyer? Also is the radio relevant for the WiFi flyer.
I keep forgetting the are 3g versions of the flyer.
DigitalMD said:
We are keeping an eye on the HTC Sensation leak. Right now there are 2 or 3 pages of things that don't work and of course its a different radio and HBOOT. So its a ways out from being useful as a port other than a novelty. By that I mean you might get something to boot, but none of the hardware functions like camera and touch screen would work.
Click to expand...
Click to collapse
ok, sounds good though!
whats the chances of a HC/ICS mix then, do you know? i mean, using what might be working in ICS (the best of it) combined with the useabilities of the HC.
*modding is not my area, as you might understand by now*
loni90 said:
ok, sounds good though!
whats the chances of a HC/ICS mix then, do you know? i mean, using what might be working in ICS (the best of it) combined with the useabilities of the HC.
*modding is not my area, as you might understand by now*
Click to expand...
Click to collapse
Snow_fox said:
May want to wait for something more stable to port..sounds more like a way to brick a flyer than a novelty.
How much difference is there between sensation and flyer? Also is the radio relevant for the WiFi flyer.
I keep forgetting the are 3g versions of the flyer.
Click to expand...
Click to collapse
1. ICS is built on top of HC so we already have most of the ICS GUI. Google is already moving some of the ICS features into individual apps like the updated Google Search.
2. Radio is always relevant because it controls GPS, Wifi , and BT in addition to 3g.
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.
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.
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