yashsingh1/xdaforums huggingface dataset:
[Remix OS for PC] yltan:
I already mapped Z to my another network drive. I tried "mountvol u: /s" which is not mapped to any drive but got the "The parameter is incorrect."
[Remix OS for PC] lollyjay:
Well in that case I don't have any further thoughts...
[Remix OS for PC] yltan:
Thanks for the effort...
[Remix OS for PC] jaibubwan:
I just went through this process this week. I had the same question as you, and did alot of experimentation to get the solution. This is how it works on my system (Lenovo tablet, Windows 10 Pro, Remix OS, dual boot using Grub boot loader).

Okay, ignore what you've done so far.

Assume we have a first-time installation of Remix OS.

My instructions will only help you in this situation.

I can't really correct any experiments you may have done after that.

1) When the Remix OS installation tool tells you to reboot, don't do it. Just exit it, and restart after we finish the steps below.

2) Open command prompt as an Administrator.

3) Mount your boot partition by following these instructions. I think you may have had problems with past advice because it is not so clear. This tutorial has clear steps:

http://linuxbsdos.com/2015/09/05/how-to-delete-grub-files-from-a-boot-efi-partition-in-windows-10/

4) Navigate to the following folder (change drive letter "Z:" to whatever you used to mount the boot drive):

Z:\Boot\Grub\

5) Edit the file "grub.cfg"

6) To set a default OS, that the Grub boot loader always highlights:

- Search grub.cfg and ensure the entry menuentry 'Windows' is above menuentry 'Remix OS'.

- This basically indicates that Windows is the first option in the boot menu, and Remix OS is second.

- Search grub.cfg and find the entry set default="${saved_entry}"

- Replace it with set default=0

- This basically tells the Grub boot loader to highlight the top entry (Windows) everytime it starts.

7) To change the countdown timer, that the Grub boot loader uses:

- Search grub.cfg for set timeout=

- Replace it with set timeout=3 (you can change "3" to whatever countdown number you like)

8) OPTIONAL! To set the default OS to repeat whatever was last selected:

- Suppose in the future, you want the the Grub boot loader to automatically highlight whatever OS was selected last.

- In my situation, the Remix OS installation tool has a glitch where it makes "Remix OS" automatically selected every startup.

- To correct this, repeat all the actions to mount the boot drive & edit the grub.cg file (see "6)" instructions).

- Search grub.cfg for menuentry 'Windows'

- In the line under it, add the text: savedefault

- Search grub.cfg for menuentry 'Remix OS'

- Ensure that somewhere in the lines below, the text savedefault exists. If not, add it manually.

- The problem, in my situation, was that the Remix OS installation tool only added "savedefault" to the Remix OS entry...and not the Windows entry. By adding that line to both OS's, the Grub bootloader can properly tell which OS was selected last & choose it for you on startup.
[Remix OS for PC] Deleted member 5437200:
piece of cake. modify this on your Grub line

set default="${savedefault}" <--------change to this

