yashsingh1/xdaforums huggingface dataset:
[Galaxy S Plus I9001 Android Development] ZordanKV:
480p works, just tested. [MENTION=4416117]smitharro[/MENTION] you probably haven't switched recording to 480p.
[Galaxy S Plus I9001 Android Development] smitharro:
You're right, silly, just didn't know I had to switch back to 480p manual. Sorry for the post.
[Galaxy S Plus I9001 Android Development] dr.wtf:
does anyone else have the problem that 3g turns on in 2g only mode?
[Galaxy S Plus I9001 Android Development] roberpao:
Hi about various weeks I have installed this rom: [ROM][JB][4.2.2][unofficial]AOKP-jb-mr1 [BETA][built 6]~04-06-13~, and your kernel 3.4 V1.3, would need to install the aries part, before the install the 1.4?, that function is performed this patch?.

Sorry for my poor english.

Thanks and regards.
[Galaxy S Plus I9001 Android Development] Christopher83:
Yes, you should install both kernel and AriesParts...
[Galaxy S Plus I9001 Android Development] roberpao:
Thanks Chris, but I have not clear the function of aries parts. Can youn explain it, please?

Regards.
[Galaxy S Plus I9001 Android Development] Christopher83:
You can find the options offered by AriesParts inside System -> Advanced

These options allow you:

- to customize the timeout of touchkeys backlight (updated version)

- to enable/disable the backlight on touchscreen press (updated version)

- to directly access to BLN control

- to perform the horizontal calibration

- to enable/disable the fast charge

- to customize the vibration intensity

- to directly access to phantom key presses manager (updated version)
[Galaxy S Plus I9001 Android Development] roberpao:
Thanks Chris, but I don't understand very well the phantom key function..

Regards.
[Galaxy S Plus I9001 Android Development] Christopher83:
Take a look at the second post inside the first page of this thread or at my signature for more info:

Phantom Key Presses Filter
[Galaxy S Plus I9001 Android Development] Rhonin86:
K^Kernel 1.4 390 MB under LiquidSmooth 2.7

Hi Christopher,

i'm not quiet sure if it is a problem of the ROM or of the kernel - but maybe you can have a closer look to the attached logcat / dmesg.

Shorty after waking up the phone the system is very laggy - for example 2 widgets (simple calendar and Googles keep) do not scroll smooth - they imidiately stop scrolling as if someone push brakes.... Also lists could not be scrolled to the end with one wipe. This behaviour disapperears after a while and i assume that the memory management causes these lags. I postet the logs partial in the LiquidSmooth-thread - hopefully with the relevant part....

THX in advance

Rhonin
[Galaxy S Plus I9001 Android Development] Christopher83:
Hi Rhonin,

I took a look at your logs, and it seems that some apps take too long to start.

Which is the launcher you're using?

Could you try to uninstall BBS for a while?

Thanks.
[Galaxy S Plus I9001 Android Development] Rhonin86:
Nova is running on my system - which is also the standard launcher of LiquidSmooth - Yes i can uninstall BBS for a while -

THX for your answer and i'll provide newer information if some changes happen...

Should i use another launcher instead ?

So long

Rhonin
[Galaxy S Plus I9001 Android Development] Christopher83:
I'm using Apex Launcher on ADC CM 10.1 Release 2, I never faced similiar issues... I have simple calendar widget too.
[Galaxy S Plus I9001 Android Development] Stefano187:
Hi Christopher,

May I have your permission in changing the boot picture of your kernel? Don't worry only on my phone, I'll never put online it. I'm sorry but I don't like the pink CID...

Thank you in advance

Stefano

Sent from my GT-I9001 equipped with:

*ROM: SlimCM based on CM10.1 RC2 by ADC Team

*Kernel: K^Kernel 3.4.50 v.1.4 with alternative exUV table

*Recovery: TWRP 2.5.0.0 by buffo1987

*Phantom Key Press Filter: ON
[Galaxy S Plus I9001 Android Development] Christopher83:
Yes, of course!
[Galaxy S Plus I9001 Android Development] JohnKersten:
Appdrawer problem

Hello Christopher,

First of all thank you for delivering us a new kernel 3.4.50.

