yashsingh1/xdaforums huggingface dataset:
[Xperia Z1 Original Android Development] Kacha13:
I have to disagree. I tested DirtyUnicorns too and it's there as well. None of the ROMs seem to be safe. Either all use some stuff from CM or the problem is inherent from the original Android code. No ROM on Lollipop seems to be able to fix it. It's the same with a larger battery drain as soon as you are on WiFi, although it should be the other way around. If WiFi is on, Apps and the system are more active. I removed the three events and followed the advice here: http://xdaforums.com/android/general/guide-extreme-battery-life-t3095884 It's not perfect, but there battery life is better. I'm not completely happy, especially if I compare it to KitKat.

Another point that I encountered through all ROMs is screen freezing. I'm not sure if that is my phone are the ROMs though. Does anybody experience something similar? For me it's mostly in WhatsApp, when I'm writing. Sometimes I can recover it by going back or dragging the quick draw bar down, but often I need to turn off the screen and turn it on again. Even when it appears in different Apps, it is always while writing. I wouldn't be surprised if it's a hardware problem, but on the other hand, I also wouldn't be surprised if it's a problem of the ROMs.
[Xperia Z1 Original Android Development] LSD DREAMER:
I have not had 1 screen freez since I changed my screen protector.
[Xperia Z1 Original Android Development] optimumpro:
If wifi background scanning is hard disabled and wifi optimizations is set to 0 in settings.db, there is no battery drain on wifi.

Screen freezing is a separate issue and happens on all roms. Indeed, it may be related to the removal of stock anti-shuttetering film, as screen was calibrated with the film on. One can tinker with /system/usr/idc/clearpad.idc values and it should help.
[Xperia Z1 Original Android Development] Kacha13:
It may be the film, as I don't think I have it anymore. What's the easiest way to change the settings? System is read only and I doubt you can remount it read/write. And are there any recommendations for the values? Did somebody try it out already?

Regarding WiFi, this needs to be set before compilation or is there any possibility changing it in an already running ROM?
[Xperia Z1 Original Android Development] optimumpro:
WIFI background scan could only be hard disabled in source. You can try to decompile framework-res.apk and change the value there, but I bet the phone won't boot because of different signing signatures. Also, the value there goes into some libs, so, the proper way is to do it in source.

On disabling wifi optimizations see this: http://xdaforums.com/showpost.php?p=61798508&postcount=102

You can change touch screen value in root explorer. I have:

touch.pressure.scale = 0.0014

touch.size..scale = 30.69

touch.filter.level = 6

----MaxSpeed = 0.042
[Xperia Z1 Original Android Development] Kacha13:
I'll try it out. The values are without the film?

I will also try it with WiFi optimisations turned off. I hope it's enough, I don't want to recompile. I doubt that the decompiling will work.

What I'm wondering though, why does nobody include that in their ROMs if it is such an easy fix?
[Xperia Z1 Original Android Development] optimumpro:
Because those values are probably not good for those who have the film on...

Disabling background WIFI is included in all my roms...
[Xperia Z1 Original Android Development] Kacha13:
I changed the values and rebooted. Seems fine so far, but I will test it during tomorrow. Did you change anything else?

I saw that your ROMs have disabled it, but I'm reluctant so far. Nothing against you, you are a great help, but some of the changes you made are not entirely my style. ;)
[Xperia Z1 Original Android Development] Diewi:
Thanks, Omar for the update and your efforts.

I noticed that the autofocus does not work like the build I posted some time ago. I tested it with a clean environment with the updated sources and the kernel that I patched a bit. As a note, this can be worked around by using the Google camera from the market.

During my experiments some weeks ago, I got it working at some point when updating vendor libs (using the sony lp5.0 firmware). However, at his point my out folder was a bit messed up, so I was not able to trace back which change made it work :( So, the solution must be somewhere there. Will have a look at it later again.

That is exactly the same I am experiencing. There is a thread in the one plus forum that describes exactly this issue : http://xdaforums.com/oneplus-one/help/event0-wakelocks-t2957829.

The correlation between the input event device (mhl, chg, etc.) and wifi is very strange. In my opinion, there a two possible explanations:

1) Google made some "optimizations" to the statistics such that the real cause of the drainage does not appear (not unlikely).

