yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] GuestK0010:
I think it will work with Fi, not sure, give it a try and let us know please.. u do not get the ex kernel manger app. U can install it via play store, and mess with those settings through the app. The features are in built, u just set them how u would like.
[Nexus 6 Android Development] ECrispy:
I don't mean kernel manager app. I mean when you flash EX kernel in recovery it runs thru a wizard which lets you choose all these settings. If I dont do it here, then in my experience even if I choose 'apply on boot' in kernel manager, the settings never stick. e.g. dt2w, if I set it while flashing it works every time, otherwise I have to open the setting app every boot and again set it.

Hope that makes sense? I'm sure there's some file thats being written maybe init.d scripts etc.
[Nexus 6 Android Development] GuestK0010:
I know what u are saying. U do not have that setup wiz within the ROM, every feature and option is just in built and u can use that ex kernel manager to set those settings as u would have when u do a standalone ex kernel install with the wizard. It will work this time, cuz the ROM was compiled together with the ex kernel source code and the rom itself.it is built with them all in there. Just try it and u will see what I mean.. paid version of the app btw..

Update: any settings u adjust or change within the ex kernel manager app to turn on or off fast charge, double tap to wake etc, they all can be set, then tap the power looking button to turn on and then they are set. I tested this with a couple reboots to be sure. They stick and are working great. Wavesdashdoc has some settings listed on his rom repo, that may benefit as well. For now I am personally just running default and everything is running perfectly....
[Nexus 6 Android Development] maijinservo:
So happy to see this.
[Nexus 6 Android Development] BigDig:
The ROM is great. Running since last night after a clean flash. One bug I've found so far is that the volume down key does not lower the ring volume and does not enter DND mode. Instead it lowers the media volume. I've checked the button settings and they are correct. Also the phone got a little laggy at some point today and I rebooted.
[Nexus 6 Android Development] GuestK0010:
Thanks, I am glad you like it. Couple things that may help you out, The volume key being for the media volume is a setting. Go to settings/screwd settings/system/buttons/ Turn off "volume keys control media volume" and turn on "do not disturb switch"( this will allow you to show DND when hitting vol down..hold it and it will turn it on).. this fixes both of your issues. About lag, that must be some app you are using. I have been using the Rom for the past 2 months and chose to build this specific rom because of the zero lag. So i am not sure other than maybe user apps, old gapps, or maybe u changed the default kernel settings to try to improve the performance and messed up the default config by mistake... I built with EX Kernel's newest source because it has so many inbuilt features and in my opinion is a flawless kernel. So, any suggestion i would gladly look into for you but on your end i ask that you please document what running services you have and when and under what circumstances the lag occurs. That way i can better help. Additionally, i do not condone the use of Xposed b/c the lag/performance drop resulting from it. That is another possibility.
[Nexus 6 Android Development] BigDig:
Thanks for the quick response! I followed your advice and got the volume button thing sorted out. I didn't root until today, I changed the ex cpu governor to ex instead of interactive that's the default one as I find ex provides better performance... I'll let u know if the lag appears again and under what conditions
[Nexus 6 Android Development] Duyo:
Rom is fantastic. Fast, great battery life, Viper, Maps, You Tube, Netflix all working. Bluetooth connection to watch is very good.

Question: I have jump to camera with power button on. When I changed the bottom right lock screen shortcut to messaging and double press the power button with the screen off it opens up messaging instead of the camera. Is this intended? First time I have seen this behavior.

