yashsingh1/xdaforums huggingface dataset:
[Samsung Gear S2] ffarber:
A couple of questions:

Do you get buzzed for the text messages? The notifications still come to the watch in DnD mode but should not cause a vibration.

Do you have the application Brrr installed? I use that for telling me if my watch got disconnected. It does not respect DnD mode.

Do you have the built-in bluetooth disconnect alert enabled? I have not tried that but it should respect DnD.

Hope that helps.

Fred
[Samsung Gear S2] rprussell:
Hey there Fred - thanks for the reply.

I did get buzzed for the text messages last night, which is what threw me. The little minus-sign-icon on the main watchface was there, indicating DnD mode.

I've never heard of Brrr, so no.

I just disabled that alert now, since I really don't care about it. It buzzes me as I walk around the house and yard. It's more annoying than useful. I hadn't thought to look for a setting for that until you mentioned it :eek:

It occurs to me to test the notification buzz again - so I just turned on DnD and sent myself a text... and of course it's nice and silent. I wonder what's going on?
[Samsung Gear S2] ffarber:
Possibly, the buzz you got was for a disconnect alert and the text message happened about the same time so that it was confusing. I use DnD a lot and find it works pretty well. It does let alarms through though.

Fred
[Samsung Gear S2] rprussell:
I'm planning on the alarm getting through, but most mornings would welcome the extra sleep :D

I turned off the bluetooth disconnect alert and last night was smooth. I have my fingers crossed!
[G4 Android Development] DaarkieDoo:
What's the pros of having a decrypted device? Is going to be smoother, faster or what?
[G4 Android Development] sirsomething:
+1 for this question
[G4 Android Development] Sztermel:
I'm curious what that technical talk means as well!
[G4 Android Development] ufocus:
It's good to see progress and interest for our device. Is it possible to add dt2w like op3 here and the date and time of nandroids fixed ?
[G4 Android Development] steadfasterX:
When you enable full device encryption in your favorite ROM or using stock without modification then your data partition is encrypted. That means no one can access your data when you shutdown your phone.

So in twrp you will see the data partition as a big 32gb unreadable partition even if 3GB are in use when you booted (and therefore decrypted) your ROM.

You CAN still backup that data partition but it will backup the whole 32GB because of encryption.

With this twrp version when started you will be asked for the decryption password and your data partition is readable as in the ROM. When you backup now the data partition it just backups the data in use so 3 GB instead of 32GB.

Regarding any pros of not using full disk encryption in your ROM I can say it doesn't matter in performance in normal cases. You will always read that disabling decryption will give you much more power and so on but the today's spec of phones are so good you will feel a slightly diff only. The ONLY way to find an answer is testing on your own using the SAME ROM and same version! Once with encryption once without.

On the other hand you will get a minimum of security if you enable it but give access to everyone finding your lost phone if not! So it's up to you if you want this risk for a minimum on performance improvement.

And just for sure:

decrypting in twrp is *not* permanent it is just decrypted for backing up nothing more nothing less.

Hope that answers your question

.
[G4 Android Development] steadfasterX:
I think that is possible without problems. I check that.

checked:

its not such easy as stated in your commit link. we do not have "touchpanel" there so we need to check what else we could choose maybe those: https://github.com/CyanogenMod/andr...mmit/d3c0189ab7384d42906eea9d521c4d591a160c2f

edit 2:

changing /sys/devices/virtual/input/lge_touch/tap2wake --> 1 (as set in CM) has no effect in twrp.. Need further research..

edit 3:

ok got it. double tap will be added in the next build :)

.
[G4 Android Development] albuntu:
How about the correct date and time? Is this also an easy one?
[G4 Android Development] steadfasterX:
no afaik this is a bug in twrp 3 as it was not a problem as in twrp 2 but I cannot say for sure.

Can you tell me what ROM do you use? and more important: When you reboot is the time correct (directly after reboot!) or is it not correct and gets corrected when connected to the carriers network?

.
[G4 Android Development] albuntu:
I'm on CM13 and yes, the time and date are always correct. I know for sure because i often reboot with flight mode enabled.
[G4 Android Development] ufocus:
Now that was fast :) Thank you! Appreciate the effort. For now we can live with wrong date and time it's not that big of a deal.
[G4 Android Development] HorstiG:
I do not understand the whole thing.

