[Q] Gapps Package Bugs.. where to report? - Android Q&A, Help & Troubleshooting

While testing CM7.1 I found that my google cloud backup was not working.
Restore worked fine, but backup was enabled, but not provisioned.
So I started reproducing that error, created logs and finally found that there is an incompatible version mismatch between several components of the gapps package.
In this special case, the GoogleBackupTransport.apk shows version 2.3 whereas other components show version 2.3.3 and 2.3.4 - a colorful mixture...
Some code from the newer packages is calling a service intent of GoogleBackupTransport which does not exist in version 2.3.
Read the full "story" in CM bug tracker, issue 4353 (I'm not allowed yet to post URLs here)
CM Team told me that they are not responsible for gapps - which I understand and respect.
So where could I report such an issue? Who created those packages?
In my special case, I used a newer GoogleBackupTransport.apk from an older Oxygen ROM, based on 2.3.5 - backup is working fine now, I'm happy.
I also considered creating a gapps package based on the 2.3.7 Versions that can be found in the oxygen-rom repositories, but those are not universal packages with all DPI versions, so I won't do that work if that's not a full replacement for the universal package...
Now, how to proceed getting this fixed? Or who could (and likes to) build a universal gapps package based on 2.3.7. A consistent package might solve other maybe yet undiscovered issues as well.
Edit: I'm talking about gapps-gb-20110828-signed.zip, but older versions are affected, too.

Any luck addressing this? I'm having the same problem.

No, nothing happened. This will be fixed in ICS Gapps, as this is a complete new package.
To workaround this issue, do the following:
Get the GoogleBackupTransport apk in Version 2.3.7. You could extract it from the latest Oxygen ROM, for example (www.oxygen.im), or go to the oxygen github repository if you do not want to download the whole ROM, get it here:
https://github.com/oxygen-rom/android_vendor_google/tree/gingerbread/system/app
Replace the old Version in your ROM, then delete data partition.
You have to run the Setup wizard again to activate the backup system, the only way to do this is a factory reset or a clear data from recovery.
Sent from my HTC Desire using XDA App

Related

Google apps for Wildfire on Froyo 2.2

I am looking for Google Apps for Froyo 2.2 (WildPuzzel ROM) for wildfire. can anyone send me link to download please
Thanks,
AQ
why do'n't you use a Market or google search?
eversyt said:
why do'n't you use a Market or google search?
Click to expand...
Click to collapse
I Did, currently google apps flash-able package is available for CM7 ROMs but cant find for froyo.
And another point is, i corrupted my market app.. cant download any app now
I think Google talk is also not available in the android market.
why i posted:
ROM developers may have it that's why i posted maybe someone can provide one.
otherwise i will extract apk from ROM and try to create update zip. might be useful for others too
GApps packages are only for CM Rom's (And AOSP ones), since, those ROMs by themselves do not have any Google copyrighted stuff.
Sense based ROMs do not need GApps packages because most of them include it by default. Or, even if they do not include the apps package, they include atleast the Market app,
Seeing that, as you have put, your best bet would be to extract the APK and create the Update Zip yourself.
Looks like there is more than corrupt application in my case. I have created and flashed update even individually installed apks and services over existing ROM but getting FC on launching the application. Setup Wizard doesn't seems to work anymore and getting FC in loops.
Some unknown system components or services also seems to be affected. I think I would need to go back and restore nandroid or reflash the ROM
time to flash a New ROM for primary use. and keeping nandroid backups for test purpose. as a Primary ROM I will prefer CM 7.0.3, Wildpuzzel freezes sometimes during a call. i have used cm7 before but for test purpose. So i till go for CM7 and look for solution to connect ad-hoc wifi
why not just reflash your rom and make a backup of any data you want before hand

Maps API unavailable with codeworkx CM10 + gapps 0726

Ever since I've started working the CM10 builds from codeworkx (which, by the way, are amazing), I've had a persistent problem with the Google Maps API not being available. Google Maps itself continues to work fine, but apps which depend on it don't work anymore. In the case of Instagram it just means I can't use the photomap which isn't a huge problem, but for apps like Uber and AirBNB it means that I can't install them at all (they show up as incompatible). Trying to install the apps via adb also fails with INSTALL_FAILED_MISSING_SHARED_LIBRARY.
I've tried installing a few different versions of gapps (currently using 20120726 since it's the most recent) and it hasn't helped. I also found some instructions for fixing this issue a while ago by updating the relevant files directly (can't post the link, but it's on slatedroid and the article is "fixing the INSTALL_FAILED_MISSING_SHARED_LIBRARY error") but it hasn't helped either.
I've tried all of this both with an updated CM10 build as well as after doing a full wipe and install of the updated ROM with no change.
Any ideas on what could be going on? Is there anything else I can try?

