yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] Mercado_Negro:
Fast charge is a very useful feature, incredible important in some cases. When I'm in my studio recording I always plug my phone to my computer to charge and fast charge helps a lot because it speeds up the process tremendously.

It would be great if you could add it in the future :)

Cheers
[Nexus 4 Original Android Development] MuertoKo:
It works during the time you set in the App only if if blocks itself, if you click power button it wont. If you set timeout to 5 secs then you have 5 seconds since the screen fades to wake the device by touching.

Yep, now it's JSS build... Was wondering if it will have the famous deadlocks or not now... pretty odd I must say:

Changelog latest nightly (26-09 is the one causing this right?):

===================================

Since Do 26. Sep 00:08:47 CEST 2013

===================================

* hardware/qcom/display

4355a44 qcom bsp fix

* vendor/pa

502f288 mako 3.1
[Nexus 4 Original Android Development] richardddd:
My log does not work even tough I have enabled the logger module from the app :/
[Nexus 4 Original Android Development] MuertoKo:
You Enable Logger and then click menú and go to display KMSG, it should display the log (working for me on stock + 1.6.5 at least, just tested)
[Nexus 4 Original Android Development] XNemia:
OTG

Hello mates,

Dose this Kernel supports the OTG on Nexus 4 ?

Thank you :)
[Nexus 4 Original Android Development] AhmedFaiz:
Ya Noting mentioned about it by fabi.

N⁴| PA3.99_RC2 (nightly) |

FRANCO touch experimental | V4A
[Nexus 4 Original Android Development] alen1901:
No. Read 1st post for features.

---------- Post added at 11:10 AM ---------- Previous post was at 11:09 AM ----------

1st post. Read. Jss version is here for a long time now.
[Nexus 4 Original Android Development] AhmedFaiz:
But on last builds I used to flash jwr kernels and it was working fine!

N⁴| PA3.99_RC2 (nightly) |

FRANCO touch experimental | V4A
[Nexus 4 Original Android Development] szucsgf:
There are two versions of each kernel, one with a "j" at the end and one without. With J = jss, without J = jwr.
[Nexus 4 Original Android Development] XNemia:
So do you mean that the Semaphore kernel SUPPORT the OTG on Nexus 4 ?
[Nexus 4 Original Android Development] szucsgf:
Try wakelock detector from Google Play. It sometimes names the guilty app if bbs doesn't.
[Nexus 4 Original Android Development] XNemia:
so? what build should I flash to use the OTG ?

With "j" or without "j" ?

EDIT:

My current ROM is JWR66Y, so when flash the "without ' j ' build, I can use the OTG ?
[Nexus 4 Original Android Development] szucsgf:
I'm sorry, I accidentally quoted your post. I meant to quote the guy asking for a jss kernel.

But since you asked:

http://xdaforums.com/showthread.php?t=2412689

[RECOVERY/MOD] TWRP 2.6.0.0 with externally-powered USB-OTG support [2013-08-19]

That's a way you can use OTG without changing kernels. I haven't tested it yet but it works for others.
[Nexus 4 Original Android Development] AhmedFaiz:
Who is taking about OTG here. I don't have info on it.

N⁴| PA3.99_RC2 (nightly) |

Matr1x v11 | V4A
[Nexus 4 Original Android Development] richardddd:
KSMG does not show the log :/
[Nexus 4 Original Android Development] MuertoKo:
It takes a bit, but it shows up for me at least, can you add more info? Try clearing semaphore manager data and try again, try another KSMG reader, check your ROM's changelog... all you can try and share here :D
[Nexus 4 Original Android Development] stratosk:
Enable logger and then reboot.

Logger is compiled as module and it can only be enabled/disabled during boot.
[Nexus 4 Original Android Development] mylord92:
Hi all. I love this kernel performance but with 1.6.5 version i have faced random reboot :( My cpu PVS is slow. So i accept +25m voltage. Also use stock rom JWR66Y and disabled SOC. Which parameters should i check and fix? Thanks :)
[Nexus 4 Original Android Development] ciprianruse88:
If you don't know how to take last_kmsg with adb please download syslog app from playstore and take last_kmsg after a reboot happends and post it here to help.:thumbup:
[Nexus 4 Original Android Development] stratosk:
Also try without undervolting.

I'm sorry, what is SOC?
[Nexus 4 Original Android Development] mylord92:
O.K., i downloaded syslog from playstore :)

Trickster MOD define it like that " SOC setting of temperature limiting ". I really dont know what is it :) Its only off mode.