The incorrect date is for me a Problem.

Imperium Stock ROM

View attachment 3852244
[G4 Android Development] steadfasterX:
Please see the the comment of Dees_Troy and bigbiff (both main devs of TWRP):

https://github.com/TeamWin/Team-Win-Recovery-Project/issues/178#issuecomment-35728685

https://github.com/TeamWin/Team-Win-Recovery-Project/issues/238#issuecomment-28525937

--> Means the ROM have to save the time data and TWRP tries to read that. If the ROM do not save that time data TWRP can't know the time.

Well there is a flag for QCOM since some day:

https://github.com/TeamWin/android_...mits/8b9b9c5d869e57cb7857723592044028a8874f61

--> that one is set already in my build but it is still not working

I still looking through the code what the devs actually expecting maybe ... well lets see.

update:

ok so far I can say the following

The Qualcom Time Daemon (proprietary) need to be available in your ROM (e.g. not available in RR)

The time daemon has to run properly (it has to work actually)

The time daemon has to write into either /data/time/ats_* or /data/system/time/ats_*

If those are ok then TWRP will display the time correct. If not blame the ROM not TWRP..

.
[G4 Android Development] HorstiG:
I have 4 Files, but all without content.

It´s the same with Stock LG ROM (KTZ)

Have a look please

https://dl.dropboxusercontent.com/u/73964661/Time.zip

View attachment 3852395 View attachment 3852396
[G4 Android Development] HorstiG:
On my older Baby LG D290 :D the Time is OK

View attachment 3852403
[G4 Android Development] steadfasterX:
It may be not a device with RTC that would explain it. Or the time daemon in that rom works better/other.

The files are not empty so it should work for you afaik...

Which timezone do you live and can you join the twrp channel? That would make it easier for troubleshooting..

.
[G4 Android Development] HorstiG:
OT. Meine Zeitzone ist die gleiche als Deine. Bei TWRP G+ und xda habe nicht nur ich schon mehrmals das Problem angesprochen. Deshalb hatte ich etwas Hoffnung, dass Du...

Dann werde ich damit leben muessen.

Danke trotzdem und sorry for german
[G4 Android Development] steadfasterX:
ok no I meant IRC channel thats much much better because it is a chat so much more responsive

but I want to investigate that further (I mean my nick says it all) - can you do the following when booted into Android and paste their results:

ls -la /dev/rtc0 /dev/rtc

hwclock -uw (<-- if this gives you an error let me know but continue with the next part)

ls -la /dev/rtc0 /dev/rtc (again)

Boot up in TWRP and paste the results of:

ls -la /dev/rtc0 /dev/rtc

If it is not the correct time in UTC do the above hwclock command again

reboot recovery (so reboot into twrp again)

let me know your results

I'm normally online daily so grab an IRC client like hexchat or pidgin and connect to the channel #twrp. you will see me there. If you do not want to install anything simply use the webchat here: http://webchat.freenode.net/?channels=twrp

.
[G4 Android Development] kirby_hegner:
I like the 'If it isn' t broken, it can always be better" way.
[G4 Android Development] raptorddd:
it did not installed a rom for me h811 reverting back to official 3.02.0 i was able to flash rom. ?
[G4 Android Development] steadfasterX:
You can always go back ;)

Raptorddd this doesn't help anything. You do not tell which rom you do not tell which twrp version and most important: you do not provide the recovery log. This way no one can help you! :p

.
[G4 Android Development] steadfasterX:
really interesting: I tried your method and it works by just pressing vol up and power without releasing a single button :D cool :)

So if it do not work for you anymore I would try what you mentioned: just re-flash twrp image. You can do this while within twrp - just copy the twrp image to your device and when flashing make sure you click the "image" button at the bottom while in the menu "Install". Then select the twrp image and choose "recovery" partition as target.
[G4 Android Development] thewild:
Grrrr, still not working for me after reflashing 3.0.2-1 ! :mad:

Yeah I liked that option, really more straightforward than the other way.