2) It has something to do with wifi direct / wifi display etc. This technology allows to output the display via wifi to a screen (like mhl does), maybe also forwarding keypresses from a remote control (see the connection?). Following this logic, I disabled wifi display in the device-specifc framework overlay (found in rhine-common), but it did not have an effect :(. Someone has thoughts on this?

During the examination of the battery drainage, I experimented with disabling the background scanning as well (without positive results). However, I did not identify the toggle in any of the board configs. The only flag that I found was in the device-framework-overlay that contributes to the framework-res.apk. The only references to background scanning that I found in the libraries were a wrapped call to this key. Am I missing something here?

Regards,

Diewi
[Xperia Z1 Original Android Development] optimumpro:
That's the only flag, but that entry alone will cause rebuilding of the entire rom, as opposed to just framework-res.apk.

Edit: What I mean is if you turn background scanning in msm8974 overlay off and compile framework-res.apk, that won't do the trick. If however, you execute "make -j4 otapackage" without any "repo sync", the make will start recompiling the entire rom, which means that that flag goes into many more java/native/C++ files, as make is pretty good in figuring out whether you need one or two files to recompile or the majority of the rom.

Wakelocks based on gestures: disable everything related in settings including tap to wake. These are not needed and cause the system not to sleep (I mean the way it is implemented by Doodle, oops, google.). I can vouch for at least 2 roms that I have compiled and posted here not to have any wakelocks related to wifi or any gesture/touch issue. These are DU and PA. Moreover, I have also tried: Teslaredux, Slimroms (before break up) and Validus and found absolutely no battery drain related to wifi. As a matter of fact, with wifi on 24/7 there is less battery drain than with GSM data.
[Xperia Z1 Original Android Development] Diewi:
Thanks for the extensive answer. I noticed too that this switch causes a rebuild of the whole rom. From what I have learned now, the xml files in the values folder are translated into a binary table at compile time. Hence, the references from other apks must be update as well to get the references right. (I should have looked this up earlier :angel:). Since almost every apk and much of the jni stuff depends on framework-res it is logical that almost everything must be re-compiled. Got it now.

Tap2wake and the gesture stuff is disabled. On honami, t2w prevents deep sleep completely, as the display(sensor) generates no interrupts or this feature. But I'm noticing just a much reduced deep sleep time.

Currently, I'm still trying to figure out the common cause that triggers this issue. All the recommendations I read show no correlation, e.g. switching to 5Ghz only, static IPs, disable location services, downgrading the wifi driver. The only trigger I found up to now is being connected to a wifi, leaving wifi active when not being connected does not trigger the issue. But thank you very much for the references. It will help a lot to identify the real cause by comparing the differences, one the problem is located better.
[Xperia Z1 Original Android Development] M-Rom:
I really hope this time Theme Engine comes to Slim
[Xperia Z1 Original Android Development] optimumpro:
Ain't happening. Slimroms have layers.
[Xperia Z1 Original Android Development] Diewi:
You may consider the cause of the wifi related battery drain identified ;)

The wifi driver frequently wakes up the cpu, if braod-multicast ARP packets are received (e.g., Whatsapp uses those). This, of course, can only happen when being connected to wifi network where some devices emit those kind of packets. Hence, the number of devices in the network typically has an impact of the number of wakeups of your phone. Consequently, the eventX wakelocks appearing in the wakelock statistics are completely misleading and they occur -as far as I understand it- only because the wifi driver receives a packet and wakes the cpu. Then, the eventmanager checkes for an input event (where the kernel generates a wakelock), meanwhile the system detecting the irrelevance of the incoming arp paket, and hence the system must wait for the event processing to go to sleep again.

So, how to fix this battery drain? One workaround is diabling the wifi during sleep (of course! ;) ). Another one is to disable the arp offloading feature in the config file of the prima wifi driver (WARNING: be aware that Whatsapp etc. may have delays for incoming messages): Just set the values for gEnableActiveModeOffload and hostArpOffload to 0 in the file /system/etc/firmware/wlan/prima/WCNSS_qcom_cfg.ini (/system must be mounted r/w therefore).

Sources:

[1] http://xdaforums.com/nexus-4/general/wifi-network-connectivity-issues-fix-t2072930

[2] http://xdaforums.com/showthread.php?p=43930361#post43930361

Next steps: I will iteratively update the wifi driver to pull in some modifactions related to ARP offloading and are related to the filtering. This way, it may be possible to avoid the disadvantages mentioned in the paragraph above.However, this will take some time ;)

