yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Android Development] Phil3759:
big thanks, so it is the way google implemented the qcom drivers

[MENTION=2872010]rootSU[/MENTION]

Can you compile new version with libtouch updated to 1.11?

It should allow the daemon when using /data/system/time
[Nexus 5 Android Development] Unb0rn:
Great news we won't have to symlink or copy anything :)

Thank you!
[Nexus 5 Android Development] danarama:
Yep sure, I'll build tonight.

Thanks!
[Nexus 5 Android Development] danarama:
Test build 6.23.9

Please can you guys test the qualcomm time daemon settings for me? Particularly those who have /data/system/time directory but not /data/time

http://d-h.st/users/rootsu/?fld_id=34576#files

My experience is that it works for the date and time, but the time is 1 hour ahead so I have to go -1 in time zone or even I can put correct time zone and then change the time settings to go back 1 hour. I am not sure if this is because I've been fiddling with things though so would be interesting what everyone else sees before updating OP.
[Nexus 5 Android Development] Unb0rn:
Flashed. Everything works fine without /data/time (only hammerhead-default /data/system/time). No shift in time zone nedded for me. I think there might be a problem with DST-it would explain everything-we don't have DST here in Russia anymore...
[Nexus 5 Android Development] danarama:
Thanks.

Yeah DST is Sunday for me.

I don't actually understand what's going on though. I may need to reset recovery settings to see what time I get haha.

I'll do that now.
[Nexus 5 Android Development] Unb0rn:
Hehe, hope that helps! Hammerhead maintainer with problems sounds sad;)
[Nexus 5 Android Development] aow1980:
It worked holding my time settings.. Only thing it was an hour fast. I changed that with the offset.

Using Slimkat 3.10, Franco r37.
[Nexus 5 Android Development] danarama:
I'm using slimkat too... and was an hour ahead....

Any other slimkat users? Are you an hour ahead?

Non-slimkat users?
[Nexus 5 Android Development] kufikugel:
Uh rootSU sorry saw that all way to late. You guys figured all out now?
[Nexus 5 Android Development] danarama:
No worries [MENTION=4790322]kufikugel[/MENTION] :)

Yes and no.

All hammerhead use /data/system/time so this has been added to the recovery. Some CM commits on other devices were to /data/time hence the original confusion.

Now it's just a case of trying to identify why some of us have an hour difference.
[Nexus 5 Android Development] Phil3759:
Are you on DST already?

In my case it is end of the week

When DST will come, I'll have to lock main thread to avoid complaints

The setting is broken, since... winter time :D

I hoped to fix it before the new summer time, but did not find time
[Nexus 5 Android Development] danarama:
Nah DST is also Sunday for me too in UK :)

But that's why I cannot understand the 1 hour difference. It's like it already thinks I'm in DST

Its not a big deal for me, I can just offset. It will be correct time next week ;)
[Nexus 5 Android Development] adrman:
Flashed fine and I have the correct time settings. I've been on DST for about the last two weeks though.

Forgot to mention, I'm on rooted stock.
[Nexus 5 Android Development] aow1980:
I'm in the US and my time is an hour fast. Been on daylight saving time for a few weeks now.
[Nexus 5 Android Development] danarama:
What rom?
[Nexus 5 Android Development] aow1980:
Slimkat 3.10.

I believe it is due to in the rom it has eastern time zone as - 4 hours. But in recovery it has eastern as - 5 hour.
[Nexus 5 Android Development] danarama:
EST is -5 but EDT is -4 and both are "Eastern Time". Actually if you set your date back 1 month, you will see that "Eastern Time" becomes -5 again. So the time zones in SlimKat are dynamic and change based on the date.

[MENTION=4666971]Phil3759[/MENTION] admitted DST isn't configured to work yet in recovery, so it makes sense that yours is 1 hour fast in recovery if you are in EDT right now.

For me, I am GMT (0) but in recovery my clock is 1 hour ahead. When I change to BST (GMT+1) on Sunday, I am not sure what will happen to my clock in recovery.

EDIT > after resetting my recovery settings, syncing time in ROM (I use clock sync to sync to atomic clock) and reboot into Philz, It's all correct for me now.
[Nexus 5 Android Development] amirsh77:
I flashed and tested it, it works fine, show correct time and date. I just set my time zone (Iran), I'm on MahdiRom with ElementalX.
[Nexus 5 Android Development] danarama:
Further to what I said above, could you do the same please?

Just backup all your recovery settings,the reset them.

Set the qualcomm dameon in settings

