[ROM][11.x]AospExtended-v8.7[UNOFFICIAL][Suzuran]

Search This thread

steve8x8

Senior Member
Jul 7, 2014
519
162
Samsung Galaxy S4 Mini
OnePlus One
Did you attempt to "prime" your GPS with A-GPS data? Which region of the world are you in, and do your localization settings of the OS match it?

Modifying NTP_SERVER and stuff was pretty common about 10 years ago, using apps like GPSfix and AngryGPS, but that was with 2010 hardware, not 2015...
 
  • Like
Reactions: DevelLevel

Kilavagora

Member
Oct 31, 2021
6
5
Did you attempt to "prime" your GPS with A-GPS data? Which region of the world are you in, and do your localization settings of the OS match it?

Modifying NTP_SERVER and stuff was pretty common about 10 years ago, using apps like GPSfix and AngryGPS, but that was with 2010 hardware, not 2015...
I have no idea how to "prime" GPS 😕 I am in Eastern Europe, and I don't use any special localization settings, just whatever was the default.
 
  • Like
Reactions: DevelLevel

DevelLevel

Senior Member
Did you attempt to "prime" your GPS with A-GPS data? Which region of the world are you in, and do your localization settings of the OS match it?

Modifying NTP_SERVER and stuff was pretty common about 10 years ago, using apps like GPSfix and AngryGPS, but that was with 2010 hardware, not 2015...

I have no idea how to "prime" GPS 😕 I am in Eastern Europe, and I don't use any special localization settings, just whatever was the default.
I'm not 100% sure what @steve8x8 means but it is probably similar to what I am going to say, you could try downloading an app which could get a signal (GPSTest seems to work for you) and then use it, and the device would be "primed" and you could try on another non working app afterwards.
Also have you tried to switch between the different GPS modes? "Sensors only", "High accuracy" and "Battery saving"?
 
Last edited:

steve8x8

Senior Member
Jul 7, 2014
519
162
Samsung Galaxy S4 Mini
OnePlus One
With "priming" I meant to download A-GPS data to the device (and therefore the GPS receiver).

There are multiple apps around which can do this: GPS Test (caution, there are several apps with the same name), GPS Status & Toolbox, SatStat, ...

You 'll need an internet connection once, to download the actual satellite ephemerides (where to find them in the next hours).
A-GPS allows to find satellites more quickly. Once the receiver is running and locked to satellites, it'll update satellite positions on the go.
 
  • Like
Reactions: DevelLevel

Kilavagora

Member
Oct 31, 2021
6
5
I'm not 100% sure what @steve8x8 means but it is probably similar to what I am going to say, you could try downloading an app which could get a signal (GPSTest seems to work for you) and then use it, and the device would be "primed" and you could try on another non working app afterwards.
Also have you tried to switch between the different GPS modes? "Sensors only", "High accuracy" and "Battery saving"?

With "priming" I meant to download A-GPS data to the device (and therefore the GPS receiver).

There are multiple apps around which can do this: GPS Test (caution, there are several apps with the same name), GPS Status & Toolbox, SatStat, ...

You 'll need an internet connection once, to download the actual satellite ephemerides (where to find them in the next hours).
A-GPS allows to find satellites more quickly. Once the receiver is running and locked to satellites, it'll update satellite positions on the go.
Does not make any difference whether I "prime" it, either in SatStat or GPS Test (Or "Sensors only", "High accuracy" and "Battery saving" with those). After they acquire lock, all other apps still take forever to do the same.

I will be in US in couple of days and I will check if the region matters.
 

Kilavagora

Member
Oct 31, 2021
6
5
No dice! Although it seems GPS test takes less time to acquire the lock in US, I was never able to get the position in Uber 🤷‍♂️
 

Kilavagora

