Hi guys,
I stopped a while to build rom for tatoo but I continued to follow the thread.
For fun I have compiled the latest stable kernel ... if anyone cares to test it I'll put the link here.
I take this opportunity to insert a link to my kernel sources generated using HTC.
I think it's correct to use this kernel for the development of libraries on the camera and radio, as it turns out to be the only kernel you know works.
Compiling the latest kernel I have seen many great features ... but totally missing some drivers, such as those in radio ...
I do not understand this anxiety developers to have a custom kernel and the most updated ... But I think it is appropriate to start building a secure kernel. When the camera and the radio works then you can create as many kernels you want ... but not before.
This is my thought ... meanwhile I'll use this post to whoever wants to download the kernel and HTC for those who want to test my kernel 2.6.35.4.
Kernel_2.6.29_HTC
contain for shure all drivers for FMRadio,camera,bt ecc and all htc patches (if presents). this kernel il generated from HTC kernel source downloaded from htc site.
Features added: ext3 and ext4 partitions support
Kernel_2.6.35.4_v1NOT WORKING
Is a testing kernel. it is generated compiling the last stable source released on kernel.org
Kernel_2.6.35.4_v2
- FMRadio diriver inculded
- voltage and current regulator support
- Led drivers
- ext3 ext4
nice job, my friend.
francians said:
nice job, my friend.
Click to expand...
Click to collapse
is not nice... it haven't the radio drivers and i don't know if it work well...
i have only spent some time today because i have nothing to do..
it isn't a serious kernel for me...
ikxdf said:
Hi guys,
... But I think it is appropriate to start building a secure kernel. When the camera and the radio works then you can create as many kernels you want ... but not before.
Click to expand...
Click to collapse
Although I´m no dev, this is actually very sensible. I´d rather had a slightly outdated but FULLY functional kernel, than the most up-to-date but crippled one...
No source or config files or tweeks you made?
Good day ikxdf!
Seg
segway_ said:
No source or config files or tweeks you made?
Good day ikxdf!
Seg
Click to expand...
Click to collapse
i will upload the source and the config soon
The attached kernel Kernel_2.6.35.4_v1_[ikxdf].zip does not even boot.
No adb no something on /proc/last_kmsg after boot to recovery!!
Nice try ikxdf.
Seg.
segway_ said:
The attached kernel Kernel_2.6.35.4_v1_[ikxdf].zip does not even boot.
No adb no something on /proc/last_kmsg after boot to recovery!!
Nice try ikxdf.
Seg.
Click to expand...
Click to collapse
This is because he based it on the stock Linux kernel, and not the android branch... I don't even know if it's compiled for ARM or x86, but I'll check that soon...
Sent from my HTC Hero using XDA App
EDIT: I have checked for the kernel architecture and it is compiled for ARM. I also took the liberty of extracting the config from it, and saw that it seriously need lots of attention. I have attached a copy of the config below... BTW: good luck with getting this to work
segway_ said:
The attached kernel Kernel_2.6.35.4_v1_[ikxdf].zip does not even boot.
No adb no something on /proc/last_kmsg after boot to recovery!!
Nice try ikxdf.
Seg.
Click to expand...
Click to collapse
please sega-way evitate your sarcasm and read well before writing:
ikxdf said:
is not nice... it haven't the radio drivers and i don't know if it work well...
Click to expand...
Click to collapse
ikxdf said:
For fun I have compiled the latest stable kernel ... if anyone cares to test it I'll put the link here.
Click to expand...
Click to collapse
if u don't know i haven't a tatto for testing.
if anyone want test and send me the error i will try to fix if i find the time.
for me the only correct kernel is the 2.6.29 compiled from the htc source. All other kernel is only a game.
For the next time...learn to read all post before writing.
Thanks
kiljacken said:
This is because he based it on the stock Linux kernel, and not the android branch... I don't even know if it's compiled for ARM or x86, but I'll check that soon...
Sent from my HTC Hero using XDA App
EDIT: I have checked for the kernel architecture and it is compiled for ARM. I also took the liberty of extracting the config from it, and saw that it seriously need lots of attention. I have attached a copy of the config below... BTW: good luck with getting this to work
Click to expand...
Click to collapse
thanks Kill. I can't take a look now but next week i will try to recompile it. Please i need a .config of a original 1.6 ROM...can u upload it here?
ikxdf said:
thanks Kill. I can't take a look now but next week i will try to recompile it. Please i need a .config of a original 1.6 ROM...can u upload it here?
Click to expand...
Click to collapse
from the tattoo.. it was gz now is zip
ikxdf said:
please sega-way evitate your sarcasm and read well before writing
Thanks
Click to expand...
Click to collapse
Its just a feedback...
Sorry if you take it as something else....
Seg
i'm trying to made this kernel booting and have add some features:
- FMRadio diriver inculded
- voltage and current regulator support
- Led drivers
if anyone want test it i will upload it today
uploaded in first posts
I've been away from the Tattoo scene since we got root on this little device.
I'm currently interested in getting psfreedom to run on Tattoo but it seems that the stock HTC kernel is crippled (missing usb stuff). If your kernel is at least bootable, this would be a nice place to start
mainfram3 said:
I've been away from the Tattoo scene since we got root on this little device.
I'm currently interested in getting psfreedom to run on Tattoo but it seems that the stock HTC kernel is crippled (missing usb stuff). If your kernel is at least bootable, this would be a nice place to start
Click to expand...
Click to collapse
if u are talking about 2.6.35.4 version you have to try if it can boot because i haven't a tattoo for test it.
I have sell my tattoo after 2 week but all great users of this thread have always made a great testing job for me and for my rom.
If anyone want test if this kernel is booting or not i will contine to develope it.
If it doesn't boot and adb will start i need a logcat.
if u are talking of the original htc kernel 2.6.29 version it is already working on my rom (Pancake) .
i will release sonn the wlan.ko module for 2.1 and for 2.2 roms for the 2 versions of kernel.
Hi, ikxdf!
I'm willing to try your kernel. I am quite an experienced linux user of desktop and server but I'm quite new regarding ROM flashing. But still, from what I gather I have to flash your kernel archive in the boot sector, right?
I have AmonRA's recovery installed and tested. And I'm eager to try cooked stuff as I've just gotten my Tattoo out of service today after 3 weeks!!! I was so dissapointed in having my old Nokia again.
Related
This kernel is a joint effort between ralle.gade and myself to make a kernel that really performs as expected.
Introducing CoburnKernel v7 Series. Originally the heart and soul of AzusaROM, I'm releasing the kernel in case anyone wants to make a custom ROM that will rocket. On AzusaROM 1.03, this kernel loaded the Android home/desktop within 3 "HTC" logo shine cycles. It boots within a minute, depending on your ROM configuration.
You can download it from my Coburn's Domain Server in the Android Project File Browser located here. Login with the user "android", and password "android" and look in the ckernel7series directory. There is nothing private on the server and you are restricted in what you can do - no uploading, i.e. look but you can't touch. Your IP Address is logged by using the File Browser, and if you abuse the server I will ban your IP. Do not attempt to gain access in areas that you shouldn't be in.
Look at the system/modules folder for what CoburnKernel includes. EXT4 is used as EXT2 and EXT3 support, and ralle.gade has done countless graveyard shifts to clean out rubbish that HTC left behind and squish bugs. The kernel is based on 2.6.29 with countless tweaks and mods done by ralle.gade.
I hope you can make use of CoburnKernel! Let's see some ROMs that fly like the wind!
Nice!!! Thank you, will try it out right now!!
What did u change on the Kernel? is it OC'ed?
It's just hacked for optimum performance and has a lot of bloat removed. It has like NFS support and all sorts of cool stuff that ralle.gade complied in.
can you please enable oc ?
Coburn64 said:
It's just hacked for optimum performance and has a lot of bloat removed. It has like NFS support and all sorts of cool stuff that ralle.gade complied in.
Click to expand...
Click to collapse
Not that I don't appreciate people spending their own free time improving the speed of the tattoo, but why would you spend time removing all the htc bloat only to add more (nfs support? why? to connect to nfs shares with your phone?!).
By bloat, I mean, leftovers from HTC's kernel cooking. There was a HTC bug that could cause mismatches between the kernel modules, causing Android to reboot that ralle.gade fixed. The NFS Support is in a form of a .ko file... Removing that wouldn't hurt, I guess.
is there anyone that would like to have a rebase of my kernel?
if yes i can make some new + old options like:
compiled with gcc 4.4.1
more compiler tweaks
android tether buillt directly in
maybe some ram could be freed
and lets not forget OC
and a ton of other stuff
then i would make a version with alot of addons, one with less addons and a super simple and fast one
would that something or?
Nice!!! I would tell my pals (still with tattoos) that you are making an OC Kernel! Would be nice if you would cook then
dude im on it
ralle.gade said:
dude im on it
Click to expand...
Click to collapse
on what?
liderzre said:
on what?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=6773788&postcount=7
i have the base done now and when ready ill release something with oc
Yiiihaaaa
if you want to try the base kernel check out kiljacken's 1.1 which should come out later 2day
it will have my new kernel work
anyone that wanna have a look at ma base kernel can extract it directly from kiljacken's 1.1 ROM please give me some feedback
ralle.gade said:
anyone that wanna have a look at ma base kernel can extract it directly from kiljacken's 1.1 ROM please give me some feedback
Click to expand...
Click to collapse
when will wi-fi be operational in Kiljacken's 1.1 ROM (it's up to you or ? )
at the moment it's not up to me no, it's problems with the rom itself
so i can't help it
ralle.gade said:
at the moment it's not up to me no, it's problems with the rom itself
so i can't help it
Click to expand...
Click to collapse
Thanks.
Np bro try it out
Friend says that Kernel doesn't work with Abyzou ROM - lots of fc's...^^
Hi all,
If anyone wants to play with this and let me know how it works feel free.Its the system directory from an AOSP eclair build using the Samsung Vibrant source download from the opensource website.I have no Vibrant myself I just built this as a test to see if it would build clean with no errors using the samsung files as a test for when the Epic 4g sources get released.Please feel free to use it in a rom or whatever you chose and post back if it works or not.
www[DOT]mediafire[DOT]com/?wytytv44odtdsdx
EDIT: This is not flashable! This is a stock /system filesystem from a build of AOSP android this is the base for a ROM not a complete ROM in itself.
Most likely it won't work cause Eugene is working from the aosp but is running into problems getting sound and camera to work.
I was just surprised it compiled the first run I saw another post where they were getting a lot of errors.And I figured there would be corrupt files I had a hell of a time extracting the archieve.
Sent from my SPH-M900 using Tapatalk
Thanks for posting that. I would like to have a look around but I wasn't sure where and what to grab.
www.mediafire.com/?wytytv44odtdsdx
heh
10char
Rhcp thanks for reposting a real link kinda sucks not being able to post them.
Sent from my SPH-M900 using Tapatalk
skeeterslint said:
Rhcp thanks for reposting a real link kinda sucks not being able to post them.
Sent from my SPH-M900 using Tapatalk
Click to expand...
Click to collapse
Not a problem. Post some more so you can update your OP.
Good work on the build. Did you build the kernel too?
rhcp0112345 said:
Not a problem. Post some more so you can update your OP.
Good work on the build. Did you build the kernel too?
Click to expand...
Click to collapse
There is no Kernel in a system image.
just got home, gonna dl and see what cooking
rhcp0112345 said:
Not a problem. Post some more so you can update your OP.
Good work on the build. Did you build the kernel too?
Click to expand...
Click to collapse
I haven't tried building the kernel yet but I pulled the intramfs from a vibrant and captivate kernel to compare them togther and see if there are any real differences which it seems there really isn't that I noticed.One thing I did notice though is that the samsung kernel sources don't build the initramfs into the kernel that I noticed.With the Samsung Moment the sources had a file to build the kernel modules and a couple other programs that went into the intramfs and it had the initramfs_list file hidden inside the source somewhere it doesn't seem like they did that with the vibrant kernel source.How do they expect you to build a kernel that requires an initramfs in it and not build it into the kernel during the compile?I am gonna tinker around and probably use the initramfs_list file from the Moment initramfs and just add in all the directorys and files that are in the vibrant/epic/captivated initramfs.
it gets stuck on "installing update"
my clockwork does that from time to time with any zip file, just pull the battery and retry
Thats just a raw /system filesystem it would need to be cooked into a rom for it to be flashable.I threw it up there for someone to try and cook a rom out of it.
Has anyone had the problem when trying to compile a kernel that the suppiled build script doesn't build the modules?I can get the zImage to build but it won't build the modules at all.I would like to at least get it built with the samsung script and get the modules built then use the modules in the initramfs and try to build it with another script with the initramfs in the kernel.
skeeterslint said:
Thats just a raw /system filesystem it would need to be cooked into a rom for it to be flashable.I threw it up there for someone to try and cook a rom out of it.
Has anyone had the problem when trying to compile a kernel that the suppiled build script doesn't build the modules?I can get the zImage to build but it won't build the modules at all.I would like to at least get it built with the samsung script and get the modules built then use the modules in the initramfs and try to build it with another script with the initramfs in the kernel.
Click to expand...
Click to collapse
same problem I had with building the kernel
chaoscentral said:
same problem I had with building the kernel
Click to expand...
Click to collapse
The captivate kernel builds with the samsung script with no problem modules and all, used the captivate script with the vibrant kernel source same deal builds the kernel but no modules.
Almost Done! http://twitpic.com/2et5cb
eugene373 said:
Almost Done! http://twitpic.com/2et5cb
Click to expand...
Click to collapse
You're out of your mind - in a good way. Vanilla has got to FLY on this thing, right?
eugene373 said:
Almost Done! http://twitpic.com/2et5cb
Click to expand...
Click to collapse
Thank you so much for your hard work Eugene! Now if only we can get a mod or someone to lock your threads so only you can update, I'm tired of having to explain adb push/pull to people over-and-over, so I know you must be too.
Cheers,
=)
eugene373 said:
Almost Done! http://twitpic.com/2et5cb
Click to expand...
Click to collapse
Eugene,
If I'm not mistaken...that's the stock home launcher for 2.2 isn't it? Or are you running adw/launcherpro
Sent from my SGH-T959 using XDA App
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
reported it to be deleted.
wait till tomorrow for my new personal build
Will complete it later on.
Will complete it later on.
wuut?
This is yours CM7 or based on CM7 bieltv?
Alucard1989pl said:
This is yours CM7 or based on CM7 bieltv?
Click to expand...
Click to collapse
Yep my cm7 built from source
The device trees are by biel which I am working on.
downloading .... report in half an hour ...!
EDIT: Sbrick too, trying with hell lock now...
Phone has soft brick by kernel in your cm7 rom . . . system data and cache must be formated to ext4?
Alucard1989pl said:
Phone has soft brick by kernel in your cm7 rom . . . system data and cache must be formated to ext4?
Click to expand...
Click to collapse
use hells fusion from the other thread..
I already use hells fusion kernel but when i installed your cm7 my phone stuck on splash screen and led for 1 sec turn on.
Alucard1989pl said:
I already use hells fusion kernel but when i installed your cm7 my phone stuck on splash screen and led for 1 sec turn on.
Click to expand...
Click to collapse
logcat? its really weird cuz it worked for someone else..
what instructions did u use?
prototype-U said:
use hells fusion from the other thread..
Click to expand...
Click to collapse
Please include your kernel in this thread to make it clearer
You have to use this updater-script for flash cm7. If you don't use this one, the phone will get bricked. http://pastebin.com/htJ8NYTs
For use this updater-script you have to put in the first root of the zip two files: bmlunlock and busybox.
Remember to add the boot.img of hells fusion kernel at second post!
P.S. OP I think that you have to give credits to biel!
Soft Brick. Tried with hell lock flashable zip, softbrick with flashlight with 2 seconds. Now tried with the kernel you provided, stuck on the SGAi bootlogo. Any solution? You said it worked on someone else's device... How did he install? From stock or another rom?
EDIT: Now will try with the updater script you said, @Lopicl.00 . What attachment are you talking about?
mathm2013 said:
Soft Brick. Tried with hell lock flashable zip, softbrick with flashlight with 2 seconds. Now tried with the kernel you provided, stuck on the SGAi bootlogo. Any solution? You said it worked on someone else's device... How did he install? From stock or another rom?
Click to expand...
Click to collapse
Follow my post!
bricked the device while trying to install this rom, i had the kernel from your threat
Angryace said:
bricked the device while trying to install this rom, i had the kernel from your threat
Click to expand...
Click to collapse
Threat is something that puts you in danger
Well, I don't know which is the point of this thread. You are building my sources. You are making my ROM. Why create another thread? You don't have the device, me neither, but I started that project from 0. Why instead of making your CM7 you don't help us? Why don't you make a pull request? Do we need to talk with testers, which are the same for the both of us, to just test the same ROM!? If we want to have something big, we should focus on one CM and not building various CM7. I don't know which is the point of this, and I don't know what were you thinking. In your github there is 0 changes on my device tree. I committed all my changes during the last month and you used my work to build your own, and then it seems that your ROM is better than mine, because I don't release mid-done ROM's. I want to give the best expierence to all the users.
Also, I committed all the changes to help people understand on what I'm working. Many users asked me if I was really working on it, as I did not commit anything to github, but I was. And what happens if I commit? other users use my work to build their ROM's? I think that's not the way to go.
And what about a simple credit to the real author of this ROM? as your signature says: Send me device tree and I'll build the ROM. Why? To be more famous using other people's work? I don't get the point of anything here...
Oh, btw, where are the permissions to do that?
Thanks, Biel.
bieltv.3 said:
Well, I don't know which is the point of this thread. You are building my sources. You are making my ROM. Why create another thread? You don't have the device, me neither, but I started that project from 0. Why instead of making your CM7 you don't help us? Why don't you make a pull request? Do we need to talk with testers, which are the same for the both of us, to just test the same ROM!? If we want to have something big, we should focus on one CM and not building various CM7. I don't know which is the point of this, and I don't know what were you thinking. In your github there is 0 changes on my device tree. I committed all my changes during the last month and you used my work to build your own, and then it seems that your ROM is better than mine, because I don't release mid-done ROM's. I want to give the best expierence to all the users.
Also, I committed all the changes to help people understand on what I'm working. Many users asked me if I was really working on it, as I did not commit anything to github, but I was. And what happens if I commit? other users use my work to build their ROM's? I think that's not the way to go.
And what about a simple credit to the real author of this ROM? as your signature says: Send me device tree and I'll build the ROM. Why? To be more famous using other people's work? I don't get the point of anything here...
Click to expand...
Click to collapse
Ok I am also starting the device tree from scratch. Is that alright?
I will suspend the current build and post a new one tomorrow which will based on my device trees.
About credits? I didnt even complete writing this thread..
About changes thing? I have made changes at my end which are not committed becuz I dont wanna put untested changes on github.
Sorry If I offended someone but I had no real intentions of doing that..
and btw.. I mean somehting else from my sign.. I want to help other device owners to get new roms to their device. Though it contradicts to this build.
Welcome to the official thread for the Lollipop roms for our Optimus 2x
As to start, this thread is exclusively for the developers who are interessted/working on on the Lollipop ports for our Optimus 2x
We had alredy some build like the OmniRom , CM12 and even ParanoidAndroid.
This thread is exclusively for discussions for the developers and for the testers to test the new made roms so I will update the links as the roms get made. So I am only posting here the links of the latest version, to get the versions from the past you wil need to browse throught this thread
Update 05/6/2016
Gucky did it again! New build for CyanogenMod 12.1 is up, and now with fixed camera! When I get the full list of working features and bugs, I will upload it here. Thank you Gucky for your massive help and contribution to this community. This device is very old after all, and you still find the time to tinker on it. No words really. Respect!
CM12.1 : https://sourceforge.net/projects/lg...cm-12.1-20160531-UNOFFICIAL-p990.zip/download
WARNING the Rom is still not stable, but we are close!
ParanoidAndroid: https://s.basketbuild.com/devs/Puri/p990/AOSPA(lollipop)
Take in mind that all these roms are unstable besides the CM12 rom,but it still has some major bugs which we as a group will fix.
As in all of this, stay tuned for updates
Good job my friend
Thank you very much. I'm downloading right now. It would be useful, if you could upload your (Lokal) Manifest, too. So we are able to re- build the rom with the necessary changes.
Looking forward!
Credits goes to you!
um
gucky01 said:
Thank you very much. I'm downloading right now. It would be useful, if you could upload your (Lokal) Manifest, too. So we are able to re- build the rom with the necessary changes.
Looking forward!
Credits goes to you!
Click to expand...
Click to collapse
um.......*noob mode activated.....BOOP * what you mean with manifest? lol
Could you please share your sources.
TheMysteryouse said:
Hello everyone.As you might know me from some threads where i comment some stuff.Anyways, since Lollipop was announced i was obssesed with it and my wish was that i would be the first one to make the version availble for our device.
Well i kinda did it....KINDA of course but we need some help if we wanna make it work.I call ALL of the developers for our device to work together to make it work.We are so close to get it fully booting.I made it boot to the animation and now where the help comes in use.We need some developers who can enable ADB on our device in the bootanimation.TO be honest i dont really know anything about sources and that stuff but i know some things.With the help of @tonyp and @timduru which I am the most thankfull of that gave me hope to make this.So here we go!
WARNING!!!
ONLY FOR DEVELOPERS
No one should download and flash this rom because you will get stuck in the bootanimation and will need to install previouse rom again and install everything over...blah blah blah.
Also the link to the rom is here ----> https://www.dropbox.com/s/fwhg08ux7qhtgsh/5.0 test.zip?dl=0
So if someone gets it working, please pm me in the progress. Cheers
Click to expand...
Click to collapse
TheMysteryouse said:
um.......*noob mode activated.....BOOP * what you mean with manifest? lol
Click to expand...
Click to collapse
a little help.
http://wiki.cyanogenmod.org/w/Doc:_Using_manifests
Oh
Hugo-PT said:
a little help.
http://wiki.cyanogenmod.org/w/Doc:_Using_manifests
Click to expand...
Click to collapse
Well to be honest, i dont really know how to share the menifest because i didn't use much the source. I was porting the Cm11 tonyp's rom and the rom from timduru, so i dont really know how to share the manifest lol
TheMysteryouse said:
Well to be honest, i dont really know how to share the menifest because i didn't use much the source. I was porting the Cm11 tonyp's rom and the rom from timduru, so i dont really know how to share the manifest lol
Click to expand...
Click to collapse
Did you change some files in the zips or did you build a new rom in the way Raum described, my friend?
http://forum.xda-developers.com/nexus-4/general/guide-cm11-how-to-build-cyanogenmod-11-t2515305
nope
gucky01 said:
Did you change some files in the zips or did you build a new rom in the way Raum described, my friend?
http://forum.xda-developers.com/nexus-4/general/guide-cm11-how-to-build-cyanogenmod-11-t2515305
Click to expand...
Click to collapse
nope, didn't touch anything other than the updater script i think and the build prop because i wanted fully stock experience
I can be your tester my phone got a battery problem so im having fun with flashing roms
I will try to exchange the updater script from my build with yours.
Lets see if I can flash mine.
And your your problem: I think there are one or more patches that we maybe need, witch timduru wont need because of the tegra3 hardware. (maybe some patch for our old egl hardware)
DJNoXD said:
I will try to exchange the updater script from my build with yours.
Lets see if I can flash mine.
And your your problem: I think there are one or more patches that we maybe need, witch timduru wont need because of the tegra3 hardware. (maybe some patch for our old egl hardware)
Click to expand...
Click to collapse
Well, it might be that he used KatKiss from timduru for the TF101 which has a Tegra 2, but still our phone uses the Tegra 2 AP20H, while the TF101 uses Tegra 2 T20. Small difference in the chipset, but still a difference. Easiest would be to port from the Galaxy R or Captivate Glide, but they too struggle with Lollipop over in their forum. Anyway, TheMysteryouse used timduru's AOSP rom, so maybe it would be easier building the whole thing from the demo CM12 sources available.
nonono
DJNoXD said:
I will try to exchange the updater script from my build with yours.
Lets see if I can flash mine.
And your your problem: I think there are one or more patches that we maybe need, witch timduru wont need because of the tegra3 hardware. (maybe some patch for our old egl hardware)
Click to expand...
Click to collapse
Nope, this rom has NOTHING to do with the tegra 3 rom.I used the rom for TF101 tablet which is tegra 2 but had a cmall chipset difference.So yeah I am still trying to do some things like searching the framework sources from tony to see if he has a code in the build.prop which directly enables ADB from the boot, but cant really find it.Anyways try your best and so the others.Cheers
Hi guys, after some testings I could get booting to finish. There are some errors left. But I will work further this evening and upload the rom afterwards. Think this will remain a test build for some time, till Tony or DJ can fix the errors.
Stay tuned!
Any video or screenshot? xD
Sorry for nob request, but working well or not, its great to our comunity
p.s. if need tester in future, you, TheMysteryouse or DJNoXD.
Im ready for
...WoW!...That´s Good News...Thank You for All of You, Guy´s...
gucky01 said:
Hi guys, after some testings I could get booting to finish. There are some errors left. But I will work further this evening and upload the rom afterwards. Think this will remain a test build for some time, till Tony or DJ can fix the errors.
Stay tuned!
Click to expand...
Click to collapse
Awesome news buddy! Lollipop on first power dual core android device! Switch to 1+ One as a primary phone for some reason but I will continue to follow and supporto you!
That is great!!! ))))))))
Ok. I have to go one step back. The rom is not ready for the testers and I'm too tired to test more. For those, who want to repeat my steps or want to finish...
I replaced the files in Mystery's rom with my own Kitkat ones. The first half, than the second. Now I could get it to finish the booting process. This steps I went on and on. So I could reduce the problem to the framework-files in "system". If you replace all of them, it boots up with some error messages.
I think we have to reduce the 40 files inside more and more to find the reason for the bootloop.
All the best to you,my friends!
Damm this is great a device from 2010 receives android L. 4years later. If I can borrow the old optimus 2x from my father then I could also look into the problems if it's not booting yet then. Till then continue your work.