User reported problems for Liquid and Mourta kernel goes here.

[Guest Mourta]

I'm trying to keep this simple and i want you to try to keep it simple too.

 

A user reported problem in a thread about kernel development is misplaced, a user reported problem should go in it's own thread.

 

This is how you report a problem:

 

You state clearly what the problem is: number that 1

You state clearly when the problem was encountered: number that 2

You provide a last_kmsg or logcat so i can review it and see what went wrong and when.

 

The information i need is which version of my ROM you are running and which version of my kernel and if you didn't fully wipe or did a restore by any means after the wipe then please mention that so i can ignore it completely. If starting an application slows your system down and ONLY when you do that... i can't fix it for you, contact the app dev.

 

New addition, undervolting/CPUFreq/CPQ governors used are things i need to know about, if you have a problem charging in any way, try a different charger, if it persists, then provide a log of the experience.

 

If you are curious about updates, stay curious, if i haven't posted it for all your concerns it doesn't exist. Do NOT hound the testing crew for them or you will be banned in a heartbeat.

 

These are the rules, play nice or go away.

Edited April 16, 2015 by Mourta

[Guest technofreak]

Why on latest kernel release CPU often scaling from 51-370-475 MHz in Idle. On previous was stand still on 51Mhz. Ain't to big problem but no one reported that except me. So maybe this is because i'm on CM official or...row,Westwood, abyssplugv2,inteliplug enabled

[Guest daniel.mota]

 Well, I have an issue to report too.

 

 I can´t use ROW scheduler, because it makes the GPS receiver crazy.

 

 It takes ages to get a valid signal, and when it finally does the signal is very weak (often lost) and erratic, the position of the phone is almost always wrong.

 

 Using CFQ makes a huge difference, it works much much better.

[Guest LGaljo]

1:   I have problem with charging. In the morning when I turn the phone on I can see that I have only 93 % of battery. What I think is that it charges to the 100 % and then fall down to constant 93 % because of "muic_lock". In other ROM I tried is muic_lock is present but battery stays at 100% untill I unplug it. (will paste screenshot in the morning) @Mourta can you tell me which file is in charge of monitoring of charging and is it in kernel or ROM.

2:   When I play music on headphones with apollo and DSPmanager phone become partially hot. I don't remember that anytime before phone become hot just because of playing music. I had played music for 4 hours.

 

Which log do you need?

 

phone config:

mourta kernel 28.8.2014

cyanogenmod 11 20.8.2014

[Guest derders]

1:   I have problem with charging. In the morning when I turn the phone on I can see that I have only 93 % of battery. What I think is that it charges to the 100 % and then fall down to constant 93 % because of "muic_lock". 

 

+1

 

If I notice this I shutdown, wait a while and reboot with 100% ... little bit annoying

[Guest Mourta]

1:   I have problem with charging. In the morning when I turn the phone on I can see that I have only 93 % of battery. What I think is that it charges to the 100 % and then fall down to constant 93 % because of "muic_lock". In other ROM I tried is muic_lock is present but battery stays at 100% untill I unplug it. (will paste screenshot in the morning) @Mourta can you tell me which file is in charge of monitoring of charging and is it in kernel or ROM.

2:   When I play music on headphones with apollo and DSPmanager phone become partially hot. I don't remember that anytime before phone become hot just because of playing music. I had played music for 4 hours.

 

Which log do you need?

 

phone config:

mourta kernel 28.8.2014

cyanogenmod 11 20.8.2014

 

1. I do not have this problem, i need the logcat.

 

2. Mine does not become hot when doing so, could you send me a logcat on that too to see which states it's been in while playing music?

[Guest Mourta]

 Well, I have an issue to report too.

 

 I can´t use ROW scheduler, because it makes the GPS receiver crazy.

 

 It takes ages to get a valid signal, and when it finally does the signal is very weak (often lost) and erratic, the position of the phone is almost always wrong.

 

 Using CFQ makes a huge difference, it works much much better.

 

This makes absolutely no sense, the scheduler is not related to GPS at all. Though the GPS sucks it's low on my list of things to fix right now but after the next update i'll get to it.

[Guest daniel.mota]

This makes absolutely no sense, the scheduler is not related to GPS at all. Though the GPS sucks it's low on my list of things to fix right now but after the next update i'll get to it.

 

Well, I use the GPS a lot (for car navigation, sports tracking and geocaching).

 

I realize that changing the scheduler shouldn't make a difference, but I tested it using TomTom and things went a lot smoother using CFQ. With ROW the navigation was terrible, because the receiver was constantly "placing" me in the side streets.

 

My only (possible) explanation is that somehow the app usage is incompatible with ROW.

 

Oh, and other thing, I also have the charging problem, after getting to 100%, the battery level slowly drops to 93% (over some minutes), and stays in 93% till I unplug it.

[Guest derders]

1. I do not have this problem, i need the logcat.

 

 

 

 

logcat for while charging and staying at 93%

logcat-2014-08-27_030648366.txt

[Guest Gerard Szulc]

i have this problem too, but i thought interactive should resolve it, so tasker is changing into interactive always while charging but it gives me no success..

[Guest Mourta]

Well, I use the GPS a lot (for car navigation, sports tracking and geocaching).

 

I realize that changing the scheduler shouldn't make a difference, but I tested it using TomTom and things went a lot smoother using CFQ. With ROW the navigation was terrible, because the receiver was constantly "placing" me in the side streets.

 

My only (possible) explanation is that somehow the app usage is incompatible with ROW.

 

Oh, and other thing, I also have the charging problem, after getting to 100%, the battery level slowly drops to 93% (over some minutes), and stays in 93% till I unplug it.

 

 

