Related
Hello,
First let me say thanks for all the amazing roms and for making my device a 100 times better. I am running the second instalment of the xoom dev aokp (now official!) i see that is supports Long press volume to change songs when the screen is off, however i cant seem to get it to funciton. I found the setting that enables screen wake w/ volume keys but not to change songs... i also dont see a native music player so i am using google music. Please help. any feedback would be appreciated. Thanks again.
CM10 has that very same feature and it works perfectly fine on my VGS3. I know AOKP has more features and mods then CM10 (so i've heard) but if you're looking for that specific feature then why not go with CM10. This is just a confirmation that the volume rocker track skip feature is definitely working on the rom i'm using (CM10). Just thought I'd let you know. The version I'm using is Here
Sunnyboy167 said:
CM10 has that very same feature and it works perfectly fine on my VGS3. I know AOKP has more features and mods then CM10 (so i've heard) but if you're looking for that specific feature then why not go with CM10. This is just a confirmation that the volume rocker track skip feature is definitely working on the rom i'm using (CM10). Just thought I'd let you know. The version I'm using is Here
Click to expand...
Click to collapse
the thing is, i love the ROM I'm on Beantown jellybean build 8 to be precise, and volume up to skip is a feature of that ROM. I think it is a great feature.
I did another mod to include acid sound enhancements and have lost the volume rocker mod. I was hoping I could add the volume rocker mod back in manually to try and get both.
Is it not possible to add the mod on its own?
Flashlight apps make AOKP for Verizon GS3 reboot
Hi.
First of all, thanks to the developers of AOKP for making this terrific ROM.
I installed it 5 days ago, and have had only 1 issue: if I install, and then try to use a flashlight app, it causes the GS3 to reboot.
I tried it with 3 different flashlight apps that I had successfully tested on the GS3 when it was unrooted with the OTA 4.1.1 ROM update; and, with the 4.1.1 rooted stock ROM.
Those apps are
Flashlight: https://play.google.com/store/apps/...me.ledflashlight.washer&feature=search_result
TESLA LED Flashlight: https://play.google.com/store/apps/details?id=com.teslacoilsw.flashlight&feature=search_result
Flashlight HD LED: https://play.google.com/store/apps/details?id=ch.smalltech.ledflashlight.free&feature=search_result
I have already done a factory wipe, cleaned the regular and Dalvik caches and re-installed each app fresh.
Despite this, the flashlight problem persists.
I always make a lot of use of my smartphone flashlight; so, this is a huge inconvenience.
Any suggestions?
Thanks, in advance!
PJ Arts
edit
jaguarpaw said:
Hello,
First let me say thanks for all the amazing roms and for making my device a 100 times better. I am running the second instalment of the xoom dev aokp (now official!) i see that is supports Long press volume to change songs when the screen is off, however i cant seem to get it to funciton. I found the setting that enables screen wake w/ volume keys but not to change songs... i also dont see a native music player so i am using google music. Please help. any feedback would be appreciated. Thanks again.
Click to expand...
Click to collapse
Hold on, are you saying there's an official AOKP build out? And I haven't flashed it???
Danno131313 said:
Hold on, are you saying there's an official AOKP build out? And I haven't flashed it???
Click to expand...
Click to collapse
Rootzwiki my friend..
Sent from my SCH-I535 using xda app-developers app
Danno131313 said:
Hold on, are you saying there's an official AOKP build out? And I haven't flashed it???
Click to expand...
Click to collapse
It's only a preview build. Nothing official yet really. They're more like alphas I think.
Sent from my SCH-I535 using xda app-developers app
I'll keep it short for now and update this topic start as needed.
Here you can find instructions on downloading & installing a preliminary version of Cyanogenmod 10 for Alcatel OT-995.
I'm fairly happy with the progress I've made recently, though it should not be considered stable. Some features are known to be broken, for others it's your job to point out missing functionality.
Links of interest:
Installation instructions
Downloads
Installation instructions
Changelog
Issue tracker
Source code
Please read the installation instructions carefully
Most basic device functionality should be working. A list of known issues (incomplete):
Video mode camera overlay may bug; workaround: launch regular camera, switch to video
Occasional artifcats on window transitions
Hardware video decoding is unavailable, use MX Player or VLC instead.
Not implemented: HDMI out, FM radio
The custpack partition is used to store /system/app, that's why a separate CWM images is required to install CM10 releases. This also means it's backup/restore functionality is currently broken. Advanced backup might allow you to just backup/restore /data though.
You may mention any broken functionality here, but I prefer receiving an issue report here, as that allows me to keep track of things more easily.
Do check whether your specific issue has already been reported, and try to be as detailed as possible.
You should be comfortable flashing/recovering your device - if not, this might not be for you yet - wait until we smoothen things out
Bring on the feedback. I'm sure I missed something in the guides or release.
Disclaimer: I'm still working on a best-effort basis, every now and then my spare time is severely limited..
Nice - nice indeed.
many thanks for taking time and developing for ot 995.
it was just today that i had installed ics and now this??? my lucky day...
anyway, will help you in reporting bugs.... keep rocking.....
extra great news ! Iuss, i'm downloading it right now and flashing it Thank you very much for this release (even though is preliminary)
EDIT: I flashed it. Booting was quick. I was setting the phone and i restarted the phone.
So at first touch everything looks nice
- Scrolling is a bit strange (is scroll downward the screen goes up).
- The phone is charging and the LED is not lit.
- Camera works (photos, video, and panorama with some greenish overlay).
- Data not working. Confirmed.
- Wifi works
Tnx again iuss!
Thanks for the hard work, I'm sure this will be WAY better than Alcatel's ICS release. Just love me some jellybeans :silly:
Just booting it up now. Nice boot logo, I haven't seen that one before. Yours?
Yes, thanks very very much!
Envoyé depuis mon Galaxy Nexus avec Tapatalk
Very nice indeed.
Testing it right now
First of all. Fantastic job! Well done! I tested the rom.
My experience was
# My camera and video worked pretty good. It took pictures and video was working. Maybe a little problem with the focus on Video. And some greenish with the transition between taken picture and camera.
# Wifi, Phone works
# No Data/3G
# Led Backlight keys dosen't work when u wake the phone up from sleep. But if u change the light settings the Keys lights up, and works.
# Multi touch works good and responsive.
Thanks alot an keep up the good work!
It seems very nice, but I'm confused because I was asked to unlock my sim again which was done when I bought it months ago, and it didn't even work with that code. What could be the cause, and would it work if I went back to ICS?
tcmixx said:
# Led Backlight keys dosen't work when u wake the phone up from sleep. But if u change the light settings the Keys lights up, and works.
Click to expand...
Click to collapse
tcmixx, can u be more specific about where is that option, because i'm blind
aleksandar.1 said:
tcmixx, can u be more specific about where is that option, because i'm blind
Click to expand...
Click to collapse
You should adjust the settings for your screen brightness. What i did was that I used the quick settings widget. There's an option for brightness click that one, and the backlight keys should light up.
Awesome start...
Iuss, CM10 is great. It has a few quirks, but so far I am loving it.
I have run into one issue, I can't create a Google account. I ran recovery, booted CM10, and went to create my Google account under System settings > Accounts and there is no option for Google, just Corporate and Email. Am I missing something?
I was able to manually download Titanium and restore many of my apps, but several won't load. That's too be expected though. But being able to create a Google account is pretty important to me.
If anyone can point me in the right direction it would be greatly appreciated.
Somebody wanna tell me where to find the" log cat" file please?
Sent from my OT-995 using xda premium
tumaini418 said:
Somebody wanna tell me where to find the" log cat" file please?
Sent from my OT-995 using xda premium
Click to expand...
Click to collapse
Try the automated tool at my siggy, it's easy to use
mightyjackstar said:
Iuss, CM10 is great. It has a few quirks, but so far I am loving it.
I have run into one issue, I can't create a Google account. I ran recovery, booted CM10, and went to create my Google account under System settings > Accounts and there is no option for Google, just Corporate and Email. Am I missing something?
I was able to manually download Titanium and restore many of my apps, but several won't load. That's too be expected though. But being able to create a Google account is pretty important to me.
If anyone can point me in the right direction it would be greatly appreciated.
Click to expand...
Click to collapse
Did you flash gapps? If not do that,then see if you're still not able to start your account. I flashed it before I booted for the first time and not only did I get prompted to start/login to an account, most of my apps were reinstalled.
Sent from my OT-995 using xda premium
tumaini418 said:
Did you flash gapps? If not do that,then see if you're still not able to start your account. I flashed it before I booted for the first time and not only did I get prompted to start/login to an account, most of my apps were reinstalled.
Sent from my OT-995 using xda premium
Click to expand...
Click to collapse
tumaini418, yes, I did (I followed iuss' instructions including the download links). Another odd thing that has happened is I have lost the ability to access SD Card through USB.
Fortunately I backed ICS before setting CM10, so I was able to Recover back to ICS, and I suddenly have access to my SD Card again. I'm going to stay with ICS for tomorrow as I must have a working phone, but I'll try ICS again later this weekend.
Could you say me if there is a CM9 build which should be totally functional?! It help me to wait CM10!
Envoyé depuis mon Galaxy Nexus avec Tapatalk
emic2 said:
Could you say me if there is a CM9 build which should be totally functional?! It help me to wait CM10!
Envoyé depuis mon Galaxy Nexus avec Tapatalk
Click to expand...
Click to collapse
There is a Alcatel official ICS rom that iuss fixed so that anyone with this phone can use, but no CM9.
I almost forgot, the same rom is available in a tweaked and stripped version also. Thanks to mistercheese.
Sent from my OT-995 using xda premium
tcmixx said:
# My camera and video worked pretty good. It took pictures and video was working. Maybe a little problem with the focus on Video. And some greenish with the transition between taken picture and camera
Click to expand...
Click to collapse
These are the transition artifacts I meant.
# No Data/3G
Click to expand...
Click to collapse
As I feared. I'll try configuring an apn myself and see if I can fix it.
# Led Backlight keys dosen't work when u wake the phone up from sleep. But if u change the light settings the Keys lights up, and works.
Click to expand...
Click to collapse
That was supposed to work, seems I had my brightness control set to 'half' (or whatever it is) - then it does work. Will replace the proprietary liblights - it appears to be broken and/or depend on framework hacks.
It seems very nice, but I'm confused because I was asked to unlock my sim again which was done when I bought it months ago, and it didn't even work with that code. What could be the cause, and would it work if I went back to ICS?
Click to expand...
Click to collapse
I'm confused - what do you mean by unlocking? A network lock, or the SIM PIN?
mightyjackstar said:
I have run into one issue, I can't create a Google account. I ran recovery, booted CM10, and went to create my Google account under System settings > Accounts and there is no option for Google, just Corporate and Email. Am I missing something?
Click to expand...
Click to collapse
As other said, you either forgot to flash gapps, or used the wrong CWM image when flashing.
Could you say me if there is a CM9 build which should be totally functional?! It help me to wait CM10!
Click to expand...
Click to collapse
Previous releases (CM9 included) had less functionality.
iuss concerning the phone asking for a sim pin. I got the same thing when switching from airplane mode. It's a popup. I tried to enter a pin I used in the screen lock before, but of course that wasn't it. It's very confusing because my sim has never had a pin to unlock it.
Sent from my OT-995 using xda premium
Hey Guys,
as CM10.1 posts are flooding the two CM10 threads I'm opening a new discussion Thread here so that you/we can keep the CM10 Threads for CM10.
Feel free to post videos & screenshots, I will add some of them to the OP if you want me to!
I also would encourage you to tell me what works & what doesn't, please use a proper listing method therefor.
As always all credit goes to intervigil, xkonni & the others behind CM10(.1)!
said/found to be working / not working:
Screen tearing (nearly unnoticeable)
Working: everything else
I'm looking forward to get CM 10.1
Thanks for the 10.1 thread!
So the first question I got the 10.1-20121210-experimental and got no developers and power options Besides the camera and this issue, it works great! Thanks to all developers!
Just tab 7 times on "Build name" to become developer,
gesendet von meinem HTC One S mit Tapatalk
All is allowed to contribute for a better clarity.
Voice search within apps won't work. (Any voice assistant) [Still able to make/recieve calls]
Lag spike once in a while
Screen tearing
No camera applications as all.
BT problem
No audio when connected headphones (From what I hear someone confirm this) a13xemz's quickfix from the playstore Playstore: SoundAbout
Quick setting menu can be a bit restless while downloading apps and trying access it. (Setting vanish and come back)
Hope GPS and Nav will work, hopefully some people can tests this out to make sure. While all of this is being resolved
For those expirencing issues with headphones not working this app/widget fixes the problem. https://play.google.com/store/apps/details?id=com.woodslink.android.wiredheadphoneroutingfix
Sent from my One S using xda app-developers app
I can confirm that the issues mentioned in post 6 cover everything I've noticed so far.
Fyi, I dirty flashed over CM10 and the camera app was present and had the new icon, it just didn't work. I thought it was odd that the new gallery didnt seem to sync to Picasa either (like the current cm10 gallery) because when i used the leaked 4.2 camera, the gallery sync worked great.
a13xemz said:
For those expirencing issues with headphones not working this app/widget fixes the problem. *removed URL, under 10 posts. See original quote*
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
I can confirm that this workaround fixes (forces) headphone usage.
Also, attached some screenshot goodies for yall
i just did a dirty flash and flash the boot.img, and when it boots its stuck on HTC but then again when i hit the power button off, what it does is off but when i push the power back on, and hit the screen the buttons light up how come?
klutch said:
i just did a dirty flash and flash the boot.img, and when it boots its stuck on HTC but then again when i hit the power button off, what it does is off but when i push the power back on, and hit the screen the buttons light up how come?
Click to expand...
Click to collapse
Because dirty flash is not recommended. Try a full wipe and you will be fine.
well i did that and still the same bro, but now when i went to the previous backed up its looping
klutch said:
well i did that and still the same bro, but now when i went to the previous backed up its looping
Click to expand...
Click to collapse
What version of TWRP do you have? I had the same problem and had to get the latest to properly restore my backup.
el_smurfo said:
What version of TWRP do you have? I had the same problem and had to get the latest to properly restore my backup.
Click to expand...
Click to collapse
TWRP v2.3.1.0
and this is how it stays
well now i guess i have to find a way to take that loop of cM its not passing no matter wat cm10 dates or boot.img
Michael1101 said:
Thanks for the 10.1 thread!
So the first question I got the 10.1-20121210-experimental and got no developers and power options Besides the camera and this issue, it works great! Thanks to all developers!
Click to expand...
Click to collapse
To get developer options, tap the build date 7 or so times.
only issue after fresh install, full wipe
is remapping of hw keys--no issue on other roms
if i chose long press on recent app as voice leaving short press menu
and long press home screen as recent apps--I get voice for any press of recent apps and home key
i can get recent apps to be menu and home stays as home
then no recent apps
hope this is not confusing and mentioned before--did look around
did wipe caches and rebooted
maybe only option is too reflash, but no recent apps is not a big deal as rom runs very smooth and I have my voice turns in GMaps with street names spoken now. street names were not mentioned on other roms for me for a while now--
forget it i found the problem ill wait till the next CM10.1 arrives
klutch said:
forget it i found the problem ill wait till the next CM10.1 arrives
Click to expand...
Click to collapse
how did you fix it klutch
Here is an app that allows you to hold your back button to kill the currently open application.
If popularity is high enough, I will update it with things like whitelist etc.
If you use a Samsung device, the only problem is that you can't show the MultiWindow bar anymore. I will work on a fix for it. I only made this because xposed doesn't work on Samsung Lollipop yet so this is what I wanted until it is. Once it works, I prolly won't ever touch this app again.
Thanks everyone!
UPDATE:
- Performance improvement
useful, thanks for this!!!!
Great job! I've been missing this feature since I switched to Lollipop. Thanks!
hi,
It seems to be working on CM12 but a little too good
Apps get killed right away when i press "back"whatever time-out i set in the settings.
Droidphilev said:
hi,
It seems to be working on CM12 but a little too good
Apps get killed right away when i press "back"whatever time-out i set in the settings.
Click to expand...
Click to collapse
I dont know i dont have cm12. i know cm12 has a default native option to hold back to kill maybe that is enabled?
elesbb said:
I dont know i dont have cm12. i know cm12 has a default native option to hold back to kill maybe that is enabled?
Click to expand...
Click to collapse
Hello, CM12 with standard navbar (3 buttons) doesn't have that setting. It s only implmented in roms with navbars with extra settings like opening an app etc etc
Having Trouble
I'm having a similar problem where even a single tap on the back button is closing the app. I have a rooted Galaxy S4 running Android 4.4
Droidphilev said:
Hello, CM12 with standard navbar (3 buttons) doesn't have that setting. It s only implmented in roms with navbars with extra settings like opening an app etc etc
Click to expand...
Click to collapse
ndg1988 said:
I'm having a similar problem where even a single tap on the back button is closing the app. I have a rooted Galaxy S4 running Android 4.4
Click to expand...
Click to collapse
So this is happening when using the navbar and not the physical buttons?
It seems like the up action isn't being triggered. I could try to implement maybe a double click back to kill option. Ill try to debug on my 5.0 emulator that uses the navbar and see if i can figure anything out. Weird how that's happening.
elesbb said:
So this is happening when using the navbar and not the physical buttons?
It seems like the up action isn't being triggered. I could try to implement maybe a double click back to kill option. Ill try to debug on my 5.0 emulator that uses the navbar and see if i can figure anything out. Weird how that's happening.
Click to expand...
Click to collapse
hello again,
No, i dont use the navbar In cm12 (disabled) I use hardware buttons. If ndg1988 uses stock then he doesn't have a navbar so i guess he uses the hardware buttons too
Droidphilev said:
hello again,
No, i dont use the navbar In cm12 (disabled) I use hardware buttons. If ndg1988 uses stock then he doesn't have a navbar so i guess he uses the hardware buttons too
Click to expand...
Click to collapse
Hm, I truly don't know then. I really would need the device in hand to test with. I could try to do testing by sending you a file with loads of debug information in it. Would you mind that?
Good News
elesbb said:
So this is happening when using the navbar and not the physical buttons?
It seems like the up action isn't being triggered. I could try to implement maybe a double click back to kill option. Ill try to debug on my 5.0 emulator that uses the navbar and see if i can figure anything out. Weird how that's happening.
Click to expand...
Click to collapse
I was just an idiot that assumed the activation time was in units of seconds, not milliseconds. This may be what most people are having trouble with. It works well now, so thank you and keep up the good work.
ndg1988 said:
I was just an idiot that assumed the activation time was in units of seconds, not milliseconds. This may be what most people are having trouble with. It works well now, so thank you and keep up the good work.
Click to expand...
Click to collapse
Haha okay good. Nice one It does say "milliseconds"
elesbb said:
Hm, I truly don't know then. I really would need the device in hand to test with. I could try to do testing by sending you a file with loads of debug information in it. Would you mind that?
Click to expand...
Click to collapse
no, but it will take a while. i need to test multirom on my device and i have have to finish the translation of an app first.
Thanks mate
Awesome - best thing that can happen to a rooted stock rom.
btw its labled "Main Activity" in App Drawer, not "Hold Back To Kill"
Droidphilev said:
no, but it will take a while. i need to test multirom on my device and i have have to finish the translation of an app first.
Click to expand...
Click to collapse
What delay are you setting for it in the settings?
leechseed said:
Awesome - best thing that can happen to a rooted stock rom.
btw its labled "Main Activity" in App Drawer, not "Hold Back To Kill"
Click to expand...
Click to collapse
Yup. Realized that after releasing and didn't care too much about it. In the next update (if ever one would exist) i'll fix it.
elesbb said:
What delay are you setting for it in the settings?
Click to expand...
Click to collapse
I have tried 2, 3, 4 and 5 seconds
Did you put in 2 or 2000? (check post #11)
leechseed said:
Did you put in 2 or 2000? (check post #11)
Click to expand...
Click to collapse
DAMNED!!!!!!!!!!!!!!!!!!!!!!!!!!
Thank you, leechseed! Was making the same mistake.
OP please forget all my postings. Working very well!!!
leechseed said:
Did you put in 2 or 2000? (check post #11)
Click to expand...
Click to collapse
Droidphilev said:
I have tried 2, 3, 4 and 5 seconds
Click to expand...
Click to collapse
Droidphilev said:
DAMNED!!!!!!!!!!!!!!!!!!!!!!!!!!
Thank you, leechseed! Was making the same mistake.
OP please forget all my postings. Working very well!!!
Click to expand...
Click to collapse
That is why I asked. I have it set to milliseconds because I have mine set to a value of 200 milliseconds
Love seeing everyone helping everyone. Thanks guys!!!
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.