yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] pseudoheld:
had to revert back to r32 because r33 and r34 give me bluetooth issues.

my pebble keeps getting disconnected without my phone or pebble actually noticing it. i just stop getting notifications. have to turn off my bluetooth and turn it back on again to get it working.

r32 seems to not have this issue so thats what im sticking with atm
[Nexus 5 Original Android Development] djmcnz:
I appreciate the informative response even though I was aware of this. It's not a solution, it's a correction. Logically no terminal commands should be required to tune a kernel to behave properly.

If Franko wanted his kernel to act abnormally he'd make that claim. He doesn't.

There's clearly a case for him to investigate further as evidenced by the hordes of recent complaints about this function.

I'm not sure why so many people are jumping to defend an untenable argument, there is clearly a regressive change in the default settings and this needs to be investigated and understood. Where's the harm in this?
[Nexus 5 Original Android Development] WettbackMartyr:
Regarding the latest FKU beta. I cannot seem to get the zips download directory path I enter to stick.

1) cannot manually type in directory (keyboard won't pop up)

2)following "hint" and long pressing to select directory does not seem to work

3)copied and pasted directory path from note application (cause keyboard won't pop up within FKU) and the entered path will not stick when tapping apply.

Obviously this is a beta release so there will always be issued and this one is incredibly minor. Just doing my testing duty and reporting none the less. Other than that all seems well!

As always thank you Franco!
[Nexus 5 Original Android Development] djmcnz:
Do the XDA links under 'Support' work in the new beta?
[Nexus 5 Original Android Development] @wells:
as I said I am usually not no this kernel and don't want to make this fight between senior member and recognized developer. I just tried the kernel to see what's the fuss and couldn't notice any regression.. sorry if I jumped in, I just expressed my opinion and I appreciate yours. over & out!
[Nexus 5 Original Android Development] WettbackMartyr:
They do.

To edit my previous post, after fiddling around a bit I was able to get the keyboard to pop up when entering app download directory by swiping up at the point of text entry. The value entered still does not save when pressing apply however.
[Nexus 5 Original Android Development] vomer:
FYI- Franco ninja pushed a beta app update.

Looks like changes were made to per app mode. Had to RE load settings

Sent from my Nexus 5
[Nexus 5 Original Android Development] bigbiceps:
I'm not sure if its placebo , but my Bluetooth audio sounds awesome !! And r34 feels solid ,smooth, easy on battery & the best till date. (Hated 33 for all the lag and ram leaks).

Thanks Frankie. ??
[Nexus 5 Original Android Development] Ris84:
I am finding that my Nexus 5 is charging very slowly after update rom and kernel. I`m on Android Paranoid 4.1 BETA 2 with franco r34. Does anyone have the same problem? Any solution?
[Nexus 5 Original Android Development] Enddo:
this happened to me once with Cataclysm and all i had to do was do a reflash of the ROM. i chalked it up to a bad flash of the ROM
[Nexus 5 Original Android Development] Ris84:
Thanks, i will try now re-flashing rom. :)
[Nexus 5 Original Android Development] bradputt:
Happened to me too, it would start charging fast but after a while it will become slow again.

After a few charging cycle it became normal.

Btw I was on AOSB (a CM based rom) and was suffering from the screen flicker and right audio glitch

But after I change to aosp rom (PA) I don't have any of these issues.

Maybe it's because of the ROM?
[Nexus 5 Original Android Development] Tzfardaya:
It has been noted before, has to do with how well your device handles the extremely low backlight settings. Franco himself figures that the variation in how devices handle the low light setting may be the reason why google set the lowest backlight so high in the first place...

I asgree, nothing is wrong with the feature, problems are with how the device handles the feature... mine blacks out completely on lowest manual brightness setting,,, (so I don't use it..)

Actually, check back through the posts to when r34 was first pushed, lots of back and forth with franco about it.. supposedly there is a toggle switch to enable/disable the brightness settings coming in fku... The harm comes from people not reading older posts/searching and muddying the situation with demands/requests to fix something that was previously discussed upon and are just waiting for the implementation.

Work for me...
[Nexus 5 Original Android Development] harshalkatakia:
I'm on stock and it happened to me. Thought it might be the charger, but it took wayyyy too much time to charge.
[Nexus 5 Original Android Development] deepakanand:
Just flashed r34 and feeling the difference straight away. Facebook scrolling and whatsapp contact list scrolling was never so smooth before. Loving it so far :good:
[Nexus 5 Original Android Development] FlorinXstyle:
To correct autobrightnes.
[Nexus 5 Original Android Development] vomer:
[MENTION=3292224]franciscofranco[/MENTION] what/how do we maunally change voltage values in this kernel? tried a bunch of commands but was unsuccessful :eek:
[Nexus 5 Original Android Development] bigknowz:
Voltage

check /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
[Nexus 5 Original Android Development] KuChar_:
[MENTION=3292224]franciscofranco[/MENTION] where are you? Come back to us :D
[Nexus 5 Original Android Development] Tzfardaya:
Yes... [MENTION=3292224]franciscofranco[/MENTION], just a reminder you did say you would give us a posting with all the tunable files/paths. :P
[Nexus 5 Original Android Development] vomer:
no, I don't mean the location ... I mean the command.

Also, I believe the right path is : /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
[Nexus 5 Original Android Development] educk:
Here are some of them:

https://github.com/erik96/android_qcom_device_info/blob/master/source/constants.h
[Nexus 5 Original Android Development] Tzfardaya:
I'd say still out with his young lady....
[Nexus 5 Original Android Development] vomer:
Really useful! thnx :good:

edit" looks like some of those are wrong... eg. vibrate path is wrong
[Nexus 5 Original Android Development] educk:
Have you tried:

echo <freq>: <vdd>

Hmm...it should be OK: (see attachment)
[Nexus 5 Original Android Development] vomer:
Ya I tried that, but the way the UV table is setup is:

300mhz: 775 mV
422mhz: 775 mV
652mhz: 795 mV
729mhz: 805 mV
883mhz: 825 mV
960mhz: 835 mV
1036mhz: 845 mV
1190mhz: 865 mV
1267mhz: 875 mV
1497mhz: 910 mV
1574mhz: 925 mV
1728mhz: 955 mV
1958mhz: 995 mV
2265mhz: 1050 mV
2419mhz: 1065 mV
2572mhz: 1080 mV
2726mhz: 1095 mV
2803mhz: 1125 mV
2880mhz: 1150 mV
3014mhz: 1175 mV

not sure how we can echo for multiple changes?

Also for amp - Strangely... timed_output does not have those files for me. :eek::eek:
[Nexus 5 Original Android Development] daniel84cs:
Franco great work R34 with purity ROM is The best combo....
[Nexus 5 Original Android Development] Tzfardaya:
No, I do t think so... That vibrate path/file does show what I have set in fku....
[Nexus 5 Original Android Development] MrThreeChains:
Wow my battery life is over the roof. Best i had so far!
[Nexus 5 Original Android Development] Tzfardaya:
I believe each Freq will need it's own echo...

Try
[Nexus 5 Original Android Development] vomer:
Tried it, but it caused a reboot

echo "freq mhz: voltage mV" > file

echo "freq mhz: voltage mV" >> file (for appending)

That's why I was wondering if there was another way
[Nexus 5 Original Android Development] lolerpro8:
Well that is the setting file of freq and mV, so tht is the only way. But why dont use franko app or some else for that use..
[Nexus 5 Original Android Development] Tzfardaya:
Interesting.... I echo 300mhz: 750mV and it sets the 400mhz step to 750 instead....
[Nexus 5 Original Android Development] vomer:
Just curious on how to do it manually for init.d integration
[Nexus 5 Original Android Development] Tzfardaya:
Oh, we do, we are just trying to learn beyond the app....
[Nexus 5 Original Android Development] Technecium:
You don't need to enter the mhz, only the numerical value of the freq. Starts at 300 then 422 etc. You should end up with 20 entries, lowest mhz to highest mhz.

echo "600 600 750... [17 more] " > file

koeASOP 4.4.2 w/ Franco kernel + F2FS
[Nexus 5 Original Android Development] franciscofranco:
Hey guys. Back from the weekend getaway with my GF. r35 is ready with increased minimum brightness, it was definitely too low on r34, and obviously other misc patches from CAF (though not so many, just fixes). Kinda waiting for the next Android release at this point (being it incremental or am entirely new release).

Just testing a bit more and I'll release.
[Nexus 5 Original Android Development] Tzfardaya:
Welcome back. Enjoyed the mini vacation I hope?
[Nexus 5 Original Android Development] vomer:
I don't think that would be correct... the file's content structure would change :confused:
[Nexus 5 Original Android Development] franciscofranco:
Yes, brain batteries recharged!

Its correct, you just need to input echo 600 600 600 600 etc > uv_mv_table.
[Nexus 5 Original Android Development] vomer:
That simple?! now I feel stupid trying to do find and replace commands lol

will try now!
[Nexus 5 Original Android Development] educk:
Ahaha..it was definitively not that easy on my old Samsung, but the VDD implementation was a bit different though...
[Nexus 5 Original Android Development] Technecium:
latest commits in staging?

koeASOP 4.4.2 w/ Franco kernel + F2FS
[Nexus 5 Original Android Development] Tzfardaya:
Brain batteries recharged, other battery is completely drained? :angel:
[Nexus 5 Original Android Development] vomer:
PSA: VomerTweaks has been updated with some new features :) pls re-download/apply the latest file

---------- Post added at 01:02 PM ---------- Previous post was at 01:02 PM ----------

LMAO "other battery" :silly:
[Nexus 5 Original Android Development] Red5:
Thank you. So if r35 is good, then will that be our last release for awhile until Google decides to push something out? Not complaining, just curious.
[Nexus 5 Original Android Development] Woody:
The battery life on 34 is really unparalleled. Even the latent drain overnight is something as well. Only problem that I had (notice tense there) was redraws. All fine until I got one and then after that they were every time I backed out off an app. I wiped cache and a simple reboot here and there, but once I got one it was a cascading effect until I either rebooted or cleared cache.

Sucks because 34 is really a fluid kernel (aside from the auto-brightness which I don't use and BT which I use very sparingly). No UV at all and just using stock kernel settings. Had to go back to 32 for the time being. Even tried to put Apex in memory and still redraws. Sadpanda.jpg
[Nexus 5 Original Android Development] Tzfardaya:
[MENTION=3292224]franciscofranco[/MENTION], any thoughts on what might be causing the bluetooth le disconnects? (primarily seen with those who have Pebble smart watches)
[Nexus 5 Original Android Development] vomer:
I think r35 should have some fixes for the ram problem. Franco mentioned he was going to roll back on CAF stuff to see where the problem came from :good:
[Nexus 5 Original Android Development] Woody:
Resident RAM is not an issue as it seems like the memory leak is gone (I hover around 700+/- if I am doing nothing). Literally the only thing wrong (for me) is the launcher redraws. Everything else is perfect for my daily use. Will wait for 35, but regardless I am quite happy with what I have for the time being.
[Nexus 5 Original Android Development] Red5:
Ive noticed that everytime I use the camera, thats when my memory problems start to happen. Yesterday I started getting redraws about 4-5 hours after using the camera and saw that I was using 1.3GB of space. I rebooted and everything has been fine. I can go days and my memory is fine, but as soon as I fire up the camera app, thats when my memory goes bezerk.

I know the camera bug isnt kernel related... its a Google problem and they are working on it. Having said that, if you take that out of the equation, this kernel is still awesome and should not be overlooked.
[Nexus 5 Original Android Development] nerotix:
[MENTION=3292224]franciscofranco[/MENTION] New release of android? that can take quite a while or what? or are u not sharing something?(A)
[Nexus 5 Original Android Development] harshalkatakia:
Any changes in the tunables? I checked the pastebin link, but nothing seems to be changed.
[Nexus 5 Original Android Development] Tzfardaya:
Well.. Google i/o is coming up (june) and that's where Google traditionally release the next full version of Android.. And there is the camera bug/background service bug fixes in the works....
[Nexus 5 Original Android Development] pchtc:
I think he is talking about KVT49L which right now was only released for nexus 7 2013 LTE

---------- Post added at 02:26 PM ---------- Previous post was at 02:22 PM ----------

funny you should mention that

just finished a family vacation where i used my n4 (didnt want anything to happen to the n5)

and im just realizing now that the n4 never had a single bt disconnect

but now today back at work with n5 getting a few throughout the day

worth mentioning, my n4 has the same stock kk rom and the newest franco kernel
[Nexus 5 Original Android Development] Zyphur:
[MENTION=3292224]franciscofranco[/MENTION] [MENTION=1363323]vomer[/MENTION]

This is absolutely disgusting. Stock rom, r34, vomer settings. 6h 45m SOT. http://imgur.com/ibvieoY,rvrkZ8r,4jAdaIz#0

Entry that got cut off by volume slider fail was screen at around 46%. Only entry cut off is standby at 2%.

I turned my phone off while I slept, it was at 3%. I turned it on, it was at 9%. Not sure how that happens but okay?

PS: How do I make pictures show up as attachments so they don't take up half the page?
[Nexus 5 Original Android Development] vomer:
Love these nasty results ;) :p

---------- Post added at 02:29 PM ---------- Previous post was at 02:29 PM ----------

Nope, not yet. Voltage changes to lower steps + vibration amp changes :good:
[Nexus 5 Original Android Development] harshalkatakia:
Possible to see them in a file or something? For those of us who prefer doing things manually :)

EDIT: Or you could just edit some settings with new incoming r35 and post them later once you're done testing the settings out.
[Nexus 5 Original Android Development] vomer:
yup that's always an option :good:

---------- Post added at 02:39 PM ---------- Previous post was at 02:38 PM ----------

Link to the original image within IMG tags:

[IMG]http://i.imgur.com/ibvieoY.png[/ IMG]
[Nexus 5 Original Android Development] Tzfardaya:
That's the new patent pending [MENTION=3292224]franciscofranco[/MENTION] wireless air charger at work...

Only way I've found is to open them in an image editor and resize them before linking them here...
[Nexus 5 Original Android Development] vomer:
I heard it absorbs moisture from the air to convert it to energy and then fuels the cells inside the phone. Some next level ****! :p
[Nexus 5 Original Android Development] ConMcCRay:
R34 is KILLING it. Thank you Franco!
[Nexus 5 Original Android Development] Tylog:
Thx for your Balanced Profile Vomer , I really like it :)

Tapatalk Team SlimRoms
[Nexus 5 Original Android Development] fbf2201:
I don't think it's only bluetooth le, but a general bluetooth issue.
[Nexus 5 Original Android Development] vomer:
Glad you do buddy :) always great to hear feedback :highfive:
[Nexus 5 Original Android Development] BRiANj64:
Some bluetooth issues are a ROM issue. I think PURITY fixed bluetooth problems in 9/3
[Nexus 5 Original Android Development] Tylog:
Sure , a please and a thanks is the least that one should say when like anybody's work :)

Tapatalk Team SlimRoms
[Nexus 5 Original Android Development] fbf2201:
I use stock...
[Nexus 5 Original Android Development] chikimonke:
Yeah, I just got my Pebble and this issue has caused my to stop using the kernel for the time being. I get zero disconnects using the stock Slim kernel and Faux, so it seems that it points to something in this kernel. [MENTION=3292224]franciscofranco[/MENTION], I know you've said in the past that you don't touch the BT stuff for your kernel, so I have to imagine it's something else inadvertently causing the issue. Is it possible one of the CAF power management merges is putting the BT in a low power state or something? Maybe it's not compatible with BT LE and therefore it doesn't think there's enough activity to keep the connection fully active? But then as soon as it drops, the watch speaks up again and BT is powered back up? The disconnects seem to happen during longer periods of inactivity, which is what's leading me to my rambling hypothesis. I'll load up r34 again and see if I can get a log of the disconnect. Tzfardaya, you should too.
[Nexus 5 Original Android Development] chazall1:
Purity Rom 3/9 has improved many of the bluetooth issues that were occuring. Much better with the new Rom!
[Nexus 5 Original Android Development] carlese:
Didn't change anything actually.. The problem is in the kernel, sorry to say it.. After the first connection it won't connect to my car system (new seat leon).. Reverted back to r32 and everything works like a champ! It's a shame though since I think r34 is a bit better.. Hope franco finds a solution!
[Nexus 5 Original Android Development] PhantomGamers:
So it reconnects immediately? I have an original Pebble Smart Watch running the latest 2.0 firmware and I haven't seen any disconnects, I check it periodically throughout the day and it's always connected to BT and I always get notifications as expected... Is yours (and Tzfardaya's) fully updated? I know you said that other kernels don't have this problem but maybe something was changed in 2.x that affects BT behavior to help this.
[Nexus 5 Original Android Development] chikimonke:
I have had a Steel for about a week now, and it's run nothing but the 2.X firmware. The disconnect and reconnect will be back to back and I don't think I've ever missed any notifications because of it. I just get the to vibrations back to back on the watch with no notifications to speak of.
[Nexus 5 Original Android Development] Tzfardaya:
Heh, I'd grab logs if I could, but I don't have a BT le device... (my Pebble is still about 7 weeks away from arrival). I just said earlier I'd bring the issue up with Franco when he got back... :P

No issues with my current crop of BT devices... Gps, obd2 adapter, radio dangle...
[Nexus 5 Original Android Development] Ben36:
I tried sending some pics by Bluetooth and it just stopped at 32% and would not carry on or exit or anything. Had to reboot to sort it out
[Nexus 5 Original Android Development] Kpoch:
I got a reboot using Stock, ive downloaded comer lastest settings, i was at playstore this os the log why my device got rebooted

https://www.dropbox.com/s/mgekzx7equgiggz/last_kmsg. This os my last kernel panic

Enviado desde mi Nexus 5 mediante Tapatalk
[Nexus 5 Original Android Development] hounter17:
Why is not compatible francos kernel with the latest carbonrom nightlys?? Someone knows??
[Nexus 5 Original Android Development] chikimonke:
[MENTION=3292224]franciscofranco[/MENTION] On the latest FKU beta, I can't seem to set the download path. I've tried long pressing everything I can think of, and nothing seems to be sticking. Can anyone else confirm this?
[Nexus 5 Original Android Development] ChazzMatt:
Because carbon went CAF?

_______

Sent from my Nexus 5 (LG-D820)
[Nexus 5 Original Android Development] pkelly517:
In the update I got a couple hours ago,

App Settings -> ZIPs download path -> (short click at flashing bar.... File Manager!!)

Yay! Even though app says use long press.

edit: ack! spoke too soon. Can't get it to pick a directory.

edit again: Pick a file in the directory. Long press on the name that comes up to delete the name of the file. The directory remains. Note that the directory is used correctly, but doesn't show up next time.
[Nexus 5 Original Android Development] chikimonke:
I get that too, but when I select the folder I want, it just opens it, and I haven't been able to actually set that folder. If I just hit back, nothing stays selected.
[Nexus 5 Original Android Development] b3ndik:
Will r32 work with CM11 M4? Or do I have to use an even older version? Did some searching, but couldn't really dig up an answer.

thanks
[Nexus 5 Original Android Development] gee2012:
Dude realy, Franco kernels are NOT compatible with CM11 atm. Its written in BIG red letters in the OP :(
[Nexus 5 Original Android Development] @wells:
it shouldn't and not even any older version as stated in first post.

Sent from my Nexus 5
[Nexus 5 Original Android Development] pkelly517:
See my edits above.

It's not just an app, it's an adventure! :)
[Nexus 5 Original Android Development] SedyBenoitPeace:
Great! However do you think to look into the audio problems? (glitches or headphones that stop working), your kernel is really great....i know that i can reboot when i have the audio problem but it really bothers me when i need to listen music only for 10 minutes or so!
[Nexus 5 Original Android Development] b3ndik:
Since it said atm i thought it was just the newer versions. My bad.
[Nexus 5 Original Android Development] Zyphur:
Not kernal related, but how do I change the toggles in the secondary task bar (the squares)? :P
[Nexus 5 Original Android Development] kenkiller:
Not on stock, that's for sure.

Xposed with gravitybox mod might help.
[Nexus 5 Original Android Development] PhantomGamers:
Ah right there is a vibration when it dcs, so I definitely don't have that problem as I haven't had any vibrations not associated with a notification or alarm.
[Nexus 5 Original Android Development] shreddintyres:
Is carbon ROM caf or cm based? IIRC it is hence read the banner at the beginning of the op if you need further explanation please search for cm or caf in this thread, there is simply too much to be said for me to explain it all.

Happy reading :)

-Cheers
[Nexus 5 Original Android Development] Tylog:
Carbon switched to Caf since a few days , more I don't know, not really interesting for me :)

Tapatalk Team SlimRoms
[Nexus 5 Original Android Development] chikimonke:
That all said now, I've been going the whole day on r34 and haven't had a disconnect. The most recent weekly from Slim did have a lot of BT merges this week so maybe it was ROM + Kernel related? Still not sure why it was fine on Stock Slim kernel and Faux, but not on Franco. We'll see what happens after I connect to my car's BT simultaneously, I feel like that may have been a trigger in the past too.
[Nexus 5 Original Android Development] The Gingerbread Man:
Latest beta fku version, anyone else finding their min CPU speed has increased on its own for no reason? Iv caught min at 1036mhz twice now.
[Nexus 5 Original Android Development] PetritH:
Did you try clearing FKU app data bro ? Sometimes I do it after update when strange things happen :)
[Nexus 5 Original Android Development] aow1980:
I've had it happen a couple times the past week. It's almost like per app mode doesn't disengage. I'm keeping an eye on it to see if I can duplicate it.
[Nexus 5 Original Android Development] omvir:
Yes I've seen this happen with per app modes, sometimes my per app modes service will die leaving the per app settings to stay as the default.
[Nexus 5 Original Android Development] fugn:
mine was different as well
[Nexus 5 Original Android Development] neriamarillo:
As some said I've had it happen with the per-app-modes but it's not something constant. It happens randomly. I haven't been able to actively reproduce it.
[Nexus 5 Original Android Development] Tzfardaya:
enough with the teasing already!! :P

patiently waiting.

patiently waiting..

patiently waiting...

patiently waiting....

patiently waiting.....

impatiently waiting

patiently waiting

impatiently waiting

patiently waiting...

GAAAAAAAAAAAAAAAAAAAA can't wait anymore!!! :P