boot into SlimKat and Sync your time (using Clock Sync if you can*) https://play.google.com/store/apps/details?id=ru.org.amip.ClockSync

boot back into recovery and check time

*I'm sure android does this but I have no idea how often so this will ensure your daemon reports the correct data in ast_1 and ast_2

I'm not sure if Timezone settings are even used in recovery if we're using time_daemon. Theres certainly no need to use them as long as the rom is correct, the daemon should report correctly.
[Nexus 5 Android Development] danarama:
Thanks for checking
[Nexus 5 Android Development] aow1980:
Followed the steps and still was an hour behind. I also updated the time zone info with the app click sync popped up. I'm wondering if it is because in the US we have already went to dst time and others haven't.

I had a similar situation with a work pda being an hour due to it. When the rest of the world switched last year it was then an hour ahead.

Overall though thank you for taking the time to help figure this out with the recovery. I personally can handle the time an hour off. It's nice having the day and year correct.
[Nexus 5 Android Development] danarama:
Cheers. Yeah it must be DST related for you. My issue was my own due to having configured and reconfigured recovery times multiple times. A wipe sorted it for me.

[MENTION=4666971]Phil3759[/MENTION] - Do the recovery timezones mean anything in recovery if using time_daemon? I would expect all other settings would be uneccessary if correct in ats_1

Can we read what is contained within those binaries?
[Nexus 5 Android Development] Phil3759:
Time daemon reports gmt time

Recovery still needs manual timezone setting
[Nexus 5 Android Development] danarama:
Oh I see. So time_daemon doesn't see ROM timezone at all. It is always GMT (UTC) regardless of the timezone set in the ROM? Then we need recovery timezone to offset to the correct time.

In which case, why is time_daemon like that?
[Nexus 5 Android Development] danarama:
Minor update for qualcomm time daemon added to OP. Its the test build linked yesterday 6.23.9

Time Daemon reports in GMT. Recovery will pick this up. Apply your local time zone in Philz to get correct time. Please note, DST offset is not yet working so you may need to change your time zone to get the right time if you are already in DST
[Nexus 5 Android Development] ddloco:
What is this and how do I get rid of it thanx

(using legacy property inviorment for update-binary please update)
[Nexus 5 Android Development] danarama:
Can you be a bit more specific about your question please?
[Nexus 5 Android Development] Phil3759:
he's talking about the new message when using outdated update-binary
[Nexus 5 Android Development] danarama:
Yes I know what he is talking about but I want to understand why he needs to know what it is and why he thinks he needs to get rid of it.
[Nexus 5 Android Development] ddloco:
I take it you guys know about this and its supposed to be there in that case I'm sorry I thought something was wrong
[Nexus 5 Android Development] danarama:
Oh ok. I understand.

Yes, every flashable zip has an update-binary within it that allows it to be a flashable zip. As the android environment and kernel progresses, so too do the functions of recoveries and the need to keep up-to-date update-binaries.

Some devs use old binaries which cannot perform all necessary duties in more modern environments. This means recovery developers must go to crazy lengths to allow backwards compatibility with older update-binary that shouldn't even be used any more.

All this is is a message that whatever you're flashing has an outdated update-binary in the zip that whoever made the zip should replace
[Nexus 5 Android Development] amirsh77:
Is there a new update? :)
[Nexus 5 Android Development] FlyinGrub:
Wow i think you don't unserstand xda's rules ...

[MENTION=2872010]rootSU[/MENTION] is there a way to only wipe /system ?

Envoyé de mon Nexus 5 en utilisant Tapatalk
[Nexus 5 Android Development] danarama:
Its actually against the rules to ask for eta updates.

The main code base has a couple of changes but nothing that would be major for us. There have been a few successive updates

in a relatively short time so i'm waiting to bundle a few more changes in before the next build.

Yep, mounts and storage > format /system
[Nexus 5 Android Development] fatspirit:
Does it have dup format support?
[Nexus 5 Android Development] danarama:
tar, dup, tar+gzip
[Nexus 5 Android Development] FlyinGrub:
Where can we found up-to-date update-binary ?
[Nexus 5 Android Development] Phil3759:
any last cm nightly
[Nexus 5 Android Development] aheeejd:
Hey guys, I'm a bit confused about backing up my efs partition, I guess I am under the impression that I should have done this like right after I rooted & installed a recovery. But reading through the thread here I'm not sure. Is it as simple as just going to recovery right now & backing up efs 1, & then efs 2. And why are there 2 efs backups. I know not to play around with them, only in emergency. Also, for regular backups, from the cwm folder, can I move my backups to PC, or even cloud storage, just to get some more space on this phone. Moving them around may/may not corrupt them, so I'll make a few. Thanks for any help.