At now, im waiting for another reset and take last_kmsg for upload here.
[Nexus 4 Original Android Development] cantevencode:
SOC is system on a chip. Turning off that setting will prevent thermal throttling but could damage your CPU
[Nexus 4 Original Android Development] stratosk:
I don't know why trickster shows this disabled.

Semaphore does not change anything related to thermal protection.
[Nexus 4 Original Android Development] ciprianruse88:
Yes...trickster always shows thermal off on semaphore kernel.Idk why...
[Nexus 4 Original Android Development] QUIETLYloud:
It shows it off but the phone still throttles down, run back to back benchmarks and you see temp throttle working properly
[Nexus 4 Original Android Development] ciprianruse88:
I know :)
[Nexus 4 Original Android Development] thracemerin:
This refers to the in kernel msm_thermal protection, stratosk uses the stock thermald protection.
[Nexus 4 Original Android Development] richardddd:
Still no log. Logcat says:

Unable to open log device '/dev/log/main': No such file or directory
[Nexus 4 Original Android Development] stratosk:
Please enable logger in Semaphore app and then check that the file logger.ko exists in /data/local

If yes, then check that the initramfs is properly patched with Semaphore changes running this command in terminal emulator:

su

grep logger init.rc

this should return the line

insmod /data/local/logger.ko
[Nexus 4 Original Android Development] richardddd:
Returns the line, but log does not Work stil :/
[Nexus 4 Original Android Development] ihancioglu:
Hi Guys, [MENTION=3750240]stratosk[/MENTION]

I just realized that , only 4 CPU frequencies are using with latest Semaphore.

Deep Sleep,

384 MHz,

1.2 GHz,

1.5 GHz,

Is this normal behaviour?

Thanks,
[Nexus 4 Original Android Development] capoooro:
Yes

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Original Android Development] ioucorsa:
Mine uses all the frequencies but mostly deep 384 1.0 and 1.5 and the others having about 1 minute or less each...
[Nexus 4 Original Android Development] Holer Togni:
I'm on PA 3.99 RC2 and my logger module is located at

/lib/modules/logger.ko

If yours is too maybe setting a symlink helps?

ln -s /lib/modules/logger.ko /data/local/logger.ko
[Nexus 4 Original Android Development] snak3ater:
What Governor are you using?& did you change any settings related to hotplug Driver or the Governor itself:confused:

Btw this Freq thing that you realized,it's not normal :eek:

With the default settings & Ondemand Governor,the freq's used mostly are 384,1134 & 1512..But the frwq's in between are also used..

If you use Interactive Governor,then all of your Freq's are used equally
[Nexus 4 Original Android Development] stratosk:
This is weird. I just rechecked and it works on my side.

Did you check that the module exist on /data/local/? Did you reboot your phone?

Yes, the module is located in /lib/modules but the init.rc tries to load it from /data/local/.

Semaphore manager copies the logger.ko file in /data/local if user checks the logger option.

No this is not normal. I guess the app you are using hides freqs with minimum usage (CPU spy plus?)

In stock ondemand the most used freqs are the min and max. The patch that I sent to upstream Linux improves this behavior a little bit and makes ondemand to use middle freqs more.

But using a touch boost mechanism forces ondemand to use the touch frequency more than the others.

So, it's normal that the freqs you mentioned are used more.
[Nexus 4 Original Android Development] Tex99:
hi, i remember semaphore from galaxy s on ginger, great kernel.

there is the possibility to have touch wake always on ?
[Nexus 4 Original Android Development] -iNSiGhT-:
No, it would cause too much wackelocks.

Paranoid mako
[Nexus 4 Original Android Development] ihancioglu:
Yes that's application problem which hides rarely used freq. I just installed CpuSpyPlus. All of them active but for a few minutes..

About the settings; touch load 85, threshold 10, duration 1600ms

Thanks everyone.
[Nexus 4 Original Android Development] twowheeler:
I installed the app right away! Question though: I see only c3 state is used, is there a reason for that? I know faux has some info about the different states in his thread, so I guess the nexus 4 can use all states right? I'm just curious :D

I have greenify installed to try that out.
[Nexus 4 Original Android Development] Barbatos19:
Finally. . . after two days of using this kernel i encountered one single issue. Upon taking some pictures and viewing it for a while the phone suddenly stop and reboot itself. well it just happened once but i will observe it again.
[Nexus 4 Original Android Development] szucsgf:
Have you manually rebooted since? If not, if you want you can post the log to see if stratosk can see the reason for reboot.

