yashsingh1/xdaforums huggingface dataset:
[Treble-Enabled Device Development A/AB ROMS] elmxx:
AOSP 10.0 Quack Phh-Treble Update!

Hi!,

I installed official AOSP 10.0 v208 but now There is new update AOSP 10.0 v209.

when I checked system-update in sony xperia xz phone update section I cant see Phh-Treble new Update AOSP 10.0 v209.!

Do I have to use Install GSI via "fastboot flash system your-gsi-image.img" every time for each new update ?

I need little info;

Thanks advance,
[Treble-Enabled Device Development A/AB ROMS] amrazing33:
Hi,

I just flashed v208 to my treble-ized Galaxy A8+. Almost everything works perfectly (Camera, Fingerprint, although network bars only go up to two bars), but I found this weird bug where I can't seem to update Chrome to the newest version.

Does anyone have the same bug? Any solution?

Thanks.
[Treble-Enabled Device Development A/AB ROMS] DarkestSpawn:
Were those logcats of radio data helpful in figuring out the not receiving texts issue #976 on GitHub or did you need anything else?
[Treble-Enabled Device Development A/AB ROMS] saiz0313:
it's working!

Thanks!

e2fsck -y /dev/block/by-name/system

e2fsck -f /dev/block/by-name/system

resize2fs /dev/block/by-name/system

reboot twrp

/system is bigger !

flashed gapps !
[Treble-Enabled Device Development A/AB ROMS] saiz0313:
How can i do to remove build-in superuser?(AOSP 10 V209)

and bootloop to TWRP

I want to remove superuser,and flash magisk.
[Treble-Enabled Device Development A/AB ROMS] dhacke:
That can be done over the Securize button under 'settings' => 'Phh Treble Setting' => 'Misc features'.

But in my case it leaded at least on v208 to a bootloop on my pixel 4 xl, too. So i can't suggest it.

Better root once with Magisk and after that disable the pre-installed su app. That's the way i handle it.
[Treble-Enabled Device Development A/AB ROMS] saiz0313:
SafetyNet passed?

I have another problem.

Flashed some ROMs:

AOSP 9 v122 v123, Havoc-OS 3.x v20191225 by turbolukex5,

PixelExperience 20191208 by turbolukex5 ,

volutionX_3.5 20191214-1916by turbolukex5

All are no signal,dual sim.

AOSP 10 V209 works well

why~?
[Treble-Enabled Device Development A/AB ROMS] dhacke:
Idk because i don't use any app which needs that. So i don't care.

Sry but again Idk. Probably it has something to do with baseband or vendor. But it's only a suggestion from a no-dev. Logs would be a good idea;)

Then the devs can mayby fix it.
[Treble-Enabled Device Development A/AB ROMS] koyo:
Did you ever fix this problem? Its happening on my Moto G6 as well. Doesn't happen on LineageOS 17 GSI though
[Treble-Enabled Device Development A/AB ROMS] dotKin:
The system is in setup mode. Do

'adb shell settings put secure user_setup_complete 1'

'adb shell settings put global device_provisioned 1'

