I would be willing to run logcats, test installs, and check features for alpha testing, but I am curious to learn more about whether or not HTC has released the source code on the PrimoC yet. If anyone knows...I wud appreciate the help.
Molikai1988 said:
I would be willing to run logcats, test installs, and check features for alpha testing, but I am curious to learn more about whether or not HTC has released the source code on the PrimoC yet. If anyone knows...I wud appreciate the help.
Click to expand...
Click to collapse
No, they haven't.
Sent from my HTC One V using Tapatalk 2
I am beginning to wonder if this is Virgin Mobile not letting them. If they won't release the source to the cdma but they will for the GSM then perhaps a reverse compile is possible. If the code is similar enough then using the source from the GSM as a base could yield some source.
Molikai1988 said:
I am beginning to wonder if this is Virgin Mobile not letting them. If they won't release the source to the cdma but they will for the GSM then perhaps a reverse compile is possible. If the code is similar enough then using the source from the GSM as a base could yield some source.
Click to expand...
Click to collapse
CDMA CM9 needs custom kernel for audio. That's all I known
Sent from my HTC Desire using xda premium
Lloir said:
CDMA CM9 needs custom kernel for audio. That's all I known
Sent from my HTC Desire using xda premium
Click to expand...
Click to collapse
So the hardware should be close, but I see that this is true about the audio...will have to keep one eye on HTC for the source...till then I guess its NoN-sEnSe primo-c 1.1.
I don't think it would be Virgin Mobile calling the shots imo. They would lose potential sales whereas HTC will find a different carrier.
Yeah I just checked with a guy I know that works support for htc. He said its scheduled soon. So at least its soon lol. Just wish he cud say when.
Sent from my HTC One V using xda app-developers app
Molikai1988 said:
Yeah I just checked with a guy I know that works support for htc. He said its scheduled soon. So at least its soon lol. Just wish he cud say when.
Sent from my HTC One V using xda app-developers app
Click to expand...
Click to collapse
really? cause im honestly saying close to the end of august or beginning of september. This is their track record....
I also talked to them about the kernel source for CDMA/Virgin Mobile USA HTC ONE V, they do have plans to release the source however it takes longer for CDMA vs GSM, something to do with the more proprietary nature of CDMA, we've seen this cause delays with AOSP build on CDMA Nexus Devices, so it doesn't surprise me that it's taking longer to release. However in the mean time the hardware differences between GSM and CDMA variants should be minuscule (cellular data being the obvious one) so could we continue making the build without data/sound and just add those when the drivers are available so time isn't wasted on waiting for sources to be released? I would be willing to test.
MtDewFella said:
I also talked to them about the kernel source for CDMA/Virgin Mobile USA HTC ONE V, they do have plans to release the source however it takes longer for CDMA vs GSM, something to do with the more proprietary nature of CDMA, we've seen this cause delays with AOSP build on CDMA Nexus Devices, so it doesn't surprise me that it's taking longer to release. However in the mean time the hardware differences between GSM and CDMA variants should be minuscule (cellular data being the obvious one) so could we continue making the build without data/sound and just add those when the drivers are available so time isn't wasted on waiting for sources to be released? I would be willing to test.
Click to expand...
Click to collapse
I already have a thread up for CM9. I am releasing a new one today that has sound working and is on par with the GSM version status.
jmztaylor said:
I already have a thread up for CM9. I am releasing a new one today that has sound working and is on par with the GSM version status.
Click to expand...
Click to collapse
Yup just found it, like I said over there, I'll risk my phone in testing (joking, I don't actually believe your build will destroy my phone, this isn't my first beta testing rodeo) for the benefit of the Greater android community.
Related
I am a noob to these forums and this seemed the best place to ask considering it is a Q&A forum. Considering the G2 is a stock android device how hard would it be to make a stock gingerbread ROM for it? Are any devs out there working on it? Is teamdouche working on CM v7 based on 2.3? I have been looking around for any inclination of this but have seen none whilst other devices get gingerbread ported over/compiled for them. Just want to know the status (or hopefully an ETA) on a Gingerbread ROM for the G2. If I posted this in the wrong place or this has been posted before my apologies.
Sent from my HTC Vision using XDA App
I don't know if it's out yet, mang... but I'm sure that once it is, it'll be a hot commodity. The modding community is absolutely amazing and I think they seriously need to be hired by some of the mobile companies out there. Their work is fantastic.
well nobody can make a rom or anything until the source code is released...and that hasnt happend yet. as soon as the nexus s comes out (which is this week) then the source code will be extracted from gingerbread and itll be able to be used. right now we just had a SDK file, and that really isnt used for anything but looks. mainly used for themes and such.
Then why does the EVO have a full working ROM for gingerbread? I believe the DESIRE and the HD2 also have it going.
Sent from my HTC Vision using XDA App
There isn't a working gingerbread ROM for the EVO, it's just FroYo with some parts ripped from 2.3. Gingerbread will be released in a couple of days along with the Nexus S, after which the AOSP will be ported to existing devices - but it'll still be a few days, if not weeks until something stable comes out.
I wouldn't hold my breath for it.
My apologies for my ignorance. I thought they were actual 2.3 builds considering the XDA posted list says "devices running gingerbread". So absolutly nothing can happen with gingerbread until a device with gingerbread (nexus S) comes out?
Sent from my HTC Vision using XDA App
Cyanogen will not port it to the G2until 2.3 is released for the G2.
Sent from my CyanogenMod G2 using XDA app
Veiger said:
My apologies for my ignorance. I thought they were actual 2.3 builds considering the XDA posted list says "devices running gingerbread". So absolutly nothing can happen with gingerbread until a device with gingerbread (nexus S) comes out?
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Not a problem, you were just asking
All we have running Gingerbread right now is the android emulator, from which we can pull apk's and libs, but most of them need tweaking to get them to work on FroYo. Plus I don't know if the market works on Gingerbread.
ddgarcia05 said:
Cyanogen will not port it to the G2until 2.3 is released for the G2.
Sent from my CyanogenMod G2 using XDA app
Click to expand...
Click to collapse
Is that an actual statement from teamdouche/cyanogen or just from studying release behavior in the past? When you say release you mean T-mo pushes it as an OTA correct, I know someone on here will "release" 2.3 long before T-mo stamps it for approval.
Sent from my HTC Vision using XDA App
keinengel said:
Not a problem, you were just asking
All we have running Gingerbread right now is the android emulator, from which we can pull apk's and libs, but most of them need tweaking to get them to work on FroYo. Plus I don't know if the market works on Gingerbread.
Click to expand...
Click to collapse
So at the moment there is no actual gingerbread (save for the reveiw models floating around phonedog,mobileburn,etc are unboxing) out just froyo with the modified characteristics of gingerbread? Pardon the question if it seems silly, most of the comment went over my head.
Sent from my HTC Vision using XDA App
I'll bet we have a ported ROM before New Years, usually a huge release like this gets all the attention of the devs. Especially since with perm-root, s-off and several stable 2.2 ROMs, the devs don't have all that much to work on atm.
Team Villain were working on one, but it became clear that there was going to be no way to make Audio work until AOSP is out so its on hold until then.
and without audio a phone is useless, no ringing, no sound in calls, no music etc etc
Lennyuk said:
Team Villain were working on one, but it became clear that there was going to be no way to make Audio work until AOSP is out so its on hold until then.
and without audio a phone is useless, no ringing, no sound in calls, no music etc etc
Click to expand...
Click to collapse
Definatley looking forward to it when Villain gets their hands on the source code. I bet T-mo's is going to be ladened with the same bloatware that their 2.2 install on the G2 had.
Sent from my HTC Vision using XDA App
Well atleast we have the themes for now, that will hold me over for a couple weeks but not to impressed by the nexus s enough to shell out $520 I might just buy vibrant when functional gingerbread port is out allot cheaper and almost same phone well close anyway.
Sent from my G2 Cyanogen 6.1 gingerbread theme
Honestly I would wait if your shelling out any money for anything samsung just placed a MASSIVE order for tegra 2's today which hints at dualcore phones sometime in q1 or Q2 next year hopefully. Wait for the qualcomm dualcore and nvidia dualcore wars to begin.
Sent from my HTC Vision using XDA App
Anyone know roughly how long it takes google to drop the source in aosp after the sdk is released?
ddgarcia05 said:
Cyanogen will not port it to the G2until 2.3 is released for the G2.
Sent from my CyanogenMod G2 using XDA app
Click to expand...
Click to collapse
Highly doubt that's true. I came from a CDMA Hero running CM6 RC1 (Froyo) and as most of us know, the lower end devices (such as the Hero), never got an official 2.2, yet there was a fully functional, highly stable CM6 out for it.
Which ran magnificently BTW.
Ah yeah, those seem to be more like proof of concept. Once a retail version of handsets start coming out with Gingerbread, as well as the source code, I imagine we'll start seeing custom ROMs based off it.
Veiger said:
Honestly I would wait if your shelling out any money for anything samsung just placed a MASSIVE order for tegra 2's today which hints at dualcore phones sometime in q1 or Q2 next year hopefully. Wait for the qualcomm dualcore and nvidia dualcore wars to begin.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Thats all i needed to hear...samsung should'nt getanybody money with their softaware build qaulity and support
Gingerbread doesn't seem to be very promising though, what's with all this hype around it?? The update seems pretty piss poor to be honest. Nothing much.
As stated in the subject is Google supporting the GSM version before the LTE and is cyanogenmod focusing on the LTE more than the GSM?
Sent from my Galaxy Nexus using XDA App
GSM will probably get updates first, but it probably won't be by a discernible amount. They're working on both concurrently.
CM is focusing on both models.
So far, Toro has received them first.
4.0.2 was out for Toro before Maguro, but Toro wasn't released yet for sale.
4.0.4 is out for Toro, but not officially. Maguro hasn't seen a "leak" (4.0.4 is on an ota server for Toro, just not pushed).
Personally, I'd say its a crapshoot as to which is quicker (so far).
Most of the devs doing both release updates at the same time for both (its easy to do both).
The source will always be released for both at the same time, OTA's have been coming out on the LTE before though...it just depends.
I thought I read somewhere that Goog had dropped Toro as a dev phone - which would imply the Maguro is now top dog?
I'd hope so, I think maguro should be the first to get the updates considering it was the first one out
Sent from my Galaxy Nexus using XDA App
danger-rat said:
I thought I read somewhere that Goog had dropped Toro as a dev phone - which would imply the Maguro is now top dog?
Click to expand...
Click to collapse
Misconception, it was removed from their dev list along with all the CDMA phones due to CDMA needing proprietary files to join the network. Or at least that is how I understood the articles I read on it.
Sent from my Galaxy Nexus using Tapatalk
I just wish the updates came faster
_Dennis_ said:
Misconception, it was removed from their dev list along with all the CDMA phones due to CDMA needing proprietary files to join the network. Or at least that is how I understood the articles I read on it.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
That's about right. Basically the CDMA network stack required for full functionality on Sprint and Verizon isn't open source, so Google decided it wasn't a good idea to put up code that would effectively create incomplete builds for the NS4G, Xoom LTE, and VZW Galaxy Nexus.
Sent from my Galaxy Nexus using XDA App
So, logically, what would the alternative complete build be?
Considering any source released for one will be cooked into roms for both likely the same day it doesn't matter one bit.
danger-rat said:
So, logically, what would the alternative complete build be?
Click to expand...
Click to collapse
What comes out in the OTA... because that'll contain all the proper radios and network code.
Who gets the update first?
Of course people from the XDA forum, who else?
Take a look at current official version of Galaxy Nexus, 4.0.2.
What version are available? 4.0.3... If leaked 4.0.4 should not be counted...
Google is recently becoming sux at updates.
I would imagine upcoming ICS new phones will have newer version than the official Galaxy Nexus.
Sad, but that's the truth....
Sent from my Galaxy Nexus using xda premium
At the moment, neither
I just hope Google doesn't let ICS turn into another Honeycomb fiasco.
martonikaj said:
That's about right. Basically the CDMA network stack required for full functionality on Sprint and Verizon isn't open source, so Google decided it wasn't a good idea to put up code that would effectively create incomplete builds for the NS4G, Xoom LTE, and VZW Galaxy Nexus.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Almost.
The stack is open source, the blobs needed for it are not, and cannot be redistributed any longer. AOSP will not remove CDMA or LTE code from telephony.
martonikaj said:
What comes out in the OTA... because that'll contain all the proper radios and network code.
Click to expand...
Click to collapse
AOSP contains all required network code and will continue to do so. Us CDMA devs just have to be...creative in how we get our proprietary blobs.
adrynalyne said:
Almost.
The stack is open source, the blobs needed for it are not, and cannot be redistributed any longer. AOSP will not remove CDMA or LTE code from telephony.
Click to expand...
Click to collapse
adrynalyne said:
AOSP contains all required network code and will continue to do so. Us CDMA devs just have to be...creative in how we get our proprietary blobs.
Click to expand...
Click to collapse
Thanks for the slight clarification. I was just trying to generalize to make it easy to digest.
I'd like to say maguro gets it first as toro had the leaked 4.0.4 but then perhaps that's more reason they would get it first. I wouldn't of thought there will be much in it, less than a few days I hope.
Sent from my Galaxy Nexus using Tapatalk
hello all
i look at the list of roms and its amazing how little support for this device there is. Most roms either discontinued or not been updated for a while.
but i have an idea how we can change this.
i have built cyanogenmod for many devices (xperia play, htc wildfire, htc desire) and even thou most of them wasn't released i wanna make something to share and help keep this device going. i am hoping that if this is successful then we would see or devices running android 5 (if that's what version it is)
so on to the question...
Where do i get the sources to build cyanogenmod for our device?
hope you guys can help me, i really want to start working on this device
dtronics said:
hello all
i look at the list of roms and its amazing how little support for this device there is. Most roms either discontinued or not been updated for a while.
but i have an idea how we can change this.
i have built cyanogenmod for many devices (xperia play, htc wildfire, htc desire) and even thou most of them wasn't released i wanna make something to share and help keep this device going. i am hoping that if this is successful then we would see or devices running android 5 (if that's what version it is)
so on to the question...
Where do i get the sources to build cyanogenmod for our device?
hope you guys can help me, i really want to start working on this device
Click to expand...
Click to collapse
which cyanogenmod? we do have already cm 9/10
Sent from my One V using xda premium
Well currently there are two devices, the CDMA and GSM. Both have different device trees. Check the Guthubs of Deva like Rukin, Awidawad, Lloir, etc.
Sent from my One V using xda premium
martijn99 said:
which cyanogenmod? we do have already cm 9/10
Sent from my One V using xda premium
Click to expand...
Click to collapse
either but preferably cm 10
reV17 said:
Well currently there are two devices, the CDMA and GSM. Both have different device trees. Check the Guthubs of Deva like Rukin, Awidawad, Lloir, etc.
Sent from my One V using xda premium
Click to expand...
Click to collapse
cheers because i live in the UK i would only be able to dev the GSM version unless i can find someone to test the CDMA version then i might do both
When will see some custom kernels? If we have cm 10.2 ROMs thejbwe should have kernels right.
Sent from my HTC One VZW using Tapatalk 4
coldconfession13 said:
When will see some custom kernels? If we have cm 10.2 ROMs thejbwe should have kernels right.
Sent from my HTC One VZW using Tapatalk 4
Click to expand...
Click to collapse
Htc has to release the source code first. Please bug them on Twitter or HTC Dev
Sent from my HTC6500LVW using xda app-developers app
But isn't cm 10.2 a custom kernel
Sent from my HTC One VZW using Tapatalk 4
coldconfession13 said:
But isn't cm 10.2 a custom kernel
Sent from my HTC One VZW using Tapatalk 4
Click to expand...
Click to collapse
You really need to give it some time. The Verizon One is still new and locked because of yours truly. I'm just as anxious as you are but development takes time; especially with devices on VZW.
DroidOnRoids said:
You really need to give it some time. The Verizon One is still new and locked because of yours truly. I'm just as anxious as you are but development takes time; especially with devices on VZW.
Click to expand...
Click to collapse
+1 very well said.
Patience is a virtue in the Android world.
I've got one in the works
EDIT: It's not gonna be anything major or groundbreaking right now, but it'll be based on cm's and have most of the cool features on m7ul custom kernels
From what I've read the international LTE kernel source is what is being used to make custom kernels for our device. I haven't seen it implemented yet, so it would be great to see a kernel with system write protection disabled.
Sent from my HTC6500LVW using xda app-developers app
xenakis said:
From what I've read the international LTE kernel source is what is being used to make custom kernels for our device. I haven't seen it implemented yet, so it would be great to see a kernel with system write protection disabled.
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
Those kernels are for AOSP. For a sense kernel, you would probably be better off waiting for kernel source to drop from HTC
sonicxml said:
Those kernels are for AOSP. For a sense kernel, you would probably be better off waiting for kernel source to drop from HTC
Click to expand...
Click to collapse
Unfortunately, waiting on HTC to drop kernel source is like waiting on a Verizon OTA lol
Sent from my HTC6500LVW using Tapatalk 4
DroidOnRoids said:
Unfortunately, waiting on HTC to drop kernel source is like waiting on a Verizon OTA lol
Sent from my HTC6500LVW using Tapatalk 4
Click to expand...
Click to collapse
maybe verizon is making htc delay on releasing kernel source to try and slow down development lol
DroidOnRoids said:
Unfortunately, waiting on HTC to drop kernel source is like waiting on a Verizon OTA lol
Sent from my HTC6500LVW using Tapatalk 4
Click to expand...
Click to collapse
Except HTC is legally required to release the code in a timely fashion. The code will not drop until after 4.3 is out and they usually take 2-3 months to release it. It has absolutely no bearing on an exploit or root. When the DNA got the 2.04 update, HTC took about a month to release it. AOSP kernels like CM do not rely on this. Luckily, the M7 has a nice device tree so whoever is maintaining it now (I am assuming flyhalf) does not need to modify it drastically (much much unlike the DNA). So CM wise, we seem to be fine. You will not see a custom sense kernel until the source is released.
123421342 said:
Except HTC is legally required to release the code in a timely fashion. The code will not drop until after 4.3 is out and they usually take 2-3 months to release it. It has absolutely no bearing on an exploit or root. When the DNA got the 2.04 update, HTC took about a month to release it. AOSP kernels like CM do not rely on this. Luckily, the M7 has a nice device tree so whoever is maintaining it now (I am assuming flyhalf) does not need to modify it drastically (much much unlike the DNA). So CM wise, we seem to be fine. You will not see a custom sense kernel until the source is released.
Click to expand...
Click to collapse
That never happens lol only for GE HTC One it was released the same day or something
As for kernel, it could be patched from international One but then it would be a hacky impllementation.. imo not good. Because most AOSP ROMs are based of a derivative of the CM One kernel, the CDMA Ones use this same kernel: maybe there are a few patches to get it working but most of it is just from the international AOSP kernels.
Thats why there are Verizon AOSP kernels and not sense kernels. No one has patched a sense kernel to work on Verizon yet (whether they can't or are simply waiting for proper source is irrelevant, however I would lean towards the latter)
i not???
poondog said:
That never happens lol only for GE HTC One it was released the same day or something
As for kernel, it could be patched from international One but then it would be a hacky impllementation.. imo not good. Because most AOSP ROMs are based of a derivative of the CM One kernel, the CDMA Ones use this same kernel: maybe there are a few patches to get it working but most of it is just from the international AOSP kernels.
Thats why there are Verizon AOSP kernels and not sense kernels. No one has patched a sense kernel to work on Verizon yet (whether they can't or are simply waiting for proper source is irrelevant, however I would lean towards the latter)
Click to expand...
Click to collapse
Whassup my vivo brethren...? I may try to patch said kernel to Verizon soon...no promises though.
123421342 said:
Except HTC is legally required to release the code in a timely fashion. The code will not drop until after 4.3 is out and they usually take 2-3 months to release it. It has absolutely no bearing on an exploit or root. When the DNA got the 2.04 update, HTC took about a month to release it. AOSP kernels like CM do not rely on this. Luckily, the M7 has a nice device tree so whoever is maintaining it now (I am assuming flyhalf) does not need to modify it drastically (much much unlike the DNA). So CM wise, we seem to be fine. You will not see a custom sense kernel until the source is released.
Click to expand...
Click to collapse
Yeah...But whether they actually do it or not is another thing. "Timely" isn't actually defined very concretely.
---------- Post added at 05:58 PM ---------- Previous post was at 05:54 PM ----------
coldconfession13 said:
But isn't cm 10.2 a custom kernel
Sent from my HTC One VZW using Tapatalk 4
Click to expand...
Click to collapse
The reason there is AOSP source even though there is no Verizon kernel source is because CM commonizes the kernels by related device families to minimize the amount of work that needs to go into it. There is one and only one kernel for all the M7 variants, with a couple options changed, etc, but it's the exact same source tree.
brymaster5000 said:
Whassup my vivo brethren...? I may try to patch said kernel to Verizon soon...no promises though.
Click to expand...
Click to collapse
Hathoiught i might see one of you guys here one day.. Hopefully I get my One back from repair (having huge issues with their and my carriers services) so I can start doing stuff to it
I reckon there's not much harm in waiting, and that's better for the long run anyway
Has anyone tried flashing faux123's kernel that states it works on all carriers except Sprint?
The 4.2.2 version?
brymaster5000 said:
Has anyone tried flashing faux123's kernel that states it works on all carriers except Sprint?
The 4.2.2 version?
Click to expand...
Click to collapse
If it doesnt work on sprint, a cdma carrier, why would it work for verizon?
123421342 said:
If it doesnt work on sprint, a cdma carrier, why would it work for verizon?
Click to expand...
Click to collapse
I was thinking that because it is 4GLTE (which I read was bridging the gap between CDMA and GSM...or eventually going to), it may work. We ported a kernel from the international Incredible 2 (GSM) onto the Verizon Incredible 2 (CDMA) without issues...
Just thinking out loud.
brymaster5000 said:
I was thinking that because it is 4GLTE (which I read was bridging the gap between CDMA and GSM...or eventually going to), it may work. We ported a kernel from the international Incredible 2 (GSM) onto the Verizon Incredible 2 (CDMA) without issues...
Just thinking out loud.
Click to expand...
Click to collapse
As long as there is ril support and all drivers work then it's a simple build prop tweak
Sent from my HTC6500LVW using xda app-developers app
How does HTC compare to Samsung?
Is *everything* HTC produces available to devs? Or does HTC refuse to release proprietary source code like Samsung does?
Will 'unofficial' builds be able to be rated as stable?
Sent via my Markox/Gustavo_s powered KitKatted S2
HTC does release source and stable builds of aosp are typically achieved. The main thing you have to worry about is when HTC decides end of update lifecycle. That's when stable releases for aosp base becomes really slow.
Since there's a gpe version, I'm hoping the update lifecycle will be longer than previous HTC phones.
I owned an Evo 3d and one xl previously.
Sent from my HTC One_M8 using XDA Free mobile app
Thanks @exad
How quickly does that happen?
What sort of update life cycle can the M8 expect?
Sent via my Markox/Gustavo_s powered KitKatted S2
Hmmm a year and a halfish? As for what we can expect for the m8.. I am without a crystal ball.
Sent from my HTC One_M8 using XDA Free mobile app
exad said:
Hmmm a year and a halfish? As for what we can expect for the m8.. I am without a crystal ball.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Lol....I wasn't expecting an exact answer, just wondered if HTC had a policy of updating for a specified set duration irrespective of model.....
Sent via my Markox/Gustavo_s powered KitKatted S2
Not that I know of.
Sent from my HTC One_M8 using XDA Free mobile app
keithross39 said:
Lol....I wasn't expecting an exact answer, just wondered if HTC had a policy of updating for a specified set duration irrespective of model.....
Sent via my Markox/Gustavo_s powered KitKatted S2
Click to expand...
Click to collapse
They're committed to two years on major Android updates for North American phones.
The ever necessary source so that the naysayers are kept at bay: http://www.reddit.com/r/Android/comments/1xxjfx/hi_were_the_htc_usa_product_team_amaa/
jdk2 said:
They're committed to two years on major Android updates for North American phones.
The ever necessary source so that the naysayers are kept at bay: http://www.reddit.com/r/Android/comments/1xxjfx/hi_were_the_htc_usa_product_team_amaa/
Click to expand...
Click to collapse
That's not so bad.......
The average phone contract here in the UK is 2 years........
By the time my current contract is up and I get the M8, the end of my new 2 year contract will put me about 6 months past that 2 year update life cycle........
I can live with that.......
Sent via my Markox/Gustavo_s powered KitKatted S2
keithross39 said:
How does HTC compare to Samsung?
Is *everything* HTC produces available to devs? Or does HTC refuse to release proprietary source code like Samsung does?
Will 'unofficial' builds be able to be rated as stable?
Sent via my Markox/Gustavo_s powered KitKatted S2
Click to expand...
Click to collapse
well it IS proprietary...meaning it isn't open source so they don't have to release it.
and yes, they refuse to release sources for Sense and many of their Sense applications.
Hellscythe said:
well it IS proprietary...meaning it isn't open source so they don't have to release it.
and yes, they refuse to release sources for Sense and many of their Sense applications.
Click to expand...
Click to collapse
THAT I can understand.....it'll be the same for any manufacturer.......
But then Sense, Touchwiz and the like isn't strictly needed for AOSP.
What I was asking about (and probably should have been clearer about) was device source code......
Case in point......
Samsung and Exynos.......source code needed to make the device function correctly irrespective of what is running on it.....
Sent from my GT-I9100 using XDA Free mobile app
keithross39 said:
THAT I can understand.....it'll be the same for any manufacturer.......
But then Sense, Touchwiz and the like isn't strictly needed for AOSP.
What I was asking about (and probably should have been clearer about) was device source code......
Case in point......
Samsung and Exynos.......source code needed to make the device function correctly irrespective of what is running on it.....
Sent from my GT-I9100 using XDA Free mobile app
Click to expand...
Click to collapse
I understood what you meant and answered you. They do for all versions until support for the device ends
Sent from my HTC One_M8 using XDA Free mobile app
keithross39 said:
How does HTC compare to Samsung?
Is *everything* HTC produces available to devs? Or does HTC refuse to release proprietary source code like Samsung does?
Will 'unofficial' builds be able to be rated as stable?
Sent via my Markox/Gustavo_s powered KitKatted S2
Click to expand...
Click to collapse
HTC refuses to release proprietary code. This has always been a problem with HTC and will likely continue to be one. Don't believe me ask kernel developer @flar2. The first source code they released not too long had a fair amount of code lopped off of it. The only truly open source is AOSP. Even the Nexus line diverges a bit from true open source as they have closed source certain apps like google calendar, maps and keyboard. But these can at least be downloaded from play store.
So is HTC still perceived as the least (or so I have read) 'dev friendly' manufacturer?
Sent from my rooted debloated thingy
keithross39 said:
So is HTC still perceived as the least (or so I have read) 'dev friendly' manufacturer?
Sent from my rooted debloated thingy
Click to expand...
Click to collapse
There definitely up there, I think Samsung especially the exynos version is worse. At the least we have access to Code Aurora (Qualcomm source code) and they are very good about releasing source.
jlevy73 said:
There definitely up there, I think Samsung especially the exynos version is worse. At the least we have access to Code Aurora (Qualcomm source code) and they are very good about releasing source.
Click to expand...
Click to collapse
EDIT: Sorry @jlevy73 - I quoted the wrong person.
They all have things that include IP that is closed, including Google Nexus, which is also different from AOSP.
Some of the things aren't even HTC related, there are proprietary drivers & such that they themselves license from Qualcomm, & other component manufacturers. I would say that they are much more developer friendly than most of the OEM's.
Well, none of that is going to affect my decision to get the M8.......
I just want to be able to proceed with all the relevant information......
So long as I can.....
A) root it
B) install some root access apps
C) debloat (if necessary)
D) *maybe* flash a custom rom
(In that order, with D being a possibility rather than a certainty)
Sent from my rooted debloated thingy