[Q] "Status 7" error while installing CM 10.1 7/28 and 7/27 nightlies

Hello,
I'm trying to install CM 10.1 on my HTC One on T-Mobile. Im using CWM Touch v6.0.3.3. I've tried flashing both the 7/28 and the 7/27 daily builds of CM 10.1 as found on the cyanogenmod website. I selected the T-Mobile version of the software "m7tmo.zip" and tried uploading it, but got the error "status 7". It says "assert device: getprop" and then says a bunch of code about the product names "m7" and "m7tmo". So somehow I think there's a problem with the device and the software matching, even though I'm pretty sure I'm getting it from the official place. Currently I'm using the stock Sense 5 firmware, but I don't have Google Play access because I mistakenly installed the gapps. package (for Android 4.2). Does any one know of CM builds that work right now? And in the short term (and for my own edification), is it possible to download an older version of the gapps package that works with Android 4.1 that I can use?
Thanks for all your help!
Gapps: http://wiki.rootzwiki.com/Google_Apps
Lists Gapps packages by Android build. You should be good to go there.
CM10:
Use TWRP instead of CWM: http://teamw.in/project/twrp2/164
CM10: http://get.cm
Hope this helps.
Sent from my Nexus 10 using Tapatalk HD
Thanks for the link. I'm downloading the older version of GApps now. A little while ago I tried installing the older GApps package straight through ROM Manager but I don't think it worked. I'm still having trouble, except now I can't get into the play store and Drive won't sync, but other google services (gmail, etc) are working. Somehow, trying to install the GApps package via ROM Manager seems to have broken ROM Manager itself - I get an error message when I try to run it... and of course I can't just uninstall because I don't have Google Play access .
As for using TWRM, I tried already, but for some reason I don't see any files come up when I try installing a .zip package. I'm pretty sure I'm in the right spot and yet TWRM only ever shows directories with no files in any of them.
I think it's also worth mentioning that I have S-ON still, and the only methods I've seen to get S-OFF involve downloading apps from the play store which I don't have (ie. some terminal emulator and a different ROM app). I know its possible to do it through a computer but I haven't been able to find good documentation on how to do it.
So I think my troubleshooting flow chart looks something like this:
Fix Play store error > use terminal emulator to turn S-OFF > flash a better recovery file > install ROM of choice (after some more research I think i'll go with SentinelMod, any one use that one?)
Thanks again for the help folks!

[Q] How to deactivate wipe in zip ROM

Hi!
The main thing I am looking for, is how to make a zip version of a ROM stop erasing everything from the previous version and only update it.
More details about why I need this, below:
I have a SMARTQ Z Watch and the latest official ROM v3.7 no longer has the remote camera function. It was deleted starting with version 3.2, so 3.1 must have been the last to have it.
If I install an older version, which has the remote camera function, it works, but updating to latest always wipes absolutely everything from the phone, including any apps and files installed manually.
Unfortunately, the remote camera function is not an apk that I can find in the system/app folder, so it must be somehow else build in the ROM. I have no idea how to locate it.
Any help to this request would be highly appreciated.
this is the latest 3.7 ROM http://d2.smartdevices.com.cn/files/SmartQ_EN_Z1_V3.7/update.zip
this is one of the older versions, which has the remote camera function included http://d2.smartdevices.com.cn/files/SmartQ_EN_Z1_V2.5/update.zip

[DEPRECATED][ROM][UNOFFICIAL][N][SM-T285] /e/ OS for Samsung Galaxy Tab A 7.0 LTE (gtexslte) | BYE Google, HELLO Privacy!

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
brought to you by the
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
About /e/
/e/ is an a mobile ecosystem (ROM + onlines services) that:
is open source
is pro-privacy
is compatible with most existing Android applications
cares about usability
is as far as possible freed from shackles by Google and OEMs
already exists!
It’s the alternative to the Apple/Google duopoly on the smartphone.
... so again and just to be clear: /e/ is not just a ROM, it is more a complete privacy ecosystem and consists of:
an installable mobile operating system for smartphones, which is forked from Android and strongly “ungoogled”
a set of sorted and improved default open source applications
various online services that are linked to the mobile operating system, such as: a meta search engine for the web, drive (with synchronization), mail, calendar, notes, tasks.
Features
Based on the stable Lineage OS
microG fully pre-installed with Signature Spoofing in restricted mode!
All features described on the /e/ page: What is e
All features and fixes of LineageOS
My builds come with full OTA update support
... you know that thing which informs you that a new update is there and where you just click to download + install
Difference from pure /e/ or: why are the builds UNOFFICIAL?
There are no differences. its pure /e/. "just" build on my server
Known issues:
Keep in mind that this is brand new stuff so it may (still) contain unknown issues!
So back up regularly and frequently!
Camera does work but only for photo, i.e. video recording fails.
If you find a bug not listed let me know and SHARE LOGS! -> READ FAQ#1 for how to provide proper logs.
Requirements
Latest TWRP or SHRP (recommended) build.
Do a full (i.e. Nandroid) backup before doing anything!
Samsung STOCK firmware should be on T285XXU0AQH1.
You can check your current firmware version in Android -> settings -> About / Phone info -> Baseband version
If you like try first without flashing this firmware but if you encounter any issues upgrade to this version first before reporting
Fast and (afaik) good site for downloading: https://sfirmware.com/samsung-sm-t285/
(scroll down and type T285XXU0AQH1 in the search box, choose the one for your country, download, flash as usual, flash TWRP/SHRP again, flash this ROM)
Installation
Full clean install as described here (FAQ #2) is highly recommended. DO NOT REPORT ISSUES when you have skipped that step!
Flash /e/
Optional (if you want root): Flash Magisk
Flashing OpenGapps ????? STOOOOOOP! NO No no! you don't want that on a google-free phone! /e/ contains everything you need to live without Google! So flashing OpenGapps on /e/ is like using a bit more secure LOS but that's not the point of /e/. Either try without or go with LOS (imho).
Boot it (will take a bit on first boot!!! be patient!)
Enjoy the most easiest way to have a privacy focused and google-free phone!
Download
Get your builds from my leech server (new installs or re-installs)
http://leech.binbash.rocks:8008/e-os/nougat/gtexslte/
If you have a previous version of my(!) /e/ ROM installed already and just want to update to a newer release:
Android settings -> Updater (yes my builds have built-in OTA support!)
Note:
Builds are updated as soon as possible. There is no build cycle.
Information pertaining to your device is displayed accordingly.
The current build is the latest for your device.
Changelogs
search results from this thread: click
Support
Of course in this thread but also by Telegram.
I have created a generic group for all stuff around Android : here
and another one if you want to keep up2date whenever I build something (TWRP, SHRP, LOS, /e/, ...): here
Credits
jedld, really he did a great job and making this project possible at first!
LineageOS (the base of /e/)
The /e/ foundation and all related devs making this experience possible!
and all I forgot to mention ....!
Sources
build manifest
XDA:DevDB Information
gtexslte_eos-n_unofficial, ROM for the Samsung Galaxy Tab A series
Contributors
steadfasterX, jedld(!)
Source Code: https://gitlab.e.foundation/e
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information
Status: Beta
Created 2020-11-18
Last Updated 2020-11-18
FAQ
Frequently Asked Questions (FAQ)
Q #01: I want to report an issue. What is the proper way to do so?
I'm glad that you are asking: before doing so check the KNOWN ISSUES topic in the OP and ofc the other FAQ's listed here!
if you have an audio issue follow FAQ #6 instead.
If your issue is not listed there click here to proceed:
If your issue is not listed there follow the directions here briefly and I may can fix it:
logcat GUIDE
Ensure you have done a full CLEAN install before doing so (refer to FAQ #2 for what that means).
Warning: NO SUPPORT when:
- magisk is installed (known to cause issues sometimes - regardless of the ROM or version)
- Xposed is installed (known to cause issues sometimes - regardless of the ROM or version)
If you have installed any of these UNINSTALL or better do a FULL CLEAN install (see FAQ #2) before doing anything else. Often enough these above causes several issues like battery draining, problems on booting and much more. Even when they may work properly you should re-produce your issue without them first and follow the above to grab the log.
Magisk is a great piece of software and besides that it is Open Source which SuperSu never was.
I just saying I do not "support" issues when you have Magisk installed. Why? It is (like Xposed) extendable with modules (made by whoever) and those can cause billions of issues.
Other then that magisk was sometimes the reason for battery drain etc. Magisk modifies the boot "process" and sits very deep in the system (which is needed to make it work ofc) but that has the potential to make a system/ROM unstable or result in strange behaviors.
so in order to support a specific issue I have to be sure the ROM is in a "clean" state, no magisk, no xposed.
Pro-Tip: a very first test is to set magisk on core functions only to see if an extension causes your issue or not.
Q #02: I want to install clean, how? What is a clean install? What is the recommended way to flash a new ROM version?
A clean install ensures that there are no leftovers from any previous install. One can say that there are 2 phases of a clean flash:
1) regular
2) full - when you (still) encounter issues
Usually the regular one is fully ok when flashing a new ROM version but if you encounter strange issues nobody else is reporting or if a release post is recommending it you should do a full clean install instead.
A regular clean install can be done like this:
WIPE -> Advanced -> select: System + Cache
Flash the ROM
reflash root addon/magisk if you want root
A full clean install needs 2 steps more then the regular:
follow the steps for regular clean
go back in WIPE -> touch the "FORMAT data" button and type "yes" to format the internal storage (you will LOOSE ALL YOUR DATA - obviously)
REBOOT -> Recovery
Flash the ROM
reflash root addon/magisk if you want root
It is absolutely recommended to create a backup before and COPYING IT to your PC(!) before doing the above.
Q #03: Are there any plans or a chance of official /e/ builds?
No plans on my site. I may check that later but the chance is very low.
Q #04: Will this ROM support / pass SafetyNet?
When you install Magisk you can hide and so yes you might be able to pass SafetyNet. Which can change every day though because even when that might work atm you should note the following:
Magisk has its own protections to ensure you pass safetynet but this is something which will change one day and there is no known method yet to workaround that.
Q #5: Is there an /e/ specific FAQ?
Sure:
FAQ: click
Forum: click
HOWTOs: click (a great resource for all your first questions)
Q #6: issues with audio (e.g. echo's, silence on one or the other site, ..)? Read here how to provide a specific log for that:
Do the following steps:
1) Ensure you have adb set up on your PC, and have adb debugging and adb root enabled in developer options on your phone
2) Then perform the following (all one command)
On Linux:
adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver" && sleep 10 && adb logcat -b all |egrep -vi "(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)"
Click to expand...
Click to collapse
On windows:
adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver && sleep 10 && logcat -b all |egrep -vi '(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)' "
Click to expand...
Click to collapse
3) Then re-produce your audio issue and cancel the logcat from step 2 before hanging up!
4) Share the logcat output from the console screen using paste.omnirom.org
Q #7: I'm scared about that microG , I don't want to expose my phone so is this /e/ version a security risk?
First of all you need a lot of trust installing ANY custom ROM. A developer can do nasty things right? Besides that yes microG allowing to let apps act like as they are another app, also known as signature spoofing. This CAN be a good and a bad thing. Read on why my builds are different:
In general the microG patch is an all or nothing. A ROM which supports microG (i.e. signature spoofing) have that feature enabled, always.
The difference in my /e/ builds is that I am using the "restricted" option of signature spoofing so as long as you trust me you are as safe as without microG.
.-
steadfasterX said:
Frequently Asked Questions (FAQ)
Q #01: I want to report an issue. What is the proper way to do so?
I'm glad that you are asking: before doing so check the KNOWN ISSUES topic in the OP and ofc the other FAQ's listed here!
if you have an audio issue follow FAQ #6 instead.
If your issue is not listed there click here to proceed:
If your issue is not listed there follow the directions here briefly and I may can fix it:
logcat GUIDE
Ensure you have done a full CLEAN install before doing so (refer to FAQ #2 for what that means).
Warning: NO SUPPORT when:
- magisk is installed (known to cause issues sometimes - regardless of the ROM or version)
- Xposed is installed (known to cause issues sometimes - regardless of the ROM or version)
If you have installed any of these UNINSTALL or better do a FULL CLEAN install (see FAQ #2) before doing anything else. Often enough these above causes several issues like battery draining, problems on booting and much more. Even when they may work properly you should re-produce your issue without them first and follow the above to grab the log.
Magisk is a great piece of software and besides that it is Open Source which SuperSu never was.
I just saying I do not "support" issues when you have Magisk installed. Why? It is (like Xposed) extendable with modules (made by whoever) and those can cause billions of issues.
Other then that magisk was sometimes the reason for battery drain etc. Magisk modifies the boot "process" and sits very deep in the system (which is needed to make it work ofc) but that has the potential to make a system/ROM unstable or result in strange behaviors.
so in order to support a specific issue I have to be sure the ROM is in a "clean" state, no magisk, no xposed.
Pro-Tip: a very first test is to set magisk on core functions only to see if an extension causes your issue or not.
Q #02: I want to install clean, how? What is a clean install? What is the recommended way to flash a new ROM version?
A clean install ensures that there are no leftovers from any previous install. One can say that there are 2 phases of a clean flash:
1) regular
2) full - when you (still) encounter issues
Usually the regular one is fully ok when flashing a new ROM version but if you encounter strange issues nobody else is reporting or if a release post is recommending it you should do a full clean install instead.
A regular clean install can be done like this:
WIPE -> Advanced -> select: System + Cache
Flash the ROM
reflash root addon/magisk if you want root
A full clean install needs 2 steps more then the regular:
follow the steps for regular clean
go back in WIPE -> touch the "FORMAT data" button and type "yes" to format the internal storage (you will LOOSE ALL YOUR DATA - obviously)
REBOOT -> Recovery
Flash the ROM
reflash root addon/magisk if you want root
It is absolutely recommended to create a backup before and COPYING IT to your PC(!) before doing the above.
Q #03: Are there any plans or a chance of official /e/ builds?
No plans on my site. I may check that later but the chance is very low.
Q #04: Will this ROM support / pass SafetyNet?
When you install Magisk you can hide and so yes you might be able to pass SafetyNet. Which can change every day though because even when that might work atm you should note the following:
Magisk has its own protections to ensure you pass safetynet but this is something which will change one day and there is no known method yet to workaround that.
Q #5: Is there an /e/ specific FAQ?
Sure:
FAQ: click
Forum: click
HOWTOs: click (a great resource for all your first questions)
Q #6: issues with audio (e.g. echo's, silence on one or the other site, ..)? Read here how to provide a specific log for that:
Do the following steps:
1) Ensure you have adb set up on your PC, and have adb debugging and adb root enabled in developer options on your phone
2) Then perform the following (all one command)
On Linux:
On windows:
3) Then re-produce your audio issue and cancel the logcat from step 2 before hanging up!
4) Share the logcat output from the console screen using paste.omnirom.org
Q #7: I'm scared about that microG , I don't want to expose my phone so is this /e/ version a security risk?
First of all you need a lot of trust installing ANY custom ROM. A developer can do nasty things right? Besides that yes microG allowing to let apps act like as they are another app, also known as signature spoofing. This CAN be a good and a bad thing. Read on why my builds are different:
In general the microG patch is an all or nothing. A ROM which supports microG (i.e. signature spoofing) have that feature enabled, always.
The difference in my /e/ builds is that I am using the "restricted" option of signature spoofing so as long as you trust me you are as safe as without microG.
.-
Click to expand...
Click to collapse
Very nice job. Looking awesome:good:
Everything is ok except some problems/issues.
First is the camera. As you have said, camera does work but only for photo. But it only happens on the foundation.e.camera (default camera app). And in other apps require camera such as Qanda, it does not work. Like this:
The second problem is the cellular (or phone signal) problem. It says that "Emergency calls only" and I can't use mobile data(4g) or make any phone calls.
The next one is stability. Sometimes Espeak have fc (force-close) after using camera app.
and sometimes Bliss launcher (pre-installed) have some fc when i press home button.
Sorry if I can't provide to you the proper log because of some reasons.
Anyways, the rom works very well and actually better than the LOS i used before.
Without Google spyware, The performance increases and i have more ram to do other things.
I hope you will fix those issues i have mentioned above in future OTA updates.
Thank you for the nice work.
espeak is a known issue of /e/ OS and should be fixed hopefully anytime soon: https://gitlab.e.foundation/e/backlog/-/issues/1890
cam is nothing I will work on sorry..
signal issue is very likely because of your STOCK firmware --> make a screenshot of the full " about" menu in settings (where you see build number etc)
Can I encrypt /data partition like in the Settings > Encryption > Encrypt phone
and Encrypt SD Card with this ROM?
Also, how stable it is for daily driver/use?
Did you fix the mic routing issue when in call? Use earphone mic instead of the built in mic of the tablet?
How about the video when app like Element.io or some other video conferencing apps?
steadfasterX said:
espeak is a known issue of /e/ OS and should be fixed hopefully anytime soon: https://gitlab.e.foundation/e/backlog/-/issues/1890
cam is nothing I will work on sorry..
signal issue is very likely because of your STOCK firmware --> make a screenshot of the full " about" menu in settings (where you see build number etc)
Click to expand...
Click to collapse
Here are some screenshots
This one is from "about tablet" menu.
And I bonus some screenshots include some information i have from the "Device info HW" app (ru.andr7e.deviceinfohw, maybe you've already known it before).
That's all the screenshot i provided.
GAPS does not work. I'm using the open_gapps-arm-7.1-nano-20170503.zip version
ijlara said:
GAPS does not work. I'm using the open_gapps-arm-7.1-nano-20170503.zip version
Click to expand...
Click to collapse
Uhm.. Maybe read the OP again??
Sorry ... I really read it and ended up forgetting that GAPS doesn't work ....
johnnyhoang said:
Everything is ok except some problems/issues.
First is the camera. As you have said, camera does work but only for photo. But it only happens on the foundation.e.camera (default camera app). And in other apps require camera such as Qanda, it does not work. Like this:
The second problem is the cellular (or phone signal) problem. It says that "Emergency calls only" and I can't use mobile data(4g) or make any phone calls.
The next one is stability. Sometimes Espeak have fc (force-close) after using camera app.
and sometimes Bliss launcher (pre-installed) have some fc when i press home button.
Sorry if I can't provide to you the proper log because of some reasons.
Anyways, the rom works very well and actually better than the LOS i used before.
Without Google spyware, The performance increases and i have more ram to do other things.
I hope you will fix those issues i have mentioned above in future OTA updates.
Thank you for the nice work.
Click to expand...
Click to collapse
ok your cell service issue could come from a too old stock firmware. yours is from 2016 and there were some releases later on.
I have adjusted the OP with instructions (pls see topic "Requirements") with the firmware I am using without issues.
.-
It is difficult to find a ROM that works well on this device. It is for my daughter and I also can't get a ROM that works with Samsung's Kids Mode.
steadfasterX said:
ok your cell service issue could come from a too old stock firmware. yours is from 2016 and there were some releases later on.
I have adjusted the OP with instructions (pls see topic "Requirements") with the firmware I am using without issues.
.-
Click to expand...
Click to collapse
i have tried so many ways. And it is not working after all.
installed T285XXU0AQH1 baseband from the BTU csc , but the cell service issues still happening.
my original csc is XXV, and the latest update still T285XXU0API1 baseband (20171115 ver.)
johnnyhoang said:
i have tried so many ways. And it is not working after all.
installed T285XXU0AQH1 baseband from the BTU csc , but the cell service issues still happening.
my original csc is XXV, and the latest update still T285XXU0API1 baseband (20171115 ver.)
Click to expand...
Click to collapse
uhm.. well that was not what I said. I did not say "install the baseband" I said install the FULL(!!!!!) STOCK firmware. Here again:
Samsung STOCK firmware should be on T285XXU0AQH1.
You can check your current firmware version in Android -> settings -> About / Phone info -> Baseband version (===> hint: this info is the best indicator to find out your current STOCK firmware, afaik)
If you like try first without flashing this firmware but if you encounter any issues upgrade to this version first before reporting
Fast and (afaik) good site for downloading: https://sfirmware.com/samsung-sm-t285/
(scroll down and type T285XXU0AQH1 in the search box, choose the one for your country, download, flash as usual, flash TWRP/SHRP again, flash this ROM)
There is nothing mentioned to extract just a subset and only flashing a subset. No. flash it completely or leave it. Just flashing part of it will break and/or even hard brick.
steadfasterX said:
uhm.. well that was not what I said. I did not say "install the baseband" I said install the FULL(!!!!!) STOCK firmware. Here again:
Samsung STOCK firmware should be on T285XXU0AQH1.
You can check your current firmware version in Android -> settings -> About / Phone info -> Baseband version (===> hint: this info is the best indicator to find out your current STOCK firmware, afaik)
If you like try first without flashing this firmware but if you encounter any issues upgrade to this version first before reporting
Fast and (afaik) good site for downloading: https://sfirmware.com/samsung-sm-t285/
(scroll down and type T285XXU0AQH1 in the search box, choose the one for your country, download, flash as usual, flash TWRP/SHRP again, flash this ROM)
There is nothing mentioned to extract just a subset and only flashing a subset. No. flash it completely or leave it. Just flashing part of it will break and/or even hard brick.
Click to expand...
Click to collapse
Ok,i have given up. I don't know the way to install that properly because of the CSC differences(you said it should be in T285XXU0AQH1 but it didn't available in my country XXV. XXV still use T285XXU0API1 even with the latest update from 2017). So i will use that normally bc i'm ok without cellular.​Btw things still work like a charm, and i have no regret of choosing this rom.
steadfasterX said:
uhm.. well that was not what I said. I did not say "install the baseband" I said install the FULL(!!!!!) STOCK firmware. Here again:
Samsung STOCK firmware should be on T285XXU0AQH1.
You can check your current firmware version in Android -> settings -> About / Phone info -> Baseband version (===> hint: this info is the best indicator to find out your current STOCK firmware, afaik)
If you like try first without flashing this firmware but if you encounter any issues upgrade to this version first before reporting
Fast and (afaik) good site for downloading: https://sfirmware.com/samsung-sm-t285/
(scroll down and type T285XXU0AQH1 in the search box, choose the one for your country, download, flash as usual, flash TWRP/SHRP again, flash this ROM)
There is nothing mentioned to extract just a subset and only flashing a subset. No. flash it completely or leave it. Just flashing part of it will break and/or even hard brick.
Click to expand...
Click to collapse
Sorry for misunderstanding.
I have found the reason why the cellular issues comes out. It is made by the SIM card itself, not the baseband version or the stock firmware version as you have said. I was wrong when i think that it come from the software or stock firmware. Now i found out the reason for that. Sincerely apologize to you.
johnnyhoang said:
Ok,i have given up. I don't know the way to install that properly because of the CSC differences(you said it should be in T285XXU0AQH1 but it didn't available in my country XXV. XXV still use T285XXU0API1 even with the latest update from 2017). So i will use that normally bc i'm ok without cellular.​Btw things still work like a charm, and i have no regret of choosing this rom.
Click to expand...
Click to collapse
Anyways thanks for noticing the recquirements. I think it is not necessary now since i found the real reason for the cellular issues.
When I changed another SIM card, it works flawlessly.
johnnyhoang said:
Sorry for misunderstanding.
I have found the reason why the cellular issues comes out. It is made by the SIM card itself, not the baseband version or the stock firmware version as you have said. I was wrong when i think that it come from the software or stock firmware. Now i found out the reason for that. Sincerely apologize to you.
Anyways thanks for noticing the recquirements. I think it is not necessary now since i found the real reason for the cellular issues.
When I changed another SIM card, it works flawlessly.
Click to expand...
Click to collapse
great stuff and thx for the feedback!
It ok, but google services framework stop. Fash zip Dolby Atmos (DAP_r6.5.zip) work Vanced manager install Youtube Vancednon root work. addonsu-14.1-arm-signed.zip work. VOLUME+BOOSTING+SOUND+(Very+Loud).zip work
binhdt said:
It ok, but google services framework stop. Can not flash zip Dolby Atmos, Vanced manager can not install Youtube Vanced
Click to expand...
Click to collapse
apps which require google crap will not work on /e/. That is by design..
You can browse the e foundation forum to find alternatives though.
How To's: https://doc.e.foundation/how-tos/
General Forum: https://community.e.foundation/
--> e.g a quick search here shows a bunch of alternatives for youtube: https://community.e.foundation/t/alternative-to-youtube/23703/10
or here another huge listing: https://github.com/tycrek/degoogle
Other alternatives: https://community.e.foundation/t/ho...urce-alternatives-of-your-apps-services/13616
.-
steadfasterX said:
brought to you by the
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
About /e/
/e/ is an a mobile ecosystem (ROM + onlines services) that:
is open source
is pro-privacy
is compatible with most existing Android applications
cares about usability
is as far as possible freed from shackles by Google and OEMs
already exists!
It’s the alternative to the Apple/Google duopoly on the smartphone.
... so again and just to be clear: /e/ is not just a ROM, it is more a complete privacy ecosystem and consists of:
an installable mobile operating system for smartphones, which is forked from Android and strongly “ungoogled”
a set of sorted and improved default open source applications
various online services that are linked to the mobile operating system, such as: a meta search engine for the web, drive (with synchronization), mail, calendar, notes, tasks.
Features
Based on the stable Lineage OS
microG fully pre-installed with Signature Spoofing in restricted mode!
All features described on the /e/ page: What is e
All features and fixes of LineageOS
My builds come with full OTA update support
... you know that thing which informs you that a new update is there and where you just click to download + install
Difference from pure /e/ or: why are the builds UNOFFICIAL?
There are no differences. its pure /e/. "just" build on my server
Known issues:
Keep in mind that this is brand new stuff so it may (still) contain unknown issues!
So back up regularly and frequently!
Camera does work but only for photo, i.e. video recording fails.
If you find a bug not listed let me know and SHARE LOGS! -> READ FAQ#1 for how to provide proper logs.
Requirements
Latest TWRP or SHRP (recommended) build.
Do a full (i.e. Nandroid) backup before doing anything!
Samsung STOCK firmware should be on T285XXU0AQH1.
You can check your current firmware version in Android -> settings -> About / Phone info -> Baseband version
If you like try first without flashing this firmware but if you encounter any issues upgrade to this version first before reporting
Fast and (afaik) good site for downloading: https://sfirmware.com/samsung-sm-t285/
(scroll down and type T285XXU0AQH1 in the search box, choose the one for your country, download, flash as usual, flash TWRP/SHRP again, flash this ROM)
Installation
Full clean install as described here (FAQ #2) is highly recommended. DO NOT REPORT ISSUES when you have skipped that step!
Flash /e/
Optional (if you want root): Flash Magisk
Flashing OpenGapps ????? STOOOOOOP! NO No no! you don't want that on a google-free phone! /e/ contains everything you need to live without Google! So flashing OpenGapps on /e/ is like using a bit more secure LOS but that's not the point of /e/. Either try without or go with LOS (imho).
Boot it (will take a bit on first boot!!! be patient!)
Enjoy the most easiest way to have a privacy focused and google-free phone!
Download
Get your builds from my leech server (new installs or re-installs)
http://leech.binbash.rocks:8008/e-os/nougat/gtexslte/
If you have a previous version of my(!) /e/ ROM installed already and just want to update to a newer release:
Android settings -> Updater (yes my builds have built-in OTA support!)
Note:
Builds are updated as soon as possible. There is no build cycle.
Information pertaining to your device is displayed accordingly.
The current build is the latest for your device.
Changelogs
search results from this thread: click
Support
Of course in this thread but also by Telegram.
I have created a generic group for all stuff around Android : here
and another one if you want to keep up2date whenever I build something (TWRP, SHRP, LOS, /e/, ...): here
Credits
jedld, really he did a great job and making this project possible at first!
LineageOS (the base of /e/)
The /e/ foundation and all related devs making this experience possible!
and all I forgot to mention ....!
Sources
build manifest
XDA:DevDB Information
gtexslte_eos-n_unofficial, ROM for the Samsung Galaxy Tab A series
Contributors
steadfasterX, jedld(!)
Source Code: https://gitlab.e.foundation/e
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information
Status: Beta
Created 2020-11-18
Last Updated 2020-11-18
Click to expand...
Click to collapse
I just flashed it and looks very nice thank you, titanium backup force closed, is there any restriction?
hotmatua.parulian said:
I just flashed it and looks very nice thank you, titanium backup force closed, is there any restriction?
Click to expand...
Click to collapse
Should work. Follow FAQ #1 in the second post

Categories

Resources