Thanks
[Nexus 6 Android Development] GuestK0010:
Thanks that means a lot. Ok so the past few mins I have been trying to replicate your issue. I have to mess with it some more, but I got it to do what u said. I think the gesture for power2x=camera, only works like it's supposed to if the bottom default lockscreen apps are left at default. When we changed them, it modifies the power2x=camera gesture to match the new default app that has now replaced the camera. I got it to gesture and open 3 different apps I set as my bottom right default. So it's kinda a bug, and nice catch I don't miss much and missed it..lol. but I will ask the team if they know if I can fix it, or not. Worst case, I remove that jump feature or at least set it up a bit differently so doesn't have unintended results. It should maybe just say hold the power button to shortcut to your bottom designated application...Sorry if it "screwed" up your intended shortcut..(pun intended..screw'd) har har..
[Nexus 6 Android Development] GuestK0010:
Some info for anyone wondering
[Nexus 6 Q&A, Help & Troubleshooting] vigkumar:
Hi Folks,

Need some help here. I'm new to flash and other stuff.

I tried to install Lineage 15.1. I did fastboot oem unlock which erased everything. I'm stuck in AP fastboot Flash Mode.

I tried below things.

C:\Downloads\Nexus\platform-tools-latest-windows\platform-tools>fastboot.exe flash system lineage-15.1-20180402-nightly-shamu-signed.zip

< waiting for any device >

(bootloader) slot-count: not found

(bootloader) slot-suffixes: not found

(bootloader) slot-suffixes: not found

(bootloader) has-slot:system: not found

target reported max download size of 536870912 bytes

sending 'system' (498496 KB)...

OKAY [ 18.385s]

writing 'system'...

(bootloader) Failed to erase partition

(bootloader) Failed to flash partition system

FAILED (remote failure)

finished. total time: 18.400s

C:\Downloads\Nexus\platform-tools-latest-windows\platform-tools>fastboot.exe flash recovery twrp-3.2.1-0-shamu.img

(bootloader) slot-count: not found

(bootloader) slot-suffixes: not found

(bootloader) slot-suffixes: not found

(bootloader) has-slot:recovery: not found

target reported max download size of 536870912 bytes

sending 'recovery' (12027 KB)...

OKAY [ 0.391s]

writing 'recovery'...

(bootloader) Failed to erase partition

(bootloader) Failed to flash partition recovery

FAILED (remote failure)

finished. total time: 0.406s

C:\Downloads\Nexus\platform-tools-latest-windows\platform-tools>fastboot.exe boot twrp-3.2.1-0-shamu.img

(bootloader) slot-count: not found

(bootloader) slot-suffixes: not found

(bootloader) slot-suffixes: not found

downloading 'boot.img'...

OKAY [ 0.422s]

booting...

OKAY [ 0.031s]

finished. total time: 0.469s

[PHONE GETS TWRP RECOVERY SCREENS]

I tried adb sideload as suggested in one of the pages and got this

C:\Downloads\Nexus\platform-tools-latest-windows\platform-tools>adb sideload lineage-15.1-20180402-nightly-shamu-signed.zip

Total xfer: 0.01x

In Phone :

Starting ADB sideload feature ..

Installing zip file '/sideload/package.zip'

Warning: No file_contexts

Target : google/shamu/shamu:7.1.1/N6F27m/4299435:user/release-keys

could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system, assuming ext4

mount: Failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: Invalid Argument

Failed to unmount /system : No such volume

script aborted (no error message)

Updater process ended with ERROR: 7

Finally, I tried with copying installer files in OTG Drive and tried to install from there. But couldn't mount it as I can't make OTG check in Mount in TWRP.

Please help .. How can I overcome this and install OS in my phone.
[Nexus 6 Q&A, Help & Troubleshooting] mal13:
Can you boot into twrp?? When i flashed my shamu first time...i unlocked bootloader, flashed twrp, rooted and then via twrp flashed roms from zips, gapps and magisk. As far as i remember. Otg is some times really tricky...i tried several usb sticks and suddenly one worked and i got forward in flashing. Nowadays my pc recognise my shamu in twrp and i can move files in it (if needed). Hope that helps.
[Nexus 6 Q&A, Help & Troubleshooting] vigkumar:
Yes, I can boot into twrp using this command...

fastboot.exe boot twrp-3.2.1-0-shamu.img

This bringstwrp in my phone. But I can't move files to the phone. Even I tried adb push which pushes the files to the phone but while installing it got failed.. I'm not sure what I'm missing..
[Nexus 6 Q&A, Help & Troubleshooting] ktmom:
I think the problem is the fastboot you are using is not compatible with shamu. See if this minimal install works any better; [TOOL]Minimal ADB and Fastboot. Try one of the older releases, maybe 1.4 or 1.3.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[Nexus 6 Q&A, Help & Troubleshooting] vigkumar:
Same issue with Minimal ADB. I used 1.4 ...

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.2.1-0-shamu.img

(bootloader) has-slot:recovery: not found

target reported max download size of 536870912 bytes

sending 'recovery' (12027 KB)...

OKAY [ 0.391s]

writing 'recovery'...

(bootloader) Failed to erase partition

(bootloader) Failed to flash partition recovery

FAILED (remote failure)

finished. total time: 0.406s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system lineage-15.1-20180402-nightly-shamu-signed.zip

(bootloader) has-slot:system: not found

target reported max download size of 536870912 bytes

sending 'system' (498496 KB)...

OKAY [ 15.628s]

writing 'system'...

(bootloader) Failed to erase partition

(bootloader) Failed to flash partition system

FAILED (remote failure)

finished. total time: 15.644s
[Nexus 6 Q&A, Help & Troubleshooting] vigkumar:
Looks to me that my filesystem on is corrupt. Is there any commands to fix the filesystem. I tried with repair in TWRP but that is also not working.
[Nexus 6 Q&A, Help & Troubleshooting] ktmom:
When in doubt, my philosophy is to return to stock and start over. If you have any data on the user data partition, back it up through ADB and then try fastboot flashing the last google stock ROM. The instructions (if you need them) are on the Factory Image page. If Fastboot still fails, you can try sideloading through ADB an Full OTA.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[Nexus 6 Q&A, Help & Troubleshooting] vigkumar:
Thank you very much for your response. I tried both Fastboot and ADB. Both failed :( Well, I suppose if I could flash the right radio 'D4.01-9625-05.45+FSG-9625-02.117', I guess Fastboot would work. Am I right.

What is the right way to identify the correct radio file.

checking product...

OKAY [ -0.000s]

checking version-bootloader...

OKAY [ 0.016s]

checking version-baseband...

FAILED

Device version-baseband is 'D4.01-9625-05.51+FSG-9625-02.118'.

Update requires 'D4.01-9625-05.45+FSG-9625-02.117'.

finished. total time: 0.094s

ADB devices produces nothing. Hence I booted in twrp and use ADB sideload from there.

C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\platform-tools>fastboot boot twrp-3.2.1-0-shamu.img

(bootloader) slot-count: not found

(bootloader) slot-suffixes: not found

(bootloader) slot-suffixes: not found

downloading 'boot.img'...

OKAY [ 0.432s]

booting...

OKAY [ 0.038s]

finished. total time: 0.469s

C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\platform-tools>adb sideload shamu-ota-n6f27m-df27bd83.zip

Total xfer: 0.01x

Even it got failed with the below error.

Installing zip file '/sideload/package.zip'

Target: google/shamu/shamu:7.1.1/N6F27M/4299435:user/release-keys

Patching system image unconditionally...

E1001: Failed to update system image.

Updater Process ended with Error 7.
[Nexus 6 Q&A, Help & Troubleshooting] ktmom:
Radio makes no difference. You can run any radio from any release on any release. It affects only the data/cell connection and sometimes an older one forces better performance depending on carrier and location.

Try fastboot flashing with the sim card removed.

The manual steps to flash through fastboot are in the [GUIDE][HOW TO] Flash Factory Images thread. Scroll down to "Method 2 : (Long, but works always)".

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[Nexus 6 Q&A, Help & Troubleshooting] Elektroschmock:
That was your first error! You can't flash a nightly via fastboot.

You need to boot into recovery and select it there to install.
[Nexus 6 Q&A, Help & Troubleshooting] vigkumar:
Both method failed. :crying::crying:
[Nexus 6 Q&A, Help & Troubleshooting] ktmom:
You are trying to fastboot flash the STOCK ROM I linked to earlier, right?

As [MENTION=3383960]Elektroschmock[/MENTION] pointed out -and I originally missed- your first mistake was trying to fastboot flash the lineage ROM. You also CAN NOT ADB sideload anything except the OTA stock image linked to earlier. That includes the stock ROM used to fastboot flash, or any custom ROM.

** If ** you really are trying to fastboot flash stock, and it doesn't work, what does:

fastboot devices

return?

The N6 is a simple device to work with and very forgiving, but you must use common sense and think about what your doing.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[Nexus 6 Q&A, Help & Troubleshooting] vigkumar:
Yes, I'm trying stock and followed links that you provided. Both installation methods failed.

Fastboot devices returns,

C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\platform-tools>fastboot devices

ZX1G525DZX fastboot
[Nexus 6 Q&A, Help & Troubleshooting] ktmom:
Extract the zip file downloaded from the factory image page. For example, downloaded file is "shamu-n6f27h-factory-718e138f.zip" then when extracted I get a folder "shamu-n6f27h".

Navigate into the extracted folder (e.g "shamu-n6f27h")

Now copy the radio-shamu-XXXXXX.img (the x's are placeholders it depends on the radio version) to the location where your fastboot is then rename it to just "radio.img"

Back in the originally extracted folder ("shamu-n6f27h"), there will be another zip file, in my example it's "image-shamu-n6f27h.zip". Extract that and I end up with a folder "image-shamu-n6f27h".

Now copy the following files from the new folder (e.g. "image-shamu-n6f27h") to the location where your fastboot is;

boot.img

cache.img

recovery.img

system.img

userdata.img

Navigate on the PC to the location where the fastboot binary is.

Boot the phone into fastboot by pushing and holding the volume down and power buttons

Look on the phone's screen and there should be a message "Device is unlocked. Status Code 3" confirming the bootloader is unlocked.

Double check that "fastboot devices" returns your device.

Now type "fastboot reboot-bootloader", which will power off the phone and start it again in the same place. Just double checking that you are communicating correctly with the device.

1) flash the boot image (also called the kernel):
fastboot flash boot boot.img

reboot:

fastboot reboot-bootloader

2) If you want, you can flash the radio:

fastboot flash radio radio.img

reboot:

fastboot reboot-bootloader

3) flash recovery:

fastboot flash recovery recovery.img

reboot:

fastboot reboot-bootloader

4) flash system partition:

fastboot flash system system.img

reboot:

fastboot reboot-bootloader

5) flash userdata (which will wipe the internal storage:

fastboot flash userdata userdata.img

reboot:

fastboot reboot-bootloader

6) flash cache:

fastboot flash cache cache.img

Now we are done flashing all of the partitions on a N6 so reboot to system:
fastboot reboot

If any of these fail, or don't match what I described above, post the exact errors here, preferably formatted within CODE tags. They look like: [ CODE ] [ / CODE ] without any spaces inside the brackets. The spaces are necessary to prevent the forum from executing the example as formating tags.

Posting "it doesn't work" may be funny, but it does nothing to help others help you. You must be specific as to what you were doing and what happened.
[Nexus 6 Q&A, Help & Troubleshooting] ktmom:
Couple of questions.

You are working on a Nexus 6, right? Not a 6P or other device?

Did you reboot between each img flash? When you returned to the bootloader each time after rebooting, did you long press the power button because it still said "locked status 2"?

I have to say, this is the first I've ever heard of a reboot causing it to be locked then long pressing the power button to unlock. Either the bootloader is unlocked or it isn't.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

---------- Post added at 14:03 ---------- Previous post was at 14:00 ----------

