yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] catpunt:
i tried to flash r10 over r9 using the play store FKU via the auto-flash boot img. this was clearly a bad idea because it hard bricked my N5.

It won't even boot into fastboot or recovery, but I can get some USB devices to show up in Windows when holding power button + volume down, and power button + volume down / up. but fastboot and adb don't find any devices attached

any ideas how to unbrick?
[Nexus 5 Original Android Development] kman79:
Franco is a beast with these releases!

I'd flash r10 right now, but I'm at work and testing out r8 to see what my real world battery life is with a -50mv UV. Will definitely do it when I get home in the mornings
[Nexus 5 Original Android Development] ptesmoke:
do you see the Google splash screen at all? what do you see when power and volume down? make sure your not just in a bad sod. press and hold power for 15 seconds.
[Nexus 5 Original Android Development] shawnaye:
I gotta ask.

With my gnex, osmosis created a zip to flash prior to flashing a kernel.

Do we need to wipe anything for flashing kernels on the n5?
[Nexus 5 Original Android Development] ptesmoke:
nope. flash away
[Nexus 5 Original Android Development] caribouxda:
I think you did not understand. I said it jumps to 2.3 from 300 and vice versa switching between the 2 cpus. Nothing running in the background. And I know it is franco's hotplug to keep both on when screen on, but from what I remember they would stay at min frequency both when screen on and not touching anything.
[Nexus 5 Original Android Development] :
Franco! The screen calibration is now too blue. The stock color calibration was near 6500k (which is ideal). Hopefully you add an option in FKU to switch back in the future.

The 6500 may seem really warm but most people are accustomed to the cool tones of most mobiles..
[Nexus 5 Original Android Development] zephiK:
He will add it... its just going to take time. Just be patient :good: I personally like the new colors.
[Nexus 5 Original Android Development] snjke.me:
same here... i like them too. good work franco!

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] timvdlinde:
I don't know if someone already asked, because there are 30 new pages with answers. Should system monitor work or not in fku?
[Nexus 5 Original Android Development] carlese:
Man how did you do this magic? 7h21min overnight and lost 3%!
[Nexus 5 Original Android Development] :
http://www.phonearena.com/reviews/Google-Nexus-5-vs-Apple-iPhone-5s_id3480

Check out the display section.

The Blues and reds are perfect, the Green is overblown.

Yeah I'm just trying to help folks. I just bought the app today. I've been a longtime user of the free version. I'm glad I got it.

Again, thanks Franco.
[Nexus 5 Original Android Development] schizophrenia:
check his channel

http://www.youtube.com/watch?v=NnExU45OZSI
[Nexus 5 Original Android Development] Edo 91:
I'm checking this thread every day to see if the 33 nightly was released, can't wait ;)
[Nexus 5 Original Android Development] pitjago74:
I do use last tester 33 and its great so far..Smooth and battery life:thumbup:

Enviado desde mi Nexus 5 mediante Tapatalk
[Nexus 5 Original Android Development] Delacor:
Btw franco, Can I send you a Pair of headphones so you can debug volume Control? I would send it to you..

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] casonswag:
Where can i find the latest test version?

NVM i found it
[Nexus 5 Original Android Development] ironjon:
http://192.241.177.15/Nexus5/4.4/tests/
[Nexus 5 Original Android Development] shaker2k:
Are bluetooth changes kernel level? I've been reading that a few roms have bluetooth fixes and was wondering if Franco has, or is going to implement them?
[Nexus 5 Original Android Development] franciscofranco:
I'm holding off until I figure out why its RAM is filling up that much, but I've been unsuccessful so far.

Debug volume control? You mean the keys in the headphone?
[Nexus 5 Original Android Development] carlese:
Franco what do you suggest, r32 or latest test build to avoid the ram problem?
[Nexus 5 Original Android Development] Enddo:
i would imagine it's a little bit of both. i know franco was talking about doing testing/bug fixing on the sixaxis controller and connecting it to the n5 via bluetooth
[Nexus 5 Original Android Development] dark_ente:
I don't have any ram problem, maybe because I'm using aosp?
[Nexus 5 Original Android Development] Delacor:
Yes, right! I read in some of the Key-control Apps that it is not possible to implement it because of the API?!

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] franciscofranco:
Since that ram thingy only happens on the latest r33 test I suggest you to stick to r32 if you don't want that to happen, although battery life is so much improved with r33.
[Nexus 5 Original Android Development] carlese:
Thanks, I will try the latest r33 for a day and see if the ram problem occurs!
[Nexus 5 Original Android Development] blueren:
So, if I remember correctly, this ram issue want there is the previous r33 test, correct? It was only with the 27th jan edition.
[Nexus 5 Original Android Development] :
Franco , there is no such problem of over filling RAM here , running the latest test33. Flashed it about an hour ago , So I can't say anything on battery life yet , YES the battery graph on idle is a straight line .

