I just flashed the new official CM12 nightlies and noticed that the "Powered by android" text in the splash screen is now gone. Was this a deliberate hit at OnePlus by Cyanogen or just coincidence?
itsdacj said:
I just flashed the new official CM12 nightlies and noticed that the "Powered by android" text in the splash screen is now gone. Was this a deliberate hit at OnePlus by Cyanogen or just coincidence?
Click to expand...
Click to collapse
How would that be seen as a hit at OnePlus? It's just coincidence.
timmaaa said:
How would that be seen as a hit at OnePlus? It's just coincidence.
Click to expand...
Click to collapse
I just thought that Cyanogen were trying to distance themselves from OnePlus. If this isn't a concern, just remove it.
Related
Is it possible to change the logo that comes on before the boot animation? I really just want to get the unlocked padlock to go away. TIA
Sent from my OmniROM toting Nexus 5
markusf21 said:
Is it possible to change the logo that comes on before the boot animation? I really just want to get the unlocked padlock to go away. TIA
Sent from my OmniROM toting Nexus 5
Click to expand...
Click to collapse
no. you seriously risk bricking your phone if you actually try to change it properly.
markusf21 said:
Is it possible to change the logo that comes on before the boot animation? I really just want to get the unlocked padlock to go away. TIA
Sent from my OmniROM toting Nexus 5
Click to expand...
Click to collapse
It requires to edit partition files in the /dev/block path, you can even edit all bootloader dialog (like "Unlocked" to "Locked", "Carrier info". etc..). It is doable but there's not documented mods for the Nexus 5 yet. The chances of bricking (real blackout bricking) are guaranteed 99:1 and are not worth the risk. Lets wait for a Dev who know what he's doing to do it first, then we follow.
All of that we did on HTC phones, but things vary from device to device. So, DO NOT ATTEMPT
Thanks for the responses. The padlock is annoying but not so annoying to risk a brick.
Sent from my OmniROM toting Nexus 5
markusf21 said:
Thanks for the responses. The padlock is annoying but not so annoying to risk a brick.
Sent from my OmniROM toting Nexus 5
Click to expand...
Click to collapse
If the padlock icon annoys you that much, you can use BootUnlocker to lock and unlock the bootloader from within the app if you have root permissions.
Keep the bootloader locked until you need to unlock it. No more padlock.
BootUnlocker: https://play.google.com/store/apps/details?id=net.segv11.bootunlocker
Would I still be able to keep the custom recovery there while doing this
I'm a tail wagging, Android loving, Googly sheep fanboy!
Blasted from my Nexus 5 using the XDA pay me for this or else you get bombarded with ads Premium App
I can't believe it is that big of a problem.
DREWHAMM974 said:
Would I still be able to keep the custom recovery there while doing this
Click to expand...
Click to collapse
Yes
Sent from my Nexus 5 using Tapatalk
mistahseller said:
I can't believe it is that big of a problem.
Click to expand...
Click to collapse
I wouldn't really call it a problem. It just looks better/cleaner without the padlock
Sent from my OmniROM toting Nexus 5
I am exchanging my M8 today and I flashed a custom splash screen so I need to get it back to stock. Anyone have this? TIA
shojus said:
I am exchanging my M8 today and I flashed a custom splash screen so I need to get it back to stock. Anyone have this? TIA
Click to expand...
Click to collapse
I think this thread has the stock Verizon boot up animation.
http://forum.xda-developers.com/showthread.php?t=2710544
shortstuff_mt said:
I think this thread has the stock Verizon boot up animation.
http://forum.xda-developers.com/showthread.php?t=2710544
Click to expand...
Click to collapse
Thanks for the reply but I actually need the splash screen and not the boot animation. I will keep searching... :good:
You can just RUU. I think there was a thread in general section on where to download it
Sent from my HTC6525LVW using Tapatalk
So I got my 1+1 a few days ago and am okay with CM11s.I see blisspop is popular and people are getting good battery with it. But are there Abby downsides of upgrading to L? Should I wait for stable CM12s
Sent from my A0001 using XDA app
SilentRazor said:
So I got my 1+1 a few days ago and am okay with CM11s.I see blisspop is popular and people are getting good battery with it. But are there Abby downsides of upgrading to L? Should I wait for stable CM12s
Sent from my A0001 using XDA app
Click to expand...
Click to collapse
It's daily driver material. Just don't flash the most recent nightlies. They have some firmware update issues.
I have been using using Temaseks rom and its as smooth as possible, well worth upgrading to.
rudi_j7 said:
It's daily driver material. Just don't flash the most recent nightlies. They have some firmware update issues.
Click to expand...
Click to collapse
Not true, I have most recent CM12 nightly and it's ok.
giaur said:
Not true, I have most recent CM12 nightly and it's ok.
Click to expand...
Click to collapse
Maybe not true for you, bit still true for others.
Transmitted via Bacon
timmaaa said:
Maybe not true for you, bit still true for others.
Transmitted via Bacon
Click to expand...
Click to collapse
Nobody confirmed this problem on Oneplus. There are some problems on Find7/Unofficial CM12 builds (there is no official CM12 for Find7). It's safe to user latest CM12 nightly on bacon, dont be afraid
giaur said:
Nobody confirmed this problem on Oneplus. There are some problems on Find7/Unofficial CM12 builds (there is no official CM12 for Find7). It's safe to user latest CM12 nightly on bacon, dont be afraid
Click to expand...
Click to collapse
I'm not afraid. I'm simply saying that just because you are not experiencing a particular bug personally it does not mean the bug doesn't exist for the greater community.
Transmitted via Bacon
timmaaa said:
I'm not afraid. I'm simply saying that just because you are not experiencing a particular bug personally it does not mean the bug doesn't exist for the greater community.
Transmitted via Bacon
Click to expand...
Click to collapse
Not only me, many people flashed today CM12 build and nobody has any problems. I have no idea why do you think there is any bug on latest CM12 nightlies?
giaur said:
Nobody confirmed this problem on Oneplus. There are some problems on Find7/Unofficial CM12 builds (there is no official CM12 for Find7). It's safe to user latest CM12 nightly on bacon, dont be afraid
Click to expand...
Click to collapse
timmaaa said:
I'm not afraid. I'm simply saying that just because you are not experiencing a particular bug personally it does not mean the bug doesn't exist for the greater community.
Transmitted via Bacon
Click to expand...
Click to collapse
Well, usually a minor glitch or bug wouldn't be a big deal, but here, the consequence could be a hard brick as reported on the Find 7. There's no coming back from there, and official or unofficial doesn't matter because both are from the same sources.
rudi_j7 said:
Well, usually a minor glitch or bug wouldn't be a big deal, but here, the consequence could be a hard brick as reported on the Find 7. There's no coming back from there, and official or unofficial doesn't matter because both are from the same sources.
Click to expand...
Click to collapse
Find7 != Oneplus, latest nightly is tested by many people and it's ok on bacon. Besides - sources are the same but there can be something messed while compilation process that prevents rom to boot. Do you mean hard brick, so phone is completly bricked and can't even boot into recovery mode?
giaur said:
Find7 != Oneplus, latest nightly is tested by many people and it's ok on bacon. Besides - sources are the same but there can be something messed while compilation process that prevents rom to boot. Do you mean hard brick, so phone is completly bricked and can't even boot into recovery mode?
Click to expand...
Click to collapse
Yep. Hard brick as in an expensive paperweight. CM has merged a commit to stop CM nightlies for Find7 and Bacon temporarily because of this issue. They merged some firmware update which has botched everything up.
rudi_j7 said:
Yep. Hard brick as in an expensive paperweight. CM has merged a commit to stop CM nightlies for Find7 and Bacon temporarily
Click to expand...
Click to collapse
Which commit is it? CM nightlies are still available for bacon, I have installed today nightly. And I can't see any CM12 nightlies for Find7, there are only CM11
giaur said:
Which commit is it? CM nightlies are still available for bacon, I have installed today nightly. And I can't see any CM12 nightlies for Find7, there are only CM11
Click to expand...
Click to collapse
http://review.cyanogenmod.org/#/c/85323/
Sent from my A0001 using XDA Premium 4 mobile app
rudi_j7 said:
http://review.cyanogenmod.org/#/c/85323/
Sent from my A0001 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It's merged today morning, 14.01 nightly was compiled yesterday and it's still available: http://jenkins.cyanogenmod.com/job/android/98199/console download is here: http://download.cyanogenmod.org/get/jenkins/98199/cm-12-20150114-NIGHTLY-bacon.zip
It seems there will not be new nightly tommorow, the one already built is ok.
@timmaaa what do you use?
Sent from my A0001 using XDA Free mobile app
And I guess no CM12 nightlies, which Blisspop version should I hop on to?
So the cm12s update has been released and as long as know it is supposed to come over the air to cm11s devices but im not sure im running cm11s.
iy doesnt say Cyanogen on the back of the device. i have not rooted flashed or done anything like that
it says the cyanogen version is 11.0-XNPH05Q
im pretty confused and need a answer quick..
sorry for bad english.
You are running CM11S and will get Cyanogen OS 12.
New OPOs don't come with the Cyanogen branding on the back.
THANKS
Amro90 said:
You are running CM11S and will get Cyanogen OS 12.
New OPOs don't come with the Cyanogen branding on the back.
Click to expand...
Click to collapse
Thanks for quick answer and the question now is when i will get it. have you got it? if so when?
AntonAtom said:
Thanks for quick answer and the question now is when i will get it. have you got it? if so when?
Click to expand...
Click to collapse
Can't really tell when you will get it. Probably in the next few days. I didn't get the OTA so I just flashed it with the fastboot images.
Amro90 said:
Can't really tell when you will get it. Probably in the next few days. I didn't get the OTA so I just flashed it with the fastboot images.
Click to expand...
Click to collapse
Right... As per Carl, the updates are pushed in batches not limiting to any geographical areas.
Within next few days almost everyone should have it.
Hi,
It has been a long time. I wonder if there will ever be a LineageOS for Pixel phone. Is the team short of hands? Or there's technical issue?
Thanks,
David
Try OctoS
Surely there is a better spot to ask this question lmao
Sent from my Pixel using Tapatalk
I think it's because they can't include gapps in linwageOS, which is necessary for many pixel rom, but there is one for pixel xl though
Sent from my Pixel using Tapatalk
davidshen84 said:
Hi,
It has been a long time. I wonder if there will ever be a LineageOS for Pixel phone. Is the team short of hands? Or there's technical issue?
Thanks,
David
Click to expand...
Click to collapse
AOKP ROM is based off LineageOS I believe and is in the XL forum and has a Sailfish version mentioned in the thread.
I was going to research it more when I get some spare time.
https://www.androidfilehost.com/?w=files&flid=168819
Found this link from the AOKP thread, if you get time time to try it out before I do please let me know.
Here's a link to invisiblek's fully working unofficial version. http://www.invisiblek.org/roms/lineage-14.1/sailfish/
Sent from my Pixel using Tapatalk
Electroz said:
Here's a link to invisiblek's fully working unofficial version. http://www.invisiblek.org/roms/lineage-14.1/sailfish/
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
It seems invisiblek.org is always ahead of the official LineageOS. I am using its unofficial 14.1 for hammer head CAF. I think I will try this one first.
BTW, do you know it has Google assistant in this build?
Thanks,
David
davidshen84 said:
It seems invisiblek.org is always ahead of the official LineageOS. I am using its unofficial 14.1 for hammer head CAF. I think I will try this one first.
BTW, do you know it has Google assistant in this build?
Thanks,
David
Click to expand...
Click to collapse
I have to use a MOD to enable the Assisant.
Sent from my ONEPLUS A3003 using Tapatalk
OK, I got LineageOS installed and everything seems working. However, I found I cannot reboot into TWRP recovery. If I try, I get into a factory Android recovery interface, and there's nothing I can do except force power off.
According to https://twrp.me/devices/googlepixel.html, fastboot boot using the image, then flash the zip file should get TWRP setup. Did I miss anything?
Thanks.
davidshen84 said:
OK, I got LineageOS installed and everything seems working. However, I found I cannot reboot into TWRP recovery. If I try, I get into a factory Android recovery interface, and there's nothing I can do except force power off.
According to https://twrp.me/devices/googlepixel.html, fastboot boot using the image, then flash the zip file should get TWRP setup. Did I miss anything?
Thanks.
Click to expand...
Click to collapse
You have to flash the Roman then TWRP zip each time you update rom