Sad to say goodbye... missing cast feature - LineageOS News & Discussion

I'm gonna go back to stock because it seems lineage is not going to get screen cast feature in my nexus 9 flounder. Already tried editing build.prop file... didn't work.
It's sad 'cause it's a really fast and well made rom, but it misses a critical feature for me.
Thanks for the great work!

I was having cast troubles with my Nexus 9 as well, but managed to resolve it. Here's what I did:
1) Dirty flash stock Gapps (I was on tiny).
2) Update my device to the latest LineageOS release.
3) Reset the Chromecast's WIFI setting.
After that full system casting started working again, though I did notice something weird - the system gets frozen for a few seconds after disconnecting, however it does come back and should I want to cast again - it still works.
Hope this helps anyone who comes across this thread.

Related

Dead NFC Sensor??

Hello all,
It appears my NFC sensor has quit working on my T-Mobile Galaxy S5. To provide some back story in hopes of finding a solution, here's what's going on:
A few days back, everything was running fine. I flashed an unofficial CM12 ROM (Albinoman887's) to my phone, which at the time had broken hotspot and no Netflix support. NFC worked for me at that point, as I used it to 'Tap n Go' when setting up my account to transfer everything to my S5 from my N7.
The next build that was released fixed Netflix for me, but since then I haven't been able to get any functionality out of NFC. According to the ROM developer, NFC works on his device, as it also does for several other T-Mobile S5 owners. I definitely believe that it works for them, but it's super frustrating to me that it won't for me -- even though I rarely use NFC. I'm just irritated at the thought that my sensor may have died and I have no idea why/how. The phone has never been dropped, so it shouldn't be shock damage.
It's also worth noting that I Odin'd back to my stock firmware, just to test NFC, and I couldn't get any NFC functions to work once I started fresh.
I'm not sure what my options are at this point, but I was hoping someone might have some input to help steer me in the right direction.
Quick update: I flashed a CM 11 ROM (Bliss Stalk, to be exact), and my NFC sensors now work like normal. I'm glad to see it's not dead, but I'm completely baffled as to why it doesn't work on CM 12, when the ROM developer is running the same device and it works for him.
Ahh, the perils of Android development. I'm still glad Lollipop is coming along so smoothly, and I apologize to @albinoman887 for being such a pain in his butt!

SM-N900W8 & CM11 M12 bugs and issues :(

I have a Canadian Note 3 (SM-N900W8), it's KNOX 0x0 rooted and I have CM11 M12 installed. I have been using only the M builds since I got this phone, I didn't even set up Touchwiz when I got it, I rooted and installed Cyanogenmod out of the box.
Now, with the new CM12 builds coming out, what happened to CM11, are they going to fix the remaining issues? Or did they just bail on legacy KitKat users because I'm having TONS of problems and I don't want lollipop, it runs like absolute crap for the nightlies right now and CM11 M12 isn't much better. Bluetooth takes a couple of attempts to connect, when it does my phone runs super slow to the point it force restarts. For instance, if I'm driving around, listening to music on the car stereo, pull over some where, find a new album on Google Music, start playing that, it's all good, do this a few times, every time I use my phone it gets slower and slower until it force restarts and then bluetooth has trouble connecting again. I've tried this on a few other vehicles of different brands and aftermarket stereos and it's the same result.
Audio is all funky when bluetooth is on too, it sounds like robots for the system sounds and if bluetooth drops while it's connected the music starts playing from the phone and sounds all roboty. I always do clean flashes too and the latest Paranoid Android GAPPS every time I reflash, the ROM is fine out of the box, works flawless for the first few days but after awhile, it becomes so bad I have to backup, wipe, reflash, and start over for another few weeks.
Another issue is somewhere between M8 and M12 one of the builds corrupted my SD card, I tossed in a second new card, it was corrupted again, FutureShop won't give me another one and said my phone is breaking them so I'm SD-less right now.
There are also quite a few apps that force close, but always at random, it's never when doing the same thing over and over, for instance, I can be scrolling through G+ and it tells me settings has stopped working, wasn't even using settings, didn't even have it open, haven't clicked it since booting my phone, just randomly stops working for no reason, this also happens all the time with the Camera, it says it just stops working when I haven't even used it and then if I try to use it, it says the camera is disconnected and won't work until I reboot.
I turn my phone off every night while it's charging and turn it back on every morning so every morning it gets a fresh restart, and I have to restart my phone probably 5ish times a day, if I'm using bluetooth more then normal then there's quite a few more unintentional reboots in there as well.
The last issue, which is a known issue is NFC not working, is there a fix for this yet? I kinda miss this feature and with how flawed CM11 is getting I don't know where to turn since they always seemed to be the most stable out of everything I've tried.
Any before anyone says Temasek's CM builds, I tried it, the final for CM11, it was worse then M12, it's exactly the same as M12, but every issue happens more frequently. Also, the pull down menu (when pulling down from the top right to show toggles), the bottoms of the last row was cut off so it didn't look very appealing either, it also used WAY more battery life, I usually get a full day out of one charge, so around 18 to 20ish hours on one charge, with temaseks cm11 I had to charge my phone half way through the day, sometimes my phone would just die on me without me knowing, the battery usage was always Android System.
A new problem that just happened lastnight was Google Keyboard was deleted and only the voice search would work, but "voice search can't be reached" so I couldn't search for another keyboard app from the playstore. I also used the stock GAPPS so AOSP keyboard is replaced with Google Keyboard, I had to reflash again this morning because I couldn't figure out the keyboard thing, there wasn't even a keyboard under languages in settings so I had no options to pick which keyboard to use. When I reflashes this morning I used the Modular GAPPS to it keeps the AOSP Keyboard just in case this happens again but I'm getting really tired of only having a reliable phone for a few weeks.
So, are there any fixes for these issues?
Bluetooth taking multiple attempts to connect
Bluetooth forcing random reboots
Bluetooth making audio from device all funky and sounds like a robot
Corrupting SD cards
Random system apps stopping without me even using or opening them
Google Keyboard vanishing
Are there any stable ROMs I could try for the HLTE? Maybe one that has working NFC? I'm almost thinking of going back to stock *throws up in mouth* but I don't know what else to do with how many bugs there are and Lollipop is only getting worse with the issues.
I'm also trying to avoid Lollipop because everything is white, Note 3 is an AMOLED display, each pixel illuminates on it's own so white screens use WAY more battery life then black ones which was a feature of Temasek's CM11 that I liked, had the option in settings to make everything black like the good old days.
So guys? Really out on my luck here, not sure what the next step is, any fixes for these problems? Any other ROM's I could try? Would flashing a new recovery and reflashing CM11 M12 fix some of these issues? I'm using Xiaoli CWM v6.0.4.7(20140125). Would the fact that KNOX isn't tripped have something to do with this? I really don't understand why there aren't more posts for these issues which leads me to believe I'm one of the only ones experiencing them.
Any help or suggestions would be greatly appreciated
EDIT:
I forgot to mention that when recording audio or video, it's as if the mic gain is set on full so even the slightest sound is pure distortion, normal talking volume and it clips, I found an app that lets me choose between the mics and when I pic the external mic, it's all muffles as if something is covering it but my phone wasn't in a case while I was testing so I'm not sure what the deal is there but I can't record any decent audio with this and when I record in 4K using Cinema FV-5, all the videos turn out looking like Anaglyph 3D but all pink and green, it's really weird and I don't understand why, but 1080p at 60fps works fine.
I am on CM12 and luckily have had no issues at all. I came from KK 4.4.4 and still have the NB7 BL and modem. I tried one of the guys slim ROMs alpha builds but had issues (probably operator error) but I've tried Bluetooth, GPS, WiFi , LTE etc and everything is good. Not sure what to tell you. I do however always wipe internally and d/l all my apps again through WiFi. A bit cumbersome I know but it won't give me any residual data.
Sent from my SM-N900W8 using XDA Free mobile app

CM 12.1 Nightlies discussion

So i finally gave cm 12.1 a chance because it's been rolling for a while now... and i was actually pretty impressed. The one issue i couldn't deal with is the bluetooth audio playback in my car. Basically it was playing too fast, then pausing every 10-20 seconds and then continuing to play too fast again (also at a slightly higher pitch). I was able to temporarily fix the problem by turning bluetooth off and on but it came back. other than this i didn't see many issues and thought it was pretty good, but for no i'm going to go back to stock until this issue is fixed, i did find that it was already reported to the cyanogenmod team and they are already working on a fix so i'm waiting impatiently until it's fixed and i'll probably be moving from stock kitkat as my main rom to cm 12.1. How has everyone elses experience been with cm 12.1 nightlies so far?
What doesn't work. (if i missed something here post so i can update)
- saving 4k video (1080p works tho)
Battery life ?
- used to be terrible but it's almost as good as stock now but with better performance.
hey
i would like to use CM as i was doing that on my Moto G. the questions I have to users of the newest CM version:
- does quickcircle, google text-to-speech, intelligent screen (LG app) features work?
- what is the quality of videos and pictures taken by the phone running CM opposite to android v20i?
thank you.
Brtnsk said:
hey
i would like to use CM as i was doing that on my Moto G. the questions I have to users of the newest CM version:
- does quickcircle, google text-to-speech, intelligent screen (LG app) features work?
- what is the quality of videos and pictures taken by the phone running CM opposite to android v20i?
thank you.
Click to expand...
Click to collapse
1. Quickcircle won't work. To make it work again you have to install a special app. Google text-to-speech works ok for me (I haven't test it too much). LG features/apps won't work
2.For me the quality of pics and videos are the worst I have ever seen!!!! (Much better in the stock LG)
My experience with CM12.1 was average. I was waiting for something better. Camera is awful in the Custom roms. Battery life wasn't the best. In terms of performance the cm12.1 is better than the stock lg.
i've only been running cm 12.1 for a few days now so i don't have alot of substantive input, i did find a fix for the bad bluetooth car audio using a macro/tasker app but i think they have fixed it in the nightly released today, i'm downloading it now it says bluetooth stream parameters in the patch notes so i wont bother sharing my fix until i try this nightly to see if they already fixed it. i'll give a better review of whats working and the camera/video quality after i have a chance to play around with it more.
by the way anything running ART instead of DALVIK cache/runtime is going to perform better but it's at the price of xposed modules and such, i'm not expert on it but i know they switched to ART cache/runtime to be more competitive with the iphone. On Kitkat and lower an android device needs better hardware to output the same performance as an iphone with lesser hardware. ART should fix that problem. If you are curious google ART vs DALVIK
*edit* yeah bluetooth is fixed with the newest nightly update... atleast for my car which is a mazda 3. (yay)
Avrage camera and bugs like video not saving after recording is main culpit to not use CM 12.1. Otherwise it is good as clean android can be.
it's getting alot better every day now
netmaniack said:
Avrage camera and bugs like video not saving after recording is main culpit to not use CM 12.1. Otherwise it is good as clean android can be.
Click to expand...
Click to collapse
Videos do save. It is a issue with 4K video ONLY. Switch to 1080p video and videos save just fine.
c_brown93 said:
Videos do save. It is a issue with 4K video ONLY. Switch to 1080p video and videos save just fine.
Click to expand...
Click to collapse
I found that myselfe, tnx. But I believe that issue is fixed already. Maybe Im wrong, but I did see in changelog or other forum. Maybe someone can test it?
I switched to stock kitkat, I love CM, been running CM since it was 10.1, the problem is that it starts really really fast and after a while CM 12.1 becomes laggy it drives me crazy, other than that is the camera quality which doesn't bothers me as the performance issue,
I guess we'll need to wait for LG to release the G3 source file but who know's when that's gonna happend
good news the latest daily added some balancing between power and battery life. I went from losing a huge chunk of my battery during work when my phone is in my pocket to going 9.5 hours at work and coming home with 94% battery. (that is alot of standby but i use my phone at lunch and have bluetooth running for about 50 minutes of driving). Basically it got alot better, i'm not sure what they did but i did notice that there is a balanced setting in battery screen that i didn't notice before. Anyways I think those who were concerned about battery drain my have had their wishes answered over the last few nightlies.
netmaniack said:
I found that myselfe, tnx. But I believe that issue is fixed already. Maybe Im wrong, but I did see in changelog or other forum. Maybe someone can test it?
Click to expand...
Click to collapse
i still can't get 4k video to save but 1080p did.
Do knock on and knock code work?
Lucenzo7 said:
Do knock on and knock code work?
Click to expand...
Click to collapse
Knock on works but knock code doesn't, which is quite normal considered it's an LG feature.
Lucenzo7 said:
Do knock on and knock code work?
Click to expand...
Click to collapse
Partly working. You can turn screen on by clicking anywhere, and turn it off by knocking at notification bar.
Phone encryption not working?
I've just flashed the 20150603 CM12.1 and I cannot seem to get the phone encrypted. On the reboot to start the encryption, the phone gets stuck in the CM boot animation and the encryption process never starts. Any ideas or suggestions? Many thanks in advance.
I'm on 06/05 nigthly. When I plug the phone in my computer, it's not being recognized. If I change from MTP to PTP, then it works.
I've tried going to Device Manager, and could see that my phone is being recognized as a Nexus device. I tried installing latest drivers from Google's website, but I got a message saying that I'm already on the latest version. So that didn't do anything. I've tried uninstalling that "nexus" driver and rebooting my PC, but it somehow came back when I plugged my phone in. Trying to update gave me the same message.
If I run "adb devices", I can see that there's no devices (it's enabled in developer settings). If I enable ADB over WiFi and try to connect -- it works, and I can do whatever I want. But only over WiFi and not via USB.
Tried different cable and different port as well.