Running Omnirom latest nightly
[Nexus 5 Original Android Development] The Gingerbread Man:
Same, no ram issue for me either. I'm sat at 1.2 GB free currently and just been playing worms Armageddon for a while
[Nexus 5 Original Android Development] mendozaram:
Back to r32 because of that RAM thingy... sometimes my N5 went down to 400MB free. Ill wait the stable r33 ;)
[Nexus 5 Original Android Development] franciscofranco:
I wouldn't worry too much about ram usage, it fills up after a couple hours, but it doesn't grow more than 1GB or something, I'm sure there's a memory leak somewhere or the pages are not being cleared, but I'm gonna hold on the release until I find out why this is happening. I asked myfluxi if he knows why so maybe he also finds the problem first. We'll see, its no big deal at this point.
[Nexus 5 Original Android Development] baedaa:
take your time. we apreciate this kind of perfection :)
[Nexus 5 Original Android Development] shaker2k:
Okay I am running stock plus gravity box. And I am having a situation where I when someone calls me I have to turn my bluetooth off and on to clear up the distortion . So what I am wondering if this is the ROM problem for kernel problem?

Thanks
[Nexus 5 Original Android Development] kmakiki:
Hey Franco, out of curiosity, what did you change to make battery life so much better? I haven't had a chance to parse git yet, but do you have a summary for all us curious boys and girls?
[Nexus 5 Original Android Development] ivan08v:
At long long term there is a leak of memory like said, i must reboot the device to multitask like ever, its expected for a test build :thumbup: battery seems to behave better on idle, with higher voltages

Enviado desde mi Nexus 5 mediante Tapatalk
[Nexus 5 Original Android Development] jb0ne:
[MENTION=3292224]franciscofranco[/MENTION]

Had just installed r33 1/27 an hour or so prior. Plugged phone in to charge and got instant kernel panic and reboot. Have not been able to reproduce. Sorry about using pastebin, pastie acting weird and won't give me a URL:

http://pastebin.com/Zc97cWxE

Edit: Nexus 5 stock 4.4.2 w/ xposed and Gravitybox latest. Also running System Monitor pro w/ Battery service, and "Custom Auto Brightness" which replaces the screen auto brightness service.
[Nexus 5 Original Android Development] LibiSC:
Maybe this one... https://github.com/franciscofranco/hammerhead/commit/94329bc6c2516eddbf4ccb9df75768d6a65a154f

Its annoying cause last version of viper needs to be as user app for the irs to work properly and when there's less memory gets killed more often :eek:
[Nexus 5 Original Android Development] nexusmaniac:
[MENTION=410271]fransisco[/MENTION]franco My RAM usage with r33 seems to be very bad, it gets to 70-75% usage and then my phone becomes unresponsive, it randomly exits apps, the launcher kind of crashes (it just goes grey/black and kicks me back to page 1 of the home screen if I try to open the drawer or an app) the back button stops working and the keyboard doesn't open. (I'm not complaining before anyone says anything :) ) but I'm just posting my problem to stop it from happening to anyone else. Is there a log I can post? kmsg? or logcat? I'm using stock kernel settings and am on stock ROM. Thanks r33 is really incredible for heat and battery much better than r32 (except for the ram issue). A reboot fixes the problem but only for a few hours/ day

edit: I can't reproduce this, it's completely random, no processes are eating much ram either.
[Nexus 5 Original Android Development] LibiSC:
Truth...but thats after a while...reboot fixes it... I noticed it while playing games
[Nexus 5 Original Android Development] Technecium:
For what it is worth, I am not having issues with RAM. I am on the latest test and never noticed any issues with previous releases. Someone else mentioned AOSP and I am on AOSP too. It is quite stripped down and I have only a few Google related apps installed. I have tried to fill up the RAM by opening multiple browser tabs, open as many apps as I can but I show no sign of anything unusual.

Edit: After getting about 60% full had no issues switching between apps. Swiped the apps away and memory cleared out as expected.