When I use the ADC ROM release 2 or David Teri beta 10.50 ROM, the appdrawer sometimes hangs.

The homekey doesn't respond to go back to homescreen, apps are frozen inside the appdrawer.

When keep pressing the homekey for longer time I can only pick the programs already loaded.

Maybe you have time to look in the logfile and hopefully you can find something.

Regards John.
[Galaxy S Plus I9001 Android Development] Christopher83:
Hi John,

I'm sorry, but there is nothing useful in this kernel log, the last_kmsg is useful if you had an unexpected shutdown or reboot.

Please, the next time could you give me your logcat?

Maybe there's something app/rom related, which is the launcher you're using?

Thanks.
[Galaxy S Plus I9001 Android Development] JohnKersten:
Thank you Christopher for the answer.

It happens also on the stock launcher ADC ROM (Trebuchet 1.0).

Here is the logcat, Christopher.

I installed David Teri 10.1 Beta 11 ROM with your kernel version 1.3, freezing happens sometimes, when I turn device 90 degrees, it takes me to home screen and everything is normal again. With your kernel version 1.4 freezing more often happens

Regards John
[Galaxy S Plus I9001 Android Development] krakowiak84:
Hi Christopher. Thanks for the update to 3.4.50 ... :)

The battery keeps me really well even when using a 3G phone also now got a big kick.:victory: Good luck in your work:p:D
[Galaxy S Plus I9001 Android Development] muhammadnajmi96:
Impressive battery life and buttery smooth :D , doesn't' lags at all. Thanks Christopher :)
[Galaxy S Plus I9001 Android Development] dr.wtf:
do you have a non-stock battery? 5 hours screen on is near impossible...
[Galaxy S Plus I9001 Android Development] mrjraider:
WOW 5 hours onscreen time :eek:

Amazing.. Did you use 3G?
[Galaxy S Plus I9001 Android Development] ZordanKV:
I have 4h 30 minutes with 1500 mAh battery with K^Kernel :)

But didn't use 3G.

Here is the post in the JellyBeer ROM thread.
[Galaxy S Plus I9001 Android Development] mrjraider:
And thats why i dont use JB jet.. I need some conclusive answers regarding the drain. I know its big (in android) but on GB i can still get 2 days with relative ammount of 3G useage ;)
[Galaxy S Plus I9001 Android Development] smitharro:
Well, I understand you. But why do you always have to use 3g? Standard I only use 2g (more than enough for WhatsApp, and use of gps, like with runtastic, or even xda) . Only when I want to download anything or use my Internet browser I switch to 3g and then only when there's no wifi around. This way I can almost get 2 days with de ADC rom!
[Galaxy S Plus I9001 Android Development] adomm420:
I must use 3g at all times, because my provider (three uk) doesn't have 2g at all, it uses other networks to support 2g, and with 2g you can't have internet with this kind of setup. What you can do with 2g is calling and messaging and signal isn't very strong too.
[Galaxy S Plus I9001 Android Development] smitharro:
Ok, I'm in the Netherlands (kpn). I as you can read above here, I can do most things on 2g. Signal is (especially on 2g) usually strong here. 3g unfortunately uses al lot of power, and not only in this rom... Switch back to gingerbread is always possible of course, but that feels so much like 'old school'!
[Galaxy S Plus I9001 Android Development] ckiikc:
pkf

After your last release I noticed worst performances for pkf moustly from touch keys events. Now I'm using CyanogenMod 10.1.0 Beta 10.5 --- Kernel 3.4.x and your Kernel with your kernel and I got hundred of thousend of events. To let the phone works in 2g I've to set max number on input interrupt to 1 and 25 ms to wait time for home key in order to let my phone work. Is it something that I've to deal with or is something that is changed in CM10.1 or in your kernel that made the thing going worst?
[Galaxy S Plus I9001 Android Development] Christopher83:
I haven't changed anything related to phantom key presses filtering module.

But that's normal, it means that the module is working, because your phone is receiveing a lot of bad interrupts in 2G mode, probably the signal is poor or bad, and the module is filtering them.

My phone was suffering from this problem too (probably it started to have this problem after a fall) and I have usually more than 100000 ignored key presses in a day, before to develop this solution I had hundreds of screen activations, back to home and google search popups, I was exausted of this hardware issue, now I can happily use my phone...

