Related
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.
When jellybean leaks or is officially released do you think there will be more devs working on custom roms?? Im ordering mine on tuesday no matter what tho. cant wait
Probably not. Already a number of devs working on things.
I would imagine that you will see a few new devs and roms when/if the first person figures out a reasonable way of converting N4 / ASOP roms over though.
Sent from my LG-E970 using Tapatalk 2
JasonJoel said:
Probably not. Already a number of debs working on things.
I would imagine that you will see a few new devs and roms when/if the first person figures out a reasonable way of converting N4 / ASOP roms over though.
Sent from my LG-E970 using Tapatalk 2
Click to expand...
Click to collapse
that sounds great
thanks for the quick reply
JoeyGuard said:
When jellybean leaks or is officially released do you think there will be more devs working on custom roms?? Im ordering mine on tuesday no matter what tho. cant wait
Click to expand...
Click to collapse
The Base rom will probably be updated to 4.1 or 4.2 depending on what's released.
We probably won't see more devs immediately but, keep in mind Christmas is coming up so a lot of people will be getting new devices and have no free time till Christmas..
Then after Christmas people will have less to do, more time, and a new device to play with.
Snow_fox said:
The Base rom will probably be updated to 4.1 or 4.2 depending on what's released.
We probably won't see more devs immediately but, keep in mind Christmas is coming up so a lot of people will be getting new devices and have no free time till Christmas..
Then after Christmas people will have less to do, more time, and a new device to play with.
Click to expand...
Click to collapse
Great point. Plus, we really only need a few devs. Give me one that can compile CM10.1, one that handles AOKP and maybe a few that make some hybrids. Hell, if development doesn't pick up once JB source for this device is available, I will buy a phone for a member on my team that can build from source
Sent from my LG-E970 using Xparent ICS Tapatalk 2
JohnCorleone said:
Great point. Plus, we really only need a few devs. Give me one that can compile CM10.1, one that handles AOKP and maybe a few that make some hybrids. Hell, if development doesn't pick up once JB source for this device is available, I will buy a phone for a member on my team that can build from source
Sent from my LG-E970 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
Any idiot with Linux could learn easily how to compile assuming the sources are all there, but there are things we have to make from scratch or modify from the nexus. We are working on it.
Sent from my LG-LS970 using Tapatalk 2
One of the reasons they changed the moderator system was to keep Questions out of General and the Development fora. There's a whole Q/A forum for this device. Please try to remember that.
Moved to Q&A please post in proper sections.
krook6023 (mod team)
Hey guys just wondering if there are any devs out there that can work on kernels. I think it would be awesome to have a kernel that includes dt2w. Anyone else as interested in this as me?
Sent from my HTC6435LVW using Tapatalk
coachcrey said:
Hey guys just wondering if there are any devs out there that can work on kernels. I think it would be awesome to have a kernel that includes dt2w. Anyone else as interested in this as me?
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
crparmer
not sure if i spelled it right.
thayl0 said:
crparmer
not sure if i spelled it right.
Click to expand...
Click to collapse
Yeah but I think he likes to keep thing as stock as possible.
Sent from my HTC6435LVW using Tapatalk
coachcrey said:
Yeah but I think he likes to keep thing as stock as possible.
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
Not really it done a amazing kernal for cm 10.2
And I believe he is working on one for 4.4 kitkat cm 11
thayl0 said:
Not really it done a amazing kernal for cm 10.2
And I believe he is working on one for 4.4 kitkat cm 11
Click to expand...
Click to collapse
I know that but when people have asked him to add sleep to wake he didn't seem interested in that I'm not dogging him at all man he great no question asked.
Sent from my HTC6435LVW using Tapatalk
Adding it takes time, adds risk to the stability of the phone and gives me no benefit. My phone is heavily locked down by my IT department and with a minimum 8 character alpha numeric password, the sweep or double tap to wake is not improving my life.
I love s2w as much add the next guy..... but try omnirom 4.4, and enable active display.... you might like it better.
Sent from my HTC6435LVW using xda app-developers app
crpalmer said:
Adding it takes time, adds risk to the stability of the phone and gives me no benefit. My phone is heavily locked down by my IT department and with a minimum 8 character alpha numeric password, the sweep or double tap to wake is not improving my life.
Click to expand...
Click to collapse
This is why i was trying to shout out to other. I know your work is the real deal man. Its just something I'm interested in. In no way was i trying to insult you.
Kauffman_c said:
I love s2w as much add the next guy..... but try omnirom 4.4, and enable active display.... you might like it better.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I'm not sure what settings you use with active display but I'm not really sold using it. I like sweep2wake as well.
Sent from my HTC6435LVW using Tapatalk
Okay, here's a dumb question... Right now we share the AOSP kernel source with the HTC One. Wouldn't flashing a custom AOSP kernel for the One work on the DNA?
yeah some nice s2w like the old cubed kernel so you can do just "back to home" to wake it, its so nice i dont see how ppl dont want it of course unless they have some crazy circumstance like crpalmer just described
but we have a lot of diff roms so something like this would be rather difficult to choose one version of android for this to be implemented on or many kernels, lotta work it seems.
Ask .torrented. He made a s2w kernel a few months ago. He may have a very busy schedule but if enough people ask he may do it.
jamiethemorris said:
Okay, here's a dumb question... Right now we share the AOSP kernel source with the HTC One. Wouldn't flashing a custom AOSP kernel for the One work on the DNA?
Click to expand...
Click to collapse
Yeah I Dont think it's that simple unfortunately.
Sent from my HTC6435LVW using Tapatalk
I don't think one of those kernels would be difficult to port though. I'm just wondering what exactly makes the kernels different, because if you compare the CyanogenMod pages for the DNA and the One, the kernel source link is for the M7 on both of them. I was considering trying to port a kernel myself a while back, but I couldn't find enough information online about it... I think it may be one of those things where if you have enough knowledge of ROM building and git than you just intuitively know how to do it.
Sent from my Droid DNA using Tapatalk Pro
jamiethemorris said:
I don't think one of those kernels would be difficult to port though. I'm just wondering what exactly makes the kernels different, because if you compare the CyanogenMod pages for the DNA and the One, the kernel source link is for the M7 on both of them. I was considering trying to port a kernel myself a while back, but I couldn't find enough information online about it... I think it may be one of those things where if you have enough knowledge of ROM building and git than you just intuitively know how to do it.
Sent from my Droid DNA using Tapatalk Pro
Click to expand...
Click to collapse
Yeah I'm not sure either. If you wanted to give it a run for your money I'm sure palmer would give you some pointers. I would love to see a dt2w kernel!! Lol
Sent from my HTC6435LVW using Tapatalk
I couldn't resist, I just had to try it. I figured the worst that would happen is I'd have to reflash my ROM. So I flashed the HTC one sti kernel here: http://forum.xda-developers.com/showthread.php?t=2507710 it flashed and booted just fine and everything works... None of the s2w dt2w features etc are working but it said it flashed successfully so I'm assuming it's running the kernel... I don't remember what it said in about phone before but it currently shows "3.4.10-CM-gbce7128 Robert @ minty #1."
Edit: yeah I'm pretty sure that's the stock kernel...
It was worth a try right?
@crpalmer would you be willing to give me some pointers on porting or building a kernel? I'm somewhat inexperienced with building, so I don't know if I should bother taking on a task like this.
Sent from my Droid DNA using Tapatalk Pro
coachcrey said:
Yeah I'm not sure either. If you wanted to give it a run for your money I'm sure palmer would give you some pointers. I would love to see a dt2w kernel!! Lol
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
Do not, really, do NOT flash a kernel for a different phone. The Linux kernel is setup to have the same core files across a huge number of devices but then have device specific files. We share the M7 kernel but we have different device specific files. These files control lots of things but the most important is determining what pieces of hardware are given specific voltages, etc.
If you want to try to build my kernel, you should be able to do so fairly easily. Porting the functionality will require some programming knowledge and some knowledge of git. If you think you can do it, let me know and I'll try to give you some first steps on building my kernel.
Porting a M7 kernel to our device might be hard. There is a high probability that they aren't necessarily keeping up-to-date on the changes to our device specific files. You'd have to figure out if they were and, if not, pull in the missing changes.
crpalmer said:
Do not, really, do NOT flash a kernel for a different phone. The Linux kernel is setup to have the same core files across a huge number of devices but then have device specific files. We share the M7 kernel but we have different device specific files. These files control lots of things but the most important is determining what pieces of hardware are given specific voltages, etc.
If you want to try to build my kernel, you should be able to do so fairly easily. Porting the functionality will require some programming knowledge and some knowledge of git. If you think you can do it, let me know and I'll try to give you some first steps on building my kernel.
Porting a M7 kernel to our device might be hard. There is a high probability that they aren't necessarily keeping up-to-date on the changes to our device specific files. You'd have to figure out if they were and, if not, pull in the missing changes.
Click to expand...
Click to collapse
I wasn't implying anybody should ever flash a kernel not built for this phone.
Sent from my HTC6435LVW using Tapatalk
coachcrey said:
I wasn't implying anybody should ever flash a kernel not built for this phone.
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
My bad. I quoted the wrong post! I just wanted to make sure it was clear that the same source is not the same as safe to flash because we have completely different hardware configuration. So, I guess it was good that I misquoted so that I have a chance to say it a second time!
crpalmer said:
My bad. I quoted the wrong post! I just wanted to make sure it was clear that the same source is not the same as safe to flash because we have completely different hardware configuration. So, I guess it was good that I misquoted so that I have a chance to say it a second time!
Click to expand...
Click to collapse
OK right in man. Thanks for all the hard work.
Sent from my HTC6435LVW using Tapatalk
I guess my post didn't go through... @crpalmer what type of programming knowledge are we taking about? My knowledge is limited to some dsdt editing and supercollider... In other words, I'm definitely not a programmer but I understand the general concepts.
Edit: I'm not too experienced with git either but I have built cm10.1 From the source for my nexus 7 a few just as learning experience.
Sent from my Droid DNA using Tapatalk Pro
Hey guys,
First off. Mahdi rom is Amazing! I love all the features and it had just the right amount of features for my new G2! Thanks Doc for maintaining this for us!
Second, I am a kernel dev and am working on my own kernel for the G2. I have essentially made my base Savoca's Furnace Kernel (With his permission of course) and will be adding in features as I go. Currently I build for the Moto G but wanted to buy a higher end device and love this phone. I have the D800 (AT&T) so as it stands I only have a test kernel for the D800/JDI. You may be able to use Savoca's new panel tool that you flash after flashing the kernel to swap screen support. I would love for some others to test it out and let me know. I will be bringing a different perspective to kernel Dev'n than normal. I like to be hands on about the process and to instigate discussion so others can learn. Let me know if anyone is interested.I will be building for all variants that Furnace kernel supports.
Note to ALL: I will open an official thread when I am satisfied with testing. Thanks for your interest! Hope I can bring something new to the G2!
Right now I have added:
Custom Hotplug from Blechd0se (Moto G) Falcon Hotplug - Ultra simplified and efficient.
Sl(auo)b optimizations
frandom
ETC
Check source for more indepth info!
Just pm me if you are interested. Everything looks to be going pretty good so I should be opening a thread pretty soon. Remember this is still in Beta. Still I would love to hear from others out there. Thanks!
Render-Kernel-AOSP_d800-06-29-BR3-JDI.zip
Render-Kernel-AOSP_vs980-06-29-BR3-LGD.zip
Render-Kernel-AOSP_d800-07-01-BR3-LGD.zip
Render-Kernel-AOSP_d802-07-01-BR3-LGD.zip
Kind Regards,
Render
Source
kk-test is my active branch right now
Glad to see you here! I'll test out VS980 when you start building the other variants ?
JRJ442 said:
Glad to see you here! I'll test out VS980 when you start building the other variants ?
Click to expand...
Click to collapse
I will go ahead and rip you a build. Give me a sec . . .
JDI?
RenderBroken said:
I will go ahead and rip you a build. Give me a sec . . .
JDI?
Click to expand...
Click to collapse
LGD
JRJ442 said:
LGD
Click to expand...
Click to collapse
OK Give me a tick and I will build it. Should not take long.
Nice, love devs being able to jump in on the g2. Glad your here. The link you posted for the d800....should that work on aicp...?
Sent from my LG-D800 using XDA Premium 4 mobile app
jeff5347 said:
Nice, love devs being able to jump in on the g2. Glad your here. The link you posted for the d800....should that work on aicp...?
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Not 100% sure but give it a try. Should hurt anything. I am fairly new to the G2 and don't know every single in and out yet. I do know that the source base is pretty fractured but I am hoping to bridge the gap a bit. Let me know so I can let others know in the future. Thanks!
OK just flashed. Booted fine but froze and that is my fault
..I started playing around and enabled intellidemand. From what I remember for some reason that gov is a problems. Rebooted and left the kernel stock. Now running fine and no problems. I'll update on battery and perf.
Sent from my LG-D800 using XDA Premium 4 mobile app
JRJ442 said:
LGD
Click to expand...
Click to collapse
OK Built and posted in OP#1
jeff5347 said:
OK just flashed. Booted fine but froze and that is my fault
..I started playing around and enabled intellidemand. From what I remember for some reason that gov is a problems. Rebooted and left the kernel stock. Now running fine and no problems. I'll update on battery and perf.
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Great, Thanks for the info, I will most likely be removing it anyways. I have inherited Savoca's source and am laying mine down ontop. He did all the amazing groundwork that will allow me to support numerous devices much much sooner. Thanks and let me know how it continues to work for you!
@RenderBroken booted up just fine. Running smooth. I'll report back tomorrow as well. Thanks again for building for us. ?
Render, since I cleaned the kernel and left it stock I'm getting the SOD. If I let the screen go off and try to turn the screen back on it just lights up black. Tried and tried but just a black screen. Unfortunately I had to go back for now. Can't wait to try it once it gets cleaned up.
Sent from my LG-D800 using XDA Premium 4 mobile app
Link to source ?
I looked at Savoca source and it appeared to have no FM support in audio driver, same as Mahdi now.
I'll copy my post from Mahdi thread, in case your interested in enabling FM:
I've concluded that sound/soc/msm/msm8974.c needs to be patched with the "#ifdef CONFIG_SND_FM_RADIO" code seen here: https://github.com/CyanogenMod/android_kernel_lge_msm8974/blob/cm-11.0/sound/soc/msm/msm8974.c
Unless you're up for that, I'll presume I'll try it myself.
Any tips for kernel building for a JDI LS980 ? I built a few Android kernels in 2013, but never even tried flashing them.
That said, I've been doing embedded linux professionally since 1997.
Thanks !
1 question. Why didn't you post the kernel in one of the development sections??
Transmitted via Geass
At first it could be in Original Dev section. I can test something on d802 LGD. @mikereidis u have a G2? if yes then it's great to see more devs here
RenderBroken said:
Not 100% sure but give it a try. Should hurt anything. I am fairly new to the G2 and don't know every single in and out yet. I do know that the source base is pretty fractured but I am hoping to bridge the gap a bit. Let me know so I can let others know in the future. Thanks!
Click to expand...
Click to collapse
hi, thank you for supporting our beloved g2 we all appreciate it, i just have a request. you see , only the Qremote can control the IR on our device, lg didnt use the real android open source drivers for it . so we cant use apps like smartIR whereas samsung n htc are compatible. im just suggesting if you can try and implement open source IR drivers to the g2 ? so that we can use all these apps that utilize that api i know this is gonna be an insanely though part as you'd have to figure out which hw IR we are using and then implement a compatible driver for it. but im just suggesting that this is perhaps the only bad part of the g2 till now
Super Post!
jeff5347 said:
Render, since I cleaned the kernel and left it stock I'm getting the SOD. If I let the screen go off and try to turn the screen back on it just lights up black. Tried and tried but just a black screen. Unfortunately I had to go back for now. Can't wait to try it once it gets cleaned up.
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Then it sounds like you don't have LDG like you said but you have JDI.
mikereidis said:
Link to source ?
I looked at Savoca source and it appeared to have no FM support in audio driver, same as Mahdi now.
I'll copy my post from Mahdi thread, in case your interested in enabling FM:
I've concluded that sound/soc/msm/msm8974.c needs to be patched with the "#ifdef CONFIG_SND_FM_RADIO" code seen here: https://github.com/CyanogenMod/android_kernel_lge_msm8974/blob/cm-11.0/sound/soc/msm/msm8974.c
Unless you're up for that, I'll presume I'll try it myself.
Any tips for kernel building for a JDI LS980 ? I built a few Android kernels in 2013, but never even tried flashing them.
That said, I've been doing embedded linux professionally since 1997.
Thanks !
Click to expand...
Click to collapse
I will go ahead and push the latest changes and post link. Also I am fairly new to the G2 scene and just how fractured the source code is for it. I would love to take a look at this if its simple enough to add in. I am not against trying though. If you could, remind me when I open up the main thrad in the next few days. I am heading to the beach with my wife and son so will not be able to do much in the next 2 days but when I get back and I get some good word about the builds, I will open the thread and kick in to overdrive.
Ace42 said:
1 question. Why didn't you post the kernel in one of the development sections??
Transmitted via Geass
Click to expand...
Click to collapse
Just wanted some testers for now. I dont want to open a thread to a million questions about each device yet when I don't have a kernel ready for them. I will be creating a thread very soon.
shriom_manerker said:
hi, thank you for supporting our beloved g2 we all appreciate it, i just have a request. you see , only the Qremote can control the IR on our device, lg didnt use the real android open source drivers for it . so we cant use apps like smartIR whereas samsung n htc are compatible. im just suggesting if you can try and implement open source IR drivers to the g2 ? so that we can use all these apps that utilize that api i know this is gonna be an insanely though part as you'd have to figure out which hw IR we are using and then implement a compatible driver for it. but im just suggesting that this is perhaps the only bad part of the g2 till now
Click to expand...
Click to collapse
I like challenges, I will take a look as soon as I can. Most likely it will be after I get everything completely setup. If you could remind me later when I open up the official thread. Thanks!
Planning d801?
RenderBroken said:
I like challenges, I will take a look as soon as I can. Most likely it will be after I get everything completely setup. If you could remind me later when I open up the official thread. Thanks!
Click to expand...
Click to collapse
im experienced at coding, c,java,html and php. i ahve compiled kernels in the past but that was like 4 years ago.ill try my best to help you. although ill need your help too.
I've looked under terminal and it states I have a lgd. Flashed savacos older kernels that were lgd and they all worked fine. I get no black lines just when I shut the screen off it comes on but full black.
Sent from my LG-D800 using XDA Premium 4 mobile app
jamesd1085 said:
Planning d801?
Click to expand...
Click to collapse
I planning for all variants.
shriom_manerker said:
im experienced at coding, c,java,html and php. i ahve compiled kernels in the past but that was like 4 years ago.ill try my best to help you. although ill need your help too.
Click to expand...
Click to collapse
Great, I love to collaborate. That's the best way to learn! Thanks for the offer. My Google hangouts is
[email protected]
jeff5347 said:
I've looked under terminal and it states I have a lgd. Flashed savacos older kernels that were lgd and they all worked fine. I get no black lines just when I shut the screen off it comes on but full black.
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Weird, I am pretty certain I build to LGD variant. Sorry brother. Try using Savoca's panel changer that you flash after the kernel. I even used Savoca's build script so not sure what the problem is but I am pretty sure that it's not a SoD problem you are having but a panel issue.