Marshamallow piece of crap - Moto G 2015 Q&A, Help & Troubleshooting

Hi,
I have a moto g 3 and updated to marshamallow.
it was the first time i ever upgraded an android phone.
little did i know the troubles this would cause.
-phone is now considerably slower.... **noticeable SLOWER!**
- I used to shake my phone and lit up the flashlight. now that works 1 out of 20 tries. its bugged.
- at lollipop i would click the volume key and it would show an option to silence the phone.
they removed that feature and moved it to the slide menu. so now i have touch screen, unlock it, slide down,
click the silence button, click ok.... thats 3 more clicks, and even more if you use an unlock passwd or pattern.
its stooopid. at lollipop it didnt matter if ur phone was locked, volume key would be accesible and silence it.
thats a 2click procedure.
/rant off
I want to downgrade to lollipop.
Can anyone point me to a how to link procedure?
i need some foolproof very in detail.procedure, im a guy with general computer knowledge, but not a die hard.
have not rooted a phone ever. but if theres a procedure for downgrading that is detailed thoroughly & foolproof id appreciate the link so I can study it.
This

Have you done a factory reset? that solves most problems.

jazf78 said:
Hi,
- at lollipop i would click the volume key and it would show an option to silence the phone.
they removed that feature and moved it to the slide menu. so now i have touch screen, unlock it, slide down,
click the silence button, click ok.... thats 3 more clicks, and even more if you use an unlock passwd or pattern.
its stooopid. at lollipop it didnt matter if ur phone was locked, volume key would be accesible and silence it.
thats a 2click procedure.
/rant off
Click to expand...
Click to collapse
Being a fellow who uses the phone as a phone, I immediately noticed that thing after upgrading from a CM12.1 based rom to a CM13 based one... It was one of the functions I used more during the day.
Some other things that makes me want to come back to CM12.1...? yes.
-The fact that the Contact tab inside the dialer doesn't filters out contacts I decided to not show on the Contact app.
-(Not really a MM issue, but instead related to Cyanogenmod.) No call recording (another essential feature for me)!
The phone part of our "smart" devices is becoming worse and even more worse every update . Maybe it's time to come back to a Nokia 3310 or a Qtek 9090 like in the good old days

jazf78 said:
Hi,
I have a moto g 3 and updated to marshamallow.
it was the first time i ever upgraded an android phone.
little did i know the troubles this would cause.
-phone is now considerably slower.... **noticeable SLOWER!**
- I used to shake my phone and lit up the flashlight. now that works 1 out of 20 tries. its bugged.
- at lollipop i would click the volume key and it would show an option to silence the phone.
they removed that feature and moved it to the slide menu. so now i have touch screen, unlock it, slide down,
click the silence button, click ok.... thats 3 more clicks, and even more if you use an unlock passwd or pattern.
its stooopid. at lollipop it didnt matter if ur phone was locked, volume key would be accesible and silence it.
thats a 2click procedure.
/rant off
I want to downgrade to lollipop.
Can anyone point me to a how to link procedure?
i need some foolproof very in detail.procedure, im a guy with general computer knowledge, but not a die hard.
have not rooted a phone ever. but if theres a procedure for downgrading that is detailed thoroughly & foolproof id appreciate the link so I can study it.
This
Click to expand...
Click to collapse
If your using Indian XT1550 please take TWRP backup and give me the download link I need it very badly.

ethaniel said:
Being a fellow who uses the phone as a phone, I immediately noticed that thing after upgrading from a CM12.1 based rom to a CM13 based one... It was one of the functions I used more during the day.
Some other things that makes me want to come back to CM12.1...? yes.
-The fact that the Contact tab inside the dial
no idea what this all meant. plz stay on topic, thanks
Click to expand...
Click to collapse

Nazeerchauhan said:
If your using Indian XT1550 please take TWRP backup and give me the download link I need it very badly.
Click to expand...
Click to collapse
im from México.

