I'm receiving this error after enabling ultra power saving mode: > "Unfortunately, Launcher has stopped." Its dialog only has the option "OK". Restarting doesn't work. Clearing cache partition through recovery doesn't work. I can access settings by pulling down from the top of the screen but the settings menu is not complete; It only has Wi-Fi, Bluetooth, Airplane mode, Mobile networks, Location, Sound and Display entries. My device is not rooted. It seems that the device is still on ultra power saving mode, even after clearing cache. I have the option to factory reset through recovery but I prefer not loosing my data, if it's possible. What can I do?

Samsung Galaxy Note 4 (Verizon SM-N910V), Android 6.0.1. After a sudden reboot, my phone is now displaying a new notification. > The weird header alignment and a few typos ['Samsungs'; 'MMC(Mobile Country Code)'] put me ill at ease, and Googling this service from Samsung doesn't turn anything up. Also, after this reboot a few details are off: - The lock screen background changed to one of the Android defaults (I had a plain black background) - The font reverted to the default size (I had it set to small) - The settings buttons (screen rotation, data, etc.) in the pulldown menu changed order - The interface seems more responsive What does this mean? I shut off the device and am going to talk to Verizon, but I'm hoping people here might have some ideas. My phone occasionally reboots for no reason (every couple of weeks), but I am not sure this is related. I haven't seen these symptoms before and Googling didn't turn up anything quickly.

I bought one Galaxy Note 4 on Amazon. I used it in Europe with no problems. Few months are passed and now I moved to China for a while. Well, I can't use my phone here because it is Network Locked (asks for a code at the splash screen). Nothing when I bought it let me suppose this phone was locked to some network, nor I can find any information inside the phone (or the box, or some appearing logo) suggesting to which network it is locked. I am aware there are many service to unlock a phone, but I can't even step up the process of unlocking since I have no idea which network my phone is locked to. My questions: 1) how to know which network carrier I'm locked on? I got some information on the *#0011# menu, but nothing useful, also in about of the phone no hints. 2) Are this unlock services reliable? Thanks for your help.

I got a problem with my Samsung device and now I've no idea how to fix this, hope anyone want to help me in fixing this problem. So this thing started yesterday when I just went in to Recovery Mode to "Wipe Partition Cache" and turn my phone off. 1)When I tried turning my phone on, it doesn't go to normal boot but it go to "recovery boot" I dont't know why, restarted, unplugged the battery and turned on my phone again but it won't make my phone get out from recovery boot. 2)Now I'm trying to flash my phone with Odin, when I tried to flash it says **"There is no PIT partition"**, **"There is no PIT Binary",** ***how to fix this ?*** I've tried to download and used the pit file but it didn't worked. please help