[Q] Sound Lag

Hello,
I am getting a 1 second sound delay effecting menu and all apps after the device is left on over night, tried factory resetting and with and without sleep mode. Has anyone else experienced this issue or have a solution for me?
Thanks
I was going to say the same thing. I have random one second lag in YouTube (rarely), BSDroid (always), but not in Plex or Kodi. The problem is fixed by pausing in YouTube and jumping forward on BSDroid. It's a big pain as these issues don't affect the chrome cast I have on the same TV and network.
I don't have to wait, it's pretty much out of the box. I have tried stock 5.1.1, rooted 5.1.1, CM12 nightlies, and all AOSP roms available. I feel like it's an issue with the Google Cast app? I'll try 5.1 and see if the situation changes tomorrow.
I haven't even bothered rooting mine yet, as this issue goes right down into the system. Even moving around the menu their is a 1 second delay in the sound. Only goes away with a reboot.
I think I may have found my issue, it seems that when I put the TV into PC mode to fix the overscan I get this sound lag after the TV turns off and then back on again. still troubleshooting it though.
Waited a while to get some new nightlies out and still the same problem. Tried 3 different TVs, all casted audio is delayed and has to be reset. Guess i have a junker now

Help! I've fallen for 10.0 & I can't get up.

*Copied from my post in discussion*
So quick rant. Updated to 10.0 from the zip file posted a couple pages back. I have a standard international model straight from the site, not t-mobile version or anything like that. I've been unrooted since the beginning and still am. I've never touched a beta. My phone is as stock as it can get and not once have I ever had an issue up until this "stable" update. I went from 9.0.17 to 10 (and I really hope it's not just me), and boy does this have issues. If anyone is also experiencing any of these symptoms and has a fix please help.
Issue 1:
I now have this black bar at the bottom of the keyboard that won't go away no matter if I change the height in gboard settings or wipe data and force close and re-update the app even wiping cache in recovery did nothing. I've read other places that this is a thing for Q if you have gestures enabled to give you room at the bottom, but that's seriously BS as if this is the case it should've been an optional setting because now I get screwed up when I type because everything is raised. It's the same on any other keyboard app I've tried.
Issue 2:
Random reboots. This is with no apps open with the phone literally just sitting next to me as I'm doing work. When I'll look at my phone to see ambient it'll just randomly be rebooting. I keep getting them and I have no clue why. Idk if anyone else is experiencing this but sometimes it'll even get stuck in a boot loop and look as if it's bricked then I force restart it using the power and volume keys and it'll boot up for a while until it does that again and I have to keep redoing the process. Again, I tried wiping cache from recovery and I literally went in and force closed every user app I had that wasn't related to the system to no avail.
Issue 3:
Also, there's a brightness and color issue that I'm not quite sure are related but either way they don't work well. If I select the force dark mode in developer settings with enhance video in display settings, or even sometimes one or the other, it'll do either one of two things or both. Either makes every app dark mode and doesn't revert black text to white on apps that are able to support it, and/or it dims videos in landscape mode to lowest brightness no matter if I try to change it, meanwhile the videos are at the proper brightness level in portrait mode.
Issue 4:
Another minor issue is with the fingerprint animation. I've had the McLaren animation from the no-root bypass from another thread somewhere in the phones' forums and when it updated it switched it back to that basic ripple animation. When I try to fix it again and change it as described in the other thread using "setedit" changing the custom fingerprint animation value to 3, it doesn't work and won't set it. It is also noticeably slower from the McLaren animation and it's a small issue but still really annoying.
Issue 5:
Battery life is hit with this update. I usually get around 7hrs~ SOT from the time I wake up to the time I put it back onto the charger with around 15% or so to spare. Last night, I charged it fully and took it off the charger around 2ish and didn't touch it until 8, which is about the same as I normally do daily because I'm a student so I stay up late b/c studying and I don't want to kill the battery overnight so I unplug it right when I sleep and its always at 100% when I unplug. As of right now, its 4:45pm and it's at 32% with 4 hours of SOT from 8-now through minimal, like extremely minimal, use.
I've attached screenshots for most of these issues. I even tried to re-flash the whole update again to overwrite the first attempts', but at this point I just want to go back to 9.0.17 w/o losing data, which is probably a super long shot. I am just super confused as to how this update made it through the stable channel. If you haven't updated, dont.
sonic1675 said:
*Copied from my post in discussion*
So quick rant. Updated to 10.0 from the zip file posted a couple pages back. I have a standard international model straight from the site, not t-mobile version or anything like that. I've been unrooted since the beginning and still am. I've never touched a beta. My phone is as stock as it can get and not once have I ever had an issue up until this "stable" update. I went from 9.0.17 to 10 (and I really hope it's not just me), and boy does this have issues. If anyone is also experiencing any of these symptoms and has a fix please help.
Issue 1:
I now have this black bar at the bottom of the keyboard that won't go away no matter if I change the height in gboard settings or wipe data and force close and re-update the app even wiping cache in recovery did nothing. I've read other places that this is a thing for Q if you have gestures enabled to give you room at the bottom, but that's seriously BS as if this is the case it should've been an optional setting because now I get screwed up when I type because everything is raised. It's the same on any other keyboard app I've tried.
Issue 2:
Random reboots. This is with no apps open with the phone literally just sitting next to me as I'm doing work. When I'll look at my phone to see ambient it'll just randomly be rebooting. I keep getting them and I have no clue why. Idk if anyone else is experiencing this but sometimes it'll even get stuck in a boot loop and look as if it's bricked then I force restart it using the power and volume keys and it'll boot up for a while until it does that again and I have to keep redoing the process. Again, I tried wiping cache from recovery and I literally went in and force closed every user app I had that wasn't related to the system to no avail.
Issue 3:
Also, there's a brightness and color issue that I'm not quite sure are related but either way they don't work well. If I select the force dark mode in developer settings with enhance video in display settings, or even sometimes one or the other, it'll do either one of two things or both. Either makes every app dark mode and doesn't revert black text to white on apps that are able to support it, and/or it dims videos in landscape mode to lowest brightness no matter if I try to change it, meanwhile the videos are at the proper brightness level in portrait mode.
Issue 4:
Another minor issue is with the fingerprint animation. I've had the McLaren animation from the no-root bypass from another thread somewhere in the phones' forums and when it updated it switched it back to that basic ripple animation. When I try to fix it again and change it as described in the other thread using "setedit" changing the custom fingerprint animation value to 3, it doesn't work and won't set it. It is also noticeably slower from the McLaren animation and it's a small issue but still really annoying.
Issue 5:
Battery life is hit with this update. I usually get around 7hrs~ SOT from the time I wake up to the time I put it back onto the charger with around 15% or so to spare. Last night, I charged it fully and took it off the charger around 2ish and didn't touch it until 8, which is about the same as I normally do daily because I'm a student so I stay up late b/c studying and I don't want to kill the battery overnight so I unplug it right when I sleep and its always at 100% when I unplug. As of right now, its 4:45pm and it's at 32% with 4 hours of SOT from 8-now through minimal, like extremely minimal, use.
I've attached screenshots for most of these issues. I even tried to re-flash the whole update again to overwrite the first attempts', but at this point I just want to go back to 9.0.17 w/o losing data, which is probably a super long shot. I am just super confused as to how this update made it through the stable channel. If you haven't updated, dont.
Click to expand...
Click to collapse
1. The Keyboard issue is with all Phones on Q. Like how Apple has the space at the bottom of their Keyboard for Gestures. Unfortunately there is no way to get rid of that but of you're using Q Gestures try Hiding the Pill. The option is there in Gestures.
2. Random Reboots. Now these are annoying. Personally, I had been Daily Driving the Beta for a while. Haven't tried Stable Yet but I had no Random Reboots. Updating from Pie to Q can leave many Apps Broken and long story short that's the casue of your Reboots as well as Battery Darin. My advice is to Factory Reset and Download everything from Play Store. And the McLaren Animation is another known issues. Even the McLaren users Don't have it. Could be wrong
Simply backup storage....Format...go back to 9.0.17 and enjoy.
The Keyboard-Extra-Space at the bottom is not an issue. Its a feature of the gBoard. It was introduced to have a better typing position.
Okay so I face the same issues as you do that is issue 2 and issue 5
issue 2 got solved on its own idk how, i just factory resetted once and wiped cache twice and just left it the way it was (it rebooted and stuck on bootloop twice) then it just stopped, its been a whole day since its been fixed.
issue 5 i face the same but idk how to resolve that, probably with a new update where they fix all these issues if reported by oneplus members
sonic1675 said:
*Copied from my post in discussion*
So quick rant. Updated to 10.0 from the zip file posted a couple pages back. I have a standard international model straight from the site, not t-mobile version or anything like that. I've been unrooted since the beginning and still am. I've never touched a beta. My phone is as stock as it can get and not once have I ever had an issue up until this "stable" update. I went from 9.0.17 to 10 (and I really hope it's not just me), and boy does this have issues. If anyone is also experiencing any of these symptoms and has a fix please help.
Issue 1:
I now have this black bar at the bottom of the keyboard that won't go away no matter if I change the height in gboard settings or wipe data and force close and re-update the app even wiping cache in recovery did nothing. I've read other places that this is a thing for Q if you have gestures enabled to give you room at the bottom, but that's seriously BS as if this is the case it should've been an optional setting because now I get screwed up when I type because everything is raised. It's the same on any other keyboard app I've tried.
Issue 2:
Random reboots. This is with no apps open with the phone literally just sitting next to me as I'm doing work. When I'll look at my phone to see ambient it'll just randomly be rebooting. I keep getting them and I have no clue why. Idk if anyone else is experiencing this but sometimes it'll even get stuck in a boot loop and look as if it's bricked then I force restart it using the power and volume keys and it'll boot up for a while until it does that again and I have to keep redoing the process. Again, I tried wiping cache from recovery and I literally went in and force closed every user app I had that wasn't related to the system to no avail.
Issue 3:
Also, there's a brightness and color issue that I'm not quite sure are related but either way they don't work well. If I select the force dark mode in developer settings with enhance video in display settings, or even sometimes one or the other, it'll do either one of two things or both. Either makes every app dark mode and doesn't revert black text to white on apps that are able to support it, and/or it dims videos in landscape mode to lowest brightness no matter if I try to change it, meanwhile the videos are at the proper brightness level in portrait mode.
Issue 4:
Another minor issue is with the fingerprint animation. I've had the McLaren animation from the no-root bypass from another thread somewhere in the phones' forums and when it updated it switched it back to that basic ripple animation. When I try to fix it again and change it as described in the other thread using "setedit" changing the custom fingerprint animation value to 3, it doesn't work and won't set it. It is also noticeably slower from the McLaren animation and it's a small issue but still really annoying.
Issue 5:
Battery life is hit with this update. I usually get around 7hrs~ SOT from the time I wake up to the time I put it back onto the charger with around 15% or so to spare. Last night, I charged it fully and took it off the charger around 2ish and didn't touch it until 8, which is about the same as I normally do daily because I'm a student so I stay up late b/c studying and I don't want to kill the battery overnight so I unplug it right when I sleep and its always at 100% when I unplug. As of right now, its 4:45pm and it's at 32% with 4 hours of SOT from 8-now through minimal, like extremely minimal, use.
I've attached screenshots for most of these issues. I even tried to re-flash the whole update again to overwrite the first attempts', but at this point I just want to go back to 9.0.17 w/o losing data, which is probably a super long shot. I am just super confused as to how this update made it through the stable channel. If you haven't updated, dont.
Click to expand...
Click to collapse
1. You can't do nothing about it...
2,3,4,5. Clean install(Factory reset )and all issues will be gone
Android 10 is way better than pie ( smoother performance & better battery life)
Phoenix4Life said:
The Keyboard-Extra-Space at the bottom is not an issue. Its a feature of the gBoard. It was introduced to have a better typing position.
Click to expand...
Click to collapse
It's not just for gboard. I use swiftkey and still had that space, which annoys me for some unknown reason. I wasn't able to completely get rid of it, but reduced it by using Navigation Gestures,
https://play.google.com/store/apps/details?id=com.xda.nobar
I only enabled the "Hide Navigation Bar" option and it shrunk it down a bit. Still noticeable, but less annoying now.
cultofluna said:
1. You can't do nothing about it...
2,3,4,5. Clean install(Factory reset )and all issues will be gone
Android 10 is way better than pie ( smoother performance & better battery life)
Click to expand...
Click to collapse
When I back up with OnePlus Switch then factory reset then restore the backup with OnePlus Switch, will the same issues be there again or will it probably solve the problem? I have poor battery life as well after updating...
roter$baron said:
When I back up with OnePlus Switch then factory reset then restore the backup with OnePlus Switch, will the same issues be there again or will it probably solve the problem? I have poor battery life as well after updating...
Click to expand...
Click to collapse
Noooo..
Not restore with oneplus switch...
Start from scratch ..
Just Google back up...( Accounts , passwords, contacts, etc)
Factory reset will definitely solve your battery issues
cultofluna said:
Noooo..
Not restore with oneplus switch...
Start from scratch ..
Just Google back up...( Accounts , passwords, contacts, etc)
Factory reset will definitely solve your battery issues
Click to expand...
Click to collapse
Did the factory reset. Much better now
cultofluna said:
Noooo..
Not restore with oneplus switch...
Start from scratch ..
Just Google back up...( Accounts , passwords, contacts, etc)
Factory reset will definitely solve your battery issues
Click to expand...
Click to collapse
Really really dumb question, but if I factory reset the device is going to cause a problem for twrp or magisk? I'm thinking I would just have to reinstall magisk manager and modules correct? Twrp and magisk themselves would still be intact?
Ryano89 said:
Really really dumb question, but if I factory reset the device is going to cause a problem for twrp or magisk? I'm thinking I would just have to reinstall magisk manager and modules correct? Twrp and magisk themselves would still be intact?
Click to expand...
Click to collapse
After factory reset you'll loose twrp & magisk....
The best you can do is , reinstall the stable 10 through local upgrade, boot to OS ( now you have stock recovery & unrooted) boot to stock recovery and wipe data
Boot to fresh android 10 system....
Now to root the device, boot on fastboot and flash the magisk patched img ...
Reboot ..install magisk manager and install magisk from there ( choose direct install)
Forget the twrp ... doesn't work properly atm ( decryption issues) ..
I see a lot of users updating from pie to Q without wiping data and then are reporting issues ( not working sensors, lags , hiccups, increased battery life, etc)
Go and make a clean install and enjoy android 10...
Phoenix4Life said:
The Keyboard-Extra-Space at the bottom is not an issue. Its a feature of the gBoard. It was introduced to have a better typing position.
Click to expand...
Click to collapse
I've been waiting for MONTHS to get that space at the bottom in Q and I hope that OnePlus won't remove that feature just to humour some people who don't know sh* about UX. My finger hurts and almost slipped my phone many times when I was trying to reach the spacebar prior to Q
cultofluna said:
After factory reset you'll loose twrp & magisk....
The best you can do is , reinstall the stable 10 through local upgrade, boot to OS ( now you have stock recovery & unrooted) boot to stock recovery and wipe data
Boot to fresh android 10 system....
Now to root the device, boot on fastboot and flash the magisk patched img ...
Reboot ..install magisk manager and install magisk from there ( choose direct install)
Forget the twrp ... doesn't work properly atm ( decryption issues) ..
I see a lot of users updating from pie to Q without wiping data and then are reporting issues ( not working sensors, lags , hiccups, increased battery life, etc)
Go and make a clean install and enjoy android 10...
Click to expand...
Click to collapse
That was really concise, however to which "magisk patched img" do you refer?
pbergonzi said:
That was really concise, however to which "magisk patched img" do you refer?
Click to expand...
Click to collapse
https://drive.google.com/drive/mobile/folders/14_DnSq9OTss0EHvA9_qG546dRuHBIS7h?usp=sharing

Categories

Resources