Additional question, when you reboot using only the key combination, does it always show unlocked?

If yes to that, maybe it's back to my concern that the version of fastboot is not working well with the N6.

If you haven't, try with the minimal version you downloaded the other day.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

I
[Nexus 6 Q&A, Help & Troubleshooting] HueyT:
1] If u can get to twrp, use microUSB flash drive and move ROMs over to flash via TWRP. Must mount OTG drive in TWRP after plugin to recognize flash drive

2) if u can get to fastboot mode and your PC recognizes your device via "fastboot device" command, try using WUG NRT tool kit to restore back to stock, then root [MENTION=293102]ND[/MENTION] put TWRP on there, then flash custom Roms via TWRP
[Nexus 6 Q&A, Help & Troubleshooting] dr1445:
novice here. screwed up my 6p and got in a similar place as you are. i started adb side load in my phone and linux pc terminal, adb start-server, then adb sideload [add a space] then i dragged and dropped the factory firmware to terminal then enter. i had to try a couple of googles angler firmware before it found the the right format. saved my bacon.
[Nexus 6 Q&A, Help & Troubleshooting] HueyT:
Good point. If fails on Windows, Linux PC may work
[LineageOS Questions & Answers] arko9699:
Is there an official implementation for this device or is it possible to use another compatible version as present on the downloads webpage. If so please specify which zip is the one I want.
[MDA III, XDA III, PDA2k, 9090 General] ponciusz:
Hi.