Btw, I'm only using a different rom (ADC CM 10.1 Release 2)...
[Galaxy S Plus I9001 Android Development] adomm420:
Basicly I have no problem with using 3g with data on all the day now with this kernel, and I have no option for internet: either I use 3g and have internet or I use 2g and have only calls and messaging ;)
[Galaxy S Plus I9001 Android Development] .NetDeveloper:
i dont understand what shold i download i found so many links with diffrerent size and so many verisions

i just have 4.2.2 CM 10.1 from Dev Connection Team

so please cany anyone help me and explain which links should i download
[Galaxy S Plus I9001 Android Development] ktulu84:
there are 3 folders, each one contains kernel with different free ram (360MB - 370MB - 390MB), the differences are that 390MB can't take videos on 720P, 370MB uses less RAM than 360MB for the window manager to leave more free ram but everithing is working fine. In each folder you can find 2 version, one is UV, and the other is ExUV, ExUV saves more battery, but it can create freezes or reboot on some devices, UV should work well for everyone.
[Galaxy S Plus I9001 Android Development] .NetDeveloper:
so mine mobile llike urs

SAMSUNG GALAXY S PLUS (GT-i9001)

can you tell me what you use and works fine with ur mobile?
[Galaxy S Plus I9001 Android Development] ktulu84:
It depends on your needs... I'm using 390 exuv because I do not take videos and my phone works well with exuv, try exuv first, if you have freeze or reboots try uv

Inviato dal mio GT-I9001 con Tapatalk 2
[Galaxy S Plus I9001 Android Development] chocotermi:
Battery usage on K^Kernel 3.4.50 ExUv with 370MB is quite well. The system DevConnection_Team rc2, scheduler SmartassV2, I/O Row. I set the frequency 245-1209MHz
[Galaxy S Plus I9001 Android Development] MHN.1515:
Hi, I'm asking you if you are working on a brick phone (EMMC)

Bricks on the phone so you can use the kernel

This requires a lot of time there?

Brick phone now works only on 3.0 kernel

If you did it very well could be :)

Thank's
[Galaxy S Plus I9001 Android Development] gemtin92:
Yes, ofcourse they work. Just be patient and folllow xda forum.

Tapatapatap i9001
[Galaxy S Plus I9001 Android Development] risingsunxx:
Someone can be so kind and explain me the difference between Row & Sio? :)

Gesendet von meinem GT-I9001 mit Tapatalk 2
[Galaxy S Plus I9001 Android Development] DreamerTKM:
Just click and go~
[Galaxy S Plus I9001 Android Development] smeroni68:
Up to now the only possibility to use a v3.4 kernel on 9001 is to have a NOT bricked phone... I hope it is clear.

Our focus is to develop and enhance the rom/kernels... is not to find a solution to let use bricked phones... I hope this is also clear...

We have only Ivendor that has a bricked phone to test and check... his "Team activity" is to try to find a solution when he has time... we can not do anything, because on working phone the issue do not appear... I hope this is clear too...

So please stop asking if and when there will be a fix for v3.4 kernel... we do not know if and when will be possible...

For you would be better to solve the brick with the exchange of the motherboard... if is not possible, just use the phone with the given patch and wait if any news.

Thanks for your cooperation and understanding.
[Galaxy S Plus I9001 Android Development] MHN.1515:
Thanks for your help

But no need to be angry

My only query about time kernel 3.4

I had a brick phone

And if you explained that you

I should not ask questions about it!

Maybe I've asked a lot of questions. Sorry

I stand waiting for news :)
[Galaxy S Plus I9001 Android Development] mrjraider:
Is does makes sense that users are asking for a solution since custom software build by members here on XDA have ruined some phones here and are only able to run CM 10 wih some special configuration on ext sd.

So please think a bit longer before you answer... ;)

If your phone has been ruined by the emmc/mmc bug wouldnt you find a solution to run the latest Android by the "great" ADC team?

Regards
[Galaxy S Plus I9001 Android Development] ktulu84:
Hi, i think that you know well what every modding thread says...

