[Q] Can I get the Google edition? - One (M7) Q&A, Help & Troubleshooting

Hi, Today the Google edition kernel became availble one htcdev.com
http://www.htcdev.com/devcenter/downloads
can I use this on my regular HTC One? if yes how can I do it?
Thank you

Roms will be out soon enough after a dump is given ...but for the time being we have kernel source so devs can implement Google's fixes into their Roms to make pretty much bugless roms

a box of kittens said:
Roms will be out soon enough after a dump is given ...but for the time being we have kernel source so devs can implement Google's fixes into their Roms to make pretty much bugless roms
Click to expand...
Click to collapse
Thank you, I'll wait for the ROMs Then.

Related

3.0 Kernel for AOSP JB?

I've been using Codename ever since it came out but I got tired of the problems related to the Kernel and switched to ProjectX. I and I'm sure others really want to use a smooth and working JB ROM.
Is there anyone working on the 3.0 Kernel for our device? I know Nik said he contacted someone to help us out but there's been no news on that front yet.
If anyone knows how to modify Kernels, Adi_pat gave some tips here -
http://forum.xda-developers.com/showthread.php?p=33291894
He'll probably help us out if we make some progress in booting up Codename with it at least
TheDareDevil said:
I've been using Codename ever since it came out but I got tired of the problems related to the Kernel and switched to ProjectX. I and I'm sure others really want to use a smooth and working JB ROM.
Is there anyone working on the 3.0 Kernel for our device? I know Nik said he contacted someone to help us out but there's been no news on that front yet.
If anyone knows how to modify Kernels, Adi_pat gave some tips here - http://forum.xda-developers.com/showthread.php?t=1899335&page=38
He'll probably help us out if we make some progress in booting up Codename with it at least
Click to expand...
Click to collapse
Upon the exit of JB roms ago, were used GB modified kernel, now with source code maybe will be possible to compile a fully working kernel, but afaik there are no 3.x kernel for JB, maybe someone is working out of xda on irc channel but don't known..
Sadly I do not have much competence, plus I don't have the phone it's to repair....
There is kernel 3 for incredible 2 and desire s..may be someone can port it..
Sent from my HTC Incredible S using xda app-developers app
I might be crazy, but I remember reading a post not too long ago about a dev that was writing the 3.0 kernel from source for our phones. I haven't heard an update since then, but I remember hearing it was someone with relation to the cm9 team. It sounded promising, but that development was very slow.
Sent from my HTC Incredible S using xda app-developers app
TheMegosh said:
I might be crazy, but I remember reading a post not too long ago about a dev that was writing the 3.0 kernel from source for our phones. I haven't heard an update since then, but I remember hearing it was someone with relation to the cm9 team. It sounded promising, but that development was very slow.
Sent from my HTC Incredible S using xda app-developers app
Click to expand...
Click to collapse
Off the top of my head I seem to recall Noverbose saying he was trying to write a 3.0 Kernel. I also remember at least one other person mentioning something similar to, so there are people working on this. From what I understand it's not easy - I doubt we'll see anything this side of Christmas tbh. I hadn't realised that the Inc 2 and DS had a 3.0 Kernel though. Anyone know if they are actually a made from source version, rather than the same hacked version that we have in Codename, for example?
Well tbh honest a working GB kernel would do too.
Like the front camera and chrome and screen flickering etc.
Damn I wish kaijura was here
Sent from my HTC Incredible S using xda app-developers app
CyanideJack said:
Off the top of my head I seem to recall Noverbose saying he was trying to write a 3.0 Kernel. I also remember at least one other person mentioning something similar to, so there are people working on this. From what I understand it's not easy - I doubt we'll see anything this side of Christmas tbh. I hadn't realised that the Inc 2 and DS had a 3.0 Kernel though. Anyone know if they are actually a made from source version, rather than the same hacked version that we have in Codename, for example?
Click to expand...
Click to collapse
Yes those 3.0 kernels are compiled from source. I checked out AOSP ROM threads in the Desire S and Inc 2 section that had 3.0 kernel, then looked up the creator of the ROM on github and found the sources. I was going to try tackle the 3.0 kernel to get a hang of the make system before building CM9, but I don't have enough monthly data left to download the kernel toolchain! Nov 1st is close, so I can get to work soon! :highfive:
The best way to build an AOSP 3.0 kernel for our device would probably be to look at the source code for 3.0 kernels on our sister devices, and figure it out from there.
ZaySk said:
Yes those 3.0 kernels are compiled from source. I checked out AOSP ROM threads in the Desire S and Inc 2 section that had 3.0 kernel, then looked up the creator of the ROM on github and found the sources. I was going to try tackle the 3.0 kernel to get a hang of the make system before building CM9, but I don't have enough monthly data left to download the kernel toolchain! Nov 1st is close, so I can get to work soon! :highfive:
The best way to build an AOSP 3.0 kernel for our device would probably be to look at the source code for 3.0 kernels on our sister devices, and figure it out from there.
Click to expand...
Click to collapse
Well holy crap, dude, get on that! Seriously though, getting a working 3.0 kernel for our device would go a long way to making JB a usable ROM for our device. Would it be possible to port JellyTime or a similar JB ROM to our device as well?
The source doesn't need changing, it is the ramdisk that is the problem. I have been trying to get help, but so far no luck, adi_pat said he would take a look, but it is hard for me to test as I no longer have an inc s
CyanideJack said:
Well holy crap, dude, get on that! Seriously though, getting a working 3.0 kernel for our device would go a long way to making JB a usable ROM for our device. Would it be possible to port JellyTime or a similar JB ROM to our device as well?
Click to expand...
Click to collapse
I'm gonna worry mainly about compiling CM9 from source once November hits, that's gonna take up the majority of my time. After I get the first release of CM9 out, I'll start work on a 3.0 kernel if it hasn't been done yet. I have no experience whatsoever dealing with kernels though, except for small ramdisk edits, so don't expect any miracles.
It should be possible to port other JB ROM's over using one of nik's ported JB ROM's as a base and reference point, the only problem is I don't know exactly what files I have to substitute to port a ROM. I've PM'd nik about that a few hours ago, so hopefully I'll get some more information on the subject. Nik has been a big help to my dev efforts as a whole.
l0st.prophet said:
The source doesn't need changing, it is the ramdisk that is the problem. I have been trying to get help, but so far no luck, adi_pat said he would take a look, but it is hard for me to test as I no longer have an inc s
Click to expand...
Click to collapse
Interesting, if it's only the ramdisk that needs changing, couldn't you look at the ramdisk from one of niks JB ROM's? Or is it not as simple as that? I'm assuming the latter, seeing as if it were that obvious I'm sure someone would've done it by now. If you ever need help testing, send me a PM I'd be more than willing to test for you.
ZaySk said:
I'm gonna worry mainly about compiling CM9 from source once November hits, that's gonna take up the majority of my time. After I get the first release of CM9 out, I'll start work on a 3.0 kernel if it hasn't been done yet. I have no experience whatsoever dealing with kernels though, except for small ramdisk edits, so don't expect any miracles.
It should be possible to port other JB ROM's over using one of nik's ported JB ROM's as a base and reference point, the only problem is I don't know exactly what files I have to substitute to port a ROM. I've PM'd nik about that a few hours ago, so hopefully I'll get some more information on the subject. Nik has been a big help to my dev efforts as a whole.
Interesting, if it's only the ramdisk that needs changing, couldn't you look at the ramdisk from one of niks JB ROM's? Or is it not as simple as that? I'm assuming the latter, seeing as if it were that obvious I'm sure someone would've done it by now. If you ever need help testing, send me a PM I'd be more than willing to test for you.
Click to expand...
Click to collapse
About using one of Nik's JB roms as a reference
What I understood was that the rom has been built around the old 2.6.x kernel and has to be modified again to work with the 3.0.x kernel, if you guys get one up and running. If that is the case, wouldn't you be going down the wrong path if you model it around nik's existing 2.6.x roms?
We need kaijura here, he was our AOSP kernel master. Hopefully he is doing ok, and has found something else other than xda because he hasn't been online for months. At least other devs, like lordclokan and kali- have moved on and are active with other devices... kaijura hasn't been on at all. Anyone been in contact with him/her?
markj338 said:
About using one of Nik's JB roms as a reference
What I understood was that the rom has been built around the old 2.6.x kernel and has to be modified again to work with the 3.0.x kernel, if you guys get one up and running. If that is the case, wouldn't you be going down the wrong path if you model it around nik's existing 2.6.x roms?
We need kaijura here, he was our AOSP kernel master. Hopefully he is doing ok, and has found something else other than xda because he hasn't been online for months. At least other devs, like lordclokan and kali- have moved on and are active with other devices... kaijura hasn't been on at all. Anyone been in contact with him/her?
Click to expand...
Click to collapse
I know, it would be going down a pretty redundant path. If I was able to port over a JB ROM using nik's ROM's as a base, then my ported ROM would inherit all the same bugs nik's ROM's already have.
I wish kaijura was still around, I have so many questions I want to ask about compiling from source! Luckily lordclokan was a massive help to me in that regard. Kaijura's github hasn't seen action in months either, sadly.
Forgive my ignorance, but isn't the Desire HD essentially our device with a bigger screen and less memory? That being the case, could we not just port across one of the 3.0 Kernels from that?
The problem with the ramdisk that come with the official ROM's that have 3.0 kernels, is that they are built for the sense framework and don't work on AOSP ROM's. The ram disk that is included with Nik's JB ROM's is heavily modified to run a GB kernel with ICS / JB sources, so the problem is I don't have a base to work from, I am basically trying to merge the two init's to make the 3.0 kernel boot.
Saying that we need to port 3.0 kernel is probably a bit misleading, and for that I apologise, the kernel itself has very little Sense specific stuff, it's the ramdisk that is responsible for launching the kernel that is the issue here at the moment.
The only problem with the desire HD kernel would be that our front camera would not work
+ I forgot to link to adi_pat's post - http://forum.xda-developers.com/showthread.php?p=33291894
Sent from my HTC Incredible S using xda app-developers app
l0st.prophet said:
The problem with the ramdisk that come with the official ROM's that have 3.0 kernels, is that they are built for the sense framework and don't work on AOSP ROM's. The ram disk that is included with Nik's JB ROM's is heavily modified to run a GB kernel with ICS / JB sources, so the problem is I don't have a base to work from, I am basically trying to merge the two init's to make the 3.0 kernel boot.
Saying that we need to port 3.0 kernel is probably a bit misleading, and for that I apologise, the kernel itself has very little Sense specific stuff, it's the ramdisk that is responsible for launching the kernel that is the issue here at the moment.
Click to expand...
Click to collapse
Well you can prolly get ideas from adi ( he posted http://forum.xda-developers.com/showpost.php?p=33302707&postcount=387 not sure if you saw it) he seems to know what's up.
TheDareDevil said:
The only problem with the desire HD kernel would be that our front camera would not work
+ I forgot to link to adi_pat's post - http://forum.xda-developers.com/showthread.php?p=33291894
Sent from my HTC Incredible S using xda app-developers app
Click to expand...
Click to collapse
So it looks like the furthest things got regarding a 3.0 Kernel was;
Adi_Pat said:
chan
Ok so 2.6.35 works with Jellybean. Why not pack the ramdisk with zImage compiled from 3.0.y sources(Considering you are using standard boot.img format[?]) Because to get it to boot, you would not require any hacks/changes to source, editing ramdisk(init.rc) is enough to make it boot initally.
EDIT: You may also need to change init binary.
Click to expand...
Click to collapse
l0st.prophet said:
The problem with the ramdisk that come with the official ROM's that have 3.0 kernels, is that they are built for the sense framework and don't work on AOSP ROM's. The ram disk that is included with Nik's JB ROM's is heavily modified to run a GB kernel with ICS / JB sources, so the problem is I don't have a base to work from, I am basically trying to merge the two init's to make the 3.0 kernel boot.
Saying that we need to port 3.0 kernel is probably a bit misleading, and for that I apologise, the kernel itself has very little Sense specific stuff, it's the ramdisk that is responsible for launching the kernel that is the issue here at the moment.
Click to expand...
Click to collapse
Very interesting, thanks for the informative post. :good:
zaysk said:
very interesting, thanks for the informative post. :good:
Click to expand...
Click to collapse
happy november!!!
markj338 said:
happy november!!!
Click to expand...
Click to collapse
A very happy November indeed

[Q] Are there any Sense JB Rom?

Hi All,
Still sense rom with Jelly Bean not released right? Is it not possible at all? I know if it was possible devs would have made it.. but still.. many HTC handsets got JB update,.. why not any port to our phone..
I am on MiUi JB rom and certainly miss sense as its still on ICS..
Rah0ol said:
Hi All,
Still sense rom with Jelly Bean not released right? Is it not possible at all? I know if it was possible devs would have made it.. but still.. many HTC handsets got JB update,.. why not any port to our phone..
I am on MiUi JB rom and certainly miss sense as its still on ICS..
Click to expand...
Click to collapse
I'd suggest you do a snooping around in the Development Forums first, but because there are a lot of ROMs in which it was discussed, Ill just tell you here.
To put it simply, it is possible but quite difficult. It is possible to have Jellybean Sense running on our device but A LOT of kernel work has to be done. JellyBean kernels require something call Ion. Some devices support it natively (like the newer ones) while others like our device, does not support it natively, and as a result, there are some conflicts, the most common and widely known is probably the camera breaking. Some libs and modules need to be fixed/replaced in order for the Jellybean ROM to work.
But patience, if a dev has the time, maybe he/she will work on a Jellybean Sense kernel for us.
072665995 said:
I'd suggest you do a snooping around in the Development Forums first, but because there are a lot of ROMs in which it was discussed, Ill just tell you here.
To put it simply, it is possible but quite difficult. It is possible to have Jellybean Sense running on our device but A LOT of kernel work has to be done. JellyBean kernels require something call Ion. Some devices support it natively (like the newer ones) while others like our device, does not support it natively, and as a result, there are some conflicts, the most common and widely known is probably the camera breaking. Some libs and modules need to be fixed/replaced in order for the Jellybean ROM to work.
But patience, if a dev has the time, maybe he/she will work on a Jellybean Sense kernel for us.
Click to expand...
Click to collapse
Thanks a lot for the explanation. So the Kernel is the issue here for the JB sense ROM development. I will just have to wait for the kernel to be developed..
and yeah snooping around the Dev forum, I am a mad flasher.. I have flashed all the firmware that are currently released for HTC on the dev forum and have played around with all dude
Was patiently waiting for a JB sense.. Guess I have to wait more..
Thanks a lot for the detailed explaination..
Brilliant explanation by 072665995, but dont get your hopes up guys
The Epik Dude said:
Brilliant explanation by 072665995, but dont get your hopes up guys
Click to expand...
Click to collapse
Agreed, brilliant explanation.
Yeah seriously!! Sense is so awesome that release of new version of JellyBean just makes its so expected to have a sense version of it. Bad that we face an issue in achieving that..

Stupid question about custom roms and kernels

Aside from installing what other devs make, I've never really been a part of the Android dev scene, despite being a programmer (mostly web dev and interpreted languages) myself. I'm not sure if its my inexperience or naivete talking, but isn't technically possible to compile AOSP with the kernel source Motorola posted and install that on a Moto X with an unlocked bootloader? Is there any real roadblock between me and my own custom rom (besides my lack of a linux computer to compile everything on)?
mrbradeli said:
Aside from installing what other devs make, I've never really been a part of the Android dev scene, despite being a programmer (mostly web dev and interpreted languages) myself. I'm not sure if its my inexperience or naivete talking, but isn't technically possible to compile AOSP with the kernel source Motorola posted and install that on a Moto X with an unlocked bootloader? Is there any real roadblock between me and my own custom rom (besides my lack of a linux computer to compile everything on)?
Click to expand...
Click to collapse
I dont see why you would want to... It basically ships with AOSP and a couple Motorola apps.. Unless you mean to compile 4.3 or 4.4 when it releases. Compiling 4.2.2 for the X would be kinda useless...
kernozlov said:
I dont see why you would want to... It basically ships with AOSP and a couple Motorola apps.. Unless you mean to compile 4.3 or 4.4 when it releases. Compiling 4.2.2 for the X would be kinda useless...
Click to expand...
Click to collapse
Useless or not I want to get into the custom rom game. Compiling AOSP from the source and installing it is a great start.
mrbradeli said:
Useless or not I want to get into the custom rom game. Compiling AOSP from the source and installing it is a great start.
Click to expand...
Click to collapse
If you know that then porting 4.3 could be a good start.
kernozlov said:
If you know that then porting 4.3 could be a good start.
Click to expand...
Click to collapse
Well I'm certainly up to looking into it. Is it as simple as compiling 4.3 with the kernel motorola gave us?
mrbradeli said:
Well I'm certainly up to looking into it. Is it as simple as compiling 4.3 with the kernel motorola gave us?
Click to expand...
Click to collapse
I cant really help you with that. Im not a dev, just a long time android tinkerer who saw an unanswered thread I could provide a little insight in.

Android 4.4 ROM

When we will have available an android 4.4 rom ? Is someone working on this ?
SilentGTX said:
When we will have available an android 4.4 rom ? Is someone working on this ?
Click to expand...
Click to collapse
Hey, well we can get some pre-alpha 4.4 AOSP builds maybe, but these will definitely have bugs, i do believe adam has built a 4.4. omni rom but i don't know much about bugs/boot status etc.
We are still waiting for cyanogenmod to merge sources, however they have stated that they are in no rush to start dishing out 4.4 roms as they have only just sunken their teeth into 4.3 Roms, we will get them eventually, however any builds within the next few days will have little customization or lots of bugs, patience is all we have till then
I hope this answered your question, also, this needs to be in the Q&A section next time bro
Good evening.
penguin449 said:
Hey, well we can get some pre-alpha 4.4 AOSP builds maybe, but these will definitely have bugs, i do believe adam has built a 4.4. omni rom but i don't know much about bugs/boot status etc.
We are still waiting for cyanogenmod to merge sources, however they have stated that they are in no rush to start dishing out 4.4 roms as they have only just sunken their teeth into 4.3 Roms, we will get them eventually, however any builds within the next few days will have little customization or lots of bugs, patience is all we have till then
I hope this answered your question, also, this needs to be in the Q&A section next time bro
Good evening.
Click to expand...
Click to collapse
Yeah thank you very much , it was very helpful , sorry for the wrong section . I can't wait for Android 4.4 ROMs :fingers-crossed: Good evening .
SilentGTX said:
Yeah thank you very much , it was very helpful , sorry for the wrong section . I can't wait for Android 4.4 ROMs :fingers-crossed: Good evening .
Click to expand...
Click to collapse
Please understand that all the great things you've been hearing about android 4.4 wont apply to us for quite some time, what i mean by this is all the efficiency/ performance improvements will be somewhat mitigated buy bugs and firmware incompatibilities, these things take time for devs to work through, 4.3 still isnt mature enough on this device to call it stable.
I just don't want people to get overly excited by a 4.4 port, its improvements will come gradually.
JoinTheRealms said:
Please understand that all the great things you've been hearing about android 4.4 wont apply to us for quite some time, what i mean by this is all the efficiency/ performance improvements will be somewhat mitigated buy bugs and firmware incompatibilities, these things take time for devs to work through, 4.3 still isnt mature enough on this device to call it stable.
I just don't want people to get overly excited by a 4.4 port, its improvements will come gradually.
Click to expand...
Click to collapse
I understand , of course , but still I can't wait :victory:
Gonna join this group, too
4.4 sure is on its way for our device, BUT:
Google is removing more and more support for our device, as it already is pretty old. So we need to re-add everything.
Even if it's booting, we still need a lot of work in order to get the most important stuff working (like SurfaceFinger, Audio, and ofc also data/RIL)
So regarding 4.4, all I can say is: Have patience
BTW, Thread moved to Q&A section
JoinTheRealms said:
4.3 still isnt mature enough on this device to call it stable.
Click to expand...
Click to collapse
im using pa 3.99 rc2 wich is 4.3 and it is perfectly stable, has great performance and no big bugs, i use it as a daily driver and it is the most perfect rom i used on my p880 till date
~MaX~ said:
im using pa 3.99 rc2 wich is 4.3 and it is perfectly stable, has great performance and no big bugs, i use it as a daily driver and it is the most perfect rom i used on my p880 till date
Click to expand...
Click to collapse
Yes they are functionally stable to a user, but to call a rom stable (at least by Cyanogenmods standards) requires more than that.
JoinTheRealms said:
Yes they are functionally stable to a user, but to call a rom stable (at least by Cyanogenmods standards) requires more than that.
Click to expand...
Click to collapse
please define stable then
~MaX~ said:
please define stable then
Click to expand...
Click to collapse
Doesn't use dirty patch code to fix issues in source, usually done to get a release out quicker, between release candidates to stable this code is refined.
JoinTheRealms said:
Doesn't use dirty patch code to fix issues in source, usually done to get a release out quicker, between release candidates to stable this code is refined.
Click to expand...
Click to collapse
Well.... Thank you
That's Well explained
I hope you are working on 4.4 rom
laufersteppenwolf said:
Gonna join this group, too
4.4 sure is on its way for our device, BUT:
Google is removing more and more support for our device, as it already is pretty old. So we need to re-add everything.
Even if it's booting, we still need a lot of work in order to get the most important stuff working (like SurfaceFinger, Audio, and ofc also data/RIL)
So regarding 4.4, all I can say is: Have patience
BTW, Thread moved to Q&A section
Click to expand...
Click to collapse
i'm really excited to see you releasing the 4.4 rom Aosp or custom, anyway your work is cool
You guys really doing great work here so l know that stable 4.4 will come eventually
Sent from my HTC Explorer A310e using Tapatalk 2
JoinTheRealms said:
Doesn't use dirty patch code to fix issues in source, usually done to get a release out quicker, between release candidates to stable this code is refined.
Click to expand...
Click to collapse
Sometimes it's still necessary to do. This is the case with our EGL libs for example. The best would be getting an update from LG, but this is very unlikely to happen. I got 4.3 BSP partially working, updated all graphics-related libs to 4.3 from grouper, but it broke a few things. Porting the full BSP might not be even possible.
Regarding Omni 4.4, I gradually found probably all needed patches for it, will see when I get to computer.
Sent from my OmniROM-powered LG Optimus 4X HD

[Q] Queries regarding custom kernels

Hello everyone
This is the first time Im creating a thread in all my years here on XDA. So please bear with me
Im very happy and excited to see the recent boom of custom roms for our device, its going really well and at a break neck speed.
Much rapid then I can download and flash it too
However, the only thing bugging me the lack of custom kernels.
I understand that the pINKman kernel by slukk and unnamed kernel by luca are both fantabulous kernels , and are mighty contenders for your time.
Dont get me wrong, I fully and whole-heartedly appreciate the kernel-devs and the awesome work made by them
The furnace kernel by savoca seemed to be a good one too, but I noticed that the thread has been closed and my recent pm to him about some possible update has not yielded any results.
I dont possibly know where im going with this conversation (lol), but if you catch my drift, we'd certainly want to see the boom of custom kernels just as we did with custom roms
Sorry for such a lengthy post .
*bows out*
:cyclops:
EDIT- lol, sorry for creating a thread in the general section, I botched it
Should have created in the QA section
metalrules321 said:
However, the only thing bugging me the lack of custom kernels.
Click to expand...
Click to collapse
Well, as long as Motorola doesn't release the kernel sources for lollipop, there isn't much that can be done. I found today some commits for lollipop but nothing official (look at Motorola's github kernel under issues). It took Motorola quite a while to release the sources for kitkat, so we have to keep patient.
need some OC and OV feature
@doppelhelix
Whelp
Thanks for clearing that up for me man.
Yeah it kinda sucks , I mean with the recent influx of so many roms and only 2 kernels was an eye-sore xD
Anys ways
*fingers crossed*
@doppelhelix
But on a second thought
How come slukk is developing and updating kernels even though the sources have not been released ??
metalrules321 said:
@doppelhelix
But on a second thought
How come slukk is developing and updating kernels even though the sources have not been released ??
Click to expand...
Click to collapse
based on kitkat. Thats why they don't work on stock lollipop, only cm

Categories

Resources