No write-permision with root - Android Q&A, Help & Troubleshooting

Redmi Note 9 Pro : I've had a lot of cell phones, but only on my Redmi Note 9 Pro does the following happen:
Miui 12 has a function "Automatically on/off speaker ...". But this only works with "talkback". For generations of mobile phones there have been extra programs for this function that either run separately or are built into audio recorders or phone apps. However, these apps do not work on my Remi 9. That was the reason why I rooted the device. However, there was no change. The rooting process had no effect. E.g. I would like to send an SMS to myself using "AutomateIt" when I receive an email. - But it doesn't work either. AI asks for permission to read emails. I give permission. Everything looks well, but if I check the permissions under "additional permissions" afterwards, no permission has been granted.
At first I thought it was due to AI - but I think it is due to Redmi n9: I tried to rename any file in the root - e.g. "media / mybootanimation.zip". A message appears that this cannot be carried out. Whereby it doesn't work with multiple explorers. If I change the rights of the file to "755", that doesn't work either
Accordingly, there is generally a write block.
Can someone tell me what to do to make this work?

Hint: Add "Redmi Note 9 Pro" to front of this thread's title thus owners of such a device get addressed.

Related

[Q] Tab 4 pairing with gear S?

Has anyone managed to connect a Tab 4 (7 inch, if it makes a difference) with the Gear S? Would it need to be the LTE version?
I am getting sick of my Note2, so this could free me up for a different cell brand.
Thanks!
I've been trying
xendula said:
Has anyone managed to connect a Tab 4 (7 inch, if it makes a difference) with the Gear S? Would it need to be the LTE version?
I am getting sick of my Note2, so this could free me up for a different cell brand.
Thanks!
Click to expand...
Click to collapse
I want to know this too. I have tried on mine and it doesn't see the device. The bluetooth screen does but when you click on it, it says it is not a supported device.
I've also altered the build.prop file but still no joy.
I read that a guy got it to work on a Tab S LTE, which would indicate it may only be the LTE versions of the tablets that work. If not, I don't see why the Tab S would work.
I have e-mailed Samsing support and also posted a message on their support site, although I reckon I'll get a stock reply of "It is only supported on the following Samsung phones......".
snpg said:
I want to know this too. I have tried on mine and it doesn't see the device. The bluetooth screen does but when you click on it, it says it is not a supported device.
I've also altered the build.prop file but still no joy.
I read that a guy got it to work on a Tab S LTE, which would indicate it may only be the LTE versions of the tablets that work. If not, I don't see why the Tab S would work.
I have e-mailed Samsing support and also posted a message on their support site, although I reckon I'll get a stock reply of "It is only supported on the following Samsung phones......".
Click to expand...
Click to collapse
Per their own How To guide, it is supposed to work with tablets. What I don't understand is why they won't list which tablets are compatible. It's the most basic info a manufacturer should provide.
Let me know if they answer you. I'll contact them as well and ask for a full compatibility list, since there are even a bunch of cheap Galaxy phones that may not work with it, meaning, KK+"Galaxy" in the device name is not enough of an inidicator.
On FB, someone from Samsung Support states that all Samsung devices with android 4.3 and above are compatible.
You may want answer them there and get to the bottom of this.
Got it working!!!
Right, after fiddling about and thanks to user bqwd36 who posted instructions for the Tab S in Chinese which I translated and just took a bit of, my Gear S is now working with my Tab 4 7.0 (T230). This may also work for any other Samsung tablet that can run Gear Manager.
Right, here's what you need to do which basically involves changing the build.prop file, so you may have to root your tablet to do it (there is a guide on the XDA Tab 4 forum - go with the TWRP method as it worked first time).
1) Install an older version of Gear Manager, I used version 2.0.14040401.
https://www.mediafire.com/folder/e7h23e12rzesi/Gear_Manager#e7h23e12rzesi
2) Make sure you have enabled bluetooth on your Gear S and that you have ticked so it can be seen by other devices (you may not need to do this if yours is not activated yet).
3) Open the Gear Manager app and scan, you should see the Gear S appear in the list. DON'T click on it as you don't want to do anything with the Gear S yet.
4) You now need to edit the build.prop file (I recommend using ES File Explorer). In build.prop change the following entries so they are:
ro.product.model=SM-N900
ro.build.characteristics=phone
5) Now reboot your Tab 4.
6) Open the Gear Manager app and check it can still see your Gear S (you may need to turn on bluetooth again so it is visible if you already have an active Gear S).
7) Now open Galaxy Apps and install the latest version of Gear Manager.
8) Open the Gear Manager app and the Gear will still be seen.
9) Now go ahead an click on the entry and setup your phone (it will wipe your Gear S).
Everything works as it does if it was being done on a phone. The only thing you need to remember is that as the tablet does not have a phone app, it means that the Gear S cannot make or receive calls when you have it connected via bluetooth to the tablet. Once you turn off bluetooth on the tablet the Gear S will automatically change itself so it can do calls.
You can now change the build.prop back to it's original settings if you want as the Gear Manager will continue to work with the Gear S.
The other thing is that the Remote Connection (where you can get notifications like e-mail from your tablet over the internet) worked the first time. When I changed the build.prop back to it's original settings it wouldn't do it, and hasn't since I then went and changed the settings back to the ones above. I just need to have another play.
It worked with my 12.2 note pro thank you only thing is when I pair it to a new device or rests the gear s
Sent from my SM-N900 using Tapatalk
Snpg, sounds a bit complicated for my skills, but I'll read all the instrucutions carefully next time I feel reckless and may give it a try.
Thanks for posting.
epic4grooted said:
It worked with my 12.2 note pro thank you only thing is when I pair it to a new device or rests the gear s
Sent from my SM-N900 using Tapatalk
Click to expand...
Click to collapse
This is typical gear behavior when switching phones. It stupid, but that's how it's worked since gear 1.
Tab 4 pairing with Gear S
I also have a new Tab 4 (the NOOK edition) , you have made a great discovery making the Gear app work with the 'S", i am not familar enough with the procedure with editing the files mentioned,
is there a tutotrial for doing this, i am trying to learn more about it, thanks for your posts.
Could someone explain what the purpose of pairing the Gear S with the phone or tablet is?
I was talking to a Samsung rep at Best Buy tonight and he indicated that you could pair with a tab 4 that was NOT a phone and did NOT have a data plan (ie wifi only tablet). What I don't understand is how the Gear S becomes "activated" to send and receive calls if it is not being paired with a device that has a sim, a phone number and IS able to make calls. I have an iPhone 5S and it seems there are some things going on to make forwarding of calls from an existing phone to the Gear S possible. I've read other threads that it is possible to pair with a non-samsung device and you'd think they would make it easy to do this to sell more Gear Ss. Thanks in advance for explanation.
butopia said:
Could someone explain what the purpose of pairing the Gear S with the phone or tablet is?
I was talking to a Samsung rep at Best Buy tonight and he indicated that you could pair with a tab 4 that was NOT a phone and did NOT have a data plan (ie wifi only tablet). What I don't understand is how the Gear S becomes "activated" to send and receive calls if it is not being paired with a device that has a sim, a phone number and IS able to make calls. I have an iPhone 5S and it seems there are some things going on to make forwarding of calls from an existing phone to the Gear S possible. I've read other threads that it is possible to pair with a non-samsung device and you'd think they would make it easy to do this to sell more Gear Ss. Thanks in advance for explanation.
Click to expand...
Click to collapse
The purpose is so you can install apps and forward notifications. My Gear S has a SIM card and its own phone number anyway, and yeah, call forwarding would not work.
Sent from my SM-T230NU using XDA Free mobile app
pairing gear s with your tab 4
snpg said:
I want to know this too. I have tried on mine and it doesn't see the device. The bluetooth screen does but when you click on it, it says it is not a supported device.
I've also altered the build.prop file but still no joy.
I read that a guy got it to work on a Tab S LTE, which would indicate it may only be the LTE versions of the tablets that work. If not, I don't see why the Tab S would work.
I have e-mailed Samsing support and also posted a message on their support site, although I reckon I'll get a stock reply of "It is only supported on the following Samsung phones......".
Click to expand...
Click to collapse
Watch the you tube video on "how to pair gear s with any phone" it will have you reset the phone then go through a series of taps on the screen. After that you will be able to pair your gear s to your tab 4 (or any phone/tablet).
[/LIST]any phone
Ask
snpg said:
Right, after fiddling about and thanks to user bqwd36 who posted instructions for the Tab S in Chinese which I translated and just took a bit of, my Gear S is now working with my Tab 4 7.0 (T230). This may also work for any other Samsung tablet that can run Gear Manager.
Right, here's what you need to do which basically involves changing the build.prop file, so you may have to root your tablet to do it (there is a guide on the XDA Tab 4 forum - go with the TWRP method as it worked first time).
1) Install an older version of Gear Manager, I used version 2.0.14040401.
2) Make sure you have enabled bluetooth on your Gear S and that you have ticked so it can be seen by other devices (you may not need to do this if yours is not activated yet).
3) Open the Gear Manager app and scan, you should see the Gear S appear in the list. DON'T click on it as you don't want to do anything with the Gear S yet.
4) You now need to edit the build.prop file (I recommend using ES File Explorer). In build.prop change the following entries so they are:
ro.product.model=SM-N900
ro.build.characteristics=phone
5) Now reboot your Tab 4.
6) Open the Gear Manager app and check it can still see your Gear S (you may need to turn on bluetooth again so it is visible if you already have an active Gear S).
7) Now open Galaxy Apps and install the latest version of Gear Manager.
8) Open the Gear Manager app and the Gear will still be seen.
9) Now go ahead an click on the entry and setup your phone (it will wipe your Gear S).
Everything works as it does if it was being done on a phone. The only thing you need to remember is that as the tablet does not have a phone app, it means that the Gear S cannot make or receive calls when you have it connected via bluetooth to the tablet. Once you turn off bluetooth on the tablet the Gear S will automatically change itself so it can do calls.
You can now change the build.prop back to it's original settings if you want as the Gear Manager will continue to work with the Gear S.
The other thing is that the Remote Connection (where you can get notifications like e-mail from your tablet over the internet) worked the first time. When I changed the build.prop back to it's original settings it wouldn't do it, and hasn't since I then went and changed the settings back to the ones above. I just need to have another play.
Click to expand...
Click to collapse
Please ask ! Can i use this method with Galaxy Grand Prime SM-G530H ? Because Gear S still not support with my device.
And please what about notification such text message, email still can recieve by gear ?
Sorry for my bad english. Thank you for your help.
10x
THANK YOU!!!! It works perfectly on Tab S 8 (T700) and Gear S.
snpg said:
Right, after fiddling about and thanks to user bqwd36 who posted instructions for the Tab S in Chinese which I translated and just took a bit of, my Gear S is now working with my Tab 4 7.0 (T230). This may also work for any other Samsung tablet that can run Gear Manager.
Right, here's what you need to do which basically involves changing the build.prop file, so you may have to root your tablet to do it (there is a guide on the XDA Tab 4 forum - go with the TWRP method as it worked first time).
1) Install an older version of Gear Manager, I used version 2.0.14040401.
https://www.mediafire.com/folder/e7h23e12rzesi/Gear_Manager#e7h23e12rzesi
2) Make sure you have enabled bluetooth on your Gear S and that you have ticked so it can be seen by other devices (you may not need to do this if yours is not activated yet).
3) Open the Gear Manager app and scan, you should see the Gear S appear in the list. DON'T click on it as you don't want to do anything with the Gear S yet.
4) You now need to edit the build.prop file (I recommend using ES File Explorer). In build.prop change the following entries so they are:
ro.product.model=SM-N900
ro.build.characteristics=phone
5) Now reboot your Tab 4.
6) Open the Gear Manager app and check it can still see your Gear S (you may need to turn on bluetooth again so it is visible if you already have an active Gear S).
7) Now open Galaxy Apps and install the latest version of Gear Manager.
8) Open the Gear Manager app and the Gear will still be seen.
9) Now go ahead an click on the entry and setup your phone (it will wipe your Gear S).
Everything works as it does if it was being done on a phone. The only thing you need to remember is that as the tablet does not have a phone app, it means that the Gear S cannot make or receive calls when you have it connected via bluetooth to the tablet. Once you turn off bluetooth on the tablet the Gear S will automatically change itself so it can do calls.
You can now change the build.prop back to it's original settings if you want as the Gear Manager will continue to work with the Gear S.
The other thing is that the Remote Connection (where you can get notifications like e-mail from your tablet over the internet) worked the first time. When I changed the build.prop back to it's original settings it wouldn't do it, and hasn't since I then went and changed the settings back to the ones above. I just need to have another play.
Click to expand...
Click to collapse
it's not work with me
I have done step 1 to 5 but I couldn't save the change in file any one can help me
I have tab s 10.5
essambak said:
I have done step 1 to 5 but I couldn't save the change in file any one can help me
I have tab s 10.5
Click to expand...
Click to collapse
pardon the necropost
you need to set your root folder to rw from ro
No intention for any duplication and absolutely no plagiarism, authorship is legitimate.
1. Tab S or Tab 4 must be rooted (you should head over to the forum where one of our spectacular devs would have done a write up on it)
2. Obtain Android a build.prop editor or in my case, I use Android Tuner (Free Version: http://www.3c71.com/atfree - Pro Version: https://play.google.com/store/apps/details?id=ccc71.at&hl=en)
3. Using the above applications, use the menu/tool to edit the build.prop. I this instance, I am unsing Android Tuner, so I will go over to the first page to select "Build.prop editor", select it by tapping on the button. First things first, click the backup button to save your existing build.prop file. Don't ever progress into modifications, without having a backup or recovery method. Once you have completed all of the above, here are the edits you need to make in the edit by simply click on the pen (blue/white icon) for each key).
Please note, I am having my Tab S indicate its the SM-N900P (Sprint Variant of Note 3), however, you can choose any other smartphone of you liking, once you know the details of the keys indicated below).
key: ro.build.characteristics
value: phone
key: ro.build.product
value: hlte
key: ro.product.device
value: hlte
key: ro.product.model
value: SM-N900P
4. Once you have completed edits for the aforementioned keys, verify your changes, then save your build.prop with your editor or in the case of Android Tuner, you're all good and just need to reboot your device.
5. Once your device completes the reboot and you're back on the Android platform, clear the data for your Galaxy Apps, before proceeding to the store. Once cleared, you will be able to download Gear Manager, Gear Fit or other application may not ordinarily have on a tablet.
6. Go over to your Bluetooth, add a new device (your gear should be reset to factory settings in order to pair with another device, so you will need to complete this step if you want to proceed with pairing the Gear S with the Tab S or Tab 4 and probably any other tablet device.
7. Follow the normal pairing settings and everything will go accordingly, gear manager will launch, the device will pair with the Gear S and continue to installing all prerequisite apps).
8. You have completed the pairing of your Gear S with your Tab S or Tab 4.
Feel free to reach out for assistance if you are having difficulty with any of the steps above and always remember, before proceeding, backup your devices.
Troubleshooting
If you realize any issues with launching settings on your Tab S or Tab 4 after making the aforementioned changes in the build.prop file, revert to the following and save.
key: ro.build.characteristics
value: tablet
Reboot and everything should be back to normal, without the loss of functionality.
Thx, worked like a charm on my 8" Tab4 (sm335). Pairing over bt with iPhone6+ is also confirmed (after removing a directory on gearS).
In that case, the Tab4 is still 'remote connected' (i.e. updates and s-voice continues to work) while the Gear-S plays nice as well with my iPhone.
Note ... i have the Gear-S modified with the StarTrek theme and iOS8 icons.
The Gear-S can work on its own, with the tab4 for management, and with iphone for call-forward/ bt connect.
dear snpg pls help me !!!
follow your guide and root my tab4 10"!
after root with buid.prop edit items you that you said !
key: ro.build.characteristics
value: phone
key: ro.product.model
value: SM-N900
but after root in last level i recived this pop up :
unfortunately com.android.systemui has stopped
at last i flash my tab4 for resolve it !
pls help for pairing my gear s to tab4!
thank so much!!
Worked for me! You are a ****ing genius, I just have one note! I kept my buildprop the same because I didn't want to mess with it. My question to you is, did you get any addition applications to install because I could not successfully complete that task. -AP

