Related
Someone please correct me if I am wrong but please don't flame me.
Other than UI features, will there be any benefit to an ICS ROM made from source? Won't we still have to use a gingerbread kernel? From what I understand, there will be zero performance gain from it until we get a kernel source from HTC. Am I wrong in thinking that? Or will someone be able to make an ICS kernel for it when the source for ICS drops?
The reason I ask is because the most exciting thing to me about ICS is the hardware acceleration.
Sent by my Supercharged dual core from the 3rd Dimension
I remember reading somewhere that ICS is supposed to take advantage of the dual core power of cell phones. Not 100% sure but I want ICS because of the looks and the UI
Sent from my PG86100 using Tapatalk
We have HTC kernel source its just not fully complete (unfortunately) but toastcfh was able to tweak it to work. The only reason you see custom kernels is because of source. ICS does impelement the first mobile Linux 3.0 kernel. Once ICS source drops, one of the first things to do is merge our kernel source with the new 3.0 kernel and then go from there. Not only will ICS have full 2D acceleration throughout the entire UI the new kernel should bring a few benefits at the least just slight overall improvements. Although it will be interesting to see how large the new AOSP roms will end up being. Google has specifically said that ICS will a bit on the heavy side and even ruled out a nexus one upgrade due to out-of-date hardware. Our HTC shooter's will definitely be just fine but just a thought. To answer your question though yes, expect major UI improvements and "under-the-hood" speed improvements. Due to the nature of open source we will be able to take advantage almost every enhancement ICS brings.
Sent from my PG86100 using xda premium
bballer71418 said:
We have HTC kernel source its just not fully complete (unfortunately) but toastcfh was able to tweak it to work. The only reason you see custom kernels is because of source. ICS does impelement the first mobile Linux 3.0 kernel. Once ICS source drops, one of the first things to do is merge our kernel source with the new 3.0 kernel and then go from there. Not only will ICS have full 2D acceleration throughout the entire UI the new kernel should bring a few benefits at the least just slight overall improvements. Although it will be interesting to see how large the new AOSP roms will end up being. Google has specifically said that ICS will a bit on the heavy side and even ruled out a nexus one upgrade due to out-of-date hardware. Our HTC shooter's will definitely be just fine but just a thought. To answer your question though yes, expect major UI improvements and "under-the-hood" speed improvements. Due to the nature of open source we will be able to take advantage almost every enhancement ICS brings.
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Toast has a isc kernel?
Sent from my PG86100 using Tapatalk
bballer71418 said:
We have HTC kernel source its just not fully complete (unfortunately) but toastcfh was able to tweak it to work. The only reason you see custom kernels is because of source. ICS does impelement the first mobile Linux 3.0 kernel. Once ICS source drops, one of the first things to do is merge our kernel source with the new 3.0 kernel and then go from there. Not only will ICS have full 2D acceleration throughout the entire UI the new kernel should bring a few benefits at the least just slight overall improvements. Although it will be interesting to see how large the new AOSP roms will end up being. Google has specifically said that ICS will a bit on the heavy side and even ruled out a nexus one upgrade due to out-of-date hardware. Our HTC shooter's will definitely be just fine but just a thought. To answer your question though yes, expect major UI improvements and "under-the-hood" speed improvements. Due to the nature of open source we will be able to take advantage almost every enhancement ICS brings.
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
I understand what you are saying. The biggest thing I was wondering is, will we have a true ICS kernel as soon as ICS source drops. I think I remember some phones having to use froyo kernels with gingerbread ROMs. I could be wrong but I think that's right.
Sent by my Supercharged dual core from the 3rd Dimension
Even if the kernel source isnt released yet, its gonna take months for a full working ics aosp rom. UI improvements, the UI is a huge improvement. Seems like android was rebuilt to me. Hardware improvements. Its worth it.
Temari x Shikamaru
novanosis85 said:
Toast has a isc kernel?
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Toast has an AOSP kernel. Once the ICS source gets dropped (which includes kernel source) toast and others will merge our drivers and such with the new AOSP Linux 3.0 kernel
Sent from my PG86100 using xda premium
lyon21 said:
I understand what you are saying. The biggest thing I was wondering is, will we have a true ICS kernel as soon as ICS source drops. I think I remember some phones having to use froyo kernels with gingerbread ROMs. I could be wrong but I think that's right.
Sent by my Supercharged dual core from the 3rd Dimension
Click to expand...
Click to collapse
I think I remember what you are talking about with og Evo. The kernel source only gives us libs and drivers and such that we modify to be able to use AOSP roms. Once the EVO 3D officially gets ICS the process of making custom kernels becomes a bit easier but will not necessarily improve performance. Idk if you had an og Evo but toastcfh as well as others from savaged-zen had a functional Linux 2.8 kernel while all stock android kernels were on 2.5 & 2.6. Once we get any kind of source at all we can get a Linux 3.0 ICS kernel with all of the new benifits it entails. Completed (which we don't really have) or updated source just makes the process easier
Sent from my PG86100 using xda premium
thanks everyone, esp OP, for creating a good read and a productive thread in the General section. these are becoming a rarity!
No1ustad said:
thanks everyone, esp OP, for creating a good read and a productive thread in the General section. these are becoming a rarity!
Click to expand...
Click to collapse
That they are, but it was actually a question so it should have gone in the Q/A thread....
tgruendler said:
That they are, but it was actually a question so it should have gone in the Q/A thread....
Click to expand...
Click to collapse
I understand it should have gone in Q&A but I personally never look in there and figured that was the same for many people here. Figured something like this should be in general, where a lot of people would see it and answer the question or enjoy reading the answers. With all of the bull crap posted in the general section lately, thought it would be a nice change to have something that many people would be interested in. Thought people would rather see this here than another SGSII vs 3D thread, or some other bull****. If I am wrong, mods feel free to move it but I think most people will agree.
Sent by my Supercharged dual core from the 3rd Dimension
lyon21 said:
I understand it should have gone in Q&A but I personally never look in there and figured that was the same for many people here. Figured something like this should be in general, where a lot of people would see it and answer the question or enjoy reading the answers. With all of the bull crap posted in the general section lately, thought it would be a nice change to have something that many people would be interested in. Thought people would rather see this here than another SGSII vs 3D thread, or some other bull****. If I am wrong, mods feel free to move it but I think most people will agree.
Sent by my Supercharged dual core from the 3rd Dimension
Click to expand...
Click to collapse
Man...I should just put (sarcasm) at the end of my posts instead of the winking smiley guy.
tgruendler said:
That they are, but it was actually a question so it should have gone in the Q/A thread....
Click to expand...
Click to collapse
Q/A section seems to be more for technical help and advice help. Trivial questions that require conversing and the spread of general knowledge of the topic seem reasonable in the general section, imho.
tgruendler said:
Man...I should just put (sarcasm) at the end of my posts instead of the winking smiley guy.
Click to expand...
Click to collapse
I wasn't being a **** about it. I was just explaining why I didn't put it in the Q&A section. Hope it wasn't taken that way.
Sent by my Supercharged dual core from the 3rd Dimension
Thought we'd have a thread here for mainly Dev's so we can communicate in one section with the already isolated sections.
Well, I'll start off first:
Does anyone have luck on the following?
- Creating AOSP kernel (GB base)
^ 2.6.35 source is out on htcdev, but kernels are not my expertise. I contacted cayniarb to see if he'd be willing to make one for us.
- Building any AOSP roms? GB/ICS hacks
^ Been trying CyanogenMod 7 unsuccessfully for a few days.
I don't think it's impossible, however given several tries at compiling. Resulting zips just don't boot, probably bootimage/kernel related... Think I have got all the proprietaries pulled and needed files set up by mostly mimicking other MSM8655 builds.
- Direct porting flyer roms to express
^ Something I may try soon if I can't get any progress done on my end. This is probably not very hard, but looking at the Flyer choices there doesn't seem to be a whole lot we are missing out completely on.
kaijura said:
- Direct porting flyer roms to express
^ Something I may try soon if I can't get any progress done on my end. This is probably not very hard, but looking at the Flyer choices there doesn't seem to be a whole lot we are missing out completely on.
Click to expand...
Click to collapse
I can vouch for this; using any Flyer ROM with the View kernel that matches the version of Android (i.e. GB or HC) WILL work on the View. Namely, LeeDroid's GB ROM with the OC View GB kernel. Although, using the Flyer kernel will cause a bootloop :\
The only thing we are missing out on is an optimized kernel. We wouldn't even need Flyer ports with a "proper" View kernel
I am more interested in getting ICS working right now. I'm working on the final build of CypherROM and from there working on themes and a kernel. My team has been trying to build a kernel based off of leedroid's work for some time, but haven't had any luck.
It looks like a dev just made an alpha AOSP kernel for the flyer, which we can't use of course (for the newbs reading):
http://forum.xda-developers.com/showpost.php?p=22955319&postcount=103
kaijura said:
It looks like a dev just made an alpha AOSP kernel for the flyer, which we can't use of course (for the newbs reading):
http://forum.xda-developers.com/showpost.php?p=22955319&postcount=103
Click to expand...
Click to collapse
The biggest problem is the WiMAX. Doing some research it looks as though we might be able to use HTC "speedy" aosp kernel source. Same processors and gpu. Just need to get a hold of kernel source and comparing def_configs. I have done nothing but kinda look into it. I have built the device folders too. But I knew the kernel was the issue so I wasn't going to compile. And once we get an aosp kernel we can also get a decently functional touch recovery.
Sent from my PG41200 using XDA Premium App
---------- Post added at 05:23 PM ---------- Previous post was at 05:12 PM ----------
Also, I noticed cyanogenmod kernel source for msm7x30 has the express in its defconfig. So Im looking into that right now
Hello everyone....I am a previous developer from the EVO 3D and would like to let some devs know that if they want working Beats then take a peak at the Sensation XL!
HTCFlyerX said:
Hello everyone....I am a previous developer from the EVO 3D and would like to let some devs know that if they want working Beats then take a peak at the Sensation XL!
Click to expand...
Click to collapse
Why don't you just port it for us?
If I only had more time I could actually get more done with my rom and try to build AOSP. Getting promoted has just taken away all my time.
spartan1987 said:
Why don't you just port it for us?
If I only had more time I could actually get more done with my rom and try to build AOSP. Getting promoted has just taken away all my time.
Click to expand...
Click to collapse
In my opinion beats makes music sound like crap when ported. And I have had it on multiple devices.
My aosp kernel testing is not going very well. I really need to read up on board files in the kernel to remove the sense stuff from them
Sent from my HTC_A510c using xda premium
jmztaylor said:
In my opinion beats makes music sound like crap when ported. And I have had it on multiple devices.
My aosp kernel testing is not going very well. I really need to read up on board files in the kernel to remove the sense stuff from them
Sent from my HTC_A510c using xda premium
Click to expand...
Click to collapse
I thought it sounded good on the E3D...(?)
@jmztaylor As for the kernel, would you be interested in working with my team to get the stock one working on cypherROM? Daniels7 (leedroid tweaks) gave me permission to port his tweaks over to my rom, but I need a kernel port of the leedroid kernel or something to that effect (I'd like to build our own). I don't know enough about kernels to do it myself and unixdood hasn't had any luck building one. Everytime I try to cook it in, or even make it flashable it causes bootloop. PM me if you do or if you'd like to work on anything else (including teaching me lol). Thanks!
Hmmm maybe I will just go ahead and do that but idk....getting kicked out and my ROMs shut down was not very nice....just maybe though!
maff1989 said:
I can vouch for this; using any Flyer ROM with the View kernel that matches the version of Android (i.e. GB or HC) WILL work on the View. Namely, LeeDroid's GB ROM with the OC View GB kernel. Although, using the Flyer kernel will cause a bootloop :\
The only thing we are missing out on is an optimized kernel. We wouldn't even need Flyer ports with a "proper" View kernel
Click to expand...
Click to collapse
So would LeeDroids HC Flyer Rom work on the the View?
Sent from my HTC EVO View using XDA on viperROM
wyldkard said:
So would LeeDroids HC Flyer Rom work on the the View?
Sent from my HTC EVO View using XDA on viperROM
Click to expand...
Click to collapse
No it won't. Kernel won't boot for one. I don't think I have tried putting EVO view kernel on it. But I still highly doubt it would boot.
Sent from my PG41200 using XDA Premium App
spartan1987 said:
I thought it sounded good on the E3D...(?)
@jmztaylor As for the kernel, would you be interested in working with my team to get the stock one working on cypherROM? Daniels7 (leedroid tweaks) gave me permission to port his tweaks over to my rom, but I need a kernel port of the leedroid kernel or something to that effect (I'd like to build our own). I don't know enough about kernels to do it myself and unixdood hasn't had any luck building one. Everytime I try to cook it in, or even make it flashable it causes bootloop. PM me if you do or if you'd like to work on anything else (including teaching me lol). Thanks!
Click to expand...
Click to collapse
I have tried taking flyer kernel and porting it to the view but I can't get it to finish compiling. Even after fixing the missing stuff I still was getting a lot of errors. So I put it on the back burner. I got too many projects going on. HTC policy officially is 90-120 days to release kernel source. So we are almost there. LOL
Sent from my PG41200 using XDA Premium App
@HTCflyerX What happened?
Sent from my PG41200 using XDA Premium HD app
Spartan.....hold your horses LOL....I've got to port the beats sound effect into our htcmusic app first....once that's finished ill be releasing the first Beats ROM for the View
HTCFlyerX said:
Spartan.....hold your horses LOL....I've got to port the beats sound effect into our htcmusic app first....once that's finished ill be releasing the first Beats ROM for the View
Click to expand...
Click to collapse
*tear* all that anticipation...gone...
jk
Got some good news from tiamat
Sent tiamat a message, got a reply back. There is hope for us, but we need people to jumpstart and kick development back into the Evo View. So, testers needed on irc...
Hey there, your kernels have been a hit with the vivo on the latest ICS rom we have, we built over the IceColdSandwich LorD ClockaN has been working on for the ace.
I was wondering, if you would ever take the time to look into making a few extra kernels for a few spots where development is really sore.
It's with the HTC Flyer / EVO View 4G tablets, as since we don't have any AOSP kernels, no unofficial CyanogenMod with us too.
The chipsets of those tablets uses the same one as other devices.. I don't think the Flyer has a popular chipset (MSM8255T) but the View uses the mecha's MSM8655 only to be clocked at 1.5Ghz instead of 1.0.
If it's not too much to ask, we could really use your help.
Click to expand...
Click to collapse
The only thing that has been holding me back from working on kernels for the Evo View 4G / Flyer is a lack of testers. the difference in the two processor numbers is not actually related to the processor. The 2 indicates GSM basebands whereas the 6 indicates CDMA bands. I imagine the WiFi-only Flyer is numbered 8055. In any case, to further confuse the numbering/naming scheme here, this chipset is usually referred to as the 7x30 platform. The Thunderbolt, Desire HD, Desire Z, Desire S, Incredible 2, Inredible S, Evo Shift, MyTouch 4G, View/Flyer, Bliss, Merge, Sensation XL, Rhyme, the upcoming One V, and some more I'm missing all use the same platform and should theoretically be easy to merge into my existing code. I only support the first 8, but if I had testers on any of the others, I'd be happy to add them in. The catch there is that I can't make the ROMs for it.
Send me an email or find me on IRC and we can talk more about it.
Click to expand...
Click to collapse
kaijura said:
Sent tiamat a message, got a reply back. There is hope for us, but we need people to jumpstart and kick development back into the Evo View. So, testers needed on irc...
Click to expand...
Click to collapse
Willing tester here! I'm off tomorrow and have no problem staying up late!
Sent from my PG41200 using xda premium
I'd be willing to test. Not tonight, as my View is out of juice right now, but in the future I'd be happy to try and test out stuff. Just tell me where to go.
tiamat is on IRC, find him on irc.freenode.net channel room #tiamat
His handle is cayniarb, but probably isn't hard to find and people in the room will help out.
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
Ok I have been working on getting wimax working in the evervolv jellybean build. I have spent the week only about an hour a day (darn kids won't leave me alone 8)) setting it all up. Im able to bring up the wimax menu and attempt to connect. My problem is that i can get the wimax server to start. If I rip apart cm10's boot img and input my kernel leaving everything alone it boots up wimax server and im able to run with no problem well other problems because im using a little different setup. So I have it down to the boot img specificly the files inside initrd.img. I have reviewed all those files and can't seem to find anything wrong. Everything is setup properly from what i can tell. Im stuck and i know there is alot of great people on this fourms that will help me . I have a github with my device tree and kernel for review https://github.com/flintman
Pre thanks
flintman said:
Ok I have been working on getting wimax working in the evervolv jellybean build. I have spent the week only about an hour a day (darn kids won't leave me alone 8)) setting it all up. Im able to bring up the wimax menu and attempt to connect. My problem is that i can get the wimax server to start. If I rip apart cm10's boot img and input my kernel leaving everything alone it boots up wimax server and im able to run with no problem well other problems because im using a little different setup. So I have it down to the boot img specificly the files inside initrd.img. I have reviewed all those files and can't seem to find anything wrong. Everything is setup properly from what i can tell. Im stuck and i know there is alot of great people on this fourms that will help me . I have a github with my device tree and kernel for review https://github.com/flintman
Pre thanks
Click to expand...
Click to collapse
Good luck Flintman!! I'll be cheering you on!!:highfive::good:
evervolv JB is a source built rom....
if you set up your github and repos to sync evervolv
then all u need to do is fork cmwimaxsettings
then cherry pick two commits to add the wimax
PM me for links and details
Lens_flare said:
evervolv JB is a source built rom....
if you set up your github and repos to sync evervolv
then all u need to do is fork cmwimaxsettings
then cherry pick two commits to add the wimax
PM me for links and details
Click to expand...
Click to collapse
It's not as easy as that... We had to do some more modifications to get it working tonight (flintman and myself). Seems that most aosp jellybean builds had been using a prebuilt HTC init binary, but we figured out how to get around this. At least everything seems to be working properly now. Flintman will be testing it out later tomorrow morning.
Working Great. I posted under comments in gerrit. I notice one more small thing.
So hows the progress
Sent from my PG86100 using xda app-developers app
thatboiken said:
So hows the progress
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Go check the evervolv thread............this thread was just used to discuss things
Wimax already works on Evervolv....lol
thatboiken said:
So hows the progress
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Latest Nightly includes the Wimax and it is working very well.
preludedrew said:
It's not as easy as that... We had to do some more modifications to get it working tonight (flintman and myself). Seems that most aosp jellybean builds had been using a prebuilt HTC init binary, but we figured out how to get around this. At least everything seems to be working properly now. Flintman will be testing it out later tomorrow morning.
Click to expand...
Click to collapse
Thanks for the headsup....
forgot AOSP is alot different than CM10
and may depend on some different things
Im glad to see you got it up and running
Sorry I have been very busy this is working in evervolv. The status bar indicator isn't working yet. I'm on hold with that until 4.2 has been fully merge. Once the merge is complete I want to fix the indicator then move onto another broken feature. Thanks to prelude for the help in getting a fully working WiMAXwith thether capabilities
Sent from my PG86100 using xda app-developers app
Random question has anyone got 4g to work in a sense 4.0 rom?
Sent from my Evo3D using xda app-developers app
thatboiken said:
Random question has anyone got 4g to work in a sense 4.0 rom?
Sent from my Evo3D using xda app-developers app
Click to expand...
Click to collapse
Supposedly newtoroot has http://forum.xda-developers.com/showthread.php?t=1981551 BUT he's yet to put out anything OTHER then screenshots hahahaha
Mazda said:
Supposedly newtoroot has http://forum.xda-developers.com/showthread.php?t=1981551 BUT he's yet to put out anything OTHER then screenshots hahahaha
Click to expand...
Click to collapse
Well you gotta trust the guy, he is the one that started all of the sense 4 Rom fad in the 3d forums
Sent from my PG86100 using Tapatalk 2
No update since last month but thanks anyways
Sent from my Evo3D using xda app-developers app
VictoriousShooter said:
Well you gotta trust the guy, he is the one that started all of the sense 4 Rom fad in the 3d forums
Sent from my PG86100 using Tapatalk 2
Click to expand...
Click to collapse
Didn't say I don't trust him, just said it was only screenshots
I'm sure there's other things to be worked out with wimax on sense 4.0 and when is ready, it'll come........WHEN will it come? Who knows hahahahaha
Mazda said:
..WHEN will it come? Who knows hahahahaha
Click to expand...
Click to collapse
The day after I upgrade in July to the newest Evo.
coal686 said:
The day after I upgrade in July to the newest Evo.
Click to expand...
Click to collapse
Not before I get mine in april
are there wimax drivers that are released, i want to experiment putting wimax in a sense 4 rom
You know I have posted in my public github how I got Wimax working in my MIUI jb builds although I haven't updated it on there since September. What I've learned while trying to get it to work on sense based ROMs is that HTC has about 10000 lines of fairly useless code to sort through to get it going. In most sense ROMs for our device, and of course this is all smali, everything you need is in framework.jar, only the connection service email in services.jar, wimax.jar of course, and believe it or not the bear of the whole thing Settings. apk. Settings is where my focus has been on DH Miui ICS. See settings has all the action for the most part such as all the messy HTCPreference* classes. Those classes are crazy in the sense that there are so many events triggered in each one that most of my days trying to get it to work have been spent trying to follow all of these events to see which ones are necessary and which aren't. The Aosp wimax on our devices only requires a third of that editing and the rest is getting the right libs and modules for the most part. If you do a grep of the word wimax after decompiling everything in the sense roms you'll see all of the places you need to mess with and sometimes write your own smali classes from scratch for the most part. I believe someone could do it without much difficulty but its the time it will take that's most likely the hardest part. As long as you have the correct binaries.
Sent from my Evo 3D CDMA using Tapatalk 2
cmbaughman said:
I believe someone could do it without much difficulty
Sent from my Evo 3D CDMA using Tapatalk 2
Click to expand...
Click to collapse
I vote for you to be that someone.
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