eemgee said:
Have you done a factory reset? that solves most problems.
Click to expand...
Click to collapse
i haven´t but i read somewhere else that a factory reset would not downgrade android version. since it also changed its firmware..
dont know if thats true or false.. did you or anyone reading this has actually done a factory reset and their android device downgraded itself? need to be sure, dont want to waste time, backing **** up, doing factory reset
only to notice it still marshmallow and then redownload and restore everything so i can use the phone and still have the problem.
thanks

jazf78 said:
ethaniel said:
Being a fellow who uses the phone as a phone, I immediately noticed that thing after upgrading from a CM12.1 based rom to a CM13 based one... It was one of the functions I used more during the day.
Some other things that makes me want to come back to CM12.1...? yes.
-The fact that the Contact tab inside the dial
no idea what this all meant. plz stay on topic, thanks
Click to expand...
Click to collapse
I wasn't so much off-topic, it was something related to the thread title (Marshmallow piece of crap), but OK! I respect your statement. Last reply I make on this thread.
Hope tomorrow will be a better and happier day for you
Click to expand...
Click to collapse

jazf78 said:
Hi,
I have a moto g 3 and updated to marshamallow.
it was the first time i ever upgraded an android phone.
little did i know the troubles this would cause.
-phone is now considerably slower.... **noticeable SLOWER!**
- I used to shake my phone and lit up the flashlight. now that works 1 out of 20 tries. its bugged.
- at lollipop i would click the volume key and it would show an option to silence the phone.
they removed that feature and moved it to the slide menu. so now i have touch screen, unlock it, slide down,
click the silence button, click ok.... thats 3 more clicks, and even more if you use an unlock passwd or pattern.
its stooopid. at lollipop it didnt matter if ur phone was locked, volume key would be accesible and silence it.
thats a 2click procedure.
/rant off
I want to downgrade to lollipop.
Can anyone point me to a how to link procedure?
i need some foolproof very in detail.procedure, im a guy with general computer knowledge, but not a die hard.
have not rooted a phone ever. but if theres a procedure for downgrading that is detailed thoroughly & foolproof id appreciate the link so I can study it.
This
Click to expand...
Click to collapse
I think downgrading will be a more difficult task than a factory reset. A factory reset should clear all your issues.

Related

Automatically activate speaker when placing phone face down

