Database Info

Htc Touch Pro (Raphael 500) Running Android , How to overclock?

Alright so Yesterday I installed the android os on my touch pro (raph 500)
i orginally have windows mobile 6.5 which is preety fast
but android is really slow!
i turned off all the settings which i would think it used alot of memory but still no help, so i started seeing videos on overclcking?
can someone explain to me on how to do this,
with links to the download
i really need to speed this up ,it would be amazing if it worked.
also if you give me a response that helps me , ill donate 10.00+ to you .

I do not require funds as I enjoy helping out!
From THIS thread and THIS post:
Overclocking
acpuclock.oc_freq_khz=XXXXXX ( suggested 600000-640000 )
but it is very unstable if you try to get higher than 650000-700000
Click to expand...
Click to collapse
Basically, you add that to the startup.txt file somewhere between the parentheses with an added space between the next command. Keeping in mind, with added OC, you may and may not notice a difference in stability. I honestly never use OC and I am using FroYo from THIS thread. Additionally you can try out Gingerbread Alpha from THIS thread. Please leave feedback in their respective threads, thanks!
n-Joie! (Enjoy)

thanks but this is my startup text :
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2182
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=210 msmvkeyb_toggle=off physkeyboard=raph board-htcraphael-navi.wake=0 gsensor_axis=2,-1,3 acpuclock.force_turbo=1"
boot
Click to expand...
Click to collapse
so which am i supposed to edit, sorry im a noob lol
& u said that was the one you used,
is it fast?

Actually, I can't use that one because I have an at&t Fuze. If you have a RAPH500, you might want to use the following:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2182
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=210 msmvkeyb_toggle=off physkeyboard=raph board-htcraphael-navi.wake=0 gsensor_axis=2,-1,3 pm.sleep_mode=1 acpuclock.oc_freq_khz=XXXXXX"
boot
Click to expand...
Click to collapse
Where XXXXXX is equal to a value between 600000-640000
Additional note: make sure you type something like 600000 or any value up to 640000

lol thanks im trying to see if theres a difference in speed.
but you used froyo?
is that running fast?

It's running fine with sync and a few other apps running in the background. I would be mindful of livewallpaper and HQ video at the moment as this project is currently still under development, at best. At least that is what I have noticed as far as performance is considered. I have also run a stripped Gingerbread alpha build (the one I linked you to earlier) and it is running faster/smoother than FroYo. To be expected without all the bells and whistles...
NOTE: Speed is relative to performance at the moment. Hence why I say it's still under development...

intresting ill test that out in about 15 mins
but does yours take a long time to come out of sleep mode?

Hmmm, that might be the notorious sleep of death SOD. I usually do something that most don't like but I sort of turn off the screen time out by first making the screen time out greater than 10 or 30 minutes. After that it should make things easier as far as disabling the auto back light/screen timeout feature. Keep in mind this is only a work around, I believe there is mention of actually fixing this issue. You'll need to download a free app called batterybooster (use the link if you want to read up on it a little). Once installed, run it and look for the far right icon and tap it. Set the timeout to Never and you'll notice a decent performance enhancement in the screen off and screen on.
NOTE: You will need to manually turn it off from here-on. You can try to play around with the setting but I find it somewhat problematic. Meaning that if you enable the timeout, it might and it might not work.

alright well i tried the gingerbread and that didnt work it lagged .
i tried froyo , it was amazing then i found out wifi didnt work
so now im back to the regular android one i had before ill be trying to see if theres a difference now that i "overclocked" it .
but thanks for all the help.
ill post back if i need something!

Odd, wifi(wap not wep) works for me... Must be a random occurrence? Have you attempted to update any files and are you using OC? Probably best to stick to a stock-like startup till you get a good feel of most of the basic functions, which may or may not include wifi, gps, 3d and camera; these should be on the "to be worked on" list of things for the devs to complete.

R^7Z said:
Odd, wifi(wap not wep) works for me... Must be a random occurrence? Have you attempted to update any files and are you using OC? Probably best to stick to a stock-like startup till you get a good feel of most of the basic functions, which may or may not include wifi, gps, 3d and camera; these should be on the "to be worked on" list of things for the devs to complete.
Click to expand...
Click to collapse
it works for you?
wth!
and i havenet updated any files on the deive.
no im not using overclock on this onr,
but on another android version which is on my sd card i am
& is there a way i can lock my screen so it doesn't touch any buttons in my pocket &kepp it from going into SOD .

