Related
I have had the payed version of Lock 2.0 since there was an option to buy but since I got my Nexus One it has now become pretty much unusable. The sad part is that it is better than the lock button that is on the top of the phone cause it lets you bring up the lock screen by pressing your track ball. I love all the different back grounds and sounds you can download and how they stay in a folder and not in your app draw (which is really annoying). Now the thing I don't like is that when you press the volume buttons when the phone is locked you can and will turn down or up the volume on accident and this is why this app is now unusable. Can it really be that hard to add an option to disable these buttons? I have emailed Android Apps and they say the reason the volume button does that is for when you are listening to music and thats great but whats the use if when you get a call or text and you can't hear it cause you turned the volume down to 0 on accident. I emailed them today again and asked if they could update their app and I hope they do. The reason I started this thread is so anybody could comment on this problem with I have to say is probably my second favorite app on the market. I will also email them a link to this thread so they can see what everybody thinks. One more thing on another lock app LockBot when you press the volume button the sound does not get turned down but I don't want to really pay for two apps that can do the same thing. Edit: OK they fixed it but their is a new problem with the home button.
isjr said:
I have had the payed version of Lock 2.0 since there was an option to buy but since I got my Nexus One it has now become pretty much unusable. The sad part is that it is better than the lock button that is on the top of the phone cause it lets you bring up the lock screen by pressing your track ball. I love all the different back grounds and sounds you can download and how they stay in a folder and not in your app draw (which is really annoying). Now the thing I don't like is that when you press the volume buttons when the phone is locked you can and will turn down or up the volume on accident and this is why this app is now unusable. Can it really be that hard to add an option to disable these buttons? I have emailed Android Apps and they say the reason the volume button does that is for when you are listening to music and thats great but whats the use if when you get a call or text and you can't hear it cause you turned the volume down to 0 on accident. I emailed them today again and asked if they could update their app and I hope they do. The reason I started this thread is so anybody could comment on this problem with I have to say is probably my second favorite app on the market. I will also email them a link to this thread so they can see what everybody thinks. One more thing on another lock app LockBot when you press the volume button the sound does not get turned down but I don't want to really pay for two apps that can do the same thing.
Click to expand...
Click to collapse
What rom are you using?
Cyanogens latest has an option for trackball wake-up (and of course that mod can be applied to other roms as well) if that is indeed the biggest thing about it you like. I personally never saw the need to change my lockscreen from stock, but can understand why some people do.
I am using the stock rom, I didn't want to root this phone since you void your warranty and mine is pretty messed up I should get a replacement this week. Also I am glad Cyanogen added that and that tells you it is a problem in the stock or he wouldn't have had to improve on it. So people like me only have the option of downloading an app to get the same results. Also I have used a rooted phone before, I had been using my Google Ion rooted for about 6 months before I got my Nexus One.
Ok I just got an email from the developer and they have disabled the volume buttons by default on the new version that was fast. Now there is a weird problem where even after you set the Launcher as the default for your home button it still keeps opening Lock 2.0, its really annoying but I already told them so I'm sure they will fix it. Now if only Google would respond like this for their "Support Forums" on fixing the 3G and Touchscreen problems the world would be a better place.
I understand the issue with the volume keys. I don't listen to music so i installed the app (ringer mode locker) by kaa from the market. It overrides the system setting and locks on your choose of settings: vibrate, ringer silent etc. If you volume up or down it stays on you set point. I like if because it is not a background app using extra battery trying to monitor a set point.
isjr said:
Ok I just got an email from the developer and they have disabled the volume buttons by default on the new version that was fast. Now there is a weird problem where even after you set the Launcher as the default for your home button it still keeps opening Lock 2.0, its really annoying but I already told them so I'm sure they will fix it. Now if only Google would respond like this for their "Support Forums" on fixing the 3G and Touchscreen problems the world would be a better place.
Click to expand...
Click to collapse
Please don't critisize Google like this, 3G issues and Touchscreen problems are not simple applications in which code can be modified to turn off the "Volume" buttons.. I've noticed the employees on their forums try to solve things to the best of their abilities - but Google can not just correct everything as if it takes a small flick of the wrist, or click of a mouse...
Honestly I don't see how they will fix any 3G issue entierly without modifiying the insides of the phone.. guess I dont know enough about phones to make such a conclusion anyways.
isjr said:
Now there is a weird problem where even after you set the Launcher as the default for your home button it still keeps opening Lock 2.0, its really annoying but I already told them so I'm sure they will fix it.
Click to expand...
Click to collapse
I emailed them about this a couple of weeks ago. I told them exactly that and I got a "Steve Jobs-like" response lol..
"Something is wrong with your phone."
I even posted about it a couple of times in the Q&A section but got no responses. I'm glad to see someone on a stock ROM is experiencing the same issue because I thought it was due to using CM. Are you using an auto task-killer?
!!
I want to get rid of my lockscreen! its anoying having to press the power button then unlock the screen!
frankzua77 said:
I want to get rid of my lockscreen! its anoying having to press the power button then unlock the screen!
Click to expand...
Click to collapse
Get "KeyGuard disabler" from the market. It costs 1.49 but does exactly what you want. I'm sure there are free versions of similar software too but this is only one i've ever tried.
!!
gIMpSTa said:
Get "KeyGuard disabler" from the market. It costs 1.49 but does exactly what you want. I'm sure there are free versions of similar software too but this is only one i've ever tried.
Click to expand...
Click to collapse
________________
wow dude just tried it! works perfect! thanks man!
Meh....
After installing and trying to use it, I finally gave up. It has the potential to be by far one of the best android apps. The developer has designed programs that mesh with android so natively that I am jealous of his understanding. But even after a few reinstallations, this program never delivered. A replacement lockscreen must be more than just pretty. It wasn't sized right for the Nexus One screen and constantly froze "Updating List", even when I was just trying to unlock. The "Updating List" freeze causes a loop that just recalled the freeze when I hit home. There is no escape short of hitting menu, more, home, then selecting my home screen program. I would consider that a lock screen fail if I have to navigate a menu to select a home screen instead of sliding the sexy little slider over. I hate taking refunds from the market, but Lock 2.0 needs more work. If I see anyone saying it has been adjusted for the N1 screen and the home bug has been fixed, I'll buy it again, but until then, I'll stick with the just weather and toggle widgets.
I hear that Lock 2.0 disables notifications on the Nexus One. Does anybody know of any apps thats just as attractive as Lock 2.0 that doesn't disable notifications or freeze.. etc.. (something iphone-ish i guess)
Any news about the home button bug bypassing the lock screen in Lock 2.0?
As far as a can tell its been working good and the dev added the option to clear the home screen default if it does it again. Its pretty sad that he left it messed up for months until I sent him the link to this thread.
Sent from my Nexus One
isjr said:
As far as a can tell its been working good and the dev added the option to clear the home screen default if it does it again. Its pretty sad that he left it messed up for months until I sent him the link to this thread.
Sent from my Nexus One
Click to expand...
Click to collapse
Thanks, but I was referring to another bug (unless I'm totally mistaken):
When you turn on your nexus and you're still on Lock 2.0 lock screen, if you press the home button, it unlocks the phone without having to use the slider.
Hope this was clear...
I am running Dman's rooted stock UCLB3 with Entropy's DD and Voodoo Lagfix. I love the setup but one this is really bothering me: I can't set the screen security time. I like the screen to go off in 15 - 30 seconds, but I want to be able to decide how long it will be until I have to use the security unlock. Now, there used to be a setting for this under Location and Security, but for some reason it is no longer there. Is it this ROM or is this missing from all 2.3.6 builds (i.e. stock)?
In case you aren't following me, I am attaching two screenshots, one from Samsung's website, the other from my phone. As you can see there is no "Timeout" menu on my phone. Was this somehow stripped from Dman's ROM (not impossible since the android.policy.jar file - the one that I believe is related to this menu - sometimes encounters issues from deodexing) or is this feature just gone from the phone? If it was stripped, how might I go about getting it back?
This is driving me mad right now, so I'd love to hear a definitive answer.
The setting that you are looking for can be found under Settings / Display. It wasn't stripped, you're just not in the correct menu.
No, that is a different setting. You'll notice that the display setting is to determine when the display will go to sleep (when it will automatically turn off), the setting I am talking about determines when the screen will lock after the screen turns off.
There are two programs with similar functions: Delayed Lock and JuiceDefender Ultimate. However, I suspect that the phone setting is still partially alive somewhere because both programs seem to wreak havoc with whatever settings are now default.
Oh, okay, now I understand. That feature isn't available in stock UCLB3, and there were no issues when deodexing.
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2
Thanks. That's basically the answer I wanted. I've been poking through the guts of both the stock and rooted builds trying to find out what happened. It is really irritating that it's not there (well, for me it is!) because the security screen seems to have a mind of its own, particularly if you introduce alternative lockers into the mix.
For anyone who may be interested, you may be able to set the timeout by editing values in the android.policy.jar file in framework folder. Search around, you'll find instructions. I haven't tried this.
The two apps I have found that enable this functionality are Delayed Lock and Juice Defender Ultimate. However, neither app works well with 3rd party security locks such as Go Locker. The lock delay apps trigger the system security screen lock so you may have to go through as many as 3 screens before you get to your home screen.
Sorry, there is one other app: Password Delay. I did not try this because I want to use a pattern lock. PD does not work with patterns.
Yeah, join the club lol. I just learned to deal with it after a while. But I hear you. Tried looking for some alternative ideas... and I just kept unlocking everytime.
Sent from my A500 using Tapatalk 2
I remember shortly after getting my Nexus 5 that I noticed a hand icon in quick settings for do not disturb setting..
I went to use it the other day and it had disappeared. I had unlocked and rooted and also flashing custom kernel.
So as I couldn't find any setting to re enable, and suspecting it might have been something I had done, I downloaded Google nexus 5 image and reflashed to stock, but still no joy .
Any advice ?
Sent from my Nexus 5 using xda app-developers app
I don't remember seeing anything like this, as I recall. But I am disappointed that the Quick Settings are not really all that quick. Tapping things like Bluetooth or Wifi takes you to the full settings page for that feature instead of simply toggling it on and off as I usually am trying to do.
rochrunner said:
I don't remember seeing anything like this, as I recall. But I am disappointed that the Quick Settings are not really all that quick. Tapping things like Bluetooth or Wifi takes you to the full settings page for that feature instead of simply toggling it on and off as I usually am trying to do.
Click to expand...
Click to collapse
If you hold the icon instead of clicking it, it turns on the radio. For example, pressing WiFi takes you to the WiFi settings page, but long holding the icon will just turn it on. Same for BT.
As for the Do not Disturb, I've never seen that. I know iOS has it...and I'm sure there are Google Play apps to do something similar, but Android doesnt have that stock.
Sadly it doesn't exist in stock android. They really have to add that. Every other platform has it except stock android.
EDIT: Yes, I know touchwiz and sense have it.
mdandashly said:
If you hold the icon instead of clicking it, it turns on the radio. For example, pressing WiFi takes you to the WiFi settings page, but long holding the icon will just turn it on. Same for BT.
Click to expand...
Click to collapse
Thanks. It makes me wonder though how the "average" person is ever supposed to learn little things like this -- certainly not intuitive IMO.
Mystery solved, just realised that I had switched back to my HTC One with a leaked version of sense 5.5
Sent from my Nexus 5 using xda app-developers app
I found that you can press the power button and from that menu you can set the volume to vibrate or mute. Not sure if this is what you were looking for.
Thankfully custom ROMs will be here soon (in more complete/stable forms) to make all of these annoying issues better. Stock Android lacks some seriously useful little touches, but that's why we got unlocked devices....
Sent from my Nexus 4
About three months ago my Pixel 2 (purchased new from Google) began having an issue where it becomes unresponsive or extraordinarily delayed on responding. It almost always happens when I'm waking the phone up from being locked. When it happens, the phone will eventually unlock but everything reacts several seconds after contact (power button, taps, swipes). A reboot or power down fixes the problem, but is always necessary.
I switched to Project Fi around that time and thought it had something to do with the switching between CDMA and GSM (Sprint/US Cellular vs T-Moble) towers, but I've switched to T-Mobile (a solely GSM provider) since and the problem persists.
I am running Android Pie (stock). My bootloader is unlocked and I do have Magisk installed. No TWRP. I don't have any obvious troublemakers installed (like Xposed, for example) and only a few apps that even use root (Cerberus, Adaway, and Nova Launcher).
I have heard about the Pixel 2 XL having a hardware issue that results in unresponsiveness and that ultimately requires sending in the device for a replacement. Is this the same thing?
Any advice would be much appreciated. If it would be helpful, I can produce logs, but I'll have to wait until it happens again to offer logs that might contain clear indications of what might be happening.
- Computerslayer
computerslayer said:
About three months ago my Pixel 2 (purchased new from Google) began having an issue where it becomes unresponsive or extraordinarily delayed on responding. It almost always happens when I'm waking the phone up from being locked. When it happens, the phone will eventually unlock but everything reacts several seconds after contact (power button, taps, swipes). A reboot or power down fixes the problem, but is always necessary.
I switched to Project Fi around that time and thought it had something to do with the switching between CDMA and GSM (Sprint/US Cellular vs T-Moble) towers, but I've switched to T-Mobile (a solely GSM provider) since and the problem persists.
I am running Android Pie (stock). My bootloader is unlocked and I do have Magisk installed. No TWRP. I don't have any obvious troublemakers installed (like Xposed, for example) and only a few apps that even use root (Cerberus, Adaway, and Nova Launcher).
I have heard about the Pixel 2 XL having a hardware issue that results in unresponsiveness and that ultimately requires sending in the device for a replacement. Is this the same thing?
Any advice would be much appreciated. If it would be helpful, I can produce logs, but I'll have to wait until it happens again to offer logs that might contain clear indications of what might be happening.
- Computerslayer
Click to expand...
Click to collapse
Do you have the navbar hidden by any chance
crixley said:
Do you have the navbar hidden by any chance
Click to expand...
Click to collapse
Well, I have Nova set up to hide the dock unless I swipe up (or down) on it. I can't seem to find a setting about hiding the navbar. Where should I be looking to check?
computerslayer said:
Well, I have Nova set up to hide the dock unless I swipe up (or down) on it. I can't seem to find a setting about hiding the navbar. Where should I be looking to check?
Click to expand...
Click to collapse
Did you install any apps to hide your navigation bar? Is it always visible? Immersive mode apps for example
crixley said:
Did you install any apps to hide your navigation bar? Is it always visible? Immersive mode apps for example
Click to expand...
Click to collapse
We're talking about the back button and the new pill gesture button, right? If so, then no I haven't installed anything to hide those: they are always visible.
Well, after 24 hours, I had the issue resurface. Unfortunately, the logging app I was using (matlog) froze up with the phone and produced a blank text file. While rebooting restored normal function of the phone, I can't produce a log as a result.
It occurs to me that while I am not disabling the navbar, I do use a function of the Cerberus anti-theft app to disable the notification bar while locked. Could this be the source of my issue? If so, is there any way to confirm this?
In the meantime, I've disabled that function and will see if the lock-up occurs again.
I'm curious where you were going with the question about the navbar. Could you tell me more about what you were thinking it might have been?
I went ahead and disabled the 'block status bar' function of the Cerberus app and the problem has not resurfaced in over two days (it was occurring several times daily). Although I can't definitively prove it, I think the culprit was the app.
Thanks for the time and assistance!
computerslayer said:
I went ahead and disabled the 'block status bar' function of the Cerberus app and the problem has not resurfaced in over two days (it was occurring several times daily). Although I can't definitively prove it, I think the culprit was the app.
Thanks for the time and assistance!
Click to expand...
Click to collapse
Sorry I didn't get back to you I read this a while back and totally thought I responded. Yeah anything that hides the status bar or navbar from the system UI at all times is known to cause wake issues. On my essential phone it would require me to restart it to actually get the screen to come back on. It's called the deep sleep of death or something haha
crixley said:
Sorry I didn't get back to you I read this a while back and totally thought I responded. Yeah anything that hides the status bar or navbar from the system UI at all times is known to cause wake issues. On my essential phone it would require me to restart it to actually get the screen to come back on. It's called the deep sleep of death or something haha
Click to expand...
Click to collapse
Hello Crixley,
No worries at all - I'm always grateful when anyone responds around here because I know that we're all balancing regular life and our hobby time!
I'm relieved to hear that it is a known issue, though I'm going to miss the functionality! I wish Google would build some kind of equivalent security measure so that the network state can't be changed while the phone is locked. I'm guessing that this issue is exactly why they haven't gotten to it (yet?).
Thanks for your time & support, both here with my issue and across the forums.
Peace,
Computerslayer
computerslayer said:
Hello Crixley,
No worries at all - I'm always grateful when anyone responds around here because I know that we're all balancing regular life and our hobby time!
I'm relieved to hear that it is a known issue, though I'm going to miss the functionality! I wish Google would build some kind of equivalent security measure so that the network state can't be changed while the phone is locked. I'm guessing that this issue is exactly why they haven't gotten to it (yet?).
Thanks for your time & support, both here with my issue and across the forums.
Peace,
Computerslayer
Click to expand...
Click to collapse
I'm glad to hear it's fixed for you!
I try to help as much possible, I remember how good it was to have people help me when I needed it and sometimes I need a hand as well.
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.