Related
Yeah, I know...let's get a stable Froyo first.
But...
I pulled the 2.3.1 (gingerbread) source, and it's currently building. I hit a couple of snags, but I'm off and running so far.
I've also compiled the latest 2.6.36 kernel -- compiled, not tested! Don't get excited just yet.
I'm not going to lie, I'm green to android. But I've worked with Linux professionally for 15+ years. I've been compiling kernels since Linus released 2.0 oh so long ago. Building Linux x86 from scratch (go gentoo linux!) is nothing new to me. But android and arm...ehh...bear with me.
So is anyone else trying to do this? I'd like to collaborate and hear about your progress and any problems you've had. No need to try to reinvent wheels or anything.
Step 1 is getting it to boot...
Here's my 2.6.36 kernel zImage file and .config build if anyone is curious.
My suggestion...change your title to [Dev] AOSP Gingerbread. Start a github or similar repository and get cracking. I'm sure there are plenty of people that would consider jumping on board. With the Nexus S source out, some things shouldn't be TOO hard, but I think porting the CDMA stuff is probably a huge challenge.
plapczyn said:
My suggestion...change your title to [Dev] AOSP Gingerbread. Start a github or similar repository and get cracking. I'm sure there are plenty of people that would consider jumping on board.
Click to expand...
Click to collapse
id jump on board if i knew what i was doing
Glad your focusing on this! I don't think we have to finish froyo to start gingerbread. Not sure how much I can help but hit me up if you need anything done.
Sent from my SPH-D700 using Tapatalk
I glad too see that someone is taking initiative here. My thinking all along is the drivers for froyo will most likely work in someway for gingerbread but without kernel source for froyo yet, I would think you would have to start from ground up. But good luck to you regardless.
Sent from my SPH-D700 using XDA App
This is delicious. Now it only needs sauce.
Everyone can learn from the OP's example. Less posturing more action.
msponsler said:
Yeah, I know...let's get a stable Froyo first.
But...
I pulled the 2.3.1 (gingerbread) source, and it's currently building. I hit a couple of snags, but I'm off and running so far.
I've also compiled the latest 2.6.36 kernel -- compiled, not tested! Don't get excited just yet.
I'm not going to lie, I'm green to android. But I've worked with Linux professionally for 15+ years. I've been compiling kernels since Linus released 2.0 oh so long ago. Building Linux x86 from scratch (go gentoo linux!) is nothing new to me. But android and arm...ehh...bear with me.
So is anyone else trying to do this? I'd like to collaborate and hear about your progress and any problems you've had. No need to try to reinvent wheels or anything.
Step 1 is getting it to boot...
Click to expand...
Click to collapse
About time!
Thank you for working on this. I never really understood the source argument. I just put gingerbread on my old hero and everything works except for camera and screen rotation. It sure as hell doesn't have an official/leaked release or even froyo source. Anyways just ranting about the things I hear. I know I dont have the skills to work on this stuff, so thanks for the effort.
Sent from my SPH-D700 using XDA App
I have it just about booting(;
Sent from my SPH-D700 using XDA App
somedude0608 said:
Thank you for working on this. I never really understood the source argument. I just put gingerbread on my old hero and everything works except for camera and screen rotation. It sure as hell doesn't have an official/leaked release or even froyo source. Anyways just ranting about the things I hear. I know I dont have the skills to work on this stuff, so thanks for the effort.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I agree, I had froyo on my hero long before I even thought about switching to the epic.... and they've made so much progress on gingerbread... I often wonder whether I made the right choice or not going with the epic. Although the evo doesn't have a keyboard and is really square, it gets a lot of attention and has had many official updates. I wish samsung would get off of their asses and just release the source.
I'd love to help out any way I can. I'm not a programmer, but I hve a great understanding on what the issue is. I had a hero before the epic, and they have fully functional froyo despite never having kernel source. One would have to be built, cause I don't think samsung is going to really support us that much longer (if at all) and give us any hope for gingerbread source. The trickiest part is the cdma/wimax radios (wimax still not supported in cyanogenmod for evo).
Sent from my SPH-D700 using XDA App
bubby323 said:
I have it just about booting(;
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Did you build gingerbread from source?
What kernel are you using?
I built a 2.6.36 last night...but the more I thought about it, the more I realized it doesn't do me any good as it is right now.
I've downloaded samsung's kernel source for 2.6.29 and I'm trying to get the modules for the video, radio, etc... to compile with 2.6.36.
The nexus s is using 2.6.35, which is fine when it comes to the video drivers, wifi, and such....but it doesn't do us any good when it comes to 3G because tmobile doesn't use CDMA, so it wouldn't have the same radio kernel modules.
I'm currently running noobnl's cyanogenmod (froyo) on my epic, and that has a 2.6.32.9 kernel. I'll have to take a closer look at how you built that kernel.
Thank you for your initiative OP! I appreciate it.
Sent from my SPH-D700 using XDA App
nerdtaco said:
Thank you for your initiative OP! I appreciate it.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Seconded! I know nothing about developing software but I'm a pretty good test dummy =)
This is pretty kickass. Is there anything in particular you could use for help? I have some limited experience with both linux and android specific kernels.
furysama said:
This is pretty kickass. Is there anything in particular you could use for help? I have some limited experience with both linux and android specific kernels.
Click to expand...
Click to collapse
At this point I don't necessarily need any assistance. But thanks for all the offers!
If I have any questions / requests I'll sure to let everyone know!
Thanks!
The only other question i have is this: how difficult is it to integrate Samsung's 4g drivers into an AOSP mod? Now, I know if we wanted to keep it 100% AOSP it would be... difficult. But is it possible to run a 90% AOSP mod, and just keep the drivers for 4G in the AOSP kernel?
furysama said:
The only other question i have is this: how difficult is it to integrate Samsung's 4g drivers into an AOSP mod? Now, I know if we wanted to keep it 100% AOSP it would be... difficult. But is it possible to run a 90% AOSP mod, and just keep the drivers for 4G in the AOSP kernel?
Click to expand...
Click to collapse
Very very difficult considering it took a team of developers a few months on the EVO to get 4G working with a AOSP kernel. I guess it will depend on how Samsung releases the code, they'll probably not release the 4g code because it doesn't fall under the GPL. If they were to release the drivers as modules that could be included in a kernel, that would be great, but I doubt they'd do that either.
In other words... don't hold your breath...
-Daryel
daryelv said:
Very very difficult considering it took a team of developers a few months on the EVO to get 4G working with a AOSP kernel. I guess it will depend on how Samsung releases the code, they'll probably not release the 4g code because it doesn't fall under the GPL. If they were to release the drivers as modules that could be included in a kernel, that would be great, but I doubt they'd do that either.
In other words... don't hold your breath...
-Daryel
Click to expand...
Click to collapse
The reason it took the CM team so long is because they developed their own drivers from the ground up. I'm willing to bet that it's much easier to rip the drivers out of the kernel we already have than to replicate the work that the CM team did.
The GPL licensing is *why* the CM team developed their own drivers; not because its impossible to get Samsung's code, but because doing so would have violated the licensing terms of Samsung's code and of Cyanogenmod.
Any word from any one on when the devlopers will get the source code for this phone? I realize that this will help everyone developer wise get a better handle on kernels and greatly help the community.
I went back to GB for a second there but the charging issues have gotten out of control with the kernels which is why I'm starting to wonder when the sourrce will be released. We obviously need it to make further advancement with the community ROMs at this point.
I also seen where HTC said that they will unlock their bootloaders here soon.
Thanks for any one who contributes to this conversation.
Gingerbread? Or Froyo? Cuz Froyo been out...
Thunderbolt «» das BAMF Remix
Kid_Cudi said:
Gingerbread? Or Froyo? Cuz Froyo been out...
Thunderbolt «» das BAMF Remix
Click to expand...
Click to collapse
I like Kid Cudi as well first of all.
What I mean is and I'm probably not going to use the right term here but the RIL or perhaps SDK.. Bear with me here I'm good at trouble shooting stuff but not programming.
I was googling it didn't help me get the right term lol. Chime in who ever knows what the hell I'm talking about here lol.
The kernel source itself has been out for quite some time. We will never see the "source" for the RIL (Radio Interface Layer) because it is proprietary on both HTC and Qualcomm's side. That's about as simple as it gets.
ProTekk said:
The kernel source itself has been out for quite some time. We will never see the "source" for the RIL (Radio Interface Layer) because it is proprietary on both HTC and Qualcomm's side. That's about as simple as it gets.
Click to expand...
Click to collapse
Yeah I think it's RIL. It's what the Cookers keep stating they're waiting for to finish their ROMs like CM7 for instance. The developer for it states that he's waiting for RIL to be able to officially finish his work. We really need to get this released from HTC so we can fix some of the issues people are having with CM7 and the leak for GB. I went back to Froyo because of the issues the leaks having with charging etc..
thewebsiteisdown said:
Any word from any one on when the devlopers will get the source code for this phone? I realize that this will help everyone developer wise get a better handle on kernels and greatly help the community.
I went back to GB for a second there but the charging issues have gotten out of control with the kernels which is why I'm starting to wonder when the sourrce will be released. We obviously need it to make further advancement with the community ROMs at this point.
I also seen where HTC said that they will unlock their bootloaders here soon.
Thanks for any one who contributes to this conversation.
Click to expand...
Click to collapse
HTC and google do not have to release any of the android source if they don't want to because the source (NOT THE KERNEL) uses the apache license, which is very permissive like the BSD/MIT licenses. It lets you use any code additions you make to the source for commercial projects without having to give it back unless you choose to http://en.wikipedia.org/wiki/Apache_license. This is why google doesnt have to release the Honeycomb source as long as they didn't make any additions/modifications to the kernel itself.
Google went through lots of effort as well to make sure they would not be bound by the GPL by writing their own clibs based off of code from various BSD ports. See here for an interesting article on some of the low level features of android (it's a bit old, but most of it is still relevant). http://codingrelic.geekhold.com/2008/11/six-million-dollar-libc.html
The kernel (like all linux kernels) is GPL and must be released.
RIL will be released when it is finished. Slayher is working hard as hell on it. Not saying anyone is under appreciating just give the man some time and soon we will all have MIUI and CM7 running flawlessly on our devices.
miketoasty said:
RIL will be released when it is finished. Slayher is working hard as hell on it. Not saying anyone is under appreciating just give the man some time and soon we will all have MIUI and CM7 running flawlessly on our devices.
Click to expand...
Click to collapse
I think there is a misunderstanding here. The RIL from Slayher is not the same as the RIL from HTC/Qualcomm.
Slayher will merge his "source" into the public CyanogenMod repo once he deems it's ready.
On the other hand, the "source" from HTC/Qualcomm is a whole different subject. We won't be getting a drop of it from them. Not now, not ever.
miketoasty said:
RIL will be released when it is finished. Slayher is working hard as hell on it. Not saying anyone is under appreciating just give the man some time and soon we will all have MIUI and CM7 running flawlessly on our devices.
Click to expand...
Click to collapse
I deffinately appreciate all the hard work. I just thought that HTC had to release this info. I didn't know that Slayher or any other coder could just reverse engineer it.
thewebsiteisdown said:
I deffinately appreciate all the hard work. I just thought that HTC had to release this info. I didn't know that Slayher or any other coder could just reverse engineer it.
Click to expand...
Click to collapse
No the RIL source and Sense source run under the apache license which states that the software developer can use the open source code but does NOT have to repost anything he or she produces.
So it is up to our dev's to do that and make it readily available.
I'll keep this post upto date with the last on the status of the build.
I've updated the manifest and it's inline with cm10. https://github.com/TeamICS/manifest_ics_cm/tree/jellybean
Builds are located here.
Nightlies are here or here
If you are not using firerats or don't know what that is make sure you use one of the "_shrunk" nightlies.
Currently the room boots. Lots of things work, here is what doesn't:
Bluetooth (pairing)
HW Acceleration (not likely)
Anything missing from CM10
Known issues are:
Headphone + speaker plays when headphones are in
<--previous-->
IT LIVES!
The build doesn't flash, but it successfully built. You need to use firerats as the system partition is over 173mb by itself. Not sure of optimal settings as it doesn't flash but we're getting closer.
Complete repo diff and repo status is here:
https://gist.github.com/3095432
Things disabled at build:
audioinwrapper from srec
libaac/libFDK
compiler-rt
maybe others.
Please note I haven't cleaned anything so it's quite messy and some stuff isn't pushed up to the repos yet. However it builds and that's a big step. It's off to bed and work tomorrow so I won't get a chance to work on it until the evening/friday.
Very close to a build, libaac is the only blocker, I've reached out to cyanogenmod guys to see if they have any ideas to fix aac, without completely rewritting the asm code. The problem is armv6j doesn't support smmul, clz and others in thumb mode, but armv7 (and the few devices with thumb2 on armv6t2) do. I don't have enough experience with arm asm to figure out how to rework the code to convert from 32 bit operations to 16bit operations. Also valgrind is not supported in armv6 (and can't be) so its disabled.
problems building aac, due to asm code, currently disabled a blocker
problems building srec due to audio issue, disabled
haven't ported camera
So far there is only two show stoppers, first is the audio because its changed again slightly. Shouldn't be too hard to work around. Second is cm team is still porting over all armv6 patches. Building on armv5 get stuck at audio, but armv6 get stuck on some asm code in bionic.[/sstrike] aac. AAC is being a really PITA!
<--Original Post-->
So I'm sure some of you guys are watching the I/O live. For those that aren't it's offical Jellybean will be 4.1. It's got loads of new and nice features. A lot of performance upgrades and the most important thing is the annoucement of the platform development kit. It's got all the low level details and apis need to port hardware to android.
Source code will be released in mid july, which is when the real development starts.
The hardwork everyone did on ICS, jaybob, matt, evervolv team and everyone from the G1, hero and eris forums laid the foundation. The main issue that has always held the heroc back has been the drivers. We have a great .35 kernel but with ICS a lot of the framework, that is hardware <-> software interactions changed. Thats what our audio issue was at first, and the camera. Audio was fixed by porting gingerbread patches and legacy audio support. The camera was tougher but eventually fell to the power of the community! The only two major things left are camcorder and full gpu acceleration.
The PDK will hopefully provide the last little bit we need to get acceleration working fully. It's no magic but from the keynote sounds like it might provide the information we need. Or it might not. Won't know until it lands on the web.
Overall jellybean is a step further from our old heroc's but there is still almost 20k devices officially running cm7! We obviously still have a community here who has yet to upgrade so the new goal is jellybean or bust!
As more information and sources are released I'll update the thread. I plan to port our TeamICS github account to Jellybean as soon as it's released. With luck everything will compile and be in the same boat as ics but only time will tell.
Thank you so much for posting this thread! I would have never knew about this. I'm willing to contribute to Jellybean although I'm with the Evo Shift now. I can make AOSP whenever the first jellybean Rom is released hopefully fixing some things!
count me in, i still have a few months on my heroc left until i upgrade
most of the fixes that happened from eligorom should be able to be applied to jellybean, as its basically the same rom as ics (from early reports)
I really need to add it to a signature when here in the HeroC forums, but:
My HeroC has been inactive on a carrier for the last year +, that being said, I still use the crap out of the device when I can, for a clock/alarm, music, GVoice and GrooveIP phone calls when home...
Basically, I would LOVE to see this thing continue to get updates, I still run CM7 over CM9 or ICS because for me, I see the most performance with CM7. Your talk of the PDK has me excited that I might see equal or better performance out of Jelly Bean on my HeroC!
TYVM, keep us updated
im pretty sure jellybean is going to run equal with ics for us, since hardware acceleration is still not available to us
i've been scouring the web for a solution, but no dice so far. we can turn off hwa, but i see no performance increase from doing so
from what i read, its going to take a module and some tweaks, so its going to take a dev with alot of time and knowledge on their hands to get us up to par with the adreno 200, which may never happen (although i hope it does, the heroc is awesome)
Thanks for sharing! Hard!
Not to sure if it can get 4.1. I'm having troubles getting it on the Evo Shift right now...
whoshotjr2006 said:
im pretty sure jellybean is going to run equal with ics for us, since hardware acceleration is still not available to us
i've been scouring the web for a solution, but no dice so far. we can turn off hwa, but i see no performance increase from doing so
from what i read, its going to take a module and some tweaks, so its going to take a dev with alot of time and knowledge on their hands to get us up to par with the adreno 200, which may never happen (although i hope it does, the heroc is awesome)
Click to expand...
Click to collapse
So will Project Butter have no effect on the Hero? I would think that it would at least have some effect in adding smoothness.
Sent from my SPH-D710 using xda app-developers app
I have to say I'm really exited about this. I ran ICS a few times on my hero with no problems, but I'm still using it as a daily even though I'm sure it would run fine. Ive been thinking about upgrading, but i don't see why. I really don't like any new phones. Their too big, no track ball, and i just simply don't like any of the new phones out right now. So all that being said... JELLYBEAN !!!!!
Source is out!
https://groups.google.com/forum/#!topic/android-building/XBYeD-bhk1o
edit: Not quite yet.
I'll update the TeamICS github with a new manifest for it as soon as it's out. Good news is that I happen to have tomorrow off so looks like I'll get a nice full day of playing around and trying to get it building. As with ICS I suspect most things will be broken, audio, dalvik, etc. So we'll have to port the ICS patches to jb. Once cm updates it's sources to jb, then we can switch back to them as they will have most of the patches in place already.
Shelnutt2 said:
Source is out!
https://groups.google.com/forum/#!topic/android-building/XBYeD-bhk1o
edit: Not quite yet.
I'll update the TeamICS github with a new manifest for it as soon as it's out. Good news is that I happen to have tomorrow off so looks like I'll get a nice full day of playing around and trying to get it building. As with ICS I suspect most things will be broken, audio, dalvik, etc. So we'll have to port the ICS patches to jb. Once cm updates it's sources to jb, then we can switch back to them as they will have most of the patches in place already.
Click to expand...
Click to collapse
I change my mind, i do think the hero can run jb BUT im not to sure about 5.0 or whatever they call it.. i upgraded to the evo shift and love it!! Just letting y'all know because this might be the last upgrade sadly said :/
Sent from my BNTV250 using xda premium
awesome, cant wait to see the first source build
ill help in whatever way i can, i just cant dl source because of my crappy internet connection (but if i can find someone to borrow faster internet from for a few hours ill most definitely dl source and try to contribute back that way)
Lol may take me a while before I can start porting for the hero again..
My current projects for the evo shift:
Motoblur
Porting Sense
4.1
3.0
Thats pretty much it =)
Well the cyanogenmod guys are making quick work of jellybean. Every hour more and more patches are ported over. Good news is we are very close to a build. Here are the current issue and workarounds.
Audio doesn't build, working on porting it over
problems with v6 in dalvik, changed to arm mode and ported ics *.S files
problems building aac, due to asm code, currently disabled
problems building srec due to audio issue, working on porting audio
haven't ported camera
Currently hungry and looking for lunch :fingers-crossed:
Shelnutt2 said:
Well the cyanogenmod guys are making quick work of jellybean. Every hour more and more patches are ported over. Good news is we are very close to a build. Here are the current issue and workarounds.
Audio doesn't build, working on porting it over
problems with v6 in dalvik, changed to arm mode and ported ics *.S files
problems building aac, due to asm code, currently disabled
problems building srec due to audio issue, working on porting audio
haven't ported camera
Currently hungry and looking for lunch :fingers-crossed:
Click to expand...
Click to collapse
So excited. My Hero has a sweet tooth.
Ha yeah to be honest the hero is getting more development on ics then my evo shift because y'all have aokp.. I need help with someone getting it to work on my evo shift.. We just had a ICS Kernel released so that better get some devs working .. Even though we lost A LOT to the evo 4g lte sadly said..
megaghostgamer said:
Ha yeah to be honest the hero is getting more development on ics then my evo shift because y'all have aokp.. I need help with someone getting it to work on my evo shift.. We just had a ICS Kernel released so that better get some devs working .. Even though we lost A LOT to the evo 4g lte sadly said..
Click to expand...
Click to collapse
I dont know about AOKP. Sure it was ported, but what work has there been done on it since? Honestly ICS ran super smooth for me on my Hero, especially coupled with V6SuperCharger. I was using LauncherPro on ICS to add to the smoothness, but the V6SuperCharger allows for smooth use of Apex.
yeah, it wasnt aokp that accelerated our cause, aokp has only been around for a few weeks for us so far. it was jaybob's ics aosp rom that really kicked things into gear. that and stritfajt with the camera fix, and the guys over at hero gsm for all the different tweaks and fixes, and mongoosehelix over at eris that kicked butt with evervolv for us. im sure im missing some people, but it doesnt make them any less important to the cause.
and last but not least all the testers and rom flashers that gave excellent feedback
i look forward to seeing jb run like ics
So the reason it's unflashable was because it's over the 170mb limit of the phone. Even though I'm using firerats there still seems to be a hard limit of the recovery and fastboot. The solution is to use a newer recovery, anything cwm 3.x or higher works. The dev phone I'm using had 2.5 cwm and that was the issue. Now it flashes fine. Only problem is for some reason sh didn't build, so now I'm looking to see why it didn't build.
we can cut out some cruft, like live wallpapers, and ringtones/notification sounds. live wallpapers dont work well on heroc anyway.
the sh error is boggling me too, supposedly its mksh symlinked as sh, which should have worked as thats how it is in ics roms.
im on the job lol
edit: yeah something is definitely rotton with those permissions, i checked them against an ics rom and everything checks out, but we still get the permissions error. i'm wondering if its the update binary possibly? ill do some checking and let you know one way or the other
I've had a few folks message me with requests for guidance on how to add 4G WiMax to CM7-based ports. I figured I would go ahead and write up this quick guide on how to do it for LeWa OS. This should be very similar with other ROMs.
Let's start with the easy part.
- Copy /system/app/CMWimaxSettings.apk.
- Copy /system/framework/wimax-api.jar.
Decompile /system/framework/framework-res.apk
Edit ./res/xml/bools.xml
- change config_wimaxEnabled value to true
Edit ./res/xml/strings.xml
- change config_wimaxServiceJarLocation value to /system/framework/wimax-api.jar
- change config_wimaxManagerClassname value to com.htc.net.wimax.WimaxController
- change config_wimaxServiceClassname value to com.android.server.WimaxService
Edit ./res/xml/arrays.xml
- in networkAttributes element, add <item>wimax,6,6,2</item> (I add it after wifi)
- in radioAttributes element, add <item>6,1</item> (I add it to the top)
- in config_tether_upstream_regexs element, add <item>wimax\\d</item> (I add it to the bottom)
Now somewhere (probably Settings.apk), you'll want to add a link to it.
Example from my LeWa OS port:
Code:
<com.android.settings.IconPreferenceScreen android:title="@string/wimax_settings" android:key="wimax_settings" settings:icon="@drawable/ic_settings_wifi">
<intent android:targetPackage="com.android.settings.wimax" android:action="android.intent.action.MAIN" android:targetClass="com.android.settings.wimax.WimaxSettings" />
</com.android.settings.IconPreferenceScreen>
.
That should be it.
PS-
While you're in arrays.xml and looking at config_tether_upstream_regexs, you should also look for something like wlan\\d (if it's there, it's probably the second item) and change it to eth\\d if you see it. This will fix tethering.
I appreciate this guide shall use this on my aed ios port
Sent from my PC36100 using xda premium
Stupid question, so why are developers not including this did in there work?
Sent from my PC36100 using xda app-developers app
monty_python said:
Stupid question, so why are developers not including this did in there work?
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
I'd first like to emphasize that this guide is primarily targeted at developers of "CM7-based ports," i.e., taking a ROM that is based on CM7 from one device and bringing to the Evo 4G.
Now to answer your question: It's because device from which they are taking the ROM does not support WiMax and/or is not an HTC phone.
As an example, the version of LeWa OS that I use is made for a Chinese phone (U8800X) that doesn't have built-in WiMax support (and it is not made by HTC). The ROM should not be expected to support WiMax out of the box and certainly shouldn't be expected to use HTC's WiMax API. The developers that are porting the ROM are then tasked with having to shoehorn WiMax support into the ROM. This is a breeze when the ROM is based on CM7 (not nearly as easy when the ROM is, for example, MIUI) because it's just a matter of changing some settings, as demonstrated in the first post.
dumpydooby said:
I'd first like to emphasize that this guide is primarily targeted at developers of "CM7-based ports," i.e., taking a ROM that is based on CM7 from one device and bringing to the Evo 4G.
Now to answer your question: It's because device from which they are taking the ROM does not support WiMax and/or is not an HTC phone.
As an example, the version of LeWa OS that I use is made for a Chinese phone (U8800X) that doesn't have built-in WiMax support (and it is not made by HTC). The ROM should not be expected to support WiMax out of the box and certainly shouldn't be expected to use HTC's WiMax API. The developers that are porting the ROM are then tasked with having to shoehorn WiMax support into the ROM. This is a breeze when the ROM is based on CM7 (not nearly as easy when the ROM is, for example, MIUI) because it's just a matter of changing some settings, as demonstrated in the first post.
Click to expand...
Click to collapse
Ok, that makes more sense.. thanks for your letting us in on your mod...
Sent from my PC36100 using xda app-developers app
dumpydooby said:
I'd first like to emphasize that this guide is primarily targeted at developers of "CM7-based ports," i.e., taking a ROM that is based on CM7 from one device and bringing to the Evo 4G.
Now to answer your question: It's because device from which they are taking the ROM does not support WiMax and/or is not an HTC phone.
As an example, the version of LeWa OS that I use is made for a Chinese phone (U8800X) that doesn't have built-in WiMax support (and it is not made by HTC). The ROM should not be expected to support WiMax out of the box and certainly shouldn't be expected to use HTC's WiMax API. The developers that are porting the ROM are then tasked with having to shoehorn WiMax support into the ROM. This is a breeze when the ROM is based on CM7 (not nearly as easy when the ROM is, for example, MIUI) because it's just a matter of changing some settings, as demonstrated in the first post.
Click to expand...
Click to collapse
So...any ideas about the MIUI roms? I have been trying to get 4g to work forever. Gave up, and now I'm back at it. I'm using the kitchen btw. I tried including all the libs, jars, etc. from c7 and the phone booted normally, but I got nothing as far as wimax. There was no toggle present so I DL'd one from the market. It stated that my phone wasn't 4g capable. Back to the drawing board.
Do you have any ideas why this isn't working? You mentioned that your method wouldn't be as easy with MIUI. Why? I'm only asking because I'm seeking the education. My research has only rendered complaints from those who want it but can't figure it out. BTW, I'm not a fan of CIUI but I understand their reasons for the departure from MIUI altogether.
Thanks in advance!
kz6fittycent said:
So...any ideas about the MIUI roms? I have been trying to get 4g to work forever. Gave up, and now I'm back at it. I'm using the kitchen btw. I tried including all the libs, jars, etc. from c7 and the phone booted normally, but I got nothing as far as wimax. There was no toggle present so I DL'd one from the market. It stated that my phone wasn't 4g capable. Back to the drawing board.
Do you have any ideas why this isn't working? You mentioned that your method wouldn't be as easy with MIUI. Why? I'm only asking because I'm seeking the education. My research has only rendered complaints from those who want it but can't figure it out. BTW, I'm not a fan of CIUI but I understand their reasons for the departure from MIUI altogether.
Thanks in advance!
Click to expand...
Click to collapse
Yeah, the reason none of this will work in MIUI (or any other ROM not based on CM7) is because these are all just configuration settings. The CM7 framework reads the value of config_wimaxServiceJarLocation so that it knows where to find the WiMax API, for example. MIUI framework would simply ignore that value because it's not programmed to interpret it.
I know fergie and the guys got WiMax working on MIUI on some other device(s). Last I checked, they were working on getting it to work with the Evo 4G as well.
LOL I was gonna do this exactly for the JoyOS port. I saw the differences in Decks framework and the JoyOS framework and was like hmmmmmm. I put it off until I got everything else where I wanted it! Good looking out for those who need it for their ports or future ports!!
dumpydooby said:
Yeah, the reason none of this will work in MIUI (or any other ROM not based on CM7) is because these are all just configuration settings. The CM7 framework reads the value of config_wimaxServiceJarLocation so that it knows where to find the WiMax API, for example. MIUI framework would simply ignore that value because it's not programmed to interpret it.
I know fergie and the guys got WiMax working on MIUI on some other device(s). Last I checked, they were working on getting it to work with the Evo 4G as well.
Click to expand...
Click to collapse
So basically I'd need to build a cm7 based miui rom from scratch to make it work...Jeeze.:what:
sent from my o.g.
Can I pop the link to WiMax in wireless_settings.xml?
T10NAZ said:
Can I pop the link to WiMax in wireless_settings.xml?
Click to expand...
Click to collapse
I would assume so. That's where I put it in mine.
dumpydooby said:
I would assume so. That's where I put it in mine.
Click to expand...
Click to collapse
Cool just wanted to double check
Hi Guys,
I'm very new to this scene and have already started experimenting with ROMS (running Leedroid at the moment). I've just had a quick play with Coldblooded CM10 and love it but I'm intrigued about the current 'broken list'.
Is this just the way it goes with ROM Development on a new device that it goes through multiple iterations until the dev engineers a fix to all the issues? Does it make any difference when HTC for example eventually release the kernel source (which I assume they will once the official JB release comes out). I'm guessing stuff like the headphone issue/in-call echo will be 'fixed' in the official release from HTC so could be implemented in existing ROMs?
Hope that makes sense and I haven't just broken a load of noob xda rules....
Thanks
basically a rom is never really finished.
theres always something to be ironed out or a bug that needs to be squashed. or sometimes its just enhancements,
but yea like you said until htc releases the source then stuff wont be 100%
Even when they do release the sources, there's still lots of things that potentially might not work.
Like take for example CM9 (ICS based) - although there are kernel sources out already for HTC's ICS, a bunch of things are not yet working. You can blame that on closed-source drivers, like wifi or camera, etc.
So it might take a while for everything to work properly, but as long as we have dedicated developers like xkonni, intervigil, etc, there's nothing to be worried about.
Sent from my HTC One S using xda premium
Nice thanks guys that makes sense. I just assumed that things like drivers could be poached and reused but I guess a lit of that is part of the sense framework.
I look forward to seeing what happens
Sent from my HTC One S using xda app-developers app
dillinga said:
Hi Guys,
I'm very new to this scene and have already started experimenting with ROMS (running Leedroid at the moment). I've just had a quick play with Coldblooded CM10 and love it but I'm intrigued about the current 'broken list'.
Is this just the way it goes with ROM Development on a new device that it goes through multiple iterations until the dev engineers a fix to all the issues? Does it make any difference when HTC for example eventually release the kernel source (which I assume they will once the official JB release comes out). I'm guessing stuff like the headphone issue/in-call echo will be 'fixed' in the official release from HTC so could be implemented in existing ROMs?
Hope that makes sense and I haven't just broken a load of noob xda rules....
Thanks
Click to expand...
Click to collapse
No worries man this was a very legit question.