Related
hello fellow xda-ers
I recently updated to the latest and stable CM10.1 (after using M2,M3, RC3 and RC5) and noticed that my home button stops working after a while. I'm not sure when it started but I think it was with the RC.
I did a search but it didn't yield anything particularly relevant. Is that a known problem?
I just reinstalled everything after resetting all data and it still happening.
thanks in advance for your input,
n
edit: before someone mentions it, I read this thread:http://forum.xda-developers.com/showthread.php?t=2340170 where the user indicates that re-flashing everything and restoring his apps using TB fixed the problem. That's exactly what I did but the problem persists unfortunately.
edit2: the problem seems to be limited to when the app drawer is opened. Home works fine with apps
same thing is happening to me. i was running cm since i bought the phone in February. Decided to flask Franco and now I'm getting this weird touch screen problems. The bottom row where the home button is located will become unresponsive. I decided to go into developer settings and enable "show touches". My phone is sometimes touches without my physical input.
Not sure if kernel related or if my touchscreen coincidentally has given out. I'm gonna try flashing stock kernel and see if that fixes things
nks2105 said:
edit2: the problem seems to be limited to when the app drawer is opened. Home works fine with apps
Click to expand...
Click to collapse
I have the same problem on
Franco M3 and CM10.1 stable, just I'm not sure if it started when I flashed CM stable or Franco M3. Home button doesn't work with app draw open and also it doesn't swap from one homescreen to the default.
However if I got to settings>Launcher>Homescreen>Default screen and change it to another screen then back again the home button works properly but after a few days it stops again.
edit: its as if it just forgets what screen is supposed to be default
Has anyone faced similar issue? Here's bit of background. I was using Liquidsmooth custom ROM with navigation bar disabled and pie controls enabled for navigation. I used to to enable pie control to swipe from bottom border.
So, the day I got system update available notification (for 4.4.3), my pie control stopped working from bottom border. Just a coincidence I think. It was still working from other trigger positions though. I also had this incredible urge to see new update of Kitkat. So, I just got Google factory image of 4.4.3 & flashed it. Everything done, I got to home screen only to find out my navigation buttons are not working. That area is completely dead. Those buttons will randomly start working for some time. Only for a minute or so.
So I went back to the latest version of Liquid Smooth ROM. Pie control from bottom border & navigation bar is not working. Tried going back to stock 4.4.2 & take a 4.4.3 OTA. Still no go.
And to me, it seems a software issue since navigation buttons work in landscape mode. And the area where navigation buttons are in portrait mode also works fine for everything else. So, it's not as of that part of touch screen is dead.
So, to cut long story short, please help me out here guys!!! :crying::crying::crying:
Regards,
Mrugesh.
Did you find a solution to this? I know of a Nexus that also started having this problem and no clue how to fix.
Sent from my SM-T320 using Tapatalk
No clue dude... No resolution... I'm just using my Nexus with pie controls whichever way I can.... Thank God it's a Nexus. Else I'd have been screwed by now buddy.... But surprising to see no resolutions from XDA.
Sent from my Nexus 4 using XDA Free mobile app
Spoke to google support and they told me to return it for another device.
Sent from my SM-T320 using Tapatalk
I created this thread in order to share the problems which I am facing on my 1+1. Hope can get resolved by CM soon... As well as others can discuss about the problem and solution (if available) that we are facing. State method if others can try reporduce the problem to confirm will the problem affect all other 1+1 device, if have screenshot the better.
Firstly, please state:
ROM version (Root Y/N, Other than CM11s don't discuss here, Nightly, Color OS etc.):
ROM mod (State which app will affect system files, from your opinion):
Custom kernel (Y/N, If yes please state kernel you've used):
Model & storage (CN/INT ver, 16/64G):
Recovery (Apparently has nothing to do with ROM I think, just state better)
Problem/bugs:
Okay, start with me...
ROM version: CM11s Rooted, XNPH25R - latest at the moment
ROM mod: AdAway, BusyBox 1.22.1, Xposed Framework 2.6
Custom kernel: NO
Model & storage: CN ver 16G
Recovery: PhilZ Touch 6.49
Problem/bugs:
USB OTG will be not functional when plug in while the screen is OFF, if screen is ON then no such problem, even if you insert USB OTG while screen off and reinsert back after waking the phone, the USB OTG still not working (suspect deep sleep cut off USB OTG power) - Temporary solution: Reboot the phone
MX Player crashes more often while playing with H/W decoder, however S/W decoder works flawlessly. Format Played - 480p FLV.S/W uses more battery consumption so I don't like it, I confirm the same type of video played on other phone doesn't have such MX Player FC problem (If it crashes too many times it will stop working at some point, you can't even play MP4 files with H/W decoder and or stock Gallery app - Temporary solution: Reboot the phone
GPS sometimes takes forever to lock - Temporary solution: Reboot the phone
Torch gesture not working 80% of the time, and crashes the phone - This has been confirmed will be fixed on next OTA
As you can see all these problems can be fixed by rebooting the phone, so I guess it's ROM related problem.
ROM version: CM11s running XNPH25R
ROM mod: None, running stock and unrooted for now
Custom kernel: NO
Model & storage: 64gb sandstone black
Recovery: None
Problem/bugs:
Torch gesture not working 80% of the time, and crashes the phone - This has been confirmed will be fixed on next OTA
Same issue with torch. I ended up disabling torch and music gestures.
Haven't had any other issues per se, but my battery hasn't been nearly as impressive as others have stated. I am going to continue monitoring it and will report back once I have solid information on battery usage.
I have the yellow hue at the bottem 25% of screen but its faint and not too noticeable. I am hoping its just temporary.
oneplusonepwns said:
ROM version: CM11s running XNPH25R
ROM mod: None, running stock and unrooted for now
Custom kernel: NO
Model & storage: 64gb sandstone black
Recovery: None
Problem/bugs:
Torch gesture not working 80% of the time, and crashes the phone - This has been confirmed will be fixed on next OTA
Same issue with torch. I ended up disabling torch and music gestures.
Haven't had any other issues per se, but my battery hasn't been nearly as impressive as others have stated. I am going to continue monitoring it and will report back once I have solid information on battery usage.
I have the yellow hue at the bottem 25% of screen but its faint and not too noticeable. I am hoping its just temporary.
Click to expand...
Click to collapse
At battery stats see any other apps are draining your battery. In my case, sometimes Android OS/System, Google Play Service and Media Server are keeping awake draining the battery while screen is off, in that case, enable privacy guard deny them from keeping awake, or reboot your phone.
ROM version: CM11s running XNPH25R
ROM mod: Rooted with xposed framework, AdAway.
Custom kernel: Franco Kernel
Model & storage: 64gb sandstone black
Recovery: Stock
Firstly: I always like to disable the backlight illumination of the hardware buttons. This works perfect but it doesn't stick. After reboot, its back to lit up.
Secondly: Notification sounds can't be set on per app basis. For eg, Hangouts has its own notification tones and I like gmail and other email app to have different notification tone from the system wide one, however it doesn't happen. All apps use the system wide notification tone regardless of what I set separately on them. I guess this has something to do with the theme engine coz I chose tones from it.
Thirdly: when rotation is locked, camera interface doesn't rotate. I thought camera interface is meant to auto rotate regardless of the "rotate setting on or off"
Sent from my One using Tapatalk
ROM version: CM11s XNPH25R rooted
ROM mod: Why mess with a good thing?
Custom kernel: N
Model & storage: INT 64G
Recovery: PhilZ CWM
Lock screen delay doesn't work on built-in custom lock screen. Works fine otherwise.
ROM version: CM11S XNPH25R, not rooted
ROM mod: None
Custom kernel: N
Model & storage: INT 64G
Recovery: Stock
[ ] 2 Google Play Services force closes while setting up phone
[ ] Ringtone and default notification sound were reset to default once randomly
[ ] Double-tap to wake setting becomes checked again randomly after turning it off, but the feature is not re-enabled
[ ] Google Now keeps showing "Good morning / evening! Here are your current cards" and "Google Now is always working for you" cards even after swiping them away many times
[ ] In-call speaker volume is too low, MUCH lower than volume for everything else
[ ] Some ringtones and notification sounds are duplicated with different names
[ ] The screen seems to miss touches occasionally
[ ] "Ok Google" and Google voice searches only work if I speak VERY loudly
[ ] The phone occasionally sticks in landscape orientation and I have to shake it to get it to rotate back to portrait
[ ] Scrolling is not as smooth as my stock Nexus 5 (more dropped frames) in not all, but some apps. This could just be poor optimization, but I'm calling it a bug because really this phone should always perform better than a Nexus 5 because it has an 801 and 3GB of RAM.
Is there anyone who types fast on the OnePlus One?
Do you find it that it misses some keys sometimes and generally makes it hell to type on...
Does this have anything to do with it's multi touch issues?
Sent from my One using Tapatalk
ROM version: Stock CM11S XNPH25R, rooted
ROM mod: Busybox,Xposed
Custom kernel: No
Model & storage: CH 64G
Recovery: Philz
Problem:
Screen not wake when press power button,navigation light is on, but screen not wake. my solution for now is need to force restart.
Sent from my One using XDA Premium 4 mobile app
SleemLDJ said:
Is there anyone who types fast on the OnePlus One?
Do you find it that it misses some keys sometimes and generally makes it hell to type on...
Click to expand...
Click to collapse
Yes, I believe I have experienced this and quite often too.
Apart from the missed keystrokes, my phone reboots randomly every 30 mins or so. I haven't gotten around to root causing it.. Maybe due to ART (?)
ROM version: Stock CM11S XNPH25R, rooted
ROM mod: None
Custom kernel: No
Model & storage: INT 64G
Recovery: Stock
I have also issues with the touchscreen; some parts of the screen doesn't react on touch or swipe...For example when I touch the letter 'b' on the standard keyboard, its always the letter before or behind. In landscape modus it works well. Also games like candy crush and 2048 where you have to swipe alot on the screen and difficult to; sometimes it doesn't react on parts of the screen or it does something else ( to the right instead going down,...)
I 'm waiting since Friday for an answer...because I'm afraid its hardware failure
https://www.youtube.com/watch?v=SSmpYQYofOc
Sent from my LG-V500 using XDA Free mobile app
Maybe I'm just lucky I haven't come across any problems yet.
CM Version 11.0-XNPH25R
Completely Stock.
magnum73 said:
I have also issues with the touchscreen; some parts of the screen doesn't react on touch or swipe...For example when I touch the letter 'b' on the standard keyboard, its always the letter before or behind. In landscape modus it works well. Also games like candy crush and 2048 where you have to swipe alot on the screen and difficult to; sometimes it doesn't react on parts of the screen or it does something else ( to the right instead going down,...)
I 'm waiting since Friday for an answer...because I'm afraid its hardware failure
https://www.youtube.com/watch?v=SSmpYQYofOc
Sent from my LG-V500 using XDA Free mobile app
Click to expand...
Click to collapse
Oh god that looks terrible.
i haven't seen this mentioned yet, but sometimes when i open the Google keyboard in landscape mode, it will only show 1 line of keys. i fix it by force stopping the keyboard
Main ones for me are the speaker phone volume and incompatibility with the Google launcher "OK Google" feature.
Sent from my One using XDA Free mobile app
cas8180 said:
Main ones for me are the speaker phone volume and incompatibility with the Google launcher "OK Google" feature.
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
You are most likely missing a couple lib files, like hotword detection for Google now..
Sent from my Nexus S using XDA Premium 4 mobile app
Setting.Out said:
You are most likely missing a couple lib files, like hotword detection for Google now..
Sent from my Nexus S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
One of the moderators on the OP forums replied to my comment about the hotword detection and stated it is a known bug with CM and has been addressed and will be resolved in the next OTA.
cas8180 said:
Main ones for me are the speaker phone volume and incompatibility with the Google launcher "OK Google" feature.
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
The speakerphone problem has been addressed in one of the recent nightlies. Call volume is good now. It is scheduled for the upcoming ota.
M9 just came out. Only in a matter of time we get the ota for the next update
jarjar124 said:
M9 just came out. Only in a matter of time we get the ota for the next update
Click to expand...
Click to collapse
Where are you guys seeing these updates. I went to cm's website but didn't see our device on there. Also tried googling it and didn't see it. Maybe I am just blind.
Edit:
Just found it nevermind...
Sent from my One using XDA Free mobile app
cas8180 said:
Where are you guys seeing these updates. I went to cm's website but didn't see our device on there. Also tried googling it and didn't see it. Maybe I am just blind.
Edit:
Just found it nevermind...
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
Where
Sent from my One using XDA Free mobile app
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
*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