I know this has been covered in one way or another in other threads but mine is slightly different. I have the newest philz touch recovery for my ls-970. I installed the newest cm12 unofficial (nightly 1/11/2015 is the newest). I then installed jolla kernel but was having problems with system ui crashing so i stupidly decided to install the stock version of the kernel ( this kernel is an all in one bundle using aroma to select which kernel for your device). Right after this was installed, it would not boot into cm12 and gave me this lg security error. Problem is all Ig et is the LG symbol and the words security error. Unlike other people that have a cause listed, this has nothing. I am able to go into recovery easily. The boot loader still says unlocked (i assume fastboot is an option too?). I installed optimus de (which was residing as a backup on my sd) and the phone boots fine. But as soon as I go back to cm12, it has a security error. I have already taken it upon myself to download lgnpst and the lg drivers.
What are my options here? When it shows this error, it simply powers off after a few seconds.
thejase said:
I know this has been covered in one way or another in other threads but mine is slightly different. I have the newest philz touch recovery for my ls-970. I installed the newest cm12 unofficial (nightly 1/11/2015 is the newest). I then installed jolla kernel but was having problems with system ui crashing so i stupidly decided to install the stock version of the kernel ( this kernel is an all in one bundle using aroma to select which kernel for your device). Right after this was installed, it would not boot into cm12 and gave me this lg security error. Problem is all Ig et is the LG symbol and the words security error. Unlike other people that have a cause listed, this has nothing. I am able to go into recovery easily. The boot loader still says unlocked (i assume fastboot is an option too?). I installed optimus de (which was residing as a backup on my sd) and the phone boots fine. But as soon as I go back to cm12, it has a security error. I have already taken it upon myself to download lgnpst and the lg drivers.
What are my options here? When it shows this error, it simply powers off after a few seconds.
Click to expand...
Click to collapse
I am not sure, but the "Stock" kernel you flashed might have been for a locked bootloader. It seems backwards, but I know you get that error when you flash a rom, or another kernel that is not for a locked device on a locked bootloader.
Try this:
Restore your CM12 or flash a new one;
flash the rom again so it will be the built in kernel, OR
Flash an alternate kernel.
I am not sure which CM you used but there are a few different ones. If you used the official, I don't think jollaman has support for it yet.
Same goes for the unofficial ls970. They are both built with gproj sources, so you will have to find a kernel that uses the same sources. I believe solid kernel does. It is in the international threads, they use the same sources (not all do, if you see GEE, that is not gproj. that is unified across most of the Optimus G devices).
dopy25 said:
I am not sure, but the "Stock" kernel you flashed might have been for a locked bootloader. It seems backwards, but I know you get that error when you flash a rom, or another kernel that is not for a locked device on a locked bootloader.
Try this:
Restore your CM12 or flash a new one;
flash the rom again so it will be the built in kernel, OR
Flash an alternate kernel.
I am not sure which CM you used but there are a few different ones. If you used the official, I don't think jollaman has support for it yet.
Same goes for the unofficial ls970. They are both built with gproj sources, so you will have to find a kernel that uses the same sources. I believe solid kernel does. It is in the international threads, they use the same sources (not all do, if you see GEE, that is not gproj. that is unified across most of the Optimus G devices).
Click to expand...
Click to collapse
I did indeed use the unofficial built from gproj sources. That was my mistake. I wound up cleaning it out and restarting fresh with the same rom. It's a shame as it runs so well. Thanks for the tip on solid kernel, I'll check it out. Just to be clear, with the ls970 I can basically run any international rom as long as the kernel is right?
Sent from my LG-LS970 using XDA Free mobile app
thejase said:
I did indeed use the unofficial built from gproj sources. That was my mistake. I wound up cleaning it out and restarting fresh with the same rom. It's a shame as it runs so well. Thanks for the tip on solid kernel, I'll check it out. Just to be clear, with the ls970 I can basically run any international rom as long as the kernel is right?
Sent from my LG-LS970 using XDA Free mobile app
Click to expand...
Click to collapse
Actually, the international and the Sprint are basically the same phone. The only difference I know of is that their SIM is removable and ours is built in. So essentially you can use any of their ROMs but you might have data issues. I know any of the ROMs Kevin builds will work for both devices with little to no issues. OMNI runs perfect, the others have data toggle not working and built in messenger not working. OMNI is almost identical to CM at this point. The only thing I can think of right off hand is the messenger and gallery apps are different and I think OMNI has some extra options in the settings of the device.
You want a great rom, try omni. You will not be disappointed. Plus, you can use Jollaman's kernel if you really want to. Use his GEE kernel option. Built in kernel is great for me and I am constantly on my device.
ALSO: there are no mistakes using the official or unofficial. Each has their perks or quirks. Both are amazing.
dopy25 said:
Actually, the international and the Sprint are basically the same phone. The only difference I know of is that their SIM is removable and ours is built in. So essentially you can use any of their ROMs but you might have data issues. I know any of the ROMs Kevin builds will work for both devices with little to no issues. OMNI runs perfect, the others have data toggle not working and built in messenger not working. OMNI is almost identical to CM at this point. The only thing I can think of right off hand is the messenger and gallery apps are different and I think OMNI has some extra options in the settings of the device.
You want a great rom, try omni. You will not be disappointed. Plus, you can use Jollaman's kernel if you really want to. Use his GEE kernel option. Built in kernel is great for me and I am constantly on my device.
ALSO: there are no mistakes using the official or unofficial. Each has their perks or quirks. Both are amazing.
Click to expand...
Click to collapse
Could you link me to the omni for ls970 thread?
Sent from my LG-LS970 using XDA Free mobile app
thejase said:
Could you link me to the omni for ls970 thread?
Sent from my LG-LS970 using XDA Free mobile app
Click to expand...
Click to collapse
It's not specifically for the ls970, it's for any gee* device.
http://forum.xda-developers.com/optimus-g-intl/orig-development/rom-cyanogenmod-12-t2980060
Choose one of the servers, you'll see a link to parent directory, from there you'll see omni and the others.
Any gee*= you might need a different kernel for gee/b.
dopy25 said:
It's not specifically for the ls970, it's for any gee* device.
http://forum.xda-developers.com/optimus-g-intl/orig-development/rom-cyanogenmod-12-t2980060
Choose one of the servers, you'll see a link to parent directory, from there you'll see omni and the others.
Any gee*= you might need a different kernel for gee/b.
Click to expand...
Click to collapse
Thanks for much for the info! I installed Omni from the link and I cannot obtain root now. Says that root is not there. I tried towel root, freegee (refuses to load). Now what?
thejase said:
Thanks for much for the info! I installed Omni from the link and I cannot obtain root now. Says that root is not there. I tried towel root, freegee (refuses to load). Now what?
Click to expand...
Click to collapse
I replied to one of your other posts about root for omni (try to only ask once. It will be answered). Flash superSU from recovery.
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
dopy25 said:
I replied to one of your other posts about root for omni (try to only ask once. It will be answered). Flash superSU from recovery.
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Click to expand...
Click to collapse
Thank you and sorry.
Sent from my LGOG with much love to the xda community!
Related
Howdy folks
I'd like to thank:
Dan Rosenberg (djrbliss) for Loki (the exploit that allows for custom boot images)
Dees_Troy (for TWRP)
Everybody who has contributed to the CyanogenMod Project
xiaolu for github tools used for unpacking and repacking boot images
I picked up my brand new LG G2 on Friday and I've been hard at work to get CM10.1 booting on it ever since yesterday; but a few hours ago I got my first boot -> http://imgur.com/a/1sZz2
I'm using a few proprietary files that I'd like to not use in the future (more than just the Adreno blobs)
But I'm looking to get a team together to get this working 100%
I will post device and vendor source as soon as I get back from cleaning gutters at my dad's house
What works:
Literally nothing, Android won't boot unless you have the necessary EGL libraries, so I just threw those in because I knew it would boot, and nothing else just to get a bare-bones (but booting) ROM. You can navigate throughout UI fine though (it's very smooth believe it or not).
I'll also upload a proof-of-concept build for those willing to see what CM10.1 will look like on our G2s. I'm currently unable to flash a zip in TWRP recovery, so I have to boot into recovery, wipe data, boot into fastboot, flash a system.img and a boot.img and reboot
If I were any person who likes to ROM but will like to remain stock until there's a stable ROM, I'd add a random "#" to any empty line in the file /system/build.prop which will throw off the sha1sum checker when the recovery goes to install an OTA update (this will block all OTAs from ever installing, thus keeping the current boot image exploit viable and it won't be patched up as the OTA won't be able to install. (root is required)
Edit: kernel, device and vendor sources are up!
https://github.com/JackpotClavin/android_device_lge_g2
https://github.com/JackpotClavin/android_kernel_lge_g2
https://github.com/JackpotClavin/android_vendor_lge_g2
10/17/13:
http://forum.xda-developers.com/showpost.php?p=46554268&postcount=271
10/12/13: alpha
http://forum.xda-developers.com/showpost.php?p=46407049&postcount=138
10/3/13: Super alpha
http://forum.xda-developers.com/showpost.php?p=46147336&postcount=74
I would love to help, but I admit I don't know much about Android development. I've got an AT&T G2 and I know C# and a bit of C++, so I'm sure I can figure out C. I think it's awesome that you're working on CM, if I can help out somehow I'd love to!
Not trying to be a **** because I can't wait for CM on this device, but why 10.1? Why not just go ahead to CM 10.2 and Android 4.3?
bose301s said:
Not trying to be a **** because I can't wait for CM on this device, but why 10.1? Why not just go ahead to CM 10.2 and Android 4.3?
Click to expand...
Click to collapse
Because our kernel, etc., are all set up for Android 4.2.2. Meaning, it is easier to get 4.2.2 running, and then move forward to get 10.2.
JackpotClavin: We already have a "few" devs prepping a device tree, though it still misses the proprietary blob references. You should take a look at them, all the device trees are on Github, under TeamLGOG.
fonix232 said:
Because our kernel, etc., are all set up for Android 4.2.2. Meaning, it is easier to get 4.2.2 running, and then move forward to get 10.2.
JackpotClavin: We already have a "few" devs prepping a device tree, though it still misses the proprietary blob references. You should take a look at them, all the device trees are on Github, under TeamLGOG.
Click to expand...
Click to collapse
Ok, that is what I was thinking but I have never done any dev work or anything so I figured I would ask.
I cant help but I sure want to thank you folks for trying to get this up and running. This phone is an absolute BEAST! Coming from the gnex I'm excited about the G2's potential.
Sent from my VS980 4G using Tapatalk 4
Thanks!
I just wanted to thank you very very much for working on this! I knew this was going to be a well developed phone and I bet before 4 months we will have a good amount of choice as far as roms go. Thanks again!
I've been trying to port beanstalk to the G2 but I need the same information you are trying for. I need device trees to sync with. I can PM you with what info I've came up with So far if you are interested.?
Edit: tress are up! Great work
Sent from my LG-D800 using xda app-developers app
If you lived in my town I'd probably help by cleaning the gutters for you hehe. Thanks for your work!
Sent from my EVO using xda app-developers app
I am definitely willing to help in any way I can.
I am willing to beta test and report bugs, dont know much about development but I want CM i have been using it forever...
grandmasterlarry said:
I am willing to beta test and report bugs, dont know much about development but I want CM i have been using it forever...
Click to expand...
Click to collapse
same goes for me, I have the Korean version.
Does CyanogenMod get rid of features like KnockON? I have grown accustomed to it and don't know if I could do without it (my device sits in a vehicle dock a lot of the time where the buttons on the back are 100% inaccessible unless I disconnect the charger, remove phone from dock/holder and find the buttons on the back.)
Is KnockON a Snapdragon 800 feature, or an LG UI feature (I think so, as it doesn't seem to work except in the notif bar, the stock browser, and the stock lock screen)? Can it be added to the AOSP/CM code perhaps?
mrbig012 said:
Does CyanogenMod get rid of features like KnockON? I have grown accustomed to it and don't know if I could do without it (my device sits in a vehicle dock a lot of the time where the buttons on the back are 100% inaccessible unless I disconnect the charger, remove phone from dock/holder and find the buttons on the back.)
Is KnockON a Snapdragon 800 feature, or an LG UI feature (I think so, as it doesn't seem to work except in the notif bar, the stock browser, and the stock lock screen)? Can it be added to the AOSP/CM code perhaps?
Click to expand...
Click to collapse
LG UI feature. I'm fairly sure it will be ported to an AOSP/CM10/LGUI hybrid ROM at some point. I believe part of the issue that devs are running into is that a lot of the custom LG software appears to be tied together.
Can you guys keep us updated on your progress, this is a make or break thing for me with this phone, CM is just so much better than any stock ROM that I don't know if I can deal with a phone that has no prospect of official support.
JackpotClavin said:
Howdy folks
I'd like to thank:
Dan Rosenberg (djrbliss) for Loki (the exploit that allows for custom boot images)
Dees_Troy (for TWRP)
Everybody who has contributed to the CyanogenMod Project
xiaolu for github tools used for unpacking and repacking boot images
I picked up my brand new LG G2 on Friday and I've been hard at work to get CM10.1 booting on it ever since yesterday; but a few hours ago I got my first boot -> http://imgur.com/a/1sZz2
I'm using a few proprietary files that I'd like to not use in the future (more than just the Adreno blobs)
But I'm looking to get a team together to get this working 100%
I will post device and vendor source as soon as I get back from cleaning gutters at my dad's house
What works:
Literally nothing, Android won't boot unless you have the necessary EGL libraries, so I just threw those in because I knew it would boot, and nothing else just to get a bare-bones (but booting) ROM. You can navigate throughout UI fine though (it's very smooth believe it or not).
I'll also upload a proof-of-concept build for those willing to see what CM10.1 will look like on our G2s. I'm currently unable to flash a zip in TWRP recovery, so I have to boot into recovery, wipe data, boot into fastboot, flash a system.img and a boot.img and reboot
If I were any person who likes to ROM but will like to remain stock until there's a stable ROM, I'd add a random "#" to any empty line in the file /system/build.prop which will throw off the sha1sum checker when the recovery goes to install an OTA update (this will block all OTAs from ever installing, thus keeping the current boot image exploit viable and it won't be patched up as the OTA won't be able to install. (root is required)
Edit: device and vendor sources are up!
https://github.com/JackpotClavin/android_device_lge_g2
https://github.com/JackpotClavin/android_vendor_lge_g2
Click to expand...
Click to collapse
Are we going to try getting mobile network and wifi working first? Is adb working?
droid_<3er said:
Are we going to try getting mobile network and wifi working first? Is adb working?
Click to expand...
Click to collapse
First is audio. It's proving to be a big problem. I can't get anything working using either prebuilt binaries from stock, or building from source
JackpotClavin said:
First is audio. It's proving to be a big problem. I can't get anything working using either prebuilt binaries from stock, or building from source
Click to expand...
Click to collapse
I am NOT a developer, but this could help perhaps?
http://opensource.wolfsonmicro.com/content/wm5110-linux-driver-released
Not sure if it really is open source or only available as binaries, but the WM5110 is the audio SoC in this phone... I am probably not helping.
Additionally, I think the S4 uses this SoC as well. It's a pretty new part but is gaining a lot of momentum.
Edit: My god that WM5110 is a hell of a part... quad-core, 600 MIPS... dayum!
Glad to hear an update, even if it's about issues. Seeing that there are people actively working on this to make it happen makes me much happier and less worried about keeping this phone vs. returning it tomorrow or Friday to see how the Nexus 5 plays out etc.
Have any of you tried talking to Ricardo Cerqueira? He is in fact the primary maintainer for all LG Devices with regards to Cyanogenmod. I am sure he is planning on supporting this device in the near future, I just don't know when. It will probably be when the device is more readily available since it was pretty much just released.
They are released officially und http://download.cyanogenmod.com/?device=n1 :victory:
With the lastest "cm-11-20140126-NIGHTLY-n1.zip" I get no location data - wich makes the N1 unusable for Maps, Foursquare, Ingress aso..
Switches back to "cm-11-20140124-NIGHTLY-n1.zip" everything works fine again.
Flash with stock recovery?
Is there a way to flash a nightly build with the sotck recovery? If not how to change the recovery? Thx
dryll said:
Is there a way to flash a nightly build with the sotck recovery? If not how to change the recovery? Thx
Click to expand...
Click to collapse
You will not be able to flash this with the stock recovery. I imagine once it goes stable CM will push out an official update that will work on the stock recovery setup.
Until then, TWRP works great: http://forum.xda-developers.com/showthread.php?t=2537080
dryll said:
Is there a way to flash a nightly build with the sotck recovery? If not how to change the recovery? Thx
Click to expand...
Click to collapse
I bet I could make that happen. Probably just a reverse of what I do to make it flash in TWRP instead of stock. I bet I could add the first line back in and have it flash properly.
Harfainx said:
I bet I could make that happen. Probably just a reverse of what I do to make it flash in TWRP instead of stock. I bet I could add the first line back in and have it flash properly.
Click to expand...
Click to collapse
Flashify works great for installing TWRP, just backup your stock recovery first, that way you can flash it back before rebooting recovery and flashing colour OS. 27th Nightly is available.
mcteague said:
Flashify works great for installing TWRP, just backup your stock recovery first, that way you can flash it back before rebooting recovery and flashing colour OS. 27th Nightly is available.
Click to expand...
Click to collapse
I meant flash nightlies in stock recovery. I have TWRP on mine, but I bounce back and forth for testing.
Sent from my N1 using Tapatalk
Harfainx said:
I meant flash nightlies in stock recovery. I have TWRP on mine, but I bounce back and forth for testing.
Sent from my N1 using Tapatalk
Click to expand...
Click to collapse
I'm 90% certain stock recovery will not flash nightlies, as it will only flash ZIPs signed with specific signing keys.
Unless CM is signing their nightly ZIPs with the same key as their "official" releases, which is highly unlikely.
Entropy512 said:
I'm 90% certain stock recovery will not flash nightlies, as it will only flash ZIPs signed with specific signing keys.
Unless CM is signing their nightly ZIPs with the same key as their "official" releases, which is highly unlikely.
Click to expand...
Click to collapse
Correct. Currently since they're coming direct from CM as nightlies, they aren't final stable versions. Those will be released like the other two were, and I'm sure will be built to flash in the N1 Stock Recovery.
Location not working
location still not working on latest nightly (130214).
anyone has any idea on how to fix it? the 240114 nightly is not longer on the getCM servers.
Anyone on M6? Thoughts?
I went straight from CM10.2 (CM edition N1) to 11 M6, so I don't know how battery life compares with Omni or other ROMs... would love to hear from those of you that have tried other ROMs and can compare with M6.
With M6, I am getting ~4% battery drain over 7 hours overnight (2G network on only).
All People Update CM. there is the cm-11-20140724-NIGHTLY
First update to the latest nightly in CM page, after that you can update via OTA in your phone, there is Daily updates!!
O-Click, Works, meaby a second lag (while focusing?)
O-Touch Works, not as the touchpad of your lap but works, And for some reason changing the VM to ART works better for me.
3G works
Battery last very good, and its suposed to las more in stand-by if you use ART instead of Dalvik
ART works well by the way.
ThommmF said:
They are released officially und http://download.cyanogenmod.com/?device=n1 :victory:
With the lastest "cm-11-20140126-NIGHTLY-n1.zip" I get no location data - wich makes the N1 unusable for Maps, Foursquare, Ingress aso..
Switches back to "cm-11-20140124-NIGHTLY-n1.zip" everything works fine again.
Click to expand...
Click to collapse
Hi,
I am trying to install Cyanogend mod. N1 a OPPO
The steps are simple, but not working,
I've tried: (http://download.cyanogenmod.com/?device=n1&type=snapshot)
** Cm-11-20140804-SNAPSHOT-M9-n1
cm-11-20140805-NIGHTLY-N1
cm-11-20140124-EXPERIMENTAL-n1.zip
They all show the same error.
"Installation failed"
I downloaded the. zip for wifi, ethernet MAC, WINDOWS ........ and still shows the same error.
:crying:
ThommmF said:
They are released officially und http://download.cyanogenmod.com/?device=n1 :victory:
With the lastest "cm-11-20140126-NIGHTLY-n1.zip" I get no location data - wich makes the N1 unusable for Maps, Foursquare, Ingress aso..
Switches back to "cm-11-20140124-NIGHTLY-n1.zip" everything works fine again.
Click to expand...
Click to collapse
Sorry to bump a 3 year old thread for such an unrelated reason, but you have PMs disabled, and, well, CM11 is not that appealing anymore so I'm confident not many people are gonna read this anyway [any mods reading this, please spare my soul :silly: ]
That said, I just wanted to ask you why you rated my porting of LAOS 15 Trebuchet so poorly, since you didn't leave any comment; if it's some bug, crash or other error i can look into it.
BTW you can answer me on the app's thread if you wish (https://forum.xda-developers.com/android/apps-games/app-lineageos-15-trebuchet-laucher-rom-t3667436)
ThommmF said:
They are released officially und http://download.cyanogenmod.com/?device=n1 :victory:
With the lastest "cm-11-20140126-NIGHTLY-n1.zip" I get no location data - wich makes the N1 unusable for Maps, Foursquare, Ingress aso..
Switches back to "cm-11-20140124-NIGHTLY-n1.zip" everything works fine again.
Click to expand...
Click to collapse
Thank you for leaving your feedback, here are some answers to your points:
- (update mechanism) i actually caught a nasty bug in XDA Labs web console which prevents me from uploading new builds there (and I also deleted all previous reviews in the attempt to reupload the app ??); (i already filed a bug report and managed to get the dev's attention so I hope it gets fixed soon)
- (open source) being a porting, the app mostly shares the original staging/trebuchet15.1 source code, with only a handful edits for fixing crashes due to compatibility errors (and is built with gradle plugin 2.3.3 instead of 3.0.1)
- (very buggy) it inherits all current staging/trebuchet15.1 bugs, not that much from my tests, but yes, there are some
Hello everybody,
I,ve read all around the forum but I couldn´t find information about my problem so i try it here.
From stock V500 20d I rooted and Installed TWRP 2.7.1.0 thanks to the good information in the Forum. After that, I've installed the ROM CM11 (M10) and, from the first reboot, the screen bright is very low. I hardly could do the first configuration and when it finished I selected the full bright.
After some time working it seems that it recovers some bright and I can down a little bit the bright from top.
Every time I restart the device I have the same bright issue.
Can anyone help me?.
Thanks a lot
reypescador said:
Hello everybody,
I,ve read all around the forum but I couldn´t find information about my problem so i try it here.
From stock V500 20d I rooted and Installed TWRP 2.7.1.0 thanks to the good information in the Forum. After that, I've installed the ROM CM11 (M10) and, from the first reboot, the screen bright is very low. I hardly could do the first configuration and when it finished I selected the full bright.
After some time working it seems that it recovers some bright and I can down a little bit the bright from top.
Every time I restart the device I have the same bright issue.
Can anyone help me?.
Thanks a lot
Click to expand...
Click to collapse
Extremely common problem when you were on the 4.4.2 base and are now an AOSP based rom. You either need to change kernels to RedKernel or flash the tablet back to the 4.2.2 base and then reflash your CM rom.
RedKernel info is here: http://forum.xda-developers.com/lg-g-pad-83/development/kernel-redkernel-t2856297
4.2.2 base info is here: http://forum.xda-developers.com/showthread.php?t=2719411
muiriddin said:
Extremely common problem when you were on the 4.4.2 base and are now an AOSP based rom. You either need to change kernels to RedKernel or flash the tablet back to the 4.2.2 base and then reflash your CM rom.
RedKernel info is here: http://forum.xda-developers.com/lg-g-pad-83/development/kernel-redkernel-t2856297
4.2.2 base info is here: http://forum.xda-developers.com/showthread.php?t=2719411
Click to expand...
Click to collapse
Thank you very much
I try to read the info and decide what to do.
Thanks again
Ok it´s done
First I´ve installer V500-4.2.2-Base from recovery, I have reinstalled CM 11 and everything OK.
I have tried a step beyond and I have installed [KERNEL][v500][4.4.4][AOSP] RedKernel [16/09] (everybody seems to be very happy with it) but, after install synapse I run it and appears "No UCI support detected". Seems that kernel doesn´t support it.
Thank you again for your help
reypescador said:
but, after install synapse I run it and appears "No UCI support detected". Seems that kernel doesn´t support it.
Thank you again for your help
Click to expand...
Click to collapse
Seems to be problems with Super SU but I can´t solve them at the moment
You must install the UKM scripts from recovery. Read the op from the red kernel thread...
edisso10018 said:
You must install the UKM scripts from recovery. Read the op from the red kernel thread...
Click to expand...
Click to collapse
What he said!
This confused me at first too. In the very early days of redkernel he included his own forked version of the UKM scripts those have been removed because the UKM script maintainer agreed to merge his changes and therefore he doesn't have to maintain his own copy (better for all involved so he can focus on kernel development). Search the thread you will find a link to where you can download the official UKM scripts and your problem will go away.
I currently run redkernel on the 4.4.2 base myself. I have not reverted to the 4.2.2. base since my last factory restore. I am very happy with this configuration...
muiriddin said:
I currently run redkernel on the 4.4.2 base myself. I have not reverted to the 4.2.2. base since my last factory restore. I am very happy with this configuration...
Click to expand...
Click to collapse
Originally I had issues with the sd card mounting with the 4.4.2 base. Has this been fixed with Red Kernel?
Sent from my LG-V500 using xda premium
ncguy68 said:
Originally I had issues with the sd card mounting with the 4.4.2 base. Has this been fixed with Red Kernel?
Sent from my LG-V500 using xda premium
Click to expand...
Click to collapse
I had the same problems. Mine was two fold, my sd card was dying (I have since got a new one) and the 4.4.2 base was still sometimes having an issue that sd card monitor would show as a bad removal. This was even with the new sd card. Once I switched to Infected's build of slimkat with the redkernel I have not had a bad removal (after running this way now for over a month) and the sd card monitor used to track at least one bad removal a week with stock 4.4.2. I have no idea if this will help others but it is working so far for my device. I am always running sd card monitor since I had problems and it is still reporting a clean record.
muiriddin said:
I had the same problems. Mine was two fold, my sd card was dying (I have since got a new one) and the 4.4.2 base was still sometimes having an issue that sd card monitor would show as a bad removal. This was even with the new sd card. Once I switched to Infected's build of slimkat with the redkernel I have not had a bad removal (after running this way now for over a month) and the sd card monitor used to track at least one bad removal a week with stock 4.4.2. I have no idea if this will help others but it is working so far for my device. I am always running sd card monitor since I had problems and it is still reporting a clean record.
Click to expand...
Click to collapse
Thanks. I am already using Infected's Slimkat, but I am still on 4.2.2 base. I may flash 4.4.2 base and give redkernel or mani kernel a try.
Sent from my LG-V500 using xda premium
ncguy68 said:
Thanks. I am already using Infected's Slimkat, but I am still on 4.2.2 base. I may flash 4.4.2 base and give redkernel or mani kernel a try.
Sent from my LG-V500 using xda premium
Click to expand...
Click to collapse
You didn't ask, but my approach would be:
Use LG tool to revert to 4.4.2 stock
Root with towel root
Install recovery and loki (I need to get you a link for this, but it involves editing a batch file to tell it to still install with revision d instead of b)
reboot recovery using adb, and immediately unplug cable
flash a recovery designed for 4.4.2 (2.7.0.1) from this link http://forum.xda-developers.com/showthread.php?t=2551499
Then install infected slimkat, redkernel and the ukm zip files
I never use the 4.4.2 base files to flash the device to 4.4.2 I always use the LG Tool and go from there.
muiriddin said:
You didn't ask, but my approach would be:
Use LG tool to revert to 4.4.2 stock
Root with towel root
Install recovery and loki (I need to get you a link for this, but it involves editing a batch file to tell it to still install with revision d instead of b)
reboot recovery using adb, and immediately unplug cable
flash a recovery designed for 4.4.2 (2.7.0.1) from this link http://forum.xda-developers.com/showthread.php?t=2551499
Then install infected slimkat, redkernel and the ukm zip files
I never use the 4.4.2 base files to flash the device to 4.4.2 I always use the LG Tool and go from there.
Click to expand...
Click to collapse
Just curious … is there something wrong with flashing the base files to switch between 4.2.2 and 4.4.2?
Now that I have two Gpad's I plan to install 4.4.2 base on one and compare it with 4.2.2 base on the other. Just wonder if I can tell any difference.
Thanks for the info.
Sent from my LG-V500 using xda premium
ncguy68 said:
Just curious … is there something wrong with flashing the base files to switch between 4.2.2 and 4.4.2?
Now that I have two Gpad's I plan to install 4.4.2 base on one and compare it with 4.2.2 base on the other. Just wonder if I can tell any difference.
Thanks for the info.
Sent from my LG-V500 using xda premium
Click to expand...
Click to collapse
I am unaware of a problem with the 4.4.2 base files provided. I have just never used them, I already had the LG Support Tool downloaded and it was easiest to use the path I knew and was comfortable with.
The key thing (and why I run the 4.4.2 base instead of the 4.2.2. base) that is different is the brightness at its lowest setting. The 4.2.2 base on many of the V500's suffers from alternating light and dark spots on one side of the tablet when viewing the tablet in low light with the brightness at its lowest setting and viewing gmail (any app with a white background basically). I use my tablet mostly in dark conditions like this (man I make it sound like I live in a basement somewhere *laughs*). The 4.4.2 base firmware changes the tablet so it functions well at the lowest brightness.
The first picture in this thread shows the screen problem I refer to (although not on a white screen):
http://forum.xda-developers.com/showthread.php?t=2553055
Q&A for [ROM] [5.0] Samsung Galaxy S3 [d2tmo] [Nightly] LiquidSmooth Lollipop
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] [5.0] Samsung Galaxy S3 [d2tmo] [Nightly] LiquidSmooth Lollipop. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
cameron_taylor said:
Camera fix ??? .... really wanna use snapchat and instagram ...
Click to expand...
Click to collapse
Stock and instagram cameras are not working, but snapchat's IS working for me!
From my experience with the rom, open camera is working really good.
Willbur415 said:
Stock and instagram cameras are not working, but snapchat's IS working for me!
From my experience with the rom, open camera is working really good.
Click to expand...
Click to collapse
You can also take a picture with open camera/nexus camera and then share it with instagram/snapchat. A few extra steps but it works
Sent from my SGH-T999 using XDA Free mobile app
Does this rom have a black material design theme?
lilipop roms
So I am running the cyanide L shift kernel version of lolipop or android 5 and I was wondering what the differences are between the two...
Is it the Launcher used? or Is Cyanide L and Liquid Smooth the firmware and the Launchers are a totally different thing? I'm not having any issues with my build right now... its running smooth like butter (only negative thing is my data wifi signal is really bad... I updated to NC1 but heard I may need to go to NC2 or NC4?? I dunno... anyways whats the differences? and I don't mean one is cyanide the other is Liquid smooth... I mean what are the actual differences in detail please...
I really really don't like the launcher (nova) used in the cyanide L build...
Mic issues
Mic isnt working with video chat apps
Anyone able to deposit a check using any banking app? Bank of America app doesn't work for me. I assume this is related to the camera issues.
Sent from my SGH-T999 using XDA Free mobile app
scheduler
Hi i want to thank you for the great work your doing. Im having issues with changing the i/o scheduler in the performance menu. No matter what i pick it stays as row as soon as i exit settings and apply on boot doesnt work either. I have tried clean flash reboot clear cache wipe dalvik and no luck. The only way i can make it stay is by another app.
Seriously, what is going on with VIPER?
No matter how many time I install the driver it's always "Not running, or Driver Status: Abnormal."
I downloaed the se Linux change, and it set it to permissive. Everytime the phone resets it goes back to enforcing. WHy won't it stay on permissive? I am using the default kernel with the LiquidSmooth
I can't get viper to work. At all. This is on a brand new fresh install, wiped away clean internal SDCard, starting completely anew.
This is frustrating the crap out of me.
Sent from my SGH-T999 using XDA Free mobile app
two files
[/COLOR]Soft keys on my s3 don't vibrate I can't seem to find the option to turn them on?
[/COLOR]
nafeasonto said:
Seriously, what is going on with VIPER?
No matter how many time I install the driver it's always "Not running, or Driver Status: Abnormal."
I downloaed the se Linux change, and it set it to permissive. Everytime the phone resets it goes back to enforcing. WHy won't it stay on permissive? I am using the default kernel with the LiquidSmooth
I can't get viper to work. At all. This is on a brand new fresh install, wiped away clean internal SDCard, starting completely anew.
This is frustrating the crap out of me.
Sent from my SGH-T999 using XDA Free mobile app
Click to expand...
Click to collapse
Have you tried installing a different kernel yet? I have shift kernel installed on my LS LP and VIPER is working smoothly on my phone.
Jesus226 said:
[/COLOR]
Have you tried installing a different kernel yet? I have shift kernel installed on my LS LP and VIPER is working smoothly on my phone.
Click to expand...
Click to collapse
do you have a link, the link in the post is not working.
Sent from my SGH-T999 using XDA Free mobile app
Camera
I flashed latest version "v4.0-2015-01-27", disabled and wiped data for stock Camera app, installed both Open Camera and Nexus Camera and neither are working. The window just goes black and crashes. Any idea on how to fix? People were saying it worked earlier in the thread so maybe it broke in a more recent update, would flashing an older version fix it?
This more updated that the 5.0.2 LP version?
Is this ROM more updated than the 5.0.2 LP ROM that you have fenixus??
Reply
Thanks
WHich do I choose?
Do I choose the Liquid Themes or Liquid Layers??
jestincheppad said:
Do I choose the Liquid Themes or Liquid Layers??
Click to expand...
Click to collapse
That's up to you, but I believe LS is going to discontinue the Themes builds...
GS³: SlimKat + leanKernel Edition™
ギミチョコ！！
no sound for the incomming calls
Hey. I really like this ROM, however I have a problem with calls. When someone calls me, the phone doesn't ring, just vibrates (sometimes it vibrates just once and that is it). THat is very sad because this ROM is so smooth and fast. Does this happen only on my phone? and also, I am on the slimkat now with cyanogenmod based recovery, so whenever I flash this rom or any other lollipop based ROM, I get the message from the recovery that I may lose the root access. I always chose the Fix option and everything runs just fine with the root access. But, I get this message everytime I go to recovery. Thank you for your great work. Oh, and just to clarify, the above mentioned problems happen on the newest build (3/6/2015) and the previous build (don't remember which one specifically).
INazar said:
Hey. I really like this ROM, however I have a problem with calls. When someone calls me, the phone doesn't ring, just vibrates (sometimes it vibrates just once and that is it). THat is very sad because this ROM is so smooth and fast. Does this happen only on my phone? and also, I am on the slimkat now with cyanogenmod based recovery, so whenever I flash this rom or any other lollipop based ROM, I get the message from the recovery that I may lose the root access. I always chose the Fix option and everything runs just fine with the root access. But, I get this message everytime I go to recovery. Thank you for your great work. Oh, and just to clarify, the above mentioned problems happen on the newest build (3/6/2015) and the previous build (don't remember which one specifically).
Click to expand...
Click to collapse
Get with fenixus on the main thread on the calling issue. You may have to provide logcats for him. As for the second problem, I believe SuperSU should be automatically flashed when the ROM is flashed, not sure of that's a recovery issue, but I know the auto flashing of SuperSU works on TWRP...
GS³: SlimKat + leanKernel Edition™
ギミチョコ！！
This suffers from the same thing every Slim rom does.
Anytime you set your default Ringtone, when you restart it defaults back to default. I guess because it is on the External SD card. Is there no way around this?
Another thing that is happening is everytime i restart the phone it has to update Google Play services.
I am in the middle of installing the ROM.
When I did the same ROM before, it took a few minutes to install, this time it's just stuck there it looks like.
Have I done something wrong? its been 15minutes or so. I will wait longer.
TWRP 2.7.1.0 , stock revovery (v1.2), unlocked recovery (original by wmjan)
hope there will be some custom roms for this LCD soon...
tonyjih said:
TWRP 2.7.1.0 , stock revovery (v1.2), unlocked recovery (original by wmjan)
hope there will be some custom roms for this LCD soon...
Click to expand...
Click to collapse
Could you please explain the difference between these 3 recoveries?
GaroRobe said:
Could you please explain the difference between these 3 recoveries?
Click to expand...
Click to collapse
they both for newer model of find7 comes with a newer screen
You'll need these recoveries ONLY if you own a R63419+ LCD model
reference:
http://www.oppoforums.com/threads/r63419-cannot-install-3rd-party-rec-rom.24924/
tonyjih said:
they both for newer model of find7 comes with a newer screen
You'll need these recoveries ONLY if you own a R63419+ LCD model
reference:
http://www.oppoforums.com/threads/r63419-cannot-install-3rd-party-rec-rom.24924/
Click to expand...
Click to collapse
1. The "*##*37847#" method doesn't work for me since I'm on 1.2.8i , thus cannot verify the screen model
2. My phone is x9076 int'l, manufactured in december 2014
3. I have the "bleached screen" bug on 3rd party ROMs and namelessTWRPs
4. The twrp-x9076 takes only half of a screen area (it does work though, but still identifies my phone as find7a which is incorrect)
5. you still didn't describe the difference between the other two
I tried flashing CM12 nightly with twrp-x9076 (had to remove assert from update script). No good - same as before, bleached screen and such. So this particular recovery seems to be useless for anything other than backup/restore and rooting (which is awesome, but still not what I'd like to have access to).
GaroRobe said:
I tried flashing CM12 nightly with twrp-x9076 (had to remove assert from update script). No good - same as before, bleached screen and such. So this particular recovery seems to be useless for anything other than backup/restore and rooting (which is awesome, but still not what I'd like to have access to).
Click to expand...
Click to collapse
you have to wait CM update their drivers , otherwise it just .... don't work.
I also have an issue with this and have installed this recovery and its fixed the problem. Now we wait for custom ROM developers to catch on.... I'm going to keep myself glued to cyanogen to see if they change anything!
sof006 said:
I also have an issue with this and have installed this recovery and its fixed the problem. Now we wait for custom ROM developers to catch on.... I'm going to keep myself glued to cyanogen to see if they change anything!
Click to expand...
Click to collapse
Same here. Other than the official beta rom there seems to be nothing available for us. I am seriously considering returning the Oppo since I can't even get hold of 1.2.8i (only stable version which ships with the phone).
So sad... I really want to use 5.0 on my OPPO Find 7. I've reached out to Cyanogen but had no replies, reached out to other ROM developers only to either be ignored or have my question washed away by a sea of people complaining that they can't get a game to work on their phone.
Just found out that cyanogen is working on the new oppo find 7 with new lcd panel issue. So anyone disappointed they'll have it sorted soon hopefully!
Does the offical TWRP and CM support this find7 with new LCD????
Any updates on this? I have managed to get the official AOSP ROM working but nothing else unfortunately.
Double the question. Lack of working TWRP is just fatal to any tinkering.
GaroRobe said:
1. The "*##*37847#" method doesn't work for me since I'm on 1.2.8i , thus cannot verify the screen model [...]
Click to expand...
Click to collapse
Test with adb (requires root):
Code:
adb devices
adb shell
su
cat /proc/devinfo/lcd
the answer for me (X9006 with COS 2.0.8i) is
Code:
Device version: R63417
Device manufacture: JDI
close the shell
Code:
exit
exit
Maybe if the ROM is compiled from source, the extra driver could be included? I am noob to this so if someone experienced could take a look that'd be great!
Just found this thread and didn't read much.
I am on unified storage (stock 2.0.8I). Are these recoveries compatible (unified partition)?
And yes, I have the new LCD screen...
Thanks
betoNL said:
Just found this thread and didn't read much.
I am on unified storage (stock 2.0.8I). Are these recoveries compatible (unified partition)?
And yes, I have the new LCD screen...
Thanks
Click to expand...
Click to collapse
Yes they are compatible with LVM, using it with the official AOSP rom since it's been the only way for me to get Lollipop so far, will probably test out the new beta ColorOS 2.1 Lollipop ROM as well.
EDIT: Actually just noticed some issues with it, can't mount internal_sd or data partitions and thus can't back up, avoid. I thought I'd backed up on LVM but clearly not.
Speaking of ROMs... I've taken the screen driver of the original Oppo kernel from the github and added it to the cm12.1 kernel (ie overwritten the cm12 driver with the Oppo one), I'm now compiling it from source and will report back if this works. If so, this will mean working Cyanogenmod for the new panel!
djzic said:
Yes they are compatible with LVM, using it with the official AOSP rom since it's been the only way for me to get Lollipop so far, will probably test out the new beta ColorOS 2.1 Lollipop ROM as well.
EDIT: Actually just noticed some issues with it, can't mount internal_sd or data partitions and thus can't back up, avoid. I thought I'd backed up on LVM but clearly not.
Speaking of ROMs... I've taken the screen driver of the original Oppo kernel from the github and added it to the cm12.1 kernel (ie overwritten the cm12 driver with the Oppo one), I'm now compiling it from source and will report back if this works. If so, this will mean working Cyanogenmod for the new panel!
Click to expand...
Click to collapse
Ok thanks,
I am on stock 2.0.8i with unified storage and gonna have a look on some CM / AOSP based roms soon ...
.
betoNL said:
Ok thanks,
I am on stock 2.0.8i with unified storage and gonna have a look on some CM / AOSP based roms soon ...
.
Click to expand...
Click to collapse
Edit I did a backup of the stock recovery (2.0.8i) with Flashify app for instance so I think I am going to try this out anyway ....
Twrp cant seen to find my internal storage. Im using unified storage setting on colorOS 2.1