ndnmaster096 said:
it works for you?
wth!
and i havenet updated any files on the deive.
no im not using overclock on this onr,
but on another android version which is on my sd card i am
& is there a way i can lock my screen so it doesn't touch any buttons in my pocket &kepp it from going into SOD .
Click to expand...
Click to collapse
NVM I got the wifi to work now .

Glad to hear about the wifi success story I don't know if I could walk you through that as it seems that wifi can be temperamental ( or just mental )
The only way I could get out of the SOD issue was to try for that work around (setting it to never timeout with the app mentioned) and to set a pattern unlock

R^7Z said:
Glad to hear about the wifi success story I don't know if I could walk you through that as it seems that wifi can be temperamental ( or just mental )
The only way I could get out of the SOD issue was to try for that work around (setting it to never timeout with the app mentioned) and to set a pattern unlock
Click to expand...
Click to collapse
well i set it to never timeout and i have a lock pattern
but since it never times out it wont lock .

also now im starting to notice froyo is rebooting for some weird reason automatically .

Calm down, that is kind of "usual behavior" . There are quire a few things going on and the OS is attempting to "handle it". Sometimes it can't and just quits instead of freezing up ( which would be the lesser of two evils ). To get it to lock, you will have to turn it off manually (power button). Unfortunately, I think if the keyboad slides out, it self unlocks (kind of a self defeating purpose, more or less). If you turn the screen off and wait like 10 seconds then turn the screen on (power key), you should see the lock. I can't say for sure but it does work for me. I don't really have much time for troubleshooting today, as I am at work currently but do look over the threads I linked you to earlier if at all possible.

okay so i turned it off using the power button and it booted to windows mobile (odd)
then i tried running haret.exe & got this message:
"The file HARET cannot be opened. Either it is not signed with a trusted certificate, or one of its components cannot be found. IF the problem persists, try reinstalling or restoring the file."
im not sure what to do.
i tryed reformatting the card and installing fresh files, which didnt work so now im left questioned?

When you say you turned it off, did you hold the button or just press it once? If you pressed it once, then, that is definitly not "usual" behavior. I recall having that issue once upon a time but for the life of me, I don't recall what I did to recover from it. However, it sounds like you are attempting to run from a shortcut that references the program(haret) that is no longer there. To resolve this, I need you to confirm that you are running from the microSD and not a shortcut. Also, you aren't formatting under windows, right? If you are formatting from windows, that would be a "no-no"
Find something like the HP tool (can be googled) that everyone else talks of or even something like the free version of partition wizard should work.