yes, they were unlucky, that is true.. but no one had an idea that our phone could have the same bug as gs2 or gnote, and don't forget that ivendor himself bricked his own phone.

plus I think that this users have the possibility to run CM10.1 from ADC, they can use the patch provided for them... is not our fault if 3.4 kernel is not booting for now on ext-sd, i tested by myself the patch and it worked for me, but it seems that is not working on bricked phones. smeroni only said that the team is working on this, if something comes up we will publish this as long as we have confirmation that it is working on bricked devices... I think that if i have my phone bricked, and i can't get it to warranty is a great thing that i can use it, even if is not the latest kernel, i can use a broken phone and i don't have to buy a new one... don't you think?
[Galaxy S Plus I9001 Android Development] mrjraider:
Yes that is true but it is a bit unfair to be shoved off because you flashed some broken software.. Even if the creator is not responible for any damage ;)
[Galaxy S Plus I9001 Android Development] ktulu84:
smeroni was only clarifying some points, just to avoid to spam the forum with similar requests everyday (the 3.0 patch was released 2 days ago... it is not a month without any news..)
[Galaxy S Plus I9001 Android Development] smeroni68:
I confirm ktulu84 post.
[Galaxy S Plus I9001 Android Development] peppolax:
The best combination governo/scheduler for this kernel ?... :D

Thanks

Inviato dal mio GT-I9001 con Tapatalk 2
[Galaxy S Plus I9001 Android Development] Rhonin86:
For me the standard settings deliver the best performance - concerning akku drain there might be better combinations but for now i'm satisfied with the performance and the akku drain...

Cheers

Rhonin
[Galaxy S Plus I9001 Android Development] freemanandrei87:
I use stock settings to but some games run like crap ..on GB they ware playable any tips how to improve gaming hit this kernel it s the one whit 390m ...temple run 2 is one of them
[Galaxy S Plus I9001 Android Development] Rhonin86:
That depends not only on the kernel - afair the graphic drivers are outdated and not improved by the manufacturer. So the only thing that helps at the moment is overclocking up to max and use performance governor - but be careful !!!! The temperature will rise with every minute and your cpu could be damaged, because performance tries to keep the highest frequency...

Otherwise you should wait or go back to CM10 R 2.5 with the k^kernel/phenom/castagnaIT kernels....

Wish you success with your search for ultimate gaming performance.... but keep in mind our device is an "oldtimer" meanwhile :o

Cheers

Rhonin
[Galaxy S Plus I9001 Android Development] pierm:
I do have a question about deep-sleep apparent death.