Sent from AOSP koeMod 4.4.2 w/ Franco kernel
[Nexus 5 Original Android Development] Enddo:
if you're on stock ROM and getting this bug then i would imagine it's the kernel that is causing the issue. but i could be wrong.

the test you should do is to flash the stock kernel. if this doesn't happen with the stock kernel, then you can report the bug here and franco could try his best to replicate the bug with your step by step instructions.
[Nexus 5 Original Android Development] PresidentMcCain:
I'm at 680 MB free after 2 days on the latest test33. Definitely a memory leak in the kernel somewhere which isn't present in r32.
[Nexus 5 Original Android Development] casonswag:
I had found it earlier
[Nexus 5 Original Android Development] ironjon:
I can't notice any problem with ram in latest r33, is faster with amazing battery life.

I really enjoy it
[Nexus 5 Original Android Development] Alaris:
Does USB fast charger damage the battery at all?
[Nexus 5 Original Android Development] lolpok:
No.
[Nexus 5 Original Android Development] Alaris:
OK thanks so you recommend turning that setting on then? Sorry new to the whole kernal thing.
[Nexus 5 Original Android Development] abdel12345:
That's only for charging through your computer port. If you don't charge with a computer then there's no point in it because it turns off file transfer while it's on

Sent from my white LG Nexus 5
[Nexus 5 Original Android Development] Alaris:
Ok thanks for clearing that up for me
[Nexus 5 Original Android Development] pidocchio:
I don't have any RAM issue with latest r33, just had one hard reboot

last kmesg attached
[Nexus 5 Original Android Development] DerItaliener:
For me File Transfer works with Fast-Charge activated. AFAIK this was possible since it has been implemented on this device. :)