Sent from my Nexus 5 using Xparent BlueTapatalk 2
[Nexus 5 Android Development] fbf2201:
It appears like any other cwm backup and contains efs1.img and efs2.img
[Nexus 5 Android Development] danarama:
There are 2x efs partitions on the Nexus 5, so each option backs up each partition. Both can be backed up in the same backup job. DO NOT restore your efs backup on another Nexus 5.
[Nexus 5 Android Development] aheeejd:
Thank you, I just wanna do this right, so I go to recovery, & back up both, just the efs1 & efs2, I mean I don't include those backups with a normal rom backup correct, just do those 2 & save in a safe place. The backups will show in the cwm backup folder. I only have 1 backup in there now, a rom. Thanks again

Edit- I just went to recovery to look. So I would go to recovery, hit custom backup, check efs1 & 2, & uncheck all the other ones that are checked by default? Is this what I was to do, & then hit start custom backup

Sent from my Nexus 5 using Xparent BlueTapatalk 2
[Nexus 5 Android Development] danarama:
Yep
[Nexus 5 Android Development] aheeejd:
Thank you very much, I know it $ucks when someone asks to be hand held through stuff, & I'll admit, that's just what I needed. I wasn't positive how to do it, & I was reading in the sense port thread where people fried (possibly) their sensors, & a few people had no efs backups, were even asking people to post their backups, & I knew each 1 is phone specific, anyways, I'm good to go now, thanks again.

Sent from my Nexus 5 using JellyBombed Tapatalk 2
[Nexus 5 Android Development] fbf2201:
[emoji106] looks almost as mine [emoji1]
[Nexus 5 Android Development] toanau:
How do we turn off the vibrate on touch when in recovery
[Nexus 5 Android Development] danarama:
All user interface settings are in Philz Settings > GUI Preferences.
[Nexus 5 Android Development] Tylog:
After again and again issues with Twrp ( use it very long on all devices and really love it ) I use now Philz, for now it works fine, thanks for it on N5

Tapatalk Team SlimRoms
[Nexus 5 Android Development] danarama:
Thanks to [MENTION=4666971]Phil3759[/MENTION] :

Changes between 6.23.9 and 6.26.1

- fb2png: better error logging

- sort files using case insensitive order

- remove old no more needed md5 check code

- fix successive gestures

- set these default gesture actions:

* swipe left = screen off

* swipe right = increase brightness

* press 1 sec and lift = show log

* press 2 sec and small move = screen shot

- merge "Only init legacy property environment once"

- revert using ntfs module and drop to fuse for complete write support

- use new md5digest code to generate/verify nandroid backups

- bring progress bar during nandroid md5 generation and check

- exclude log and md5 file when regenerating md5 files

- twrp mode: use new md5digest function with status bar during md5 check/create

- twrp mode: fix double md5 verification bug

- fix delete backup menu failed to reopen base backup folder + weird log message

- fix the "umount: can't umount /data: Invalid argument" log message on start when time daemon was loaded

- show "time daemon loading" message on recovery start when we're waiting for the daemon to load
[Nexus 5 Android Development] Tylog:
Great update, thanks :)

Tapatalk Team SlimRoms
[Nexus 5 Android Development] micens:
Hi.

Why we have two times same thing here? In fact, why do we have the option to format something that could destroy our phone? :rolleyes:
[Nexus 5 Android Development] Phil3759:
These should be hidden by setting some ro properties
[Nexus 5 Android Development] danarama:
Not sure why it shows up twice. Whether it should be there or not is another question. Sometimes a format is required before a restore to give a proper fix. Recovery is and always was a tool so users must always use at their own risk and exercise caution at all times.

Edit > you know Philz can take screenshots no? Look in gesture settings
[Nexus 5 Android Development] Phil3759:
Restore will format before restoring
[Nexus 5 Android Development] micens:
How?

Is this be same in the previous version? Or this is "bug" in new version?