function savedefault {

saved_entry="${chosen}"

save_env saved_entry

menuentry 'Windows 10' --class windows {

savedefault <-----------Add this(Tells it to always highlight Windows)

search --file --no-floppy --set=root /EFI/MICROSOFT/BOOT/BOOTMGFW.EFI

chainloader (${root})/EFI/MICROSOFT/BOOT/BOOTMGFW.EFI

Go to the RemixOS line and remove savedefault from that line and done. Now it will always boot with Windows highlighted

set timeout=30 <---------Modify 30 to whatever youd like for Timeout

I made a batch file for Easy Mounting of the EFI partition. It's set up to use drive Z, so if you have a drive Z already, modify my batch file to use whatever drive you'd like. Extract and run as Admin

PizzaG Windows 10 EFI Partition Helper: https://drive.google.com/open?id=0B_NCp06S3NUmUVpNR2RheHpOTlk
[Nexus 10 Q&A, Help & Troubleshooting] XxM4tzexX:
Hi

How is the status on development of LineageOS for manta? Is anyone working on this?
[Nexus 10 Q&A, Help & Troubleshooting] asc1987:
Would be great LineageOS on Nexus 10....nougat flavour please!!!
[Nexus 10 Q&A, Help & Troubleshooting] dekapode:
To get LOS on our beloved Nexus 10 would be awesome. :victory:
[Nexus 10 Q&A, Help & Troubleshooting] AgentOrange96:
Apparently, Manta is on the list of devices that will be getting Lineage. However, the initial release is likely to be Marshmallow based still.
[Nexus 10 Q&A, Help & Troubleshooting] XxM4tzexX:
I'm fine with mm since there is no Xposed for nougat so far.
[Nexus 10 Q&A, Help & Troubleshooting] AgentOrange96:
I've bee trying to build for three days now. My last attempt ended right before making the zip after six hours on my old Acer laptop (because it has Ubuntu) with the error:

TypeError: argument of type 'nonetype' is not iterable android
[Nexus 10 Q&A, Help & Troubleshooting] Roatandave:
I managed to get a nougat build but, it will not go past the google logo.

I am using bbqlinux.

Kernel source from binkybear for nethunter support.

The kernel works I just cant get it to go further
[Nexus 10 Q&A, Help & Troubleshooting] zerebruin:
Got a working LineageOS 13 build for manta without too much of a hitch.

The build guide ///wiki.lineageos.org/manta_build.html#extract-proprietary-blobs) is missing the required package libxml2-utils. If you install that and follow the guide closely it should run fine.

Remember to activate caching really helps speed up build times. I'm down to 15 minutes on consecutive builds on a ubuntu headless server on virtualbox with 4 cores & 8G RAM.

Getting the build installed was a bit trickier. TWRP flash over the last CM13 build didn't work.

I needed to flash the official ROM first, then install the latest TWRP version (//twrp.me/devices/samsungnexus10.html)

It's been running reasonably stable for two days with the 6.0 micro opengapps package apart from some PlayStore installation issues, but I haven't tested extensively.

Cheers
[Nexus 10 Q&A, Help & Troubleshooting] AgentOrange96:
Your VM has twice the cores and twice the RAM as my laptop. I wish I could run this on my desktop, but the Linux subsystem is nearly impossible to build on >.<

I'll see if I didn't have that package installed and give it another go I suppose.
[Nexus 10 Q&A, Help & Troubleshooting] AgentOrange96:
Build success! And in an hour fifteen minutes this time! (Last time it failed after six hours) I already had libxml2-utils installed. I did use distcc with another computer, but I'm not sure if it was even used. I suspect the majority of the speedup was due to caching from my last attempt.

Edit: I can't for the life of me get the home button to work...

I'm having the exact issue described here, but no solutions will work.
[Nexus 10 Q&A, Help & Troubleshooting] zerebruin:
Hmm, home button works fine for me.

I've only got one bug that I had infrequently on the official CM builds, too: I can only install one app from the play store at a time.

Have to close the playstore and reopen it. That's probably related to GAPPS, though.

If you want, you can try out the build I'm currently running. Not absolutely fresh, but haven't had any problems except the one above:

//androidfilehost.com/?fid=745425885120704233
[Nexus 10 Q&A, Help & Troubleshooting] XxM4tzexX:
I compiled lineage os yesterday in 1,5h. I will try to install it this evening. I could upload it for everyone until there are official builds.
[Nexus 10 Q&A, Help & Troubleshooting] XxM4tzexX:
My build doesnt boot. I don't know if the file size of the zip is right. Mine is 283 mb . [MENTION=8029997]zerebruin[/MENTION]
[Nexus 10 Q&A, Help & Troubleshooting] zerebruin:
[MENTION=4855645]XxM4tzexX[/MENTION] not sure, if build size is a good indicator. My build from Jan 27 build was 278.4 MB (291,889,838 Bytes).

Just built again with a fresh repo sync and that was 278.4 MB (291,885,568 Bytes). So not much of a difference.

Your installation works, just not the system bootup? which bootloader are you using?
[Nexus 10 Q&A, Help & Troubleshooting] XxM4tzexX:
Installation is fine although the install process is quite fast compared to a installation of cm. What do you mean by 'which bootloader'?
[Nexus 10 Q&A, Help & Troubleshooting] zerebruin:
sorry, I meant the recovery, of course. still getting mixed up with terms here sometimes :|

Are you using the stock recovery or a custom one like TWRP or CWM?

They might give more/better feedback on installation errors.
[Nexus 10 Q&A, Help & Troubleshooting] XxM4tzexX:
i'm using TWRP.

Are you using repo sync or repo sync -c (to downoad only the current brunch, should not make any difference)?
[Nexus 10 Q&A, Help & Troubleshooting] zerebruin:
I've been using the full repo sync...

I'm using TWRP 3.02 and If I remember correctly, I needed to do a full wipe for the first install to work. Then again, after the installation went through it all worked fine.

I guess the next step would be to go through the build log...
[Nexus 10 Q&A, Help & Troubleshooting] XxM4tzexX:
I finally got it working now.
[Nexus 10 Q&A, Help & Troubleshooting] zerebruin:
Congrats!

Out of interest: What was the fix?
[Nexus 10 Q&A, Help & Troubleshooting] XxM4tzexX:
I started fresh and made a full repo sync this time instead of repo sync -c. Don't know if this was the "fix" but it is working now[emoji3]
[Nexus 10 Q&A, Help & Troubleshooting] followmsi:
Did you try to build 14.1 branch too ?
[Nexus 10 Q&A, Help & Troubleshooting] XxM4tzexX:
No didn't try to build 14.1. Don't know if this is even possible yet.
[Nexus 10 Q&A, Help & Troubleshooting] followmsi:
It seems to be possible .. just made a test build - based on 14.1 branch. :)

lineage-14.1-20170214-UNOFFICIAL-manta.zip

lineage-14.1-20170214-UNOFFICIAL-manta.zip.md5sum

Pls download from here .. https://drive.google.com/open?id=0By6p5AdQfavBNHkxVWhNOW5CdVk

This build has not beed tested yet ..

Cheers
[Nexus 10 Q&A, Help & Troubleshooting] XxM4tzexX:
No doesn't boot. Tried it.
[Nexus 10 Q&A, Help & Troubleshooting] followmsi:
Thanks for testing .. just dit flash it myself.

Stuck at google logo. :(

Seems to be kernel related .. maybe we get it running on 14.1.
[Nexus 10 Q&A, Help & Troubleshooting] followmsi:
It was actually the missing "external/stlport" and not the kernel :)

https://github.com/LineageOS/android_external_stlport

Now it's booting fine .. running very well.

Made a dirty flash over my CM13/LineageOS13 installation .. seems to work fine.

lineage-14.1-20170216-UNOFFICIAL-manta.zip

lineage-14.1-20170216-UNOFFICIAL-manta.zip.md5sum

Installation:

1. Boot into TWRP

2. Install lineage-14.1-20170216-UNOFFICIAL-manta.zip

3. install open_gapps-arm-7.1-nano-20170216.zip

4. install SuperSU-v2.79-201612051815.zip

5. Reboot into system ..

Due to supersu installation it will boot twice - no panic, it´s normal !

Pls download from here .. https://drive.google.com/open?id=0By6p5AdQfavBNHkxVWhNOW5CdVk

Enjoy Android 7.1 on Nexus 10 ... :)
[Nexus 10 Q&A, Help & Troubleshooting] essentially_mia:
That is amazing, downloading!
[Nexus 10 Q&A, Help & Troubleshooting] *effeks*:
Hello guys!

I'm freshly registered to xda forums. I'm a happy and proud owner of a Nexus 10 32Gb.

I do install like followmsi says. It boots up to the huge lineage logo green on white. I see the battery circle upper right. It doesn't goes any further. Didn't saw any apps initialising process. I can press volume buttons and see the volumes pull down.

I can't pull bars.

I tried installing with pico. Tried wiping between each zips. Tried without SuperSU.

Always stucked at the big LOGO!

Any suggestions for a simple user!? Or I'll go back to LOS 13. Which works fine enough for now. Some little bugs with button savior app. Beside that works well.

By the way I have the first EXPERIMENTAL and Nightly that appeared few hours at the beginning February at download.lineageos.org/manta . It's been removed quickly. It was MM. For me the EXPERIMENTAL didn't transit properly, it got stucked after initialising apps. I needed to install the nightly from the raw.

Thanks

Cheers all! :)
[Nexus 10 Q&A, Help & Troubleshooting] followmsi:
As said before, I did a dirty flash .. no problems at all.

