Related
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.
Hello All,
I want to start off with a very big thank you to everyone in this community, everyone here has been very helpful to someone who is a general noob to HTC-Android devices (last HTC I owned was a TPII).
With that out of the way, I've had my Rezound for about a week and I love this phone. It feels great in the hand, has a gorgeous screen that is second to none, and an amazing camera that I'm happy to walk around with in case I need to grab a quick picture of something. Truly, this is a top notch device.
The problem I'm having is that after a week of owning this phone, I'm ready to leave stock. I was settled on CleanROM ICS for the time being until CM9 came out, but then I did some reading looking into CM9 which brought up a few questions.
1) What is S-Off and why is it important? Coming from a Droid X, I thought the important thing was an unlocked Bootloader. Why are other HTC Phones "S-Offed" and this one isn't? How does this affect ROM Development? Does this hurt the chances of CM9 making it to the Rezond (very hard to tell because they have not announced CM9 device support other than the G-Nex)?
2) What is the RIL and why is it important? This seems to be a problem amongst developers.
The main reason I bought this phone over the G-Nex was the SD-Card slot, the camera, and the screen. If development of an AOSP or AOKP is going to be lackluster because of the issues above, I still have one week to return the device and go back to my X for the time being. I will admit, I'm loving 4G, but I'm going to have this device for 2 years; I need to make sure I can get as much as I can out of this device.
Thank you as always for your answers!
EtherBoo said:
1) What is S-Off and why is it important? Coming from a Droid X, I thought the important thing was an unlocked Bootloader. Why are other HTC Phones "S-Offed" and this one isn't? How does this affect ROM Development? Does this hurt the chances of CM9 making it to the Rezond (very hard to tell because they have not announced CM9 device support other than the G-Nex)?
2) What is the RIL and why is it important? This seems to be a problem amongst developers.
Click to expand...
Click to collapse
The 2 questions you have are very related. What it means, from what I understand, is custom radio developments. Also referring to your first question and your concern, that's what we are waiting on. To not rely on a leak for custom roms and to get an official OTA to base the roms off of, which refers back to your 2nd question if this device can't get s-off capability. We already have a way to flash custom kernels & roms, so at this time, s-off would just add the functionality of creating a custom radio.
Snuzzo said:
The 2 questions you have are very related. What it means, from what I understand, is custom radio developments. Also referring to your first question and your concern, that's what we are waiting on. To not rely on a leak for custom roms and to get an official OTA to base the roms off of, which refers back to your 2nd question if this device can't get s-off capability. We already have a way to flash custom kernels & roms, so at this time, s-off would just add the functionality of creating a custom radio.
Click to expand...
Click to collapse
So what makes custom radios important?
EtherBoo said:
So what makes custom radios important?
Click to expand...
Click to collapse
it's more of nodding radios and not creating them. the only advantage is possibly better signal(depending on location,prl and tower) which leads to better voice quality but since this is high end as it is it might not even make a better difference even with possible data speed increases.
dyetheskin said:
it's more of nodding radios and not creating them. the only advantage is possibly better signal(depending on location,prl and tower) which leads to better voice quality but since this is high end as it is it might not even make a better difference even with possible data speed increases.
Click to expand...
Click to collapse
It sounds to me like an excuse not to develop on this device if this is really something stopping us from a solid AOSP or AOKP build.
I'm really torn. I want a Sense-less ICS ROM, but I really love this phone. I have a week left before I can return it. I suppose worst case I could steal my wife's upgrade in May and give her this phone if we don't see development start picking up.
Unrelated, I'm starting to think this device will never see a solid 5.0 build. CM9 isn't even out of beta and official device support is still showing CM7 devices.
I guess it's a tough decision. At least my wife is willing to take this phone.
The radio isn't the issue. The RIL in android is. I don't know of any android devices that have needed modded radios in order to get AOSP working. There is a working build of MIUI with 4G working... but it seems like the dev wants to get it perfect before he releases it. Once that is done we should be able to get CM9.
But by all means though, if you don't like sense, get a nexus. It is possible nothing will ever be released though so don't hinge your plans on it.
con247 said:
The radio isn't the issue. The RIL in android is. I don't know of any android devices that have needed modded radios in order to get AOSP working. There is a working build of MIUI with 4G working... but it seems like the dev wants to get it perfect before he releases it. Once that is done we should be able to get CM9.
But by all means though, if you don't like sense, get a nexus. It is possible nothing will ever be released though so don't hinge your plans on it.
Click to expand...
Click to collapse
So con247- Do you think there is a chance that an ASOP ril will never be developed?
I guess my question is- how is the rezound>RIL>sense different than rezound>RIL>ASOP? If that makes sense?
It is possible it won't ever happen, but I have 99% faith it will be completed soonish.
EtherBoo said:
It sounds to me like an excuse not to develop on this device if this is really something stopping us from a solid AOSP or AOKP build.
I'm really torn. I want a Sense-less ICS ROM, but I really love this phone. I have a week left before I can return it. I suppose worst case I could steal my wife's upgrade in May and give her this phone if we don't see development start picking up.
Unrelated, I'm starting to think this device will never see a solid 5.0 build. CM9 isn't even out of beta and official device support is still showing CM7 devices.
I guess it's a tough decision. At least my wife is willing to take this phone.
Click to expand...
Click to collapse
Seems like an odd thing to buy a phone on the expectation of AOSP. I'm pretty sure we will see a solid AOSP ROM before long though. Not sure how development is going to pick up much more than it is. We have a ton of great ROMs that these awesome devs have been working on tirelessly since before the unlock was even announced. It's only been four months since the phone came out. The development has been moving at breakneck speed! The lack of flashing unsigned radios has no bearing on ROM developing. Con is dead on. Patience folks.
It looks like some progress is being made with MIUI for Rezound. Seems to be some issues, but I thought it was worth sharing. Check this twitter for progress:
http://twitter.com/#!/Paullie_Vicious
Pfff I forgot it was even being worked in
wow i thougth miui was a no go for the rezound. Keep us posted i loved miui on my incredible.
jski711 said:
wow i thougth miui was a no go for the rezound. Keep us posted i loved miui on my incredible.
Click to expand...
Click to collapse
Yeah I'm excited for it too. Apparently it has RIL intact (at least the guy working on it thinks it does), and if this is true, I bet it would really help the RIL issues on AOSP ROMs (like CM9 hopefully)
Troider said:
Yeah I'm excited for it too. Apparently it has RIL intact (at least the guy working on it thinks it does), and if this is true, I bet it would really help the RIL issues on AOSP ROMs (like CM9 hopefully)
Click to expand...
Click to collapse
you lost me at RIL. LOL, i know how to flash roms and thats about it. so whatever RIL is hopefully it works!!!
jski711 said:
you lost me at RIL. LOL, i know how to flash roms and thats about it. so whatever RIL is hopefully it works!!!
Click to expand...
Click to collapse
RIL is the Radio Interface Layer. It's basically the phone and data portion of the software, so without a working RIL, you do not get data and you can't send texts or make phone calls. They've had a rough time getting it to work on ROMs without Sense (completely without Sense, not desensed to look like it is), but hopefully this changes soon.
I was starting to think he quit building miui for us. He's always tweeting about the thunderbolt and nexus.
Sleek69 said:
I was starting to think he quit building miui for us. He's always tweeting about the thunderbolt and nexus.
Click to expand...
Click to collapse
He's been working on it recently. Someone who was helping him says that the issue now is finding a good kernel, and that none of the AOSP ones work well with the ROM. Hopefully he sticks with it and we get MIUI (and other AOSP ROMs) soon.
I'm not a big fan of MIUI, but I'm glad it's being worked on. The bigger the variety the better I say.
does seem its getting close, I can't wait, I love MIUI, and we need more options than just Sense roms
This will for sure give us cm9 as well. Im stoked!
Any progress is progress at this point. As much as Sense is as sleek as ever I just want that screaming speed you get from aosp.
I'm so ready for miui or sense 4.0 I can't stand thinking about it lol. Soooo bored with.gingerbread sense
I loved Miui on the Inc, even though it did kinda cripple the video camera. The customizability was unmatched.
Sent from my ADR6425LVW using XDA
I'll sum up what I know about the current issues for the Rezound and non-Sense ROMs. Correct me if I'm wrong but...
The problem most developers are having with AOSP ROMs is with the RIL, or Radio Interface Layer. Vicious claims to have this working on MIUI, but does not have a good kernel for the ROM. So when HTC releases the kernel source for ICS (like they just did for the Sensation and Vivid), it should give developers a lot more to work with to make good kernels for AOSP ROMs and MIUI.
The question I have is whether or not a working RIL for MIUI really does mean it would also work for AOSP ROMs like CM9, or at least with minor changes. Also, (if they can't get the kernel to work without the source) once the ICS kernel source is released by HTC, would it speed up the problems that people are having with their kernels on non-Sense ROMs like MIUI? Or would it still pose a big problem because it is made for Sense?
Yes we need a custom aosp kernel. From what ive heard both IMO & aeroevan might be interested in helping us out.
exactly like the op says, now that we have s-off, do you guys think we will get official aosp support sice some devs arent really willing to deal with s-on? im not requesting. i'm just interested in what others think
My question is what does the one have to do with the other? Or put it this way what does S-Off have to do with AOSP? just wondering, thanks.
Stryker1297 said:
exactly like the op says, now that we have s-off, do you guys think we can get official aosp support soon? im not requesting. i'm just interested in what others think
Click to expand...
Click to collapse
My personal opinion, i'm sure others will. I won't compile an AOSP rom for the DNA. My reason. I happen to love sense. Reason I stick with HTC phones. I don't like touchwiz (earth, haze, whatever they keep changing the ui name to) and moto ui is too much like stock. I like personality in my phone.
Stryker1297 said:
exactly like the op says, now that we have s-off, do you guys think we can get official aosp support soon? im not requesting. i'm just interested in what others think
Click to expand...
Click to collapse
Not to sound like a jerk but it seems like you should know your way around....
We always have AOSP thats why its called android OPEN SOURCE project. The question is will someone be able to port it to the DNA.
Go to the Orig. Android Dev section for the DNA and you will see drewx2 an others have been working tirelessly on porting CM10.1 (AOSP) to the DNA. Instead of asking a question that has been answered in the thread you should go check it off.
And S-OFF has nothign to do with porting AOSP. It might make a difference considering other devs may get the phone now that the bootloader is fully unlocked. But it has no DIRECT effect.
How many of these threads do we need?? You could not have posted in the AOSP thread right below yours?? Besides if you people wanted AOSP you should have bought a Nexus. SMH
zone23 said:
My question is what does the one have to do with the other? Or put it this way what does S-Off have to do with AOSP? just wondering, thanks.
Click to expand...
Click to collapse
My dear Zone. I think the question was, now that there's no security whatsoever, does it mean now we have the capability to modify the device even further.
The S-off feature allows us to upgrade the firmware (ie, bootloader ver, radios) on our devices. The software is capable after root is achieved. Root in lamens terms is giving yourself administrative rights over your phone, ,much like you have administrative rights on your windows computer. BUT, linux does not have administrator priveleges, it has root priveleges. Thats why Zone is confused by your queston.
Unphazed MD said:
Not to sound like a jerk but it seems like you should know your way around....
We always have AOSP thats why its called android OPEN SOURCE project. The question is will someone be able to port it to the DNA.
Go to the Orig. Android Dev section for the DNA and you will see drewx2 an others have been working tirelessly on porting CM10.1 (AOSP) to the DNA. Instead of asking a question that has been answered in the thread you should go check it off.
And S-OFF has nothign to do with porting AOSP. It might make a difference considering other devs may get the phone now that the bootloader is fully unlocked. But it has no DIRECT effect.
Click to expand...
Click to collapse
number 1, yes you sound like a jerk. number 2, some people dont have time to search for a partial answer to somebody else's question. 3, i asked for OPINIONS on the subject. not answers or eta's. 4, i have seen the thread, i asked for speculations on official ports, and i am very aware of the hard work devs put in (donated to jcase and beaups). and 5, s-off has a LOT to do with aosp ports, since many devs refuse to support locked phones, which is an effect. not direct, but still an effect.
honestly i know now why xda's rep is such crap now. when i try to start a conversation on this site all you get is a bunch of trolls with nothing better to do than act condescending and sarcastic.
and thank you dragonstalker for being just about the only person on this thread that even attempted to act sensible and polite
Memnoch73 said:
How many of these threads do we need?? You could not have posted in the AOSP thread right below yours?? Besides if you people wanted AOSP you should have bought a Nexus. SMH
Click to expand...
Click to collapse
where's the fun with nexus phones? number one, i am a strict lte user. two, i dont really like nexus because you dont get to really choose other oem skins. some days i like sense/touchwiz, and other days i like aosp. and no wont post in the other thread. they arent looking for the same conversation/info i am, and i'm not gonna add another question to a question thread. SMH
well some devs might be more interested in getting the phone now that it has s off. I don't think it has a direct effect either but making things more convenient for the end user to install kernels should entice more people, including devs looking for a new toy.
Stryker1297 said:
number 1, yes you sound like a jerk. number 2, some people dont have time to search for a partial answer to somebody else's question. 3, i asked for OPINIONS on the subject. not answers or eta's. 4, i have seen the thread, i asked for speculations on official ports, and i am very aware of the hard work devs put in (donated to jcase and beaups). and 5, s-off has a LOT to do with aosp ports, since many devs refuse to support locked phones, which is an effect. not direct, but still an effect.
honestly i know now why xda's rep is such crap now. when i try to start a conversation on this site all you get is a bunch of trolls with nothing better to do than act condescending and sarcastic.
and thank you dragonstalker for being just about the only person on this thread that even attempted to act sensible and polite
Click to expand...
Click to collapse
Theres nothing wrong with "XDA's" rep. Its people posting/asking the same quesitons over and over again without taking the 5 minutes to browse the forums or 30 seconds to do a search. Theres been like 800 S-OFF/AOSP related threads/questions when in truth they honestly arent that related. S-OFF is essentially disabling a security check. AOSP is the source.
You could of also just posted like someone else said in one of the other threads on the front page of DNA Q/A asking about S-OFF/AOSP. I dont post a lot but honestly all of these questions being asked over and over again is really silly.
Same with asking about an ETA. The ETA is when the devs finish it. If you want it faster help out. Its not easy.
Maybe you should have reworded your question to something like "Now that we have S-OFF is porting AOSP and easier/quicker which would speed up the eta?"
Im sorry but after the whole debacle with people bugging devs and almost driving them out of the scene and taking them for granted I am not trying to have this widespread post spam happen.
and btw official CM10 support usually happens after somone has a stable and organized build. Then CM10 will usually ask them to become the official maintainer for that device. DrewX2 posted about it in the CM10.1 DNA thread I am not giving that great of an explanation.
dragonstalker said:
My dear Zone. I think the question was, now that there's no security whatsoever, does it mean now we have the capability to modify the device even further.
The S-off feature allows us to upgrade the firmware (ie, bootloader ver, radios) on our devices. The software is capable after root is achieved. Root in lamens terms is giving yourself administrative rights over your phone, ,much like you have administrative rights on your windows computer. BUT, linux does not have administrator priveleges, it has root priveleges. Thats why Zone is confused by your queston.
Click to expand...
Click to collapse
Ya I get confused a lot thanks for cleaning that up for me.
Technically we have AOSP but with Sense skin. If you want AOSP feel then flash a deSensed rom (Sence isn't completely removed, only as much as possible) and use an AOSP theme.
orangechoochoo said:
Technically we have AOSP but with Sense skin. If you want AOSP feel then flash a deSensed rom (Sence isn't completely removed, only as much as possible) and use an AOSP theme.
Click to expand...
Click to collapse
Let me clarify something... AOSP is nothing like sense... Sense isn't a skin it's a full OS. HTC didn't theme AOSP, they built from ground up an os based on android kernel / Linux kernel
Sent from my HTC6435LVW using XDA Premium HD app
Nevermind, you're right.
http://www.xda-developers.com/andro...d-skins-aosp-sense-touchwiz-xda-developer-tv/
orangechoochoo said:
Nevermind, you're right.
http://www.xda-developers.com/andro...d-skins-aosp-sense-touchwiz-xda-developer-tv/
Click to expand...
Click to collapse
Yea that's exactly what I was referencing from lol
orangechoochoo said:
Nevermind, you're right.
http://www.xda-developers.com/andro...d-skins-aosp-sense-touchwiz-xda-developer-tv/
Click to expand...
Click to collapse
Wow, someone who admits they're wrong. I didn't know that existed on the Internet.
Sent from my HTC6435LVW using xda app-developers app
Unphazed MD said:
Theres nothing wrong with "XDA's" rep. Its people posting/asking the same quesitons over and over again without taking the 5 minutes to browse the forums or 30 seconds to do a search. Theres been like 800 S-OFF/AOSP related threads/questions when in truth they honestly arent that related. S-OFF is essentially disabling a security check. AOSP is the source.
You could of also just posted like someone else said in one of the other threads on the front page of DNA Q/A asking about S-OFF/AOSP. I dont post a lot but honestly all of these questions being asked over and over again is really silly.
Same with asking about an ETA. The ETA is when the devs finish it. If you want it faster help out. Its not easy.
Maybe you should have reworded your question to something like "Now that we have S-OFF is porting AOSP and easier/quicker which would speed up the eta?"
Im sorry but after the whole debacle with people bugging devs and almost driving them out of the scene and taking them for granted I am not trying to have this widespread post spam happen.
and btw official CM10 support usually happens after somone has a stable and organized build. Then CM10 will usually ask them to become the official maintainer for that device. DrewX2 posted about it in the CM10.1 DNA thread I am not giving that great of an explanation.
Click to expand...
Click to collapse
did you not read how i just said i didnt ask for eta's or roms. do you know how to read. also did you read how i said i donate to devs when possible. also did you read how i said i wasnt asking for progress updates. i said i was looking for CONVERSATIONAL OPINIONS ON THE SUBJECT
Bigandrewgold said:
Wow, someone who admits they're wrong. I didn't know that existed on the Internet.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
It doesn't hurt to be wrong, it's a learning experience :good:
No s off won't make CM10 any easier to build. Fixing not being able to push or pull system files while phone is booted makes things much easier to work with and in my opinion was way more helpful to the devs on general.
If you look at some of the recent HTC devices, a good number of those devices are s off, and the AOSP developers went back to s on because of safety concerns for the device after a few mishaps building from source.
To build AOSP for a device like this requires some serious skill on the RIL (radio interface layer) department especially. Using the command line for a few things like boot.img isn't challenging to someone that can build from source for AOSP. And definitely is a skill someone porting AOSP roms and especially trying to crack RIL would have acquired a long time ago. While on the surface it seems so advantageous to the end user, to port AOSP over to a brand new device, my 2 sense is that s on is the least of their worries.
And yeap the guys above me are right, sense is built as sense from the ground up. And unlike AOSP, most of sense is proprietary so unlike AOSP Android, it has to be reverse engineered and then built to work on the hardware in our phones. The linux kernel used by HTC is open source and they comply with the GPL and release kernel source code for it. But everything proprietary is kept pretty locked down to prevent Samsung from using sense 5 and calling it "Samsung inSense"
There may be
Sent from my DNA... S-Off like a baws
Why do so many people buy HTC phones which all come with some form of Sense and then spam XDA with questions about when can we get AOSP? The answer to the question by the OP is no because S-Off has nothing to do with getting AOSP. As Charles put it the biggest hurdle on every HTC device I have had for the devs to get AOSP working is RIL and kernel.
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