yashsingh1/xdaforums huggingface dataset:
[Moto 360] :
Bottom line is regardless of any settings, and regardless of any process done, my screen is still faintly illuminated black when docked, no matter what.
[Moto 360] raduque:
You tried Enabling "Stay Awake when Charging" in the Dev options? I just did it (Uninstalled Slumber too) and the results are my screen is completely off.

I just took a picture with my Canon in a pitch black room, but all you can see is my S6's charging LED, so that's pretty worthless.
[Moto 360] marctronixx:
and to piggy back off the previous post,

the watch i use goes completely dark. i even posted a video earlier in this thread to try to show this.

im not doing anything different. there is still the bug that shows where the charging time does not update even though the watch is charging/charged but i dont care about that...
[Moto 360] xuser:
I tried that last night (Enabling "Stay Awake when Charging" in the Dev options) and the screen did turn off, go completely black. But after a few minutes it turned back on to that dark grey theater mode. I tried to put my phone into airplane mode to stop all communication and the watch still turned back on to theater mode. I'm on the August update software.
[Moto 360] MikusP:
Tried exactly the same method with the same results. This has to be a bug in the firmware. I've only had the watch two days and already this is bugging me. Hope they get it fixed..!
[Moto 360] albie999:
Did anyone find a good fix to this. I have had my watch a few days, am on 5.1.1 (latest), and it was going totally black for the first few days when on charge, but last night the backlight started to come on after 15 odd seconds after I had double tapped the button to turn the screen off when charging. Not sure why all of a sudden it would change?
[Moto 360] :
Never got it working, despite argument with some people here that think this bug doesn't exist.
[Moto 360] albie999:
I have factory reset my watch, and set it up again (just like I did when I first had it), and the backlight is still coming on after around 15 seconds, after double tapping the power button. The first few days, it stayed dark all night and then suddenly started coming on ... really weird.
[Moto 360] :
Yep. I've never been able to get it to stay off, no matter what settings used.
[Moto 360] albie999:
What I don't understand is why for the first few days it was switching off completely ... Annoying much
[Moto 360] aftnoon2:
Don't wait for a fix.

My experience with Motorola Droid 1, back on Froyo era, is very negative, sorry.

And we know that Google is very resilient to recognize its own bugs.

Hope that 360 2nd generation be a better smart watch than the 1st.

Otherwise, hope that some devs take care of this object.
[Moto 360] 92lleo:
This is way too complicated :) Just use the crown double press feature - it will set the watch to cinema mode, press again to disable.

1st: Place watch on dock, wait till it shows charging screen

2nd: Double press crown, -done
[Moto 360] :
And that doesn't work for everyone including myself. After a few seconds it will go back to lightly illuminated display.
[Moto 360] 92lleo:
Didn't know that, sorry
[Moto 360] :
I actually stopped using the device, was making my wrist hurt. :)
[Moto 360] jkcz:
Hey guys it seems that there actually is an option for this but the button text is incorrect. Enable developer options then the first setting in the menu is called "Stay awake when charging". I had it disabled because I thought that would be the logically correct choice but it seems that when this option is ENABLED the screen actually goes off after a few seconds and stays off until you wake the watch! Let me know if it works on other watches or only on mine.
[Moto 360] vivebatu:
Works for me too!! (Took me 8 months to discover your post)
[Moto 360] thegoodboy66:
It worked for me too! Thanks for sharing this!
[T-Mobile Galaxy Note 4 Original Android Developmen] bigbiff:
[RECOVERY] TWRP 3.2.0-0 - TeamWin Recovery Project

TeamWin is proud to present 3.2.0-0 for the Samsung Galaxy Note 4 (T-Mobile)!

Youtube video: http://www.youtube.com/watch?v=RIvWVS_Rkxo

Full TeamWin credits are on the TWRP page on the TeamWin website: http://teamw.in/project/twrp2

Introduction:

Team Win Recovery Project or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.

Key Features:

Touchscreen driven with real buttons and drag-to-scroll

XML-based GUI that allows full customization of the layout true theming!

Settings are saved to the sdcard and persist through reboots

Ability to choose which partitions to back up and which to restore

Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)

Onscreen keyboard

Decryption of /data

Easy selection of internal/external storage

See changelog below for new features

In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe cache & dalvik, and run a backup.

We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.

Source Code:

GitHub - https://github.com/omnirom/android_bootable_recovery

Gerrit for TWRP Official Device Configs - http://gerrit.twrp.me

Gerrit Instance - http://gerrit.omnirom.org

If you have made your own twrp build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.