1. Use any file Explorer to navigate to /System/proc

2. See if there is a file called "last_kmsg" there

3. If the file exists, post it here.
[Nexus 4 Original Android Development] stratosk:
I'm not sure about this. I didn't change stock behavior regarding power states. I guess they are not properly working in our CPU.
[Nexus 4 Original Android Development] Barbatos19:
here you go buddy. . .
[Nexus 4 Original Android Development] szucsgf:
Thanks.

Kernel panic, something to do with wi-fi is my best guess. But I'm not the expert.

[46395.711483] wcnss_8960: crash shutdown : 0

[46399.217602] Rebooting in 5 seconds..

[46404.225568] Going down for restart now

No errors detected

Boot info:

Last boot reason: kernel_panic
[Nexus 4 Original Android Development] Barbatos19:
Oh i see. Not a major problem. Thanks buddy
[Nexus 4 Original Android Development] twowheeler:
No problem though. C3 is the deepest deepsleep anyway
[Nexus 4 Original Android Development] stratosk:
Thanks for the log!

It's a kernel panic in netfilter module.

I will check if I can do something or if there is a fix for this.

Let me check something more on this... It seems that something goes wrong...
[Nexus 4 Original Android Development] twowheeler:
For anyone liking the bundi22 iPhone5 based color settings but want some more saturation. Try these values: (5 is the saturation value, so play with that if you want, it's simple ;) )
[Nexus 4 Original Android Development] panart:
I had a lot of random reboots in last 2 days. Last reboot was minutes ago while i was watching a video in MX Player.

In last_kmsg i found this: pm8921_probe: PMIC Restart Reason: Triggered from CHG (usb charger insertion)

Note: I'm undervolting 700-1000mV but didn't have any issues on Semaphore 1.6.0 and Franco r183/r184. I also use Touch Control.
[Nexus 4 Original Android Development] stratosk:
This log shows that you previously booted to TWRP recovery.

I need the last_kmsg exactly after the reboot.

Did your phone booted in recovery after reboot?
[Nexus 4 Original Android Development] panart:
No it did not, it went straight to boot animation (no black screen at all) and loaded fairly faster than it normally would.
[Nexus 4 Original Android Development] stratosk:
This is a soft reboot and most probably related to ROM.

Kernel didn't have a panic and last_kmsg will not help (it just shows that you booted from recovery mode).
[Nexus 4 Original Android Development] panart:
Ok, i will post last_kmsg the next time it happens (if it happens) and if it still shows it's a soft reboot i will make a clean install of Cataclysm ROM.

Thank you Stratos.
[Nexus 4 Original Android Development] stratosk:
Maybe, you can enable logger (and then reboot).

Then get a logcat after the soft reboot. I'm not sure I can help fixing this but maybe it will show us the issue.
[Nexus 4 Original Android Development] alen1901:
Well, i would suggest all users to stop using crappy roms and go with stable ones (close to stock), like purity, kalo, sima or cm stable. Its hard to debug on buggy roms, nightlies.
[Nexus 4 Original Android Development] Barbatos19:
I tried this and color is saturated. Hahaha . looking great on my PA 3.99 rc2. So crisp display it seems like it is so much contrasted.
[Nexus 4 Original Android Development] panart:
I tried the apps aLogcat and CatLog but they don't log anything.

I also tried "adb logcat" but i get the error "Unable to open log device '/dev/log/main': No such file or directory"

***EDIT***

I'm an idiot... I flashed Semaphore coming from franco kernel without flashing the stock kernel first. Now i can get logcat. Most probably that's the reason of the random reboots i had the last 2 days.
[Nexus 4 Original Android Development] twowheeler:
Yeah looks great right? Background suddenly pops of the screen here :P. Anyway, it's a fun thing to play with if you know what every number means ;)
[Nexus 4 Original Android Development] Barbatos19:
That's my problem. I don't know the meaning of each numbers. Hahahah. Can link me to it?
[Nexus 4 Original Android Development] fortunz:
I just installed this today, I don't normally make a donation so quick, but I was pretty happy to find the associated app was free. That made it really easy to test drive semaphore, especially for me since I don't already have a voltage control app. Thanks much :D

I initially chose semaphore because faux's had a min undervolt of 800 as far as I could tell. From what I can see on your changelog, it looked like the minimum here is 700. I wanted to at least test sub 800 settings for my lowest frequencies. I'm using it with pa 3.99 rc2 and am pretty happy so far.

Anyway, thanks. [MENTION=1007992]everyone[/MENTION] else, Please donate to this guy if you like the kernel and/or app. It's good karma to reward generous devs. :good:
[Nexus 4 Original Android Development] edbertin:
Giving a try. Just installed on my N4, I'm coming from FK Linaro on stock rom, let's see how's going during the day.

Cheers
[Nexus 4 Original Android Development] stratosk:
Thanks so much for your donation, my friend! :)

