yashsingh1/xdaforums huggingface dataset:
[HTC EVO 3D] masterdukill:
Hi,

I have a Sprint HTC Evo3D

-HTCDev "Unlocked"

-Shooter XC Ship S-ON RL

-HBOOT 1.50

-TWRP Recovery 2.8.7 Loaded

I'm trying to make this phone usable, and all guides kind of shoot me in dead end. Nothing is working, and i tried flashing a bunch of random roms.

Can anyone give me directions, or point me in the right direction? I'm looking to revert this to a stock rom or something usable. Preferably the latest Andriod revision. I don't care for root, or anything special... I just need the wifi and browser, this isn't a service phone.
[HTC EVO 3D] Coaxs94:
Try to flash boot.img from the rom.rar that you have installed. What is your radio baseband version?
[HTC EVO 3D] masterdukill:
How do i tell what radio baseband do i have?

When you say try to flash the boot.img, do you mean literally "fastboot flash recovery xxxx.img" to the system? I grabbed the VILLUMINATI-08152014-shooter.zip & it did flash via the TWRP, but did not boot up afterwards.
[HTC EVO 3D] Coaxs94:
No, actually "fastboot flash boot boot.img" to the system. Just extract boot.img form rom.zip and put it to your ADB tools folder a hit "fastboot flash boot boot.img" command, try it. Does bootloader shows your radio version? Check that.
[HTC EVO 3D] bigsupersquid:
villuminati, liquid smooth both require s-off and specific HBOOT.

you are s-on. cm11 won't run.

try a stock-based rom, those should work.
[HTC EVO 3D] bigsupersquid:
oops, read closer, you're not finding stock roms.

this one works ok without s-off on the two 3vo's I tried it on.http://xdaforums.com/htc-evo-3d/cdma-development/rom-3d-anthology-12-18-2014-t2977403
[HTC EVO 3D] masterdukill:
I tried flashing the base, waiting 20min, and got nothing. The phone is stuck on the white HTC boot screen logo. I then flashed the badassrom over it, and got the same result. FYI, i'm using the twrp recovery to flash both these roms.

Does anybody have a link to the stock rom? I tried the "PG86IMG_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304-signed.zip" and it seemed to be stuck also.

Any other ideas?
[HTC EVO 3D] bigsupersquid:
you could try flashing an official RUU

they're posted in the stickies somewhere.

that'll rewrite all your firmware to something that should hopefully boot up.
[HTC EVO 3D] masterdukill:
When you flash the RUU, is that running through the executable? I find that impossible b/c it requires you to have a working OS first to start off with? Can you flash a RUU with fastboot?
[HTC EVO 3D] bigsupersquid:
there's .exe ruu's for window$ fastboot and PG86IMG.zip files for the root of your SD card in fastboot. since the phone's gotten long in the tooth a lot of links are dead so you may need to hunt a bit.
[HTC EVO 3D] masterdukill:
Couldn't' find much working links on this forum, but i googled & found "PG86IMG_Shooter_Sprint_WWE_2.89.651.2_Radio_1.09.00.0706_signed.zip" on other forums. Renamed it, rebooted to bootloader & this phone is alive again! Thanks for the help
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] JasonPGz:
Hey hey I 'm new to this community. s4 have a i337 at & t but maybe you wanted to change your system or install a rom s6 possess something like android 4.4.2 could help me before hand
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] audit13:
I believe the AT&T s4 has a locked bootloader which limits the custom ROMs that can be installed on the phone. Have a look in the development forum to see what is compatible with your phone.
[Galaxy S6 Q&A, Help & Troubleshooting] tahleel:
I see that Cricket has the Samsung Galaxy S6 for $249.99 (along with the S5 for $199.99 and the S4 for $99.99). I am debating whether I should buy the Galaxy S6 or the Galaxy Alpha G850M (around $250 at Target after discounts). I've had quite a few Samsung phones (Galaxy Epic, Nexus, S3 and S4) and became tired of the same design language and cheap feeling plastic. The phones I've had in the past year (Moto G LTE, Padfone X and Amazon Fire Phone) have been great phones in their own rite, however, locked bootloaders and very minimal aftermarket support have made me want to go back to a phone that's more popular with aftermarket support (e.g. Cyanogenmod, Zeiss VR One headset and so on). I've played around with the Galaxy Alpha earlier this year, and I really do like the size and quality of it- however, the variant may have a locked bootloader and the Marshmallow update isn't planned as of yet. Phone size is a huge deal to me, as trying to hold larger phones have definitely caused hand cramps and I prefer something smaller (4.7" screen or less) for one handed use. I've also considered the One Plus X, however, the phone not having all the LTE bands for AT&T/Cricket has been a huge drawback for me.