I'm trying to install multiple .apk files to my Samsung Note 4, over adb. I'm able to install the same set of files individually using the 'install' command, but when I try to 'install-multiple' I get the following error: adb: failed to finalize session Failure [INSTALL_FAILED_INVALID_APK: Split null was defined multiple times] All my own research on the error turns up issues relating to development, but nothing relating to simply installing some .apks. The actual files do not have any spaces or special characters in their names. When I run the command with tracing enabled, you can see that the command that is actually being executed after expansion is syntactically correct. adb install-multiple /tmp/update_phone/* + adb install-multiple /tmp/update_phone/firefox.apk /tmp/update_phone/protonmail.apk /tmp/update_phone/protonvpn.apk /tmp/update_phone/whatsapp.apk Any advice would be heartily appreciated! Ubuntu 20.04 | adb version 1.0.39 | Samsung Galaxy Note 4 | Lineage OS 17.1

I tried to transfer files (of extension PPT, DOC, MP4 and so on) from my Samsung Galaxy Note 4 to my laptop (Windows 10; tried on two laptops from Dell and Lenovo). Once I plug the USB cable I can see both device storage and card storage and I can sometimes (let's say 1 out of 3) browse the folder. When I try to copy the file from that mobile folder into my laptop mobile, it works 1 out of 10 times! Most of the time explorer freezes or it starts to browse the folder (i.e. the path bar is progressing but never ends). I installed USB drivers on my laptop. I even installed Kies but then Kies itself launches explorer and loops. Please do not tell me to use Wi-Fi as I am in a hotel with very poor connection and I am using my 4G phone to actually download files and then (I thought that would be easy) I was thinking to transfer those files to my laptop through USB cable. Actually, what is working is: I plug the cable, I go into the folder and select the file. Then I unplug the cable but I keep the explorer opened. Then I plug again and at that time I right-click, copy the selected file and then I am able to paste it in a laptop folder. Yes, that is working. But I would not do that for all the files I need to transfer. There should be a simple way, right?

I made a post about this yesterday, and I managed to make a lot of progress today, but I'm stuck again, and I am trying to decide what to do. I am not really experienced with coding, but I happen to be very good at teaching myself how to do something when needed and also very bad at giving up. Below is a summary of my progress thus far: **INITIAL PLAN** 1. Install Android SDK, drivers to PC (Win7, 64 bit) 2. Root phone (used CF-Auto-Root) 3. Patch adbd to allow root permissions (installed adbd insecure and SuperSU) 4. Access /data/userdata 5. Get image of /userdata, attempt to find files I am stuck at step 3. I have adbd insecure and SuperSU, but using either of these causes USB debugging to be disabled. Regardless of how I toggle things, I lose my connection to my PC and cannot enable USB debugging. Some research uncovered that there's something called SELinux that is preventing me from enabling USB debugging while adbd insecure is enabled (patched adbd). There are posts in the adbd insecure thread on the XDA forums from other people (check the last page) describing a similar problem: https://forum.xda-developers.com/showthread.php?t=1687590 And one post at the end explaining that they fixed it with an app called SELinux Switch: https://forum.xda-developers.com/showpost.php?p=79689054&postcount=267 SELinux Switch would allow me to turn off the protection preventing adbd insecure from working. Can I get some feedback about this? I'm not enjoying this stuff, and I really need to get back to other endeavors, so it'd be a one-time use, and then I will probably uninstall it from my phone because I won't need it. **ALTERNATIVE PLANS** I also have two alternative "paths" I could take to attempt to recover the deleted photos. I'd rather not do that right now, because I don't think I have time, and because I am trying to avoid anything that would overwrite the deleted photos, but they exist nonetheless: Alternative 1: Droidexplorer and busybox I already have droidexplorer installed on my PC and my phone is rooted, so I guess I could install busybox and see if droidexplorer can recover the deleted photos. Alternative 2: Magisk with/without busybox I would rather not do this, because it sounds like it would take the most time and more monkeying around with internal storage, but apparently adbd insecure isn't an active project anymore and most people use magisk for rooting, etc. This is an alternative, but it's the least attractive option. What do people think? For now I am going to try the SELinux switch, since it seems the simplest way. If people could please try to avoid using too much jargon and explain commands, etc. it would really help out; that way I wouldn't need to look up unfamiliar terms first.

I'm guessing it's called boot loop from research over the past few hours. I switch it on, it loads the logo and phone introduction screen, the screen goes dark, it resets and then repeats. Charges fine, works without charger. I've tried lots from Google results like take out battery, soft and hard reset, recovery boot screen: clear cache, factory reset. I've even tried installing TWRP and rooting via odin which was successful, computer recognised it via USB. I then tried installing a custom ROM and gapps which was also successful but still have boot loop issue. Possible water damage, if so what part will be faulty?

i tried to flash the latest firmware, but after i press the start button,it says PIT partition error,so i installed a PIT partition for note 4 and then tried,still it says PIT partition error.....can ypu help mewith it?

*Alternatively*, can android force an app to use Cellular data? **The app in question:** Amazon Video [Version 3.0.57.30110 "Prime Video for Android Software"] **Device in use:**Samsung Galaxy Note 4 - Android Version: 5.0.1 Build LRX22C.N910TUVU1COG2 (USA TMobile Completely Stock, No Root etc) **Issue:** AV doesn't allow 'download for offline viewing' of media larger than 50mb in size. The app wants to see the device is connected to a WiFi network to allow downloads. **Why this is an issue:** When travelling, I use my unlimited network to download media for offline use when leaving network coverage areas (wilderness, trains/planes etc) - with an unlimited cellular plan, I don't care about what size file I'm downloading; Amazon is undoubtedly attempting to help users from inadvertently maxing out their data plans and blaming Amazon in the process (yes, those users exist)... Interestingly, a cellular hotspot will allow download - as the app see's the device as being on a WiFi Network. **Restating the Question:** Is there a way to either, force the app into using cellular data, or, spoof the phone's wifi state as 'on' but use cellular data anyway? Research: Reading other threads, this problem is unique in the sense that wifi is not an option to use - assume i only have cellular data; how can i use apps that request wifi for their functions?

I'm trying to install **TWRP** ("openrecovery-twrp-2.8.1.1-trltetmo.img.tar") on Samsung Galaxy **Note 4 SM-N910F** with Android 5.1.1 . I tried to do it with **Odin** versions v3.09 and v3.10.7 using different USB cables and ports. The process always seems correct: it shows '*ID:COM*' and finishes without errors, showing **green** and ends up resetting the device, but after that I try to boot into '*Download mode*' and after pressing "*volume down*" + *Home* + *Power* it keeps showing the **default recovery**, it doesn't boot on TWRP. I've uploaded here five screenshots showing what's happening. Here's one of them, showing that apparently everything has worked fine and the device is beeing rebooted: PC configuration: - Windows 7 - Already installed Drivers "*SAMSUNG_USB_Driver_for_Mobile_Phones.zip*" from here Device configuration: - '*USB debugging*' is enabled - Security => '*Reactivation lock*' is disabled. How can I install and boot correctly TWRP? Any help will be appreciated, thanks in advance /Angel

I am getting 2 notifications for the same email, both from the Gmail app. One notification is for the Inbox and the other is for a custom Label. I do not want two notifications for the same email, so how do I prevent an Inbox notification if a label notification is triggered? If I disable the Inbox notification, I will not be notified when a new email arrives. If I disable the Label notification, I will not hear the sound that is set to that label. A couple more things to note... - Some suggest moving the label emails away from the Inbox will solve it, which is true, but I need the label emails to show in my Inbox because I need to action them. - I have the Inbox sound notification disabled because it clashes with the label notification sound (separate issue, but same cause). Using Gmail v5.0.1 on Galaxy Note 4. Thanks.

Is there a way to recover the internal storage (images, video, photos, notes, app data, music, etc) of an Android phone which is *currently* **in a bootloop**? Additional info: 1. Wiping the cache partition in recovery mode does not solve the bootloop issue. 2. The phone is not rooted. 3. USB debugging (hopefully) has been enabled prior to the soft-bricking. 4. The bootloop occurred after the battery run out of power. 5. The phone is SAMSUNG Galaxy Note 4

I just got a refurbished Samsung Galaxy Note 4 to replace a dead Note II. When compared with the Note II, it is giving me terrible audio quality for voice recordings done with headset mics — there is a severe high-frequency roll‑off that leaves the recording sounding muffled. I initially discovered this when using the headset that came with the Note II. I have a homemade windscreen rigged up on it, so I wanted to keep using it rather than trying to transfer that to the headset that came with the Note 4. So, the exact same microphone and windscreen, using the stock Voice Recorder app on both phones, neither rooted, in high quality mode in both cases (recording MPEG-4 audio), and the difference is night and day when listening to existing recordings done on the Note II vs. tests on the Note 4. The recordings from the Note II certainly donʼt sound like a studio condenser mic (like in the appʼs graphic, lol), but theyʼre of reasonable quality, more than adequate for speech. High frequency detail is there; I can hear leaves rustling very crisply, and sibilants in speech are clear and distinct. The recordings from the Note 4, by contrast, sound muffled. Sibilants are muted and somewhat indistinct. It sounds like it was put through a low‑pass filter. Speech is still basically intelligible, but the gap in quality could well make the difference between making out certain words or not under less ideal conditions. The overall signal level in the Note 4 recordings is also noticeably lower. I have to turn up those recordings more than the Note II recordings to compare them equally. (Iʼm wondering if that and the fidelity problem may be related — the MPEG codec might throw out very quiet high-frequency data by design.) I should note that in the Note 4 the “Recording volume” setting is set to “High” (thereʼs only that and “Low”). Iʼm listening to both files on a PC with VLC media player, through a home hi‑fi system with proper speakers — not some cheezy self-powered made‑for‑computers garbage. VLC is showing the recordings from both phones to have a content bitrate around 128kb/s, so I donʼt think itʼs a matter of bandwidth loss from more aggressive data compression. I figured maybe the electrical parameters of the headset had changed between the two models, and so also did a test with the headset that came with the Note 4. It was maybe very slightly better due to the lack of the windscreen, but basically still horribly muffled — low signal level and significant loss of high frequency response. I should note that this is _not_ a problem with the Note 4ʼs internal mics. When I unplug the headset and record with the internal mic, the recording is much louder and has decent frequency response. Possible explanations I can think of: * There has been a significant regression in the quality of the preamp or ADC circuitry for the external mic from the Note II to the Note 4. * My particular Note 4 has a problem in the audio connector that is introducing extra resistance. I have tried cleaning it with a cotton swab and isopropanol, and the issue remained. * My particular Note 4 has a damaged mic preamp or ADC circuit. * There is a system setting buried somewhere that I need to change, other than the obvious settings in Voice Recorder, which are already set to their highest levels. * There is a bug in the Note 4ʼs firmware. * There is a bug in the Note 4ʼs Voice Recorder app, but this seems unlikely, as I expect it just encodes whatever audio the OS gives it. Any ideas which of these might be happening? If this is a problem in the model itself, surely someone else has encountered this long ago. The exact model is SM-N910W8 running Android 6.0.1, kernel 3.10.40-8000148. **UPDATE:** I did testing with a 3rd party app that can record raw PCM into a RIFF (WAV) file, and the same muffled sound was there, so itʼs not the fault of the stock recording app or data compression. Robertʼs suggestion led me to figure out that the ADC for the headset input is in a Qualcomm WCD9330 chip. I also discovered from schematics I was able to dig up that the _internal_ mics are digital mics (the ADC is built into the mic), so the WCD9330ʼs ADCs are not being used for those. I also checked out the engineering specs for a couple similar chips in the same line (Qualcomm doesnʼt seem to have published specs for that exact device), and nothing there suggested that the frequency response should be anywhere near so poor unless the firmware has drastically misconfigured the chip. I _did_ find a reference, on XDA Developers [here](https://forum.xda-developers.com/tab-s2/orig-development/rom-lineageos-15-1-t3732074/page10) , regarding a totally different device, the Samsung Galaxy Tab S2 8.0 LTE, that uses the same chip and has muffled audio input caused by a firmware issue. In that case, a custom ROM was causing the issue, and the stock ROM worked fine. In my case, itʼs using the stock ROM (AFAIK!), but perhaps in this case the stock ROM is at fault. I did some testing and found, somewhat surprisingly, that the frequency response is actually full hi‑fi with the exception of a two-octave 10dB notch at around 8kHz. This dip at 8kHz is very consistent with what the recordings are doing to speech. Given that the response is consistent with a notch filter, it now looks like the behaviour is probably half‑ways _intentional_, which was a bit mystifying. I decided to put up [this](https://electronics.stackexchange.com/questions/450492/why-an-8khz-notch-on-the-headset-mic-input-of-a-qualcomm-wcd9330) question on the Electrical Engineering SE, to see if there might be a plausible engineering explanation. The result of that discussion is that it would be normal, due to sampling rates used in telephony, to knock out frequencies above 4kHz in order to avoid transmitting severe aliasing artefacts to the remote party. That filter _should_ get turned off when an app asks for PCM data at a higher sampling rate, but the electronics allows independent control over the filtering, so itʼs quite plausible that the firmware in this particular model, when disabling the filter for audio recording, forgets to disable it on the external mic input. So far I have not found a confirmation of this as a known issue of this model, but it seems like the most likely explanation. On a firmware/software level, Android devices are basically a black box to me, so I have no idea where in the software stack this issue would be most likely to be, whether this might be fixed by a custom ROM, or by some utility that runs rooted, or what. Another dimension to the problem is the very low input volume level. I had originally thought that was related, though it now seems more likely it may be a separate issue. I did find the following suspicious lines in mixer_paths.xml: There are a number of other places there and in mixer_paths_i2s.xml (I2S is Inter‑IC Sound, a hardware bus used by the WCD93xx) that also set a similarly low number for the volume for ADC2. I say this is suspicious because from what I understand, the integer setting here is in 1dB increments with 84 being 0dB. This would suggest that ADC2 is being set to -70dB — a _remarkably_ low level! However, ADC2 is a hardware port whereas DEC5 is I think some kind of software mixing channel, so without much more intimate knowledge of Androidʼs audio hardware abstraction scheme, I canʼt be sure that the numbers for ADC2 are interpreted in the same way. To make matters more confusing, there are two identical copies of this file, one in /etc and one in /system/etc. Also, the mixer_paths_wcd9330.xml file, mentioned for the Galaxy Tab S2, does not occur in either of these locations. And there doesnʼt even seem to be a /system/vendor/etc directory on this phone. I canʼt edit this file to play around with it without rooting the phone, but Iʼm a little reluctant to do that, partly from having zero experience rooting phones, and also because if I _do_ discover a hardware issue, I donʼt want the store to be able to blame it on that. So Iʼd need to first be confident itʼs going to fix the problem.

My phone is a Samsung Galaxy Note 4 SM-N910G. I have absolutely no idea why it's stuck in a boot loop, and I can't even go to recovery mode by holding Vol Up + Home + Power. It was constantly restarting even when it showed a blue warning that it is going to boot on recovery mode. Then I flashed it with ODIN using a tar I downloaded. I'm a novice, so I just followed a guide on the internet. Now it says set warranty bit recovery? and still doesn't start on recovery mode or otherwise. Holding VOL Down + Home + Power always takes me to the download mode without an issue, and also the phone vibrates twice every time it reboots. Any help to recover the phone would be greatly appreciated. I wouldn't mind installing something like CyanogenMod if that's an option, or somehow factory reset the thing.

Can anyone please advise on how to activate a function that will allow me to view lock screen notifications when an email is received just as I can with missed calls and sms messages etc. The only way I become aware an email has been received is by noticing the addition of a status bar icon once the phone has been unlocked. If it helps I am currently using the stock email client and run with kitkat 4.4.4. To date I have tried all I can to find this facility but to no avail. Many thanks in advance.

So I want to basically redirect my phone's audio to my computer's playback device through USB and not through Bluetooth which is what most posts are seemingly concerned with. ---------- This guy https://android.stackexchange.com/questions/120326/streaming-audio-from-smartphone-to-pc-without-bluetooth asked a similar question about 2 years ago which hasn't really been answered so far so I thought I would bring it up again. ---------- Devices and Os's : Phone : Samsung Galaxy note 4 under Android 6.0.1 Pc : Windows 10 pro

I have an AT&T Samsung Note4 currently running Marshmallow 6.0.1. In the past it and all other Android phones used to prompt me for and app to open files or links with. The menu wold have a sellection of apps and 'Once' and 'Always' buttons. An app would only become default for a given link/file type by pressing 'Always'. Otherwise I would get prompted each time. Not too long ago this behavior changed. The 'Once' and 'Always' buttons are gone and apps automatically become default after the first choice. This is fine for some files/links but not others. There are many different kinds of things I want to do with some file types (eg pdfs) and I use different apps for each. Now I either have to unset the default each time or open the file in whatever the current default is and than 'share' it to the app I actually want. This is a pain and not all apps are equally good at sharing to other apps. **How can I get the old behaviour back?** Or at least select some file/link types to not have a default associated with them? I know how to unset default apps in settings; I am after a way to avoid needing to do that for files/links I open with multiple apps. I am not sure if this change is due to some update or if it is something I enabled unintentionally FWIW, I also have a Huawei running Android 4.4.4 that still has the old behavior --- This question is about the same problem in a specific context, but i am after a solution to the general problem that none of the commants & answers there address.

I click the home button to activate the phone. If I don't swipe within two seconds, it goes black and I have to hit Home again. This is frustrating when I want to just view the time and weather on the lock screen. It's almost enough time to view time and weather, but if I also want to see what date it is, then 2 seconds isn't enough time to view all three things and digest the information. So I find myself hitting the Home button 2 or three times. So I guess I might as well just swipe and activate the phone. But I really wanted to just set the screen to stay on a little longer. I set the display timeout to 10 minutes but this doesn't affect the lock screen. It still blinks off after 2 seconds. Is there any setting or something from a Tasker app or something, that can extend the time the lock screen will appear?

So yesterday I accidentally changed my phone's *(Samsung Galaxy Note 4 SM-N910C)* dpi from 640 to 140 using Nomone Resolution changer that uses root and that **screwed** up my whole phone because now it completely skips my lock screen background and straight to my home background but all it shows me is the background itself and a *tiny* error that says "System UI has stopped" and its literally the only thing there. I tried resetting my dpi using adb commands but the problem is that my laptop isn't authorized to my phone, I mean usb debugging is on (i think) but I don't think that will help because I have no access whatsoever inside of my phone and I don't have CWM recovery flashed so I have no clue what to do :'(( I saw this post that says i should try installing a custom launcher to fix the problem but like I said its no use trying to do anything because my laptop isn't authorized:( I seriously have no clue what to do and I really don't want to reset my phone because I have a lot of important files and pictures there, any suggestions? Thanks. ***Update***: So i managed to flash TWRP recovery but now i don't know what to do because I don't have a back up and i dont know the file that managed to change my dpi but at least i managed to progress somehow. What do i do next?