Related
Overview
This is my second GUIDE post. My first GUIDE explains how to compile the kernel from source. Follow that guide first before reading on. You can find it here: http://forum.xda-developers.com/showthread.php?t=1516051
This guide will get you started on how to modify your file-system (ROM). I will go over some examples of changing your phone functionality to show you how things are done. After that it is up to you to change what ever you want.
This first post will contain general information and requirements. The 2nd post will have guides on how to modify the initramfs. The 3rd post will have example modifications of the ROM.
These instructions work for both T989 (T-Mobile) and I727 (AT&T) variants of the Samsung Galaxy S2 phones. I do not take any credit for these instructions. I am just gathering what I learned from other posts and articles. I have listed the references below.
Requirements
The following instructions assumes you are using Ubuntu. I am using version 10.10.
ADB Setup
Android Debug Bridge (ADB) is a command line tool that allows you to command your phone via a USB connection. This requires you to turn on "USB debugging" on your phone. To do this on your phone goto Settings->Applications->Development. Make sure "USB debugging" is checked.
To get ADB and setup the USB driver go here: http://esausilva.com/2010/05/13/setting-up-adbusb-drivers-for-android-devices-in-linux-ubuntu/
Java Setup
In order to change the functionality of your Android system you will sometimes need to edit the jar/apk files. To do this you will need the Java Development Kit (JDK). Install the JDK with this:
Code:
sudo apt-get install sun-java6-jdk
Still Under Construction
How To Modify Initramfs
If you ever flash any of the custom ROM released by the great developers found in this forum you should be familiar with the terms "insecure kernel" and "init.d support." With an "insecure kernel" you can easily root your phone by bypassing the security through using ADB. With "init.d support" you can make automatic scripts to run at bootup. Both of these features require you to modify your initramfs.
In this post I will show you how to modify your initramfs to enable these features and in the future I will add more examples here.
If you do not know what a initramfs is or where to get it then you need to read my first GUIDE here: http://forum.xda-developers.com/showthread.php?t=1516051
Insecure Kernel
An insecure kernel allows ADB as root and commands like "adb remount" to enable write mode for your system. To make an insecure kernel it is a matter of modify the file "default.prop" in your initramfs. Open up this file with a text editor and change the line
Code:
ro.secure=1
to
Code:
ro.secure=0
After you make the change recompile the kernel with the modified initramfs using my kernel building guide. If you search in the forums there are guides on how to use your insecure kernel to root your phone.
Change Boot Image
In the initramfs folder you will find "initlogo.rle" This is the logo that appears during boot. You can replace this with a custom image as long as the format is compatible. When I have time, I will post the programs to convert from "rle->raw->png" and back "png->raw->rle" (search for "from565" and "to565").
Init.d Support
TODO (Sorry I have been really busy lately. I'll post this as soon as I get some free time. Basically you need to modify "init.rc" in your initramfs directory)
Introduction to Modifying ROM
In this post I will explain how to modify your stock ROM to include features like "volume wake-up" and more.
Getting your stock ROM
First we need to get a copy of your ROM. I found the easiest way to get this is to flash ClockworkMod and doing a backup of your phone to an external sd card. Connect your phone to your computer and grab the file called "system.ext4.tar" in your backup folder. This is your filesystem or ROM. Extract it to a working folder.
If you do not have ClockworkMod, please search the forums for instructions. ClockworkMod is a replacement for your default "Recovery" partition.
System folders
Here is a walkthrough of the folder structure of the system:
app\ - folder containing your apps (apk)
bin\ - folder containing binary executables
csc\ - consumer software customization, contains the software packages specific to your carrier
etc\ - system configurations
fonts\ - fonts folder
framework\ - folder containing android core files
lib\ - folder containing libraries (like .dll in windows) and modules (drivers)
media\ - folder containing media files
T9DB\ - looks like it contains keyboard layouts
tts\ - text to speech
usr\ - user settings
vsc\ - ????
xbin\ - alternate folder to hold binary executables???
build.prop - android settings file
CSCFiles.txt - carrier specific configuration file???
CSCVersion.txt - Configuration version???
SW_Configuration.xml - List of version numbers
The folders with question marks I am not sure of. If you know please post them here and I will update the list.
Understanding Odex and Deodex
Before getting your hands dirty, you need to know what odex and deodex means. Here is a good article on the issue: http://www.talkandroid.com/guides/m...n-the-all-inclusive-explanation/#.T1f7BN7Km9V
Remove Apps
All of your stock apps are in the "app" directory. You can remove all the bloat apps from this directory if you like.
Change Android Settings
You can modify "build.prop" in you system directory to change different Android settings. You can read more about the different settings here:
http://www.android-hilfe.de/root-ha...imus-3d/145592-tweaks-scripts-collection.html
Volume Wakeup
This volume wakeup guide was adapted from these two guides: http://www.jordanhotmann.com/2011/08/how-to-change-default-orientation-of.html and http://forum.xda-developers.com/showthread.php?p=18226553
In this guide I will show you how to modify your system files to allow waking up your phone with the volume keys instead of just the power key. This will prolong the life of the power key.
Requirements
This mod requires an edit to a jar file (Java archived file), specifically the file "/system/framework/android.policy.jar." To do this we need some tools that will disassemble the jar or apk file so we can edit the source code. After that we need to assemble it back and overwrite the original file(s).
Download the 4 files located here (smali-1.3.2.jar, baksmali-1.3.2.jar, baksmali, and smali): http://code.google.com/p/smali/downloads/list
Put the 4 files in a folder which is included in your path. For example, I placed the files in my home directory under a folder called bin (~/bin). Then in my ".bashrc" file I have this call at the end of the script:
PATH=~/bin:$PATH
This allows you to make calls to "baksmali" and "smali" in any directory.
Still Under Construction
To Do List
- How to make ClockworkMod flashable ROM. I have no clue how to do this. I always modify my ROM in place using "root explorer" and/or ABD, so I have never needed to flash a new one. It would be great if someone can post a guide on how to do this. Thanks.
*Update - See post #7. Thanks to one5
- How to modify cpu voltage and frequency
- How to change boot animation
My Request
I am still very new to all of this and android in general. I learned everything I posted here from reading other guides and articles on the internet and this forum. Through my searching, I found that the information on this stuff are there but very spread out making it very hard to find. This is why I started these guides to help out noobs like me. A central place where all the T989 (and I727, didn't forget you guys) noobs can come to learn.
I thank anyone for thanking me but my goal is to not get my "thank you" meter up. All I ask is if you learn something in regards to android development, please post up a GUIDE so everyone can benefit.
Also, my last request is if you see any errors or optimization to my steps please leave a note and I will change them.
Thank you.
References
http://esausilva.com/2010/05/13/setting-up-adbusb-drivers-for-android-devices-in-linux-ubuntu/
http://www.jordanhotmann.com/2011/08/how-to-change-default-orientation-of.html
http://www.neopeek.com/viewtopic.php?f=24&t=6801
http://www.talkandroid.com/guides/m...n-the-all-inclusive-explanation/#.T1a_ed7Km9V
http://www.freeyourandroid.com/guide/de-odexing_with_baksmali
Can't wait to read the full guide.
Sent from my SGH-T989 via Satanic Unicorns.
+1 can't wait for full guide.
Maybe i can do my own roms. If i trust myself.. Lol
cheers!!
How to make ClockworkMod flashable ROM
To make a flashable ROM:
Make a folder to dump the files from your phone, for example a folder named ROM on your desktop.
From CMD: adb pull / C:\Users\(yourusername)\Desktop\ROM
Download AutoUpdateCreator
Open CreateUpdateZip.exe and follow the directions.
Your ROM will be added to the generatedZips folder.
one5,
Thanks for the guide on making the ROM flashable.
one5 said:
To make a flashable ROM:
Make a folder to dump the files from your phone, for example a folder named ROM on your desktop.
From CMD: adb pull / C:\Users\(yourusername)\Desktop\ROM
Download AutoUpdateCreator
Open CreateUpdateZip.exe and follow the directions.
Your ROM will be added to the generatedZips folder.
Click to expand...
Click to collapse
thanks for the link. this is way nicer than doing it by hand.
Reserved
Sent from my SGH-T989 using xda premium
how could I easily make my phones kernel inscure... Semms like it should be easy but not sure... Im on ICS so befor I go doing all this just wanted to know if their was a easy way to get adb up and running again. without making a whole kernel I guess is what I want to know
Rushing said:
how could I easily make my phones kernel inscure... Semms like it should be easy but not sure... Im on ICS so befor I go doing all this just wanted to know if their was a easy way to get adb up and running again. without making a whole kernel I guess is what I want to know
Click to expand...
Click to collapse
If your on the stock T-mobile ICS update, just root it with the oden method. If your on one of the roms on here than you probably are already insecure.
---------- Post added at 11:34 AM ---------- Previous post was at 11:07 AM ----------
one5 said:
To make a flashable ROM:
Make a folder to dump the files from your phone, for example a folder named ROM on your desktop.
From CMD: adb pull / C:\Users\(yourusername)\Desktop\ROM
Download AutoUpdateCreator
Open CreateUpdateZip.exe and follow the directions.
Your ROM will be added to the generatedZips folder.
Click to expand...
Click to collapse
Works like a charm!! However, that command will also pull all data off int. & ext. sd storage. I was meaning to back them up any ways lol. Thanks to you and op!
Rushing said:
how could I easily make my phones kernel inscure... Semms like it should be easy but not sure... Im on ICS so befor I go doing all this just wanted to know if their was a easy way to get adb up and running again. without making a whole kernel I guess is what I want to know
Click to expand...
Click to collapse
Here is a guide if your stock. http://forum.xda-developers.com/showthread.php?p=23343879
This ROM AOSP, or TW, o wait, its neither.
It doesn't have to be a rom to be under development, loopy. Guides are very helpful to the community.
No offense loopdog just saying...
Sent from my SGH-T989 using xda premium
Rushing said:
It doesn't have to be a rom to be under development, loopy. Guides are very helpful to the community.
No offense loopdog just saying...
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Guides are indeed very helpful and this looks like a good one. Correct me if I'm wrong, but I was under the impression that any thread in development had to involve coding. It had to provide something that can be flashed or installed. IMHO, guides and tutorials; in general. Questions, of course Q&A. Apps and themes, pretty self explainetary. Development, all that is done thru coding involving Android and is flashable
Agreed my friend but I've noticed that on many forums guides may go under development and even get stickied in some cases. Just saying the scope is just a bit more wide than flashables and code oriented posts... TheRe should be a section just for guides I think that would make it really easy to find guides anyway... Peace threadjack over .
Sent from my SGH-T989 using xda premium
15 toggles
Any known Guides to implement 15 Toggles to a TW Rom ??? can't find one for our device !!!
Thanks
Tornade69 said:
Any known Guides to implement 15 Toggles to a TW Rom ??? can't find one for our device !!!
Thanks
Click to expand...
Click to collapse
Yes. well what do you mean exactly by implement?
Sent from my SGH-T989 using xda premium
Rushing said:
Yes. well what do you mean exactly by implement?
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
I want to add this mod in my own custom rom but can't find how to do it...
Sent from my SGH-T989 using xda app-developers app
Hello,
I've seen many threads implying that editing your build.prop file is simple, yet many other threads exclaiming that people have bricked their devices.
Has anyone successfully edited their SGH-T989/D phones to emulate the SGH-1337M? I have an odd reason, but I don't want to screw up.
Here is a link to the Galaxy S4 (I9500) build prop:
http://www.androidpolice.com/2013/0...gb-system-dump-leaked-and-ready-for-download/
Here is a link to the SIIx build.prop:
http://forum.xda-developers.com/showthread.php?t=1697142
How simple is this process? Which lines should I edit? What is your recommended editor app?
Thanks, I'd rather ask now than beg for solutions later.:fingers-crossed:
fishstick2k8 said:
Hello,
I've seen many threads implying that editing your build.prop file is simple, yet many other threads exclaiming that people have bricked their devices.
Has anyone successfully edited their SGH-T989/D phones to emulate the SGH-1337M? I have an odd reason, but I don't want to screw up.
Here is a link to the Galaxy S4 (I9500) build prop:
http://www.androidpolice.com/2013/0...gb-system-dump-leaked-and-ready-for-download/
Here is a link to the SIIx build.prop:
http://forum.xda-developers.com/showthread.php?t=1697142
How simple is this process? Which lines should I edit? What is your recommended editor app?
Thanks, I'd rather ask now than beg for solutions later.:fingers-crossed:
Click to expand...
Click to collapse
What exactly are you trying to do in the build prop to emulate the S4?
smokinjoe2122 said:
What exactly are you trying to do in the build prop to emulate the S4?
Click to expand...
Click to collapse
Maybe 'emulate' is the wrong word, but I am under the impression that I can swap the model number by changing the ro.product.model in the build.prop file. I want Google to think my SIIx is an S4 so I can access advanced apps that aren't optimized for my SIIx.
Here is a guide I found for simpletons like myself, but I just want to see if anyone else has done so successfully.
http://forum.xda-developers.com/showthread.php?t=1948558
I got impatient and changed the model number in the Build.prop and the phone did not brick. The System Settings on the phone does in fact confirm the updated model number as being SGH-1337M but the Play store hasn't updated the device yet so I can't confirm if my 'illusion' has completely worked.:laugh:
Get play store set correctly
http://www.howtogeek.com/116456/how-to-install-incompatible-android-apps-from-google-play/
looks like you done it all right except for the final step.
I changed my build.prop to make my LG L70 work with my Gear 2 watch. The watch got boring so I sold it, now I am looking to switch it back. I copied the original and tried to delete the modded one and it did not allow me. I tried to manually edit build.prop and it wouldnt save.
Any of you know how to revert?
Change permissions to rw
Sent from my MB855 using XDA Free mobile app
zzEvilGeniuszz said:
I changed my build.prop to make my LG L70 work with my Gear 2 watch. The watch got boring so I sold it, now I am looking to switch it back. I copied the original and tried to delete the modded one and it did not allow me. I tried to manually edit build.prop and it wouldnt save.
Any of you know how to revert?
Click to expand...
Click to collapse
yess...
if you have rooted your phone and then edited your build.prop with a change in android version....
then you have to root it again, and then go through the same process....
hey guys,
this might be a more broader android question, but either way: is there a way to change the hardware device name of a device?
i.e. my issue is the following - i use the "good for work" application for my work emails. My company basically has every manufacturer added to their approved list (HTC, Samsung, even Nexus devices work no problem). Now that I have my sweet OP3, I get the below error message (pic attached)
"the device hardware version is 'oneplus a3000 android 6.0.1' and is not permitted. Install the application on a permitted device."
now - before you tell me to go to my network admins and have the device added - I can't do that for reasons I won't go into here. Basically i want to understand if there's a way to change certain files on the phone that will make this application think it's a nexus device and clear it.
I tried editing the build.prop file (using twrp and adb - since I don't have root) to remove all mention of oneplus, etc. and replacing with "nexus" or something else (used the build.prop file from my 5x for reference). But the app still does not work and the OP3 still shows the model as One Plus 3 in the "about phone" section. This is really fascinating to me. What is driving this device's identity?
Appreciate any thoughts/suggestions you might have.
Try xposed mods... I think it is possible
Wrong forum.
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
wrong section.
post this in Q&A
@piotrus22, If you correctly modified your build prop then it's almost impossible to come as Oneplus name in about section of setting.
as far as I know the name in about section is read from build prop.
can you provide link to your modified build.prop file so i can see what's a problem.
Have you applied correct permissions (rw-r--r-- or 0644) to build prop after side loading
Go to your Bluetooth settings, select the menu, and Rename this device.
JumboMan said:
@piotrus22, If you correctly modified your build prop then it's almost impossible to come as Oneplus name in about section of setting.
as far as I know the name in about section is read from build prop.
can you provide link to your modified build.prop file so i can see what's a problem.
Have you applied correct permissions (rw-r--r-- or 0644) to build prop after side loading
Click to expand...
Click to collapse
thanks @JumboMan. attached are both build.props (edited and non-edited). I ran the command "adb shell chmod 644 /system/build.prop" after I pushed the file onto the phone. I believe it worked because I added the line about LCD density (ro.sf.lcd_density=420) and the density did indeed change. Also - I am able to view the updated build.prop in a file browser when I open the phone with the changes I've made.
...still confused...
piotrus22 said:
thanks @JumboMan. attached are both build.props (edited and non-edited). I ran the command "adb shell chmod 644 /system/build.prop" after I pushed the file onto the phone. I believe it worked because I added the line about LCD density (ro.sf.lcd_density=420) and the density did indeed change. Also - I am able to view the updated build.prop in a file browser when I open the phone with the changes I've made.
...still confused...
Click to expand...
Click to collapse
I have carefully inspected build.prop file and i found that build.prop doesn't have "ro.product.model" line . That's why you are not able to change device name.
So if you have to change device name you have to manually add above line with whatever device name you want and push file to phone and apply proper permissions
e.g ro.product.model=device name you want
In your case above line will look like ro.product.model=Nexus 5x
Though not required,change lines containing OnePlus to your custom device name
JumboMan said:
I have carefully inspected build.prop file and i found that build.prop doesn't have "ro.product.model" line . That's why you are not able to change device name.
So if you have to change device name you have to manually add above line with whatever device name you want and push file to phone and apply proper permissions
e.g ro.product.model=device name you want
In your case above line will look like ro.product.model=Nexus 5x
Though not required,change lines containing OnePlus to your custom device name
Click to expand...
Click to collapse
ok - making progress here. the model name now shows up as Nexus 5x, but when the computer recognizes the phone it still shows up as ONEPLUS A3000... and what about the build? I've tweaked everything I can think of but still can't change the build number from "ONEPLUS A3000_16_0705"
any ideas?
piotrus22 said:
ok - making progress here. the model name now shows up as Nexus 5x, but when the computer recognizes the phone it still shows up as ONEPLUS A3000... and what about the build? I've tweaked everything I can think of but still can't change the build number from "ONEPLUS A3000_16_0705"
any ideas?
Click to expand...
Click to collapse
now I think I'm going out of ideas.
I think you have to ask some experienced dev
JumboMan said:
now I think I'm going out of ideas.
I think you have to ask some experienced dev
Click to expand...
Click to collapse
how do I do that? just hope one of them sees this post? LOL
piotrus22 said:
how do I do that? just hope one of them sees this post? LOL
Click to expand...
Click to collapse
Yesterday I researched a lot about your question but I only found half answer.
Now Today I'm back with more build prop lines that will 100% solve your question.
This time I tested myself first before posting to confirm the changes
So here is a Trick
=====
1.To change Model Number
ro.product.model=Nexus 5x
2.To Change Build Number
ro.build.display.id=Nexus 5x
ro.build.display.full_id=Nexus 5x
ro.build.id.hardware=Nexus 5x
=====
Note - value "Nexus 5x" is used just as an example.
You change this value to anything you want.
JumboMan said:
Yesterday I researched a lot about your question but I only found half answer.
Now Today I'm back with more build prop lines that will 100% solve your question.
This time I tested myself first before posting to confirm the changes
So here is a Trick
=====
1.To change Model Number
ro.product.model=Nexus 5x
2.To Change Build Number
ro.build.display.id=Nexus 5x
ro.build.display.full_id=Nexus 5x
ro.build.id.hardware=Nexus 5x
=====
Note - value "Nexus 5x" is used just as an example.
You change this value to anything you want.
Click to expand...
Click to collapse
you sir are amazing. just tried it and it worked. will test it out to see if it causes other issues. may I buy you a beer?
piotrus22 said:
may I buy you a beer?
Click to expand...
Click to collapse
For me Thanks=Beer, so thanks are sufficient
JumboMan said:
For me Thanks=Beer, so thanks are sufficient
Click to expand...
Click to collapse
Ok @JumboMan, so now my phone won't save video. Basically when I try to take a video with the camera app, it hangs up on the "saving" section. Then the only way to get the camera running again is to reboot. I can't believe this is related to what I did in the build.prop files right?
The driver names will ever be the real device name. So...
:thumbup:
Sent from my XT320 using xda premium
piotrus22 said:
Ok @JumboMan, so now my phone won't save video. Basically when I try to take a video with the camera app, it hangs up on the "saving" section. Then the only way to get the camera running again is to reboot. I can't believe this is related to what I did in the build.prop files right?
Click to expand...
Click to collapse
It may be due to build prop changes but I'm not sure. can you use 3rd party camera app check for your problem. or it only occurs with stock camera.
JumboMan said:
It may be due to build prop changes but I'm not sure. can you use 3rd party camera app check for your problem. or it only occurs with stock camera.
Click to expand...
Click to collapse
Third party camera app has the same problem. Will revert to original build prop and see if that fixes the issue. Will report back.
JumboMan said:
For me Thanks=Beer, so thanks are sufficient
Click to expand...
Click to collapse
Dethfull said:
The driver names will ever be the real device name. So...
:thumbup:
Sent from my XT320 using xda premium
Click to expand...
Click to collapse
@Dethfull do you know which items in the build prop coordinate to the drivers for the camera?
ok so I think I fixed it. I played around with the build.prop file and it appears changing the ro.product.manufacturer =OnePlus back from Nexus5 did the trick. Camera seems to be much faster than before and videos can save now, and the Good app still works.
Will update if things change but hopefully not!
!!ATTENTION!!
As Google recently changed how the device_profile files are located, these steps below do NOT work anymore. There are only two options you can choose from which you can follow and read about here
#I'll not be responsible for anything that happens to your device when you follow these steps#
If you don't know what ARCore is read this https://en.m.wikipedia.org/wiki/ARCore
After you understand what ARCore is for then continue reading.
@Arnova8G2 has made a flashable zip with support for our device.
AR Stickers download https://drive.google.com/open?id=1Uvspxje-myBIKIeDHfgMpZ4Uv_o5ZFYL
Installation steps:
1. Install original arcore linked below
2. Reboot to TWRP
3. Install twrp-Patch-ARcore-for-all-device.zip
4. Reboot to system
Zip download here. This method is still under testing, so the original method is still shown below.
Step 1. Download ARCore from here https://www.apkmirror.com/apk/googl...se/arcore-1-4-180716096-android-apk-download/
Step 2. Install an app that use ARCore. If you're lazy, you can use this https://www.apkmirror.com/apk/google-creative-lab/just-a-line-draw-anywhere-with-ar/
Step 3. Open the app you installed in step 2 and let it crash. This will make the folders and files that we're going to use later on.
Step 4. Download the file named device_profile_vince.textproto.txt at the end of this post and rename the file to device_profile_vince.textproto
Step 5. Using root explorer, copy the file you just renamed to /data/data/com.google.ar.core/files/device_profile_database2 and change SE context by selecting the file you just copied and press the three dots. Then select Restore default context and then press OK.
Step 6. Now you can use any apps that require ARCore!:victory:
NOTE: If you updated ARCore repeat step 3 to step 5
Tested on my vince running AEX and havoc os with omnivision sensor
Not really necessary anymore as we've Arnova8G2's flashable zip but I'll keep it here anyways
During the steps above, you probably saw a bunch of files in /data/data/com.google.ar.core/files/device_profile_database. One file is for one device or another variant of the same device. These files come from the manufacturers or Google themselves for the devices that officially ARCore.
Unfortunately, vince, like a lot of other devices, don't officially support ARCore, so some of these files maybe more compatible with vince but I don't have time to test them all. So if anybody have extra time, you can help me find out which one of these files is best suited for our device. You just have to rename the file you want to test to device_profile_vince_.textproto(the _ is to make sure you don't accidentally replace the original device_profile_vince.textproto file) and rename the original device_profile_vince.textproto to device_profile_vince.textproto.bak
If you believe you've found a file that's better than the one on the OP, then please tag me and post the file name in this thread and I'll test it to see if it's better before adding it to the OP
CHANGELOGS;
Code:
3.9.18:Updated links in OP and ARstickers link
5.7.18:Updated OP and Arstickers link
3.7.18:Updated OP
27.06.18:Updated OP
23.06.18:Updated ARCore link
16.06.18:Updated device_profile_vince file
31.05.18:Updated ARCore link
23.05.18: Updated ARStickers link
21.05.18: Initial post
FAQ:
Q:Why (insert app name) can't detect surface?
A:Find a surface that's not shiny or white color. Surfaces that are textured and have sufficient lighting can help. Sometimes a reboot can help too
Q:Why can't I install all apps that use ARCore in play store?
A:They're supposed to be only for devices that officially support ARCore. If you want to use them on vince, download using apkmirror
Q:Why ARCore still isn't working on MIUI even after I followed all the steps?
A:This could be because that MIUI is heavily modified from stock Android so a lot of things aren't working on it.
Q:Why isn't AR Stickers working?
A:Use this version Download, (MIRROR). Thanks to @Arnova8G2 for this
Reserved
Hi.
Thank you for your hard work.
Can I know if potentially all arcore's app can work on Vince?
I am asking this because I'm fully stock and I would like to know for root it.
Sent from my Redmi 5 Plus using Tapatalk
vespino75 said:
Hi.
Thank you for your hard work.
Can I know if potentially all arcore's app can work on Vince?
I am asking this because I'm fully stock and I would like to know for root it.
Sent from my Redmi 5 Plus using Tapatalk
Click to expand...
Click to collapse
All apps that use ARCore should work except for ARStickers, which you've to use the one linked in the FAQ. It's the only app so far I tested that needs to be modded to work.
Deer developer tried every step describe by you on miui costum rom wash n dish by Jerome-X but not worked any AR core based software always it is saying that device is not supported check the screen shots.
irfan.shikarpuri said:
Deer developer tried every step describe by you on miui costum rom wash n dish by Jerome-X but not worked any AR core based software always it is saying that device is not supported check the screen shots.
Click to expand...
Click to collapse
I wish Venice could support the AR core
Really good work done by you to enable this feature.
May be I am getting error due to miui
Mhhh... Weird.
I must wait 110 hours until unlock my bootloader... Damn.
Anyway.
I developed some app with Google tango.
And yes, the problem can be the Android version also.
Arcore works on few models with Android nougat. If you use a smooth vanilla 8.0 it can works (maybe).
If someone wants to try, please, try this app (now I can't because the bootloader),
Sent from my Redmi 5 Plus using Tapatalk
Now I got it that I have android 7.0 and AR core works good on android 8.0
Does not work with dotos.... why?
i followed exactly the guide...
irfan.shikarpuri said:
Now I got it that I have android 7.0 and AR core works good on android 8.0
Click to expand...
Click to collapse
Hmm, that's weird, it should work for nougat ROMs too. Maybe because MIUi is heavily modified
vespino75 said:
Does not work with dotos.... why?
i followed exactly the guide...
Click to expand...
Click to collapse
Are you sure you followed all the steps exactly? And how does it not work?
Yes I followed the instructions, and all the app (I tested 3 app) does not work (included the area stickers and yours in the guide).
I did also the last modify with root explorer... But I have the same problem of irfan
vespino75 said:
Yes I followed the instructions, and all the app (I tested 3 app) does not work (included the area stickers and yours in the guide).
I did also the last modify with root explorer... But I have the same problem of irfan
Click to expand...
Click to collapse
How does it not work? Did the app just crash or something else?
Stampyron said:
How does it not work? Did the app just crash or something else?
Click to expand...
Click to collapse
The app says "your device is not compatible with AR"
Sent from my Redmi 5 Plus using Tapatalk
vespino75 said:
The app says "your device is not compatible with AR"
Sent from my Redmi 5 Plus using Tapatalk
Click to expand...
Click to collapse
Then either you didn't rename the file correctly or you didn't restore SE context
Stampyron said:
Then either you didn't rename the file correctly or you didn't restore SE context
Click to expand...
Click to collapse
I did it. Both.
There is some problem... Can I do something?
I tried also to use the extension .proto instead .textproto, with the first extension the app crash.
Sent from my Redmi 5 Plus using Tapatalk
vespino75 said:
I did it. Both.
There is some problem... Can I do something?View attachment 4512944View attachment 4512945
I tried also to use the extension .proto instead .textproto, with the first extension the app crash.
Sent from my Redmi 5 Plus using Tapatalk
Click to expand...
Click to collapse
Try put permission to rw and reboot
Hi there, I was search about the SHealth but for S10 Plus I didn't find any of thread related to the app instead one patched version. Yesterday I somewhere read the tutorial once I had S7 Edge to change build.prop text i.e ro.config.tima = 1 to ro.config.tima = 0 and it works without any issues or updating app. Just sharing with you nothing else. All credits goes to the original creator and I am just sharing it only. Just use the editor to edit file like root explorer or something like. Or use BuildProp Editor for this.
Best Regards
Well yeah, this change to build.prop is only needed for those running stock rom rooted, as most (if not all) custom roms already have this tweak and many others.
GearCEO said:
Hi there, I was search about the SHealth but for S10 Plus I didn't find any of thread related to the app instead one patched version. Yesterday I somewhere read the tutorial once I had S7 Edge to change build.prop text i.e ro.config.tima = 1 to ro.config.tima = 0 and it works without any issues or updating app. Just sharing with you nothing else. All credits goes to the original creator and I am just sharing it only. Just use the editor to edit file like root explorer or something like. Or use BuildProp Editor for this.
Best Regards
Click to expand...
Click to collapse
Do ro.config.knox=0
ro.config.timaversion=0
ro.config.rkf=0
That disables knox.
ExtremeGrief said:
Do ro.config.knox=0
ro.config.timaversion=0
ro.config.rkf=0
That disables knox.
Click to expand...
Click to collapse
Nice find sir
I'm not interested to root phone but I'll be glad to get Pixel ROM on S10+.
Sent from my SM-G975F using Tapatalk
No work with root in Android 10
Shealth works with root on Android10.
Only set tima=0
GearCEO said:
Hi there, I was search about the SHealth but for S10 Plus I didn't find any of thread related to the app instead one patched version. Yesterday I somewhere read the tutorial once I had S7 Edge to change build.prop text i.e ro.config.tima = 1 to ro.config.tima = 0 and it works without any issues or updating app. Just sharing with you nothing else. All credits goes to the original creator and I am just sharing it only. Just use the editor to edit file like root explorer or something like. Or use BuildProp Editor for this.
Best Regards
Click to expand...
Click to collapse
Just make a magisk module for it, very simple, it persists with updates.