As a side note: The drainage did not happen on older CM versions since it was using an older version of the wifi driver which did not support the ARP offloading.

Regards,

Diewi
[Xperia Z1 Original Android Development] optimumpro:
Why not disable multicast at all together with all wifi "optimizations." Those optimizations cause more battery drain than when you have a straight connection, as wifi manager alone causes wakelocks (every 10-15 seconds). My problem with LP changes is that wifi disconnects completely after 15 minutes of deep sleep and no amount of changes in Settings.Global can prevent it. Even if I set wifi_idle to 16 hours. Never had it on kitkat. I even made changes in the java file directly to no avail, while there is a comment in the file that the default 15 min disconnect will only be used if there is no entry in Settings/Global. There are multiple issues on this created on google aosp site, some since November 2014. Google does not know how to fix it. Their engineers should be sent back to school (but I am pretty sure they won't pass the entrance apptitude test).

If this was up to me, I would just recall LP. This puppy just can't move...
[Xperia Z1 Original Android Development] optimumpro:
OK. I think I have solved it. I have looked at that WCNSS.qcom.cfg.ini file and found that Qcom proprietary driver has total control of wifi including power management overriding Android. That explains why wifi gets disconnected after about 15 min of sleep despite global commands not o disconnect. So, I have made two changes which take care of your issue (battery drain) and my disconnect issue:

1. I enabled deep sleep instead of mcast/bcast; and

2. Let Android framework take care of power saving, especially, that it also has its own arp implementation.

I have tested the changes for a half of day and had no single wifi disconnect. Also there was a pretty good deep sleep.

Edit: Here, you can look at the changes: https://github.com/AOSPME/device_sony_rhine-common/commit/2616267495ffeea5dcd1ef7a2018f87d068dbe38
[Xperia Z1 Original Android Development] Diewi:
You found the other changes faster than I could reply ;)

I also enabled the switch to allow android framework to control power settings, which has quite a positive effect (I forgot to add this info before, sorry). Hence, disabling wifi optimizations could have no effect on the power savings (as far as I understand it), except the framework did mess something up if it cannot manuipulate power saving options although it wants to.

Regarding the "gEnableSuspend" setting: Have you tested modifying this switch alone, such that the power savings do not result from another change? I'm asking because from my understanding the value '3' allows even more power savings than option '2', as the firmware itself filters out Multi- & Broadcast packets, Ohterwise, it would wake the CPU each time, resulting in reduced deep sleep times

Regards,

Diewi
[Xperia Z1 Original Android Development] optimumpro:
Let's move this discussion to one of my threads: http://xdaforums.com/showpost.php?p=62086781&postcount=12
[Xperia Z1 Original Android Development] Kacha13:
I tested out the screen settings you mentioned and somehow the problem persist, sometimes better, but not always. Do you have any other advice?

Do you have the changes included in your builds? Or are these still in testing? I would really love to have LP with KitKat battery drain when WiFi is on. ;)
[Xperia Z1 Original Android Development] optimumpro:
Yes, the changes are in the latest builds of Slimrom and DU in their respective threads...
[Xperia Z1 Original Android Development] OmarEinea:
SlimLP Beta 0.5 [2015/08/16] Is Up!

ChangeLog:

- Android 5.1.1_r10 Build [LMY48J]

- Included all new changes from SlimRoms, Take a look HERE

- Included all new changes from CyanogenMod

Download Links:

Slim-honami-5.1.1.beta.0.5-UNOFFICIAL-20150816-0134.zip

And here are Slim Gapps for Android 5.1

Regards,

Omar.
[Xperia Z1 Original Android Development] XDM inc:
why is there red particles in photos or certain menus?
[Xperia Z1 Original Android Development] lm/\/trix:
does this rom contains red particles in photos or certain menus?
[Xperia Z1 Original Android Development] optimumpro:
It is not the rom, it is your phone that 'contains' an after-market display that is causing the 'red particles.' As I said in another post, try to get a non-working Z1: it could be sim locked/bootloader locked; the only thing you need is an original OEM screen. Then that screen together with the frame it is glued to, could be transferred to your phone. I spend $28 on such a phone (negotiated down from $45). It was sim locked to a Canadian company, speaker and microphone didn't work, wifi didn't work, bad battery etc). In other words unusable phone, except the screen.
[Xperia Z1 Original Android Development] lm/\/trix:
Thanks for reply, i asked this Q because some android roms doesnt contain the red particles i.e. SlimKat, Miui, CM11, etc. but some ROMs like Jaguar, CM12.1, etc. has it...
[One (M8) Q&A, Help & Troubleshooting] Bombi22:
hi i accidentally used this command Fastboot oem lock