trltetmo Device Config: https://github.com/TeamWin/android_device_samsung_trltetmo

Kernel: https://github.com/bigbiff/android_kernel_samsung_trlte

DOWNLOAD:

All official devices are listed at the top of the page on the Team Win website. Search for the device in the textbox.

http://twrp.me

Support:

Click http://webchat.freenode.net/?channels=twrp for live support or join us in #twrp on Freenode IRC servers
[T-Mobile Galaxy Note 4 Original Android Developmen] bigbiff:
reserved2
[T-Mobile Galaxy Note 4 Original Android Developmen] bugzy113:
Very nice... You guys rock
[T-Mobile Galaxy Note 4 Original Android Developmen] VeNuMuS:
We appreciate your work big biff. Thank you
[T-Mobile Galaxy Note 4 Original Android Developmen] bstapley:
Woot! So excited. Thanks all who helped bring this to the Note 4!

Successfully made a backup. Bring on the custom ROMs!
[T-Mobile Galaxy Note 4 Original Android Developmen] Nihonno:
Flashed in. Works perfectly. Year after Year. Phone and phone. Thanks.
[T-Mobile Galaxy Note 4 Original Android Developmen] twistedumbrella:
Didn't you have the device configuration on your github?

I sent you a pull request to fix it up for the Sprint version, but it looks like the repo got deleted instead.
[T-Mobile Galaxy Note 4 Original Android Developmen] bigbiff:
Soonerish.
[T-Mobile Galaxy Note 4 Original Android Developmen] siraltus:
Thank you!!!!

BTW, screen timeout does not work properly. It dims once, then dims again even darker when the timeout elapses, but never turns off completely like it does on other phones. Not good on an AMOLED screen that can get burned in.

Log attached.
[T-Mobile Galaxy Note 4 Original Android Developmen] ndtemple417:
thanks bigbiff and team I really appreciate the time put in on this hopefully you'll continue work as ive seen at least it looks that you may not continue as it wasnt supposed to be our yet thanks for all your teams time
[T-Mobile Galaxy Note 4 Original Android Developmen] arrogantS3:
Thanks OP, working great. via odin install.
[T-Mobile Galaxy Note 4 Original Android Developmen] twistedumbrella:
Soonerish? You have a time machine?
[T-Mobile Galaxy Note 4 Original Android Developmen] blacklabel2020:
We got it working
[T-Mobile Galaxy Note 4 Original Android Developmen] siraltus:
Also, ADB Sideload doesn't work - adb does not see the phone when in sideload mode ("adb devices" returns nothing), but it sees it just fine when in not in sideload mode ("adb devices" returns "recovery").

Second log attached.
[T-Mobile Galaxy Note 4 Original Android Developmen] siraltus:
Great, thank you! Does this mean there will be a new build? Can you look at the adb sideload problem too?
[T-Mobile Galaxy Note 4 Original Android Developmen] chakra:
Great job BigBif!
[T-Mobile Galaxy Note 4 Original Android Developmen] raw2000j:
Thanks great work btw these themes work if anyone uses themes

http://xdaforums.com/lg-g3/themes-apps/theme-holofied-twrp-2-7-x-x-t2845196
[T-Mobile Galaxy Note 4 Original Android Developmen] BeauSmith:
If my provider is Us Cellular, would either the T-Mobile version or Sprint work for me?
[T-Mobile Galaxy Note 4 Original Android Developmen] mike28:
Thanks sir for this
[T-Mobile Galaxy Note 4 Original Android Developmen] scrubsja:
Bigbiff I do not see any options for filesystem repair in the GUI. The filesystems to repair are those of the target and source correct?
[T-Mobile Galaxy Note 4 Original Android Developmen] bigbiff:
They should be under advanced in the mount page.
[T-Mobile Galaxy Note 4 Original Android Developmen] phaze1:
system bin sdcard.backup error

