Related
Okay, so CM7 is out and everything. I know that the Galaxy S phones aren't close or unknown how far or close we are to finally getting this. I know it might sound dump but my girlfriend just got the mytouch 4g for free and I've been playing with it. I noticed that when you go to settings there is an option for theme selection. Is that how CM works? I see all these themes out there from CM and all of them seem to have that same looking interface when selecting themes. I don't have friends that are into phones as I am so none of them know about this stuff.
Thanks in advance guys!
That is what they incorporated from T-Mobile, who, to their credit has an account on github and gave the code... impressive to t-mobile.
and of course, a lot of people theme for the best rom in town.
So you're saying that T-Mobile integrated the CM theme selector on the stock ROM? So can I just download any of the CM themes and just apply them?
no, not at all.. t-mo had code on github for theming, CM incorporated it into CM7
Ahhh, I see. Any idea how close or far the Galaxy S line is from getting CM7?
there are buggy versions already... source would help, a lot.
I have heard about the source that we need but didn't the update just pop in? I'm using the Bionix-V ROM which is based on the official 2.2. I'm sure that it's the source that we are looking for? I'm not sure where to ask but I want get involved with the community see if I can help out with the CM. I've been looking into the CM7 for the mytouch 4g for my girlfriends phone and I'm really liking it!
Source is not released yet: http://opensource.samsung.com/
s15274n said:
Source is not released yet: http://opensource.samsung.com/
Click to expand...
Click to collapse
Yes the recent release was the 959D the Captivate (att) We are still waiting for ours to be released.
oka1 said:
Yes the recent release was the 959D the Captivate (att) We are still waiting for ours to be released.
Click to expand...
Click to collapse
Uhh no.. 959d is facinate(telus) it looks just like vibrant (u.s version)
I897 is att ccaptivate.
One more thing, how can they have source code before us when they don't even have 2.2 yet. Att have not release the 2.2 for captivate(u.s)yet. The 2.2 that was released while back was for Canadian captivate( Rogers)
Axura 2.3.0 with adw launcher ex
Until we get the 2.3 source, we will be quite far from CM7, huh?
Can anyone possibly explain to me exactly how CM works though? I don't have anyone that's as enthusiastic as me when it comes to phones. I don't have a phone that has a CM capable ROM. Also, the videos just show the ROM but don't actually show the feature.
All I know is that CM allows you to customize your phone past the limits that are put on it. That being said, does it allow you to customize things individually or do you have to have a fully skinned theme or something along those lines?
Will we ever get a 2.3 source?
Sent from Bionix powered vibrant! If I helped, hit the thanks button!
isnt this us? or Is that a different file?
DynamicXL said:
Until we get the 2.3 source, we will be quite far from CM7, huh?
Can anyone possibly explain to me exactly how CM works though? I don't have anyone that's as enthusiastic as me when it comes to phones. I don't have a phone that has a CM capable ROM. Also, the videos just show the ROM but don't actually show the feature.
All I know is that CM allows you to customize your phone past the limits that are put on it. That being said, does it allow you to customize things individually or do you have to have a fully skinned theme or something along those lines?
Click to expand...
Click to collapse
Since not many devs are working on it it will take a while. If I'm not wrong if we get 2.2 source it can get ported.
Mytouch 4g and many other phones don't have 2.3 source but they have cm 7. I guess its because this is Samsung first Android phone ( I think) and its more complicated than HTC phones. I could be wrong, after all I know nothing about coding
axura 2.3.0 with adw launcher ex
HectikDroid said:
isnt this us? or Is that a different file?
Click to expand...
Click to collapse
What does it say can't see the picture.
bionix 1.2.1 with adw launcher ex
eunkipark92 said:
Since not many devs are working on it it will take a while. If I'm not wrong if we get 2.2 source it can get ported.
Mytouch 4g and many other phones don't have 2.3 source but they have cm 7. I guess its because this is Samsung first Android phone ( I think) and its more complicated than HTC phones. I could be wrong, after all I know nothing about coding
axura 2.3.0 with adw launcher ex
Click to expand...
Click to collapse
Yeah, I have noticed that almost all new phones that HTC comes out with, including the mytouch 4g that my girlfriend just got herself, there are a lot of CM themes and ROMs for it. Even though it came out a few months ago, while as Vibrant like half a year ago.
I did look around, it does seem like the Galaxy S line of phones is the first of android for Samsung. I'm thinking this is the biggest reason that they don't have this many developers.
It seems that there a plenty of new Galaxy S phones heading this way, so perhaps there will be more developers for our community.
I would like to help out as much as I can. I am no developer but perhaps I can help out with beta testing and all that fun stuff.
Samsung and HTC are very different... transitioning from one is not the easiest. HTC is certainly easier.
eugene has 6.1 running on his forums
I tried that CM 6.1 and I just couldn't get it to work at all. My CWR would always crash everytime I tried to do it.
On the other hand, I know HTC has been making android phones for some time now, there has been a lot more work and development done with them. Samsung is fairly new, I don't see why in the near future there will be a lot more development for Galaxy S phones, considering that they just announced a new line of these phones this year. Possibly a stable CM mod.
Sent from my SGH-T959 using XDA App
well until samsung gets off their ass and release source for 2.2 and then 2.3 we will never see true cm6 or cm7 on our phones yes lots of ports but never true cm
We'll take Supra Rom for example.
If it LOOKS like AOSP, the apps WORK like AOSP, why isn't it considered AOSP?
Is there something that MAKES a Rom AOSP specifically?
Android Open Source Project. When you see AOSP it means its as basic as it gets.
Sent from my PG86100 using Tapatalk
an AOSP ROM is compiled from the sources provided by the Android project.
SupraROM is still a Sense-based ROM, just with a bunch of AOSP stuff thrown in
Yes, my ROM isn't technically AOSP because it wasn't built directly from Google's source with ONLY Google programming. True AOSP has zero Sense in it, whereas mine was just heavily modified to look as much like AOSP as I could possibly make it. The new ROM in my sig however, Pulse, is true AOSP because it has no influence from HTC's devs. No apps from them, no framework from them, nothing. Just straight Android.
empiire said:
my ROM isn't technically AOSP because it wasn't built directly from Google's source .... The new ROM in my sig however, Pulse, is true AOSP....
Click to expand...
Click to collapse
Um, Pulse was not built from Google's source. If it was, where is your modified source code? Do you have a Github link?
rstuckmaier said:
Um, Pulse was not built from Google's source. If it was, where is your modified source code? Do you have a Github link?
Click to expand...
Click to collapse
I never said it was built from Google's source.
Okay, thank you everyone.
That's exactly what I thought.. but I just wanted to make sure whether there's something specific that sets them apart.
And Empiire, to be completely honest.. I LOOOOOVE SupraRom, just for that reason alone (that it's merged between the two). I hope you never stop working on it. =]
novanosis85 said:
Android Open Source Project. When you see AOSP it means its as basic as it gets.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
it seemed so sad to have all these posts about aosp but nobody provided a link to the actual repository where all official android developer publically released code and comments are kept!
for those interested and for the record - below is the link for the official aosp code in all its glory!!
http://android.git.kernel.org/
arozer said:
Okay, thank you everyone.
That's exactly what I thought.. but I just wanted to make sure whether there's something specific that sets them apart.
And Empiire, to be completely honest.. I LOOOOOVE SupraRom, just for that reason alone (that it's merged between the two). I hope you never stop working on it. =]
Click to expand...
Click to collapse
Well thank you, I was originally planning on leaving the thread to die but I've had plenty of PMs asking to keep development going, so I guess I will.
empiire said:
Well thank you, I was originally planning on leaving the thread to die but I've had plenty of PMs asking to keep development going, so I guess I will.
Click to expand...
Click to collapse
You should at least keep up on it until you get sound working on Pulse. Seriously, if we had an AOSP Rom with sound working I would be rockin it. I have to be able to make and receive calls, or I would be all over it. From what I understand, you can't hear the person you are calling. I'm going to continue to use Supra AOSP version until we get a working AOSP build with sound.
empiire said:
I never said it was built from Google's source.
Click to expand...
Click to collapse
You implied it. I quoted it. You defined an AOSP ROM as being one built from source then claimed Pulse was "true AOSP."
To the OP: their ROMs currently are "AOSP based" at best. They are not compiling these ROMs from source. They are "porting" them, in a sense.
rstuckmaier said:
You implied it. I quoted it. You defined an AOSP ROM as being one built from source then claimed Pulse was "true AOSP."
To the OP: their ROMs currently are "AOSP based" at best. They are not compiling these ROMs from source. They are "porting" them, in a sense.
Click to expand...
Click to collapse
Damn dude, chill. I'd check out a dictionary if I was going to be this technical about everything. Lmao.
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
Hello All,
As you all know I've been part of Xda and assiting in a positive resolution from HTC in requests from Bootloaders to source codes. Well seeing we have a great device that seemed to be given EOL to early in its game.. in my opinion due to lack of marketing skills. Well I will be posting in HTC FB to get our voice out to them for the Source Code release for our device.
Please comment "Like" and comment to request this so we can continue development for the Flyer.
https://www.facebook.com/photo.php?fbid=10151213297764443&set=o.165420456859572&type=1&ref=nf
And Here:
https://www.facebook.com/photo.php?fbid=10151213304969443&set=o.101063233083&type=1&relevant_count=1
Um, source code of what? They release sources of Honeycomb, and there are no sources of ICS or Jelly Bean, so what's the whole point?
Source code for drivers which can be ported to ICS and JB. Anyway it helps coders make their own drivers for Camera/Front camera and for video
kayoma said:
Source code for drivers which can be ported to ICS and JB. Anyway it helps coders make their own drivers for Camera/Front camera and for video
Click to expand...
Click to collapse
Then we would need not just the drivers, but the whole 3.x kernel. I believe it's much harder to adapt ICS/JB drivers to GB/HC kernels
kayoma said:
Source code for drivers which can be ported to ICS and JB. Anyway it helps coders make their own drivers for Camera/Front camera and for video
Click to expand...
Click to collapse
Then we're asking the wrong ppl, it's not HTC. to understand this first you need to understand what makes up a ROM.
There is the kernel which is low level device specific, the kernel is mostly based on open source linux code, htc adds some board and device specific configuration on top of that.
Then there is the aosp which is also open source, an operating system provided by google that makes up most part of any ROM.
Then you have your aosp derivative like CM or AOKP, which provides board specific fixes and some customization. HTC's ROM is also based on aosp, but they add their own sense look and feel to it.
And finally and most importantly you have your close source proprietary drivers provided by chip manufactures like Qualcomm and TI. They control cameras, wifi, BT...etc. So in reality there is very little HTC could do as they don't have the rights to release these code. And that's is where most ppl run into issues.
So to create a ROM is not hard at all, anybody can download the source code and compile it to generate a ROM as most of the source code are all open source. What will be helpful is if Qualcomm releases the source code for their drivers, which I doubt they will ever do, otherwise they wouldn't be close source in the first place. The only thing we could do is try to reverse engineer the device base on logs and understanding of how each component should work and make educated guesses.
Due to HTC lack of effort on this device (No ICS - HC was slow joke) I will never buy another HTC product again, same goes for sony, though they did eventually update xperia x10i it was only due to huge pressure not because they wanted to.
I want to buy an electronic product that potentially remains relevant at least a year later otherwise forget it.
so i sent this letter to HTC
after reading this page where HTC discusses 4.1 upgrades i decided to drop them a line "
DIRECTLY FROM YOUR WEBSITE:
When will additional devices receive Android 4.1?
In addition to the HTC One X and HTC One S, we are actively reviewing our product portfolio to identify candidates to receive Jelly Bean. Our goal is to prioritize review for devices launched in 2012 with our numerous carrier partners across multiple regions and then consider our ability to provide updates to products from 2011.
What devices will not get Android 4.1?
We work hard to ensure each of our products has the optimal user experience and therefore some products will remain at their current version of Android. In general, devices with 512MB RAM or less will not be upgraded to Android 4.1. At present, these devices include the HTC One V and the HTC Desire C. As we identify other devices that will not be upgraded, we'll provide updated information.
What about a development version of Android 4.1?
For our developer community, we plan to make generic development ROMs of Jelly Bean available for both the HTC One X and HTC One S. As soon as the ROMs are ready, they will be posted to our HTCdev site (www.htcdev.com). We strongly recommend customers take the time to understand the limitations of the development software along with the terms and conditions on the site before downloading to their device.
REALLY!? have you listened to what your customers have asked/said about the HTC flyer at all?! where is OUR 4.1 DEVELOPMENT ROM! wtf! where are you for us!? I can tell you where... you are giving us 3.2 HC that takes away two very important features i bought the device for #1 GPS! completely broken by your newest update to HC. #2. Hardware Keys.... WHY?! i understand that HC introduced soft keys. so you say you "We work hard to ensure each of our products has the optimal user experience" BULL! you clearly weren't thinking about the end user when you pushed out that HC update for the flyer. Would have been smarter for you to leave us on working GB and go straight to ICS or JB when it was ready! this is lunacy! who ever is making decisions in your company needs fired. you are bleeding money from everywhere. why don't you bring it back to the old school HTC that CARED! ABOUT! IT'S CUSTOMERS! listen to what we are saying! hear our voice! we have signed petitions. we have pleaded on multiple forums. WE have poured over your FB and twitter pages asking for you to throw us a freaking bone here.... when is it gonna happen? ever?!
I still have my flyer and i love it dearly. but without updates it's falling behind the pack. I recently bought a 10.1 galaxy note. while i'm happy with it's speed and what not. it's not the form factor i want. which is what the flyer is for me. perfect. PLEASE DON'T GIVE UP ON US OR THIS DEVICE! PLEASE RELEASE A DEVELOPER ROM FOR OUR FLYER! "
this was their reply (you will want to read it for sure)
Dear Matt,
Thanks for contacting HTC!
We completely understand your concern and I thank you for your patience and am deeply sorry if this issue has caused you any dissatisfaction with HTC or its phones. I hope that it will not detract from your overall perspective of the device or the company. You are the most important part of the HTC Family.
We listen to our community and feedbacks like yours are the ones that make us revise our decisions, and try to find the correct balance between the device’s performance and usability. We cannot announce or say anything about the Flyer right now but what I can tell you is that we are, indeed, paying attention to the community´s feedback and opinions.
Should you require further assistance, please do not hesitate to contact us through http://www.htc.com/us/support/email-support or call us at +1-866-449-8358 from 6AM to 1AM EST, 7 days a week.
Have a great day!
Let me know if I have successfully answered your question, please click here to complete this.
To send a reply to this message, please click here.
Sincerely,
Carlos
HTC
I appreciate the passion here, but HTC left this device for dead along with the Jetstream and View shortly after releasing it. We received what would amounted to a Beta of Honeycomb then they closed up shop. You live and learn, and although I still use my Flyer and enjoy it I will not buy another HTC device
I completely agree with you .. HTC should give us ICS or JB for our Flyer as a good faith. We must keep GB because honeycomb is a joke..
I use my Flyer and i try as much as possible with the optimized news on GB .. and share with you.
Hoping for a good action on their part for JB!!
Fatal1ty_18_RUS said:
Then we would need not just the drivers, but the whole 3.x kernel. I believe it's much harder to adapt ICS/JB drivers to GB/HC kernels
Click to expand...
Click to collapse
so the kernel source for HC 3.2 that's in HTCDev,,that is NOT the entire kernel sourcecode?
i know it's an old thread but i am wondering...
gersto said:
so the kernel source for HC 3.2 that's in HTCDev,,that is NOT the entire kernel sourcecode?
i know it's an old thread but i am wondering...
Click to expand...
Click to collapse
that the honeycomb kernel .
doesn't do you much good for ICS or JB
yncconsulting said:
Then we're asking the wrong ppl, it's not HTC. to understand this first you need to understand what makes up a ROM.
.
.
.
Click to expand...
Click to collapse
You didn't understand I think. The drivers are part of the kernel. May they be compiled into the kernel itself or in form of modules. Drivers can be binary objects to be linked (already compiled) or source code which will be compiled when the kernel is built.
If you have the drivers source code there is a fairly good chance to get them running in newer kernels with some minor changes.
So from my point of view you will have a good chance to even get 4.2 up and running as long as you have the drivers source code.
Sent from my GT-I9100G using xda app-developers app
ktp1976 said:
You didn't understand I think. The drivers are part of the kernel. May they be compiled into the kernel itself or in form of modules. Drivers can be binary objects to be linked (already compiled) or source code which will be compiled when the kernel is built.
If you have the drivers source code there is a fairly good chance to get them running in newer kernels with some minor changes.
So from my point of view you will have a good chance to even get 4.2 up and running as long as you have the drivers source code.
Sent from my GT-I9100G using xda app-developers app
Click to expand...
Click to collapse
yeah, so my point is HTC publishes kernel source code, not drivers, they don't even own some of the drivers .,so you will never get that. You get a HC kernel ,that works with a HC blob set and you cannot build a working 4.xx kernel because you don;t have a 4.xxx blob set and HTC won't give you one because they have never written one and never will
DigitalMD said:
that the honeycomb kernel .
doesn't do you much good for ICS or JB
Click to expand...
Click to collapse
well they must be of some good since we have ICS/JB ROMs out there that are "mostly" complete, slick and usable, although slightly buggy, so obviously yeah i get that it doesn't solve all the issues we have, since some drivers are missing: as evident by the non-working FC, no hardware decoding for video, and semi-working BT
DigitalMD said:
yeah, so my point is HTC publishes kernel source code, not drivers, they don't even own some of the drivers .,so you will never get that. You get a HC kernel ,that works with a HC blob set and you cannot build a working 4.xx kernel because you don;t have a 4.xxx blob set and HTC won't give you one because they have never written one and never will
Click to expand...
Click to collapse
Not exactly. The kernel is also part of AOSP. And even if HTC does not supply the driver sources there is a slight chance to use old driver binaries or to have them reverse engineered by some genius dev. Hope is the last to die
Sent from my GT-I9100G using xda app-developers app
ktp1976 said:
Not exactly. The kernel is also part of AOSP. And even if HTC does not supply the driver sources there is a slight chance to use old driver binaries or to have them reverse engineered by some genius dev. Hope is the last to die
Sent from my GT-I9100G using xda app-developers app
Click to expand...
Click to collapse
Keep dreaming. Some of the best around have tried that path.
No the device kernel is not in AOSP, the base linux (ANdorid) kernel source resides there, but if you look at the build, it calls in device , vendor, OS verson and board specific components to make a complete build. All that hooks into the blobs (drivers and libs) to make up the device specific environment that allows Android version X.XX to run
DigitalMD said:
Keep dreaming. Some of the best around have tried that path.
No the device kernel is not in AOSP, the base linux (ANdorid) kernel source resides there, but if you look at the build, it calls in device , vendor, OS verson and board specific components to make a complete build. All that hooks into the blobs (drivers and libs) to make up the device specific environment that allows Android version X.XX to run
Click to expand...
Click to collapse
Thanks for clarification. So I was not wrong about the drivers, which are the device and vendor specific components. In other words if you can get the vendor to release their sources or make their chip/board manufacturers to release their sources is the only way to go. Seems a bit unrealistic though but who knows...
Sent from my GT-I9100G using xda app-developers app
All should email the HTCDev
Use this link http://www.htcdev.com/contact
They themselves posted on that link
https://www.facebook.com/photo.php?fbid=10151213304969443&set=o.101063233083&type=1&relevant_count=1
Takes just f**kin 5 seconds
May be they will listen some day
freworld said:
All should email the HTCDev
Use this link http://www.htcdev.com/contact
They themselves posted on that link
https://www.facebook.com/photo.php?fbid=10151213304969443&set=o.101063233083&type=1&relevant_count=1
Takes just f**kin 5 seconds
May be they will listen some day
Click to expand...
Click to collapse
+1
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