i was following a tutorial how to flash something but im stuck in bootloader now and i cant get to recovery what command will unlock this ?

in top of bootloader it says

*** TAMPERED ***

*** RELOCKED ***

*** Sercurity Warning ***

thanks in advance
[One (M8) Q&A, Help & Troubleshooting] LenAsh:
Thread closed - you already have one open HERE

Please avoid creating duplicates... it may result in less replies.

Thanks
[8525, TyTN, MDA Vario II, JasJam Accessories] mplang:
Anyone have any recommendations for an automount that is GPS Ready...you know, the cradle can power a GPS unit (Garmin GPS 10)??? I have been looking but drawing blanks on units specific to the Hermes...any help is greatly appreciated...
[8525, TyTN, MDA Vario II, JasJam Accessories] vp3G:
I recently picked up this mount and it rocks. Only one I've seen that will power a BT GPS unit. Looks like it will power the Garmin 10x, although I use an i.Blue 737 with it.
[8525, TyTN, MDA Vario II, JasJam Accessories] icemantwilight:
That's very cool and almost exactly what I need..

would you mind telling me:

How good is the speaker, I find the built in one just a bit quiet for tomtom..

Can it be toggled on/off for voice calls?

What is the vent clip like? I'm not a fan of windscreen mount..
[8525, TyTN, MDA Vario II, JasJam Accessories] vp3G:
The powered speaker is great and is automatically activated when you cradle the device. Actually, the mount turns your phone into a completely hands-free speakerphone. There's a 2.5mm headset jack on the mount and cable with built-in hands-free mic that plugs in between the headset jack and the powered speaker. Or you can just use a BT headset and bypass all of that.

There isn't and on/off toggle for the speaker, although my navigation software (Odyssey 4.0) shuts up whenever I'm on a call. I think this must be a feature of the software rather than the hardware, although I'm not entirely sure.

There is an on/off toggle for charging your phone while cradled, although the mount must always be plugged in order to use the powered speaker. There's a separate modular port (always on, not toggled by the aforementioned on/off switch) and pigtail cable included that can be used to charge your BT GPS unit. My only complaint is that the speaker picks up some interference from the phone and/or GPS unit when the charging switch is "on". It's barely noticeable over road noise once you're moving, however.

Haven't used it, primarily because it forces you to use your device in portrait mode (which was a non-starter for me).
[8525, TyTN, MDA Vario II, JasJam Accessories] Fourgig:
I have the same OnCourse mount and my unit also has interference in the mount's speaker when the phone charging is turned on. It's like a constant clicking sound - not terribly loud though, so road noise drowns it out. But then again, I drive a Lancer Evo and there's not much noise dampening material in the car so YMMV.

One other thing is my Hermes doesn't plug into the cradle's mini USB connector easily. I have to rock the phone back and forth a little bit in order for the phone to seat onto the USB connector. Obviously a tolerance issue, but I don't know if it's caused by my phone or the cradle.

The clips are pretty decent. They have 3 notches so you can vary the distance the cradle mounts from the air vent. The clips sit in a slot on the cradle so you can slide them horizontally to change the distance between the two clips. Pretty useful for getting the clips to line up between the air vent's vertical slats.

Overall, it's a pretty decent product.
[8525, TyTN, MDA Vario II, JasJam Accessories] vp3G:
Yep, I assume it's the radio in the phone, although I haven't done a thorough investigation as to the source. I just don't charge it in the cradle unless I really have to. Kinda wish the powered speaker would function without the power cord, but oh well.

Ditto. Not terribly easy to get it mated with the USB connector on the way in. Or very easy to get it out, for that matter as it's pretty much impossible to avoid pressing all the buttons on either side of the phone when grasping it. But, like anything, you eventually get the hang of it.

If only they'd have designed it such that you could go landscape, too. :(
[8525, TyTN, MDA Vario II, JasJam Accessories] Trinergy:
Here is the sam mount but by i.trek over at semsons

http://www.semsons.com/ipocrmowiins18.html

