You are paniqued over unknown asumptions. Read this https://switchchargers.com/faq/
Switchroot devs are well concerned about how charging works on this unofficial version of android 10.
On the battery discussion, there's a little bit to the person's concerns, though overall they're misunderstanding a lot of stuff. Android systems do indeed intentionally fast charge batteries by choice and this isn't actually as ideal as it seems. No this won't destroy the battery and no Nintendo doesn't have any proprietary charging methodologies or etc, but they might intentionally be limiting the charge rate to maximize battery lifetime and this is a very real thing if so. Phone/tablet users as a whole want fast charging no matter what, fully with the intent to replace their devices every few years at the latest anyway, but when you buy a console like the Switch you typically want it to last a long time (plus you know how Nintendo tends to build their stuff to high tolerances -- even if they have been slipping a lot lately.) Fast charging is indeed more stressful to the battery, but no it won't damage or break it, it merely decreases its useful lifetime slightly. I do want to add that it's not just charge rate that matters, but temperature and voltage as well (which are, in fact, more important.) Of course a higher charge rate tends to produce a higher battery temperature. Obviously Nintendo has elected to at least choose to limit the charge rate. (And it's worth noting that even in the stock OS at the slow rate the battery does get a bit warm, so I'm guessing they really had to strike a balance here.) That, or maybe they were just lazy and simply didn't integrate fast charging into the system. (The lower charge rate is absolutely necessary when running at 5V since that already pushes around 3 amps from the power source, so perhaps they were just too lazy to make it decide smartly to use more current when it gets a higher voltage than that.) Obviously they didn't choose to limit the charging voltage (most people would hate that.)
It's not even a huge difference at first, but it's all the difference between a 2017 phone that is having a pitiful battery life and a Nintendo Switch from 2017 still having a fairly useful lifetime even if not exactly great (not that it ever was great.) Both are reduced from when they were new, but the phone is significantly more so (and let me tell you that games murder the phone's battery, but then Android gaming always did suck anyway.) I do think it has legitimately helped with my phone as its battery life is still pretty decent despite everything.
I do think that ALL Android distributions should actually take this into consideration more and give the user a bit more of an option as to which they prefer. Fast charging is great for the on-the-go user's lifestyle where one needs to charge that phone quickly and get going again and intends to toss it in the trash and buy the latest thing to hit the shelves in a couple of years anyway. But some of us don't tend so much this direction and a slow charge with a longer lasting battery is actually more suitable for us who feel this way. I've actually seen a bit of an inkling of this sort of idea in SONY's stock ROMs which was nice to see at least -- at least someone out there has had the idea. I really think this is something that should be ultimately up to the user as the choice is significant and affects how the hardware will be used.
To some extent the "acc" module (available for Magisk or I think can be manually installed on fully rooted writable systems) attempts to correct this for those of us who want to increase the overall lifetimes of our batteries. I find this particularly necessary on my phone because it *is* a 2017 phone ironically and never had a great battery (it's a cheap economy model) so the last thing it needs is for that battery to wear out. However, I've also found out the hard way that acc is pretty limited in what it can do depending on the system itself (and to that end I think the issue comes down to the OS more than anything. Which is LineageOS on my phone too.) In many cases it can even limit charge rate (albeit in a bit of a hacky way on some,) but in mine it won't. It can limit maximum charge percentage (which, voltage-wise, seems to work out to 92% being optimal on mine) but then it stops charging until the next reboot on that phone. I haven't had the chance to try it on the Switch yet, but my suspicion is I'll see similar poor support. At best a maximum percentage limit, not a rate limit would be my guess. (I do intend to try it soon though. My classic stays docked 99% of the time anyway, so a maximum charge limit would not be the worst thing in the world.) Ultimately the only real solution is that the OS itself -- which can handle this stuff at a much lower level than rooted/Magisk/etc software can do -- to allow the user to decide. If it had proper low level control it would be quite easy to limit charge voltage and current and there is definitely a notable benefit to doing so and this ultimately should be the OS's job IMO.
So, coming back to the ongoing discussion, this is more a matter to take up with the LineageOS developers themselves. And I have no clue how you'd even get in touch with them as I never even got really simple stuff like the volume steps fix to even reach their attention (and all that is is a simple change of some numbers in one single source file that would take mere seconds to do. It's worth noting that Google has ignored users trying to bring that one to their attention since the Android 2.x days, so I guess some things just get auto ignored. BTW, given its strong media focus maybe it wouldn't be the worst thing in the world if the Switch port had more volume steps hint hint.) Giving the user optional control over battery charging (preferably both rate and max voltage) is significantly more work to say the very least. Still, they are the ones to talk to about this, not the Switch port's developers. Such a thing needs to be integrated into the base system and then that would make it over to the Switch by default anyway. So to be clear, this is definitely not a Switch-specific matter and there are advantages and disadvantages both ways with Nintendo's choice likely making more sense for normal Switch use (but then a fast charge could be handy if you're about to head out the door and want to just charge it real fast. Thus it should definitely be a choice.) Feel free to see if you can have more luck catching their attention.
You use the TvBox version or the Tablet one?, because i cant run prime video on the TvBox version, but i found an custom apk for the netflix app on TvBox tooIt looks like netflix doesn't want to work, i downloaded the release netflix tell you to download when you get the "device not supported" error but i still get it anyway. I also tried to change the device fingerprint to pass the safetynet checks but no dice (as in i pass the checks now but netflix still doesn't work).
Every other streaming service seems to work fine, prime video and disney+ included.
i have the same problem! just trailers in "prime video" working but the content only says "something went wrong please try again later", helpDoes someone have an working apk or an method to run prime video on the TvBox version?, i already tried with magisk and it didnt work :c
atv doesn't support prime or netflix apps, you could try the tablet apksi have the same problem! just trailers in "prime video" working but the content only says "something went wrong please try again later", help
If you use magisk, i think that error come with it. i had the same probleme, i have installed the update via twrp.Hi I get an error after trying to update Lineage via OTA(13/02/2021). Does anyone knows how to solve this? Do I have to install the update manually? Thanks.
When the switch is docked, the audio and video feed is surely switched to hdmi. I think the easiest way is to use a hub with hdmi and jack output, compatible with switch.Hello, my TV doesn't have a sound output, so I have to use my wired earphone through the jack.
When I dock my switchroot to play on TV, the sound in the earphone instantly stop working, do you have any idea why ? I can't manage to have sound when docked as my TV doesn't have sound output.
It's strange, in Horizon my wired earphone is still working when docked on the TVWhen the switch is docked, the audio and video feed is surely switched to hdmi. I think the easiest way is to use a hub with hdmi and jack output, compatible with switch.
I have this same issue too.After applying OTA 12/02/2021, the other grip controller becomes unresponsive when the HORI grip controller is reconnected.
05/02/2021 build confirmed that this is not happening, so I am unable to update to 12/02/2021.
Will be fixed in next OTAruns great games run great emulators runs great but my bluethoot headphones cut in and out the audio for some reazon maybe a bug anyone having the same problem? apart from that android is running great
Running great except "Bluetooth" keeps crashing multiple times after starting up the system.
But Bluetooth works afterwards.
Is this a known issue?
thx
Will be fixed in next OTA
Thanks, does it only crash after sleep?I was able to get some logs concerning my broken Wifi. Below is a logcat of me tapping on the wifi icon in the notification dropdown. There's some errors and I hope it helps getting to the bottom of the problem.
Code:=u:r:magisk_client:s0:c84,c256,c512,c768 tcontext=u:r:hal_graphics_allocator_default:s0 tclass=fd permissive=1 app=com.android.terminal 02-08 20:40:39.375 6777 6777 I su : type=1400 audit(0.0:714): avc: denied { read } for name="audio.primary.tegra.so" dev="mmcblk0p3" ino=536 scontext=u:r:magisk_client:s0:c84,c256,c512,c768 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=1 app=com.android.terminal 02-08 20:40:39.375 6777 6777 I su : type=1400 audit(0.0:715): avc: denied { getattr } for path="/vendor/lib/hw/audio.primary.tegra.so" dev="mmcblk0p3" ino=536 scontext=u:r:magisk_client:s0:c84,c256,c512,c768 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=1 app=com.android.terminal 02-08 20:40:39.375 6777 6777 I su : type=1400 audit(0.0:716): avc: denied { read } for name="bin" dev="mmcblk0p3" ino=26 scontext=u:r:magisk_client:s0:c84,c256,c512,c768 tcontext=u:object_r:vendor_file:s0 tclass=dir permissive=1 app=com.android.terminal 02-08 20:40:39.727 6781 6781 D AndroidRuntime: >>>>>> START com.android.internal.os.RuntimeInit uid 0 <<<<<< 02-08 20:40:39.733 6781 6781 I AndroidRuntime: Using default boot image 02-08 20:40:39.734 6781 6781 I AndroidRuntime: Leaving lock profiling enabled 02-08 20:40:39.739 6781 6781 I /system/bin/app_process: Core platform API reporting enabled, enforcing=false 02-08 20:40:39.888 6781 6781 D ICU : Time zone APEX file found: /apex/com.android.tzdata/etc/icu/icu_tzdata.dat 02-08 20:40:39.906 6781 6781 I /system/bin/app_process: The ClassLoaderContext is a special shared library. 02-08 20:40:39.930 6781 6781 W /system/bin/app_process: JNI RegisterNativeMethods: attempt to register 0 native methods for android.media.AudioAttributes 02-08 20:40:39.938 6781 6781 D AndroidRuntime: Calling main entry com.android.commands.content.Content 02-08 20:40:39.957 6781 6781 D AndroidRuntime: Shutting down VM 02-08 20:40:39.967 6574 6574 I RenderThread: type=1400 audit(0.0:717): avc: denied { call } for scontext=u:r:untrusted_app_27:s0:c129,c256,c512,c768 tcontext=u:r:hal_cplservice_default:s0 tclass=binder permissive=1 app=com.topjohnwu.magisk 02-08 20:40:39.971 6574 6574 I RenderThread: type=1400 audit(0.0:718): avc: denied { call } for scontext=u:r:untrusted_app_27:s0:c129,c256,c512,c768 tcontext=u:r:hal_cplservice_default:s0 tclass=binder permissive=1 app=com.topjohnwu.magisk 02-08 20:40:41.115 3376 3376 I InputReader: type=1400 audit(0.0:719): avc: denied { call } for scontext=u:r:system_server:s0 tcontext=u:r:init:s0 tclass=binder permissive=1 02-08 20:40:41.972 3376 3911 W NotificationService: Toast already killed. pkg=com.topjohnwu.magisk callback=android.app.ITransientNotification$Stub$Proxy@f6bb064 02-08 20:40:43.435 3149 3149 I storaged: type=1400 audit(0.0:720): avc: denied { call } for scontext=u:r:storaged:s0 tcontext=u:r:init:s0 tclass=binder permissive=1 02-08 20:40:43.463 3376 3398 W WindowManager: Unable to start animation, surface is null or no children. 02-08 20:40:52.965 3376 3376 W WindowManager: removeWindowToken: Attempted to remove non-existing token: android.os.Binder@3f976a3 02-08 20:41:00.002 3586 3586 D KeyguardClockSwitch: Updating clock: 20:41 02-08 20:41:08.115 3376 3412 E LightsService: Light requested not available on this device. 2 02-08 20:41:08.117 3376 3470 E LightsService: Light requested not available on this device. 2 02-08 20:41:46.319 3586 3586 D StatusBar: disable<e i a s b h r c s > disable2<q i n > 02-08 20:41:46.363 3519 3538 D RSMouse : mFeatureEnabled=true mPackageEnabled=true 02-08 20:41:48.149 3376 4233 I WifiService: setWifiEnabled package=com.android.systemui uid=10097 enable=true 02-08 20:41:48.149 3376 3485 D WifiController: StaEnabledState.enter() 02-08 20:41:48.149 3376 3486 D WifiActiveModeWarden: received a message in WifiDisabledState: { when=0 what=0 target=com.android.internal.util.StateMachine$SmHandler } 02-08 20:41:48.149 3376 3486 D WifiActiveModeWarden: Switching from WifiDisabledState to ClientMode 02-08 20:41:48.149 3376 3486 D WifiActiveModeWarden: Entering ClientModeActiveState 02-08 20:41:48.150 3376 3486 D WifiClientModeManager: entering IdleState 02-08 20:41:48.150 3376 3486 D WifiActiveModeWarden: State changed from client mode. state = 2 02-08 20:41:48.151 3376 3376 D WifiP2pService: Wifi enabled=false, P2P Interface availability=true 02-08 20:41:48.151 3376 3486 I WifiVendorHal: Vendor Hal started successfully 02-08 20:41:48.153 3376 3486 I SupplicantStaIfaceHal: Starting supplicant using HIDL 02-08 20:41:48.154 3376 3487 I WifiP2pNative: Registering for interface available listener 02-08 20:41:48.156 3376 3486 I android_os_HwBinder: HwBinder: Starting thread pool for getting: android.hardware.wifi.supplicant@1.0::ISupplicant/default 02-08 20:41:48.156 3376 3486 E SupplicantStaIfaceHal: Death handler already present 02-08 20:41:48.161 3068 3068 E android.hardware.wifi@1.0-service: Failed to open wlan fw path param: No such file or directory 02-08 20:41:48.155 3068 3068 I wifi@1.0-servic: type=1400 audit(0.0:721): avc: denied { read } for name="fw_path" dev="mmcblk0p10" ino=784924 scontext=u:r:hal_wifi_default:s0 tcontext=u:object_r:wifi_vendor_data_file:s0 tclass=lnk_file permissive=1 02-08 20:41:48.161 3068 3068 E android.hardware.wifi@1.0-service: Failed to change firmware mode 02-08 20:41:48.161 3376 3486 D HalDevMgr: updateRttController: no one is interested in RTT controllers 02-08 20:41:48.161 3376 3486 E HalDevMgr: executeChipReconfiguration: configureChip error: 9 () 02-08 20:41:48.161 3376 3486 E WifiVendorHal: Failed to create STA iface 02-08 20:41:48.161 3376 3486 E WifiNative: Failed to create STA iface in vendor HAL 02-08 20:41:48.161 3376 3486 E WifiClientModeManager: Failed to create ClientInterface. Sit in Idle 02-08 20:41:48.161 3376 3486 D WifiActiveModeWarden: State changed from client mode. state = 4 02-08 20:41:48.161 3376 3486 D WifiClientModeManager: expected stop, not triggering callbacks: newState = 1 02-08 20:41:48.161 3376 3486 E WifiNative: Could not get Iface object for interface null 02-08 20:41:48.162 3376 3376 D WifiP2pService: Wifi enabled=false, P2P Interface availability=true 02-08 20:41:48.162 3376 3486 D WifiActiveModeWarden: ClientMode failed, return to WifiDisabledState. 02-08 20:41:48.162 3376 3486 D WifiController: ClientMode unexpected failure: state unknown 02-08 20:41:48.162 3376 3486 D WifiClientModeManager: currentstate: IdleState 02-08 20:41:48.162 3376 3486 D WifiScanRequestProxy: Sending scan available broadcast: false 02-08 20:41:48.162 3376 3489 I WifiScanningService: wifi driver unloaded 02-08 20:41:48.163 3376 3486 I WifiScanRequestProxy: Scanning is disabled 02-08 20:41:48.164 3376 3409 D KernelCpuUidUserSysTimeReader: Removing uids 1037-1037 02-08 20:41:48.165 3376 3486 D WifiActiveModeWarden: Entering WifiDisabledState 02-08 20:41:48.166 3376 3486 D WifiActiveModeWarden: received a message in WifiDisabledState: { when=-3ms what=3 target=com.android.internal.util.StateMachine$SmHandler } 02-08 20:41:48.166 3376 3486 D WifiActiveModeWarden: Switching from WifiDisabledState to WifiDisabled 02-08 20:41:48.166 3376 3486 D WifiActiveModeWarden: Entering WifiDisabledState 02-08 20:41:48.166 3376 3486 E WifiNative: Could not get Iface object for interface null 02-08 20:41:48.169 4206 4782 W Settings: Setting airplane_mode_on has moved from android.provider.Settings.System to android.provider.Settings.Global, returning read-only value. 02-08 20:41:49.891 3069 3069 I joycond : type=1400 audit(0.0:722): avc: denied { read } for scontext=u:r:init:s0 tcontext=u:r:init:s0 tclass=netlink_kobject_uevent_socket permissive=1
EDIT:
I also grabbed admesg
which I have uploaded to my server since it's too large to attach here
Grepping for "wifi"/"wlan" yields a whole lot of errors, for example:
service "vendor.wifiloader" exited with status 255
Naturally, wifi works just fine in Horizon, just in case you suspect faulty hardware
Reboot and hold vol-
Should be fixed in OTAFor me the sleep mode is not working. Battery draining really fast. Anyone with the same problem?
Should be fixed in OTAToday my Lp0 didn't work. I use CPU spy to observe this. This happened after a reboot.
My switch stayed on with 100mhz all the time but screen was off.
I turned wifi and bt on and off. This helped. Afterwards my switch went into deep sleep again and stayed there as long as the screen was off.
Maybe this helps.
anyone get safetynet to pass?
I flashed it and gapps and tested safety net and it failed. Wasn't sure if there was something I missed