Related
I downloaded the CM7 source today to give porting a go spent 4 hours or so writing scripts etc for the p970 thought I could use a bunch of the libs from other phones etc like the galaxy S for the power VR libs and stuff like that...
first just wondering why no one has thought of this before guessing its not doable before i go any further any rom devs given this a go?
it's not so easy
port cm7 to p970 is a huge work
and maybe few mount later ,LG release official 2.3 update,CM7 may release a version for us,i guess
dxdiag32 said:
it's not so easy
port cm7 to p970 is a huge work
and maybe few mount later ,LG release official 2.3 update,CM7 may release a version for us,i guess
Click to expand...
Click to collapse
well, it's hard but not imposible.
there is no official gingerbread release for huawei ideos x5 but they have four different custom gingerbread rom(inculding cm7 and miui)
our devices need more developer love
murrun said:
well, it's hard but not imposible.
there is no official gingerbread release for huawei ideos x5 but they have four different custom gingerbread rom(inculding cm7 and miui)
our devices need more developer love
Click to expand...
Click to collapse
you're right. not only more developers but also users,users give devs power
Yeah i figured it'd be a lot of work i haven't got time atm to do much but hopefully during the next holidays i'll have a better look.
i hope all the bugs are fix the develop. i know its to hard to develop..
thnx to many developer...hooray.
Just flash the latest aokp rom its genius and i dont have any issues with it, its working even faster than the stock rom on my double speeded gt-p6200... have fun. By the way, there will never be a final ics on custom roms, there is always an idea to make it better ;-)
Sent from my GT-P6200 using XDA
marvz098 said:
i hope all the bugs are fix the develop. i know its to hard to develop..
thnx to many developer...hooray.
Click to expand...
Click to collapse
There is no such thing as 'bug free' buld that is why we always have new versions(builds) untill the dev team decides to move on to something new. Therefore I would imagine there won't be 'Final' ICS untill Android 5 (Jellybean) available and the dev team decides to move on to Jellybean (assuming many of us still sticking to our G-tab 7 and plenty developers still willing to crack one for us.)
However the latest builds of ICS are very stable and suitable for daily use.
yappoe said:
There is no such thing as 'bug free' buld that is why we always have new versions(builds) untill the dev team decides to move on to something new. Therefore I would imagine there won't be 'Final' ICS untill Android 5 (Jellybean) available and the dev team decides to move on to Jellybean (assuming many of us still sticking to our G-tab 7 and plenty developers still willing to crack one for us.)
However the latest builds of ICS are very stable and suitable for daily use.
Click to expand...
Click to collapse
You right, i'm using AOKP for my daily use. 3G,wifi, active sync exchange, dropbox all of them working smoothly only usb tethering not working in milestone #5 but overall great rom...
Sent from my GT-P1000 using Tapatalk 2
Hey guys, I'm thinking of compiling a CM ROM from source next month (have to wait for data cap to reset) and was wondering what you guys would prefer, a significantly more stable CM9, or a more buggy (and more headaches for me) CM10 ROM? I personally would prefer to do a CM9 ROM since it would be easier to support and fix bugs on, since we already have relatively stable, working builds of AOSP ICS. CM10 would be great as well, but it would be much harder for me to support, since I would be the second dev for the Inc S to build a JB ROM from source for us. I just don't think I have the know-how to be the only one working on it, and the only one fixing bugs and whatnot, without any already working source code to view and compare.
So I could compile CM9.2 stable, and we would have the latest CM9 code using kaijura's IceColdSandwich as a reference. I would have an easier time supporting the ICS ROM since I would have working source code to compare and review. Also, it would be significantly more stable simply due to the fact that multiple devs for our device have already worked on it. I'm sure I'd be able to fix bugs and support it fairly easily, other devs are the best resource around
Or I could compile a CM10 ROM. I would have to take device proprietary files from nik's JB ROM's, which would mean my compiled ROM would share a lot of the same bugs our current JB ROM's already have. I could support and fix bugs in CM10, it would just take longer and be harder to do. Nothing's impossible though, so if that's what the community wants, then that's what I'll build!
So what do you guys think? CM10 or CM9?
It's your time and effort you do what Rom you want to do. Any Rom would be great!
Sent from my HTC Incredible S using Tapatalk 2
vizzy said:
It's your time and effort you do what Rom you want to do. Any Rom would be great!
Sent from my HTC Incredible S using Tapatalk 2
Click to expand...
Click to collapse
I'm torn between the two! On the one hand, I want a stable ROM which would be CM9, but I also love that JellyBean goodness. I've also seen some people here that simply want a stable CM9 that's up to date, and other's that want the latest CM10 despite bugs. That's the point of this thread
I would tell u is that first for cm9 when we get a stable awesome cm9 for sure it will be easy to get a cm10... btw are u going to build a kernel?
My vote goes towards CM9! been using codename for the past couple months and although i'm enjoying all the new features, i still find myself yearning for a rock solid & stable ASOP based build.
Sent from my Incredible S using Tapatalk 2
linezero said:
I would tell u is that first for cm9 when we get a stable awesome cm9 for sure it will be easy to get a cm10... btw are u going to build a kernel?
Click to expand...
Click to collapse
I could give it a try, but if nik and others couldn't get a 3.0 kernel up and running for AOSP, then I'll have a damn hard time. I'd prefer to have someone else make the new kernel, I don't know much about compiling them. Till then, I would just use X-ICS4.0 for the kernel.
Make a CM9, CM10 would have in the end too much bugs and they would just chance again. I'm waiting for a stable cm9 anyway
Sent from my HTC Incredible S using xda app-developers app
Kernel 3, Cm10 got my vote
sent from my jellybean device
ZaySk said:
Hey guys, I'm thinking of compiling a CM ROM from source next month (have to wait for data cap to reset) and was wondering what you guys would prefer, a significantly more stable CM9, or a more buggy (and more headaches for me) CM10 ROM? I personally would prefer to do a CM9 ROM since it would be easier to support and fix bugs on, since we already have relatively stable, working builds of AOSP ICS. CM10 would be great as well, but it would be much harder for me to support, since I would be the second dev for the Inc S to build a JB ROM from source for us. I just don't think I have the know-how to be the only one working on it, and the only one fixing bugs and whatnot, without any already working source code to view and compare.
So I could compile CM9.2 stable, and we would have the latest CM9 code using kaijura's IceColdSandwich as a reference. I would have an easier time supporting the ICS ROM since I would have working source code to compare and review. Also, it would be significantly more stable simply due to the fact that multiple devs for our device have already worked on it. I'm sure I'd be able to fix bugs and support it fairly easily, other devs are the best resource around
Or I could compile a CM10 ROM. I would have to take device proprietary files from nik's JB ROM's, which would mean my compiled ROM would share a lot of the same bugs our current JB ROM's already have. I could support and fix bugs in CM10, it would just take longer and be harder to do. Nothing's impossible though, so if that's what the community wants, then that's what I'll build!
So what do you guys think? CM10 or CM9?
Click to expand...
Click to collapse
cm9 bro! because ics kernel source is out and bugs can be fixed!
Yeah. CM9 would be OK for me too. I can help with testing if needed.
But what would be those great JB features we would be missing out? Sry I haven't been following the differences between 4.0 and 4.1.
IncS community is desperate for at least one fully functional, bugless AOSP ROM, so my vote goes for CM9
CM9 bro..wishing for bugless one.. gud luck..
Sent from my HTC Incredible S using xda app-developers app
My 2 cents.
CM9. Kernel sources for ICS has been release by HTC and ANY AOSP rom that is stable would be very welcome in our community.
(I know there is gingerbread roms.. But.. Its ginger bread..)
Jelly Bean is nice and all,
But the odds of getting a stable AOSP rom are much higher with cm9.
CM9 I would say. I hope you can fix data problems for Vodafone NL users. We always have problems with data connection on AOSP ROMs.
CM9 would be great....!!
Its great to see devs are enthusiasticaly working on Roms..!!
You are the one dude...
Jst for info u might already aware of
This thread
http://forum.xda-developers.com/showthread.php?t=1914015
CM10 test build
Sent from my HTC Incredible S using xda app-developers app
my vote a CM9 ASOP rom and bugless
Sent from my Incredible S using xda premium
naathaanb96 said:
cm9 bro! because ics kernel source is out and bugs can be fixed!
Click to expand...
Click to collapse
Totally agree. I don't like much sense ROMs, CM9 with working camera and camcorder would be perfect!
Thanks ZaySk
CM9!!!!
ZaySk said:
Hey guys, I'm thinking of compiling a CM ROM from source next month (have to wait for data cap to reset) and was wondering what you guys would prefer, a significantly more stable CM9, or a more buggy (and more headaches for me) CM10 ROM? I personally would prefer to do a CM9 ROM since it would be easier to support and fix bugs on, since we already have relatively stable, working builds of AOSP ICS. CM10 would be great as well, but it would be much harder for me to support, since I would be the second dev for the Inc S to build a JB ROM from source for us. I just don't think I have the know-how to be the only one working on it, and the only one fixing bugs and whatnot, without any already working source code to view and compare.
So I could compile CM9.2 stable, and we would have the latest CM9 code using kaijura's IceColdSandwich as a reference. I would have an easier time supporting the ICS ROM since I would have working source code to compare and review. Also, it would be significantly more stable simply due to the fact that multiple devs for our device have already worked on it. I'm sure I'd be able to fix bugs and support it fairly easily, other devs are the best resource around
Or I could compile a CM10 ROM. I would have to take device proprietary files from nik's JB ROM's, which would mean my compiled ROM would share a lot of the same bugs our current JB ROM's already have. I could support and fix bugs in CM10, it would just take longer and be harder to do. Nothing's impossible though, so if that's what the community wants, then that's what I'll build!
So what do you guys think? CM10 or CM9?
Click to expand...
Click to collapse
My request would be neither CM9 nor CM 10.... it will be great if you can work on Kernel Version 3.... Becz that is the only roadblock for us for Jelly Bean and would open doors for may developers to come up with fresh and exciting jelly bean ROMs.....Why stay behind the world guys... lets target Jelly bean step by step.....who knows if you start working on kernel it may really turn out to be good.....Try for kernel bro......all the best.. try to compile it from source....
A rock solid cm9 would be great!
Sent from my Incredible S using xda app-developers 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
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.