Hi all, I'm new to the forums and to android. I've done some searching and haven't been able to find a solution to my problem, at least in the case of the S3.
I've had my phone just over a week and hadn't noticed any issues until today I realized that landscape mode wasn't working in the web browser. It doesnt seem to want to flip to landscape in other instances I would expect it to either such as in SMS or memo pad. I've tried the gyroscope calibration, tuning auto-rotate on/off, even did a factory reset to see if that would work.
The shortcut to use the camera by tilting to landscape in the lock screen still works so I'm trying to rule out the possibility of a complete hardware malfunction.
I found a post here talking about a similar problem solved by deleting a system file and using a couple shell commands but it's about another galaxy and I can't find the target calibration files in the S3 so I think it's a safe bet that they're different. http://forum.xda-developers.com/showthread.php?t=816131&page=2
Anyway I guess my question is does anyone know what the problem might be and if theres a way to fix it? If there is a way to calibrate the sensors using a terminal or something like what was described in that thread I wouldn't mind giving that a shot, but if there is a simpler solution then that would be great too.
Any help would be greatly appreciated!
Kered42 said:
Hi all, I'm new to the forums and to android. I've done some searching and haven't been able to find a solution to my problem, at least in the case of the S3.
I've had my phone just over a week and hadn't noticed any issues until today I realized that landscape mode wasn't working in the web browser. It doesnt seem to want to flip to landscape in other instances I would expect it to either such as in SMS or memo pad. I've tried the gyroscope calibration, tuning auto-rotate on/off, even did a factory reset to see if that would work.
The shortcut to use the camera by tilting to landscape in the lock screen still works so I'm trying to rule out the possibility of a complete hardware malfunction.
I found a post here talking about a similar problem solved by deleting a system file and using a couple shell commands but it's about another galaxy and I can't find the target calibration files in the S3 so I think it's a safe bet that they're different. http://forum.xda-developers.com/showthread.php?t=816131&page=2
Anyway I guess my question is does anyone know what the problem might be and if theres a way to fix it? If there is a way to calibrate the sensors using a terminal or something like what was described in that thread I wouldn't mind giving that a shot, but if there is a simpler solution then that would be great too.
Any help would be greatly appreciated!
Click to expand...
Click to collapse
Are you using stock launcher? Is the box checked in accessibility options?
Thanks for the reply. Stock launcher, rooted using MrRobinsons bell images here http://forum.xda-developers.com/showthread.php?t=1739426 . Have also flashed the original stock rom without root and had the same problem.
And yes the box is checked in accessibility settings.
Kered42 said:
Thanks for the reply. Stock launcher, rooted using MrRobinsons bell images here http://forum.xda-developers.com/showthread.php?t=1739426 . Have also flashed the original stock rom without root and had the same problem.
And yes the box is checked in accessibility settings.
Click to expand...
Click to collapse
Ya just have to ask the basics never no ... there's also another setting in display u got that one also? If u have I got nothing, maybe factory reset from recovery but also format data and system be4 u flash ur rom
Related
I finally took the courage (putting aside fears of bricking the phone) and decided to upgrade my Canvas HD to 4.2.1 all by myself .
So I went through a few tutorials on here and realised they are more or less the same, and decided to use this one.
I did get the device upgraded, but not before going through some troubles.
Firstly, the SP tools wouldn't stay stuck at 0% even after clicking download and connecting the device.
(Turned out I needed to install the MTK Vcom drivers.(I had already installed the Mobistel Cynus T1 Drivers).
And after that, to my horror, even the TP upgrade it seemed had failed .
Was showing a message saying 'TP Upgrade failed' or something similar.
The OK button wouldn't work either. (NO, I didn't touch the phone while TP Upgrade was in progress. Left it alone for a good half an hour)
Removed and battery and put it again and booted up the phone. (I was bracing my self for a touch-less phone, as reported by a few others.)
To my surprise, the touch was working, and the OS was updated to 4.2.1.
However, I'm not a 100% satisfied with the upgrade.
The colors and clarity of the screen seem a little off.
And I even see a set of blurry pixels just below the notification bar. (I only see this when I am on the homescreen. When I open the app drawer, they go away)
Also, I've set swipe as the lock screen protection. Previously it used to have 3 icons - camera, google now and of course unlock.
But now only the unlock icon is there. (attached screen)
Can anyone help me out here. Has my upgrade gone wrong somehow?
Has anyone faced similar issues?
Should I re-do the process? I'm worried about the TP Upgrade ruining my phone.
im1nfected said:
However, I'm not a 100% satisfied with the upgrade.
The colors and clarity of the screen seem a little off.
And I even see a set of blurry pixels just below the notification bar. (I only see this when I am on the homescreen. When I open the app drawer, they go away)
Also, I've set swipe as the lock screen protection. Previously it used to have 3 icons - camera, google now and of course unlock.
But now only the unlock icon is there. (attached screen)
Can anyone help me out here. Has my upgrade gone wrong somehow?
Has anyone faced similar issues?
Should I re-do the process? I'm worried about the TP Upgrade ruining my phone.
Click to expand...
Click to collapse
the face that you're able to use the phone normally now shows that TP upgrade has already completed good. the lockscreen of android 4.2 shows only the unlock ring by default. it doesn't show others. so it's all working fine. you don't need to worry about any of it, unless your apps start crashing. regarding the colors, you say it becomes normal when the app drawer is opened, which means it's not really a problem. stock wallpapers are not that good. try changing the wallpapers.
The issue related to colours is persistent, i.e. it doesn't go away after I open the app drawer.
You can see the screenshots I posted in reply to this thread.
The colours were definitely not like this before the upgrade. Something is definitely wrong.
I don't know if it is due to some new economical backlight features added by micromax, but turning that off doesn't help either.
I even installed the MIUI rom by ahishek kumar, and that doesn't seem to solve the problem either.
I would definitely like to revert all of this and then let the mmx service centre take care of this.
Do you know how would I do that? I guess I can revert to the backup taken using CWM before installing MIUI, but how to downgrade to 4.1.2 then?
im1nfected said:
The issue related to colours is persistent, i.e. it doesn't go away after I open the app drawer.
You can see the screenshots I posted in reply to this thread.
The colours were definitely not like this before the upgrade. Something is definitely wrong.
I don't know if it is due to some new economical backlight features added by micromax, but turning that off doesn't help either.
I even installed the MIUI rom by ahishek kumar, and that doesn't seem to solve the problem either.
I would definitely like to revert all of this and then let the mmx service centre take care of this.
Do you know how would I do that? I guess I can revert to the backup taken using CWM before installing MIUI, but how to downgrade to 4.1.2 then?
Click to expand...
Click to collapse
Try re-flashing the stock rom and maybe this time you wont get a tp update and your device will work just fine
---------- Post added at 09:55 AM ---------- Previous post was at 09:43 AM ----------
im1nfected said:
The issue related to colours is persistent, i.e. it doesn't go away after I open the app drawer.
You can see the screenshots I posted in reply to this thread.
The colours were definitely not like this before the upgrade. Something is definitely wrong.
I don't know if it is due to some new economical backlight features added by micromax, but turning that off doesn't help either.
I even installed the MIUI rom by ahishek kumar, and that doesn't seem to solve the problem either.
I would definitely like to revert all of this and then let the mmx service centre take care of this.
Do you know how would I do that? I guess I can revert to the backup taken using CWM before installing MIUI, but how to downgrade to 4.1.2 then?
Click to expand...
Click to collapse
If you want to downgrade to 4.1 just flash 4.1 stock rom using sp flash tool.you can refer to this link http://www.youtube.com/watch?v=b4Kkj_R9Rq8
Hello everybody I am new here and before posting this question I have read similar posts searching for my answer but none of them regarded my specific problem:
I just got a Star N7189 with android 4.2.1 and the first thing I did, because it was a used phone that my dad gave me, was to perform a factory reset.
My dad told me the phone was fine except the camera didn't worked, so I thought the factory reset could also help to fix this.
After the reset everything in the phone is fine and running without any problem except the camera. In first place there isn't even a camera icon or app, the only way I can access the camera is by sliding the screen after I press the lock/unlock button, and after a second of thinking it gives me the 'can't connect to camera' error.
I haven't installed any application or anything.
Is there any way to fix this? Thanks in advance.
just install another camera app
Goettsch said:
just install another camera app
Click to expand...
Click to collapse
I've tried several other camera apps and all give me errors. All other apps run fine but apps that need to connect to the camera just fail and shut down lol maybe the phone doesn't have a camera at all and the lens in the back is just to pretend
Hi guys!
I need your help in something that looks like a little problem, but for me it's very, very annoying.
I have an ASUS Transformer Pad TF300T, which I jumped from 4.2.1 to 4.4.4 (CROMBi-kk Custom ROM by @sbdags). With this change I lost the ability to make old apps that were designed for old mobile phones to use the entire screen in portrait mode. One of the apps that I'm talking about is "iMobsters".
Now those old apps use about 20-25% of the tablet screen in portrait mode, and it's stuck this way no matter what I try... It's very annoying, cuz you need to watch real closely to be able to read something, and it ruins the gameplay experience...
I hope you guys can give me a solution to my problem. Maybe an app is the sollution to my problem?
Anyone?
I still have this problem. Sollution?
Try the Xposed Framework + App Settings Module.
I tried, it's not working.
Basically, it's not working at all. No matter what I try, it doesn't do anything...
Does anyone else have issues with their launcher following the Lollipop update? I'm on B309, stock everything and not rooted. Since the update, everytime I reboot my handset it forgets nova as the default launcher. Have factory reset, cleared cache, data etc. No joy. Also, since the updatey my smart cover has stopped working. Now it just shows a demo clock onthe window with writing telling me to hold and swipe to choose a new clock. Suffice to say, holding and swiping does nothing.
Anyone else had such issues? I've reported them to Huawei, but just wondering if re-flashing it would help?
drrobo said:
Does anyone else have issues with their launcher following the Lollipop update? I'm on B309, stock everything and not rooted. Since the update, everytime I reboot my handset it forgets nova as the default launcher. Have factory reset, cleared cache, data etc. No joy. Also, since the updatey my smart cover has stopped working. Now it just shows a demo clock onthe window with writing telling me to hold and swipe to choose a new clock. Suffice to say, holding and swiping does nothing.
Anyone else had such issues? I've reported them to Huawei, but just wondering if re-flashing it would help?
Click to expand...
Click to collapse
Yeah. This is an issue we have been telling them about since the Friendly User Test (FUT) began. There is a Let's Mod thread. Inside that are the workarounds. I'll find it and edit this post in a minute. Basically you freeze the HWHome and your launcher will stick.
EDIT: Here is the thread, http://forum.xda-developers.com/ascend-mate2/general/mod-5-1-update-t3149523. See the third bullet in the OP. Also, read thru the thread. Good stuff.
kimtyson said:
Yeah. This is an issue we have been telling them about since the Friendly User Test (FUT) began. There is a Let's Mod thread. Inside that are the workarounds. I'll find it and edit this post in a minute. Basically you freeze the HWHome and your launcher will stick.
EDIT: Here is the thread, http://forum.xda-developers.com/ascend-mate2/general/mod-5-1-update-t3149523. See the third bullet in the OP. Also, read thru the thread. Good stuff.
Click to expand...
Click to collapse
Need root to freeze though. There isn't a workaround for this if you aren't rooted.
ArkAngel06 said:
Need root to freeze though. There isn't a workaround for this if you aren't rooted.
Click to expand...
Click to collapse
Correct. But the issue is (hopefully) being worked on because it has certainly been brought to their attention.
Awesome, sorry my bad for not searching enough for this issue on the forums. However, I still have this stupid issue with the smart cover. Maybe I'll just use my giant trident cover instead
I don't have/use smart cover, but have you enabled smart cover under settings-smart assist-more?
I'm pretty sure Smart Cover is turned on by default. I don't have one either. Sorry I can't help.
IF you freeze the stock launcher, you better not have your 3rd party launcher crash cause if you do and it requires an uninstall and reinstall you're ****ed. My phone will now not boot because there is no launcher to boot to
Hi everyone, Im a bit desperate right now, since Ive searched all the internet (or I tried) and all of xda, but couldnt find a solution to my problem. Also Im unsure what causes it (ROM, device, some app,...?), which is why Im posting in the general section. So on to my problem:
I have a Oneplus 6, with the most current official LOS release. Sometimes when I unlock my phone, some random app will start. I said semi-random, because its mostly Instagram or Authy, probably depending on which of the two I had opened most recently (actually sometimes both will open; I see Authy for a split-second and then instagram will appear and stay), but never (as far as I remember) other apps, even if I had antoher one open before it happens.
Now, I recently discovered that I can reproduce the behavior if I go to developer settings and change the display cutout setting to something different. It will reliably happen. So the screen goes black for a second, (probably re-drawing the UI) come back and Instagram will open. This led me to the idea that the UI crashes in a way. When it happens after unlocking the device, its always black for a second as well, while usually the screen is just there.
I only found evidence of the problem online regarding Samsung phones, mostly using Nova. Im using Nova as well, so that may be the cause. But I dont know for sure.
Does anyone know this problem? Why is it always one of those two apps, that appear? Can a log help me find the issue?
Things I already tried: factory resetting and setting up Nova from the ground.
Help very much appreciated
EDIT: I dug through the log file a bit and found something interesting (as far as I can say, Im far from an expert). I attached the relevant part, may be someone can tell me what happens?
diemadedrei said:
Hi everyone, Im a bit desperate right now, since Ive searched all the internet (or I tried) and all of xda, but couldnt find a solution to my problem. Also Im unsure what causes it (ROM, device, some app,...?), which is why Im posting in the general section. So on to my problem:
I have a Oneplus 6, with the most current official LOS release. Sometimes when I unlock my phone, some random app will start. I said semi-random, because its mostly Instagram or Authy, probably depending on which of the two I had opened most recently (actually sometimes both will open; I see Authy for a split-second and then instagram will appear and stay), but never (as far as I remember) other apps, even if I had antoher one open before it happens.
Now, I recently discovered that I can reproduce the behavior if I go to developer settings and change the display cutout setting to something different. It will reliably happen. So the screen goes black for a second, (probably re-drawing the UI) come back and Instagram will open. This led me to the idea that the UI crashes in a way. When it happens after unlocking the device, its always black for a second as well, while usually the screen is just there.
I only found evidence of the problem online regarding Samsung phones, mostly using Nova. Im using Nova as well, so that may be the cause. But I dont know for sure.
Does anyone know this problem? Why is it always one of those two apps, that appear? Can a log help me find the issue?
Things I already tried: factory resetting and setting up Nova from the ground.
Help very much appreciated
EDIT: I dug through the log file a bit and found something interesting (as far as I can say, Im far from an expert). I attached the relevant part, may be someone can tell me what happens?
Click to expand...
Click to collapse
Dude reflash your rom..
I'm also using nova no such problem
([emoji813]9/[emoji725]/9[emoji813])
PoochyX said:
Dude reflash your rom..
I'm also using nova no such problem
([emoji813]9/[emoji725]/9[emoji813])
Click to expand...
Click to collapse
did you even bother reading my post? I did that already. Multiple times
diemadedrei said:
did you even bother reading my post? I did that already. Multiple times
Click to expand...
Click to collapse
You said factory restore not reflash buddy use the appporiate wording you have a expensive phone you want to modify it and when issues happen you come here if you stood on stock with no modifications or custom rom you wouldn't have this issue I would suggest simply using an alternative launcher
([emoji813]9/[emoji725]/9[emoji813])
PoochyX said:
You said factory restore not reflash buddy use the appporiate wording you have a expensive phone you want to modify it and when issues happen you come here if you stood on stock with no modifications or custom rom you wouldn't have this issue I would suggest simply using an alternative launcher
([emoji813]9/[emoji725]/9[emoji813])
Click to expand...
Click to collapse
look, if you do not want to help me, thats perfectly fine, then please just dont post. I reflashed the ROM when factory resetting and flashed OOS in between.
If I wanted advice on which ROM or launcher to use, I would have asked for it.
diemadedrei said:
look, if you do not want to help me, thats perfectly fine, then please just dont post. I reflashed the ROM when factory resetting and flashed OOS in between.
If I wanted advice on which ROM or launcher to use, I would have asked for it.
Click to expand...
Click to collapse
Try reporting it as a bug