[MOD][Xposed] Patch SmartcardService for use with SIM-card-based banking apps

Hi!
I've written another Xposed module for my LEX720 for a very specific purpose, so probably it won't be of much use for the most. But I'm still publishing it for reference reasons.
Background:
First the good news: The stock firmware of LeEco includes the "SmardcardService" (which also often is referred to as "Open Mobile API" or short "OMAPI") which is an extension API to plain Android (i.e. not existing in the Nexus devices or the Pixels) to allow apps accessing Secure Elements (i.e. secure applications embedded in a tamper-resistant hardware) within the SIM-card.
A real world example: in Austria some banks (in cooperation with the 3 largest network operators) support Tap'n'Pay with your phone by installing the NFC-capable banking card as an additional application into the SIM card (which is the same secure chipcard technology as a banking card). This means you get a new SIM card and then you can tap'n'pay with your phone (without Google, without VISA or MasterCard, just as with the Austrian NFC banking cards). AFAIK in some other countries the same concept is used for public transport and others.
The main difference to Android Pay is, that this system is backed by the chipcard (the SIM) and not by a cloud service. But this just as background information.
The problem:
The LEX720 is a dual-sim phone, and so the (banking) apps could read SIM-cards from either SIM1 or SIM2 slot (I tested, SmartcardService works with both). But if you also want to use NFC for payment it has to be inserted into SIM1 (as it seems that only the SIM1 slot ist connected over an SWP line to the NFC chipset). Unfortunately the Austrian banking apps don't seem to handle the dual-SIM situation correctly and only try to read SIM2 (which is empty for me) and therefore don't work.
Additionally, at the end of an transaction, when the application running within the SIM card signalizes that it just had finished a payment transaction to the Android system, the NFC service (/system/vendor/app/NQNfcNci/NQNfcNci.apk) broadcasts this message as an intent to the relevant (banking) app, so that the app can display a transaction result activity.
Unfortunately this mechanism is implemented often very different by different OEMs and so also by LeEco. There exists a standard (GSMA NFC Handset APIs Requirement Specification) but it seems there are a lot of different implementations in the wild.
(Note: this is probably the case because this type of functionality is not part of the official reference Android source code. Plain open source Android like it is running on all Nexus phones and the Pixels just doesn't support these type of applications - which is very unfortunate).
My workaround:
TL;DR I just made an Xposed module which fixes these 2 issues for me. Look into the README on Github for more details.
Source on Github: https://github.com/johnzweng/XposedOmapiBankcardFix
Download Xposed Module: Xposed-module-OMAPI-BankcardMobil-Fix-1.1.apk
Maybe it's also useful for other applications which use the SIM card as secure storage for keys of any type. Use at your own risk.
As a reference: these are the Austrian banking apps this module should work with:
Bank Austria Mobile Geldbörse
BankCard Mobil
Oberbank Bankomatkarte Mobil
Raiffeisen ELBA-pay
VKB-Pay - Bankomatkarte mobil
The module might also help to get other similiar apps working which have problems with Dual-SIM or don't show Transaction confirmation screens. I am talking here about apps which use a special SIM card for payment, ticketing or similiar use-cases via NFC. This has nothing to do with "normal" NFC apps or cloud-based HCE (host card emulation) NFC apps. This module is only for apps which use special SIM cards.
[edit]
Updated download link to version 1.1.
For details see the CHANGELOG in the Github repoistory.
[/edit]
Btw, during debugging I noticed another small bug in the LeEco NFC service:
The package com.android.nfc (/system/vendor/app/NQNfcNci/NQNfcNci.apk) declares a permission which allows apps to receive Intents about EVT_TRANSACTION events. On the LeEco LePro 3 (LEX720, running 5.8.018S, WAXCNFN5801811012S) this permission looks like this
Code:
declared permissions:
com.gsma.service.nfc.permission.TRANSACTION_EVENT: prot=dangerous, INSTALLED
You can check this easyily yourself with this adb command:
Code:
adb shell pm dump com.android.nfc > dump-nfc-service.txt
This will dump all infos into a file named dump-nfc-service.txt. Open the file with an editor and search for "declared permissions:".
The problem with this permission is, that its name is missing a letter!
Correctly it should be called: com.gsma.services.nfc.action.TRANSACTION_EVENT (note the missing "s").
This is specified in the GSMA NFC Handset APIs Requirement Specification (see at the top of page 13 in the PDF)
Funny enough the specification in the PDF also contains a typo in the very same permission name the Intent action name (the dot "." after the word "gsma" is a comma "," in the PDF). It must be really hard to type this correctly.
Nevertheless this typo leads to errors like:
Code:
W/PackageManager( 2357): Unknown permission com.gsma.services.nfc.permission.TRANSACTION_EVENT in package ......
and prevents applications of requesting the correct permission.
Does anybody know if and how it's the best way to report bugs to LeEco?
[edit1]
I contacted them on Twitter. I hope they will forward this issue to developers.
Btw, it seems that also LG had included the same typo in some of its devices:
Devices without the "s": https://census.tsyrklevich.net/permissions/com.gsma.service.nfc.permission.TRANSACTION_EVENT
vs.:
Devices with the "s": https://census.tsyrklevich.net/permissions/com.gsma.services.nfc.permission.TRANSACTION_EVENT
[/edit1]
Hi androcheck,
first i am really impressed that somebody found a solution for that problem (i already have several posts with no answer at all)
But now i have a problem as when i install the fix i stuck in a boot loop. Is this maybe cause i am on custom ROM (Turbo MIUI) ?
Hope you have an idea
thanks
Robert
viercp said:
Hi androcheck,
first i am really impressed that somebody found a solution for that problem (i already have several posts with no answer at all)
But now i have a problem as when i install the fix i stuck in a boot loop. Is this maybe cause i am on custom ROM (Turbo MIUI) ?
Hope you have an idea
thanks
Robert
Click to expand...
Click to collapse
So far seems a "one time bug" - all ok with patch but i still get the very same error mssg
Any poss to tell me where i can check if entries provided by fix are really done ?
viercp said:
So far seems a "one time bug" - all ok with patch but i still get the very same error mssg
Any poss to tell me where i can check if entries provided by fix are really done ?
Click to expand...
Click to collapse
Hi!
Sorry for the delayed answer.
First of all the ROM you are using must have the SmartcardService (=implementation of OpenMobile API), the corresponding library (org.simalliance.openmobileapi.jar) and permission manifest (org.simalliance.openmobileapi.xml) installed. I downloaded miau_destroyer_v12.zip from this thread here, extracted it and it seems that it contains all three of them.
My Xposed module "XposedOmapiBankcardFix" doesn't do very much besides forcing the apps which are using the OpenMobile API to always use "SIM1" as SmartcardReader. This was necessary because at the time of writing the Bankcard apps in Austria from PSA (Payment Services Austria) didn't correctly check for multiple SIM slots. So in fact this was a bug in the PSA apps, not in the phone.
Back then I reported this back to the developers (of the banking app) and today it seems to be fixed (I didn't check in detail but the Bank Austria app now is working for me on Android 7 without Xposed installed - with the SIM inserted in slot 1).
Another point I realized: By looking into the build.props of the miau_destroyer_v12 ROM it seemed to me that this ROM is configured for single SIM use. This means that the SmartcardService also only sees one cardreader (SIM slot). Maybe this also interferes with the Xposed module?
For clarification:
Before I wrote my Xposed module, the Bank Austria banking app worked already perfectly (no errors displayed, recognized the NFC SIM card, personalization of the bankcard worked ok) when I inserted the SIM card into slot 2. It just didn't work when the SIM card was inserted in slot 1. The problem is that it must be inserted in slot 1 if you want to use it over NFC. This is why I decided to work around this limitation with my Xposed module.
The second feature ("Fix EVT_TRANSACTION Intent") of my module was just a gimmick "on the way". I realized that the confirmation dialog after paying is not displayed, but this was just a "cosmetic" problem. Payments did still work, even if the confirmation dialog on the phone is not displayed.
Another sidenote:
As I have mentioned before I have switched already to an Android 7.1 based ROM on my personal phone (as a developer I want to use some of the new APIs) so I don't have Xposed anymore (as Xposed is not available for Android 7). So at the moment I cannot really test anything.
Which error exactly do you get? What do you see in logcat?
Kind regards,
john
androcheck said:
Hi!
Another point I realized: By looking into the build.props of the miau_destroyer_v12 ROM it seemed to me that this ROM is configured for single SIM use. This means that the SmartcardService also only sees one cardreader (SIM slot). Maybe this also interferes with the Xposed module?
Click to expand...
Click to collapse
Changed in build.prob to enable Dual SIM
Which error exactly do you get? What do you see in logcat?
Click to expand...
Click to collapse
Havent worked with before - which entry you are looking for ?
Lot Of Thanks for your great work!
Btw,Do you use AOSP 8.1(such as AICP8.1)
On these roms,after add SmartCardService.apk ,it still cann't work with these bank apps. Actually,it can read other nfc tags,but it's HCE (Host-based Card Emulation) can not work
Could you have a try to fix it?
My post:
https://forum.xda-developers.com/le...a-zl1-x727-x720-t3698058/page356#post76274677
Hi,
Google says that Pixel 7 series don't support SWP-SIM while Pixel 6 and others supported.
So I started googling that if there's any 'Magisk way' to solve this issue, then I find your xda posts.
If you happen to be a Pixel 7 user, are you interested in looking into this issue?
I'd like to buy you a $30 coffee or more if I can use the SWP-SIM for payment on my Pixel 7.
jasonlee0315 said:
Google says that Pixel 7 series don't support SWP-SIM while Pixel 6 and others supported.
So I started googling that if there's any 'Magisk way' to solve this issue, then I find your xda posts.
Click to expand...
Click to collapse
Hi!
I don't have Pixel 7 and currently I am not working in this field, but for clarification:
"SWP-SIM support" is (also) a hardware feature.
To be able to use SWP-SIMs there must be a physical connection between the SWP pin of the NFC controller (this is a separate chip on the mainboard of your phone, not the main application processor, where Android runs on) and the respective pin of the SIM card slot.
Google in the past tended to not connect these 2 pins. I don't know if the Pixel 7 has this connection. I just wanted to let you know, that if this connection does not exist, there is no way to solve this in software.
[edit]
(see also this old question on stackexchange, this was about the Nexus 5X and 6P: https://stackoverflow.com/questions...-to-the-uicc-on-the-nexus-5x-and-the-nexus-6p)
[/edit]
androcheck said:
Hi!
I don't have Pixel 7 and currently I am not working in this field, but for clarification:
"SWP-SIM support" is (also) a hardware feature.
To be able to use SWP-SIMs there must be a physical connection between the SWP pin of the NFC controller (this is a separate chip on the mainboard of your phone, not the main application processor, where Android runs on) and the respective pin of the SIM card slot.
Google in the past tended to not connect these 2 pins. I don't know if the Pixel 7 has this connection. I just wanted to let you know, that if this connection does not exist, there is no way to solve this in software.
[edit]
(see also this old question on stackexchange, this was about the Nexus 5X and 6P: https://stackoverflow.com/questions...-to-the-uicc-on-the-nexus-5x-and-the-nexus-6p)
[/edit]
Click to expand...
Click to collapse
Thanks for replying. I guess I might give up trying to get SWP-SIM working on Pixel 7.

(What are) Must have APPS and To-Do to newbies to Galaxy S9+ (?)

Hey all.
Within a couple of days I'm getting my new Galaxy S9+ (Exynos) phone.
I made a year break from Android and switched to Apple, and now I'm back.
Unfortunately, I know nothing about newest Galaxy phones.
Maybe anyone has suggestions what should I do (download) when I'll set-up my phone (I've watched all the reviews of "must have" etc., don't suggest me to do that)?
I used to root and unlock bootloader for each my android phone, but I won't do that to my Galaxy S9+ at least for 6 months.
Hence, many root apps not working: "AdAway", "Viper4Android" etc.,
Maybe anyone knows Ad Blocking app without rooting a phone?
Or just mention anything that newbie to Galaxy S9+ should know.
(If you're wondering why am I "spamming" with these "stupid" questions: And no, I didn't find any similar thread to this)
Thanks in advance!
I use to root and rom all my phones, but I don't think it is as necessary as before.
I also use to download all the tweaks, but I don't do that either.
Non-root to block adds try Blokada it is in the F-Droid store.
It is Free and it Works.
I also swear by ES File Explorer to view and move files on your app. Also to sync any cloud storage you have.
If you have a regular phone number and google voice number going to the same phone
Voice Choice 2.0 is a nice app that allows you to make calls with a specific number
i.e. family and close friends have you carrier number
work partners, resume, business line has your google number
when you make a call you don't have to select anything, based on your rules set up it will dial out using the appropriate number.
re
qnc said:
I use to root and rom all my phones, but I don't think it is as necessary as before.
I also use to download all the tweaks, but I don't do that either.
Non-root to block adds try Blokada it is in the F-Droid store.
It is Free and it Works.
I also swear by ES File Explorer to view and move files on your app. Also to sync any cloud storage you have.
If you have a regular phone number and google voice number going to the same phone
Voice Choice 2.0 is a nice app that allows you to make calls with a specific number
i.e. family and close friends have you carrier number
work partners, resume, business line has your google number
when you make a call you don't have to select anything, based on your rules set up it will dial out using the appropriate number.
Click to expand...
Click to collapse
Thanks! Maybe you know anything about removing / disabling Bloatware as well?
LaurynasVP said:
Thanks! Maybe you know anything about removing / disabling Bloatware as well?
Click to expand...
Click to collapse
check out this thread at your own risk. It works I disabled Facebook (don't see why that would be on and unlocked phone fro Samsung, but i digress)
https://forum.xda-developers.com/galaxy-s9-plus/how-to/s9-s9-bloatware-removal-thread-g960u-t3817810
Be careful with the commands and understand what is being done before you hit the enter/return key
Good thing about disabling is if you fubar the phone you can do a factory restore and start all over
I only disabled Facebook. will investigate the other software as i play with the phone. Only had it 2 weeks so far.
re
qnc said:
check out this thread at your own risk. It works I disabled Facebook (don't see why that would be on and unlocked phone fro Samsung, but i digress)
https://forum.xda-developers.com/galaxy-s9-plus/how-to/s9-s9-bloatware-removal-thread-g960u-t3817810
Be careful with the commands and understand what is being done before you hit the enter/return key
Good thing about disabling is if you fubar the phone you can do a factory restore and start all over
I only disabled Facebook. will investigate the other software as i play with the phone. Only had it 2 weeks so far.
Click to expand...
Click to collapse
Thanks, I'll keep everything in mind

[Root required] Daydream on android 8/9/10 in 2020

If anyone is still (trying) to use daydream on normal devices, I'm going to share my experiences with getting it to "work" in a redmi note 4 (sd625 variant), along some other problems I do still face.
First of all, you need to know that daydream is designed to have always reprojection on, if you don't know what that is, take a look at this. This means that unless you have an oled display, with their inherit characteristics (low persistence), or an lcd that's capable of doing 90hz or more, you're going to experience a lot of motion blur with fast head movements or circular movements. That's not a bug, it's how it's supposed to work, that's why if you go check the list of official compatible daydream phones all have oled displays. The benefit of that blur is the buttery smooth head tracking, use it for 5 min, and you won't be able go back.
Once you have prepared your stomach for the ride;
1st: You need a rooted device (easiest method is flashing with a custom recovery the latest magisk version). You might be able to avoid rooting if somehow you manage to modify the files in the next steps, but at least for me, to access those files I needed root permissions.
2nd: Go to the play store and just search for daydream (do not install it), if you're able to see the app, you could jump to the next step. If you don't, download a file explorer with root capabilities (I personally like fx explorer) and paste the "android.hardware.vr.high_performance" file attached to the following route;
Code:
/system/vendor/etc/permissions
.
In this same folder you'll find the handheld_core_hardware that's mentioned in other guides, you might be also capable of getting it working by editing handheld_core_hardware, just like the old tutorial said
3rd: In order to get most of the daydream apps to render in SBS mode or even open, you need to spoof the id of your device to one of the certified ones. This is exactly the same step contained in the tutorial above, but at least in my case, once I opened the build.prop in the /System folder, I didn't saw a "ro.product.device", but a "ro.product.system.device". What I did was modify the latter by changing "mido" (the name of my device) to "walleye" (pixel 2) and adding a new line with "ro.product.device=walleye"
4th: Restart your phone and install Daydream, google vr services, and daydream keyboard all three from version 1.13. Daydream
Google vr services
Daydream keyboard
This version, along with 1.14 are the last ones that at least in my phone don't distort the aspect ratio, making it all squezzed. Version 1.14 has some handy implementations but worse performance and the lack of a developer option that I find really interesting for our unsupported phones that I will mention later.
5th: Now that's all installed, open the app and it will tell you that it need some permisions to work, press cancel and it will exit itself. go press it again and this time you'll see the daydream menu, swipe to the right to open the side menu, go to settings, VR settings, and if you don't have developer options, press compilation version several times to make them appear. Once you're inside those developer options, check the "skip VR entry screens". This is essential for all of us that don't have nfc, otherwise we wouldn't be able to run any app.
6th: Go to to visor and select your daydream version, bare in mind that if want to use a controller, you'll need to chose between gen1 and gen2, as cardboard custom profiles gray out the controller.
7th: Go to the controller tab and press and new controller, you'll be asked to fix the permissions, by enabling bluetooth, gps, and location you should be good to go, but considering we are using google play and google already knows all about us, I would say go ahead and try go give all permissions, just in case some specific app requires them.
Now follow the tutorial and the controller should pair... or maybe not. This is one of the problems that I don't know how to fix. The controller appears to be paired, as the light no longer blinks, but the daydream app doesn't detect it. At least for me, I couldn't get it to work in android 7 or 9, android 8 I (think?) I managed to get it working, and all android 10 roms I tried worked fine. I suspect it has something to do with the bluetooth settings, as it's a low energy device.
8th: You're good to go. Depending on your display and calibration, you might want to download an app called sa2ration that allows you to boost the intensity to get a more vivid image, I personally use 1.25 and it works wonderfully. Bare in mind that this works system wide, you could toggle it on and off whenever you want, and the settings don't reset with phone restarts.
---------------------------------------------------------------------------------------------------------------------------------------
Now that everything is "working", If you want to avoid the blur, and the app you're going to use is capable of holding a steady 60fps, you could go to developer setttings, and tick the "Force undistorted rendering". This will supress most of the motion blur at the cost of smoothness. This for me also reveals another problem, the resolution/dpi settings, as the image "bleeds" outside the supposed rendering area.
@Retrete: THX for your hints.
Any xiaomi/redmi or oppo/realms device you can recommend? Is the experience as good as on official daydream phones?
I remember that on my axon7 the amoled needs to be switched to low persistence mode via fw command.
---------- Post added at 08:22 PM ---------- Previous post was at 08:21 PM ----------
[/COLOR @Retrete: THX for your hints.
Any xiaomi/redmi or oppo/realms device you can recommend? Is the experience as good as on official daydream phones?
I remember that on my axon7 the amoled needs to be switched to low persistence mode via fw command.
hmn, i cant get to edit neither the build.prop nor the folder where i have to paste the vr file. I have magisk root, OnePlus 5T Android 10 OxygenOS 10.0.0

List of Removable Bloatware on Samsung Galaxy S7

Hi. I posted this in the Gerneral Q&A forum (here), which apparently doesn't seem like the right place to post that in.
Here it is:
Hi. I'm looking for a list of all the apps I can uninstall (or disable if necessary) for the device to keep working (and for the Settings app to still work). I did reset my device a few times after a DeadObjectException error and the Settings app not responding. Before reseting, I noted which apps I installed myself and retrieved my text message backup file (the contacts are there and also in my SIM card). Everything else is either backed up (e.g. Pocket Frogs data) or the data doesn't have to be kept (like clearing app data).
Please list apps as the package name (e.g. Pocket Frogs's package name is com.nimblebit.pocketfrogs), so I can quickly find and uninstall/disable them without choosing the wrong one by mistake.
Note: My samsung galaxy s7 is model g930t (I don't know if that has any affect) with my carrier as tmobile.
Click to expand...
Click to collapse
Correction: Listing the package name (e.g. google play services) is ok, but the file name (e.g. com.google.andoird.gms) is preferred. I changed to using APKSharp, developed by a fellow XDA member, which does display both name variations.
I currently have nothing on the device (stuff is either backed up/saved or deleted), so resetting is ok, though not preferred. I did check out other methods, but my device isn't supported for most of them. (It's the same samsung galaxy s7 G930T model with tmobile as the carrier.)
Note: A partial list is ok; I just want to get started somewhere without hitting errors and issues like "Settings keeps stopping".
Note 2: Stuff I don't use: samsung stuff, google stuff, bluetooth, nfc, dictionary, all game-related "tools", car mode, tv conenction, radio, voicemail, news/briefing, most tmobile stuff (excluding SIM card-related stuff), etc.
Look inside here.
jwoegerbauer said:
Look inside here.
Click to expand...
Click to collapse
Ah, thanks. I've been looking for something like that for days... Also just found one here. Both, unfortunately, isn't specifically for an S7, but at least I can follow most of it.
Additional guides/threads: Galaxy S9 Plus and Galaxy S8. Also found one for S7 (and a script, too), but I'll have to verify it works with m device.
I guess my main issue is what do I need to keep for the device to function properly while removing bloatware via ADB or APKSpark (ADB-based I assume).
No idea why I couldn't find the lists before. Maybe I was looking in the "wrong" place.

Categories

Resources