On my old Rhodium TP2 there was a feature to automatically activate speaker when placing phone face down. Is that possible with HD2?
Err... yeah. You just place it face down
johncmolyneux said:
Err... yeah. You just place it face down
Click to expand...
Click to collapse
LOLLLL
didn't know that
It never worked for me for some reason. It could be disabled but I can't find the setting to turn it on. Anyway, I am planing to do a hard reset this weekend and see if that feature is back.
ma6inista said:
It never worked for me for some reason. It could be disabled but I can't find the setting to turn it on. Anyway, I am planing to do a hard reset this weekend and see if that feature is back.
Click to expand...
Click to collapse
I can only assume it will be there after a hard reset, as it's something I've used countless times and have never had to enable it. (I seem to remember reading it in the manual too!)
Confirmed working with Dutty's ML series ROMs.
It does not work for me. WWE ROM. I just did a hard reset.
Always worked for me on Stock 1.66 ROM.
Working on Axlor.
Weird this, ive always wanted it!
and just never tried it
joshzzz2001 said:
It does not work for me. WWE ROM. I just did a hard reset.
Click to expand...
Click to collapse
that's strange. the feature is documented in the HD2 manual, so it at least works on all stock ROMs. If not, approach HTC support.
i'd say if it doesn't work, its something related to a flashed rom and a setting more than anything else
Turing On Speaker While Facing Up More Useful
I would rather somehow have the proximity sensor turn the spearkers on while the phone is facing up because it would be nice to multi-task and take notes or update my contacts while I am talking to that person/business. For example, a business gives me an RMA so I would have to edit my notes for that contact and enter the RMA number. I can't do this while the phone is faced down.
yea the speaker function works the same on mine as on the TP2
Is there a setting or reg key that I can change to enable this? (doesn't work on Artemis 6.0)
ma6inista said:
On my old Rhodium TP2 there was a feature to automatically activate speaker when placing phone face down. Is that possible with HD2?
Click to expand...
Click to collapse
Maybe it's too late and you already found the solution but here it goes for other people:
To turn the HD2's speaker on do one of these:
1 - Long press phone button (furtherest left)
2 - Turn it upside down
3 - On the call screen slide down & press the speaker's button

[Q] Missed call unlocks screen

Hi, I searched the forum but had no luck:
Completely new Nexus 5, White 16GB, and I have this issue:
When i receive and miss a call, as soon as the ringer stops the phone automatically shows the unlocked homescreen and it just stays there, instead of locking itself normally. This is really weird, and happens even if the phone is in my pocket (so it's not sensor-related like whatsapp pop-ups for example). Also not really safe i'd say. If I select another lockscreen method, it behaves normally (showing, for example, unlock pattern for a certain amount of time before turning the monitor off again.)
Anyone experiencing the same issue?
http://www.reddit.com/r/Nexus5/comments/1q04f7/nexus_5_unlocks_itself_after_a_missed_call/
This is the only other reporting I found on the web. Can anyone test this? It's really fast and easy, and I think this could be a pretty serious issue.
My phone (pin locked) doesn't do that. Phone stays locked. Is your phone kept unlocked?
jj14 said:
My phone (pin locked) doesn't do that. Phone stays locked. Is your phone kept unlocked?
Click to expand...
Click to collapse
Yes. I don't really like the pin/passcode unlock (also don't really need it). Classic slide is simple and fast enough, but it's crazy that it stays unlocked after a missed call.
Also, I noticed that it automatically enters the last application that was open the last time you locked it, creating even more concerns (last online on messaging applications, online status in facebook, ecc.)
Just imagine you boss calling you, with no luck, and founding out a second later you're online in Facebook. Just because you were ignoring your phone, while driving for example.
themcfly said:
Yes. I don't really like the pin/passcode unlock (also don't really need it). Classic slide is simple and fast enough, but it's crazy that it stays unlocked after a missed call.
Also, I noticed that it automatically enters the last application that was open the last time you locked it, creating even more concerns (last online on messaging applications, online status in facebook, ecc.)
Just imagine you boss calling you, with no luck, and founding out a second later you're online in Facebook. Just because you were ignoring your phone, while driving for example.
Click to expand...
Click to collapse
I agree - that should not be the expected behavior
nexus5 32gb here, exactly the same behavior.. I had to enable a pin/password unlock method because every missed call would unlock my phone, even in my pocket..
I have the same issue.
Maybe it is because of the app Light Flow Lite ?
mr_smith1 said:
I have the same issue.
Maybe it is because of the app Light Flow Lite ?
Click to expand...
Click to collapse
I thought this as well, but then I tried it on my friends N5 and had the same behavior, without light flow. I think many of us actually discovered this trying notifications in Light Flow (i bought the pro version) but it's not related to that.
kowloon12 said:
nexus5 32gb here, exactly the same behavior.. I had to enable a pin/password unlock method because every missed call would unlock my phone, even in my pocket..
Click to expand...
Click to collapse
Me too, but I hate it because I can't swipe down from the top to quickly see my notification without unlocking the device first.
Let me know if you guys have any advice on this issue, also report it in this thread to keep it bumped and see if anyone is reporting any solution.
themcfly said:
Me too, but I hate it because I can't swipe down from the top to quickly see my notification without unlocking the device first.
Click to expand...
Click to collapse
exactly this, it was so useful to just throw a glance to the notifications to decide if open them or simply clean them away
Yes same here, this looks to be a bug surely?
Sent from my Nexus 5 using xda app-developers app
OK thanks,
I reported the problem on google discussion (I copy/paste our first topic because you explained the problem very well ^^).
the URL:
"https://productforums.google.com/forum/#!category-topic/nexus/nexus-5/KML5nWW9q6o"
mr_smith1 said:
OK thanks,
I reported the problem on google discussion (I copy/paste our first topic because you explained the problem very well ^^).
the URL:
"https://productforums.google.com/forum/#!category-topic/nexus/nexus-5/KML5nWW9q6o"
Click to expand...
Click to collapse
Nice one, I have posted in that discussion as well. Hopefully we will get a response.
Others have the same problem, do you know how to report a problem to google ?
I just tried it on my phone, called from my desk number, missed call. It did open the phone all the way, but the screen turned back off in 5 seconds, per my settings.
My phones is currently stock, have not rooted or unlocked the bootloader yet. Only UI modification apps are Widgetzoid and Dashclock, I wanted to stay stock for a bit.
Sorry, that you are having issues. Unfortunately sometimes the easiest way to figure out what is causing the problems is to do a factory reset, and re-dowload your apps one by one, to see what is causing the problem.
Ok, but a several people have the same issue ...
Anyway, I think I will tri not to miss a call whenever the phone is in my pocket !
Zandeer said:
I just tried it on my phone, called from my desk number, missed call. It did open the phone all the way, but the screen turned back off in 5 seconds, per my settings.
Click to expand...
Click to collapse
I don't like setting the screen timeout so short, many thimes i just place the phone on my desk while messaging and I want the screen to stay on, for at least 2 minutes.
And when I lock my phone to keep it in my pocket, it's supposed to stay locked and ignore any unintended touches as soon as i slide to unlock, which was originally introduced to prevent an unlock by accident. Yes, I could lower my screen timeout to 5 seconds, but that does not solve the problem because still unintended touches can occur in that time frame.
themcfly said:
I don't like setting the screen timeout so short, many thimes i just place the phone on my desk while messaging and I want the screen to stay on, for at least 2 minutes.
And when I lock my phone to keep it in my pocket, it's supposed to stay locked and ignore any unintended touches as soon as i slide to unlock, which was originally introduced to prevent an unlock by accident. Yes, I could lower my screen timeout to 5 seconds, but that does not solve the problem because still unintended touches can occur in that time frame.
Click to expand...
Click to collapse
I wasn't sing o set your screen lock time to what I have it set at, I was just saying that it did re-lock. However, you are right, IMO it should not completely unlock the screen when the phone is ringing.
Though I have never not had a passcode on my phone, so not sure if that is how it always behaves. Was just trying to test and be helpful.
I sent a message to the google team, let's wait and see.
here is a link to see the bug :"http://www.youtube.com/watch?v=SSTq8Xhe6Kc&"
Zandeer said:
I wasn't sing o set your screen lock time to what I have it set at, I was just saying that it did re-lock. However, you are right, IMO it should not completely unlock the screen when the phone is ringing.
Though I have never not had a passcode on my phone, so not sure if that is how it always behaves. Was just trying to test and be helpful.
Click to expand...
Click to collapse
Thanks for testing, I was wondering if this could have been related to root / unlocked bootloader somehow but you have confirmed this is not the case as it happens on a totally stock phone.
good catch there. same issue here.
at least a Google employee has responded to the topic created HERE. Maybe that will expedite then pushing out an update ASAP.