What happens is that if I leave the cell for a short time idle, quietly goes into deep sleep by detecting a 80% (walking fast in the dorm, within 2-3 minutes, I'd say great drain the battery).

But if the time of deep sleep and 'long enough, at least 15 - 20 minutes of non-use of the cell, the phone when you press the home button does not start immediately, even 4-5 seconds pass, you have to press the home button one more time to have the screen lock screen.

it also happened that the lack of recovery of the cell gives the impression of having gone to sleep death (by pressing the home button more 'times and waiting about 30 seconds). I had to remove the battery and restart the cell,

question:

Perhaps, however, was in a deep sleep long? What do you think? Stems from the fact that the high battery drain could generate this phenomenon (undervolt too much?)

I have the kernel 390MB the last but not the 3:50 EXUV.

thanks
[Galaxy S Plus I9001 Android Development] Christopher83:
Hi Pierm,

if you can, provide me a last_kmsg after that this problem occured.

You can find it at the path "/proc/last_kmsg" after the reboot.
[Galaxy S Plus I9001 Android Development] anuseb89:
Hi,

Battery life is amazing with last version..see my stats below..

Screen on time:: 1 hr

Call duration :: 20 mints

Wifi off

9 hrs of 2g only mode with data on all the 9 hrs..

I took phone on Nov 2011 and considering that along with 3.4 kernels reactivity i dont want anymore battery friendly kernel.. Thanks chris and team for all the work..

Smartassv2+sio and 245-1400 Mhz cpu..
[Galaxy S Plus I9001 Android Development] pierm:
Hello

I checked the file exists kmsg (no last_kmsg). Now this file has zero bytes.

As soon as it happens again this deep-death I send it in zip.

This problem 'also happened to another user.

thanks

I ask for advice:

After I sent the file msg, trying EX_UV kernel?
[Galaxy S Plus I9001 Android Development] Christopher83:
If there is no last_kmsg, I suspect this is a problem caused by an app or a battery failure...
[Galaxy S Plus I9001 Android Development] spdrfx:
Hello!

The "mediaserver" (player pro) cause high battery drain. Anybody can confirm this?
[Galaxy S Plus I9001 Android Development] pierm:
Hi Chris,

I would drain the battery very good until all'emergersi of the problems that I have highlighted. From 7:00 this morning at 9:00 cellullare with the ordinary operation of my mail widget, etc. .. battery usage '1%. good ok

The transition from deep sleep to death sleep eat 3-4% battery. So now at 18:05 normal use is 43%. that's okay.

Filter by PKF and the 'of course I got up on interrupts from 1 to 9. Number pressures ignored is 36, the waiting time is 12ms, the touch key and 'out on a number of controls at 10 and 24 number of pressures ignored.

Now change the governor to on demand at all as you suggested, leaving the CPU frequency equal min and max.

thanks
[Galaxy S Plus I9001 Android Development] educk:
Hello Christopher!

I think there is something wrong with the persistent RAM console we are currently using. The old RAM console implemented by ivendor worked much better.

When that freeze problem with the 3.4.48 squash update occurred on my device, it generated a kernel panic but there was no last_kmsg inside /proc.

Now, I tried to generate a forced kernel panic by executing this command:

echo c >/proc/sysrq-trigger

it generated a kernel panic, the unit shutdown after 30 sec but after reboot, again, there was no last_kmsg....

Could you please generate a kernel panic on your device to see if the RAM console really does it's job or not? Because I think it doesn't work properly and we won't be able to debug further kernel errors using this persistent RAM console as it is.

Thank you!

Erik
[Galaxy S Plus I9001 Android Development] Christopher83:
Hi Erik,

I successfully got the last_kmsg after the reboot by using the suggested command...
[Galaxy S Plus I9001 Android Development] educk:
OK, thank you!

It means the problem is in my kernel. I don't know what could it be yet, since I enabled ANDROID_RAM_CONSOLE in the kernel config, strange...
[Galaxy S Plus I9001 Android Development] Christopher83:
It's strange, I tried 2 times and both times I got the last_kmsg correctly...

[ 12.625457] yda165: yda165_shutdown : done
[ 12.625579] sdio_alInitiating msm_sdio_al_shutdown...
[ 12.625701] sdio_al: msm_sdio_al_shutdown: msm_sdio_al_shutdown complete.s6e63m0 start s6e63m0_shutdown
[ 12.625915] s6e63m0 lcdc_s6e63m0_panel_off : Draw Black screen.
[ 12.630340] s6e63m0 lcdc_s6e63m0_panel_off + (1,1,1)
[ 12.775573] config_lcdc_gpio_table: gpio_tlmm_config(0xc0850d44)=-5
[ 12.775695] s6e63m0 start s6e63m0_disp_powerdown
[ 12.781250] s6e63m0 lcdc_s6e63m0_panel_off - (0,0,0)
[ 12.781433] Restarting system.
[ 12.781524] BUG: scheduling while atomic: charging_mode/143/0x00000002
[ 12.781646] Modules linked in:
[ 12.781799] [<c0013d0c>] (unwind_backtrace+0x0/0xf8) from [<c072121c>] (__schedule+0x5cc/0x6d4)
[ 12.781951] [<c072121c>] (__schedule+0x5cc/0x6d4) from [<c071f628>] (schedule_timeout+0x228/0x31c)
[ 12.782073] [<c071f628>] (schedule_timeout+0x228/0x31c) from [<c0721c90>] (wait_for_common.constprop.71+0xb4/0x224)
[ 12.782165] [<c0721c90>] (wait_for_common.constprop.71+0xb4/0x224) from [<c00cabcc>] (flush_workqueue+0xe8/0x698)
[ 12.782318] [<c00cabcc>] (flush_workqueue+0xe8/0x698) from [<c0052a98>] (msm_rpcrouter_close+0x94/0xdc)
[ 12.782440] [<c0052a98>] (msm_rpcrouter_close+0x94/0xdc) from [<c00af35c>] (msm_pm_restart+0x8/0xe4)
[ 12.782592] [<c00af35c>] (msm_pm_restart+0x8/0xe4) from [<c000fa68>] (machine_restart+0x34/0x60)
[ 12.782714] [<c000fa68>] (machine_restart+0x34/0x60) from [<c00c7780>] (sys_reboot+0x16c/0x2e0)
[ 12.782867] [<c00c7780>] (sys_reboot+0x16c/0x2e0) from [<c000ee00>] (ret_fast_syscall+0x0/0x30)
[ 12.782958] BUG: scheduling while atomic: charging_mode/143/0x00000002
[ 12.783081] Modules linked in:
[ 12.783233] [<c0013d0c>] (unwind_backtrace+0x0/0xf8) from [<c072121c>] (__schedule+0x5cc/0x6d4)
[ 12.783355] [<c072121c>] (__schedule+0x5cc/0x6d4) from [<c071f628>] (schedule_timeout+0x228/0x31c)
[ 12.783508] [<c071f628>] (schedule_timeout+0x228/0x31c) from [<c0721c90>] (wait_for_common.constprop.71+0xb4/0x224)
[ 12.783630] [<c0721c90>] (wait_for_common.constprop.71+0xb4/0x224) from [<c00d2068>] (kthread_stop+0x44/0x74)
[ 12.783752] [<c00d2068>] (kthread_stop+0x44/0x74) from [<c00cb8d4>] (destroy_workqueue+0x1cc/0x204)
[ 12.783843] [<c00cb8d4>] (destroy_workqueue+0x1cc/0x204) from [<c0052aa0>] (msm_rpcrouter_close+0x9c/0xdc)
[ 12.783966] [<c0052aa0>] (msm_rpcrouter_close+0x9c/0xdc) from [<c00af35c>] (msm_pm_restart+0x8/0xe4)
[ 12.784118] [<c00af35c>] (msm_pm_restart+0x8/0xe4) from [<c000fa68>] (machine_restart+0x34/0x60)
[ 12.784240] [<c000fa68>] (machine_restart+0x34/0x60) from [<c00c7780>] (sys_reboot+0x16c/0x2e0)
[ 12.784393] [<c00c7780>] (sys_reboot+0x16c/0x2e0) from [<c000ee00>] (ret_fast_syscall+0x0/0x30)
[ 12.784484] msm_pm_restart: send PCOM_RESET_CHIP
[ 12.785186] msm: proc_comm: proc comm disabled
[ 12.785247] msm_pm_restart: do nothing!!

No errors detected
[Galaxy S Plus I9001 Android Development] educk:
For sure there is something in my sources... I must find out what's the problem.
[Galaxy S Plus I9001 Android Development] maxbluz:
I can confirm it on my phone too
[Galaxy S Plus I9001 Android Development] chocotermi:
Is it possible that the last kmsg depends from that phone is after reset or after power off? I'm only thinking, I don't know kmsg behavior
[Galaxy S Plus I9001 Android Development] stuffynet:
Hey christopher

Just want to point out a feature that can be implemented in your kernel (hopefully). It is called timer slack (don't know if heard of it, maybe you did).

What does the timer slack feature do?

Timer slacking aims to synchronize applications' and processes' CPU requests. The goal is to wake up the CPU less often in oder to save battery. What you need to know here is the following: waking the CPU up and putting it back to sleep again consumes power. Imagine that four apps wake the CPU up four times each in one second. While without timer slacking the CPU would be woken up 16 times, it is desirable to coordinate the wakeups. If done right, the CPU would wake up less often, effectively allowing power savings and longer sleep periods. This is what timer slacking does.

Apple has recently introduced this feature under the name 'timer coalescing' with their Mac OSX Maverick (link).

More information: How Apple does timer slacking ('Timer coalescing') (Scroll a little down to the diagrams)

Credit for this info goes to @boype from the galaxy nexus development thread and to charmacas for pointing it out.

Boybe's github here

Hope you will make it work. Should have some impact one battery draining.
[Galaxy S Plus I9001 Android Development] Christopher83:
I'll surely try this, thank you very much!