Ok, more option is not bad, but be interesting if we could hide this if we don`t need :)

Yes, I saw that, but I forgot :angel:

Thank you Phil3759 for your hard work. This is not a criticism, just would like to help to improve best recovery ;)
[Nexus 5 Android Development] kronflux:
looks like there's an update. 6.26.6, which is built against CWM 6.0.4.8. No idea what advantages the new CWM has, but there is a changelog available for PhilZ:

6.26.6 (14.04.2014)
- m7 unified for m7ul, m7att and m7tmo
- CWM 6.0.4.8
- merge support for native dual boot devices
- sync sources

6.26.4 (12.04.2014)
- update libloki to latest sources
- broken root: help victims of bad custom ROMs
This adds extra code to detect if two su instances are installed in /system/bin and /system/xbin
It will kill both and properly apply SuperSU
- fixing root on exit was never done what ever was user choice
[Nexus 5 Android Development] efan3719:
[MENTION=2872010]rootSU[/MENTION] doesn't update this version unless something in the main version pertains to the nexus 5
[Nexus 5 Android Development] kronflux:
ah, okies :) just thought I'd mention it. sorry if it's considered spam or thread bloat :P
[Nexus 5 Android Development] efan3719:
No worries. Maybe there is something in there that is useful. I have no idea. Doesn't hurt to ask questions. :thumbup:
[Nexus 5 Android Development] danarama:
The CWM base may be worthwhile. I've not seen an official change log from Koush yet.

I'd happily build every night but we end up with people fed up of upgrading and a wider spectrum of versions which makes troubleshooting more difficult.

I try to bundle as many changes into a single release whilst trying to balance that with nexus 5 users not feeling left out.

If anyone feels we are missing out on a particular feature that we could benefit from, I invite you to let me know - otherwise I'll keep bundling.
[Nexus 5 Android Development] Phil3759:
There are no meaningful changes in cwm 6.0.4.8 except the 8 LoL

However, wired that you have 2 format efs entries

Can you post your /etc/recovery.fstab contents?
[Nexus 5 Android Development] micens:
Hm I can`t find this in etc... :( Do I need to create first somehow or...???
[Nexus 5 Android Development] Phil3759:
it is in recovery ramdisk

boot into recovery and it will be there
[Nexus 5 Android Development] micens:
How to save this on different location that it can be transferred to my pc, and sent to you?
[Nexus 5 Android Development] fbf2201:
Here you go...

efs1 and efs2 are listed twice.
[Nexus 5 Android Development] micens:
I found it :D

Here you go...
[Nexus 5 Android Development] Phil3759:
[MENTION=2872010]rootSU[/MENTION] needs to fix the fstab

Also, he must add the needed props to stop showing the items in Mounts and Storage:

device.mk

#hide partitions from format/mount: (device.mk)
#system.prop
# CWMR Options
ro.cwm.forbid_format=/efs1,/efs2
#ro.cwm.forbid_mount=/efs1,/efs2
[Nexus 5 Android Development] micens:
I hope it will be fixed soon :p

Thank you for response ;)
[Nexus 5 Android Development] danarama:
Will do so.
[Nexus 5 Android Development] micens:
:good:
[Nexus 5 Android Development] Phil3759:
can you test a build based on cm kernel sources? See if it fixes the graphic issues
[Nexus 5 Android Development] danarama:
Yup, will try
[Nexus 5 Android Development] danarama:
[MENTION=4666971]Phil3759[/MENTION]

1) Fixed my error in fstab

2) Sorted props

3) CM Kernel returns graphical glitches

4) Also breaks md5 verification (see screenshot. Expected matches but errors as if not matching)

5) Stock kernel build solid as always

Will publish with Stock kernel soon
[Nexus 5 Android Development] Phil3759:
the md5 check error, as you can see in pic, is caused by a bad formatted 09-DanMods_new.zip.md5 file

the md5 file MUST NOT contain whole path, but only file name

you probably generated md5 sum without a cd to containing folder
[Nexus 5 Android Development] danarama:
I used the same script I wrote and posted in post 1 of this thread. I have always used without error. Works perfectly on recovery with stock kernel, just not with CM kernel.

Edit > My mistake, I did create with a different (test) md5 script I created for Tasker, however still works with stock and not with CM. How come?
[Nexus 5 Android Development] Phil3759:
then you have a bug in your script

the log (E:Expected...) prints content of your *.md5 file. It is clearly showing the full path to your zip which is against md5sum convention

only filename must figure in your *.md5 file, which is not the case in example above
[Nexus 5 Android Development] danarama:
See above edit. There is a difference between how Cm kernel in Philz handles it and how stock kernel in Philz handles it as the same files flash fine with stock kernel. Its a non-issue really but doesnt make sense.
[Nexus 5 Android Development] Phil3759:
kernel has nothing to do with this

it is the script you use and from where you run it

md5sum command must not have full path of file as input

edit:

if you put the same zip/zip.md5 couple as your screen shot, it is impossible to make it flash what ever the kernel is

recovery code has nothing to do with kernel
[Nexus 5 Android Development] danarama:
I get that but see below....

Example.

