Hi. I am at a loss on how to fix my GPS on my device. When using Lineage 7.1.2 I can use Google Maps without issue and use navigation to get me places. When I try and use ANY Oreo ROM I can get a GPS lock only on my current location however I can not use navigation; the device stays locked to the start point and will not follow me. When Oreo first came out I was able to upgrade to Oreo and use Maps without issue. I am somewhat a flashaholic and like trying different ROMS to see how they work day to day so I have flashed GZOP, Cardinal, Omni, Lineage 15. I have tried all different Firmware updates by Lord Boeffla trying 4.1.7 (Which I am currently using and Lineage 7.1.2 navigation works) 4.5.0 and 4.5.1 to try and rectify this but it does not matter. No matter what firmware I try and use the results are the same. Lock but will not follow At one point I even tried downgrading to Stock 3.5.4 firmware and software to which I was able to flash but the system would not boot only would bootloop. At this point I am not able to flash any stock OOS ROMS and I must use a custom built ROM such as Lineage to get the phone to boot. I have tried many GPS fix apps such as AGPS to try and force clear GPS cache and reset they system but the results are the same. Lock and no follow. Any ideas on what else can be tried to resolve this? I fear I may have damaged the device throuh flashing the firmware so many times and I will be stuck with Nougat forever with the current phone.
All Oreo ROM's are in Alpha/Beta build stages. I've experienced similar results on many Oreo ROMs. The best course of action you can take is providing logs to the developers of the consecutive ROM, and let them work.
Different firmware versions don't make any difference to the GPS. ROM's are built on top of the firmware, and such. Flashing different firmware's will not fix the issue. Go back to Nougat if you want a stable system.
The issue here is you're complaining about bugs on Alpha/Beta ROM's.
I have been facing the same problem in Nougat Roms too. I think it has been introduced in 4.1.7
The only course of action would be to get it fixed in Beta OOS by providing the logs to the devs.
Here's a related thread :
https://forum.xda-developers.com/oneplus-3t/help/poor-gps-oos-4-1-7-t3664864
Had same issue, refresh latest beta firmware.
I've no issue using gmaps on ob 17 I use it daily.
I've been having loads of issues with installing Treble ROMs. Currently I'm on the PRA-LX1's most recent update with EMUI 8, (C432) and have only recently found out that Askuccio's TWRP is around. Previously I've been trying and trying with TWRPs like Haky86's which couldn't have even worked because it's built for EMUI 5, I've tried Pretoriano's for the P10 lite, as well as some other random one which is Chinese. Pretoriano's is always unable to mount my /storage/ or /system/ and therefore I can't wipe or flash anything properly, and the chinese one just placed me in a bootloop after flashing the Treble RR ROM.
I now have the Askuccio TWRP and I need to know before I try again - will I get a bootloop, or get in a mess all over again? I can't back anything up beforehand because of encryption and inability to root before switching to a custom ROM. The last times I've tried I've had to keep booting and messing around until eRecovery manages to reproduce itself from seemingly nothing and then redownloads my system firmware again.
Has anyone had proper success? Do you recommend any ROMs to use? I'd prefer RR, Lineage or Omni but at this point anything is fine. Thanks
I'm in the same boat as you. I have had many phones and rooted them all, but somehow the help on this forum lacks detail and consistency. I also have the TWRP installed but can't get any further down the line - where is the root? Can't install custom roms, can't get adaptive SD, just got unlocked bootloader and FWP!
Ok, got a T380. Device specs show it should be much more snappy and responsive than it is. I want to build an ASOP or lineage build for it. There are no custom ROMs right now for my device. Can any dev point me in the direction of a tutorial for building the device tree and obtaining the proprietary blobs? I have been googling for weeks and most of them tell me to get the blobs from a similar device running LOS. I have some coding, flashing and linux expericence, so I am not going in as a complete noob. Any advice or help would be greatly appreciated. TIA
I started compiling roms in August so I have been through this journey in which you are about to start. I'm not a developer, but this is what I learned so far.
If you have a supported lineageos device, I suggest you build that first following the guides they have written. This will ensure you have the proper toolchain, tools, OS, memory, hard disk space, etc setup properly. Here is an example.
https://wiki.lineageos.org/devices/gtelwifiue/build
For the device tree, I did a search using "github sm-t380" and it came up with
https://github.com/tangalbert919/android_device_samsung_gta2swifi
Once I knew the code name, gta2swifi, then I searched "github gta2swifi" which lead to
https://github.com/lilindian16/android_device_samsung_gta2swifi
which looks like a good start.
In order to build the rom, you need 5 things.
1) device tree
2) kernel source
3) vendor blobs
4) roomservice.xml
5) twrp
For kernel source, the T380 has open source code at
https://opensource.samsung.com/main
Type T380 in search box and download the Pie kernel source code.
For vendor blobs, if the
https://github.com/lilindian16/android_device_samsung_gta2swifi/blob/master/proprietary-files.txt
is correct, there's over 2300 files that you need to copy over.
For roomservice.xml, take an existing one that is close to the T380 and make modifications to it. I built the T350 and you can look at the roomservice.xml file at
https://forum.xda-developers.com/ga...ficial-lineageos-17-1-galaxy-tab-8-0-t4162573
For twrp, use an existing T380 twrp.
Video tutorials that I found useful in building roms.
https://www.youtube.com/c/AlaskaLinuxUserAKLU/videos
Thanks so much for the help. I am pretty much in the same spot. I have rooted and flashed just about every device I have ever owned and feel pretty confident I can build a ROM for this device. I already have rooted and TWRPed my T380 it was the vendor files and proprietary blobs that were totally dumbfounding me. I will check your links and work through it. Again, thanks so much for the links.
Okiera29 said:
it was the vendor files and proprietary blobs that were totally dumbfounding me.
Click to expand...
Click to collapse
If you haven't noticed, the vendor blobs are at
https://github.com/lilindian16/android_vendor_samsung_gta2swifi
One other tip. For your first build, build an eng build so you have adb logcat enabled right away. It took me days to figure that out when the boot animation was stuck or the tablet was boot looping. The magic command is
TARGET_BUILD_TYPE=debug TARGET_BUILD_VARIANT=eng make -j2 bacon
-j2 because my machine is only dual core and I only have 12GB DRAM to build.
It's the only way to see debug and information messages while the tablet is booting.
Thanks man! Still trying to get it set up right. I tried to build a debloated, deknoxed stock rom with Android Kitchen and failed. Luckily, had a TWRP back up so the soft brick wasn't an issue. I am determined to figure this out and get a thin custom ROM built for this sucker. I need to figure out overclocking too. You have been a tremendous help!!!
@Okiera29 Were you able to get a working LineageOS rom for your T380. If you don't mind telling me what you have tried and if you had success that would help me out a lot. I'm a newbie trying to find my way around custom roms
I forgot that I participated in this thread. I don't have the SM-T380, but one of the links I referenced earlier shows activity in the last month for the SM-T380 and as recent as < 48 hours.
Looking through the commit history, @andr01dfr3ak might actually have a running 18.1 because enforcing selinux is usually done last after the build is up and running.
Albert, aka andr01dfr3ak also worked on earlier versions of the SM-T350 with 15.1. Since then, I have helped build SM-T350 16.0 with some people and then built 17.1 and 18.1 basically on my own.
I do not have the SM-T380 either, so I am not sure if what I have right now even works. I just know that I can build LineageOS for this device.
@andr01dfr3ak built this rom for me I posses a SM-T380 but I don't have it rn I got stuff removed... for awhile.... If @retiredtab has the device may I suggest having @andr01dfr3ak give @retiredtab the rom to run?
{Mod edit: Link removed} my Discord Server.
i'm trying to download the rom from @andr01dfr3ak but there aren't any available mirrors on androidhost
Want to chime in here -- I too have a Samsung SM-T380, rooted and have TWRP 3.2.3-1 flashed to recovery. I downloaded an image lineage-18.1-20220114-UNOFFICIAL-gta2swifi.zip from somewhere, which is what I think @andr01dfr3ak has been working on.
I am able to successfully install the image, but when booting, the following message is displayed at initial splash screen: "KERNEL is not seandroid enforcing"
And then the display goes dark.
I'm more than happy to provide logs and/or test images if that would be helpful? Please let me know if there's anything I can do to move this along so we have a stable Lineage 18.1 image for the SM-T380!
I've (somehow) got this tree to boot. Whatever the manifest in the tree was doing, it wasn't working, but reverting to the stock one (and downgrading everything) seemed to do it.
I can't get the camera HAL to detect any cameras, though. I think Bluetooth also has issues, but at least WiFi/sound/earbuds are working so at the very least you can use it as a media consuming tablet. And I also have no idea if it works outside of my own device either.
Am a little uncomfortable uploading something that barely works, though, but if anyone capable of building it wants to find out, I have a tree here:
https://github.com/lifehackerhansol-android/android_device_samsung_gta2swifi
https://github.com/lifehackerhansol-android/android_vendor_samsung_gta2swifi
@lifehackerhansol Mind DM'ing me a link to your build? I'd like to work on this a bit and reviewing your progress would be helpful!
christophershaw said:
@lifehackerhansol Mind DM'ing me a link to your build? I'd like to work on this a bit and reviewing your progress would be helpful!
Click to expand...
Click to collapse
So I no longer have this device, it has been given to a family member and reverted to stock. So I can't really make a build and confirm that it's working. The device tree I left above is exactly as I left it back when it did work, so you can go off that.
Sorry, I lost the existing build since. Had to reinstall Linux on my machine and all.
I now have another SM-T380. (lol)
The camera was a kernel issue. Turns out we were using j4primelte's kernel, and it worked all the way until it tried to initialize cameras, because our device's cameras aren't supported in that kernel. It's a miracle anything else worked... Well that was the first problem. The second one was that the blobs were old and Samsung botched their upgrade to 9.0 so I had to deal with several workarounds for that. Anyway camera fixed.
Currently in the middle of mucking with SELinux. When that looks clean I'll push a build(?)
okay so ive tested a number of treble GSI's on SM-X200 but im finding that the device randomly reboots on all Android 13 GSIS, now when i say reboots im talking about youve set up, youve loaded the tablet, your just using your tablet as you normally will and the device reboots
Lineage OS 19 works perfectly fine without reboots, but as soon as i flash LOS20 GSI it reboots all the time
What makes it even more strange is when i install Android 14 Beta GSI i get no reboots, but then i have another problem where my Device cant connect to any bluetooth Devices, so the GSI itself is really stable, but i use Bluetooth Earphones, and Googles Android GSIS dont have the PHH settings menu, which fixes the problem on all other roms
Any Sugguestions on how to fix? im stumped
Hmmm maybe I'll hold off installing LOS20
billyb1987 said:
Hmmm maybe I'll hold off installing LOS20
Click to expand...
Click to collapse
i advice against installing any android 13 gsis, i have tested rooted/unrooted, Magisk Rooted, and Inbuilt superuser
Ive tried every single android 13 gsi out there, AOSP, ArrowOS, Evolution X, you name it, ive tried android 12, 12L and 13 roms, If you have any questions about other specific roms and my results feel free to ask me, but as a general rule, Android 12 works fully on lighter roms, but Android 13 is a Glitchfest
MrFluffyOven said:
i advice against installing any android 13 gsis, i have tested rooted/unrooted, Magisk Rooted, and Inbuilt superuser
Ive tried every single android 13 gsi out there, AOSP, ArrowOS, Evolution X, you name it, ive tried android 12, 12L and 13 roms, If you have any questions about other specific roms and my results feel free to ask me, but as a general rule, Android 12 works fully on lighter roms, but Android 13 is a Glitchfest
Click to expand...
Click to collapse
Sure...a question - have you ever been able to flash a non LOS GSI successfuly (besides PHH based ones)? I've probably tried just as many GSIs and all the rest seem to be too big
kevinco1 said:
Sure...a question - have you ever been able to flash a non LOS GSI successfuly (besides PHH based ones)? I've probably tried just as many GSIs and all the rest seem to be
Click to expand...
Click to collapse
As a general rule, if the image is a very basic image without the modifications so for example AOSP 12, that is generally smaller in size it works, if you get a really heavily modified system, to pull some out of a hat Evolution X, Project Elixir they get stuck on the Samsung screen and just sit there for days, so the smaller roms android 12 work really well, but the bigger ones don't
However Android directly from the developer site works even on android 13, 14, the only drawback if there's no compatibility layers for bluetooth
MrFluffyOven said:
As a general rule, if the image is a very basic image without the modifications so for example AOSP 12, that is generally smaller in size it works, if you get a really heavily modified system, to pull some out of a hat Evolution X, Project Elixir they get stuck on the Samsung screen and just sit there for days, so the smaller roms android 12 work really well, but the bigger ones don't
However Android directly from the developer site works even on android 13, 14, the only drawback if there's no compatibility layers for bluetooth
Click to expand...
Click to collapse
Yeah I figured that all out...but larger ROMs like Evolution and Elixir based off of A12 don't work as well? Just tried the A13 based ones
MrFluffyOven said:
okay so ive tested a number of treble GSI's on SM-X200 but im finding that the device randomly reboots on all Android 13 GSIS, now when i say reboots im talking about youve set up, youve loaded the tablet, your just using your tablet as you normally will and the device reboots
Lineage OS 19 works perfectly fine without reboots, but as soon as i flash LOS20 GSI it reboots all the time
What makes it even more strange is when i install Android 14 Beta GSI i get no reboots, but then i have another problem where my Device cant connect to any bluetooth Devices, so the GSI itself is really stable, but i use Bluetooth Earphones, and Googles Android GSIS dont have the PHH settings menu, which fixes the problem on all other roms
Any Sugguestions on how to fix? im stumped
Click to expand...
Click to collapse
Does the boot logo appear twice when it reboots?
andr_SMOLKEYS said:
Does the boot logo appear twice when it reboots?
Click to expand...
Click to collapse
on odd occasions its been the logo from the GSI itself, others it reboots back to Samsung, and starts the whole tablet again, either way its quite annoying
andr_SMOLKEYS said:
Does the boot logo appear twice when it reboots?
Click to expand...
Click to collapse
By this, I meant does the "Samsung Galaxy" text appear once, disappear, then reappear again? If so, then the tablet is going through a kernel panic/crash. One major way of knowing this is when music playing through the speakers repeats and then stops after a bit. Another way of knowing is if a chunk of text appears at the top left of the screen.
andr_SMOLKEYS said:
By this, I meant does the "Samsung Galaxy" text appear once, disappear, then reappear again? If so, then the tablet is going through a kernel panic/crash. One major way of knowing this is when music playing through the speakers repeats and then stops after a bit.
Click to expand...
Click to collapse
sounds familliar, and yes when it reboots to the samsung logo, theres some script in the top left, then it reboots again, if thats the case is there currently a fix?
Are you rooted? If so, check out /sys/fs/pstore/console-ramoops-0 and send me its contents.
If you can't do that, do you use mobile data?
Do I have to be using one of the roms thats causing the reboot in order to get the information you need, if so I'll flash one now and get you the information, yes rooted with magisk 26.1
MrFluffyOven said:
Do I have to be using one of the roms thats causing the reboot in order to get the information you need, if so I'll flash one now and get you the information, yes rooted with magisk 26.1
Click to expand...
Click to collapse
For an idea...I'd try patching again with either Magisk 25.2 or Delta. 26 has been giving a lot of people trouble, especially with Samsung devices
Whatever caused the kernel panic was resolved by refreshing stock firmware, including repartition, and refreshing los20 its not doing it now, I'll pay close attention to what happens from here, I'm using the latest los20 gsi from June, there's 2 possibility, the less likely being the new rom had something change thats stopped the device getting irritated, but the most likely thing is that in refreshing stock firmware and flashing los20 after something got fixed that was broken, either way, working now
kevinco1 said:
Yeah I figured that all out...but larger ROMs like Evolution and Elixir based off of A12 don't work as well? Just tried the A13 based ones
Click to expand...
Click to collapse
Non Treble gsis work, I tried a leaf os gsi that didn't support Treble, and everything worked, Google gsis have a Bluetooth issue which don't work on audio devices, everything else works perfectly, I'm pretty sure there's a magisk patch for the audio problem