Dont know why but I couldn't just let it go and reflash. Something told me that because it was fine before as far as flashing it must be something else. I did some digging on the "/system/bin/sdcard.backup" file and figured out (after some considerable work) that a rooted program called Folder Mount was causing the problem. It seems it makes a backup then creates its own modified sdcard file which for some reason corrupted the bin folder. So I used TWRP, mounted the system folder, then used TWRP to clean dalvic and cache then formatted the system folder. I then dirty flashed Firekat rom and rebooted to system. Booted fine with most everything intact. I then tested out backing up using TWRP and successfully made a backup of the now working rom. Just figured I would post this solution if anyone ever needed it.
[T-Mobile Galaxy Note 4 Original Android Developmen] YourCancer01:
Just wanted to verify this worked prefect thank you for the solution!
[T-Mobile Galaxy Note 4 Original Android Developmen] paranoid android85:
I accidentally wiped my sd card in twrp and now I'm having trouble downloading from a lot of apps. How can I fix this? Would I have to Odin back to a stock firmware to get it back to where it was? Titanium back up and other apps say I have insufficient space, but I know I have a good amount. I reflashed the ROM I've been on and started fresh, but I'm still having issues. Thanks in advanced.
[T-Mobile Galaxy Note 4 Original Android Developmen] freakyd9984:
OK so I updated my baseband and boot loader what will this exactly do for me I'm running DYNAMIC 3.0
[T-Mobile Galaxy Note 4 Original Android Developmen] psycho4us4:
I wonder if [MENTION=3105374]bri315317[/MENTION] can add support for custom background wallpapers like you have in that screen shot?
[T-Mobile Galaxy Note 4 Original Android Developmen] bigbiff:
Please try in android terminal as root: restorecon -Rv /data
[T-Mobile Galaxy Note 4 Original Android Developmen] d@rklink:
After some testing, I think this might actually be a driver related issue. I tried using the above link and the device was not even recognized when connected to my laptop while in recovery. I once more flashed the .tar image from the TWRP download site and when I connected the device to my computer, it was recognized briefly. When attempting to copy a file to the external SD card I received an error, so I decided to try and copy the file to the phone storage. Windows Explorer froze for a moment and then the phone was no longer recognized.

When I go to device manager, I see a device listed as "trlte" and it shows that the device has stopped. I tried to disconnect and reconnect the phone and the "trlte" device did not show back up. Disconnected and reconnected one last time and once more the "trlte" device showed up, but still with an error. When I attempt to update drivers, Windows reports that the best driver is already installed. Is there a specific driver that I need?
[T-Mobile Galaxy Note 4 Original Android Developmen] bigbiff:
Windows uses a default MTP driver for all devices that are registered as an MTP device. With the test build can you please do the debugging steps and post the log again?
[T-Mobile Galaxy Note 4 Original Android Developmen] mandog202:
I'm having the same issue, and don't have an advanced option on the mount page

Edit: found it, its under wipe, not mount, ran it and it fixed my problem
[T-Mobile Galaxy Note 4 Original Android Developmen] d@rklink:
I flashed the test build through adb shell and when I reboot into recovery, whether MTP is enabled or disabled, the device is not recognized. When I run adb devices, no devices show as attached to the computer so I can't run debugging or try to copy anything over. To flash the test build (since it is just a zipped .img file), I extract the recovery.img file to my adb folder. I connect the phone and run adb shell then su. Next I run "dd if=/sdcard/recovery.img of=dev/block/platform/msm_sdcc.1/by-name/recovery" and I get a successful message. Maybe I'm not doing something right to flash?

EDIT: Never mind. In the time it took me to write the above, adb finally recognizes the device as "recovery" while in TWRP. I will start debugging and post updated log once complete.

EDIT EDIT: Okay..... maybe I spoke too soon. When I run adb devices, the phone shows as attached "recovery". However, the device is not showing up in Windows Explorer. I was able to run the start debugging command, but I have no way of pulling up the device in Windows to attempt to copy a file to.
[T-Mobile Galaxy Note 4 Original Android Developmen] bigbiff:
Sorry for telling you the wrong page.
[T-Mobile Galaxy Note 4 Original Android Developmen] thatotherguy..:
My vibrate doesn't work in twrp? Anyone else having same problem
[T-Mobile Galaxy Note 4 Original Android Developmen] bigbiff:
Can you pull /tmp/recovery.log?
[T-Mobile Galaxy Note 4 Original Android Developmen] Closed Source Project:
When ever I try to flash iBASTID's ROM (the Rapture one) I am getting an error: "error executing updater binary in zip". I tried installing the ROM (downloaded multiple times) off of my SD and Internal storages with the same error.

Anyone else getting this or have a solution? I googled the error and everyone is blaming the recovery. Unfortunately, we don't have CWM for me to test this... Thanks.
[T-Mobile Galaxy Note 4 Original Android Developmen] bigbiff:
Post /tmp/recovery.log
[T-Mobile Galaxy Note 4 Original Android Developmen] billb23ok:
I was wondering if anyone could help me?

I am trying to get the n910t to be f2fs compatible. I was told to change the zimage from a f2fs compatible kernel boot.img. with the one in the recovery.img

I am able to format to f2fs but after i try to wipe it I get an error unable to mount cache partition. And disk info can't see the cache partition after the phone boots up. Any help would be appreciated.