is wizard is most stable than blueangel i mean:

-wi-fi

-Movies

-phone

-comfortable

-BT

-fast and stable rom

Anybady can tell something about this?
[MDA III, XDA III, PDA2k, 9090 General] Towserspvm2000:
Double post
[MDA III, XDA III, PDA2k, 9090 General] Towserspvm2000:
Hi,

I had a Blue Angel (Orange SPV m2000) for 2 years before switching contracts and getting a Tytn/Hermes (successor to the wizard). After getting used to the smaller screen, I thought the Hermes was great for the next 18 months, until I dug out my Blue Angel. I couldnt believe how much nicer and easier the 3.5 inch screen is to read and use without the stylus compared to the 2.8 inch screen of the hermes. But what really surprised me was how much quicker the blue angel was compared to the hermes, which seemed real sluggish in comparision. I have now just flashed the Blue angel to WM6, and it is awesome. I'll sacrifice the lack of 3g and size of the blue angel for all it's benefits!

Regards

PS - I could watch movies no problem on the Blue Angel in full screen. I couldnt on the Hermes as the play back was too choppy. It's even worse on my mates Kaiser!
[Samsung Galaxy S9+ Questions & Answers] nviz22:
I have the Snapdragon factory unlocked US model. 2nd day of owning the device. I notice the phone has touchscreen issues since it will not register my taps right away. Does that issue get solved in the March 2018 software patch update? Or would I need to just return my device? No deadzones and it passed the secret menu test multiple times.
[Samsung Galaxy S9+ Questions & Answers] eurosteve:
After 17 days of ownership (S9 plus) I had deadspots. After much effort to try to get a new replacement, Samsung offered warranty repair service, which would take 2 weeks. They suggested I might try a repair service in the Phoenix area called Ubreakifix. I brought the phone to them, they transferred the repair ticket to them and they repaired it in 3 hours. It's as good as new now (hopefully).

Ubreakifix confirmed that the touchscreen was defective. Definitely not a software issue.

I'm surprised that I'm not seeing more postings about this problem...
[Samsung Galaxy S9+ Questions & Answers] nviz22:
I am not getting dead spots like others, but my screen requires multiple touches to get stuff work. Is it true once you replace the screen, the phone's water resistance may not be as trust worthy?
[Samsung Galaxy S9+ Questions & Answers] midmadn:
My touchscreen is driving me insane. No deadspots but if my finger slides even the slightest bit when I tap the screen - it doesn't register. I have bad arthritis which must be aggravating the situation. I've tried everything I can think of with no help. I also have a new samsung tablet I have to use at work that behaves exactly the same way.
[Samsung Galaxy S9+ Questions & Answers] zathus:
Out of curiosity do any of you have dry hands? Or very calloused fingers? I've experienced touch issues but on multiple devices and it seems more prevalent when my hands are dried out. When I moisturize them I get much better response from the touch screen
[Samsung Galaxy S9+ Questions & Answers] nviz22:
Some say it is a software issue and the Exynos patch solved it. I hope this is the case with the unlocked USA Snapdragon model once the patch comes out. I only have about 2 weeks to decide if I want to keep the device.
[Samsung Galaxy S9+ Questions & Answers] midmadn:
I just updated the Tab-E and it still does it. Not sure how old the update was though as it's a new tablet to me.
[Samsung Galaxy S9+ Questions & Answers] nviz22:
Haven't used a Samsung tablet in ages. I own an iPad myself, so I stay away from Android tablets. I only like Android phones haha. I have 14 days left to return the device, so the ball is in Samsung's court.
[Samsung Galaxy Note 8 Questions and Answers] JamFarhan:
I can not send sms over 4g network with 4 bars, this happens most of the time and i also receive repeated messages upto 5 6 times, also mobile data works sometimes on 4g while on 3g internet works fine and i can send messages without any delays.
[Samsung Galaxy Note 8 Questions and Answers] gpap2004:
This happened to me , too. But not always and not to all numbers!
[Samsung Galaxy Note 8 Questions and Answers] winol:
The problem may be carrier related, same thing ocurred in my zone, the service provider was making some changes when implementing 4.5G LTE
[Samsung Galaxy Note 8 Questions and Answers] poison_snake:
Do you have advanced messages turn on? Turn it off and try