Related
Hi,
For a couple of days now, the GPS doesn't work with the CM10.1 nightlies.
I checked my device with an app called "Z-Device test" and it says there is no GPS in my phone.
Nevertheless, the hardware is OK, as it works with the stable builds of CM.
Any ideas?
drAstic99 said:
Hi,
For a couple of days now, the GPS doesn't work with the CM10.1 nightlies.
I checked my device with an app called "Z-Device test" and it says there is no GPS in my phone.
Nevertheless, the hardware is OK, as it works with the stable builds of CM.
Any ideas?
Click to expand...
Click to collapse
I'm having similar problems. Although Z-Device test thinks that I do have GPS. None of the apps ever get a reading and the little icon on the status bar never appears.
I've tried resetting it using GPS status to reset all cached GPS data and also 'Download GPS assistance data' but it has not helped.
Its been fixed... New nightlies are back with gps :|
meilbox said:
Its been fixed... New nightlies are back with gps :|
Click to expand...
Click to collapse
OK, I'm on cm-10.1.2. Is it fixed in a newer one than this?
Jemsquash said:
OK, I'm on cm-10.1.2. Is it fixed in a newer one than this?
Click to expand...
Click to collapse
Let me elaborate, sorry I'm relatively new to cyanogen mod. I've got it set to nightlies and check for updates is turned on to daily. I've also checked manually but there are no updates available.
If I check the build date in about phone it is Fri Jul 12 12:25:13 PDT 2013.
This correlates to:
umts_spyder
Motorola Razr stable Send to ROMManager Direct Download: cm-10.1.2-umts_spyder.zip
md5sum: 222891ba743c8e6bead634d22010129e Short URL: http: //get. cm/get/9cR 158.25 MB 2013-07-12 13:25:13
on the page http: //get. cm/?device=umts_spyder (new to the forum so I can't post urls)
There seem to be more recent updates but I'm not sure how to tell if I've got them..
Hopefully it will start to roll down into the other CM based roms now as well.
It may be that you have to delete your ROM as the dirty upgrade will also contain the old/broken things as well. I had to re-do mine from a fresh corrected rom before things started to work as I expected. My $.02.
It has started working this evening...does CM update quietly? I thought I would see a different update version install if it did update.
Perhaps it has fixed itself somehow. I'm a bit confused about this.
Jemsquash said:
It has started working this evening...does CM update quietly? I thought I would see a different update version install if it did update.
Perhaps it has fixed itself somehow. I'm a bit confused about this.
Click to expand...
Click to collapse
You have to flash the nightlies through recovery in order to update. A full wipe is recommended before flashing.
Sent from my XT912 using Tapatalk 2
THREAD DEPRECATED! project moved here:
http://forum.xda-developers.com/goo...om-openpdroid-patched-cyanogenmod-11-t2817655
----------------------------
title is self explanatory. I'll share my builds in case others are interested.
please look for them here:
THREAD DEPRECATED!
EDIT:
information in the edit below is not longer current. please see:
http://forum.xda-developers.com/showpost.php?p=52664423&postcount=5
EDIT:
additional information as requested by moderator:
this is just a build of master branch cyanogenmod for hammerhead patched with the latest openpdroid patches as available on openpdroid's github (https://github.com/OpenPDroid/OpenPDroidPatches). not a single line of code was changed, as the source level patches still apply without errors.
it used to be the case that auto-patcher could smali-patch binary android builds. now auto-patcher has gone unmaintained and smali patches no longer apply on recent builds of cyanogenmod.
many people are not willing to build from source and are abandoning openpdroid. i will continue to use it on kit-kat at least. these are my builds and are shared here as a convenience for hammerhead users who do not want to build their own OS. no changes were introduced. source code is available on the respective project githubs.
NOTE: uploads are in progress, please check later.
new build (currently uploading to the dropbox link)
new build (currently uploading to the dropbox link)
this one cherry picks this:
http://review.cyanogenmod.org/#/c/62281/
to support 5x5 grid size in the home screen.
new build (currently uploading to the dropbox link)
CM11-M6 broke OpenPDroid patch compatibility. i forked OPD to restore compatibility, fix several bugs and clean up the code. sources here:
https://github.com/Lanchon/OpenPDroid-patches
cherry picks this (patchset 6) to support 5x5 grid size in the home screen:
http://review.cyanogenmod.org/#/c/62281/
Is it Art compatible ?
yuuzhantar said:
Is it Art compatible ?
Click to expand...
Click to collapse
Dude,
OP's built CM11 from source with the added OpenPDroid patches. The ROM that he's linked to us is just CM11 with OpenPDroid.
Your question should be: "Does CM11 allow you to select different runtimes?".
The answer to that question is: "Yes, this option is located under 'Developer Options'.".
If you next question is: "How do I access 'Developer Options'?", then look here: http://www.youtube.com/watch?v=XcFVRDZ5Z9Q.
LewisD94 said:
Dude,
OP's built CM11 from source with the added OpenPDroid patches. The ROM that he's linked to us is just CM11 with OpenPDroid.
Your question should be: "Does CM11 allow you to select different runtimes?".
The answer to that question is: "Yes, this option is located under 'Developer Options'.".
If you next question is: "How do I access 'Developer Options'?", then look here: http://www.youtube.com/watch?v=XcFVRDZ5Z9Q.
Click to expand...
Click to collapse
Dude,
last time we had informations about pdroid, it was "not compatible with art"
http://forum.xda-developers.com/showpost.php?p=47902311&postcount=3796
As we don't know if it's because of the smali patching process or anything else,
I asked to know if a rom build with openpdroid included in the source was Art compatible.
And if I ask about Art, likerly I know how to use it (it switched since 4.4 was released ... )
Anyway, I'm done with CM, I switched to Omni this week-end after my phone became unusable, corruption of system data
yuuzhantar said:
Dude,
last time we had informations about pdroid, it was "not compatible with art"
http://forum.xda-developers.com/showpost.php?p=47902311&postcount=3796
As we don't know if it's because of the smali patching process or anything else,
I asked to know if a rom build with openpdroid included in the source was Art compatible.
And if I ask about Art, likerly I know how to use it (it switched since 4.4 was released ... )
Anyway, I'm done with CM, I switched to Omni this week-end after my phone became unusable, corruption of system data
Click to expand...
Click to collapse
you should try making your own rom before you bad mouth another.
flex360 said:
you should try making your own rom before you bad mouth another.
Click to expand...
Click to collapse
What business is it of yours?
I just sayed that I stop using cm after it crashed
Great to have someone building CM11 with openpdroid! Can't thank you enough!!!
Just one question:
Which kernel works best with this CM11? Any bad experiences?
Gesendet von meinem Nexus 5 mit Tapatalk 2
new build!
EDIT: this build is now based on android 4.4.4. remember to UPDATE YOUR GAPPS, or else...
sorry for the delay. i took off to europe to try out something with someone i met last year... it was a good bet that didnt work
but im back!!!
this build includes the custom home screen grid size selection that was merged into master recently, and so the old cherry pick slash hack (http://review.cyanogenmod.org/#/c/62281/) is gone for good.
NOTE: the update WILL NOT import your home screens beyond the upper left 4x4 area. so if you were using the previous cherry pick to increase the grid size, make sure you reshuffle the icons and widgets to the upper left 4x4 subset of each screen. anything outside that area will be lost. after the update you can increase the grid again and reshuffle back to your liking.
yuuzhantar said:
Is it Art compatible ?
Click to expand...
Click to collapse
all OPD changes are at the java/dalvik level, which makes me suspect that this build is as ART compatible as standard CM. that said, i've never used ART.
schwarzlichtkind said:
Which kernel works best with this CM11? Any bad experiences?
Click to expand...
Click to collapse
any kernel that works well with CM standard should work as well with this build.
@Lanchon
Are you getting com.android.phone has stopped messages upon first boot? I have tried full wipe, flashing different kernels, different gapps packages, etc to no avail. I am installing as secondary ROM with MultiROM by the way. Your previous build (M6 I think) installs this way with no issues.
Thanks so much for keeping pdroid alive!
stone_ship said:
@Lanchon
Are you getting com.android.phone has stopped messages upon first boot? I have tried full wipe, flashing different kernels, different gapps packages, etc to no avail. I am installing as secondary ROM with MultiROM by the way. Your previous build (M6 I think) installs this way with no issues.
Thanks so much for keeping pdroid alive!
Click to expand...
Click to collapse
i havent done a clean install since i dont know when!! nor have i used multirom. im using BaNkS gapps minimal with some add-ons and i dont experience a hitch. note that you need 4.4.4 gapps for this rom. recommend you format the system partition (if it makes sense with multirom) before flashing rom and gapps. then wipe cache and dalvik.
new build uploaded!
i will also be building for the i9100; first build is uploading now...
THREAD DEPRECATED! project moved here:
http://forum.xda-developers.com/goo...om-openpdroid-patched-cyanogenmod-11-t2817655
ALL WORK HAS MOVED TO THE 3.4 BRINGUP. YES, THAT MEANS 3.4 IS BOOTING AND WIP AND THIS KERNEL IS NOW DEPRECATED! CLICK HERE TO VIEW 3.4 PROGRESS
Check latest posts for updates
As you may be aware, we've been trying unsuccessfully to boot Nvidia's 3.4 kernel for tegra 3 on grouper.
Progress has pretty much halted, as this project needs to be finished before we have any hope of 3.4 ever working.
SAUCES
-
WE ALSO HAVE A GITHUB ORGANIZATION
What is this?
An attempt to get Google's ludicrously outdated grouper 3.1 kernel up-to-date with Nvidia's 3.1 kernel.
Why?
1) It'll be, put simply, "better" than Google's out-of-date kernel (...potentially)
2) This *must* be completed before work on 3.4 goes ahead
3) Hopefully other kernels, such as franco's, could be merged with this
How?
I did a "git rev-list" of Nvidia's branch, then Google's branch, all the way back to the point where Google added grouper support (Around March 2012), then diffed the result. I've attached the files in this post: The commits in the diff which have a + next to them are Nvidia's commits, as these are not present in Google's log. I simply need to cherry-pick all 1,699 of these, and make sure to manually update the grouper board files exactly as Nvidia's dev. boards are updated (because of course grouper itself is not updated at all in Nvidia's source). Then I need to fix all the compilation errors. If I get through around 50 - 80 commits a day, and fix the compilation errors the next day, I should be finished in 2 months max. Then serious 3.4 work can begin.
Should I use it?
From a user's perspective, in all honesty, no. This is a) a WIP and b) a means to another end (3.4). Other offerings such as franco's kernel are so far more improved than Google's anyway that this will not be necessarily "better" than those simply due to a load of updates from Nvidia. What *will* make this useful is if the final product is merged, as I said, into existing kernels, thus improving those. That said, I'll never upload a new version before having tested it myself, so you can be in the very least assured that it'll boot and run.
HOWEVER it would be extremely useful if you could run this simply for testing purposes. All my trust is placed in Nvidia's commits and my own ability to fix conflicts and compilation errors. Things may go wrong and your help would be massively appreciated.
Shutupandletmeflash!!!
I'll post updates regularly as possible here. I've used agnostic as it's fantastic. The naming scheme is: Alpha whilst I'm still cherry-picking, Beta once that's done and we're testing to fix bugs, then RC once its in a stable, releasable state (there'll probably only be 1 RC, then no more work); The numbering is x.y where x indicates major release (0 is Alpha, 1 will be Beta) and y will be increment by 1 on every single release.
Credits
@sgt. meow
Nvidia
Google
Asus
@legolas93 for F2FS
@frantisek.nesveda for agnostic-kernel
Anyone else I've forgotten (sorry, it's a while since I opened the 3.4 discussion thread)
XDA:DevDB Information
linux-tegra-nv-3.1-grouper, Kernel for the Nexus 7
Contributors
HTCDreamOn, Ziyan, n1kolaa, sgt. meow
Source Code: https://github.com/Ziyann/android_kernel_asus_grouper
Kernel Special Features:
Version Information
Status: No Longer Updated
Created 2014-11-23
Last Updated 2015-06-07
FAQ
Q: Why is TricksterMod/ CPUSpy/etc. Not showing 1300MHz?
A: read this post.
GREAT! :good:
Its great to see people giving attention to an old device.
I will look forward to it.
What you forgot me
You know moral support!!
Lol J/K
Good thing you put it in original development
That will help.
So keep up the... Hmm dont know how to express it....
Your doing an beyond awesome job!
Maaayyybeeee Google will update the grouper kernel when Lollipop code will be pushed to AOSP... But I'd be suprised if the Nexus 7 even got official Lollipop.
frantisek.nesveda said:
Maaayyybeeee Google will update the grouper kernel when Lollipop code will be pushed to AOSP... But I'd be suprised if the Nexus 7 even got official Lollipop.
Click to expand...
Click to collapse
I'm sure we will get Android 5 one way or another
USBhost said:
I'm sure we will get Android 5 one way or another
Click to expand...
Click to collapse
Well, it will be official, at least according to Android Police.
http://www.androidpolice.com/2014/10/15/being-the-will-of-our-lord-duarte-the-nexus-7-2012-will-receive-the-holy-blessing-of-android-5-0-official/
frantisek.nesveda said:
Well, it will be official, at least according to Android Police.
http://www.androidpolice.com/2014/1...ve-the-holy-blessing-of-android-5-0-official/
Click to expand...
Click to collapse
USBhost said:
I'm sure we will get Android 5 one way or another
Click to expand...
Click to collapse
I appreciate your interest and support, but please, this is a development thread, and nothing to do with L whatsoever. That topic belongs here. If you want to post here a bugreport or in the very least a relevant question from a development perspective is all I ask. Thanks.
frantisek.nesveda said:
Maaayyybeeee Google will update the grouper kernel when Lollipop code will be pushed to AOSP... But I'd be suprised if the Nexus 7 even got official Lollipop.
Click to expand...
Click to collapse
I expect the kernel will be updated as it was for 4.4 from 4.3. I'm still carrying on with this, however, as of course the new kernel will still be 3.1.10. Then I can apply those updates on top of this.
P.S Did some more cherry-picking today. Mostly smooth, very few conflicts so far.
HTCDreamOn said:
I appreciate your interest and support, but please, this is a development thread, and nothing to do with L whatsoever. That topic belongs here. If you want to post here a bugreport or in the very least a relevant question from a development perspective is all I ask. Thanks.
Click to expand...
Click to collapse
Sorry, I got a little carried away with the Lollipop release. I'll test the kernel during the weekend. This is only for AOSP, or can we run it on CyanogenMod as well?
frantisek.nesveda said:
Sorry, I got a little carried away with the Lollipop release. I'll test the kernel during the weekend. This is only for AOSP, or can we run it on CyanogenMod as well?
Click to expand...
Click to collapse
Same here
the kernel should work with CM
frantisek.nesveda said:
Sorry, I got a little carried away with the Lollipop release. I'll test the kernel during the weekend. This is only for AOSP, or can we run it on CyanogenMod as well?
Click to expand...
Click to collapse
No idea... CM use CAF for Qualcomm but we're Tegra 3 so I think it should be fine. Nandroid, flash, restore if it breaks, and no harm done. I'm uploading Alpha 0.1 right now Android browser is a pain with attachments, 0.1 will be tomorrow.
HTCDreamOn said:
No idea... CM use CAF for Qualcomm but we're Tegra 3 so I think it should be fine. Nandroid, flash, restore if it breaks, and no harm done. I'm uploading Alpha 0.1 right now.
Click to expand...
Click to collapse
Awesome will test 0.1
also 0.0 booted just fine on All-F2FS CarbonROM
USBhost said:
Awesome will test 0.1
also 0.0 booted just fine on All-F2FS CarbonROM
Click to expand...
Click to collapse
0.1 uploaded. Glad it works.
0.1 running ok so far only thimg i have noticed is interactive locks at 1200mhz on all 4 cores. On demamd scales fine
gptwarrior said:
0.1 running ok so far only thimg i have noticed is interactive locks at 1200mhz on all 4 cores. On demamd scales fine
Click to expand...
Click to collapse
Interactive has never ran good on my tablet no matter what kernal.
Sent from my Nexus 7 using Tapatalk 2
gptwarrior said:
0.1 running ok so far only thimg i have noticed is interactive locks at 1200mhz on all 4 cores. On demamd scales fine
Click to expand...
Click to collapse
Thanks for pointing this out, I hadn't noticed this before but it's happening to me as well. I seem to remember a commit affecting cpufreq scaling somewhere so this could be it, but it should be easy to fix. I might stock up these smaller problems and fix them right at the end to reduce conflicts, but if its simple enough I'll fix it soonish.
In other news, Alpha 0.2 has been uploaded (first post as usual) mostly just more commits picked, but we're starting to get to the good stuff: changes to tegra3 drivers etc. And some things I can use to update grouper board files :good:
Alpha 0.2 works well here.
Snappy for a stock kernel.
Only things to report:
Max freq is 1200 with all governors.
To turn the tablet on after sleep I have to press the button a lot.
Keep up the good work!!!
Agreed with alpha 2 running smooth same as above with frequency at 1200 keep up the good work looking forward to future updates
I just installed Alpha 2 on LiquidSmooth 3.2. After the first boot, I got multiple force closes on "com.android.acore" but after a reboot everything seems to work just fine. I will use it for the next days and report any bugs I encounter.
I just tried the alpha 2 on my tilapia running a clean install of CyanogenMod 2014-10-23. On the first boot everything is fine, but after a reboot I get SystemUI FC's everytime I unlock the device and it relocks again.
When I install M-kernel a69 or alpha 1 of this kernel, everything seems to be fine. I am using Data-F2FS, if it matters somehow.
I can post a logcat or kmesg tomorrow, right now I screwed up my hackintosh bad and it doesn't even boot, so I don't have a way to access adb.
Edit: I no longer own this phone. Information in the OP may be outdated and/or incorrect. Please go to the new thread at http://forum.xda-developers.com/nexus-6/development/rom-cyanogenmod-13-nightlies-snapshots-t3363769
DISCLAIMER: I AM IN NO WAY RESPONSIBLE FOR ANY PROBLEMS ON YOUR DEVICES CAUSED BY FLASHING THESE BUILDS. THE UPSTREAM CODE AND BUILDING IS MAINTAINED BY THE CYANOGENMOD TEAM, NOT ME. I AM NOT ASSOCIATED WITH THEIR TEAM, I AM JUST THE THREAD OWNER.
It was a fun round of unofficial nightlies but the official upstream CM13 builder for shamu is active! Please use the new download links below to grab the official nightlies. Dirty flash seems to work fine if you go from my unofficial 11-29 build to the official 11-30 one. As mentioned in the first post, I will be ceasing my personal builds for now and leave it to the CM team.
Notes: CyanogenMod's stock kernel forces encryption of storage. Please download one of the third party kernels if you wish to avoid this. Also this thread assumes you have kept up to date with bootloaders and radio. At the time of writing, the latest is from the MRA58K release and can be downloaded here.
CyanogenMod 13.0 Nightlies: Download
Open GApps: Download (I recommend arm, 6.0, micro)
Changelog: CMX Changelog
Third party kernels:
Elite Kernel
Hells Core
XDA:DevDB Information
CyanogenMod 13.0, ROM for the Nexus 6
Contributors
djh816
ROM OS Version: 6.0.x Marshmallow
Based On: CyanogenMod
Version Information
Status: Nightly
Created 2015-11-22
Last Updated 2015-12-06
There's already a thread
http://forum.xda-developers.com/nexus-6/development/rom-cyanogenmod-13-0-android-6-0-t3231497
HipKat said:
There's already a thread
http://forum.xda-developers.com/nexus-6/development/rom-cyanogenmod-13-0-android-6-0-t3231497
Click to expand...
Click to collapse
Correct, but not nightly and as far as I can tell albinoman887 is also making fixes which implies altering of upstream code. My thread intends to serve as a purely upstream source build.
djh816 said:
Correct, but not nightly and as far as I can tell albinoman887 is also making fixes which implies altering of upstream code. My thread intends to serve as a purely upstream source build.
Click to expand...
Click to collapse
I would like to say thank you, and I believe that this ROM deserves its own thread respectfully. Since there isn't much action from that other Alpha build and if you are truly building on a nightly basis then this is much appreciated and I look forward to testing.
Thanks!
HipKat said:
There's already a thread
http://forum.xda-developers.com/nexus-6/development/rom-cyanogenmod-13-0-android-6-0-t3231497
Click to expand...
Click to collapse
A Thread with Zero Support from the Thread OP and no Nightlys , its good to see this Thread with hopfully regular updates since I currently have working in the border guarding Work and never have time for building. But what i know from @djh816 updates come many times.
Tylog said:
A Thread with Zero Support from the Thread OP and no Nightlys , its good to see this Thread with hopfully regular updates since I currently have bodybuilding in the border guarding Work and never have time for building. But what i know from @djh816 updates come many times.
Click to expand...
Click to collapse
Thanks for the support and glad to build it. Just to make sure credit is given where due, any bug fixes will be made only by the CyanogenMod team and/or any git contributors. Not sure if you'll get much support from me either but I'll certainly be glad to give any tips I find. For example, if this one specific bug rears its ugly head again, you may need to rename the SetupWizard apk inside /system/app-priv/ as that has been constantly force closing for me prior to today's build.
djh816 said:
Thanks for the support and glad to build it. Just to make sure credit is given where due, any bug fixes will be made only by the CyanogenMod team and/or any git contributors. Not sure if you'll get much support from me either but I'll certainly be glad to give any tips I find. For example, if this one specific bug rears its ugly head again, you may need to rename the SetupWizard apk inside /system/app-priv/ as that has been constantly force closing for me prior to today's build.
Click to expand...
Click to collapse
MAybe test other Gapps, i had this isues with a few cm 13 builds in combination with banks gapps , i like Banks gapps but for now not with CM13 . No support for me no problem , only 1 builds in 3 Weeks in this early stage is a problem , thats what i mean . I have at the moment zero time , i am one day in the week at home and thats time for my son and my wife
Thanks for the builds. I tried (unsuccessfully) to build my own, so this helps out a lot!
nightlies has not started yet.. looking forward..
Awesome! Thanks!
Sent from my Nexus 6 using Tapatalk
Can anyone confirm that you can write to system on this build???? Wasn't working on a build from 11.20.
Sent from my Nexus 6 using Tapatalk
mexiken said:
Can anyone confirm that you can write to system on this build???? Wasn't working on a build from 11.20.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Still is not working.. I'd love to know of a fix, if any...
mexiken said:
Can anyone confirm that you can write to system on this build???? Wasn't working on a build from 11.20.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I modified build.prop just fine.
---------- Post added at 03:10 AM ---------- Previous post was at 03:08 AM ----------
Thanks OP, for bringing this to us. Seems pretty good for such an early build. I just barely flashed it but seems great so far.
Does ad away work on this build? It wouldn't work on the previous build.
Is security disable on the ROM?
cz829x18 said:
Does ad away work on this build? It wouldn't work on the previous build.
Click to expand...
Click to collapse
Doesn't seem to just yet. As others have mentioned, no /system writing just yet.
evolishesh said:
Is security disable on the ROM?
Click to expand...
Click to collapse
Doesn't seem like it, I've tried "adb shell" with "su" after but still drops me to a "$" shell rather than "#"
Will you be adding any features or will this be more of a slim to stock cm13 builds? Also thanks for your contributions
nighthawk626 said:
Will you be adding any features or will this be more of a slim to stock cm13 builds? Also thanks for your contributions
Click to expand...
Click to collapse
No features added whatsoever If they add it upstream (included in CM) it'll be here, otherwise no. Absolutely stock. Consider me a third party buildbot slave
Very nice ROM. Just to let everyone know I just finished flashing with the Open GApps Pico and it's working fine. I know, it's bad form to use something that's not recommended.
One quick question, do we get any notification that the new nightly is ready to flash or do we just check the download site?
dlbarron said:
Very nice ROM. Just to let everyone know I just finished flashing with the Open GApps Pico and it's working fine. I know, it's bad form to use something that's not recommended.
One quick question, do we get any notification that the new nightly is ready to flash or do we just check the download site?
Click to expand...
Click to collapse
For now just the download site. I may setup something similar to the pushbullet feed Chroma has if people are interested but haven't spent the time to do it yet. New 11-23 build is up now though
Edit: Woot, looks like they fixed the system rw mounting. Hm but my test file disappeared on reboot.. maybe not yet
ROM Lineage 15.1 unofficial. Built with latest GCC+ compiler.
All credits go to Lineage team.
Download Link
https://www.androidfilehost.com/?fid=818070582850505463
XDA:DevDB Information
Lineage 15.1 Unofficial, ROM for the Nexus 6
Contributors
Rondeau79
Source Code: https://github.com/LineageOS/android
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked bootloader ,latest TWRP
Version Information
Status: Stable
Created 2018-04-03
Last Updated 2018-04-03
Or you just use the official version here:
https://download.lineageos.org/shamu
does it force encrypt the phone?
mahir555 said:
does it force encrypt the phone?
Click to expand...
Click to collapse
Yes (as every official version), but you can flash the FED-Patcher to disable it. Just flash it right after LOS.
Maybe Magisk will do the trick too.
Render issue upon booting
After the booting finishes and lock screen appears, there is a pop-up saying vendor image not up to date..i understood that it wants me to install the last available factory image from google site but I was not able to successfully do it..help please!
aradhya10 said:
After the booting finishes and lock screen appears, there is a pop-up saying vendor image not up to date..i understood that it wants me to install the last available factory image from google site but I was not able to successfully do it..help please!
Click to expand...
Click to collapse
It's just a pop up. Shamu does not have a vendor image.
Go forward, it will work
gothy.gothy said:
It's just a pop up. Shamu does not have a vendor image.
Go forward, it will work
Click to expand...
Click to collapse
Except there is exclamation point notification in upper L hand corner which says "You might be a victim of software counterfeiting" and no way to cancel it.
HueyT said:
Except there is exclamation point notification in upper L hand corner which says "You might be a victim of software counterfeiting" and no way to cancel it.
Click to expand...
Click to collapse
In terminal adb/ recovery or app shell terminal:
Setprop persist.lineage.nofool true
That will fix that annoying notification.
toto-w said:
Or you just use the official version here:
https://download.lineageos.org/shamu
Click to expand...
Click to collapse
April fool's joke is terrible.
TheGreatess1223 said:
April fool's joke is terrible.
Click to expand...
Click to collapse
The official build is dated April 2nd, did the Lineage team REALLY still make an April fool's day build? Lol
H4X0R46 said:
The official build is dated April 2nd, did the Lineage team REALLY still make an April fool's day build? Lol
Click to expand...
Click to collapse
yes. yes they did. the dirty rat bastards
H4X0R46 said:
The official build is dated April 2nd, did the Lineage team REALLY still make an April fool's day build? Lol
Click to expand...
Click to collapse
Yes and have not released a updated yet. Lol
There is the 4/12/18 15.1 version available.
Sent from my Nexus 6 using Tapatalk
@Rondeau79
Now that we have official builds I think this thread doesn't make much sense anymore.
Can you please delete it?
@Rondeau79
Unfortunately, you currently seem to be the Rodney Dangerfield of XDA for Shamu. For those unfamiliar, Rodney Dangerfield is a comedian who is known for the catchphrase, "I get no respect." First with DU and now with LOS, you are asked to discontinue your threads and builds.
Just for the record, I'm not criticizing you, or DU and LOS! I understand the situation and reasoning behind why these requests were made.
I've used some of your builds on both my Hammerhead and Shamu. I have a great appreciation for those who build roms for those who cannot. So, I thank you for both your effort and sharing your work. Most recently, I used your Omni Nougat build and it was solid. From what I've read on Omni's G+, they are never going to make Shamu official for Oreo. So, maybe Omni would be a good rom for you to build unofficially.
Omni has always been a pretty innovative rom, I think there would be decent interest here in the Shamu community. Anyway, just a thought.
Thanks,
Mike T
webdroidmt said:
@Rondeau79
Unfortunately, you currently seem to be the Rodney Dangerfield of XDA for Shamu. For those unfamiliar, Rodney Dangerfield is a comedian who is known for the catchphrase, "I get no respect." First with DU and now with LOS, you are asked to discontinue your threads and builds.
Just for the record, I'm not criticizing you, or DU and LOS! I understand the situation and reasoning behind why these requests were made.
I've used some of your builds on both my Hammerhead and Shamu. I have a great appreciation for those who build roms for those who cannot. So, I thank you for both your effort and sharing your work. Most recently, I used your Omni Nougat build and it was solid. From what I've read on Omni's G+, they are never going to make Shamu official for Oreo. So, maybe Omni would be a good rom for you to build unofficially.
Omni has always been a pretty innovative rom, I think there would be decent interest here in the Shamu community. Anyway, just a thought.
Thanks,
Mike T
Click to expand...
Click to collapse
I know who Rodney Dangerfield is/was. I can build ROM's fairly well, it took 2 years for me on and off to get CM built. I first started rooting and flashing with a low end Metro PCS phone and I finally got my hands on Hammerhead. I have flashed hundreds of different ROM's and kernels over the years. Back in the days at another forum I used to see official and unofficial builds all the time. If people have an issue with my builds then why is everything so called open source. I guess the old school grassroots base of custom ROM's allure is over. I the problem I face is no one will help me with the programing part of github and what it takes to work out the coding. To any device maintainer that could lend a a helping hand that would be great. I will leave this thread open for a few more days.
@Elektroschmock I really didn't think it would have been such an issue. I get it takes a lot of work to do this, but how is anyone supposed to learn anything without trying it themselves. If I have offended anyone then I apologise.
I personally love UNOFFICIAL builds and don't see any harm especially since OFFICIAL builds can be just as unpredictable and/or unavailable
Rondeau79 said:
I know who Rodney Dangerfield is/was. I can build ROM's fairly well, it took 2 years for me on and off to get CM built. I first started rooting and flashing with a low end Metro PCS phone and I finally got my hands on Hammerhead. I have flashed hundreds of different ROM's and kernels over the years. Back in the days at another forum I used to see official and unofficial builds all the time. If people have an issue with my builds then why is everything so called open source. I guess the old school grassroots base of custom ROM's allure is over. I the problem I face is no one will help me with the programing part of github and what it takes to work out the coding. To any device maintainer that could lend a a helping hand that would be great. I will leave this thread open for a few more days.
@Elektroschmock I really didn't think it would have been such an issue. I get it takes a lot of work to do this, but how is anyone supposed to learn anything without trying it themselves. If I have offended anyone then I apologise.
Click to expand...
Click to collapse
It's only because this is confusing users. I get so many logs from users thinking they use lineage but they're using some custom, inofficial homebrew build.
toto-w said:
Yes (as every official version), but you can flash the FED-Patcher to disable it. Just flash it right after LOS.
Maybe Magisk will do the trick too.
Click to expand...
Click to collapse
Does the fadpatcher survice lineage updates or do i need to apply it each and every time?
DDQW said:
Does the fadpatcher survice lineage updates or do i need to apply it each and every time?
Click to expand...
Click to collapse
In the meantime I found out that Magisk modifies the force encryption flag too and Magisk survives OTA updates.