Wouldn't this option be in the kernel rather than in the recovery ?

BTW, which ROM are you using ? I lost this functionality after flashing CM14.1 I believe.
[G4 Android Development] steadfasterX:
Yea I strongly believe that this activated in the kernel because the other way on reaching twrp is controlled by the bootloader.

I have made that key combo thing a while ago in a kernel for another device btw... Just hadn't remembered that yet ;)

So it seems you just have to flash another kernel ;) I think the llama kernel is available for CM14 as well. Try that one because I use the same kernel and its working for me (in RR - MM / CM 13).

I currently use RR (MM edition). I will wait some months and then switch to the RR - Nougat edition but stay on MM for the moment (I use that as my daily driver and need a stable ROM).

.
[G4 Android Development] steadfasterX:
The AMAZING and INCREDIBLE twrp BENCHMARK

Status

see http://xdaforums.com/g4/general/knowledge-amazing-incredible-twrp-t3509582 :D

.
[G4 Android Development] thewild:
Yeah I might give llama a try, but I'm getting lazy.

I was using stock cm13 kernel before and it worked fine, maybe they will implement this later. I'll ask in the cm14 thread.
[G4 Android Development] kessaras:
its super stable stable ;) rr remix **Android 7.1 rocks in everyway
[G4 Android Development] steadfasterX:
Well it's like with every new software release I wait a while before using it in productive. This way I drive best in the last years..
[G4 Android Development] genesixxbf3:
https://gerrit.twrp.me/#/c/1939/1 merge that please and update it
[G4 Android Development] steadfasterX:
Has to be done by bigbiff or dees troy.
[G4 Android Development] genesixxbf3:
but you can build with it no ?
[G4 Android Development] steadfasterX:
I prepare for the official build only. I request merges and the devs merge and build. I create beta builds on my own for testing.

.
[G4 Android Development] genesixxbf3:
this commit fix bootloop to recovery
[G4 Android Development] steadfasterX:
Sure I know.

I requested the merge 1 sec ago.

Edit

-----------

Merged.

New build will be released asap.

Edit 2

-------------

Reverted. That change alone is not enough or more worse it means it will factory reset instead of just opening twrp.
[G4 Android Development] DevUt:
There is a Tmp(abandoned) flag for this problem

What happens :

You enable /misc

The stock rom puts wipe script in that /misc folder

TWRP as usual and expected wipes it

jcadduono made a flag that make sures the script inside the /misc folder isnt executed.

But he abandoned it as he thought commenting out /misc would be enough.

But the commit can be still be found on the gerrit
[G4 Android Development] steadfasterX:
/misc is disabled atm.

AOSP and therefore CM writing into /misc partition because of a recent change in AOSP.

When doing the hardware key combo with enabled(!) /misc partition it results in a factory reset - that's the reason why I do not want to add /misc atm.

I searched for such a "flag" but not able to find what you mean. Could you share the commit?
[G4 Android Development] draymond1987:
I'm sorry if this is a really noob question, which it is LOL. I can't seem to get F2FS on my T-mobile LG G4. I flashed the unoffical TWRP (that was outdated), but it would not change /data or /cache to F2FS. I tried to flash the official TWRP in this thread, but when I flash a h811, I get an error that this device is an h815, not h811. So I am currently just running the official build of TWRP for my device. I tried following the guide and google'd before asking on this thread. Every time when I changed filesystem and swiped, it would delete everything, but it would still show me that I have EXT4. I flashed the TWRP image while I was on an CM based ROM, if this matters. Thanks so much for any help!!
[G4 Android Development] kessaras:
you downloaded and flashed what exactly ? the twrp here is updated just recently (i saw it in another thread) and for h811 will soon be ready. did you flash the twrp for h815 ? the name of the zip you flashed had in the name the device h815.... we must be careful what we install , we can't just download and install any random file we see on the screen.

anyway https://dl.twrp.me/h811/ see the link ? h811. see the file name ? h811. if you flash for h815 then it will work but it will think your phone is a h815
[G4 Android Development] steadfasterX:
There are checks within most of the ROM zips that will check for the product model before the installation starts..

e.g .when you download CM for h811 it expects a h811 which is currently not the case in this twrp version. I saw this bug today because of another problem I was trying to solve.

