So i decided to Start this topic because of actually given destrictions of using and sharing a kernel,which Source Code is closed Source.actually it will affect our device in that way,that only ics could be compiled and shared... So I think we should build a kernel by ourselves,not by recompiling a OEM Source Kernel,but by deving from scratch.All related Files were given by ics Source Code
Sent from my HTC Desire X using xda premium
Our device is said to be fully backward compatible with msm7x27a or 7x25a devices ,in Software and Hardware.So it cannot to heavy to dev own aosp Kernel ,which cozld pass jb or in Future new releases
Sent from my HTC Desire X using xda premium
So really no Dev there,who has enough knowledge to build a kernel from e.g. caf-sources?
Sent from my HTC Desire X using xda premium
greeneyes2910 said:
So really no Dev there,who has enough knowledge to build a kernel from e.g. caf-sources?
Sent from my HTC Desire X using xda premium
Click to expand...
Click to collapse
We can build it, but you won't be able to boot your phone with that kernel.
atis112 said:
We can build it, but you won't be able to boot your phone with that kernel.
Click to expand...
Click to collapse
how successful were you with your JB CM10.1 kernel? this must be so frustrating for you
So why are could not boot with such kernel? Every Board have its own made board files e.g. Htc Bravo... The Aosp board files are free build by cyanogen for e.g
greeneyes2910 said:
Our device is said to be fully backward compatible with msm7x27a or 7x25a devices ,in Software and Hardware
Click to expand...
Click to collapse
No, it's not. The SoC is designed to make upgrading a msm7x27a-based device easy; there's no need to alter the rest of the hardware or PCB. So the pin-out (and a few other details) are backwards compatible. This is useful to phone manufacturers, since re-designing hardware and PCB's (and getting it re-certified) is a time consuming affair; being able to upgrade a phone model just by replacing the SoC is a huge time saver and allows manufacturers to introduce a stop-gap upgrade model easily and cheaply.
However, this does not imply any compatibility with the software.Software is cheap to modify, especially in the case of an Android phone.
To draw a (perpetually flawed) car-analogy: Back in the day, you could swap the engine of a VW beetle with the engine of a Porsche with relatively little effort, as the mounting points, engine bay size and drive shaft location were roughly the same. (hardware compatibility). However, this doesn't mean the resulting car has the same performance, handling or fuel efficiency as the original beetle, and the driver had better be aware of the more powerful engine and take approriate caution (But no software compatibility).
Ok that seems clear, but why is it such a problem to bring a kernel aosp ?
greeneyes2910 said:
Ok that seems clear, but why is it such a problem to bring a kernel aosp ?
Click to expand...
Click to collapse
Because HTC (or indeed Qualcomm) made modifications to the Linux kernel, and they haven't disclosed those changes yet. Without those changes, it is nigh impossible to reproduce the kernel as shipped by the current JB rom, let alone make a modified version.
This wouldn't have been such a pain in the rear end if Qualcomm wasn't so restrictive with the amount of information they supply. In order to be able to make a kernel (AOSP has little to do with this), we need the changes HTC (or Qualcomm) made, either
By waiting until HTC releases the source code (Will probably happen at some point, but will take a while)
By reverse-engineering the changes they made to the previous kernel, and porting them to the new 3.4.0 kernel - which is a gargantuan task, and offers little guarantee for success.
We can port a kernel from a similar phone like pico guys did
Yeah something like this was my intension, because such boards or bravo, dhd, desire s, etc, are all don have original kernel sources. so this is exact same to our dx . What makes protou so different to all other devices? anyway, as in fact, that a kernel is compiled from sources (including spezific needed board files etc) it must be possible to recompile a kernel to its sources...
Its ok to wait for HTC Sources already but it also should be clear, that further apis , android os, or real development, would never be possible, when Htc decided that protou will not be upgradeble in future.
greeneyes2910 said:
Yeah something like this was my intension, because such boards or bravo, dhd, desire s, etc, are all don have original kernel sources. so this is exact same to our dx . What makes protou so different to all other devices? anyway, as in fact, that a kernel is compiled from sources (including spezific needed board files etc) it must be possible to recompile a kernel to its sources...
Its ok to wait for HTC Sources already but it also should be clear, that further apis , android os, or real development, would never be possible, when Htc decided that protou will not be upgradeble in future.
Click to expand...
Click to collapse
But it would be really difficult to port a kernel for our phone cuz we have really less no of devs. Even if we had 5 proper devs then we could have made it.
Sent from my HTC Desire X using xda app-developers app
prototype-U said:
But it would be really difficult to port a kernel for our phone cuz we have really less no of devs. Even if we had 5 proper devs then we could have made it.
Sent from my HTC Desire X using xda app-developers app
Click to expand...
Click to collapse
We appreciate the hard work everybody does here, and we are always grateful. Do not feel pressured into doing something just because everybody else wants it
) > Galaxy 3 Android Development > [script] repack-zImage.sh: Unpack and repack a zImage without kernel source, V. 5
So this is nearly exactly what I mean and should be possible with our Kernel
Sent from my HTC Desire X using xda premium
greeneyes2910 said:
) > Galaxy 3 Android Development > [script] repack-zImage.sh: Unpack and repack a zImage without kernel source, V. 5
So this is nearly exactly what I mean and should be possible with our Kernel
Click to expand...
Click to collapse
I assume you're referring to this thread. I fail to see how this will help though, as this is unrelated to the kernel source in any way, shape or form. It merely extracts the initial ramdisk.
But it says that it is possible to decompile a zimage.
So it must be possible to get Board Files from it
Sent from my HTC Desire X using xda premium
greeneyes2910 said:
But it says that it is possible to decompile a zimage.
Click to expand...
Click to collapse
It doesn't.
that s wrong. it is already possible...But that is not needed. all compiled files from kernel should be located anywhere on device
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.
Hey guys,
Could you explain to me in an accessible way, why the exynos source code is so important for the development of custom roms?
We have a multitude of rooms already, how were they build? If no official sources are available, are custom roms in any way inferior to Samsung stock android (eg lacking hardware video acceleration, heavier battery drain, non-functioning ports/radio, etc. )
Does the code have to be released periodically in a best case scenario by Samsung, ie. with any major android or firmware update, or is it a one-time thing?
And finally, can devs do something with the source code that was recently released by Samsung?
You probably will instantly recognise that I have no programming background, so apologies in advance if this sounds stupid
A simple way to understand is this..
Just how with every new update of windows you need updated drivers to get the graphics card, audio etc working same way we need certain drivers for the chips inside the phone. Since these are designed by Samsung they control the right to not allow others to know the design of these chips. That's why they won't make it open source instead release these drivers so that custom ROM builders can use it.
Currently these drivers have not been released for jellybean so the phone won't perform in optimal way. Till they release it we will be using previous drivers along with clever fixes by the developers.
Sent from my GT-I9100 using xda app-developers app
iamanoopmk said:
Currently these drivers have not been released for jellybean so the phone won't perform in optimal way. Till they release it we will be using previous drivers along with clever fixes by the developers.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Thanks- this really helps. So that means we have the official and fully functional drivers in CM9, but only through workarounds can the devs get them to work in, for example, Jelly bean based CM10?
They are doing the exact same thing in CM10 and CM10.1
They have used old ones and some fixes to compensate. That is why CM10 is smooth but not as much as original JB
Sent from my GT-I9100 using xda app-developers app
Hello!
Would it be possible to port one of the Jellybean ROMs available for the Desire X to devices that use the same H/W (the device in question would be the Huawei Ascend G600)? If yes, how would one go about doing it?
Thanks in advance!
You want to port desire x sense jb Rom or aosp ?
Because porting sense would be near impossible
And,
We don't have any jelly bean aosp Rom so nothing to port actually
Sent from my HTC Desire X using xda app-developers app
Either would do, at least in my case - I primarily wish to get Jellybean on my phone. Might I ask why porting Sense-based ROMs would be prohibitively difficult?
shadeMe said:
Either would do, at least in my case - I primarily wish to get Jellybean on my phone. Might I ask why porting Sense-based ROMs would be prohibitively difficult?
Click to expand...
Click to collapse
I see Sense 4.1 ported to the S III Goodluck with that maybe ask help from that guy in the SIII part of XDA if you want Sense Its very hard because of different sense components especially framework and kernel drivers sense is Hardware dependent based of my knowing
I see. But the reason I posted this question here was because I was under the impression that the Desire X is, in fact, kernel compatible with the G600. Both of them use the same SOC (Qualcomm MSM8225).
shadeMe said:
I see. But the reason I posted this question here was because I was under the impression that the Desire X is, in fact, kernel compatible with the G600. Both of them use the same SOC (Qualcomm MSM8225).
Click to expand...
Click to collapse
They are.
But the fact is, you have nothing to port. YET. Stay tuned, people are working hard.
neXus PRIME said:
They are.
But the fact is, you have nothing to port. YET. Stay tuned, people are working hard.
Click to expand...
Click to collapse
Point taken
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