Related
{
"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"
}
On Google I/O 2013, Google has launched new IDE based on IntelliJ IDEA, called Android Studio. I'm really interested in Android Studio, given that I usually using Eclipse in developing Android application. I find that this IDE is really good (or should I say awesome!). But some of my friends said that they're having difficulties in using Android Studio, and prefer the 'good but old' Eclipse. Yes, Eclipse is good, but Google is more supporting the Android Studio. So with this articles, I want to share my experiences in migrating from Eclipse to Android Studio. I also included Google's official guide from d.android.com/
Let's start with pros and cons of Android Studio:
PROS:
- Better UI in designing and coding
- ProGuard and app-signing capabilities.
- Gradle-based build support (For you that has already get used to it)
CONS:
- Hard to manage multiple projects. (For example: to delete a project you have to delete from the explorer)
- Gradle-based build support (For you that's not get used to it)
- Still in EAP (Early Access Preview)
If you have something to say about PROS-&-CONS, I'm glad to hear from you.
Now move along to installing Android Studio. It's very easy.
First of all, go to http://developer.android.com/sdk/installing/studio.html and download the installer.
Windows:
- Launch the downloaded EXE file, android-studio-bundle-<version>.exe.
- Follow the setup wizard to install Android Studio.
- Known issue: On some Windows systems, the launcher script does not find where Java is installed. If you encounter this problem, you need to set an environment variable indicating the correct location. Select Start menu > Computer > System Properties > Advanced System Properties. Then open Advanced tab > Environment Variables and add a new system variable JAVA_HOME that points to your JDK folder, for example C:\Program Files\Java\jdk1.7.0_21.
Mac OS X:
- Open the downloaded DMG file, android-studio-bundle-<version>.dmg.
- Drag and drop Android Studio into the Applications folder.
- Known issue: Depending on your security settings, when you attempt to open Android Studio, you might see a warning that says the package is damaged and should be moved to the trash. If this happens, go to System Preferences > Security & Privacy and under Allow applications downloaded from, select Anywhere. Then open Android Studio again.
Linux:
- Unpack the downloaded Tar file, android-studio-bundle-<version>.tgz, into an appropriate location for your applications.
- To launch Android Studio, navigate to the android-studio/bin/ directory in a terminal and execute studio.sh.
- You may want to add android-studio/bin/ to your PATH environmental variable so that you can start Android Studio from any directory.
After you installed Android Studio, let your journey begin. But first, you must remember that Android Studio is still in EAP, so there will be many bugs/glitches/errors/whatever-you-call-it that can be annoying. But if you patient enough, you will find it very fun.
How to create project?
It's easy! Just use File -> New Project...
Or, if it's your first time using Android Studio, you will be welcomed with options to "Create New project"
Exploring your projects
File system is quite different with Eclipse. Considering that your android apps will be Gradle-based. So you just have to modify everything inside main project folder (See picture, file under "DMap" is main project folder). Unless you're an expert in Gradle and Intellij.
After you get used to the UI and layout, you can start coding & designing your app.
Designing Layout using Android Studio is Better?
Yes! You can see pictures below that you have 2 options to design layout. First by typing it directly through "Text" mode, or "Drag-and-drop" design. Both of them enable you to preview your design. Just have a 15-minutes experiments with your preview, and you will feel the power!
Let me give you some examples:
Design with "Text" mode
Design with "Drag and Drop" mode
How to include support library?
Another beautiful thing that announced in Google I/O 2013 is ActionBar Compat. I'm waiting it for a long time, because using "Sherlock ActionBar" is a little bit complicated. And now it's released. Download it with your SDK Manager.
Then include it in your project. How? Because this is Gradle-based, it's quite simple. Open "build.gradle" in your main project folder.
For Android-Support v4:
- It's automatically included when you created new project. But if not, use second step.
- Add this line:
Code:
dependencies {
...
compile "com.android.support:support-v4:18.0.+"
}
For Android-Support v7:
- Add this line:
Code:
dependencies {
...
compile "com.android.support:appcompat-v7:18.0.+"
}
How tot test your app?
Just like Eclipse, Android Studio support 2 way of testing. By using AVD (Android Virtual Devices) or by real devices. To edit configurations, go to "Run" -> "Edit Configurations". I recommend you to choose "Target Device" -> "Show chooser dialog", to give you more freedom in testing.
For AVD:
- You have to create at least one AVD. To create AVD, go to "Tools" -> "Android" -> "AVD Manager"
- In the chooser dialog, select AVD, and choose your devices.
For Real Device:
- You have to enable USB Debugging in your devices! Enable it, then go forward.
- Connect it through USB. In chooser dialog, you will see your device there.
Known issue: Sometimes the driver is not right. You should use Google USB Driver for testing app in Android. Or sometime, your device won't be detected if it's in sleep/locked mode.
How to generate a signed APK?
This is also easy! Android Studio is provided with App-signing capability so you don't have to open up your keytool or do somewhat-complicated task.
Here's some steps:
- Go to "Build" -> "Generate Signed APK..."
- Click "Create new..."
- To make a new keystore, just put a non-exist keystore in "Key store path:" (The folder MUST exist, while the file MUST NOT exist). And other details.
- It will automatically completed our last dialog in keystore. Just click "Next"
- And "Finish"
TIPS & TRICKS
If you want to change to Darcula Look and Feel, (in Windows) just press: "Ctrl + ~" -> "Switch Look and Feel" -> "Darcula".
This look and feel is very interesting, and I like it so much.
End of articles
It's easy doesn't it? There will be many improvements in the future that I don't know. But let's waiting for it. If you have any suggestions, questions, or even critics, just ask me. And also if you find it helpful, please click "Thanks" or "Donate". I will appreciate it very much.
Also check this official video from Google I/O 2013. About what's new in Android Studio
Multiple Projects
I currently have 8 active projects open in eclipse and during a single day I will work on at least 2-3 of them.
Does anyone know if android-studio will support this?
From what I have seen so far, it will only allow 1 project to be open at a time, this would mean have 4/5 android studios open at once just so that I can switch between projects.
Andy.
p.s. another question is : Can we use eclipse keystores for signing apps? if not what do we do about existing applications?
The thing that kept me off this was that it was impossible to correctly import an Eclipse project, when I tried it... I might give it a try by your instructions later.
Hi Andy,
Android Studio will separate your projects into multiple windows. But not multiple instances. So don't worry it will not consume your memory excessively.
And based on my experiences, Java keystore will be saved as (.keystore) file. So yes, even though you're using Eclipse or Android Studio both of them are the same. Just locate your keystore file, and "Choose existing...".
aspellclark said:
I currently have 8 active projects open in eclipse and during a single day I will work on at least 2-3 of them.
Does anyone know if android-studio will support this?
From what I have seen so far, it will only allow 1 project to be open at a time, this would mean have 4/5 android studios open at once just so that I can switch between projects.
Andy.
p.s. another question is : Can we use eclipse keystores for signing apps? if not what do we do about existing applications?
Click to expand...
Click to collapse
d.android.com has provided a useful solution for your problems, I think. Try this tips for export/import android projects from Eclipse to Android Studio. http://developer.android.com/sdk/installing/migrate.html
bassie1995 said:
The thing that kept me off this was that it was impossible to correctly import an Eclipse project, when I tried it... I might give it a try by your instructions later.
Click to expand...
Click to collapse
JoshieGeek said:
d.android.com has provided a useful solution for your problems, I think. Try this tips for export/import android projects from Eclipse to Android Studio. http://developer.android.com/sdk/installing/migrate.html
Click to expand...
Click to collapse
This way of working was not correctly working for me...
Have you checked that you do it right? For example: Have you export it from Eclipse first, then import it from Android Studio? And not import it directly from Android Studio?
Or do you have any specific screenshot for logs / things that can give me some clues?
bassie1995 said:
This way of working was not correctly working for me...
Click to expand...
Click to collapse
JoshieGeek said:
Have you checked that you do it right? For example: Have you export it from Eclipse first, then import it from Android Studio? And not import it directly from Android Studio?
Or do you have any specific screenshot for logs / things that can give me some clues?
Click to expand...
Click to collapse
I followed the steps, but long ago. I'm going to try again soonish.
Sent from my GT-I9300 using Tapatalk 4
Could someone give me a little guidance?
i checked that path and there isnt even a config folder.
Never mind, figured it out myself.
Has to make it run as administrator
Sent from my Galaxy Nexus
That's why if I'm using windows 7 (or above), I will not install some development-related programs to C partition. But another, it will be much more flexible to edit and something like that. By the way, you do a good job to solve your problems by yourself. Experimenting the problems is a good way to learn.
:good:
Garridon said:
Never mind, figured it out myself.
Has to make it run as administrator
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
JoshieGeek said:
For Android-Support v4:
- It's automatically included when you created new project. But if not, use second step.
- Add this line:
Code:
dependencies {
...
compile "com.android.support:support-v4:18.0.+"
}
For Android-Support v7:
- Add this line:
Code:
dependencies {
...
compile "com.android.support:appcompat-v7:18.0.+"
}
Click to expand...
Click to collapse
Thank you !
I think you mean "Android-AppCompat v7" not "Android-Support v7"
BTW when to use support-v4 vs appcompat-v7 ? What's the difference? Should I use both?
The difference is that appcompat-v7 will cover many more support libraries (for example: ActionBar compat). But your minimum version of App will be 7. So I recommend you to use appcompat-v7 than support-v4. Because there're not so many users that still using < v7.
From my experiences after I declare that dependencies, I got android support v4 and android v7. But still the minimum version MUST 7.
Have any questions? Feel free to ask me, I would be glad to help.
ceefour said:
Thank you !
I think you mean "Android-AppCompat v7" not "Android-Support v7"
BTW when to use support-v4 vs appcompat-v7 ? What's the difference? Should I use both?
Click to expand...
Click to collapse
JoshieGeek said:
The difference is that appcompat-v7 will cover many more support libraries (for example: ActionBar compat). But your minimum version of App will be 7. So I recommend you to use appcompat-v7 than support-v4. Because there're not so many users that still using < v7.
From my experiences after I declare that dependencies, I got android support v4 and android v7. But still the minimum version MUST 7.
Have any questions? Feel free to ask me, I would be glad to help.
Click to expand...
Click to collapse
Thanks Joshie! So appcompat-v7 it is...
So ActionBar is now provided by Google? So long Sherlock (it's still very nice though! yet I'm happy Google finally implements it too)
Yupz. And also implementation of Google's ActionBarCompat is very easy. So I prefer Google's to Sherlock..
But yeah, Sherlock is a good alternatives when Google has not even been releasing it.
Sent from my Nexus 4 using xda app-developers app
JoshieGeek said:
Yupz. And also implementation of Google's ActionBarCompat is very easy. So I prefer Google's to Sherlock..
But yeah, Sherlock is a good alternatives when Google has not even been releasing it.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I switched to the Google one, too. However, there is this annoying bug: http://code.google.com/p/android/issues/detail?id=58321
And it does not provide a PreferenceActivity with the ActionBar.
Waiting for the next version...
Yupz.. Wait for the next version... It's quite a small bugs, and they promise will fix it in next release..
nikwen said:
I switched to the Google one, too. However, there is this annoying bug: http://code.google.com/p/android/issues/detail?id=58321
And it does not provide a PreferenceActivity with the ActionBar.
Waiting for the next version...
Click to expand...
Click to collapse
Sent from my Nexus 4 using xda app-developers app
JoshieGeek said:
Yupz.. Wait for the next version... It's quite a small bugs, and they promise will fix it in next release..
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Well, if you want to implement multi-selection with it, it won't work.
However, a fixed version can be found here: https://github.com/CyberEagle/SupportLibraryV7AppCompatPatched
I'll use that till they publish the new version.
Starter choice : Eclipse or Android Studio?
Hi,
I'm currently an Enterprise Java developer and want to start building some apps in mobile space. As a new mobile developer, which one should I get start with now; Eclipse or Android Studio?
Regards
So now with GDR1 we have all the API for smartwatches, but MS decided to block this API from regular developers. Only for OEMs.
Still is there any way I can use methods from this class? When I'm trying I always get System.UnauthorizedAccessException exception.
Any ideas? Should I add some compatibility declarations to the manifest?
try
{
AccessoryManager.GetApps();
}
catch (Exception ex)
{
MessageDialog d = new MessageDialog(ex.ToString(),"Exception ");
d.ShowAsync();
}
I have not had experience with the WP8.1/WP8.1 Update 1 yet but it could be related to how you have to ask the user for permission in the new API. It looks like the process is not straight forward but I would research that.
How to access to that libraries
I just want to ask, how did you access to that libraries, i already installed GDR1 update, but I cant access to that libraries.
Thanks
as anyone got the access to this api?? how??
As Cyanogen pulled the plug on CyanogenMod, this project will continue under Lineage OS
{
"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"
}
This ROM is Alpha and not ready for daily use at the moment
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community
First I would like to thank the following developers :
@RaymanFX
@CTXz
I used @RaymanFX's T815 image to base my cm 13.0 build on, which in turn is the base of this cm-14.1.
Before you start
THIS ROM IS ONLY FOR THE SM-T810
Code:
*
* Your warranty will be voided !
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* 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.
*
About the ROM
Current state of ROM : testing
Everything except what's reported below is working (or not yet reported as not working).
What is Fixed
In '20-09' build reboot to recovery triggers message 'Factory reset'. (wrong messagem not resetting)
Camera not working in selinux enforcing
Front facing camera unable to save image
Bluetooth not working
Hardware codecs not working (fallback to software for mp3/flac works)
Limited wifi 5GHz support (channels above 100 give issues)
Video recording not working? (not tested on T810, reported not working on T815)
What is not working
Important
Fingerprint scanner not working
Minor
Compass is 180 degrees mis-aligned
Mic not working (no input routing)
Instructions
How to install CM13.0
If you haven't run stock Android 6.x, flash that first with odin. (image won't boot without this step)
If you don't have TWRP yet, get it from here : TWRP by ashyx
Download the ROM and the Gapps that are located below to your device
Reboot into TWRP by holding VOL UP + POWER + HOME on boot
In case things go wrong make a backup
After the backup has completed return to home and select Wipe and then Advanced Wipe
Now ONLY tick Dalvik Cache, System, Data and Cache
After ticking those, Swipe below to wipe
Once the wipe has completed return to home and select the ROM
After you selected the ROM swipe below to install it
After the ROM has installed flash the Gapps
When all of this is done, reboot into system, wait, and enjoy CM12.1
How to ROOT
In CM 14.1 Enable the developer options
Select Root access
Select Apps Only
Done
Questions and bug reporting
The following questions will be ignored
Inappropriate questions
Forced orders, EX. : "PLS FIX!!!!!!"
ETA's
Often repeated questions usually by the same user
Requests that are out of CM's framework (Ex. Adding Samsung Apps)
How to report a bug/issue
Explain exactly what happens
Mention a log if you can (Please use hastebin or any other paste site to keep the thread clean)
If you can't mention a log, explain as precise as possible when, why and where it occurs!
Changelog
Code:
**********
08-12-2016 - Compile with curren cm-14.1 source and [URL="https://review.cyanogenmod.org/#/c/173951"]this patch[/URL].
**********
25-11-2016 - Cm-14.0 is abandoned upstream, limiting uploads to cm-14.1.
- Recompile with camera fix merged in cm sources.
**********
21-11-2016 - Fixed camera (again).
**********
20-11-2016 - Broke camera in enforcing mode (unable to save picture).
**********
17-11-2016 - Recompile from clean tree, camera and youtube work now.
- Confirmed lock-screen-rotate fixed, but only after clean flash and [b]no restore of device ID[/b].
**********
14-11-2016 - First succesful cm-14.1 boot. (Switched project to cm-14.x)
**********
31-10-2016 - Selinux set to enforcing.
**********
12-10-2016 - Disabled telephony that got included regardless specifying I don't want it.
- Fixed several bluetooth issues
- Removed use of old api (v1) by camera
**********
03-10-2016 - First build with cm-14.0 release (previous were staging builds)
- Fixed bluetooth
**********
25-09-2016 - Fixed selinux contexts for camera so it works in enforcing mode
- Fixed front facing camera so it is able to save images.
**********
22-09-2016 - Reboot to recovery now triggers correct message
- 2nd build selinux permissive.
**********
20-09-2016 - 1st cm-14.0 build
**********
Downloads
Latest CM 14.1 build : https://www.androidfilehost.com/?fid=673368273298915423
All CM 14.1 releases can be found here : https://www.androidfilehost.com/?w=files&flid=128488
Recommended GAPPS by opengapps.org : http://opengapps.org/ (I use pico)
Source
Special Thanks to @RaymanFX for releasing his Exynos 5433 source, and already patching the common sources to cm-14.0, without him this ROM would most likely not be possible!
All my sources can be found here : https://github.com/CyanogenMod/android_device_samsung_gts210wifi
Screenshots
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
XDA:DevDB Information
CyanogenMod 14.1 for Tab S2 9.7 wifi, ROM for the Samsung Galaxy Tab S2
Contributors
T_I, Raymanfx, CTXz
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Stock Android 6.x flashed at least once before install
Based On: Cyanogenmod
Version Information
Status: Alpha
Created 2016-09-22
Last Updated 2016-12-29
Nice! Thank your very much for this early build!
I will try it as soon as I am able.
Sent from my SM-T810 using XDA-Developers mobile app
GO hard brother, thanks for all your efforts!
I've been using cm-14 since the 20-9 build, it's running pretty stable, although it's even more stable with selinux in permissive. Looks like some contexts have changed a bit in cm-14. (or the camera and some other routines ignore them)
I found 1 game not playing nicely with Nougat, CSR Classics, but the racing set from CSR work nicely, so I think that's a CSR related bug.
Fixed camera so it'll work in selinux enforcing (not yet activated) and front facing camera is able to save images.
Updated OP.
Awesome thank you!
@T_I Thought you might like 2 comments re your really great adaptation of CM14. Have been using your CM13 nightly downloads for about the last 5 weeks on my T810 and was so pleased with the result that I was slightly hesitant about trying CM14, however this afternoon I took the plunge and installed it as per your instructions. First impression is that I can hardly believe how problem free the installation of the Rom and the Open Gapps 7.0 pico proved to be.
I don't have a huge number of apps installed, about 30, but with one exception they are all performing as scheduled and I couldn't be more pleased, the one app that doesn't work is "Set CPU", there is no "forced closure", no error message, it just doesn't work. There are no forced closures of any other app including the Google Play & Services.
One point which might interest you as you mentioned it in your "OP" notes. I play mp4 movies using the app "MX Player Pro" with the Arm 7 codec installed and they play using the HW+ codec perfectly,
Was initially disappointed that "Theme Chooser" was missing from "Settings" but I can live with that considering how well everything else performs.
Once more congratulations on a really superb "port".
EDIT on 09.27.... @T_I I know this point is insignificant and pure "eye candy" but I love the touch ..... I'm talking about when one connects a usb connection from PC to S2 then the "icon" displayed at top left is now "N" (for Nougat ?) instead of the normal CM icon.
planning to attempt with the t710 again?lol
NalNalas said:
I've had this flashed since last night, and the battery so far has been great. Thanks a ton for this.
Click to expand...
Click to collapse
How much better would you say the battery life has been?
Would also appreciate input from anyone else whos noticed a difference (good or bad) with the battery life.
This ROM is working great so far!!
samsung_xoom said:
planning to attempt with the t710 again?lol
Click to expand...
Click to collapse
I can run a cm-14 build for T710 to see if that one boots.
I can test it and let you know , in my limited time I have lol
This rom is very stable, fast and reliable. The battery life is excelent. I use it as my daily driver since sept. 22!!! (Now i have a sept. 27 update)
Thanks T_I for your hard work!!!
Uploaded new image. @RaymanFX got bluetooth working on his device and the fix works on T810 as well. Also CM switched cm-14.0 from staging to release. There is still work to be done, but build shows working bluetooth (at least I can connect a keyboard and that one works).
I noticed crashing phone app and saw one ExchangeServices crash. (don't use both) Updates OP.
Latest build works wonders after I deleted from /system/app and /system/priv-app all the apks related to telephony/SMS/MMS/etc. for my T810.
EDIT: After some time, it all came crashing down, Play Services didn't like the removal of the packages, and some apps auto-removed themselves. Better wait until dev ships out another build.
Just tried to install the Oct 3 version of this ROM and as soon as it boots a box appears saying "com.android.phone has stopped". No matter how many times I click OK, the message just reappears and I can't get past it. Even have to use the power-home-vol- button combination to power off. This is on a T810 after full wipe, install ROM and install 7pico gapps. Tried the install three times. Coming from cellular south 6 ROM.
Please don't forget T710....
lewmur said:
Just tried to install the Oct 3 version of this ROM and as soon as it boots a box appears saying "com.android.phone has stopped". No matter how many times I click OK, the message just reappears and I can't get past it. Even have to use the power-home-vol- button combination to power off. This is on a T810 after full wipe, install ROM and install 7pico gapps. Tried the install three times. Coming from cellular south 6 ROM.
Click to expand...
Click to collapse
I got the same message, but can mute. Don't know where it comes from. I was working on the staging version of cm-14 and switched to the release version. Looks like there are some bugs left. (it's now less stable then with the staging cm-14)
T_I said:
I got the same message, but can mute. Don't know where it comes from. I was working on the staging version of cm-14 and switched to the release version. Looks like there are some bugs left. (it's now less stable then with the staging cm-14)
Click to expand...
Click to collapse
Just by clicking the OK button? Message just pop right back up when I do that.
lewmur said:
Just by clicking the OK button? Message just pop right back up when I do that.
Click to expand...
Click to collapse
I get the message with the 2 options 'stop application' and 'Mute until reboot'. The Mute option silences the warnings, but the app will still misbehave.
Exchange services I've been able to freeze, the phone app is also used for syncing contacts and I think calendar.
{
"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 our LOS 15.1 builds.
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 CUSTOM?
The /e/ app store has been removed completely (read FAQ #0 why I did this drastic change)
AuroraStore has been added (pls always use "anonymous" unless you need paid apps to avoid bans)
F-Droid has been added (The OpenSource alternative store. First search for any apps here!)
Dozens of F-Droid repositories are pre-installed (activate them with just a finger tip! That's needed to ensure you only get what you want)
The above changes are the reasons why my builds are of the type "CUSTOM" and not "UNOFFICIAL".
This is according to the rules defined by /e/.
Known issues:
Keep in mind that this is brand new stuff so it may (still) contain unknown issues!
So back up regularly and frequently!
When your current STOCK firmware or the latest you had flashed is PIE (Android 9) RIL will not work in this ROM. I am trying to fix that currently but while it works when your STOCK firmware/bootloader stack is on Oreo or earlier it stops working when you ever upgraded to pie
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 build.
Latest TWRP build based on Oreo sources (build by myself) can be found here: click
Do a full Nandroid backup before doing anything!
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 ????? 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 easy 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/oreo/
If you have /e/ installed already and just want to update to a newer release:
Android settings -> Updater (yes my builds have 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
nailyk
LineageOS (the base of /e/)
The /e/ foundation and all related devs making this experience possible!
The Exynos7870 Team
and more..
Sources
build manifest
XDA:DevDB Information
j5y17lte_eos-oreo_custom, ROM for the Samsung Galaxy J5
Contributors
steadfasterX, nailyk, ananjaser1211,DarkLord1731,Exynos7870 Team (github)
Source Code: https://gitlab.e.foundation/e
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: NOUGAT/OREO only - if you have stock PIE installed RIL won't work!
Based On: Lineage OS
Version Information
Status: Beta
Created 2020-08-05
Last Updated 2020-09-09
-
Frequently Asked Questions (FAQ)
Q #0: Why is the /e/ App store not included??? It is GREAT!
Mainly due to security and privacy concerns. Wth? I thought /e/ is secure and privacy focused? Yes it is but.. read on:
First of all the App store itself has no security or privacy issues. It is opensource and I see no issues with the app itself!
... the most important point for a smartphone is the availability of apps. I mean having a secure device which respects your privacy is great but it will have no chance to win when you cannot get easily apps on it.
... and the most dangerous part for a smartphone is installing apps because here is where Malware can easily step in! So whatever you do never install APK files from a website directly unless you can be 100% safe it is trustworthy.
It is all about trust again and when you look in the sources of the /e/ Apps store you find it connects to: cleanapk.org.
/e/ makes that not a secret though as you can read here.
So who is behind that cleanapk.org? Why is /e/ trusting them? While reading through the /e/ forums I found that this page hosts (as far as we know) apps mirrored from apkpure + fdroid.
.. and it's completely unclear who hosts that site and where is behind it. On the other site /e/ (Gael, the founder as well) states clearly they are not in any relation to that site. "They just using their api".
here some facts:
you cannot get the owner by a whois request
They have a info page here which just roughly describes where the apps are coming from and how
There is no detailed privacy statement or even an info if they keep your data GDPR compliant or not
No way for devs to get their apps removed or updated
The /e/ foundation clearly states they have no relationship to that repository of apps but some things are interesting aren't they:
IP's of /e/ and cleanapk are at least nearby
During an ongoing discussion about exactly that topic something took my attention: the welcome notification on api.cleanapk.org was exactly at that time: https://archive.is/U1E0y (I mean.... )
/e/ itself was audited several times by a site named "infosec-handbook" and of course even they find that app store at least "mysterious"
During that mentioned discussion and after pointing Gael to that - the welcome message suddenly changed to what it is today..
The full topic where even Gael is talking (not that friendly) is: here
TL;DR:
/e/ is providing apps (the most used way to get infected by malware) by an API which is at least questionable.
I do not say /e/ is doing questionable things and as said before the /e/ ROM is 100% trustworthy (otherwise I would not do any builds for it) but that cleanapk.org site is truly another story.
An interesting quote of Gael can make one read between the lines (I marked the interesting ones bold and cursive):
Some users have reported that they are using Aurora, [...] (context: we will never integrate this) because it’s infriging the play store terms of services.
For this, we have to use indirect mechanisms, that don’t infrige the play store TOS, and therefore, we are using a service that is not officially part of the /e/ project, and which is called cleanapk.org
On the long run, we other plans with partners, to offer something more transparent, but it’s too soon to talk about this.
Click to expand...
Click to collapse
Of course /e/ needs to ensure that what they are doing is 100% legal and offering an app repository like cleanapk.org is not.
My personal assumption is that /e/ is offering that repo - indirectly so not officially by the e.foundation itself.
A relation between is for sure nothing they want to have public as this would cause legal questions.
So the last question is:
Q: Why do I consider AuroraStore "better" then using cleanapk.org and so removed the /e/ apps store and adding AuroraStore instead?
A: Because I definitively know where the apps are coming from when using Aurora instead of /e/. Not just the app itself is OSS (like the /e/ one) the apps are coming directly from the play store instead of an unknown source.
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?
TL;DR answer is: who knows...
Background:
/e/ points to LineageOS requirements which need to be met first. LineageOS has "some" requirements before they accept it to do official builds: device-support-requirements.
No I personally do not have any plans in going official atm. That might change though.
If someone else wants to go that way and needs help, I am here. But I cannot spend my whole free time on that.
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.
.-
Reserved
Encryption of storage works?
jw96 said:
Encryption of storage works?
Click to expand...
Click to collapse
Haven't tested yet
Sent from my OnePlus 7T Pro using XDA Labs
I just installed it on my J5 2017 (SM-J530F). I did a full clean install (No magisk or xposed installed), but sadly my sim card is not detected.
Morceaux said:
I just installed it on my J5 2017 (SM-J530F). I did a full clean install (No magisk or xposed installed), but sadly my sim card is not detected.
Click to expand...
Click to collapse
yes one reason for that (I encountered that rn) might be the bootloader version.
What was the last stock ROM version you flashed? exact version if possible but at least if it was nougat, oreo, pie
or even better show a screen of "baseband version" in Android settings
.-
steadfasterX said:
yes one reason for that (I encountered that rn) might be the bootloader version.
What was the last stock ROM version you flashed? exact version if possible but at least if it was nougat, oreo, pie
or even better show a screen of "baseband version" in Android settings
.-
Click to expand...
Click to collapse
My baseband Version is "Unknow" rn, and I didn't check on my last ROM.
I used the stock ROM and was in pie version (I don't have the exact version rn, if you really want it I'll check tonight.
Do you want more informations ?
Morceaux said:
My baseband Version is "Unknow" rn, and I didn't check on my last ROM.
I used the stock ROM and was in pie version (I don't have the exact version rn, if you really want it I'll check tonight.
Do you want more informations ?
Click to expand...
Click to collapse
exactly what happened to me. I have upgraded the STOCK bootloader and modem to pie and RIL stops working. Was trying to figure out the reason for that but no luck yet.
so for sure the prev. STOCK version is an issue here. My last Samsung is a while ago so I dont know if one can downgrade without an issue or if I would brick it..
EDIT:
woa.. I cannot downgrade.. "check fail" in ODIN pointing to lower ARB levels.. damn.
so it seems that I have to find out the root cause for newer (i.e pie) bootloader stack
.-
steadfasterX said:
exactly what happened to me. I have upgraded the STOCK bootloader and modem to pie and RIL stops working. Was trying to figure out the reason for that but no luck yet.
so for sure the prev. STOCK version is an issue here. My last Samsung is a while ago so I dont know if one can downgrade without an issue or if I would brick it..
EDIT:
woa.. I cannot downgrade.. "check fail" in ODIN pointing to lower ARB levels.. damn.
so it seems that I have to find out the root cause for newer (i.e pie) bootloader stack
.-
Click to expand...
Click to collapse
I tried the same things last night, and I had the same problems (just so you know, If maybe it can help)
Morceaux said:
I tried the same things last night, and I had the same problems (just so you know, If maybe it can help)
Click to expand...
Click to collapse
thx. yes it definitively depends on the bootloader stack if it works or not. I have updated the OP with that information ("firmware required").
technical site info: I was able to flash the OREO radio (modem.bin) and cp_debug (modem_debug.bin) partitions without a problem but this alone does not make it work again.
Like for LG the 2nd stage bootloader likely initializes the hardware and the software (i.e. e.g. RIL) must know where and how these are loaded in memory etc. That's why just replacing the radio partitions will not fix it. RIL (and that is not just replacing a file) must fit to that as well..
The good news are: I am able to boot the radio now - PIN popup comes up and baseband is now correctly displayed (I am on the latest stock pie ROM available..)
but as you can see in the status bar still no cell service so still something missing..
IMEI is still 0 as well so it might has to do with the EFS.. which would explain it
but at least some progress.. At least it is clear now why some ppl reported on our LOS thread that SIM does not work for them while it worked for others.
.-
steadfasterX said:
thx. yes it definitively depends on the bootloader stack if it works or not. I have updated the OP with that information ("firmware required").
technical site info: I was able to flash the OREO radio (modem.bin) and cp_debug (modem_debug.bin) partitions without a problem but this alone does not make it work again.
Like for LG the 2nd stage bootloader likely initializes the hardware and the software (i.e. e.g. RIL) must know where and how these are loaded in memory etc. That's why just replacing the radio partitions will not fix it. RIL (and that is not just replacing a file) must fit to that as well..
The good news are: I am able to boot the radio now - PIN popup comes up and baseband is now correctly displayed (I am on the latest stock pie ROM available..)
but as you can see in the status bar still no cell service so still something missing..
View attachment 5078627
IMEI is still 0 as well so it might has to do with the EFS.. which would explain it
but at least some progress.. At least it is clear now why some ppl reported on our LOS thread that SIM does not work for them while it worked for others.
.-
Click to expand...
Click to collapse
Do you have a link to the last stock rom ? I think I don't have the right one, because I couldn't flash it, or maybe I did something wrong
(Nevermind, I found the right one)
Morceaux said:
Do you have a link to the last stock rom ? I think I don't have the right one, because I couldn't flash it, or maybe I did something wrong
(Nevermind, I found the right one)
Click to expand...
Click to collapse
https://sfirmware.com/samsung-sm-j530f/
goodjob
steadfasterX said:
The good news are: I am able to boot the radio now - PIN popup comes up and baseband is now correctly displayed (I am on the latest stock pie ROM available..)
but as you can see in the status bar still no cell service so still something missing..
View attachment 5078627
IMEI is still 0 as well so it might has to do with the EFS.. which would explain it
but at least some progress.. At least it is clear now why some ppl reported on our LOS thread that SIM does not work for them while it worked for others.
.-
Click to expand...
Click to collapse
Hi,
do you think there is a chance to get this running for phones which are already on PIE? (I think this is the majority of all phones.....)
kind regards
Jagged
jaggedN said:
Hi,
do you think there is a chance to get this running for phones which are already on PIE? (I think this is the majority of all phones.....)
kind regards
Jagged
Click to expand...
Click to collapse
Oof .. Well i don't have much time atm but i need that phone as my navigation device for my motor bike. so i need to fix it
Sent from my OnePlus 7T Pro using XDA Labs
New eOS v1-oreo build *20200909* has finished!
Changes:
- kernel: commits
- Device tree: commits
- Common Device tree: commits
Download: see OP
Known issue with the OTA Update!
Unfortunately it will work with the next update first. There was a missing entry in the fstab causing the install to fail. You can still use the Updater to download the package though!
1. Open Settings —> System
2. Expand Advanced & select Updater
3. Refresh if not listed already
4. Download
5. Reboot to TWRP
6. browse to /data/lineageos_updates/ and select the zip from here
BREAKING NEWS
I've decided to create a Telegram 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
The second one will also show sha256sums of every build for those who need it.
.-
No more OREO builds!
The reason is that almost everyone has flashed stock PIE in the meanwhile and I switched to Android 10 already. A10 works great so far and so backporting whatever is needed is not worth it.
Check it out: j5y17lte - Android 10 / Q
Thread closed.
.-
Hi All,
This is a revival of the original MagiskHide Props Config module.
I've been working on this all day and its finally ready to start taking fingerprint submissions so i thought id open a new thread here to reach more people.
Disclaimers -
I have copied and pasted from the original thread with a few changes where relevant.
I fully intend on handing this back over to @Didgeridoohan if they ever decide to take the reign again. Im simply just stepping in to fill a much needed void in the custom rom space.
As with any Magisk Module. This comes with risk. You can very easily break your device. I myself have a Samsung Note 10 Plus so i will be testing on my own device prior to making any releases.
I have no intention of collecting donations at all. This project depends upon the community more then myself.
What's this?
If you are wondering anything about what this module can do and how it works or if you're experiencing issues of some kind, take a look at the documentation on GitHub and see if whatever you wonder about is covered there (most things are). If they're not, look again and then post in the thread.
If you're wondering about the latest and greatest after an update, take a look at the changelog and accompanying release notes.
Prerequisites
Magisk v20.4+.
Installation
Install through the Magisk Manager Downloads section. Or, download the zip (attached below) and install through the Magisk Manager -> Modules, or from recovery. Combine a recovery installation with the use of the module configuration file and you can set up a certified fingerprint and any custom props you want without first booting on a clean flash. Instant settings.
Usage
After installing and rebooting, run the command props in terminal (you can find a terminal emulator on F-Droid or in the Play Store), and then follow the instructions to set your desired options (also see the documentation on GitHub). You might have to call su before running the command.
You can also run the command with options. Use -h for details.
Submitting Fingerprints
Now this is where you lovely people come in. There is no way ill be able to spend all my time gathering fingerprints and i have absolutely no intention of doing so. However i've made it very easy to submit your fingerprints in a way that i can process them with very little effort.
How to find your fingerprint
Submit your Fingerprint
Source
GitLab - All scripts are completely opensource and your free to download it yourself directly from source
Download Repository
MHPC Releases & Archive
Support
Discord Invite Link - For the time being i will only be able to support users either on here and Discord.
Credits and mentions
There are lots of people to thank for this project. I've included the main two below
@topjohnwu, for Magisk
@Didgeridoohan, for creating MHPC and maintaining it for so long
Original Module Thread
Link to Original Thread
@vithuselservices You forgot to attach the module in your post.
devnoname120 said:
@vithuselservices You forgot to attach the module in your post.
Click to expand...
Click to collapse
Hi. There haven't been any official releases just yet. ETA for the first beta releases are the end of this week but that's only if everything goes well and I see no issues on my tests. So far there are only Experimental releases that i have stopped uploading to the release fileshare.
Once the new build is ready I can begin working on integrating new Fingerprints from the submissions that have been given to me.
@vithuselservices I tried the latest master, and I rebooted. If I type `props` in Termux it says `No command props found`. I have the same issue with the original module though.
Any ideas how to fix this issue?
Edit: typing `su` before solves the issue..
devnoname120 said:
@vithuselservices I tried the latest master, and I rebooted. If I type `props` in Termux it says `No command props found`. I have the same issue with the original module though.
Any ideas how to fix this issue?
Click to expand...
Click to collapse
type su first
I have a really weird question:
I have a poco f3 (europe) phone. I extracted the props from the phones original system (MIUI 13.0.8.0 EEA). I editet the original printlist in the original magisk module, added the
POCO/alioth_eea/alioth:12/SKQ1.211006.001/V13.0.8.0.SKHEUXM:user/release-keys__2022-08-01
line to it, Then flashed the modified zip, and applied the new prop settings. The YASNAC apps says it passes safetynet, and i can use all my banking app except google wallet, and there is no netflix in the ploay store. If I change the props to a value that was part of the original printlist
POCO/alioth_eea/alioth:11/RKQ1.200826.002/V12.5.3.0.RKHEUXM:user/release-keys__2021-06-01
the google wallet works and the netflix app shows itself in the play store.
Is it something that I missed from the prop values? I cannot understand this behavior.
Any advice?
Is this project still alive? I haven't seen any updates for a few weeks. Did OP just ghost us?
neelchauhan said:
Post has been removed by a Moderator
Click to expand...
Click to collapse
Hi.
This is not the case. Can you please remove this post as its highly inaccurate?
Im still here. Apologies for the lack of updates.
Ive had a lot of work come in so its delayed things somewhat but the final version is indeed ready.
Theres a final bit of testing to be conducted prior to making a official release as the last thing i want is bricked phones or settings being dropped.
The first beta release will be out by sunday.
In future can you please give more then 2 hours prior to making such a claim? Its considered rude to make such a claim without reaching out to a dev with sufficient time to reply. Your welcome to fork it yourself. Thats your right. But be more thoughtful when you spread messages like this
dickta said:
I have a really weird question:
I have a poco f3 (europe) phone. I extracted the props from the phones original system (MIUI 13.0.8.0 EEA). I editet the original printlist in the original magisk module, added the
POCO/alioth_eea/alioth:12/SKQ1.211006.001/V13.0.8.0.SKHEUXM:user/release-keys__2022-08-01
line to it, Then flashed the modified zip, and applied the new prop settings. The YASNAC apps says it passes safetynet, and i can use all my banking app except google wallet, and there is no netflix in the ploay store. If I change the props to a value that was part of the original printlist
POCO/alioth_eea/alioth:11/RKQ1.200826.002/V12.5.3.0.RKHEUXM:user/release-keys__2021-06-01
the google wallet works and the netflix app shows itself in the play store.
Is it something that I missed from the prop values? I cannot understand this behavior.
Any advice?
Click to expand...
Click to collapse
Hi.
I believe google is now blocking basic Attestation on newer firmware. This is something im looking into as part of my android 13 upgrade. Certain devices will work better then others. Im sorry i cannot give you a solid answer at the moment. But once im done with my current release and the fingerprints have been updated i can work on this issue. Its likely going to require device specific configurations as newer phones come out. Some people have had luck. but it seems android 12 is the turning point.
vithuselservices said:
Hi.
I believe google is now blocking basic Attestation on newer firmware. This is something im looking into as part of my android 13 upgrade. Certain devices will work better then others. Im sorry i cannot give you a solid answer at the moment. But once im done with my current release and the fingerprints have been updated i can work on this issue. Its likely going to require device specific configurations as newer phones come out. Some people have had luck. but it seems android 12 is the turning point.
Click to expand...
Click to collapse
I understand your point but I don't think its about luck. I did the same thing with my OnePlus 6. In the original prop module the the latest fingerprint is:
OnePlus/OnePlus6/OnePlus6:11/RKQ1.201217.002/2109171635:user/release-keys__2021-09-01
and with that all apps and wallet was working fine as intended, an netflix and revolut was present in the play store.
I also edited the original print.sh file and added the latest available fingerpint extracted from a latest full OTA rom which is this:
OnePlus/OnePlus6/OnePlus6:11/RKQ1.201217.002/2111252325:user/release-keys__2021-11-01
It also did the exact same behavior as on the Poco F3: YASNAC reports that the Basic Integrity and the CTS Profile match is "PASS", normal banking apps works (local banks like OTP, Erste etc. with NFC payment), but Google Wallet reports that the phone is modified and not certified. Play store also lacks netflix, put reports the device is certified.
The results are the same when I create a printlist file in the root directory in the phone to use my fingerptints as a "Custom" one.
It seems it only happens when I manually add the fingerprint myself, but never with the inbuilt fingerprints. That's why I think something is missing when I use "my" fingerprints. It also the same under android 11. Tested with a Redmi Note 5 Pro LineageOS.
I'm not a dev but if I can help, I'm sure I will.
dickta said:
I understand your point but I don't think its about luck. I did the same thing with my OnePlus 6. In the original prop module the the latest fingerprint is:
OnePlus/OnePlus6/OnePlus6:11/RKQ1.201217.002/2109171635:user/release-keys__2021-09-01
and with that all apps and wallet was working fine as intended, an netflix and revolut was present in the play store.
I also edited the original print.sh file and added the latest available fingerpint extracted from a latest full OTA rom which is this:
OnePlus/OnePlus6/OnePlus6:11/RKQ1.201217.002/2111252325:user/release-keys__2021-11-01
It also did the exact same behavior as on the Poco F3: YASNAC reports that the Basic Integrity and the CTS Profile match is "PASS", normal banking apps works (local banks like OTP, Erste etc. with NFC payment), but Google Wallet reports that the phone is modified and not certified. Play store also lacks netflix, put reports the device is certified.
The results are the same when I create a printlist file in the root directory in the phone to use my fingerptints as a "Custom" one.
It seems it only happens when I manually add the fingerprint myself, but never with the inbuilt fingerprints. That's why I think something is missing when I use "my" fingerprints. It also the same under android 11. Tested with a Redmi Note 5 Pro LineageOS.
I'm not a dev but if I can help, I'm sure I will.
Click to expand...
Click to collapse
How odd.
Ill raise that as a issue on my Git and have a look at it. It likely wont be this week but ill aim to do some testing on it next week. Are you certain the build date is correct?
vithuselservices said:
How odd.
Ill raise that as a issue on my Git and have a look at it. It likely wont be this week but ill aim to do some testing on it next week. Are you certain the build date is correct?
Click to expand...
Click to collapse
Absolutely! I own all the 3 phones , I also did a full stock rom recovery on all to run the getprop command to make sure the fingerprint and the patch date is correct.
Ohh and almost forgot: thank you!
Beta release is now available!
You can download it via the download repo in the first post. Please let me know if you come across issues. For this first release I do not recommend upgrading daily driver devices just yet as there could still be issues.
Not much has been changed in this release. I'm working on improving the verification process during the install process. I know a lot of people are keen to get fingerprints updated so ill be focusing on that over the next few weeks.
vithuselservices said:
Beta release is now available!
You can download it via the download repo in the first post. Please let me know if you come across issues. For this first release I do not recommend upgrading daily driver devices just yet as there could still be issues.
Not much has been changed in this release. I'm working on improving the verification process during the install process. I know a lot of people are keen to get fingerprints updated so ill be focusing on that over the next few weeks.
Click to expand...
Click to collapse
I tried it right now: the installation has a little problem: it says the installation is failed but it installs it.
{
"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"
}
After that it seems the module can't access for some files and it not really working after that.
I attached a log to help.
dickta said:
I tried it right now: the installation has a little problem: it says the installation is failed but it installs it.
View attachment 5759567
After that it seems the module can't access for some files and it not really working after that.
View attachment 5759575
View attachment 5759571
I attached a log to help.
Click to expand...
Click to collapse
How odd. It works for me. Ill have a run through the logs and get it sorted. Thank you for reporting back!
vithuselservices said:
How odd. It works for me. Ill have a run through the logs and get it sorted. Thank you for reporting back!
Click to expand...
Click to collapse
Same for me. After assigning a fingerprint, reboot will clear it and it reverts back to original
This is still being looked into.
Its coming to the end of the year so im having to process a lot of projects to completion in my day job. Sorry for the delay!
New Beta Build is up. This should fix the install issues users have been having.
Ill be uploading a load of fingerprints very soon. Just finishing off testing the ones i have to hand.
For the moment. Android 13 support is very hit or miss. I'm working to find a solution to this.
A future update will need the deletion of the existing module so it can properly overwrite the new install files. This will also be completed with the next update.
The module now installs without problem, but in the app itself the behavior is the same: it not applies the selected fingerprint, always shows that "not accessible file" error in all activity. It's a good start, keep up the good work
dickta said:
The module now installs without problem, but in the app itself the behavior is the same: it not applies the selected fingerprint, always shows that "not accessible file" error in all activity. It's a good start, keep up the good work
Click to expand...
Click to collapse
Can you try uninstalling the original module and do a clean install of this one?
Im afraid i am not able to recreate the issue at all on my device which is quite infuriating