Or you can reflash system, reboot to system, reboot to recovery and flash gapps (you don't need to wipe anything)
[Treble-Enabled Device Development A/AB ROMS] saiz0313:
Baseband/vendor changed together when I flashed img?

Maybe I flash vendor again?

I don't know how to flash baseband.

I don't khow how to get Logs.
[Treble-Enabled Device Development A/AB ROMS] saiz0313:
I got removing-supersu!

chmod +x /system/bin/phh-securize.sh

auto-reboot after finished.

but bootloop to TWRP.

Factory Reset and Format /data.

booting to OS,no superuser !
[Treble-Enabled Device Development A/AB ROMS] kylek389:
Huawei P20 Lite ANE-LX3, stuck on "android" boot logo:

01-11 01:19:22.266 641 641 F libc : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 641 (netd), pid 641 (netd)
01-11 01:19:22.295 646 646 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
01-11 01:19:22.295 646 646 F DEBUG : Build fingerprint: 'HUAWEI/ANE-LX3/HWANE:8.0.0/HUAWEIANE-LX3/152(C605):user/release-keys'
01-11 01:19:22.296 646 646 F DEBUG : Revision: '0'
01-11 01:19:22.296 646 646 F DEBUG : ABI: 'arm64'
01-11 01:19:22.296 646 646 F DEBUG : Timestamp: 2020-01-11 07:19:22+0000
01-11 01:19:22.296 646 646 F DEBUG : pid: 641, tid: 641, name: netd >>> /system/bin/netd <<<
01-11 01:19:22.296 646 646 F DEBUG : uid: 0
01-11 01:19:22.296 646 646 F DEBUG : signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
01-11 01:19:22.296 646 646 F DEBUG : x0 0000000000000000 x1 0000000000000281 x2 0000000000000006 x3 0000007fdc61fc40
01-11 01:19:22.296 646 646 F DEBUG : x4 0000000000000000 x5 0000000000000000 x6 0000000000000000 x7 0000000000008000
01-11 01:19:22.296 646 646 F DEBUG : x8 00000000000000f0 x9 b6dd1444a0aaeb66 x10 0000000000000001 x11 0000000000000000
01-11 01:19:22.296 646 646 F DEBUG : x12 fffffff0ffffffdf x13 0000000000000030 x14 0000000000000001 x15 0000403ef0aa8090
01-11 01:19:22.296 646 646 F DEBUG : x16 000000736b81c8c0 x17 000000736b7fa100 x18 000000736cc1c000 x19 0000000000000281
01-11 01:19:22.296 646 646 F DEBUG : x20 0000000000000281 x21 00000000ffffffff x22 000000594f24762a x23 0000007fdc61fd51
01-11 01:19:22.296 646 646 F DEBUG : x24 0000000000000000 x25 0000000000000000 x26 000000736a821ec0 x27 000000594f242f87
01-11 01:19:22.296 646 646 F DEBUG : x28 0000000000000008 x29 0000007fdc61fce0
01-11 01:19:22.296 646 646 F DEBUG : sp 0000007fdc61fc20 lr 000000736b7aef48 pc 000000736b7aef74
01-11 01:19:22.301 646 646 F DEBUG :
01-11 01:19:22.301 646 646 F DEBUG : backtrace:
01-11 01:19:22.301 646 646 F DEBUG : #00 pc 0000000000081f74 /apex/com.android.runtime/lib64/bionic/libc.so (abort+160) (BuildId: 0c11dd187ef9ff6f833cb1140131dc26)
01-11 01:19:22.301 646 646 F DEBUG : #01 pc 000000000003f5b8 /system/bin/netd (resolv_stub_init()+688) (BuildId: 80ae64a0e7aba7c5ad38e6ddcfaec8cb)
01-11 01:19:22.301 646 646 F DEBUG : #02 pc 000000000003fe0c /system/bin/netd (main+200) (BuildId: 80ae64a0e7aba7c5ad38e6ddcfaec8cb)
01-11 01:19:22.301 646 646 F DEBUG : #03 pc 000000000007d798 /apex/com.android.runtime/lib64/bionic/libc.so (__libc_init+108) (BuildId: 0c11dd187ef9ff6f833cb1140131dc26)
[Treble-Enabled Device Development A/AB ROMS] XYZdavid:
Same Here on mi 9
[Treble-Enabled Device Development A/AB ROMS] saiz0313:
V209 on redmi note 8 pro

no call-ring,no media sound,no NFC-SIM
[Treble-Enabled Device Development A/AB ROMS] saiz0313:
v207 ,v209 both are speaker broken(no sound,no ring),youtube not play,no NFC-SIM
[Treble-Enabled Device Development A/AB ROMS] koyo:
I can't get to adb because developer options won't enable.
[Treble-Enabled Device Development A/AB ROMS] Gilbot:
installed on Galaxy Note 10+ SM-N9750. Stock rom works fine on Verizon (data, voice, mms) but on all GSIs I have tried (including this one) only Data works (no voice, mms). Is this APN or Volte related? I'm unsure where to begin. I'd really like to use this AOSP treble GSI instead of stock. :(
[Treble-Enabled Device Development A/AB ROMS] redbullman:
I have the exact same issue with oneplus 7. Tried phh gsi and express Luke based on phh. Calls and texts don't work only data.
[Treble-Enabled Device Development A/AB ROMS] Gilbot:
I've been searching for what could possibly be the answer, but I've come up short. :crying:
[Treble-Enabled Device Development A/AB ROMS] redbullman:
Yep cant find the answer anywhere!
[Treble-Enabled Device Development A/AB ROMS] MotoX4:
Consumer name: Moto X4

Developer name: payton

Model: XT1900-1

Boot type: AB

Arm type: Arm64

Consumer type: Google Fi

Cellular provider: Google Fi

Location: USA

SD card used? No. - Internal storage only (32 GB)

Before install? Full wipe + full partition + full firmware flash = clean device

File: system-quack-arm64-ab-vanilla.img

Build: v209 https://github.com/phhusson/treble_experimentations/releases/tag/v209

Status: Does not boot. :(

Hardware:

A forever loading Andriod Logo (provided by the rom) of which produces no logs.

ROM Software:

N / A
[Treble-Enabled Device Development A/AB ROMS] jwarrior319:
While on the boot logo try: adb shell setprop debug.stagefright.ccodec 0

If that works make sure to edit the build prop and add that to it so you dont need to use adb every boot.
[Treble-Enabled Device Development A/AB ROMS] rajaumarfarooq:
phone is starting issue

[MENTION=1915408]phhusson[/MENTION] cant install the gsi

here is the logcat it gives some missing file and stuck on phone is starting screen

while v202 works perfectly

and v208 and 209 have the same problem it happens on your gsi and also on havocos gsi

the phone is mate 10 lite

any solutions???
[Treble-Enabled Device Development A/AB ROMS] phhusson:
Logs.

Yeah, Verizon is a very special snowflake.

There isn't much I personnally can do since I don't live in the US, though I guess you should be able to find developers willing to work for this.

If there is the Android logo, then you have working adb, so yes it will produce logs.

If you don't have adb, perhaps you have something preventing adb from working? Magisk?
[Treble-Enabled Device Development A/AB ROMS] MIcHiJK:
Anyone know a solution, why every quack gsi since v206 and roms based on them are bootlooping on Huawei p8lite 2017 PRA-LX1? All version before 206 are working fine, which is strange.

Tested on EMUI 8 January 2018, October 2018 and February 2019.

Thanks.
[Treble-Enabled Device Development A/AB ROMS] rajaumarfarooq:
[MENTION=1915408]phhusson[/MENTION]

log for gsi not working on mate 10 lite
[Treble-Enabled Device Development A/AB ROMS] ajislav:
This is most likely due to the Huawei specific changes in v206, see here https://github.com/phhusson/treble_experimentations/releases

I suggest you file an issue on GitHub.
[Treble-Enabled Device Development A/AB ROMS] moshe_lm:
I was used two diffrent GSI-PHH based Android 10 ROMS on RAZER 2 device.

In the both, the BT Audio (music) is not working. I tried all the workarounds I found on the net, but it was not help me.

Thanks for the hard work.
[Treble-Enabled Device Development A/AB ROMS] MotoX4:
adb shell setprop debug.stagefright.ccodec 0

error: no devices/emulators found
[Treble-Enabled Device Development A/AB ROMS] jwarrior319:
Odd. Did you flash vbmeta with --disable-verification and --disable-verity ? Also since its android 10 you need to flash a zip file to disable force-encryprion, I mirrored the file i used here: https://mega.nz/#!ZQBXHS6K!h6XiQP2GB5-N_Rv8rjfeJTt4BjM7XWR2xNk9wRho3dc

It needs to be flashed via twrp.
[Treble-Enabled Device Development A/AB ROMS] th3legend:
Is anyone passing safety net with the latest gsi? I have v206 and not passing basic integrity ...searching the thread with safetynet sounds like this gsi doesn't pass even basic integrity

---------- Post added at 05:24 PM ---------- Previous post was at 04:51 PM ----------

Yes working on a20 right now...failing safetynet basic integrity though
[Treble-Enabled Device Development A/AB ROMS] MotoX4:
I'm honestly going to say, I have no idea what you're talking about.

How I flash a GSI

Boot to bootloader

Load TWRP

Select wipe, format Data

Boot to bootloader

Load TWRP

Select wipe, Advance, select all,

Boot to bootloader

Load TWRP

Push ISO to /sdcard/ <-- Internal storage

Install ISO to /system/

Reboot

It's what I've been doing for a few years now. It works! :good:

Nowhere in this thread or any other GSI have I been instructed to load another kernel. I have no idea what you're talking about when you said flash vbmeta. That said I run a few ROMS and GSI's with Android 8, 9, and 10 without needing to do so. Minus some ROMs needing a firmware update specifically to my device ... what you have said to me today is 1) the first time I've heard anything outside the norm 2) has me puzzled if perhaps what you do is exclusive to your phone.

I do appreciate your willingness to help. I just think whatever you're thinking does not apply here.
[Treble-Enabled Device Development A/AB ROMS] jwarrior319:
The vbmeta is a handful of devices, mainly huawei and in my case onn tablets.

Disabling force encryption has already been stated previously is a must with phh Android 10. What eventually hapens is twrp wont be able to access or modify your data partition. For me it always happens after the first thing flashed that modifies something on it. On boot with force encryption enabled the system scans the entire data partition for changes and locks it if it found something "wrong" for security. Wether or not you set a passcode and enabled encryption dosent matter on android 10 since its enabled by default. Since you dont seem to know much about the changes behind the scenes of android 10 I suggest you do some reading on the android dev site before you mess something up too much.

Ps. I don't mean to sound rued or something, im just trying to help before it results in data loss or "unexplainable" system crash. Never hurts to be well educated rather than just blindly following guides on the internet.
[Treble-Enabled Device Development A/AB ROMS] MotoX4:
Again, I think that is exclusive on your phone. No mention of it was stated in the OP and if you read the 1st page 2nd page of this thread you will know I had successfully install Andriod 10 of this GSI on my phone (Moto X4). I actually had another build booted before too. Which again suggests your vbmeta is exclusive to your Huawei.

Thanks for your attempt at being helpful. -- I'll wait and check out the next build.
[Treble-Enabled Device Development A/AB ROMS] phhusson:
On recent GSIs you have the button "Securize" which pass basic integrity.
[Treble-Enabled Device Development A/AB ROMS] th3legend:
Omg where is this magical button normally!?

Omg found it it's in treble settings misc settings...search doesn't find it but it's in there!...best day ever!!!

---------- Post added at 06:05 PM ---------- Previous post was at 05:12 PM ----------

Hmmm darn that securize button locks up after I grant it su rights and hangs.
[Treble-Enabled Device Development A/AB ROMS] darren1:
This happens to me as well, I'm using Huawei M5 Mediapads 8.4" and 10.1".
[Treble-Enabled Device Development A/AB ROMS] th3legend:
Ya and I tried /system/bin/phh-securize.sh and it just did some output and rebooted...still fails basic integrity and I couldn't catch the output before it rebooted
[Treble-Enabled Device Development A/AB ROMS] natedogg20050:
Realme X2 Pro Works

Things Missing

Fingerprint if fixable

Camera Unlock needs to be fixed

Camera can only Record at 1080p 60 fps not 4K

and it keeps giving me Heapsize Errors about 250 Mb
[Treble-Enabled Device Development A/AB ROMS] drexxie1962:
One issue discovered while driving in my car: no bluetooth in-call audio. Playing music over the cars bluetooth is working fine. Hope there is or will come a solution to make it all perfect :cool:.
[Treble-Enabled Device Development A/AB ROMS] eremitein:
try to comment line (add # at the begin of line)

mount -o bind /mnt/phh/empty_dir /vendor/etc/audio || true

in /system/bin/rw-system.sh
[Treble-Enabled Device Development A/AB ROMS] drexxie1962:
Thanks for your reply! I did a reboot afterwards and and still no bluetooth in-call audio.
[Treble-Enabled Device Development A/AB ROMS] Mr. Gold:
Samsung devices WiFi

Great work by [MENTION=1915408]phhusson[/MENTION]

On v209 WiFi isn't working and turning on WiFi in settings forces a restart and/or turns on for less than 5 seconds and automatically turns off

Tested on Samsung Galaxy S9+ Exynos (G965F/DS) using Pie vendor.
[Treble-Enabled Device Development A/AB ROMS] saiz0313:
Redmi Note8 Pro with V209

No BT,No NFC,no sound,youtube broken
[Treble-Enabled Device Development A/AB ROMS] JuanM2020:
Any solutions to this yet? Are you still running it or did you switch roms?
[Treble-Enabled Device Development A/AB ROMS] RubenGreg:
Just installed on to redmi go. Works wonderfully - except the app -switcher bug is still there.

none of the nav buttons are bind to task switcher

h...... github--com/phhusson/treble_experimentations/issues/876#issuecomment-552126655

any suggestions.
[Treble-Enabled Device Development A/AB ROMS] phhusson:
In ADB:

adb shell settings put secure user_setup_complete 1

adb shell settings put global device_provisioned 1
[Treble-Enabled Device Development A/AB ROMS] dhacke:
Hi,

I'm on the latest vanilla version (v209) and have the patched Magisk from phhusson installed.

On an older version of this rom i tried Titanium Backup and it didn't work.

So i made a new try on v209 and against my expectation the app works now. But it gets the root rights only over the built-in su app (when i deactivate the built-in su app Titanium Backup stucks because the Magisk popup message doesn't appear).

And i want to grant the root rights for the app over Magisk.

So my question: Is there any command or something else which allow Titanium Backup root rights over Magisk?

Thx in advance for help.
[Treble-Enabled Device Development A/AB ROMS] jwarrior319:
Have you tried looking in the superuser tab of magisk? It may be listed and you just need to flip the toggle to grant permission.

Im using the regular unpatched version of magisk 20.3 just fine.
[Treble-Enabled Device Development A/AB ROMS] dhacke:
Yes i looked at this place and Titanium Backup doesn't show up at all.

So that's the problem: No Popup and entry.
[Treble-Enabled Device Development A/AB ROMS] jwarrior319:
You could try disabling the superuser app and reinstall titanium backup. If that dosent do it install the official version of magisk 20.3 . Ive been using it no problems. Idk what's special about the modified one but i haven't had any issues with official. Also make sure force encrypt is disabled via flashing the zip in recovery, android 10 has it enabled by default which can cause issues accessing the data partition after making any modifications to system.
[Treble-Enabled Device Development A/AB ROMS] dhacke:
Neither the official Magisk or new install of Titanium Backup helps.

I didn't test the thing with disabling the encryption but i don't want that too because of security.
[Treble-Enabled Device Development A/AB ROMS] RubenGreg:
Does not work even after these two commands. I ran it as user and not 'root'. hope that is OK.

(I even restarted the device)

---------- Post added at 10:47 AM ---------- Previous post was at 10:15 AM ----------

Another query:

Is the file vbmeta.img specific for each device? or is this generic? I am wondering if I can flash it on a redmi go to disable verify boot:

fastboot --disable-verification flash vbmeta vbmeta.img
[Treble-Enabled Device Development A/AB ROMS] phhusson:
Well that's probably the issue

It kind of depends, so I prefer to say that it is device-dependant.

Please note that for GSIs you need --disable-verity, not --disable-verification.
[Treble-Enabled Device Development A/AB ROMS] dhacke:
Hi,

It seems you done a successfull build and atm i try the same (well it's my second try to be honest).

I already clone the treble experimentation repo and sync phhussons quack gsi successfull. I'm in the directory where the syncing ran.

But how do you make it that the building process starts?

I tried the command 'lunch treble_arm64_bvS-userdebug' (for the quack arm64 ab vanilla version) but it mocks that it can't find the envsetup.sh file and that there are too many arguments. Nevetheless i don't get a error when i type in .build/envsetup.

When i type 'lunch $1' it says the following:

You're building on Linux

Lunch menu...pick a combo:

Bash: cd: To many arguments

build/soong/soong_ui.bash: Can't find file or directory

Can you tell me what steps you did exactly?
[Treble-Enabled Device Development A/AB ROMS] dhacke:
Update: I made a new try and well i have at least a little progress. I choosed the manual way this time to build the rom.

That's the guide i used:

https://github.com/phhusson/treble_experimentations/wiki/How-to-build-a-GSI?

Everythings worked until step 6. When i type in the command 'lunch treble_arm64_bvS-userdebug WITHOUT_CHECK_API=true make -j8 systemimage' i get following messages in my terminal:

cat: /home/'mylinux username'/Desktop/GSI: File or directory not found

cat: phusson/quack/build/envsetup.sh: File or directory not found

cat: cat: /home/'mylinux username'/Desktop/GSI: File or directory not found

bash: cd: To many arguments

build/soong/soong_ui.bash: line 53 /home/'mylinux username'/Desktop/GSI: /home/'mylinux username'/Desktop/GSI: File or directory not found

My question: Why and how can i solve it?

PS: I overskip step 5 in the guide; mayby that's my problem?
[Treble-Enabled Device Development A/AB ROMS] RubenGreg:
adb shell settings put secure user_setup_complete 1
adb shell settings put global device_provisioned 1

even as when running as root does not make any difference!

https://pastebin.com/YgXn0bLr

I am using redmi go (tiare).

---------- Post added at 10:31 AM ---------- Previous post was at 10:27 AM ----------

First it would be polite if you can use the formatting tools in the post. Really please help others to help yourself!

Do not use the

master

Just go to github.com/phhusson/treble_experimentations/releases

For each release there is Assets, source code

Download the github.com/phhusson/treble_experimentations/archive/v209.tar.gz

tar -xvf v209.tar.gz
cd treble_experimentations-209
./build.sh android-10.0

add

depth=1

to your

git clone

if you want avoid tons of unnecessary code.

If possible edit

./build.sh

to remove unwanted architectures; otherwise you will get everything!

works beautifully!
[Treble-Enabled Device Development A/AB ROMS] dhacke:
[MENTION=10219979]RubenGreg[/MENTION]

Thx for the answer. I will test it with the 'asset' way.

Regarding formatting tools: I'm using the limited xda labs app and as far as i see it the app doesn't have much edit possibillities.

But for posts with code i can use the website in future. No problem.
[Treble-Enabled Device Development A/AB ROMS] davidbtc2009:
how do i install patches on a treble rom? I pulled v206 and my wifi doesn't work. I don't know how to load the patches to attempt to fix it. Thx in advance
[Treble-Enabled Device Development A/AB ROMS] Voenix:
Fingerprint works great
[Treble-Enabled Device Development A/AB ROMS] sirbow2:
I have some logs here if you could look at them, phhusson.

These are from a LGG7 ULM. running a 20e base with the latest AOSP 10.0 v209 gsi flashed. So far Ive noticed the following:

-no vibrate

-LED pulses blue all the time even without notifications.

-gcam doesnt open

One log has keyboard vibrate disabled, one enabled. Apparently the vibration thing is caused by running a newer version of android and the immvibed vibration service doesnt like that. It wont let me attach for some reason so: without keyboard vibration and with vib

I also snipped one of the keypresses from the log.

01-24 12:59:29.074 18090 18090 W EmulatorView: sendKeyEvent(KeyEvent { action=ACTION_DOWN, keyCode=KEYCODE_T, scanCode=0, metaState=0, flags=0x6, repeatCount=0, eventTime=6788203, downTime=6788203, deviceId=-1, source=0x0, displayId=0 })
01-24 12:59:29.074 18090 18090 W EmulatorView: sendKeyEvent(KeyEvent { action=ACTION_UP, keyCode=KEYCODE_T, scanCode=0, metaState=0, flags=0x6, repeatCount=0, eventTime=6788203, downTime=6788203, deviceId=-1, source=0x0, displayId=0 })
01-24 12:59:29.075 18090 18090 D EmulatorView: In: 't'
01-24 12:59:29.075 18090 18090 D command_bus: in onInput(t) logcat -d > LOGwithvib.
01-24 12:59:29.091 1063 1063 D ImmersionVibratorService: VibratorEx::off()
01-24 12:59:29.092 1063 1063 D ImmersionVibratorService: VibratorEx::on(39)
01-24 12:59:29.092 1063 1063 D ImmersionVibratorService: VibratorEx::on(): calling ImmVibeInitialize()
01-24 12:59:29.139 1393 1393 E VibeTonz: Cannot run on this device: the supported android version up to [9].
01-24 12:59:29.149 1063 1063 D ImmersionVibratorService: VibratorEx::on(): calling ImmVibeOpenDevice()
01-24 12:59:29.149 1393 1393 E VibeTonz: ImmVibeOpenDevice: g_nVibeAPIReferenceCount invalid.
01-24 12:59:29.149 1063 1063 E VibeTonz: ImmVibeOpenDevice: VibeOSSendRequestReceiveResponseIPC failed.
01-24 12:59:29.149 1393 1393 E VibeTonz: ImmVibeTerminate: g_nVibeAPIReferenceCount invalid.
01-24 12:59:29.149 1393 1393 E VibeTonz: ImmVibeTerminate: g_nVibeAPIReferenceCount invalid.
01-24 12:59:29.150 1063 1063 D ImmersionVibratorService: VibratorEx::setAmplitude(255)
01-24 12:59:29.172 992 992 I QTI PowerHAL: peyotes: ph_handle_interaction
01-24 12:59:29.173 992 992 I QTI PowerHAL: peyotes: ph_handle_interaction
01-24 12:59:29.189 1063 1063 D ImmersionVibratorService: VibratorEx::off()