Thanks for your help and for your kind words!
[Nexus 4 Original Android Development] McPh1st0:
I like this kernel more and more...:victory:
[Nexus 4 Original Android Development] stefan8bc:
Currently I am on Faux123's kernel, but I want to try out this one. Should I flash the stock kernel first? Or should I just wipe cache and dalvik cache and flash this kernel? Couldn't find it in the opening post or on the semaphore website...
[Nexus 4 Original Android Development] Barbatos19:
Just simply flash it. But if you want to make sure tree flash stock kernel then flash semaphore.
[Nexus 4 Original Android Development] hulicow:
Dirty Flash Rom as faux kernel touches /system files. As far as my knowledge only Franco and Semaphore are the two kernels that does not touch the /system and /init.d folder. All third-party kernels that does touch /system and /init.d folders should dirty flash rom before flashing this kernel or any other kernel to avoid conflicts.
[Nexus 4 Original Android Development] jst_tsj:
On SlimRom i cannot use the logcat. Should I install stock kernel before installing semaphore also on this rom?
[Nexus 4 Original Android Development] Skkip:
[MENTION=3750240]stratosk[/MENTION]:

Hey, my friend. Regarding your hotplug I send you a pm :) Thanks for your great work.
[Nexus 4 Original Android Development] vampire36:
[MENTION=3750240]stratosk[/MENTION] : Can you just give this small request a thought...an alternative to power button to turn on he screen...I know of touchwake...like it but something that would reduce power button use...if can be done without too much hit on battery...just a thought if you can possible think of some good way like double tap 2 wake or something :)...skip it if its too much work...or would affect the 'Awesomness' of the kernel :)...just have the fear that power button might break down...so :)
[Nexus 4 Original Android Development] snak3ater:
Never heard of Touch Control App :eek:

It works with Semaphore..Try it
[Nexus 4 Original Android Development] jolas:
I recently uninstalled TouchControl application, due to high battery drain issues and also random reboots problem... :(
[Nexus 4 Original Android Development] szucsgf:
Maybe https://play.google.com/store/apps/details?id=it.android.smartscreenonlite ?
[Nexus 4 Original Android Development] vampire36:
Nope too much battery drain...something in the kernel...that is smart uses interrupts or something on similar lines...

Doesn't cause stability issues...as many have if you look back with TC :)

---------- Post added at 05:22 PM ---------- Previous post was at 05:21 PM ----------

Those are proximity sensor based and tend to kill battery...:)

So something embedded in the kernel will be cool
[Nexus 4 Original Android Development] thracemerin:
Embedded solutions use the same methods as TC or the other methods people are pointing out so they will be similar in terms of stability and battery drain and they will cause issues with touchwake and TC support.
[Nexus 4 Original Android Development] vampire36:
Not really...if its say part of semaphore the dev knows better what exactly goes into module..whats working whats going wrong...but if you support TC and use its module...some bug in it...or even a code that works well with kernel A and B might run to issues with C...as each kernel is different in small ways...basically when its exclusive and embedded better control...if its module external...using just the interface...its difficult as number of kernels increase...:)
[Nexus 4 Original Android Development] thracemerin:
I understand that you think that, but TC is a different module built against each kernel for that specific kernel, the code is compiled separately but is the same as the code would be if it were embedded, this is how kernel modules work.
[Nexus 4 Original Android Development] cmajetic:
number 4,5 and 6 in line oft numbers equal the three whites from the color profiles that can be loaded with other kernels, right?

copied the Bundy profile but wasn't sure what the numbers are. imo only the whites make sense

Gesendet von meinem Nexus 4 mit Tapatalk 4
[Nexus 4 Original Android Development] vampire36:
But basically if its my code and am the dev I can debug better...tweak better,,,rather than being depended on someone else's module...so even if its a microkernel modularised...module made by me will always help me have better control than say a third person trying to compile :)
[Nexus 4 Original Android Development] thracemerin:
Right, but there are people who want to use TC for the additional options, adding this code to the kernel basically removes this possibility.
[Nexus 4 Original Android Development] stratosk:
Did you try to enable logger in Semaphore Manager and reboot?