Build philz with cm kernel

flash danmod

error as above (for reasons you;ve explained)

Build Philz with stock kernel

flash danmod

SUCCESS

Same file, same md5 file, same "Incorrect path" yet, works. How can the kernel NOT have anything to do with that since it is only change?

I'm not making this up.
[Nexus 5 Android Development] danarama:
Ok. Maybe it just didn't verify when I retried then, because it did flash.
[Nexus 5 Android Development] Phil3759:
can you post the kernel zip image and your md5 sum file with whole path

it is just impossible that they flash, so wanna test it myself

Also, can you provide a log of a successful flash using that combo?

we'll immediately see if it is possible and why
[Nexus 5 Android Development] danarama:
No it seems not possible after retesting. I must have somehow hit the verification button and not verified because I can't reproduce it. Must be my error.
[Nexus 5 Android Development] Phil3759:
time to sleep :cyclops:
[Nexus 5 Android Development] danarama:
Yes! I've had a terrible week. Spent hours on the phone with Microsoft trying to understand why all of a sudden Outlook stops accepting the passwords for 500 users on site. Then only fix is to reprofile outlook. ...and this is just before I push out office 2013 to our global userbase

Then on top of that, the courier cannot deliver my special cat food so I have to feed supermarket crap to cats. It doesn't fill them up so they want breakfast at 3am and I have to be up at 5:50 for work :(

In short, sorry I'm wrong. Ignore everything I said in last 24 hours and also anything I say in next 72 hours :)
[Nexus 5 Android Development] ddloco:
Was sup root can I get that danmods zip from u or can you please tell me where I can find it thanks
[Nexus 5 Android Development] danarama:
It's just personal mods I make to my roms. Applies bootanimation things like that
[Nexus 5 Android Development] Phil3759:
[MENTION=2872010]rootSU[/MENTION]

When you have time, can you try to compile a version based on latest cm kernel (revert your BoardConfig.mk changes) and add these flags:

device/lge/hammerhead/BoardConfig.mk

# QCOM
BOARD_USES_QCOM_HARDWARE := true
TARGET_USES_QCOM_BSP := true
COMMON_GLOBAL_CFLAGS += -DQCOM_HARDWARE -DQCOM_BSP

Could be it fixes the graphics bugs
[Nexus 5 Android Development] danarama:
Yeah sure. Today or tomorrow :)

Edit [MENTION=4666971]Phil3759[/MENTION] is there any advantage to using Cmdr kernel instead of stock?
[Nexus 5 Android Development] Phil3759:
It is to understand the issue

Can you test this version:

http://d-h.st/gv8
[Nexus 5 Android Development] danarama:
Worse than ever. Unusable in fact. Couldn't exit recovery without connection to PC and adb reboot.

Can't press any options without glitch but it's permanent glitch.
[Nexus 5 Android Development] kronflux:
although I now know you prefer to wait to update until there are multiple updates that benefit our device, I just wanted to point out that there is one beneficial fix, that is quite an annoyance currently.

I don't know specifically whether the currently nightlies of CM11 actually use a symlink for root or whether it's something else causing it, but right now everytime I flash an update, I get the prompt whether or not I want to fix root, when root does not need to be fixed.

*shrug* again, just an annoyance, it's livable if you prefer to wait to update, but I thought I'd point it out anyway. :)
[Nexus 5 Android Development] Phil3759:
I will commit a few patches in next days

You should wait if you do not like to update often
[Nexus 5 Android Development] danarama:
Turn root detection off.

Thanks but i am aware of every version when its released ;)

Yep, i don't want to annoy users with every version = update. From a development perspective there are lots of commits in each version but from a nexus 5 user perspective it can be one or two.

I don't mind building regularly but with a more combined release model, we avoid fragmentation hopefully ;)

What plans do you have in next build?
[Nexus 5 Android Development] kronflux:
ah right. thanks. forgot you could do that. xD
[Nexus 5 Android Development] danarama:
Changes between 6.26.6 and 6.29.2

- fix potential bug when verifying root and recovery state on exit

- merge "Fix verify_root_and_recovery menu selections

- hide the Go Back button from confirm menu

- add minitar binary to /sbin instead of busybox tar

- minitar: enable more options, enable long options, fix selinux backup/restore, enhance GNU tar compatibility

- enable seamless backup/restore selinux context using minitar binary

- TWRP mode: support backup/restore of selinux context

- confirm cancel nandroid jobs (prompt to press 'Back' twice or resume after 5 secs)

- vibrate after backup/restore operations

- do not consider su symlink in /system/bin as a broken root