yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Q&A, Help & Troubleshooting] sharmashubham33:
I am using aspire team c9 port rom with default setting

No teak, nothing.....should buying a new battery will give me nore than 3 h sot
[Galaxy S 4 Q&A, Help & Troubleshooting] foxrft:
Try using another rom like los 14.1 or 15.1 with greenify and amplify and also use open gapps pico for minimal battery consumption.
[Asus ZenFone 3 Zoom Questions & Answers] itsme.Ronjie:
Cannot Unbrick my Phone thru QFIL because of my phone is not detected.
[Samsung Galaxy S9+ Accessories] HaroonZ2:
Hello,

Is anyone aware which VR headset I can purchase that will work on my s9 plus.

Samsung are not releasing one in 2018. So far.

The latest one is for the note 8 plus. Which was released in November 2017. This one works with the s9 plus according to CNET.

Link- https://www.cnet.com/news/samsung-galaxy-s9-gear-vr-compatibility-note-8-daydream-view-mwc/

Has anyone used a VR headset with their s9 plus?

Has anyone purchased the new day dream 2 by Google and used that with their s9 plus?

I'm looking forward to reading your comments.. ??
[Samsung Galaxy S9+ Accessories] Cibor:
Gear VR SM-R323 is working with S9+ (it fits and it is recognized as Gear VR).

Wysłane z mojego SM-G965F przy użyciu Tapatalka
[Samsung Galaxy S9+ Accessories] HaroonZ2:
Good to know. I might look in to the Google day dream 2. I've used a gear vr with my s6 plus a few years ago.

I want to branch out to Google, knowing their quality!

Need to confirm if anyone has used it first.

Cibor. Is the gear vr on s9 plus improved from previous versions?

Does it work for longer? On my s6 I could get 15 mins out of it before it over heats and stops working.

I hope with the s9 plus you can watch a VR video for more that 20 mins before the handset asks to cool down ??
[Samsung Galaxy S9+ Accessories] pieces of cake:
I have the original Daydream headset (latest version is pretty much the same thing, just more accommodating of larger phones) and, personally, I find it to be a waste of money. The Gear VR experience is significantly better. Daydream is just a glorified version of Google Cardboard with a controller. If you want to know what the experience will be like with the Daydream 2, just give Cardboard a try and see if it's up your alley.
[Samsung Galaxy S9+ Accessories] HaroonZ2:
Is it pieces of cake or pieces of Bing? Haha :D Thanks for you comment!

That is good to know! I have used a Google cardboard before.

Gear VR sounds like a good idea then... well better than whats out there :D

I amm going to keep an ear open on the Samsung rumor moon to see if a new Gear VR is in the works.. I damn hope so

Thanks
[Samsung Galaxy S9+ Accessories] Zspy1985:
Just enable Samsung Gear VR Dev mode and you enable the VR feature without an official plug in head set. I'm currently using a $5 cheaply made Walmart VR headset and I get the full experience.
[Samsung Galaxy S9+ Accessories] pieces of cake:
No, I regret to inform you that you're not getting the full experience.

The Gear VR has its own sensors which operate at a far higher resolution than the one in the phone (some of the same internal hardware as the Oculus Rift, actually). Also the touchpad and buttons are on the side which are all connected via usb when inserting the phone into the device. The newer units include the motion controller which further enhances the experience.

The software also operates at a low level enabling low persistence and less latency.