i held the button and it gave me options
1) airplane mode
2)shutoff
3)vibrate
i did try to make a shortcut but i deleted it and now when i checked i was running it from the actual application.
lastly, i did format from windows but i downloaded hp format tool
and formated my device in quick format.
reinstalled the programs and it still gave me the same error message,
please help, i really miss android =(

Try deleting data.img and letting it recreate the file. To clarify about the screen off issue, when you press the power button once (not hold), what does it do? Also, which kernel package are you using and have you attempted to download a newer kernel package yet?
Also, try THIS kernel package; I got it from THIS site. It looks like that kernel package is specific to our devices.

[FIXED (kinda)] Screen turns off/Locks when I try to call

Please HELP me, my phone's screen turns off/locks when I try to make a call. It doesn't turn back on when I press the home key or power button (only the button lights come on). The call successfully goes on even when the phone locks but I can't end it though. The only solution is to pull out the battery or plug it in to charge (ac or usb). It's really weird that when I plug it to charge or out from charging, the screen comes back on.*And yes this problem comes ONLY when I call and about 90% of the time, otherwise the phones perfect. And of course, I tried everything from factory resetting to flashing tons of stock/custom firmwares like XXKPU, XXKPQ, XXKPE, DDKP1/2/3, MIUI etc and lots of kernels but nothing fixed it.
I am not exactly sure when the problem started (I mostly use my other phones to make calls) but I am 100% sure the problem started when I was around the following configuration,
Firmware: Gingerbread 2.3.6 XXKPQ
Kernel: UC kernels (V09 3009, V10, V12, V13)
Mods: battery mod from UOT Kitchen, icons ( battery, wifi, status bar) with Rom ToolBox and I think video camera fix by shriom (was flashing a lot of "bad things" lately )
Can this be a hardware or software problem? I think it's a software problem from the looks of things because if it's hardware then some other bugs should come along, right? It's surprising that reflashing/resetting can't fix it. Please help me, which firmware (or anything) can I flash to fix this, or how can I do a SOLID factory reset (whichever way) to hopefully fix this, PLEASE HELP. DON'T say I have to visit service center, I have never been there!!!
****************************************************************************************************
Flash a rom with kernel 3.0, it disables the faulty proximity sensor.

Just flash xxkpe along with .pit file.
Then xxkpq or xxkpu whatever u want.
Then flash xda bam kernel v13. In my opnion it is most stable kernel.
Dont set any screen off profile in set cpu.
Most of the time select governer which will give u best performance like performance, lagfree, ondemand etc.
Dont use any script. It spoil the smooth functionality of phone.
Dont use frequncy below 300 mhz or above 1ghz otherwise it create some instabilty in basic fuctions of phone

The_GMAN said:
Please HELP me, my phone's screen turns off/locks when I try to make a call. It doesn't turn back on when I press the home key or power button (only the button lights come on). The call successfully goes on even when the phone locks but I can't end it though. The only solution is to pull out the battery or plug it in to charge (ac or usb). It's really weird that when I plug it to charge or out from charging, the screen comes back on.*And yes this problem comes ONLY when I call and about 90% of the time, otherwise the phones perfect. And of course, I tried everything from factory resetting to flashing tons of stock/custom firmwares like XXKPU, XXKPQ, XXKPE, DDKP1/2/3, MIUI etc and lots of kernels but nothing fixed it.
I am not exactly sure when the problem started (I mostly use my other phones to make calls) but I am 100% sure the problem started when I was around the following configuration,
Firmware: Gingerbread 2.3.6 XXKPQ
Kernel: UC kernels (V09 3009, V10, V12, V13)
Mods: battery mod from UOT Kitchen, icons ( battery, wifi, status bar) with Rom ToolBox and I think video camera fix by shriom (was flashing a lot of "bad things" lately )
Can this be a hardware or software problem? I think it's a software problem from the looks of things because if it's hardware then some other bugs should come along, right? It's surprising that reflashing/resetting can't fix it. Please help me, which firmware (or anything) can I flash to fix this, or how can I do a SOLID factory reset (whichever way) to hopefully fix this, PLEASE HELP. DON'T say I have to visit service center, I have never been there!!!
Click to expand...
Click to collapse
Same for me!!
the proximity sensor is totally block, for the dust, also my frontal cam. So, dissassembly and cleanning, works for me.
Pics here
http://www.htcmania.com/showthread.php?t=381366

yeah its just proximity bugged,not working,dirty, or you are not aware of it and you cover it then phone shuts screen to save battery.

vishal24387 said:
Just flash xxkpe along with .pit file.
Then xxkpq or xxkpu whatever u want.
Then flash xda bam kernel v13. In my opnion it is most stable kernel.
Dont set any screen off profile in set cpu.
Most of the time select governer which will give u best performance like performance, lagfree, ondemand etc.
Dont use any script. It spoil the smooth functionality of phone.
Dont use frequncy below 300 mhz or above 1ghz otherwise it create some instabilty in basic fuctions of phone
Click to expand...
Click to collapse
I already tried that, it didn't fix.
Thanks for your help.
ale210 said:
Same for me!!
the proximity sensor is totally block, for the dust, also my frontal cam. So, dissassembly and cleanning, works for me.
Pics here
http://www.htcmania.com/showthread.php?t=381366
Click to expand...
Click to collapse
Na, I don't think that's the problem. My sensors and camera are pretty much clean, I can see them right through.
xGiox said:
yeah its just proximity bugged,not working,dirty, or you are not aware of it and you cover it then phone shuts screen to save battery.
Click to expand...
Click to collapse
You've gotta point man. I am sure it's proximity sensor related, but what does it have to do with screen locking & not responding? I also read some other people's similar problem, but their was when they locked the phone. The problem is exactly the same, the screen doesn't come on until you plug it to charge.
http://forum.xda-developers.com/showthread.php?t=1434323
Any way I could fix this?

Disable black screen issue after call
ro.lge.proximity.delay=25
mot.proximity.delay=25
Edit ur build.prop in system folder using root explorer..
if we can stop the sensor from working may be it will help..!
gsm.proximity.enable=false
use this to disable..!
i hope it helps u...

@geekynoob
What firmware are you using, DDKP3? I can't see any "proximity" related stuff in my build.prop
I am currently using XXKPQ with UC Kernel #1401 and here is my build.prop fairly after a fresh flash...
UPDATE: I flashed KPU but it only has...
ro.lge.proximity.delay=25
mot.proximity.delay=25
...but no gsm.proximity.enable

The add it bro..
Most of the tweaks are supposed to b added..
M on kpu.but i keeeep jumping..

@geekynoob
where exactly can I add gsm.proximity.enable. will it work if I add it anywhere? attach a file to demonstrate if possible, I'll appreciate it. Thanks.

The_GMAN said:
@geekynoob
where exactly can I add gsm.proximity.enable. will it work if I add it anywhere? attach a file to demonstrate if possible, I'll appreciate it. Thanks.
Click to expand...
Click to collapse
add at bottom of all the setting

@chongns
Nothing happen, no result

The_GMAN said:
@chongns
Nothing happen, no result
Click to expand...
Click to collapse
The line is not correct. Add this one in /system/build.prop
Code:
gsm.proximity.enable=false
Edit: I'm not sure if you included or not "=false" in the string as geekynoob wrote, but that's what I get from your posts.

K
loSconosciuto said:
The line is not correct. Add this one in /system/build.prop
Code:
gsm.proximity.enable=false
Edit: I'm not sure if you included or not "=false" in the string as geekynoob wrote, but that's what I get from your posts.
Click to expand...
Click to collapse
Yes, I did enter exactly as geekynoob said "gsm.proximity.enable=false", I was just too lazy include "=false" in my post. I also tried adding "=0" but still no result.

Issue is fixed by flashing a Rom with Kernel 3.0

I cant get cm10 to work right, Please help

The 07 version works fine but the new one i am having a problem and cant figure it out.I have cleared and reset everything and did a clean install. every things fine until i lock the phone or screen timeout. then the bottom lights dont come back on. i have done the factory reset again and cleared davlik and still not helping. If i send a email it will activate the notification lights and it will work untill screen locked again. i have toggled them on and off as well. Anyone else have this problem and have a solution for me?

Bln works, but is buggy. If this is your only problem, be happy
At some point something will click and it'll start to work right. I'm trying to stabilize that driver but it may be a while.

dr4stic said:
Bln works, but is buggy. If this is your only problem, be happy
At some point something will click and it'll start to work right. I'm trying to stabilize that driver but it may be a while.
Click to expand...
Click to collapse
anyway to disable the bnl part and have it work like the 07 version?

blazetim said:
anyway to disable the bnl part and have it work like the 07 version?
Click to expand...
Click to collapse
Settings, advanced, hit sensors tab our swipe left, uncheck keys notification light
Sent from my CM10 powered Galaxy S Blaze 4G

[Q] Home and search buttons not working

Hi all,
Since installing CM7 (20130201) and Mazout's 2.6.32.60 kernel, my phone's home and search buttons are no longer functioning. Any ideas how to fix it? These are important functions.
It also doesn't go to sleep anymore, even when I push the power button.

Sounds like some gremlin mischief. Have you tried using the nullifier to wipe?
Edit: here's the link
http://forum.xda-developers.com/showthread.php?t=1854850

Thanks TwitchyEye. That worked, for a while, but the issues are back now. And randomly, the menu/home/back/search icons light up when the phone's otherwise asleep.
TwitchyEye said:
Sounds like some gremlin mischief. Have you tried using the nullifier to wipe?
Edit: here's the link
http://forum.xda-developers.com/showthread.php?t=1854850
Click to expand...
Click to collapse

Maybe it's something you restored?

natescape said:
Thanks TwitchyEye. That worked, for a while, but the issues are back now. And randomly, the menu/home/back/search icons light up when the phone's otherwise asleep.
Click to expand...
Click to collapse
Those are your lights acting as a notification. You can turn it off in cyanogenmod settings.
Sent from my LG-P999 using xda app-developers app

Where might I find that in the settings? I went through and couldn't find it.

natescape said:
Where might I find that in the settings? I went through and couldn't find it.
Click to expand...
Click to collapse
Settings => CyanogenMod settings => Interface => LED notifications. I select unconfigured then, edit category settings, LED mode, and force LED off. I suppose if you wanted to you could set individual settings for applications. There's also a few apps in the play store that take care of it too.

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.