"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
Related
Mods, if this is in the wrong section, please move it.
*sorry for the bad english*
Alright, the purpose of this thread is simple. I made this with the intention of uniting all of the d803 users, and give them the opportunity to post a request for a rom they would like to see on their d803's that is available for other variants such as the d802. At the moment, I've found a way to "port" only d802 roms to the d803, and by port I mean making some slight changes that allow the rom to boot in our devices without any or with the least issues possible. These two devices are very similar hardware-wise, so software wise it doesnt change much.
If there's any D802 rom that you would like to see on our D803, feel free to leave a reply and I will do my best to move my gears and upload it so you guys can have it! As we all know, the development scene for the Canadian variant isnt as active as the d801 or D802, and with this I aim to end that barrier by trying to make those roms available to our device
Too long didnt read version:
If the rom exists for the D802, post a reply and I will try to make it available for the D803
Disclaimer:
I am in no way a developer, I simply edit files and put them in the right place so it boots for us. I do this to help fellow d803 users.
If I helped with a file, always make a nandroid backup just in case things go haywire. Anything that happens to your phone is your responsibility.
Everything I submit gets tested rigorously on my own G2 before being posted to ensure its working, but we all get different results, so the experience might vary. Just a heads up.
Click to expand...
Click to collapse
Any suggestions or edits by mods to the post are welcome.
[email protected] said:
Mods, if this is in the wrong section, please move it.
*sorry for the bad english*
Alright, the purpose of this thread is simple. I made this with the intention of uniting all of the d803 users, and give them the opportunity to post a request for a rom they would like to see on their d803's that is available for other variants such as the d802. At the moment, I've found a way to "port" only d802 roms to the d803, and by port I mean making some slight changes that allow the rom to boot in our devices without any or with the least issues possible. These two devices are very similar hardware-wise, so software wise it doesnt change much.
If there's any D802 rom that you would like to see on our D803, feel free to leave a reply and I will do my best to move my gears and upload it so you guys can have it! As we all know, the development scene for the Canadian variant isnt as active as the d801 or D802, and with this I aim to end that barrier by trying to make those roms available to our device
Too long didnt read version:
If the rom exists for the D802, post a reply and I will try to make it available for the D803
Disclaimer:
Any suggestions or edits by mods to the post are welcome.
Click to expand...
Click to collapse
To port any ROM to any version just download your devices patch from dr87's Mahdi ROM thread then all u gotta do is change out the boot IMG, a few lines in the build prop n updater script then flash ROM, gapps, the patch then your good. We had a similar patch for toro on the gnex forum and I was waiting for the day someone put one together for us seeing as all g2's use the same mainboard. The days of worrying about whether your variant will get support is finally over, for aosp Roms at least. I'm gonna try doing it w a stock ROM to see if that works cuz that's something I'd really love to see. Cuz as a vs980 owner I can say from experience that our stock ROM development is lacking compared to the d802 or f320
blazewit said:
To port any ROM to any version just download your devices patch from dr87's Mahdi ROM thread then all u gotta do is change out the boot IMG, a few lines in the build prop n updater script then flash ROM, gapps, the patch then your good. We had a similar patch for toro on the gnex forum and I was waiting for the day someone put one together for us seeing as all g2's use the same mainboard. The days of worrying about whether your variant will get support is finally over, for aosp Roms at least. I'm gonna try doing it w a stock ROM to see if that works cuz that's something I'd really love to see. Cuz as a vs980 owner I can say from experience that our stock ROM development is lacking compared to the d802 or f320
Click to expand...
Click to collapse
Well I meant it more in a way for those who don't understand much about editing the updater script and exchanging the boot.IMG. with what I'm offering all they have to do is ask the ROM and I'll post it online with said changes in case they don't know how to do it. Something like a small favor for everyone, but thanks for the reply!
Request
If you could please port this rom I would very much appreciate it
http://forum.xda-developers.com/showthread.php?t=2609355
---------- Post added at 08:48 AM ---------- Previous post was at 08:38 AM ----------
blazewit said:
To port any ROM to any version just download your devices patch from dr87's Mahdi ROM thread then all u gotta do is change out the boot IMG, a few lines in the build prop n updater script then flash ROM, gapps, the patch then your good. We had a similar patch for toro on the gnex forum and I was waiting for the day someone put one together for us seeing as all g2's use the same mainboard. The days of worrying about whether your variant will get support is finally over, for aosp Roms at least. I'm gonna try doing it w a stock ROM to see if that works cuz that's something I'd really love to see. Cuz as a vs980 owner I can say from experience that our stock ROM development is lacking compared to the d802 or f320
Click to expand...
Click to collapse
Could you possibly make a quick tutorial on how to do this? or possibly direct me to where i could find one?
Hi, I was looking at your old thread about how you could port d802 roms to d803. I was wondering if you could port cyanogenmod 11 snapshot m12. http://download.cyanogenmod.org/?device=d802 i would really appreciate it. and it seems like u are good at what u do so you should maybe consider building for d803 for cyanogenmod. thousands of d803 users have been waiting for cyanogenmod support but to this day have recieved none. anyways if u could port it i would really appreciate it! thanks!
can you make lollippop rom pls
http://forum.xda-developers.com/lg-g2/development/rom-android-lollipop-fast-clean-t2941922
CM12 !
PLZ !
EDIT: We got it! It boots. But some things like RIL and audio are not working, but we'll get this sorted out soon.
Official thread here: http://forum.xda-developers.com/opt...opment/rom-cyanogenmod-12-1-lg-l3-ii-t3297897Hey guys! It seems like Caio has left the "scene", and we're left with CM11... Is there anyone able to "take over" the development of CM12 for E430? I know a little bit, but I can't do it myself....
Alright, what do we have?
A local manifest: https://github.com/TeamVee/android_.repo_local_manifests/tree/cm-12.1 that includes:
A device tree for CM11: https://github.com/TeamVee/android_device_lge_vee3
Vendor files for CM11: https://github.com/TeamVee/android_vendor_lge
Kernel for KitKat: https://github.com/TeamHackLG/lge-kernel-lproj
Display CAF for CM12.1: https://github.com/msm7x27a/android_hardware_qcom_display
Media CAF for CM12.1: https://github.com/msm7x27a/android_hardware_qcom_media
Shared L1/L3/L7 II files for CM12.1: https://github.com/TeamVee/android_device_lge_vee-common/tree/cm-12.1
We also have a build of CM12.1 recovery for E430 by me. Nevermind, broken.
L5's device tree for CM12.1: https://github.com/aidasaidas75/android_device_lge_e610
L5's vendor propretiary files for CM12.1: https://github.com/aidasaidas75/proprietary_vendor_lge/tree/cm-12.1-new/e610
What do we probably need?
A device tree for CM12.1 for L3 IINot needed.
Vendor files for CM12.1 for L3 IINot needed.
Lollipop kernel.Not needed.
We need a skilled developer/group of developer to do this. Anyone willing to participate? Any help is appreciated
Some more details: when I build CM12.1, it stops after building surfaceflinger. If you got any questions, ask me
Feel free to join me at the IRC channel for a little mindstorm: http://webchat.quakenet.org/?channels=teamvee
EDIT: I managed to build CM12.1 for LG L3 II, but I don't know if it's working or not - download here and tell me: https://www.androidfilehost.com/?fid=24345424848488130
Everyone, if you can help us create CM12.1, PM me your Telegram username (a great IM), I'll add you to a group chat. @aidasaidas75 @IGGYVIP and other devs are welcome.
dadziokPL said:
Hey guys! It seems like Caio has left the "scene", and we're left with CM11... Is there anyone able to "take over" the development of CM12 for E430? I know a little bit, but I can't do it myself....
Alright, what do we have?
A local manifest: https://github.com/TeamVee/android_.repo_local_manifests/tree/cm-12.1 that includes:
A device tree for CM11: https://github.com/TeamVee/android_device_lge_vee3
Vendor files for CM11: https://github.com/TeamVee/android_vendor_lge
Kernel for KitKat: https://github.com/TeamHackLG/lge-kernel-lproj
Display CAF for CM12.1: https://github.com/msm7x27a/android_hardware_qcom_display
Media CAF for CM12.1: https://github.com/msm7x27a/android_hardware_qcom_media
We also have a build of CM12.1 recovery for E430 by me. It's the only thing we can build with the local manifest. Download here: https://mega.nz/#!Io0xxBrR!gCin0V8pDZ_-PqAGTC05PfUEWTbdLhgqdBBMjnBrhdI (I would put it in the attachments, but it's 0.43 MB too big... Dammit :/
What do we probably need?
A device tree for CM12.1
Vendor files for CM12.1
Lollipop kernel.
We need a skilled developer/group of developer to do this. Anyone willing to participate? Any help is appreciated
Some more details: when I build CM12.1, it stops after building surfaceflinger. If you got any questions, ask me
Feel free to join me at the IRC channel for a little mindstorm: http://webchat.quakenet.org/?channels=teamvee
Click to expand...
Click to collapse
First you forgeted https://github.com/TeamVee/android_device_lge_vee-common and second i will still here if anyone need, i builded CM12.1 but, without any reason, the ROM not boot, but i not tried again.
Possible, maybe, i try to build this again after update of MK.
And my last TWRP is from CM12.1
Caio99BR said:
First you forgeted https://github.com/TeamVee/android_device_lge_vee-common and second i will still here if anyone need, i builded CM12.1 but, without any reason, the ROM not boot, but i not tried again.
Possible, maybe, i try to build this again after update of MK.
And my last TWRP is from CM12.1
Click to expand...
Click to collapse
Yeah, it's that recovery I built Also, I can't test ROMs for L3 II anymore, I changed to Windows Phone But I think my cousin still has my old L3 II. I'll see. BTW I got a new PC, with a quad-core Intel Core i5-4460, and I set up a VM on it, so can build and build and build BTW You don't have to build, it's not building...
I can test anything I've got dev phone e430 and not scared of bricks. So dangerous builds send to me first before you flash yourself new paper weight ...
Caio where did you get drivers for kk ? What device ? Does it have lollipop?
Also I'm not sure if possible to get lollipop working at all since bootloader will need upgrade too :/
IGGYVIP said:
I can test anything I've got dev phone e430 and not scared of bricks. So dangerous builds send to me first before you flash yourself new paper weight ...
Caio where did you get drivers for kk ? What device ? Does it have lollipop?
Also I'm not sure if possible to get lollipop working at all since bootloader will need upgrade too :/
Click to expand...
Click to collapse
I'm a noob. Explain to me, why will the bootloader need an upgrade? It worked fine from 4.1 to 4.4. Has Lollipop brought some new kinda... thing? I was also wondering how Caio got the drivers... And have you tried that recovery for CM12.1? Is it working? I can't test myself since I don't have that phone anymore. Technically I do, but I can't brick it.
Need more info and need a dev
dadziokPL said:
I'm a noob. Explain to me, why will the bootloader need an upgrade? It worked fine from 4.1 to 4.4. Has Lollipop brought some new kinda... thing? I was also wondering how Caio got the drivers... And have you tried that recovery for CM12.1? Is it working? I can't test myself since I don't have that phone anymore. Technically I do, but I can't brick it.
Click to expand...
Click to collapse
The bootloader I'm not 100% sure but all older devices needed bootloader upgrade before they booted into lollipop from kk.
Something about secure boot and the new way it handles things.
Not tested the recovery yet but no point yet really
first we need more info on what we stand on in terms of bootloader / drivers
Caio99BR are you here ?
What device did you use as base for cm11 on L3II ?
Also I think this phone has already done very big jump with 4.4.4 and running over 150% intended level.
Lets face it Lollipop will never be stable enough to be daily driver specially that making custom lollipop kernel is near impossible without proper sources ... And stock one (still not existing lollipop one) will be super slow with no useful functions.
I would like to see it happen but it will take pain and broken fingers from hitting keyboards
I'm just not sure if it makes sense since screen resolution is so low and general hardware is not ready for functions brought by 5.1
Basically there will be more pain than gain good for side project but not really something for public
4.4.4 on it is great and I think it should gracefully get old here with all the tweaks we managed
IGGYVIP said:
The bootloader I'm not 100% sure but all older devices needed bootloader upgrade before they booted into lollipop from kk.
Something about secure boot and the new way it handles things.
Not tested the recovery yet but no point yet really
first we need more info on what we stand on in terms of bootloader / drivers
Caio99BR are you here ?
What device did you use as base for cm11 on L3II ?
Also I think this phone has already done very big jump with 4.4.4 and running over 150% intended level.
Lets face it Lollipop will never be stable enough to be daily driver specially that making custom lollipop kernel is near impossible without proper sources ... And stock one (still not existing lollipop one) will be super slow with no useful functions.
I would like to see it happen but it will take pain and broken fingers from hitting keyboards
I'm just not sure if it makes sense since screen resolution is so low and general hardware is not ready for functions brought by 5.1
Basically there will be more pain than gain good for side project but not really something for public
4.4.4 on it is great and I think it should gracefully get old here with all the tweaks we managed
Click to expand...
Click to collapse
Ohh, secure boot, alright. I see.
I heard that Lollipop actually runs better than KitKat, and it was optimized for devices with 512 MB of RAM.
At least we can try and get it to build. We can build a recovery, which is a first step according to the porting wiki
So, I was right, we need device files, vendor files, and a kernel for Lollipop?
If Caio could tell us where he got the files for KitKat, we could do something....
IGGYVIP said:
I can test anything I've got dev phone e430 and not scared of bricks. So dangerous builds send to me first before you flash yourself new paper weight ...
Caio where did you get drivers for kk ? What device ? Does it have lollipop?
Also I'm not sure if possible to get lollipop working at all since bootloader will need upgrade too :/
Click to expand...
Click to collapse
First only the Adreno is not updated, because of vsync is broken and new Adreno Blobs use hwcomposer and this is broken because vsync. When i tried to test in KK with new Adreno Blobs this happened:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Second from L5, and yes but @aidasaidas75 confused all commits, and not said the recipe to anyone.
And last i have thought this but no way to change this, the display driver of bootloader is hard edited by LG, yes i tried.
Note: No one build can make a brick of device, only if fstab is edited
dadziokPL said:
I'm a noob. Explain to me, why will the bootloader need an upgrade? It worked fine from 4.1 to 4.4. Has Lollipop brought some new kinda... thing? I was also wondering how Caio got the drivers... And have you tried that recovery for CM12.1? Is it working? I can't test myself since I don't have that phone anymore. Technically I do, but I can't brick it.
Click to expand...
Click to collapse
And not say drivers, say vendor blobs or kernel drivers, this not is windows
IGGYVIP said:
The bootloader I'm not 100% sure but all older devices needed bootloader upgrade before they booted into lollipop from kk.
Something about secure boot and the new way it handles things.
Not tested the recovery yet but no point yet really
first we need more info on what we stand on in terms of bootloader / drivers
Caio99BR are you here ?
What device did you use as base for cm11 on L3II ?
Also I think this phone has already done very big jump with 4.4.4 and running over 150% intended level.
Lets face it Lollipop will never be stable enough to be daily driver specially that making custom lollipop kernel is near impossible without proper sources ... And stock one (still not existing lollipop one) will be super slow with no useful functions.
I would like to see it happen but it will take pain and broken fingers from hitting keyboards
I'm just not sure if it makes sense since screen resolution is so low and general hardware is not ready for functions brought by 5.1
Basically there will be more pain than gain good for side project but not really something for public
4.4.4 on it is great and I think it should gracefully get old here with all the tweaks we managed
Click to expand...
Click to collapse
I think you wanted to say the kernel and ramdisk.
Use "@" i will see this in seconds
I used L5/L7/MSM7x27a-Common/and some others msm7x27a devices
I think this cant be able to daily usage, but with DualBootPatcher, all will be possible.
I have through this too, but the Android Wear saved us , and if this work is a good progess, btw the last.
dadziokPL said:
Ohh, secure boot, alright. I see.
I heard that Lollipop actually runs better than KitKat, and it was optimized for devices with 512 MB of RAM.
At least we can try and get it to build. We can build a recovery, which is a first step according to the porting wiki
So, I was right, we need device files, vendor files, and a kernel for Lollipop?
If Caio could tell us where he got the files for KitKat, we could do something....
Click to expand...
Click to collapse
Device tree, vendor files and kernel need someone with experience to this, like @aidasaidas75, but him left L5 CM12 support.
My english is bad and my keyboard too
Sorry for mistypes and long post.
Topic subscript agan of right way now!
---------- Post added at 10:54 PM ---------- Previous post was at 10:52 PM ----------
See DualBoot Custom ROMs on the LG L3 II (via PC) in TOP FORUM DISCUSSIONS -------------------->
Just for case
Caio99BR said:
First only the Adreno is not updated, because of vsync is broken and new Adreno Blobs use hwcomposer and this is broken because vsync. When i tried to test in KK with new Adreno Blobs this happened:
Second from L5, and yes but @aidasaidas75 confused all commits, and not said the recipe to anyone.
And last i have thought this but no way to change this, the display driver of bootloader is hard edited by LG, yes i tried.
Note: No one build can make a brick of device, only if fstab is edited
And not say drivers, say vendor blobs or kernel drivers, this not is windows
I think you wanted to say the kernel and ramdisk.
Use "@" i will see this in seconds
I used L5/L7/MSM7x27a-Common/and some others msm7x27a devices
I think this cant be able to daily usage, but with DualBootPatcher, all will be possible.
I have through this too, but the Android Wear saved us , and if this work is a good progess, btw the last.
Device tree, vendor files and kernel need someone with experience to this, like @aidasaidas75, but him left L5 CM12 support.
My english is bad and my keyboard too
Sorry for mistypes and long post.
Topic subscript agan of right way now!
---------- Post added at 10:54 PM ---------- Previous post was at 10:52 PM ----------
See DualBoot Custom ROMs on the LG L3 II (via PC) in TOP FORUM DISCUSSIONS -------------------->
Just for case
Click to expand...
Click to collapse
Thanks for clearing up some stuff Caio!
Ok, so here are propertiary files for L5(for CM12.1): https://github.com/aidasaidas75/proprietary_vendor_lge/tree/cm-12.1-new/e610
And here are device blobs for L5(also for CM12.1): https://github.com/aidasaidas75/android_device_lge_e610
Let's see what we can do, we got @IGGYVIP, he knows a lot, and he pretty much started everything with modding L3 II, we can bring CM12.1 for our L3 II together!
I am the orders! e-e
Wow! Let's see what we can do, I can help them in some respects too, and I can test whatever they want. I'm not afraid to have a paperweight, and I know it will be worth it. If they need a Tester, I am the orders!
It's great idea to build CM12 on LG L3 II, and if we need testers, I have working E430 phone, and I can test unstable versions of this ROM.
MinusThousand said:
It's great idea to build CM12 on LG L3 II, and if we need testers, I have working E430 phone, and I can test unstable versions of this ROM.
Click to expand...
Click to collapse
Okay, but we need to get it to build first. It won't build, there are errors, we need a proper device tree and proprietary blobs for CM12.1.
dadziokPL said:
Hey guys! It seems like Caio has left the "scene", and we're left with CM11... Is there anyone able to "take over" the development of CM12 for E430? I know a little bit, but I can't do it myself....
Alright, what do we have?
A local manifest: https://github.com/TeamVee/android_.repo_local_manifests/tree/cm-12.1 that includes:
A device tree for CM11: https://github.com/TeamVee/android_device_lge_vee3
Vendor files for CM11: https://github.com/TeamVee/android_vendor_lge
Kernel for KitKat: https://github.com/TeamHackLG/lge-kernel-lproj
Display CAF for CM12.1: https://github.com/msm7x27a/android_hardware_qcom_display
Media CAF for CM12.1: https://github.com/msm7x27a/android_hardware_qcom_media
Shared L1/L3/L7 II files for CM12.1: https://github.com/TeamVee/android_device_lge_vee-common/tree/cm-12.1
We also have a build of CM12.1 recovery for E430 by me. It's the only thing we can build with the local manifest. Download here: https://mega.nz/#!Io0xxBrR!gCin0V8pDZ_-PqAGTC05PfUEWTbdLhgqdBBMjnBrhdI (I would put it in the attachments, but it's 0.43 MB too big... Dammit :/
L5's device tree for CM12.1: https://github.com/aidasaidas75/android_device_lge_e610
L5's vendor propretiary files for CM12.1: https://github.com/aidasaidas75/proprietary_vendor_lge/tree/cm-12.1-new/e610
What do we probably need?
A device tree for CM12.1 for L3 II
Vendor files for CM12.1 for L3 II
Lollipop kernel.
We need a skilled developer/group of developer to do this. Anyone willing to participate? Any help is appreciated
Some more details: when I build CM12.1, it stops after building surfaceflinger. If you got any questions, ask me
Feel free to join me at the IRC channel for a little mindstorm: http://webchat.quakenet.org/?channels=teamvee
Click to expand...
Click to collapse
Actually device l5 is not set correctly in your tread tbh almost all l5 dependencies set wrong in op even display caf
aidasaidas75 said:
Actually device l5 is not set correctly in your tread tbh almost all l5 dependencies set wrong in op even display caf
Click to expand...
Click to collapse
Yo dude long time no see
Any chance you could make git group with correct base set of whats there that can be used to build for vee3 ? (I'm aware there will be a lot to do and missing stuffs but nice set from you would be a great start )
IGGYVIP said:
Yo dude long time no see
Any chance you could make git group with correct base set of whats there that can be used to build for vee3 ? (I'm aware there will be a lot to do and missing stuffs but nice set from you would be a great start )
Click to expand...
Click to collapse
I started building again so it might be lucky day for e430
@aidasaidas75 happy days pure cm or else ?
@freeusername
Yo santy
Would you be interested in the challenge of kernel ?
We could really use your experience with custom building this
MERRY CHRISTMAS ALL
IGGYVIP said:
@aidasaidas75 happy days pure cm or else ?
@freeusername
Yo santy
Would you be interested in the challenge of kernel ?
We could really use your experience with custom building this
MERRY CHRISTMAS ALL
Click to expand...
Click to collapse
Kernel is easy peazy lemon squizy. I was hooked on csgo but now synched cm12.1 and and started messing around it . I have new git and started everything from scratch for e610 and e430
aidasaidas75 said:
Kernel is easy peazy lemon squizy. I was hooked on csgo but now synched cm12.1 and and started messing around it . I have new git and started everything from scratch for e610 and e430
Click to expand...
Click to collapse
Cool, seems like the Optimus L series won't die so quick! Thanks to people like you, IGGYVIP or Caio the L3 II is usable. My Lumia 535 was sent to repair a MONTH ago, and they are still waiting for parts to arrive. I got a substitute device from my carrier, and surprise surprise, it's the L3 II. I know it's not my device, and that I'll have to pay if they figure out that I installed a custom ROM, but I couldn't resist. I installed CM11. The stock ROM is complete ****, it's laggy and unusable. I don't know for how much longer, but I can test. And when I'll have to return the L3 II, my cousin that got my old L3 II from me said that he'll test for me
I created this thread to encourage people to keep making ROMs for this phone, and it seems like we got our best developers back! I'll help you as much as I can, but I'm not as advanced as you guys! Although I learned how to build Cyanogenmod from source, and I got a great PC, building CM11(with cache enabled)on a VM took not even an hour! If you want me to do something, just tell me, I got lots of free time, and I'll do what I can to help!
Good luck to y'all, let's see what we can make together!
dadziokPL said:
Cool, seems like the Optimus L series won't die so quick! Thanks to people like you, IGGYVIP or Caio the L3 II is usable. My Lumia 535 was sent to repair a MONTH ago, and they are still waiting for parts to arrive. I got a substitute device from my carrier, and surprise surprise, it's the L3 II. I know it's not my device, and that I'll have to pay if they figure out that I installed a custom ROM, but I couldn't resist. I installed CM11. The stock ROM is complete ****, it's laggy and unusable. I don't know for how much longer, but I can test. And when I'll have to return the L3 II, my cousin that got my old L3 II from me said that he'll test for me
I created this thread to encourage people to keep making ROMs for this phone, and it seems like we got our best developers back! I'll help you as much as I can, but I'm not as advanced as you guys! Although I learned how to build Cyanogenmod from source, and I got a great PC, building CM11(with cache enabled)on a VM took not even an hour! If you want me to do something, just tell me, I got lots of free time, and I'll do what I can to help!
Good luck to y'all, let's see what we can make together!
Click to expand...
Click to collapse
Wow, you will gonna have a bad time if something goes wrong with you substitute device , just for case not test the CM12 builds, and i updated device tree (vee-common) and local manifests, these are the Display and Media repos used in CM12.1 by @aidasaidas75:
https://github.com/SlimLP-Y300/android_hardware_qcom_display-caf
https://github.com/SlimLP-Y300/hardware_qcom_media
Just for case (i like this phrase ), my inspiration is people like you and these awesome devs who cares for keep this device alive (but sometimes get crazy and disappear sometimes because they are also people ).
Note: i will be still here, just for case :silly::victory:
Caio99BR said:
Wow, you will gonna have a bad time if something goes wrong with you substitute device , just for case not test the CM12 builds, and i updated device tree (vee-common) and local manifests, these are the Display and Media repos used in CM12.1 by @aidasaidas75:
https://github.com/SlimLP-Y300/android_hardware_qcom_display-caf
https://github.com/SlimLP-Y300/hardware_qcom_media
Just for case (i like this phrase ), my inspiration is people like you and these awesome devs who cares for keep this device alive (but sometimes get crazy and disappear sometimes because they are also people ).
Note: i will be still here, just for case :silly::victory:
Click to expand...
Click to collapse
These are for Huawei Y300/G510. Are you sure these are gonna work?
Also, my carrier valued the phone at around 25 euro, If they figure out, I'll just have to pay it, but I can keep the phone forever, no big deal
Since everyone kept asking and I myself wanted it, I decided to start this project. The main reason why I didn't do it earlier was because I needed Asus to release the Oreo build already so I could get the required files. So for now I leave you with this, hope I made your day a bit better and have a great day!
Note: the build you see here is just so I could get the compiler working.
Sweet!! Looking forward to seeing the progress on this.
Nice. Do you think the build will have camera quality issues though?
kekley said:
Nice. Do you think the build will have camera quality issues though?
Click to expand...
Click to collapse
We'll see once I get a debuggable build running. I hope it's smooth sailing, but I can't guarantee anything.
First build?
Is this the first build?
If you want tester I am always available.
Naman Vashishth said:
Is this the first build?
If you want tester I am always available.
Click to expand...
Click to collapse
Nice to hear that you want to test the rom, but unfortunately I still don't have a flashable build. I try to work on it whenever I can to get one out as soon as possible. Do keep in mind I do this in my free time when I'm not busy with school. When I do get a debuggable build out, I'll let this forum know so I can get some testers to test it out (other than myself).
+)KEV1N(+ you are a savior , please help us get rid this sick twisted ASUS stock firmware , it's a mess in every aspect , heat, poor battery life, muffled sound via headphones, enormous amount of services running in the background (loses 20% overnight), complete failure in both firmware and kernel wise cause they massively overclocked that S625 , i can live with a rom without the main camera app , OpenCam will do just fine , just take care of that power consumption please cause on paper it should deliver 12-16h SOT , it's 5000mah with s625 and AMOLED screen for god sake !
Thank you in advance for your effort.
Kevin,
Thanks so much for taking on this project!
Not many have the skills or time to do a project like this. I think I can speak for all Z3Z owners when I say that your work will not go unappreciated.
I am simply observing the work of the gentlemen, let us continue in this to create a lineage.
rinampa said:
I am simply observing the work of the gentlemen, let us continue in this to create a lineage.
Click to expand...
Click to collapse
It is a slow process, especially since this is my daily driver. I just came back from holidays back home and now I'll continue to work on it whenever I get the chance. I'll get a working test build running eventually. Can't guarantee when, just know that as a new developer it'll take time to fix things and put them in place since porting is also not easiest of projects.
I visit this thread multiple times a day, it gives me hope)
Thank u Sir
I'm grateful that you are working on this project.
Take your time & carry on.
I want do downgrade form Oreo to MM, Q: will i need to extract recovery.img form MM zip and flash it separately or the stock Oreo recovery will work with all raw asus builds ?
Build# : ww-11.41.87.2 this is the latest MM update before Nougat update, i'm a little confused cause every build has it's own method so any advice for the safest fastest way to :
1-Downgrade to MM from Oreo
2-Flash Magisk to root and install greenify , viper4android cause i'm done with this Oreo.
3-Do i need to unlock the bootloader ?
4-Do i need twrp to flash migisk?
5-Does twrp work with all versions of android ?
3-What are the cons of this procedure if a custom ROM would fall from heaven and i would want to flash it after i flash MM?
sam.fisher190 said:
I want do downgrade form Oreo to MM, Q: will i need to extract recovery.img form MM zip and flash it separately or the stock Oreo recovery will work with all raw asus builds ?
Build# : ww-11.41.87.2 this is the latest MM update before Nougat update, i'm a little confused cause every build has it's own method so any advice for the safest fastest way to :
1-Downgrade to MM from Oreo
2-Flash Magisk to root and install greenify , viper4android cause i'm done with this Oreo.
3-Do i need to unlock the bootloader ?
4-Do i need twrp to flash migisk?
5-Does twrp work with all versions of android ?
3-What are the cons of this procedure if a custom ROM would fall from heaven and i would want to flash it after i flash MM?
Click to expand...
Click to collapse
Guess what !!!
https://forum.xda-developers.com/ze...nbrick-flash-stock-mm-asus-zenfone-3-t3840702
Its more than 100days now since this "little something" post.
Is there any progress dear KEVIN?
or shall I switch to some other device?
Aditya Tiple said:
Its more than 100days now since this "little something" post.
Is there any progress dear KEVIN?
or shall I switch to some other device?
Click to expand...
Click to collapse
I started at the end of my school year a couple of months back. I had a month-long hiatus in July due to me going back to my family back home. I came back in August and am working on it as a side project. Naman's helping me with this right now and so far we got till the boot animation. And then you have those times when we fix something and you go one step back. It's a slow process since the two of us aren't like 24/7 busy on the project. I usually work on it during weekends, but lately I've been needing my phone more and more since I'm very very busy with other priorities. Again, this is a side project I'm doing because I like coding and I like learning new things. So, I can't say for certainty when we can get a release out, but I work eagerly every time hoping it gets past the boot animation or even gets there if I fix something.
I hope this clears out any misconceptions you may have of me and this project. Have a further great day sir
It's nice to hear from you.
That's d very reason I visit this thread.
Keep ur good work going.
Keep us updating.
All d best
Hello mate, you know the whole world is waiting for this build from xda to 4pda to every other android community so what's the news my friend? can you post the bugs maybe we can help with some of them and learn about the Lineage route you chose.
The midterm examination is about to start and you'll be too busy with the study!
My full appreciation to your work.
Instead of quenching our thirst, op made it worse... Shame no developer decided to code for this device.
Mrkblo said:
Instead of quenching our thirst, op made it worse... Shame no developer decided to code for this device.
Click to expand...
Click to collapse
There is a developer who is willing to port lineage if people will crowdfund the purchase of a Z3Z for them.
https://forum.xda-developers.com/zenfone-3-zoom/help/search-developer-custom-rom-t3793680/page2
All the blah blah about "as is", you being responsible for what you choose to do and do to your device, no guarantees implied nor stated... And all the usual to install. I wont be paying much attention to bugs, however, PLEASE post them as you find them to let others know what they can expect.
This build is a ONE-OFF and you should look at the original thread by @Krizthian for possible future builds. https://forum.xda-developers.com/google-nexus-5/development/rom-crdroid-v4-0-google-nexus-5-t3767591
Special thanks to @haze_nme who provided the device and kernel for without which this build would not be possible. Please visit his post and give the thanks button a BIG slap! https://forum.xda-developers.com/showpost.php?p=76807742&postcount=315
Of course, thanks to the crDroid team for providing the ROM source itself; and making it so easy to build using LineageOS device trees.:good:
Changes from the default source:
Code:
[FONT="Verdana"] Added the MiXplorer [url]https://forum.xda-developers.com/showthread.php?t=1523691[/url]
I got the OK first too include in my unofficial ROMs that I build, visit the forum, they are very helpful for this VERY powerful file explorer. [url]https://forum.xda-developers.com/showthread.php?t=1523691[/url]
You can thank @HootanParsa for building it, and letting me include it:good: Be sure to share some thanks.
Switched over to the ResurrectionRemox launcher. I had issues with the default launcher in crDroid. Also on another device, and I think I have read some other users had the same on even more devices.
Vinyl Music Player and removed crDroid music.
It has more features but is based off the same original app in crDroid. Including a dark theme!
Just to be polite I checked with the dev to get his ok, even though its open source. It can also be fund on F-Droid
OmniClock replaces the standard deskclock. Sourced from OmniROM, so a big thanks to them. It has a nicer dark skinn also.
[/FONT]
I have only done a rudimentary test on it. I flashed PICO Gapps, and there aint much room left in the system partition.
Source: https://github.com/crdroidandroid
Device: https://github.com/hazenme/android_device_lge_hammerhead
Kernel: https://github.com/hazenme/android_kernel_lge_hammerhead
Vendor: https://github.com/TheMuppets/proprietary_vendor_lge
You can download this build, and flash at your own risk, from:
crDroidAndroid-8.1-20180614-hammerhead-v4.4-DiamondJohnDroid.zip
MD5: 25e05c3f02d34968f308ac6b4ad32b8b
Thanks a bunch, I am eager to test this out and will update once I get a chance.
Good news, love crdroid rom, downloading. , thanks
Thank you so much for taking this project, I'm waiting for updates
Greetings
Krizthian said:
Thank you so much for taking this project, I'm waiting for updates
Click to expand...
Click to collapse
I wouldnt be too grateful, it was a one-off build of a secondary/spare device I have. While I await updates to my daily devices' kernel and device tree
DiamondJohn said:
This build is a ONE-OFF and you should look at the original thread by @Krizthian for possible future builds. https://forum.xda-developers.com/google-nexus-5/development/rom-crdroid-v4-0-google-nexus-5-t3767591
...snip....
Special thanks to @haze_nme who provided the device and kernel for without which this build would not be possible. Please visit his post and give the thanks button a BIG slap! https://forum.xda-developers.com/showpost.php?p=76807742&postcount=315
...snip....
Source: https://github.com/crdroidandroid
Device: https://github.com/hazenme/android_device_lge_hammerhead
Kernel: https://github.com/hazenme/android_kernel_lge_hammerhead
Vendor: https://github.com/TheMuppets/proprietary_vendor_lge
Click to expand...
Click to collapse
Maybe I too should be looking at the commits made into @Hazenmetrees to possibly see what needs to be done against my actual device.
DiamondJohn said:
I wouldnt be too grateful, it was a one-off build of a secondary/spare device I have. While I await updates to my daily devices' kernel and device tree
Maybe I too should be looking at the commits made into @Hazenmetrees to possibly see what needs to be done against my actual device.
Click to expand...
Click to collapse
Oreo for RAZR M perhaps?
That'd be quite the display if you could get that to work, assuming that is still your daily device. I have an N5 spare as well, but the WiFi chip broke : (
4.4 is working like a champ here. Many thanks. Tried to install ElementalX 9.02 but it wouldn't take. Will investigate further soon.
Galaxyninja66 said:
Oreo for RAZR M perhaps?
That'd be quite the display if you could get that to work, assuming that is still your daily device. I have an N5 spare as well, but the WiFi chip broke : (
Click to expand...
Click to collapse
Cast your mind back. My Razr is dead! Upgrading the kernel (and the device tree) is a big task. We were very lucky for Nougat, as the XT897 was pretty damn close and it had an official LOS build. ie the device tree and kernel were basically ready to kang. As far as I know, there is no official Oreo for the xt897 and therefore, unless you spend the time and effort, there is no Oreo for the xt907/xt905/xt926 etc etc.
For now I use and build for an GT-i9506 as my daily, and I also have an N5 as a "spare", which is half dead (mic is flakey which makes a phonee useless). I build for the N5 as "practice" for the S4, and I shared the results here, as I saw the current builds were quite old; [sarcasm]and I'm such a nice guy[/sarcasm]
DiamondJohn said:
Cast your mind back. My Razr is dead! Upgrading the kernel (and the device tree) is a big task. We were very lucky for Nougat, as the XT897 was pretty damn close and it had an official LOS build. ie the device tree and kernel were basically ready to kang. As far as I know, there is no official Oreo for the xt897 and therefore, unless you spend the time and effort, there is no Oreo for the xt907/xt905/xt926 etc etc.
For now I use and build for an GT-i9506 as my daily, and I also have an N5 as a "spare", which is half dead (mic is flakey which makes a phonee useless). I build for the N5 as "practice" for the S4, and I shared the results here, as I saw the current builds were quite old; [sarcasm]and I'm such a nice guy[/sarcasm]
Click to expand...
Click to collapse
Hmmm... messed up Nexus 5 you say... maybe we can trade mother boards via mail?
eh who am I kidding my Nexus 5 is worthless to me, the modem still works making it's purpose as a backup phone fulfilled
Thank you so much!!!!!!
@DiamondJohn : thanks man
4.5 will be?
see post https://forum.xda-developers.com/showpost.php?p=77301143&postcount=50
OP request.
THREAD CLOSED
Just found a link of a absolutely usable ROM for the N6P - here's the Android Open Sources illusion Projects's latest build (not my work!) which I couldn't find anywhere else, nor any discussion about it.
Posting this only reflects only my deepest appreciation about this work!
If I was blind to not see the corresponding thread I'm sorry!
(Then go ahead and please delete this if any concerns arise, just happy to see work on this almost forgotten devices...)
AOSiP-11-Ravioli-angler-20210311-1938.zip | by voidz-maguro for Nexus 6P
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Enjoy!
GAPPS can be easily found for 11 via Google, I found a nice project on XDA actually, it offers perfect support...
Suggestion from my side:
[Android 13] [GApps] NikGApps [ARM64]
Hi Everyone, Here I'd like to Introduce you with my custom Gapps package that I use on day to day basis when I flash a new Rom. As I've observed many people struggling with finding the correct version of gapps to flash, I decided to build a...
forum.xda-developers.com
Sorry if I did wrong posting this, it's just pure happiness for the community of N6P users!!!
I flashed dirty on RROS 10 with great results! (Edit: flashed clean later on, just to be sure)
My appreciation for this stable 11 build! Let's hope for more good stuff being on the way!
Thanks
Looks great and luv the name Ravioli! Cheers
Sam Nakamura said:
Just found a link of a absolutely usable link for the Android Open Sources illusion Projects's latest build (not my work!) which I couldn't find anywhere else, nor any discussion about it.
Posting this only reflects only my deepest appreciation about this work!
If I was blind to not see the corresponding thread I'm sorry! Then go ahead and please delete this if any concerns arise, just happy to see work on this almost forgotten devices...
AOSiP-11-Ravioli-angler-20210311-1938.zip | by voidz-maguro for Nexus 6P
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Enjoy!
GAPPS can be easily found for 11 via Google, I found a nice project on XDA actually...
Sorry if I did wrong, it's just pure happiness for the community of N6P users, I flashed dirty on RROS 10 with great results!
My appreciation for this stable 11 build! Thanks
Click to expand...
Click to collapse
Love this ROM, thanks to @voidz777 for building "THE ONLY STABLE ANDROID 11 ROM" for 6p at the moment, looking forward to updates on it.
Rom is good but not 100% stable..it has minor bugs such as hotspot is turning off within 10-15 minutes everytime and also phone is charging very slowly..other than that it's stable
Aditya kukreti said:
Rom is good but not 100% stable..it has minor bugs such as hotspot is turning off within 10-15 minutes everytime and also phone is charging very slowly..other than that it's stable
Click to expand...
Click to collapse
I don't use hotspot that much, but for charging issue what i did is i managed to lower down some clock cores and it works just fine without any isse with less heat
New update is up! Thanks @voidz777 for fresh stable update
Works nicely
A few hickups here and there. Did anyone get the smart controls to work?
I am missing the option to add controls, not sure if that is an ASOP thing or something else.
as @Ata Ur Rehman already said, there has been a new update (May 26th), which can be found here:
AOSiP-11-Ravioli-angler-20210526-0638.zip | by voidz-maguro for Nexus 6P
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Also here is the .txt file with a message from @voidz777 (or voidz-maguro):
"I have been interested in other hobbies since March and left 6P alone.
In Japan, the rainy season starts in June and I can only work at home.
Probably I will play with angler for a while.
For the time being, I synced to the May source of aosip.
Device modification corresponds to drm (L3).
selinux is parmissive without change. Because it is very time-consuming to make it enforce. It will take a little longer.
Camera fix? I can't. Find a camera app that you can use without problems.
Even with this, I will spend a lot of time trying in my own way.
Is English strange? It's because of Google Translate.
I want to spend more time on other things than spending time translating into English."
Click to expand...
Click to collapse
本当にありがとうございます (Thanks a lot)
There are admins who make me stupid on the Telegram channel, so I'm not motivated to do anything about angler. Please ask developers other than me that you like to develop angler.
I also gave the device to a friend.
From now on, I'm not involved with angler anymore.
voidz777 said:
There are admins who make me stupid on the Telegram channel, so I'm not motivated to do anything about angler. Please ask developers other than me that you like to develop angler.
I also gave the device to a friend.
From now on, I'm not involved with angler anymore.
Click to expand...
Click to collapse
I am sorry to hear that. And everybody does what they can ^^
I am only temporarily (hopefully) using angler, and for that your ROM is more than awesome to use.
Thanks again and much success on whatever else you are doing.
Amazing job keeping the Angler alive with this ROM. Been using this for a few weeks now.
Ata Ur Rehman said:
"THE ONLY STABLE ANDROID 11 ROM" for 6p
Click to expand...
Click to collapse
Is this still the case or have more options appeared by now?
Sorry, I haven't been following the scene for a while.
I have the problem when I try to flash the ROM , it send the error (Failed to Mount /Vendor (no such device)
Anyone knows how to fix it ???
tonyfierros said:
I have the problem when I try to flash the ROM , it send the error (Failed to Mount /Vendor (no such device)
Anyone knows how to fix it ???
Click to expand...
Click to collapse
Try flashing vendor image manually before flashing the ROM.
Same here. Which vendor image should be flashed?
Could somebody give a step by step advise how to do a clean flash with this ROM, pls?
Thanks.
raubo said:
Same here. Which vendor image should be flashed?
Could somebody give a step by step advise how to do a clean flash with this ROM, pls?
Thanks.
Click to expand...
Click to collapse
I got it installed. The vendor error message remains but the phone is up and running. And there are no problems but one: The German Fidor bank app is not installed, because the device is said to be not compatible. Usually this message comes up if the phone is rooted. Magisk is not installed. Is the phone with this ROM rooted by itself? Any ideas?
The installation seemed to be OK. But stuck in the boot logo when booting to the system. need help.
SLo
Go to recovery and clear data and reboot.
The camera from Gapp works well, but only one is work.
I try Gcam 8.1 from BSG and the Gcam from Play Store, they work will one photo only.
BTW where did you find this ROM? I can't find any in google.
I tried searching for it and couldn't find it either???