No, i mean that it's impossible, the scheduler does not interact with programs at all. The code doesn't ever interact with any programs that you run, this is all handled by the kernel.

 

It's just... can you get me a proper logcat using ROW and this so i can check this out? Preferably a last_kmesg too.

[Guest Mourta]

logcat for while charging and staying at 93%

 

This should be solved with the latest version...

 

You're not using ararangi's or xposed?

[Guest derders]

This should be solved with the latest version...

 

You're not using ararangi's or xposed?

 

no more... as you recommended somewhere....

 

had ararangi`s tool  and xposed on older LS versions installed and yes used  ararangi`s 1500mv to charge faster in some cases.

 

atm I have a clean install without all my apps runing and new g-account on dalvik for tests (baseband, wakelocks and battery) and there is the same.

 

have made some logs(all off - wlan on - mobil on) ... will upload it tomorrow...

[Guest Mourta]

I'm reverting the new GPU OC interface. But the problem you are having is most probably because of a worn out resistor. It seems only people who have raised the charge voltage are having this problem.

[Guest moneyvirus]

Im not sure but my feeling is the gpu doesnt scale propperly when i watch trickster mod i see it running on 200mhz only even when i change screens, when i start antutu or an other benchmark i score not really high on 3d performance its like 1700 points in antutu dunno if its my side or due the CPU/gpu linking if there is a log nessesary could any body tell me which log?

[Guest Pasquale Lombardi]

I'm reverting the new GPU OC interface. But the problem you are having is most probably because of a worn out resistor. It seems only people who have raised the charge voltage are having this problem.

I can tell that my resistor is not worn because after i stopped to use araragi interface all went fine and my phone charges normally to 100%. I had this problem just with kernel based on iodak but not on yours.

I guess some issues may happen when you charge with non original usb/AC charger. The original charger can give up to 2 amper if i not goes wrong, the non original gives often 1 or at max 1,5 amperehour. I recharge good with a tablet charger of 2.1 ampere because my original was broken i had to change it.

Edited August 30, 2014 by Pasquale Lombardi

[Guest LGaljo]

Rudjgaard on XDA said this about charging problems:

 

"It happens on many different kernels.
By experience i'm drawn to think that it's caused by a wrong paring of uv table / tegra variant.
It doesn't stop at 95% though, it gets to a 100 then after it stays plugged in a while it starts decreasing and it stops either at 95 or 92%
Phone off charging will go to 100 and stop there without problems."

[Guest Mourta]

Rudjgaard on XDA said this about charging problems:

 

"It happens on many different kernels.

By experience i'm drawn to think that it's caused by a wrong paring of uv table / tegra variant.

It doesn't stop at 95% though, it gets to a 100 then after it stays plugged in a while it starts decreasing and it stops either at 95 or 92%

Phone off charging will go to 100 and stop there without problems."

 

That would work if EVERYONE had this problem.

 

So far only users of ararangi's toolkit have this problem.

 

I'm not going to fix it specifically because there is nothing wrong here, there IS a chance that it might change with the next update since i'm reverting a few fixes for GPU OC which is linked to the LP uV since.. well it just is.

 

If it doesn't, i won't spend time fixing it.

[Guest Mourta]

I can tell that my resistor is not worn because after i stopped to use araragi interface all went fine and my phone charges normally to 100%. I had this problem just with kernel based on iodak but not on yours.

I guess some issues may happen when you charge with non original usb/AC charger. The original charger can give up to 2 amper if i not goes wrong, the non original gives often 1 or at max 1,5 amperehour. I recharge good with a tablet charger of 2.1 ampere because my original was broken i had to change it.

 

 

Seems strange to me, but as i said... it's nothing that i can fix either way.

 

Unless the next update fixes it... which it might...

[Guest rtunner]

I experiencing some bugs: when I try to access the Performance menu the 'kernel tweaker stopped' appear and I'm not allowed to access it. and sometimes the power button doesn't work to turn off the screen.

[Guest Mourta]

I experiencing some bugs: when I try to access the Performance menu the 'kernel tweaker stopped' appear and I'm not allowed to access it. and sometimes the power button doesn't work to turn off the screen.

 

First of all, use the latest kernel and ROM, wait for it to boot up and note that you have to use a good gapps package (zero day gapps) and if you restored ONE SINGLE THING at all in ANY WAY you're off the support.

 

Second, provide logs, i can't fix it if i don't know what is broken.

 

Or... you could just try reading the OP of this thread to get a clue what you need to do to even be able to post in this thread.

[Guest dimi89]

@Mourta zero day PA gaaps but does it matter if i install micro - mini or full packages ?

[Guest ottomanhero]

@Mourta zero day PA gaaps but does it matter if i install micro - mini or full packages ?

 

Most people use mini modular due to it being less bloated, but still including some neccessary apps.Full package removes system apps and replaces them with google apps, which is something I wouldn't recommend.

Micro should work fine aswell.Still I'd pick mini modular if I were you.

and also 

 

 

You state clearly what the problem is: number that 1

You state clearly when the problem was encountered: number that 2

You provide a last_kmsg or logcat so i can review it and see what went wrong and when.

Please follow the rules said above, and also in OP or post in other threads.

Edited September 1, 2014 by ottomanhero

[Guest asyscom]

@mourta, which kind of log you need to try to fix my drop signal problem? I cantinue to have problem with any kernel.

 

Thanks in advance

[Guest Mourta]

@Mourta zero day PA gaaps but does it matter if i install micro - mini or full packages ?

 

You have to use the atomic package.

 

 

 

 

 

 

 

 

 

Before you go looking for that.... no, it doesn't matter which you use as long as you are using the latest version. ;)