What did you wipe ?

Pls wipe system and caches only, not data.

Start a fresh install of the ROM and gapps and/or supersu.zip.

Reboot to system ...

If you still have problems, pls wipe data partition .. e.g. do a factory reset.

Does ist help ?

Cheers
[Nexus 10 Q&A, Help & Troubleshooting] *effeks*:
Thanks for your quick reply.

Yep, I did swipe the whole thing except internal storage with all my failed trials. Including pure fresh install.

I found the answer to my issue. I had to install YOUR LOS13 and then..........

I've discovered that dirty things are "often" the best!! :silly:

I now enjoy the improved smoothness and features from Nougat onto my beloved Samsung Google Nexus 10!

Thanks again. Thanks for your work with this build and I'm looking forward for all available upgrades from my simple user position.

Cheers! :)
[Nexus 10 Q&A, Help & Troubleshooting] XxM4tzexX:
Is it normal that my first build last week took about 1,5 h and now today's build took only 15 minutes??
[Nexus 10 Q&A, Help & Troubleshooting] *effeks*:
A user question.

With the followmsi Nougat build. Under developer options, about root access I only have the "ADB only" option and the "Manage root accesses" is blurred not accessible.

Any infos to fill my user ignorance here. I always had those options fully accessible under CM.

Thanks!
[Nexus 10 Q&A, Help & Troubleshooting] XxM4tzexX:
Lineage os doesn't come with superuser by default. You have to install SuperSU by yourself.
[Nexus 10 Q&A, Help & Troubleshooting] *effeks*:
Hello! SuperSU been installed from TWRP along with the OS and opengapps.