Thanks my friend! I will check it and let you know.

I thought it many times but I think it will cause more issues than the power button issue.

Anyway, maybe in the future
[Nexus 4 Original Android Development] vampire36:
Understand...so i was looking at this feature as something exclusive to semaphore code...like Franco has picked up...something on similar lines...efficient tweaked for the users just like the kernel...not too much options limited yet awesome:)

[MENTION=3750240]stratosk[/MENTION] : Thanx man...I was sure you must have given it a thought..but ya hope you find a cool way to include it :)
[Nexus 4 Original Android Development] stratosk:
As far as I know Franco kernel changes a couple of binaries. You need to restore them back or flash stock.
[Nexus 4 Original Android Development] ak:
Faux kernel change only thermald min/max data file .. That's all.

Franco kernel delete at boot with ramdisk sh script thermald and the power lib.

reply from Neo revolution kernel :)
[Nexus 4 Original Android Development] jst_tsj:
Yes I did. Kmsg is wornig, logger.ko is in its place, init loads the module but logcat returns

root@android:/ # logcat

Unable to open log device '/dev/log/main': No such file or directory

Thx for your help!

Edit:kmsg is working :)
[Nexus 4 Original Android Development] twowheeler:
This is from the semaphore changelog:

" For your convinience, franciscofranco uses the terminology below for array's positions

"greys, mids, black, XX, contrast, brightness, saturation, white, XX"

So, he leaves positions 4 and 9 with hardcoded values. (You may also leave them untouched)"
[Nexus 4 Original Android Development] stratosk:
kmsg is a different and unrelated to logcat.

Did you flash the kernel properly (first stock and then Semaphore)? There was a report with the same issue. Problem solved with a 'clean' installation.

Did you reboot the phone? (Sorry I ask again)
[Nexus 4 Original Android Development] jst_tsj:
Yes, I did reboot. Thx for clarifying about logcat and kmsg, I thought the logger module would control both :)

So, my last question is: shall I flash stock kernel, even if I'm not stock?
[Nexus 4 Original Android Development] stratosk:
Thanks again for the log.

Well, I'm not sure if there are 2 different issues or 1. :)

The result was that a facebook process (what don't you use G+? :) ) hit a bug in netfilter module (that counts data usage).

The second one (or maybe this one caused the first) is related to power management. I found a related patch in code aurora and I will use it.

If the first one is unrelated to the second I have no idea how can be resolved. The netfilter Google's code is too cryptic for me and needs a lot of reading. I googled but there is no obvious solution.
[Nexus 4 Original Android Development] stratosk:
No. You should flash your ROM's kernel and after this Semaphore.

If you flashed Semaphore over your ROM's stock one there is no need to repeat the procedure.

Just try it if you came from other kernel.

Also, please check that logger.ko file exists in /data/local/ and check if the module is loaded with lsmod command in terminal emulator.
[Nexus 4 Original Android Development] jst_tsj:
Ok, so the procedure I did was Flash ROM+addons then flash semaphore. The file logger.ko is in /data/local, but it seems it's not being loaded during startup.

In fact, if I run lsmod, I cannot find it, while it appears if I load it using insmod.
[Nexus 4 Original Android Development] stratosk:
Then it seems that the init.rc can't load the module.

Inserting the module (insmod) in a later stage will not work. The logger module need to be loaded before framework.

Could you please post the output of these commands:

su

grep logger init.rc

ls -l /data/local/logger.ko

P.S. What's your ROM?
[Nexus 4 Original Android Development] edbertin:
Just sharing my first contact with Semaphore by [MENTION=3750240]stratosk[/MENTION] . I didn't use the phone to much today but here are my preview.

Only change i made was reduce min cpu to 1 core on dynamic hotplug (i think this can be done without problem right?). Stock Rom btw.

Tks for your hard work Sir.
[Nexus 4 Original Android Development] jst_tsj:
My rom is slim, and the output of the commands is

root@android:/ # grep logger init.rc

insmod /data/local/logger.ko

root@android:/ # ls -l /data/local/logger.ko

-rw------- root root 10853 2013-09-28 00:13 logger.ko

Thanks for your help!
[Nexus 4 Original Android Development] stratosk:
This is very weird! Everything seems normal.

Would you mind post some more info, please?

Again in terminal emulator (or adb shell):

su
strings /data/local/logger.ko | grep Sema
uname -a

Could you please post the kmsg after a reboot?

If it's convenient, please also send me the init.rc file.

Thanks for your patience. :)