use coupon seth005 to get 5% off. Just ordered it today.
[8525, TyTN, MDA Vario II, JasJam Accessories] vp3G:
Yep, same mount... better price! :D
[8525, TyTN, MDA Vario II, JasJam Accessories] icemantwilight:
Sounds could be coming from your cars electrics, they're notorious for noisy power, particularly if the ground is bad.

Why does everyone love landscape? I use tomtom and I much prefer portrait.
[8525, TyTN, MDA Vario II, JasJam Accessories] Fourgig:
Think one of those engine grounding kits would help?

I'm right there with ya! I've never found a good use for portrait mode, other than watching movies. :)
[8525, TyTN, MDA Vario II, JasJam Accessories] icemantwilight:
Really hard to say, if your ciggie lighter (power socket) and your battery both have a good ground connection then you should be right..
[8525, TyTN, MDA Vario II, JasJam Accessories] paulrockliffe:
I know this isn't the answer you're looking for, but I always use two bits of bluetack to fix the Vario to my dashboard behinf the steering wheel.

Is virtually free and very effective. You can also use a cigarette lighter to USB thing to power your GPS unit and/or the Vario, or wite a USB cable into the dashboard if you feel like it.
[8525, TyTN, MDA Vario II, JasJam Accessories] jellycow:
Semson / OnCourse car kit

I got the unit from Semson using the horn (global 9) suction mount. That's the non flexible hose mount. Whoever found that link, thank you. You saved me good amount of money compared to the OnCourse device. I highly recommend the horn mount as well. It's just a big chunk of plastic. Billion times better than those flexible ones...those shake like hell.

I noticed also that when my phone is charging, the speaker makes all kinds of noise on this thing. But if I turn the charging off, it goes whisper quiet.

It's pretty much crap as a hands-free device though. The other end always hears echo and stuff. But it's great as phone holder for TomTom use with loud announcements and such. I got the RJ11 to miniUSB and it charges my Holux mini-GPS (keychain type) one fine as well.

So far I'm rather happy with it.
[8525, TyTN, MDA Vario II, JasJam Accessories] over2land:
Anyone use this with the Visiontac Bluetooth GPS?

Its not on either of the lists, and doesn't charge with a regular mini usb plug, some some other unique plug.
[8525, TyTN, MDA Vario II, JasJam Accessories] invictive:
Does anyone know why they say it wont work with a Holux GPS device? Does the unit draw more power? or is the USB pinout different? I'm thinking it should be quite easy to mod the cable if thats all that's holding it back from working properly.

Also on that matter I imagine you could disconnect the speaker internally if you didn't want to use it.
[8525, TyTN, MDA Vario II, JasJam Accessories] vp3G:
If I'm not mistaken, the USB port on the Holux is for serial data only.

Or, easier yet, disconnect the power to the mount. Although, I believe the USB connection also stifles the Hermes speaker as if you'd plugged headphones into it.
[8525, TyTN, MDA Vario II, JasJam Accessories] invictive:
No, I'm pretty sure its for charging, as that is the only port on the device, and I always charge mine in the car or off my pc with a standard USB cable. Heck, it even came with a USB Car Charger...

I may risk it and just order one, I'm sure it can be hacked to work, unless its an issue of not having enough power or something.

I assume that I could also use the USB port to charge my Jawbone Bluetooth headset? No reason why it shouldn't work is there?

Thanks,

-Kai
[8525, TyTN, MDA Vario II, JasJam Accessories] jag121:
Would this mount work with a phone using a silicon case?
[8525, TyTN, MDA Vario II, JasJam Accessories] vp3G:
Buygpsnow.com has live chat and a forum as well, so you could ask them why they say it won't work. I thought it had a proprietary charger interface, but if it's USB... :confused:

What are the output specs of your regular charger? My i.Blue is +5V/0.5A/2.5W.

Here again, can't imagine why not, unless the output isn't sufficient.
[8525, TyTN, MDA Vario II, JasJam Accessories] vp3G:
Not a chance as the phone fits very tightly in the mount.
[8525, TyTN, MDA Vario II, JasJam Accessories] Fourgig:
I have ShieldZone's Invisible Shield on my X01HT and it is an unbelievably tight fit into the cradle. I have to pull so hard on the phone I'm afraid that one of these days, my hand will slip off the phone and break out my windshield. I also almost pull a muscle every time I have to remove the phone from the cradle. :D