I've never worked through SuperSU before. When I open it, it asked me first to enable root access and redirect me to the OS developer menu. I can't process any further. There is nothing more I can do about root through developer menu.

Since I've never worked with SuperSU, I try within it to open the little "ratchet" icon to meet with SuperSU but it crashes, crashes and crashes.

anything else guys to fill my ignorance?Usually I google stuff. For now I just sit on my lazy ass and ask here!

Thanks!
[Nexus 10 Q&A, Help & Troubleshooting] boogaloo1977:
Thanks for this. I have managed to get a build of 14.1 hanging at the Google logo. How did you determine what was missing - is there a startup log I can pull via recovery for clues as to what's not working?
[Nexus 10 Q&A, Help & Troubleshooting] ravenofdoom:
https://download.lineageos.or/manta

They've started posting to the official site for manta as of yesterday. Only CM13.1 so far though. Looks like there's somebody who's possibly fixed the screen resizing bug on 14 according to github. Hopefully we'll see 14.1 soon.
[Nexus 10 Q&A, Help & Troubleshooting] followmsi:
As I know there is no log at this stage .. maybe via serial output.

Logcat is starting later in the boot process.

Pls check if you have all the dependencies ..

https://github.com/LineageOS/android_device_samsung_manta/blob/cm-14.1/lineage.dependencies

And the vendor stuff stuff too.

Cheers
[Nexus 10 Q&A, Help & Troubleshooting] Matteo_666:
Does anyone know how to root the official Manta weekly of lineage? Tried the 14.1 ZIP without success and supersu ended up in a bootloop...

Gesendet von meinem Nexus 10 mit Tapatalk
[Nexus 10 Q&A, Help & Troubleshooting] XxM4tzexX:
The latest supersu 2.79 should work without problems
[Nexus 10 Q&A, Help & Troubleshooting] followmsi:
As said above .. SuperSU 2.79 works without issues on LineageOS 13.0 and 14.1.

I am using it on F2FS data partition .. No problems so far.

On ext4 data partitions should be no problems at all.

Cheers
[Nexus 10 Q&A, Help & Troubleshooting] boogaloo1977:
Thanks for the tip - yes I had messed up including the vendor blobs. Extracted them manually from stock image but hadn't run the setup-makefiles.sh.

Now building 14.1 and I've managed to get it to work from a clean install (eg not using 13.0 as a pre-requisite, from a clean wiped & formatted device). There's a bit of a workaround required to get past the Setup Wizard, which is:

1. When the LineageOs welcome screen loads, pull down the top of the screen and select the settings icon

2. Click back to return to the welcome page

3. Rotate the screen 90 degrees and the "Next" button will appear - continue as normal

I am not sure if this works with followmsi's build, but can share my build if not.