Honor 6x BLN-24-cannot press "allow" for any app.

When an app asks for permissions, Allow and Deny options show up (regardless if for storage, or camera, etc.) but the allow button does not work. Deny works fine. So far i have unlocked the bootloader via Huawei website method (i guess you call that official) and flashed twrp. I have not rooted the phone yet (getting to that, but one problem at a time) and this is the first one.
I also saw someone else ask, but with now answer. Is there a way to get rid of the splash scren about the phone being unlocked and not trustable, press power button again to boot?
Do you have an special theme activated? Use the standard theme and try again
My 1st question to you is... when the window prompts, do you flag the option "don't ask to me again" or not? Because if yes, the only option avalaible becomes the "deny" one. This mechanism confused me too some time ago, when i wasn't understanding why it was blacked out; Android takes your flag as an "what a bore, just shut up and go **** ya' self leavin' me alone" answer, so it automatically deactivate the possibility to let it pass even one more time. If you didn't checked the flag, i have another question for you. Did you maybe recently made an update OTA, or with an update package found online? If the 2nd answer is what u've done, do a check for being sure that you have updated the phone with the correct package model. (BLN-21, BLN-22, ecc.) If neither this is your case, begin to tell us something more 'bout your phone configuration and start to think to backup your data and do a factory reset for eliminate this weird issue.
For the question of yours about the Nag screen (the splash one, for being clear) at the moment there is nothing that we can do to avoid it to pop out; just skip it pressing immediately the power button, is the best advice that i can do so far
I'll attempt to answer all these at once since I just got home from work. I wouldn't believe rooting the phone would cause this issue, but the problem happened before i unlocked the bootloader so I think that rules that out. I do not use a special theme, but I do use squarehome launcher for my phone, not the standard android launcher. Problem there is, the problem occurs with either launcher being active. And theme wise, I have a 3-d live aquarium for a background (which if turned off and just a static wallpaper, the same behavior occurs). As far as the phone update goes, it was an OTA update from 6 to 7, so still using stock, nothing sideloaded or flashed (yet). My data is all backed up via My backup pro, and doing a full backup with TWRP onto OTG is not a problem. I prefer not throwing in the towel, since setting up squarehome perfectly is a pain in the ass, but if it has to happen, it is better than manually setting permissions for every app that needs them. Not sure what a screenshot would do, think of any app asking for permission to use phone storage, both the allow button and the deny button visible (in white, nothing grey) and allow doesn't respond where deny responds fine. and then i have to go in manually and grant the permission after the fact. I suppose I could just root my phone and give that a whirl, seems some bloatware needs to be removed anyway, and i have the SU sitting on my hard drive already. Thanx for the responses, and let me know what you may have come up with before I just factory reset it which as mentioned, I am dreading doing.
Rommco05 said:
Hi, so you have unlocked bootloader but not rooted? This is maybe problem, you need to have rooted phone if you have unlocked bootloader for fully using phone. Can you post some screeshots?
Click to expand...
Click to collapse
Well, I didn't think that would be the answer, but you, sir were right. I rooted my phone and it seemed to have fixed the problem. I don't believe I made any other change whatsoever. Thank you very much. Glad I tried it anyway as you suggested even though I didn't think it would be the answer. I am not above saying thank you, and I was wrong. Kudos. Maybe this will help someone else. Good thing is, I planned on rooting it anyway, and you just kicked me in the pants to do it.
Rooted but allow button is still not activated
Hello guys,
I wanted to activate app twin so I rooted my phone BLN-L21 android 7.0
Allow button still deactivated.
Also the boot screen that asks to press power button still exist.
I noticed that if I activate whatsapp twin it won't work simultaneously .
I.e : when you open whatsapp you get all missed calles & messeges.
Also I was able to download themes through themes app ,but now it just views the local themes.
Note: superSu is installed.
Any help will be appreciated.
Thank you
Well, I think this is not related to OP (or at least partially), but when unlocking bootloader after setting up SD card as the default storage can break some things, like default themes.
Try to restore your firmware, and then unlock the bootloader.
If successful, you can now set up SD card as default storage.
jackmeat said:
When an app asks for permissions, Allow and Deny options show up (regardless if for storage, or camera, etc.) but the allow button does not work. Deny works fine. So far i have unlocked the bootloader via Huawei website method (i guess you call that official) and flashed twrp. I have not rooted the phone yet (getting to that, but one problem at a time) and this is the first one.
I also saw someone else ask, but with now answer. Is there a way to get rid of the splash scren about the phone being unlocked and not trustable, press power button again to boot?
Click to expand...
Click to collapse
Its happened to me before i just wiped the phone. I even sometimes cant click install when installing an apk unless i lock and unlock the screen.