With that being said, can anyone help me decide the following-

In my situation, would the Galaxy S6 or Galaxy Alpha be a better choice?

Does the Galaxy S6 from Cricket have an unlocked bootloader so I can flash Cyanongenmod in the future?

Thanks!
[Galaxy S6 Q&A, Help & Troubleshooting] Jr173:
No, the S6 does not have an unlocked bootloader, Samsung is notorious about keeping their phones locked.
[Galaxy S6 Q&A, Help & Troubleshooting] adelmundo:
Sprint and T-Mo versions have unlocked bootloaders. Sadly since this is a Cricket S6, and Cricket is owned by AT&T, this will have a locked bootloader. Also if you think AT&T are slow with updates, Cricket is even worse.
[Galaxy S6 Q&A, Help & Troubleshooting] hiko36:
To second this, I actually bought the unlocked US variant that was on sale on Amazon simply because the update issue on Cricket was so atrocious. Still sitting on 5.0.1 with no update time table in sight.
[Android Q&A, Help & Troubleshooting] gangbit:
is there any way to add keywords for my android game on playstore?
[Android Apps and Games] Christian Troy:
New version.
[Android Apps and Games] IgorPofiguKh:
4.2

And for 4.2?
[Android Apps and Games] Christian Troy:
It is not possible because the notification listener requires 4.3, and integrated notifications is one of the best things of this launcher imho
[Android Apps and Games] SysC0n:
This is what I want! Works on any android box?