You will not get the full experience without the Gear VR headset, and none of the Gear VR's hardware advantages can be found in the Daydream or any 3rd party headsets of which I'm aware.
[Samsung Galaxy S9+ Accessories] mickeyleah:
The 2017 gear vr with controller works perfectly with the s9 plus
[Samsung Galaxy S9+ Accessories] Ksushant619:
Daydream VR works perfectly.
[Samsung Galaxy S9+ Accessories] HaroonZ2:
Could you confirm the model number please? I want to make sure I'm purchasing the correct one ?
[Samsung Galaxy S9+ Accessories] Toss3:
Everything headset from SM-R323 -> SM-R325 work fine. :) Using the R325 myself (could have gotten a 50% discount by using samsung pay that I missed).
[Samsung Galaxy S9+ Accessories] Moostafa29:
I have the most recent version of both Gear VR and Daydream VR, and there is really no comparison. The Gear VR platform blows Daydream VR out of the water. I feel like the Daydream is a lost and forgotten platform by Google. It feels like like the software was created in the early 2000s, and there is hardly any content, which surprises me, given how great Google's AR platform is.
[Samsung Galaxy S9+ Accessories] DLD23:
Does putting it in gear vr mess up screen protector? I have a full coverage one
[Samsung Galaxy S9+ Accessories] hem.acharya:
Works with google daydream view
[Samsung Galaxy S9+ Accessories] mickeyleah:
I have the sm-r324nzaaxar
[Samsung Galaxy S9+ Accessories] portenmoulsen:
That's not my experience. I own a SM-R323 (bought for my S7 Edge) and a S9+.

The S9+ is about 1mm too long to fit into my headset. It docks fine into the USB-C cradle, and "plings" / starts Oculus, but I can't actually click the phone into the headset holder itself. The phone is too long to fit into the top-end bracket that holds the phone in place.

Maybe I could force the phone in... it's only ever-so-slightly too large. But that looks like it could damage either the USB-C port or the top of my phone.