Unable to make phone ring

Hello
I just bought this phone, and despite navigating the entire settings menu, I am unable to turn up the volume for the ringer. The vibrate icon shows on the status bar,and a notification on the quick settings shows that I'm on vibrate mode.
What have I overlooked??
Edit..disregard.i found the little sound rocker volume above the power button. What is the purpose of it since that's what settings are for ?
nabril15 said:
Hello
I just bought this phone, and despite navigating the entire settings menu, I am unable to turn up the volume for the ringer. The vibrate icon shows on the status bar,and a notification on the quick settings shows that I'm on vibrate mode.
What have I overlooked??
Edit..disregard.i found the little sound rocker volume above the power button. What is the purpose of it since that's what settings are for ?
Click to expand...
Click to collapse
When your in a meeting or someplace where your attention is required and you don't want your phone blaring out it's downright disrespectful. And pulling out your phone to unlock and put in silence mode, says a lot to people. Now pulling it out, and hitting the slider makes people curious about the phone, it's just convenient. And with heptic feedback, you can feel what mode your on without even pulling it out.
blas4me said:
When your in a meeting or someplace where your attention is required and you don't want your phone blaring out it's downright disrespectful.
Click to expand...
Click to collapse
Thank you. That makes sense. You sound like an expert on this device. I've received a few texts, but there's no light to blink. How can I get notified when the screen is off?
Also, where can I start looking to upgrade it to Android 10 and rooting?
nabril15 said:
Thank you. That makes sense. You sound like an expert on this device. I've received a few texts, but there's no light to blink. How can I get notified when the screen is off?
Also, where can I start looking to upgrade it to Android 10 and rooting?
Click to expand...
Click to collapse
Please understand my respectful reply...but it seems to me that you know very little about this phone...and you want to root it? My serious recommendation is that you stick with stock, go to the Play Store and install Oxygen Updater as this app will get you the latest available updates for the 7 Pro. Stay away from root, and boot loader unlocking as this will wipe the phone and several people have problems doing this. Just stick with stock.
jaseman said:
Please understand my respectful reply...but it seems to me that you know very little about this phone...and you want to root it? My serious recommendation is that you stick with stock, go to the Play Store and install Oxygen Updater as this app will get you the latest available updates for the 7 Pro. Stay away from root, and boot loader unlocking as this will wipe the phone and several people have problems doing this. Just stick with stock.
Click to expand...
Click to collapse
I would agree with you on that, about sticking with stock in OOS. But, Root gives you access to tweak your device to your liking, and add extra security features. Android isn't Android unless your running at Root level. If your new, then I'd suggest you read first, and it helps if you know Linux.
blas4me said:
and add extra security features
Click to expand...
Click to collapse
Can you elaborate? What features?
I just upgraded to 10.0.2, and I will root it tonight following arden144's guide. I may not know all the technical details of this device yet, bit I've rooted every phone that I've owned.