Twrp with changed zimage flash able zip: https://www.dropbox.com/s/lvc3hpne4691414/openrecovery-twrp-2.8.1.1-trltetmo.zip?dl=0

Recovery log: https://www.dropbox.com/s/fmnxlroeqtbifjs/recovery.log?dl=0
[T-Mobile Galaxy Note 4 Original Android Developmen] twistedumbrella:
You also need either a secondary (or with TWRP, a third) fstab for f2fs or something in the init.rc to choose. In leanKernel, this is how he did it -> https://github.com/imoseyon/leanKer...4bb4a65f758b23a/lk.ramdisk/init.target.rc#L54
[T-Mobile Galaxy Note 4 Original Android Developmen] billb23ok:
A little confused but i did find the init.rc file i guess i need to now learn how to decompile and recompile or something as windows vista cant open any file that i unpacked.

I will figure it out, but not tonight. Tks for the lead
[T-Mobile Galaxy Note 4 Original Android Developmen] twistedumbrella:
This should pretty much do all the heavy lifting: http://xdaforums.com/showthread.php?t=2073775

Let me grab the one you posted and repack it with that part. At least it'll be something to test.
[T-Mobile Galaxy Note 4 Original Android Developmen] billb23ok:
That's the kitchen I used, and tks again
[T-Mobile Galaxy Note 4 Original Android Developmen] twistedumbrella:
No problem. Seems I need to update mine. I lose the ramdisk on the unpack. Always fun trying to find an update or having to build the source of everything. Cost of running it on MacOS, I guess.
[T-Mobile Galaxy Note 4 Original Android Developmen] bigbiff:
Would someone be able to test if http://techerrata.com/bigbiff/openrecovery-twrp-2.8.2.0-trltetmo.zip boots properly? Make sure you can odin back to a previous version of TWRP if it doesn't work. If it doesn't work, please check adb and if it works post /tmp/recovery.log

If you have any questions let me know.
[T-Mobile Galaxy Note 4 Original Android Developmen] billb23ok:
yes it boots just flashed it with twrp manager

log: https://www.dropbox.com/s/g62p22ia9xhhiso/recovery2.log?dl=0
[T-Mobile Galaxy Note 4 Original Android Developmen] bigbiff:
Please get the results from getenforce in twrp terminal.
[T-Mobile Galaxy Note 4 Original Android Developmen] billb23ok:
I thought it worked but after going back in i noticed nothing changed. I tried flashing from internal and external and i got failed. I still have that log above I am work so no computer near me

also how do I get the results using twrp terminal?

I am putting another log cause I don't think the other one got the install using twrp manager so I installed it again and got a log

https://www.dropbox.com/s/h4oq2dh6zkfzdfp/recovery3.log?dl=0
[T-Mobile Galaxy Note 4 Original Android Developmen] bigbiff:
That's an older log. When you say nothing changed what do you mean? TWRP isn't crashing though right? Please get the log from the TWRP session of the test image.
[T-Mobile Galaxy Note 4 Original Android Developmen] billb23ok:
The test imag fails on install
[T-Mobile Galaxy Note 4 Original Android Developmen] bigbiff:
Can you try http://techerrata.com/bigbiff/openrecovery-twrp-2.8.2.0-trltetmo.img.tar in Odin?
[T-Mobile Galaxy Note 4 Original Android Developmen] billb23ok:
Ok in a bit i will use the managers computer lol

---------- Post added at 11:43 AM ---------- Previous post was at 11:35 AM ----------

I flashed recovery.img wih rashr

2.8.2.0 boots fine

https://www.dropbox.com/s/lt9l2x2e0i1lvy6/recovery4.log?dl=0

---------- Post added at 12:09 PM ---------- Previous post was at 11:43 AM ----------

OK so I typed getenforce in twrp terminal

came back as permissive

log: https://www.dropbox.com/s/d017250optvpivy/recovery5.log?dl=0
[T-Mobile Galaxy Note 4 Original Android Developmen] thatotherguy..:
Bump
[T-Mobile Galaxy Note 4 Original Android Developmen] bigbiff:
Samsung changed the way vibrate works. A new method would need to be developed for TWRP to work with it.
[T-Mobile Galaxy Note 4 Original Android Developmen] siraltus:
Are we getting a build of 2.8.3.0? Android Police reports it dropped today, but I don't see it on the TWRP website yet (http://www.techerrata.com/browse/twrp2/trltetmo), only 2.8.1.1.