Member
Oct 31, 2021
6
5
I figured this out. The reason why GPS apps were working was that they talk directly to the hardware. But for the regular apps coordinate acquisition is mediated via Google Play services. Apparently, Google Play services need permissions to access location while running in the background. And these permissions cannot be set from the Settings. So I did this with adb:
Code:
adb shell pm grant com.google.android.gms android.permission.ACCESS_BACKGROUND_LOCATION
adb shell pm grant com.google.android.gms android.permission.ACCESS_COARSE_LOCATION
adb shell pm grant com.google.android.gms android.permission.ACCESS_FINE_LOCATION
and now GPS works fine in all apps.
 

laakssim

Member
Jul 22, 2022
19
4
Been running this ROM for a couple of days now and overall it seems good.
But some questions:
-When charging the phone the milliamp and watt values on the lock screen are way too big, and it always says "Charging slowly" no matter what charger you use. Is there any way to fix or adjust these values? In the HAVOC ROM the values were correct I think.
-I am not completely sure but it seems that the battery runs out faster that with other ROMs, even when the phone is just on standby and I'm not doing anything with it. Any tweaking that could be done about it?
-Video recording seems to work only with the included "Camera" app. I've tried ProCam X Lite and OpenCamera, which both are usually not able to record video (sometimes it works though). On the other hand when shooting photos, the viewfinder is updating ok with these two apps, but is laggy with the included "Camera" app. Any idea what is causing this and is there some other camera apps that work good with both photos and video?
 
Last edited:
  • Like
Reactions: DevelLevel

DevelLevel

Senior Member
Been running this ROM for a couple of days now and overall it seems good.
But some questions:
-When charging the phone the milliamp and watt values on the lock screen are way too big, and it always says "Charging slowly" no matter what charger you use. Is there any way to fix or adjust these values? In the HAVOC ROM the values were correct I think.
-I am not completely sure but it seems that the battery runs out faster that with other ROMs, even when the phone is just on standby and I'm not doing anything with it. Any tweaking that could be done about it?
-Video recording seems to work only with the included "Camera" app. I've tried ProCam X Lite and OpenCamera, which both are usually not able to record video (sometimes it works though). On the other hand when shooting photos, the viewfinder is updating ok with these two apps, but is laggy with the included "Camera" app. Any idea what is causing this and is there some other camera apps that work good with both photos and video?
I have noticed this milliamps issue and it is related to the source code of the ROM or how it communicates with the kernel, therefore it can not be changed after the compile. For me the values seems to be multiplied by a factor of 1000 so the readings are still usable, just annoying to interpret.
I think that it says charging slowly because the E5823 does not have a fast charger and AEX is using a general point of view to determine what is "Normal" charging, so nothing to worry about. There is no noticable difference in chargingspeed between AEX and Havoc from what I can tell.
Regarding the battery issue you mention there is nothing I can help you with. Both Havoc and AEX uses the same kernel so the only differnes is the ROM source which I do not modify. But when I tested the first build of AEX, I saw no significant battery differnes between Havoc and AEX... So I can only recommend normal battery tweaking tips (limit app activities in background and limit wakelocks etc).
The camera issue you mention is really weird because I have the opposite problem (remember that the camera is very unstable for A11 ROMs in general). For me I have a laggy view finder and can't record in the stock app, but third party apps like OpenCamera and Snapchat is able to record and take pictures with decent quality and do not have a laggy viewfinder...

You could try a factory reset with Experifirm and FlashTool to see if some of your issues gets resolved.

Sadly I don't have a lot of spare time anymore so I do not see that I will be able to fix these issues in the future. AEX has also show very little activity on the 11.x branch (last security patch from 2021) so I see no reason to publish a new build until something significant has changed in the source or I have managed to fix any of these issues or any of the other issues listed in the main post.
 
Last edited:
  • Like