So, no point in turning it off at all. :D
[Nexus 5 Original Android Development] eluspo:
Went back to r32, memory leak in latest test is just too much for me. Its affecting my multi tasking.
[Nexus 5 Original Android Development] pidocchio:
The spec for the battery is 3.8V (+/- 0.5V) at 500mA-1500mA (completely going by memory, maybe I have something wrong but it's really not important.

So what does this mean? This means that the source can provide a voltage as low as 3.3V or as high as 4.3V without risking damage to your device. While providing these voltages, it must push 0.5 to 1.5A in current. The way electricity works, if you try to pull too much amperage, then your voltage drops. So if the USB Port isn't capable of pushing 1.5A but the devices tries to pull it, it may actually receive 1.5A but at less than 3V. This is a HUGE problem both for the phone and for the USB port.

Why is this a problem? This means that in order to keep either the phone or the USB port from being damaged, you are relying 100% of the time on failsafe devices to protect them. While this may sound fine (I mean, what are failsafe devices for anyways?), in reality it's not. Failsafes are designed for emergency situations and not for ongoing use. I mean, could your Sedan tow a broken-down pickup truck 400 feet to get it in your driveway? Sure. Do you really think that same sedan could get 200k miles while pulling the pickup truck every single one of them? No way!

Not counting wiring problems on USB ports :(
[Nexus 5 Original Android Development] DerItaliener:
Thank you very much for your detailed explanation. I thought there was a protocol in the USB Standard where the devices negotiate about the current to avoid the problems described by you. Don't they get applied with USB fast-charge enabled?
[Nexus 5 Original Android Development] pkelly517:
Wow.

The amount of wrong information in this post is amazing.
[Nexus 5 Original Android Development] melbourne408:
I like twurtles!
[Nexus 5 Original Android Development] pidocchio:
Well, then just explain it.

I'm not an electronic engineer, just a computer one :D

Anyway, I just found a really interesting article, http://www.maximintegrated.com/app-notes/index.mvp/id/4803.
[Nexus 5 Original Android Development] LibiSC:
The amount of reasons of why is the amount of wrong information in the other post amazing is dissapointing
[Nexus 5 Original Android Development] flushell:
With latest CM nightly (cm-11-20140129-NIGHTLY) for my hammerhead installing R32 will render my phone unbootable! It is stuck on the boot screen with the Google logo. I was able to restore with adb. There is nog error-message. I tried both the .img (via the app) and the .zip (via TWRP) file, both times phone stuck in boot-logo. Cleaning cache / dalvik did not solve the problem.

EDIT: I did read a few pages back, but not enough. Sorry. Thanks fredfox_uk
[Nexus 5 Original Android Development] melbourne408:
It's this simple, if you want to run the risk of damaging your phone you can enable it.

To say that the implementation isn't right, wrong.

You have to be contentious.

Know how to turn things on and off.

For this reason, since my captivate, my n4 with that dam buzzing charger.

I only use the stock charger plugged into the wall to charge my devices.

Won't be turning on fast charge anytime soon.

That's just my experience.
[Nexus 5 Original Android Development] fredfox_uk:
Yes, been like that for 2 or 3 days now, it is mentioned a couple of pages back.
[Nexus 5 Original Android Development] pidocchio:
I didn't say that the implementation is wrong, I just said that it could be dangerous to use it on the long run. ;)

The implementations is simple, it just forces the IC charger to asks for a given amount of current when it detects a USB port. Nothing more, nothing less.

It's like a table:

Stock -> USB detected, use 500mA

Fast charge on -> USB detected, use 1200mA (or 900mA i just don't remember)
[Nexus 5 Original Android Development] melbourne408:
It's this simple, if you want to run the risk of damaging your phone you can enable it.

To say that the implementation isn't right, wrong.

You have to be contentious.

Know how to turn things on and off.

For this reason, since my captivate, my n4 with that dam buzzing charger.

I only use the stock charger plugged into the wall to charge my devices.

Won't be turning on fast charge anytime soon.

That's just my experience.

(Edit: Back to OT )

How's everyone liking the new PA Beta 04 alongside r32?
[Nexus 5 Original Android Development] krazeecracker:
Franco has been using fast charge since the beginning. I highly doubt this would cause any long term damage.
[Nexus 5 Original Android Development] LibiSC:
In fact no more harm than charging it with the wall charger
[Nexus 5 Original Android Development] ironjon:
Anyone with ram problem is using ART?
[Nexus 5 Original Android Development] pidocchio:
Most wall chargers have an output of 5V@1A (the original N5 charger is 5V@1.2A)

The SDP (Standard Downstream Port) USB port has an output of 5V@0.5A

That's not quite the same ;)
[Nexus 5 Original Android Development] EnricoTFYKD:
Yes but it's more theory than practice. In fact, most of the USB ports are capable of supplying well over 0.5A, usually up to 1A-ish is totally safe. It's common practice, in order to cut the production costs, to connect 2 ports in parallel to a single power rail, and in order to meet the standard, this power rail is able to supply at least 1A.
[Nexus 5 Original Android Development] cavolo:
The only differences between the wall chargers and usb is the amount of ampere that is provided. And without fastcharge, the phone will be charge with 0,5A with usb instead of 1,2A with wall charger, it only be longer to charge. Nothing dangerous.

If you let your phone to take the max of your usb port (idk how many it can be, I dont use it). Your n5 will only charge more faster than without fastcharge... Just if you are anxious, dont charge with more ampere of the stock wall charger...

E: sorry if I dont write well, english isn't my main language.
[Nexus 5 Original Android Development] pkelly517:
The article you quoted appears to be pretty useful, although I didn't do much more than skim it.

The USB charging voltage is 5V. That's already more than 4.3V.

The maximum current available from the port is determined by the source, not the load.

If the load only requires 100mA, then the source will only provide 100mA.

You still have the same 5V source, regardless of whether the current is 100mA or 1.5A (assuming the source can provide the current).

I have no idea what the whole failsafe thing was about.
[Nexus 5 Original Android Development] javacody:
My PC motherboard has a fast charge feature that enables higher amps on the USB ports. I'm betting a lot of motherboards have this feature.
[Nexus 5 Original Android Development] AGiLiT:
Forgive me for going OT and asking a kernel-related question, but I'd like some advice on how to best analyze a problem that occurred on my phone. :silly:

I'm currently on rr32, no config changes, and stock ROM. I was doing some testing to determine the battery utilization under different conditions while playing music. The tests were all done with Google Play and the same album. I pretty much just started the play and put the phone down with scren off. The only other processes that would have been running during the test were email syncs. I use BBS to monitor the results.

In most of the tests (details down below), the utilization was around 5%/hr. In one test, the utilization was 23% in one hour. When I looked at CPU states, the phone was at 2.27GHz for 40m out of the hour. I rebooted the phone and repeated the test and the utilization was back in line with the other runs (3%/hr and 58m at 300 MHz). In both cases the only significant wakelocks were Android.Media.Player.

So: any idea of what might have been going on? I have the last_kmsg after rebooting if there would be any value in it. Any way that I would have been able to tell something wacky was going on at the time?

For those interested, here are the results of the test:

Streaming via. LTE, output via. BT, no EQ in Google Play: 1h 1m of usage; battery 5%/hr; Wakelocks - MediaPlayer = AudioMix 1782 seconds.

Same as above with EQ on: same battery utilization (maybe .1% more? couldn't be sure if it was statistically significant without more testing.)

Same as above, except streaming over Wireless instead of LTE: Battery 6%/hr.

Streaming on LTE, BT off, output to headphones: Battery 4%/hr.

Playing from device, BT off, Airplane mode; output to headphones: Battery 3%/hr. (This is the situation that gave me the wacky results the first time).

I intend to do a few more tests with a different music player app and with Viper to see the impact, but it will take me a couple of days to get to that. Work is interfering with the more important things in life right now. If there seems to be interest, I'll post the results when done.
[Nexus 5 Original Android Development] FAdrums:
r33 test on stock with xposed (Gravity box & Greenify): so far so good.

Tapatalked from my Franco Xposed Gravitational Hammerhead
[Nexus 5 Original Android Development] Cheater912:
Getting wakelocks with r33 consistently a few minutes after boot. I switched back to r32. Is there any way to get a log without flashing r33 again? I'm undervolted by 25.
[Nexus 5 Original Android Development] Technecium:
I've not had any problems.

Sent from AOSP koeMod 4.4.2 w/ Franco kernel
[Nexus 5 Original Android Development] drakester09:
I did have the RAM issues and was using ART

It's unrelated to the runtime.
[Nexus 5 Original Android Development] Pete182:
Having trouble getting a gps lock for navigation. Would this be kernel related?
[Nexus 5 Original Android Development] Technecium:
I've done similar testing and the results were about the same. What exactly was causing it I don't know, but it is related to the way the kernel handled audio. This I know, for some reason the processing of audio was processed by the cpu instead of the hexagon QDSP6V5A in the soc. I also could not determine why the cpu went so high, mine would not go as high as 2ghz but usually around 1.7ghz. That is the bad news.

The good news is that Franco has fixed it in the latest test, 33. If you switch to 33 and do your tests again you you will see the cpu doesn't jump to the higher speeds.

Sorry I didn't answer your question about what exactly causes it, but the issue has been fixed.

I have been able to go 6-8 hours with PowerAmp, wifi on, auto-sync enabled and the device never went over 300mhz.

Sent from AOSP koeMod 4.4.2 w/ Franco kernel

---------- Post added at 10:04 AM ---------- Previous post was at 09:51 AM ----------

Can you try this? Check ram usage with System Monitor. Then open recent apps list. Swipe two or three of your apps away. Check ram usage again and see if the usage dopped.

600 free doesn't sound unreasonable after 2 days if you have many apps in your recent list.

After closing all in my recent list my system shows around 700+ used.

Sent from AOSP koeMod 4.4.2 w/ Franco kernel
[Nexus 5 Original Android Development] franciscofranco:
If you're getting wakelocks then you have apps acquiring them, there is absolutely no change in that regard between r32 and r33...
[Nexus 5 Original Android Development] PresidentMcCain:
I always clear out recents apps list before turning off the screen.
[Nexus 5 Original Android Development] Xsabre:
I'd like to thank Franco's kernel and Vomer's setting for breaking my battery.

It been over two weeks that I repeatedly get 2 (+/-hr) days on a charge. My

usage pattern is very similar to Vomer so your mileage may vary.
[Nexus 5 Original Android Development] Cheater912:
Could that happen just by changing kernels? Apps are still the same.
[Nexus 5 Original Android Development] Tonster1983:
Hey, where did you find these settings of Vomers??? Id love to get 2 days on a charge as well :D thanks man!
[Nexus 5 Original Android Development] franciscofranco:
Doesn't really matter if apps are the same, there are a gazillion variables that can trigger a wakelock in apps, depends on how they coded the wakelock release, acquire routines, etc etc. TL:DR: its not black & white.
[Nexus 5 Original Android Development] jb0ne:
The new r33 is amazing on battery life but the memory leak is bad. After six hours of fairly intense but intermittent use my ram with no apps running was 1.6gb in use. My battery was only 69% though.
[Nexus 5 Original Android Development] krazeecracker:
Are you running stock settings or using vomers?
[Nexus 5 Original Android Development] jb0ne:
I'd love to know what vomers are.

I'm -75mv on all but 300mhz@675, top speed locked to 1.7ghz. Stock with xposed + gravitybox and system monitor running.