I've addressed this in a new build already and will release it tomorrow as a BETA for the upcoming 3.0.2-2.

As I unify both the h811 and h815 builds currently that also means checks between h811 and h815 will not be possible anymore in TWRP. They will be both identified as just g4.

EDIT: oops that should be possible :) sorry for confusing I'm still learning every day new things since years so.. it should still work to have those both 2 identified as separate devices!

CM installer checks for "g4", too but I have to check some of the other ROMs what they check. At the end they MAY have to change things within their installer but that needs to checked.

Let me know which exact ROM and version you're trying to install and double check if h811 or h815 is the right one for you.

All this is important because:

If a user downloads and installs a h811 version on a h815 or vice versa it will NOT install currently but in the next version it WILL.

If a user tries to install a g5 or Samsung s7 ROM or whatever it will still fail as it should. Just between h811 and h815 it will not differ anymore.

EDIT: oops that should be possible :) sorry for confusing I'm still learning every day new things since years so.. it should still work to have those both 2 identified as separate devices!

You should always check if you download the correct version!

The above check is just there for the ppl not able to read and think.

Checking for a g4 is still possible and prevents bricking the device but ROM installer has to check for it that way.

Bottom line:

I will release a new beta soon which let h811 users install ROMs again (as long as the ROM installer checks for a g4)

.
[G4 Android Development] draymond1987:
Thank you for the explanation of this! Look, I'm not new to Android, but I have been away for awhile. I came across a post on T-mobile's G4, that it was safe to actually flash the h815 image. Obviously, I learned from that mistake when I couldn't flash AICP, I think it was, and I flashed back to the official TWRP. I do have a T-Mobile LG G4, and I actually had troubles with dual boot patcher, because (before I told the dev) ROMs thought I was using H815, after patching.

I actually DID get the unoffical TWRP to work (F2FS). The first issue was that I checked "rm -rf instead of formatting" . As soon as I unchecked it, I was able to convert. Then I forgot about needing a F2FS supported kernel, so I flashed Llama and am currently fine on ResRemix (Nougat). I haven't tried multiboot again, since changing my filesystem, but that's got nothing to do with your recovery or thread. Obviously, I tried everything and am asking for support on that thread, but I'll just stick to backing up and flashing a new ROM.

Again, it was my mistake, and thought it was fine to use the updated TWRP on my T-mobile LG G4, but I know now, to wait until it's built. Thanks by the way! I will certainly test it out, when it drops.
[G4 Android Development] marn3us:
I know this is not the right place to ask this question (I'm sorry [MENTION=5545101]steadfasterX[/MENTION] :angel: ) but did you manage to change file system to F2FS on Nougat? Did you use any particular tricks or just regular procedure?

I'm asking because I'd love to try f2fs on my 7.1 ROM but if I'm not mistaken I remember [MENTION=5776465]genesixxbf3[/MENTION] saying that N is not yet behaving properly with F2FS.

Thanks in advance :)
[G4 Android Development] draymond1987:
I used the method on this forum/link: http://xdaforums.com/g4/development/kernel-minamo-g4-kernel-t3385658

I definitely am running F2FS on /data and /cache partitions. It states that /system isn't supported, because you can't mount it. But yeah, on that version of TWRP, I only changed the screen off setting, and left everything default. Make sure to flash a F2FS supported kernel, or it will not boot! Trust me, I waited and waited. When I flash any ROM, I wipe dalik/cache because my phone is just picky and will sometimes hang. This is AFTER wiping and installing. It will wipe your internal storage!! :)

T-mobile H811 running ResRemix 7.1 right now, converted to F2FS on /data and /cache.

EDIT: You can check if it is F2FS after following the guide, by going into advanced wipe...change file system. It will tell you if it's EXT4 or not.
[G4 Android Development] raptorddd:
was it me who said h815 could be use.? last time i did it didnt worked. i know steady asked for logs but, didnt have the time to take logs i needed phone asap.

http://xdaforums.com/showpost.php?p=69790666&postcount=175
[G4 Android Development] draymond1987:
No, it wasn't you. If I do some looking, I could find the exact quote, but I think it will prove nothing. Obviously I should have known better :P