Since we're talking just ~1mm of clearance needed, it could maybe vary from headset to headset, so YMMV. But my S9+ doesn't fit into my VR SM-R323.
[Samsung Galaxy S9+ Accessories] azian_advanced:
My S9+ fits in my VR SM-323. It just barely fits but that's on a naked phone with no case, vinyl wrap, or screen protector.
[Samsung Galaxy S9+ Accessories] pagantek:
R325NZVAXAR is the model that I bought, and it fits great. No problems, and is oh so smooth. The S9+ has a little more screen door than the s7edge, but at least it doesn't discharge when plugged in and doesn't overheat.
[Samsung Galaxy S9+ Accessories] Dewhiz:
Get the R325 definitely for s9+ just make sure you lock the is adapter in place (there's a slider after fitting it in). First time I used mine the phone fell out, luckily no damage but heart stopping. The resolution is massively improved over the s7 edge. And the controller makes life so much easier. And seems like there's no overheating problems. Only thing I don't like is how many permissions everything wants. Occulus wanted my google account which I granted before questioning. Get it 2nd hand from cex, I did and it was actually still all in its original wrapping. Happy days!
[Google Pixel 2 Questions & Answers] xFirefly93:
Hi!

I am at the moment using latest build of FlashKernel but thinking about first reverting back to stock kernel, so I instead can flash latest ElementalX Kernel for 8.1.0 (March update.)

Now to the question..

How is the exact procedure and way to do this actually? I've tried google it but can't really find anything that tells me how-to do it. Anyone around here that can shed & share some light on this?

:confused:
[Google Pixel 2 Questions & Answers] cntryby429:
Flash the stock boot.img to the "boot" slot. That is to say:

Download the full image or ota from Google. Extract it and locate the boot.img. You may have to extract a second zipped file to find it , I forget. Fastboot flash boot path\to\boot.img where "path\to\" is the path to where the extracted boot.img file is located on the computer. Be aware that recovery lies within the boot.img so if you had twrp installed and still want it then it'll have to be reflashed with the two-step process (boot the .img and flash the .zip)
[Xiaomi Redmi 1S] bose123456789:
My Redmi 1s mobile restart automatically while playing songs of high definition audio files.. Size of mp3 files around 10 to 13 mb size files.
[MTCD Software Development] xdamember2:
Assumptions:

The unit should be rooted. Otherwise you can’t update system files.

MTCManager.apk should be de-odexed. I was able to do this successfully with "Tickle my Android". Thanks to post below for the suggestion.

The unit is configured for auto-sleep (not delayed shutdown)

Background:

When the unit goes to sleep, most processes and services are “killed”. There is an app by Graser, which goes by the name Dasaita and runs as an Xposed module, that allows apps to be whitelisted and then they will not be killed. However it doesn’t at this time work in Oreo, at least in my experience, and it does not work on Services so it doesn’t help with accessibility services.

General procedure:

1. Extract mtcmanager.apk from the head unit

2. Decompile mtcmanager.apk with apktool.exe

3. Edit a smali file

4. Recompile

5. Copy over the original apk (make a backup of course)

6. Set permissions and owner

7. Restart the HU

Details:

1.	The location of MTCManager.apk is /system/priv-app/MTCManager. It requires a file manager that uses root to access it. I like Root Explorer. Copy to USB or SD.

2.	Locate apktool and follow the installation instructions to install on a Windows machine. I don’t know if it is or isn’t available for a Unix or Linux machine (or a mac). Make MTCManager.apk readable on the machine where apktool is installed. Enter the command

Apktool d -o <where to decompile> <full path to MTCManager.apk>

Recommend entering “MTCManager.apk” with the original capitalization so it’s easy to copy back.

3.	On Oreo the file is c.smali. There are two lists, the first is services and the second processes. Malaysk has added Tasker to both lists. I add as required to both lists. One app didn’t work exactly right and it helped to remove it from the process list.

Note there is a constant before each list specifying the list length.

Adding to the lists is a simple programming task. Roughly speaking duplicate 3 lines of code,change the index (subscript) and app name string, for each of the packages to be added to each list.

4.	Enter the command apktool b -c <path where it was decompiled>

This will create a directory called “dist”, containing the modified apk.

5.	Copy the new apk to usb or sd, then on the HU copy over the original mtcmanager.apk. Overwriting seems to be the most reliable way to install.

6.	Use the file manager to change the permissions to 644, and the owner and group to <root>.

7.	Restart the HU.
[MTCD Software Development] albtross:
Thank you for the instructions. This got me started on the right path. However I believe the instructions above are missing a step. You also need to increase the size of the array(s) if you are adding additional applications to the whitelist.

My original c.smail I had the following starting in line 222:

const-string/jumbo v1, "net.dinglisch.android.tasker"

const/16 v2, 0x19

aput-object v1, v0, v2​

This is the last entry added by Malaysk in the services section.

These lines do the following:

Copy "net.dinglisch.android.tasker" to the variable v1

Copy 0x19 (decimal 25) to the variable v2

Add v1 ("net.dinglisch.android.tasker") to Array v0 at position v2 (25)

If you are not using tasker, then you can just replace "net.dinglisch.android.tasker", with the application of your choosing. Otherwise you must add another row to the array.

First you must increase the size of the array.

Starting on line 57 I had:

const/16 v0, 0x1a

new-array v0, v0, [Ljava/lang/String;​

These 2 lines establish array v0.

Copy 0x1a (decimal 26) to the variable v0

Create array v0 of size v0 (26)

To increase the size the array so that you can add another entry, change this to:

const/16 v0, 0x1b

new-array v0, v0, [Ljava/lang/String;​

And add a new entry below the tasker entry:

const-string/jumbo v1, "com.teslacoilsw.launcher"

const/16 v2, 0x1a

aput-object v1, v0, v2​

The entire process must be repeated again, if you wish to add to the process section.

On line 232 I had:

const/16 v0, 0x1b ==> Changed to 0x1c

new-array v0, v0, [Ljava/lang/String;​

Added below tasker entry on line 404:

const-string/jumbo v1, "com.teslacoilsw.launcher"

const/16 v2, 0x1b

aput-object v1, v0, v2​

After compiling with apktool, copying MTCManager.apk to the head unit and rebooting, everything works as expected.
[MTCD Software Development] Wout2426:
Is it possible to post your modified apk ? Are you on malaysk Oreo ?
[MTCD Software Development] albtross:
Yes I'm on Malaysk Oreo.

I can post the apk, but since I only added com.teslacoilsw.launcher & de.dieterthiess.ipwidget, I'm not sure it will do you much good.
[MTCD Software Development] Wout2426:
I want to do it myself, it's only to compare it with yours as a reference.

I never done this, don't even know what array size is....
[MTCD Software Development] Gnomepises:
I am at Malaysk Oreo and my c.smali is not the same at line 57.

I would like too to see how have you modified the file, as Wout2426 says I want to do it but I don't really understand your post and it would be nice to have an example to understand it.

I've tried to change tasker for another task (radardroid) and it is working well. Now I want to whitelist more tasks, not only replace tasker.

Thanks in advance
[MTCD Software Development] albtross:
Sorry for the delay, but I've been out of town. This is my modified c.smali from Malaysk Oreo version 1.1.
[MTCD Software Development] Wout2426:
I followed the guide, decompiled the MTCManager.apk. Replaced the tasker entry into com.ankai.cardvr (my dashcam app), re-compiled, and put it in system/etc/mtcmanager, with 0644 permission.

And, it works. After hu is started dvr app starts. It's a dashcam with it's own sd card, so it will start recording anyway, but now it shows correct time and gps coordinates in the time stamp.

Thx guys !
[MTCD Software Development] greg_z:
Hi! I have a problem with recompilation. I copied mtcdmanager for from unit. Inside I have a APK file and directory oat\arm64 with odex files. When I execute apk tool it creates original dir and res. I can't find c.smali file anywhere. I'm using stock Oreo

Ok I get it, needs to be deoxeted.

Regards

Greg
[MTCD Software Development] Aaaron16:
Rather than whitelisting, is it possible to modify MTCManager so it doesn't kill anything?
[MTCD Software Development] xdamember2:
That's a good question. I may try it at some point.
[MTCD Software Development] Xorit:
Id be really interested, but can't try myself due to stock rom and missing GPS slot.

By revising the c.smali, did you find the Clearprocess.java mentioned at the top? Should be stated to kill everything in that class..?
[MTCD Software Development] Brendo:
I like that the device sleeps. I dislike that the device kills the services :(

Will be looking at a non-root way to get this working (or an easy way to root haha)
[MTCD Software Development] xdamember2:
I am now more interested, I'm finding mild instability after wake. Yes, c.smali mentions Clearprocess.java.

Update: I am trying a "no kill" solution, I have added a line "return v5" in the methods ha and gz close to the top of each, just after the two constants. HU is working ok. I added an accessibility service and confirmed it persisted. I'm not sure what else to test. I will see what I notice in use.
[MTCD Software Development] Xorit:
Nice, tell us more when you got time to test.

Ive had some troubles decompiling/recompiling and found that my used framework was outdated.

Advanced apktool from xda got me the right framework AND to get the whole thing to work, you have to sign the apk after recompiling..

Though, any additions work as intended.

Cheers
[MTCD Software Development] Brendo:
Also give this a try for a non root approach

https://xdaforums.com/android-auto/mtcd-software-development/start-app-service-wake-root-t3803636
[MTCD Software Development] xdamember2:
I've been running no-kill for a week with no problems. Occasional crashes in Gmaps and Google have stopped it seems.
[MTCD Software Development] Aaaron16:
That's awesome! Mind posting your fixed apk for those of us having compilation issues?
[MTCD Software Development] Xorit:
little more details for the smali noobs would be cool tho :)

Found that adding FCC launcher to the whitelist makes it unresponsive after wake, but removing it will stop the clock ^_^
[MTCD Software Development] sicily123:
Could you upload your no-kill version of mtcmanager? I have been trying to compile my own version but no luck so far. Thanks!
[MTCD Software Development] xdamember2:
Here is my running version. It's based on Malaysk 1.1.
[MTCD Software Development] Xorit:
For me id like to have the code you changed, but ill revise your apk.

Thx man!
[MTCD Software Development] Xorit:
After a week of testing, Ill revert to my whitelist apk.

Something's fishy with the apps, some of them seem to lock up during sleep or still being killed.
[MTCD Software Development] Aaaron16:
In my MTCManager, there were two lines in d.smali that I deleted: one that referenced killProcess... and another for forceStop. I didn't want to change any other logic as I wasn't sure if there was further housekeeping in those methods. Essentially MTCManager does everything it previously did, but skips the system calls for killing a process or force stopping it in those two places.

MTCManager didn't' seem to do anything with the return value, so I'd be surprised if this destabilizes anything. I would post my recompiled version, but it'll probably have minor differences for various ROMs (mine's an older version).
[MTCD Software Development] xdamember2:
fwiw here is my no-kill version for Malaysk px5 Oreo 2.0. I've used it for a couple of days.
[MTCD Software Development] Xorit:
c.smali in Malaysk 2.0

:try_start_0

invoke-virtual {v0, v1}, Landroid/app/ActivityManager;->killBackgroundProcesses(Ljava/lang/String;)V

:try_end_0

:try_start_0

invoke-virtual {v0, p1}, Landroid/app/ActivityManager;->forceStopPackage(Ljava/lang/String;)V

:try_end_0

dunno what happens if I quote out those lines - or does it need more code?

[MENTION=1633283]Aaaron16[/MENTION]

Cheers [MENTION=7329495]xdamember2[/MENTION]

Did you use the same method as Aron?
[MTCD Software Development] xdamember2:
I did it differently. I modified the functions that search the whitelist to always return a 1.
[MTCD Software Development] skezza:
Quick question, when I decompile with apktool, I don't get any smali files. If it's a case of deodexing my ROM, how would I go about this? I'm on a stock ROM and really want to avoid messing around with Malaysk just yet.
[MTCD Software Development] Xorit:
Try this: https://xdaforums.com/showthread.php?t=2213235
[MTCD Software Development] skezza:
I've used another tool called Tickle My Android, I supposedly have a signed binary now which I'm about to go and try. With a bit of luck, I'll have Tasker, but i also made some other sweet mods, such as nop'ing a few of the ridiculous ****ing steering controls that the OEM hard coded. With these nop'd, I can set some better ones in Mcdtools and this thing will become next level top draw. ;)

Wish me luck :)
[MTCD Software Development] Xorit:
I really do, because I haven't found any reference to my hard coded buttons :) no panel buttons are recoqnized in any "remapper" - they just do what someone coded them to.. ridiculous as you said :)
[MTCD Software Development] skezza:
Yup and on my unit, they mostly make sense, but one in particular is ridiculous. There is a steering wheel button with a man shouting, I suspect if you had the OEM stereo and the optional extras (my car didn't), it perhaps activated the phone option or the opened the phonebook perhaps? Maybe voice command dialing or something. Anyway, it mutes the device. It's a bloody mute button. And no, you can't change it without hacking which is what I'm doing ;)
[MTCD Software Development] Xorit:
There should be IrKeys something in the privapps section, will try extracting an decompiling - see what it has to offer.

On MTCB the MTC keys xposed did exactly that - interrupting the system calls and map them with something else - BUT on MTCD the exposed makes the device go into a bootloop

Tested myself, can't recommend :p

BTW: I have 2 mute keys with the standard mapping + my Info button doesn't bring up climate info, but rather starting up the nav app.

I really want to be able to remap the buttons ;)
[MTCD Software Development] skezza:
I've successfully remap'd the Mute key, so it can be done. You just need to deprogram it. I suggest decompiling MTCManager.apk. However, if you can't find it, what you can do, is decompile all of the sys apps and then look for a toast or something that I suspect you see when you press the mute on your steering wheel.

I too, tried MTCKeys and yup, boot loop. Luckily reflash stock and you don't lose your apps or settings :)
[MTCD Software Development] Xorit:
We're compromising the thread :D

-> MTCManager -> which of the smali files? Tried to find anything related to the keys, but will try again. Cheers
[MTCD Software Development] skezza:
We are definitely derailing it a bit, so it might be worth us starting a new one for this..... However, just in case anyone is interested.....

I can't say which smali file because all MTCManagers are different depending on which manufacturer you bought from. Which key are you looking for though? Mute button? This was the dumb one for me.

My method of discovery was this:

Pressing the Mute button on the Steering wheel resulted in a toast for:

MUTE : ON/OFF (depending on the state)

I searched for MUTE and found the string resource in strings.xml

<string name="muteon">MUTE : ON</string>
<string name="muteoff">MUTE : OFF</string>

I then went into the R$string.smali file which is the memory address file and grabbed the address

.field public static final muteoff:I = 0x7f050008

.field public static final muteon:I = 0x7f050007

Search for the memory address of the string resource and found the only functionwhere this string resource is used.

.method protected ab()V
.registers 5

const/4 v3, 0x0

const-string/jumbo v0, "av_mute="

invoke-virtual {p0, v0}, Landroid/microntek/service/MicrontekServiceBase;->az(Ljava/lang/String;)Ljava/lang/String;

move-result-object v0

const-string/jumbo v1, "false"

invoke-virtual {v0, v1}, Ljava/lang/String;->equals(Ljava/lang/Object;)Z

move-result v0

if-eqz v0, :cond_29

const-string/jumbo v0, "av_mute=true"

invoke-virtual {p0, v0}, Landroid/microntek/service/MicrontekServiceBase;->bp(Ljava/lang/String;)V

nop

invoke-virtual {p0}, Landroid/content/ContextWrapper;->getResources()Landroid/content/res/Resources;

move-result-object v0

[B] const v1, 0x7f050007[/B]

invoke-virtual {v0, v1}, Landroid/content/res/Resources;->getString(I)Ljava/lang/String;

move-result-object v0

:goto_25
nop

return-void

:cond_29
sget-boolean v0, Landroid/microntek/service/MicrontekServiceBase;->r:Z

if-nez v0, :cond_31

sget-boolean v0, Landroid/microntek/service/MicrontekServiceBase;->be:Z

if-eqz v0, :cond_55

:cond_31
const-string/jumbo v0, "av_phone_volume="

:goto_34
invoke-virtual {p0}, Landroid/content/ContextWrapper;->getContentResolver()Landroid/content/ContentResolver;

move-result-object v1

sget v2, Landroid/microntek/service/MicrontekServiceBase;->n:I

div-int/lit8 v2, v2, 0x2

invoke-static {v1, v0, v2}, Landroid/provider/Settings$System;->getInt(Landroid/content/ContentResolver;Ljava/lang/String;I)I

move-result v0

const-string/jumbo v1, "av_mute=false"

invoke-virtual {p0, v1}, Landroid/microntek/service/MicrontekServiceBase;->bp(Ljava/lang/String;)V

nop

invoke-virtual {p0}, Landroid/content/ContextWrapper;->getResources()Landroid/content/res/Resources;

move-result-object v0

const v1, 0x7f050008

invoke-virtual {v0, v1}, Landroid/content/res/Resources;->getString(I)Ljava/lang/String;

move-result-object v0

goto :goto_25

:cond_55
const-string/jumbo v0, "av_volume="

goto :goto_34
.end method

NOP'd the function. Job done.

.method protected ab()V
.locals 4

return-void

.end method
[MTCD Software Development] Xorit:
Cheers, will try :)
[MTCD Software Development] Aaaron16:
Yes, remove the two lines starting with invoke-virtual and you should be fine. A correctly functioning package should never call forcePackageStop or killBackgroundProcesses. If you modify only these two lines, your MTCManager package *should* remain stable.