Related
Question:will someone help me?
I will begin by saying that I have no idea where the problem exists for my individual situation, and it would be great if I could get some help.
Background:
I used to run Dead Rage 1.2.
Now I have been back and fourth between Skrilax nightlies and Bytecode's cm10.1 with little to no hiccups.
Over time I began to notice a little lag(notification drawer, swiftkey, and basic ui elements).
Problem description:
Then I decided to try some other roms to fix my issues.
When I flash Carbon rom:
- It has no lock screen by default (and I have not been able to fix this in lockscreen settings)
- The home button does not work (neither in pie controls)
- the quick settings panel button in the notification drawer does not open the quick settings( nor can I access the quick settings any other way)
- the home screen apps are strangely and slightly above the software buttons
I saw someone with similar problems in the posts of carbon but it was resolved by a single reflash.
I also tried a relatively new rom called Revolt on droidrzr:
- I experienced similar issues with the home button
- I did not delve into the issues more because the issues were similar to carbon
Explained, further:
As explained above I have flashed without issue before.
I am under the impression that the way to flash is:
1. mount system
2. wipe system
3. repeat
4. reboot recovery
5. mount system
6. flash
I have tried every variation on this set of rules I think is possible for carbon. I initially had TWRP 2.3. I have flashed without rebooting recovery, without mounting system, with a factory reset on the previous rom, wiping cache and delvik as well. If I don't wipe the system I get weird crashes and the home button still doesn't work but it fixes other things like quick settings. Sometimes when I would wipe system, and not do a factory reset, and flash carbon all my apps from the Bytecode build persisted. This made me think it was a recovery problem.
Then I flashed TWRP 2.5. I have similarly tried everything with TWRP 2.5 and get the same results. I have tried 6/21, 6/23, 7/2, 7/4 carbon on both recoveries.
I have a backup of bytecode cm10.1 and I am running that currently.
If some one would help me troubleshoot or fix my problem, I would love to get carbon. And I would be very much appreciative.
If I am in the wrong place please point me.
I did not post in the carbon topic because I do not have more than 10 posts.
I know that people are not paid to help me so I respect when they do.
Also if you need screenshots, I can reflash carbon and take some shots too.
mrnathanman said:
Question:will someone help me?
I will begin by saying that I have no idea where the problem exists for my individual situation, and it would be great if I could get some help.
Background:
I used to run Dead Rage 1.2.
Now I have been back and fourth between Skrilax nightlies and Bytecode's cm10.1 with little to no hiccups.
Over time I began to notice a little lag(notification drawer, swiftkey, and basic ui elements).
Problem description:
Then I decided to try some other roms to fix my issues.
When I flash Carbon rom:
- It has no lock screen by default (and I have not been able to fix this in lockscreen settings)
- The home button does not work (neither in pie controls)
- the quick settings panel button in the notification drawer does not open the quick settings( nor can I access the quick settings any other way)
- the home screen apps are strangely and slightly above the software buttons
I saw someone with similar problems in the posts of carbon but it was resolved by a single reflash.
I also tried a relatively new rom called Revolt on droidrzr:
- I experienced similar issues with the home button
- I did not delve into the issues more because the issues were similar to carbon
Explained, further:
As explained above I have flashed without issue before.
I am under the impression that the way to flash is:
1. mount system
2. wipe system
3. repeat
4. reboot recovery
5. mount system
6. flash
I have tried every variation on this set of rules I think is possible for carbon. I initially had TWRP 2.3. I have flashed without rebooting recovery, without mounting system, with a factory reset on the previous rom, wiping cache and delvik as well. If I don't wipe the system I get weird crashes and the home button still doesn't work but it fixes other things like quick settings. Sometimes when I would wipe system, and not do a factory reset, and flash carbon all my apps from the Bytecode build persisted. This made me think it was a recovery problem.
Then I flashed TWRP 2.5. I have similarly tried everything with TWRP 2.5 and get the same results. I have tried 6/21, 6/23, 7/2, 7/4 carbon on both recoveries.
I have a backup of bytecode cm10.1 and I am running that currently.
If some one would help me troubleshoot or fix my problem, I would love to get carbon. And I would be very much appreciative.
If I am in the wrong place please point me.
I did not post in the carbon topic because I do not have more than 10 posts.
I know that people are not paid to help me so I respect when they do.
Also if you need screenshots, I can reflash carbon and take some shots too.
Click to expand...
Click to collapse
see post #7 here: http://forum.xda-developers.com/showthread.php?t=2355676
this should probably be in the Q&A/Help/Troubleshooting section....
Thank You So Much!!!!!!!!!!!!!!!!!
I know its soon and I am still crossing my fingers, but thank you!
I have created this thread to clean up the forums a bit and to fix one confusion that most people in the forums which are saying which can mislead people to think that user means that when they don't mean that.
Q: What is the different between brick and soft-brick?
A: This is the issue I was talking about above.
A soft-brick is where you cannot access the kernel or/and rom and a brick is where you cannot access the bootloader so you cannot turn on your device unless you JTag it.
Q: Since I flashed a kernel I got stuck on the splash screen (Google logo bootloader screen), I attempted to reflash but it did not help.
A: Make sure the kernel is supported by the Rom's build number and Android version, to fix this you have to flash a supported kernel, remember that not all kernels are supported.
Q: Since I upgraded to Android 4.3 via OTA I noticed a large battery drain, WHAT IS GOING ON?!?!
A: On day 1 after the upgrade Google Backup will be using your battery for restoring your data so you will have to wait until it is done BUT then it will backup your settings such has brightness and app data but you can switch off "App Data" from the sync settings to stop Google Backup.
Q: A while/day later the issue is gone but Google Services is draining my battery.
A: That is actually Google Maps doing the draining, it is using the internet to locate you, to stop the battery drain go to Settings, Location settings, and disable WiFi & Mobile network location.
Q: Titanium Backup is not restoring my backups, what can I do?
A: Flash SuperSU v1.51 via recovery, this will fix the root issues and the Titanium Backup restore issues.
Q: Root is not working on Android 4.3, I'm panicking!!!!!!!!!!!!
A: Don't worry, flash SuperSU v1.51 has mentioned above to fix root since it now uses the SU Deamon due to the new security.
Q: The stock recovery says "No command.", what can I do?
A: Either keep pressing or hold volume up and power to unlock the menu.
This does not always work for certain users so I would try volume down and power so see if that does anything.
Q: How do I disable the OTA updater?
A: You will need root and an application, thanks to @joshuab227 for the information, the following is from joshuab227's post:
Here's how to disable the auto OTA download on any ROM
Install Autorun Manager from the Play store.
Then enter its recommended advanced mode.
Go into the settings and enable the following : system entries and system app disable.
Disable com.android.gsf.update.SystemUpdateService$Reciever under Google Service Framework
Click to expand...
Click to collapse
Q: The Play Store app and web store will not recognise my device!
A: @ColdEmbrace has got this issue and found the solution so that should explain why the start of the post starts how it starts:
After trying all of the above options my device was still not showing in the store. I went to this link.
play.google.com/settings
I clicked on one of my devices and clicked the update option this loaded my Nexus 4 onto the list it is now available on the web store.
Thanks everyone for the advice and I hope this helps people who are still having issues.
Click to expand...
Click to collapse
Q: My device says that I have no internet connection with a empty signal bar with or without a sim card.
A: The user @matt0401 was one of the victims with this issue and managed to fix this issue with a interesting solution:
Wow, I'm up and running! Weird fix though...
I installed the toolkit and downloaded the ROM, and was attempting to get into fast boot manually because trying to do it during the unlocking process in the toolkit wouldn't work. I thought I remembered the buttons for getting into fast boot from my old Gnex as being "hold power and volume up at same time". I tried this, and the phone went to the white "Google" logo and then vibrated, and then screen went black and the LED notifier at the bottom of the phone glowed red for about 2 seconds. The phone then rebooted, about 10x faster than before might I add, and when I was booted up I saw "No SIM detected... emergency calls only". This would infer my SIM slot was finally being detected, whereas before even with no SIM inserted I just got "No Internet Connection".
I popped my SIM in, rebooted, and the network is connected. Time to review 5 days of missed texts. Thanks for the hand!
tl;dr --> Anybody having this problem, try turning it off, and then turning it back on with the SIM inserted, holding POWER + VOL UP til it does this hard reset type fucntion. When rebooted, the problem should be resolved.
Click to expand...
Click to collapse
Q: I have to reenter my pin code for my sim every time, what do I do?
A: @lucker#1 you guessed it has the same issue has well but he wasn't the OP of the thread that the issue was discussed in but he did sure find a fix, the following is a quote from his post:
i've also had that issue the second day after receiving the phone. I removed the sim, put it back in but that didn't help - i looked at my sim card tray and i realized that a one side of the sim card chip was close to one metal side of the tray and i figured that could be the issue - so what i did is i took a stripe of adhesive tape and made sure they wouldn't touch - I haven't had the issue again and it's been more than 2 weeks.
Click to expand...
Click to collapse
Q: Since I installed Android 4.3 a few of my apps are force closing, what should I do?
A: You have to reinstall that application to fix the issue.
Q: I am getting screen flickering.
A: Flash the correct kernel which supports your Android build and version.
Q: Got a kernel panic, HALP!!!
A: That is pretty rare for the kernel to panic but you can actually easily trigger it, to fix it you must reflash the kernel (make sure it is the correct one!).
Q: Since Android 4.3 on YouTube using Slimport there is a blue graphical glitch, why is it doing that and how to fix it?
A: Since Android 4.3 there is some major bugs, improvements and fixes and the graphical glitch (I got this myself) is due to the new Software Encoder, there is no fix yet but you can go around it by using VPlayer as it apparently supports YouTube videos and it has Hardware Encoding.
If you have any questions and answers please post them here.
Bump!, Not much people are reading this...
Sent from my Nexus 4 using xda app-developers app
Bump once again and the last time.
Sent from my Nexus 4 using Tapatalk 4
Installation
https://github.com/LegacyHuawei/local_manifests/wiki/Installation
Bugs
https://github.com/LegacyHuawei/local_manifests/wiki/Status
Downloads
https://basketbuild.com/devs/LegacyHuawei
Changelog
https://github.com/LegacyHuawei/local_manifests/wiki/CM11.0-changelog
If you have any bugs to report, open new issue at https://github.com/LegacyHuawei/local_manifests/issues
Readme
Use the standard Torch app wherever possible, it only enables flashlight. Other apps from Play Store are designed to use the camera interface, which means camera will use additional power.
For more RAM: Settings->Performance->Memory management.
Do not enable KSM, as video encoder/decoder stops working.
HuaweiSettings
Charge current - allows you to set custom charging current. While this actually limits the current input, it effectively decreases or increases the available current transferred to the battery. This is useful in multiple ways:
Slower, but more effective charging. Your battery will last longer.
Faster charging when connected to USB. For example, USB charging is limited to 500mA, but newer PCs allow drawing up to 800mA or even more. This can be configured via the setting.
Manual override of non-standard charger allowing to draw more than 500mA.
Magnetic sensor calibration - lets you delete previous calibration information. This is useful to recalibrate the compass (when it's inaccurate). Just tap the item & then open any compass up to recalibrate your sensor.
If the phone reboots unexpectedly, crash log is found at /data/dontpanic .
To report bugs, use this app: https://play.google.com/store/apps/details?id=com.tortel.syslog
Thank you, i'll try
wow, downloaded...
Many thanks, good job!
after installing cm11 and gapps, the phone always reboot to recovery
ggunzio said:
after installing cm11 and gapps, the phone always reboot to recovery
Click to expand...
Click to collapse
Did you do a factory reset before?
And does it show the cm logo or just boot to recovery?
Sent from my IDEOS X5 using Tapatalk
Blefish said:
Did you do a factory reset before?
And does it show the cm logo or just boot to recovery?
Sent from my IDEOS X5 using Tapatalk
Click to expand...
Click to collapse
before installing the rom, i've wiped everything, data, cache, system and dalvkit cache, reboot recovery. After installed the rom, and right after, installed the gapps. Then, in recovery, reboot system and after it show the huawei logo, it enters recovery without showing the CM logo.
EDIT: i will install ble_part stock, and them install again the B518, repartition again and try to install CM again.
Booted and installed just fine after doing Blepart and using your recovery. It's slow as molasses, probably in great part due to the fact that the display glitches are still there, but it certainly works, and it's as much KitKat as my Moto G. Something worth mentioning, your recovery has some sort (the same?) of display glitch as well in which the screen only seems to update after a couple of presses of the volume button, not immediately.
ROM and GAPPS, everything works fine.
No glitches for me.
Great job, thanks!
faekplastik3s said:
Booted and installed just fine after doing Blepart and using your recovery. It's slow as molasses, probably in great part due to the fact that the display glitches are still there, but it certainly works, and it's as much KitKat as my Moto G. Something worth mentioning, your recovery has some sort (the same?) of display glitch as well in which the screen only seems to update after a couple of presses of the volume button, not immediately.
Click to expand...
Click to collapse
Thanks.
I don't have any devices to compare it with so it feels "fast" to me. Its great to know the recovery suffers same display bugs, it confirms that its in fact kernel side problem. Though, kernel side does not have BLT enabled, which I thought would be the problem. I'll debug the registers, and see if I can find something odd. It could also be a clock hz issue, it was changed in 3.4.
Sent from my IDEOS X5 using Tapatalk
Blefish said:
Thanks.
I don't have any devices to compare it with so it feels "fast" to me. Its great to know the recovery suffers same display bugs, it confirms that its in fact kernel side problem. Though, kernel side does not have BLT enabled, which I thought would be the problem. I'll debug the registers, and see if I can find something odd. It could also be a clock hz issue, it was changed in 3.4.
Sent from my IDEOS X5 using Tapatalk
Click to expand...
Click to collapse
Well, it stutters a lot, and it's not nearly as smooth as something like Aurora or even stock Huawei ROMs, but I'm sure it's related to the display issues or another issue like that because even scrolling through the Settings app or the little animation in the notification drawer that flips into the shortcuts stutters like hell and drags around, which shouldn't be an issue for this device and wasn't a problem with other ROMs, and overclocking and other user-level optimizations do nothing to alleviate it.
I did also notice black screens when waking the device from lockscreen (digitizer still works) almost every time, requiring multiple attempts until the display finally wakes. I know you squashed this one multiple times, but here it is again.
It's a miracle for this to happen to begin with, so I can't help to be amazed seeing KitKat on this device. Thank YOU so much, Blefish.
do i need to have my phone rooted?
faekplastik3s said:
It's a miracle for this to happen to begin with, so I can't help to be amazed seeing KitKat on this device. Thank YOU so much, Blefish.
Click to expand...
Click to collapse
This. If some months ago anyone told me I'd be installing 4.4 on this device I'd tell them they were crazy.
Thanks for your amazing work, Blefish
Here its works as it should be, you are awesome blefish
Sent from my SM-T210 with rocketTab 2.1 + MK1 kernel using tapatalk v4
Finally i could get it to boot.
probably i broke something, i've installed the oficial rom and then, with 5.5.0.4 recovery wiped everything. Next installed the blepart, new recovery and its working
Good job sir
Thank you!
faekplastik3s said:
I did also notice black screens when waking the device from lockscreen (digitizer still works) almost every time, requiring multiple attempts until the display finally wakes. I know you squashed this one multiple times, but here it is again.
Click to expand...
Click to collapse
Yes, I have waking problems too.
Install everything (partition, 6 recovery, cm11 rom and gapps) and works pretty well so far.
Fantastico. :good::highfive:
lemene said:
Install everything (partition, 6 recovery, cm11 rom and gapps) and works pretty well so far.
Fantastico. :good::highfive:
Click to expand...
Click to collapse
is anyone having problems to connect to wifi networks? i cant connect
EDIT: i guess that is a problem with the wireless definition of the rom, im thinking this, because i can connect to open networks, but when i change the segurity of the wlan to wpa or wpa2, i can't connect to it.
Could you look at this @Blefish?
Im not sure if its a bug or not, maybe something is broken in wpa.supplicant
[]
I have flashed BlePart recovery, i have rebooted the recovery and i have flashed blepart 2.2 then i have flashed CVM Version 6.0.4.6. The phone rebooted and now i cant open the phone or recovery. I tried to install offical 2.3 from sd card but i coudn't. How can i recover my phone?
(Edit 1) Found a fix already! Read post 2!!!
Hello there,
I've been having a OnePlus Two since 4 months already, and had like 2 or 3 home button not working issues.
They used to fixed by themselves after a couple of days of not working, but not this last time.
I tried already the reinstalling system (after formatting system via TWRP), clean it several times, hard reset (hold power button for more than 20 seconds), complete drain battery and fully charge it again, force stop fingerprint service, take out the tempered glass screen protector, and none of those solutions worked.
I here attach (copy the link, can't upload a video directly to this post) a video in which you can see that whenever I power on the screen (still locked), the home button works for several times, but as soon as I unlock it (pattern lock) it stops working. This makes me think that the problem is software, not hardware, but as I said before, already tried reinstalling OOS 3.0, wiping system, cache, data, internal storage, etc.
I compressed the video so it wouldnt be too big, but quality is good enough, just rise the volume so you can listen to the "vibration" that the home button produce.
Any help would be appreciated.
Sincerely,
Daniel Castro
Fix for the issue!
Forum people, I found a fix!
Ok, the solution for making the home button work again (with fingerprint sensor) is the following.
-Factory reset while in OOS 3.0
-Set up everything up and then reboot into fastboot mode
-Install OOS 2.1 via fastboot (you will need to search the forums for it)
-Set up everything up and try to set up fingerprint (it wont work)
-Copy OOS 3.0 (Beta) in the root of the phone
-Reboot into stock recovery and flash OOS 3.0 (beta)
-Factory reset it and set up everything again
-Voila!
Feel free to try this method and reply to this threat or P.M. me for any help.
Sincerely,
Daniel Castro
I have the same problem
Tomorrow i'll try your method
I've posted a questione about this issue,
I think the One plus team should find a solution to this problem that afflict many users
Also, don't forget to rotate your phone 720 degrees, counter clock wise! ? hocus pocus....
DCastro555 said:
Forum people, I found a fix!
Ok, the solution for making the home button work again (with fingerprint sensor) is the following.
-Factory reset while in OOS 3.0
-Set up everything up and then reboot into fastboot mode
-Install OOS 2.1 via fastboot (you will need to search the forums for it)
-Set up everything up and try to set up fingerprint (it wont work)
-Copy OOS 3.0 (Beta) in the root of the phone
-Reboot into stock recovery and flash OOS 3.0 (beta)
-Factory reset it and set up everything again
-Voila!
Feel free to try this method and reply to this threat or P.M. me for any help.
Sincerely,
Daniel Castro
Click to expand...
Click to collapse
Will it erase my internal storage during that fast boot step? So I can backup all my data.
Sent from my ONE A2003 using Tapatalk
these fixes are all coincidences... we need to request a definitive fix from One plus team if is a software issue.
LOL9988 said:
Will it erase my internal storage during that fast boot step? So I can backup all my data.
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
It will erase everything, make a backup before starting the process.
faustin95 said:
these fixes are all coincidences... we need to request a definitive fix from One plus team if is a software issue.
Click to expand...
Click to collapse
Most probably hardware design fault, solution would be to redesign the phone and release a fixed design, will probably not happen unless oneplus3 is the solution.
And I second that it's just coincident behind these back and forth flashing of firmwares "solving" it, almost religious. But what are people to do when oneplus is not a company that takes responsibility for they're mistakes.
pitrus- said:
Most probably hardware design fault, solution would be to redesign the phone and release a fixed design, will probably not happen unless oneplus3 is the solution.
And I second that it's just coincident behind these back and forth flashing of firmwares "solving" it, almost religious. But what are people to do when oneplus is not a company that takes responsibility for they're mistakes.
Click to expand...
Click to collapse
If it works, its worth a try . And yeah, but we are not in any OnePlus Forum, neither debating about if they are gonna do anything about their own issue, we are trying to fix what an irresponsable company wont.
can we make together an official request to one plus to give us an answer or explanation about this? a lot of users are facing this issue, it's not normal
This is my second opt I bought that this problem has happened
sorry for my english
I had also tried lot of things but home button is not responsive at all.. H2os,exodus,oxygen 2.1 ,3.0 same everywhere
---------- Post added at 04:01 AM ---------- Previous post was at 03:59 AM ----------
Error is: when i open fingerprint setting
Enrollment not working try differnt finger or try again ... Nd fingerprint autotest not starting also
i've turned to stock i've updated to oxygen 3.0 bet and the button worked again
i think rooting installing twrp and installing different roms may be the cause of this issue
faustin95 said:
i think rooting installing twrp and installing different roms may be the cause of this issue
Click to expand...
Click to collapse
Unfortunately that is not the case, it's a hardware design bug.
However you can f-k up your finger scanner by damage your persistant-partition if you flash up and down between different ROM/bootloader revisions. But it's easily fixed by flashing the image file for that partition again.
pitrus- said:
Unfortunately that is not the case, it's a hardware design bug.
Click to expand...
Click to collapse
it's a driver issue
faustin95 said:
it's a driver issue
Click to expand...
Click to collapse
50/50 moisture sensitivity and driver issue.
Home button has been working fine for a year, installed 3.0.1 today and suddenly home button only works in OOS 3.0.1. No longer works in CM 13, yet works fine in OOS 3.0.1. Definitely a driver issue.
Tried installing OOS 2.2.1, wiping, then installing Grarak's CM 13 and home button refuses to work. Wiped system, data, cache, installed OOS 3.0.1 and home button works again. Tried wiping again and installed CM 13, home button stopped working. Wiped and reinstalled OOS 3.0.1, home button works again.
Odd thing, my phone will only work with CM13 roms and OOS 2.2.0 or less for fps and home button. Nothing will fix or ever work.
For me, the home button stopped working for a short while on Graraks, then it just jumped back to life again and I haven't had any more home button blackouts after that. If it's a driver issue, it's an extremely intermittent one.
The fingerprint scanner has stopped working from time to time at lockscreen, but this is acceptable for an official hackjobb supported scanner until official sources are released ?
Need Help with this!
Hi everyone!
I have a OP 2 for more than one and a half years now and never had any issues with it(stayed stock...) until recently. I didnt update the phone to the latest version and was putting it off, and today in the afternoon when I tried to unlock my phone it said the 'Fingerprint hardware is not available' and after unlocking the phone with the pattern, it IMMEDIATELY LOCKS ITSELF BACK !!! after split second it just locks the screen while everything is working like connection, wifi, messages, notifications, etc. but due to this I cannot access anything on the phone, can't go to settings and switch to onscreen nav bar buttons, can't force stop/wipe cache the com.fingerprints.serviceext either, tried restarting it several times, downloaded the update but can't even install it because the phone just locks! I have no idea what would fix it and I am avoiding a full reset and wipe on the phone(also based on all i have read, dont think it would fix it anyways)
If anyone knows whats the problem or has dealt with it or knows someone who has, please help me out here on how to fix this and what to do. I did not root it or flash custom ROM's on it yet so literally dont know why it happened.
Thanks,
Max
Just got my OP8 Pro last week and everything was fine until a few days ago. I noticed my screen size is off. It's almost as if it's shrunk. Everything from the top of the screen has dropped about 1mm, so that the camera hole is wrong and the notification bar is below where it should be. I've looked at the dpi, scaling, etc but can't for the life of me find what's changed. Any help would be greatly appreciated.
Did you touch any configurations before that ?
Go to Display > Advanced > Front Camera Display Area and try the option 'hide the front camera' and then go back to 'show the front camera'
see if it fixes the bug.
MoodlePro said:
Did you touch any configurations before that ?
Go to Display > Advanced > Front Camera Display Area and try the option 'hide the front camera' and then go back to 'show the front camera'
see if it fixes the bug.
Click to expand...
Click to collapse
I only set up my phone. I had previously tried switching the front camera display area when I first noticed it was wrong, but it didn't help. Regardless of what settings I use there's always a 1mm or so black area above the status bar.
BRANDENDEUCE said:
I only set up my phone. I had previously tried switching the front camera display area when I first noticed it was wrong, but it didn't help. Regardless of what settings I use there's always a 1mm or so black area above the status bar.
Click to expand...
Click to collapse
It looks like a launcher related problem.
Are you using a custom one of just stock? You could try clearing cache for the launcher in settings - apps and then reboot your phone.
Tell us how it goes.
You might also check your DPI settings (
https://www.reddit.com/r/OnePlus8Pro/comments/jh1x9e
)
Also, if you can take a picture or a screenshot (if it shows) i would highly appreciat it.
MoodlePro said:
Also, if you can take a picture or a screenshot (if it shows) i would highly appreciat it.
Click to expand...
Click to collapse
Using nova or oneplus launcher, it's both the same. I'll see if I can find an extra camera because screenshot doesn't show it
MoodlePro said:
Also, if you can take a picture or a screenshot (if it shows) i would highly appreciat it.
Click to expand...
Click to collapse
Hope this helps.
BRANDENDEUCE said:
Hope this helps.
Click to expand...
Click to collapse
If you're able to do so, clear the cache for both launchers
Update me as always.
MoodlePro said:
If you're able to do so, clear the cache for both launchers
Update me as always.
Click to expand...
Click to collapse
Same as before. I had tried wiping the cache in twrp and it didn't help. I'm trying to get the full zip for the current rom to dirty flash. I'm assuming that will fix the problem, but I can't find anyone who's got it yet.
BRANDENDEUCE said:
Same as before. I had tried wiping the cache in twrp and it didn't help. I'm trying to get the full zip for the current rom to dirty flash. I'm assuming that will fix the problem, but I can't find anyone who's got it yet.
Click to expand...
Click to collapse
it looks like you are not using stock oos or at least some modifications or UI Apps. Some of these apps/mods should be your problem. You are the first on on here reporting this issue so its very likely some of the apps you are using.
I would reset my phone and test every app alone if the issue comes back. Or maybe just deactivate all of them, restart and look what happens.
Stock roms:
[OnePlus 8 Pro][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
Just in case:
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
xtcislove said:
it looks like you are not using stock oos or at least some modifications or UI Apps. Some of these apps/mods should be your problem. You are the first on on here reporting this issue so its very likely some of the apps you are using.
I would reset my phone and test every app alone if the issue comes back. Or maybe just deactivate all of them, restart and look what happens.
Stock roms:
[OnePlus 8 Pro][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
Just in case:
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Click to expand...
Click to collapse
I'm using Oxygen OS 11.0.10.10.IN11AA that I updated right after initial setup. Bootloader unlocked and rooted, swift installer for theming. I've in uninstalled the swift mods and it stays the same. I have some magisk modules, but they were active initially before the issue arose. I did look at the thread for the OOS version, but the newest available is for the last version. As soon as I get my hands on the full zip I'll start from scratch and find out what is causing the issue.
BRANDENDEUCE said:
Just got my OP8 Pro last week and everything was fine until a few days ago. I noticed my screen size is off. It's almost as if it's shrunk. Everything from the top of the screen has dropped about 1mm, so that the camera hole is wrong and the notification bar is below where it should be. I've looked at the dpi, scaling, etc but can't for the life of me find what's changed. Any help would be greatly appreciated.
Click to expand...
Click to collapse
I think after all you've tried I would just MSM back then start over.
Hopefully it's just a very weird glitch although my guess is pointing towards hardware and an alignment issue with the screen..was the device new? Or 2nd hand?
If it's the latter then I'd be having a word, obviously after the MSM wipe, you'll be required to unlock the bootloader again and re-root
It's definitely odd.
If the wipe fails then there may be a calibration tool that enables you to bump the alignment of the screen up a bit, I'm sure dpi changes should have an effect (may need a reboot between changes)
Also change from QHD to FHD, I run in FHD and everything has always scaled really well.
So, the latest update was finally released and I dirty flashed it after disabling all my magisk modules and swift theming, but the issue was still there. I factory reset from twrp and it fixed the problem. All swift theming and modules (viper, Dolby digital, acca, oos call recording) are reinstalled with zero problems. The only thing that I can think of that caused it is an app I used to show battery levels around the camera hole, because everything else is the same. It had to have changed something that even after uninstalling and dirty flashing it didn't revert.
BRANDENDEUCE said:
So, the latest update was finally released and I dirty flashed it after disabling all my magisk modules and swift theming, but the issue was still there. I factory reset from twrp and it fixed the problem. All swift theming and modules (viper, Dolby digital, acca, oos call recording) are reinstalled with zero problems. The only thing that I can think of that caused it is an app I used to show battery levels around the camera hole, because everything else is the same. It had to have changed something that even after uninstalling and dirty flashing it didn't revert.
Click to expand...
Click to collapse
Nice one..