Thanks for the launcher :)
[Android Apps and Games] losika12:
the link is broken
[Android Apps and Games] gorilla p:
I would recommend advertising this as a TV box launcher and keep developing on that niche. There are not nearly enough decent TV box launchers available. The one that Tronsmart uses is really good, but that's the only other one that I like. I didn't know what this was, but if people know its a TV box launcher they may be interested.
[Android Apps and Games] armagani:
Launcher look fantastic,but link is broken.Please, fix it
[Android Apps and Games] theplagueisback:
Can we get a new link or a mirror please?
[Android Apps and Games] SysC0n:
https://www.dropbox.com/s/0624shqztl3oxct/WeTekNewLauncher.rar?dl=0
[Nexus 6P Q&A, Help & Troubleshooting] DrekenShark:
I've noticed that 4K video recording seems to be capped at approximately 8 minutes. I've had 2 separate videos stop recording at this time. Has anyone else had this issue and is there a way to bypass it? I have plenty of space on my 64GB 6P, so it'd be great to take advantage of all that space. Is is a processor or heat related issue?
[Nexus 6P Q&A, Help & Troubleshooting] y2whisper:
I believe recording is always capped after 4gb (I think that's the limit might be 2). That's happened to me on previous devices when I try to record 1 hour at 1080p would have to remember to change it to 720p or lower. Not sure how to change that, especially without rooting.
[Nexus 6P Q&A, Help & Troubleshooting] jlgevo:
I have the same problem recording in 1080p I can only record for 5 to 7 minutes. I also am rooted, what can I do to record longer?
[Nexus 6P Q&A, Help & Troubleshooting] dbbolton2:
This just happened to me tonight at my daughter's Christmas concert. Quit after 8 min 50 secs. I am test driving a Note 5 and a Nexus 6p. Between this and the mic problems, there's a good chance I'll send the 6p back. I never had this issue with my iPhones, and can't speak to whether the Note would have done it. It's frustrating because I really would have liked to have it all on video.
[Nexus 6P Q&A, Help & Troubleshooting] y2whisper:
Likely both devices would have done something similar.. Iphones have in the past.
[Nexus 6P Q&A, Help & Troubleshooting] dbbolton2:
I decided to do a test. I set it to record and left it alone. It recorded about 31 minutes of video before shutting off. I'm wondering if the camera app quit or if I hit something accidentally during the recording. This may be a case of user error instead of an issue with the device.
[Nexus 6P Q&A, Help & Troubleshooting] y2whisper:
At 4k?
[Nexus 6P Q&A, Help & Troubleshooting] mikexilva:
Yesterday I also came across this limitation (8 minutoes in 4k video) with Nexus 6P camera but tried the Opencamera app (free) and it got past the 12minutes without problems (and it has more manual control for exposure, focus, bitrate) and after some testing with phone on a tripod I think I'm going to record my kid's X-mas party with bitrate of 20mbps because it uses half the space (I think default is 42mbps) and on a tripod it looks as good as default bitrate.

I've done another test with 20mbps and it stopped at 27mins and 4 seconds, I think file was already 4GB at this point, so maybe I could still get a longer recording time with 15mbps if needed (it is still pretty good quality for a tripod mounted camera)..

I'm not as happy with audio, I thought it was stereo but it's mono and I have the feeling that it is captured with MIC's facing wrong side of the phone... and at this point I have no time left for ordering external MIC's to test (but it should be mono as well, maybe better direction would give better quality in high frequencies - but that has to be next time). For now best option I think is selecting audio source to camcorder (I think it's the one that comes selected as default, but not the option called "default" and I did try to force stereo but file still gets mono audio but I hear high frequencies coming from rear MIC - not as bad as I thought) - I'd love to see an option to capture the audio from the 3 MIC's givving 3 channels audio (good to play on 5.1 systems using center, left and right speakers ;)
[Nexus 6P Q&A, Help & Troubleshooting] PaisanNYC:
Perhaps the flashable zip in the Nexus 6 forums to activate stereo recording would work on the 6P also?

http://xdaforums.com/nexus-6/general/mod-stereo-audio-recording-t3001680
[Nexus 6P Q&A, Help & Troubleshooting] explorer-10:
I just recorded a Christmas ugly sweater party video at work in 720p on my 6P, and it stopped after 8m30s
[Nexus 6P Q&A, Help & Troubleshooting] DrekenShark:
Still experiencing this problem. Anyone else? Has anyone stumbled upon a fix? Thanks!
[Nexus 6P Q&A, Help & Troubleshooting] PhoeniX7na:
I was looking into the 6p specifically for 4k video so it's good to know about this problem. Sorry I can't offer help though.
[Nexus 5X Q&A, Help & Troubleshooting] airglobe:
Hello,

I tried some camera apps (Cameringo+, aillis, and ProShot) which had a horizontal level indicator, but all the indicators did not indicate the true horizontal level. It seems that the built-in accelerometer is wrong. Is there any method to calibrate the wrong sensor?

Thanks,
[Nexus 5X Q&A, Help & Troubleshooting] mallna:
*push*

I have the same problem. I can't play racing games or use cardboard apps. Can anyone help?

best regards:D
[Nexus 5X Q&A, Help & Troubleshooting] Fif_:
I have the same problem.

More precisely, when I run the "GPS Status & Toolbox" app and the device is stationery, I get a non-zero rotation vector.

GPS Status shows a 3 degrees/second rotation, even when the device is still.

Since it's a brand new unit, I'm likely to return it to Goog.
[Nexus 5X Q&A, Help & Troubleshooting] yaoppp:
I have the same problem, but don't know any solution. Seems it's a common problem.
[Nexus 5X Q&A, Help & Troubleshooting] Fif_:
After further investigations, it seems like there is some calibration data that's not being read when the device boots.

If anyone has the same problem and has root, can you:

Post the contents of:

/persist/sensorcal.json

/data/misc/sensorcal_saved.json

Then turn off SELinux or patch the SELinux policy (SuperSU required) by either running:

setenforce 0

OR

supolicy --live 'allow sensortool devpts chr_file { read write getattr }' 'allow sensortool persist_sensortool_file file { write }'

Then run:

/vendor/bin/sensortool.bullhead -c gyro

while the phone is still. This will overwrite

/persist/sensorcal.json

.

And finally post the contents of

/persist/sensorcal.json

after this modification.

Your gyro should now be functioning correctly until the next reboot.

It looks like Nexus 5X "forgets" to read the calibration data upon boot.

The above procedure will force a recalibration and forces the sensor hub to use the new calibration data.

I'm looking at a way to load the calibration data into the sensor hub without having to recalibrate, but this may need some serious hacking.
[Nexus 5X Q&A, Help & Troubleshooting] yaoppp:
Thanks for your post. Inspired by what you said, I found the other guys and myself are having an miscalibrated accelerate sensor. And it's a little bit difficult to calibrate this sensor than the gyro, since a flat table is needed and the back of 5x is not flat (due to the camera).

P.S. can you post the undo command of this?

supolicy --live 'allow sensortool devpts chr_file { read write getattr }' 'allow sensortool persist_sensortool_file file { write }'
[Nexus 5X Q&A, Help & Troubleshooting] Fif_:
Rereading /persist/sensorcal.json without rebooting

The method therein allows you to edit /persist/sensorcal.json then have the on-board sensor re-read that file without having to reboot.

Requirements:

A Nexus 5X device (duh)

Busybox installed

Supersu installed

The attached bullhead-reread-sensor-calibration.zip file.

A root shell (either via ADB or with a Terminal app + su)

Instructions:

Unzip bullhead-reread-sensor-calibration.zip under /sdcard. This will create two new files:

bullhead-reread-sensor-calibration

sensortool-writewrap.so

After every change to /persist/sensorcal.json, run in your root shell:

sh /sdcard/bullhead-reread-sensor-calibration

. You should see:

supolicy v2.74 (ndk:arm64-v8a) - Copyright (C) 2014-2016 - Chainfire

Patching policy ...
(Android M policy compatibility mode)
-allow:sensortool:devpts:chr_file:read=ok
-allow:sensortool:devpts:chr_file:write=ok
-allow:sensortool:devpts:chr_file:getattr=ok
- Success
resetting target.
sensorhub said: 'Hello, world!'
sensorhub said: 'Found Bosch BMP280 Pressure/Temperature Sensor'
sensorhub said: 'Found Rohm RPR-0521 Proximity/ALS Sensor'
sensorhub said: 'Found Bosch BMI160 Accel/Gyro Sensor'

sensorhub said: 'init: 22 -2 -8, 22 -9 -73, 0.00, 1'

The numbers on the last line will be different for your device.

Your sensor hub's calibration data has been updated. Note that if you had an app actively reading from the sensors, since they were reset, you will need to quit the app and restart it.

Further notes:

The above script makes no permanent changes to your system (but temporarily alters your SELinux policy, a reboot will reset the policy to its secure default).

The script uses an interposition shared library (sensortool-writewrap.so) that was compiled with the Android NDK from the C file source attached. If you're just using this tool, there is no need to download the C file.
[Nexus 5X Q&A, Help & Troubleshooting] Fif_:
Good guide on how to calibrate your sensors manually.

This should help calibrating your sensor manually if you use the method above:

https://docs.google.com/document/d/14uwBu0R7Yv6bwl5Y7CE1vpFWetnSzgs-zt0GwOaDwIg/edit?pref=2&pli=1

If you don't want to go through the Excel route and exporting the data from the phone, the app "Sensor Kinetics Pro" has a low-pass filter option for all sensors.

You can check that your sensor readouts are as close as possible to zero after tweaking /persist/sensorcal.json as explained in the previous posts.
[Nexus 5X Q&A, Help & Troubleshooting] CazeW:
Just wanted to thank you for all these instructions. My accelerometer was 5 degrees off in landscape and while the calibration tool did manage to calibrate it correctly (these settings also stuck for me after reboot), it also calibrated the upright position off by 2 degrees. Some quick manual editing thanks to your method and I now have everything calibrated correctly. It was impossible to take a panorama in landscape before this, so I owe you a really big thank you!
[Nexus 5X Q&A, Help & Troubleshooting] Fif_:
Happy it was useful to someone.

I would have thought the problem was more widespread.
[Nexus 5X Q&A, Help & Troubleshooting] di3l:
Ok, I probably know the answer, but is there any chance to calibrate it without root permissions? Even if it resets after reboot. I have brand new phone without any scratches, I don't want to loose warranty and change it to a perfect shiny brick (at least not yet). I know my luck, it's gonna be just like that.

I've tried to force Google to admit, that this problem affects every (or almost every) single one Nexus 5X and they should at least add calibration option, because sending phone to the service takes time and isn't the best option. They gave me a standard answer to contact the service :good:

productforums.google.com/forum/?utm_medium=email&utm_source=footer#!topic/nexus/2Xkk3X4KvYQ;context-place=forum/nexus (I can't add link as link, I'm not a trusted user :) )
[Nexus 5X Q&A, Help & Troubleshooting] Fif_:
Yes, root is required.

However, you can unlock the bootloader, root, follow the instructions and calibrate, and then reimage the device and relock the bootloader.

You'll then have a calibrated stock device, which should be covered by the warranty.
[Nexus 5X Q&A, Help & Troubleshooting] udenfox:
Can You tell me which values did You edited? I have 5 degrees off in landscape too and just can't get right value. I think I actually has problem with accel sensor, not with gyroscope.

P.S. Seems like in Android 7.0 there is no /vendor/bin/sensortool.bullhead .

Instead in init.bullhead.sensorhub.rc I found it uses /system/bin/nanoapp_cmd which have little different format like

But it actually throws me an "Failed to open /dev/nanohub: err=13 [Permission denied]" error, even after I called both

Any ideas? Anyone tried that hack on Android 7.0 stock?
[Nexus 5X Q&A, Help & Troubleshooting] di3l:
I've just changed values in /persist/sensorcal.json. My tilt was almost 6 degrees and I knew that the y-axis is bad.

My origin values:

{
"accel": [
21,
-21,
-8
],
"gyro": [
-1,
-9,
-10
],
"proximity": 9
}

I've changed -21 to -31, then reboot and then i had almost 8 degrees error so it was a bad direction. I've changed it to 0 and now it is perfect.

Now my sensorcal.json loks like this:

{
"accel": [
21,
0,
-8
],
"gyro": [
-1,
-9,
-10
],
"proximity": 9
}

I'm on the stock rom again and it still works.

[MENTION=5297163]Fif_[/MENTION] I have no words to tell you how awesome you are. THANKS!
[Nexus 5X Q&A, Help & Troubleshooting] Fif_:
Just try to disable SELinux entirely with:

setenforce 0

and then run nanoapp_cmd.
[Nexus 5X Q&A, Help & Troubleshooting] udenfox:
This not works for me unfortunately.

But actually I did calibration by doing values bust.

As a result to compensate 5 degrees at the Y axis I've changed the value in the calibration json on 25 units.

Thanks for a solution! :good:
[Nexus 5X Q&A, Help & Troubleshooting] pacmanman:
Hi, thanks, this worked great.

It was tilted almost 7°

As a note I have to modify "accel" section, not "gyro".

{
"accel": [
27,
-8,
-4
],
"gyro": [
5,
7,
-10
],
"proximity": 8
}

Main post should be as permanent is 5x section :)

JP
[Nexus 5X Q&A, Help & Troubleshooting] giorgis91:
Hi guys, I have the same problem but only in landscape mode. For example if i take a pano in portrait the image is aligned well, while if i try to do it on landscape it's inclined on the right. Which value i have to change in that file?
[Nexus 5X Q&A, Help & Troubleshooting] Fif_:
Some people had to change the gyro section, others the accel section.

Please read the entire thread, make a backup of sensorcal.json, then try to run sensortool/nanoapp_cmd, see if that helps.
[Nexus 5X Q&A, Help & Troubleshooting] giorgis91:
Yeah sry i read all already but I'm new to this and I'm afraid of a brick

---------- Post added 8th November 2016 at 12:05 AM ---------- Previous post was 7th November 2016 at 11:05 PM ----------

How can I recover the original sensorcal.json with twrp recovery? I tried to use its filemanager but I cant find persist folder in it
[Nexus 5X Q&A, Help & Troubleshooting] Fif_:
Well, after checking, TWRP does not mount /persist by default, and it's not in the fstab. You can mount it by hand by running the terminal, then typing exactly (with all lowercase and respect the spacing):

mkdir /persist
mount /dev/block/platform/*/*/by-name/persist /persist

Alternately, instead of using the TWRP Terminal, you can connect the phone to a PC with adb installed, and run these from an adb shell on the PC.

You should then be able to use TWRP File Manager to copy/restore the /persist/sensorcal.json file.

You will have to reenter those commands every time you want to see/persist from TWRP.

Be careful with the SELinux contexts if you ever have to restore the file.

These three commands will restore all permissions:

chown root:system /persist/sensorcal.json
chmod 640 /persist/sensorcal.json
chcon u:object_r:persist_sensortool_file:s0 /persist/sensorcal.json
[Nexus 5X Q&A, Help & Troubleshooting] hapiik:
Hi, I've got a little problem here.

After running

sh /sdcard/bullhead-reread-sensor-calibration

I get:

supolicy v2.79 (ndk:arm64-v8a) - Copyright (C) 2014-2016 - Chainfire

Patching policy ...
-allow:sensortool:devpts:chr_file:read=ok
-allow:sensortool:devpts:chr_file:write=ok
-allow:sensortool:devpts:chr_file:getattr=ok
- Success
/sdcard/bullhead-reread-sensor-calibration[20]: /vendor/bin/sensortool.bullhead: not found

I am using pureNexus and there is indeed no file named sensortool.bullhead in /vendor/bin/

Also

ls -laR | grep sensortool.bullhead

in /sdcard returns nothing.

I didn't try the manual 'rebooting' way yet, I don't know if it will work without that file.

Is this guide supposed to work only with stock ROM, or have I missed something in the process?

Thanks for the answer.
[Nexus 5X Q&A, Help & Troubleshooting] Fif_:
If you're using a Nougat vendor image, a user reported in post #14 that sensortool had been replaced by another command.

At this point, you can either:

1. Modify the calibration file by hand, and reboot between every change instead of using the script to reread the calibration values.

-OR-

2. Try to flash and downgrade to the latest Marshmallow vendor image to use my script. An outdated vendor image may prevent Android from booting, so be prepared to restore from backup or reflash Nougat if anything goes wrong. You might as well flash Marshmallow, calibrate and then go back to Nougat after calibration.

You could also try copying just sensortool from the Marshmallow vendor image and run this one.
[Nexus 5X Q&A, Help & Troubleshooting] hapiik:
Oh, I am sorry I must have missed that post somehow.

Anyway, yes I am using the latest, 7.1.x. based one. First I disabled the SELinux with the

setenforce 0

and then edited that /vendor/bin/sensortool.bullhead file. I ended up with editing "accel" part, second number which was -27, to 0. Then launched

/system/bin/nanoapp_cmd calibrate gyro

with no errors. Restarted the Cardboard app and it worked!

However I noticed a little constant left-ish motion, in VR apps, when the phone is still on the table, which doesn't happen with original values in sensortool.bullhead. I don't know if it's something serious or not, but when I put the phone in cardboard and put it on head, the motion is no longer present. Maybe because of that constant motion in the air?

Thank you for the fix. This should be somewhere pinned as pacmanman said. Very useful!! :)
[Nexus 5X Q&A, Help & Troubleshooting] nongrata23:
Thank you so much, for me was enough to change that on nougat with root.