I take full responsible for my noob mistake, which I'm glad didn't end with a brick LOL.

Edit: http://xdaforums.com/g4/development/rom-cyanogenmod-13-0-lg-g4-t3477475/page174

post #1732
[G4 Android Development] kessaras:
oups ! haha. i read it too,

but somewhere else i saw that it works but you cant flash rom. its not your fault too.

its just that the discussion takes place here and there (everywhere) so you can't really know for sure anything. you have to be a magician to find all the clues around. you are a "demigod" only for reading so many pages and searching so much. most people would only watch the op and a couple of pages around it.
[G4 Android Development] steadfasterX:
That's totally true.

If ppl write in a ROM thread that they can't use TWRP for flashing how should I get knowledge of that?

tbh we tested backup & restore but doing a simply flash of a ROM was out our my mind :( shame on us :(

I wonder why the persons knowing about a TWRP problem do not post it here in the official thread but in others they are able to do so.

I haven't the time to look all posts around to find issues in other threads.

All ppl want and demand but no one will test or publish logs on issues.

well nvm. That's the way it is :p

Cheers

EDIT:

sorry for confusing I'm still learning every day new things since years so.. it should still work to have those both 2 identified as separate devices!

This may delay the release of the BETA..

.
[G4 Android Development] draymond1987:
That's so true! I mean, I used to have other devices on T-mobile, but it always seemed that "International" versions of the device had more support. For example, the HTC M8 had more ROMs on the "international" side, that could be flashed on T-mobile variants! But there was also some developers that would post ONLY T-mobile, so you can see where confuse can hit LOL. I feel there's more H811/H818 AOSP/CM based ROMS on this side of the fence. So when I seen a T-mobile post stating that you can flash the recovery, I was like "oh, sweet! I thought recoveries were different, but I guess not." Obviously, I was wrong aha. I will admit that I can be flash happy, even after reading a lot! I can understand why you asked what I flashed.

---------- Post added at 07:14 PM ---------- Previous post was at 06:49 PM ----------

Side note to anybody who wants to convert to F2FS, and I'm sorry because this isn't the thread (but somebody asked). It seems both ROM and kernel need support! I flashed back to stock rooted, flashed a F2FS kernel and the device refused to boot past the bootloader screen! Like I said, I am flash happy, but I know how to recover (I'm not a total newb, I think LOL!!) All you have to do is covert back to EXT4 and you'll be fine again. I apologize because I thought it was JUST the kernel !

Anyways, I can't wait to test the beta! Have a great day, everybody!
[G4 Android Development] steadfasterX:
Sure international models means more devs so better support ;)

The beta is almost ready I was able to fix the main issues for the device model detection now (in about 56 build tests)..

Nevertheless I have to cleanup some debugging stuff before actually can release it so sorry for the delay but this will take some more time.

The good is that it will come and whenever I build a new release for the h815 it will produce a h811 build as well.

Stay tuned.

:eek:
[G4 Android Development] XeniX_Force:
Thanks so much for your hard work.
[G4 Android Development] steadfasterX:
Can anyone confirm or decline if the CM internal updater works in 3.0.2.0?

It does not work in 3.0.2.1 but I fixed this in the new beta as well so I just wanna know if that ever works before or gets broken in 3.0.2.1..

Update:

----------------

Ok I tested to update with twrp 3.0.2.0 but it was not possible to use the internal cmupdater to upgrade CM.

Good because that means 3.0.2.1 hadn't broken anything and good because I was able to fix that as a side effect of other problems solved.

The bad: unifying the devices breaks that fix I made.. Lol. Funny isn't it? So if I do not unify (means hard coding the device model) the cmupdater works but when unify (means detect model from ROM) not.

The reason lys in the upgrade process itself plus the loading of proper props. I get a permission denied of mounting /system when the upgrade starts in twrp.

To unify I load system build props which needs to mount /system before that. If I do so the mount of cmupdater fails then even when unmounting after loading the props. I think the reason is because I use mount_all fstab and that may prevent unmounting or something similar.

Please understand that I want to provide quality even it will be a beta so the release will delay more.

.