http://www.androidpolice.com/2014/1...rows-in-moto-g-2014-support-for-good-measure/
[T-Mobile Galaxy Note 4 Original Android Developmen] psycho4us4:
That was the international version that got that update. Not our devices.
[T-Mobile Galaxy Note 4 Original Android Developmen] psycho4us4:
You get that f2fs problem handled yet? Is twrp going to be full f2fs compatible soon?
[T-Mobile Galaxy Note 4 Original Android Developmen] gforceriders:
2.8.3.0 is up. Go get it.
[T-Mobile Galaxy Note 4 Original Android Developmen] sino8r:
site is down. anyone mind posting theirs?
[T-Mobile Galaxy Note 4 Original Android Developmen] paranoid android85:
I used flashify to update it.
[T-Mobile Galaxy Note 4 Original Android Developmen] sino8r:
site is back up! must have been maintenance issues.

Strange... Wouldn't flash via recovery. Had to use odin. Oh well. All seems good so far!
[T-Mobile Galaxy Note 4 Original Android Developmen] bigbiff:
Not yet.
[T-Mobile Galaxy Note 4 Original Android Developmen] bigbiff:
What error did you get flashing the zip?
[T-Mobile Galaxy Note 4 Original Android Developmen] sino8r:
I didn't check the log. Just said flash failed. The md5 matched though. I didn't try it but twice before going to odin. Was busy at work. Wish I could be more help. Did grab it from the mirror though if that helps.
[T-Mobile Galaxy Note 4 Original Android Developmen] psycho4us4:
So what's new in this version? Do you have a link to a change log?
[T-Mobile Galaxy Note 4 Original Android Developmen] bigbiff:
I will update OPs at some point. Official changelog is at teamw.in
[T-Mobile Galaxy Note 4 Original Android Developmen] bigbiff:
If you could pull /tmp/recovery.log after the install and attach it for debugging I would be grateful.
[T-Mobile Galaxy Note 4 Original Android Developmen] siraltus:
Mine also failed when flashing the ZIP, had to use ODIN. Log attached.
[T-Mobile Galaxy Note 4 Original Android Developmen] billb23ok:
The zip only contains recovery.img that's why it don't flash. Use Rashr to flash .img to recovery if your not close to a computer.

https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools

And it seems no f2fs yet.
[T-Mobile Galaxy Note 4 Original Android Developmen] psycho4us4:
[MENTION=2638973]bigbiff[/MENTION] , here's the META-INF that was left out. I just pulled it from the previous version.

Just incase you need it. I already flashed it with this meta-inf and it's successful so. Human error. It's cool. Thanks for the update.

https://www.dropbox.com/s/i7r4osohky0b6an/META-INF.zip?dl=0
[T-Mobile Galaxy Note 4 Original Android Developmen] Greenarcher707:
Can we just boot into this recovery instead of flashing it? does fastboot commands work? ie: fastboot boot recovery.img
[T-Mobile Galaxy Note 4 Original Android Developmen] manbat:
I do not think Samsung phones have "traditional fastboot"....Samsung has Download mode. Try it and let us know. I used to do it all the time on my HTC phones...lol.

Sent from my SM-N910V / VZW Note 4 DE / Factory Bootloader Unlocked / Rooted / StarKissed / TWRP 2.8.3.0 trltevzw
[T-Mobile Galaxy Note 4 Original Android Developmen] Greenarcher707:
I'll give it a shot. I think it was like that using root de la vega where it would boot into custom recovery and not actually install. A pain but for people who didn't want knox tripped it was a must.
[T-Mobile Galaxy Note 4 Original Android Developmen] sino8r:
Makes sense! Thanks psycho!
[T-Mobile Galaxy Note 4 Original Android Developmen] Misterjunky:
re: backup freezes

Since I flashed twrp 2.8.3.0 yesterday I must have done at least four nandroid

backups due to testing roms and the backups I made never had any issues.

I cannot say why you are having that freezing issue unless you have something wrong

with your sdcard, you might want to backup your sdcard to computer and reformat it.

What I can say is that the new version 2.8.3.0 twrp has nothing to do with your nandroid

backup freezing when trying to backup your data.

Good luck and have a merry happy Christmas.
[T-Mobile Galaxy Note 4 Original Android Developmen] luv2vexx:
Not backing up

Hi

I flashed 2.8.3. I went into recovery and tried to do a nandroid backup but every time it starts to backup it phone restarts and goes to recovery again. Im i doing something wrong?

Note 4 - uk version on EE

SM-N910F
[T-Mobile Galaxy Note 4 Original Android Developmen] bigbiff:
Please describe your actions and detail and provide /tmp/recovery.log for debugging.