4.0.3 AOSP release - HTC EVO 3D

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

Related

HTC Releases Kernel Source For A Slew Of Devices

http://www.androidpolice.com/2011/1...sation-jetstream-and-a-slew-of-other-devices/
What impact will this have on the EVO 3D development community? Does this have anything to do with drivers for the WiMax and 3D systems? (I have limited knowledge of how Android is structured, so I have no clue.)
Wow they released the rezound code already! Phone not even out for a week and they have kernel source. HTC must be learning. Too bad that phone ships locked up tight and even if unlocked it'll likely still be s-on and done via HTC method.
I just hope HTC makes a fully unlock in future and not this flash kernels via fastboot crap they have now.
Sorry to derail ur thread but Ima say they won't help too much. Diff phones have diff drivers completely because hardware is diff.
Sent from my PG86100 using XDA App
So what good can/will come from this move?
Isn't not having the kernel the excuse we've been getting as far as not having a true AOSP rom?
ummduh said:
Isn't not having the kernel the excuse we've been getting as far as not having a true AOSP rom?
Click to expand...
Click to collapse
No. We have our kernel source and had it for awhile
Sent from my PG86100 using XDA App

[Q] Is there a specific reason development for MoPho has been so slow?

I'm just wondering why the development community for the Photon has been so slow. I am not complaining, and am extremely greatful for everyone's work on the projects that keep us modders happy. I'm simply curioius as to whether or not there's a specific issue (an unreleased SDK, just a difficult phone to develop for, etc) as there have been several phones that have come out since the MoPho and already have more roms/kernals/etc. Again, this is simply out of curiosity. Thank you for any answers that you guys can provide.
Ive asked the same thing for a long time i still dont get it
It's the working mans phone, plus its not plagued with issues
Sent from my MB855 using XDA App
I'm just glad we have come this far...
Slow?.... we have miui and cm7 with jokers skinny rom and even sockmonkey....over 10+ oc/uv gpu enhanced kernels up to 1.5giggityhurtz ....
Only other thing I can see being modded is our pos pentile screen.....
Every optimized or enhanced android setting I come across that seem possible to port to our kernels/roms I send it jokers way cause he knows best if its worth a look or not.
So any suggestions that adds to our current awsomeness..by all means say so....
Sent from my MB855 using XDA App
A working unlocked bootloader for 2.3.5
Custodian said:
Slow?.... we have miui and cm7 with jokers skinny rom and even sockmonkey....over 10+ oc/uv gpu enhanced kernels up to 1.5giggityhurtz ....
Only other thing I can see being modded is our pos pentile screen.....
Every optimized or enhanced android setting I come across that seem possible to port to our kernels/roms I send it jokers way cause he knows best if its worth a look or not.
So any suggestions that adds to our current awsomeness..by all means say so....
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
Are those not still in Alpha phase though? Maybe I'm just nitpicking, but I was talking about full releases. However, I could be just not looking hard enough or am looking over the obvious, which with me, is entirely possible.
Well considering everything software wise should be considered beta(perfect software will never happen). Im pretty sure my stuff is safe. When i release a kernel, i upload from that kernel. I cant guarantee no bugs because not even stock isnt without bugs. I use alpha to scare away people that will brand all my stuff crap. Once a kernel goes stable its the same kernel just tested by more than just me.
Evilsj said:
Are those not still in Alpha phase though? Maybe I'm just nitpicking, but I was talking about full releases. However, I could be just not looking hard enough or am looking over the obvious, which with me, is entirely possible.
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
Evilsj said:
Are those not still in Alpha phase though? Maybe I'm just nitpicking, but I was talking about full releases. However, I could be just not looking hard enough or am looking over the obvious, which with me, is entirely possible.
Click to expand...
Click to collapse
Although listed as alpha, they work very well. Give them a try.
Sent from my MB855 using Tapatalk
I'm using MIUI alpha and is pretty solid. Has its share of bugs but very promising.
Sent from my MB855 using Tapatalk
I wish I knew the answer to this as well. In fact, I asked the exact same question about a month ago and all I was told was that it's due to poor marketing by Sprint?
http://forum.xda-developers.com/showthread.php?t=1345073
All I ever hear from everyone is how much of a kickass phone this is, which I totally agree with. You would think that for a phone with such a solid platform to work off of, the development would be insane. Unfortunately, it's just the opposite.
i have to agree with jay
ferretman61 said:
i have to agree with jay
Click to expand...
Click to collapse
Have you done any development for it? No? That's why it's slow.
Sent from my Motorola using Tapatalk
Go home troll
ferretman61 said:
i have to agree with jay
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
Instead of asking why there isn't enough development, why not state specifics on what you are looking for that is missing?
Sent from my Photon 4G using Tapatalk
honestly no offence to you but this can be pretty insulting to our developers who are highly skilled and working all their free time into getting this going, talk to Motorola for locking the bootloader and not releasing they're kernel if u want to make things faster and easier for the developers.
Sent from my MB855 using xda premium
Not too many developers have this device. If this device was on Verizon, we would have development up our a**es, but Sprint is not too popular of a service provider for Android developers, other than the Samsung Galaxy Epic Touch...
deedscreen said:
Not too many developers have this device. If this device was on Verizon, we would have development up our a**es, but Sprint is not too popular of a service provider for Android developers, other than the Samsung Galaxy Epic Touch...
Click to expand...
Click to collapse
I don't think this is entirely true. I came from the Evo 4G, and development/roms were plentiful from the dev community for that phone.
While it is a bit disconcerting to see the lack of development for my new Photon, it is important to remember that developers do this on their own time. However, as others have said, this device is far and above, even with Motoblur (which is awful, btw), what most other devices have to offer. There are, obviously, some other highly spec'd Sprint phones, like the SGSII, Evo3d, and the Nexus S 4G. And with the now impending release of the new Nexus on Sprint, I would assume development for the MoPho will likely drop altogether.
All that said, I do wish I had a stable AOSP ROM to put on this phone, with a nice guide on the most up-to-date rooting method(s). I only got this phone yesterday, so it'll be a few hours of fishing through hundreds of pages of forums before I'm ready to start rooting (I'm on 2.3.4)...my concern is what to put on my phone AFTER I'm rooted. :-(
Anyways -- thanks to all the devs that have put something together for us. Joker, it seems that your stuff is at the forefront, while some people are apparently still using the CM7 build from Cybik. Maybe I'll try it all!
Just to give a little perspective regarding software, when the company I work for goes to update an existing device with new code it takes a fair amount of full time software developers and testers (at least 3 or 4 of each) and a couple of months to get something out in a fairly stable state when they are familiar with the code that are updating.
What the developers here are doing is makes updates to code they did not create or develop and lord knows if there is one thing developers hate to do is comment code. So it makes it even more difficult for anyone to first understand what the code is doing in order to make that changes let alone someone who has a separate full time job.
I know your not complaining about the slowness, only asking why so I thought I would give me 2 cents.
Yeah jokers cm9 is running great! You should try it out. The only reason not to use it is the camera doesn't work so if that is important to you just wait. I barely use the camera so doesn't bother me.

Not S-Off, Coders for Wifi Drivers!

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

Key Lime Pie for 3vo general chat

if ? but ? when ? not possible ? am i dreaming ? lol
this is just for general chat for now
anyone know more than someone else share it here
whats peoples views so far ?
gav-collins1983 said:
if ? but ? when ? not possible ? am i dreaming ? lol
this is just for general chat for now
anyone know more than someone else share it here
whats peoples views so far ?
Click to expand...
Click to collapse
I know it isn't out yet, no release date announced, and most likely won't make it to our evo. Is there really a point for this? Stop acting like a kid a few days before Christmas. Only difference is, Christmas you typically get what you wanted.
We don't even have jelly bean except for a few roms. They work well, but aren't perfect. It's almost a year after jb and we just got it and bugs aren't worked out yet. Plus, a lot of developers have moved on. Contracts are getting close to up for a lot of early adopters and they, like myself, will likely move on too. We may only have a couple of devs left here by the time klp drops.
Sorry to be a downer, but we haven't been the thriving community we once were and htc seems to have abandoned us.
Sent from my Nexus 7 using xda app-developers app
So true so true. The evo 3d had a lot of potential and a great Dev community. As far as HTC was concerned, they care more about money than the consumer so its not surprising they dropped the evo 3d to work on another mid range device. Hardly worth the need to upgrade with very few spec upgrades. Evo 4g lte will probably abandoned sometime this year for a quad core 2gb ram device. Most carriers don't have lte set up everywhere where anybody can take advantage of it. It will be a miracle if HTC pushes a jb update to the evo 3d. If it did. You can guarantee that key lime pie will never see evo 3d
gav-collins1983 said:
if ? but ? when ? not possible ? am i dreaming ? lol
Click to expand...
Click to collapse
Are you asking about a port of an AOSP based ROM or a Sense based release from HTC? If it's the former, there's a slim chance if all the developers haven't moved on to other devices by the time KLP is released, but there is zero chance of an official Sense based version.
ramjet73
ramjet73 said:
Are you asking about a port of an AOSP based ROM or a Sense based release from HTC? If it's the former, there's a slim chance if all the developers haven't moved on to other devices by the time KLP is released, but there is zero chance of an official Sense based version.
ramjet73
Click to expand...
Click to collapse
Actually even that won't be possible unless we can get our kernels to work with ION memory allocation. ION is a requirement for 4.1.2+, we were able to get 4.1.2 working by using hacks to use old code and 4.2.1 by using legacy code (same hacks, but much harder to implement).
dastin1015 said:
Actually even that won't be possible unless we can get our kernels to work with ION memory allocation. ION is a requirement for 4.1.2+, we were able to get 4.1.2 working by using hacks to use old code and 4.2.1 by using legacy code (same hacks, but much harder to implement).
Click to expand...
Click to collapse
So 4.2.2 will probably be the last hooray for our device?
"Much Ado About Nothing"...lol
Sent from my Evo 3D GSM using xda premium
If you want KLP, go buy a Gnex, I agree with all before me, KLP and E3D are not gonna happen
Sent from my PG86100 using xda app-developers app
dastin1015 said:
Actually even that won't be possible unless we can get our kernels to work with ION memory allocation. ION is a requirement for 4.1.2+, we were able to get 4.1.2 working by using hacks to use old code and 4.2.1 by using legacy code (same hacks, but much harder to implement).
Click to expand...
Click to collapse
wasn't ION memory allocation introduced in android 4.0? so shouldn't the stock HTC kernel support it? if not, what is the problem with getting it working?
Kiinasu said:
wasn't ION memory allocation introduced in android 4.0? so shouldn't the stock HTC kernel support it? if not, what is the problem with getting it working?
Click to expand...
Click to collapse
Here's a post from dastin1015 that explains it in more detail.
ramjet73
well we got the villec2 kernel source + the evo kernel source. can't we just port a part of the ION memory allocation from the one s to the evo?
R: Key Lime Pie for 3vo general chat
Kiinasu said:
well we got the villec2 kernel source + the evo kernel source. can't we just port a part of the ION memory allocation from the one s to the evo?
Click to expand...
Click to collapse
Dastin said that's a very difficult task
Inviato dal mio Evo 3D GSM
Kiinasu said:
well we got the villec2 kernel source + the evo kernel source. can't we just port a part of the ION memory allocation from the one s to the evo?
Click to expand...
Click to collapse
You still have to properly calculate the memory allocation. msm8660 actually has to use the frame buffer of an msm8960 device. The panel and board config files need to be changed to use the new frame buffer and memory allocation. The camera drivers also have to be changed to use ION and a common-ish camera driver. Not a simple port.
私のEVO 4G LTEから送信される。
You don't have to keep re-explaining yourself brother as to the reason why. People should just learn how to search better.
dastin1015 said:
You still have to properly calculate the memory allocation. msm8660 actually has to use the frame buffer of an msm8960 device. The panel and board config files need to be changed to use the new frame buffer and memory allocation. The camera drivers also have to be changed to use ION and a common-ish camera driver. Not a simple port.
私のEVO 4G LTEから送信される。
Click to expand...
Click to collapse
Dafuq did i just read
Sent from my Evo 3D GSM
dastin1015 said:
You still have to properly calculate the memory allocation. msm8660 actually has to use the frame buffer of an msm8960 device. The panel and board config files need to be changed to use the new frame buffer and memory allocation. The camera drivers also have to be changed to use ION and a common-ish camera driver. Not a simple port.
Click to expand...
Click to collapse
thanks for your answer. i started to realize the problem. sometimes i just forget how much depends on little devices differences. think the interest for devs on this device, will be to low, once klp comes out, to make this happen....
oohaylima said:
You don't have to keep re-explaining yourself brother as to the reason why. People should just learn how to search better.
Click to expand...
Click to collapse
well if he would be super annoyed, i think he wouldn't answer. and it's extremely hard to find real information about hardware things.
ognimnella said:
If you want KLP, go buy a Gnex, I agree with all before me, KLP and E3D are not gonna happen
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
What makes you sure gnex will get klp?
Sent from my Xoom using xda premium
Lothaen said:
What makes you sure gnex will get klp?
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
Nexus devices always get the latest and greatest because they r pure Google android devices. They rolled out JB for the nexus s and it is older (and less spec savvy IMO) than the Evo 3D. Whether or not SAMSUNG chooses to update, GOOGLE will, I'm sure the gnex is slighted for next two OS versions at the least, because it can with ICS and 4.1 and 4.2 were released so quickly that it really can't be seen as 2 MAJOR updates, just my take
Sent from my Evo 3D CDMA using xda app-developers app
ognimnella said:
Nexus devices always get the latest and greatest because they r pure Google android devices. They rolled out JB for the nexus s and it is older (and less spec savvy IMO) than the Evo 3D. Whether or not SAMSUNG chooses to update, GOOGLE will, I'm sure the gnex is slighted for next two OS versions at the least, because it can with ICS and 4.1 and 4.2 were released so quickly that it really can't be seen as 2 MAJOR updates, just my take
Sent from my Evo 3D CDMA using xda app-developers app
Click to expand...
Click to collapse
The carriers do control you though. The Verizon Galaxy Nexus is in testers phase now for 4.2.2 meaning it's preparing for an OTA, while the rest of the GNEX devices have been updated.
私のEVO 4G LTEから送信される。
ognimnella said:
Nexus devices always get the latest and greatest because they r pure Google android devices. They rolled out JB for the nexus s and it is older (and less spec savvy IMO) than the Evo 3D. Whether or not SAMSUNG chooses to update, GOOGLE will, I'm sure the gnex is slighted for next two OS versions at the least, because it can with ICS and 4.1 and 4.2 were released so quickly that it really can't be seen as 2 MAJOR updates, just my take
Sent from my Evo 3D CDMA using xda app-developers app
Click to expand...
Click to collapse
Nexus S only got 4.1. No official 4.2 update.
Sent from my Nexus 4 using xda premium

[Q] I don't get it: Fixed 3D ?

So it seems there is that Chinese Rom with Sense 4.1 and working 3D, this is amazing, however, it is the only one of it's type.
The fact that HTC did not release the Driver Sources made me somehow hate them and it was the reason why many bugy couldnt be fixed, many devs left.
So, this Chinese Rom is removed because it is not allowed according to the rules, but... why exactly?
Could someone please post information on this story, really, this is EXTREMELY important, it could change our 3volife
Is it because it's a Viper fix, why then don't they release the fix?
So, the simple question is:
What's the fuzz about the 3D-fix? Somehow no one knows whats going on!
I'm gonna make it as brief as possible.
We can't release it on XDA or link to it because it is considered kang. The ROM is based off of a Viper3D build and was used without permission. Now unless Team Venom gives us permission to release their ROM with working 3D here on XDA, we can't do it because then that's kanging someone else's work, and that's highly frowned upon here, and leads to heavy infractions
Sent from my Nexus S 4G using Tapatalk 2
I can not understand how is it possible that only one team is capable to make 3D work. Why can not someone else make it from the basis without their rom?
B3!CrAZy said:
I can not understand how is it possible that only one team is capable to make 3D work. Why can not someone else make it from the basis without their rom?
Click to expand...
Click to collapse
I am pretty sure coolexe or anryl or mwakious could do it if they have time
Somebody could definitely do it, but it would be a very hard thing to do since HTC doesn't hand out their 3D drivers. That team who got it working guaranteed was working for weeks and weeks on end getting it working, somebody here could do it for sure, but nobody has tried yet, and its probably something that's more trouble than its worth. Even if we looked at what that team did to get it working we can't use any of that, or even copy any of that because then it would still be kanging their work. Its something we either A) need to get permission for or B) take care of ourselves, but have that be 10000x harder. Its not impossible, but it is improbable
Sent from my Nexus S 4G using Tapatalk 2
This is ridiculous in my opinion.
I'll probably get flamed but the whole purpose of android being open source is so anyone and everyone can contribute and make it a better experience.
I understand the HTC drivers are proprietary, but in my eyes, if you've made something better why not share it with the world...are these 'team' members making money on these fixes, are they coming out with their own proprietary phones...that's the only reason I can see to necessitate keeping these fixes to yourself...yes I applaud any ROM dev for their work (I sure as hell couldn't do what they do) but what's the point in the end? Bragging rights? Come on!
Sent from my HTC Evo V 4G using xda app-developers app
hossman said:
This is ridiculous in my opinion.
I'll probably get flamed but the whole purpose of android being open source is so anyone and everyone can contribute and make it a better experience.
I understand the HTC drivers are proprietary, but in my eyes, if you've made something better why not share it with the world...are these 'team' members making money on these fixes, are they coming out with their own proprietary phones...that's the only reason I can see to necessitate keeping these fixes to yourself...yes I applaud any ROM dev for their work (I sure as hell couldn't do what they do) but what's the point in the end? Bragging rights? Come on!
Sent from my HTC Evo V 4G using xda app-developers app
Click to expand...
Click to collapse
Amen to that
Sent from my LG-MS770 using Tapatalk 2
kajoshin201095 said:
So it seems there is that Chinese Rom with Sense 4.1 and working 3D, this is amazing, however, it is the only one of it's type.
The fact that HTC did not release the Driver Sources made me somehow hate them and it was the reason why many bugy couldnt be fixed, many devs left.
So, this Chinese Rom is removed because it is not allowed according to the rules, but... why exactly?
Could someone please post information on this story, really, this is EXTREMELY important, it could change our 3volife
Is it because it's a Viper fix, why then don't they release the fix?
So, the simple question is:
What's the fuzz about the 3D-fix? Somehow no one knows whats going on!
Click to expand...
Click to collapse
Android is open source, you changed is the exclusive copyright? This is not unreasonable.
If anyone need help, you can email me
The rules centered around this are not android related. It has nothing to do with open source, they're xda's rules. It makes sense why they're there (that way we don't see the same exact ROM under a different name pop up every 20 minutes, etc.). I don't like the rule either but hey, its just something we gotta live with
Sent from my Nexus S 4G using Tapatalk 2
I think that we could do an exception for 3D in 4.1 sense...
http://www.android-hilfe.de/custom-...1-0-0-full-3d-beats-audio-high-quality-3.html
elitman said:
http://www.android-hilfe.de/custom-...1-0-0-full-3d-beats-audio-high-quality-3.html
Click to expand...
Click to collapse
CDMA????
SketchyStunts said:
CDMA????
Click to expand...
Click to collapse
it is a german forum. So it is probably GSM. I gonna try it now. (With my GSM-device)
Gonna be quite honest, hit up that link while you can because it ain't gonna be there for long
SketchyStunts said:
CDMA????
Click to expand...
Click to collapse
GSM - working like a charm. Using the 2.0 version. Aroma is in Germany but pretty understandable.
Sent from my shooteru using xda app-developers app
Sieht gut aus, heruntergeladen! I'll probably tear the rom apart and see about making it CDMA worthy, though I won't be able to share it once I'm done being it's Kang'ed...
elitman said:
GSM - working like a charm. Using the 2.0 version. Aroma is in Germany but pretty understandable.
Sent from my shooteru using xda app-developers app
Click to expand...
Click to collapse
Is Sense scroll lagging for you?
I'm asking this coz had no problems at all with the original chinese ROM, but after flashing this one got lags during Sense pages scrolling
thesniffer said:
Is Sense scroll lagging for you?
I'm asking this coz had no problems at all with the original chinese ROM, but after flashing this one got lags during Sense pages scrolling
Click to expand...
Click to collapse
No lags at all. What I experienced was huge battery drain. So, right now, I oam in the process of reverting back to stock ROM. Tired of all these tests. Gonna get SIII tomorrow anyway
So we have fixed 3D camera now? ICS or JB?
Don't seem to see a straight answer. Only that it is using venom tweaks without perms..?
Sent from my N7100 using xda premium
Lothaen said:
So we have fixed 3D camera now? ICS or JB?
Don't seem to see a straight answer. Only that it is using venom tweaks without perms..?
Sent from my N7100 using xda premium
Click to expand...
Click to collapse
Well, we do have full 3D working on a ICS Sense 4.1 ROM

Categories

Resources