Cheers
[Nexus 10 Q&A, Help & Troubleshooting] followmsi:
Thanks for your input .. For 20170225 I have removed the SetupWizard completetly now.

Will wait for some code changes.

Cheers

EDIT:

They are quick ..

github.com/LineageOS/android_packages_apps_SetupWizard/commit/0c7b92ad7a2a6a7237e835a77b5f46932b5c72d4
[Nexus 10 Q&A, Help & Troubleshooting] boogaloo1977:
Very quick indeed - I missed that commit in my last build by about 1hr. Now re-built and confirmed works fine from clean install all the way through the Setup Wizard!
[Nexus 10 Q&A, Help & Troubleshooting] followmsi:
Nice :)

Just compiling as well ..

EDIT:

Confimed .. SetupWizard has been fixed. :)

lineage-14.1-20170227-UNOFFICIAL-manta.zip

Cheers
[Nexus 10 Q&A, Help & Troubleshooting] nesai:
hi,

first tried to flash official lineageos13, but it failed with error7. as i did not want to do a factory-reset,

yesterday i flashed my nexus10 from cm13 without factoryreset to lineage13 unoff. and than after a reboot to 14.1. unoff.

i was surprised, no problems at all, runs great an i was able to keeep all my settings an data.

thank you for your work !

hannes
[Nexus 10 Q&A, Help & Troubleshooting] followmsi:
Have seen this error 7 too .. blocks further installation. :(

Made a TWRP backup of data before Install, did wipe data, and restored data again after lineageos installation, but before SuperSU Installation.

Works too ;)

This way you can migrate your data partition from ext4 to F2FS .. keeping all your settings.

When you change to F2FS via TWRP you will loose internal-storage too, due to format of data partition.

As you know, the internal storage is not part of TWRP backup.

But to be honest .. not much performance improvement on manta, if at all :)
[Nexus 10 Q&A, Help & Troubleshooting] goodflood:
CM 13 snapshot onwards

Hello,

Ah! This is where the action is at : )

I have manta running CM 13 snapshot (december 2016).

LOS 13 released the first update -- Do I need an experimental build?

Don't I need it to go to LOS 13 official? LOS 13 Unofficial? LOS 14 Unofficial?

Should I just dirty flash the official LOS 13 on top of CM 13 Snapshot?

Don't use GAPPS... but I will want to flash addSU.zip.

Thanks!
[Nexus 10 Q&A, Help & Troubleshooting] followmsi:
Do you have a backup of your data partition ?

Try to start directly with LOS 14.1 - the dirty way ;)

In case you need a factory reset the SetupWizard is working now :)

If you have a backup you can restore at any stage for testing ..

Good luck!
[Nexus 10 Q&A, Help & Troubleshooting] DrGirlfriend:
Either the headphone jack is not being detected or I just b0rked my hardware. Built-in speakers only, didn't test Bluetooth.

Thanks for this rom

EDIT: just saw thread in Android Development section stating headphone not working - following that thread now
[Nexus 10 Q&A, Help & Troubleshooting] nomen_fictus:
I upgraded from CM13 code to the your latest version and it worked well. I had tried several times and was caught in bootloop. I then installed the twrp version you have on your download page. After installation of twrp I rebooted to recovery and the 14 install then worked. Thanks!
[Nexus 10 Q&A, Help & Troubleshooting] griffoun:
I tried CM13 20171017 nightly build and caught in bootloop just installing 10 apps... should I grab the 20171019 CM14 build from Google Drive, or the one from 2017-08-11? Thanks!
[Nexus 10 Q&A, Help & Troubleshooting] griffoun:
Just installed the 20170811 build; Can't even get past the "Google Services" setup screen during the first bootup.

---------- Post added at 07:16 PM ---------- Previous post was at 06:59 PM ----------

Same problem with 20171019 build.

It seems none of the Lineage OS Nexus 10 ROM is stable enough, CM13 or CM14..
[Omni Q&A] DREWHAMM974:
Okay guys so I started to build Omni for the Droid Turbo using existing CM 14 device trees. I got to the point where I was starting the build and had an error pop up. Does anyone know what this may be?

andrew@andrew-Z97X-Gaming-5 ~/omni $ lunch

You're building on Linux

Lunch menu... pick a combo:

1. aosp_arm-eng

2. aosp_arm64-eng

3. aosp_mips-eng

4. aosp_mips64-eng

5. aosp_x86-eng

6. aosp_x86_64-eng

7. omni_quark-userdebug

Which would you like? [aosp_arm-eng] 7

device/generic/motorola/quark/AndroidProducts.mk:18: *** missing separator. Stop.

WARNING: Trying to fetch a device that's already there

Traceback (most recent call last):

File "build/tools/roomservice.py", line 353, in <module>

fetch_device(device)

File "build/tools/roomservice.py", line 321, in fetch_device

git_data = search_gerrit_for_device(device)

File "build/tools/roomservice.py", line 81, in search_gerrit_for_device

device_data = check_repo_exists(git_data, device)

File "build/tools/roomservice.py", line 58, in check_repo_exists

"exiting roomservice".format(device=device))

Exception: quark not found,exiting roomservice

device/generic/motorola/quark/AndroidProducts.mk:18: *** missing separator. Stop.

** Don't have a product spec for: 'omni_quark'

** Do you have the right repo manifest?

:confused::confused:
[Omni Q&A] ChinmayXD:
Just add a separator on androidproducts line #18 & error's gone
[Omni Q&A] himavanth.reddy925:
help plz

Im also getting same error.. im unsing cm tree for aosp 6.0.1

Device is merlin .. im a nood im still learn so please can you say how to solve this error.

Thnks in advace bro
[Omni Q&A] BabluS:
where can open androidproducts
[Omni Q&A] Stephanizgo:
What is even a separator

How can I add a separator my English is quite bad
[Sony Xperia XZ Questions & Answers] napalm.potter:
Hi

I just notice that in CPU-Z it show clock to be 307MHz-1.59GHz, and 2.15GHz dualcore plus 1.59GHz dual-core.

I don't know if it has been like this since the beginning or it just after Nougat update, but I think I remembered it to be 2.15 GHz in CPU-Z before the update

I've attached screenshots of both program below

Best,
[Sony Xperia XZ Questions & Answers] L3RAT:
Yeap, all 820 shows that in CPU-Z. Our CPU has 2 clusters:

2 "small" cores - 307MHz-1.59GHz

and

2 "big" cores - 307MHz - 2.15GHz

CPU-Z can not present it properly so they use Intel-like system of showing 1.59GHz as normal frequency and everything above is treated as "turbo".

But what bother me is that I have never seen those "turbo frequency in CPU-Z. Also after Nougat update I barely see "big" cores working and phone is stuttering from time to time. I hope they did not overly optimised it :/
[Sony Xperia XZ Questions & Answers] DHGE:
debug info more concise on CPU-data than screen

[MENTION=3979547]napalm.potter[/MENTION]

Well mine shows 307MHz - 2.15GHz on the screen (different than yours), same Android Version than you have, CPU-Z 1.21

send to yourself "debug infos":

CPUs : 4
SoCs : 1

CPU 0 : AArch64 Processor rev 2 (aarch64)
Name : Qualcomm Snapdragon 820
Model : Qualcomm Technologies, Inc MSM8996
CPUs : 4

Core set 0 : Qualcomm 0x211
Core set 0 Nb Cores : 2
Core set 0 Max Clock : 2150 MHz
Core set 0 Impl.id : 0x51
Core set 0 Arch.id : 0x8
Core set 0 Var.id : 1
Core set 0 Part.id : 0x211
Core set 0 Rev.id : 2
Core set 0 Revision : r1p2

Core set 1 : Qualcomm 0x205
Core set 1 NbCores : 2
Core set 1 Max Clock : 1593 MHz
Core set 1 Impl.id : 0x51
Core set 1 Arch.id : 0x8
Core set 1 Part.id : 0x205

Arch : Kryo
Codename :
Process : 14 nm
GPU Vendor : Qualcomm
GPU Renderer : Adreno (TM) 530

Model : F8331 (F8331)
Manufacturer : Sony
Board : QC_Reference_Phone
Hardware : qcom
Android Ver. : 7.0
Kernel Arch. : armv8l
[Sony Xperia XZ Questions & Answers] EartHzShake:
My device is Xperia XZ Dual

It's cpu clock show me 1.59Ghz all four cores (sorry for my bad english)