Related
Hey guys. So would anyone like to help me out in building an AOSP ROM for the LG Optimus S?
Currently, I have compiled the LG AOSP 2.2 kernel (zImage), and compiled the Android 2.2 AOSP system. Apparently now I need to get the LG vendor tree so I can compile that too into a working system? Can anyone help me out with that? This is my first time ever building a ROM from source code.
i hope someone will listen your help request
I hope so too... I hope so too.
I hope so too, would be nice to have another ROM option for the Optimus S. And this is a stepping stone to CyanogenMod on it
I'm also interested to create a fully working build of 2.2.2 AOSP Froyo.
But I'm new to the Android's world. I need that someone teach me how to build android from source. Also I need to know how to port the LG's drivers.....
I'm willing to help, but I can't program in any language. However, I know the basics, I can compile stuff, can do fairly well with the command line, I use Arch Linux as my main OS (so I can pretty much do compilations and stuff without a problem), etc.
I still don't know much about Android at this time, and contributing to this "project" may be my way of getting to know things
Count be in.. i m good with C,C++ ,shell scripts .tell me wat to do..i m new to android
Building Android from source can be quite tricky when proprietary software must be compiled in. I'm compiling since 2 months on gingerbread and nothing but phone is working... no USB,no camera, no bluetooth ... its now simply a phone^^
But, if your are lucky with Froyo you need only the source from android 2.2.x and the one shipped by LG (I know there are some sources for Optimus One, but don't know about Optimus S). Put it all together and compile the code - while/after compiling you will see lot of errors, there must be fixed by yours.
Have a look at cyanogen CM6.1, there have many fixes built in. If you would like to build a brand new system from scratch by yourself, i'll wish you many luck and lots of time
andy572 said:
Building Android from source can be quite tricky when proprietary software must be compiled in. I'm compiling since 2 months on gingerbread and nothing but phone is working... no USB,no camera, no bluetooth ... its now simply a phone^^
But, if your are lucky with Froyo you need only the source from android 2.2.x and the one shipped by LG (I know there are some sources for Optimus One, but don't know about Optimus S). Put it all together and compile the code - while/after compiling you will see lot of errors, there must be fixed by yours.
Have a look at cyanogen CM6.1, there have many fixes built in. If you would like to build a brand new system from scratch by yourself, i'll wish you many luck and lots of time
Click to expand...
Click to collapse
So in your opinion it would be a lot easier to just build a CyanogenMod 6.1 ROM? Sounds like a plan. I read that I could just pull stuff from the Legend and use that as well? Could you help me with that stuff (pulling from the Legend source, that is)?
Legend stuff is less compatible then i thought. You can't use nothing from there.
As my work at 2.3 is now stopped (I haven't bugs related to working stuff, I have no idea what to do with 3d and gps and I too lazy to patch libcamera now) I hope to start work on CM6 next holiday's.
mik_os said:
Legend stuff is less compatible then i thought. You can't use nothing from there.
As my work at 2.3 is now stopped (I haven't bugs related to working stuff, I have no idea what to do with 3d and gps and I too lazy to patch libcamera now) I hope to start work on CM6 next holiday's.
Click to expand...
Click to collapse
We'll work on it together then? I started a GitHub. github.com/mrinehart93
mrinehart93 said:
We'll work on it together then? I started a GitHub. github.com/mrinehart93
Click to expand...
Click to collapse
As I already got working GSM/Audio/WiFi/Bluetooth/USB/Sensors in 2.3 (port to 2.2 is easy) I will continue work in my repo https://github.com/mik9
Ypu can send your patches via "pull request" functionality.
mik_os said:
As I already got working GSM/Audio/WiFi/Bluetooth/USB/Sensors in 2.3 (port to 2.2 is easy) I will continue work in my repo https://github.com/mik9
Ypu can send your patches via "pull request" functionality.
Click to expand...
Click to collapse
I won't have any time to work on CM tonight or probably the rest of this week, but as soon as I do I'll set up my Github.
I've been following the development of so-called ROMs for the Vibrant (and other SGS devices), but I have yet to see a single AOSP ROM. Even when Samsung released the original kernel sources for 2.1, there were no AOSP 2.1 ROMs. Why not? Is it because they don't know which BLOBs to pull for insertion or the proper vendor overlays?
Some developers have done great work with SGS kernels (especially supercurio and his Voodoo kernels ... eugene373's tend to always wipe the internal SD card unnecessarily ...). But, a kernel does not a ROM make ... therefore I ask, what is truly missing to build an AOSP ROM. I've gone through the sources, but I don't follow makefiles too well.
I know we have another month or so before Samsung is obligated to release their 2.2 kernel sources, but that should have no impact on 2.1 AOSP ROMs. Therefore, I ask "what is the hold up?" What is missing, and what might I contribute ...
Need 2.2 source code...
2.1 is a dead horse--why bother when 2.2/2.3 are out?
The reason to bother is to at least get AOSP running. Once its on 2.1, it'll be easier to get 2.2 AOSP running on it. But claiming 2.1 is a "dead horse" is the wrong path ... the real question still stands: after 9 months on the market their still are no AOSP ROMs.
MIUI
Now that vibrant 2.2 source is released ... we finally have a REAL AOSP port and my all time favorite from my old HD2 the MIUI.... so keep your heads up and wait for it to get finished.
Get a custom rom. There are so many good devs doing them don't waste your time on AOSP....... until they release the actual source code...... on April 22
sarim.ali said:
Now that vibrant 2.2 source is released ... we finally have a REAL AOSP port and my all time favorite from my old HD2 the MIUI.... so keep your heads up and wait for it to get finished.
Click to expand...
Click to collapse
Except, the 2.2 source for the Vibrant has not been released. The SGH-T959D that shows Froyo sources on Samsung's site is for the Canadian Fascinate, not the US T-Mobile Vibrant. Samsung has yet to release the 2.2 sources.
oka1 said:
Get a custom rom. There are so many good devs doing them don't waste your time on AOSP....... until they release the actual source code...... on April 22
Click to expand...
Click to collapse
Except the so-called "custom ROMs" are just modifications on the stock theme, a replacement kernel and a change of some of the supplied applications.
There is nothing close to a full "custom ROM" such as CyanogenMod or MIUI because we don't have Samsung's sources. What is passing for a "custom ROM" for the Vibrant are just repackaged files. It is akin to the "ROM cooking" that took place for the WinMo phones, not a truly ground-up build from source that is possible with Android.
EDT/Devs4Android has the MIUI build. From Source.
TW has a 2.2.1 in testing.
EDT has a 2.2.1 Beta released.
TW has a 2.3 AOSP in testing. From Source.
EDT has 2.2 AOSP in testing. From Source.
What you want is out there for you.
Watch the forums and reply when a call for Alpha testers is posted.
Hopefully it won't be long before you see a full TW/EDT/Devs4Android collaboration!
I think what the original poster is trying to ask (and I have the same question) is why were there never any real 2.1 AOSP, cyanogen5 for the vibrant. The source for 2.1 has been around for many months. Were some other proprietary bits missing, was the released source code such a mess that it was unbuildable, something else? With those questions in mind, why will things be any different when the 2.2 source comes out?
mattb3 said:
I think what the original poster is trying to ask (and I have the same question) is why were there never any real 2.1 AOSP, cyanogen5 for the vibrant. The source for 2.1 has been around for many months. Were some other proprietary bits missing, was the released source code such a mess that it was unbuildable, something else? With those questions in mind, why will things be any different when the 2.2 source comes out?
Click to expand...
Click to collapse
Yes, this is more towards what I was getting at. We do not have Samsung's kernel sources for 2.2. And, we do not have a Samsung provided vendor overlay.
When we receive these two pieces, then a true AOSP build will be possible. However, we do have the 2.1 kernel sources, so why wasn't a true AOSP build possible then? What was missing, and can we actually expect Samsung to release the overlay that's needed?
Actually, that's true. I know it was old but why didn't anyone build a 2.1 cyanogen or aosp rom? (Not to say its easy.)
Sent from my SGH-T959 using XDA App
A noob question, kindly can someone explain what is the vendor overlay stuff?
Many thanks!
Where have you been?
rpcameron said:
I've been following the development of so-called ROMs for the Vibrant (and other SGS devices), but I have yet to see a single AOSP ROM. Even when Samsung released the original kernel sources for 2.1, there were no AOSP 2.1 ROMs. Why not? Is it because they don't know which BLOBs to pull for insertion or the proper vendor overlays?
Some developers have done great work with SGS kernels (especially supercurio and his Voodoo kernels ... eugene373's tend to always wipe the internal SD card unnecessarily ...). But, a kernel does not a ROM make ... therefore I ask, what is truly missing to build an AOSP ROM. I've gone through the sources, but I don't follow makefiles too well.
I know we have another month or so before Samsung is obligated to release their 2.2 kernel sources, but that should have no impact on 2.1 AOSP ROMs. Therefore, I ask "what is the hold up?" What is missing, and what might I contribute ...
Click to expand...
Click to collapse
Dude theres been a true AOSP ROM for the Vibrant since like december and thats CM 6.1
Im running it now
rpcameron said:
I've been following the development of so-called ROMs for the Vibrant (and other SGS devices), but I have yet to see a single AOSP ROM. Even when Samsung released the original kernel sources for 2.1, there were no AOSP 2.1 ROMs. Why not? Is it because they don't know which BLOBs to pull for insertion or the proper vendor overlays?
Some developers have done great work with SGS kernels (especially supercurio and his Voodoo kernels ... eugene373's tend to always wipe the internal SD card unnecessarily ...). But, a kernel does not a ROM make ... therefore I ask, what is truly missing to build an AOSP ROM. I've gone through the sources, but I don't follow makefiles too well.
I know we have another month or so before Samsung is obligated to release their 2.2 kernel sources, but that should have no impact on 2.1 AOSP ROMs. Therefore, I ask "what is the hold up?" What is missing, and what might I contribute ...
Click to expand...
Click to collapse
For probably the same reason that many phones with non AOSP firmware running 1.5/1.6 did not bother with AOSP 1.5/1.6 when they were released around the time 2.1 source hit. Why bother developing at all for what is essentially an "out of date" OS.
The only people it seems who actively continue to develop for existing (as opposed to new) firmware are manufacturers and carriers. This stupidity should be left to the manufacturers who still do this.
One of the larger snags way back then (sits in his rocking chair on the porch) was a lack of understanding of the phones proprietary aspects and how to work around them. But we have a fairly clear understanding of Samsung's boot process now, and RFS can now easily be turned into a distant memory.
I would wager a guess that the apathy towards 2.1 will not repeat itself once we have 2.2 source widely available and the low level similarities between 2.2 and 2.3 should have Gingerbread being more than the experiment it currently is. It's been barely more than a week since Eugene's little present manifested and there are already proper and stable kernels available.
Keep in mind that the devs we do have, have done a phenomenal job of cleaning up, speeding up, and drastically enhancing our existing 2.2 release. And perhaps to the point where many will not really care, though I know many would still like to see CyanogenMod6/7 properly on this phone.
Master&Slave™ said:
Dude theres been a true AOSP ROM for the Vibrant since like december and thats CM 6.1
Im running it now
Click to expand...
Click to collapse
Um, that's not quite true. The CyanogenMod.com website lists 0 files available for download for either experimental or stable files. The CM6.1 you must be running is not a true CM build.
Also, CM is not AOSP, but rather AOSP with modifications.
phrozenflame said:
A noob question, kindly can someone explain what is the vendor overlay stuff?
Many thanks!
Click to expand...
Click to collapse
The vendor overlay tells the AOSP build system which proprietary files are needed from the device that are not available in source form. This includes things like GPS and video drivers, baseband firmware for wireless radios, &c.
hi everybody !
a month age i decided to compile a new rom for my Galaxy S absolutely from AOSP source ( branch 2.2.1_r1 ) after some compile-time problem and many painful steps to resolve ,eventually the rom successfully built and can boot it up flawlessly on emulator.
i create a nandroid backup of current rom and installed the compiled one. but i am facing new problem :
1- the phone successfully boots but after short while screen began
flicking several time and the phone go in deep sleep and never wakeup
( power button or menu button does not do any thing )
2- touch screen works only for some second that I can unlock the
phone
3- there is no network available
4- I have downloaded samsung opesource package for GT-I9000. it
contains a folder named 'platform' but when i merge these files to
AOSP , the compile process stops and fails again. if there any one can
help me which files from samsung source should i merge and how ? if
you now the answer and dont have spare time then some internet link or
online document is really useful .i have no problem studding and
reading and searching . reaching to target is my only hope .
I am really disappointed why there is not a good and complete step2step tutorial to compile an AOSP rom for galaxy s (GT-I9000) !!
such docs is available for phones like dell streak , desire , dream , magic , .... . i really want to to active these aspect on XDA forum and with help of all you ( mods and masters ) try to create such tutorial that any one in world can use to refer . i think XDA is the only reference on net to collect and create such help and document. please help me and leave PM or comment to agree ot disagree and from where can i start ?!! thank in advanced .
edit :
there is a google groups post that i send my question in Android-platform . if you prefer please join this group and active that post to ask any question related to 'galaxy s compile from source ' .
post located at http://groups.google.com/group/android-platform/browse_thread/thread/da5d6f18f3bd3c9b
A few of Sony Ericsson's newest devices are queued up to get CyanogenMod Custom ROM. Thanks to recent code submitted by Diogo Ferreira, the bits needed to bring my favorite custom ROM to three smartphones in the Xperia family:
- Xperia Play: r.cyanogenmod.com/#change,7126
- Xperia Neo: r.cyanogenmod.com/#change,7128
- Xperia Arc: r.cyanogenmod.com/#change,7127
Currently the code to add these phones to the CyanogenMod family is awaiting approval to be merged into the CyanogenMod repository. Once that's done we can expect nightly builds to follow not long after.
From that point it's just a matter of time before Release Candidates and a Final Build is available.
Source: http://r.cyanogenmod.com/#q,status:open,n,z
Via: http://pocketnow.com/android/sony-xperia-play-neo-and-arch-getting-cyanogenmod-custom-rom
Woohoo! I am getting a bit sick of my SE ROM, I want a Cyanogen!
very nice, i wasn't expecting official nightlies for our play's
Great!!!!!!!!!
Official CM7 on my Xperia Play is Very very Great
Come on!!!!!!!!
I'd like to hear word from the FreeXperia team. Are they maintaining CM7 officially?
At any rate, I already ROM Manager ready for action ^^
This is only for plays that are bootloader unlockable right? Any progress on unlocking the bootloader on simlocked phones?
RacecarBMW said:
This is only for plays that are bootloader unlockable right? Any progress on unlocking the bootloader on simlocked phones?
Click to expand...
Click to collapse
We're making progress on CDMA phones.
The problem is that simlocked phones don't have RCK_H key so there's nothing to crack the unlock key from. But as said, I'll check it, I have some people willing to test.
Looks as though it has now been merged. Really looking forward 2 flashing nightlies. Cyanogen best mod by a looooooonnnnggggg stretch.
And just in time so that Verizon users can join the party
Hi, I am Diogo Ferreira (submitter of these patches)
I think you'd be happy to know that they are now already merged and in a buildable state with nightlies following soon.
This is not an alternative to FreeXperia work, it is FreeXperia work. We've been all working together to make this happen.
I'd be happy to answer questions you might have.
deovferreira said:
Hi, I am Diogo Ferreira (submitter of these patches)
I think you'd be happy to know that they are now already merged and in a buildable state with nightlies following soon.
This is not an alternative to FreeXperia work, it is FreeXperia work. We've been all working together to make this happen.
I'd be happy to answer questions you might have.
Click to expand...
Click to collapse
Hi Diogo. Glad to hear from you. Does this mean Xperias will be listed on CM homepage under supported devices, and will get official forum's section?
Given that most of the features worked already in the betas (great job by the FX folks), the main question for the Play resides on the camera. What's the status on that?
And for those people who have ROM Manager Premium, will the nightlies come through it as well?
No ETAS on camera. It will be done when it's done but we're looking into it.
As for nightlies, they should be available soon.
deovferreira, is the team making an official kernel as well to compliment the nightly builds? If we are using ROM Manager, then CWM Recovery is essential, and it would be great to have a kernel that had this built in, like the FreeXperia's team does now.
Also, will the ROM be generic for all users? I had quite a few issues with the radio yesterday on my CDMA Play when I tried FreeXperia's latest build. I just wanted to make sure that builds would support all versions of the play, not just the R800i.
Mills00013 said:
deovferreira, is the team making an official kernel as well to compliment the nightly builds? If we are using ROM Manager, then CWM Recovery is essential, and it would be great to have a kernel that had this built in, like the FreeXperia's team does now.
Also, will the ROM be generic for all users? I had quite a few issues with the radio yesterday on my CDMA Play when I tried FreeXperia's latest build. I just wanted to make sure that builds would support all versions of the play, not just the R800i.
Click to expand...
Click to collapse
What is on CM today is on par with what we did for FreeXperia, the kernel has a builtin recovery. You'll see instructions on this soon when nightlies start to hit.
As for CDMA, I am not aware what the differences are. I support a CDMA device (desire-cdma) but it is a PITA since I have no real way to test. What would be good is if someone steps up and tried to maintain a play-cdma port, I imagine the differences would be fairly minimal.
deovferreira said:
What is on CM today is on par with what we did for FreeXperia, the kernel has a builtin recovery. You'll see instructions on this soon when nightlies start to hit.
Click to expand...
Click to collapse
Awesome. The only reason I asked is because of how its different from other devices. The kernel always has to be flashed with fastboot. So I just didn't know how the updates would work or anything like that. I assume we just flash one to start the process and go downhill from there.
deovferreira said:
As for CDMA, I am not aware what the differences are. I support a CDMA device (desire-cdma) but it is a PITA since I have no real way to test. What would be good is if someone steps up and tried to maintain a play-cdma port, I imagine the differences would be fairly minimal.
Click to expand...
Click to collapse
I agree completely. It appears that the kernel was working fine, there is just something in the CM build that was preventing the radio from working correctly. Logcat was telling me that it detected a CDMA mode and enabled it but then the phone module would crash. It was late when I started looking into it though and didn't do a lot of research, but I imagine that someone has encountered this with a CDMA port from a GSM cousin before. I'll do some more investigation this evening.
The boot will always have to be flashed separately using fastboot due to the way the sony ericsson bootloaders transforms the boot image on flashing. System updates will be done using the recovery, as usual. At some point the kernel and system may get out of sync, the symptom would be wifi failing to enable, at which point people would have to flash a new kernel.
As for CDMA, the RIL libraries should be different as should some settings in build.prop.
Awesome. I'll see what I can do this evening, and maybe even pump out a working build from the source for CDMA users.
Guys, stay calm.
this is FreeXperia CM7 "just" as official CM
So that is what you all wanted.
We worked over some time now with Diogo, all of us 3 ( Diogo, jerpela and me) have commited our changes, put them together and worked together.
All will be good See it as a surprise
I'm working for over 1 month now everyday on camera support. For now nothing new, but new knowledge
currently i'm looking into camera for new 4.x Firmware release, maybe SE changed something in a good way for us...
Best Regards
Bin4ry
Team FreeXperia
Ok I just read the thread and maybe I missed it, my xperia play is from Rogers. Will I be able to install cm 7?
Sent from my Play, with XDA Premium.
Hi all,
i'm a noob to android, but i have nit of experience on other unix based systems.
I was wondering, why there is no custom roms for GT-S5690?
What's the problem?
Is bootloader locked some other way or is it somehow different from example Gio/GT-S5660?
There is a bunch of roms for gio..
I have one xcover, wich has no screen and covers, i thought i could use it for testing.
I think there are too less people who have a xcover, and I was actually pretty disappointed when I say there is a successor to the xcover available only in the US (Rugby Smart / Pro <-- with ICS!).
From the technical side, I don't know. Even the source code of the firmware is available at opensource.samsung.com. The Bootloader seems pretty much unlocked.
For me, the xcover is the best phone ever, it takes so much abuse. Maybe someday someone will port a newer ROM from the Ace/Gio/idk. It's a shame Samsung abandons their old phones :crying:
xkawer said:
I think there are too less people who have a xcover, and I was actually pretty disappointed when I say there is a successor to the xcover available only in the US (Rugby Smart / Pro <-- with ICS!).
From the technical side, I don't know. Even the source code of the firmware is available at opensource.samsung.com. The Bootloader seems pretty much unlocked.
For me, the xcover is the best phone ever, it takes so much abuse. Maybe someday someone will port a newer ROM from the Ace/Gio/idk. It's a shame Samsung abandons their old phones :crying:
Click to expand...
Click to collapse
I didn't were aware of successor models, now i'm very dissappointed.
I'm downloading these source codes at the moment, i'll check these out.
I'm not a developer, atleast YET..
AFAIK, hardware of s5690 is way different from any other samsung phones,
correct me if i'm wrong..
jonezy82 said:
AFAIK, hardware of s5690 is way different from any other samsung phones,
correct me if i'm wrong..
Click to expand...
Click to collapse
Seems like it's the only one with a Marvell MG2.
Let me know if you do anything interesting with the sources
Just flashed my xcover to XXLJ2 yesterday. At least it seems a bit faster now, but I have a weird bug when scrolling. If I give a list (for example settings) momentum, it doesn't stop when I put my finger on it again. But it does stop if I release the finger the second time.
jonezy82 said:
I'm downloading these source codes at the moment, i'll check these out.
Click to expand...
Click to collapse
Did the same. The GT-S5690_Platform.txt says:
Code:
How to build platform
1. Get android open source.
: version info - Android gingerbread 2.3.6
( Download site : http://source.android.com )
2. Remove external\webkit module in android open source which you got.
And then execute "clean build"
2. Copy files and modules to original Gingerbread source tree (overwrite)
3. build
- ./build.sh user
So wouldn't it be possible to download the JB sources, and compile them with the original kernel? Would be so cool.
Edit: It seems you need device specific binaries (drivers) since ICS. see: http://www.freeyourandroid.com/guide/compile-ics
Found a git https://github.com/manakeri/android_device_samsung_xcover, there is a
Code:
cyanogen_xcover.mk
file, this seems interesting. Apparently someone is trying to port it.
Edit2: In this git, there is also a "extract-files.sh"-file, which is neccessary to pull the proprietary files from the phone! With this I think we actually have everything we need to compile ICS/JB, like in the "freeyourandroid" tutorial.
I have never done this before, but someone must try it lol.
Oh look, there are more people who care about it!
http://www.droidevelopers.com/f338/14412-gt-s5690-opensource-kernel-available.html
Someone discovered my link and made a overclock kernel from the sources! This is so cool.
I hope we are going to see more :good:
xkawer said:
Oh look, there are more people who care about it!
http://www.droidevelopers.com/f338/14412-gt-s5690-opensource-kernel-available.html
Someone discovered my link and made a overclock kernel from the sources! This is so cool.
I hope we are going to see more :good:[/QUOTE
I own an xcover too a developer on another forum looked at some files i pulled using adb to try to port clockworkmod but no success. Told me the files i sent weren't standard android img but he would continue to look into it. Apparently the teamhacksungs goal is to port cyanogenmod for every Samsung device surely they can get it done. I've been waiting a long time to see some development for the awesome xcover
Click to expand...
Click to collapse
If its possible on the galaxy mini its got to be possible on xcover!. Ive tried to get involved and learn to port cyanogenmod but when it comes to git, repo, source tree, source code e.t.c e.t.c its a bit behond me for now.
Step in the right direction it seems. Fingers crossed
"The G2 Dream Team" (and they well deserve that name) has released not one, but TWO lollipop builds for the LG G2. Both ROMs are based on the same build tree, but one ROM is CM12 and the other is a LiquidSmooth 4.0 ROM. Despite being built from the same build tree, they carry different features. They are stable and usable for daily drivers, but they may carry some bugs, like a non-functional video playback, NFC issues for LS/VS980 but it should all be sorted out in the near future. Head over to the threads to read more!:
Liquidsmooth 4.0:
http://forum.xda-developers.com/lg-g2/development/rom-liquidsmooth-v4-0-lg-g2-t2948395
CM12:
http://forum.xda-developers.com/lg-g2/development/rom-cyanogenmod-12-0-lg-g2-t2944269
Older posts:
An increasing amount of devices have been receiving unofficial Android Lollipop 5.0 ports, like the HTC One M8 and the LG Optimus L9. Today another device can be added to the list of phones receiving a treatment with the taste of Android Lollipop, the LG G2. While there generally has been a wide contribution from the community; testing, sharing files and giving ideas, two XDA members stood out in particular in order to create the build, @ylukasy and @InfinitusDesigner. The port is still in a very early pre-alpha stage, and the bugs are barely known yet, but the ROM boots and has even been rooted! While it might be wisest to wait until an official thread has been made before grabbing your devices and start flashing, @ylukasy has already provided a download link for the ROM, and calls for people to help discover the bugs so that they can be eliminated. Please notice that the ROM might not be stable enough to be used as a daily driver, but owners of a LG G2 are officially an important step closer to having a stable Lollipop ROM!
If this post caught your interest and you're willing to take the risk, head over to the last pages in the following thread: http://forum.xda-developers.com/lg-g2/general/unofficial-cm12-nexus-5-posted-t2936398
As previously mentioned, a lot of things are not sorted out yet, and the build might not be for your device number, so make sure you read the entire thread before continuing, or simply wait untill an official thread is made.
Update:
An official thread has been posted and it can be found by following this link: http://forum.xda-developers.com/lg-g2/development/rom-android-lollipop-fast-clean-t2941922
The build is a port of the Nexus 5 ROM, and users of the ROM have been saying that the rom is very fast and fluid, calls work, camera works (although the quality is inferior), but other users have been reporting random reboots and incompatibilities with certain apps such as YouTube or WhatsApp.
by vPro97
This post will be updated regularly when new information regarding Lollipop ports surface.
Fantastic News! Will get round to trying it shortly, thanks for the link!
While I have my doubts about it being functional (or even booting) on my LS980, I'll give it a shot and see what happens.
Nice to see things moving at breakneck speeds these days.
On a side note, I just read the AnandTech review of the Nexus 6 and am happy to report that my well over a year old G2 beats it in several benchmarks so I'm pretty satisfied at the moment, especially considering I got it for free. I mean really...
In before "no build for xxxx?!?!?!?"
Anyone know how to port a d802 rom to d800?
Ready to try it out and see what happened..??
his build is from the same source the other was he doesn't deserve credit for it. it's using cm12 kernel and dev claims it's using nexus 5 port yet requires gapps and no signs of any nexus 5 code at all.
Wouldn't it be alot easier to just post the download link here?
₪LG G2₪
Zyner said:
Wouldn't it be alot easier to just post the download link here?
₪LG G2₪
Click to expand...
Click to collapse
It's not my work, and there are some steps which must be followed in order to make it work. I am just objectively informing any news regarding Android Lollipop for the LG G2.
OP has been updated.
The download link was removed before i could get the v3 version so im stuck with v2 and ive been using it as my daily (yeah it reboots every 5 minuets and i can leave wifi on or it will bootloop) But honestly thats the fun in testing this stuff out
MrNegative370 said:
The download link was removed before i could get the v3 version so im stuck with v2 and ive been using it as my daily (yeah it reboots every 5 minuets and i can leave wifi on or it will bootloop) But honestly thats the fun in testing this stuff out
Click to expand...
Click to collapse
Me too.
Is there anyone that can share privately the V3 version with me ? :fingers-crossed:
here is something better:
http://forum.xda-developers.com/lg-g2/development/rom-cyanogenmod-12-0-lg-g2-t2944269
Jam4l said:
here is something better:
http://forum.xda-developers.com/lg-g2/development/rom-cyanogenmod-12-0-lg-g2-t2944269
Click to expand...
Click to collapse
TY !
Can anyone port the Nexus 5 ROM?
Updating this thread later today if nothing gets in the way.
Hi everybody!!
I need a tester please:
I built pure AOSP for the D802 from sources of Android right now, has anybody time to test it?
It is an experimental build and I didn't test it right now, so I don't know if it is working, please make a backup from your current rom.
The build comes with an built in CWM recovery and should be with root access. It can be flashed with the same instructions like the CM 12 build.
Edit: Bootloop right now ... Anybody, can you take a logcat?
http://builds.hubdroid.com/otherroms/aosp_d802-ota-102.zip
Thank you in advance!! Please anybody who tries it: can you send me a pm?
Flo0008 said:
Hi everybody!!
I need a tester please:
I built pure AOSP for the D802 from sources of Android right now, has anybody time to test it?
It is an experimental build and I didn't test it right now, so I don't know if it is working, please make a backup from your current rom.
The build comes with an built in CWM recovery and should be with root access. It can be flashed with the same instructions like the CM 12 build.
http://builds.hubdroid.com/otherroms/aosp_d802-ota-102.zip
Thank you in advance!! Please anybody who tries it: can you send me a pm?
Click to expand...
Click to collapse
I'd love to test this for you, but I'm on Sprint LS980 Would you mind making a build for us?
iamterence said:
I'd love to test this for you, but I'm on Sprint LS980 Would you mind making a build for us?
Click to expand...
Click to collapse
Yes sure, but right now, I have to solve the bug, that the d802 wouldnt boot, so this may take some more time until I build it for other devices too.
Regards