Reactions: laakssim

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Been running this ROM for a couple of days now and overall it seems good.
    But some questions:
    -When charging the phone the milliamp and watt values on the lock screen are way too big, and it always says "Charging slowly" no matter what charger you use. Is there any way to fix or adjust these values? In the HAVOC ROM the values were correct I think.
    -I am not completely sure but it seems that the battery runs out faster that with other ROMs, even when the phone is just on standby and I'm not doing anything with it. Any tweaking that could be done about it?
    -Video recording seems to work only with the included "Camera" app. I've tried ProCam X Lite and OpenCamera, which both are usually not able to record video (sometimes it works though). On the other hand when shooting photos, the viewfinder is updating ok with these two apps, but is laggy with the included "Camera" app. Any idea what is causing this and is there some other camera apps that work good with both photos and video?
    I have noticed this milliamps issue and it is related to the source code of the ROM or how it communicates with the kernel, therefore it can not be changed after the compile. For me the values seems to be multiplied by a factor of 1000 so the readings are still usable, just annoying to interpret.
    I think that it says charging slowly because the E5823 does not have a fast charger and AEX is using a general point of view to determine what is "Normal" charging, so nothing to worry about. There is no noticable difference in chargingspeed between AEX and Havoc from what I can tell.
    Regarding the battery issue you mention there is nothing I can help you with. Both Havoc and AEX uses the same kernel so the only differnes is the ROM source which I do not modify. But when I tested the first build of AEX, I saw no significant battery differnes between Havoc and AEX... So I can only recommend normal battery tweaking tips (limit app activities in background and limit wakelocks etc).
    The camera issue you mention is really weird because I have the opposite problem (remember that the camera is very unstable for A11 ROMs in general). For me I have a laggy view finder and can't record in the stock app, but third party apps like OpenCamera and Snapchat is able to record and take pictures with decent quality and do not have a laggy viewfinder...

    You could try a factory reset with Experifirm and FlashTool to see if some of your issues gets resolved.

    Sadly I don't have a lot of spare time anymore so I do not see that I will be able to fix these issues in the future. AEX has also show very little activity on the 11.x branch (last security patch from 2021) so I see no reason to publish a new build until something significant has changed in the source or I have managed to fix any of these issues or any of the other issues listed in the main post.
  • 6
    aex.png

    Disclaimer:
    I am building this ROM in my spare time,
    feel free to report bugs and things that do not work but I may not be able to fix does.
    I just wanted to share my project.
    I am not responsible for any bricked or faulty devices!

    Description:
    "AospExtended is just an extension to AOSP,
    through which we are trying to provide a stock AOSP experience along with some important customization features.
    We have cherry-picked the features from many other projects and hence we are very thankful to them."
    Team AEX

    Key Features:
    Android version: 11.x
    Kernel version: 3.10.108
    Security patch: 2021-11-05
    Selinux: Enforcing

    Working:
    WIFI, Bluetooth, Location, Camera, Calls, SMS, etc

    Not Working:
    The fingerprint sensor is unreliable, DT2W, you tell me

    Flashing:
    Flash TWRP
    Reboot to recovery
    Wipe
    Flash AospExtended
    (Optionally flash Magisk/Gapps)
    Reboot

    Downloads:
    Gcloud
    Mega


    Sources:
    Kernel
    Suzuran
    Kitakami-common

    Credits:
    Everybody who is involved in the AospExtended and LOS development.
    @Berni-0815 and other msm8994 kitakami developers who made this possible for our phone.
    (If you feel that you should be listed here too, just tell me.)​
    3
    New release!

    2021-10-23
    -Upstreamed sources
    -Security patches updated to 2021-10-05
    3
    New release!

    2021-07-27
    -System security patches updated to 2021-07-05
    -Upstreamed AOSP Extended sources to 8.4
    3
    New release!

    2021-06-10
    -Security patches updated to 2021-06-05
    -Upstreamed AOSP Extended sources to 8.2
    -Upstreamed Device trees and kernel from @Berni-0815 (Thanks!)
    2
    Hello DevelLevel

    "Double tap screen to wake up" is not working on my device.
    Double tap to turn off the screen
    This is working.
    Yes, it is adressed as "DT2W" in the main post (double tap to wake). It hasn't worked on this ROM. But I'm working on it...