Related
Just wondering if were gonna be getting more devs to cook up some roms for this phone.. I use to have a sensation and that forum is full of devs. Anyone devs cooking roms?... I would like cyanogen, I love me some aosp.
The development is picking up and we already have three devs and someone making a theme. Not to mention faux is putting together a custom kernel. Be patient It's only been a month.
Sent from my HTC Amaze 4G using XDA App
Working on aosp Ics not a overnight project sorry
Sent from my HTC Amaze 4G using xda premium
Quality > quantity
Sent from my HTC Amaze 4G using XDA App
Teo032 said:
Quality > quantity
Sent from my HTC Amaze 4G using XDA App
Click to expand...
Click to collapse
Sure is. Better safe than sorry.
I've been wanting to get into development for a while, but since I've had a Vibrant since before it was popular, and they have fallen out of style, it wasn't the device I wanted to really work with.
That said, I hope to be buying an Amaze today, and if I can figure out a good starting point(after I get comfortable with the differences in the flashing process), I'd be interested in learning.
The biggest appeal of the Amaze is that it is a BEAST. Hardware wise this thing will hold its own for a long time to come, should be fully capable of running whatever the future throws at it. I noticed a big part of development is the popularity of the device, this phone is new, and it is obviously popular.. it will get plenty of development I'm sure, just be patient!
Edit: One of the most important things I see about the amaze(development wise), developers won't have to work around a lack of features like they did the Vibrant. Color-fixes, enabling a notification light, getting gps to work-- there were tons of things they had to try to overcome rather than just make a solid, stable, feature filled rom. The amaze doesn't sound like it will have these issues.
Patience my friend. We just built the Dojo, and we're now filling it with some wicked devs. The only thing X isn't working on is a froyo ROM... which I am not above requesting just to see if anything can rattle the guy
Everything is good, we have Revolution.
Lacking S-OFF doesn't help bring devs into a device.
X has made some awesome roms. very very thankful
chrischoi said:
Everything is good, we have Revolution.
Click to expand...
Click to collapse
lmao good one lol
JaiaV said:
Lacking S-OFF doesn't help bring devs into a device.
Click to expand...
Click to collapse
But we could still flash roms... unless developers like to make their own radios and bootloaders... doubt it.
I am holding off because I would prefer to get full s-off rather than leave myself stuck with just HTC unlock.
rpernett said:
I am holding off because I would prefer to get full s-off rather than leave myself stuck with just HTC unlock.
Click to expand...
Click to collapse
k
10char
So the source code has been pushed to AOSP. How much of a help to our devs is that? BTW to me this is one of the greatest pieces of news ever!
http://www.droiddog.com/android-blog/2011/12/android-4-0-3-aosp-released/
What do ya'll think?
Same exact help as that last release.....
Sent from my PG86100 using Tapatalk
Why is it great? It doesn't do jack for the devs except set them back trying to implement new code.
Sent from my PG86100 using Tapatalk
novanosis85 said:
Same exact help as that last release.....
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
which of course means nothing to anyone since we don't even have a somewhat useful Alpha even, sucks i know.
dubach said:
So the source code has been pushed to AOSP. How much of a help to our devs is that? BTW to me this is one of the greatest pieces of news ever!
http://www.droiddog.com/android-blog/2011/12/android-4-0-3-aosp-released/
What do ya'll think?
Click to expand...
Click to collapse
How is this the greatest news ever if you don't even know what it means.
[email protected] said:
How is this the greatest news ever if you don't even know what it means.
Click to expand...
Click to collapse
read the actual google post. says it actually supports more then there own nexus line in 4.03.
doakills said:
read the actual google post. says it actually supports more then there own nexus line in 4.03.
Click to expand...
Click to collapse
You need way more than this to get ics on the evo 3d.
Sent from my HTC EVO 3D using xda premium
doakills said:
read the actual google post. says it actually supports more then there own nexus line in 4.03.
Click to expand...
Click to collapse
Read the OPs post. He asks how much help this is to our dev's meaning he has no clue what it means as far as getting ICS on the 3D and apparently you don't either.
NO its not.. yes. it is. No its not.. yes it is.
Stop fussing with your brothers or I'll turn this thread right around!
No need to bite his head off, he ASKED how much help it would be.
Unfortunately it means nothing for the speed to which ICS will get to the evo 3D or any other for that matter. The thing that is holding back its use and development isn't the availability of the source code of the OS or kernel. Each device needs drivers. In case anyone doesn't know exactly what that means; in the most basic and layman's terms drivers are the [low level] software for a device that "tells/instructs" the OS and other software how to interact with the hardware specific to that device. Each device needs its own drivers developed by the designer/manufacturer of the device. The drivers for the evo 3D needed to run ICS have either not been completed or have not been released. So this is the reason we are seeing alpha builds with non functioning hardware. Without the drivers it would be analogous to the evo 3D hardware speaking German, while ICS only speaks and understands English.
So unfortunately until we see drivers built and released, ICS won't fully function. Sorry! Good question though.
just wait
I know why this is such a big deal . I know it new but it will have sense skin on it . so only thing i want is the face unlock .lol
Sad Panda said:
No need to bite his head off, he ASKED how much help it would be.
Unfortunately it means nothing for the speed to which ICS will get to the evo 3D or any other for that matter. The thing that is holding back its use and development isn't the availability of the source code of the OS or kernel. Each device needs drivers. In case anyone doesn't know exactly what that means; in the most basic and layman's terms drivers are the [low level] software for a device that "tells/instructs" the OS and other software how to interact with the hardware specific to that device. Each device needs its own drivers developed by the designer/manufacturer of the device. The drivers for the evo 3D needed to run ICS have either not been completed or have not been released. So this is the reason we are seeing alpha builds with non functioning hardware. Without the drivers it would be analogous to the evo 3D hardware speaking German, while ICS only speaks and understands English.
So unfortunately until we see drivers built and released, ICS won't fully function. Sorry! Good question though.
Click to expand...
Click to collapse
Exactly. I don't know why people think we don't have kernel source...
Sent from my HTC Evo 3D
Listen up, please don't post useless comments. And if people do, don't flame them for 5 pages because of it!
I am not an expert, but this is what I have pieced together. I know this is rather long but this will roughly explain Kernels, S-Off, and why Development is lacking.
Here is the way I see community android development. There are themers, Rom chefs, kernel builders, and coders. Themers make most of the visual changes. Rom chefs take a little of everyones efforts and actually puts the Roms together. Kernel builders make the custom kernels for sense, aosp, and miui. The coders are the ones who really understand the code and make the complicated things work (S-off/Root Access/Incomplete drivers/new bootloaders/things like that). Now really everyone works together and there is some crossover in people's abilities but a community really needs all of these in order to fully develop.
Kernels/Drivers:
Think of it this way, the hardware talks to the drivers/kernel and the drivers/kernel talks to the Os. The drivers/kernels are like the translator between two different languages. The problem is that our current kernel made by Htc only knows how to translate from our hardware to Sense. We have to make custom kernels that can translate from our hardware to Aosp Gb, Aosp Ics, or Miui.
The problem:
Faux is extremely talented but here is what he has stated as the problem in making these custom kernels:
Amaze WiFi driver is a modified TI WiFi driver. The major problem is we don't know what HTC did to the WiFi driver for the Amaze.
Click to expand...
Click to collapse
Now I have talked to Htc and they said that they won't be releasing the full source code that includes the wifi drivers because of proprietary issues. My guess is that TI is the company that owns the original drivers and they don't want them released. Faux:
TI drivers are designed to work with OMAP Chipsets not Qualcomm chipsets, so HTC had to do some major hacks to make it work with Qualcomm chipset. It is NOT IMPOSSIBLE to reverse engineer what HTC did, it's very time consuming and tedious.
Click to expand...
Click to collapse
The Solution
I don't have a solution but that is what this thread is for. We need to brainstorm ideas to make this happen.
Here is a link to Htc Dev if you would like to bug them about it (though I'm not sure this would help)
http://htcdev.com/contact
The other solution is to focus on Coders that can reverse engineer the Wifi drivers. We don't need S-OFF yet! S-Off simply allows users to flash things like a kernel and radio directly to the phone through recovery. THAT IS ALL! It will not help bring Aosp faster! Here is Faux's opinion:
IMHO, S-Off at this stage does very little if at all at this moment. Having a working WiFi source is far more important and will increase development for Amaze than S-Off... S-On is just a minor annoyance...
Click to expand...
Click to collapse
I hope that this helps to clear up why development is so slow. We don't have anyone that wants to jump in and build the Wifi drivers so that Faux and Xboarder can make the Kernels for the Aosp Roms to run upon. Xboarder is still at work hacking and slashing at the code to get it working but I think we need someone with years of experience and knowledge to join the efforts. Xboarder is extremely talented but he isn't a code guru yet. Go to the forums of previous phones you have had and look around for people who have re engineered Lib files and phone drivers. Talk to some of the other Kernel builders to see if they are interested in building the driver. This is where we need to focus effort and money in order to stimulate development.
Wifi Driver
From Squish099:
@htcdev Amaze 4G needs missing wifi driver from /platform//hardware/ti/wlan/wl1283 and /wl1283_softAP. Both are missing from Amaze source.
Found it in an old tweet faux sent to htc just after thanksgiving.
Click to expand...
Click to collapse
craigtut said:
Listen up, please don't post useless comments. And if people do, don't flame them for 5 pages because of it!
I am not an expert, but this is what I have pieced together. I know this is rather long but this will roughly explain Kernels, S-Off, and why Development is lacking.
Here is the way I see community android development. There are themers, Rom chefs, kernel builders, and coders. Themers make most of the visual changes. Rom chefs take a little of everyones efforts and actually puts the Roms together. Kernel builders make the custom kernels for sense, aosp, and miui. The coders are the ones who really understand the code and make the complicated things work (S-off/Root Access/Incomplete drivers/new bootloaders/things like that). Now really everyone works together and there is some crossover in people's abilities but a community really needs all of these in order to fully develop.
Kernels/Drivers:
Think of it this way, the hardware talks to the drivers/kernel and the drivers/kernel talks to the Os. The drivers/kernels are like the translator between two different languages. The problem is that our current kernel made by Htc only knows how to translate from our hardware to Sense. We have to make custom kernels that can translate from our hardware to Aosp Gb, Aosp Ics, or Miui.
The problem:
Faux is extremely talented but here is what he has stated as the problem in making these custom kernels:
Now I have talked to Htc and they said that they won't be releasing the full source code because of proprietary issues. My guess is that TI is the company that owns the original drivers and they don't want them released. Faux:
The Solution
I don't have a solution but that is what this thread is for. We need to brainstorm ideas to make this happen.
Here is a link to Htc Dev if you would like to bug them about it (though I'm not sure this would help)
http://htcdev.com/contact
The other solution is to focus on Coders that can reverse engineer the Wifi drivers. We don't need S-OFF yet! S-Off simply allows users to flash things like a kernel and radio directly to the phone through recovery. THAT IS ALL! It will not help bring Aosp faster! Here is Faux's opinion:
I hope that this helps to clear up why development is so slow. We don't have anyone that wants to jump in and build the Wifi drivers so that Faux and Xboarder can make the Kernels for the Aosp Roms to run upon. Xboarder is still at work hacking and slashing at the code to get it working but I think we need someone with years of experience and knowledge to join the efforts. Xboarder is extremely talented but he isn't a code guru yet. Go to the forums of previous phones you have had and look around for people who have re engineered Lib files and phone drivers. Talk to some of the other Kernel builders to see if they are interested in building the driver. This is where we need to focus effort and money in order to stimulate development.
Click to expand...
Click to collapse
Good post lots of info, s-off really isn't that much of a big deal. Interesting. The WiFi drivers really are important sucks how HTC handled the amaze, I'm really hoping they're more open with the HTC one thanks for the info.
Sent from my HTC_Amaze_4G using xda premium
I was able to flash kernel through recovery?
Sent from my HTC_Amaze_4G using XDA
knifeproz said:
I was able to flash kernel through recovery?
Sent from my HTC_Amaze_4G using XDA
Click to expand...
Click to collapse
Uhh no...?
Sent from my NRGized Amaze...
via xda premium
HTC really messed up, and they call them self dev friendly,
same people that has got s-off on the sensation had tried to do for the amaze but they backed off,
but as you made a point s-off isnt really the problem here, the problem seems to be the drivers that htc wont realease
really the only person we have working hard on this device is Xboarder and binary100100 is doing what he can.
and he has done a really good job, and noobs had got on his nerves. We can not afford to lose him.
i really wish this phone have more developers working on getting things right, like that saying says two brains is better than one
i really love my phone but in the other hand i love roms. and as this phone its not a worldwide phone like the sensation i can understand the lack of developers
as you all know that the sensation have 40+ roms,themes,radios,kernerls,tweaks
sometimes i regret of getting rid of it, but specks says this is a better one,
had you guys ever though about asking for help on the android development forum? we might get lucky and find somebody that is willing to help.
but anyways thank you for saying it like it is and get us understand more of the situation, and me as i think all of you, would do anything to help..
I'm no dev, but i have done something
I HAVE PMED TWO KERNEL DEVELOPERS , TO LOOK INTO THIS THREAD TO GIVE A GLANCE , IF THEY CAN GIVE ANY INPUT ABOUT IT..
If there is any reply from them , i'll let the community know..
I think this is one of the important thread, we should probably have it in Development section and should be made sticky.
Mafioso said:
I think this is one of the important thread, we should probably have it in Development section and should be made sticky.
Click to expand...
Click to collapse
Lol good luck finding an active moderator to do anything in this Amaze forum besides handing out infractions. Binary bounced
Sent from my Energized HTC Ruby using XDA-Premium or Tapatalk
glacierguy said:
Lol good luck finding an active moderator to do anything in this Amaze forum besides handing out infractions. Binary bounced
Sent from my Energized HTC Ruby using XDA-Premium or Tapatalk
Click to expand...
Click to collapse
yeah, you will have more luck if you are looking for trolls flaming moderators indeed
Anyway,we cant stick everything in development, but i will see what i can do
Edit: oké, i will make a sticky collection thread.
So we will have less thread's sticked.
One or two sticked with all important info
This thread should be priority one in the Amaze forum.
Max Krivonos has Wifi working on his CM9 build for Amaze. Once he gets everything else working (which is limited to the rest of the radios, camera, and USB charge detection), I imagine the source will be released for use.
Accophox said:
Max Krivonos has Wifi working on his CM9 build for Amaze. Once he gets everything else working (which is limited to the rest of the radios, camera, and USB charge detection), I imagine the source will be released for use.
Click to expand...
Click to collapse
agreed. football usually drops a leak well ahead of the time ota goes live. either way, once we get the ics kernel, im rocking cm9 for good
mrmako777 said:
agreed. football usually drops a leak well ahead of the time ota goes live. either way, once we get the ics kernel, im rocking cm9 for good
Click to expand...
Click to collapse
Official ota will help but I don't think it will work for aosp. It will still only work with the sense until faux does some of his magic to it.
Sent from my HTC_Amaze_4G using XDA
Once cm9 comes out ill use it till aosp is out. I wasn't a huge fan of cm9 for hd2 but might change for this device!
Sent from my HTC_Amaze_4G using XDA
craigtut said:
Official ota will help but I don't think it will work for aosp. It will still only work with the sense until faux does some of his magic to it.
Sent from my HTC_Amaze_4G using XDA
Click to expand...
Click to collapse
dont quote me, but i think max said once he got a hold of the ics leak, he could use the wifi drivers from there...or something to that effect
he already have wifi working on cm9, but not calls, and he wont take any help. this once used to be a family in devs working together trying to get things right but now its just a race on who release it first, same thing happened on the sensation
gypsy214 said:
he already have wifi working on cm9, but not calls, and he wont take any help. this once used to be a family in devs working together trying to get things right but now its just a race on who release it first, same thing happened on the sensation
Click to expand...
Click to collapse
If I was a Dev I would take any help I could get =\
Sent from my HTC Amaze 4G using XDA
Xxxpachaxxx is a kernel developer for dhd..he is looking into it but he wants to know what is the driver number for HTC amaze ...
Can some1 pleease tell me what it is ASAP!!
Is it bcm4329 ?? Fast please
Sent from my HTC_Amaze_4G using xda premium
dullhunk said:
Xxxpachaxxx is a kernel developer for dhd..he is looking into it but he wants to know what is the driver number for HTC amaze ...
Can some1 pleease tell me what it is ASAP!!
Is it bcm4329 ?? Fast please
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
I don't know what it is but you could pm Faux123 for the info.
gypsy214 said:
he already have wifi working on cm9, but not calls, and he wont take any help. this once used to be a family in devs working together trying to get things right but now its just a race on who release it first, same thing happened on the sensation
Click to expand...
Click to collapse
He's working with a dozen other CM devs on MSM 8x60 devices. He just doesn't care for XDA. And with what this forum is turning into, I don't blame him.
Sent from my HTC Amaze 4G using xda premium
I'm genuinely curious if this big kernel source drop is going to be beneficial to us or not. I've heard two sides to the story:
1. "HTC b trollin' man, they drop source and release a new kernel..."
2. Devs can use the old kernel and fix the issues that HTC fixed, along with the other issues AOSP ROMs were having like sound and MMS.
I have no idea what's going on, and I'm curious whether I should expect things to blow up here soon, or if this kernel source has been essentially useless. I'm generally unaware of how long it takes devs to pick apart the kernel code and utilize it. Any input from those with knowledge on this topic would be greatly appreciated.
Sent from my EVO using xda app-developers app
PsiPhiDan said:
I'm genuinely curious if this big kernel source drop is going to be beneficial to us or not. I've heard two sides to the story:
1. "HTC b trollin' man, they drop source and release a new kernel..."
2. Devs can use the old kernel and fix the issues that HTC fixed, along with the other issues AOSP ROMs were having like sound and MMS.
I have no idea what's going on, and I'm curious whether I should expect things to blow up here soon, or if this kernel source has been essentially useless. I'm generally unaware of how long it takes devs to pick apart the kernel code and utilize it. Any input from those with knowledge on this topic would be greatly appreciated.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
+1
Both are correct. It doesn't really help sense based Roms because sense kernels are going to be newer than source.
However, aosp roms can now be fully functional. Aosp is what many people on here care about and are waiting for.
Sent from my EVO using Tapatalk 2
It's not useless for aosp, the problem is nobody is really working too much on aosp roms. There is a cm and MIUI port but they are a ways off and only so much one person can do..
Sent from my EVO using xda premium
Rippley05 said:
It's not useless for aosp, the problem is nobody is really working too much on aosp roms. There is a cm and MIUI port but they are a ways off and only so much one person can do..
Sent from my EVO using xda premium
Click to expand...
Click to collapse
This makes me sad. Maybe the EVO won't have the development I pictured it having after all. I'm not giving up hope for the future, but if you're correct in your assertion, that is saddening.
Sent from my EVO using xda app-developers app
PsiPhiDan said:
This makes me sad. Maybe the EVO won't have the development I pictured it having after all. I'm not giving up hope for the future, but if you're correct in your assertion, that is saddening.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
It still might, but I think I'm still somewhat jaded by the og evo and the support it had. The 3D never really had much, and it's looking like the lte is gonna be around the same.
I do think we'll eventually get some aosp goodness, just isn't hopping like I hoped it would be. I don't mean this as a slight to the devs we do have because they are great, all of them.
Sent from my EVO using xda premium
PsiPhiDan said:
This makes me sad. Maybe the EVO won't have the development I pictured it having after all. I'm not giving up hope for the future, but if you're correct in your assertion, that is saddening.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
It's only been a little over a month since the phone first came out. Give more people time to transition and we should start to see more activity. It isn't that bad so far, but most development is based around Sense because no one wants to wrestle with AOSP. Once they get AOSP stuff finished though, we'll be golden.
SoraX64 said:
It's only been a little over a month since the phone first came out. Give more people time to transition and we should start to see more activity. It isn't that bad so far, but most development is based around Sense because no one wants to wrestle with AOSP. Once they get AOSP stuff finished though, we'll be golden.
Click to expand...
Click to collapse
Yeah, I'm sure that's true. In my head, I figured everyone would be working to get to that point as quick as possible once kernel source was released. Like a giant team project, haha. Instead, it appears that only a select few are tackling it. Even custom kernels seem to be a rare mention. Oh well, I'll continue to enjoy the Sense ROMs as much as I can until someone cracks the AOSP code.
Sent from my EVO using xda app-developers app
PsiPhiDan said:
Yeah, I'm sure that's true. In my head, I figured everyone would be working to get to that point as quick as possible once kernel source was released. Like a giant team project, haha. Instead, it appears that only a select few are tackling it. Even custom kernels seem to be a rare mention. Oh well, I'll continue to enjoy the Sense ROMs as much as I can until someone cracks the AOSP code.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
We just need the support of the big guys. For some reason it feels like most of the big time devs haven't moved on to this phone yet, or went with Samsung instead. I know that Preludedrew is working on JB for our phone, I talked to him about it yesterday on Gtalk. Deck mentioned in IRC that he was working on it as well, I believe.
The kernel developers are hiding so far, probably because we don't have the big guys working for us yet. I'd love to see a Tiamat kernel, even if I'm personally not a fan of custom kernels.
Kernel.org is also down, so that's slowing things up for everyone.
Sent from my EVO using Tapatalk 2
Rxpert said:
Kernel.org is also down, so that's slowing things up for everyone.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
I've been seeing this all over, but I can access the site and perform downloads just fine.
There's is (are) custom kernels out
Sent from my EVO using Tapatalk 2
I'm actually happy with the stock kernel. It has a great balance of performance and battery life.Then again I prefer my kernels to be rock solid, as opposed to cutting edge with random reboots.
fpineda101 said:
I'm actually happy with the stock kernel. It has a great balance of performance and battery life.Then again I prefer my kernels to be rock solid, as opposed to cutting edge with random reboots.
Click to expand...
Click to collapse
I always used custom kernels with EVO 4G and remember zero reboots due to kernel issues . Easy overclocking and underclocking, volume mods, performance increases while still improving battery life... Yes please!
Sent from my EVO using xda app-developers app
PsiPhiDan said:
This makes me sad. Maybe the EVO won't have the development I pictured it having after all. I'm not giving up hope for the future, but if you're correct in your assertion, that is saddening.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
So far my experience with HTC phones have been a very disappointing one. Coming from the OG Epic, all I've kept hearing was how awesome the development for the OG EVO was. So of course when the EVO 3d came out it was my phone of choice over the Epic Touch. That was disappointment number one. Then when the LTE came out, I've noticed all the OG EVO developers and owners was all excited about this phone, so i decided to give HTC another chance. So for I've been more disappointed then at any point. The lack of ROMS, the pitifully performance of sense 4 and HTC's new stance on locking bootloader and sneaky updates with new Hboots was the last straw. What phone will I get next? Im not sure, but it won't be a HTC.
Sent from my disappointing EVO using xda premium
shook187 said:
So far my experience with HTC phones have been a very disappointing one. Coming from the OG Epic, all I've kept hearing was how awesome the development for the OG EVO was. So of course when the EVO 3d came out it was my phone of choice over the Epic Touch. That was disappointment number one. Then when the LTE came out, I've noticed all the OG EVO developers and owners was all excited about this phone, so i decided to give HTC another chance. So for I've been more disappointed then at any point. The lack of ROMS, the pitifully performance of sense 4 and HTC's new stance on locking bootloader and sneaky updates with new Hboots was the last straw. What phone will I get next? Im not sure, but it won't be a HTC.
Sent from my disappointing EVO using xda premium
Click to expand...
Click to collapse
We've had plenty of roms for this phone. Development has flown. Idk what your complaining about.
HTC has always locked the bootloader and always updated hboot to close root loopholes. This is nothing new.
This is all par for the course. You should know this having owned the 3d. Settle down my man
Sent from my EVO using Tapatalk 2
Rxpert said:
We've had plenty of roms for this phone. Development has flown. Idk what your complaining about.
HTC has always locked the bootloader and always updated hboot to close root loopholes. This is nothing new.
This is all par for the course. You should know this having owned the 3d. Settle down my man
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
I know what he means about ROMs... They're all more or less the same so far. Modified stock is great, but not what many are after when they think of development being great.
Sent from my EVO using xda app-developers app
Rxpert said:
We've had plenty of roms for this phone. Development has flown. Idk what your complaining about.
HTC has always locked the bootloader and always updated hboot to close root loopholes. This is nothing new.
This is all par for the course. You should know this having owned the 3d. Settle down my man
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
+1 on that. Seems like the other guy isn't to bright seeing as this phone is only a little over a month old
Sent from my EVO using Tapatalk 2
PsiPhiDan said:
I know what he means about ROMs... They're all more or less the same so far. Modified stock is great, but not what many are after when they think of development being great.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
And aosp is in the works and has been since shortly after launch. These things take time.
If you check out the aosp threads, they all mention ongoing development.
We JUST got kernel source. Devs have day jobs, they do this in their free time
Sent from my EVO using Tapatalk 2
Rxpert said:
And aosp is in the works and has been since shortly after launch. These things take time.
If you check out the aosp threads, they all mention ongoing development.
We JUST got kernel source. Devs have day jobs, they do this in their free time
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Oh I know that, and I no way meant to say the devs aren't doing great work. I just wanted to explain why he said there were not a lot of ROMs right now. I understand that statement, although there is plenty of reason for why that is.
Sent from my EVO using xda app-developers app
http://htcdev.com/devcenter/downloads
Swagnificent.
Sent from my EVO using Tapatalk 2
HTC must be getting ready to release an update lol
from my flying AOKP'd Evo LTE and xda premium
Hopefully Jelly Bean will be the next update
scottspa74 said:
HTC must be getting ready to release an update lol
from my flying AOKP'd Evo LTE and xda premium
Click to expand...
Click to collapse
There is a rumor that a one x (international?) Jelly Bean update is coming in a few months, hopefully the next evo update doesn't lag behind
scottspa74 said:
HTC must be getting ready to release an update lol
from my flying AOKP'd Evo LTE and xda premium
Click to expand...
Click to collapse
LOL, I think you've got the trend down.
Forgive my ignorance, but does this increase the chance of devs identifying a 1.15 Hboot vulnerability, or is Hboot not relevant to this source code?
holy tooth decay batman!!!!!!! wo0t woot!!! :highfive:
ElMadre said:
Forgive my ignorance, but does this increase the chance of devs identifying a 1.15 Hboot vulnerability, or is Hboot not relevant to this source code?
Click to expand...
Click to collapse
I'm no expert, but am fairly certain the hboot is proprietary and will never be shared.
Hope they fix the LTE connection issues in this update. Comparing it to the S3 side by side the EVO is a joke for LTE usage.
ElMadre said:
Forgive my ignorance, but does this increase the chance of devs identifying a 1.15 Hboot vulnerability, or is Hboot not relevant to this source code?
Click to expand...
Click to collapse
No this is used for making kernels for overclocking and other tweaks. The hboot will be strickly the work of our wonderful devs as HTC does not want us to be soff.
Sent from my EVO using xda premium
Well this is definitely a nice surprise
1 month almost to the day after the OTA.... ehh let's improve that a lil more HTC...
Sent from my Wolfpack EVO
Has anyone looked at the source? I thought the last kernel source release was pretty useless
Sent from my EVO using Tapatalk 2
If i remember correctly, the wifi part of the kernel was not included in prior releases. Somebody who knows better/more please chime in, im always happy 2 learn more
Sent from my EVO using xda premium
hopefully someone can get my otg cable to work now
jspsuperman said:
If i remember correctly, the wifi part of the kernel was not included in prior releases. Somebody who knows better/more please chime in, im always happy 2 learn more
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Prima_wlan source is not included.
ca1ne said:
Prima_wlan source is not included.
Click to expand...
Click to collapse
It's OK (GPL? For HTC to release source kernel code and omit the WiFi code?
from my flying AOKP'd Evo LTE and xda premium
scottspa74 said:
It's OK (GPL? For HTC to release source kernel code and omit the WiFi code?
from my flying AOKP'd Evo LTE and xda premium
Click to expand...
Click to collapse
I pmed the htc guy from the other thread asking about that. Waiting on a reply.
The jist is this.
Ask htc they say contact Qualcomm because it's propriety.
Ask Qualcomm and they say contact htc because they released the kernel source.
ca1ne said:
I pmed the htc guy from the other thread asking about that. Waiting on a reply.
The jist is this.
Ask htc they say contact Qualcomm because it's propriety.
Ask Qualcomm and they say contact htc because they released the kernel source.
Click to expand...
Click to collapse
If its proprietary stuff by Qualcomm then HTC can't release it... Just bc its in the kernel doesn't mean it has to have full source to that exact part... There are ways to still secure proprietary things and include them in kernel for open source items... It'd be interested to see if this is the case..
I would think by now someone over on CAF woulda figured this out for sure by now though...
Anyway hopefully Jeff can get something for ya that will help or least give an answer on the reasoning why...
Sent from my Wolfpack EVO