My phone's stock firmware broke my power button

Hello everyone. I would like to know if anyone experienced this, and if anyone has a solution (or at least an idea why).
The power button of my Samsung Galaxy A7 (2018) (SM-A750G) phone does not work at unlocking the screen (if it works in the rest of the functions such as opening the shutdown menu, entering recovery, etc.) when I am using stock firmware, but it works perfectly when using a GSI or any other custom OS.
Do you have any idea what could happen? It should be noted that this happened to me when my phone had the stock firmware and I had never modified my equipment at all... It just happened suddenly and for that reason I switched to a GSI. But now I would like to use the stock firmware, but I will not be able to do it with this "bug".
Thanks 4 the help
You mean unlocking or just turning the screen on an unlocked phone?
The app DoubleTap does away with using any buttons to turn the screen on/off. Simply 2x tap it. https://play.google.com/store/apps/...apk&pcampaignid=APPU_1_oD7zX7-SMMvesAWsh5_ADA
blackhawk said:
You mean unlocking or just turning the screen on an unlocked phone?
The app DoubleTap does away with using any buttons to turn the screen on/off. Simply 2x tap it. https://play.google.com/store/apps/details?id=com.vinance.lockdown&hl=en_US&gl=US&referrer=utm_source=google&utm_medium=organic&utm_term=double+tap+apk&pcampaignid=APPU_1_oD7zX7-SMMvesAWsh5_ADA
Click to expand...
Click to collapse
I mean turning on a phone screen. Since if it allows me to unlock it, but not turn it on.
P.S: I did not know the app you mention (it did not occur to me to look for something like that XD) I will try it, thanks for the link
gsosacristian said:
I mean turning on a phone screen. Since if it allows me to unlock it, but not turn it on.
P.S: I did not know the app you mention (it did not occur to me to look for something like that XD) I will try it, thanks for the link
Click to expand...
Click to collapse
That's strange. Have you tried remapping the button? Are there options to do so in settings?
Possibly another 3rd party apk remapped without you being aware of it?
I been using this app for over a year. To spite the ad warnings, it has none. Uses almost zero battery, never connects with the internet and is rock solid stable. Saves button life just keep the screen pointed away from your flesh when in your pocket to avoid accidentally taps.
Note: I never gave it administrator privileges as I never use a lock screen. So not sure about its behavior in that mode of operation.
blackhawk said:
That's strange. Have you tried remapping the button? Are there options to do so in settings?
Possibly another 3rd party apk remapped without you being aware of it?
I been using this app for over a year. To spite the ad warnings, it has none. Uses almost zero battery, never connects with the internet and is rock solid stable. Saves button life just keep the screen pointed away from your flesh when in your pocket to avoid accidentally taps.
Note: I never gave it administrator privileges as I never use a lock screen. So not sure about its behavior in that mode of operation.
Click to expand...
Click to collapse
I tried the app a few moments ago and it seems to work fine, the flesh thing is apparently configurable (assign the volume key, which is the most similar).
Regarding the mapping or 3rd party apks using the button, I see it almost impossible, not only because I don't use any app of this type (that reassigns keys) but in completely clean installations of stock firmware this happens to me (and I don't have any option key remapping that I know of).
It's very weird, at least for me. Because not only does it "break" to unlock, but it is only with stock firmware and even if I change the kernel (I tried using the quantum kernel) the key does not work when turning on the screen. But with the GSI it works without problems.
I even googled questions related to Always in display, power or something similar and nothing, there seems to be no conflicts.
gsosacristian said:
I tried the app a few moments ago and it seems to work fine, the flesh thing is apparently configurable (assign the volume key, which is the most similar).
Regarding the mapping or 3rd party apks using the button, I see it almost impossible, not only because I don't use any app of this type (that reassigns keys) but in completely clean installations of stock firmware this happens to me (and I don't have any option key remapping that I know of).
It's very weird, at least for me. Because not only does it "break" to unlock, but it is only with stock firmware and even if I change the kernel (I tried using the quantum kernel) the key does not work when turning on the screen. But with the GSI it works without problems.
I even googled questions related to Always in display, power or something similar and nothing, there seems to be no conflicts.
Click to expand...
Click to collapse
Make sure there's no remapping options for it in settings. If so it may be buried or under accessibility options... I've seen hidden Sammy drop down menus with no indication they are there until you double tap the top label. Swell.
Or simply bypass and double tap it!
blackhawk said:
Make sure there's no remapping options for it in settings. If so it may be buried or under accessibility options... I've seen hidden Sammy drop down menus with no indication they are there until you double tap the top label. Swell.
Or simply bypass and double tap it!
Click to expand...
Click to collapse
hehe, if it is true that there are really hidden things XD
Anyway, I am testing this app and if I see that it works I will be encouraged to install the stock firmware and by the way I will try to dig deep into the configuration in search of an option that I have overlooked
blackhawk said:
Make sure there's no remapping options for it in settings. If so it may be buried or under accessibility options... I've seen hidden Sammy drop down menus with no indication they are there until you double tap the top label. Swell.
Or simply bypass and double tap it!
Click to expand...
Click to collapse
Update:
I have installed the stock firmware and used the app you recommended, but no results: / The same thing keeps happening.
I have checked the accessibility options and there is nothing blocking the button :O
gsosacristian said:
Update:
I have installed the stock firmware and used the app you recommended, but no results: / The same thing keeps happening.
I have checked the accessibility options and there is nothing blocking the button :O
Click to expand...
Click to collapse
You enabled the appropriate buttons in it's settings?
I'm running Pie; it may not be compatible with 10 and up because of the overlay crap.
blackhawk said:
You enabled the appropriate buttons in it's settings?
I'm running Pie; it may not be compatible with 10 and up because of the overlay crap.
Click to expand...
Click to collapse
Oh! There is the problem, the firmware is Android 10
Bad luck for me, it will be time to return to a GSI momentarily XD
gsosacristian said:
Oh! There is the problem, the firmware is Android 10
Bad luck for me, it will be time to return to a GSI momentarily XD
Click to expand...
Click to collapse
Can't verify that but suspect it... Q sucks.
Lol, Google wants to protect you... I feel safer already. Not.
gsosacristian said:
Hello everyone. I would like to know if anyone experienced this, and if anyone has a solution (or at least an idea why).
The power button of my Samsung Galaxy A7 (2018) (SM-A750G) phone does not work at unlocking the screen (if it works in the rest of the functions such as opening the shutdown menu, entering recovery, etc.) when I am using stock firmware, but it works perfectly when using a GSI or any other custom OS.
Do you have any idea what could happen? It should be noted that this happened to me when my phone had the stock firmware and I had never modified my equipment at all... It just happened suddenly and for that reason I switched to a GSI. But now I would like to use the stock firmware, but I will not be able to do it with this "bug".
Thanks 4 the help
Click to expand...
Click to collapse
It seems like I have a similar problem. Do you have any recommendations ROM for SM - A750GN?
droidz94 said:
It seems like I have a similar problem. Do you have any recommendations ROM for SM - A750GN?
Click to expand...
Click to collapse
Personally, the one that I liked the most (and the one that works best) is the Google official (Android 10): https://developer.android.com/topic/generic-system-image/releases But one problem is that it is very outdated.
Anyway, here is a list of some GSIs that you can check and test which one works on your device: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
And here is a tutorial that worked well for me to install GSI: https://forum.xda-developers.com/t/guide-workings-gsi-best-treble-gsi-roms-for-a7-2018.4069121/
gsosacristian said:
Personally, the one that I liked the most (and the one that works best) is the Google official (Android 10): https://developer.android.com/topic/generic-system-image/releases But one problem is that it is very outdated.
Anyway, here is a list of some GSIs that you can check and test which one works on your device: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
And here is a tutorial that worked well for me to install GSI: https://forum.xda-developers.com/t/guide-workings-gsi-best-treble-gsi-roms-for-a7-2018.4069121/
Click to expand...
Click to collapse
Thanks! I'll try that
EXACTLY same problem here. I will not repet your words, I'll just say you described EXACTLY what is happening with my phone, a Galaxy A7 2018 (128GB RAM, Brazilian model - A750G/DS).
I can confirm that:
1 - Problem of screen never turning on after being turned off for the first time happens at all stock ROMs. Tried at android 10, downgraded to 9, couldn't downgrade to 8 because odin would not write the image, but the problem persisted on ALL stock ROMs up untill now.
2 - Problem DOES NOT happen at the TWRP recovery. Flashed TWRP just now, so I can flash a GSI, and I can turn the screen on or off as many times as I wish at TWRP screen, without any problem.
These informations corroborate, almost without a shadow of doubt, the idea that this is actually a software problem, not a hardware one. I'm gonna flash the google 10 GSI now, with quantum kernel V3 (seems to be a requirement, I would like to make as litle changes as possible) and post the results.
Having a hard time installing the GSI, gets stuck at bootloop all athe time...
joaodalvi said:
Having a hard time installing the GSI, gets stuck at bootloop all athe time...
Click to expand...
Click to collapse
[GUIDE][A-ONLY][A750x] Guide on How to flash GSI (Updated: 10.06.2019)
I'm not responsible for whatever damage this could possibly cause to your device. If you appreciate the work i have done, Feel free to buy me a cup of coffee @paypal Welcome to GSI For Galaxy A7 2018 ONLY FOR A750F/A750FN/A750GN Some...
forum.xda-developers.com
Try this. You need flash a "GSI Boot Fix" to use a GSI on A750.

Categories

Resources